Errors and Omissions
3
Data is invalid
error with no explanation. The
new firmware returns an error describing the field
containing the error and then returns to the page
allowing the error to be corrected.
Command Line Interface
The output of the
bridge port summary
CLI
command has been improved:
■
The
stpState
field has been replaced by
Link
and
Spanning Tree
columns to more accurately
report the active port status.
■
The
fwdTransitions
field has been renamed
Forward Trans
.
■
The
LACP PartnerID
field now reports
LACP disabled
if the protocol is disabled or not
supported on the port.
The output of the
bridge port detail
CLI
command has been improved:
■
The
stpState
field has been added. This shows if
the Spanning Tree Protocol (STP) has been enabled
on the port. The field will read
Enabled
if STP is
enabled on the port, even if STP is disabled globally
on the unit.
■
The currently active spanning tree state for the
port is reported in the
Spanning Tree
column
of the VLAN table. Please note that the product
supports a single spanning tree state for all VLANs
as per the
802.1d Spanning Tree
specification. It
does not support
802.1s Spanning Tree per VLAN
.
■
The
LACP PartnerID
field now reports
LACP disabled
if the protocol is disabled or not
supported on the port.
Traffic Prioritization
In previous versions of the software, the DSCP
prioritization of the
CS6
code point defaulted to
802.1d priority 7. This has been corrected. The
CS6
code point now defaults to 802.1d priority 6.
VLANs
In previous versions of the software, removing a port
from a VLAN left static entries bound to the
port-VLAN. This has been fixed. When you remove a
port from a VLAN all static entries for that port-VLAN
will be deleted.
802.1x Network login authentication:
■
In previous versions of the software, authentication
attempts for valid users would occasionally fail.
The bug causing this has been fixed.
■
The user name reported in the CLI command
security network access detail
was
occasionally displayed with incorrect trailing
characters. This has been fixed. The user names are
now displayed correctly.