Known issues

The following details existing device issues that have been discovered with other releases. In most cases, a resolution is included to address the issue.

Alcatel Omniswitch

• Full configuration pushes for the working and certified files require FTP to be enabled. Configlets and the running configuration use terminal mode only.

• Cold booting the device will use the configuration stored in /flash/certified/boot.cfg unless it is identical to /flash/working/boot.cfg. If these files differ, the reload working no-rollback timeout command must be issued or configuration changes will fail. This can be done using cut-through.

• The Reboot from Working post-operation on configuration pushes does not warn the user about service interruption.

• Post operations on working and certified configurations may potentially change the operating system version of the device if it is rebooted afterwards. This is due to the use of “copy working certified” and “copy certified working” commands for these operations. It is the user’s responsibility to ensure that configuration content is compatible if the software images in the working and certified directories differ.

• SNMP credential rolls are not written to the certified (startup) configuration, which is a device limitation in the copy command syntax (as detailed in the previous bullet). The commit operation used after account and SNMP rolls uses “copy running working” to avoid copying software images as part of SNMP credential changes.

• The model name is reported differently through SNMP than through terminal: SNMP uses the chassis entry of ENTITY-MIB, while the terminal query uses the “Model Name:” field in the “show system” response, which corresponds to the CMM model.

• No restrictions are enforced on password length.