Filter
Top Products
include this, while later versions did. If your system requires WinSock 2 you can locate this
application in the "Software and Utilities section" of the CD-ROM that accompanies your
Switch.
Known Problems
● 3Com recommends that link aggregations should not be configured with a mixture of automatic and
manual member ports. In addition, 3Com recommends that LACP is disabled on ports that are
added manually to aggregations. Otherwise:
❍ If the port is initially unconnected when it is manually added to an aggregation: LACP may
unexpectedly move the port to another aggregation when the port is subsequently connected
to a partner device.
❍ If the port is initially connected to another LACP enabled partner device: The LACP partnerId
of the device may conflict with that of the manual aggregation and cause a CLI error
message to be generated.
If an automatic aggregated link (created by LACP) contains ports with different VLAN
membership, the aggregated link will inherit the VLAN membership of the first port that comes up in
the aggregated link. It will override any pre-defined VLAN membership for the aggregated link.
● 3Com recommends that you set individual ports that are to be members of an aggregated link to the
same VLAN membership. This ensures communication between all VLANs at all times.
● When or if you should decide to downgrade to an older version of the agent software, you may
notice inaccurate information displayed within the web browser interface. This is typically seen as
inactive hotspots in the interface. If this should occur, 3Com recommends that you exit the browser,
clear the browser cache, and begin another session.
● If in the Distributed Fabric the user defines the management interface only (is used as a Switch),
when the Distributed Fabric is split both units will continue to use the same IP address for
management. This can make the units management interface unreachable until the IP address is
changed on one of the units. 3Com recommends that in this case the management interface be set
to auto configure.
● On downgrade to an earlier agent version (e.g. 2.00) any QoS configuration created before the
downgrade will be lost. However, if a QoS configuration was created originally on 2.00, and no
additional QoS configuration have been made with the 3.05 agent, then on downgrade the original
QoS configuration will still exist on 2.00.
● In a Layer-2 only network (i.e. with no Multicast Routers) multicast traffic destinations may not be
learnt for up to 5 minutes after a switch is powered on, or is reset.
● The Switch does not display an error message if inappropriate, but otherwise legal, IP addresses are
used for certain configurations. For example, the IP address of the switch can be supplied as the tftp
server address for software upgrade. No error is displayed to warn of the mistake. The solution is to
supply a more appropriate IP address.
● The system management password CLI command should not be used when logged in as a user
authenticated via RADIUS. To change a password in the local (non-RADIUS) database, use the
security device user modify CLI command.
● The spanning tree mode is not synchronised between units following a Distributed Fabric merge.
This should not cause any problems for the network since rapid spanning tree is fully backward
compatible with legacy spanning tree. Where units within the Distributed Fabric are operating in
different spanning tree modes, the user interfaces are not capable of reflecting this – they will
choose one setting or the other when asked to show the current spanning tree mode. When a new
spanning tree mode is written to the Distributed Fabric (via any of the user interfaces), this will be set
on all units within the Distributed Fabric regardless of whether the spanning tree mode previously