Specifications

11
Release Notes for Cisco MGX 8880 Software Release 5.4.00
OL-11772-01
Release 5.3.00 Features and Enhancements
Step 6 Proceed with the normal software upgrade procedure. Alternatively, enter the resetsys command to reset
the chassis.
Note The resetsys command interrupts all traffic on the MGX chassis.
Remote IP Management Connection Enhancements
You can manage an MGX 8850 node directly from an Ethernet or console port on the PXM, or you can
configure a remote path to the PXM through a service module or route processor module. The following
management paths are supported in prior releases:
• AXSM or MPSM to PXM
• RPM-XF or RPM-PR to PXM
Earlier releases supported intranode connections only, and you could only have one PVC between an
RPM and PXM. Release 5.3.00 enhances the atm0 feature to internode connections, where an RPM on
one MGX switch connects to PXMs on other MGX switches using PNNI. And now you can manage
multiple PXMs from a single RPM.
Management Connection Limitations
The IP addresses of hosts accessing the MGX 8850 node are stored in a RAM cache. Because this cache
has a limit of 50 entries, only 50 IP hosts can actively access the node at one time. New IP hosts are
blocked until the cache clears (as result of inactivity from some hosts) to make room for new entries.
Multiple RPMs can connect to the same PXM, but each RPM can have only one connection to the PXM.
This is because the PXM has a single atm0 address.
Note If you are connected to the MGX switch using the RPM and accidentally delete the SPVC, the
connection drops. To restore RPM access, you must re-add the SPVC using the console port or Ethernet
port.
Note The clrallcnf, clrcnf, or clrsmcnf commands clear management connections. To restore RPM access,
you must reconfigure the RPM and PXM cards for IP connectivity using the console port or Ethernet
port.