Specifications

92 ExtremeWare 7.3.1b3 Release Notes
Clarifications, Known Behaviors, and Resolved Issues
Special Characters Accepted in WEP Plaintext Key
While configuring the WEP Plaintext key, the following characters are accepted in the CLI and are also
stored as part of the key:
• - (hyphen)
• _ (underscore)
• . (dot)
For example, eg.con sec open64wep wep key add 0 plaintext a-_.. would be an accepted key.
The following character is accepted in CLI but not stored as part of the key:
• # (hash)
For example, eg.con sec open64wep wep key add 0 plaintext a-_..############ is accepted by the
switch, but is seen as identical to the previous example.
The following characters are rejected in the CLI:
• ~‘@$%^&*()+={[}]|\:;"’<,>?/
For example, eg.# con sec open64wep wep key add 0 plaintext abcd' generates a syntax error at the ‘
character.
(PD3-1853431)
A New ACL Might Not Block Packets
In certain unusual cases, a new ACL might not block packets. If you apply an ACL (without specifying
a precedence) to a port, then disable and enable the slot for that port, the ACL functions correctly.
However, if you now delete the ACL, then create a new one, it does not block packets (PD2-221267902).
Roaming Client MAC Might be Aged Out
If a network login client moves from one layer 2 switch to another switch on a different VLAN, the
MAC address might be aged out and de-authenticated, generating an error message similar to the
following (PD2-191169610):
ERROR: Port 1:3 not in vlan
False EAPOL-Flooding Alarm
If both primary and secondary RADIUS servers fail or are unreachable, you might get a false alarm of
an EAPOL-Flooding attack in the log. This is most likely to occur after boot-up with large numbers of
802.1x clients (PD2-172518964).
EAP-Failure Messages Not Sent When Client is Unauthenticated by an Administrator
If an 802.1x supplicant MAC is forced into the unauthenticated state by an administrator, an
EAP-Failure message is not sent to the client. Using the
clear netlogin state, disable port, or
restart port commands can force the client into the unauthenticated state. If this happens, the client
is not authenticated, but some 802.1x client applications appear to be authenticated and can cause
confusion in troubleshooting. This problem does not occur if the client logs off (PD2-160278605).