Specifications
Open Issues, Known Behaviors, and Resolved Issues
ExtremeXOS 12.4.1 Release Notes
70
PD4-581950231 Multicast traffic is not received even though the rendezvous point (RP) tree and source
information is shown in the PIM cache table
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-128093864 MSDP Source-Active responses received from non-RPF peers are not processed.
PD3-189399801 The command output for the show pim rp-set command does not always show all the
Rendezvous Points for a multicast group.
Workaround: Do not configure the group address in the rp-list with a non-zero host
portion.
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.
PD3-2841008 With PIM, when small-sized multicast streams are ingressed at line rate, there is an initial
packet drop of 50% to 70%. This is seen on BlackDiamond 8800 and Summit X450
switches.
Network Login
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-67431351 Configuring an ingress traffic queue and an egress traffic queue association to multiple
ports in sequential order generates the following error:
Egress queue already associated to this ingress queue
Configuration failed on backup MSM, command execution aborted!
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
QoS
PD3-16578296 The member ports of a trunk will retain the QoS profile configuration of the trunk (based
on the master port) after load sharing is disabled, or if a port is removed from the trunk.
Table 39: Platform-Specific and Feature PDs (Continued)
PD Number Description