CUSTOMER RELEASE NOTES
08/13/2008 P/N: 9038155-52
Subject to Change Without Notice
Page: 30
of 41
F0615-O
Known Issues in Previous Releases
With a basic PWA configuration on the C3 (enhance mode is disabled) the user is unable to get to the PWA login
page
—even if the full URL for the PWA login page is used. Only after enabling enhanced mode can the user get
to the PWA login page.
C2 rate limiting only supports 120 limiting instances per stack.
The C2H and C2G should support 100 rules associated with one policy role. After configuring the C2 as such, it
gives a hardware error when trying to apply the policy to a port with one 100 rules.
Although the C2H124-48/48P displays the commands for COS metering, it is not supported.
The CLI commands ―show config‖ and ―show running-config‖ will not always reflect all of the ACLs which have
been applied to the routing interfaces.
When vlanauthorization creates VLANs from the tunnel attribute returned by radius, they are created as
permanent VLANs. Since they are permanent, the vlan and egress configuration created dynamically from the
RADIUS attribute will be stored in the configuration file permanently as well. If a user were to save a configuration
file and then reload this file, VLANs and egress would be created even though they may no longer be used on
that port.
When adding a new unit to an existing stack the ctEntStateNotifications mib does not send a trap reporting the
addition of the new unit.
The CLI settings for logging local Syslog messages to console does not work.
Policy Manager reports incorrect packet count when port usage is queried on an 802.1X authenticated user.
GVRP frames not forwarded when GVRP disabled.
Packets less than 64 bytes or greater than 1518 will not be counted by IfInErrors MIB.
When a user has multiauth configured, and two authenticated users on a port, the etsysMultiAuthSession MIB will
only report one user when polled by Policy Manager.
All the VLANs learned via GVRP will appear in the GVRP MIBs regardless of there being local users attached to
those VLANs or not.
The PWA duration times may increase to values over 60 minutes
when executing the ―show PWA session‖
command.
Attempting to change the Primary RADIUS Server to the Secondary RADIUS server or vice versa, does not work.
Enabling RMON capture on an interface will cause packets to be duplicated on the interface while the functionality
is enabled.
Only RMON offset values of 1-1518 are supported.
The ―set port priority‖ command will not change the 802.1p priority tag on tagged traffic with a default priority tag.
The command only has an effect on how untagged traffic will be prioritized as it passes internally through the
SecureStack C2 switch.
Each physical port of the SecureStack C2 switch will now support six configurable priority queues per port. The
capability will be unlocked upon upgrade if the SecureStack C2 switch has no previously configured priority-queue
mapping. If the device configuration contains previously configured priority-queue mapping, the functionality can
be exposed by executing the command ―clear port priority-queue <port(s)>‖.
When modifying the 802.1p priority to transmit
queue mapping using the ―set port priority-queue‖ command,
changes made to Fast Ethernet ports are global to all Fast Ethernet ports within the stack. Changes made to
gigabyte ports are unique to the port(s) specified.
The ―set port vlan‖ command requires that the VLAN(s) specified when executing the command must already be
preconfigured statically on the device.
