on the ports configured by the Web (without a trap)
6When user tries to show VLAN, STP and GVRP information via CLI, the ‘q’ button doesn’t interrupt the displaying when type it.
7The QoS is not working properly when using queue 3 across the stack. It happens in strict priority and also in WRR, if the user does not use queue 3, everything is working fine.
8A fatal error happened when there are multiple HTTP connections sending large files at the same time (DI20080627000006).
9Sometimes when rebooting the Master or Backup Master switch in a stack, the stacking may crash (DI20081106000013).
10When configuring the ACL function with more than 100 access IDs, the system will display a warning message “Exceeded the maximum ACE allowed in the system”. However, the ACL rules are not running out actually (DI20081028000024).
11When users try to login the Web UI with ‘user’ privilege, the system will display an “Invalid username or password” error message (DI20080630000017).
12When a client sends an IGMP leave request to one multicast group, another group for that user will be disconnected, too (DI20081001000004).
13When users configure MSTP feature, MSTP can not be configured for
14Fix the problem of incorrect statistics number of Port Utilization
(DI20080807000011).
15When users connect several clients on several Slave switches and also enable flow control. If clients overload the stacking bandwidth to Master switch, the stacking may break and all switches will reboot to
16When executing “show port” command in a single switch,
1In current design, the ACL was port based and only support 128 access rules for whole system ( though in spec we stated 240 rules support and each rule is
For example, if you configure one ACL in stacking mode and apply it to more than 128 ports, you'll have problem for this function. With firmware version 2.00.47, if user applies a rule for the whole stacking, it will only be counted as 1 rule. For the detail of new ACL mechanism, please refer to the session, “Notes about ACLs capacity in the
v2.00.47
2Current system IP only supports classful IP address, such as class A, B or C with associate subnet mask such as /8, /16 or /24, if you configure Class C IP address with wrong subnet mask, say /16(255.255.0.0), you will receive an error message saying that the mask is illegal.
3When user configures ACL to change the 802.1p packet priority, the system will not map the packet to the right queue.
12
