=============================================================================== 3Com(R) Network Director Version 2.0 (Service Pack 2.01) (Product #: 3C15500) =============================================================================== This document provides the following information: 1. Legal 2. About This Software 3. System Requirements 4. Enhancements in this release 5. Enhancements included in this release from earlier service packs 6. Problems fixed in this release 7. Fixes included in this release from earlier service packs 8. Running 3Com Network Director on Windows XP Service Pack 2 9. Known Problems in 3Com Network Director Version 2.0 10. Integration with 3Com Wireless Switch Manager 11. Integration with 3Com Device Manager 12. The software upgrade process 13. World Wide Web Site
=============================================================================== 1. Legal =============================================================================== __________________________________________ IMPORTANT: READ BEFORE USING THIS SOFTWARE __________________________________________ You should carefully read the terms and conditions of the Software License Agreement that is displayed when you install this software. Your legal rights are defined therein. USE OF THIS SOFTWARE INDICATES THAT YOU ACCEPT SUCH TERMS AND CONDITIONS. If you do not agree with such terms and conditions, do not use this software.
=============================================================================== 2. About This Software =============================================================================== 3Com Network Director is a standalone application that allows you to carry out key management and administrative tasks on mid-sized enterprise networks. By using 3Com Network Director you can: - discover, map and monitor all the devices on the network - backup and restore 3Com device configurations - configure 3Com devices across the network in a single operation (including - VLANs and Traffic Prioritization) - gather historical performance information for your network and generate flexible reports 3Com Network Director also provides: - fault finding and event generating capabilities - element management for 3Com switches and routers
=============================================================================== 3. System Requirements =============================================================================== One of the following Windows operating systems is required to run the application: - Windows 2000 Professional Service Pack 4 - Windows XP Professional Service Pack 2 Adobe Acrobat Reader is required to view the PDF files installed with 3Com Network Director. A web browser is required to access the Help system and the HTML-based reports. The following web browsers have been successfully tested against 3Com Network Director: Netscape Navigator 4.72 Netscape 7.72 Internet Explorer 6 Internet Explorer 6 SP1 Mozilla Firefox 1.0.4 Opera 7.22 Mozilla 1.5
Netscape 6 is not recommended because of interoperability issues. There may also be restrictions on the web browsers supported by WebHelp. 3Com Network Director has the following platform requirements:
IBM PC or compatible RAM Free hard disk space Graphics capabilities CD-ROM drive Network adapter card
Minimum ----------------------500MHz Pentium III 512MB 500MB 1024x768 / 256 colors Yes Yes
Recommended ----------------------1GHz Pentium 4 or better 1GB or more 1GB or more 1024x768 / 64K colors Yes Yes
Allow an additional 2MB of disk space per network device for historical data logging.

=============================================================================== 4. Enhancements in this release =============================================================================== 1. Support is included, or enhanced, for the following devices or agent versions: NBX - Version NBX - Support 3Com Legacy 3Com Legacy 3Com Legacy 5 agents. for the following line cards Link for Norstar (3C10390), Link for Meridian (3C10391), Link-analog (3C10392)
Analog Line Card (3c10114C) and Analog Terminal Card (3c10117C). Siemens HiPath Wireless Controllers c10, c100 and C1000 3Com Switch 3870, Agent Version 3. 3Com Switch 8800, Agent Version 3.1.21, including support for the following hardware components: 3C17508 Fabric 3C17509 3Com SW8800 PoE Power Rack 3C16884 3Com SW7750/SW8800 PoE Power Supply 3C17525 3Com Switch 8800 1-port 10GBASE-X (XENPAK) Advanced Module 3C17527 3Com Switch 8800 2-port 10GBASE-X (XFP) Advanced Module 3C17526 3Com SW8800 4-port 10GBASE-X (XFP) 3C17528 3Com SW8800 48-port 10/100/1000BASE-T (RJ45) 3C17529 3Com Switch 8800 PoE Option 3C17530 3Com SW8800 24-port 1000BASE-X Advanced (SFP) 3C17531 3Com SW8800 24-port 10/100/1000BASE-T Advanced (RJ45) 3C17532 3Com SW8800 48-port 10/100/1000BASE-T (RJ45) Access Module 3C17518 3Com SW8800 1G Memory UPG Kit 3C17510 3Com SW8800 PoE Entry Module 3Com Switch 7700 and 3Com Switch 7750 Agent Version 3.01.51. Note: that Agent Update and Backup & Restore have been included in this release for the Switch 7750 Wireless access points 7250, 82xx,8500 and 87xx Agent Version 3.2. Note: Agent Update is included in this release Basic support for the Tipping Point X505 product is included. Note: SNMP must be enabled on the X505 (with the community string set to "public") for this to work. 2. A new manual procedure to register and activate 3Com Network Director has been introduced in this release. There is extensive online help available in the "activation" wizard.
=============================================================================== 5. Enhancements included in this release from earlier service packs =============================================================================== Support was included, or enhanced, for the following devices or agent versions: 3C13630 Router 3030 3C13631 Router 3031 3C13632 Router 3032 3C13633 Router 3033 3C13634 Router 3034 3C13635 Router 3035 3C13840 Router 6040 3C13880 Router 6080 3C16850/3C16852/3C16870 Switch 7700 Family 3C16894/3C16895 Switch 7750 family 3CR17500-91 Switch 3226 3CR17501-91 Switch 3250 3C17401 Switch 3812 3C17400 Switch 3824

3CR17402-91 Switch 3848 3CR17451-91/3CR17450-91 Switch 3870 3CNJ220 Intellijack Switch NJ220 3CNJ225 Intellijack Switch NJ225 3CRWE675075 Wireless Workgroup Bridge 3Com Switch 7700 Agent Version 2.01
=============================================================================== 6. Problems fixed in this release =============================================================================== 1. It is now possible to connected XRN units. 'settings.properties' directory. Follow the suppress unnecessary warning messages for partially These messages can be suppressed by modifying the file, located in the root of the installation instructions provided within the file.
2. 3ND now correctly detects changes in XRN fabric connections. Previously it was possible for partial XRN failures not to be reported correctly. 3. The reporting of hardware failures has been improved to clarify the precise cause of failure. 4. 3ND no longer incorrectly reports certain devices as unable to support LACP. 5. Additional traps generated by Switch 5500, 7700 and 8800 are now decoded. 6. The TFTP agent upgrade, backup and restore processes have now been improved to make them more reliable. 7. Traps generated by the Eaton Powerware Redundant Power Supply (for the Switch 5500 family and other devices) are now decoded more usefully. Note: For 3Com Network Director to recognise the Powerware RPS and decode its traps, it is necessary to configure the RPS to generate the appropriate MIB SysObjectId and register the Trap target address. Please check the Eaton Powerware documentation on how to do this.
=============================================================================== 7. Fixes included in this release from earlier service packs =============================================================================== 1. 3ND will no longer fail when discovering certain PathBuilder configurations. 2. Disabling an event will now always resolve all events against a device. 3. Configuring the number of devices to be monitored now always works as expected. 4. The subnet stress status is now updated when high stress devices are deleted. Previously, the subnet could remain red. 5. The Subnet/submap title now always matches the subnet/submap that is on display. 6. Generating a special report including non-standard values for "sysDescr" MIB
will not cause 3ND to fail. 7. The RMON menu options are now available for the 3Com Enterprise Monitor. 8. After a network re-discovery, the statuses of devices are now immediately updated. Previously they could temporarily appear not to be monitored. 9. The 3xxx and 5xxx routers may now be automatically registered for warranty support. 10. The Switch port SFP module (3C16862) is now recognised by 3ND. 11. 3ND will no longer occasionally fail while analysing a Switch 4007. 12. If live graphs were launched against a WAN link, the detailed graph for the link availability monitor showed the two states as down and warning. This has now been corrected to down and up. 13. The 303x and 60x0 routers will now always be discovered correctly by 3ND. 14. Bulk configuration of spanning tree for Switch 3300 and Switch 1100s is now reliable. 15. Bulk configuration operation on a large stack of Switch 4400s is now reliable. 16. 3ND now prevents sysName, sysLocation and sysContact from being set to text strings longer than 256 characters. 17. The bulk configuration of secure addresses for Switch 4200s is now reliable. Previously, 3ND could attempt to set more than the maximum number of secure addresses permitted by these devices. 18. 3ND will no longer incorrectly report "The device has been replaced since the operation was scheduled. 3ND has not configured the new device". 19. Configuring multiple ports on a Switch 4300 is now reliable.

=============================================================================== 8. Running 3Com Network Director on Windows XP Service Pack 2 =============================================================================== 1. When 3Com Network Director first runs, you may see a warning titled "Windows Security Alert", with the text: To help protect your computer, Windows has blocked some features of this program. Do you want to keep blocking this program? Name: javaw Publisher: Unknown This warning is generated by the Windows Firewall, which is enabled by default in Windows XP Service Pack 2.
You should select the "Unblock" option on this dialog, otherwise 3Com Network Director will not operate correctly. 2. When you first launch 3Com Network Director's HTML-based online help system, you may see a warning within Internet Explorer: To help protect your security, Internet Explorer has restricted this file from showing active content that could access your computer. To allow 3Com Network Director's online help system to operate correctly, you should enable active content execution by doing the following: - launch Control Panel - select "Internet Options" - select the "Advanced" tab - check the option for "Allow active content to run in files on My Computer" 3. By default, Windows XP Service Pack 2 will not respond to discovery requests from 3Com Network Director. This will prevent any PC running Windows XP Service Pack 2 from being discovered and mapped by 3Com Network Director. If you want to include PCs running Windows XP Service Pack 2 in your 3Com Network Director map, follow the instructions below for each PC: To allow the PC to respond to ICMP echo requests (used for basic discovery): - launch Control Panel - select "Windows Firewall" - select the "Advanced" tab - click the "Settings." button in the "ICMP" frame - check the option for "Allow incoming ICMP echo requests" - click OK To allow the PC to respond to NetBIOS requests (used for identification of type and capabilities): - launch Control Panel - select "Windows Firewall" - select the "Exceptions" tab - check the option for "File and Print Sharing" - if you want to allow requests from subnets other than the local subnet: - click the "Edit." button - change the access scope as required - click OK

For more information on running 3Com Network Director on Windows XP Service Pack 2, please visit http://www.3com.com/netman/winxpsp2
=============================================================================== 9. Known Problems in 3Com Network Director Version 2.0 =============================================================================== Installation: 1. On Windows XP and Windows 2000, you must log in with Administrator rights to install and run 3Com Network Director.
2. The 3Com Device View feature will not work properly if 3Com Network Director is launched at the end of the installation process. Please launch 3Com Network Director from the Start menu. 3. Uninstalling and reinstalling 3Com Device Manager may fail with the following error message: "Resolve config file failed, exist." To resolve this issue, manually delete the following file: <windows install directory>\DeviceMgr.ini For example: c:\Windows\DeviceMgr.ini
Installation on unsupported platforms: 1. On Windows Server 2003 and Windows NT, you must log in with Administrator rights to install and run 3Com Network Director. 2. If you are running on Windows NT, the NetUtil.exe program may stop responding when you open 3Com Network Director. To rectify this problem, install or reinstall Microsoft Windows NT Service Pack 3 (or later). 3. If you are running on Windows NT, you may need to obtain and install vcredist.exe from Microsoft before installing 3Com Network Director. For your convenience, this is available as part of the 3Com Network Director distribution: <install directory>/bin/vcredist.exe
General: 1. Files generated using 3Com Network Director's Export To Visio feature are not compatible with the Microsoft Visio Viewer. Please use Microsoft Visio 2003 to view these files.
Device support: 1. 3Com Switch 5500 (if running agent versions prior to v3.1.7):
When upgrading or restoring Switch 5500 devices using 3Com Network Director's Agent Update and Restore features, please ensure that the unit number of standalone units is set to 1. If the target device is using automatic unit numbering, you can do this by simply rebooting the device. If the target device is using manual unit numbering, you can do this by setting the unit number to 1 using the device's CLI. If the unit number of standalone units is not set to 1 then Agent Update and Restore operations may fail, and further 3Com Network Director operations may also fail until the network is rediscovered. This issue does not apply to Switch 5500 devices that form a stack of 2 or more units.

3Com Switch 8800 family.

Traps are not enabled by default on the Switch 8800 family. If Trap reporing and analysis is required, then the following CLI command should be entered in the SYSTEM view: snmp-agent trap enable Please refer to the Supported Device List installed with 3Com Network Director for information on support for 3Com devices, including known restrictions. Please also ensure that you refer to the readme files supplied with your 3Com networking products, to check for possible compatibility issues with 3Com Network Director. =============================================================================== 10. Integration with 3Com Wireless Switch Manager =============================================================================== 3Com Network Director is fully compatible with 3Com Wireless Switch Manager. These applications can be installed and executed on the same PC, simultaneously. By default only one of these applications can register for and receive traps on the standard UDP port that is reserved for trap reception. To prevent conflicts between these applications it is possible to configure 3Com Network Director to forward traps to another port and for 3Com Wireless Switch Manager to receive traps on another port. Please follow these instructions to configure 3Com Network Director to forward traps to another UDP port on the same PC: 1. Open Windows Explorer, and navigate to the following directory where 3Com Network Director is installed: <install_dir>\data\com\coms\wsd\tns\server\network 2. Using a text editor, such as Microsoft Notepad, open the following file: TrapForwarding.properties 3. Enable trap forwarding by setting the status of the trap_forwarding_enabled parameter to "true": trap_forwarding_enabled = true Please use lower case letters, as 3Com Network Director is case-sensitive. 4. By default, traps will be forwarded to UDP port 1181. This port has been reserved specifically for this purpose by the Internet Assigned Numbers Authority (IANA). However, if you are running another application which is already using this port, then you can configure 3Com Network Director to forward to a different port by setting the trap_forwarding_port parameter to the desired UDP port. e.g.

trap_forwarding_port = <port number> where <port number> is the number of an appropriate, unused UDP port. 5. Save the file, and restart 3Com Network Director. All traps received by 3Com Network Director will now be forwarded to the specified port. Please refer to the documentation that comes with 3Com Wireless Switch Manager for instructions on how to configure it to receive traps on a specified UDP port.
=============================================================================== 11. Integration with 3Com Device Manager =============================================================================== 3Com Network Director includes 3Com Device Manager. Device Manager is a graphical interface to monitor and configure certain 3Com Switches and Routers. 3Com Device Manager is automatically installed as part of the 3ND installation process; 3Com Device Manager has two components - 3Com Switch Manager and 3Com Router Manager. After installation, the appropriate management application may be launched directly from a 3ND network map.
=============================================================================== 12. The Software Upgrade Process =============================================================================== This 3ND Service Pack installs automatically over the initial release of Version 2 of 3Com Network Director. The file "3com_network_director_v2_0_sp2.exe" should be run and the usual installer instructions followed. This SP is available free of charge for all unregistered users running in the 60 day evaluation period by using the "LiveUpdate" function button on the main 3ND display. Registered users of 3ND require a suitable 3Com Service Contract to obtain this Service Pack.
=============================================================================== 13. World Wide Web Site =============================================================================== Access the latest networking information on 3Com Corporation's World Wide Web site by entering our URL into your Internet browser: http://www.3com.com _______________________________________________________________________________
(R) means registered trademark. (TM) means trademark. 3Com and SuperStack are registered trademarks of 3Com Corporation. Unless otherwise indicated, 3Com registered trademarks are registered in the United States and may or may not be registered in other countries. Other marks, brand and product names may be registered trademarks or trademarks of their respective holders. Document Number: DRA15500-DAAA01 Rev10 Revision: 01 Issued: January 2006 Copyright 2006 3Com Corporation.

3COM NETWORK DIRECTOR V2.5 SUPPORTED DEVICES
This document lists devices supported by 3Com Network Director V2.5:
Basic Support Bulk Configuration VLAN Configuration Backup, Restore and Setup Agent Update RMON Device View Switch Manager Router Manager Device Warranty 3Com TippingPoint Quarantine Support

Basic Support

3Com Network Director recognizes, and provides full monitoring and topology support for the following devices. 3Com Network Director recognizes other 3Com and third-party devices. However, it only provides full monitoring and topology support for the devices on this list.
Table 1 Basic Support: Supported 3Com Devices and Minimum Agent Versions
Device Type 3Com CoreBuilder Switch 3500 3Com LinkBuilder FMS II (standard management card) (RMON management card) (Advanced management card) (Bridge management card) 3Com OfficeConnect Hub 8/TPM 3Com OfficeConnect Switch 140M 3Com OfficeConnect Managed Switch 9 3Com OfficeConnect VPN Firewall 3Com SuperStack II Desktop Switch 3Com SuperStack II Dual Speed Hub 500 3Com SuperStack II Hub 10 (standard management card) (RMON management card) (Advanced management card) (Bridge management card) 3Com SuperStack II Hub 100 3Com SuperStack II PS Hub 40 3Com SuperStack II PS Hub 50 3Com SuperStack II Switch 610 3Com SuperStack II Switch 630 3Com SuperStack II Switch 1000 3Com SuperStack II Switch 1100 3Com SuperStack II Switch 2200 Minimum Agent Version 2.1 3.00 1.01 3.14 1.02 1.03 1.00 1.00 1.0 2.10 1.10 3.00 1.01 3.14 1.02 2.00 1.03 2.06 1.08 1.08 1.01 1.02 8.1.1
Device Type 3Com SuperStack II Switch 3000 3Com SuperStack II Switch 3300 3Com SuperStack II Switch 3300 FX 3Com SuperStack II Switch 3300 XM (3C16985) 3Com SuperStack II Switch 3300 XM (3C16985A) 3Com SuperStack II Switch 3300 TM 3Com SuperStack II Switch 3300 SM 3Com SuperStack II Switch 3300 MM 3Com SuperStack II Remote Access System 1500 Layer 3 Module for use with SuperStack II Switch 1100 and 3300 version 2.42) 3Com SuperStack II Switch 3800 3Com SuperStack II Switch 3900 3Com SuperStack II Switch 9000 3Com SuperStack II Switch 9100 3Com SuperStack II Switch 9300 3Com SuperStack 3 Switch 3300 3Com SuperStack 3 Switch 4226T 3Com SuperStack 3 Switch 4250T 3Com SuperStack 3 Switch 4300 3Com SuperStack 3 Switch 4400 3Com SuperStack 3 Switch 4400 SE 3Com SuperStack 3 Switch 4400 PWR 3Com SuperStack 3 Switch 4400 FX 3Com SuperStack 3 Switch 4900 3Com SuperStack 3 Switch 4900 SX 3Com SuperStack 3 Switch 4924 3Com SuperStack 3 Switch 4950
Minimum Agent Version 2.10 1.02 2.00 2.30 2.50 2.50 2.50 2.50 1.0.27 1.0 1.2.14 2.0 1.0.9 6.0 2.0 2.60 1.01 1.01 1.01 1.04 2.10 3.12 3.20 1.05 1.10 1.41 1.51
Device Type 3Com SuperStack 3 Remote Access System 1500 3Com SuperStack 3 Webcache 1000/3000 3Com SuperStack 3 Switch 3226 3Com SuperStack 3 Switch 3250 3Com SuperStack 3 Switch 3812 3Com SuperStack 3 Switch 3824 3Com SuperStack 3 Switch 3848 3Com SuperStack 3 Switch 3870-24 3Com SuperStack 3 Switch 3870-48 3Com Switch 4005 3Com Switch 4007 3Com Switch 4007R 3Com Switch 4050 3Com Switch 4060 3Com Switch 4070 3Com Switch 4200G Family 3Com Switch 4500 family 3Com Switch 5500-SI family 3Com Switch 5500-EI family 3Com Switch 5500G-SI family 3Com Switch 5500G-EI family 3Com Switch 7700 family 3Com Switch 7750 family 3Com Switch 8800 family 3Com Wireless Access Point 7250 3Com Wireless Access Point 8000 3Com Wireless Access Point 8200
Minimum Agent Version 1.0 2.0 1.02 1.02 1.0 1.00 1.00 1.00 1.00 1.01 3.00 3.00 2.52 2.52 3.10 3.1.0 3.1 1.0 1.0 1.0 1.0 1.0 1.0 1.0 2.3.12 1.0 1.0
Device Type 3Com Wireless Access Point 8250 3Com Wireless Access Point 8500 3Com Wireless Access Point 8700 3Com Wireless Access Point 8750 3Com OfficeConnect Wireless 11g PoE Access Point 3Com Wireless LAN Controller WX4400 3Com Wireless LAN Switch WX1200 3Com Wireless LAN Controller WX2200 3Com Wireless LAN Access Point 7760 3Com WXR100 Remote Office Wireless LAN Switch 3Com Router 3012 3Com Router 3013 3Com Router 3015 3Com Router 3016 3Com Router 3018 3Com Router 3030 3Com Router 3031 3Com Router 3032 3Com Router 3033 3Com Router 3034 3Com Router 3035 3Com Router 3040 3Com Router 3041 3Com Router 5009 3Com Router 5012 3Com Router 5231 3Com Router 5232
Minimum Agent Version 2.3 1.0 1.0 2.3 1.0 1.0 1.0 4.2.3 1.0 4.0.15 1.10 1.10 1.20 1.10 1.2 1.0 1.0 1.0 1.0 1.0 1.0 2.41 2.41 1.10 2.01 1.10 2.01
Device Type 3Com Router 5640 3Com Router 5642 3Com Router 5680 3Com Router 5682 3Com Router 6040 3Com Router 6080 3Com NBX v3000 3Com(R) Networked Telephony Solution 3Com NJ200 Network Jack 3Com NJ205 IntelliJack 3Com NJ220 IntelliJack 3Com NJ225 IntelliJack 3Com NJ240 IntelliJack Cisco Catalyst 3750 family Cisco Catalyst 4500 family Siemens C10 Wireless Switch Siemens C100 Wireless Switch Siemens C1000 Wireless Switch TippingPoint 50* TippingPoint 100* TippingPoint 200* TippingPoint 400* TippingPoint 600* TippingPoint 600A* TippingPoint 1200* TippingPoint 2000* TippingPoint 2400*

Minimum Agent Version 1.10 2.01 1.10 2.01 1.0 1.0 1.0
1.0 1.1 2.0 2.5 2.4.100 12.2 12.1 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0
Device Type TippingPoint 5000* TippingPoint X505* TippingPoint X5* TippingPoint X506*

* Discovery only.

Minimum Agent Version 1.0 1.0 1.0 1.0
General Restrictions with Supported Devices 1 By default, SNMP is disabled on the following devices:
Switch 7700 family Switch 7750 family Switch 8800 family Switch 6200 3Com Router 3xxx: 3Com Router 5xxx: 3Com Router 60x0
To allow full identification and topology by 3Com Network Director, enable SNMP. Until SNMP is enabled, these devices will be represented on the 3Com Network Director map as "Generic IP" devices. 2 When Spanning Tree is enabled on the Switch 7700, 3Com Network Director may be unable to topologize the switch properly. The switch may appear as an isolated icon on the network map, with a cloud appearing where the switch should be. This issue does not occur if Spanning Tree is disabled on the Switch 7700. This issue has been resolved in version 3.0 of the Switch 7700 agent software. 3 3Com Network Director is unable to determine the Duplex mode of the LAN ports of some 3Com routers. This limitation does not apply to 3Com Router 5682, 5642, 5232 and 5012. 4 Network Jack 205 version 1.1 will appear on the 3Com Network Director map as a Network Jack 200.
5 By default, SNMP "set" permission is disabled on Network Jack devices. In order for Network Director to be able to fully configure and monitor the Network Jack devices, enable the SNMP "set" permission, using the Network Jack configuration utility. 6 NBX v3000 will appear on the 3Com Network Director map as a NBX 100. This problem can be resolved by upgrading to the latest version of the NBX v3000 agent. 7 3Com 303x routers contain an unmanaged 4 port switch. As such, 3Com Network Director may be unable to topologize these routers properly, and may show them connected to a cloud on the network map, unless they are connected to a managed hub or switch.

Bulk Configuration

Table 2 Bulk Configuration: Supported 3Com Devices and Minimum Agent Versions
Port Autonegotiation Broadcast Storm Ctrl System Information Port Administration Port Spanning Tree Quarantine Enable Trap Destinations

Wireless Settings

Trusted IP Hosts

Radius Servers

Spanning Tree

User Accounts

IGMP settings

Access Rights

Switches Switch 610 Switch 630 Switch 1100 Family Switch 32xx Family 3Com SuperStack II Layer 3 Module 3Com SuperStack II Switch 3300 3Com SuperStack II Switch 3300 FX 3Com SuperStack II Switch 3300 XM 3Com SuperStack II Switch 3300 MM / SM / TM 1.00 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.72 2.60 2.60 2.60 2.60 2.72 2.60 2.60 2.60 2.60 2.72 2.60 2.60 2.60 2.60 2.72 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 1.0 1.0 1.0 1.0 1.0 1.0 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 1.0 1.0 1.0 1.0

Port Security

Port LACP

Device

Port Autonegotiation

Broadcast Storm Ctrl

Port Administration

System Information

Port Spanning Tree
3Com SuperStack II Switch 3300 XM (3C16985) 3Com SuperStack 3 Switch 3300 3Com SuperStack 3 Switch 3300 MM / SM / TM /MM SuperStack 3 Switch 38xx Family Switch 4005 Switch 40x0 Family

2.60 2.60

2.60 2.60 2.60 2.60 2.60

2.60 2.60 2.60 2.60 2.72

2.60 2.60 2.60 2.60
2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60
2.60 2.60 2.60 2.60 2.72 2.60 2.60 2.60 2.60 2.72
1.0 1.22 1.22 3.0 3.0 2.0 1.0 3.0 3.0 1.0
1.22 1.22 1.22 1.22 1.22 3.0 2.0 2.0 3.0 2.0 2.0 3.0 2.0 2.0 3.0 2.0 2.0 3.0 2.0 2.0
1.22 1.22 1.22 1.22 1.22 3.0 2.0 2.0 3.0 2.0 2.0 3.0 2.0 2.0 3.0 2.0 2.0 2.0 [1] 2.0 3.0
Switch 4228G Family 2.0 Switch 4200 Family SuperStack 3 Switch 4300 SuperStack 3 Switch 4400 (24 Port) SuperStack 3 Switch 4400 (48 Port) SuperStack 3 Switch 4400 PWR SuperStack 3 Switch 4400 SE SuperStack 3 Switch 4400 FX Switch 4500 Switch 49xx Family Switch 5500-SI Family Switch 5500-EI Family 3.0 1.0 1.10 3.0 3.0 3.0 3.0 3.0
1.10 1.10 1.10 1.10 1.10 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 4.0 4.0 4.0 4.0 4.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0
1.10 1.10 1.10 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 [2] 3.0 [2] 3.0 [2] 3.0 [2] 3.0 [2] 6.10 6.10 6.10 6.10 6.10 3.1. 0
3.01 3.01 3.0 3.0 3.0 3.0 3.0

3.01 3.01 3.0 3.0 3.0

3.01 3.01 3.01 3.0 3.0 3.0

3.01 3.01 3.01 3.01

3.01 3.01 3.01 3.01 3.01 3.01

Quarantine Enable

Trap Destinations
Switch 5500G-EI Family Switch 7700 Switch 7750 Wireless: Access Point 7250 Access Point 8250 Access Point 8500 Access Point 8750 Building To Building Bridge 3.0 3.0 3.0 3.0

3.01 3.01

3.01 3.01 3.01 3.01.51 3.01.51

3.0 3.0 3.0 3.0 2.0. 18

3.0 3.0 3.0 3.0
Footnotes [1] Added RADA support for agent v3.0 and above. [2] Added RADA support for agent v5.0 and above. Restriction with Bulk Configuration The Layer 3 module that is available for use with the Switch 1100 and Switch 3300 family of devices will not be configured by the bulk configuration operation. However, the presence of these modules does not affect the level of support available for the parent device.
For the Switch 610, 630, 1100 Family, 3300 Family and Switch 4005 the attributes in the User Accounts and Port Security feature that rely on RADIUS authentication are not supported because the device does not support RADIUS authentication. For the Switch 610, 630, 1100 Family, 3300 Family, Switch 4300, and Switch 4005 the attributes in the Spanning Tree feature that relate to Rapid Spanning Tree Protocol are not supported because the device does not support the Rapid Spanning Tree Protocol.

VLAN Configuration

For the Switch 4300 the link state trap attribute of the port administration feature is not supported. For the SuperStack 3 Switch 4400 a license key is required device to allow the following features to be fully supported on this device: User accounts, Secure Shell (SSH), Trusted IP, RADIUS servers, Port security. For the Switch 4005 3Com Network Director is unable to configure the non-default user account on the device. This account must be configured manually on the device, see the Switch 4005 User Guide for details of how to configure the non-default user account. For the Switch 610, 630, 1100 Family, 3300 Family, Switch 7700 and 7750, Port Security is used to enable the Quarantine feature on the device.
Table 3 VLAN Configuration: Supported 3Com Devices and Minimum Agent Versions
Type Switches Switch 610 Switch 630 Switch 1100 Family Switch 32xx Family 3Com SuperStack II Switch 3300 3Com SuperStack II Switch 3300 FX 3Com SuperStack II Switch 3300 XM 1.08 1.08 1.02 1.0 1.02 2.00 2.30 Device Minimum Agent Version
3Com SuperStack II Switch 3300 MM / 2.50 SM / TM 3Com SuperStack II Switch 3300 XM (3C16985) 3Com SuperStack 3 Switch 3300 2.50 2.60
3Com SuperStack 3 Switch 3300 MM 2.50 / SM / TM /MM SuperStack 3 Switch 38xx Family 3Com SuperStack II 3900 Switch 4005 Switch 40x0 Family 3Com Switch 4007 Switch 4228G Family 1.0 2.0 0.0 2.5 2.0 2.0
Device Switch 4200 Family SuperStack 3 Switch 4300 SuperStack 3 Switch 4400 (24 Port) SuperStack 3 Switch 4400 (48 Port) SuperStack 3 Switch 4400 PWR SuperStack 3 Switch 4400 SE SuperStack 3 Switch 4400 FX Switch 4500 Switch 49xx Family Switch 5500-SI Family Switch 5500-EI Family Switch 5500G-EI Family Switch 7700 Switch 7750 3Com Switch 8800 Family 3Com SuperStack II 9300
Minimum Agent Version 1.0 1.0 1.0 2.0 3.12 2.1 3.20 3.01 1.0 3.01 3.01 3.01 1.0 1.0 3.0 2.0
Restrictions with VLAN Configuration 1 The 3Com Switch 4007 and 3Com CoreBuilder 9000 do not support VLAN configuration on the EME card, on RAP ports or on resilient link ports. 2 The VLAN configuration operation may take up to 5 minutes to complete on Switch 7700 and Switch 8800 devices. During this time, the VLAN configuration progress dialog will appear to be frozen. 3 Switch 7700 and Switch 8800 devices allow their current configuration to be saved to a file on the device's own internal storage medium. 3Com Network Director's Backup feature instructs these devices to save their current configuration to their internal storage medium during a backup operation. This may replace a previously saved configuration file on the device's storage medium.
Backup, Restore and Setup
Table 4 Backup, Restore and Setup: Supported 3Com Devices and Minimum Agent Versions

Type Switches: Switch 610 Switch 630 Switch 1100 Family Switch 32xx Family 3Com SuperStack II Switch 3300 3Com SuperStack II Switch 3300 FX 3Com SuperStack II Switch 3300 XM 2.6 2.6 2.6 1.20 2.6 2.6 2.6 Device Minimum Agent Version
3Com SuperStack II Switch 3300 MM / 2.6 SM / TM 3Com SuperStack II Switch 3300 XM (3C16985) 3Com SuperStack 3 Switch 3300 2.6 2.6
3Com SuperStack 3 Switch 3300 MM / 2.6 SM / TM /MM SuperStack 3 Switch 38xx Family Switch 4005 Switch 40x0 Family 3Com Switch 4007 Switch 4228G Family Switch 4200 Family SuperStack 3 Switch 4300 SuperStack 3 Switch 4400 (24 Port) SuperStack 3 Switch 4400 (48 Port) SuperStack 3 Switch 4400 PWR SuperStack 3 Switch 4400 SE SuperStack 3 Switch 4400 FX Switch 4500 Switch 49xx Family Switch 5500-SI Family Switch 5500-EI Family Switch 5500G-EI Family Switch 7700 2.0 2.0 4.0 3.00 3.0 3.0 1.12 3.0 3.0 3.0 3.0 3.0 3.01 4.0 3.01 3.01 3.01 1.0
Device Switch 7750 3Com Switch 8800 Family 3Com Network Jack NJ200 3Com IntelliJack Switch NJ205 3Com IntelliJack Switch NJ220 3Com IntelliJack Switch NJ225 3Com IntelliJack Switch NJ2xx FX Family
Minimum Agent Version 3.0 3.0 1.0 1.0 1.0 1.0 2.4.100
Wireless: Access Point 7250 Access Point 8000 Access Point 8200 Access Point 8250 Access Point 8500 Access Point 8750 Access Point 8750 3Com Wireless Workgroup Bridge Routers: 3Com Router 301x Family 3Com Router 303x Family 3Com Router 5009 3Com Router 5231 3Com Router 5640 3Com Router 5680 3Com Router 5012 3Com Router 5232 3Com Router 5642 3Com Router 5682 3Com Router 6040 3Com Router 6080 Interconnect / Security: 3Com SecureIX Family 1.0 1.2 2.01 1.2 1.2 1.2 1.2 2.01 2.01 2.01 2.01 2.01 2.01 2.02 1.10 2.02 2.02 2.02 2.02 2.02 1.1.21
Restrictions Backing Up and Restoring 3Com Devices 1 The Device Restore and Device Setup operations may need to initialize target devices before applying the selected configuration. Initializing a device, or applying a configuration that is not consistent with the surrounding network devices, could result in network loops or other problems, which may bring down the network to which the device is attached. If you are using any of the following features on the device, or they are part of the configuration being applied, you should disconnect the device from the network, connect it to this management station either directly or via a single hub or switch, before attempting the Device Restore or Setup operation.
VLANs Spanning Tree Resilient Links Aggregated Links
For Switch 4007 devices only, the management PC should be directly connected to the EME management module to ensure that communication is not lost during a Device Restore or Device Setup operation. 2 Device Backup, Restore and Setup operations may fail if the target device has multiple IP addresses, but not all of these addresses have been detected by 3Com Network Director. This can occur if the device is allocated additional IP addresses after the network map is discovered. To prevent this from occurring, please ensure that the network map is up-to-date before attempting a Device Backup, Restore or Setup operation. 3 For security purposes, the Device Backup operation does not back up the user information, SNMP settings or RADIUS shared secret of the selected devices. Therefore, this information will not be changed by the Device Restore or Device Setup operations. The following devices are exceptions to this rule, storing their configuration in a non-readable binary format, therefore they do back up and restore both the user and SNMP settings information:

Switch 4005

Switch 4007
4 The Device Restore and Setup operations will reset all user passwords and RADIUS shared secrets (where supported) to their factory defaults, on the following devices:
Switch 610 Switch 630 Switch 1100 Switch 3300 Switch 4400
It is strongly recommended that the user passwords are manually re-configured, using the device's Command Line Interface (CLI), immediately following a Device Restore or Setup operation on these devices. 5 In order to prevent loss of communication between 3Com Network Director and the target device, the Device Restore operation will not change the IP address, subnet mask or default gateway being used by the device prior to the operation being started. 6 Switch 1100/3300 The Device Restore operation may be unable to find the list of associated backups for the target device, if the target device is made up of two different Switch 1100/3300 units, and one of the units has been replaced since the device was last backed up. If this occurs, contact 3Com Customer Support. 7 Switch 4400 and Switch 4005 The progress bar for the Device Restore and Device Setup operations on the Switch 4400 and Switch 4005 devices, represent how far through the file transfer process the operation is at any time. This progress bar will read 100% once the chosen backup file has been completely transferred to the target device. However, both the Switch 4400 and Switch 4005 devices require some additional time following the transfer of the file for the configuration to be applied. The time required by these devices may range from one minute to one hour, depending upon the size and complexity of the target device and the configuration being applied. A typical device and configuration is expected to require less than five minutes. The Device Restore and Setup operations will wait for the devices to apply the configuration changes, but this will not be reflected by the progress bar. Subsequently, the system may look to have been suspended for some time, when it is simply waiting for the target device to complete its
configuration changes. Therefore, please allow these operations time to complete, and do not cancel them unless required. 8 If the Device Backup and Restore operations detect that the target device has changed since it was last discovered, they will suggest that the map is rediscovered to ensure that it is up-to-date. However, if these operations continue to display this message for the same device(s), after rediscovering the network map, then you should rediscover the network map again, but from a new (empty) map. 9 Switch 4400 The Device Restore and Setup operations do not take the position of any cascade modules into consideration when determining whether or not a backup can be applied to a target device. However, Switch 4400 devices will reject an attempt to restore their configuration, if they contain a cascade module that is in a different slot from when the backup was originally created. The Device Restore and Setup operations would fail in such cases. To ensure consistency, it is recommended that Switch 4400 cascade modules always be placed in slot 1. 10 The following devices may lose communications after a restore operation. This will appear as a failure in the Wizard. To complete the restore, manually reboot the device.

Wireless LAN Access Point 8200 Wireless LAN Access Point 8250 Wireless LAN Access Point 8500 Wireless LAN Access Point 8700 Wireless LAN Access Point 8750
11 3Com Router devices allow their current configuration to be saved to a file on the device's own internal storage medium. 3Com Network Director's Backup feature instructs these devices to save their current configuration to their internal storage medium during a backup operation. This may replace a previously saved configuration file on the device's storage medium. Supported Device Parameters The Device Backup operation saves the configuration of the agent software parameters summarized in Table 5:
Table 5 Supported Parameters by Device Family
Device Family Switch 610/630 Switch 1100 Family Switch 3300 Family Supported Parameters System Information; VLANs; Roving Analysis Port; Resilient Links; Port Trunks; Port Security; Spanning Tree; Port Configuration; Advanced Stack Setup; Users and User Access; RMON Alarms; RMON Events; Trap Destination; Network Interface Configuration; Serial Port Configuration System Information; VLANs; Roving Analysis Port; Spanning Tree; Port Configuration; Port Priority; IGMP Setup; RMON Alarms; Trap Destinations The agent software for these device families has native support for Backup and Restore. Please refer to the user documentation for these products for further details of the software parameters that are supported.

Switch 4300

All other supported devices
The following network interface settings are not applied to target devices by the Device Restore or Setup operations: IP address, subnet mask and default gateway. User passwords and RADIUS secrets, where relevant, are not saved as part of the human readable backup files for security reasons. See Understanding Backup Files below for a list of device families whose configuration is stored in readable backup files. Understanding Backup Files Backup files are saved in a readable format called eXtensible Markup Language (XML). Every backup file is divided into two main sections, the head and the body. The head section describes the physical configuration of the device, at the time it was backed up. However, the content of the body section depends on the type of the source device. Table 6 shows how the content of the body section relates to the device family of the source device.
Table 6 Backup File Content by Device Family
Device Family Switch 610/630 Switch 1100 Family Switch 3300 Family Switch 4300 Content of Backup File (Body Section) The entire software configuration of the device saved in a readable XML format. The software configuration can be applied to a device only using3Com Network Administrator3Com Network Director.

Device Family Switch 4005 Switch 4007/4007R Wireless LAN Access Point 8000
Content of Backup File (Body Section) A reference to one or more auxiliary files. The auxiliary files contain the software configuration of the device saved in an unreadable binary format. The auxiliary files can be restored to the device independently of3Com Network Administrator3Com Network Director, if desired, by using the device CLI or web interface. A reference to a single auxiliary file. The auxiliary file contains the software configuration of the device saved in a readable CLI command format. The auxiliary file can be restored to the device independently of3Com Network Administrator3Com Network Director, if desired, by using the device CLI or web interface.

Agent Update

Table 7 Agent Update: Supported 3Com Devices and Minimum Agent Versions
Type Switches: 3Com OfficeConnect Switch 140M Switch 610 Switch 630 Switch 1100 Family Switch 32xx Family 3Com SuperStack II Switch 3300 3Com SuperStack II Switch 3300 XM 3Com SuperStack II Switch 3300 MM / SM / TM 3Com SuperStack II Switch 3300 XM (3C16985) 3Com SuperStack 3 Switch 3300 3Com SuperStack 3 Switch 3300 MM / SM / TM /MM 3Com SuperStack II IP Switch 3800 SuperStack 3 Switch 38xx Family 3Com SuperStack II 3900 Switch 4005 Switch 40x0 Family Switch 4228G Family Switch 4200 Family SuperStack 3 Switch 4300 SuperStack 3 Switch 4400 (24 Port) SuperStack 3 Switch 4400 (48 Port) SuperStack 3 Switch 4400 PWR SuperStack 3 Switch 4400 SE SuperStack 3 Switch 4400 FX Switch 4500 Switch 49xx Family Switch 5500-SI Family Switch 5500-EI Family 1.00 1.08 1.08 1.02 1.0 1.02 2.30 2.50 2.50 2.60 2.50 1.2.14 1.0 2.0 0.0 2.5 2.0 1.0 1.0 1.0 2.0 3.12 2.1 3.20 3.01 1.0 3.01 3.01 Device Minimum Agent Version
3Com SuperStack II Switch 3300 FX 2.00
Device Switch 5500G-EI Family Switch 7700 Switch 7750 3Com Switch 8800 Family 3Com SuperStack II Switch 9100 3Com Network Jack NJ200 3Com IntelliJack Switch NJ205 3Com IntelliJack Switch NJ220 3Com IntelliJack Switch NJ225 3Com IntelliJack Switch NJ2xx FX Family
Minimum Agent Version 3.01 1.0 3.0 3.0 6.0 1.0 1.1 2.0 2.5 2.4.100
Wireless: Access Point 7250 Access Point 8000 Access Point 8200 Access Point 8250 Access Point 8500 Access Point 8750 Access Point 8750 3Com Wireless Workgroup Bridge Building To Building Bridge Routers: 3Com Router 301x Family 3Com Router 303x Family 3Com Router 5009 3Com Router 5231 3Com Router 5640 3Com Router 5680 3Com Router 5012 3Com Router 5232 3Com Router 5642 3Com Router 5682 3Com Router 6040 3Com Router 6080 1.10 2.01 1.10 1.10 1.10 1.10 2.01 2.01 2.01 2.01 2.01 2.01 3.1 1.10 3.1 3.1 3.1 3.1 3.1 1.1.21 2.00.18
Device 3Com SuperStack II Remote Access System 1500 3Com SuperStack 3 Webcache Family 3Com SecureIX Family

Minimum Agent Version 1.0.27 1.0 1.0

Interconnect / Security:

Restrictions Updating 3Com Agent Software The Software Update Utility mentioned in this section is an application used to serially update the agent software via the console port. Documentation may refer to the application by the following names: Serial Update Utility, Serial Upgrade Utility, Software Update Utility, Agent Update Utility and Management Upgrade Utility. 1 Downgrading devices You should always read the agent software release notes before downgrading a device as not all agent software can be overwritten with significantly older software. 2 Switch 1100/3300 running agent version 2.52 or lower There may occasionally be issues when updating devices from very early versions of the agent software. In particular, when updating 3Com SuperStack II Switch 1100/3300 stacks with VLANs configured from versions earlier than 2.52, you may lose communication with the device part way through the upgrade - this will appear as a timeout failure in the Agent Update Wizard. This is more likely to happen on larger stacks and/or on devices with larger numbers of VLANs configured. If this does happen, reboot the device and try again. If it fails a second time, then you should use the Software Upgrade Utility to upgrade the device directly. 3 Switch 1100/3300, PS Hub and DS Hub 500 Stacks Occasionally these devices will fail to update all of the units in the stack. If this happens, then try the update again. If it fails a second time, then you should use the Software Update Utility to update the device directly. 4 Switch 1100/3300, PS Hub and DS Hub 500 devices There is a short period during the update process when loss of connectivity or power will result in the device becoming non-operational. The device will run up on its BOOT code, you should then use the Software Update Utility to update the device directly. 5 DS Hub 500 devices Trying to upgrade from units currently running 2.11 to another version will only be successful on units that have management modules. (Normally only one Management Module is
required per stack.) If this is a problem, then you should use the Software Update Utility to update the device directly. 6 Switch 4900 devices Updating from version 2.04 or earlier may time out on a congested LAN. This is because if the initial TFTP transfer times out due to packet loss, the transfer is not restarted by the device. If this happens, try the update again when the network is less busy. 7 Webcache 1000/3000 Agent update is only supported from software version 2.00 or later. Devices running versions earlier than 2.00 should be updated using the device's Web interface. If you attempt to update a device running earlier software, it will fail with the error: "Failure - Device not readable. The update failed because it was not possible to read one or more MIBs." 8 Webcache 1000/3000 Importing agent software from disk is not supported for this device. Agent software can only be obtained using Live Update. 9 If you intend to upgrade agent software on a Wireless Access Point 8000, 3Com recommends that you consult the readme file supplied with the Access Point 8000 first. 10 Switch 1100/3300 with Layer 3 Module Attempting to upgrade a stack of Switch 1100/3300 units, which contain a Layer 3 module can fail if the Layer 3 module has been given an IP address, but the unit in which it resides does not have an IP address. To prevent this problem from occurring, you should ensure that the unit in which the Layer 3 module resides has an IP address. 11 The Agent Update operation may fail if the target device has multiple IP addresses, but not all of these addresses have been detected by 3Com Network Director. This can occur if the device is allocated additional IP addresses after the network map is discovered. To prevent this from occurring, ensure that the network map is up-to-date before attempting an Agent Update operation. 12 Agent Audit Report The agent audit report displays the location of the latest agent, for devices whose agent is out-of-date. Currently, this will be either: "Live Update" for agents that are available via Live Update, or "Local" for agents that have already been imported onto the local system.

Device Family Switch 3226 and 3250 Switch 3300 Switch 3800 Switch 3812 and 3824 Switch 3870-24, 3870-48 and 3848 Switch 4005 Switch 4050, 4060 and 4070 Switch 4070 Switch 4200 series Switch 4200G Switch 4300 Switch 4400 Switch 4500 Switch 4500G Switch 4900 series Switch 5500 EI Switch 5500 SI Switch 5500G EI Switch 610, 630, 1100 and 3300 Switch 7700-4 Switch 7700-7 S42XX_YY.bin s3tXX_YY_ZZNetMan.zip S43XX_YY.bin S2mXX_YY.bin s3nXX_YY_ZZNetMan.zip s3qXX_YY_ZZNetMan.zip S3gXX_YY.bin s4bXX_YY_ZZNetMan.zip s4aXX_YY_ZZNetMan.zip s4cXX_YY_ZZNetMan.zip S2sXX_YY.bin 774XX_YY.app 777XX_YY.app 77hXX_YYe.app 77hXX_ZZ.app Switch 7700-8 778XX_YYr.app 778XX_YYrZZ.app 77hXX_YYre.app 77hXX_Yyr.app Switch 7700-8, 7700-7 and 7700-4 Switch 7750-8, 7750-7 and 7750-4 77hXX_YY_ZZ.app 77hXX_YY_ZZNetMan.zip 775XX_YY_ZZ.app 775XX_YY_ZZNetMan.zip 3ND 2.5 SP1 Agent Filename Format s32XX_YY.bin s2sXX_YY.bin swdXX_YY.bin swdXX_YY.bin s3hXX_YY.bin 4005vXXYY.bix gmiXX_YY.bin Notes
Device Family Switch 8807, 8810 and 8814 Switch 9 & Switch 9 FX Webcache 1000 and 3000 Webcache series Wireless Access Point 7250 Wireless Access Point 7760 Wireless Access Point 8200, 8250, 8500, 8700, 8750 and 8850 Wireless Building to Building Bridge Wireless LAN Access Point 8000 Agent Filename Format 88hXX_YY_ZZ.app 88hXX_YY_ZZNetMan.zip octXX_YY.BIX octXX_YY.bix s3b_XX_YY.bin S3b_XX_YY.bin apl_XX_YY.bin aplXX_YY.bin 7760_XX_YY_ZZ_IN.img 7760_XX_YY_ZZ_us.img wap_XX_YY.bin wapXX_YY.bin wbtXX_YY.bt opXXYYYY.bin (operational code) fsXXYYYY.bin (file system) fsXXYYYY.bin (combined operational code and file system) Wireless LAN Workgroup Bridge Zakim cb3XX_YY_ZZ.bin WDSXX_YY_ZZ.BIN Notes
Notes: XX represents the major version number. YY represents the minor version number. ZZ represents the revision version number of the agent software contained in the file.
Table 9 RMON: Supported 3Com Devices
Device Type 3Com OfficeConnect Managed Switch 9 3Com SuperStack II/SuperStack 3 Switch 1100 family 3Com SuperStack II/SuperStack 3 Switch 3300 family 3Com SuperStack 3 Switch 4200 family 3Com SuperStack 3 Switch 4300 3Com SuperStack 3 Switch 4400 family 3Com SuperStack 3 Switch 4900 family 3Com Switch 4007 3Com CoreBuilder 9000 3Com Switch 4050 3Com Switch 4060 3Com Switch 4070 3Com Switch 4200G Family 3Com Switch 4500 family 3Com Switch 5500-SI family 3Com Switch 5500-EI family 3Com Switch 5500G-SI family 3Com Switch 5500G-EI family 3Com SuperStack 3 Switch 3200 family 3Com SuperStack 3 Switch 3800 family 3Com Switch 7700 family 3Com Switch 7750 family 3Com Switch 8800 family 3Com Router 3012 3Com Router 3013 3Com Router 3016 3Com Router 5009 Minimum Agent Version 3.1.0 -

Device View

Device Type 3Com Router 5231 3Com Router 5640 3Com Router 5680

Minimum Agent Version -

Restrictions with RMON There are known issues with RMON support in agent version 1.10 of the 3Com Router 3000 and 3Com Router 5000 families. Please upgrade to at least version 1.20 if you wish to use RMON monitoring. For details of the RMON support provided by any specific device in this list, consult the User Guide for the device itself.
Table 10 Device View: Supported Devices
Supported Devices 3Com AccessBuilder 6218 3Com AccessBuilder 7000 BRI 3Com AccessBuilder 7000 PRI 3Com CoreBuilder 2500 3Com CoreBuilder 3500 3Com CoreBuilder 9000 16-Slot 3Com CoreBuilder 9000 9-Slot 3Com CoreBuilder 9400 3Com FMS II 3Com LANplex 2016 3Com LinkSwitch 2200 3Com OfficeConnect Hub 8TPM 3Com OfficeConnect Remote 531s 3Com OfficeConnect Switch 140 3Com SuperStack 3 Switch 3300 3Com SuperStack ARPS
Supported Devices 3Com SuperStack II 3900-24 3Com SuperStack II 3900-36 3Com SuperStack II 9300 3Com SuperStack II Desktop Switch 3Com SuperStack II Dual Speed Hub 3Com SuperStack II Hub 10 3Com SuperStack II Hub 100 3Com SuperStack II PS Hub 3Com SuperStack II Switch 1000 3Com SuperStack II Switch 1100 3Com SuperStack II Switch 2200 3Com SuperStack II Switch 3000 3Com SuperStack II Switch 3300 3Com SuperStack II Switch 3800 3Com SuperStack II Switch 9000 3Com SuperStack Switch 9100 3Com SuperStack 3 Switch 4400 family 3Com SuperStack 3 Switch 4900 family 3Com Switch 40x0 family 3Com SuperStack II UPS 3Com Switch 4007 3Com Superstack 4 Port 1000Base-LX downlink module for 4900/40XPort 1000Base-SX downlink module for 4900/40X0 1000Base-T downlink for 4400 1000Base-SX downlink for 4400 1000Base-LX downlink for 4400 100Base-FX downlink for 4400

Switch Manager

Supported Devices 100Base-LX downlink for Port GBIC downlink module for 4900/40x0 family 4 Port 1000BaseT downlink module for 4900/40x0 family XRN Interconnect Module for 4900/40x0 family
For information on the devices supported by Switch Manager, refer to the readme file supplied with Switch Manager.

Router Manager

For information on the devices supported by Router Manager, refer to the readme file supplied with Router Manager.

Device Warranty

Devices that can be fully registered using 3Com Network Director (that is, devices for which a serial number is passed to the 3Com server) are shown in Table 11: Other devices may be passed to the 3Com server along with their associated MAC address. However, these devices need to be registered independently (with their serial number) in order to qualify for warranty.

Table 11 Device Warranty: Supported Devices
Supported Devices 3Com Network Jack 200 3Com IntelliJack NJ205 3Com IntelliJack NJ220 3Com IntelliJack NJ225 3Com IntelliJack NJ240 3Com SuperStack 3 Switch 4200 family 3Com SuperStack 3 Switch 4400 family 3Com SuperStack 3 Switch 4900 family 3Com SuperStack 3 Webcache 1000 Minimum Agent Version -
Supported Devices 3Com SuperStack 3 Webcache 3000 3Com SuperStack II Dual Speed Hub 500 3Com SuperStack II Layer 3 Switch Module 3Com SuperStack II PS Hub 40/PS Hub 50 3Com SuperStack II Switch 3900 family 3Com SuperStack II Switch 610 3Com SuperStack II Switch 630 3Com SuperStack II/SuperStack 3 Switch 1100 family 3Com SuperStack II/SuperStack 3 Switch 3300 family 3Com Switch 4005 and modules 3Com Switch 4007 and modules 3Com SuperStack 3 Switch 32xx family 3Com SuperStack 3 Switch 38xx family 3Com SuperStack 3 Switch 3870-24 3Com SuperStack 3 Switch 3870-48 3Com Switch 4050 3Com Switch 4060 3Com Switch 4070 3Com Switch 4200G Family 3Com Switch 7700 family 3Com Switch 7750 family 3Com Switch 8800 family 3Com Switch 4500 family 3Com Switch 5500-SI family 3Com Switch 5500-EI family 3Com Switch 5500G-SI family 3Com Switch 5500G-EI family
Minimum Agent Version 3.1.0 -
Supported Devices 3Com Wireless LAN Access Point 7250 3Com Wireless LAN Access Point 7760 3Com Wireless LAN Access Point 8000 3Com Wireless LAN Access Point 8200 3Com Wireless LAN Access Point 8250 3Com Wireless LAN Access Point 8500 3Com Wireless LAN Access Point 8700 3Com Wireless LAN Access Point 8750 3Com Wireless LAN Controller WX4400 3Com Wireless LAN Switch WX1200 3Com Router 3040 3Com Router 3041 3Com Router 5012 3Com Router 5232 3Com Router 5642 3Com Router 5682
Minimum Agent Version 1.0 2.41 2.41 -
3Com TippingPoint Quarantine Support
3Com Network Director supports the 3Com TippingPoint Quarantine feature for the following devices
Table 12 3Com TippingPoint Quarantine Supported Devices
Device Switches 3Com SuperStack II Switch 3300 3Com SuperStack II Switch 3300 FX 3Com SuperStack II Switch 3300 XM 3Com SuperStack II Switch 3300 MM / SM / TM 3Com SuperStack II Switch 3300 XM (3C16985) 3Com SuperStack 3 Switch 3300 3Com SuperStack 3 Switch 3300 MM / SM / TM /MM Switch 4200 Family SuperStack 3 Switch 4400 (24 Port) SuperStack 3 Switch 4400 (48 Port) SuperStack 3 Switch 4400 PWR SuperStack 3 Switch 4400 SE SuperStack 3 Switch 4400 FX Switch 4500 Switch 7700 Switch 7750 3.0 6.10 6.10 6.10 6.10 6.10 3.0 6.10 [1] 6.10 6.10 6.10 6.10 2.72 2.72 2.72 2.72 2.72 2.72 2.72 3.0 6.10 6.10 6.10 6.10 6.10 3.1.0 3.01.51 3.01.51 2.72 2.72 2.72 2.72 2.72 2.72 2.72 3.0 6.10 6.10 6.10 6.10 6.10 3.1.0 3.01.51 3.01.51 IEEE 802.1X RADA Port VLAN Configuration Port Disable
Footnotes: [1] 4400 can support multi-Mac RADA authentication. Auto-VLAN in this situation is common VLAN returned by RADIUS. For example, PC1 is assigned VLANs 1,3, PC 2 assigned VLANs 3, 10, the 4400 would set the port to VLAN 3.