Specifications

34 ExtremeWare 7.1.1 Release Notes
Clarifications, Known Behaviors, and Resolved Issues
Do Not Reboot Immediately After Synchronizing
Using the reboot command immediately after the synchronize command, but before the MSM’s have
finished synchronizing, might corrupt the configuration. To avoid this, wait for the MSM’s to
synchronize before rebooting. The “state” column in the output of the
show msm-failover command
displays “ready” when the synchronization is complete (PD2-171614101).
RSVP-TE Path Local End Point VLANs
If you specify a VLAN as the local end point for an RSVP-TE path, the switch allows you to change the
VLAN’s IP address, unconfigure the IP address, or delete the VLAN. No error message is generated.
The path remains operational and traffic continues to be forwarded over the associated LSPs, but the
current configuration is invalid. To avoid this, use the
show mpls rsvp-te path command to verify
the local end point configuration (PD2-164224901).
RSVP-TE End Point IP Addresses Are Not Verified
An invalid IP address can be configured when creating a new RSVP-TE path. The path might be
established to an incorrect end point, causing traffic to be forwarded to the wrong destination. To work
around this, use the
show mpls rsvp-te path command to verify the end point IP address
(PD2-162547301).
Saving Health Check Configuration After Failure Causes Console Crash
If an MSM fails a system health check with packet memory errors and is taken offline, the slave
becomes the master, but you cannot save the configuration. To avoid this, clear the diagnostics, upload
the configuration, and reboot the switch before saving (PD2-171914501).
Diagnostics on MSM-3 with Hitless Failover Causes Failover and Spurious Message
Running diagnostics on the master MSM-3 with hitless failover enabled causes the MSM-3 to fail over
to the slave and log a hardware failure message. You can safely ignore this message (PD2-168317013).
Do Not Configure a Port-Based Backplane Algorithm When CMT is Enabled
Do not configure a port-based backplane policy when CMT is enabled. It might cause all egress ports on
a given slot to be skipped. To work around this problem, configure an address-based backplane policy.
In a similar manner, if a port-based algorithm is selected for the trunk, some egress ports might be
skipped. To change the load share policy of a trunk, disable sharing for the port and enable sharing
with an address-based policy (PD2-165883601).
Cross-Module Trunking and ACLs
Flooding on a CMT trunk cannot initally be blocked by ACLs. After the remote end responds with a
PDU, the destination address is learned via source address learning. Once the address is learned,
packets are blocked in hardware by an ACL (PD2-153404501, PD2-115139620, PD2-130299801,
PD2-130299807).
ExtremeWare 7.0 (and Later) Does Not Support xmodem
You cannot use xmodem to transfer ExtremeWare 7.0 (or later) to an MSM (PD2-137101701).