ATM Configuration and Troubleshooting Guide HP-UX 11.0, 11i v1, 11i v1.6 and 11i v2 Manufacturing Part Number: B1056-90008 August 2003 U.S.A. © Copyright 2003 Hewlett-Packard Development Company L.P. All rights reserved.
Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.
©copyright 1989-1991 The University of Maryland ©copyright 1988 Carnegie Mellon University ©copyright 1991-2000 Mentat Inc. ©copyright 1996 Morning Star Technologies, Inc. ©copyright 1996 Progressive Systems, Inc. ©copyright 1991-2000 Isogon Corporation, All Rights Reserved. Trademark Notices UNIX is a registered trademark of The Open Group. X Window System is a trademark of the Massachusetts Institute of Technology. MS-DOS and Microsoft are U.S. registered trademarks of Microsoft Corporation.
iv
Contents 1. ATM Adapter Overview Understanding the HP ATM Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Installing and Configuring the ATM Software Installing the ATM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Installation Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Migrating from an Earlier ATM Software Version . . . . . . . . . .
Contents Planning Your VC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary of Traffic Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a VC Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring SVC Traffic Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of SVC Traffic Profiles . . . . . .
Contents Configuring Secondary LAN Emulation Services . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring EMS HA-ATM for the ELAN Interfaces . . . . . . . . . . . . . . . . . . . . . . . . Special Considerations for HP-UX 11.X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Local Recovery Delay Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Monitor for the ELAN Interface Resource . . . . . . . . . . . . . . . . . . . . . .
Contents Checking for Bind Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Determining the Type of an ATM Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 8. Migrating from the J2803B or J2498A ATM Adapters Possible Migrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Installing the New Adapter and Software - Summary . . . . . . . . . . . . . . . . . . . . . .
Contents Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Start Logging and Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Status of NetTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 13. Cables and Connectors Cable Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . For ATM Adapters with MMF or SMF Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . For ATM Adapters with UTP Cat 5 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UTP Cat 5 Cable and Connector Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Direct-Connect Cable . . . . . . . . . . . . . . . . .
Tables Table 1. HP-UX 11i Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Table 2. Publishing History Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv Table 3. Additional Sources for ATM Product Information . . . . . . . . . . . . . . . . . . . . xvi Table 4. Additional General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Table 2-1.
Tables xii
About This Document This document describes how to install, configure, and troubleshoot ATM on HP-UX 10.20 and 11.X platforms. Intended Audience HP intends this manual for system managers or administrators responsible for configuring and maintaining ATM on HP-UX 10.20 and 11.X platforms.
Publishing History Table 2 provides the manufacturing part number, the respective operating systems, and for the publication date, for the ATM Configuration and Troubleshooting Guide. Table 2 Publishing History Details Document Manufacturing Part Number Operating Systems Supported Publication Date B1056-90007 HP-UX 10.20 HP-UX 11.0 HP-UX 11i HP-UX 11i v1 June 2002 B1056-90008 HP-UX 10.20 HP-UX 11.
Chapter 4 Configuring LAN Emulation Interfaces – Use this chapter to learn about LAN emulation, and to configure and verify ELAN Interface configuration. Chapter 5 Configuring SVCs and PVCs – Use this chapter to learn how to plan your VC configuration, configure SVC Traffic parameters, and configure PVCs. Chapter 6 Configuring EMS High Availability over ATM – Use this chapter to learn about local and remote recovery within Event Monitoring Service High Availability over ATM (EMS HA-ATM).
Related Product Information You can find related product information (except for discontinued products) in the sources listed in Table 3 below. Note that many of these documents are also available on the HP WWW site http://www.docs.hp.com. NOTE Because the J2804A and J3557A adapters are discontinued, their documentation is not included in Table 3 below.
Table 3 Additional Sources for ATM Product Information (Continued) For information about: System Administration Manager (SAM) ATM screens—contains help on parameter descriptions Read: SAM online help: - Choose an item from the Help menu. - Use the Help button. - Press the F1 key. HP-UX ATM administration commands Command man pages (see ATM Commands on page 180).
Related General Information Table 4 below lists other HP documentation that you might find useful while using and troubleshooting your ATM network. Note that many of these documents are also available on the HP WWW site http://www.docs.hp.com. Table 4 Additional General Information For information about: Read: General networking Networking Overview (for 10.
KeyCap The name of a keyboard key. Note that Return and Enter both refer to the same key. Emphasis Text that is emphasized. Bold Text that is strongly emphasized. Bold The defined use of an important word or phrase. ComputerOut Text displayed by the computer. UserInput Commands and other text that you type. Command A command name or qualified command phrase.
• xx The version of HP-UX that you are using.
1 ATM Adapter Overview This chapter contains the following section that describes the ATM adapter: • Chapter 1 “Understanding the HP ATM Adapter” on page 2.
ATM Adapter Overview Understanding the HP ATM Adapter Understanding the HP ATM Adapter The HP ATM adapter allows you to run one Classical IP (CIP) interface and up to 32 emulated LAN (ELAN) interfaces at the same time, as shown in Figure 1-1 below: Figure 1-1 ATM Configuration with CIP and ELAN Interfaces CIP LEC LEC CIP System B ATM network System A CIP LEC LEC ATM switches System C LEC LEC Edge device System D Ethernet or Token Ring network System F System E System A has one ATM adapter inst
ATM Adapter Overview Understanding the HP ATM Adapter The ATM adapter in system A is also a member of two Emulated LANs (ELANs). So, it also has another two network interfaces, which are configured as LAN Emulation Clients (LECs). Through one LEC interface, System A is a member of one ELAN, and through the other LEC interface it is a member of another ELAN. TCP/IP is used as the networking protocol on top of these ELANs.
ATM Adapter Overview Understanding the HP ATM Adapter 4 Chapter 1
2 Installing and Configuring the ATM Software This chapter contains the following sections that describe installing and configuring the ATM software: Chapter 2 5
Installing and Configuring the ATM Software 6 • “Installing the ATM Software” on page 7. • “Preparing for Configuration” on page 17. • “Configuring the ATM Card Parameters” on page 20.
Installing and Configuring the ATM Software Installing the ATM Software Installing the ATM Software ATM software installation guidelines, things to know if you are migrating from an earlier version of the software, and the steps for installation are provided in the sections below.
Installing and Configuring the ATM Software Installing the ATM Software ✓ After you have installed the new ATM software, both the new software bundle and the previous bundle are present. Do not remove the previous bundle, because it is not an empty bundle. EXCEPTION: If you are installing one of new the HP-PCI software products—A5483A, A5513A, A5515A, or J3572BA—on a system that currently has the earlier J3572AA software installed, the contents are rolled to the new software product.
Installing and Configuring the ATM Software Installing the ATM Software NOTE The J2468A, J2804A, and J3557A adapters are discontinued beginning with this release. The corresponding software numbers are still shown in Table 2-1 and 2-2 below. This is because it is still displayed when you run swinstall, for backward compatibility. Table 2-1 ATM Adapters and Corresponding ATM Software for HP-UX 10.20 and 11.
Installing and Configuring the ATM Software Installing the ATM Software Table 2-1 ATM Adapters and Corresponding ATM Software for HP-UX 10.20 and 11.0 (Continued) Corresponding ATM Software ATM Adapter 10 “New” Software Number “Old” Software Number J2499A J2499A J2806CA (HP-HSC ATM/155) (HP-HSC ATM/155 Link Software for J2499A) (HP-HSC ATM/155 & ATM/622 Link Software for HP-UX 11.
Installing and Configuring the ATM Software Installing the ATM Software The following table lists the corresponding ATM 11i software and supported hardware along with the “old” software numbers as implemented on HP-UX 10.20 and 11.0x.
Installing and Configuring the ATM Software Installing the ATM Software Table 2-2 ATM Adapters and Corresponding ATM Software for HP-UX 11i v1 (Continued) Corresponding ATM Software ATM Adapter 12 Software Number on HP-UX 11i v1 J2468A ATM-01 (HP-HSC ATM/622) (HSC ATM; Supported Hardware= J2468A, J2469A, J2499A, J3420B and J573A Supported Software= J2806CA) J2469A ATM-01 (HP-HSC ATM/155) (HSC ATM; Supported Hardware= J2468A, J2469A, J2499A, J3420B and J573A Supported Software= J2806CA) J2499A A
Installing and Configuring the ATM Software Installing the ATM Software Table 2-2 ATM Adapters and Corresponding ATM Software for HP-UX 11i v1 (Continued) Corresponding ATM Software ATM Adapter Software Number on HP-UX 11i v1 J3420B ATM-01 (HP-HSC ATM/155) (HSC ATM; Supported Hardware= J2468A, J2469A, J2499A, J3420B and J573A Supported Software= J2806CA) J3557A ATM-00 (HP-PCI ATM/155) (PCI ATM; Supported Hardware= A5483A, A5513A, A5515A and J3557A Supported Software= J3572AA and J3572BA) J3573A
Installing and Configuring the ATM Software Installing the ATM Software you have installed a J3573A ATM adapter and now are installing the ATM software for it, we recommend you select the J3573A software product (instead of the J2806CA software product) in the swinstall list. Another thing to keep in mind when installing the ATM software is that if you install multiple ATM adapters of the same bus type (HP-PCI or HP-HSC), you need to install only one of the software products for that bus type.
Installing and Configuring the ATM Software Installing the ATM Software Step 4. Run the swinstall program by using the following command: /usr/sbin/swinstall This opens the “Software Selection” window. Step 5. Change the Source Host Name, if necessary, and then enter the mount point of the drive in the Source Depot Path field. Select the OK button to return to the “Software Selection” window. The “Software Selection” window now contains a list of available software to install. Step 6.
Installing and Configuring the ATM Software Installing the ATM Software Step 14. If no errors are reported during installation, prepare for configuration, and configure the ATM adapter as described later in this chapter.
Installing and Configuring the ATM Software Preparing for Configuration Preparing for Configuration Before you start configuring your ATM adapter, check that the following are true: • The ATM adapter and software are installed (use lanscan as described in “B” on page 192). • You have an IP address and subnet mask for every interface that will be configured on the ATM adapter. You can configure one Classical IP interface and up to 32 emulated LAN interfaces on the same adapter.
Installing and Configuring the ATM Software Preparing for Configuration — When using LAN emulation, we recommend that you put all of your ATM systems in a separate subnet and use an MTU size of 9 Kbytes for the subnet. — Use an MTU size of 1500 bytes for subnets that include “legacy” systems. — Do not configure a Classical IP (CIP) interface with an MTU size less than 576 bytes (as defined in RFC 1063) or larger than 9180 bytes (the default).
Installing and Configuring the ATM Software Preparing for Configuration — For the K-Class servers, install the J2469A ATM adapter in the I/O board, avoiding the core I/O. — For the T600 servers, if you have multiple I/O boards, distribute the ATM adapters in each I/O expansion board so that the network load is balanced. • HP-PCI bus. — In the V-Class servers, each card cage connects to two PCI buses—one half of the cage connects to one bus, and the other half connects to the second bus.
Installing and Configuring the ATM Software Configuring the ATM Card Parameters Configuring the ATM Card Parameters The following steps describe how to configure the ATM card adapters. Step 1. Log in as root. Step 2. Type sam to start up the System Administration Manager (SAM) utility. Step 3. Select the “Networking and Communications” icon (double-click the icon, or choose Open from the “Actions” menu) in the SAM main window. Step 4.
Installing and Configuring the ATM Software Configuring the ATM Card Parameters • Manual entry if the ATM switch does not support ILMI. Step 8. Set the UNI Version field to the appropriate value for your ATM switch. If you intend to use the ABR traffic type on SVCs, your ATM switch must be UNI 4.0 compliant and you must also set the UNI Version field to UNI 4.0.
Installing and Configuring the ATM Software Configuring the ATM Card Parameters • LAN Emulation (see Chapter 4, “Configuring LAN Emulation Interfaces,” on page 37). Once you have configured the ATM adapter and configured at least one network interface (Classical IP or LAN Emulation), the ATM adapter is ready to transmit and receive data using Switched Virtual Connections (SVCs).
3 Chapter 3 Configuring a Classical IP over ATM Interface over an ATM Interface 23
Configuring a Classical IP over ATM Interface over an ATM Interface This chapter contains the following sections that discuss configuring the Classical IP interface on your ATM adapter: 24 • “Summary of Classical IP over ATM” on page 25. • “Configuring the ATM Adapter for Classical IP over ATM” on page 28. • “Verifying That the Classical IP Interface is Operational” on page 34. • “Configuring Multiple ATM Adapters” on page 35.
Configuring a Classical IP over ATM Interface over an ATM Interface Summary of Classical IP over ATM Summary of Classical IP over ATM Switched Virtual Connections (SVCs) are established using ATM addresses. Classical IP over ATM is a mechanism for resolving IP addresses to ATM addresses using an ATM ARP Server, which maps IP addresses to ATM addresses. “Classical IP and ARP over ATM” (RFC 1577) specifies a way of allowing IP and ARP to run over ATM.
Configuring a Classical IP over ATM Interface over an ATM Interface Summary of Classical IP over ATM Each node on the LAN reads the ARP request, and the node that “owns” the IP address replies with a packet that contains its MAC address. Figure 3-1 below shows this process.
Configuring a Classical IP over ATM Interface over an ATM Interface Summary of Classical IP over ATM server replies with the corresponding ATM address, which the client can then use to establish an ATM connection in the normal way. Once the ATM connection is established, IP traffic can be transferred over it, encapsulated in ATM cells. Figure 3-2 below shows this process.
Configuring a Classical IP over ATM Interface over an ATM Interface Configuring the ATM Adapter for Classical IP over ATM Configuring the ATM Adapter for Classical IP over ATM Your HP ATM adapter can run one Classical IP interface as well as up to 32 emulated LAN interfaces.
Configuring a Classical IP over ATM Interface over an ATM Interface Configuring the ATM Adapter for Classical IP over ATM The example in Figure 3-3 below shows an ATM LIS with one ATM ARP server and two ATM ARP clients. Figure 3-3 ATM LIS with One ARP Server and Two Clients System A IP Address: 12.13.14.13 Subnet Mask: 255.255.248.0 Node Type: ATM ARP Server ATM Address: 47000580ffe1000000f21a2087.080009c6fc00.00 A1 ATM Network A2 A3 ATM Switch System C IP Address: 12.13.14.15 Subnet Mask: 255.255.248.
Configuring a Classical IP over ATM Interface over an ATM Interface Configuring the ATM Adapter for Classical IP over ATM So, for example, if your 10.20 system has three ATM adapters, and each one has a CIP interface, the names map as follows: Table 3-1 • Adapter CIP Interface Name atm0 ipa0 atm1 ipb0 atm2 ipc0 HP-UX 11.X: cip100 Numeric ATM adapter number. Range depends on the number of ATM adapters installed in the system.
Configuring a Classical IP over ATM Interface over an ATM Interface Configuring the ATM Adapter for Classical IP over ATM NOTE Before you configure Classical IP, you must first configure the ATM adapter as described in “Configuring the ATM Card Parameters” on page 20. To configure the adapter as a Classical IP over ATM ARP Server, follow these steps (see the SAM online help for descriptions of the parameters): Step 1. Log in as root. Step 2. Type sam to start SAM. Step 3.
Configuring a Classical IP over ATM Interface over an ATM Interface Configuring the ATM Adapter for Classical IP over ATM NOTE The IP address of the Classical IP interface must not belong to the same subnet as any other network interface on any other network adapter in the same HP 9000 system. It must be unique in your network. Step 8. Ensure that the MTU Size is not smaller than 576 bytes (as defined in RFC 1063) or larger than 9180 bytes (the default setting).
Configuring a Classical IP over ATM Interface over an ATM Interface Configuring the ATM Adapter for Classical IP over ATM Step 6. If an IP interface is already listed in the “Configured Interfaces” list, highlight the interface and select Modify Interface from the “Actions” menu. This opens the “Modify IP interface” window. If no IP interface is listed in the “Configured Interfaces” list, select Add IP Interface from the “Actions” menu. This opens the “Add IP interface” window.
Configuring a Classical IP over ATM Interface over an ATM Interface Verifying That the Classical IP Interface is Operational Verifying That the Classical IP Interface is Operational To verify that the CIP interface is operational, follow these steps: Step 1. Use the command ping IP_address or ping hostname towards another operational ATM system to verify that the Classical IP interface is working correctly. Step 2.
Configuring a Classical IP over ATM Interface over an ATM Interface Configuring Multiple ATM Adapters Configuring Multiple ATM Adapters You can use multiple ATM adapters in a system, with the following restrictions: • The maximum number of ATM adapters supported in any given system, as indicated in the HP ATM Release Notes provided with the ATM software, must not be exceeded. • Duplicate IP addresses or ATM addresses must not be used in an LIS.
Configuring a Classical IP over ATM Interface over an ATM Interface Configuring Multiple ATM Adapters 36 Chapter 3
4 Configuring LAN Emulation Interfaces This chapter contains the following sections that describe LAN emulation interface configuration: Chapter 4 37
Configuring LAN Emulation Interfaces 38 • “HP LAN Emulation Client” on page 39. • “Summary of LAN Emulation” on page 40. • “Configuring an ELAN Interface” on page 50. • “Verifying the ELAN Interface Configuration” on page 57.
Configuring LAN Emulation Interfaces HP LAN Emulation Client HP LAN Emulation Client HP’s ATM adapter software provides LAN Emulation Client (LEC) functionality conforming to the ATM Forum 1.0 specifications for LAN Emulation Version 1 and Version 2. HP’s LEC software supports up to 32 instances of the LEC per adapter—that is, one adapter can belong to up to 32 emulated LANs (ELANs) simultaneously and independently.
Configuring LAN Emulation Interfaces Summary of LAN Emulation Summary of LAN Emulation Figure 4-1 below shows how the components of an emulated LAN work together, showing the functional interconnections of a simple ELAN consisting of two LECs, and LECS, LES, and BUS LAN Emulation Services. One LEC is resident on a system with a direct ATM connection, and one LEC is resident on an edge device, such as an ATM switch or bridge that connects the ATM network and the legacy Ethernet or Token Ring network.
Configuring LAN Emulation Interfaces Summary of LAN Emulation interface, which appears to the higher layer software as though a real physical Ethernet or Token Ring interface is present. The LEC must register with the LES and BUS associated with the ELAN it wishes to join before it can participate in it. Each LEC is identified by a unique ATM address and MAC address. IMPORTANT HP’s implementation of ATM does not support MPOA for Token Ring networks.
Configuring LAN Emulation Interfaces Summary of LAN Emulation LAN Emulation Connection Types LAN Emulation components communicate with each other using a series of ATM connections. LECs maintain separate connections for data transmission and control traffic. The control connections are as follows: • Configuration Direct VCC. This is a bidirectional point-to-point VCC set up by the LEC to the LECS. • Control Direct VCC. This is a bidirectional VCC set up by the LEC to the LES. • Control Distribute VCC.
Configuring LAN Emulation Interfaces Summary of LAN Emulation • From the network, using ILMI. The LECS ATM address is automatically retrieved from the network by the LEC, using ILMI. Note that the HP ATM software supports auto-discovery of the LECS ATM address using ILMI; however, the ATM switch or LECS might not. In such cases, the LEC is unable to automatically discover the LECS ATM address, and uses the LECS well-known ATM address instead (see the next bullet below).
Configuring LAN Emulation Interfaces Summary of LAN Emulation 3. Data transfer. When the LEC receives a network-layer packet from a higher layer protocol to send to some destination LEC, the source LEC initially does not know the ATM address of the destination LEC but knows only its IP address. The source LEC first sends an ARP request to the BUS to obtain the destination LEC’s MAC address. The BUS forwards this ARP request to all known end systems on the ELAN.
Configuring LAN Emulation Interfaces Summary of LAN Emulation Multiprotocol Over ATM (MPOA) Multiprotocol Over ATM (MPOA) provides high-performance, scalable routing over switched ATM networks. To do this, MPOA establishes a shortcut—a virtual circuit (VC) between two MPOA hosts in different subnets—that bypasses any routers in between the two hosts. The pieces of MPOA, and how they work together, are described below. IMPORTANT HP’s implementation of ATM does not support MPOA for Token Ring networks.
Configuring LAN Emulation Interfaces Summary of LAN Emulation that the ATM Forum specifies that an MPC can be used by more than one LEC. However, in HP’s implementation of MPOA, an MPC can be used by only one LEC. • Next Hop Server (NHS)—A server part of the NHRP protocol; it resides on an MPOA router, and the MPS on the same router works with the NHS to resolve address resolution requests from MPCs. • Next Hop Client (NHC)—A client part of the NHRP protocol; it can reside on a router.
Configuring LAN Emulation Interfaces Summary of LAN Emulation An Overview of Routing In MPOA, routing is distributed among the edge devices and the MPOA hosts in the MPOA system. MPCs examine the destination address of each outbound packet. If the packet is to be routed, the MPC forwards the packet to a router via the MPC’s internal LEC interface and then starts monitoring the flow of packets. By doing the monitoring, the MPC determines when a shortcut route would be better for a specific data flow to use.
Configuring LAN Emulation Interfaces Summary of LAN Emulation established for that specific data flow. Then, any future packets that are part of that data flow are sent over the shortcut route instead of the default route. If the packet has the destination’s MAC address and a matching Ingress Cache Entry exists—that is, the MPC has previously forwarded packets to that MAC address—the MPC then checks its Ingress Cache to see if a shortcut already exists for that data flow.
Configuring LAN Emulation Interfaces Summary of LAN Emulation Figure 4-2 below shows all of the MPOA pieces and how they work together.
Configuring LAN Emulation Interfaces Configuring an ELAN Interface Configuring an ELAN Interface NOTE Before you configure LAN Emulation, you must first configure the ATM adapter as described in “Configuring the ATM Card Parameters” on page 20. Preparing for Configuration Have the following information ready before you begin configuring an ELAN interface: • The name of the ELAN that you want the ELAN interface to join.
Configuring LAN Emulation Interfaces Configuring an ELAN Interface • HP-UX 10.20: ela0 Alphabetic ATM adapter number, translated from numeric adapter number (0 = a, 1 = b, 2 = c, etc.). Range depends on the number of ATM adapters installed in the system. Numeric ELAN number. Range is 0 through 31. So, for example, if your 10.
Configuring LAN Emulation Interfaces Configuring an ELAN Interface • HP-UX 11.X: el100 Numeric ELAN number. Range is 1 through 32. Numeric ATM adapter number. Range depends on the number of ATM adapters installed in the system. So, for example, if your 11.
Configuring LAN Emulation Interfaces Configuring an ELAN Interface For Ethernet and Token Ring Networks You can configure the ATM adapter to be a member of up to 32 ELANs simultaneously. The ATM adapter has one logical LEC for every ELAN of which it is a member. IMPORTANT HP’s implementation of ATM does not support MPOA for Token Ring networks. This is because of a lack of MPOA Server (MPS) support for Token Ring in routers. Also, HP’s implementation does not support MPOA for secondary LANs.
Configuring LAN Emulation Interfaces Configuring an ELAN Interface IMPORTANT If you want to configure MPOA, be sure to specify values for these fields: • LANE Version—select LANE V2. • MPOA Client—select enabled. • MPC Selector. For the MPC Selector field, see the SAM online help for information about determining the values to specify. We recommend that you do not enable LLC multiplexing, because it degrades performance.
Configuring LAN Emulation Interfaces Configuring an ELAN Interface Step 10. If you want to configure secondary LAN Emulation Services, see “Configuring Secondary LAN Emulation Services” on page 114.
Configuring LAN Emulation Interfaces Configuring an ELAN Interface (c) Source routing configured at the Token Ring network side must have source routing or SRT configured at the LEC side. Transparent mode configured at the Token Ring network side must have transparent mode or SRT configured at the LEC side.
Configuring LAN Emulation Interfaces Verifying the ELAN Interface Configuration Verifying the ELAN Interface Configuration To verify that the LEC has successfully joined its primary ELAN and, if configured, its secondary LAN Emulation services, follow these steps: Step 1. To view the LEC configuration and status information, exit SAM. At the command line, type this command: elstat -n net_interface -v Examples: (HP-UX 10.20) For interface ela1: elstat -n ela1 -v (HP-UX 11.
Configuring LAN Emulation Interfaces Verifying the ELAN Interface Configuration Multicast Send VCC Multicast Forward VCC : 0,113 : 0,253 Maximum Data Frame Size : 1516bytes Control Timeout : 120s Vcc Timeout Period : 1200s Maximum Retry Count : 1 Aging Time : 300s Expected Arp Response Time : 1s Flush TimeOut : 4s Maximum Unknown Frame Count : 1 Maximum Unknown Frame Time : 1s Connection Complete Timer : 4s LEC Initial Control Timeout : 10s LEC Control Timeout Multiplier : 5s LEC V2 Max Unknown Frame Coun
Configuring LAN Emulation Interfaces Verifying the ELAN Interface Configuration If there are any problems, see “Troubleshooting LAN Emulation” on page 226 for more details.
Configuring LAN Emulation Interfaces Verifying the ELAN Interface Configuration 60 Chapter 4
5 Configuring SVCs and PVCs The ATM adapter is ready to operate using SVCs as soon as it is enabled and you have configured either a Classical IP network interface (see Chapter 3, “Configuring a Classical IP over ATM Interface over an ATM Interface,” on page 23), or an Emulated LAN network interface (see Chapter 5 61
Configuring SVCs and PVCs Chapter 4, “Configuring LAN Emulation Interfaces,” on page 37). For the ATM adapter to operate using PVCs, you must first configure an IP interface (see Chapter 3, “Configuring a Classical IP over ATM Interface over an ATM Interface,” on page 23). This chapter contains these sections that describe SVC and PVC configuration: 62 • “Planning Your VC Configuration” on page 63. • “Configuring SVC Traffic Parameters” on page 68. • “Configuring PVCs” on page 76.
Configuring SVCs and PVCs Planning Your VC Configuration Planning Your VC Configuration Be sure to plan a configuration that does not exceed the capacity of your ATM adapter. Read the section about traffic parameters below. Summary of Traffic Parameters Different types of traffic parameters are available, depending on your ATM adapter. NOTE See the SAM online help for more details about the traffic parameters available on your ATM adapter. ABR Available Bit Rate.
Configuring SVCs and PVCs Planning Your VC Configuration • VBR Peak Rate Variable Bit Rate. VBR corresponds to “Guaranteed” traffic. It is defined by the following three parameters: • Peak Rate • Burst Tolerance • Sustainable Rate Traffic Configuration Limitations The traffic parameter limitations are listed below to guide you when planning your ATM configuration. If you encounter any of these limitations when configuring, a message is displayed.
Configuring SVCs and PVCs Planning Your VC Configuration Creating a VC Matrix Create a VC matrix for the configuration you intend to set up with your ATM equipment. NOTE Hewlett-Packard strongly recommends that you create a VC matrix before starting to configure SVCs and PVCs. Sample Matrix In the example in Figure 5-1 below, each system is equipped with one ATM-HSC 155 Mbit/s [+] adapter.
Configuring SVCs and PVCs Planning Your VC Configuration Table 5-2 Example of VC Matrix VC Typ e of VC Config ured on Adapte r Swi tch Port In VPI, VCI Swi tch Port Out VPI, VCI Traf fic Typ e Traff ic Valu es [Mbit s/s] A --> B PVC Sys A: atm0 A1 0,10 1 A2 0,10 1 ABR MR = 30 B --> A PVC Sys B: atm0 A2 0,10 1 A1 0,10 1 ABR IR = 60 PR = 80 A --> C PVC Sys A: atm0 A1 0,10 2 A3 0,10 2 CBR C --> A PVC Sys C: atm0 A3 0,10 2 A1 0,10 2 CBR B --> C SVC Sys B: atm0 UB
Configuring SVCs and PVCs Planning Your VC Configuration Table 5-3 Chapter 5 System and Adapter MR for ABR + PR for CBR A (atm0) 30 + 90 = 120 Mbits/s Does not exceed 155 Mbits/s, so OK. B (atm0) 30 + n/a = 30 Mbits/s Does not exceed 155 Mbits/s, so OK. C (atm0) n/a + 90 = 90 Mbits/s Does not exceed 155 Mbits/s, so OK.
Configuring SVCs and PVCs Configuring SVC Traffic Parameters Configuring SVC Traffic Parameters NOTE You can configure SVC traffic profiles for both Classical IP and ELAN interfaces. SVCs are established and cleared transparently and automatically. The ATM adapter is operational for SVCs immediately after you have performed the initial configuration described in “Configuring the ATM Card Parameters” on page 20 and configured at least a Classical IP or ELAN interface for the adapter.
Configuring SVCs and PVCs Configuring SVC Traffic Parameters • NOTE Specific destination: One or more different SVC traffic profiles for use with SVCs opened towards specific destinations. Whenever an SVC is set up to a particular destination, the predefined SVC traffic profile for that destination is used. If the source and destination end systems have different performance criteria or traffic requirements, it is often necessary to manually customize the connection to ensure operation.
Configuring SVCs and PVCs Configuring SVC Traffic Parameters Table 5-4 Supported SVC Traffic Profiles Adapter Type NOTE Adapter Part Number SVC Traffic Profiles Supporte d ATM-HSC 155 Mbit/s [+] adapters J2469A & J2499A ABR, UBR ATM-HSC 155 Mbit/s [+] adapter J3420B UBR, VBR ATM-HSC 622 Mbit/s adapter J3573A ABR, UBR ATM-PCI 155 Mbit/s [+] adapters A5513A & A5515A ABR, UBR ATM-PCI 622 Mbit/s adapter A5483A ABR, UBR The ABR traffic type is supported on SVCs only if your ATM switch suppo
Configuring SVCs and PVCs Configuring SVC Traffic Parameters Using SAM Because connections can be set up to destinations with varying traffic capabilities, it is important to be able to define the traffic parameters that are used for SVCs opened to specific destinations. So, you can configure SVC traffic profiles for use with SVCs opened to specified destinations.
Configuring SVCs and PVCs Configuring SVC Traffic Parameters NOTE The SVC traffic profile is used only if the connection setup is issued by the ATM adapter. It is not used to negotiate or reject incoming connection setup requests. To configure an SVC traffic profile in SAM, follow these steps: Step 1. Log in as root. Step 2. Type sam to start SAM. Step 3. Select “Networking and Communications”. Step 4. Select “Network Interface Cards”. Step 5.
Configuring SVCs and PVCs Configuring SVC Traffic Parameters Using the Command atmconfig See the atmconfig(1M) man pages for more information about how to configure an SVC traffic profile using the atmconfig add command. NOTE Different types of traffic profiles are available on different HP ATM adapters. Ensure that you configure a supported SVC traffic profile when you use the command atmconfig add.
Configuring SVCs and PVCs Configuring SVC Traffic Parameters Step 6. Highlight the interface that you want to configure and select Define SVC Traffic Parameters... from the “Actions” menu. This opens the “Define SVC Traffic Parameters” window, which lists all SVCs and the SVC traffic profiles already defined. Step 7. Highlight the SVC that you want to modify and select the Modify... button. The SVC traffic profile’s current traffic parameter configuration is displayed. Step 8.
Configuring SVCs and PVCs Configuring SVC Traffic Parameters Step 3. Select “Networking and Communications”. Step 4. Select “Network Interface Cards”. Step 5. Highlight the ATM adapter that you want to configure, and then choose Configure from the “Actions” menu. This opens the “Configure ATM Card” window, which lists all configured interfaces for the ATM adapter. Step 6. Highlight the interface that you want to configure and select Define SVC Traffic Parameters... from the “Actions” menu.
Configuring SVCs and PVCs Configuring PVCs Configuring PVCs PVCs can be configured for only Classical IP interfaces. NOTE When configuring a PVC, you must configure it on the ATM system, ATM switch, and destination ATM system. We recommend you configure PVCs to start automatically at system start-up time (see “Automatic Reconfiguration of PVCs” on page 85). During adapter operation, if the required resources are consumed by SVCs, you will not be able to create a PVC.
Configuring SVCs and PVCs Configuring PVCs ATM/AAL vc information table VPI,VCIPMP Type Use SEL Dest.
Configuring SVCs and PVCs Configuring PVCs Example of PVC/ATM Switch Configuration Figure 5-2 below is an example of a PVC and ATM switch configuration.
Configuring SVCs and PVCs Configuring PVCs Table 5-6 VC Example of VC Matrix Type of VC Configure d on Adapter Swi tch Port In VPI,V CI Switc h Port Out VPI,V CI Traff ic Type TV [Mbits/ sec] MR = 30 A --> B PVC Sys A: atm0 A1 0,101 A2 0,101 ABR B --> A PVC Sys B: atm0 A2 0,101 A1 0,101 ABR PR = 80 A --> C PVC Sys A: atm0 A1 0,102 A3 0,102 CBR PR = 90 C --> A PVC Sys C: atm0 A3 0,102 A1 0,102 CBR B --> C SVC Sys B: atm0 UBR C --> B SVC Sys C: atm0 UBR NO
Configuring SVCs and PVCs Configuring PVCs • PVCs towards adapters of a different type: Ensure that you configure a traffic profile type that is also supported on the destination ATM adapter. Table 5-7 below lists the PVC traffic profiles supported on HP ATM adapters (discontinued adapters are not shown).
Configuring SVCs and PVCs Configuring PVCs Using SAM To add a PVC in SAM, follow these steps: Step 1. Log in as root. Step 2. Type sam to start SAM. Step 3. Select “Networking and Communications”. Step 4. Select “Network Interface Cards”. Step 5. Highlight the ATM adapter that you want to configure, and then choose Configure from the “Actions” menu. This opens the “Configure ATM Card” window, which lists all configured interfaces for the ATM adapter. Step 6.
Configuring SVCs and PVCs Configuring PVCs Modifying a PVC Using SAM NOTE Modifying a PVC disrupts any traffic currently using it. The Modify option provided by SAM allows you to easily change the configuration details of a PVC. SAM then automatically deletes the existing PVC and adds a PVC with the new configuration. Note that the list of already defined PVCs is dynamic: when no PVCs are using a definition, it no longer appears in the list.
Configuring SVCs and PVCs Configuring PVCs The modified PVC appears in the list of PVCs already configured. Step 12. Exit SAM and verify that the PVC works, as described in “Verifying a PVC’s Configuration” on page 83 (below). Verifying a PVC’s Configuration To verify that a PVC that you have added or modified works, follow these steps: Step 1.
Configuring SVCs and PVCs Configuring PVCs 0 Up 0,198 No 0 Up SVC LLC LEC, MPC 01 * 5 Step 2. Check that the PVC is displayed for the VPI/VCI numbers of the PVC you added/modified, the destination IP address is displayed, and the status is “Up”. Step 3. To verify that the PVC works correctly, type this command: ping destination_IP_address If ping does not work, see “Checking Network Connectivity (Local PVC Configuration)” on page 196. Step 4.
Configuring SVCs and PVCs Configuring PVCs Step 5. Highlight the ATM adapter that you want to configure, and then choose Configure from the “Actions” menu. This opens the “Configure ATM Card” window, which lists all configured interfaces for the ATM adapter. Step 6. Highlight the IP (ipxx or cipxxx) interface that you want to configure and select Configure PVCs... from the “Actions” menu. Step 7. Highlight the PVC that you want to remove and select the Remove... button. Step 8.
Configuring SVCs and PVCs Creating a Back-to-Back Connection Creating a Back-to-Back Connection A back-to-back connection is used when a direct link without an ATM switch is required between systems; for example, when ATM is used as a high-speed channel between a workstation and an HP server. Figure 5-3 below shows a back-to-back connection. NOTE Only Classical IP over ATM is supported on back-to-back connections.
Configuring SVCs and PVCs Creating a Back-to-Back Connection • An IP address must be defined with a subnet mask in the correct format (for example, 255.255.255.252). For example, if you assign one system a class C address, then you must assign the other system a class C address. Cabling When cabling a back-to-back connection take special care to ensure that the receive (Rx) socket in the first system is connected to the transmit (Tx) socket in the second system, and vice versa.
Configuring SVCs and PVCs Creating a Back-to-Back Connection 88 Chapter 5
6 Configuring EMS High Availability over ATM This chapter contains the following sections that describe local and remote recovery within Event Monitoring Service High Availability over Chapter 6 89
Configuring EMS High Availability over ATM ATM (EMS HA-ATM): • “EMS High Availability Overview” on page 91. • “Types of Recovery” on page 93. • “Types of Failures Managed by EMS HA-ATM” on page 97. • “Migrating from HA-ATM to EMS HA-ATM” on page 106. • “Configuration Recommendations” on page 110. • “Configuring EMS HA-ATM for Local Recovery” on page 112. • “Configuring EMS HA-ATM for Remote Recovery (Using MC/ServiceGuard)” on page 130.
Configuring EMS High Availability over ATM EMS High Availability Overview EMS High Availability Overview EMS HA-ATM is a version of High Availability that is fully integrated with EMS. It consists of local recovery with EMS and remote recovery with MC/ServiceGuard and EMS, and its monitoring daemon is named hatmmon. NOTE EMS HA-ATM feature is now supported on HP-UX workstations (7xx series) and servers.
Configuring EMS High Availability over ATM EMS High Availability Overview • EMS HA-ATM in conjunction with HP MC/ServiceGuard manages the remote recovery and transfer of client applications from one system to another if local recovery is not possible or not configured. Recovery is provided for system failure, failure of all adapters in a system, and failure of all the ATM switches or cables connected to the adapters in the primary system.
Configuring EMS High Availability over ATM Types of Recovery Types of Recovery EMS HA-ATM consists of local recovery with EMS and remote recovery with MC/ServiceGuard and EMS. Each of these recovery types is described next. Local Recovery The EMS HA-ATM functionality manages local recovery of an ELAN interface, ATM adapter, or link failure. The EMS HA-ATM functionality performs the following tasks: • Monitors ELAN interfaces to detect failure.
Configuring EMS High Availability over ATM Types of Recovery defined at the MC/ServiceGuard level as a package with a “package/application” IP address. For more details about defining packages, see your MC/ServiceGuard documentation. NOTE For EMS remote recovery with MC/ServiceGuard, you must use MC/ServiceGuard version A.10.10 or later for HP-UX 10.20, MC/ServiceGuard version A.11.01 or later for HP-UX 11.0, and MC/ServiceGuard version A.11.01 or later for HP-UX 11.11 MC/service guard version A.11.
Configuring EMS High Availability over ATM Types of Recovery How Local and Remote Recovery are Related On systems A and B in Figure 6-1 below, each primary LAN Emulation Client interface (ela0, ela1 ...) of the primary adapter is configured and allocated a secondary LAN Emulation Client interface (elb0, elb1 ...) using SAM. Note that this example uses HP-UX 10.20 naming conventions.
Configuring EMS High Availability over ATM Types of Recovery The EMS HA-ATM software installed on systems A and B allows you to define that the interface elb0 is the secondary for primary interface ela0, and elb1 is the secondary of primary ela1. MC/ServiceGuard must also be installed on both systems; it allows you to define system B as the adoptive node in the package.
Configuring EMS High Availability over ATM Types of Failures Managed by EMS HA-ATM Types of Failures Managed by EMS HA-ATM Figure 6-2 below shows examples of the possible failure points in an ATM network. Note that this example uses HP-UX 10.20 naming conventions.
Configuring EMS High Availability over ATM Types of Failures Managed by EMS HA-ATM • EMS HA-ATM: — Failure of one of the ATM adapters in the primary system. — Failure of one of the ATM links connected to the ATM adapters in the primary system. — Failure of one of the ATM switches connected to the ATM adapters in the primary system. EMS HA-ATM in conjunction with MC/ServiceGuard provides remote recovery for the following types of failures: • System failure. • Failure of all adapters in a system.
Configuring EMS High Availability over ATM Types of Failures Managed by EMS HA-ATM • A Broadcast and Unknown Server (BUS), which manages broadcast and multicast traffic and the discovery of unknown destination end systems. The ATM adapter joins an ELAN by contacting the LECS to obtain the ATM address of the LES and BUS for that ELAN. If the primary LAN Emulation Services fail, the secondary LAN Emulation Services come into operation.
Configuring EMS High Availability over ATM Types of Failures Managed by EMS HA-ATM Figure 6-3 below shows this configuration. Figure 6-3 Configuration with Secondary LECS and ELAN Secondary LECS Primary LES/BUS Secondary LES/BUS Primary LECS Primary ELAN Secondary ELAN ELAN interface ELAN interface ELAN interface What Happens in Case of Failure In the configuration in Figure 6-3 above, if the primary ELAN fails, then the connections between all the LECs and the primary LES/BUS are released.
Configuring EMS High Availability over ATM Types of Failures Managed by EMS HA-ATM ATM Adapter/Link/Switch Failure Local recovery for an adapter, link, or switch failure requires a specific kind of configuration. The configuration, and what happens if an adapter, link, or switch fails, are discussed below. Necessary Configuration The local recovery solution relies on the recommended configuration of having at least two identical ATM adapters per system, with the adapters connected to separate switches.
Configuring EMS High Availability over ATM Types of Failures Managed by EMS HA-ATM Both ATM adapters must be enabled in SAM. The ELAN interfaces are monitored by the EMS monitor daemon hatmmon. Figure 6-4 below shows a configuration with a primary adapter (atm0) and a secondary adapter (atm1). Note that this example uses HP-UX 10.20 naming conventions.
Configuring EMS High Availability over ATM Types of Failures Managed by EMS HA-ATM secondary ELAN interfaces on the secondary ATM adapter. Figure 6-5 below shows this situation (the dotted lines represent the failure of adapter atm0). Figure 6-5 Primary ELAN Interfaces Transferred to Secondary Interfaces—Local Recovery atm0 adapter ela0 ela1 atm1 adapter elb0 elb1 The IP addresses for the primary ELAN interfaces are associated with the secondary ELAN interfaces.
Configuring EMS High Availability over ATM Types of Failures Managed by EMS HA-ATM NOTE For HP-UX 10.20, when hatmmon is started, it causes an immediate transfer to the secondary adapters if the primary ELAN interface is not operational. Also, if IP addresses are already associated with an operational secondary ELAN interface, hatmmon leaves those addresses on the secondary interface. For HP-UX 11.
Configuring EMS High Availability over ATM Types of Failures Managed by EMS HA-ATM Also, the floating (package) IP addresses are transferred (removed from the active adapter in the primary system and added to the active adapter in the secondary system).
Configuring EMS High Availability over ATM Migrating from HA-ATM to EMS HA-ATM Migrating from HA-ATM to EMS HA-ATM Note that although the non-EMS version of HA-ATM is being discontinued beginning with this release, these migration instructions are included in case you have not migrated to EMS HA-ATM yet. If you have not, we recommend that you migrate as soon as possible. Migrating from remote recovery with the non-EMS version of HA-ATM to remote recovery with EMS HA-ATM is very simple.
Configuring EMS High Availability over ATM Migrating from HA-ATM to EMS HA-ATM For each package you want to migrate for remote recovery, follow these steps (note that you must do this on each node the package runs on, within each cluster): Step 1. Per cluster, do one of these two things: • If the cluster configuration has no packages that use the ELAN interface resource, ensure that the cluster is not running.
Configuring EMS High Availability over ATM Migrating from HA-ATM to EMS HA-ATM this only when you are migrating the package on the node the package_configuration_file actually resides on (the file can be on only one node the package runs on, within each cluster). • package_control_script_file is the name of the MC/ServiceGuard package control script for the package/ELAN interface you are migrating. This command runs the migration script.
Configuring EMS High Availability over ATM Migrating from HA-ATM to EMS HA-ATM If you do not want to migrate another package, go to the next section, “Configuration Recommendations”. Remember that once you have migrated to EMS HA-ATM, you must not use the serv_hatmmon daemon (the non-EMS HA-ATM daemon) to monitor the ELAN interface. Otherwise, problems will occur.
Configuring EMS High Availability over ATM Configuration Recommendations Configuration Recommendations To eliminate single point of failure (SPOF) in a system containing ATM adapters, Hewlett-Packard recommends you follow these guidelines when designing your ATM network for High Availability: • For local recovery: — Configure your ATM network so that ATM adapters are always backed up by identical adapters. — Install at least two identical ATM adapters per system.
Configuring EMS High Availability over ATM Configuration Recommendations — For MC/ServiceGuard, we recommend that you configure each system in the cluster with two LAN adapters for MC/ServiceGuard management and migration. The LAN is used as a heartbeat by MC/ServiceGuard.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery Configuring EMS HA-ATM for Local Recovery A summary of the steps for configuring EMS HA-ATM for local recovery is as follows: Step 1. Ensure that the following things have already been done: ✓ The ATM adapters have been installed (see the installation instructions provided with the ATM adapter). Be sure the primary adapter and all of its secondary adapters are installed in the same system.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery Configuring Secondary LAN Emulation Services The rules and steps for configuring secondary LAN Emulation Services are discussed in the following sections. IMPORTANT HP’s implementation does not support MPOA for secondary LANs.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery NOTE Although the ATM software allows you to configure only one LECS, we do not recommend this, because a failure of the LECS will prevent operation of the part of your ATM network that relies on that LECS. Configuring Secondary LAN Emulation Services Configuring secondary LAN Emulation Services means configuring a secondary LECS and a secondary LES/BUS pair.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery The LEC Selector you specify modifies the last byte of the ATM address of the ATM adapter. Each ELAN interface on an ATM adapter must have a unique LEC Selector. Step 9. Specify the ELAN name of the secondary ELAN. NOTE The ELAN name is case sensitive. So, you must configure the ELAN name in SAM exactly as it is configured in the LECS. NOTE The primary ELAN and secondary ELAN can have the same name.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery • Figure 6-6 Install several secondary ATM adapters, and configure the secondary ELAN interfaces for a primary ELAN interface “in series.” An example of this—with one secondary ELAN interface configured on each secondary adapter—is shown in Figure 6-6 below (note that this example uses HP-UX 10.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery As another example, the secondary ELAN interfaces for primary interface ela0 were configured in this order: eld0, elb0, and elc0.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery Configuring EMS HA-ATM for ELAN Interfaces When SAM creates an ELAN on a secondary adapter, it always uses the same secondary ELAN interface allocation conventions. For example, if you have three primary ELAN interfaces (ela0, ela1, and ela2) configured on primary adapter atm0, the secondary interfaces on secondary adapter atm1 will be allocated as follows: • HP-UX 10.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery Step 1. Log in as root. Step 2. Type sam to start SAM. Step 3. Select “Networking and Communications”. Step 4. Select “Network Interface Cards”. Step 5. Highlight the primary ATM adapter that has the ELAN interface you want to configure EMS HA-ATM for, and then choose Configure from the “Actions” menu. This opens the “Configure ATM Card” window, which lists all configured interfaces for the ATM adapter. Step 6.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery The assigned secondary interface is now ready to take over from the primary interface if it fails. The HA Related Interface Name field in the “Configure ATM Card” window now shows all of the assigned secondary interfaces for each primary ELAN interface.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery Special Considerations for HP-UX 11.X If you are running EMS HA-ATM on HP-UX 11.X, you must keep in mind the following things: • On HP-UX 11.X, EMS HA-ATM requires that the primary ELAN interface being monitored must have been operational at least once since the last reboot of the system. Additionally, all secondary ELAN interfaces should be operational when EMS HA-ATM is started for the first time after a reboot.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery • If a local recovery occurs to a secondary ELAN interface, and the system reboots at a later time, if the primary ELAN interface is still not operational, EMS HA-ATM will not provide local recovery to the secondary ELAN interfaces. This is due to the information described in the previous bullet (above). At this time, follow all steps described in the previous bullet.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery Configuring the Local Recovery Delay Period NOTE Once you have configured the delay period, it is not in effect when the hatmmon monitor first starts (regardless of whether you start it manually or MC/ServiceGuard starts it [see “Starting the Monitor for the ELAN Interface Resource” below]).
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery Starting the Monitor for the ELAN Interface Resource NOTE If you will also be using EMS HA-ATM for remote recovery (with MC/ServiceGuard), you do not need to do this task; MC/ServiceGuard will perform the monitoring request. To start the EMS HA-ATM monitor for the ELAN interface resource in SAM, follow these steps: Step 1. Log in as root. Step 2. Type sam to start SAM. Step 3. Select “Resource Management”. Step 4.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery When you add a monitoring request for an ELAN interface resource, the monitoring daemon (hatmmon) is automatically started for that interface. The daemon continues to run as long as that monitoring request exists in SAM.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery atm3 9360 ipd0* 9180 none none none none 0 0 0 0 0 0 0 0 0 0 atm1 9360 ipb0* 9180 none none none none 0 0 0 0 0 0 0 0 0 0 atm2 9360 ipc0* 9180 none none none none 0 0 0 0 0 0 0 0 0 0 ela0 ela1 ela2 1500 1500 1500 200.128.168 201.128.168 202.128.168 200.128.169.5 201.128.169.5 202.128.169.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery Step 14. Go to the next section, “Verifying the Local Recovery Configuration”. Verifying the Local Recovery Configuration To verify that each configured primary ELAN interface is assigned one or more corresponding secondary ELAN interfaces, follow the steps below for each ELAN interface you want to verify. Step 1. Check the log files by typing this command: more /var/opt/hatmmon/log/*hatmmon.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery Step 4. Unplug the ATM cable on the adapter configured with the primary ELAN interfaces. If local failover has occurred correctly, the following things are true: • The telnet connection is not broken when you disconnect the cable. • The netstat -in command shows that the IP address has been transferred to a secondary ELAN.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Local Recovery Stopping the Monitor for the ELAN Interface Resource To stop the monitor for the ELAN interface resource in SAM, follow these steps: Step 1. Log in as root. Step 2. Type sam to start SAM. Step 3. Select “Resource Management”. Step 4. Select “Event Monitoring Service”. This opens the “Event Monitoring Service” window, which lists all the monitored resources on the system. Step 5.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Remote Recovery (Using MC/ServiceGuard) Configuring EMS HA-ATM for Remote Recovery (Using MC/ServiceGuard) A summary of the steps for configuring EMS HA-ATM for remote recovery (using MC/ServiceGuard) is as follows: Step 1. Ensure that the following things have already been done: ✓ EMS HA-ATM for local recovery has been configured (see “Configuring EMS HA-ATM for Local Recovery” on page 112).
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Remote Recovery (Using MC/ServiceGuard) Each of these ways is described in the following sections. Editing the MC/ServiceGuard File To manually edit the MC/ServiceGuard package configuration file (/etc/cmcluster/package_name/package_configuration_file), follow these steps: Step 1.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Remote Recovery (Using MC/ServiceGuard) Step 7. Select the Modify Package Resource Dependencies... button. This opens the “Package Resource Dependencies” window. Step 8. Select the Add Resource... button. Step 9. Step through the hierarchy of classes until you get to the appropriate class level. To do this, in the “Resource classes” list, select the following items, in this order: a. net b. interfaces c. switched d.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Remote Recovery (Using MC/ServiceGuard) Verifying the Remote Recovery Configuration NOTE This verification assumes that you have already configured and verified EMS HA-ATM for local recovery. To verify the remote recovery configuration, follow these steps: Step 1.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Remote Recovery (Using MC/ServiceGuard) elb1 elb1 atm1 ipb0* elb0 elb0 elb0 1500 1500 9360 9180 1500 1500 1500 25.128.20.0 25.128.20.0 none none 25.128.10.0 25.128.10.0 none 25.128.20.193 25.128.20.194 none none 25.128.10.193 25.128.10.194 none 4 4 0 0 2 2 0 0 0 0 0 0 0 0 10 10 0 0 3 3 0 2 2 0 0 0 0 0 0 0 0 0 0 0 0 The netstat -in display for HP-UX 10.
Configuring EMS High Availability over ATM Configuring EMS HA-ATM for Remote Recovery (Using MC/ServiceGuard) el200 el200:1 el101 el201 Chapter 6 1500 1500 1500 1500 25.128.20.0 25.128.20.0 none none 25.128.20.195 25.128.20.
Configuring EMS High Availability over ATM Modifying ATM Parameters when Using EMS HA-ATM Modifying ATM Parameters when Using EMS HA-ATM CAUTION While the hatmmon daemon is running, do not use SAM or any of the ATM configuration commands to change the configuration for an ATM adapter that has any ELAN interfaces being monitored by EMS HA-ATM. If you need to modify the configuration of an ATM adapter that is involved in EMS HA-ATM, always follow these steps: Step 1. Unconfigure EMS HA-ATM: a.
Configuring EMS High Availability over ATM Modifying ATM Parameters when Using EMS HA-ATM See the MC/ServiceGuard documentation and the cmhaltnode and cmrunnode man pages for details.
Configuring EMS High Availability over ATM Stopping the Daemon Stopping the Daemon You can stop the hatmmon monitoring daemon in two ways: • Unconfigure EMS HA-ATM, which stops the daemon immediately (see “Unconfiguring EMS HA-ATM” on page 139). Note: this is the preferred way.
Configuring EMS High Availability over ATM Unconfiguring EMS HA-ATM Unconfiguring EMS HA-ATM EMS HA-ATM manages local and remote recovery with the EMS monitor hatmmon. If EMS HA-ATM is unconfigured for a primary ELAN interface, the monitor for that interface stops immediately. An MC/ServiceGuard package that has specified a package resource dependency for an ELAN interface relies on hatmmon to provide status for that resource.
Configuring EMS High Availability over ATM Unconfiguring EMS HA-ATM 140 Chapter 6
7 Getting Status Information with ATM Commands This chapter contains the following subsections that describe commands you can use to get status information about your ATM system: Chapter 7 141
Getting Status Information with ATM Commands 142 • “Getting Information about an ATM Adapter” on page 143. • “Getting Information about ATM Network Interfaces” on page 144. • “Getting ATM Information” on page 147. • “Getting Information for All Active Virtual Circuits” on page 148. • “Getting Information for a Specific VPI and VCI” on page 150. • “Getting Statistics for the AAL Interface” on page 151. • “Getting Cell Statistics, Addresses, Used VCCs, and UNI Version” on page 151.
Getting Status Information with ATM Commands Command Summary Command Summary The commands you can use to get information about an ATM adapter, the ATM network interfaces, and about ATM in general are described in this section. Getting Information about an ATM Adapter To get information about a specific ATM adapter, you can use the commands shown in Table 7-1 below.
Getting Status Information with ATM Commands Command Summary Table 7-1 Commands for Getting ATM Adapter Information (Continued) To do this: Use this command: Display the Classical IP ARP table atmmgr card_inst_num show -i Display SVC traffic profiles for an ATM adapter atmconfig show -c card_inst_num Note that card_inst_num is the card instance number; for example, 0, 1, 2....
Getting Status Information with ATM Commands Command Summary Note that net_interface is the name of the network interface; for example, ela0, ela1... for HP-UX 10.20, or el101, el201... for HP-UX 11.X.
Getting Status Information with ATM Commands Command Summary Getting MPOA Information To get MPOA information, you can use the commands shown in Table 7-3 below.
Getting Status Information with ATM Commands Command Summary Getting ATM Information To get information about ATM in general, you can use the commands shown in Table 7-4 below. Table 7-4 Commands for Getting General ATM Information To do this: HP-UX 10.20: Display IP statistics and check traffic on an ATM adapter HP-UX 11.X: Display IP statistics and check traffic on ATM network interfaces HP-UX 10.
Getting Status Information with ATM Commands Command Examples Command Examples The following sections provide examples of the commands you can use to monitor your ATM system. Getting Information for All Active Virtual Circuits You can get information on all currently active virtual circuits for an adapter, and also check SVC and PVC connections with other systems. Both Classical IP and LAN Emulation virtual circuits are listed.
Getting Status Information with ATM Commands Command Examples The output from the atmmgr card_inst_num show -v command shows all currently active VCs for the specified adapter. The above example shows this information: • The VC used by the signaling protocol (0,5). The destination IP address is displayed as N/A (not applicable). • The VC used by ILMI (0,16). The destination IP address is displayed as N/A (not applicable).
Getting Status Information with ATM Commands Command Examples • Two VCs (0,202 and 0,203) that are carrying LLC ISO 8802/2 multiplexed types of traffic (for example, MPOA MPC-to-MPS, MPOA MPC-to-MPC, or LLC V2-capable LEC-to-LEC traffic). LLC LEC, MPC is in the “Use” field for each of these VCs. The “Index” column in the output refers to the “Current Traffic Parameters Configurations” table, displayed with the command atmmgr card_inst_num show -t.
Getting Status Information with ATM Commands Command Examples The output from the command is as follows, where EPtRf is the End Point Reference, whose value is given as a decimal: ATM/AAL vc information Getting Statistics for the AAL Interface Use the following command to check AAL interface statistics (a card instance number of 0 is used): atmmgr 0 show -a The output from the command is as follows: AAL5 statistics CRC-32 errors in received SDUs : 0 SDUs lost due to reassembly timeout : 0 SDUs too big :
Getting Status Information with ATM Commands Command Examples ATM Cell statistics and status ATM address :47000580ffe1000000f21c154e.080009c6fc91.00 Maximum number of VCCs : 1979 VCCs in use : 8 0 VPI bits, 11 VCI bits UNI version : 3.0 Received cells : 2248029122 Dropped received cells : 0 Transmitted cell : 61570485 In the ATM address, the separators (.) are used to indicate the different fields, but are not counted as part of the 40-character maximum.
Getting Status Information with ATM Commands Command Examples Number of Line FEBE : Number of Section BIP (B1): 0 9767789 Note: BIP is Bit Interleave Parity, FEBE is Far End Block Error To determine the type (HP-HSC or HP-PCI) of the ATM adapter, you can use the ioscan command (see “Determining the Type of an ATM Adapter” on page 166).
Getting Status Information with ATM Commands Command Examples VPI,VCI -----------------------------------------------------------------------25.128.169.200 Static PVC 0,100 25.128.169.201 Dynamic PVC 0,101 25.128.169.202 Dynamic < ATM Address on 40 characters > SVC 0,50 25.128.169.
Getting Status Information with ATM Commands Command Examples Getting an ATM Network Interface’s SVC Traffic Profiles Use the following command to display the SVC traffic parameters for an ATM network interface (the example given is for the network interface el100): atmconfig show -n el100 The output from the command is as follows: SVC traffic parameters configurations for ATM adaptator 0 Destination ATM Address Traffic Peak Sust. Burst Min. Init Interface type:Source ATM selector Type Rate Rate Tol.
Getting Status Information with ATM Commands Command Examples ATM address : 47000580ffe1000000f124121f.080009c6fca2.00 MAC address : 080009123456 ELAN name : elk1 Status : Operational State : Current LECS’s ATM Address : 47000580ffe1000000f21a1e28.0020481a1e28.05 (Manual entry) Configuration Direct VCC : -,LES’s ATM Address : 47000580ffe1000000f21a1e28.0020481a1e28.10 Control Direct VCC : 0,110 Control Distribute VCC : 0,255 BUS’s ATM Address : 47000580ffe1000000f21a1e28.0020481a1e28.
Getting Status Information with ATM Commands Command Examples Note that for the above example, only the primary LEC has been configured. To list all current ELAN interfaces, use the command netstat -i.
Getting Status Information with ATM Commands Command Examples The above output example shows the destination MAC address-to-ATM address mappings for the Primary LEC and, if configured, the Secondary LEC. It also shows the VPI/VCI numbers of the Data Direct VC that is open between both LECs.
Getting Status Information with ATM Commands Command Examples mpcstat -n el100 -s And, that output could look like this: Ingress/Egress Cache statistics of all of the MPCs on the system: Ingress Cache Total Tx Packets over shortcut : 1000 Egress Cache Total Rx Packets over shortcut : 1234 Primary MPOA Client statistics MPOA - Tx Resolve Requests Imposition Reply Acks Imposition Reply Insuf EC Resources Imposition Reply Insuf SC Resources Imposition Reply Insuf SC/EC Resources Imposition Reply Unsupporte
Getting Status Information with ATM Commands Command Examples Unrecognized Extensions Loop Detecteds Protocol Address Unreachables Protocol Errors SDU Size Exceededs Invalid Extensions Invalid Replies Authentication Failures Hop Count Exceededs : : : : : : : : : 4 6 56 100 20 50 54 12 15 Getting MPC Ingress/Egress Cache and MPS Tables To display the Ingress Cache, Egress Cache, and MPS tables for the MPC tied to the LECs for a specific ATM network interface, use this command: mpcarp -n net_interface So,
Getting Status Information with ATM Commands Command Examples MPOA Routers (MPOA Servers) Table for LEC interface el100: MPOA Routers (MPOA Servers) Table for Primary LEC: MPS MAC (MPS Router) Address -----------080900010203 080900020304 080901010101 080900030405 Router MPS Address -----------------------------------------47010203040506070809101112.010203040506.98 47010203040506070809101112.010203040506.98 47010203040506070809101112.010203040506.98 47010203040506070809101112.010203040506.
Getting Status Information with ATM Commands Command Examples MPC Egress Cache Table for LEC interface el100: MPC Egress Cache Table for Primary LEC: MPS MAC (MPS Router) Address IPV4 Address Ingress MPC Address ------------ -------------- -----------------------------------------080910010203 192.234.118.67 47010203040506070809101112.010203040506.99 47010203040506070809101112.010203040506.
Getting Status Information with ATM Commands Command Examples ni1* lo0 atm0 ipa0 lan0 ela0 ela1 ela2 0 4608 9360 9180 1500 1500 1500 1500 none loopback none 25.128.1 15.128.168 25.128.10 25.128.20 25.128.30 none localhost none atm0_sihaya sihaya 25.128.10.18 25.128.20.18 25.128.30.
Getting Status Information with ATM Commands Command Examples Getting Network I/F IP Stats/Traffic (HP-UX 11.X) To check traffic on a system, use the netstat -i command, as follows: netstat -i The output from the command is as follows, for HP-UX 11.X: Name lo0 lan0 cip100 el100 cip101 el200 Mtu 4136 1500 9180 1500 9180 1500 Network 127.0.0.0 15.128.168.0 25.128.1.0 25.128.10.0 25.128.2.0 25.128.20.0 Address localhost coriolis 25.128.1.9 25.128.10.79 25.128.2.8 25.128.20.
Getting Status Information with ATM Commands Command Examples Getting Adapter & Network I/F Info (HP-UX 11.X) Use the following command to see if the ATM adapter has been installed and is up, and to see which network interfaces have been configured: lanscan The output from the command is as follows, for HP-UX 11.
Getting Status Information with ATM Commands Command Examples You can also use the ioscan command to identify the number of ATM adapters in the system; in the Class column of the above output, two ATM adapters (card instances 0 and 1) are present.
Getting Status Information with ATM Commands Command Examples For example, the output of the ioscan -fCatm command might look like this (the driver names are shown in bold in this example): Class I H/W Path Driver S/W State H/W Type Description ======================================================================= ...
Getting Status Information with ATM Commands Command Examples 168 Chapter 7
8 Migrating from the J2803B or J2498A ATM Adapters When you migrate from a J2803B or J2498A ATM adapter to an A5483A, A5513A, A5515A, J2469A, J2499A, or J3573A adapter, the configuration Chapter 8 169
Migrating from the J2803B or J2498A ATM Adapters of the ATM adapter that was previously in the same slot is maintained. However, because certain parameters and functions are not the same on all Hewlett-Packard ATM adapters, you might need to change the configuration accordingly. This chapter contains the following sections that describe how to migrate from the J2803B adapter or the J2498A adapter: 170 • “Possible Migrations” on page 171.
Migrating from the J2803B or J2498A ATM Adapters Possible Migrations Possible Migrations Table 8-1 below shows the possible ATM adapter migrations. NOTE Because the J2468A adapter is discontinued, it is not shown in the “To ATM Adapter” column. Table 8-1 Possible ATM Adapter Migrations From ATM Adapter To ATM Adapter Reconfiguration Necessary J2803B (HP-HSC ATM/155) J2469A (HP-HSC ATM/155) Check for unsupported traffic profiles on SVCs and reconfigure if necessary.
Migrating from the J2803B or J2498A ATM Adapters Installing the New Adapter and Software - Summary Installing the New Adapter and Software Summary NOTE Details of installing ATM adapters are given in the installation documentation provided with each adapter. A summary of the steps for installing the new ATM adapter and the software is as follows: Step 1. Halt and power off the system. Step 2. Remove the old adapter. Step 3. Install the new adapter. Step 4. Reboot the system. Step 5.
Migrating from the J2803B or J2498A ATM Adapters Checking for and Reconfiguring Unsupported Traffic Profiles Checking for and Reconfiguring Unsupported Traffic Profiles To check for unsupported traffice profiles and then reconfigure any, if necessary, follow these steps: Step 1. Use the following commands to see the configuration of the configured VCs (the example is for card instance number 0): atmmgr 0 show -v This shows all the PVCs configured and all SVCs currently open.
Migrating from the J2803B or J2498A ATM Adapters Checking for and Reconfiguring Unsupported Traffic Profiles NOTE The ABR traffic type is supported on SVCs only if your ATM switch supports UNI 4.0 and if you set the UNI version parameter to UNI 4.0 on the ATM adapter (see “Configuring the ATM Card Parameters” on page 20). Step 3.
9 Troubleshooting This chapter helps you verify basic ATM adapter functionality and isolate and identify some of the more common problems that might occur when using an ATM network.
Troubleshooting identify the actual location of the problem. The troubleshooting procedures described in this chapter are presented in the form of flowcharts that help you check the following: • The ATM hardware and software installation. • Specific PVC and SVC connections. • Your LAN Emulation configuration. • Your High Availability configuration.
Troubleshooting Chapter 9 • “Troubleshooting Classical IP” on page 195. • “Checking the ATM Address Network Prefix” on page 219. • “Troubleshooting LAN Emulation” on page 226. • “Troubleshooting Secondary LAN Emulation Services” on page 245. • “Troubleshooting MPOA” on page 250. • “Troubleshooting EMS HA over ATM” on page 265. • “Contacting Your HP Representative” on page 281.
Troubleshooting Before You Begin Troubleshooting Before You Begin Troubleshooting Before you start to troubleshoot any part of the ATM product, follow these steps: Step 1. Ensure that the switch and cabling (MMF, SMF, or UTPCat5, and 155 Mbits/s or 622 Mbits/s) are appropriate for the type of connector on your ATM adapter. Consult your switch documentation if necessary. Step 2.
Troubleshooting Before You Begin Troubleshooting Step 10. If your adapter has an SMF or MMF interface, disconnect the cable. Using a special, commercially-available cleaning kit, clean the adapter sockets and the cable plugs. Reconnect the cable. Wait for 10 minutes before checking if the problem persists. When troubleshooting network connections, you must also check the switch and the remote end system.
Troubleshooting ATM Commands ATM Commands Table 9-1 below lists commands you can use when administering and troubleshooting the ATM network. For details of the full command syntax and command usage, see Chapter 7, “Getting Status Information with ATM Commands,” on page 141, or the command’s man page.
Troubleshooting ATM Commands Table 9-1 ATM Administration and Troubleshooting Commands To do this: NOTE Chapter 9 Use this command: Display MPC Ingress Cache, Egress Cache, and MPS tables mpcarp Display MPC configuration, status, and statistics mpcstat Do not use the lanadmin command with the ATM adapter.
Troubleshooting Determining Which ATM Adapters You Have Determining Which ATM Adapters You Have If you want to find out the types of ATM adapters you have installed on a system, you can use one or both of these commands, depending on the information you are looking for: • atmmgr card_inst_num show -p The applicable information in this command’s output is as follows: — Medium: SONET or SDH. — Speed: 155 Mbits/sec or 622 Mbits/sec.
Troubleshooting Determining Which ATM Adapters You Have Note: BIP is Bit Interleave Parity, FEBE is Far End Block Error Now that you know the speed (155) and media (Multi-Mode fiber) of the adapter with card instance number 1, you might want to determine which type (HP-HSC or HP-PCI) that adapter is.
Troubleshooting Determining Which ATM Adapters You Have So, using Table 9-2, the ATM adapter with card instance number 1 is an A5513A adapter (because that is the 155 Multi-Mode fiber adapter that corresponds to the driver name atm2pci).
Troubleshooting Resetting an ATM Adapter Resetting an ATM Adapter To reset an ATM adapter, use the command atminit, as follows: atminit card_inst_num where: card_inst_num is the card instance number of the ATM adapter (also called the logical unit number).
Troubleshooting Restarting an ATM Adapter Restarting an ATM Adapter To restart an adapter, use the command atminit card_inst_num or the appropriate selection in SAM (see the steps below). The PVCs closed by atmstop are automatically re-established. To use SAM to restart an ATM adapter, follow these steps: Step 1. Log in as root. Step 2. Type sam to start SAM. Step 3. Select “Networking and Communications”. Step 4. Select “Network Interface Cards”. Step 5.
Troubleshooting Resetting/Restarting an ATM Network Interface Resetting/Restarting an ATM Network Interface You can reset/restart a specific network interface, without having to reset/restart the entire ATM adapter and disrupt traffic on other network interfaces on the adapter. To reset/restart a specific network interface, use the command atminit_net, as follows: atminit_net net_interface where net_interface is the ATM network interface name.
Troubleshooting Stopping an ATM Adapter Stopping an ATM Adapter To stop an ATM adapter, use the command atmstop, as follows: atmstop card_inst_num where: card_inst_num is the card instance number of the ATM adapter (this is also called the logical unit number). You can use the command ioscan -fCatm to display the logical unit numbers of all ATM adapters in your network (see “Resetting an ATM Adapter” on page 185). The command stops the ATM adapter gracefully, closing all PVCs and SVCs.
Troubleshooting Stopping an ATM Network Interface Stopping an ATM Network Interface To stop a specific ATM network interface on an adapter without stopping the entire adapter, use the command atmstop_net, as follows: atmstop_net net_interface where net_interface is the ATM network interface name. For example, net_interface could be one of the following: — For HP-UX 10.20: — ipa0 for the adapter’s Classical IP interface. — ela1 for an ELAN interface. — For HP-UX 11.
Troubleshooting Troubleshooting the ATM Adapter and Software Installation Troubleshooting the ATM Adapter and Software Installation The flowchart for troubleshooting ATM adapter and software installation is shown in Figure 9-1 below. Each of the circled letters is described on the pages after the flowchart.
Troubleshooting Troubleshooting the ATM Adapter and Software Installation Figure 9-1 Flowchart for Checking Adapter and Software Installation Start A Check the hardware installation using ioscan C No OK? Reinstall the adapter (see the appropriate installation instructions) Yes B Check the software installation using lanscan Reinstall the software (see "Installing and and Configuring the ATM Software") No OK? Yes Check the hardware link connectivity G F E No No LEDs OK? Turn the connector Yes
Troubleshooting Troubleshooting the ATM Adapter and Software Installation A Use ioscan. Use this command to check that the driver is accessible: ioscan -f The ATM adapter ioscan entry should look something like this: Class I H/W Path Driver S/W State H/W Type Description ==================================================================== ...
Troubleshooting Troubleshooting the ATM Adapter and Software Installation Hardware Path 8/8 10/12/6 Station Address 0x112233445566 0x0800098421C7 Crd In# 0 0 Hardware State UP UP Net-Interface NameUnit State atm0 UP lan0 UP NM ID 4 5 MAC Type ATM ETHER HP DLPI Support No Yes Mjr Num 163 52 Example (HP-UX 11.
Troubleshooting Troubleshooting the ATM Adapter and Software Installation If the LED display does not indicate a successful installation, ensure that the ATM adapters are connected to the correct type of switch port with the correct type of cable (MMF or SMF or UTP Cat 5) and interface (155 Mbits/s or 622 Mbits/s). F Turn the connector. Check the cable to make sure that the connector is connected transmit-receive and not receive-receive (with the connector installed the wrong way).
Troubleshooting Troubleshooting Classical IP Troubleshooting Classical IP To troubleshoot Classical IP, check the following things: Chapter 9 • The local PVC configuration; see “Checking Network Connectivity (Local PVC Configuration)” on page 196. • The switch and end system configuration; see “Checking Network Connectivity (Switch & End System)” on page 201. • SVCs and the ARP mechanism; see “Checking Network Connectivity (SVC and ARP)” on page 206.
Troubleshooting Troubleshooting Classical IP Checking Network Connectivity (Local PVC Configuration) The flowchart for checking the local PVC configuration is shown in Figure 9-2 below. Each of the circled letters is described on the pages after the flowchart.
Troubleshooting Troubleshooting Classical IP Figure 9-2 Flowchart for Checking the Local PVC Configuration A Start B Create a PVC matrix C D Use lanscan ping to ATM interface on the remote system No ping OK? Yes Network connectivity OK; end of troubleshooting E Verify local system’s PVC configuration Yes OK? Go to "Checking Network Connectivity (Switch & End System)" in this section.
Troubleshooting Troubleshooting Classical IP NOTE If you use the flowchart to troubleshoot a PVC that has not been fully configured and has no path to the remote node, the Classical IP mechanism will use SVCs to establish the connection. Consequently, a problem with the PVC will not be detected and you will be unable to troubleshoot correctly. If a PVC is fully configured and is not functioning properly, an error is returned. A Start.
Troubleshooting Troubleshooting Classical IP The destination IP address should appear on the same line as the PVC you created (defined with a VPI,VCI). The type of the PVC should be Dynamic. Step 2. If the IP address of the destination host is not present, wait a minute and use atmmgr 0 show -i to display the IP ARP table again. The IP ARP entity repeats a request for an address until it receives a valid response. Step 3.
Troubleshooting Troubleshooting Classical IP the local system, on the switch, and on the remote system, ping will open an SVC to the destination. To check that ping is operating over the PVC use this command: atmmgr card_inst_num show -v If the PVC was not correctly configured, the atmmgr show -v command will show that an SVC has been opened to your destination. In this case, you must correct the PVC configuration. E Verify local system’s PVC configuration (ping has reported an error).
Troubleshooting Troubleshooting Classical IP Checking Network Connectivity (Switch & End System) The flowchart for checking the switch and end system configuration is shown in Figure 9-3 below. Each of the circled letters is described on the pages after the flowchart.
Troubleshooting Troubleshooting Classical IP Figure 9-3 Flowchart for Checking Switch and End System Configuration Start A B Use ifconfig to check if local IP interface is correctly set up C OK? No Use SAM to reconfigure the ATM adapter Yes D Verify local system’s No PVC configuration E No Use SAM to reconfigure the PVC OK? Yes F Verify the switch’s PVC configuration G No Reconfigure the switch OK? Yes H Verify remote system’s PVC configuration I OK? No Reconfigure the PVC on the remote system
Troubleshooting Troubleshooting Classical IP A Start. You should already have completed the steps outlined in the flowchart “Checking Network Connectivity (Local PVC Configuration)” on page 196. B Use ifconfig. If the ping command hangs, check that the adapter’s IP interface has been set up correctly. Use this command: ifconfig net_interface where net_interface is the IP interface to be checked; for example, ipa0 or cip100.
Troubleshooting Troubleshooting Classical IP For HP-UX 11.X: Routing tables Dest/Netmask Gateway 127.0.0.1 127.0.0.1 25.128.1.9 25.128.1.9 25.128.2.8 25.128.2.8 25.128.10.79 25.128.10.79 25.128.20.79 25.128.20.79 15.128.175.79 15.128.175.79 127.0.0.0 127.0.0.1 25.128.1.0 25.128.1.9 25.128.2.0 25.128.2.8 25.128.10.0 25.128.10.79 25.128.20.0 25.128.20.79 15.128.168.0 15.128.175.79 default 15.128.168.
Troubleshooting Troubleshooting Classical IP H Check the remote system’s configuration. Using the configuration software provided with the remote system’s ATM adapter, check that the PVC has been configured correctly. Ensure that the same traffic parameters are configured on both the local and remote systems. I Correct the configuration. If the remote system’s configuration is not correct, use the configuration software provided with the remote system’s ATM adapter to add or modify the PVC.
Troubleshooting Troubleshooting Classical IP Checking Network Connectivity (SVC and ARP) The flowchart for checking the SVC and ARP configurations is shown in Figure 9-4 below. Each of the circled letters is described on the pages after the flowchart.
Troubleshooting Troubleshooting Classical IP Figure 9-4 Flowchart for Checking SVC and ARP Configurations A B Start ping destination IP address OK? Yes Network connectivity OK No Read NetTL log C Yes OK? D E Contact switch vendor No No Enable tracing I Yes Check IP interface with ifconfig OK? No HP problem? Contact HP Reconfigure ATM adapter with SAM Yes F G Check ATM connectivity No OK? Yes H Use trace to locate problem Read IP/ARP table IP address located? No Go to "Checking
Troubleshooting Troubleshooting Classical IP For detailed descriptions of any of the commands described in this section, see to the command’s man pages. A Start. Before starting the flowchart, do these things: Step 1. Use SAM to ensure that the local interface is set up correctly. Ensure that the type of traffic parameters configured are compatible with those available at the remote destination system. Step 2.
Troubleshooting Troubleshooting Classical IP b. If the UNI version configured on the ATM adapter is not the same as that configured on the switch port to which it is connected, use SAM to open the “Configure ATM Card Parameters” screen. Set the UNI Version field to the correct value for your switch. Step 6. Ensure that the local and remote node are on the same logical LIS (they must use the same ARP server). Step 7.
Troubleshooting Troubleshooting Classical IP 10 bytes from 15.128.131.156: icmp_seq=2. 10 bytes from 15.128.131.156: icmp_seq=3. 10 bytes from 15.128.131.156: icmp_seq=4. ----15.128.131.156 PING Statistics---5 packets transmitted, 5 packets received, 0% packet loss If ping to the remote system is successful, the SVC is working and the ATM adapter is correctly configured. C Read NetTL log. Try to correct the problem using information logged in the file /var/adm/nettl.LOG00.
Troubleshooting Troubleshooting Classical IP The output could look like this: ipa0:flags=61 inet 25.128.169.32 netmask ffffff00 For HP-UX 11.X: ifconfig cip100 The output could look like this: cip100: flags=843 inet 25.128.1.9 netmask ffffff00 broadcast 25.128.1.255 Check that the IP address (inet) and subnet mask (netmask) are valid. Alternatively, use netstat -rn. Look at the line with the ATM adapter entry in the Interface column.
Troubleshooting Troubleshooting Classical IP 15.128.168.0 default 15.128.175.79 15.128.168.1 U UG 2 0 2 4 lan0 lan0 1500 1500 F Use the atmcheck and atmserver commands on the same (local) adapter to ensure that the SVCs between the local ATM stack and first switch are tested and working correctly. NOTE The atmcheck and atmserver commands can be used only between any two of the following ATM adapters: HP-HSC or HP-PCI. Step 1.
Troubleshooting Troubleshooting Classical IP ATMCHECK (A.01.00) Test starts on ... (c) COPYRIGHT Hewlett-Packard Company 1995. Wed Mar 13 09:59:45 1996 ATMCHECK running parameters : -------------------------------------------------------------------ATM card instance number : 0 Number of messages : 1 Length of messages : 128 ATM address of remote node: 47000580FFE1000000F21A1E2819800108000082 -------------------------------------------------------------------ATMCHECK : Connection setup time : 114 ms.
Troubleshooting Troubleshooting Classical IP QSAAL and Q93b. Symbolic values of the fields are provided if the -N option is used in the netfmt command; otherwise, output is formatted in hexadecimal. If you use the -1T option (terse mode), the formatter produces only the most significant fields in the traced packet. See “Tracing” on page 292 for more information. H Examine the IP/ARP table. Use the command atmmgr 0 show -i.
Troubleshooting Troubleshooting Classical IP Checking a Local ARP Client The flowchart for checking a local ARP client is shown in Figure 9-5 below. Each of the circled letters is described on the pages after the flowchart.
Troubleshooting Troubleshooting Classical IP Figure 9-5 Flowchart for Checking a Local ARP Client Start A Use SAM to check if ATM address of server is entered correctly No OK? Reconfigure ATM address of ARP server with SAM Yes B Check that ARP server is operational and configured as the ARP server G No Configure the ARP server OK? Check ATM connectivity for server and switch Yes On ARP server, check that local ATM adapter is registered in ARP table No C Check that SVC to server is open OK? D N
Troubleshooting Troubleshooting Classical IP Before using this flowchart you should do the following things: Step 1. Follow the troubleshooting steps outlined in the flowchart “Checking Network Connectivity (SVC and ARP)” on page 206. Step 2. Look at the “Modify IP Interface” screen in SAM to confirm that the system has been configured as an ARP client. A Use SAM to check if the ATM address of the ARP server is entered correctly. This should be performed on the local system.
Troubleshooting Troubleshooting Classical IP Before using this flowchart, use SAM to check that the system is an ARP server. Figure 9-6 Flowchart for Checking a Local ARP Client Start A Check remote system B No OK? C Reconfigure remote system Yes Troubleshoot remote system and switches A Check remote system. Ensure that the remote system is configured as an ARP client and that the ATM address of its ARP server is the one used by the local ATM adapter.
Troubleshooting Checking the ATM Address Network Prefix Checking the ATM Address Network Prefix The steps to follow to check the ATM address network prefix—a manual prefix and a dynamic prefix—are given in the sections below. Checking a Manual Network Prefix The flowchart for checking an ATM address manual network prefix is shown in Figure 9-7 below. Each of the circled letters is described on the pages after the flowchart. The ATM adapter must be started before you use this flowchart.
Troubleshooting Checking the ATM Address Network Prefix /etc/atm/atm_0/ipa0 and /etc/atm/atm_0/ela0 (HP-UX 10.20), or /etc/atm/atm_0/cip100 and /etc/atm/atm_0/el100 (HP-UX 11.X)—by hand. Figure 9-7 Flowchart for Checking a Manual Network Prefix Start A Read the ATM address No OK? C B Enter valid network prefix Yes Check the switch No OK? Configure switch Yes ATM address OK A Read the ATM address.
Troubleshooting Checking the ATM Address Network Prefix Checking a Dynamic Network Prefix (ILMI) The flowchart for checking an ATM address dynamic network prefix is shown in Figure 9-8 below. Each of the circled letters is described on the pages after the flowchart. The ATM adapter must be started before you use this flowchart (the state can be checked by using this command: atmmgr card_inst_num show -p To see how the network prefix was specified, run SAM and look at the appropriate SAM window.
Troubleshooting Checking the ATM Address Network Prefix /etc/atm/atm_0/ipa0 and /etc/atm/atm_0/ela0( HP-UX 10.20), or /etc/atm/atm_0/cip100 and /etc/atm/atm_0/el100 (HP-UX 11.X)—by hand.
Troubleshooting Checking the ATM Address Network Prefix Figure 9-8 Flowchart for Checking a Dynamic Network Prefix (ILMI) Start A Read the ATM address Yes OK? ILMI and ATM address configuration OK No B Check that ILMI daemon is running C No Start ILMI daemon OK? Yes D Check that ILMI PVC exists E No Run atminit OK? Yes F Check switch configuration OK? G No Configure the switch Yes Check log file for ILMI information Chapter 9 223
Troubleshooting Checking the ATM Address Network Prefix A Read the ATM address. Use this command: atmmgr card_inst_num show -c Check that the ATM address is known. B Check that the ILMI daemon is running. Use this command: ps -ef | grep ilmid The output should look similar to this: HP-UX 10.20: root 470 1 0 09:33:03 ? 0:00 /usr/lbin/ilmid HP-UX 11.X: root 470 1 C 0 07:39:03 ? 0:00 /usr/sbin/ilmid Start ILMI daemon. For HP-UX 10.20, use this command: /usr/lbin/ilmid For HP-UX 11.
Troubleshooting Checking the ATM Address Network Prefix E Run atminit. Use the command atminit card_instance_number to create the ILMI PVC. Applications using PVCs are disrupted when you use this command. Check the log file for information. If possible, correct the problem. F Check switch configuration. Ensure that the ILMI PVC exists and that ILMI is running on the port of the switch connected to the local system. G Check log file for ILMI information. If the switch is faulty, troubleshoot it.
Troubleshooting Troubleshooting LAN Emulation Troubleshooting LAN Emulation For LAN Emulation, there are two possible cases you might need to troubleshoot: Figure 9-9 • ATM-connected-to-ATM-connected, where both end-systems (LECs) are directly connected to an ATM switch. This is the case for systems A and B in Figure 9-9 below. • ATM-connected-to-legacy-LAN-connected, where one ATM connected end-system communicates with an end-system on a legacy LAN.
Troubleshooting Troubleshooting LAN Emulation When an ATM-connected end system is communicating with a legacy LAN end system, use traditional Ethernet or Token Ring LAN troubleshooting procedures to troubleshoot the legacy LAN system. Use the edge device’s troubleshooting procedures to troubleshoot the edge device connected to the legacy LAN system; this ensures that everything on the legacy LAN side is working correctly.
Troubleshooting Troubleshooting LAN Emulation Checking the Status and Configuration of Both Systems The flowchart for checking that both end systems are up and correctly configured is shown in Figure 9-10 below. Each of the circled letters is described on the pages after the flowchart.
Troubleshooting Troubleshooting LAN Emulation Figure 9-10 Flowchart for Checking Both End Systems’ Status Start A Run ping from source to destination LEC. Yes OK? Connection OK. END. No B Are source and destination IP interfaces both up? OK? No Run SAM to reconfigure and enable the IP interfaces. Yes C Check IP ARP table. No OK? D Yes Check that both systems' IP addresses and subnet masks belong to the same subnet. Check the end systems are operational and registered with the correct ELAN.
Troubleshooting Troubleshooting LAN Emulation NOTE This procedure assumes that both end systems are on the same IP subnet. If not, then you need a router to enable communication between subnets. If this is the case, check that your router is configured correctly to allow routing between the two subnets, then use the procedure described below. Start. Before you start this flowchart, do the following: Step 1. If practical, kill all other traffic running through both systems’ adapters before you begin.
Troubleshooting Troubleshooting LAN Emulation Step 4. Ensure that you have configured all intermediate switches. In particular, if you configured a VC with ABR traffic type on both end nodes, you must also configure the intermediate switches for ABR. Step 5. For HP-UX 11.
Troubleshooting Troubleshooting LAN Emulation a. Check that both systems’ IP addresses and subnet masks belong to the same IP subnet. If necessary, run SAM to reconfigure the IP addresses and subnet masks. If, intentionally, both systems’ IP addresses and subnet masks do not belong to the same IP subnet, check that your router is configured correctly to route between the two subnets. b.
Troubleshooting Troubleshooting LAN Emulation If the MAC-to-ATM address mapping is displayed, but the VPI/VCI numbers are not displayed, then the destination system is known to the LES, but the Data Direct VC cannot be set up between the source and destination. Do the following: Step 1. Check that the maximum number of VCCs that can be run simultaneously has not been reached.
Troubleshooting Troubleshooting LAN Emulation Checking Source/Destination ELAN IP I/F Configurations The LEC needs a unique IP interface for each ELAN that it joins. You must configure each ELAN interface with an IP address and subnet mask, by using SAM. Each ELAN represents a logical IP subnet, so the IP address and subnet mask for the LEC must be valid for the IP subnet. To verify that the LAN Emulation interfaces are configured correctly, do the following: Step 1.
Troubleshooting Troubleshooting LAN Emulation Step 4. Repeat steps 1 and 3 on the destination system. Confirm that both systems’ IP addresses and subnet masks belong to the same IP subnet and ELAN. If the two LEC interfaces belong to the same IP subnet and ELAN, but ping still does not work, there might be a problem with the LAN Emulation Services or with the ATM switch or edge device.
Troubleshooting Troubleshooting LAN Emulation Checking That Both LECs are in the Same ELAN The flowchart for checking that both LECs have successfully joined the same ELAN is shown in Figure 9-11 below. Each of the circled letters is described on the pages after the flowchart.
Troubleshooting Troubleshooting LAN Emulation Figure 9-11 Flowchart for Checking That Both LECs are in Same ELAN A B Start Is the primary LEC on both systems operational and current? Yes Both LECs have joined the ELAN. Check that ping works. OK? No C Is LECS ATM address correct on both LECs? OK? D No Run SAM and configure the correct LECS ATM address. Yes Are both LECs registered with the same LES/BUS? No OK? E Yes Run SAM and check the ELAN names on both systems.
Troubleshooting Troubleshooting LAN Emulation NOTE When an ATM-connected device is communicating with a legacy LAN device, use traditional Ethernet or Token Ring LAN troubleshooting procedures to troubleshoot the legacy LAN device. Use the edge device’s troubleshooting procedures to troubleshoot the edge device connected to the legacy LAN device; this ensures that everything on the legacy LAN side is working correctly.
Troubleshooting Troubleshooting LAN Emulation Aging Time : 300s Expected Arp Response Time : 1s Flush TimeOut : 4s Maximum Unknown Frame Count : 1 Maximum Unknown Frame Time : 1s Connection Complete Timer : 4s LEC Initial Control Timeout : 10s LEC Control Timeout Multiplier : 5s LEC V2 Max Unknown Frame Count : 3 LEC Config Local Segment ID : 345 LEC Config V2 Capable : LUNI (LANE V2) LEC Config Selective Multicast : Yes LEC Forward Disconnect Timeout : 300s LEC Min Reconfigure Delay : 1000s LEC Max Reconfi
Troubleshooting Troubleshooting LAN Emulation Aging Time : 300s Expected Arp Response Time : 1s Flush TimeOut : 4s Maximum Unknown Frame Count : 1 Maximum Unknown Frame Time : 1s Connection Complete Timer : 4s LEC Initial Control Timeout : 10s LEC Control Timeout Multiplier : 5s LEC V2 Max Unknown Frame Count : 3 LEC Config Local Segment ID : 345 LEC Config V2 Capable : LUNI (LANE V2) LEC Config Selective Multicast : True LEC Forward Disconnect Timeout : 300s LEC Min Reconfigure Delay : 1000s LEC Max Reconf
Troubleshooting Troubleshooting LAN Emulation B • The current state of the ELAN. Normally, any primary LEC configuration should be returned as “Current”, and the secondary LEC configuration should be shown as “Backup”. If the secondary LEC configuration is shown as “Current,” the primary services have failed and the backup services have taken over. • LAN Emulation Version 2 (LANE V2) information, which is associated with MPOA and LLC multiplexing, if one or both of them are enabled.
Troubleshooting Troubleshooting LAN Emulation D Check that the correct ELAN name is present. Check that the LES ATM address displayed for the ELAN name is correct. NOTE The ELAN name is case sensitive, so check that the ELAN name that is configured in the LECS exactly matches the ELAN name configured in SAM. If no value is returned for the LES ATM address, check that the LECS is OK, and that the LES ATM address is correctly defined for the ELAN in the LECS configuration file.
Troubleshooting Troubleshooting LAN Emulation • The switch/edge device. If the problem persists, make a trace (see “Tracing” on page 292) and call HP. G Once both the source and destination LECs are “Operational” on the same ELAN, check that works between the end systems, as described in “Checking the Status and Configuration of Both Systems” on page 228. Check that they both have correctly configured IP interfaces for the ELAN.
Troubleshooting Troubleshooting LAN Emulation Check that the LES is correctly defined for the ELAN in the LECS configuration file. See “Checking ELAN Access Control Rules Definitions on LECS” on page 244 for details about checking the LECS configuration file.
Troubleshooting Troubleshooting Secondary LAN Emulation Services Troubleshooting Secondary LAN Emulation Services The flowchart for troubleshooting secondary LAN Emulation Services is shown in Figure 9-11 below. Each of the circled letters is described on the pages after the flowchart.
Troubleshooting Troubleshooting Secondary LAN Emulation Services Figure 9-12 Flowchart for Checking Secondary LAN Emulation Services A Start B Is secondary LEC configuration "Operational" and "Current" on both LECs? Yes OK? Both secondary LECs have joined the secondary ELAN. Check that ping works.
Troubleshooting Troubleshooting Secondary LAN Emulation Services This troubleshooting procedure covers the following case: the Primary LAN Emulation Services have failed, the configured Secondary LAN Emulation Services have failed to take over, and the source system is unable to communicate with the destination. You should have already checked the Primary LEC, as described in “Checking the Status and Configuration of Both Systems” on page 228, before you troubleshoot the secondary LAN Emulation Services.
Troubleshooting Troubleshooting Secondary LAN Emulation Services LEC LEC LEC LEC LEC LEC LEC LEC LEC LEC LEC LEC B Initial Control Timeout : 10s Control Timeout Multiplier : 5s V2 Max Unknown Frame Count : 3 Config Local Segment ID : 345 Config V2 Capable : LUNI (LANE V2) Config Selective Multicast : True Forward Disconnect Timeout : 300s Min Reconfigure Delay : 1000s Max Reconfigure Delay : 2000s Max Bus Connect Retries : 2 Token Ring Explorer Frame Excluded : exclude Preferred LES Addr : 47000580ffe1000
Troubleshooting Troubleshooting Secondary LAN Emulation Services NOTE If you configured a secondary LES/BUS pair only—that is, only one LECS and two LES/BUS pairs—the primary LECS must be the same as the secondary LECS ATM address. Although the ATM software allows you to configure only one LECS, this is not recommended, because a failure of the LECS will prevent operation of the part of your ATM network that relies on the LECS.
Troubleshooting Troubleshooting MPOA Troubleshooting MPOA To help clarify this troubleshooting section, we have used the simple MPOA setup shown in Figure 9-13 below. Most command outputs shown in this section were gathered on these systems and somewhat filtered to show only the relevant information.
Troubleshooting Troubleshooting MPOA • host51: One LAN Emulation interface. — ELAN: mpoalan2 — ELAN interface: el200 — IP address: 25.61.185.51 — LEC selector: 0x25 — MPC selector: 0x26 • host178: One LAN Emulation interface. — ELAN: mpoalan3 — ELAN interface: el301 — IP address: 35.61.185.178 — LEC selector: 0x35 — MPC selector: 0x36 • router22: Two LAN Emulation interfaces. — First LAN Emulation interface: — ELAN: mpoalan2 — IP address: 25.61.185.
Troubleshooting Troubleshooting MPOA The flowchart for troubleshooting MPOA is shown in Figure 9-14 below. Each of the circled letters is described on the pages after the flowchart.
Troubleshooting Troubleshooting MPOA Figure 9-14 Flowchart for Troubleshooting MPOA Start A Run ping from local MPOA-capable LEC to any target on local ELAN. No Troubleshoot your LAN Emulation (see the section earlier in this chapter). OK? Yes B Run ping from local MPOA-capable LEC to the “real” MPOA destination. C No OK? D Troubleshoot the routing configuration. Yes Yes Run atmmgr to check the MPOA VCs. Changes made? Yes E No MPOA is correctly set up. OK? No Contact HP.
Troubleshooting Troubleshooting MPOA IMPORTANT HP’s implementation of ATM does not support MPOA for Token Ring networks. This is because of a lack of MPOA Server (MPS) support for Token Ring in routers. Also, HP’s implementation does not support MPOA for secondary LANs. To use the MPOA feature, you should first make sure that all of the components of your ATM network that are involved in establishing the MPOA shortcuts are MPOA-capable and have had their MPOA capability configured and turned on.
Troubleshooting Troubleshooting MPOA Start. Before you start this flowchart, do the following: Step 1. If practical, kill all other traffic running through both the local and destination systems’ adapters before you begin. Step 2. Gather all the necessary routing information of your network. A Check the ELAN interface status. MPOA uses the services of LAN Emulation (LANE) Version 2.
Troubleshooting Troubleshooting MPOA You can use the command netstat -rn to display the configured routes on the local system. Shown below is the ouput of this command on host51: host51:> netstat -rn Routing tables Dest/Netmask 127.0.0.1 15.61.185.51 25.61.185.51 25.61.185.0 15.61.184.0 35.61.185.0 127.0.0.0 default Gateway 127.0.0.1 15.61.185.51 25.61.185.51 25.61.185.51 15.61.185.51 25.61.185.22 127.0.0.1 15.61.185.
Troubleshooting Troubleshooting MPOA determine which are MPOA-specific VCs.
Troubleshooting Troubleshooting MPOA host51:/> atmmgr 0 show ATM/AAL vc information table VPI,VCI PMP Type Use SEL Dest.
Troubleshooting Troubleshooting MPOA Source ATM SEL AAL Dest.ATM Address Traffic Type Peak Rate Status : : : : : : 25 5 47000580ffe1000000f21c4c21.0000ef03a864.01 UBR 149.76 UP Shown below are the two control LLC LEC, MPC VCs established between the MPC on the ATM host and the MPS on the router. You can identify the ATM host’s MPC selector (0x26), the router’s ATM address (47000580ffe1000000f21c4c21.0000ef03a864), and the router’s MPS selector (0x92), which is shown at the end of the ATM address.
Troubleshooting Troubleshooting MPOA Peak Rate Status : 0.00 : UP Shown below is the shortcut LLC LEC, MPC VC established between the ATM host’s MPC and the MPC on the remote MPOA-capable destination system (or the edge device used to reach a legacy-LAN destination system). You can identify the ATM host’s MPC selector (0x26), the destination system’s ATM address (47000580ffe1000000f21c4bea.0060b06e747a), and the destination system’s MPC selector (0x36), which is shown at the end of the ATM address.
Troubleshooting Troubleshooting MPOA E Check for MPS discovery. Use the command mpcarp to see whether the local gateway/router (whose IP address you used when you issued the route command [see “B” on page 255]) has been recognized as an MPOA-capable device (an MPS) by the local ATM host. Shown below is part of the output of the mpcarp command issued on host51 in our example.
Troubleshooting Troubleshooting MPOA If the destination is a LAN-legacy system located behind an MPOA-capable edge device, consult the edge device’s documentation to check its MPOA configuration. If you think all the devices along the data path have been properly configured and the MPOA feature is still not working, contact HP. G Check for the MPC-MPS VC’s existence. Ensure that the VC from the local ATM host’s MPC to the destination’s MPS exists.
Troubleshooting Troubleshooting MPOA Primary MPOA Client statistics MPOA - Tx Resolve Requests Imposition Reply Acks Imposition Reply Insuf EC Resources Imposition Reply Insuf SC Resources Imposition Reply Insuf SC/EC Resources Imposition Reply Unsupported Inet Prot Imposition Reply Unsupported MAC Encaps Imposition Reply Unspecified/Other Egress Cache Purge Requests Data Plane Purges : : : : : : : : : : 1000 1000 5 7 50 2 5 9 500 500 MPOA - Rx Resolve Reply Acks Resolve Reply Insuf EC Resources Resolve
Troubleshooting Troubleshooting MPOA MPC Egress Cache Table for LEC interface el200: Egress Cache Table for Primary LEC: MPS MAC (MPS Router) Address IPV4 Address Ingress MPC Address ------------ ------------ -----------------------------------------0000ef03a860 25.61.185.178 47000580ffe1000000f21c4bea.0060b06e747a.36 J Check the MPOA devices.
Troubleshooting Troubleshooting EMS HA over ATM Troubleshooting EMS HA over ATM The flowchart for troubleshooting EMS High Availability over ATM is shown in Figure 9-15 below. Each of the circled letters is described on the pages after the flowchart.
Troubleshooting Troubleshooting EMS HA over ATM Figure 9-15 Flowchart for Troubleshooting EMS HA-ATM Start A Does the message "Configuration OK" appear in the EMS HA-ATM log files? Monitoring unable to start due to incorrect configuration. Ensure that the HA configuration is correct. Check that the ELAN status is "Operational" by using the elstat command.
Troubleshooting Troubleshooting EMS HA over ATM NOTE EMS High Availability over ATM (EMS HA-ATM) is managed by the EMS HA-ATM functionality incorporated into the core ATM software running on the HP ATM adapter. EMS HA-ATM handles local recovery within a system. MC/ServiceGuard handles remote recovery from one system to another, when EMS HA-ATM notifies EMS that local recovery is no longer possible. This section covers only troubleshooting of local recovery managed by EMS HA-ATM.
Troubleshooting Troubleshooting EMS HA over ATM Table 9-3 Events in the EMS HA Log File (Continued) Event Event numbe r The Current ELAN interface status has changed to DOWN. Waiting num_of_seconds for recovery of the ELAN interface. 314 The Current ATM adapter status has changed to DOWN. Waiting num_of_seconds for recovery of the ELAN interface. 315 An ELAN interface status has changed to UP. 316 An ATM adapter status has changed to UP. 317 An ELAN interface has changed to DOWN.
Troubleshooting Troubleshooting EMS HA over ATM Status : UP State : Backup Configuration is OK. ------------------------ EVENT #1 ----------------------30:09:1997:17:57:54:327 302 : Stopping the monitoring by EMS HA-ATM On Primary LEC interface : ela1 Example for 11.X: ------------------------ EVENT #0 ----------------------30:09:1997:17:57:10:939 301 : Starting the monitoring by EMS HA-ATM Primary interface : el100 Primary IP address : 25.128.24.
Troubleshooting Troubleshooting EMS HA over ATM If you configured a local recovery delay period for a primary ELAN interface (see “Local Recovery” on page 93), the message INTERFACE_FAILURE_DELAY set in monitor options file is written to the log file. Example for HP-UX 10.20: ------------------------ EVENT #1 ----------------------20:09:1998:22:49:19:986 313 : INTERFACE_FAILURE_DELAY set in monitor options file. ELAN interface: ela0 Switchover for the ELAN interface will be delayed for 20 seconds.
Troubleshooting Troubleshooting EMS HA over ATM Current ELAN interface is DOWN Local recovery made An ATM adapter has changed to DOWN 305 307 319 For both the 318 and 305 messages—concerning an ELAN interface failure—the ATM adapter number is included in the message. If a corresponding adapter failure message is not logged, that means the LAN Emulation Services have failed (see “Troubleshooting LAN Emulation” on page 226).
Troubleshooting Troubleshooting EMS HA over ATM If an ATM adapter fails, all of the IP addresses for ELAN interfaces configured on that ATM adapter must be transferred locally to secondary ELAN interfaces on a secondary ATM adapter (see Figure 9-16 below).
Troubleshooting Troubleshooting EMS HA over ATM Example for HP-UX 10.20: 03:02:1997:13:57:18:294 308 : Local recovery not possible Primary interface : ela0 Primary IP address : 200.128.169.5 Status : DOWN State : Backup Secondary interface : elc0 Status : DOWN State : Current Example for HP-UX 11.
Troubleshooting Troubleshooting EMS HA over ATM interface status has changed to DOWN and The Current ATM adapter status has changed to DOWN. The messages also tell you how long the delay will be before local recovery is started. Example for HP-UX 10.20: ------------------------ EVENT #2 ----------------------20:09:1998:22:49:19:986 314 : The current ELAN interface status has changed to DOWN. ELAN interface: ela0 Waiting 20 seconds for recovery of the ELAN interface.
Troubleshooting Troubleshooting EMS HA over ATM The reason separate messages exist for ELAN interface failure and ATM adapter failure is because the detection and logging of ELAN interface status changes and ATM adapter status changes are separate events. Either event causes hatmmon to enter the delay period; the delay period’s timer starts when the first of these events occurs.
Troubleshooting Troubleshooting EMS HA over ATM C Checking a current ELAN interface failure. If the message Current ELAN interface is DOWN is present in the log file for one or more ELAN interfaces, but the message Current ATM adapter is DOWN is not present, this means that the current ATM adapter is operational but the current ELAN interface has failed. ELAN interface failure occurs when contact is lost with the primary and secondary LAN Emulation Services (LECS, LES, and BUS).
Troubleshooting Troubleshooting EMS HA over ATM Example for HP-UX 11.X: ------------------------ EVENT #4 ----------------------20:09:1998:22:49:19:986 320 : The current ELAN interface or ATM adapter has recovered from a failure. ELAN interface: el100 is UP. ATM adapter: atm0 is UP. Usually, when the current ATM adapter and its ELAN interface become operational, these two messages are logged: ATM adapter has changed to UP and ELAN interface has changed to UP.
Troubleshooting Troubleshooting EMS HA over ATM If all adapters and interfaces went down—and so local recovery was not possible—but the primary ELAN interface later becomes up, you might see these messages logged: Current ELAN interface status has changed to UP An ATM adapter status has changed to UP 309 317 or Current ATM adapter status has changed to UP An ELAN interface status has changed to UP 310 316 The word “Current” is used in the above messages because the primary ELAN interface is the current
Troubleshooting Troubleshooting EMS HA over ATM If the Recovery Delay Period is Configured If you configured a local recovery delay period for a primary ELAN interface (see “Local Recovery” on page 93), and the interface fails, one or both of these messages are written to the log file at the beginning of the delay period: The Current ELAN interface status has changed to DOWN and The Current ATM adapter status has changed to DOWN.
Troubleshooting Troubleshooting EMS HA over ATM Example for HP-UX 11.X: ------------------------ EVENT #22 ----------------------20:09:1998:22:49:19:986 314 : The current ELAN interface status has changed to DOWN. ELAN interface: el100 Waiting 20 seconds for recovery of the ELAN interface. ------------------------ EVENT #23 ----------------------20:09:1998:22:49:36:294 315 : The current ATM adapter status has changed to DOWN. ATM adapter name: atm0 Waiting 20 seconds for recovery of the ELAN interface.
Troubleshooting Contacting Your HP Representative Contacting Your HP Representative If you have a service contract with HP, document the problem as a Service Request (SR) and forward it to your HP representative. Include the following information where applicable. If you do not have a service contract with HP, you can provide the information described below, but you will be billed accordingly for time and materials. • A description of the problem, including the events and symptoms leading to the problem.
Troubleshooting Contacting Your HP Representative • A description of any solution or workaround that you have found. Comparing the situation in which a problem occurs and does not occur can often help locate the cause. • Copies of any trace files that were active when the problem occurred. • Copies of log files that were active when the problem occurred. • In the event of a system failure, a full memory dump (check the directory /var/adm/crash). • Copies of these files: — /etc/hosts — /etc/rc.
Troubleshooting Contacting Your HP Representative • Output from this command: ps -ef Chapter 9 • Output from the commands ioscan and lanscan. • Which troubleshooting flowchart you are using, and the step where you are unable to resolve the problem.
Troubleshooting Contacting Your HP Representative 284 Chapter 9
10 Logging and Tracing ATM Activity This chapter contains the following sections that describe logging and tracing ATM activity: Chapter 10 285
Logging and Tracing ATM Activity 286 • “Overview” on page 287. • “Before You Start Logging and Tracing” on page 288. • “Logging” on page 290. • “Tracing” on page 292. • “Viewing Log and Trace Files” on page 295. • “More Information about Tracing” on page 302.
Logging and Tracing ATM Activity Overview Overview NetTL is a standard HP-UX troubleshooting tool. It is used to trace both data and signalling traffic passing through the ATM adapter, and to log significant ATM events. The NetFmt facility allows you to filter out messages you are not interested in and format the information produced by NetTL. The default logging settings record unusual or exceptional events such as errors, warnings, and state transitions.
Logging and Tracing ATM Activity Before You Start Logging and Tracing Before You Start Logging and Tracing NetTL daemons receive data from the network subsystems, format it, and write it to trace and log files that contain messages for all network subsystems running on the machine. The NetTL daemon must be running before you can use tracing or logging. The value of the NETTL in the file /etc/rc.config.d/nettl determines if the NetTL daemon is started at system start-up.
Logging and Tracing ATM Activity Before You Start Logging and Tracing NS_LS_DRIVER NS_LS_RLBD NS_LS_BUFS NS_LS_CASE21 NS_LS_ROUTER21 NS_LS_NFS NS_LS_NETISR NS_LS_X25 NS_LS_NSE NS_LS_STRLOG NS_LS_TIRDWR NS_LS_TIMOD NS_LS_COUNT FILTER NAME ATM FORMATTER ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR DISASTER DISASTER DISASTER DISASTER DISASTER DISASTER DISASTER DISASTER DISASTER DISASTER DISASTER DISASTER DISASTER DISASTER DISASTER DISASTER DISASTER Tr
Logging and Tracing ATM Activity Logging Logging The following sections describe how to do the following things: • Start logging. • Specify the type of information you want to log. • Stop logging. The ATM software logs messages that record unusual or exceptional events such as errors, warnings, and driver state transitions. It also captures ATM network activities such as connection establishment, and ILMI events.
Logging and Tracing ATM Activity Logging The default log file is specified in /etc/nettlgen.conf. You can change the default log files by editing the /etc/nettlgen.conf file. Logging Options To modify the default logging options, use the nettl command with the -log and -entity parameters, as follows: nettl -log disaster error warning informative -entity atm This command causes ATM disaster, error, warning, and informative messages to be logged.
Logging and Tracing ATM Activity Tracing Tracing The following sections describe how to do the following: • Start tracing the packet information you want to trace. • Verify the status of tracing. • Stop tracing. NetTL must be running and must have been configured correctly for ATM before the tracing can start (refer to the nettl(1)man page for more information about NetTL). NOTE Trace data can rapidly occupy large amounts of disk space.
Logging and Tracing ATM Activity Tracing NOTE When tracing begins, two additional nettl daemons begin execution. If you issue a ps command, you will see four processes: two shown as ntl_reader and two shown as nktl_daemon. One pair of nettl daemons is dedicated to network logging and one pair is concerned with tracing. There is also a netfmt process running, to send disaster log messages to the system console. Verifying Status Use the command nettl -ss to verify the status of the tracing.
Logging and Tracing ATM Activity Tracing Stopping Tracing To stop tracing, use this command: nettl -traceoff -entity atm 294 Chapter 10
Logging and Tracing ATM Activity Viewing Log and Trace Files Viewing Log and Trace Files The following sections describe how NetFmt is used to format, filter and view trace and log data. For more information about netfmt, see the command man pages. Viewing Log Files The netfmt command is used to view log data by manipulating it into a readable format. For example, the command netfmt -N -l -f /usr/adm/nettl.LOG00 -t 50 formats the last 50 records in the file /usr/adm/nettl.LOG00.
Logging and Tracing ATM Activity Viewing Log and Trace Files Viewing Trace Files The netfmt command is also used to view trace data. ATM traces can be filtered by packet type, VPI, VCI, and signalling call references. The ATM filter commands can be included in a global filter configuration file or can be in an ATM-specific filter configuration file. NetFmt reads the filter commands from the filter configuration file specified with the -c option.
Logging and Tracing ATM Activity Viewing Log and Trace Files where dev is the card instance number of the ATM adapter. User Filter Options The user filter options are used to include or exclude trace records for users at specific ATM levels such as AAL (data transfer), ILMI, IP, ARP, and signalling Protocol Data Units (PDUs). For AAL and ILMI PDUs For AAL and ILMI PDUs, the syntax is as follows: atm user_aal status atm user_ilmi status where status is one of the following: • * to display the PDUs.
Logging and Tracing ATM Activity Viewing Log and Trace Files • !* for no display. • !Qsaal or !Q93b to not display QSAAL or Q93b, respectively. Use QSAAL for signalling PDUs without Q93b information. Use Q93b for signalling PDUs encapsulating Q93b information. VC Filter Options Circuit filter options are used to include or exclude trace records of circuit traffic filtered for VPIs and VCIs. Filtering on the VPIs and VCIs is specified as follows: atm VPI argument [argument] ...
Logging and Tracing ATM Activity Viewing Log and Trace Files • A range (for example, 100-200). Up to 10 arguments can be specified. Call reference filtering is active for only signalling packets. LAN Emulation LEC_ID Filter Options For filtering on LAN Emulation LEC_ID ranges, the syntax is as follows: atm LecId argument [argument] ... where argument is one of the following: • * for all. • !* for none. • A numeric value (for example, 128). • A range (for example, 100-200).
Logging and Tracing ATM Activity Viewing Log and Trace Files (see “For IP and ARP PDUs” on page 297 for a description of the options for IP and ARP PDUs).
Logging and Tracing ATM Activity Viewing Log and Trace Files atm VCI 0-32 128 # Filtering users : aal (data PDUs) atm user_aal !* # No data PDUs are displayed # Filtering users : ILMI (SNMP PDUs) atm user_ilmi * # ILMI PDUs are displayed # Filtering users : Classical IP / ATM_ARP atm user_iparp IP # IP PDUs are displayed atm user_iparp !ARP # No ARP PDUs displayed # Filtering users : Lan Emulation atm user_lanemul CTRL# Control frames are displayed atm user_lanemul !DATA # No data frames displayed (IP and A
Logging and Tracing ATM Activity More Information about Tracing More Information about Tracing Some other information you might find useful when you are using tracing is given below. Protocol Information The following protocol information is traced for data packets: • AAL5 PDU ATM header. Only the VPI and VCI are supported (there is no tracing by cell, so no other ATM header fields are captured). • LLC (Type I) header. • SNAP header.
Logging and Tracing ATM Activity More Information about Tracing Decoding and Formatting Incorrectly Formatted IEs If an IE does not contain the required number of mandatory fields, or is incorrectly encoded so that the IE cannot be properly decoded, an error message is displayed indicating the bad IE and decoding for the IE is aborted. The IE is displayed in hexadecimal. The remainder of the packet is formatted normally.
Logging and Tracing ATM Activity More Information about Tracing 304 Chapter 10
11 Replacing a Defective Adapter This chapter contains the following sections that describe how to replace a bad ATM adapter: • Chapter 11 “General Information” on page 307.
Replacing a Defective Adapter NOTE 306 • “Replacing an ATM ARP Client Adapter” on page 308. • “Replacing an ATM ARP Server Adapter” on page 309. • “Changing an Adapter’s MAC Address” on page 310. • “Replacing a LAN Emulation LEC Adapter” on page 312. If you are replacing a defective adapter with a different type of adapter, see Chapter 8, “Migrating from the J2803B or J2498A ATM Adapters,” on page 169.
Replacing a Defective Adapter General Information General Information The ATM address of an HP ATM adapter is generated by using the hard-coded MAC address of the adapter as the End System Identifier. If you have to change an adapter, this can have consequences for the configuration of the rest of the ATM adapters on the Logical IP Subnet (LIS). NOTE You do not need to save any information before replacing a defective adapter.
Replacing a Defective Adapter Replacing an ATM ARP Client Adapter Replacing an ATM ARP Client Adapter If an HP ATM adapter used as an ATM ARP Client needs to be replaced, you can just remove the old adapter and replace it with a new one. See the relevant installation guide (listed in “Related General Information” on page xviii). To replace an ATM ARP Client adapter, follow these steps: Step 1. Shut down and turn off the system, and disconnect it from the telecommunications network and electricity supply.
Replacing a Defective Adapter Replacing an ATM ARP Server Adapter Replacing an ATM ARP Server Adapter If you need to replace a defective ATM adapter, and the adapter is configured as an ATM ARP Server, you might want the replacement adapter to use the same MAC address as the defective adapter. This will avoid your having to reconfigure the ATM ARP Server ATM address on every ATM ARP Client on the same subnet.
Replacing a Defective Adapter Changing an Adapter’s MAC Address Changing an Adapter’s MAC Address Changing the MAC address disrupts any connections currently using the ATM adapter and can also cause temporary confusion on the network. All nodes auto-recover once the new MAC address is registered. So, if problems occur on the ATM network at the same time as the adapter is being replaced, complete the replacement procedure before trying to troubleshoot.
Replacing a Defective Adapter Changing an Adapter’s MAC Address • new_address is the MAC address of the ATM adapter that you are replacing. For example, the command atmmgr 1 macaddr -A 080009C6FC90 specifies a MAC address of 080009C6FC90 for the ATM adapter 1. For more information about the command atmmgr macaddr, see the atmmgr(1) man page.
Replacing a Defective Adapter Replacing a LAN Emulation LEC Adapter Replacing a LAN Emulation LEC Adapter Changing the adapter’s hardware MAC address has no effect on the LAN Emulation configuration. So, you do not need to perform any reconfiguration if you replace an ATM adapter on which ELAN interfaces are configured. The MAC address is not updated dynamically in the configuration files for each ELAN interface, so the previous MAC address continues to be used.
12 Supported Standards This chapter contains these sections that provide information about the standards supported by the HP-HSC and HP-PCI ATM adapters: • Chapter 12 “UNI Versions” on page 315.
Supported Standards 314 • “LAN Emulation” on page 317. • “MPOA” on page 318. • “Internet RFCs” on page 319. • “Switch Requirements” on page 322. • “Router Requirements” on page 323.
Supported Standards UNI Versions UNI Versions The ATM adapter complies with UNI 3.0, 3.1, and 4.0, and with the user part of the specifications. Physical Layer Standards (SONET and SDH) The transmission convergence sub-layer of the ATM adapter’s physical layer can be set to either SONET or SDH. The implementations conform to the following standards: • SONET STS-3 (ANSI T1E1.2/94-002R1). • SDH STM-1 (ITU recommendation G.707, 708, 709, and I.432).
Supported Standards UNI Versions 4 bits for VPI, 8 bits for VCI — A5513A and A5515A: 11 bits, of which up to 8 bits can be used for VPI range. Examples 0 bits for VPI, 11 bits for VCI 4 bits for VPI, 7 bits for VCI • The ATM adapter transmits only cells with the following payload types: — 000 for user cells. — 101 for F5 OAM flows. • The ATM adapter has the following pre-defined VPI/VCI values: — 0-16 for ILMI traffic, unless the value is modified. — 0-05 for the signalling protocol.
Supported Standards LAN Emulation LAN Emulation The LAN Emulation compliances are as follows: Chapter 12 • For non-MPOA and non-LLC multiplexing usage, the LEC of the ATM stack complies with LAN Emulation over ATM Version 1.0 from the ATM Forum. • For MPOA and/or LLC multiplexing usage, the LEC of the ATM stack complies with LAN Emulation over ATM Version 2.0 LUNI from the ATM Forum.
Supported Standards MPOA MPOA The MPOA functionality compliances are as follows: 318 • Multi-Protocol Over ATM Version 1.0. • Multiprotocol Over ATM Version 1.0 MIB.
Supported Standards Internet RFCs Internet RFCs The internet-related RFCs supported by the ATM adapters are listed below. RFC 1483 RFC 1483 defines two encapsulation methods for carrying network interconnect traffic over AAL5: • LLC type 1 encapsulation. • VC-based multiplexing. The HP ATM adapters support LLC encapsulation type 1 for IP traffic and VC-based multiplexing.
Supported Standards Internet RFCs SNMP Support The following RFCs are supported: • RFC 1155 SMI V1. • RFC 1157 SNMP V1 protocol. • RFC 1213 (MIB II). ILMI Support ILMI is an ATM Forum specification describing how to implement local management functions. It uses SNMP exchanges directly on top of AAL5 over a given VPI and VCI. Depending on the UNI version, ILMI functions are defined in dedicated MIBs specified, respectively, in UNI 3.0, UNI 3.1, and ILMI 4.0. Implementation, Section 4 of UNI 3.0 and 3.
Supported Standards Internet RFCs Address Registration Support The only functionality based on ILMI on the user-side UME is the address registration facility. This means that no proprietary extensions are defined. The address registration procedures as specified in UNI 3.0/3.1 section 5.8, and ILMI 4.0 section 9 are supported, with the following implementation-specific choices: NOTE Chapter 12 • Only private ATM address formats are supported. • Only User Side UME is supported (refer to UNI 3.0/3.
Supported Standards Switch Requirements Switch Requirements The requirements for switches connected to ATM adapters are as follows: 322 • The switch to which the ATM adapter is connected must support the network part of the UNI 3.0, 3.1, or 4.0 specifications, including physical layer, ATM layer, MMF, SMF, or UTP Cat 5, and signalling and ILMI protocols. • The switch must support the 155 Mbits/s or 622 Mbits/s interface defined by the ATM Forum UNI 3.0, 3.1, or 4.0.
Supported Standards Router Requirements Router Requirements To connect legacy equipment, the HP ATM software supports routers that implement the following: Chapter 12 • PVC configuration or the UNI 3.0, 3.1, or 4.0 specifications for SVC establishment. • RFC 1483 with LLC type 1 encapsulation. • RFC 1577 for SVC handling. • RFC 1755.
Supported Standards Router Requirements 324 Chapter 12
13 Cables and Connectors This chapter contains the following sections that discuss the cables and connectors used with the ATM adapters: • Chapter 13 “Cable Recommendations” on page 327.
Cables and Connectors • 326 “UTP Cat 5 Cable and Connector Pinouts” on page 328.
Cables and Connectors Cable Recommendations Cable Recommendations Table 13-1 below show the cables we recommend you use with HP ATM adapters: Table 13-1 Recommended Adapter Cables Product Description SC to SC cable Cable Suppliers Include AMP, Amphenol Socapex, 3M SC to ST cable (duplex adapter) SC loopback connector UTP Cat 5 direct cable (1.5 m) HP, INMAC, BLACK BOX, AMP UTP Cat 5 direct cable (3.0 m) UTP Cat 5 direct cable (7.
Cables and Connectors UTP Cat 5 Cable and Connector Pinouts UTP Cat 5 Cable and Connector Pinouts The pinouts of the different UTP Cat 5 cables and connectors are shown in the subsections below. Direct-Connect Cable The pinout of the direct-connect cable is shown in Figure 13-1 below.
Cables and Connectors UTP Cat 5 Cable and Connector Pinouts Crossover Cable The pinout of the crossover cable is shown in Figure 13-2 below. Figure 13-2 Pinout of the Crossover Cable ATM user device (HP ATM adapter) ATM user device (HP ATM adapter) 1 Tx+ 1 Tx+ 2 Tx- 2 Tx- 3 3 4 4 5 5 6 6 7 Rx+ 7 Rx+ 8 Rx- 8 Rx- Loopback Connector The pinout of the loopback connector is shown in Figure 13-3 below.
Cables and Connectors UTP Cat 5 Cable and Connector Pinouts 330 Chapter 13
Glossary A AAL ATM Adaptation Layer. The AAL translates digital voice, image, video, and data signals into the ATM cell format, and vice versa. There are five AALs defined (AAL1 through AAL5) that provide different services. For example, AAL5 supports connection-oriented variable bit rate data services. ABR Available Bit Rate. An ATM traffic type that optimizes the transmission resources available during data transmission.
Glossary CPE CPE Customer Premises Equipment. Equipment owned by a customer, which is used to terminate or process information from public networks (for example, a T1 multiplexer or a PBX). associated with an MC/ServiceGuard package. It can move from one cluster node to another. A single package can have several floating IP addresses. H D default route The hop-to-hop route between routers that packets would take if no shortcut route exists.
Glossary LLC multiplexing maximum packet size varies from network to network, but is usually a few thousand octets. A typical size is 1536 octets. means to have a control relationship with that ELAN’s LES. Each LES is identified by a unique ATM address. IP address Internet Protocol address. An identifier for a network node expressed as four fields separated by decimal points (for example, 136.19.0.5.). An IP address is site-dependent and assigned by a network administrator. LIS Logical IP Subnet.
Glossary MMF M MMF Multi-Mode fibre. A wide-core fibre-optic cable that allows transmission of data in the form of many light beams. Multi-Mode fibre is normally used with an LED light source. MPC MPOA Client. A logical component of MPOA; it implements the client side of the MPOA protocol. An MPC resides on a LEC that is an edge device or an MPOA host. MPC cache The VCC information stored by an MPC. The MPC reuses the information for address resolution for shortcut routes.
Glossary unshielded twisted pair PVC Permanent Virtual Circuit. A channel through a network provided by a carrier between two end points for dedicated long-term information transfer between two locations. Contrast with SVC. duration of the transfer. It is the data communications equivalent of a dialed phone call. S threshold Within MPOA, the maximum number of packets that can be forwarded over the default route to a specific address during a fixed amount of time.
Glossary UTP Cat 5 UTP Cat 5 A standard that specifies how an unshielded twisted pair cable should be installed to ensure a specific quality of signal. V router’s performance is not limited by hop-to-hop routing like a traditional routed network often is. VPI Virtual Path Identifier. The field in the ATM cell header that labels (identifies) a particular virtual path. VBR Variable Bit Rate. An ATM traffic type that is equivalent to guaranteed traffic type.
Index A AAL interface, displaying statistics, 151 supported, 316 ABR configuring, 76 configuring on SVCs, 70 UNI version for ABR on SVCs, 21 active virtual circuits, displaying information, 143 adding PVCs, 76 address registration, for UNI 3.0/3.
Index pinouts, UTP Cat 5, 328 SC loopback, 327 SC to SC, 327 SC to ST, 327 UTP Cat 5, 327 cabling, back-to-back, 87 cache LE ARP, displaying, 144 MPC Egress, displaying, 160 MPC Ingress, displaying, 160 calling HP, 281 card instance number, displaying, 165 carrier LED, 193 categories of logging messages, 290 CBR, configuring, 76 changing a MAC address, 310 checking connections for SVCs and PVCs, 148 status of nettl, 288 status, end-to-end connectivity, 180 Classical IP ARP table, displaying, 154 configuring
Index statistics, 158 status, 158 traffic parameter configurations, 153 version of UNI configured, 151 documentation, related to product, xviii E edge device configuration for Token Ring, 55 in MPOA, 46 elarp -n, 157 elstat -n net_interface -v, 155 EMS HA, 91 local recovery, 91 starting the monitor, 124 stopping the monitor, 129 with MC/ServiceGuard, 92 end system configuration, troubleshooting, 201 end-to-end connectivity, checking status, 180 error messages, 290 errors, bind, displaying, 147 Ethernet, LA
Index starting, 290 stopping, 291 viewing files, 295 logical IP subnet, 26 loopback connector, pinout, 329 test, 194 M MAC address changing, 310 displaying, 143, 152 locating, 310 matrix for PVCs, 78 PVCs, for ATM switch, 79 MC/ServiceGuard, 92 migrating from versions before A.10.
Index monitoring, 163, 164 tracing, 292 P packets incoming, 292 outgoing, tracing, 292 performance, monitoring, 143 physical layer standards, 315 pinout crossover cable, 329 loopback connector, 329 PVCs adding, 76 automatic reconfiguration, 85 checking configuration, 204 checking connections for, 148 configuring, 76 matrix for configuring, 78 modifying, 82 removing, 84 sample configuration, 78 troubleshooting, 196 R reconfiguration, automatic, for PVCs, 85 reinstalling the product, 193 related product infor
Index switch configuration, 194 configuration, troubleshooting, 201 requirements, 322 T TCP/IP, 319 supported standards, 319 Token Ring configuring edge device, 55 LAN Emulation, 39 topology back-to-back, 86 logical IP subnet, 29 tracing checking status, 293 file naming mechanism, 292 specifying a file name, 292 specifying an entity for, 292 specifying output file, 292 starting, 292 stopping, 294 traffic configuration limitations, 64 configurations in use, 153 displaying parameter configuration, 143 monitor
