Specifications
Open Issues, Known Behaviors, and Resolved Issues
ExtremeXOS 12.5.4 Release Notes
83
PD4-521915271 The Internet Group Management Protocol (IGMP) group reports may occasionally
change from Version 2 to Version 3.
PD4-339945634 When a load-sharing group is a member of a mirrored VLAN, packets ingressing on the
member of the load-sharing group in the mirrored VLAN should be mirrored. On the
Summit family switches and BlackDiamond 8800 modules, packets ingressing on
member ports other than the master port of the load-sharing group in the VLAN are not
mirrored.
Workaround: Packets ingressing non-master ports in the load sharing group on the
mirrored VLAN can be mirrored by adding virtual port mirroring filters for each of the non-
master member ports.
PD3-78144711 The show ipstats command does not increment IGMPv3 statistics.
PD3-79383551 IGMPv3 Report Record type "5" does not work as expected when sent after a type "2" or
a type "4" message.
Network Login
PD4-1842342791,
PD4-1291631579
When working in network login, after a dot1x client logs out, the port is not moved to a
MAC-based VLAN.
PD4-468366251 A network login client is not authenticated if the username is 32 characters. Only 31
character user names are supported, even if the user can create a 32-character
username.
PD4-763062511 Hitless upgrade is not supported for network login in ExtremeXOS 12.3.1.
PD4-752731351 You should not be able to enable network login if a VLAN is a VLAN-aggregation
subVLAN. The system should generate a syntax error.
Network Services
PD3-93829391 Configurations using a VR-Mgmt interface as a RADIUS client IP may not load at boot-
up. However, using an interface in VR-Default will load correctly.
PD3-67727590 Creating two sets of vMAN ACLs with 4000 entries each and performing a vMAN ID
translation on each ACL may generate the following error:
.....03/15/2006 17:57:28.84 <Info:pm.config.openingFile> MSM-B:
Loading policy RLL20k from file /config/RLL20k.pol
...03/15/2006 17:57:32.46 <Info:pm.config.loaded> MSM-B: Loaded
Policy: RLL20k number of entries 4002
.........Error in alloc txmi txmi 0x9f2 txmdi 0xffffffff
Error in alloc txmi txmi 0x9f4 txmdi 0xffffffff
Error in alloc txmi txmi 0x1102 txmdi 0xffffffff
Error in alloc txmi txmi 0x9f6 txmdi 0xffffffff
Error in alloc txmi txmi 0x9f8 txmdi 0xffffffff
OSPF
PD4-2067574233 When an OSPFv3 intra-area route becomes unreachable, the corresponding inter-area
prefix LSA may not be purged under certain conditions.
PD4-2087108135,
PD4-1196732534
Receiving an OSPF LSA ACK message with an invalid LSA type value causes an
assertion failure in the OSPF process.
PD4-1641495299 When 5,000 routes are received via the OSPF neighbor and advertised to 253
neighboring OSPF routers, all 253 sessions go down. It then takes nearly 20 minutes for
the sessions to come back up.
PD4-1548969848 OSPF neighbors remain in the Exchange state after disabling and enabling an OSPF
instance.
Table 38: Open Issues, Platform-Specific and Feature PDs (Continued)
PD Number Description