Administrative Operations

This article provides information about accessing and navigating in Legacy orchestrator. Supported Web Browsers The Legacy orchestrator user interface is entirely web-based. The user interface has been tested with the following web browsers ...

This article explains how to add an interface to a virtual port of a Legacy orchestrator appliance. Legacy orchestrator supports eight ports (eth0 to eth7): Normally, eth0 is the management port. It can only be edited. See Editing the MGMT I...

This article explains how to change the password of the visionems account in Legacy orchestrator. This procedure is highly recommended. It is important to not lose the password after it has been changed from the factory default. Procedure Requir...

The retention period for the performance session data collected by Legacy orchestrator is the maximum amount of time that the data is kept on Legacy orchestrator before it is purged. Older data (stored for longer than the retention period) is auto...

With the disk configuration done, the deployment profile can now be assigned to the virtual appliance. This must be done with the application turned off. The assignment of the deployment profile will perform the following actions: Configure ...

This article explains how to stop Legacy orchestrator software by stopping the Legacy orchestrator application server. This action stops the processes that provide the business logic and graphical user interface. It should be noted that the Legacy ...

This article explains how to stop the Legacy orchestrator data store on an appliance. Procedure Requirements A. This procedure must be executed from the console of the Legacy orchestrator appliance. B. This procedure must be executed as the v...

The article explains how to restart Legacy orchestrator software on a appliance. The restart command stops and starts the Legacy orchestrator software. This procedure is typically used after a change to the system configuration. Procedure Requ...

This article explains how to start the Legacy orchestrator data store service. Procedure Requirements A. This procedure must be executed from the console of the Legacy orchestrator appliance. B. This procedure must be executed as the visionem...

This article explains how to start Legacy orchestrator software. Procedure Requirements A. This procedure must be executed from the console of the Legacy orchestrator appliance. B. This procedure must be executed as the visionems user. To ex...

This article explains how to power off an appliance safely. Procedure Requirements A. This procedure must be executed from the Legacy orchestrator console. B. This procedure must be executed as the visionems user. To execute this procedure, ...

This section explains how to configure the Legacy orchestrator appliance to create regular backups and how to perform recovery operations. Two types of backup can be made on a Legacy orchestrator appliance: Data store backup Captures the dy...

To provide redundancy, the network operator can maintain a secondary Legacy orchestrator system that is ready to take charge if the primary Legacy orchestrator system fails. Legacy orchestrator supports two redundancy methods: Warm Standby Re...

This article contains the procedures required to set up the primary Legacy orchestrator appliance to prepare it for standby operations. Procedure Requirements A. Certain procedures in this section require access to the primary Legacy orchestrato...

The secondary appliance must be prepared in advance for standby operations. Procedure Requirements A. Certain procedures in this section require access to the secondary Legacy orchestrator appliance through its web user interface. Other procedur...

If the primary Legacy orchestrator appliance is unavailable, service can be recovered by switching to the secondary appliance as explained in this section. Restoring the Data Store on the Secondary Appliance The first step is to restore the most...

After maintenance or repair is done on the primary Legacy orchestrator appliance, you may want to put it back into service. The following procedures explain how to put the primary Legacy orchestrator appliance back in service. Making a Backup of t...

Introduction This article explains how the Legacy orchestrator Hot Standby Redundancy feature works and covers the requirements for deploying the feature. Redundancy ensures continuous operation of the Legacy orchestrator system by various hardwar...

Configuring redundancy involves the following tasks: A. Obtain all the information that you will need for the procedures. See Information Needed to Configure Hot Standby Redundancy . B. Ensure that all required appliances are installed. See ...

Three commands allow you to view key information about the redundancy feature: redundancy show configuration redundancy show statistics redundancy show status. Viewing Redundancy Configuration Enter the following command to view detail...

After the redundancy feature has been configured and is enabled, you can control its behavior using the redundancy control commands: CAUTION : The commands below MUST only be run on one of the sites. Running commands on both sites simultaneous...

The Hot Standby Redundancy requires a license. The license file specifies the MAC addresses of the Legacy orchestrator appliances for Site-A and Site-B. Two commands allow you to manage the license for the redundancy feature: redundancy licen...

After the redundancy feature has been configured, enabled and started, you can check that it is operating normally with the redundancy test command. This command is executed from the appliance console. For more information about the appliance cons...

Tab-completion help is available for the redundancy commands on the Legacy orchestrator command line. The following tables of redundancy commands list all the parameters and possible parameter values. redundancy config redundancy config vir...

The following alarms related to redundancy may be raised. They are visible in the Appliance Monitor CLI on both sites and in the Legacy orchestrator web user interface. © 2024 Cisco and/or its affiliates. All rights reserved.  ...

The redundancy feature writes a log of activity and error messages. You can find the log file that contains entries about redundancy is located in the following directory on the appliance for the active site: /opt/accedian/skylight/logs/hamon.lo...

Overview This article explains how to move a virtual machine (VM), of a site on Hot Standby Redundancy system, to another server. Key Terms The following key terms are used throughout this article: Original site : Existing site that must ...

This article will provide guidelines related to checking the disk’s IOPS on the system against the requirements. Procedure Requirements This procedure must be executed as the visionems user. To execute this procedure, you must know the account...

Performance sessions are ongoing measurements set up between two termination points: a sender (a Provider Connectivity Assurance Sensor Control) and a reflector (any device with the required capabilities). They capture a wide range of metrics that c...

The Legacy orchestrator command line interface is called Appliance Monitor. From the Appliance Monitor command line, you can access another set of commands (called mgr-commands) that are used primarily to set up performance sessions. To create per...

The deployment tool is a utility that makes it easy to create sender endpoints, reflector endpoints, and sessions. You use an Appliance Monitor command (sdmm-deploytool) to run the deployment tool. Typically, the deployment tool is used to create ...

Collection and export of performance monitoring data can be done by Legacy orchestrator. The collection portion of the process involves establishing a permanent SSH connection to/from orchestrator and storing the retrieved data points into binary fi...

The metrics export process is divided into the CSV Producer and the CSV Exporter. The article that follows explains the characteristics of each component. CSV Producer The producer’s role is very straight forward: it periodically looks for any n...

The Metrics Collection feature allows Legacy orchestrator to collect performance metrics from Provider Connectivity Assurance Sensors via dedicated data streams. This article provides engineering guidelines related to metrics collection. Provider ...

This article provides further engineering guidelines related to metrics collection from the Provider Connectivity Assurance Sensor Control controller. Assurance Sensor Control Data Retention Under normal operating conditions, Assurance Sensor Co...

Legacy orchestrator appliances come with a minimal set of services and software that are required for operation. Several precautions have been taken to ensure the security of the system in its default configuration. Some customers may want to furt...

Procedure Requirements This procedure must be executed from the appliance console. This procedure must be executed as the visionems user. To execute this procedure, you must know the account’s credentials. Procedure Steps To change t...

This procedure configures the appliance to limit the age of the password for the visionems user to 90 days. Procedure Requirements This procedure must be executed from the appliance console. This procedure must be executed as the visionems...

This procedure explains how to disable the emergency support account. This account is meant to be used by Technical Support if the visionems account password is lost. CAUTION: Disabling the support account will limit the ability of the Techni...

This article explains how to configure the greeting message for the Legacy orchestrator console. Procedure Requirements This procedure must be executed from the appliance console. This procedure must be executed as the visionems user. To ex...

Legacy orchestrator keeps a log of actions performed by users in its web interface and of requests made on its web services REST API . Here are a few examples of the user actions that are registered in the log: Successful login Addition of a ...

Log File Locations Functional Logs Auditing Logs These are logs related to the actions performed by users in the web interface and as well as logs of requests made on the web services REST API. The following are examples of user actions that...

This article provides information regarding an SNMP agent in relation to Legacy orchestrator and explains how to set up an SNMP trap configuration job that can be applied to all managed Provider Connectivity Assurance Sensors. SNMP Agent on Legacy...

This article provides the procedures required to deploy a signed certificate to the application server of the Legacy orchestrator. By default, the product ships with a self-signed certificate. If your organization prefers to use a trusted certific...

Introduction You can use the Rsync protocol to transfer Provider Connectivity Assurance metrics collection files from Legacy orchestrator to an external server. Rsync offers many advantages over SFTP: It supports the transfer of the same file...

Legacy orchestrator only supports public and private keys in PEM format. However, when generating the SSH key on Ubuntu 20.04, it is not in PEM format. To generate the SSH Key Access SSH to the Legacy orchestrator via port 22 . Ente...

The following table provides a description of all system error codes and associated error messages. © 2024 Cisco and/or its affiliates. All rights reserved.   For more information about trademarks, please visit: Cisco tradema...

Software Specifications This appendix explains how to replace a broken endpoint (hardware) in a running supervision case. All endpoints are assigned a unique node identifier (NodeId). The Node ID is initially set to the same value as the unit iden...

Under normal operating conditions, the Legacy orchestrator webserver configuration file is preserved and maintained in its full integrity. Under certain scenarios such as hard reboots or disk full situations, it is possible that this configuration ...

The following procedure for Legacy orchestrator virtual machine is used to increase the number of concurrent users in Legacy orchestrator to 100 (for VM version 23.04.1 and prior) or 250 (for VM version 23.12). The following steps are required: ...

Overview Roadrunner runs in a Docker container and is the interface between Legacy orchestrator and Provider Connectivity Assurance. This connection allows you to: Receive performance monitoring data from orchestrator and forward it to Prov...

Note: The commands may have changed and need to be validated with the 3rd party. Depending on vendor of the TWAMP-Control server (reflector) the Provider Connectivity Assurance solution TWAMP solution has implemented operation in two disti...

Preparing to Migrate This procedure contains instructions on how to migrate from one of the following releases: Legacy orchestrator virtual machine (23.12 or prior version) to the same version of Legacy orchestrator Docker Legacy orchestrato...

Use the Command Line Interface (CLI) of the Appliance Monitor to enable or disable Transport Layer Security (TLS) 1.0 or 1.1 configuration for reverse proxy. For command descriptions, see the Appliance Monitor Command Reference. for virtual ma...

This article details the process of maintaining devices on Legacy orchestrator, from the On First Login state to the In Service state, after performing a factory reset or managing the initial installation of the devices. This procedure applies...