Nortel Networks 100 manual RMON Alarms and Event entries

Known Restrictions

•RMON Alarms and Event entries

RMON Alarms and Event entries are not saved to nonvolatile random access memory (NVRAM). When a reset condition or power-down sequence occurs, the entries are not preserved. This conforms to the current RFC 1757 standard. All RMON Alarms and Events must be reentered.

•RMON Event Log table’s secondary index

The RMON Event Log table’s secondary index is not incremented when all of the table’s entries have been used. In this case, the existing indexes are reused. Thus, the index number cannot be used to indicate the total number of log entries received.

•RMON History Control entries

A maximum of 85 RMON History Control entries per stack unit are supported. The entry exists on the unit containing the “ControlDataSource.”

•Changing from a stack unit to a standalone switch

When you change a switch from a stack unit into a standalone switch, or vice versa, the IP address of the switch/stack changes. As a result, all existing management applications that use the previous IP address are lost until you reconnect using the new IP address.

•Console may display a blank screen

When you connect a console terminal to an operating switch through the Comm Port, the console may display a blank screen. This is a normal condition. Press [Ctrl]-C to refresh the screen or, to get beyond the Nortel Networks logo screen, press [Ctrl]-Y.

•Adding or removing stack units

When you add a new unit to the stack or remove an existing stack unit, you will not be able to perform IP management functions for approximately 30 seconds.

During this time period, the following can occur:

--Packets are lost when performance testing with SmartBits or any other traffic generator.

--IP Multicast streams stop receiving.

--TELNET sessions time out and users lose their TELNET connection without warning. Users must re-establish lost TELNET sessions.

311523-C Rev 00 11