CoreBuilder 9000 Release Notes ® Fast Ethernet and Gigabit Ethernet Layer 2 Switching Modules, Release 3.0 http://www.3com.com/ Part No.
3Com Corporation 5400 Bayfront Plaza Santa Clara, California 95052-8145 Copyright © 2000, 3Com Corporation. All rights reserved. No part of this documentation may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without written permission from 3Com Corporation.
CONTENTS 1 OVERVIEW Important Notices 7 Supported Modules 8 System Requirements 9 Boot Code and Operational Code 9 Optional Switch Fabric Module Redundancy Optional Management Redundancy 10 2 10 RELEASE HIGHLIGHTS Web-based Management 12 ISO Date and Time Format 13 New Modules 13 IGMP 14 10/100 Mbps Ethernet Port Monitoring 14 RMON Monitoring Applications 15 802.
3 RELEASE ISSUES Corrected Problems 27 System 27 Management 27 Ethernet 27 Bridging 28 VLANs 29 System Issues 29 Staging 29 System 29 Management 30 Web-based Management 30 SNMP 30 Ethernet 30 Bridging 31 Resilient Links 32 IGMP 32 Trunking 32 VLANs 32 Known Problems 34 System 34 Management 34 Ethernet 37 Bridging 38 Trunking 38 Documentation Changes 40 Ethernet 40 Web-based Management 40
4 SOFTWARE INSTALLATION How to Obtain Software Image Files 41 Installation and Upgrade Prerequisites 41 Verifying and Updating Modules for an Existing Chassis 42 Verifying and Updating Modules for a New Chassis 43 Downloading Software 44 Downloading Release 3.0 Software 44 Update Emergency Download Parameters 46 Downgrading Switching Modules to Software Release 2.1.
1 OVERVIEW These release notes summarize operational requirements and issues for CoreBuilder® 9000 Layer 2 switching module software Release 3.0. Important Notices Read these important notices before you begin. For the most up-to-date release notes for the CoreBuilder 9000 management modules, switch fabric modules, Layer 3 interface modules, and other Layer 2 interface modules, visit the 3Com Web site: http://support.3com.com/nav/switches.htm CAUTION: CoreBuilder 9000 software Release 3.
CHAPTER 1: OVERVIEW See “Installation and Upgrade Prerequisites”, in Chapter 4 “Software Installation”, for information about how to determine the software release on each module in the chassis. CAUTION: Before you attempt to download any module software, save the configuration file for the release that you are currently running to an external device using the EME upload command. See the CoreBuilder 9000 Enterprise Management Engine User Guide for an explanation of how to use the EME upload command.
System Requirements System Requirements Each CoreBuilder 9000 Enterprise Switch has these minimum system requirements: ■ One switch fabric module installed in the CoreBuilder 9000 chassis with appropriate software: ■ ■ ■ Boot Code and Operational Code 9 For all CoreBuilder 9000 chassis: One 24-port Gigabit Ethernet Switch Fabric Module (Model Number 3CB9FG24 or Model Number 3CB9FG24T) For the 7-slot chassis and 8-slot chassis: One 9-port Gigabit Ethernet Switch Fabric Module (Model Number 3CB9FG9)
CHAPTER 1: OVERVIEW Table 1 Software Compatibility Requirements for Layer 2 Switching Modules (continued) Minimum Software Model Number Requirements Filename 9-port 1000BASE-SX Gigabit Ethernet Layer 2 Switching Module 3CB9LG9MC 3.0.0 lg9mc30000.all 24-port Gigabit Ethernet Switch Fabric Module, 4 trunks 3CB9FG24 3.0.0 fga2430000.all 24-port Gigabit Ethernet Switch Fabric Module, 12 trunks 3CB9FG24T 3.0.1 fga24t30001.all 9-port Gigabit Ethernet Switch Fabric Module 3CB9FG9 3.0.
2 RELEASE HIGHLIGHTS Software Release 3.0 includes the following changes: ■ Web-based Management ■ ISO Date and Time Format ■ New Modules ■ IGMP ■ 10/100 Mbps Ethernet Port Monitoring ■ RMON Monitoring Applications ■ 802.
CHAPTER 2: RELEASE HIGHLIGHTS Web-based Management Software Release 3.0 supports the Web Management suite of features, which consists of embedded Web Management applications and installable tools: ■ Embedded Web Management applications — Use the embedded Web Management applications, which are part of the system software image, for most of your device configuration and management tasks. You can manage a single port or device, or, using multiple windows, you can manage multiple devices.
ISO Date and Time Format ISO Date and Time Format 13 The format for date and time has changed for Release 3.0 to the following syntax and now complies with ISO 8601: YYYY-MM-DDThh:mm:ss Table 2 Date and Time Format Description YYYY Year (1999 – 2098) MM Month (01 – 12) DD Day (01 – 31) T Time designator (the literal character “T”) hh Hour (00 – 24) mm Minute (00 – 59) ss Second (00 – 59) Example: 2000-02-05T03:25:34 New Modules Software Release 3.
CHAPTER 2: RELEASE HIGHLIGHTS IGMP 10/100 Mbps Ethernet Port Monitoring The Internet Group Management Protocol (IGMP) ensures that multicast traffic is forwarded from the local router to multicast group members on directly attached subnetworks. The Snooping function monitors IGMP packets to ensure that multicast traffic is only forwarded to areas of the network that contain multicast group members.
RMON Monitoring Applications RMON Monitoring Applications 15 New versions of LANsentry® Manager are being released. You can use LANsentry Manager to monitor traffic and error rates for hosts on a network, along with traffic flows between these hosts. When you set up LANsentry Manager with the CoreBuilder 9000, take these factors into consideration: ■ To access a CoreBuilder 9000 module, use the community string plus extension format as follows: @slot_.
CHAPTER 2: RELEASE HIGHLIGHTS You configure the front-panel ports to participate in this algorithm using three options in the bridge loopdetectmode menu: ■ disable — This default setting disables the module’s port-based algorithm.
Loop Detection 17 When the module disables a front-panel port to eliminate a loop, you must bring the port back online manually. Example: CB9000@slot 5.
CHAPTER 2: RELEASE HIGHLIGHTS CB9000@slot 1.
Bridge Address Learning Limits Bridge Address Learning Limits 19 By default, the 36-port 10/100BASE-TX Desktop Switching Modules (Model Numbers 3CB9LF36RL and 3CB9LF36TL) support two bridging addresses (learned plus static) per front-panel port. You can manually change this limit to a value from 1 through 36 addresses per port.
CHAPTER 2: RELEASE HIGHLIGHTS If the module disables a front-panel port, you must bring the port back online manually. The following example shows how to specify a maximum of six bridging addresses on port 1: CB9000@slot 5.
Secure Address Learning Mode 21 The source address in an incoming packet must match a static address that you have configured on a port before the packet can enter that port. If an incoming packet contains a different source address than the one set for the port, the module shuts the port down and you must bring the port back online manually. In secure mode, the module does not learn “unauthorized” source addresses.
CHAPTER 2: RELEASE HIGHLIGHTS Configuring One Untagged System VLAN The 36-port 10/100BASE-TX Desktop Switching Modules (Model Numbers 3CB9LF36RL and 3CB9LF36TL) support a backplanePortPVID command that allows you to assign one virtual LAN (VLAN) to be an untagged system VLAN on the backplane. Tagged frames that the module sends to the backplane on the selected untagged system VLAN are stripped of their tags and priority bits. All frames that belong to other VLANs are sent to the backplane tagged.
Broadcast, Multicast, and Flood Rate Limiting Broadcast, Multicast, and Flood Rate Limiting 23 You can define rate limits for broadcast, multicast, and flood packet types on the 36-port 10/100BASE-TX Desktop Switching Modules (Model Numbers 3CB9LF36RL and 3CB9LF36TL). To participate in broadcast, multicast, and flood rate limiting, a front-panel port must be configured for each rate limit packet type.
CHAPTER 2: RELEASE HIGHLIGHTS Example: CB9000@slot 5.1 [36L-E/FEN-TX-L2] (bridge): multicast Menu options (CoreBuilder 9000-10AD6C): igmp - Administer IGMP snooping multicastLimit - Set the multicast packet rate limit broadcastLimit - Set the broadcast packet rate limit floodLimit - Set the flood packet rate limit CB9000@slot 5.
Broadcast, Multicast, and Flood Rate Limiting 25 Example: If in a 1-second period, 3,500 fps are received from the backplane port, 3,000 packets are transmitted out ports 3 and 10. Port 11, however, which does not participate in module multicast rate limiting, transmits the entire 3,500 fps. Port Multicast Packet-ingress Rate Limiting You can define an ingress rate limit for multicast packets per port on the 36-port 10/100BASE-TX Desktop Switching Module.
CHAPTER 2: RELEASE HIGHLIGHTS This example sets the port-ingress threshold to 1000 fps for port 1. If incoming traffic exceeds this 1,000-fps threshold on the port for 7 continuous seconds, the module permanently disables the port. How Port Rate Limits and Thresholds Work The following example illustrates what happens when, for example, you specify an ingress threshold of 2,000 fps for multicast packets on ports 3 and 10.
RELEASE ISSUES 3 This chapter discusses the following issues for major software Release 3.0: Corrected Problems ■ Corrected Problems ■ System Issues ■ Known Problems ■ Documentation Changes This section discusses problems that have been corrected in software Release 3.0. The numbers that appear in parentheses at the end of some descriptions are for internal 3Com use only. ■ The system no longer displays os socket err after you reset the chassis and during the system start-up procedures.
CHAPTER 3: RELEASE ISSUES ■ ■ Current autonegotiation status is now correctly reflected the first time that you view the Ethernet summary and detail displays.
System Issues VLANs System Issues 29 ■ Removing the default VLAN before you create additional VLANs no longer causes modules to go down after a module reset. Previously, you had to move the module to another slot in the chassis to reinitialize. (26223) ■ Previously, in some configurations, the system did not allow the proper number of VLANs to be defined, causing an out-of-resources message. The system now allows correct VLAN definition.
CHAPTER 3: RELEASE ISSUES Management ■ You may experience slow performance (response time) when you perform a walk of the a3Com.29 MIB, particularly when you request the following fields: ■ a3ComBridgePortAddressBridgeIndex ■ a3ComBridgePortAddressPortIndex Performing a walk of this MIB may also affect the performance of the Administration Console interface and other management functions.
System Issues Bridging 31 ■ The rxFrameRate and rxBytes statistics in the ethernet detail 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 72 is displayed in the ethernet detail rxBytes field. Also, when 148,880 frames per second are sent into a 100 Mbit port, the value 151,143 frames per second is displayed in the ethernet detail rxFrameRate field.
CHAPTER 3: RELEASE ISSUES These control addresses are included in the bridge display address count field, but are not listed in the bridge port address list. Resilient Links ■ The 36-port 10/100BASE-TX Desktop Switching Modules (Model Numbers 3CB9LF36RL and 3CB9LF36TL) do not support resilient links. The modules have only one backplane port. IGMP ■ Do not allow a 36-port 10/100BASE-TX Desktop Switching Module (Model Number 3CB9LF36RL or 3CB9LF36TL) to act as an IGMP Querier.
System Issues ■ 33 When shipped from the factory, the 36-port 10/100BASE-TX Desktop Switching Modules (Model Numbers 3CB9LF36RL and 3CB9LF36TL), default to VLAN 1 and can communicate with all CoreBuilder 9000 ports on that VLAN. Each client (front panel) port on the 36-port 10/100BASE-TX Desktop Switching Module defaults to system VLAN 1, untagged. The module’s backplane port also defaults to VLAN 1, untagged.
CHAPTER 3: RELEASE ISSUES Known Problems This section describes problems that are known to exist in Layer 2 switching module operational software Release 3.0. The numbers that appear in parentheses at the end of some descriptions are for internal 3Com use only. System ■ At the Administration Console, entering a seemingly valid command string (two or more commands taken from menus and nested submenus) may not work. If this situation occurs, enter commands separately from one menu prompt at a time.
Known Problems ■ ■ snmplnASNParseErrs ■ snmplnBadVersion ■ snmplnBadCommunityNames ■ snmplnBadCommunityUses 35 The following ifIndex objects return invalid index numbers: ■ ipAdEntIfIndex ■ ipRouteIfIndex ■ ipNetToMediaIfIndex ■ An SNMP getnext ifIndex request with a very large instance ID returns the value ifIndex.1 rather than ifDescr.1, which is the next object in the MIB tree. ■ An SNMP get request on entLPPhysicalIndex is not implemented.
CHAPTER 3: RELEASE ISSUES ■ The following requests return incorrect or incomplete 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) is 13. The value should be 9, which represents the value for the module. The value of entPhysicalVendorType that is returned for the instance of the module itself (entPhysicalVendorType.4) contains an incorrect cb9000 description.
Known Problems ■ 37 The object a3ComSysBridgePortAddressStaticPort should return one of the following values: ■ ■ The local bridge port index when a static address is configured for the port The value 0 when a dynamic address is configured for the port However, the 9-port 1000BASE-SX Gigabit Ethernet Layer 2 Switching Module returns the following reversed values: ■ ■ ■ The value 0 when a static address is configured for the port If there is a trunk on the switching module, an SNMP getnext request
CHAPTER 3: RELEASE ISSUES Bridging ■ The bridge incorrectly forwards frames that are sent to their own port MAC address. Trunking ■ 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.
Known Problems 39 In addition, the port for which the report is requested does not have to be involved in the trunk for this situation to occur. ■ On a CoreBuilder 9000 with a single switch fabric module installed, 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.
CHAPTER 3: RELEASE ISSUES Documentation Changes Ethernet This section discusses issues that apply to CoreBuilder 9000 documentation. Table 16, Ethernet Media Specifications, in Chapter 5 “Ethernet” on page 93 of the CoreBuilder 9000 Implementation Guide, the Recommended Distance column for the 100BASE-FX multimode fiber should read 412 m and not 412 km.
4 SOFTWARE INSTALLATION This chapter contains the following topics: How to Obtain Software Image Files ■ How to Obtain Software Image Files ■ Installation and Upgrade Prerequisites ■ Downloading Software ■ Downgrading Switching Modules to Software Release 2.1.0 To obtain image files for software Release 3.0, contact your network supplier or 3Com representative, or visit the 3Com Web site at: http://support.3com.com/infodeli/swlib/index.
CHAPTER 4: SOFTWARE INSTALLATION CAUTION: Before you attempt to download any module software, save the configuration file for the release that you are currently running to an external device using the EME upload command. See the CoreBuilder 9000 Enterprise Management Engine User Guide for information about the EME upload command. CAUTION: If the EME contains a Release 3.0.
Installation and Upgrade Prerequisites 43 If you have a new module that uses software Release 3.0, you can now select a slot for your module and install it. See the Quick Start Guide for your module for guidelines and procedures. Verifying and Updating Modules for a New Chassis When you purchase a new chassis and modules, you may receive some modules that are loaded with software that is incompatible with other modules. CAUTION: All modules in a single chassis must operate at compatible software levels.
CHAPTER 4: SOFTWARE INSTALLATION To obtain software upgrades and release notes, see your network supplier or 3Com representative, or visit the 3Com Web site at: http://support.3com.com/infodeli/swlib/index.htm 10 Download software to appropriate switch fabric modules and interface modules in any order. CAUTION: Downloaded software does not become active on a module until you cycle the power to the module slot.
Downloading Software ■ 45 You have loaded the boot image and the operational load image in the file server directory, usually named “tftp” or “tftpboot”, from the Software CD-ROM or from the 3Com Web site at the following URL: http://support.3com.com/infodeli/swlib/index.htm ■ The management modules (EME and EMC) that are installed in your chassis are running the compatible software release before you can attempt a module download.
CHAPTER 4: SOFTWARE INSTALLATION 3 Confirm that all of the downloads were successful. To verify that the software releases that you downloaded are correct and that the information in the module’s Auto Emergency Download fields is correct, enter the following command: show module .1 verbose 4 Update the Emergency Download parameters. See “Update Emergency Download Parameters”next and complete all the steps.
Downloading Software 47 3 At the prompt, enter nvData The nvdata menu options screen appears. 4 At the prompt, enter emergencyDownload The following prompt appears: Enter file server IP address {?} []: Where is the location of the server where the 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.
CHAPTER 4: SOFTWARE INSTALLATION Downgrading Switching Modules to Software Release 2.1.0 Follow this procedure to downgrade the switching modules in your chassis that are running software Release 3.0 to software Release 2.1.0: CAUTION: The 36-port 10/100BASE-TX Desktop Switching Modules (Model Numbers 3CB9LF36RL and 3CB9LF36TL) cannot be downgraded to software releases earlier than Release 3.0.0. 1 Download the operational code for your previous software Release 2.1.
5 REFERENCE This chapter contains the following topics: Identifying Modules in the Switch ■ Identifying Modules in the Switch ■ Applicable Documents ■ MIB Files ■ Entering Commands ■ Understanding Autonegotiation ■ Year 2000 Compliance The CoreBuilder 9000 Enterprise Switch uses an abbreviated version of each module name in various menu prompts and displays. Table 3 lists the model numbers of modules, descriptions, and the corresponding abbreviated name.
CHAPTER 5: REFERENCE Table 3 Identifying Modules in the CoreBuilder 9000 (continued) Model Number Description Abbreviated System Identification Name 3CB9LF10MC 10-Port 100BASE-FX Fast Ethernet Layer 2 Switching Module 10-E/FEN-FX-L2 3CB9LF20MM 20-Port 100BASE-FX (MT-RJ) Fast Ethernet Layer 2 Switching Module 20-E/FEN-FX-L2 3CB9LF36R 36-Port 10/100BASE-TX Fast Ethernet RJ-45 Layer 2 Switching Module 36-E/FEN-TX-L2 3CB9LF36T 36-Port 10/100BASE-TX Fast Ethernet Telco Layer 2 Switching Module
Applicable Documents Applicable Documents MIB Files 51 For information about installing, managing, and using the Layer 2 switching modules, as well as their specifications, see these documents: ■ The Quick Start Guide that is shipped with each module ■ CoreBuilder 9000 Implementation Guide ■ Command Reference Guide, which covers the CoreBuilder 3500, 9000, and 9400, and the SuperStack® II Switch 3900 and 9300 products.
CHAPTER 5: REFERENCE ■ IF-MIB-V1SMI.mib — IF MIB Version 1, RFC 1573. Unsupported tables in this MIB: ■ ■ ifTestTable ■ ifRcvAddressTable ■ ifHC 64-bit counters MIB2-MIB.mib — MIB-II MIB, RFC 1213. Unsupported group in this MIB: egp group ■ RMON-MIB.mib — RMON MIB, RFC 1757. Supported groups in this MIB: 3Com Enterprise MIBs ■ statistics ■ history ■ alarm ■ event ■ SNMPv2-MIB.mib — Used by other MIBs. ■ 3Com Enterprise MIBs — See “3Com Enterprise MIBs” next.
Entering Commands ■ 3cVlan.mib — 3Com VLAN MIB (43.10.1.14.1). ■ 3cWeb.mib — 3Com Web Management MIB (43.29.4.24). ■ cb9000Mod.mib — Layer 2 and Layer 3. 53 MIB names and numbers are usually retained when organizations restructure their businesses; therefore, some of the 3Com Enterprise MIB names may not contain the word “3Com.
CHAPTER 5: REFERENCE ■ If a Gigabit Ethernet switching module port has autonegotiation enabled with the port enabled, but the remote end of the connection has autonegotiation enabled with the port disabled, the enabled port goes on-line and the port LED lights green. The disabled port stays off-line. To avoid such problems, 3Com recommends that you always set the connected port pairs to the same mode, in one of the following ways: ■ Enable autonegotiation at both ends of the connection.
6 TECHNICAL SUPPORT 3Com provides easy access to technical support information through a variety of services. This chapter describes these services. Information contained in this chapter is correct at time of publication. For the most recent information, 3Com recommends that you access the 3Com Corporation World Wide Web site.
CHAPTER 6: TECHNICAL SUPPORT 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 your FTP client: ■ Hostname: ftp.3com.com ■ Username: anonymous ■ Password: You do not need a user name and password with Web browser software such as Netscape Navigator and Internet Explorer.
Support from Your Network Supplier 57 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 Automated Fax Service The 3Com Facts automated fax service provides technical articles, diagrams, and troubleshooting instructions on 3Com products 24 hours a day, 7 days a week.
CHAPTER 6: TECHNICAL SUPPORT When you contact 3Com for assistance, have the following information ready: ■ Product model name, part number, and serial number ■ A list of system hardware and software, including revision levels ■ Diagnostic error messages ■ Details about recent configuration changes, if applicable Here is a list of worldwide technical telephone support numbers: Country Telephone Number Country Telephone Number Asia, Pacific Rim Australia Hong Kong India Indonesia Japan Malays
Returning Products for Repair Country Telephone Number North America 1 800 NET 3Com (1 800 638 3266) Country 59 Telephone Number Enterprise Customers: 1 800 876-3266 Returning Products for Repair Before you send a product directly to 3Com for repair, you must first obtain an authorization number. Products sent to 3Com without authorization numbers will be returned to the sender unopened, at the sender’s expense.
