Filter
Top Products
You can obtain the latest technical information for your Switch, including a list of known problems and
solutions, from the 3Com Knowledgebase:
http://knowledgebase.3com.com
Software License Agreement
Before you use the 3Com Switch 4050 and 4060 software, please ensure that you read the license
agreement text. You can find the license.txt file on the CD-ROM that accompanies your product, or in the
self-extracting exe that you have downloaded from the 3Com website.
If you intend to use a 3Com Switch 4050 and 4060 with version 3.05 software in a Distributed Fabric, ensure
that all other units in the Distributed Fabric are upgraded to version 3.05 as well. 3Com cannot guarantee
correct operation if different software versions are used within a Distributed Fabric. Please note that under
the terms and conditions of the 3Com End User Software License Agreement, you will need to purchase a
service contract for each existing 3Com Switch 4050 and 4060 before upgrading to version 3.05 software.
About This Software Version
The version 3.05 agent feature set is a compatible superset of that provided by all previous versions of this
software. This software provides support for the following:
● 3Com Switch 4050 (3C17708)
● 3Com Switch 4060 (3C17709)
The 3Com Switch 4050 and 4060 Gigabit Multilayer Switching Software Version 3.05 does not operate on
any other 3Com Switch.
Upgrading to Software Version 3.05
3Com strongly recommends that you upgrade all Switch 4050 and 4060 units which are running a previous
version of software to version 3.05.
Fixes for Known Faults
The following known faults have been fixed in version 3.05:
● When a group of routers that exchange RIP messages use DHCP/BOOTP for the configuration of
the first IP interface and receive IP addresses within the same network, the first router to get its
configuration can interfere with the other routers from getting their configuration. You should disable
RIP until the DHCP/BOOTP/ process completes.
● When upgrading from any previous version of software to V3.00 the discard on Tx setting was
corrupted for link aggregations. The effect of this could possibly result in traffic being blocked due to
oversubscribed 10/100M links. Upgrading to version 3.05 will correct this problem and force Discard
on transmit to 'on' for link aggregations.
● Under some circumstances with high traffic loads it was possible that on a fabric merge, one or both
of the XRN units could reset.