Page 1: Release Notes
Part No. 10013820 Published August 2000 Switch 4007 Release Notes Management Module, Release 3.0.5 Layer 2 Switch Fabric Modules, Release 3.0.5 Layer 2 Switching Modules, Release 3.0.5 Multilayer Switching Modules, Releases 3.0.5...
Page 2 3Com Corporation reserves the right to revise this documentation and to make changes in content from time 95052-8145 to time without obligation on the part of 3Com Corporation to provide notification of such revision or change. 3Com Corporation provides this documentation without warranty, term, or condition of any kind, either implied or expressed, including, but not limited to, the implied warranties, terms, or conditions of merchantability, satisfactory quality, and fitness for a particular purpose.
Page 3: Table Of Contents
ONTENTS VERVIEW Scope Important Notices System Requirements ELEASE IGHLIGHTS Accelerated Address Aging Purpose How It Works Recommendations Interaction with Transcend Enterprise VLAN Manager Advanced Autonegotiation Sample Problem Description How Advanced Autonegotiation Works Configuration Options Configuring Standard Autonegotiation Configuring a Fixed Port State Configuring Advanced Autonegotiation or Port Monitoring Sample Configurations and System Behavior Configuration A...
Page 4 ELEASE SSUES Corrected Problems in Release 3.0.0 Operating Considerations for Release 3.0.5 Diagnostic events Chassis Reset Software Transfers Password Access System and Module Naming Web Management Known Problems in Release 3.0.5 Diagnostics SLIP Interfaces System Time Software Downloads ELEASE SSUES Corrected Problems in Release 3.0.0 System Ethernet...
Page 5 Transmit and Receive Ports on GBIC Modules Bridging Trunking Resilient Links VLANs Known Problems for Release 3.0.5 System Management Ethernet Trunking VLANs ELEASE SSUES FOR Corrected Problems in Release 3.0.0 System Management Ethernet Bridging VLANs Corrected Problems in Release 3.0.5 Bridging Management NVRAM...
Page 6 Trunking VLANs Known Problems in Release 3.0.5 System Management Ethernet Bridging Trunking ELEASE SSUES FOR Corrected Problems in Release 3.0.0 System Bridging Virtual LANs (VLANs) Roving Analysis Web Console Ethernet 4-port Gigabit Ethernet Layer 3 Switching Module (GBIC) Corrected Problems in Release 3.0.5 RMON RMON-2 Network Management Applications IP Policies...
Page 7 RMON Ethernet Bridging Backplane Port Trunking Trunking Packet Filtering Virtual Router Redundancy Protocol (VRRP) IP Multicast AppleTalk Roving Analysis Filter Builder Transmit and Receive Ports on GBIC Modules Web-based Management VLANs 4-port GBIC Multilayer Switching Module (3CB9RG4) Known Problems in Release 3.0.5 System SNMP Ethernet...
Page 8 OCUMENTATION Terminology Ethernet Internet Packet Exchange (IPX) Important Considerations Quality of Service (QoS) Web-based Management Resetting Modules SNMP Traps EME Command Changes in Release 3.0.5 Old command structure in software release 3.0.0: New command structure in software release 3.0.5: Examples Setting SNMP Trap Destinations OFTWARE NSTALLATION...
Page 9 World Wide Web Site 3Com Knowledgebase Web Services 3Com FTP Site 3Com Bulletin Board Service Access by Analog Modem Access by Digital Modem 3Com Facts Automated Fax Service Support from Your Network Supplier Support from 3Com Returning Products for Repair...
Page 11: Overview
Scope These release notes summarize operational requirements and issues for the following Switch 4007 modules and software releases: Table 1 Software Release Numbers Addressed in These Release Notes Description Management Module (EME) 9-port Gigabit Ethernet Layer 2 Switching Fabric 24-port Gigabit Ethernet Layer 2...
Page 12: Important Notices
EME module, or arrange software downloads. The 10-port 100BASE-FX Multilayer Switching Module (3CB9RF10MC) that is listed in Table 1 is new to the Switch 4007 product line at this release. Although the heritage of the Switch 4007 product line is the CoreBuilder 9000 product line, these Switch 4007 release notes do not cover all aspects that apply to the CoreBuilder 9000.
Page 13 CAUTION: Except for the EME which operates four different files on mixed release numbers (see Table 1), all modules in the Switch 4007 chassis must run software release 3.0.5 for functional reasons. The software for CoreBuilder 9000 modules and Switch 4007 modules is identical.
Page 14: System Requirements
See the Switch 4007 Implementation Guide for an explanation about how to use this command.
Page 15 ELEASE Software Release 3.0.5 is a maintenance release, however it also includes a few new features. The applicability of new features to the Switch 4007 module types is outlined in Table 2. Table 2 New Features on Switch 4007 Modules...
Page 16: Release Highlights
2: R HAPTER ELEASE IGHLIGHTS Accelerated For all Layer 2 Switching Modules in Release 3.0.5, a third option has Address Aging been added to the agingOnly Purpose If you select the disabled on the module but the address table’s aging interval will change (becomes shorter) whenever the module detects that one of its links has gone down.
Page 17: Recommendations
If you select the This will ensure that addresses flush as quickly as possible. If you are using Transcend Enterprise VLAN Manager on your network but are not running STP on your module, 3Com recommends that you select Interaction with Transcend Enterprise...
Page 18: Advanced Autonegotiation
This problem affects any vendor’s switch that complies with the IEEE 802.3u specification. It is not unique to 3Com. In this example, if port B had been fixed in half duplex mode, then a duplex mismatch would not have occurred.
Page 19: Configuration Options
As with Port Monitoring, Advanced Autonegotiation also monitors port error levels and provides notification, but goes further by changing a port’s mode into full duplex mode. However, if errors continue to exceed the system threshold, Advanced Autonegotiation partitions the port. Configuration To provide flexibility, the Advanced Autonegotiation and Port Monitoring Options...
Page 20: Sample Configurations And System Behavior
2: R HAPTER ELEASE IGHLIGHTS Sample This section describes how the system behaves in certain feature Configurations and configurations. Refer to Table 3 when reading the corresponding System Behavior paragraphs below. Table 3 Sample Configurations Configuration A Configuration B Configuration C Configuration D Configuration E Configuration A...
Page 21: Configuration C
Configuration C Ports autonegotiate connections according to the IEEE 802.3u specification. The system monitors specified ports for errors and sends alerts through traps and console messages. If a high error rate is detected on a given port, Advanced Autonegotiation forces that port into full duplex mode.
Page 22: Information Display
2: R HAPTER ELEASE IGHLIGHTS Information Display From the display of information. Some fields, such as fields, are repeated from the convenience if you are troubleshooting. However, there are three new fields: „ „ „ Important „ Considerations „ „ ethernet monitoring portNumber ethernet detail...
Page 23: Lx 70 Gbic Transceiver
1.25 Gbit/sec and distances of up to 70km over single mode fiber. To ensure optimal performance, compatibility, and regulatory compliance, use only GBIC transceivers that 3Com supports. For a list of GBIC devices that are qualified for the CoreBuilder 3500, CoreBuilder 9000 (Switch 4007), and CoreBuilder 9400, see this 3Com Web site: http://www.3com.com/gigabit_ethernet/gbics...
Page 24: Trap Filtering
2: R HAPTER ELEASE IGHLIGHTS Trap Filtering In Software Release 3.0.5, the command interface for managing SNMP traps has changed and new features have been added for filtering (enabling or disabling) link state, topology change, and authentication traps. Available Trap Filters These trap filters are available: „...
Page 25 command enables you to configure trap set snmp trap destinations, filters, and trap receive settings. set snmp trap destination <community> filter link_state enable disable topology_change enable disable authentication enable disable receive enable disable Trap Filtering Set the trap destination. The system prompts for an IP address.
Page 26 2: R HAPTER ELEASE IGHLIGHTS configuration and extensions. show snmp clear snmp command displays the status of the SNMP trap show snmp trap extensions command clears SNMP trap destinations. clear snmp trap_destination <index> Displays the status of the trap receive setting and link state, topology change, and authentication trap filters.
Page 27: Release Issues For Management Modules
Switch 4007 (for example, issues that deal with dual switch fabrics are not included because the Switch 4007 chassis only has one fabric slot). For a list of modules that are officially supported in a Switch 4007 system, see Table 1.
Page 28: Corrected Problems In Release
3: R HAPTER ELEASE SSUES Corrected Problems This section describes problems that were corrected in EME software in Release 3.0.0 Release 3.0.0. ANAGEMENT ODULES The condition that caused the EME to excessively ARP from its 10BASE-T port when you inserted it into a multinetted subnetwork has been corrected.
Page 29: Operating Considerations For Release
Operating This section describes the operating considerations that exist for an EME Considerations for that is operating with software Release 3.0.5. Release 3.0.5 Diagnostic events Chassis Reset Software Transfers Operating Considerations for Release 3.0.5 The EME no longer redirects broadcast frames to its default gateway. (27142) The EME password no longer reverts back to the default password after a reset of the switch fabric module and a switchover to the...
Page 30: Password Access
However, when you create a module name that contains spaces, then you must use quotation marks around the module name. 3Com recommends that you not use spaces for the module name. You need to click some security windows in the Web Management interface twice for the browser to accept the information.
Page 31: Slip Interfaces
See Chapter 8 in these release notes for software installation procedures. (30404) If your Switch 4007 has a redundant EME configuration that has both of the EME Ethernet ports connected to a SuperStack II Switch 3900, Switch 9300, CoreBuilder 9400, or Layer 2 module on another Switch 4007 system, in the event of a failover the secondary EME cannot immediately send traffic.
Page 32 3: R HAPTER ELEASE SSUES ANAGEMENT ODULES...
Page 33: Release Issues For Switch Fabric Modules
Switch 4007 (for example, issues that deal with dual switch fabrics are not included because the Switch 4007 chassis only has one fabric slot). For a list of modules that are officially supported in a Switch 4007 system, see Table 1 in Chapter 1 of these release notes.
Page 34: Corrected Problems In Release
4: R HAPTER ELEASE SSUES Corrected Problems This section discusses problems that pertain to switch fabric modules and in Release 3.0.0 that were corrected in software Release 3.0.0. System Ethernet Downloading Release 3.0.1 code to the 9-port Gigabit Ethernet Switch Fabric Module (Model Number 3CB9FG9) or 24-port Gigabit Ethernet Switch Fabric Module, 12 trunks (Model Number 3CB9FG24T) resolves this problem (30063).
Page 35: Corrected Problems In Release
Release 3.0.5. Bridging Management Spanning tree bridges that are attached to a Switch 4007 via Gigabit Ethernet interface module ports no longer experience topology changes during a switch fabric module failover event. (29865) If you want addresses to age more quickly after a link down event, you...
Page 36: Problems Fixed In V3.0.5 Address Table
4: R HAPTER ELEASE SSUES Problems Fixed in The “instability” issue caused by TCMP messages not being processed v3.0.5 Address Table properly in MPLA configurations, has been fixed. Stimulus such as Address Table MIB walks, or Address Tracker application queries, on any of the v3.0.0 devices had caused a problem where other “high availability”...
Page 37: Work Around
gathering agent will time out and not report any MAC addresses have been returned by the EME. Work Around There is a work around for the issues of timing out while gathering MAC addresses. That is, you must extend the timeout interval of the SNMP gathering agent to allow for up to 15 seconds of delay when your network is using high availability features such as VRRP and MPLA.
Page 38 For more information about this issue, please visit the 3Com Knowledgebase on the 3Com Web site. Applications such as Enterprise VLAN Manager and Address Tracker have background daemons that continue to poll the network even when the GUI (or front-end) applications are not running.
Page 39: Important Notes
If you are using the Enterprise VLAN Manager and Address Tracker applications, do one of the following: Under the /usr/3Com/diagnostics directory run: ./tncs_diagnostics.sh 1 Choose #1 to administer TNCS servers 2 Choose #1 to start/stop specific TNCS servers 3 Choose each of the application servers and follow the directions on the...
Page 40 If you do not wish to un-install these applications and plan to use them in the future, you can Start and Stop VLAN Manager and Address Tracker specific daemons by doing the following: 1 Proceed to /usr/3Com/diagnostics directory and run: ./tncs_diagnostics.sh 2 Verify the daemons have shutdown by using the ps command as follows:...
Page 41: Operating Considerations For Release
However, when you create a module name that contains spaces, then you must use quotation marks around the module name. 3Com recommends that you not use spaces for the module name. (25677) You may experience slow performance (response time) when you...
Page 42: Ethernet
4: R HAPTER ELEASE SSUES Ethernet Transmit and Receive Ports on GBIC Modules Bridging Trunking WITCH ABRIC ODULES Each gigabit link in the system sends congestion control frames every two seconds to detect and recover from traffic congestion. Flashing LEDs on the front panel and the corresponding statistics counters indicate this traffic.
Page 43: Resilient Links
3Com recommends that you enable the Trunk Control Message Protocol (TCMP) on each end station of a trunk. If this protocol is not enabled on both end stations, TCMP cannot correctly validate trunk configuration rules. (29581) When moving a staged module the trunking configuration is learned from the fabric when automapping is used.
Page 44: Known Problems For Release
The following MIB objects have write access according to the corresponding RFC: ifAdminStatus ipDefaultTTL etherStatsDataSource ipRouteAge However, the 3Com implementation does not allow these parameters to be changed from their default values. The Administration Console interface incorrectly displays the following unsupported trap: MIBII: Authentication Failure...
Page 45: Ethernet
Because the 64-bit counters in the ifXTable are read-only counters, you cannot reset them. Attempting to do so results in no response from the SNMP agent, and the values are not set. Through SNMP the object a3ComSysEthernetPortRequestedPortMode can be set to values out of range for the port, only use the values that are for 10 or 100.
Page 46: Vlans
4: R HAPTER ELEASE SSUES WITCH ABRIC ODULES port to a trunk without changing the port mode in a single modify operation. (29804) When you insert a switching module that supports trunks on the backplane into an unpopulated slot that has AutoMap enabled, only the first link of the trunk for that slot is in the Up state, and other links are in the Down state.
Page 47: Switching Modules
Switch 4007 (for example, issues that deal with dual switch fabrics are not included because the Switch 4007 chassis only has one fabric slot). For a list of modules that are officially supported in a Switch 4007 system, see Table 1 in Chapter 1 of this document.
Page 48: Release Issues For Layer 2 Switching Modules
5: R HAPTER ELEASE SSUES FOR Corrected Problems This section describes problems that relate to Layer 2 Switching Modules in Release 3.0.0 and that were corrected in software Release 3.0.0. System Management Ethernet Bridging AYER WITCHING ODULES The system no longer displays chassis and during the system start-up procedures.
Page 49: Vlans
VLANs Corrected Problems This section describes problems that have been corrected for Layer 2 in Release 3.0.5 Switching Modules operating with software Release 3.0.5. Bridging The 36-port 10/100BASE-TX Layer 2 modules (Model Numbers 3CB9LF36R and 3CB9LF36T) now correctly populate the address table ®...
Page 50: Management
5: R HAPTER ELEASE SSUES FOR Management AYER WITCHING ODULES The following request now returns correct and complete values for the 9-port 1000BASE-SX Gigabit Ethernet Layer 2 Switching Module: The value of entPhysicalClass that is returned for the instance of the module itself (entPhysicalClass.4) now returns 9, which represents the value for the module.
Page 51: Nvram
NVRAM Problems Fixed in The “instability” issue caused by TCMP messages not being processed v3.0.5 Address Table properly in MPLA configurations, has been fixed. Stimulus such as Address Table MIB walks, or Address Tracker application queries, on any of the v3.0.0 devices had caused a problem where other “high availability”...
Page 52: Problem Detail
5: R HAPTER ELEASE SSUES FOR Problem Detail SNMP applications that query and the other “allClosed VLAN” address table MIBS may cause traffic slowdowns if issued asynchronously with multiple variable binds as described below: Work Around There is a work around for the issues of timing out while gathering MAC addresses.
Page 53: Recommendations
For more information about this issue, please visit the 3Com Knowledgebase on the 3Com Web site. Applications such as Enterprise VLAN Manager and Address Tracker have background daemons that continue to poll the network even when the GUI (or front-end) applications are not running.
Page 54: Important Notes
When applying the Transcend patch, the patch installation utility looks to see which applications are installed and patches those applications only. 1 Proceed to the /usr/3Com/install/bin directory 2 Run the Tracker applications for de-installation. Be aware that even though the application GUI is not running, there are several background daemons that are running.
Page 55 If you do not wish to un-install these applications and plan to use them in the future, you can Start and Stop VLAN Manager and Address Tracker specific daemons by doing the following: 1 Proceed to /usr/3Com/diagnostics directory and run: ./tncs_diagnostics.sh This requires that you have root access to the workstation. Stopping these daemons prevents any background SNMP polling on the network.
Page 56 ELEASE SSUES FOR AYER WITCHING ODULES Another way to prevent VLAN Manager from polling: The /usr/3Com/ncd/runtime/sav directory contains all files comprising the Enterprise VLAN Manager database. These files are 127.0.0.1.ppp {NMS , and and should be moved somewhere else IP}.6790.PDP {NMS IP}.ppp...
Page 57: Operating Considerations For Release
There is no SNMP support for creating or deleting trunks. To prevent timeouts of SNMP requests, 3Com recommends that you increase the default timeout for the network management station. The value returned by ifType for backplane interfaces (117) are specified as defined by the Internet Assigned Numbers Authority (IANA) and not as specified in RFC 1213 or RFC 1573.
Page 58: Bridging
5: R HAPTER ELEASE SSUES FOR Bridging AYER WITCHING ODULES The rxFrameRate and rxBytes statistics in the display are incorrect. These statistics incorrectly add an extra 8 bytes to every packet that a 100 Mbps port receives. For example, when a 64 byte frame is sent into a 100 Mbit port, the value rxBytes field.
Page 59: Trunking
VLANs The maximum number of virtual LANs (VLANs) that you can define in a Switch 4007 system is 127. You may not be able to add every bridge port in the system to every VLAN that you have defined. When the...
Page 60: Known Problems In Release
MIB tables. These features and protocols include Trunk Control Message Protocol (TCMP) and Spanning Tree Protocol (STP) topology changes. 3Com recommends that you use these Transcend management applications only for configuration and problem isolation purposes. When you use these applications, SNMP polling can contribute to unexpected events in the configuration associated with TCMP and STP.
Page 61: Ethernet
The following MIB objects have write access according to the RFC’s. However, 3Com implementation does not let you change these values to anything other than the default value: ifAdminStatus, ipDefaultTTL, etherStatsDataSource, ipRouteAge The Administration Console interface incorrectly displays the following...
Page 62: Trunking
5: R HAPTER ELEASE SSUES FOR Trunking AYER WITCHING ODULES Do not use special characters in trunk names. (25715) The Administration Console of the 36-port 10/100BASE-TX Fast Ethernet RJ-45 Layer 2 Switching Module (Model Number 3CB9LF36R) incorrectly allows you to add a roving analysis port when that port has already been defined as part of a trunk group.
Page 63 Known Problems in Release 3.0.5 Each module is allowed a certain number of member ports in a trunk (L2=6 and L3=8). When you modify a trunk so that the sum of existing ports plus the added ports is greater than the number of ports allowed, an error is generated which states that the internal resource threshold has been exceeded and the ports have not been added to the trunk.
Page 64 5: R HAPTER ELEASE SSUES FOR AYER WITCHING ODULES...
Page 65: Release Issues For Multilayer Switching Modules
Switch 4007 (for example, issues that deal with dual switch fabrics are not included because the Switch 4007 chassis only has one fabric slot). For a list of modules that are officially supported in a Switch 4007 system, see Table 1 in Chapter 1 of these release notes.
Page 66: Corrected Problems In Release
6: R HAPTER ELEASE SSUES FOR Corrected Problems This section describes the problems that were corrected for Multilayer in Release 3.0.0 Switching Modules in software Releases 3.0.0 and 3.0.1. System Bridging Virtual LANs (VLANs) Roving Analysis Web Console Ethernet ULTILAYER WITCHING ODULES Multilayer switching modules no longer return erroneous MBA...
Page 67: 4-Port Gigabit Ethernet Layer 3 Switching Module (Gbic)
The command line interface now accepts a single line definition of an import/export policy. You also may use valid minimum abbreviations as well as progressing through the menus. For complete information on valid command abbreviations, see the Switch 4007 Command Reference Guide.(29565) Corrected Problems in Release 3.0.5...
Page 68: Ospf
6: R HAPTER ELEASE SSUES FOR OSPF VRRP Problems Fixed in The “instability” issue caused by TCMP messages not being processed v3.0.5 Address Table properly in MPLA configurations, has been fixed. Stimulus such as Address Table MIB walks, or Address Tracker application queries, on any of the v3.0.0 devices had caused a problem where other “high availability”...
Page 69: Problem Detail
Problem Detail SNMP applications that query a3ComSysBridgeVlanPortAddressRemoteAddress and the other “allClosed VLAN” address table MIBS may cause traffic slowdowns if issued asynchronously with multiple variable binds as described below: Asynchronous requests — an SNMP request that is sent by an SNMP program before the previous request has been processed, and responded to, by the EME in the system.
Page 70: Recommendations
For more information about this issue, please visit the 3Com Knowledgebase on the 3Com Web site. Applications such as Enterprise VLAN Manager and Address Tracker have background daemons that continue to poll the network even when the GUI (or front-end) applications are not running.
Page 71: Important Notes
When applying the Transcend patch, the patch installation utility looks to see which applications are installed and patches those applications only. 1 Proceed to the /usr/3Com/install/bin directory 2 Run the script and select the VLAN Manager and Address ./deinst.scr...
Page 72 If you do not wish to un-install these applications and plan to use them in the future, you can Start and Stop VLAN Manager and Address Tracker specific daemons by doing the following: 1 Proceed to /usr/3Com/diagnostics directory and run: ./tncs_diagnostics.sh 2 Verify the daemons have shutdown by using the ps command as follows:...
Page 73 Corrected Problems in Release 3.0.5 Another way to prevent VLAN Manager from polling: The /usr/3Com/ncd/runtime/sav directory contains all files comprising the Enterprise VLAN Manager database. These files are 127.0.0.1.ppp {NMS , and and should be moved somewhere else IP}.6790.PDP {NMS IP}.ppp or renamed with a extension.
Page 74: Operating Considerations In Release
Modules can be staged in one chassis type then moved to a different chassis type (For example, from a 16-slot CoreBuilder 9000 chassis to a 7-slot Switch 4007 chassis). However, a module’s backplane port trunking configuration (if there is any) may change; it depends on the differences in the backplane port mapping scheme of each chassis and the types of switch fabric modules that are installed.
Page 75: Rmon
Operating Considerations in Release 3.0.5 The MIB a3ComSysBridgePortReceiveMulticastLimit allows setting an out-of-range value. (28995) You cannot configure more than one routing interface on a multiprotocol VLAN using SNMP. Instead, configure the routing interface through the Administration Console. You can use the command on the RMON snmp rmonConfiguration...
Page 76: Backplane Port Trunking
6: R HAPTER ELEASE SSUES FOR Backplane Port Trunking Trunking ULTILAYER WITCHING ODULES port address list under certain conditions. The command does not list control addresses. (Control addresses are list MAC addresses for control frames that go directly to the processor.) Control addresses are installed in the address table under the following circumstances: Spanning tree for the bridge is enabled.
Page 77: Packet Filtering
If you have defined four trunk groups on one of these modules, remove one trunk group before you upgrade to Release 3.0.0. 3Com recommends that you enable the Trunk Control Message Protocol (TCMP) on each end station of a trunk. If this protocol is not enabled on both end stations, TCMP cannot correctly validate trunk configuration rules.
Page 78: Qos
6: R HAPTER ELEASE SSUES FOR See the chapter “Documentation Changes” later in these release notes, for additional information about QoS Control aggregate rate limit types. ULTILAYER WITCHING ODULES If you add a second time zone control, the first time zone control displays the start date for the second time zone control.
Page 79: Roving Analysis
“Documentation Changes” later in these release notes. The maximum number of virtual LANs (VLANs) that you can define in a Switch 4007 system is 127. You may not be able to add every bridge port in the system to every VLAN that you have defined.
Page 80: 4-Port Gbic Multilayer Switching Module (3Cb9Rg4)
Control Message Protocol (TCMP), Virtual Router Redundancy Protocol (VRRP), and Spanning Tree Protocol (STP) topology changes. 3Com recommends that you use these Transcend management applications only for configuration and problem isolation purposes. When you use these applications, SNMP polling can contribute to unexpected events in the configuration associated with TCMP, VRRP, and STP.
Page 81: Ethernet
There is no SNMP support for the AppleTalk Interface Count MIB (a3ComSysAtInterfaceCount). (05994) You cannot configure more than one routing interface on a multiprotocol VLAN using SNMP. Instead, configure the routing interface through the Web Management software or the Administration Console. You cannot delete and then successfully recreate an hlHostControlStatus entry using SNMP.
Page 82: Trunking
6: R HAPTER ELEASE SSUES FOR Trunking ULTILAYER WITCHING ODULES Do not enter the bridge port flush all switching module when there are more than 1000 MAC addresses in its bridge address table. When you add ports to an existing trunk, and change the port mode in the same modify operation, you need to reset the module and modify the trunk twice to add the additional ports to the trunk.
Page 83: Vlans
Known Problems in Release 3.0.5 VLANs VLAN statistics may have non-zero values when you first define a VLAN. When defining multiple VLANs after a VLAN mode change, you should wait a short period (5 minutes) after you change the mode before defining additional VLANs.
Page 84: Virtual Router Redundancy Protocol (Vrrp)
IP Multicast traceRoute does not work if one router hop further downstream of the router with tunnels defined. (29564) 3Com recommends that you use VLAN-based IP interfaces with STP enabled rather than port-based IP interfaces in IP networks that use DVMRP as the multicast routing protocol when these networks have physical loops in them.
Page 85: Rsvp
Known Problems in Release 3.0.5 After you perform a NVRAM conversion, the port numbering of the QoS controls becomes incorrect if a control is applied to trunked ports. (29407) QoS rate limits do not work on packets that are routed in software. (25036) Multicast traffic will not be rate limited on a port that is part of overlapped VLANs.
Page 86: Web-Based Management
6: R HAPTER ELEASE SSUES FOR ULTILAYER WITCHING ODULES Web-based Using the WebConsole to renumber the 100th QoS flow classifier Management removes that classifier when you have defined the maximum number of flow classifiers (100 classifiers). You can renumber all other flow classifiers through the WebConsole correctly.
Page 87: Documentation Changes
SNMP Traps Some Switch 4007 manuals use the product name CoreBuilder their titles. This is because the heritage of the Switch 4007 is the CoreBuilder 9000 and certain components of the latter product line are supported in the Switch 4007 chassis.
Page 88: Terminology
7: D HAPTER OCUMENTATION Terminology In any Switch 4007 document, the terms Layer 3 modules, Layer 3 switching modules, or Multilayer Switching Modules refer to the same group of modules: Ethernet In the Ethernet chapter of the Switch 4007 Implementation Guide: The “Port Monitoring”...
Page 89: Important Considerations
The IPX grep facility actually implements a modified subset of the egrep regular expression syntax. Table 4 lists the pattern-matching characters that are implemented. Table 4 IPX Grep Regular Expression Pattern-Matching Characters Pattern Character Important ipx route display Considerations not on everything in the route database. ipx server display not on everything in the service database.
Page 90: Quality Of Service (Qos)
7: D HAPTER OCUMENTATION Quality of Service In the QoS and RSVP chapter of the Switch 4007 Implementation Guide: (QoS) Now that the 10-port 100BASE-FX Multilayer Switching Module has been added to the Switch 4007 product line, the following paragraph should be added to the last point in the “General Guidelines”...
Page 91: Resetting Modules
URL syntax in the Help Server Configuration form in the software. Resetting Modules Use the following command information to supplement the information that exists about the EME in the Switch 4007 Implementation Guide: Issuing the failover to the Secondary EME. The Secondary EME becomes the Primary EME.
Page 92: Snmp Traps
7: D HAPTER OCUMENTATION SNMP Traps There are two topics that deal with SNMP traps: EME Command This section reviews the EME interface command structure for SNMP Changes in traps in software release 3.0.0, then shows the modifications that were Release 3.0.5 made in software release 3.0.5.
Page 93: Examples
Severity: Inform Type: Trap Enterprise: CoreBuilder-9000 Trap source slot: 03.01 Trap info: Link Down Octet string: Corebuilder 9000-10 Port 100FX Layer 3 Switching Module, manuf: 3Com, Fast-Ethernet Port 1 CB9000> set snmp trap filter link_state disable Link state trap set to DISABLE.
Page 94: Setting Snmp Trap Destinations
7: D HAPTER OCUMENTATION Setting SNMP Trap The following EME command is not documented in Switch 4007 Implementation Guide: Destinations Where you want to send the trap and receiver. HANGES set snmp trap destination Network Management Protocol (SNMP) trap to a specific destination.
Page 95: Software Installation
3Com factory will be pre-loaded with an earlier release of software. If you want to upgrade modules to run release 3.0.5 in your Switch 4007 system, then read this chapter to learn about the prerequisites, as well as how to download the software from the Web and how to install it.
Page 96: Verifying Module Software Releases And Compatibility
8: S HAPTER OFTWARE NSTALLATION Verifying Module To determine what software release is currently loaded on a Switch 4007 Software Releases module, follow either of these sets of steps: and Compatibility Verifying Software Releases on an Existing System 1 Connect to a powered-up chassis that is loaded with at least one EME and a variety of switching modules.
Page 97 4 MB of permanent RAM to yield the required 20 MB. To order a 16 MB DRAM card (order number 3CB9EE), contact your network supplier or 3Com representative. Before you upgrade the RAM, read the related cautions in the section titled “Prerequisites for Software Installation”...
Page 98: Verifying Software Releases On A New System And Modules
8: S HAPTER OFTWARE NSTALLATION Verifying Software Releases on a New System and Modules When you purchase a new chassis and modules or if you have had a system in storage and are just now installing it, you may have a collection of modules with incompatible software.
Page 99 4 MB of permanent RAM to yield the required 20 MB. To order a 16 MB DRAM card (order number 3CB9EE), contact your network supplier or 3Com representative. Before you upgrade the RAM, read the related cautions in the section titled “Prerequisites for Software Installation”...
Page 100: How To Obtain The Latest Software
8: S HAPTER OFTWARE NSTALLATION How to Obtain the The image files for software release 3.0.5 are available from the 3Com Latest Software Web site: http://support.3com.com/infodeli/swlib/index.htm Refer to Table 1 in Chapter 1 of these release notes to record the software filename for each different type of module.
Page 101: Terminology For The Eme Module
Terminology for the An EME module provides controller functions and management functions EME Module for the Switch 4007 chassis. Controller functions regulate physical aspects of the chassis such as power and temperature. Management functions regulate more sophisticated aspects such as system configuration, software downloads, and obtaining SNMP data.
Page 102: Prerequisites For Software Installation
8: S HAPTER OFTWARE NSTALLATION Prerequisites for Read this section for important notices that pertain to Switch 4007 Software modules prior to upgrading them to software release 3.0.5. Installation CAUTION: Software installation procedures may also contain prerequisite steps. Be sure to read the complete procedure even if you have updated software on your Switch 4007 in the past.
Page 103 (i.e., do not use the default file name). See the Switch 4007 Implementation Guide for an explanation about how to use this command. You must save these configuration files because they are not guaranteed to work with revisions of code other than the ones with which they were created.
Page 104: Upgrading The Eme Module To Release
CAUTION: This section assumes that you have already downloaded the necessary software from the 3Com web site, that your EME has the required 20 MB of CPU RAM, and that you have saved the configuration files that are associated with the current software release on the module.
Page 105: Upgrading A Single Eme Module
Upgrading a Single With only one EME module installed in a chassis, the module’s software EME Module should be installed in this order: This is an overview procedure. Each step leads you to a set of specific instructions elsewhere in this chapter. After you complete a set of instructions, return to this procedure and go to the next step.
Page 106: Upgrading Two Eme Modules
8: S HAPTER OFTWARE NSTALLATION Upgrading Two For a chassis with two EME modules installed, upgrade the software EME Modules images according to this procedure: This is an overview procedure. Each step leads you to a set of specific instructions elsewhere in this chapter. After you complete a set of instructions, return to this procedure and go to the next step.
Page 107 Upgrading the EME Module to Release 3.0.5 c Install EME boot software, version 3.0.0. For instructions, see “Installing EME Boot Software” later in this chapter. (Do not reinstall it if this version already exists on your module.) After the module finishes resetting, go to the next step.
Page 108: Installing Emc Boot Software
8: S HAPTER OFTWARE NSTALLATION Installing EMC Boot To upgrade a module’s EMC boot software to version 2.1, enter the Software following commands and information: When downloading this software to either a Master/Primary module or a Slave/Secondary module, use this command: CB9000>...
Page 109: Installing Eme Boot Software
Installing EME Boot To upgrade a module’s EME boot software to version 3.0.0, enter the Software following commands and information: When downloading to a Slave/Secondary module, use this command: CB9000> download module <slot.subslot> boot_image <server address> eme30000.bt When downloading to a Master/Primary module, use this command: CB9000>...
Page 110: Upgrading Layer 2 Switching Modules To Release 3.0.5
You have already upgraded the software on the EME modules in your system to the release numbers noted in Table 1 on page 11. You have downloaded (from the 3Com Web site) the appropriate Release 3.0.5 images in a TFTP server directory (usually named “tftp”...
Page 111: Upgrading Multilayer Switching Modules From 2.1 To
You have already upgraded the software on the EME modules in your system to the release numbers noted in Table 1 on page 11. You have downloaded (from the 3Com Web site) the appropriate Release 3.0.5 images in a TFTP server directory (usually named “tftp”...
Page 112 8: S HAPTER OFTWARE NSTALLATION The filename that you enter may include a path to the directory within the file server if this directory is not the file server’s default directory. 4 Reset the module so that the new software takes effect. At the system prompt, enter: cb9000>...
Page 113 Upgrading Multilayer Switching Modules From 2.1 to 3.0.5 Note 3: If Fast Ethernet or Gigabit Ethernet trunks are configured in Release 2.x, the requested flow control value in the displays may appear incorrectly after you upgrade to Release 3.0.5. This has no impact on traffic flow through the device.
Page 114: Upgrading Multilayer Switching Modules From 3.0 Or 3.0.1 To
3.0.0 or 3.0.1 to Release 3.0.5. However, before you begin the upgrade to 3.0.5, if you have previously upgraded the module from Release 2.1 to 3.0.0 or 3.0.1, 3Com recommends that you first check the settings of some features, as that particular upgrade transition caused many settings to change.
Page 115 Table 6 NVRAM Conversion Issues That Result When Upgrading From Release 2.1 to Release 3.0.0 or 3.0.1 Release 3.0 or 3.0.1 Command bridge trunk define bridge packetFilter create bridge vlan define ipx interface SAPadvertising Note 5: You must make these IGMP changes regardless of whether you use IP multicast routing on your module.
Page 116: Upgrade Procedure
You have already upgraded the software on the EME modules in your system to the release numbers noted in Table 1 on page 11. You have downloaded (from the 3Com Web site) the appropriate Release 3.0.5 images in a TFTP server directory (usually named “tftp”...
Page 117: Updating Emergency Download Parameters
1 From the EME, connect to the module: CB9000> connect <slot>.1 The Switch 4007 menu options screen appears. 2 At the prompt, enter The Module menu options screen appears. 3 At the prompt, enter The nvdata menu options screen appears.
Page 118 8: S HAPTER OFTWARE NSTALLATION 4 At the prompt, enter The following prompt appears: Enter file server IP address {?} [<IP address>]: Where non-corrupted software image file resides. 5 To modify the indicated IP address, enter an IP address, or to keep the existing IP address, press Enter.
Page 119: Downgrading Modules From 3.0.5 To 3.0.0 Or 3.0.1
Downgrading In the event that you need to downgrade all modules in a Switch 4007 Modules From 3.0.5 system to Release 3.0.0 or 3.0.1 (except for EMC boot code which to 3.0.0 or 3.0.1 remains at Release 2.1), follow these steps: Releases previous to 3.0.0 are not supported on the Switch 4007.
Page 120 8: S HAPTER OFTWARE NSTALLATION 7 To downgrade an EME module from Release 3.0.5 to Release 3.0.0, you only have to downgrade the EME operational image. The other three images on an EME module should already be the appropriate releases. At this point, a switchover in EME module status will occur.
Page 121: Reference
The organization of a Management Information Base (MIB) allows a Simple Network Management Protocol (SNMP) network management application to manage a network device without having a specific description of that device. The Switch 4007 Management Module (EME) supports the following MIBs in software Release 3.0.x: EFERENCE...
Page 122: Entering Commands
Entering Before you enter any command, 3Com recommends that you: Commands Year 2000 For information on Year 2000 compliance and 3Com products, visit the Compliance 3Com Year 2000 Web page: http://www.3com.com/products/yr2000.html Examine all menus and submenus carefully to obtain the complete and correct command string.
Page 123: Technical Support
3Com recommends that you access the 3Com Corporation World Wide Web site. Online Technical 3Com offers worldwide product support 24 hours a day, 7 days a week, Services through the following online systems: World Wide Web Site...
Page 124: 3Com Ftp Site
3Com FTP Site Download drivers, patches, software, and MIBs across the Internet from the 3Com public FTP site. This service is available 24 hours a day, 7 days a week. To connect to the 3Com FTP site, enter the following information into...
Page 125: Access By Digital Modem
Access by Digital Modem ISDN users can dial in to the 3Com BBS using a digital modem for fast access up to 64 Kbps. To access the 3Com BBS using ISDN, call the following number: 1 847 262 6000 3Com Facts...
Page 126 10: T HAPTER ECHNICAL UPPORT When you contact 3Com for assistance, have the following information ready: Here is a list of worldwide technical telephone support numbers: Country Telephone Number Asia, Pacific Rim Australia 1 800 678 515 Hong Kong 800 933 486...
Page 127: Returning Products For Repair
Returning Products Before you send a product directly to 3Com for repair, you must first for Repair obtain an authorization number. Products sent to 3Com without authorization numbers will be returned to the sender unopened, at the sender’s expense. To obtain an authorization number, call or fax:...

3Com 4007 Release Note

Overview

Release Highlights

Release Issues for Management Modules

Release Issues for Switch Fabric Modules

Release Issues for Layer 2 Switching Modules

Release Issues for Multilayer Switching Modules

Documentation Changes

Software Installation

Reference

Technical Support

Quick Links

Release Notes

Need help?

Questions and answers

Related Manuals for 3Com 4007

Summary of Contents for 3Com 4007

Table of Contents