ONcore ATM Switch/Control Module Installation and User's Guide Document Number: 17-00616-3 Printed March 1996 Model Number: 6416SW 3Com Corporation 118 Turnpike Road Southborough, MA 01772-1886 U.S.A.
Federal Communication Commission Notice This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.
This is to certify that the (6416SW) is shielded against radio interference in accordance with the provisions of Vfg 243/1991. The German Postal Services have been advised that this equipment is being placed on the market and that they have been given the right to inspect the series for compliance with regulations. Compliance with applicable regulations depends on the use of shielded cables. The user is reponsible for procuring the appropriate cables.
Fiber Cable Classification Use this equipment only with fiber cable classified by Underwriters Laboratories as to fire and smoke characteristics in accordance with section 770-2(b) and Section 725-2(b) of the National Electrical Code.
The following terms are trademarks or service marks of the IBM Corporation in the United States or other countries: AIX, AIXwindows, IBM, NetView for AIX, Nways and RISC System 6000. XNS is a trademark and Ethernet is a registered trademark of Xerox Corporation.
vi ONcore ATM Switch/Control Module: Installation and User's Guide
Contents Chapter 1. Introduction to ATM . . . . . . 3Com ONcore ATM Subsystem . . . . . . . ATM Backplane . . . . . . . . . . . . . . . ATM Switch/Control Module . . . . . . . . ATM Subsystem Traffic Management . . ATM Subsystem Chassis Management . Benefits of Using ATM in the ONcore Hub LAN Emulation Client (LEC) . . . . . . . . . Chapter 2. Installation . . . . . . . Before You Start . . . . . . . . . . . Unpacking the Module . . . . . . . . Installing the 6416SW Module . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . Entering 6416SW Commands . . . . . . . . . . . . . . . . Keyboard Functions . . . . . . . . . . . . . . . . . . . . . . Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . Command Completion . . . . . . . . . . . . . . . . . . . . Setting Up a Configuration Console in Normal (ASCII) Mode Setting Up a Configuration Console in SLIP Mode . . . . .
Default Gateway (IP & LE) . . . . . . . . . . . ARP Server (IP only) . . . . . . . . . . . . . . Community Table (IP & LE) . . . . . . . . . . Alerts (IP & LE) . . . . . . . . . . . . . . . . . Setting the LECS ATM Address . . . . . . . . . Saving Configuration Settings and Logging Off Working With Configuration Settings . . . . . . . Reverting Configuration Changes . . . . . . . Displaying Configuration Settings . . . . . . . Modifying Configuration Settings . . . . . . .
ONcore Cannot PING the ARP Servers and Vice-versa . . . . . ONcore Hub Cannot PING an ARP Client . . . . . . . . . . . . . ONcore LEC Cannot PING another Client and Vice-versa . . . ARP Client Cannot PING the ARP Server . . . . . . . . . . . . . Two Devices Using IP Over a PVC Cannot Ping Each Other . . ONcore LEC Cannot Initialize to the LES/BUS . . . . . . . . . . Administrative Problems (Netview/SNMP/Telnet) . . . . . . . . . Communication Problems in an IBM LAN Emulation Environment Other Problems . . .
Appendix D. Configuring AIX for Download and Upload Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix E. ONcore ATM Address Formats Network Prefix . . . . . . . . . . . . . . . . . End System Part . . . . . . . . . . . . . . . Appendix F. Technical Support . . . . . Online Technical Support . . . . . . . . . . E-mail Technical Support . . . . . . . . . World Wide Web Site . . . . . . . . . . . Support from Your Network Supplier . . . . Support from 3Com . . . . . . . . . . . . .
xii ONcore ATM Switch/Control Module: Installation and User's Guide
Figures 1-1. 1-2. 2-1. 2-2. 2-3. 2-4. 3-1. 3-2. 3-3. 3-4. 4-1. 6-1. B-1. B-2. B-3. B-4. B-5. B-6. E-1. ATM Backplane in the 17-slot 3Com ONcore Hub . . . . Wiring Star Topology in ATM Backplane (17-slot model) . Installing the 6416SW Module in an ONcore Hub . . . . . ONcore Module Ejectors . . . . . . . . . . . . . . . . . . . Attaching a Terminal to the 6416SW RS-232 Console Port Front Panel of 6416SW Module . . . . . . . . . . . . . . . Components of an ATM Campus Network . . . . . . . . .
xiv ONcore ATM Switch/Control Module: Installation and User's Guide
Tables 1-1. 1-2. 2-1. 2-2. 2-3. 5-1. 7-1. B-1. C-1. C-2. C-3. ATM Connections Supported in ONcore Hubs . . . . . . . . . 1-7 Maximum PING and TELNET Message Lengths . . . . . . 1-15 Meaning of the 6416SW LEDs . . . . . . . . . . . . . . . . . 2-10 RS-232 Console Port Pin Assignments (DB9) . . . . . . . . 2-13 RS-232 Auxiliary Port Pin Assignments . . . . . . . . . . . . 2-14 6416SW Configuration Commands . . . . . . . . . . . . . . . 5-4 6416SW Trap Messages . . . . . . . . . . . . . . . . . . . .
xvi ONcore ATM Switch/Control Module: Installation and User's Guide
How to Use This Guide This guide presents information on how to install and configure the 3Com ONcore ATM Switch/Control Module (Model Number 6414SW) in the 3Com ONcore Switching Hub. It describes how to diagnose and solve problems associated with the operation of the 6416SW module, and describes some of the principles of asynchronous transfer mode (ATM) technology on which the 6416SW module is based. This guide also describes how to install and configure a management console for the 6416SW module.
Chapter 3, “ATM Addressing” describes the components of an ATM Campus network, guidelines for defining ATM addresses for the 6416SW, how to set up trunk connections within and between networks, and how to use Permanent Virtual Connections (PVCs). It also describes how to connect a console to the 6416SW module in order to perform configuration tasks.
Appendix E, “ONcore ATM Address Formats” describes the ATM addressing formats. Appendix F, “Technical Support” describes the support services provided by 3Com Corporation.
Prerequisite Knowledge To understand the information presented in this guide you should be familiar with: Features and characteristics of the 3Com ONcore Switching hub, as described in 3Com ONcore Switching Hub Installation and Operation Guide, 17-00362. Principles of asynchronous transfer mode (ATM) technology ATM Forum UNI Specifications V3.0 and V3.1. ATM Forum LAN Emulation Specifications V1.0.
Conventions Used in This Guide The following text conventions are used in this guide: Text Convention Meaning Example Bold Text emphasis Selective backpressure temporarily stops one virtual connection. Global backpressure temporarily stops an ATM link. Italics Special term This is known as a hot swap. Document titles Refer to the ATM User-Network Interface Specification - Version 3.0 for more information. Command syntax (parameters and variables) SET PORT slot.
Related Documents This section provides information on supporting documentation, including: 3Com Documents Reference Documents 3Com Documents The following documents provide additional information on 3Com products: ONcore Switching Hub Installation and Operation Guide 17-00362 provides information on the installation, operation, and configuration of the ONcore Switching Hub. This guide also describes the principal features of the ONcore Fault-Tolerant Controller Module.
Reference Documents The following documents supply related background information: Case, J., Fedor, M., Scoffstall, M., and J. Davin, The Simple Network Management Protocol, RFC 1157, University of Tennessee at Knoxville, Performance Systems International and the MIT Laboratory for Computer Science, May 1990. Rose, M., and K. McCloghrie, Structure and Identification of Management Information for TCP/IP-based internets, RFC 1155, Performance Systems International and Hughes LAN Systems, May 1990.
Service and Support 3Com Corporation is committed to providing our customers with a full range of support services to provide maximum network uptime. This section describes: Warranty Information Software Subscription Service Support Warranty Information 3Com products are covered under a limited factory warranty. This warrranty covers defects in the hardware, software, or firmware. Hardware and firmware is covered for one year and software is covered for 45 days.
Note: You can buy SSS for less that a full year period so that all software products have the same renewal date for your convenience. Support 3Com Corporation supports product-related questions through the Customer Support Organization (CSO). CSO is available Monday through Friday from 8:30 am to 8:00 pm, Eastern Time. Technical Support Engineers are available to help diagnose and solve customer problems.
xxvi ONcore ATM Switch/Control Module: Installation and User's Guide
Chapter 1. Introduction to ATM This chapter presents an overview of the main principles and modes of operation of asynchronous transfer mode (ATM) technology on which the 3Com ONcore ATM Switch/Control (6416SW) module is based. It also describes how ATM is implemented in the 3Com ONcore Switching Hub and shows how an ONcore-based ATM campus network can be built by interconnecting ATM subsystems.
3Com ONcore ATM Subsystem By interconnecting 3Com ONcore Switching hubs, you can build a private campus network that uses ATM to provide: The backbone structure, with possible extensions to the WAN New LAN capability for attaching workstations and servers with dedicated bandwidth and isochronous transmission. ATM is implemented in the ONcore hub to permit existing LANs (such as Token-Ring) to coexist with the new ATM technology.
ATM Backplane All data transmitted between modules in the ATM subsystem passes through the ATM backplane. Data is switched between ATM media modules in the ATM subsystem by a 6416SW module. 6416SW modules are installed in slot positions 9 and 10 in the ATM backplane of 10-slot models, and slot positions 9 and 10 and/or 11 and 12 in the ATM backplane of 17-slot models. These positions are shown in Figure 1-1.
The major difference between the ATM backplane and other ONcore hub LAN backplanes is that each ATM media module has a dedicated set of connections to the 6416SW module. This set of dedicated connections constitutes a wiring star topology in which ATM media modules are at the tips of the star and the 6416SW module is at the center. The wiring topology used in the ATM backplane is shown in Figure 1-2.
The main characteristics of the ATM backplane are as follows: Modular structure Full floating ATM media modules Support of two 6416SW modules for reliability and redundancy (in 17-slot models) Full coexistence with existing legacy LAN modules. ATM media modules can be hot-swapped into any open slot. Also, you can remove an ATM module and re-insert it into another slot without disturbing the operation of other ATM modules and without causing a failure in ATM connections in the hub.
ATM Switch/Control Module The ATM Switch/Contol Module (6416SW) module used in the ONcore hub consists of two cards packaged into a double-slot module: A base card (ATM Switch fabric) that switches cells from one ATM port to another ATM port or to another output link on the same module. ATM cell switching is carried out by means of the Switch integrated circuit, a technology used by the ONcore switch. This single chip is a non-blocking 16-by-16 times 256 Mbps 8-bit parallel switch.
The 3Com ONcore Switch imbedded Control Point provides a complete set of functions to control an ATM campus network and to interconnect local ATM networks over ATM wide area networks. The Control Point supports an extensive set of ATM connections, including: Switched (SVC) and permanent (PVC) Point-to-point and point-to-multipoint Reserved Bandwidth (RB) and Available Bit Rate (ABR) Note: The Available Bit Rate service will be available in future releases of the 6416SW module. Table 1-1.
Each 3Com ONcore Switch/Control provides the following functions: Control plane: – Support of ATM signaling (SVCs) according to ATM Forum V3.0 and V3.1 specifications. – Switch-to-switch interface (SSI) based on an extension of the ATM Forum UNI V3.0 as stated in the ATM Forum P-NNI framework – Topology services and route computation based on TRS, with automatic bypass of failed nodes and links only for SSI connections (TRS is an extension of OSPF, Open Shortest Path First.
Management plane: – Full SNMP support (get, getnext, set, and traps) – MIB-II support – IETF AToMIB – Full Interim Local Management Interface (ILMI) support at UNI and from the network management station – OSPF MIB support for managing topology and route computation – 3Com extension — — — — Hub-specific: switch, modules and ports Enhanced PVC management (automatic route computation and recovery) Signalling (Q.
The SNMP ATM agent is a function of the Control program in the 6416SW module and implements the ATM MIB defined in the V3.0 UNI Specification of the ATM Forum. The AToMIB is defined by the IETF and by the 3Com extensions. It can be driven by SNMP managers, such as IBM NetView for AIX . The 3Com ATM management application, Transcend ONcore ATM Campus Manager, can be used by a LAN administrator to better tune the system. Both PVCs and SVCs are supported.
ATM Subsystem Traffic Management High-speed ATM networks support a variety of applications with different traffic and quality of service (QOS) requirements. For example, multimedia and time critical data applications require guaranteed levels of delay and throughput, while other applications can tolerate variations in delay and throughput (LAN traffic). This diversity requires different congestion management methods.
ATM Subsystem Chassis Management Management of the ATM subsystem can be achieved in two ways: Via a Distributed Management Module (DMM) installed in the ONcore hub. Via the 6416SW module, which contains a subset of DMM, when the ONcore hub is only running ATM. (Check the Release Notes for the level of 6416SW code required). Note: If a DMM module is present, or hot-inserted, in the hub, the DMM module will assume chassis management, and 6416SW commands entered will not be effected.
ATM Switch/Control Redundancy By installing a second 6416SW in a 17-slot hub, a backup to the active 6416SW is provided (check the Release Notes for the level of 6416SW and the level of code required). If the active 6416SW fails, the standby will take over control. The active 6416SW continually updates the tables in the standby 6416SW to ensure that the backup configuration is current, and to reduce the impact should a switch to the standby be required.
Benefits of Using ATM in the ONcore Hub The use of ATM in the ONcore hub offers the following benefits: Use of ATM in local and wide area networks, and in both private and public networks ATM support for multimedia applications and mixed traffic, such as voice, video, and data Extension of current application solutions by providing bandwidth on demand and allowing applications to share bandwidth Support for current and future high-bandwidth applications and protocols Low transfer delay and support for both
LAN Emulation Client (LEC) The 6416SW contains an integrated ‘lite’ LEC that provides basic LAN emulation client functions for use by an SNMP agent or for Internet FTP functions. Such functions include Netview, TELNET, and TFTP. The LEC implementation is fully ATM Forum compliant. The maximum length of PING and TELNET messages depends on the maximum SDU size supported on the corresponding emulated LAN. Table 1-2 lists the correspondence (in bytes): Table 1-2. Maximum PING and TELNET Message Lengths 802.
1-16 ONcore ATM Switch/Control Module: Installation and User's Guide
Chapter 2. Installation This chapter describes how to install the 6416SW module. Before you unpack the module, please follow the precautions in “Before You Start.” Before You Start Take the following precautions before unpacking the 6416SW module: Do not remove the 6416SW module from its anti-static shielding bag until you are ready to insert it into the ONcore hub. This avoids the possibility of having electrostatic discharge damage static-sensitive devices in the 6416SW cards.
Unpacking the Module To unpack the 6416SW module, follow these steps: 1. Remove the 6416SW module from the shipping carton. 2. Remove the 6416SW module from the anti-static bag and inspect it for damage. Always handle the module by the faceplate being careful not to touch the internal components. If the module appears damaged, put it back in the anti-static bag, and put the bag back into the shipping carton. Then contact your local 3Com dealer or 3Com representative.
Installing the 6416SW Module To install a 6416SW module in the ONcore hub, follow these steps: 1. Install the ONcore hub in its rack or on a desktop by following the instructions in the 3Com ONcore Hub Installation Guide (17-00362). 2. Insert the 6416SW module into slots 9 and 10 (or slots 11 and 12 in A17 models) of the hub by matching the top and bottom board guides as you slide the module cleanly into place (by pressing evenly on the top and bottom of the faceplate).
4. Close the top and bottom ejectors simultaneously. Figure 2-2.
5. Fasten the spring-loaded screws on the front panel of the module to the hub using your fingers. Do not over-tighten. 6. (optional) Press the LED Test button on the Controller module to verify that all LEDs are functional. 7. If you want to use a local console to configure (out-of-band) the ATM subsystem, you must attach an ASCII-type terminal to the RS-232 Console port on the 6416SW module. The connection can either be local or via modems.
1 1 2 2 3 3 4 4 AT ST ITY TIV AC AT ST ITY TIV AC RS-232 Console port RE T SE SE RE T PORT 2 PORT 3 PORT 4 LE T DU SE MO RE LE T DU SE MO RE PORT 1 PORT 1 PORT 2 PORT 3 PORT 4 Figure 2-3. Attaching a Terminal to the 6416SW RS-232 Console Port 9. Attach cables to the ATM media modules and ATM user devices you want to use. Then enter 6416SW commands from the console (as described in Chapter 5, “Configuring the ATM Switch/Control Module” on page 5-1) to configure the ATM subsystem.
Verifying Normal 6416SW Operation After installing the 6416SW module, you can verify that it is operating properly by checking the status of the LEDs and the message displayed on the console screen. The position of the LEDs is shown in Figure 2-4 on page 2-9. The RUNNING LED on the module should light (yellow). The ACTIVE LED should light (yellow) if the 6416SW module is managing ATM media modules. The WRONG SLOT LED should not light.
Front Panel The front panel of the 6416SW module contains: Seven LEDs that show the operating state of the module 9-pin RS-232 Console port 9-pin RS-232 Auxiliary port (reserved for 3Com service personnel) ATM Reset button that resets all ATM modules (6416SW and ATM media) in the ONcore hub.
Running LED Active LED AC TI V ST E BY Standby LED Maintenance LED E R RR U O N R N IN G Error LED M AI N Reset LED ATM Reset button (resets all ATM modules and ATM traffic) R T ES ET R AT ES M ET RS-232 CONSOLE RS-232 Console Port RS-232 AUXILIARY RS-232 Auxiliary Port Wrong Slot LED W R SL ON O G T Figure 2-4.
Meaning of the LEDs Table 2-1 shows the meaning of each LED on the front panel of the 6416SW module. Table 2-1 (Page 1 of 2). Meaning of the 6416SW LEDs LED Name Color State Meaning Active Yellow OFF 6416SW module is not able to control ATM traffic and ATM media modules. ON 6416SW module is able to control ATM traffic and ATM media modules. OFF Either a second 6416SW module is not installed or, if a second 6416SW is installed, it is not active.
Table 2-1 (Page 2 of 2). Meaning of the 6416SW LEDs LED Name Color State Meaning Maintenance (MAINT) Yellow OFF 6416SW module is functioning properly. ON Maintenance mode is active. OFF 6416SW module is functioning properly. ON 6416SW and ATM media modules in hub are being reset. OFF Normal operation. ON 6416SW module is not installed in the correct slots.
ATM Reset Button The ATM Reset button resets the 6416SW and all ATM media modules in the ONcore hub. All data traffic and connections in the ATM subsystem are stopped. Press this button when instructed after you correct an error condition. Before pressing it, be sure to save any configuration settings entered in the current session with the SAVE command. When you press the ATM Reset button, all unsaved settings will be lost.
RS-232 Console Port The 9-pin RS-232 Console port (the topmost RS-232 port on the front panel) is a DTE male connector (DB-9) to which a console or modem is connected in order to: Initialize the 6416SW module at installation. Enter 6416SW network management commands (described in the ONcore Switching Hub/CELLplex 4000 ATM Command Reference Guide). Download new software versions. Table 2-2.
RS-232 Auxiliary Port The 9-pin RS-232 Auxiliary serial port (the bottommost RS-232 port on the front panel) is also a DTE male connector (DB-9). The RS-232 Auxiliary port is reserved for 3Com service engineers. No device should be connected to it during normal hub operation. Table 2-3.
Chapter 3. ATM Addressing This chapter describes: The components of an ATM Campus Network Guidelines for defining an ATM Address for the ATM Switch/Control How to set up trunk connections within and between subnetworks How to use Permanent Virtual Connections (PVCs). ATM Campus Networks The purpose of an ATM network is to set up connections between ATM user devices, the two endpoints of a connection.
Figure 3-1.
Network Components The various parts of the ATM address form a hierarchy of network components, as shown in Figure 3-2. Figure 3-2. ATM Address Hierarchy For a full description of the ATM address formats supported by the 6416SW, see Appendix E, “ONcore ATM Address Formats” on page E-1. The terms used to describe the components of an ATM Campus Network are defined here: ATM Campus Network One or more ATM subnetworks interconnected using NNI interfaces.
ATM Subnetwork One or more ATM clusters interconnected using NNI interfaces. An ATM subnetwork is identified by: The first 9 bytes of the network prefix, which are the same for all subnetworks in a Campus Network, plus A 2-byte routing domain number (RDN), which is unique within the ATM Campus Network. ATM Cluster One or more ATM subsystems interconnected using SSI interfaces.
An ATM User Device is identified by: The first 13 bytes of the network prefix, which are the same for all user devices attached to an ATM subsystem, plus A 6-byte End System Identifier (ESI), unique within the ATM Subsystem, plus A 1-byte Selector field that may be used by the user device. The 6416SW passes the network prefix of an ATM address to attached end systems using the Interim Local Management Interface (ILMI) protocol.
Network Interfaces ATM standards define three protocols used across the interfaces connecting the components of an ATM campus network: UNI Defines the interface between an ATM User Device (such as a terminal, router, bridge, server, workstation, or concentrator equipped with an ATM adapter) and the ATM network. The ATM subsystem supports the private UNI defined by the ATM Forum UNI Specification V3.1. SSI Defines the interface between two ATM switches in the same ATM Cluster.
Defining the ATM Address of the 6416SW A default ATM address is provided with the 6416SW. You can continue to use this default address only if you use your 6416SW as a stand-alone ATM switch. If you want to connect the 6416SW to other ATM subsystems, the ATM address must be defined as follows: AFI-RDN The first (leftmost) 11 bytes of the Network Prefix is the address of the ATM subnetwork to which this 6416SW belongs.
Setting-Up ATM Trunk Connections To configure a trunk between two ATM subnetworks or two ATM clusters in the same subnetwork over a virtual path (VP) service provider, you must configure a logical link between a pair of ATM ports. The ATM ports must both use a network-to-network (NNI) interface and be on the boundary hub of each subnetwork or cluster. Figure 3-3 shows an example of logical links between pairs of ATM clusters from a boundary hub in each cluster. Figure 3-3.
You can configure multiple logical links over the same physical port. However, you can only configure one logical link (using one pair of ATM ports) for each ATM cluster-to-cluster or subnetwork-to-subnetwork connection. Using Static Routes In an ONcore/CELLplex 4000 ATM network, you can only set a logical link to a cluster number (ACN) that is defined within your own ATM subnetwork.
Trunks Between Subnetworks In order to define a logical link between switches in different subnetworks, you must also use the SET STATIC_ROUTE command to associate the address of the boundary hub in the remote cluster with a locally defined ACN. The SET LOGICAL_LINK command then uses this ACN to establish the logical link with the remote cluster.
Example: Configuring a Connection Between User Devices When configuring a connection between two ATM user devices attached to different subnetworks (for example, between Workstation D and Workstation E in Figure 3-4 on page 3-12), you must: Configure the route between the clusters in the first subnetwork; for example, between Clusters A and B in subnetwork Y. Configure the route between the clusters in both subnetworks; for example, from Cluster B in subnetwork Y to Cluster C in subnetwork X.
4. From hub H (boundary hub), enter the SET LOGICAL_LINK command with the ACN for Cluster A. The ATM address of Workstation D is known in Cluster A by the TRS updates. Figure 3-4.
Using Permanent Virtual Connections Permanent virtual connections (PVCs) for virtual channel and virtual path connections are created via the SET PVC command. See the ONcore Switching Hub/CELLplex 4000 ATM Command Reference Guide for details.
3-14 ONcore ATM Switch/Control Module: Installation and User's Guide
Chapter 4. Setting-Up and Using a Configuration Console This chapter describes: How to enter commands and get help on the 6416SW configuration console How to set up the 6416SW configuration console in Normal (ASCII) mode How to set up the 6416SW configuration console via a SLIP protocol connection How to access the 6416SW from a remote console via TELNET How to reconfigure configuration console settings.
SLIP mode In SLIP mode, commands are entered via a TELNET session between an IP workstation and the 6416SW. If your workstation supports TFTP, it can also be used as a TFTP server to perform DOWNLOAD and UPLOAD operations between your workstation and the ONcore. (See “Uploading and Downloading Operations” on page 6-5.) Note: If no activity takes place for a period of 20 minutes, the console is automatically returned to normal mode.
Before You Start The following section describes keystrokes and the command syntax to use to enter 6416SW commands from a configuration console. For a complete description of all 6416SW configuration commands, see the ONcore Switching Hub/CELLplex 4000 ATM Command Reference Guide. Entering 6416SW Commands By entering commands at the prompt on the 6416SW configuration console, you can configure various functions of the 6416SW.
Keyboard Functions When entering 6416SW commands the following keyboard functions are available: Keystroke Function BS or Backspace Moves the cursor one space backward and deletes the character. Enter Runs the command or prompts you to enter missing parameters. Space bar Types the complete 6416SW command. Ctrl + C Cancels the command that is currently running and returns you to a blank command line. Ctrl + R Retypes the last command you entered on the command line.
Getting Help @ To get help on available 6416SW commands, type ? on the command line and press Enter. For example, to see what commands start with the word SAVE, you would enter: ONcoreATM> save ? [ENTER] @ The following response is displayed: Possible completions: alert all community device lan_emul module_port static_route terminal tftp @ If you logged on as the system administrator, you can enter ? to display a list of all active 6416SW commands.
Command Completion The 6416SW management command line accepts abbreviated command input with a facility called command completion. Command completion lets you enter a command and its parameters by typing the minimum number of characters to uniquely identify the command or a parameter.
Setting Up a Configuration Console in Normal (ASCII) Mode The following procedure sets up the configuration console in Normal mode and logs you on as the system administrator with full access to all 6416SW commands: 1. Connect an ASCII-type terminal to the RS-232 console port on the front panel of the 6416SW. 2. In the terminal’s user guide, locate the procedure for setting parameters for baud rate, data bits, parity, and stop bits. 3.
Setting Up a Configuration Console in SLIP Mode The procedure that follows sets up the configuration console in SLIP mode and logs you on as the system administrator with full access to all 6416SW commands. Note: A typical workstation includes two serial ports (COM1, COM2): One dedicated to an ASCII-terminal emulator, The other dedicated to an IP stack and supported via the SLIP protocol. Both ports are needed for this procedure. 1.
7. Configure the IP stack SLIP with the IP address of the 6416SW and verify the 6416SW-to-workstation connectivity by issuing a PING request. @ C:\ping 9.1 .86.138 [ENTER] 8. Start a TELNET session to the 6416SW. @ ONcoreATM> telnet 9.1 .86.139 [ENTER] 9. Logon as administrator. The Welcome screen is displayed: @ Password: Welcome to system administrator service on ONcore.
SLIP Support The SLIP function is supported on: TCP/IP for AIX version 3.2.5 TCP/IP V2.1.2 for IBM DOS V7 (no TFTP support) TCP/IP V2.0 for OS/2 V3 (WARP) ChameleonNFS V4.0 for Windows Using TCP/IP for AIX version 3.2.5 1. Enter smitty mkinet 2. Enter serial line INTERNET Network Interface 3. Configure the local and remote IP addresses 4. The mask is not required 5. Do not fill in the baud rate and the dial string 6. PING the IP address of the remote 6416SW. Using TCP/IP V2.1.
Using TCP/IP V2.0 for OS/2 V3 (WARP) 1. Configure the SLIP connection using the TCPIPCFG icon then SLIP. 2. Enable the SLIP interface on the correct COMM port. 3. Keep VJ compression off and use 1000 as MTU size. 4. Configure the local and remote IP addresses. 5. The mask is not required. 6. Configure FTFP server using TCPIPCFG icon thru AUTOSTART. This is required in the FTFP server for 6416SW download and upload operations. 7. Set terminal speed with the mode com1 command. 8.
TELNET Sessions Via a Remote Switch The 6416SW’s remote login feature allows you to log on to an 6416SW from a remote configuration console or network workstation that supports the TELNET protocol. You can remotely log on to only one 6416SW at a time. Minimum Local Configuration Before you can log on to the 6416SW from a remote switch, you must perform a minimum configuration using a configuration console (in either Normal or SLIP mode).
Logon Procedure @ You specify the 6416SW by entering its IP address with the TELNET command: C:\ telnet 123.94.2 2.9 [ENTER] Once you are connected to the remote switch, you must log on by entering the correct password. Afterwards all the commands you enter are run on the remote module as if entered from a local 6416SW session. @ To log off from a TELNET session, enter the LOGOUT command.
Figure 4-1 shows an example of an 6416SW remote login. Note that once you are connected to 6416SW A, you can remotely log on and manage the 6416SW modules in either hub B or hub C. Note: The TELNET protocol is not routable. Hub C Hub B Hub A RS-232 Console Port of a 6416SW Module Modem Modem Figure 4-1. Working in Remote 6416SW Sessions You can set a timeout period for a remote 6416SW by entering the SET TERMINAL TIMEOUT command.
Reconfiguring 6416SW Configuration Console Settings Carry out the procedures in this section only if you need to connect another device (besides the 6416SW configuration console) to the 6416SW, and if the other device runs at a slower baud rate, uses a different parity, or has a different data bit value than the 6416SW's pre-configured factory settings.
Automatic Modem Hangup If you use a modem to connect to the 6416SW, you can use the SET TERMINAL HANGUP command to automatically hang up the modem connection when you log off the 6416SW. If you do not hang up the modem connection, an unauthorized user can pick up your open session and work in it. @ The following command shows what to enter to automatically hang up the modem after you log off the 6416SW. The command is set by default to disable so that the modem does not automatically hang up.
Chapter 5. Configuring the ATM Switch/Control Module This chapter describes: How to enter the commands needed to configure the 6416SW module How to save, modify and revert configuration settings How to use 6416SW commands for fault management. Before beginning the procedures listed below, make sure that: 1. You have installed the 6416SW module correctly (see Chapter 2, “Installation” on page 2-1) 2.
Configuration Summary To configure the 6416SW, follow the steps listed below. Each of these steps is described in a subsequent section of this chapter. 1. Set the 6416SW user and administrator passwords. 2. Set the internal clock. 3. Set the local 6416SW parameters such as: Switch name Switch location Service contact information Console prompt Console timeout 4. Define the ATM address of the 6416SW. This resets the ATM subsystem. 5.
9. If you want external LAN Emulation Configuration Server (LECS) support, configure the LECS ATM address or fixed PVC, depending on the configuration requirements of the LECS and external LECs (workstations, bridges, and so on). 10. Save all the configuration settings for the 6416SW. Some of these procedures are mandatory; others are recommended. They are summarized in Table 5-1 on page 5-4.
Table 5-1 (Page 1 of 2).
Table 5-1 (Page 2 of 2). 6416SW Configuration Commands Procedure 6416SW Command Priority Set SNMP parameters - Classical IP SET SET SET SET SET Mandatory to manage the 6416SW from a Classical IP subnetwork Set SNMP parameters - LAN emulation SET DEVICE LAN_EMULATION_CLIENT SET DEVICE DEFAULT_GATEWAY SET COMMUNITY SET ALERT Mandatory to manage the 6416SW from an 802.
Setting 6416SW Passwords It is necessary to set two levels of 6416SW passwords: Administrator password that provides access to all 6416SW commands with read-write (configuration) access User password that provides access to a subset of 6416SW commands including most SHOW commands, PING and TELNET. See the ONcore Switching Hub/CELLplex 4000 ATM Command Reference Guide for more information on access to 6416SW commands. Administrator Password 1.
@ ONcoreATM> save device Then press Enter. You will need to enter the new administrator password the next time you log on to the 6416SW. Note that you have only ten seconds to enter a password when the Password prompt is displayed. If you do not enter a password, a Timeout message is displayed. To redisplay the Password prompt and start again, press Enter.
User Passwords 1. Log on to 6416SW using the administrator password. 2. At the management prompt, type the SET DEVICE PASSWORD USER command: ONcoreATM> set device password user Then press Enter. 3. In the next three fields displayed, enter the administrator password and the new user password (up to fifteen characters) twice as shown here: Enter current administrator password: {admin password} New password: {new user password} Re-enter password: {new user password} Then press Enter.
Setting the Internal Clock You need to set the 6416SW's 24-hour internal clock only once, when you install the 6416SW. When you set the internal clock, you establish a starting time, date, and day. To set the internal clock, enter the SET CLOCK command and specify the time and date parameters. Then press Enter. @ For example, the following command sets the internal clock to 4:44 p.m.
Setting Local 6416SW Parameters The 6416SW is pre-configured with default settings that may need to be changed before you can use the switch. To modify these 6416SW parameters, you must log on using the system administrator password. Then use the SET command to change the values for any of the following: 6416SW name Contact name and location Console prompt Console timeout value. A brief description of each parameter is given in the following sections.
Service Contact Information After installing and logging on to the 6416SW, you should enter the location of the 6416SW and the name of the appropriate person to contact in case of a failure in the ATM subsystem or with the 6416SW To do so, enter the following commands: SET DEVICE LOCATION to specify where the 6416SW is installed SET DEVICE CONTACT to specify the name of the service personnel to contact. Console Prompt 3Com also recommends that you customize the prompt used by each 6416SW console.
Console Timeout The TERMINAL TIMEOUT parameter is a safety precaution that lets you specify how long you can remain logged on to the 6416SW console without entering any data from the keyboard. This prevents unauthorized users from accessing the 6416SW if you forget to log off the system. If no keystroke is entered for the time period specified by SET TERMINAL TIMEOUT, the system automatically logs you off. The default value for SET TERMINAL TIMEOUT is .
Setting the ATM Address of the 6416SW A default ATM address is provided with the 6416SW. You can use this default address only for a stand-alone (isolated) 6416SW. For all other 6416SW configurations, a new ATM address must be defined. See “Defining the ATM Address of the 6416SW” on page 3-7 for more information. @ To set the ATM address for the 6416SW, you use the SET DEVICE ATM_ADDRESS command: ONcoreATM> set device atm_address [ENTER] ONcoreATM>Enter ATM address: 39.11.FF.22.99.99.99. 11.11.
Connecting ATM media Modules After setting the ATM address, you must connect the ATM media modules to the network. This is necessary because the factory default setting isolates them from receiving network traffic. @ To connect an ATM media module, you use the SET MODULE command: ONcoreATM> set module 3 connected [ENTER] Afterwards, you can enable individual ports on the module and configure an ATM interface for each port.
Enabling ATM Ports and Interfaces @ Before you can use the devices attached to the ATM media ports in the 6416SW, you must enable each port and configure the type of interface used by the port to receive and transmit ATM data. For example, to enable port 2 (‘slot’ 1) as a UNI port: ONcoreATM> set port 1.2 enable uni [ENTER] You can set a port to any of the ATM interfaces: User-to-Network (UNI) Switch-to-Switch (SSI) Network-to-Network (NNI).
Setting Up Trunks (Logical Links) To connect the 6416SW to another ATM switch, you must create a trunk using the SET LOGICAL_LINK command. See “Setting-Up ATM Trunk Connections” on page 3-8 for a description of the strategy for setting up trunk links in an ATM network. The ONcore Switching Hub/CELLplex 4000 ATM Command Reference Guide also gives an example of the SET LOGICAL_LINK command.
Setting SNMP Parameters Carry out the procedures in this section only if you want to manage your ATM subsystem from an SNMP workstation. If you want to manage the ATM subsystem in the 6416SW from an SNMP workstation, you may access the 6416SW through either a Classical IP subnetwork or a LAN Emulation subnetwork.
IP Address and Subnetwork Mask (IP only) In order for SNMP to run properly, every device in the network must have a unique IP address and subnetwork mask. In a classical IP subnetwork, you must use the SET DEVICE IP_ADDRESS command to assign a unique IP address and subnetwork mask to the 6416SW @ For example, the following command sets a unique IP address for a Classical IP over ATM subnetwork on the 6416SW and a subnetwork mask for an ATM class C device: ONcoreATM> set device ip_address atm 195.44.45.
LAN Emulation Client (LE only) In order for SNMP to run properly, every device in the network must have a unique IP address and subnetwork mask. In a LAN emulation subnetwork, you must use the SET DEVICE LAN_EMULATION_CLIENT command to assign a unique IP address and subnetwork mask to the 6416SW. To configure the LEC, use the SET DEVICE LAN_EMULATION_CLIENT with the following parameters: LAN type IP address Subnetwork Mask Individual MAC address Associated LES ATM address Notes: 1.
@ ONcoreATM>set device lan_emulation_client eth ip_address 9.1 .2 .55 [ENTER] Client starting. ONcoreATM> After the eth parameter, the other parameters may be entered in any order. The first time the SET DEVICE LAN_EMULATION_CLIENT ETH is used, you must configure all four parameters before saving the configuration settings (no default values are provided).
Default Gateway (IP & LE) The default gateway is the IP address of the gateway that will receive and forward packets whose addresses are unknown to the ATM subnetwork. The default gateway is useful when sending 6416SW alert packets to a management workstation that is on a different network and is accessible via a router. @ For example, the following command defines the gateway with the address 195.44.45.26 as the default gateway: ONcoreATM> set device default_gateway 195.44.45.
Community Table (IP & LE) The Community table defines which SNMP stations in the network can access information from the 6416SW, and which station(s) will receive a trap from the 6416SW when the detects an error. To create an entry in the Community table, you use the SET COMMUNITY command. For example, the following command specifies that a community name called ATMMGMT with an IP address of 195.44.45.244 has read-write access to the 6416SW: @ ONcoreATM> set community ATMMGMT 195.44.45.
Setting the LECS ATM Address To set the ATM address of the LAN emulation configuration server (LECS) enter the SET LAN_EMUL CONFIGURATION_SERVER command. This is to support LECs which get their associated LES ATM address from a LECS. LECs have three possible ways to establish a connection to the LECS: During ILMI, the LEC gets the unicast ATM address that is available from the ILMI MIB (atmSrvcATMAddress). LECS ATM addresses can be defined to be returned to the LEC during ILMI exchange.
ACTIVE_WKA The LECS address table is to contain an ATM address to be substituted to the well known address (WKA). There can be only one ACTIVE_WKA entry in the LECS table. The ATM address you specify will be the one selected to be substituted with the WKA (WKA active). If an ACTIVE_WKA entry already exists in the LECS address table, it will no longer be used as the WKA substitution address.
Saving Configuration Settings and Logging Off Use the SAVE command to save the last configuration changes made to any of the following parameters: Alert All Community Device LAN_emul Module_port Static_route Terminal TFTP. When you make changes with the SET command, they are activated immediately but are not saved permanently. You must use the SAVE command in order to permanently store the new parameter values. When the 6416SW is reset, only the parameter values that have been permanently saved are loaded.
@ To save the changes made to an individual parameter, enter the parameter name in the SAVE command. For example, if you changed the type of interface used on an ATM port, you would save this setting as follows: ONcoreATM> set port 1.3 enable UNI [ENTER] Port set ONcoreATM> save module_port [ENTER] ONcoreATM> Note that if you changed configuration settings for the DEVICE or TERMINAL, these values are not saved using the SAVE MODULE_PORT command.
@ When all your configuration changes are saved, log off the console by entering the LOGOUT command and pressing Enter. The system prompts you when you are logged off: ONcoreATM> logout [ENTER] Bye @ If, when logging off, you have changed 6416SW configuration parameters but forgotten to save them, the following message appears: ONcoreATM> logout [ENTER] WARNING: Save unsaved changes before logout. The system prompt is redisplayed.
Working With Configuration Settings The following sections describe how to: Revert to previously saved configuration settings Display the current configuration settings Modify the current configuration settings. Reverting Configuration Changes Use the REVERT command to restore the configuration parameters that were active at the time of the last SAVE. Any changes made using the SET command since the last SAVE are lost.
@ atm2: revert terminal [ENTER] Reverting terminal configuration. ONcoreATM> Note that when you enter the REVERT TERMINAL command, you revert all TERMINAL parameters, such as BAUD, DATA_BITS, HANGUP, PARITY, STOP_BITS, and TIMEOUT. Displaying Configuration Settings The 6416SW lets you display your currently configured settings for: Alerts ATM_ESI Clock Community Device LAN_emul Logical_link Module Static_route Port PVC Terminal TFTP Trace.
To do so, use the SHOW command.
ONcoreATM> show module 4 verbose [ENTER] Slot Install Connect Operation General Information -------------------------------------------------4 Y Y Y ONcore ATM 1 Mbps Module status: connected / hardware OK enable / normal P/N: F 4FFFF EC level: G 4GGG Manufacture: I 41 Operational FPGA version : 7 Backup FPGA version : 7 Type Mode Status -----------------------------------------------------------------------------4. 1:UNI enabled UP-OKAY 4. 2:UNI enabled UP-OKAY 4. 3:SSI enabled UP-OKAY 4.
Modifying Configuration Settings Using the SET command, you can change the configuration settings for any of the following parameters: Alert ATM_ESI Clock Community Device LAN_emul Logical_link Module Static_route Port PVC Terminal TFTP Trace. Important: Remember that (except for SET CLOCK, ATM_ESI, PVC, TRACE, and LAN_EMUL CONFIGURATION_SERVER) the changes you make with the SET command are not saved permanently in nonvolatile memory. To do so, you must use the SAVE command before logging off.
Isolating and Reconnecting ATM Media Modules Use the SET MODULE command to: Isolate and reconnect ATM media modules to the ATM network. Enable and disable ATM media modules that are connected to the network. When you isolate an ATM media module from the network, it remains in Reset mode and no activity takes place on it. Its current configuration settings cannot be accessed by the network. In order to use the module for ATM data transmission, you must reconnect it to the network and enable it.
As another example, to display the complete status of ATM port 10, enter: ONcoreATM> show port 1.1 verbose [ENTER] 1.
Chapter 6. Network and Switch Management This chapter gives an overview of the management options for the ONcore hub: The three methods for managing the ATM Switch/Control Guidelines for SNMP network management Procedures for uploading and downloading operations. Managing the ATM Subsystem You can manage the ATM subsystem in any of the following ways: From an ASCII terminal with a character-based, command-line interface that is directly connected to the RS-232 Console port on a 6416SW.
SNMP Support In a campus environment managed by the Simple Network Management Protocol (SNMP), the 6416SW module acts as an SNMP agent allowing you to configure all ATM modules in the hub using SNMP. 6416SW software contains a community table with up to ten IP addresses. Each IP address has one of the following access attributes assigned: Read-only Read-write Read-trap Trap All (read-write and trap).
Accessing MIB Files For information on the commands that can be used to manage the ATM subsystem from SNMP via a 6416SW module, refer to the Management Information Base (MIB) documents for ATM. MIB documents are available over Internet and intended to help you with Configuration and Performance management. MIBs are stored in files on an anonymous FTP server. The MIB files are regularly updated. How to access the MIB files on Internet is described on page F-6.
Security Control To prevent unauthorized access to an ATM subsystem, the 6416SW module provides two password levels to protect against network tampering and unauthorized access to the 6416SW console. The administrator password allows full use of all 6416SW commands; the user password allows use of a limited set of 6416SW commands that does not let you change configuration settings. See the ONcore Switching Hub/CELLplex 4000 ATM Command Reference Guide for more information.
Uploading and Downloading Operations The picocode or microcode for your 6416SW and ATM media modules can be upgraded by inband, manual, and out-of-band operations. Data such as error logs, traces, and dumps can also be uploaded to the host. These operations are shown in Figure 6-1. For more information on the commands used to start these operations, see the ONcore Switching Hub/CELLplex 4000 ATM Command Reference Guide. Microcode Upgrade ATM network administrators perform inband operations.
Inband Operations To upgrade ATM microcode, ATM network administrators perform inband operations from a server connected to a ONcore hub, using a workstation connected to the 6416SW module as the 6416SW console. After locating the directory where the microcode updates are stored, log on using the administrator password and perform one of the following operations: Upgrade 6416SW microcode. Upgrade hardware picocode in the Field Programmable Gate Array (FPGA) of the 6416SW and ATM media modules.
Upgrading FPGA Picocode in ATM Modules To upgrade hardware picocode in the FPGA of 6416SW and ATM media modules, enter the following commands at the directory prompt: 1. SET TFTP SERVER_IP_ADDRESS (to define the server where the picocode is stored) 2. SET TFTP FILE_NAME (to define the file on the server) 3. SET TFTP FILE_TYPE (to specify FPGA) 4. SET TFTP TARGET_MODULE (to specify the slot number of the 6416SW or ATM media module) 5. DOWNLOAD INBAND (to load new hardware picocode) 6.
Uploading Traces To upload a trace log to the host, enter the following 6416SW commands at the directory prompt: 1. SET TRACE (to enable and disable trace recording) 2. SET TFTP SERVER_IP_ADDRESS (to define the server connected to the 6416SW module) 3. SET TFTP FILE_NAME (to define the path name of the file on the host) 4. SET TFTP FILE_TYPE (to specify the trace type) 5. UPLOAD INBAND (to upload the trace).
Out-of-band Operations ATM network administrators can upgrade 6416SW microcode (but not ATM media modules) using an out-of-band operation with an RS-232 plug. To do this, you must attach a workstation with an emulated VT100 protocol to the 6416SW module. After locating the directory where the microcode updates are stored, use the workstation as the 6416SW console. Log on using the administrator password and enter the following commands: 1. MAINTAIN (to activate Maintenance mode) 2.
6-10 ONcore ATM Switch/Control Module: Installation and User's Guide
Chapter 7. Troubleshooting This chapter describes how to diagnose and solve problems associated with the installation and operation of the 6416SW and ATM media modules. Troubleshooting operations are described according to the phase in which they are necessary. Phase 1 Problems that occur during installation, after turning ON the hub, and after resetting the ATM subsystem. This phase ends when the 6416SW ACTIVE LED lights ON (yellow).
Phase 1: Installation and Power Problems This section describes the troubleshooting operations for problems that occur after you turn ON the ONcore hub and wait for the 6416SW ACTIVE LED to light ON (yellow). “Verifying Normal 6416SW Operation” on page 2-7 describes the other LED conditions. Phase 1 problems concern the installation tasks described in Chapter 2, “Installation” on page 2-1 and are divided as follows: Prerequisites for diagnosing normal operation of the ATM subsystem.
Prerequisites for ATM Troubleshooting In order to determine the cause of a problem during installation of 6416SW and ATM media modules or after turning ON the hub: The correct microcode must be installed. 6416SW LEDs must function properly. 6416SW and ATM media modules must be plugged into the hub. To ensure that these conditions are satisfied, follow these steps: 1. From the Distributed Management Module (DMM), enter show module 18.
Diagnosing Problems from the ATM Media LEDs The following section details problems that can occur with ATM media modules. WRONG SLOT LED is ON. Explanation: Either the ATM backplane is not installed in the ONcore or the ATM media module has been inserted in an incorrect slot. Steps to Take: 1. Check that the backplane is installed (in the upper part of the ONcore). 2.
4. Check that the power of the slot has not been disabled. Issue the command SHOW POWER SLOT ALL to determine if that is the real cause. If this is the cause, issue the SET POWER SLOT n ENABLE command. If a DMM module is installed, this command must be issued from the DMM console.
Diagnosing Problems from the 6416SW LEDs After installing the 6416SW module, the following should occur when you turn ON the ONcore hub: All seven LEDs on the front panel light (ON) and then turn OFF, except for the RUNNING LED. The RUNNING LED stays lit (yellow). After 7 seconds, the ACTIVE LED lights up and stays lit (yellow). If the diagnostics are disabled, the ACTIVE LED lights up immediately and stays lit.
Power is ON but the RUNNING LED does not light (yellow). Steps to Take: 1. Press the TEST LED button on the power supply module to verify that the RUNNING LED is not burned out. 2. Verify that the 6416SW module has been installed correctly by following the installation procedure in Chapter 2, “Installation” on page 2-1. 3. Press the ATM Reset button on the 6416SW module. 4. If the RUNNING LED still does not light, call your 3Com dealer or your 3Com representative.
5. Press the ATM Reset button on the 6416SW module. 6. If the ACTIVE LED still does not light, call your 3Com dealer or your 3Com representative. MAINT LED is lit and you have not entered the MAINTAIN command. Steps to Take: 1. Make sure that the console cable is plugged into the topmost RS-232 port on the front panel of the 6416SW module. 2. Enter the BOOT command. MAINT LED is lit, ONcore stays in Maintenance Mode. Steps to Take: 1. The 6416SW is badly plugged. Replug the 6416SW.
Diagnosing Problems with the Power Supply If, during installation or after turning ON the hub, you suspect that power is not reaching all ATM modules in the hub, see if the problem is caused by one of the conditions described below. If you cannot solve the problem and if the 6416SW ACTIVE LED does not light ON, contact an 3Com service representative before configuring the ATM subsystem.
Phase 2: Problems During ATM Configuration The problems in this phase occur after you turn ON the ONcore hub and the 6416SW ACTIVE LED lights ON (yellow). This indicates that the 6416SW module is ready to control the ATM subsystem.
Diagnosing Problems Concerning the 6416SW Console The following section describes the problems that may arise after attaching the local console to the 6416SW module through the RS-232 Console port. If you find that the problem does not concern the 6416SW console, continue troubleshooting with “Diagnosing Problems with ATM Modules” on page 7-14. No prompt appears on your console screen when you press ENTER. Steps to Take: 1.
Characters appear on the screen but they are not legible. Steps to Take: 1. Make sure that the attached console is an ASCII terminal. 2. Check the terminal parameters, especially the baud-rate, parity, and data bits. The default parameters are: 9600 bauds, 8 data bits, 1 stop bit, no parity. If these values do not work, try different settings until you find the right configuration. 3. Replace the ASCII terminal.
The passwords do not work or you forgot a password. Steps to Take: 1. Enter force at the password prompt. Then press the ATM Reset button on the front panel of the 6416SW module within 3 seconds. This will reboot the 6416SW to the factory default settings. When you turn ON the hub, your last configuration settings are not loaded. A different configuration is activated. Steps to Take: 1. Re-enter the configuration settings and save them using the SAVE command.
Diagnosing Problems with ATM Modules If the cause of a Phase 2 problem is not due to the 6416SW console connection, make sure that all ATM modules are operational by following these steps: 1. Enter the SHOW MODULE ALL command as described in the ONcore Switching Hub/CELLplex 4000 ATM Command Reference Guide. 2. Check that each module is installed, connected, and functioning properly.
Diagnosing Problems with ATM Ports If all ATM modules are operational (connected, hardware okay, and normal displayed with SHOW MODULE VERBOSE), the cause of the problem may be due to an inoperational ATM port. To see if the ATM ports on a given module are functioning correctly, use the SHOW MODULE and SHOW PORT commands to display port status. Any of the following types of port status may appear: Unknown Error No Activity Not In Service Okay Okay PVC-Only.
Status: Error Explanation: An internal error is detected on the port. Steps to Take: 1. Reset the ATM media module using the RESET MODULE command. 2. If the problem persists, replace the ATM media module. Status: No Activity Explanation: No physical layer activity is detected (either there is no cable/fiber attached, or there is no signal on the Receive cable/fiber. Steps to Take: 1. See if the port is enabled by entering the SHOW PORT command. 2.
Status: Not In Service (UNI port) Explanation: Physical layer activity is detected (there is a receive signal on the Receive fiber/cable) but the remote device is not responding to ILMI polling. Steps to Take: 1. See if the port is enabled by entering the SHOW PORT command. 2. If the port is not enabled, use the SET PORT command to set the mode parameter to enable. 3. If the port is enabled, make sure that the remote device is operational and that its adapter is securely plugged in. 4.
Status: Not in Service (SSI Port) Steps to Take: 1. Use the command SHOW PORT slot.port VERBOSE command to determine the problem. 2. There may be a problem of bandwidth availability on the module. Spread the SSI ports over several modules. If, after trying to solve the problem, the status of ATM media ports does not change to OKAY, perform the Wrap test as described in the ONcore Switching Hub/CELLplex 4000 ATM Command Reference Guide. If you find that the module is faulty, replace it.
Phase 3: Problems on ATM Media Ports Without ATM Traffic The problems in this phase occur after the status of all ATM media ports is NO ACTIVITY and ATM devices have been attached to ATM media ports. No ATM traffic is started in the hub. Phase 3 problems occur because one or more ATM media ports are not functioning properly.
Diagnosing Problems with ATM Ports Attached to ATM Devices After you attach ATM devices to ATM media ports, the status of the ports may still not change to OKAY (ready for ATM traffic). To diagnose this type of Phase 3 problem, follow these steps: 1. Use the SHOW PORT VERBOSE command (described in the ONcore Switching Hub/CELLplex 4000 ATM Command Reference Guide) to display the status of each port. 2.
For SSI ports, the bandwidth allocated must be the same at both ends of the trunk. 5. If the status of an SSI port is ACN mismatch, make sure that the hub belongs to the same ATM cluster as the attached device. Enter the SHOW DEVICE command to check the configured ATM address. 6. If the status of an SSI port is Misconfigured, make sure that the device is attached to an SSI port.
Checking ATM Address Registration If you suspect that a Phase 3 problem is due to faulty ATM address registration between a ONcore hub and an attached ATM device, follow these steps: 1. Enter the SHOW PORT command to make sure that the ATM media port is configured with a UNI interface. If not, enter the SET PORT command and specify uni for the interface parameter. 2. Make sure that the attached device supports the ATM network prefix used by the ONcore hub.
Diagnosing Problems in the Hardware Configuration If you suspect that a Phase 3 problem is due to a problem in your hardware configuration (for example, using a LAN Emulation server, ONsemble ATM 25 Mbps Concentrator, 25Mbps client, and so on), check the following: If the attached device is an ONsemble ATM 25 Mbps Concentrator, enter the SHOW PORT command to see if the port's status is OKAY. If the status is not OKAY, follow the steps in “Diagnosing Problems with ATM Ports” on page 7-15.
Phase 4: Problems with Normal ATM Operation The problems in this phase occur after ATM traffic is started in the network between ATM devices attached to ATM media ports. The ATM port status is OKAY. Important: Problems in the normal operation of your ATM subnetwork may occur when the maximum number of virtual connections (VCs) allowed on a ONcore hub or an individual ATM media module is exceeded.
ONcore Cannot PING the ARP Servers and Vice-versa Use the SHOW DEVICE command and look at the Q2931 cause: Cause Code: 31 Explanation: The IP address of the hub is not in the same IP subnet as the ARP server. Steps to Take: 1. Change the IP address or IP subnet mask of the ONcore hub. Cause Code: 1 Explanation: A wrong ARP server address was entered with the SET DEVICE ARP_SERVER command, or the port of the ARP server is NOT IN SERVICE or NO ACTIVITY status. Steps to Take: 1.
Cause Code: 3 Steps to Take: If the ARP-server is in another cluster (NNI links): 1. The NNI network-side/user-side definition rules have not been applied. Check that one side of the NNI link is defined as user, and that the other side is defined as network. 2. No logical-link has been defined for the NNI port. Define the logical link, using the SET LOGICAL_LINK command. 3. The peer logical links do not match (bad vpi match, bad cluster match, bad bandwidth match).
ONcore Hub Cannot PING an ARP Client Steps to Take: Check if the ONcore hub can ping the ARP server. If not, then see “ONcore Cannot PING the ARP Servers and Vice-versa” on page 7-25. If it can ping the server: 1. The port of the ARP client is not OKAY. Check that the port of that ARP client is enabled. If it is enabled, and not OKAY, then the problem comes from the ARP client or from the cable attached to it. 2. The ARP client is not registered in the ARP server.
ONcore LEC Cannot PING another Client and Vice-versa Steps to Take: 1. Check that the port of the LEC is enabled. If it is enabled, and not OKAY, then the problem comes from the LEC or from the cable attached to it. 2. The LEC does not support the same Ethernet type as the ONcore LEC. Check that the LEC is emulating IEEE 802.3 Ethernet frames. 3. If the ONcore LEC and the other LEC are not in the same IP subnet, there may be a Gateway definition problem. Check the Default Gateway addresses in both machines.
ARP Client Cannot PING the ARP Server Steps to Take: 1. The IP address of the client is not in the same subnet as the ARP server. Re-define the IP address of the ARP client so that it is in the same subnet as the ARP server IP address.
Two Devices Using IP Over a PVC Cannot Ping Each Other Steps to Take: 1. If the PVC is not active, make sure that the PVC is 'in-service' from ATMC or 'active' (from the terminal). If not, then try to re-enable that PVC. 2. The hardware connections may be failing, in which case replug the cables attached to the devices. 3. If the source and destination IP addresses are not in the same IP subnet, check both IP addresses. Change them so that they belong to the same IP subnet.
ONcore LEC Cannot Initialize to the LES/BUS Use the SHOW DEVICE command and look at the subnet lan emulation status message: Abnormal Termination: LES connection cleared. ATM Forum cause xx: The LEC automatically tries to reconnect to the LES/BUS when the connection is lost. It will try to reconnect every 5 seconds, 5 times, and thereafter every 1 minute.
If the LE server is in another cluster (NNI links): 1. The NNI network-side/user-side definition rules have not been applied. Check that one side of the NNI link is defined as user, and that the other side is defined as network. 2. No logical-link has been defined for the NNI port. Define the logical link, using the SET LOGICAL_LINK command. 3. The peer logical links do not match (bad vpi, cluster, or bandwidth match).
LAN Emulation JOIN failed. ATM Forum LE status xx: When this message occurs, the LEC is stopped. To restart the LEC, enter the SET DEVICE LAN_EMULATION_CLIENT ETH command (the additional parameters will automatically retain their previous values). For more information, see the ONcore Switching Hub/CELLplex 4000 ATM Command Reference Guide. Cause Cod: 1 Explanation: The LE version for the LEC is not compatible with the LES/BUS version.
Administrative Problems (Netview/SNMP/Telnet) This section details problems occuring during the administration of your ONcore hub (PING,Telnet,TFTP,SNMP/ATMC). PING: Your ONcore hub cannnot ping your management station. Steps to Take: 1. Since all the management services are running over IP, you have to ensure that your ONcore hub can ping the destination station where you will run either Telnet, the TFTP daemon (TFTP server), or the SNMP manager (ATMC).
When an upload fails, an error code is returned. That error code can be different between the terminal dialog and the ATMC/MIB browser, which is why both return codes are documented. Note: When the upload fails from the terminal dialog (console or Telnet), check the return code by using the SHOW TFTP command. Steps to Take: 1. Messages: Error/generic error..Host Access Violation...Access Rights Violation/access-rights-violation...File already exists/file-already exits..
4. Message: File not found/file-not-found. You tried to upload without specifying the name of the file to be uploaded. Specify the name of the file. 5. Message: File too big/file-too-big. There is no space left on the server. Check that space is made available before retrying the upload. TFTP: Download Inband fails from your ONcore hub Explanation: The download inband can be done either from the terminal console (console or Telnet) or from the SNMP Manager (ATMC or MIB Browser).
2. Message: Cannot connect to Host/no-repsonse-from-host. Check that you can ping the host from the ONcore hub. If the ping fails, see the previous sections on ping failures. 3. Message: Connection lost/connection-lost. The SVC connection between the ONcore hub and the host has been cleared during the file transfer. Retry the download. Look at all the Clear Tables of all intermediate ONcore hub/4412SWs that are on the path between your ONcore and the host.
either get a new source (re-install the source file from your installation package), or, if it fails again, contact your 3Com Service or 3Com representative. 8. Message: Flash memory failure/hardware-error. Try to download several times. If it always fails, contact your 3Com representative. 9. Message: Target Blade Mismatch. You tried to download FPGA picocode that is incompatible with the target module number. Check the type of module (6404M-100, 6402M etc.) and the TFTP parameter.
Communication Problems in an IBM LAN Emulation Environment This section details the problems that may occur during the setup of the IBM LAN emulation environment. Such an environment may include concentrators (ONsemble ATM Workgroup Concentrator) and bridges (4404B), the external IBM LAN Emulation Server (LES), workstations (WS), ATM Workgroup Switches (4412SW), and the ONcore hubs. A workstation/bridge cannot connect to another workstation/bridge. Steps to Take: 1.
LES Monitor Statistics: Default Vccs counter oscillating, too few registered workstations. Steps to Take: Explanation: The workstation knows its ATM address, but that address has been de-registered at the Switch/Control-point level. This happens when the workstation is behind a concentrator (ONsemble ATM Workgroup Concentrator) that has been disconnected from the switch for a short time. Note: You can check whether the station is registered in the ONcore by using the command SHOW ATM_ESI. 1.
originating ATM station. In a network where the number of ATM stations exceeds 256, which is the maximum number of SVCs per 4404B, some stations will not be able to connect until the bridges clear their SVCs that are unused (aging out process). Steps to Take: 1. Wait up to 4 minutes (aging time on the 4404B bridge), or avoid parallel bridging. LES Monitor: after 3 minutes, the workstation is de-registered from the LES (valid only for IBM proprietary LAN emulation).
LES Monitor: Bridge is on General Multicast Tree, but not on Bridge Multicast Tree. (valid only for IBM proprietary LAN emulation). Explanation: The bridge did not send its route descriptors to the LES. Steps to Take: 1. The bridge is faulty. Contact your 3Com representative. At workstation reboot: the ATM adapter initialization failed. Explanation: The switch or concentrator port attached to the workstation is not enabled, or is not a UNI port. Steps to Take: 1.
No Traffic in a Client Environment. Steps to Take: 1. Make sure that each LES client does not have more than 12 virtual connections. Problems between two LAN-emulated stations, or between a LAN-emulated station and a LAN station located behind a bridge (valid only for IBM proprietary LAN emulation). Steps to Take: 1. For performance problems, first consider the frame sizes defined at the workstation level and at the bridge level. 2.
Other Problems Cannot create a PVC between two ONcore hub/CELLplex 4000s located in different clusters. Explanation: This is normal. The ONcore hub/CELLplex 4000 does not allow the creation of PVCs over network-to-network (NNI) links. You have created two different PVCs, each one ending at the NNI port. Note: Make sure that the VPI used by the PVC on the NNI port corresponds to the one of the logical link defined on that port. ATM server/token-ring client's applications fail: frames are lost.
at a time until the Telnet session gives a normal response time. The last port that you disabled should be the one through which the congesting calls were coming. 2. If you can be in front on the ONcore hub/CELLplex 4000, log on to the console, make sure that the trace is not active, then if the ATM switch is an ONcore, look at the traffic LEDs and disable the for which the traffic LED is constantly lit. If your ATM switch is a CELLplex 4000, disable the high-bandwidth port.
REPLY_MODE ENABLE. Your NNI port is now redirecting Received Cells to the transmit side. Now, from the ATM Analyzer, generate traffic on the VCI=5, and compare the outgoing cells with the incoming cells. If some cells are lost or corrupted, contact your public network provider. When you are finished, enter the command WRAP slot.port REPLY_MODE DISABLE. Hardware wrap test through the WAN up to the media module, install the ATM Analyzer at one side of the WAN, and the ONcore hub/CELLplex 4000 at the other.
ATM Connection Problems No Connection between Two ATM Hub in the Same Cluster Steps to Take: 1. Use the SHOW PORT command to: Make sure that the ATM media port at each end of the connection is configured with an SSI interface. If not, use the SET PORT command and specify SSI as the interface parameter. Make sure that the the status of each port is OKAY. If not, follow the procedure described in “Diagnosing Problems with ATM Ports Attached to ATM Devices” on page 7-20. 2.
No Connection Between Two ATM Clusters in the Same Subnetwork Steps to Take: 1. Use the SHOW PORT command to: Make sure that the ATM media port at each end of the connection is configured with an NNI interface. If not, use the SET PORT command and specify NNI as the interface parameter. Make sure that the status of each port is OKAY. If not, follow the procedure described in “Diagnosing Problems with ATM Ports Attached to ATM Devices” on page 7-20. 2.
No Connection Between Two ATM Subnetworks Steps to Take: 1. Use the SHOW PORT command to: Make sure that the ATM media port at each end of the connection is configured with an NNI interface. If not, use the SET PORT command and specify NNI as the interface parameter. Make sure that the status of each port is OKAY. If not, follow the procedure described in “Diagnosing Problems with ATM Ports Attached to ATM Devices” on page 7-20. 2.
Using 6416SW Trap Messages A trap message is sent to the 6416SW local console when a configuration change is made or when an error occurs in the ATM subsystem. For example, if an ATM module is removed from a ONcore hub, a message describing this change is sent to the console. A sample message is shown here: @ Change trap on module 2 The first field in the trap message is described in Table 7-1. The other fields of information that can appear are self-explanatory and depend on the type of trap received.
Contacting Your 3Com Service Representative To get technical help to solve installation and operation problems with the ATM subsystem in a ONcore hub, call your local 3Com Customer Support center. Depending on the phase in which the problem occurs, an 3Com service engineer will ask you to write down all or parts of the information listed in the following sections.
Troubleshooting Phase 3 Problems To troubleshoot Phase 3 problems, an 3Com service engineer needs the information listed in this section. In order to record trace information, follow these steps: 1. Use a TFTP file server in IP over ATM or LAN emulation mode. 2. Reproduce the problem and activate the trace by entering set trace main_trace on or set trace trs_trace on, as requested by the 3Com service engineer. 3. Stop the trace by entering the SET TRACE command and specifying off.
Troubleshooting Phase 4 Problems To troubleshoot Phase 4 problems, an 3Com service engineer needs the information listed in this section. Note that in order to record trace information, perform dumps, and upload the error log, you must use a TFTP file server in IP over ATM or LAN emulation mode. For information on how to record trace information, see “Troubleshooting Phase 3 Problems” on page 7-52.
– atmfAtmAddressTable from the ILMI MIB Q.2931 error code for the clear cause in the SVC.
Appendix A. Technical Specifications General Specifications Connectors One RS-232 DB-9 connector (topmost on front panel) for Console port connections. One RS-232 DB-9 connector (bottommost on front panel) for Auxiliary port connections. Processors MC 68EC040 and MC 68EN360 used in companion mode.
Electrical Specifications Power consumption 45W @ +5V 3.5W @ +12V Fuses Two 1A (+12V) for the Switch/Control cards (one for each card). Two 7A (+5V) for the Switch/Control cards (one for each card). Environmental Specifications Operating Temperature 0° to 50° C (32° to 122° F) Humidity Less than 95% (non-condensing) BTU/hr 55. Mechanical Specifications Dimensions 2.0 in. (5 cm) W x 10.7 in. (27 cm) L x 15.2 in. (38.5 cm) H Weight 5.3 lbs. (2.
Appendix B. RS-232 Cable and Modem Requirements This appendix describes: How to attach a console, modem, or server to the 6416SW module RS-232 cable pin assignments used for connecting a console, modem, or server to the 6416SW module. Requirements for using a modem with the 6416SW module.
RS-232 Cable Requirements RS-232 Connector The RS-232 connector is the 9-pin female connector on the 6416SW that attaches to an EIA 232 cable. Table B-1 lists the signal name associated with each pin on this connector, and Figure B-1 shows how the pins are numbered. Table B-1.
9-Pin/9-Pin Cable Figure B-2 shows the pin assignments for the 9-pin to 9-pin RS-232 cable used to attach a console to the 6416SW Console port: Console 9-pin Port 6416SW 9-pin Console port CD1 1 CD RD2 2 RD TD 3 3 TD DTR 4 4 DTR GND 5 5 GND DSR 6 6 DSR RTS 7 7 RTS CTS 8 8 CTS 9 NOT USED 9 Figure B-2. Console Attachment: 9-pin to 9-pin RS-232 Cable Note: CD (Carrier Detect) is a synonym for RLSD (Receive Line Signal Detect). CTS (Clear To Send) is a synonym for RFS (Ready For Sending).
9-Pin/25-Pin Cable Figure B-3 shows the pin assignments for the 9-pin to 25-pin RS-232 cable used to attach a console to the 6416SW Console port. A-CPSW 9-pin Console port Console 25-pin Port RD 2 2 TD TD 3 3 RD RTS 7 5 CTS CTS 8 4 RTS DTR 4 8 CD DSR 6 6 DSR CD 1 GND 5 20 DTR 7 GND Figure B-3.
Null-Modem Interposer Figure B-4 shows the pin assignment of the interposer (null modem) used for a console attachment. The RS-232 interposer is shipped with the ONcore hub. Figure B-4. Pin Assignment: RS-232 Interposer After attaching a console to the 6416SW RS-232 Console port, make sure that the console is set up for asynchronous serial communication.
Modem Attachment Figure B-5 shows the pin assignment for the RS-232 cable used to attach a modem to the 6416SW Console port. Male (Modem) Female (6416SW Console Port) 5 6 1 14 1 25 13 IBM IBM 9 Pin Pin 0 Volt 5 7 Received Data 2 3 8 3 Transmitted Data Clear to Send 2 5 Request to Send 7 4 DTR 4 20 Carrier Detector 1 Data Set Ready 6 8 6 Figure B-5.
Modem Requirements The 6416SW module supports the use of dial-in modems with the following requirements: The modem must be 100% Hayes-compatible. Any valid baud rate (300, 1200, 2400, 4800, 9600, 19200) may be used. 2400 and 9600 are recommended. The modem must be set to Dumb/Auto Answer mode. Modem Configuration To configure a modem, enter the following commands from the console to which the modem is attached: 1. Type at&F and press Enter (to restore the factory default settings). 2.
DTE Interface Data Type Idle/Data ASYNC Async Format.8N1 XmitClock 7855 Async DTE Speed DTS Speed..TELCO Connect Char.YES Async Data Path Direct Path...NO Escape Sequence Asynchronous ...YES ... 43 (/5 )... 5 Signals 7855 to DTE RFS(1 6) RFS On....ALWAYS RLSD(1 9) RLSD On...ALWAYS DSR(1 7)PSN DSR On....ALWAYS DTR(1 8)Drop Polling...NO DTR Off...V24 DTR Delay... Break Signals From DTE...QUICK From Telco.QUICK Commands,Results Async Characters ......... 13 ... 1 ... 8 Async.
Appendix C. Error and Information Codes This appendix contains explanations of the error and information codes displayed for the Q.2931 protocol, the codes issued from Maintenance Mode, and the IBM LAN Emulation Server error codes.
Q.2931 Error Codes for Clear Causes Table C-1 lists the error codes from the Q.2931 protocol for clear causes generated by ONcore hubs and other ATM devices in an ONcore-based ATM network. For a detailed explanation of each cause, see the ATM User-Network Interface Specification - Version 3.0 and Version 3.1. The decimal and hexadecimal values of the codes are both given below. The terminal dialog issues the codes in hexadecimal format. Table C-1 (Page 1 of 3). Q.
Table C-1 (Page 2 of 3). Q.2931 Error Codes for Clear Causes in ONcore-based ATM Networks Error Code (decimal) Error Code (hex) Meaning of Clear Cause 35* 0x23* Requested VPI/VCI is unavailable. 36 0x24 VPI/VCI assignment failed (on user side) (UNI 3.1). 37 0x25 User cell rate not available (UNI 3.1). 38* 0x26* Network is out of order. 41* 0x29* Temporary failure. 43 0x2B Access information has been discarded. 45* 0x2D* No VPI/VCI is available.
Table C-1 (Page 3 of 3). Q.2931 Error Codes for Clear Causes in ONcore-based ATM Networks Error Code (decimal) Error Code (hex) Meaning of Clear Cause 89* 0x59* Invalid end-point reference. 91 0x5B Invalid transit network selection. 92* 0x5C* Too many pending add-party requirements. 93* 0x5D* AAL parameters cannot be supported. 96* 0x60* Mandatory information element is missing. 97* 0x61* Message type does not exist or is not implemented.
Maintenance Codes The following table explains the prompts that can be displayed in Maintenance Mode. Table C-2. Maintenance Codes and Meanings Code Meaning >>0020>> The NVRAM diagnostics failed, the battery may be low. >>0021>> Bad checksum, the loading or de-compression of the operational code failed. >>0023>> After 3 retries, the 6416SW FPGAs did not initialize properly. >>0030>> The initialization or the diagnostics failed for the switch, the SPU (Switch Processing Unit), or the serial link.
IBM LAN Emulation Server Error Codes Table C-3.
Appendix D. Configuring AIX for Download and Upload Operations If you are uploading or downloading ATM software to or from a server running AIX, you must first configure AIX for the TFTP file transfer before entering the DOWNLOAD INBAND or UPLOAD command. To do so, follow these steps: 1. Log on as a root user. 2. Edit the /etc/inetd.conf file that is stored on AIX and make sure that the TFTP line is not commented out. 3.
D-2 ONcore ATM Switch/Control Module: Installation and User's Guide
Appendix E. ONcore ATM Address Formats The ONcore ATM subsystem supports the addressing scheme defined by the ATM Forum for addressing end-points in private ATM networks. The scheme is modeled after the format of the OSI Network Service Access Point (NSAP) as specified in ISO-8348 (CCITT X.213). As shown in Figure E-1 on page E-2, the 6416SW supports the three initial domain identifier (IDI) formats specified by the ATM Forum: DCC (Data Country Code) E.
Figure E-1.
Network Prefix The fields that make up the Network Prefix part of an ATM address include: AFI The one-byte AFI identifies the authority allocating the portion of the address that follows. It defines the structure of the NSAP format. The AFI values accepted by the ONcore ATM subsystem are as follows: 39 (ATM format of the Domain-Specific Part) 45 (ATM format of the E.164 Initial Domain Identifier) 47 (ATM format of the International Code Designator).
E.164 E.164 IDI (8 bytes) Specifies the international addressing format used by B-ISDN public transport providers and is up to 15 digits long (BCD syntax). This field is padded with leading '0000' semi-bytes to reach the maximum length. A closing semi-byte '1111' is used to obtain an integral number of bytes. This code is handled as a bit mask and is not checked by the ATM subsystem. ICD International Code Designator (2 bytes) Identifies an international organization.
End System Part The fields that make up the End System part of an ATM address are: ESI End System Identifier (6 bytes) Identifies an end system unique within an area or within any larger addressing structure such as the IEEE MAC address space. Not used for routing within the ATM network. SEL SELector (1 byte) Has local significance only within the end system.
E-6 ONcore ATM Switch/Control Module: Installation and User's Guide
Appendix F. Technical Support 3Com provides easy access to technical support information through a variety of services.
Online Technical Support 3Com offers worldwide product support through the following online systems: E-mail Technical Support World Wide Web Site E-mail Technical Support You can contact the Integrated Systems Division (formerly Chipcom) on the Internet for technical support using the e-mail address: techsupp@3com.com. World Wide Web Site You can access the latest networking information on the 3Com World Wide Web site by entering our URL into your Internet browser: http://www.3com.
Support from Your Network Supplier If additional assistance is required, contact your network supplier. Many suppliers are authorized 3Com partners who are qualified to provide a variety of services, including network planning, installation, hardware maintenance, application training, and support services.
Support from 3Com If you are unable to receive support from your network supplier, technical support contracts are available from 3Com. For direct access to customer service for Integrated Systems Division products in: U.S.A. and Canada - call (800) 724-2447 Asia Pacific - call (508) 787-5151 Europe - refer to the table below. For European countries not listed, call 31 30 60 299 00.
Returning Products for Repair A product sent directly to 3Com for repair must first be assigned a Return Materials Authorization (RMA) number. A product sent to 3Com without an RMA number will be returned to the sender unopened, at the sender's expense. To obtain an RMA number for Integrated Systems Division products (formerly Chipcom), use the following numbers. Country Telephone Number Fax Number U.S.
Accessing the 3Com MIB and atswitch.mib The 3Com Management Information Base (MIB) for the Integrated Systems Division describes commands that enable you to manage 3Com SNMP-based products. The MIB is available over the Internet on an anonymous FTP server. Updates to these MIBs are released as new 3Com products are introduced. To access Internet versions: 1. FTP to ftp.3com.com (192.156.136.12). 2. Enter the login name anonymous. 3.
Index Numerics 6416SW module accessing MIB files 6-3 alerts 5-22 ATM address 5-13 ATM connections 1-7 ATM Reset button 2-12 base card functions 1-6 cabling B-2 clock 5-9 configuration 5-1, 5-32 connectors A-1 console, attaching 2-5, 6-1 default settings 5-10 dimensions A-2 displaying configuration 5-29 distributed control functions 1-7 gateway configuration 5-21 inband upgrade 6-6 installation 2-1, 2-3 IP address 5-18 LEDS on front panel 2-8 location 5-11 memory A-1 modems 4-15, 4-16, A-1, B-7 naming 5-10 n
ARP client 7-27, 7-29 ARP server 5-18, 5-21, 7-25, 7-29 ATM Forum specifications 1-8 Auxiliary port 2-14 Available Bit Rate 1-7, 1-9 B backplane in ATM subsystem 1-3 baud rate, configuring 4-7, 4-15 best effort data transmission 1-11 boot software 6-6 boundary hub 3-8, 5-16 C cabling 2-5 console attachment B-2 for RS-232 ports B-2 modem attachment B-6 campus network 3-1, 3-3, 3-4, 5-15, 5-16 cells used in data transmission 1-3 changing configuration settings 5-32 classical IP over ATM networks 1-8, 5-18 c
console attaching to RS-232 port B-1 cabling B-2 configuration 4-7, 5-32 default settings 2-5, 4-7 displaying configuration 5-29 entering 6416SW commands 4-3 installation message 2-7 logging off 5-12, 5-26 modem configuration B-7 RS-232 port attachment 2-5, 2-13 sending alerts 5-22 setting prompt 5-11 setting timeout 5-12 SNMP traps 7-50 troubleshooting 7-11 used for network management 6-1 Console port 2-5, 2-13 E D H data bits, configuring 4-7, 4-15 disabling ATM media modules 5-33 ATM ports 5-15 displ
isolated mode 5-33 modifying configuration settings 5-32 K N keystroke functions for 6416SW commands 4-4 naming 6416SW 5-10 NetView for AIX 1-9 network service access point (NSAP) E-1, E-2 network-to-network interface 3-6, 3-8, 5-15, 5-16 NNI See network-to-network interface notices, electronic emissions ii Nways Campus Manager - ATM 6-1 L LANs, interconnecting via ONcore ATM hub 1-2 LE client 7-28 LE server 7-31 LEDs error conditions 7-4, 7-6 module and port status 2-10 normal 6416SW operation 2-7,
ports (continued) configuring logical links 3-8, 5-16 Console port 2-13 displaying configuration 5-29 status displayed by LEDs 2-10 troubleshooting 7-15, 7-19, 7-20 using NNI interface 3-8, 5-16 power supply problems 7-2, 7-9 problem determination See troubleshooting prompt, configuring 5-11 Q Q.
SET LOGICAL_LINK command 3-8, 5-16 SET MODULE command 5-32, 5-33 SET PORT command 5-15, 5-32 SET STATIC_ROUTE command 5-16 SET TERMINAL HANGUP command 4-16 SET TERMINAL PROMPT command 5-11 SET TERMINAL TIME_OUT command 5-12 SHOW MODULE command 5-29 SHOW PORT command 5-29 slot positions for 6416SW module 1-5 slot positions in hub 2-3 SMIT facility 7-25, 7-27, 7-28, 7-29, 7-31 SNMP access rights 5-22 ARP server 5-21 community table 5-22 default gateway 5-21 functions supported 1-9, 6-2 IP address 5-18 managin
troubleshooting (continued) LAN emulation 7-39 other problems 7-44 ping operation 7-25, 7-27, 7-28, 7-29, 7-31 power supply 7-9 using RS-232 ports 2-14 using trap messages 7-50 U UNI See user-to-network interface unpacking 2-2 upgrading 6416SW microcode 2-13, 6-6 FPGA picocode 6-7 UPLOAD command D-1 upload operations configuring AIX for TFTP D-1 dumps 6-7 error log 6-8 traces 6-8 user devices 3-3, 3-6 user password 5-8, 6-4 user-to-network interface 3-6, 5-15 V virtual path service provider 3-8 W WANs,
