Cisco LX-S 25.07.4 Release Notes

These release notes cover the requirements, new features, and changes for the Cisco® LX-S firmware version 25.07.4.

We highly recommend that you read all release notes prior to installing this firmware version.

For more information, see: Cisco LX-S Features and User Material

Requirements

Cisco LX-S 25.07.4 requires Crosswork Assurance 25.7.250 or later, and Sensor Management 25.07.1-LTS or later.

Software files are available from the Cisco Software Download page. You must sign in with valid customer credentials to access the page.

Operational Considerations

Be aware of these operational considerations:

• IMPORTANT: If you are downgrading the firmware without performing a factory reset, you will not be able to connect to the board via CLI or WEB interfaces.
• IMPORTANT: Prior to upgrading the firmware on a unit where the History Buckets feature is enabled, certain precautions may need to be taken to prevent a loss of history data during the upgrade. Refer to ATRC-B10797 for details.
• In a G.8032 ring configuration, the Assurance Sensor LX-S supports a maximum of 62 policies on the LAG port (i.e. policies that govern how traffic is dropped from the ring to UNI ports). This limitation does not apply to the UNI ports (i.e. policies that govern how traffic is added to the ring) unless the VLAN-tagged customer traffic is passed transparently from the UNI port to the ring through one-to-one mapping.
  One way to avoid this limitation and maximize the number of usable UNI policies is to encapsulate multiple customer VLANs (coming from the UNI) under a single service provider VLAN on the ring. Doing so reduces the number of policies required by the LAG port.
• Redundant Parameter Handling: If you enter redundant parameters in a command line, the system applies only the value of the last instance. For example, in the command mode edit syslog-ng enable syslog-ng disable, the system applies the final parameter value syslog-ng disable.
• When the system starts and PCA-AAA is not yet configured, the pca-aaa-client show connection status command intentionally displays the default value of OK for last token status and last auth request, and 0D:00H:00M:00S for next token update. In contrast, similar parameters for the pca-aaa-client show session status command, such as Last status and Uptime, are empty.
• Safari is not a supported browser. Accessing the application with Safari may result in limited functionality or unexpected behavior.

New Features and Enhancements

None

Corrected Issues

This release corrects the following issues:

RADIUS Login Returns Viewer-Only Access Instead of Admin Rights

RADIUS authentication assigns viewer-only access instead of administrative rights, even when the server returns Service-Type = Administrative-User. The RADIUS reply includes a mandatory Message-Authenticator attribute (Type 80).

Release Lifecycle