Known Problems | 23 |
you do this, however, the system fails when you attempt to remove one of the interfaces.
In the following example, the FDDI and the Ethernet interfaces both have class B IP addresses, and both have the same subnet mask:
FDDI interface 158.101.101.1 Subnet mask: 255.255.0.0
Ethernet interface: 158.101.20.1 Subnet mask: 255.255.0.0
Do not assign different subnet masks to these interfaces (such as 255.255.255.0 and 255.255.0.0) if they have the same class of IP address.
■Changing the port speed or port mode before setting a system baseline on the TRSM might cause incorrect Token Ring port and bridge port statistics.
■The NVRAM conversion for SNMP traps does not adjust correctly for two new additions to the trap table. After installing LANplex software revision 8.0.2, verify that the appropriate traps are enabled.
■Some bridge port statistics are not counted on the TRSM’s Token Ring ports. The following statistics report 0 in the bridge port display for Token Ring ports on the TRSM:
■rxDiscard
■rxFloodUcasts
■rxForwardMcasts
■rxForwardUcasts
■System does not display the correct hardware revision number for EFSMs.
■When running large scripts, you might receive the following message after the script is complete:
Received ftpCommand Quit not completed errno 421
To be sure that the script has completed successfully, check to see that the last two commands in the script have completed successfully.
■Performing a manual NVDATA RESTORE causes configurations to be restored to slots that have been specified not to restore.
When restoring NV data, the system proposes a method of restoration based on restoration rules. You are prompted to load the proposal. Entering yes restores the system NV data as proposed. Entering no displays the saved configuration for you to load manually.
