Management

Access to the Legacy orchestrator web user interface and web services is controlled by means of user accounts and user roles. System administrators manage user accounts and must assign a user role to each account. Each role has a predefined set of p...

By default, Legacy orchestrator uses its own local user accounts to control access to its web-based user interface and its REST API. The Legacy orchestrator web user interface also supports RADIUS-based user authentication. If RADIUS is conf...

Legacy orchestrator can receive SNMP messages (about alarms and other events) from managed elements and send them to various destinations, typically Operations Support Systems (OSS). Legacy orchestrator's support for handling messages vi...

Legacy orchestrator supports SNMPv3. SNMPv3 defines User-based Security Model (USM), a security mechanism that enables per-message authentication and encryption. To use SNMPv3 on Legacy orchestrator, you need to define one or more USM user ...

The Legacy orchestrator data store contains all Legacy orchestrator application data (including all the data displayed in the Legacy orchestrator user interface). The data store is backed up automatically on a regular basis. The factory default se...

Legacy orchestrator keeps a log of actions performed by users in its web interface and of requests made on its web service REST API . This is known as the audit log. Here are a few examples of the user actions that are registered in the audit log...