Download ExtremeXOS 12.1 - Release Notes
Transcript
Open Issues, Known Behaviors, and Resolved Issues Table 57: Platform-Specific and Feature PDs (Continued) PD3-210637311 Using MVR on a Summit and BlackDiamond 8800 a-series, e-series, or c-series platforms configured with tagged subscribing VLANs may cause unexpected untagged packet forwarding and error level log messages such as: 06/09/1920 00:08:49.87 <Erro:Kern.IPv4Mc.Error> Slot-8: Unable to Del IPmc vlan 210 for 8:1 s,G=c1010104,e101000a IPMC 9, unit 0 Entry not found Workaround: Assign an IP interface to each tagged subscriber VLAN. PD3-209983742 When a slot on a BlackDiamond 8800 or SummitStack switch reboots with active Layer-3 IP multicast subscribers, traffic will not resume until the IP multicast cache is flushed and relearned. PD3-208735701 Removing a PIM VLAN from a PIM domain using the configure pim delete vlan <vlan name> command and adding the VLAN back into the PIM domain using the configure pim add vlan <vlan name> sparse command does not restore traffic on a remote MSDP domain. Explicitly disable PIM and enable PIM to restore traffic. PD3-206283185 When PIM snooping is enabled both globally and on a VLAN, disabling PIM snooping on the VLAN also disables PIM snooping globally. PD3-163090651 No error messages are displayed when unconfiguring a group limit on a port that does not have a group limit configured. PD3-168968151 When configuring IGMP, the maximum response time can be configured to a higher time interval that the query response time without the system displaying a warning message that this is not allowed. PD3-171281681 PIM Layer 3 multicast forwarding is not working properly on a private VLAN with PIM enabled in dense mode. PD3-177958011, PD3-201244849 A switch configured for MVR leaks multicast packets to VLANs that are not configured to receive multicast streams. Network Login PD3-204414763 When a switch is up and running and all ports are in a default VLAN, the switch does not forward an EAPOL frame from a supplicant. Network Services PD3-65450031 When configuring and applying a certain ingress ACL, traffic stops forwarding to ports belonging to the same vMAN. Removing the ingress ACL restores traffic. OSPF PD3-202839989 Static routes advertised to OSPF are lost after restarting OSPF when graceful restart is enabled PoE PD4-283661276 A false alarm is occasionally generated even though the measured power is well below the power usage threshold. 07/28/2008 07:27:05.33 <Noti:POE.power_cleared> Power usage threshold condition cleared, slot 1 07/28/2008 07:27:03.12 <Warn:POE.power_exceeded> Power usage exceeding threshold for slot 1 07/28/2008 07:27:00.92 <Noti:POE.power_cleared> Power usage threshold condition cleared, slot 1 07/28/2008 07:26:56.51 <Warn:POE.power_exceeded> Power usage exceeding threshold for slot 1 SNMP PD4-264761905 The Object Identifier (OID) for a Summit X150-24 is missing from the MIB files. The OID should have the form 1.3.6.1.4.1.1916.2.xx. If you upload the MIB file to an SNMP browser, all system identifiers are shown except for the Summit X150. PD4-217023403 Traps can now be sent to trap receivers on VR-Default even when the default gateway is configured on VR-Mgmt. ExtremeXOS 12.1.4 Installation and Release Notes 179