Filter
Top Products
remarked. To avoid this, we recommend that you do not mix “DSCP marking” and “DSCP No-
change” service levels.
● 802.1p (packet prioritization) overwriting. If the ingress port is untagged and the egress port is
tagged, the packet’s 802.1p priority will be marked appropriately. However, if the ingress port is
tagged and the egress port is tagged, the packet’s 802.1p priority will not be remarked.
● DSCP value of 0 cannot be used as a QoS classifier.
● Ethertype IP (0x800) and ARP (0x806) cannot be used as QoS classifiers.
● The OK button in the System > Cache Config > Summary of the web interface does not function
properly if you have Windows 95 loaded and are using Internet Explorer version 5.5. The status may
change while the summary screen is open and therefore reflect an inaccurate reading.
● If Spanning Tree is disabled on your Switch, you must have each port assigned to an untagged
VLAN. Ports can also be assigned to multiple tagged VLANs.
● Using the Web interface operation Physical Interface > Ethernet > Setup, it is not possible to disable
a range of ports if the port types included in the range are different (for example, fiber and copper).
The CLI command physicalInterface Ethernet Portstate must be used instead. The CLI
also must be used to disable an Empty GBIC port.
● You may see addresses in the RIP Neighbors table that do not belong to any of your locally
configured subnets. This will not cause any negative effects to routing while using RIP.
● It is not possible to access the Device View in the Web interface if the Switches in your Distributed
Fabric are running different versions of the Gigabit Multilayer Switching software.
● When upgrading the Gigabit Multilayer Switching software within a Distributed Fabric containing both
SuperStack 3 Switch 4900 Family and 3Com Switch 40x0 Family units via the Web interface, it is
necessary to enter both software file names on the same line in the Filename text box, separated by
a space (e.g. gmi3_05.bin s3g3_05.bin). Failure to do so may result in a mixed software version
Distributed Fabric and loss of connection to the Web interface.
Known Interoperability Issues
An incompatibility exists in the default settings for Link Aggregation between the Switch and the following
3Com products:
● 3Com Switch 4007
● SuperStack II Switch 3900
● SuperStack II Switch 9300
● CoreBuilder 9000 family
● CoreBuilder 9400
● CoreBuilder 3500
The products listed above disable auto-negotiation when a port is added to an aggregated link (trunk).
In order for link aggregation (trunking) to work, ports at either end of an aggregated link (trunk) must be
identically configured. To resolve the incompatibility, you must complete the following steps:
1.
On any of the Switches listed, you must disable TCMP on a trunk (aggregated link) that
connects to a Switch, as TCMP is not supported on the Switch.
2.
You must disable auto-negotiation on all ports on the Switch that you want to place in
an aggregated link before you place them in the aggregated link.
Refer to the Documentation on the Switch CD-ROM or the 3Com Web site for more information about