3Com 4060, 4050 User Manual

3Com® Switch 4050 and 4060 Gigabit Multilayer Switching Software Version 3.05 Release Notes
Table of Contents
Related Documentation
Software License Agreement
About This Software Version
Fixes for Known Faults
Points to Note when using the Switch 4050 and 4060
Supported Expansion Modules
Inserting and Replacing Expansion Modules
Auto-MDIX
Serial Cable
TFTP Upgrades
Configuring Link Aggregations
LACP Protocol
CD-ROM
Telnet and HyperTerminal
Software Update Utility
SLIP
Traceroute
QoS
Software Upgrade
IGMP
XRN Distributed Fabric
Long Haul Fiber GBICs
WinSock 2 Libraries for Windows 95
Known Problems
Known Interoperability Issues
Software Upgrades
How do I upgrade the Software on my Switch?
3Com Network Supervisor
Documentation Errors and Omissions
Management Interface Reference Guide (DHA1770-9AAA03):
3Com Switch 4050 and 4060 Getting Started Guide (DUA1770-9AAA04)
3Com Switch 4050 and 4060 Implementation Guide (DUA1770-9BAA03)
Related Documentation
Please use these notes in conjunction with the following documents:
“3Com Switch 4050 and 4060 Series Getting Started Guide”
Part number: DUA1770-9AAA03 (supplied with your SuperStack 3 Switch and in PDF format on the 3Com Web site)
“3Com Switch 4050 and 4060 Implementation Guide”
Part number: DUA1770-9BAA03 (supplied in PDF format on the CD-ROM that accompanies your Switch and on the 3Com Web site)
“3Com Switch 4050 and 4060 Management Quick Reference Guide”
Part number: DQA1770-9AAA03 (supplied with your SuperStack 3 Switch and in PDF format on the 3Com Web site)
“3Com Switch 4050 and 4060 Management Interface Reference Guide”
Part number: DHA1770-9AAA03 (supplied in HTML format on the CD-ROM that accompanies your Switch and on the 3Com Web site)
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.
Some packet duplication lasting for a few seconds was possible after an XRN fabric split.
TCP connection setups could corrupt the memory causing the Switch to reset. This has been seen
whilst managing the unit via the Web interface, with the http traffic going via a proxy server hosted by Novell Border Manager.
Using the Web Interface, the 1hour statistics and the 24hour statistics were the same.
Excessive and/or inconsistant failover times on XRN Fabric split and merge were found under some
configurations and traffic scenarios.
Points to Note when using the Switch 4050 and 4060
Supported Expansion Modules
3C17710 – 4 port 1000BASE-SX module
3C17711 – 4 port 1000BASE-T module
3C17712 – 4 port 1000BASE-LX module
3C17714 – 4 port GBIC module
3C17716 – XRN Interconnect module
Inserting and Replacing Expansion Modules
CAUTION: The Modules are not hot-insertable or hot-swappable. You must always power down the
Switch and disconnect it from the mains before installing or removing a Module.
When you insert a Module into the Switch, push the Module in until the Module’s back plate is in full
contact with the Switch’s chassis.
When you have inserted the Module, secure the Module to the Switch by tightening the three
cap-tive screws fully with a screwdriver.
If an error is indicated during the Power On Self Test, check that the module has been correctly
inserted.
Ensure that the blanking plate and its fastenings are stored in a suitable place. If the module is
removed, the blanking plate must be replaced.
When an expansion module is replaced by another module of a different type, the configuration will
not be completely reset to factory defaults. Specifically, the following module parameters will not be reset:
Static addressesResilient linksIGMP router portsRMON alarm variablesSpanning Tree port data
It is recommended that all module configuration should be reviewed after the expansion module has
been replaced.
Auto-MDIX
Auto-MDIX is not available if auto-negotiation is disabled on a port. That port will only operate in MDIX mode.
Serial Cable
When using a serial cable you must ensure that it is wired correctly as described in Appendix B of the Getting Started Guide.
TFTP Upgrades
Note that when initiating a TFTP upgrade using the Web interface or CLI, if an incorrect TFTP server IP address or software upgrade filename is entered you will not be able to correct the IP address or filename until the TFTP upgrade operation has timed out. The default time out period is 5 minutes.
You can avoid the 5 minute time out period by aborting the upgrade, either using the Abort button in the Web interface or the Esc character in the Command Line Interface.
Configuring Link Aggregations
When creating a manual aggregation between two systems the ports in the aggregation must not be physically connected together until the aggregation has been correctly configured at both ends of the link. Failure to configure the aggregation at both ends before physically connecting the ports can result in a number of serious network issues such as lost packets and network loops.
LACP Protocol
CAUTION: The LACP protocol is disabled by default in version 3.05 software. Some legacy devices do not support LACP and 3Com strongly recommends LACP remains disabled on ports connected to these devices (in rare cases, if LACP is enabled on ports connected to these devices, it can result in incorrect network configurations).
CD-ROM
When using the setup.exe that displays the splash screen on the CD-ROM you may experience a problem if you have an early version of virus checker installed on your PC. If you experience this problem the following error is displayed when the setup.exe is activated:
Application Error
Exception EResNotFound in
Module 0DSCD.EXE at 0016:0B37
Resource TMainForm not found.
You can either:
Turn off your virus checking software whilst using the CD-ROM
or
Upgrade your virus checking software to the latest version.
Loading...
+ 9 hidden pages