Skylight sensor control Release Notes 21.12
- 07 Jan 2022
- 9 Minutes to read
- Contributors
- Print
- DarkLight
- PDF
Skylight sensor control Release Notes 21.12
- Updated on 07 Jan 2022
- 9 Minutes to read
- Contributors
- Print
- DarkLight
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
These release notes cover the requirements, new features, and changes for this release of the Skylight sensor: control firmware version 21.12. Please read all the notes prior to installing this firmware version.
Requirements
This firmware version applies to the following products from Accedian:
| Product Name | Product ID | Firmware Name | Image or Firmware File |
|---|---|---|---|
| Skylight sensor: control | sensor control-1000 | VCX_21.12 | VCX_21.12.0_24458_VMWARE.ova |
| Skylight sensor: control | sensor control-1000 | VCX_21.12 | VCX_21.12.0_24458_KVM.tar.bz2 |
| Skylight sensor: control | sensor control-1000 | VCX_21.12 | VCX_21.12.0_24458_SingleDiskVMWARE.ova |
| Skylight sensor: control | sensor control-1000 | VCX_21.12 | VCX_21.12.0_24458_SingleDiskKVM.tar.bz2 |
| Skylight sensor: control | sensor control-1000 | VCX_21.12 | VCX_21.12.0_24458.afl |
Note: This firmware release includes the images needed to deploy the Skylight sensor: control using a KVM or VMware Hypervisor, as well as the .afl upgrade file that is typically part of a Skylight sensor: control release.
Skylight sensor: control 21.12 requires Skylight orchestrator 20.05 as its minimum. Customers using SD Vision must first upgrade to Skylight orchestrator 20.05 before upgrading to Skylight sensor: control 20.05.
Important Notes
Skylight sensor: control version 21.12 limitation for Skylight orchestrator:
The following Skylight orchestrator functions fail when managing devices using IPv6:
- Backup Job
- Restore function
- FW Upgrade/download jobs, FW upgrade function FW Management page
- SAT report
The reason for this limitation is that the updated DropBear requiring command URLs with [ ] for IPv6 address is not supported in the current Skylight orchestrator release.
Workaround: Skylight orchestrator can manage devices using IPv4, otherwise do not upgrade sensor: control until IPv6 is supported in the next release.
Availability of Skylight orchestrator fix: The next Skylight orchestrator release will support command URLs with [ ] for IPv6 address.
Skylight sensor: control upgrades
In Skylight sensor: control 21.12, any module upgrades from firmware versions previous to VCX 2.2 FWSuite (FWSUITE_VCX_2.2_10190) have been blocked, in order to protect against a potential complete loss of connectivity/functionality that cannot be recovered. In order to upgrade a module from an older FWSuite version, an older version of Skylight sensor: control must be used to first upgrade the module to FWSUITE_VCX_2.2_10190:
| Release | Files |
|---|---|
| Skylight sensor: control 21.12 | VCX_21.12.0_24458 FWSUITE_VCX_21.12_15916 |
| Skylight sensor: control 20.11.1 | VCX_20.11.1_23836 FWSUITE_VCX_20.11.1_15890 |
| Skylight sensor: control 20.11 | VCX_20.11_23687 FWSUITE_VCX_20.11_15890 |
| Skylight sensor: control 20.05 | FWSUITE_VCX_20.05.0_22954 |
| Skylight sensor: control 19.12 | FWSUITE_VCX_19.12_15659 |
| Skylight sensor: control 19.07 | FWSUITE_VCX_19.07_15467 |
| VCX 2.7 | FWSUITE_VCX_2.7_15346 |
| VCX 2.6.0.1 | FWSUITE_VCX_2.6.0.1_15306 |
| VCX 2.6 | FWSUITE_VCX_2.6_15213 |
| VCX 2.5.0.2 | FWSUITE_VCX_2.5_15076 |
| VCX 2.5 | FWSUITE_VCX_2.5._15076 |
| VCX 2.4 | FWSUITE_VCX_2.4_11337 |
| VCX 2.3 | FWSUITE_VCX_2.3_10553 |
| VCX 2.2 | FWSUITE_VCX_2.2_10190 |
Skylight sensor: control upgrade consideration
When upgrading the Skylight sensor: control software, the modules firmware is not upgraded automatically. It is not recommended to operate Skylight sensor: control with a different module firmware version since the functionality is limited to management. The management includes:
- Module discovery
- Connect to module and have a management Link state
- Upgrade module firmware version using feature suite
- Update module interface (IP address, VLAN, and DHCP)
CAUTION: The upgrade process was hardened in VCX 2.7. Under specific circumstance the module upgrade can still fail. This happens if the module management is lost and the module performs an automatic rollback. The module can brick if the power is lost in a critical short time period. This was seen in a lab environment only and never reported by a customer.
Before doing the upgrade, it is recommended to enable Extra Reconnection Delay with the previous release (refer to the Skylight sensor: control User Manual, section 4.3, “Adding Remote Devices” for more details on how to enable Extra Reconnection Delay).
The downgrade is still executed using the previous software that still has the update process deficiencies. The downgrade can still cause remote devices to fail and should be avoided at the exception of VCX 2.5.0.2 and VCX 2.6.0.1 for which the downgrade is supported without issue.
It is not recommended to change any other module configuration when operating with a different firmware version. Changing the configuration could result in unknown behavior. A factory reset using AMD could be required in some cases. In a future release, the Skylight sensor: control software will prevent changing configuration for modules running a different firmware version.
For cases where all modules cannot be upgraded at the same time, it is recommended to run different Skylight sensor: control instances with different software versions. Modules to be upgraded should be moved between Skylight sensor: controls.
When downgrading Skylight sensor: control software, the modules firmware version shall also be downgraded. The downgrade process shall follow these steps in order to successfully downgrade Skylight sensor: control software and modules firmware. Note that downgrades are not recommended (see CAUTION above).
CAUTION: The downgrade is still executed using the previous software that still has the update process deficiencies. The downgrade can still cause remote devices to fail and should be avoided.
Before doing the downgrade, it is recommended to enable Extra Reconnection Delay with the previous release (refer to the Skylight sensor: control User Manual, section 4.3, “Adding Remote Devices” for more details on how to enable Extra Reconnection Delay).
Scenario 1: downgrade using Skylight sensor: control rollback
- The modules firmware must be downgraded first using the newest Skylight sensor: control software.
- Perform Skylight sensor: control rollback.
Scenario 2: downgrade using a different Skylight sensor: control instance
- The modules firmware must be downgraded first using the newest Skylight sensor: control software.
- Delete modules from the newest Skylight sensor: control instance.
- Discover the modules using the older Skylight sensor: control instances.
Firmware Version 21.12_24428 (2022-01-07)
New Features and Enhancements
Removed License enforcement for license for Skylight sensor: control
Removed dependencies on Skylight director license server (SDLS), so that the license enforcement is no longer in Skylight sensor: control.
Updated dropbear SSH to latest
Updates to dropbear SSH to remove any vulnerabilities or security issues.
Removed web help
Web help has been removed from the firmware and added to the docs.accedia.io documentation website.
Accedian MIBs to include Flex 100 sub OIDs
Integration of new private sub OID in the Accedian MIBs to accommodate the introduction of Flex 100 in Accedian's
Update OpenSSL Library
Updates to SSL library to support TLSv1.3 to include all 5 ciphersuites.
System capabilities
The Skylight sensor: control offers the following system capabilities:
| Feature | Maximum | Changes in Skylight sensor: control 21.12.1 |
|---|---|---|
| Remote Device | ||
| Remote devices configured and supported | 1500 | |
| Remote device ports | 6000 | |
| Interfaces, remote devices | 3000 | |
| Discovery | ||
| Discovery instances | 500 | |
| Discovered remote devices | 2000 | |
| Skylight sensor: control Local Port & Interface | ||
| Local ports (typically referred to as LOCAL-xyz) | 10 (including the Management port) | |
| Skylight sensor: control local route | 4092 | |
| Interfaces, local ports | 100 | |
| CFM | ||
| Number of modules supporting CFM MEP session | 500 | |
| CFM MEP session per second generation module | 8 | |
| CFM Maximum number of Remote MEP | 99 | |
| CFM MEP smallest interval | 1 second | |
| Number of CFM MEP per Skylight sensor: control | 4000 | |
| Number of Packet loss per Skylight sensor: control | 4000 | |
| Number of Packet loss per second generation module | 8 | |
| Number of DMM session per Skylight sensor: control | 4000 | |
| Number of DMM session per second generation module | 8 | |
| DMM smallest interval | 1 second | |
| Number of SLM session per Skylight sensor: control | 4000 | |
| Number of SLM session per Skylight sensor: control | 4000 | |
| Number of SLM session per second generation module | 8 | |
| SLM smallest interval | 100 ms | |
| SAT | ||
| SAT Traffic Generation configuration (up to four flows) | 1000 | |
| SAT Traffic Generation execution (up to four flows) | 500 | |
| SAT Test Suites in the system (one test suite per device) | 500 | |
| Y.1564 (8 flows) | 500 (tested 4) | |
| SAT reports | 500 | |
| TWAMP reflection instances (module) | 1500 | |
| TWAMP reflection, stateful per module | 16 | |
| DMM reflection instances (module) | 1500 | |
| Loopback reflection per remote device | 2 | |
| Flowmeter | ||
| Flowmeter flows supported per remote port | 28 per device | |
| Flowmeter flows supported per Skylight sensor: control instance | 4000 | |
| Flow broker | ||
| Flow broker Analyzers | 100 | |
| Flow broker Analyzers in an Analyzer set | 4 | |
| Flow broker rules per Skylight sensor: control | 1000 | |
| Flow broker capture bandwidth per 1G module | 300 Mbps with 1 ms RTT 50 Mbps with 20 ms RTT | |
| Flowbroker capture bandwidth per 10G module | 700 Mbps with 1 ms RTT 100 Mbps with 8 ms RTT | |
| Flow broker capture bandwidth per Skylight element: FSX | 100 Mbps with 1 ms RTT | |
| Flow broker ERSPAN streaming bandwidth | 200 Mbps | |
| Flowbroker PCAP streaming bandwidth | 150 Mbps using SCP 500 Mbps using FTP | |
| Flowbroker Port Streaming bandwidth | 150 Mbps | |
| Flow Probes | ||
| PM Accuracy direct actuation (i350) | 50 us | |
| NFV PM Accuracy | 15 us | |
| PM Accuracy with SR-IOV | 200 ms | |
| Skylight sensor: control Actuator maximum number of probes | 4000 | |
| Skylight sensor: control Actuator maximum number of packets per second (receive and transmit) | 80 K in TX and 80 K in RX | |
| Maximum number of probe reflection | 4000 | |
| Maximum number of probes per module | 2000 | |
| Maximum number of packets per second (receive and transmit) per module | 40 K in TX and 40K in RX | |
| PPS accuracy | ± 1.0 % | |
| NFV TWAMP support | Yes | |
| NFV ETH-DM support | Yes | |
| NFV UDP Echo support | Yes | |
| NFV ICMP Echo support | Yes | |
| NFV ETH-VSP support | Yes | |
| NFV ETH-LB support | Yes | |
| NFV CFM maximum number of PPS | E-Line 500 remote device per Skylight sensor: control. E-LAN 100 remote device per Skylight sensor: control. CFM instances: E-LAN : 1 MEP (each 99 RMEP) per RD 1 SLM per MEP per RD 1 DMM per MEP per RD. Tx: 11 pps, RX: 111 pps per RD CFM instances: E-LINE : 8 MEP per Module 6 SLM@10pps for 1 MEP per Module 8 DMM@1pps for 1 MEP per Module Tx: 76 pps, Rx: 76 pps per Module | |
| NFV Tunnel | ||
| Packet loss requirement | 10^-6 | |
| RTT requirement | Validated with RTT between 5 ms and 50 ms | |
| Virtual-Connection | ||
| VCE with IP domain enabled | 500 | |
| VCE without IP domain | 50000 | |
| Number of VCEs route | 2500 | |
| VCA | 30000 | |
| Synchronization | ||
| ARTS | 500 | |
| PTP TC layer-2 | Yes (Ant2, Ant 10G, Nano2 Copper and Nano2 Optical) | |
| SyncE | Yes (Ant2, Nano2 Copper and Nano2 Optical) | |
| No (Ant 10G) | ||
| PTP OC for module | NA | |
| Service Creation | ||
| Policies and traffic filters per remote device | 10 for second generation | |
| Bandwidth Regulator per second generation module | 16 | |
| Bandwidth Regulator per Skylight sensor: control | 24000 | |
| PCP CoS mapping per port | 1 | |
| CoS mapping per Skylight sensor: control | 50 | |
| DSCP CoS mapping per port | 1 | |
| Alarms | ||
| Number of trap alarm per second | 1000 | |
| Users | ||
| Local users | 15 | |
| User groups | 8 | |
| Sessions | ||
| CLI sessions | 5 | |
| WEB UI sessions | 15 | |
| Total maximum sessions | 20 | |
| Supported Filters | ||
| Layer-2 filter | 6500 | |
| Ipv4 filter | 6500 | |
| Ipv6 filter | 6500 | |
| Total maximum sessions | 19500 |
Skylight sensor: control 21.12 Lifecycle
This section lists the planned lifecycle dates of this software release. See the table below outlining the following milestones:
| Milestone | Description | Date |
|---|---|---|
| General Availability | Date where the product is available for general field deployment for both new installations and upgrades. | 2022-01-07 |
| End of Security Support | Date where security patches will no longer be delivered for this release. Any correctives for security defects required after this date will be delivered using the next major release of the software. | Next Major Release |
| Last Time Buy / Last Time Ship | Date where this release can no longer be purchased from Accedian. | 2024-01-07 |
| End of Product Support | Date where functional patches will no longer be delivered for this release. Any correctives for functional defects required after this date will be delivered using the next major release of the software. | 2024-01-07 |
| End of Technical Support | Date where technical assistance is no longer available from the Accedian Technical Assistance Center for this release. | 2027-01-07 |
© 2024 Accedian Networks Inc. All rights reserved. Accedian®, Accedian Networks®, the Accedian logo™, Skylight™, Skylight Interceptor™ and per-packet intel™, are trademarks or registered trademarks of Accedian Networks Inc. To view a list of Accedian trademarks visit: http://accedian.com/legal/trademarks/.
Was this article helpful?
