Specifications

Known issues with
firmware v4.7 fdr 35
28
6.2.17. LNXNM-OT: RmonDeleteRow: . . .can't fetch
variable (no such).
(BZ#: 8625)
Description: On module removal and re-insertion, this is expected behavior. On removal the module
RMON settings in the LNXNM-OT are removed, but they persist in MegaVision. When the settings are
polled, the error is seen until the RMON settings are available in the LNXNM-OT.
Suggested Work-Around: None. This is expected behavior.
Customer Impact: Minimal.
Corrective Action: Message level is changed from warning to debug level.
6.2.18. LNXNM-OT: Upgrading form v4.0 to v4.7 may
affect DMR3G mapping
(BZ#: 8796)
Description: When upgrading a v4.0 NM to v4.7 software in a chassis with a DMR3G module, the
mapping commands are not translated correctly if user issues a restart cold command instead of a
restart upgrade command.
Suggested Work-Around:
It is recommended that users issue a restart upgrade command following a software upgrade from
v4.0 to v4.7.
If user needs to issue a restart cold, then the following procedure should be applied:
1- Upgrade from v4.0 to v4.3
2- Issue write file command
3- Upgrade from v4.3 to v4.7
4- Issue restart cold
Customer Impact: Moderate.
Corrective Action: This issue will be addressed in future software upgrades.
6.2.19. SSH session denied due to low available memory.
(BZ#: 9154)
Description: A Telnet session may allocate significantly more system memory than normal. This
blocks the initiation of SSH sessions due to low available system memory.
Suggested Work-Around: The Telnet session will eventually terminate due to memory constraints,
and new SSH and Telnet sessions can then be started. Alternatively, MegaVision can be used to close
existing Telnet sessions to release the system memory.
Customer Impact: Moderate. Requires closing existing Telnet sessions to free system memory.
Corrective Action: This issue will be addressed in future software upgrades.