Known Behaviors

The following are limitations in ExtremeXOS system architecture that have yet to be resolved.

Table 1. Known Issues, Platform-Specific, and Feature Change Requests (CRs)
CR Number Description
ExtremeSwitching X435 Series Switches
xos0076494 On ExtremeSwitching X435 24-port series switches, with fully populated ports, jumbo frames greater than 4,000 bytes are not forwarded with all 8 QoS queues.
xos0076664 ExtremeSwitching X435 series switches do not support WRED.
xos0076882 Starting with ExtremeXOS 30.5, on ExtremeSwitching X435 series switches, priority of the port is given preference even though the disconnect precedence is deny port in case of switch reboot and disable/enable in-line power except "reset inline-power".
xos0077008 On ExtremeSwitching X435 series switches, due to hardware limitations, the Sys LED does not blink in amber during failure conditions such as overheating.
xos0077043 Clear Flow is not supported on ExtremeSwitching X435 series switches.
xos0076410 On ExtremeSwitching X435 series switches, ATTN LED has no functionality defined.
xos0077324 For the ExtremeSwitching X435-24P-4S switches, you cannot view the fan speed in the output of the show fan command.
Policy
xos0078266

Downgrading from ExtremeXOS 30.5, or later, to 30.4, or earlier, causes loss of policy profile configurations.

Workaround: Before upgrading to 30.5, or later, save your 30.4, or earlier, policy configuration to ensure that you can downgrade back to 30.4, or earlier, if needed.

SummitStack
xos0075762

If you are upgrading to ExtremeXOS 30.x from 22.x or earlier, you cannot use the synchronize slot slotid command initially.

Workaround: Upgrade both the primary and secondary images on all switches in your stack to the same version of 30.x. You can then use synchronize slot slotid to upgrade the stack to any later version of ExtremeXOS as usual.

Security
xos0077285 MLAG does not work when the peers are different switch platforms.