Legacy Orchestrator 24.09.1 Release Notes

Overview

Cisco is pleased to announce the 24.09.1 release of Provider Connectivity Assurance Legacy Orchestrator (formerly Accedian Skylight orchestrator). These release notes cover the new features, changes, and corrected issues for Legacy Orchestrator version 24.09.1. Read the release notes before installing this firmware version.

For further information, questions, or clarifications regarding this release, please contact the Technical Assistance Center (TAC) at skylight_tac@cisco.com.

The following topics are addressed in this document:

• New Features: Covers the new features introduced in this release.

• Corrected Issues: Lists issues that have been corrected in this version of the software.

• Technology Support: Covers the applicable product information.

• Upgrade Paths: Details the supported upgrade paths for this release.

• Deployment Considerations: Covers general limitations of the current release.

• Release Lifecycle: Lists the planned lifecycle dates of this software release. Includes table with milestones.

For more information, see the Legacy Orchestrator documentation.

New Features

Legacy Orchestrator 24.09.1 introduces the following features and enhancements.

Enhanced Device Backup Information

The Legacy Orchestrator Backup & Restore tab for devices includes additional information for increased clarity; the firmware version of each device is visible at the time the backup was taken, providing users with essential data for system management and troubleshooting.

Provider Connectivity Assurance Sensor Compatibility

Legacy Orchestrator has been enhanced to be backward compatible with Provider Connectivity Assurance Sensors, including release 25.07 for Assurance Sensors LT, LX, and GT.

Provider Connectivity Assurance Sensor Control Compatibility

Legacy Orchestrator has been enhanced to operate with Assurance Sensor Control releases 25.07 and 25.07.1. Please note that Legacy Orchestrator releases prior to release 23.04 are unable to provide RTT values for TWAMP and ETH-DM using Sensor Control releases 22.12 or later.

If you intend to deploy Sensor Control 22.06 - 24.x to your network, please ensure you have first upgraded to Legacy Orchestrator release 24.09 or later.

If you intend to deploy Sensor Control 25.07 or 25.07.1 to your network, please ensure you have first upgraded to Legacy Orchestrator release 24.09.1 (this release).

See the Assurance Sensor Control Release Notes 25.07.1 for more information.

Corrected Issues

The following key issues have been addressed in Legacy Orchestrator 24.09.1.

Legacy Orchestrator 24.09 HA Mode Fails to Start on Ubuntu 22.04.5

Legacy Orchestrator 24.09 in High Availability (HA) mode could not start on Ubuntu 22.04.5 due to a compatibility issue with the DRBD driver and the newer Ubuntu kernel. This prevents the redundancy feature from working.

Technology Support

These release notes apply to the following product:

The following table lists key functionality of Assurance Sensors, Assurance Sensor Control, Assurance Sensor Modules, and Assurance Sensor SFPs supported by Legacy Orchestrator 24.09.1.

Supported in Legacy Orchestrator Version 24.09.1

* CLI step support for Device Commissioning
** Y.1564 with flow template support

Upgrade Paths

The upgrade to Legacy Orchestrator version 24.09.1 requires that you are running a system with one of the following previously-installed software versions. It includes support for both Ubuntu and Red Hat operating systems.

Docker running:

• 24.09 5K profile

• 24.09 15K profile

• 24.09 30K profile

• 24.09 60K profile

Detailed procedures for upgrading to this release are provided in Upgrading to Legacy Orchestrator Docker 24.09.1.

IMPORTANT: You cannot upgrade hardware appliances to version 24.09.1.

For customers running SkyLIGHT Director software on hardware appliances, a rehoming procedure is available that allows the transfer of the software and its configuration to a new virtual machine. That said, rehoming process is no longer required since all hardware appliances have been retired at this point.

Detailed procedures for rehoming on a virtual appliance are provided in the Features and User Material subcategory titled Virtual Machine Rehoming for Releases Prior to 20.05.

Deployment Considerations

Docker Environment Guidelines

The engineering guidelines of the product must be respected. The Docker host must meet the requirements stated in Docker Deployment.

Failure to respect these engineering settings can lead to application downtime and possible data loss.

The Docker host configuration related to interface IP addresses, hostname, NTP server, additional disks (add, format, mount), is configured via standard command of Ubuntu without any procedure or script to support them.

Device Interoperability

The following section details the firmware releases that are known to interoperate with this release of Legacy Orchestrator. Please refer to the Legacy Orchestrator Administrative Operations documentation for a listing of supported functions for each firmware version.

Support for sensor element software releases 4.7.x, 5.4.x and 5.5.x is deprecated. Plans should be put in place to upgrade your performance elements to more recent versions.

For the releases mentioned below, support for maintenance releases is also included.

Note: The backup job and firmware update features are not supported for Skylight Element GE. This limitation affects these legacy devices because they only support FTP and do not support SFTP.

HTTP Interface

The HTTP interface of Legacy Orchestrator is no longer supported for GUI operations or for REST and XML APIs. Web service clients are strongly urged to switch to the more secure HTTPS protocol.

Customers using browsers or APIs with HTTP protocol on port 6080 will automatically be redirected to HTTPS protocol on the same port (6080). This means no firewall changes are required as part of this change.

Please ensure all integrations and client applications are updated to utilize HTTPS to maintain security and functionality.

Disk Sizing for New Installations

The default image size for Legacy Orchestrator is now 150 GiB. This image is large enough to support small networks of under 100 network elements and 1,000 performance sessions. For larger networks, the disk size of the image must be increased. This can be achieved via VMware and KVM management tools.

Example disk sizing:

• For 5,000 elements and 20,000 performance sessions with Round trip delay mode disabled: 370 GiB is recommended

• For 5,000 elements and 20,000 performance sessions with Round trip delay mode enabled: 430 GiB is recommended

• For 52,000 performance sessions with Round trip delay mode disabled: 482 GiB is recommended

• For 52,000 performance sessions with Round trip delay mode enabled: 638 GiB is recommended

• For 125,000 performance sessions with Round trip delay mode disabled: 920 GiB is recommended

• For 125,000 performance sessions with Round trip delay mode enabled: 1295 GiB is recommended

Please consult the Legacy Orchestrator documentation for sizing guidelines and for procedures on how to increase the disk size.

IPv4 Addresses for Hot Standby

The hot standby feature requires the use of IPv4 addresses for its configuration. For planning purposes, it should also be noted that hot standby configuration requires three (3) distinct subnets for the management, data replication, and heartbeat functions.

IPv6 addresses can be used in addition to these IPv4 interfaces for connectivity to the application interfaces (web and REST APIs) and devices being managed. IPv4 addresses are only required strictly for the hot standby functions.

If you wish to make use of this feature, please contact your Solution Engineering representative to initiate network planning activities.

XML Interface Deprecated

The XML interface is deprecated and has been phased out. Northbound systems are urged to migrate to the CSV file format for PM data reception.

Manager Module Interoperability

Conflicts will arise if both Manager Module and Legacy Orchestrator are configured to manage the same Assurance Sensor Control. Legacy Orchestrator will effectively take over all management of the performance sessions for the Assurance Sensor Control, and leave the Manager Module with un-acquired supervision endpoint.

Using this release to add Manager Modules as managed elements is not recommended.

Manager API

The performance session management calls defined at the /nbapi REST endpoint were introduced in SDV 1.6 to duplicate the calls present in the Skylight Director Manager Module. This endpoint was preserved in a backwards compatible fashion to allow REST API clients of the Manager Module to seamlessly switch to the Legacy Orchestrator.

This endpoint is to be considered capped. Any new features pertaining to performance session management will be implemented using the /nbapiemswsweb REST endpoint in future releases.

CLI Additions and Changes

The CLI command set of the appliance monitor interface was enhanced to duplicate the mgr-commands that are present in the SkyLIGHT Director Manager module.

These commands were preserved in a backwards compatible fashion to allow customers familiar with the Manager Module command set to migrate to the Legacy Orchestrator.

This command set is to be considered capped; no new features will be developed on the CLI functionality.

Browser Support Limitations

The minimum recommended screen resolution to operate Legacy Orchestrator is 1360 x 768. Lower resolutions will not provide an optimal experience.

Performing a zoom on your display is not recommended due to incompatible implementations with browsers. If a zoom must be applied, please use a Firefox browser as it has the most standard support for this function.

Due to issues with browser compatibility mode and web sockets, Internet Explorer is no longer supported. Please use Google Chrome (version 70 or higher) or Firefox (version 52 or higher) to access the Legacy Orchestrator web interface.

For Windows users, it is also recommended to leave the scale and layout option of the Display settings at a value of 100%.

Restoring Virtual Machine Configuration Backups

Configuration backups of the virtual machine (done via the configuration export command) are not portable from release to release. That is to say, a configuration backup from a 1.6 system should not be used to restore a 19.12 system. Unexpected behavior may occur.

Please ensure that configuration backups are restored on systems running the same release from which the backup was taken.

Metrics Collection CSV Filename Timestamp

In order to align with the CSV filename convention of all other Cisco Provider Connectivity Assurance products (Assurance Sensor Control and Assurance Sensors), this naming strategy is changed in Legacy Orchestrator. The timestamp in the CSV filename represents the time when the file was created.

In all cases, the timestamps of the metrics themselves (present within the content of the file) represent the time of when the metric was produced. Only the timestamp contained in the CSV filename is impacted by this change.

Vision Collect Streaming Limitations on 6.4.1.2 and 6.4.2

When using release firmware 6.4.1.2 with Vision Collect, a disconnection from Legacy Orchestrator may incur data loss. The data retention periods are not respected and data loss can occur after a few seconds of disconnection.

When using firmware release 6.4.2 in Skylight elements in high resolution mode with packet loss greater than 10% of the management network, some reporting periods may be lost. Please ensure a reliable management network is in place.

These issues are corrected in Skylight element firmware releases 6.4.3 and higher.

The First Result Records for a New Session Are Skipped by CSV Export

When the CSV producer detects a new performance session, it marks its data for extract from the first time it views the session. If the CSV producer is configured to run every five (5) minutes, this can mean that the first five minutes of result data for a new session will not be exported.

This is expected behavior; all performance data after this initial detection phase will be captured by the CSV producer.

Number of Acceptable Firmware Loads

Before upgrading or starting app_server on Legacy Orchestrator, you must validate the number of acceptable firmware loads based on the specific profile of the system and upgrade version.

Legacy Orchestrator Profile and Acceptable Firmware Loads

Note: When the requirements from the table above are met, the upgrade can be performed and the system will restart. After the system restarts, the partition can be checked. The partition must have at least 1 GB of free space remaining.

Result Records for Sync Sessions Are Not Exported in Real Time

Sync sessions are not properly aligned with CSV export. Results are not being exported in real time as Assurance Sensor Control is delivering measurement results and Legacy Orchestrator is generating CSV files at the exact same time.

If the CSV producer is configured to run every five (5) minutes and sync session has five (5) minute interval, this can indicate that result data for that session will be exported five minutes late.

Memory Limitations

In the event of an excessive number of simultaneous commands being executed, it is recommended that JVM memory be increased.

FTP Support

Support for the FTP transfer method has been removed for the functions below:

• CSV export

• Inventory export

Please ensure the FTP export method is not used on Inventory Export and CSV Export before upgrading.

Device Password Management Considerations

When supporting or upgrading devices, be aware of password management requirements and potential limitations that may affect device access and integration.

• When supporting Assurance Sensor Control 24.09 or later and Assurance Sensors 24.07 or later, users may not be aware when a device password change is required. As a result, the device may remain in-service but not function properly because most commands are disabled in Legacy Orchestrator. To change the password, users must either manually access the device(s) via Web GUI or CLI or follow the procedure in Changing Default Password for Devices to update the password via CLI set on Legacy Orchestrator.

• When either Assurance Sensor Control or Assurance Sensors running version 25.07 or later has an expired password, the device will be out of service, and users may not be notified in advance. To change the password, access the device directly (via Web GUI or CLI). Alternatively, you can disable the password policy. Disabling the policy prevents password expiry for the credential being used to manage the device on Legacy Orchestrator.

• It is not possible to change the password for Assurance Sensor Control or Assurance Sensors running version 25.07 or later during the first login if accessing through a reverse proxy. To change the password, access the device directly (via Web GUI or CLI) or follow the procedure in Changing Default Password for Devices to update the password via CLI set on Legacy Orchestrator.

24.09.1 Lifecycle

This section lists the planned lifecycle dates of this software release. See the table below outlining the following milestones: