Specifications

Open Issues, Known Behaviors, and Resolved Issues
ExtremeXOS 12.4.2 Release Notes
65
PD4-854675001,
PD4-860561781
A BlackDiamond 20808 switch with a single MM running ExtremeXOS 12.3.2 software
fails to upgrade during a firmware upgrade process. It also fails during the firmware
downgrade process. You may need to try and install the firmware multiple times.
PD4-552222911 DUT is hanging with a busy message (dots) after configuring 7,250 ingress dynamic ACLs
with conduit errors.
PD4-757707981 Proxy ARP does not work in a PVLAN.
PD4-526514731 On a BlackDiamond 20800 series switch, the system experiences a random packet drop
from the MM to the packet processor health check loopback interface.
PD4-730820249 If a route prefix in a BlackDiamond 20800 series switch is more than 24, only 100,000
routes are stored in the hardware. For the route prefixes less than 24, then 512,000
routes are stored in the hardware.
PD4-734160880,
PD4-697230006
Extreme Networks does not support the same (S,G) stream entering a switch through
multiple constituent VLANs of a private VLAN or VLAN aggregation. If a source moves
from one constituent VLAN to another, run the clear igmp snooping command.
PD4-1048824150 Deleting meters reports an error after an access list is configured and unconfigured
multiple times.
Workaround: Configure another meter.
PD4-1066604251 In dual MM systems, whenever a meter deletion results in a timeout, the show meter
command output still shows the meter, even though the error meter could not be
found is displayed.
Workaround: Create and use another meter.
PD4-1064653511 The error ........***** Process hal pid: 474 died with signal:11 is
displayed on an active MM when 1,000 policy files are configured on multiple egress
ports.
Workaround: Configurations exceeding the scaling limit are not supported.
PD4-1064653532 When configuring an access list with traffic queues, with a 10G port as one of the egress
port, traffic is lost when the corresponding 10G I/O module is hot swapped.
Workaround: Disable and re-enable the I/O module.
PD4-1056439342 I/O modules reboot when egress rate shaping is configured above 1,000 traffic queues
with all egress ports.
Workaround: Configure egress rate shaping with the proper scaling limits.
PD4-861903959 When the backup MM is not yet synced (because of run msm-failover or running
diagnostics) and one performs an MM-failover, the command is accepted, however, both
MMs will then reboot.
Workaround: Make sure that run-time diagnostics command checks that both MMs
are in sync before running the diagnostics.
PD4-847978862 A monitor port does not come up after enabling a port after a DUT is rebooted with a
disabled monitor port. The following error is displayed while rebooting:
MM-A: voyagerCardPowerEnabl
e:1144:- Invalid System mode information returned from dm.
dmGetSystemMode
() = 33
08/15/2009 16:47:02.47 < Erro:HAL.Card.Error > MM-A:
voyagerCardPowerEnabl
e:1144:- Invalid System mode information returned from dm.
dmGetSystemMode
() = 33
PD4-803757411 Configuring a meter on a BlackDiamond 20808 switch to limit broadcast or multicast
traffic (rate-limit flood-traffic) is not possible without an HQoS license.
Table 39: Platform-Specific and Feature PDs (Continued)
PD Number Description