Open Issues

The following are new open issues for supported features found in ExtremeXOS 30.3.

Click to expand in new window

Open Issues, Platform-Specific, and Feature Change Requests (CRs)

CR Number Description
General
xos0076126 Netlogin web in policy mode does not resolve the login page on DNS cache enabled VLANs. A "Page Not Found" Error appears.
xos0076221

On an unconfigured switch running ExtremeXOS 30.3, there is an issue with ZTP+ connecting to Extreme Management Center (XMC) on the management port (Mgmt VR).

Workaround: Configure option 43 with a TRAP IP address on the DHCP server.
ExtremeSwithing X465 Series Switches
xos0075819

1. With Fast PoE disabled, a mismatch of operator limits occur between hardware and configured states in ExtremeSwitching X465 series switches when running the show inline-power fast ports {port_list} command.

2. With Fast PoE enabled/disabled, a mismatch of state occurs between hardware and configured states on ExtremeSwitching X465 series switches when running the show inline-power fast ports {port_list} command.

Extended Edge Switching
xos0074983 SLLP guard is not disabling the VPLAG master port if the SLPP PDU is received on its member port. It disables the member port only. Also, in the show port command, the disabled port's status does not have a "D" Flag. Only the link status appears with an 'R' flag.
xos0075777 When inline power is disabled, and then enabled, on bridge port extender (BPE) ports, it takes 10–20 seconds for updated information to appear in the output of the show inline-power stats command.
xos0076077

With orchestration mode enabled on Extended Edge Switching redundant (MLAG) controlling bridges (CBs), when running the commands disable/enable inline-power port, the correct port state does not appear in the output of the show inline-power command of the backup CB.

Workaround: Run disable/enable inline-power port commands on both CBs to see correct port information.
Insight for Guest Virtual Machines
xos0075406 The commands show cpu-monitoring, show memory, etc. do not show memory/CPU usage for guest virtual machines (VMs). It shows usage for virtMgr, which is always low, since it only deals with a few minor tasks, such as VM autostart, handling VM related CLI, etc.