10
S
UPER
S
TACK
®
3 S
WITCH
3226
AND
S
WITCH
3250 S
OFTWARE
V
ERSION
1.02 R
ELEASE
N
OTES
■
The ACL which is being bound has more rules than
can be accommodated by the hardware. The
number rules available depends on the port type:
■
10/100 Ports - At least 15 rules per port
■
10/100/1000 Ports - Maximum of 2 rules per
port.
■
You try to bind an ACL to a port which forms part
of an aggregated link, or a port that has LACP
enabled.
The Switch supports ACLs based on IP addresses and
port ranges rather than VLAN IDs. To set up ACLs to
restrict routing between VLANs, each VLAN should
comprise a clearly defined subnet.
ACLs should not be used on inter-switch links as they
may interfere with routing messages required for
normal network operation.
Traffic Prioritization
■
There is no CLI command available to remove IP
port based traffic prioritizations. If you wish to
remove these entries you must either use the Web
interface or initialize the unit.
■
The IP Port traffic prioritization only examines the
destination port number field of TCP and UDP
frames when determining the priority of the
packet. This may result in the request and response
frames being prioritized differently as they traverse
the network.
■
The Switch prioritizes traffic internally but does not
mark or remark packets other than NBX packets.
NBX traffic is remarked to DSCP 46 and 802.1d
priority 6.
VLAN Configuration
Every port on the unit must be an untagged member
of a single VLAN. Every port defaults to being an
untagged member of VLAN1. If you add the port as
an untagged member of another VLAN then this will
replace the VLAN1 membership. If the port is an
untagged member of a VLAN other than 1, then
removing membership of this VLAN will cause the
port to return to being an untagged member of
VLAN1. The unit will respond with the following error
if you attempt to remove the untagged membership
of VLAN1:
Failed to delete untagged port 1:2 from VLAN
1
Management via SNMP / MIBs
■
Items configured using SNMP/MIB will be lost
when the unit is power cycled. 3Com recommends
that the CLI and Web interfaces are used to
configure the unit instead.
■
The counters for the
etherStatsPkts(64~1518)
MIB
item count traffic which is sent and received by the
unit. This does not conform to the MIB which
states that it should count only received packets.
■
Small variations in the sampling of traffic statistics
may cause the unit to incorrectly measure the
traffic rates used for RMON alarms. To minimize
the generation of incorrect alarms 3Com
recommends that they are configured with a
