Specifications

Open Issues, Known Behaviors, and Resolved Issues
ExtremeXOS 12.4.1 Release Notes
71
Known Behaviors
The following are limitations in ExtremeXOS system architecture that will not be resolved.
RMON
PD3-12950492 Issuing the clear counter command might cause a high number to be displayed in
variables such as etherHistoryOctets, etherHistoryPkts, and etherHistoryTable.
ScreenPlay
PD3-111344472 ScreenPlay allows you to configure DHCP but you cannot enable DHCP.
Security
PD3-205012219 The source-ip-lockdown dynamic deny acl counter is not working properly and increments
valid traffic from a trusted client.
PD3-186939931 Ingress mirroring is not working for DHCP snooping when snooping is enabled on
BlackDiamond 12800 series switches. DHCP snooping works correctly when DHCP
snooping is disabled.
PD3-75120608 The unconfigure radius and unconfigure tacacs commands do not reset the
timeout value to the system default of 3 seconds.
SNMP
PD4-705730556 AES/3des users created using ExtremeXOS 12.3.1 software cannot be used for SNMP
operations in ExtremeXOS 12.1 or earlier releases. This may cause the SNMP master to
crash.
PD3-39411271 icmpInMsgs counter will display the incoming ICMP packets for VR-Default only.
Spanning Tree Protocol
PD4-1161434651 MSTP edge ports are not correctly learning MAC addresses.
PD3-189927343 A temporary loop occurs when a root bridge is taken down by disabling all ports or
powering down the switch.
WAN PHY
PD3-101226461 When show wan-phy commands are run on non WAN PHY ports, the ports display the
headers. It should only display the error wan command is not supported on
non-wanphy port 25.
Table 40: Platform-Specific and Feature PDs
PD Number Description
General
PD4-1072411171 Performing an SNMP get on vplsConfigVpnId may return the same value when configuring
a larger pseudo-wire ID value.
PD4-482808326 When a configuration is saved as a default.xsf configuration, errors are seen when the
configuration comes up after running the unconfigure switch command.
PD4-486972363 Bandwidth for the detour LSPs are calculated from the PLR node to the egress node, and
not from the PLR node to the MP. Therefore, detour LSP is signaled only when there is
enough bandwidth that is equal to or greater than the requested bandwidth for the detour
LSP from the PLR node to the egress node.
Table 39: Platform-Specific and Feature PDs (Continued)
PD Number Description