User guide

Open Problem Reports and Feature Exceptions
page 94 OmniSwitch 6600/7000/8800—Release 5.1.6.R02
PR 90855
The no aaa authentication 802.1x CLI command does not work properly.
Workaround: Put onex port in the Force Authorized mode first before executing the command.
PR 92093
When using the XP service pack 2 native 802.1x client and some version of Steelbelted RADIUS, the XP
802.1x client will not always be able to "successfully" authenticate.
Workaround: Use pure XP without any service pack or with Steel-belted RADIUS Service Provider
Edition 4.70.661.
PR 92652
When a port is in the 802.1x forced authorized mode, the relay agent does not flood DHCP packets to the
same VLAN as the 802.1x client.
Workaround: This is a limitation, if only 802.1x is configured. Once the DHCP server is on a different
VLAN, then it works.
PR 92719
When an 802.1x port is configured with direction=both and port control = force-authorized, no DHCP traf-
fic is allowed to broadcast out to the 802.1x client VLAN. This is because port control is applied to both
incoming and outgoing broadcast traffic.
Workaround: When an 802.1x port is configured with direction=in and port control = force-authorized,
DHCP traffic is allowed to broadcast out to the 802.1x client VLAN. This is because port control is only
applied to incoming traffic.
PR 92818
If the 802.1x port port-control is changed from force-authorized and then changed back to auto, the Guest
VLAN feature may not work.
Workaround: Manually use admin down/up to reset the port.
PR 92863
When an 802.1x guest VLAN PC is moved from a Hub to a Guest VLAN port, it may not be able to send/
receive traffic until the MAC address is aged out on the hub port.
Workaround: There is no known workaround at this time.