Specifications

66 ExtremeWare 7.3.1b3 Release Notes
Clarifications, Known Behaviors, and Resolved Issues
Workaround. Do not allow IP address changes to be made to the VLAN transmitting BGP traffic
(PD2-238197001).
CMT Group Will Not Forward Traffic Without a Master Slot
When you create a cross-module trunk (CMT) group with the master slot missing or disabled, the group
will not forward traffic. A save and reboot will resolve the problem. If a working CMT group already
exists, and that group is disabled and re-enabled, the CMT group works correctly (PD2-175975513).
Connection to G12SXi Might be Lost
If you reboot a BlackDiamond, you might lose the connection between the MSM64i and a G12SXi in slot
4 of a BlackDiamond 6804 or BlackDiamond 6808, or in slot 9 of a BlackDiamond 6816 (PD2-149449300).
Messages similar to the following are generated:
<CRIT:SYST> [2] The connection between MSM-A mother board and I/O module 4 is broken,
need to fix immediately
<INFO:SYST> Start initializing module in slot 4
<INFO:SYST> Generating default port configuration for slot 4 module oper type G12SXi
config type Unknown
To avoid this, install the G12SXi in a different slot, or use an MSM-3. To work around this, reboot the
switch again. For more details, see Field Notice FN 0147.
MPLS and ESRP
When a TLS VC is configured for an ESRP sub VLAN, the TLS VC is not deactivated when ESRP goes
into the slave state (PD2-85254107).
EAPS and Hitless Failover
If you have an EAPS domain with one MSM64i installed in the master switch and two MSM-3s installed
in the transit switch, the master switch enters the unknown state when you initiate hitless failover on
the transit switch (PD2-219743398).
Cross-Module Trunking and Hitless Failover
For traffic load-shared across I/O modules, failover is not hitless; traffic loss occurs for approximately
four seconds (PD2-186133901).
Autonegotiation Off Command Accepted on 10 Gigabit Ethernet Modules
Although you cannot disable autonegotiation on the 10 gigabit Ethernet modules, the command to turn
off autoneogtiation is accepted and the resulting display shows autonegotiation status as off
(PD2-223283401, PD2-232279703).
Memory Corruption with RRO on PATH Message
When the egressing switch receives an RSVP PATH message with a Record Route Object (RRO) from a
directly attached peer with the Session Attributes Flags set to Label Recording Requested, the switch
might crash. This can happen when the Session Attribute Flags field indicates Label Recording
Requested on a non-Extreme Networks switch (PD2-213821701).