Specifications

Open Issues, Known Behaviors, and Resolved Issues
ExtremeXOS 12.4.1 Release Notes
64
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-969859031 After upgrading from CR21 to CR22 firmware on a BlackDiamond 20808 chassis, the log
fills up with error and warning messages.
PD4-973196566 When downgrading from CR22 in ExtremeXOS 12.4.1 to CR 21 in ExtremeXOS 12.3.2.5,
multiple error and warning messages are displayed.
* (debug) BD-20808.5 # sh log sev err
12/01/1933 21:56:17.48 <Erro:HAL.Card.Error>
MM-B:voyagerCardPowerEnable:1153:- Invalid System mode information
returned from dm. dmGetSystemMode() = 33
12/01/1933 21:48:23.10 <Crit:HAL.Fabric.Critical> MM-A: Failed to
initilize Fabric Elements in Slot:
12/01/1933 21:48:23.10 <Crit:HAL.Fabric.Critical> MM-A:
fe200_init_fabriccard_1 FE-200 Power up Failed for Fabric Slot: 5
PD4-708913560 ExtremeXOS software does not monitor the temperature of I/O modules or the fan speed.
If the temperature sensors on an I/O module exceeds 80 Celsius (C), set both fan trays to
100%. When all temperature sensors on the I/O modules drop below 60 C, set the fan
speed to default (bottom fan tray at 40%, and the top fan tray at 60%). If a temperature
sensor on an I/O module exceeds 90 C, disable the slot and flag it as failed.
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.
Table 39: Platform-Specific and Feature PDs (Continued)
PD Number Description