HP HP-PB 10 User Manual

Download

Using HP-PB 10/100Base-TX/9000

HP 9000 Networking

Manufacturing Part Number: J2760-90017

E0699

U.S.A.

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 ﬁtness 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.

Warranty. A copy of the speciﬁc warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtained from your local Sales and Service Ofﬁce.

Restricted Rights Legend. Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 for other agencies.

HEWLETT-PACKARD COMPANY 3000 Hanover Street Palo Alto, California 94304 U.S.A.

Use of this manual and ﬂexible disk(s) or tape cartridge(s) supplied for this pack is restricted to this product only. Additional copies of the programs may be made for security and back-up purposes only. Resale of the programs in their present form or with alterations, is expressly prohibited.

Reproduction, adaptation, or translation of this document without prior written permission is prohibited, except as allowed under the copyright laws.

This software is based in part on the Fourth Berkeley Software Distribution under license from the Regents of the University of

©copyright 1986-1992 Sun Microsystems, Inc. ©copyright 1985-86, 1988 Massachusetts Institute of Technology. ©copyright 1989-93 The Open Software Foundation, Inc. ©copyright 1986 Digital Equipment Corporation. ©copyright 1990 Motorola, Inc. ©copyright 1990, 1991, 1992 Cornell University ©copyright 1989-1991 The University of Maryland ©copyright 1988 Carnegie Mellon University

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.

OSF/Motif is a trademark of the Open Software Foundation, Inc. in the U.S. and other countries.

Contents

1. Installing and Conﬁguring 10/100Base-TX/9000

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Required and Optional Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Compatibility and Installation Requirements. . . . . . . . . . . . . . . . . . . . .12

Manual Speed and Duplex Mode Conﬁguration. . . . . . . . . . . . . . . . . .13

Autonegotiation and Autosensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Known Problems and Workarounds. . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

What Manuals are Available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Software Availability in Native Languages. . . . . . . . . . . . . . . . . . . . . . .18

Overview of Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Step 1: Check the 10/100Base-TX Installation Prerequisites. . . . . . . . .20

Step 2: Loading 10/100Base-TX Software . . . . . . . . . . . . . . . . . . . . . . . .22

Step 3: Access the System Card Bay . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Step 4: Install the 10/100Base-TX Card. . . . . . . . . . . . . . . . . . . . . . . . . .25

Step 5: Attach the System to the Network. . . . . . . . . . . . . . . . . . . . . . . .26

Step 6: Conﬁgure the 10/100Base-TX Link . . . . . . . . . . . . . . . . . . . . . . .29

Step 7: Verifying the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

What Happens During Card Initialization Sequence? . . . . . . . . . . . . . .34

2. Conﬁguring Network Connectivity Using SAM

Step 1: Conﬁguring Network Connectivity . . . . . . . . . . . . . . . . . . . . . . .37

Step 2: Deleting a Default Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Contents

3. 100Base-TX Resources

HP-UX Manual Reference Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Logging Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Manual Installation and Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . 47

Contacting Your HP Representative . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

4. Troubleshooting 10/100Base-TX/9000

Troubleshooting Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Diagnostic Flowcharts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Flowchart 1: Network Level Loopback Test . . . . . . . . . . . . . . . . . . . . 58

Flowchart 2a: 10/100Base-TX Connections/LED Test . . . . . . . . . . . . 62

Flowchart 3: Conﬁguration Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Flowchart 4: Conﬁguration Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Flowchart 4 Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Flowchart 4A: Conﬁguration Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Flowchart 4A Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Flowchart 5: Conﬁguration Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Flowchart 5 Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Flowchart 6: Network Level Loopback Test . . . . . . . . . . . . . . . . . . . . 75

Flowchart Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Flowchart 7: Link Level Loopback Test. . . . . . . . . . . . . . . . . . . . . . . . 77

Flowchart 7 Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Flowchart 8: Transport Level Loopback Test (using ARPA). . . . . . . . 80

Flowchart 8: Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Flowchart 9: Bridge/Gateway Loopback Test . . . . . . . . . . . . . . . . . . . 82

Flowchart 9 Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Contents

A. 10/100Base-TX Interface Card Statistics

RFC 1213 MIB II. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

RFC 1284 Ethernet-Like Interface Statistics . . . . . . . . . . . . . . . . . . . . .91

Create a Record or Map of Your Internetwork. . . . . . . . . . . . . . . . . . . . .93

B. Hardware Reference Information

Basic Troubleshooting Tips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Meaning of LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

Connector Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

HP-PB 10/100Base-TX Card Twisted-Pair Connector . . . . . . . . . . . . .99

Connector Pin Usage for 10-Mbit/s Twisted-Pair Connector. . . . . . . .99

Connector Pin Usage for 100-Mbit/s Twisted-Pair Connector. . . . . .100

HP-PB 10/100Base-TX Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

C. Hardware Regulatory Statements

FCC Statement (For U.S.A.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

Canada . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

VCCI (Japan) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

EMI Statement (European Community) . . . . . . . . . . . . . . . . . . . . . . . .108

Contents

1 Installing and Conﬁguring

10/100Base-TX/9000

Installing and Conﬁguring 10/100Base-TX/9000

Introduction

The HP-PB 10/100Base-TX/9000 product provides the means for interfacing various types of HP 9000 Series 800 computers to either a 10Base-T or 100Base-TX network. Refer to the Release Notes for the list of supported systems.

100Base-TX is a subset of 100Base-T networking deﬁned by the IEEE

802.3u-1995 standard. 100Base-TX provides 100 Mbit/s data transmission over category 5 unshielded twisted-pair (UTP) cable. Two pairs of wires in the cable are used--one wire pair is for receiving data, and one wire pair is for transmitting data. The same card port that supports 100Base-TX operation can also support 10Base-T operation.

IEEE 802.3u 100Base-TX LANs have topologies very similar to 10Base-T LANs; however certain aspects of the topology such as the maximum permitted cable lengths are more stringent for 100Base-TX than for 10Base-T. The category 5 UTP cable used in 100Base-TX networks between devices such as an HP computer and a 100Base-TX hub must be less than 100 meters long.

Formore information on network topologies and associated speciﬁcations for 100Base-TX networking, refer to the IEEE 802.3u speciﬁcation. Also, a useful practical reference is Fast Ethernet, Dawn of a New Network by HowardW. Johnson (published 1996 by Prentice Hall PTR, Upper Saddle River, New Jersey 07458. Phone 800-382-3419. The ISBN number is 0-13-352643-7).

Announcements

There are no changes in the way the HP-PB 10/100Base-TX/9000 LAN card works for this release. As of June 1999, the product has a new product number: A3495A. This release supports the ability to change speed and duplex mode in the System Admin Manager (SAM). This release also provides upport for MTU size setting/resetting using

lanadmin -[m|M|R].

10 Chapter1

Installing and Conﬁguring 10/100Base-TX/9000

Required and Optional Patches

The following patches are required in order to use the HP-PB 10/100Base-TX/9000 card:

Server

• PHNE_17113—a patch for lanadmin changes on HP-UX 11.x

versions.

• PHNE_17000—a patch for lanadmin changes on HP-UX 10.20

versions.

• PHCO_17631—a SAM patch for HP-UX 11.0-Based servers.

• PHCO_17871—a SAM patch for HP-UX 10.20-Based servers. Workstation

• PHNE_17113—a patch for lanadmin changes on HP-UX 11.x

versions.

• PHNE_16999—a patch for lanadmin changes on HP-UX 10.20

versions.

• PHCO_17871—a patch for SAM to support HP-UX 10.20

workstation-Based versions of HP-PB 10/100Base-TX/9000.

The patch numbers listed above are current as of this release note. Please contact the Worldwide Enterprise Response Center if you need to ensure that you have the latest patches.

Chapter 1 11

Installing and Conﬁguring 10/100Base-TX/9000

Compatibility and Installation Requirements

Following are the compatibility requirements of the HP-PB 10/100Base-TX/9000:

• The HP-PB 10/100Base-TX/9000 card supports autonegotiation and autosensing. You should not normally need to manually conﬁgure the speed, autonegotiation, or duplex mode of the card. If your switch does not support autonegotiation but is set to full-duplex mode, there may be a mismatch between the card and the switch, because the card defaults to half-duplex for switches that do not support autonegotiation. You can determine what the card is set to using lanadmin -x and reset it if necessary using lanadmin -X. See “Manual Speed and Duplex Mode Conﬁguration” for details.

• Both full- and half-duplex modes are supported. Ensure that your hub or switch is set to the desired duplex mode.

• The HP-PB 10/100Base-TX/9000 LAN software is for use with only the following protocols: TCP/IP, UDP/IP, ARPA, NFS, and Advanced Server/9000.

12 Chapter1

Installing and Conﬁguring 10/100Base-TX/9000

Compatibility and Installation Requirements

Manual Speed and Duplex Mode Conﬁguration

Because the HP-PB 10/100Base-TX/9000 card supports autonegotiation, you should not normally need to manually set the duplex mode. Sometimes you may need to manually set the duplex mode of the card--for example, if the switch is operating at full duplex but does not autonegotiate. Because the card defaults to half-duplex when autonegotiation is turned off, this could cause a mismatch between the card and switch (at either 10 or100 Mbits/s). To ﬁx this, use the lanadmin -X command as described later in this section.

The CSMA/CD media access method used in IEEE 802.3u-1995 is inherently a half-duplex mechanism. That is, at any one time, there can be only one sender of data on the link segment. It is not possible for devices on either end of the link segment to transmit simultaneously.

Since Category 5 UTP contains multiple pairs of wires, it is possible to have devices on both ends of a link segment sending data to each other simultaneously. This is known as full-duplex operation. While the details of full-duplex operation are not currently deﬁned by IEEE 802.3u-1995 (full-duplex mode essentially involves “turning off” the CSMA/CD access method which is the foundation of IEEE 802.3), the autonegotiation mechanism deﬁned in IEEE 802.3u-1995 allows devices to advertise and conﬁgure themselves to operate in a full-duplex mode which is essentially vendor-speciﬁc. Devices that do not support autonegotiation can sometimes be manually conﬁgured to operate in full-duplex mode.

Full-duplex mode is most commonly found in, and indeed only makes sense for, switches rather than hubs. It may be found in either 10 Mbit/s or 100 Mbit/s switch devices. Full-duplex mode may provide a throughput advantage under some circumstances, the degree of the advantage is application-dependent.

The HP-PB 10/100Base-TX card supports both half and full-duplex operation.

Ensure that the speed, duplex mode, and autonegotiation of the associated switch are conﬁgure the same as on the HP-PB 10/100Base-TX card. If the switch supports autonegotiation on the ports connected to the cards, this should be enabled as explained in the section in this release note called “Autonegotiation and Autosensing.”

Chapter 1 13

Installing and Conﬁguring 10/100Base-TX/9000

Compatibility and Installation Requirements

To list the current speed and duplex mode of the HP-PB 10/100Base-TX/9000 card, use the -x option (NOTE: lowercase x) of the lanadmin command. Determine the speed and duplex mode of your hub or switch before performing manual conﬁguration as follows:

lanadmin -x lanadmin -x

To manually set the duplex mode of the interface, install one of the patches above and then use the -X option of lanadmin as follows:

lanadmin -X mode lanadmin -X mode

where :mode can be any one of the following strings (and the fd or hd are

case-insensitive):

10fd =10 full-duplex 10hd =10 half-duplex

100fd =100 full-duplex 100hd =100 half-duplex

and

lanadmin -X auto_on

and 11.0)

lanadmin -X auto_on

The

ppa

HP-UX 10.20, use the can get the

ppa

(HP-UX 10.30 or 11.0)

nmid

(HP-UX 10.20)

ppa

(on HP-UX 10.30 and 11.0)

nmid

(on HP-UX 10.20)

ppa

(turns autonegotiation on for HP-UX 10.30

nmid

(turns autonegotiation on for HP-UX 10.20)

is the physical point of attachment on HP-UX 10.30 or 11.0. On

nmid

or Network Management ID of the card. You

ppa (nmid

) from the output of the lanscan command. Example: If the

command to set the card to 10Mbits/s and full-duplex mode would be:

lanadmin -X 10fd 5

After issuing the lanadmin -X, you must wait at least 11 seconds before attempting to use the speciﬁed network interface. If you want the duplex mode setting to be effective in all subsequent reboots, you must enter the information in the following ﬁle:

/etc/rc.conﬁg.d/hpBasetconf

ppa (nmid

14 Chapter1

on HP-UX 10.20) of the 100Base-TX interface is 5, the

Installing and Conﬁguring 10/100Base-TX/9000

Compatibility and Installation Requirements

Manually conﬁguring the speed or duplex setting of a switch port on some switches may disable that switch port from doing autonegotiation. Verify that both the card and the switch port are operating in the same speed and duplex mode as desired.

If you use manual conﬁguration to change the card to a different speed and duplex mode, you may need to turn autonegotiation on ﬁrst before the manual setting takes place.

Mismatches between the speed, autonegotiation, or duplex mode of the card and switch will cause incorrect operation.

Speciﬁc items for each installed 10/100Base-TX interface card can be conﬁgured by creating an array of variables, where each array index corresponds to one interface card; refer to the existing contents of the hpBasetconf ﬁle for more detail. For each 10/100Base-TX interface card whose duplex mode is to be set, entries of the following form must be made in the hpBasetconf ﬁle:

HP_BaseT_INTERFACE_NAME[n]= HP_BaseT_SPEED[n]= [10HD 10FD 100HD 100FD auto_on]

NameUnit

determined from the output of the lanscan command. n is the array index which should start at 0 but which itself bears no relation to speciﬁc interfaces.

For example, if the name of the 10/100Base-TX interface to conﬁgure as shown by lanscan is lan3, and this is the only interface to be conﬁgured, the entries in the hpBasetconf ﬁle to “permanently” conﬁgure this interface to full duplex mode across system reboots would be:

HP_BaseT_INTERFACE_NAME[0]=lan3 HP_BaseT_SPEED[0]=[10FD 100FD auto_on]

If there were a second 10/100Base-TX interface with the name of lan4 on the system whose duplex mode were also to be “permanently” conﬁgured to full-duplex, the additional entries in the hpBasetconf ﬁle would be:

HP_BaseT_INTERFACE_NAME[1]=lan4 HP_BaseT_SPEED[1]=[10FD 100FD auto_on]

To determine the current duplex mode of the card, use the -x option of the lanadmin command as explained earlier.

is the name of the interface to be conﬁgured, which can be

NameUnit

Chapter 1 15

Installing and Conﬁguring 10/100Base-TX/9000

Compatibility and Installation Requirements

Autonegotiation and Autosensing

Autonegotiation is a mechanism deﬁned in the IEEE 802.3u speciﬁcation whereby devices sharing a link segment can exchange information and automatically conﬁgure themselves to operate at the highest capability mode shared between them.

Autonegotiation is like a rotary switch that automatically switches to the correct technology such as 10Base-T or 100Base-TX or between half- and full-duplex modes. Once the highest performance common mode is determined, auto-negotiation passes control of the link to the appropriate technology, sets the appropriate duplex mode, and then becomes transparent until the link is broken.

Following is the IEEE 802.3u-deﬁned hierarchy for resolving multiple common abilities for a 10/100Base-TX card. The HP-PB 10/100Base-TX/9000 product provides the means for interfacing various types of HP 9000 workstations to either a 10Base-T or 100Base-TX network. 100Base-TX is a subset of 100Base-T networking deﬁned by the IEEE 802.3u-1995 standard. 100Base-TX provides 100 Mbit/s data transmission over category 5 unshielded twisted-pair (UTP) cable. Two pairs of wires in the cable are used—one wire pair is for receiving data, and one wire pair is for transmitting data. The same card port that supports 100Base-TX operation can also support 10Base-T operation.

• 100Base-TX half duplex

• 10Base-T full duplex

• 10Base-T half duplex

• 100Base-TX full duplex For example, if both devices on the link support 10Base-T (half duplex)

and 100Base-TX (half duplex), autonegotiation at both ends will connect the 100Base-TX (half duplex) instead of the 10Base-T (half duplex).

Most Fast Ethernet devices on the market today such as hubs and switches do not support autonegotiation. Either the speed and duplex mode of the device are ﬁxed (as is usually the case with hubs), or they are often manually conﬁgured at the desired speed and duplex (as is often the case for switches). However, switches that support autonegotiation are starting to be offered.

If the HP-PB 10/100Base-TX/9000 card is connected to a device, such as

16 Chapter1

Installing and Conﬁguring 10/100Base-TX/9000

Known Problems and Workarounds

a switch, that is autonegotiating, the HP-PB card will autonegotiate with the device to mutually determine the highest possible speed and duplex settings between them.

NOTE If the HP-PB 10/100Base-TX/9000 card is connected to a device that

does not support autonegotiation or a device that has autonegotiation disabled, the HP-PB card will autosense the speed of the link and set itself accordingly. The duplex mode of the card will be set to

half-duplex in this case. If you want the card to operate in full-duplex mode, you have to set it using the method described in “Manual Speed and Duplex Mode Conﬁguration.”

The HP-PB 10/100Base-TX card will sense when the connection between itself and a hub or switch on the other end of a link has been broken. If a connection is made to another (or the same) device, the autonegotiation and autosensing process will be done again automatically. Autonegotiation and autosensing are also done whenever the interface is reset.

Known Problems and Workarounds

If your switch supports autonegotiation, you should not normally need to set the duplex mode or the speed of the HP-PB 10/100Base-TX card. Optionally, you can set the full- or half-duplex mode of the card by using the lanadmin -X Speed and Duplex Mode Conﬁguration” in this Release Note.

NOTE You cannot set the mode of the card in SAM (the ﬁeld in SAM that

contains the setting for full-duplex is ignored--it may show the MAC address of the card but cannot be used for conﬁguration).

Chapter 1 17

mode ppa (nmid)

command as explained in “Manual

Installing and Conﬁguring 10/100Base-TX/9000

What Manuals are Available

The following documents summarize installation, conﬁguration, veriﬁcation and troubleshooting of the HP-PB 10/100Base-TX/9000 LAN link:

• HP-PB 10/100Base-TX/9000 Quick Installation

• Using HP-PB 10/100Base-TX/9000. Available on Instant Information

CDROM or www.docs.hp.com.

Software Availability in Native Languages

The commands used with this product are the ones supported by the Native Language Support Catalog of HP-UX.

18 Chapter1

Installing and Conﬁguring 10/100Base-TX/9000

Overview of Installation Steps

NOTE The HP 9000 10/100Base-TX/9000 Quick Installation guide lists the

steps required to install your 10/100Base-TX/9000 hardware and software. The quick installation guide refers you to complete descriptions of the software installation steps in this manual. Use the quick installation guide as your primary reference to installation and conﬁguration procedures.

This chapter describes the procedures to load 10/100Base-TX software and hardware onto your system. It contains the following sections:

• Step 1: Check the 10/100Base-TX Installation Prerequisites.

• Step 2: Load the 10/100Base-TX Software.

• Step 3: Access the system Card Bay.

• Step 4: Install the 10/100Base-TX Card.

• Step 5: Attach the system to the Network.

• Step 6: Conﬁgure the 10/100Base-TX Link.

• Step 7: Verify the Installation.

NOTE Prior to installing 10/100Base-TX/9000, HP recommends that you create

a network map or update the existing map of your 10/100Base-TX network. Refer to appendix B for an example 10/100Base-TX network map.

Chapter 1 19

Installing and Conﬁguring 10/100Base-TX/9000

Step 1: Check the 10/100Base-TX Installation Prerequisites

NOTE The 10/100Base-TX card is a combination card that allows you to connect

to a 10Mbit/s 10Base-T or 100 Mbit/s 100Base-TX network. The hardware card will be referred to as a 10/100Base-TX card throughout this manual.

Prior to loading the 10/100Base-TX product onto your system, check that you have met the following hardware and software prerequisites:

1. Check that the /usr/bin,/usr/sbin, and /sbin directories are in your

PATH using the command: echo $PATH

2. The operating system should have been upgraded to 10.20 or later

software. To obtain this information, execute the command:

/bin/uname -a

3. You have a twisted pair cable to connect your 10/100Base-TX card to

your hub. (The cable and hub do not come with the HP 10/100Base-TX product.) A hardware checklist is shown below:

A. Cable: category 5 unshielded twisted pair (UTP). B. Card: HP 9000 10/100Base-TX card. C. Hub or switch: 100Base-TX hub for 100 Mbit/s speed

10Base-T hub for 10 Mbit/s speed.

4. Ensure that there is at least one HP-PB slot available in the system

backplane for the HP-PB 10/100Base-TX card.

5. You have an IP/Internet address, alias, and subnet mask (optional),

for your new 10/100Base-TX card. After you have obtained the information, ﬁll out the Network Card Conﬁguration worksheet in your 10/100Base-TX quick installation card.

A summary of the major characteristics of the 10/100Base-TX card is

20 Chapter1

Installing and Conﬁguring 10/100Base-TX/9000

Step 1: Check the 10/100Base-TX Installation Prerequisites

shown in “Table 1: 10/100Base-TX/9000 Card Summary.”

Table 1-1 10/100Base-TX/9000 Card Summary

Category 10/100Base-TX

UTP Connection 8-pin RJ45

Speed

10 Mbit/s or 100 Mbit/s

Conﬁgure Speed At hub or switch port LED on Card Yes Card Selftest Yes Half-Duplex Yes Full-Duplex Yes Conﬁgure Duplex

Mode

Half-Duplex at hub or full-duplex at switch.

Autonegotiation Yes

*The speed conﬁguration of the 10/100Base-TX card is determined by the speed setting of the hub or switch port to which the card is connected. The card automatically senses this speed. The card only runs at one speed at a time. To verify the speed selection, use the LED indicators on the front of the 10/100Base-TX card as shown below or run lanadmin and check the link speed and duplex mode at the LAN Interface Status Display.

6. You have super-user status.

NOTE The only Application Programmatic Interface (API) supported by the

10/100Base-TX /9000 product is the Data Link Provider Interface (DLPI). Refer to the DLPI Programmer’s Guide for more detailed information .

Chapter 1 21

Installing and Conﬁguring 10/100Base-TX/9000

Step 2: Loading 10/100Base-TX Software

Follow the steps below to load 10/100Base-TX /9000 software using the HP-UX swinstall program.

1. Log in as root.

2. Insert the software media (tape or CD) into the appropriate drive.

3. Run the swinstall program using the command:

swinstall

This opens the Software Selection Window and Specify Source Window of the swinstall program.

4. Change the Source Host Name, if necessary, enter the mount point of

the drive in the Source Depot Path ﬁeld, and activate the OK button to return to the Software Selection Window. Activate the Help button to get more information.

The Software Selection Window now contains a list of available software bundles to install.

5. Highlight the HP-PB 10/100Base-TX/9000 software.

6. Choose Mark for Install from the “Actions” menu to choose the

product name(s) is to be installed.

7. Choose Install from the “Actions” menu to begin product

installation and open the Install Analysis Window.

8. Activate the OK button in the Install Analysis Window when the

Status ﬁeld displays a Ready message.

9. Activate the Yes button at the Conﬁrmation Window to conﬁrm that

you want to install the software. swinstall displays the Install Window.

View the Install Window to read processing data while the software is being installed. When the Status ﬁeld indicates Ready and the Note Window opens. swinstall loads the ﬁleset, runs the control scripts for the ﬁleset, and builds the kernel. Estimated time for processing: 3 to 5 minutes.

10.Activate the OK button on the Note Window to reboot the system.

The user interface disappears and the system reboots.

22 Chapter1

Installing and Conﬁguring 10/100Base-TX/9000

Step 2: Loading 10/100Base-TX Software

11.When the system reboots, check that the swinstall log ﬁle in tail /var/adm/sw/swagent.log to make sure the installation was successful. Use the tail command to locate the 10/100Base-TX

software.

12.Go to the next section “Access the System Card Bay.”

Chapter 1 23

Installing and Conﬁguring 10/100Base-TX/9000

Step 3: Access the System Card Bay

NOTE The HP-PB 10/100Base-TX card is not for use on a personal computer

(PC).

NOTE If you installed the card before you installed the software, execute

shutdown (no -h option) and proceed to “Step 5: Attach the System to the Network.”

Follow the steps below to prepare the system for installation of 10/100Base-TX hardware. Refer to the documentation for your system for detailed information about opening and closing the system and locating the slots in the HP-PB backplane.

1. At the HP-UX prompt, execute the following command and wait for the system to shutdown completely.

/etc/shutdown -h 0

Power off and unplug the system.

2. Observe antistatic precautions. Equalize any static charge on your body and your computer by using a grounded wrist strap or by touching the chassis of the computer frequently while you are installing the card.

Handle the card by the edges and avoid touching the edge connector and the components.

3. Open the system to gain access to the HP-PB backplane, if applicable.

4. On the HP-PB backplane, select the lowest empty HP-PB slot and remove the slot cover.

5. Go to the next section, “Step 4: Install the 10/100Base-TX Card.”

24 Chapter1

Installing and Conﬁguring 10/100Base-TX/9000

Step 4: Install the 10/100Base-TX Card

Follow the steps below to install the 10/100Base-TX card.

1. Grasp the card by its edges or faceplate with both hands.

2. Slide the card into the HP-PB slot.

3. Press the card ﬁrmly into place until you feel it mate fully.

4. Secure the card with the captive screws.

5. Reassemble the system.

Chapter 1 25

Installing and Conﬁguring 10/100Base-TX/9000

Step 5: Attach the System to the Network

Follow the steps below to attach the system to the network.

1. Attach the 8-pin RJ-45 plug on your twisted-pair LAN cable into the RJ-45 10/100 Mbit/s connector on the card. The same RJ-45 connector is used for either 10 or 100 Mbit/s operation. Push the plug into the connector until the plug clicks into place.

The 10/100Base-TX card automatically runs at the same speed that has been set on the 10/100Base-TX hub or switch.

2. Attach the free end of the cable to the appropriate port on the 10/100Base-TX switch or hub (or into a wall jack that is connected to a hub or switch). Connect power cable to system.

Set the hub or switch speed and duplex mode.The HP-PB 10/100Base-TX/9000 card supports both full- and half- duplex operation.

3. Power up the system. The 10/100Base-TX card will run an initialization test automatically. Any error messages will appear on the system’s screen. You can also view the initialization messages later by typing the dmesg command at the HP-UX prompt.

4. Verify that the LEDs on the card reﬂect the correct mode of operation. Refer to the LED matrix in Chapter 4, for the meaning of the LED patterns. Also, refer to the illustration on the HP-PB 10/100Base-TX/9000 Quick Installation for the LED pattern for normal 10 Mbit/s and 100 Mbit/s operation. Verify that the Test LED is OFF. If the TestLED remains lighted, an error has occurred and an error message will appear on the system’s screen.

5. When the system is up, log in as root and verify that btlan1 and its hardware path are displayed by executing the command: ioscan.

6. Execute ioscan -f to make sure the hardware path and driver are listed.

The ioscan command scans the system hardware and displays output similar to the following.

The driver for the 10/100Base-TX product is btlan1. Proceed to “Step

26 Chapter1

Installing and Conﬁguring 10/100Base-TX/9000

Step 5: Attach the System to the Network

6, Conﬁgure the 10/100Base-TX Link” to conﬁgure the card.

Class I H/W Path Driver S/W State H/W Type Description ======================================================================== bc 0 root CLAIMED BUS_NEXUS bc 1 8 ccio CLAIMED BUS_NEXUS I/O Adapter bc 2 10 ccio CLAIMED BUS_NEXUS I/O Adapter ext_bus 0 10/0 c720 CLAIMED INTERFACE GSC built-in Fast/Wide SCSI Interface target 0 10/0.5 tgt CLAIMED DEVICE disk 0 10/0.5.0 sdisk CLAIMED DEVICE SEAGATE ST31230W target 1 10/0.6 tgt CLAIMED DEVICE disk 1 10/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST31230W bc 3 10/4 bc CLAIMED BUS_NEXUS Bus Converter tty 0 10/4/0 mux2 CLAIMED INTERFACE MUX lan 2 10/4/4 btlan1 CLAIMED INTERFACE HP HP-PB 100 Base TX card lanmux 0 10/4/8 lanmux0 CLAIMED INTERFACE HP J2146A - 802.3 LAN lan 0 10/4/8.1 lan3 CLAIMED INTERFACE lan 3 10/4/16 btlan1 CLAIMED INTERFACE HP HP-PB 100 Base TXcard ba 0 10/12 bus_adapter CLAIMED BUS_NEXUS Core I/O Adapter ext_bus 2 10/12/0 CentIf CLAIMED INTERFACE Built-in Parallel Interface ext_bus 1 10/12/5 c700 CLAIMED INTERFACE Built-in SCSI target 2 10/12/5.0 tgt CLAIMED DEVICE tape 0 10/12/5.0.0 stape CLAIMED DEVICE HP HP35480A target 3 10/12/5.2 tgt CLAIMED DEVICE disk 2 10/12/5.2.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM XM-5401TA lan 1 10/12/6 lan2 CLAIMED INTERFACE Built-in LAN ps2 0 10/12/7 ps2 CLAIMED INTERFACE Built-in Keyboard/Mouse processor 0 32 processor CLAIMED PROCESSOR Processor memory 0 49 memory CLAIMED MEMORY Memory

NOTE For HP 9000 HP-PB systems, the hardware path is in the format, a/b.

Chapter 1 27

Installing and Conﬁguring 10/100Base-TX/9000

Step 5: Attach the System to the Network

number by 4. For example 10/4 speciﬁes that the HP-PB card is located in bus converter 10, slot number 1.

28 Chapter1

Installing and Conﬁguring 10/100Base-TX/9000

Step 6: Conﬁgure the 10/100Base-TX Link

NOTE Make sure the 10/100Base-TX card and software are installed in the

system before you use SAM to conﬁgure the software.

NOTE The instructions below are for the Motif version of the System

Administration Manager (SAM). To activate the X11 software on your system, you must ﬁrst run the command: .

export DISPLAY=

1. At the HP-UX prompt, type: sam

2. Double click Networking and Communications at the SAM main window.

3. Double click Network Card Conﬁguration at the Networking and Communications window.

4. Highlight the HP-PB 10/100Base-TX interface card that you want to conﬁgure from the object list. If the card is not displayed, then go back to Step 3 “Access the System Card Bay” and check that your hardware has been properly installed.

NOTE The term 10/100Base-TX on the display indicates that a 10/100Base-TX

card is present. To determine the speed of the 10/100Base-TX card you must run lanadmin and reference the link speed at the LAN Interface Status Display or check the 10 and 100 Mbit/s LEDs on the 10/100Base-TX card.

The SAM object list always shows the name of the built-in LAN (IEEE802.3/Ethernet) as lan0 and the ﬁrst networking card in an HP-PB slot as lan1. The networking cards installed in other slots are named sequentially (lan2, lan3, etc.), according to the order of the occupied slots.

system name

:0.0

Chapter 1 29

Installing and Conﬁguring 10/100Base-TX/9000

Step 6: Conﬁgure the 10/100Base-TX Link

5. Verify that the hardware path is correct for your 10/100Base-TX card. The slot number speciﬁed in the hardware path should be the

backplane slot number of the 10/100Base-TX card multiplied by 4. Forexample, if the hardware path is 32, then the 10/100Base-TX card should be in slot 8.

6. Choose Configure from the “Actions” menu to open the Conﬁgure LAN Card window.

a. Enter the information about the 10/100Base-TX card. To do so,

press the Tab key to move through the data entry ﬁelds.

NOTE SAM displays the Card Name, Hardware Path, and Station Address

ﬁelds with the appropriate values. These ﬁelds cannot be modiﬁed after the ﬁrst conﬁguration of the card.

b. Verify that the card type is one of the following:

10/100Base-TX IEEE8023 Ethernet 10/100Base-TX IEEE8023 10/100Base-TX Ethernet The default is 10/100Base-TX Ethernet

c. Enter the Internet address for your 10/100Base-TX card.

Upon exiting the ﬁeld, SAM checks to make sure that the IP/Internet address you entered is correctly formatted and is not currently in use.

d. Optionally, choose Add Aliases to open the Conﬁgure Aliases

window, if you want to assign aliases for the local host. You must complete this step if you have more than one LAN card

installed in your system. You can also modify or remove alias names for your 10/100Base-TX card on this menu.

Activate the OK button to perform the task and return to the Conﬁgure LAN Card window.

e. After returning to the LAN Card window, specify whether your

10/100Base-TX card will be on a subnetwork. f. Optionally, enter comments about your 10/100Base-TX card. g. Optionally, add the following advanced options: your station

30 Chapter1

Installing and Conﬁguring 10/100Base-TX/9000

Step 6: Conﬁgure the 10/100Base-TX Link

address and the Internet broadcast address. Activate the SAM online help for additional information on these options.

7. Activate the OK button at the Conﬁgure LAN Card window to enable your 10/100Base-TX card.

If the software is correctly conﬁgured, SAM displays the Network Card Conﬁguration object list with the status Enabled for your 10/100Base-TX card; otherwise, SAM displays an error message.

8. At the Network Card Conﬁguration menu, choose Exit from the “File menu.”

If you have moved or removed any 10/100Base-TX cards from the system, HP recommends that you verify the IP/Internet address of every card in the backplane before leaving SAM

9. Use lanscan to check the network interface and the hardware state of the 10/100Base-TX card.

NOTE For HP 9000 HP-PB systems, the hardware path is in the format, a/b.

For 10/100Base-TX/9000, a is the address of the optional bus converter, and b is the slot number where the card is installed. To determine the hardware path of an HP-PB LAN card, multiply the system bus slot number by 4. For example 10/4 speciﬁes that the HP-PB card is located in bus converter 10, slot number 1.

Chapter 1 31

Installing and Conﬁguring 10/100Base-TX/9000

Step 7: Verifying the Installation

Once your 10/100Base-TX/9000 software is installed, fully conﬁgured and running, you should run the following commands to verify 10/100Base-TX hardware and software installation. Refer to the online man pages for complete descriptions of the commands listed below.

1. To check that the link is working, enter the linkloop command at the HP-UX prompt. In this example, 5 is the Network Management ID (NMID) of your 10/100Base-TX card and 0x080009266C3F is the station address of a local or remote node. (You can obtain the NMID and the local station address from the lanscan command.)

linkloop -i 5 0x080009266C3F

100Base-TX/9000 installation is veriﬁed if linkloop succeeds. You can further verify the link by doing the following steps.

2. To check that the network connection is working, enter the ping command at the HP-UX prompt. In this example, 191.2.1.2 is the conﬁgured IP/Internet address of the remote system.

ping 191.2.1.2

3. To view information about the station address, hardware state, and network interface state of your 10/100Base-TX card, enter the lanscan command at the HP-UX prompt as shown in the example below:

lanscan

4. To show the number of packets sent or received, and any link errors, enter the netstat -i command at the HP-UX prompt as shown below:

netstat -i

5. To show the status of the 10/100Base-TX interface, enter the lanadmin diagnostic command at the HP-UX prompt. For example:

lanadmin

After entering the utility, enter the following lanadmin menu commands in sequence to show the status of the 10/100Base-TX device with the NMID of 5.

lan nmid 5

32 Chapter1

Installing and Conﬁguring 10/100Base-TX/9000

Step 7: Verifying the Installation

display

To exit the utility, enter:

quit

Refer to appendix A for a description of the lanadmin display ﬁelds.

Chapter 1 33

Installing and Conﬁguring 10/100Base-TX/9000

What Happens During Card Initialization Sequence?

Following is an overview of the initialization sequence for the HPPB 10/100Base-TX card:

Initialization of an HP-PB 10/100Base-TX card happens during system bootup only, and it is driven by the btlan1 driver for the card. The card consists of two boards: the motherboard and the daughterboard. Initialization is divided into two phases: initialization of the motherboard and initialization of the daughterboard. The initialization of each of these boards is further divided into the initialization of each of the major programmable components on the boards. Initialization consists of the following sequential tasks: identiﬁcation of a component, resetting a component, if applicable, and conﬁguration.

Two LEDs on the card are related to the proper installation and functioning of the card: the Power and Test LEDs. None of the components on either of the boards is identiﬁable if the power does not reach the card, in which case the Power LED on the card does not light. The card might not be seated properly in this case. Even if the Power LED is lit, some of the components could still fail to identify correctly if the card is not properly seated or if the card is defective. In such a case the initialization of that component fails to complete and the Test LED on the card is lit. In one case, the component on the motherboard which is responsible to drive the Test LED may be defective or may not be reached due to the improper seating of the card in which case the initialization aborts without lighting the Test LED. However, whenever initialization fails, it prints a message on the console identifying the failure. You can later retrieve initialization messages after the system is fully booted up by using the dmesg command.

Finally, the driver tries to establish a good data link between the card and the hub or switch. If there is no cable connection, or if the cable connection is bad, or if the hub or switch is not compatible, that is, not 10Base-T or 100Base-TX capable, the Link LED will not be lit and either 10Base-T LED or 100Base-TX LED will be lit at random. In this situation, the Test LED will not be lit. Also, a message indicating the detection of a bad cable connection is printed on the console as well as logged in NETTL logs.

34 Chapter1

2 Conﬁguring Network

Connectivity Using SAM

This chapter describes how to conﬁgure remote connectivity using SAM. It contains the following sections:

Conﬁguring Network Connectivity Using SAM

• Step 1: Conﬁguring Network Connectivity

• Step 2: Deleting a Default Gateway (Optional)

36 Chapter2

Conﬁguring Network Connectivity Using SAM

Step 1: Conﬁguring Network Connectivity

Your system may not be able to communicate with other systems, for example, PCs, workstations, servers, etc., until you conﬁgure system-to-system connections by adding an entry in hosts for the remote system. You can use SAM to do this automatically by completing the following steps:

1. At the HP-UX prompt, type: sam

2. Double click Networking and Communications at the SAM main window.

3. Double click Internet Addresses to enable your system to communicate with other systems using the TCP/IP protocol.

SAM displays the remote system names and Internet addresses that are already conﬁgured.

4. Choose Add from the “Actions” menu to open the Add Internet Address window to add the internet address and system name of a remote system.

Use the SAM online help system for information about adding remote system connections.

a. Enter the Internet address for the remote system.

Upon exiting the Internet Address ﬁeld, SAM checks to make sure you have entered a valid IP/Internet address. SAM also determines if a gateway is required for the connection (see step 4c).

b. Enter the remote system name.

Upon exiting the Remote System Name ﬁeld, SAM checks to make sure that connectivity has not already been conﬁgured for this system. If it has, SAM displays an error message.

c. Optionally, choose Add Aliases to open the Add Aliases window

if you want to conﬁgure aliases for a remote system. You can modify or remove alias names for a remote system on this

menu Activate the OK button to perform the task and return to the Add

Chapter 2 37

Conﬁguring Network Connectivity Using SAM

Step 1: Conﬁguring Network Connectivity

Internet Addresses window. Proceed to step 5 if a gateway is not required for this remote

connection. SAM displays ﬁelds for entering gateway information if a gateway

is required for this remote system connection. Use the SAM online help system for information about gateways.

5. Activate the OK button to enable your system to communicate with this system and return to the System-to-System Connectivity object list.

SAM updates the object list to include the remote system you conﬁgured.

NOTE You can modify or remove remote systems and modify default gateways

by highlighting the Remote System Name from the object list and choosing Modify, Remove, or Modify Default Gateway from the “Actions” menu.

6. Choose Exit from the “File” menu.

7. At the Networking Communications window, choose Exit SAM from the “File” menu to leave SAM.

8. Verify remote system conﬁguration. a. View the list of remote systems you can communicate with using a

symbolic name by typing the following command at the HP-UX prompt:

more /etc/hosts

b. View the conﬁgured destinations reached through gateways and

the gateways used to reach those destinations by typing the following command at the HP-UX prompt:

netstat -r

To verify that you can communicate with a remote system via the 10/100Base-TX product, return to chapter 1, “Step 8: Verify the Installation.”

38 Chapter2

Conﬁguring Network Connectivity Using SAM

Step 2: Deleting a Default Gateway

To delete a default gateway that you have added with SAM, do the following:

1. Enter the following command at the HP-UX prompt:

route delete default gateway_hostname

where gateway_hostname is the hostname of the default gateway you want to delete.

2. Edit the /etc/rc.conﬁg.d/netconf ﬁle to remove the corresponding internet routing conﬁguration parameter values for the gateway. For example:

ROUTE_DESTINATION [0] = ROUTE_GATEWAY [0] = ROUTE_COUNT [0] =

Chapter 2 39

Conﬁguring Network Connectivity Using SAM

Step 2: Deleting a Default Gateway

40 Chapter2

3 100Base-TX Resources

In addition to this manual, use the following resources to maintain and administer HP-PB 10/100Base-TX/9000.

100Base-TX Resources

HP-UX Manual Reference Pages

While installing, conﬁguring, or troubleshooting 10/100Base-TX, you may need to refer to any of the following online manual reference pages (man pages) for useful HP-UX operating system or 10/100Base-TX commands. To display a man page, type the following at the system prompt: man <command name>. For example, man arp.

• arp(1M) displays and modiﬁes the Internet-to-station address mapping tables used by the Address Resolution Protocol.

• hosts(4) is a database that contains a single line entry for each host name entry.

• ifconﬁg(1M) assigns an address to a network interface, and conﬁgures and displays network parameters.

• ioscan(1M) scans system hardware, usable I/O system devices, or kernel I/O system data structures as appropriate, and lists the results.

• lanadmin(1M) resets or reports the status of the LAN card.

• lanconﬁg(1M) sets/resets the packet encapsulation method for a network interface. Applicable only to HP-UX 10.20 or earlier.

• lanscan(1M) displays information about LAN cards that are successfully bound to the system.

• linkloop(1M) veriﬁes network connectivity through the Data Link Layer (OSI Layer 2).

• netfmt(1M) formats common tracing and logging binary ﬁles.

• netstat(1) provides network statistics and information about network connections.

• nettl(1M) logs network events and traces packets as they enter and exit the 10/100Base-TX driver.

• ping(1M) veriﬁes network connectivity through the Network Layer (OSI Layer 3) and reports the round-trip time of communications between the local and remote hosts.

• route(1M) adds and deletes entries to the network routing table.

• sam(1M) conﬁgures networking software.

42 Chapter3

100Base-TX Resources

HP-UX Manual Reference Pages

• swinstall(1M) loads software ﬁlesets onto HP-UX-based systems.

• swverify(1M) veriﬁes software installation.

Chapter 3 43

100Base-TX Resources

Error Messages

HP-PB 10/100Base-TX comes with an online message catalog that is used to report networking problems. You must use the nettl logging and tracing utility to display the probable cause and action for a message.

44 Chapter3

100Base-TX Resources

Logging Messages

HP 100Base-TX/9000 uses the nettl(1M) logging and tracing facility supplied with HP-UX. You may access the logging and tracing utility using either the graphical user interface (GUI) version or the command line interface.

Features of the GUI version, which are now a part of your HP 9000 system, include:

• An interface which guides you through logging and tracing tasks.

• An interface which allows you to create and format reports.

• The capability to collect logging and tracing subsystem-speciﬁc information.

• Report screens which are updated instantaneously with current logging and tracing information by the subsystem.

• Context-sensitive on-line help.

To access the GUI version of the logging and tracing utility, run the command:

nettladm See the nettladm(1M) man page for information on using the GUI

version, or the nettl(1M) manual (man) page for information on using the

command line interface. Listed below are some example commands using the command line

interface.

• To examine the log ﬁle with cause and action descriptions. netfmt -v -f /var/adm/nettl.LOG00 | more The -v option enables the reporting of available cause and action

descriptions for each log message. A sample 10/100Base-TX log message using the -v option is shown below.

******100 Mb/s LAN/9000 Networking**********************

Fri Aug 30 PDT 1996 15:08:07.091398 DISASTER Subsys:LAN100 Loc:00000 <6011> HPPB 10/100Base-T driver detected bad cable

Chapter 3 45

100Base-TX Resources

Logging Messages

connection between the adapter in slot 2 and the hub or switch.

• To examine just the log messages in the log ﬁle.

netfmt -f /var/adm/nettl.LOG00

• To check network logging and tracing status.

nettl -status

• To start 10/100Base-TX tracing to the ﬁle /tmp/traceﬁle.TRC0. nettl(1m) adds the .TRC0 postﬁx for you.

nettl -traceon all -entity LAN100 -file /tmp/tracefile

• To stop 100Base-TX tracing.

nettl -traceoff -entity LAN100

• To format the 10/100Base-TX trace ﬁle into the ﬁle /tmp/traceout.

netfmt -f /tmp/tracefile.TRC0 > /tmp/traceout

Refer to the netfmt(1M) man page for further information about this card and how to create a ﬁlter for trace formatting.

46 Chapter3

100Base-TX Resources

Manual Installation and Conﬁguration

If you want to manually install and conﬁgure your 10/100Base-TX/9000 product, refer to the detailed instructions in the Installing and Administering LAN/9000 Software manual.

You may need some of the following 10/100Base-TX/9000-speciﬁc information when you follow those steps:

• HP 9000 HP-PB driver keyword: btlan1

• The driver for the HP-PB 10/100Base-TX card has a ﬂoating major number (that is, a major number assigned dynamically by the operating system).

Chapter 3 47

100Base-TX Resources

Contacting Your HP Representative

If you have no service contract with HP, you may follow the procedure described below, but you will be billed accordingly for time and materials.

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:

• A characterization of the problem. Describe the events leading up to and including the problem. Attempt to describe the source and symptoms of the problem.

Your characterization should include: HP-UX commands; communication subsystem commands; job streams; result codes and messages; and data that can reproduce the problem. You should also provide a network map with the host name, IP/Internet address, and station address of each system connected with the HP system.

Illustrate as clearly as possible the context of any message(s). Prepare copies of information displayed at the system console and user terminal.

• Obtain the version, update, and ﬁx information for all software. To check the 10/100Base-TX version number, execute what vmunix and look for the keyword, vtlan1.

To check the version of your kernel, execute uname -r. This allows HP to determine if the problem is already known and if

the correct software is installed at your site.

• Prepare copies of the /etc/hosts, and /etc/rc.conﬁg.d/netconf ﬁles.

• Execute the dmesg command and record messages about the status of the 10/100Base-TX card.

• Execute the lanscan -v command and record the output.

• Execute the display command of the lanadmin diagnostic on the 10/100Base-TX interface and record the output.

• Record the troubleshooting ﬂowchart number and step number where you are unable to resolve the problem.

• Record all error messages and numbers that appear at the user terminal and the system console.

48 Chapter3

100Base-TX Resources

Contacting Your HP Representative

• Save all network log ﬁles. Make sure that ERROR and DISASTER log classes are enabled when log ﬁles are collected.

Prepare the formatted output and a copy of the log ﬁle for your HP representative to further analyze.

• Prepare a listing of the HP-UX I/O conﬁguration you are using for your HP representative to further analyze. Use the ioscan(1M) command to help collect this information

• Try to determine the general area within the software where you think the problem exists. Refer to the appropriate reference manual and follow the guidelines on gathering information for that product.

• Document your interim, or “workaround,” solution. The cause of the problem can sometimes be found by comparing the circumstances in which it occurs with the circumstances in which it does not occur.

• Create copies of any Internet or 10/100Base-TX/9000 link trace ﬁles that were active when the problem occurred for your HP representative to further analyze.

• In the event of a system failure, a full memory dump must be taken. Use the HP-UX utility savecore(1M) to save a core dump. Send the output to your HP representative.

Chapter 3 49

100Base-TX Resources

Contacting Your HP Representative

50 Chapter3

4 Troubleshooting

10/100Base-TX/9000

This chapter provides guidelines for troubleshooting 10/100Base-TX. It contains the following sections:

Troubleshooting 10/100Base-TX/9000

• Troubleshooting Overview.

• Diagnostic Flowcharts.

52 Chapter4

Troubleshooting 10/100Base-TX/9000

Troubleshooting Overview

10/100Base-TX problems can be caused by problems in a variety of hardware and software components. The problem impacting your system may originate in another part of the 10/100Base-TX network.

As with any troubleshooting, a systematic approach is helpful. The following two tables and the following ﬂowcharts provide a logical sequence of steps to follow when troubleshooting 10/100Base-TX/9000. Using the diagnostic ﬂowcharts provided in this chapter, identify whether the problem is with 10/100Base-TX/9000 or any of the connections to the hub or switch, or whether it is in some other part of the network, verify your assumptions and, if it is limited to 10/100Base-TX/9000 software or hardware, correct the problem.

NOTE Toquickly isolate and diagnose 10/100Base-TX/9000 problems, follow the

steps in the troubleshooting ﬂowcharts, beginning with Flowchart 1, and stay with the ﬂowcharts until the problems are resolved. Continue sequentially through ﬂowcharts 2, 3, 4, 5, 6, and 7, referring back to ﬂowchart 1 (ping) until you have corrected the problems.

If you cannot solve the problem on your own, contact your HP representative. Use the guidelines at the end of chapter 3 to help you effectively communicate what is wrong. T he 10/100Base-TX product uses diagnostic tools compatible with the HP LAN/9000 Link product.

Table 4-1 Troubleshooting Information

Symptom Corrective Action

The system does not recognize the card; the HP-PB Test LED is off.

Chapter 4 53

Ensure that the card is seated in the system backplane. Check for boot-time error messages by typing the dmesg command at the HP-UX prompt. Ensure that kernel contains driver by issuing what command on kernel.

Troubleshooting 10/100Base-TX/9000

Troubleshooting Overview

Table 4-1 Troubleshooting Information

Symptom Corrective Action

The card LEDs are okay, but you can’t communicate with other systems.

If the card LEDs appear to be okay:

1) Verify that the cable being used complies with the IEEE 802.3u-1995 standard.

2) Ping the broadcast address for the card, and check to see if the activity light on the hub blinks. Other active hosts must be connected to the hub or else the activity light will not blink.

3) If the activity light on the hub does not blink, and there are other active hosts connected to the hub, open another window and enter: netstat

-i 1 Try the broadcast ping again. The

transmitted packets counter should start to increment. If the counter does not increment, then there is an IP conﬁguration problem.

4) If the counter does increment, but the activity light on the hub does not blink, check the card’s activity light. If it is blinking, the problem is likely with the hub or connection to the hub. If the activity light on the adapter is not blinking, then there may be a problem with the driver or the card. Contact HP.

Link LED off. Check RJ-45 connector, switch, hub,

and cable.

54 Chapter4

Troubleshooting 10/100Base-TX/9000

Troubleshooting Overview

In the following HP-PB 10/100Base-TX LED Matrix:

X = LED ON, and O = Flashing

HP-PB 10/100Base-TX LED Matrix

Power 10 100 Link Activity Test Description

X Improperly seated card or

defective card.

X X Driver has not initialized card.

Link cable is not connected to card or to

hub or switch. X X Same as above but is for 100Base-TX. X X X Driver couldn’t complete the

initialization of the card because an error

has been detected. Card may be

defective. X X X Same as above but is for the 100Base-TX

mode. X X X Normal quiescent state for 10Base-T. X X X Normal quiescent state for 100Base-TX. X X X O Normal state during transfer of 10Base-T

data. This state is also seen when the card

is connected to a switch and the card is

quiescent. Switch is sending link pulses. X X X O Sameas above but is for the 100Base-TX

mode.

Chapter 4 55

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Below is a summary of the types of network tests in the diagnostic ﬂowcharts.Followthe ﬂowcharts in sequence beginning with ﬂowchart 1. Continue sequentially through ﬂowcharts 2, 3, 4, 5, 6, 7, 8, and 9, referring back to ﬂowchart 1 (ping), as indicated at the end of each ﬂowchart, until you have corrected the problem.

Table 4-2 Flowchart Descriptions

Flowchart Description

1 Network Level Loopback Test 2 10/100Base-TX Connections/LED Test 3, 4, and 5 Conﬁguration Test 6 Network Level Loopback Test 7 Link Level Loopback Test 8 Transport Level Loopback Test (using ARPA) 9 Bridge/Gateway Loopback Test

Network Level Loopback Test: Checks roundtrip communication between Network Layers on the source and target host using the ping(1M) command.

10/100Base-TX Connections/LED Test: Checks that all the hardware connections between your system and the 10/100Base-TX network are connected and operational.

Conﬁguration Test: Veriﬁes the conﬁguration of the network interface on a host using the lanscan(1M), netfmt -vf, lanadmin(1M), and ifconﬁg(1M) commands.

Network Level Loopback Test (cont): Checks arp entries using the arp(1M) command.

Link Level Loopback Test: Checks roundtrip communication between Link Levels on the source and target host using the linkloop(1M) diagnostic.

56 Chapter4

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Transport Level Loopback Test: Checks roundtrip communication between Transport Layers on the source and target host using ARPA services telnet and ftp commands.

Bridge/Gateway Loopback Test: Checks general network connections through a gateway.

Chapter 4 57

Figure 4-1

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 1: Network Level Loopback Test

Execute: ping

to remote host

ping

successful

yes

Stop

Network

unreachable

Command

Unknown

No route

to host

Call HP

hangs

host

yes

2,3,4,5 6 & 7

Correct BIND, YP or

/etc/hosts conﬁguration

Add route

table entry

58 Chapter4

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 1 Procedures

A. Execute: ping to remote host.Using ping(1M), send

a message to the remote host to which you are having problems connecting. For example:

ping spiff

B. ping successful? A message is printed to stdout for

each ping packet returned by the remote host. If packets are being returned, your system has network level connectivity to the remote host. Note what percentage of the total packets are lost, if any. Losing ten percent or more may indicate the network or remote host is extremely busy. You may also ﬁnd it useful to note the round-trip transmission times. Periodically high transmission times may indicate that the network or remote host is extremely busy. Consistently high transmission times may indicate the local host is extremely busy. If a message is not returned after executing ping, ping is not successful. Do Cntrl C to stop the ping output.

C. Network unreachable? If yes, go to ﬂowchart 3 to

display connection status using the lanscan(1M) command.

D. Command hangs. If a message is not returned after

executing ping, go to ﬂowcharts 2 through 7, referring back to ﬂowchart 1 (ping) until you have corrected the problem.

E. Unknown host? If you receive this message, go to step

F. Correct BIND, YP or hosts conﬁguration. Add the

missing host name and start again with ﬂowchart 1.

G. No route to host? If Error= Sendto: No route to

host, go to Step H. Otherwise, call your HP representative for help.

H. Add route table entry. Using route, add a route

table entry for that host. Refer to the route(1M) online man page for more details. Start again with ﬂowchart

Chapter 4 59

Figure 4-2

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 2: 10/100Base-TX Connections/LED Test

Power LED =ON

Check:

Power outlet

yes

Test LED = ON

LED Display:

100 Mbit port LED=ON

Test Error Message

10 Mbit port LED=OFF

on Screen (dmesg ouput)

Check status of

10, 100, Link, and Activity

LEDs

yes

Check card installation.

Reset card. Call HP if

problem persists.

Check card installation.

Reset card. Call HP if

problem persists.

Link

LED = OFF

Check connection to hub

yes

or switch.

Ensure hub/switch is 10Base-T or 100Base-TX. Reset card.

60 Chapter4

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 2 Procedures

A. Check TestLED. Check the on/off pattern of the three

LEDs on the hardware card and make a note of it. Refer to the LED matrix at the beginning of this chapter for interpretation of the LED patterns.

B. Test LED=ON? If Test LED is ON, type the dmesg

command and look for an error message. Go to step C.

If Test LED is OFF, go to step D.

C. Check card installation. Reset card according to

Steps D through G in Flowchart 4. If problem persists, Call HP. Go back to ﬂowchart 1.

D. Check Power outlet. Ensure the power cord is

plugged in to a live outlet.

E. Test LED = OFF? At the HP-UX prompt, type the

dmesg command, and look for an error message. Does the dmesg output show an error message from btlan1? If not, go to step G.

F. Check card installation. If dmesg reported an

error message from btlan1, reset card according to Steps D through G in Flowchart 4. If problem persists, call HP. Go back to ﬂowchart 1.

G. Check status of 10, 100, Link, and Activity LEDs. H. Link LED = OFF? If it is off, proceed to step I.

If Link LED = ON, proceed to ﬂowchart 2a.

I. If Link LED = OFF, check connection to hub or switch.

Ensure hub or switch is 10Base-T or 100Base-TX. Reset card according to Steps D through G in Flowchart 4. Go back to ﬂowchart 1.

Chapter 4 61

Figure 4-3

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 2a: 10/100Base-TX Connections/LED Test

Is either

10 Mbit or 100 Mbit LED=ON

yes

LED Display:

100 Mbit port LED=ON

Does link speed match

10 Mbit port LED=OFF

what you expect

yes

Check connection to hub or switch.

Reset card.

Set attached hub or switch to correct speed.

Reset card.

LED Display:

100 Mbit port LED=ON

Check duplex mode

10 Mbit port LED=OFF

on switch. Same mode

Does Activity LED come on during test

yes

Set attached switch to correct speed, and duplex, mode. Reset card.

Call HP

yes

62 Chapter4

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 2a Procedures

I. Either 10 Mbit or 100 Mbit LED = ON? If yes, go to

step K.

J. If either 10 Mbit or 100 Mbit LED = OFF, check

connection to hub or switch. Reset card according to Steps D through G in Flowchart

4.Go back to ﬂowchart 1.

K. Does Link speed match what you expect? If it

does, proceed to step M

L. If Link speed does not match what you expect,

set attached hub or switch to the correct link speed. Reset card according to Steps D through G in Flowchart 4.Go back to ﬂowchart 1.

M. Check duplex mode on switch port. Is the duplex

mode set to the same duplex mode on both the card and the switch port? If it is, proceed to step O.

N. Set attached switch port to the same duplex mode on

both the card and the switch. Reset card according to Steps D through G in Flowchart 4. Go back to ﬂowchart

O. Does Activity LED come on during test? If the

Activity LED does not come on, Call HP. If it does come on, go to ﬂowchart 3.

Chapter 4 63

Figure 4-4

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 3: Conﬁguration Test

Execute: lanscan

your interface

Run ioscan

Is driver in

displayed

kernel

yes

Check

hardware

Problem

ﬁxed

yes

Hardware

-f

to add driverkeyword

Install driver.

Verify or edit

/stand/system

btlan1

Regen kernel.

yes

Reboot the

system

Stop

64 Chapter4

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 3 Procedures

NOTE Check that your 10/100Base-TX connectors to the card and hub (or wall

plug) are fully connected before beginning this ﬂowchart.

A. Execute: lanscan. Enter the lanscan command to

display information about LAN cards that are successfully bound to the system. See the lanscan online manpage for more detailed information.

B. Is your interface displayed? lanscan shows

information about every LAN card in the system backplane. The Hardware Path of one of the entries should correspond to the HP-PB 10/100Base-TX card slot multiplied times 4. For example, a hardware path of 32 corresponds to an HP-PB 10/100Base-TX card in slot 8.

C. Hardware up.The hardware state is operational if up is

displayed for the 10/100Base-TX card under the Hardware State heading. If it is, continue to ﬂowchart

5. If not, go to D.

D. Run ioscan. ioscan will scan the system hardware

and list the results. If you execute ioscan -f, output similar to the following will be displayed:

Chapter 4 65

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

E. Is driver in kernel? If the driver has not been

generated into the kernel, ioscan output will be:

ioscan -f Class I H/W Path Driver S/W State H/W Type Description =================================================================== unknown -1 10/4/4 UNKNOWN UNCLAIMED INTERFACE

66 Chapter4

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

The class and driver ﬁelds alone will indicate “unknown” status if the kernel has not been generated. If the driver has not been generated, continue to step H. If the driver is in the kernel, go to step G.

F. Verify or edit /stand/system and regen kernel.

Verify/edit /stand/system contains theekeyword. If not, see “Creating a New Kernel” in chapter 3 of the

Installing and Administering LAN/9000 Software

manual for instructions on how to edit /stand/system to create a new kernel.

G. Check hardware. Verify that the network card is

seated correctly and that it is operational. H. Reboot the system. I. Problem ﬁxed? If you have found the 10/100Base-TX

card problem, stop. If not, start again with ﬂowchart 1.

Chapter 4 67

Figure 4-5

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 4: Conﬁguration Test

Execute: netfmt

Check causes and actions on display

in the formatted log

output

Problem

solved

Execute: lanadmin

Select LAN from

Select PPA (NMID)

and

enter it

Reset card

Reset

successful

yes

68 Chapter4

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 4 Procedures

A, Execute: netfmt. Use the netfmt command to view log

data (error and disaster messages). An example

command is shown below.

netfmt -v -f /var/adm/nettl.LOG00 | more

B. Check causes and actions on display in the

formatted log output. Use the time stamp to ﬁnd the

proper logs. Ensure that you are looking at the

10/100Base-TX information. C. Problem solved. If yes, go to ﬂowchart 1. If not,

continue with step D. D. Execute lanadmin. Run lanadmin(1M). For a

complete description of this command, refer to the

lanadmin(1M) on-line manual page. E. Select LAN from Menu. Select lan from the menu to

enter LAN Interface Diagnostic. F. Select the PPA (NMID) and enter the

10/100Base-TX NMID. You can use the lanscan

command to ﬁnd the current PPA (NMID) for

10/100Base-TX. The PPA (NMID) you enter becomes

the current device to be tested. G. Reset the card according to Steps D through G in

Flowchart 4. Using the reset command in lanadmin

re-executes the LAN card self-test.

Reset successful? The reset is successful if no errors

are displayed as a result of the reset command. If the

self-test was successful, the problem may be that you

are not connected to the 10/100Base-TX network.

Correct the problem and verify the resolution by

continuing with ﬂowchart 1. Otherwise, go to ﬂowchart

4A.

Chapter 4 69

Figure 4-6

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 4A: Conﬁguration Test

Execute: netfmt

Check causes and actions on display

in the formatted log

output

Problem

solved

yes

Call HP

70 Chapter4

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 4A Procedures

A. Execute: netfmt. Use the netfmt command to view log

data (error and disaster messages). An example netfmt

command is shown below:

netfmt -v -f /var/adm/nettl.LOG00 | more

Extend the search to LOG01 as information may have

rolled (overﬂowed) into this ﬁle from LOG00. B. Check causes and actions on display in the

formatted log output.Use the time stamp to ﬁnd the

proper logs. Ensure that you are looking at the

10/100Base-TX information. C. Problem solved. If yes, go to ﬂowchart 1. If not,

contact your HP representative.

Chapter 4 71

Figure 4-7

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 5: Conﬁguration Test

Execute

ifconﬁg <interface>

...<IP address> up

Execute:

ifconﬁg <interface

/etc/rc.conﬁg.d/netconf

ifconﬁg

successful

yes

ifconﬁg entry in

/etc/rc.conﬁg.d/netconf

Add ifconﬁg

command to

yes

Are

ﬂags correct

yes

Any error

messages

returned

Correct ifconﬁ

ﬂag settings

Call HP

Correct problem

according to the

message received

yes

72 Chapter4

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 5 Procedures

A. Execute: ifconﬁg <interface> <IP address> up.

Execute ifconﬁg on the interface you want to conﬁgure

in order to ensure that the interface is enabled. For

example, to conﬁgure the 10/100Base-TX interface

lan1, enter:

ifconfig lan1 192.6.1.17 up

For more examples of the ifconﬁg command, refer to

the ifconﬁg(1M) online man page. B. Execute: ifconﬁg <interface>. Execute ifconﬁg

without the up parameter again on the interface you

want to test to check the ﬂag setting for the up

parameter. For example, to check the 10/100Base-TX

interface lan1, enter:

ifconfig lan1

C. ifconﬁg successful? ifconﬁg is successful if the

output shows the correct Internet address and the

ﬂags:

<UP,BROADCAST, NOTRAILERS, RUNNING>.

Note: Make sure the UP ﬂag is displayed. D. Are ﬂags correct? If ﬂags are not correct, use the

ifconﬁg command to correct them. If they are correct,

go to step F.

Correct ifconﬁg ﬂag settings.If ifconﬁg returns an

incorrect ﬂag setting, re-execute the command with the

proper setting. For more information, refer to the

ifconﬁg(1M) online man page. Start again with

ﬂowchart 5, as necessary. E. Any error message returned?If ifconﬁg is not

successful, and an error message appears, go to Step G.

If no error messages appear, contact your HP

representative. F. Correct problem according to the message

received.If you received an error message, make the

appropriate corrections stated in the message and then

begin this procedure again.

Chapter 4 73

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

ifconﬁg entry in /etc/rc.conﬁg.d/netconf? Check that there is an entry in the /etc/rc.conﬁg.d/netconf ﬁle for your 10/100Base-TX card.

I. Add ifconﬁg command to /etc/rc.conﬁg.d/netconf

ﬁle. Add the ifconﬁg command to /etc/rc.conﬁg.d/netconf, and reboot. For more information, refer to the ifconﬁg(1M) online man page. Go to ﬂowchart 1 to verify that the problem has been solved.

74 Chapter4

Figure 4-8

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 6: Network Level Loopback Test

Host entry

complete

ping local host

in ARP

cache

yes

Entry

yes

Remote

host up

Bring up

remote host

Use arp to

complete entry

yes

Chapter 4 75

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart Procedures

A. Host entry in ARP cache? Using arp, check that an

entry exists for the remote host in your system's ARP cache. For example:

arp spiff

B. Remote host up? If there is no ARP cache entry for

the remote host, ﬁrst check that the remote host is up. If not, the remote host has not broadcast an ARP message, and that probably is why there is no entry in the ARP cache.

C. Bring-up remote host. Have the node manager of the

remote host bring that system up and start again with ﬂowchart 1.

D. Entry complete? Perhaps there is an ARP cache

entry, but it is wrong or not complete. If the entry is complete, go to step F.

E. Use arp to complete entry. Using arp, enter the

correct Station Address. For more information, refer to the arp(1M) online man page. Start again with ﬂowchart 1.

F. ping local host. Using ping, do an internal loopback

on your own system. In other words, ping your own system.

If the internal loopback is successful, your system is operatingproperly to the Network Layer (OSI Layer 3). In addition, you know an ARP cache entry for the remote host exists on your system. Start again with Flowchart 1.

76 Chapter4

Figure 4-9

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 7: Link Level Loopback Test

Execute: linkloop

to remote host

Loopback FAILED:

Address has bad

format

linkloop

successful

Loopback FAILED:

Not an individual

address

Correct the link

address parameter

yes

Loopback

FAILED

Choose a different

remote host;

re-execute

linkloop

successful

yes

Check remote host’s

connectivity to

100Base-TX

Chapter 4 77

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 7 Procedures

A. Execute: linkloop to remote host. Enter the PPA

(NMID) of your 10/100Base-TX card and link level address (station address) of the remote host in hexadecimal form (preceded by “0x”). Execute lanscan (1M) on the local system to ﬁnd the PPA (NMID) and obtain the link level address (station address) of the remote host. For more information on linkloop, refer to the linkloop(1M) online man page.

B. linkloop successful? If the test was successful, go to

ﬂowchart 1 to verify that the problem is solved. Network connectivity is o.k. through the Link Layer (OSI Layer 2). If not successful, note which error was returned and continue with this ﬂowchart.

C. Loopback failed: Address has bad format. The

link level address is not correct. Go to F.

D. Loopback failed: Not an individual address. The

link level address is not correct. The ﬁrst hexadecimal digit has its high order bit set (if the value is equal to or greater than 8, it is set). This means it is a multicast or broadcast address, which is not allowed. The address must be unique to one remote host. Go to F.

F. Loopback failed. The remote host did not respond.

Go to G. Correct the link address parameter. Change the

link level address to an allowed value and start again with ﬂowchart 7.

G. Choose a different remote host; re-execute

linkloop. Restart ﬂowchart 7 using a different remote host.

H. linkloop successful? If the test was successful, go to

step I. Network connectivity is o.k. through the Link Layer (OSI Layer 2). If not successful, the problem may be with the remote system. Go to ﬂowchart 6.

I. Check remote host's connectivity to

10/100Base-TX. Contact the node manager of the remote host. Check that the host is conﬁgured

78 Chapter4

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

correctly and that its network interface is up. If

necessary, use ﬂowchart 1 to verify conﬁguration of the

remote host.

Chapter 4 79

Figure 4-10

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 8: Transport Level Loopback Test (using ARPA)

Execute: telnet to

remote host

Successful

Execute: ftp to

remote host

Successful

not conﬁgured

on local or

Network

congested

TCP

remote

host

yes

Call HP

Stop

Conﬁgure

TCP

Call HP

80 Chapter4

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 8: Procedures

A. Execute: telnet to remote host. Try to establish a

telnet connection to the remote host. B. Successful? If your telnet attempt was successful,

stop. The connection is o.k. through the Transport

Layer (OSI Layer 4). C. Execute: ftp to remote host. Unlike telnet, ftp does

not go through a pseudoterminal driver (pty) on your

system. This step tests to see if the pty is why telnet

failed. D. Successful? If ftp is successful, you likely have a

problem with a pty on your system. Contact your HP

representative. E. TCP not conﬁgured on local nor remote host?

Neither telnet or ftp will work if TCP is not conﬁgured

on either side of the connection. Check the

/etc/protocols ﬁle on both hosts to be sure TCP is

installed and conﬁgured. F. Network congested? If TCP is installed on both

hosts, do a ﬁle transfer to another remote host on the

network. Use netstat(1) to check for lost packets.

If network congestion is not the cause, more detailed

diagnostics are required. Again, contact your HP

representative. G. Conﬁgure TCP. If necessary, install TCP on either or

both hosts. Start again with this ﬂowchart.

Chapter 4 81

Figure 4-11

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 9: Bridge/Gateway Loopback Test

Execute: ping from

known good host

through gateway to

known good host

Non-HP 9000 or

Refer to networking

other vendors.

documentation

Successful

Examine

gateway

yes

Check route table

on problem host and

all hosts between

If HP 9000

execute: ifconﬁg

on gateway host

Network

interface up

Conﬁgure interface

Correct route

tables

yes

82 Chapter4

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

Flowchart 9 Procedures

A. Execute: ping from known good host through

gateway to known good remote host. This will test

gateway connectivity to the remote network. B. Successful? If the executing ping returned

successfully, the problem may exist in the routing table

for the problem host. Go to C. C. Check route table on problem host and all hosts

in between. Execute netstat -r to examine a route

table. D. Examine gateway. If the gateway is an HP 9000, go

to G. If it is not, go to F. E. Correct route tables. Ensure that the proper

IP/Internet addresses are assigned in the Destination

and Gateway ﬁelds. If you are using subnetting, make

sure that the destination is what you expect: a network

or a host. Go to ﬂowchart 1 to verify that the problem is

solved. F. Non-HP 9000 or other vendors.Refer to

networking documentation. Refer to the

documentation that came with the gateway for

additional diagnostics. G. If HP 9000, execute ifconﬁg on gateway host.

Execute ifconﬁg for all network interfaces on the

gateway. H. Network interface up? If the output from ifconﬁg

does not include the UP parameter, the network

interface is down. Execute netstat -i to check the

status of the network interfaces. An asterisk (*)

indicates that the interface is down. If the network

interface is down, go to I.

If the network interfaces are UP, start again with

ﬂowchart 3. Using ﬂowchart 3, test all network

interfaces on the gateway. I. Conﬁgure interface up. Execute ifconﬁg on each

interface to bring it up. Start again with ﬂowchart 1.

Using ﬂowchart 1, test all network interfaces on the

Chapter 4 83

Troubleshooting 10/100Base-TX/9000

Diagnostic Flowcharts

gateway.

84 Chapter4

A 10/100Base-TX Interface Card

Statistics

This appendix contains descriptions of the RFC 1213 MIB II statistics ﬁelds for LAN interface cards which are displayed on the screen with the

10/100Base-TX Interface Card Statistics

display command in lanadmin LAN Interface Test Mode. A description of each ﬁeld follows the display.

LAN INTERFACE STATUS DISPLAY Tue , Aug 20,1996 11:45:17

Network Management ID = 5 Description = lan3 Hewlett-Packard 10/100Base-TX Half-Duplex Hw Rev 0 Type (value) = ethernet-csmacd(6) MTU Size = 1500 Speed = 100000000 Station Address = 0x80009d40d69 Administration Status (value) = up(1) Operation Status (value) = down(2) Last Change = 0 Inbound Octets = 0 Inbound Unicast Packets = 0 Inbound Non-Unicast Packets = 0 Inbound Discards = 0 Inbound Errors = 0 Inbound Unknown Protocols = 0 Outbound Octets = 0 Outbound Unicast Packets = 0 Outbound Non-Unicast Packets = 0 Outbound Discards = 0 Outbound Errors = 0 Outbound Queue Length = 0 Specific = 655367

Ethernet-like Statistics Group

Index = 3 Alignment Errors = 0 FCS Errors = 0 Single Collision Frames = 0 Multiple Collision Frames = 0 Deferred Transmissions = 0 Late Collisions = 0 Excessive Collisions = 0 Internal MAC Transmit Errors = 0 Carrier Sense Errors = 0 Frames Too Long = 0 Internal MAC Receive Errors = 0

86 AppendixA

10/100Base-TX Interface Card Statistics

RFC 1213 MIB II

For more detailed information about the ﬁelds described below, refer to RFC 1213.

Field Description Network Management ID

A unique ID assigned by the system for the network

management of each network interface.

Description

A textual string containing information about the

interface.

Type (value)

The type of interface, distinguished according to the

physical/link protocols, immediately below the network

layer in the protocol stack.

10/100Base-TX can have one of the following values:

ethernet-csmacd(6), or iso88023-csmacd(7).

The following values are for other networking products.

MTU Size

The size of the largest datagram which can be

sent/received on the interface speciﬁed in octets. This

value is 1500.

Speed in bits per second

The speed of the 10/100Base-TX card, 10 Mbit/s or 100

Mbit/s.

Station Address

The interface address at the protocol layer immediately

below the network layer in the protocol stack. For

interfaces which do not have such an address, such as

serial line, this object contains an octet string of zero

length.

Appendix A 87

10/100Base-TX Interface Card Statistics

RFC 1213 MIB II

Administration Status

The desired state of the interface. This parameter is set to up(1) and is not conﬁgurable. It will have one of the following values:

up(1) Ready to pass packets down(2) Not operative testing(3) In test mode

Operation Status

The current operational state of the interface. This value is the same as the hardware status displayed by lanscan(1M). It will have one of the following values.

up(1) Ready to pass packets down(2) Not operative (card is down) testing(3) In test mode

Last Change

The value of SysUpTime at the time the interface entered its current operational state. If the current state was entered prior to the last reinitialization of the local network management subsystem, then this object contains a zero value.

Inbound Octets

The total number of octets received on the interface, including framing characters.

Inbound Unicast Packets

The number of subnetwork-unicast packets delivered to a high-layer protocol.

Inbound Non-Unicast Packets

The number of non-unicast (subnetwork-broadcast or

88 AppendixA

subnetwork-multicast) packets delivered to a

higher-layer protocol.

Inbound Discards

The number of inbound packets that were discarded

even though no errors had been detected, to prevent

their being delivered to a higher-layer protocol. One

possible reason for discarding such a packet could be to

free up buffer space.

Inbound Errors

The number of inbound packets that contained errors

preventing them from being deliverable to a

higher-layer protocol.

Inbound Unknown Protocols

The number of packets received via the interface which

were discarded because of an unknown or unsupported

protocol.

Outbound Octets

10/100Base-TX Interface Card Statistics

RFC 1213 MIB II

The total number of octets transmitted out of the

interface, including framing characters.

Outbound Unicast Packets

The total number of packets that higher-level protocols

requested be transmitted to a subnetwork-unicast

address, including those that were discarded or not

sent.

Outbound Non-Unicast Packets

The total number of packets that higher-level protocols

requested be transmitted to a non-unicast (a

subnetwork-broadcast or subnetwork-multicast)

address, including those that were discarded or not

sent.

Outbound Discards

The number of outbound packets that were discarded

even though no errors had been detected to prevent

their being transmitted. One possible reason for

discarding such a packet could be to free up buffer

Appendix A 89

10/100Base-TX Interface Card Statistics

RFC 1213 MIB II

space.

Outbound Errors

The number of outbound packets that could not be transmitted because of errors.

Outbound Queue Length

The length of the output packet queue (in packets).

90 AppendixA

10/100Base-TX Interface Card Statistics

RFC 1284 Ethernet-Like Interface Statistics

Field Description Index

A value that uniquely identiﬁes an interface to an

802.3 medium.

Alignment Errors

A count of frames received on a particular interface

that are not an integral number of octets in length and

do not pass the FCS check.

FCS Errors

A count of frames received on a particular interface

that are not an integral number of octets in length and

do not pass the FCS check.

Single Collision Frames

A count of successfully transmitted frames on a

particular interface for which transmission is inhibited

by exactly one collision.

Multiple Collision Frames

A count of successfully transmitted frames on a

particular interface for which transmission is inhibited

by more than one collision.

Deferred Transmissions

A count of frames for which the ﬁrst transmission

attempt on a particular interface is delayed because

the medium is busy. The count represented by an

instance of this object does not include frames involved

in collisions.

Late Collisions

The number of times that a collision is detected on a

particular interface later than 512 bit-times into the

transmission of a packet.

Excessive Collisions

Appendix A 91

10/100Base-TX Interface Card Statistics

RFC 1284 Ethernet-Like Interface Statistics

A couple of frames for which transmission on a particular interface fails due to excessive collisions in 10-Base-T mode. For 100Base-TX mode, excessive collisions indicate the number of packets dropped.

Internal MAC Transmit Errors

A count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error.

Carrier Sense Errors

The number of times that the carrier sense condition waslost or never asserted when attempting to transmit a frame on a particular interface.

Frames Too Long

A count of frames received on a particular interface that exceed the maximum permitted framer size.

Internal MAC Receive Errors

A count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error.

92 AppendixA

10/100Base-TX Interface Card Statistics

Create a Record or Map of Your Internetwork

Be sure to create or update a record of your network and internetwork before attempting 10/100Base-TX installation. You may wish to create a map showing how pieces of your internetwork are related. Your records should include:

• Approximate dimensions of the building or room containing the

10/100Base-TX network.

• Location of, routers, bridges, and gateways

• Location of nodes and node connections.

• Location of network segments and subnets within each segment

• Hostname of each node.

• Internet Address and Alias of each node (in the case of gateways, each

10/100Base-TX card has its own Internet Address and Alias).

• Hardware Path of each card in the system including 10/100Base-TX

cards. You can use this information as part of a disaster recovery plan.

• Version number of the operating system installed on each node.

Appendix A 93

10/100Base-TX Interface Card Statistics

Create a Record or Map of Your Internetwork

94 AppendixA

B Hardware Reference

Information

This appendix contains information about the card LEDs, cabling speciﬁcations and card speciﬁcations.

Hardware Reference Information

Basic Troubleshooting Tips

Listed below are some tips on troubleshooting common hardware problems. Refer to this information when you are trying to identify 10/100Base-TX hardware problems.

• Check the network cables. Make sure the network cable connections are secure and that the cables are not damaged. If you ﬁnd any connections that are loose, or cables that are damaged, ﬁx the problem and then see if your computer can communicate on the network

• Check the LEDs. The six LEDs on the LAN card bulkhead can be used to help identify the problem. Figures 3 through 7 will help you to interpret the LED display.

Refer to the ﬁgure below to interpret the LEDs on the front of the card.

Figure B-1 LED Display for 10 or 100 Mbit/s Normal Operation

Power

RJ-45 Connector (TX)

100-Mbit/s Indicator

Activity

(On=Data transmitted/received)

10 or 100 Mbit/s

Refer to the following picture to see how the LEDs indicate a 10 or 100 Mbit/s fault condition. Note that if either the Link Status LED is OFF or

96 AppendixB

= LED ON = LED OFF

Test (On=fail;Off=pass)

10-Mbit/s Indicator(On for 10Mbit/s) Link Status (On=link established)

Hardware Reference Information

Basic Troubleshooting Tips

if the Test LED is ON, this indicates a fault. The possible causes of a fault condition could be:

• Defective cable

• Cable not connected to active hub or switch

• Defective card

NOTE If the Link LED is ON and the Test LED is OFF and there still is a fault,

at the HP-UX command line, type: dmesg and view the output on your screen to see if any error messages exist.

Figure B-2 LED Display Indicating Fault Conditions for 10 or 100 Mbit/s

Card

= LED ON

= LED OFF

Power

RJ-45 Connector (TX)

100-Mbit/s Indicator = ON

Activity = OFF

Appendix B 97

Test LED=ON

10-Mbit/s Indicator(ON for 10Mbit/s)

Link Status LED = OFF

10 or 100 Mbit/s

Hardware Reference Information

Meaning of LEDs

Following is a summary of the purpose of the front-panel LEDs.

If this LED is ON... It means this ...

Power The card’s power is on. Test The card has not passed its initialization

sequence. 10 Operating at 10 Mbit/s 100 Operating at 100 Mbit/s Link Link established with hub or switch. Activity Data transmitted/received.

98 AppendixB

Hardware Reference Information

Connector Information

This section includes pin usage information for the RJ-45 twisted pair connector. Connectors on LAN adapters adhere to appropriate standards agreed upon by various standards bodies and are widely available.

Incorrectly wired or installed cabling is the most common cause of communications problems for local area networks. HP recommends that you work with a qualiﬁed cable installer for assistance in your cabling requirements.

CAUTION The unshielded twisted-pair cables you use with the HP-PB

10/100Base-TX card must comply with the IEEE 802.3u 100Base-TX standards in order to meet emissions requirements. These standards support cabling up to 100 meters only.

HP-PB 10/100Base-TX Card Twisted-Pair Connector

There is only one connector on the card that is used for either 10Base-T or 100Base-TX operation. The operating mode is determined by the

setting of the hub or switch to which the card is connected.

Connector Pin Usage for 10-Mbit/s Twisted-Pair Connector

Use unshielded twisted-pair cables that comply with the IEEE 802.3 Type 10Base-T standard.

Table B-1 IEEE 802.3 Type 10Base-T Standard

Pins Signal

1 2

Appendix B 99

(transmit +) (transmit -)

Hardware Reference Information

Connector Information

Table B-1 IEEE 802.3 Type 10Base-T Standard

Pins Signal

3 6

Figure B-3 Pin Layout of RJ-45 Connector on HP-PB Card

Available HP Cables:

• HP 92268A - 4 meter with attached 8-pin connectors.

• HP92268B - 8-meter with attached 8-pin connectors.

• HP 92268C - 16-meter with attached 8-pin connectors.

• HP 92268D - 32-meter with attached 8-pin connectors.

(receive +) (receive -)

• HP 92268N- 300-meter (no connectors supplied).

Connector Pin Usage for 100-Mbit/s Twisted-Pair Connector

Use Category 5 unshielded twisted-pair cables that comply with the IEEE 802.3u 100Base-TX standard.

100 AppendixB

HP HP-PB 10 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual