Fddi

PCI FDDI Administrator’s Guide HP-UX 11.0, 11i v1, 11i v1.5, and 11i v2 Edition 2

Manufacturing Part Number: J3626-90033 August 2003

United States © Copyright 2003 Hewlett-Packard Development Company L.P. All rights reserved.

Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty A copy of the specific warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtained from your local Sales and Service Office. U.S. Government License Proprietary computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Copyright Notice Copyright  1997-2003 Hewlett-Packard Development Company L.P. All rights reserved. Reproduction, adaptation, or translation of this document without prior written permission is prohibited, except as allowed under the copyright laws. Use of this manual and flexible 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. ©copyright 1979, 1980, 1983, 1985-93 Regents of the University of California This software is based in part on the Fourth Berkeley Software Distribution under license from the Regents of the University of California. 2

©copyright 1980, 1984, 1986 Novell, Inc. ©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 © xntpd is a 1992 copyright of David L. Mills. © INN is a 1993 copyright of Richard Salz. 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.

Safety and Regulatory Information This product was tested for conformance to various national and international regulations and standards. The scope of this regulatory testing includes electrical and mechanical safety, electromagnetic emissions, immunity, acoustics, and hazardous materials.

3

When required, approvals are obtained from third party test agencies. Approval marks appear on the product label. In addition, various regulatory bodies require some information under the headings noted below.

Safety Symbols WARNING

A WARNING denotes a hazard that can cause personal injury.

CAUTION

A CAUTION denotes a hazard that can damage equipment.

FCC Statement (USA only) The United States Federal Communications Commission (FCC) has specified that the following notice be brought to the attention of users of this product: FCC rules part 15, subpart A, class A devices. Information to User (section 15.105) This device complies with part 15 of the FCC rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference recieved, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits of a Class A digital device, pursuant to part 15 of FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy, and

4

if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his own expense. Any changes or modifications not expressly approved by Hewlett-Packard could void the user’s authority to operate this equipment. Use of shielded interface cables is required to comply within the Class A limits in part 15 of the FCC rules.

DOC Statement (Canada only) This Class A digital apparatus meets all the requirements of the Canadian Interference-Causing Equipment Regulations. Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada.

Europe RFI Statement This is a Class A product. In a domestic environment, this product may cause radio interference, in which case the user may be required to take adequate measures.

Australia and New Zealand EMI Statement This product meets the applicable requirements of the Australia and New Zealand EMC Framework. 5

Radio Frequency Interference (Japan Only) VCCI, Class A (Model A4891-62001 only)

6

Declaration of Conformity

7

Cable Information Below are cable specifications for the PCI FDDI Dual Attach adapter. Product safety and/or regulatory conformance may depend upon observance of the following information. A and B Port Connections The A and B ports on the adapter require one (SAS) or two (DAS) standard 62.5/125 multimode fibre optic cable(s) with an SC-Duplex connector. These cables are not provided and must be furnished by the customer. For existing installations that use cables with MIC (Media Interface Connector) connectors, SC to MIC cable adapter cables must be ordered by specifying “Option 001”.

WARNING

Never look directly into an optical fiber port. While not used or supported by this adapter, some fiber optic equipment can emit laser light that can injure your eyes. Always assume the cable is connected to a light source.

Optical Bypass Relay Connection The Optical Bypass Relay (OBR) connector allows the OBR device to maintain integrity of the dual FDDI rings if the adapter fails or if system power is removed. The OBR connector is an RJ-12 modular jack connector. The pin assignments (counting from right to left, with pin 1 in the rightmost position) are described in the list below.

WARNING

Do not insert telecommunications cabling into the optical bypass relay connector.

OBR RJ-12 Connector Pin Assignments Pin 1, 2: Relay drive +5.0 V dc Pin 3, 4: Bypass enable Pin 5: Bypass present Pin 6: Return grounded internally

8

Operating Environment The list below shows the recommended operating environment for the PCI FDDI Dual Attach Adapter.

Operating Environment Operating Temperature Range: 5 to 30 degrees C Non-operating Temperature Range: -40 to 70 degrees C Recommended Operating Temperature Range: 20 to 30 degrees C Temperature Shock Immunity (Max rate of change): 20 degrees C Non-operating Humidity Range: 15 to 90% RH Operating Humidity Range @ 22 degrees C: 15 to 80% RH Recommended Operating Humidity Range @ 22 degrees C: 15 to 80% RH Recovery Procedure from Condensation: None

9

10

Contents 1. PCI FDDI The PCI FDDI Adapter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FDDI Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FDDI Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCI FDDI Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ANSI FDDI Standards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FDDI Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stand-alone Concentrator Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tree of Concentrators Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dual Ring Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dual Ring of Trees Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dual Homing Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCI FDDI Adapter & Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCI FDDI Adapter Cards: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCI FDDI Adapter Software Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCI FDDI Adapters Supported on HP Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCI FDDI Adapters Supported on HP Workstations . . . . . . . . . . . . . . . . . . . . . . . . . PCI FDDI Adapter Features and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Administration Manager (SAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Management Using the PCI FDDI Subagent . . . . . . . . . . . . . . . . . . . . . . . . . Important Terms and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for Using Subagent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On Line Addition and Replacement (OLA/R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software and Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What’s Different in PCI FDDI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contacting Your HP Representative . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

20 20 21 23 24 24 26 26 27 27 28 29 30 30 31 31 32 32 34 36 36 36 38 38 40 42

2. Installing and Configuring PCI FDDI PCI FDDI Adapter Installion Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 - Verify Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - Load the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - Install the Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - Verify Adapter Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - Connect the Adapter to the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5a - Cables and Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

47 48 49 51 53 55 57

11

Contents 5b - Handling the Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5c - Attach the Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5d - Normal LED, Ring Management and Configuration States . . . . . . . . . . . . . . . . 6 - Configure the Adapter Using SAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - Configure the Adapter and Verify For Network Connectivity . . . . . . . . . . . . . . . . .

58 59 60 61 62

3. Troubleshooting PCI FDDI Troubleshooting Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Man Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Adapter Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Network Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Diagnostic Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 fddipciadmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 dmesg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 arp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 ifconfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 ioscan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 lanadmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 lanscan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 linkloop(1M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 netstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 nettl, netfmt, nettladm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Diagnostic Flowcharts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Flowchart 1: Link Level Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Flowchart 2: Network Level Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Flowchart 2a: arp Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Flowchart 2b: ping Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Flowchart 3: Transport Level Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Flowchart 4: Bridge/Gateway Loopback Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Flowchart 5: Configuration Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Flowchart 5a: lanscan and ioscan Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Flowchart 5b: netfmt and lanadmin Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Flowchart 5c: ifconfig Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

12

Contents Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

13

Contents

14

About This Document This guide provides the user with the FDDI concepts, features and limitations of the PCI FDDI Adapter, and installation procedure, configuration summary, troubleshooting utilities and support tools.

15

This guide also covers step-by-step procedures for installation of the adapter and it’s software found in chapter 2 of this manual. Flow charts of the diagnostics have been provided in chapter 3. The intention of this document is to provide key support information for the HP customer to be used in conjunction with the Quick Configuration card as the primary reference for ICVT steps (installing, configuring, verification and basic trouble-shooting). This document does not describe how to install/remove PCI controller cards in the various classes of servers. This topic is covered in their respective Service Guides and Electronic Performance Support System (EPSS) CDs.

Intended Audience This guide is intended for anyone who needs to install and/or configure the PCI FDDI Adapter cards and the included software. This document is not a tutorial.

What’s in This Document The manual is organized according to the sections listed below. Table 1

Organization Chapter

16

Description

PCI FDDI

This chapter provides the user with the FDDI concepts and an overview of the PCI FDDI adapter card and included software.

Installing and Configuring PCI FDDI

Describes the steps to install and configure PCI FDDI

Troubleshooting PCI FDDI

Provides references to other useful tools for installing, configuring, and maintaining HP Token Ring software

Troubleshooting Token Ring

Provides instructions to troubleshoot PCI FDDI with procedures and flowcharts to help diagnose PCI FDDI software and hardware problems

Typographical Conventions This document uses the following conventions. audit (5)

An HP-UX manpage. In this example, audit is the name and 5 is the section in the HP-UX Reference. On the web and on the Instant Information CD, it may be a hot link to the manpage itself. From the HP-UX command line, you can enter “man audit” or “man 5 audit” to view the manpage. See man (1).

Book Title

The title of a book. On the web and on the Instant Information CD, it may be a hot link to the book itself.

KeyCap

The name of a keyboard key. Note that Return and Enter both refer to the same key.

Emphasis

Text that is emphasized.

Bold

Text that is strongly emphasized.

Bold

The defined use of an important word or phrase.

ComputerOut

Text displayed by the computer.

UserInput

Commands and other text that you type.

Command

A command name or qualified command phrase.

Variable

The name of a variable that you may replace in a command or function or information in a display that represents several possible values.

[ ]

The contents are optional in formats and command descriptions. If the contents are a list separated by |, you must choose one of the items.

{ }

The contents are required in formats and command descriptions. If the contents are a list separated by |, you must choose one of the items.

...

The preceding element may be repeated an arbitrary number of times.

|

Separates litems in a list of choices.

17

NOTE

All the occurances of the term, HP-UX Systems in this document refer to HP Integrity servers and workstations, unless explicitly stated otherwise.

HP-UX Release Name and Release Identifier Each HP-UX 11i release has an associated release name and release identifier. The uname (1) command with the -r option returns the release identifier. This table shows the releases available for HP-UX 11i. Table 2

HP-UX 11i Releases Release Identifier

Release Name

Supported Processor Architecture

B.11.11

HP-UX 11i v1

PA-RISC

B.11.20

HP-UX 11i v1.5

Intel Itanium

B.11.22

HP-UX 11i v1.6

Intel Itanium

B.11.23

HP-UX 11i v2.0

Intel Itanium

Related Documents The following documentation is available with the PCI FDDI software in print, on the Instant Information CD, or on the HP web site http://www.docs.hp.com, under Networking & Communications: •

PCI FDDI Release Notes

HP Encourages Your Comments HP encourages your comments concerning this document. We are truly committed to providing documentation that meets your needs. Please send comments to: [email protected] Please include document title, manufacturing part number, and any comment, error found, or suggestion for improvement you have concerning this document. Also, please include what we did right so we can incorporate it into other documents.

18

1

PCI FDDI This chapter provides the user an overview of the PCI FDDI adapter card, FDDI concepts, PCI FDDI devices, standards, terms, topologies, support, and other related information.

Chapter 1

19

PCI FDDI The PCI FDDI Adapter Overview

The PCI FDDI Adapter Overview The PCI FDDI adapter is a high-speed network link offering both single-attach connections and dual attach connections to a Fiber Distributed Data Interface dual-ring network that complies with the ANSI standards (ANSI X3T9.5) for FDDI. This product consists of a PCI FDDI adapter and its driver, developed by Hewlett-Packard. The current PCI FDDI adapter is Hewlett-Packard part number A3739B. It supports dual voltage 3.3 and 5 volts. The A3739B adapter card is not supported on workstations earlier than B1000, C3000, and J5000. The previous PCI FDDI adapter version A3739A is a 5 volt card, which has been obsoleted, but still fully supported by the 11i operating system. The PCI FDDI adapter can be connected directly to adjacent stations on a dual-ring network or to a concentrator. It is customer-installable on any class system supporting PCI except V-Class and Superdome, and supports the standard HP link tools on all of the systems. The PCI FDDI adapter uses fiber optic cables, and SC connectors. The dual-attachment can be run in single-attach mode by connecting one cable.

FDDI Concepts The Fiber Distributed Data Interface (FDDI) is a high speed local area network, defined by the standard from the American National Standards Institute committee, ANSI X3T9.5 and by ISO. The FDDI interface (single or dual) can be implemented with Fiber Optic or Unsheilded Twisted-Pair cabling.

NOTE

20

The HP implementation of the PCI FDDI interface is Fiber Optic only.

Chapter 1

PCI FDDI FDDI Architecture A Timed Token Protocol (TTP) is used to control when a station can transmit data to the network. A station can transmit until the message is transmitted or until the TTP timer expires. This allows all stations fair access to the ring. Once the message is sent or the timer expires, the station generates a new token and releases it on the ring. Any downstream station with data to send can capture the token and repeat the timed-transmission cycle. A dual ring configuration for the network media provides a secondary backup ring in case of a fault on the primary ring. It is typically implemented as a campus backbone or within buildings where a failure in the primary ring would have serious consequences. A break in the primary ring causes the two stations on each side of the fault to automatically wrap the data to the secondary ring. Stations in a single ring configuration can only attach to the primary ring. No secondary backup path is available in the event of a failure. The PCI FDDI standard pertains to the Physical and Data Link layers of the OSI model.

Table 1-1

Physical and Data Link Layers - OSI Model Data Link

802.2 Logical Link Control (LLC) Media Access Control - (MAC)

Physical

Physical Layer Protocol (PHY)

Station Management

Physical Layer Medium Dependent (PMD)

FDDI Architecture The following figure shows the FDDI architecture and the most commonly used topologies.

Chapter 1

21

PCI FDDI FDDI Architecture Figure 1-1

22

A Typical FDDI Network Layout

Chapter 1

PCI FDDI PCI FDDI Devices

PCI FDDI Devices To promote ease of installation and maintenance, PCI FDDI allows for several types of networking devices. These include dual ring and single ring concentrators and stations. Concentrators are the building blocks of a PCI FDDI network. Stations and concentrators connect to the PCI FDDI ring as follows: •

Dual Attachment Concentrators (DAC): Connects to the dual ring and serves as a hub for single or dual attachment devices. It also allows stations to be added and removed from the ring with minimal interruption of network traffic.

•

Single Attachment Concentrator (SAC): Connects to the primary ring through a DAC and serves as a single ring hub. SACs can be stacked to form a span of trees topology.

•

Dual Attachment Station (DAS): Connects to a dual ring. Both primary and secondary paths are connected.

•

Single Attachment Station (SAS): Connects only to the primary ring. Generally, a SAS connects to the PCI FDDI ring through a DAC.

Network designers and administrators are given the opportunity to balance the costs of installation and operation with the quality of service demanded by each segment. For example, a dual set of fiber running between stations is much more expensive than connecting the stations with a single fiber. Thus, a dual ring topology is typically used for major backbones in the system. Single rings are generally used to branch off the backbone to various workgroups and peripheral installations. DAC and DAS connect directly to the PCI FDDI dual ring while SAC and SAS only connect to a single, primary ring. Dual attachment does not provide greater performance than single attachment. It only provides a secondary means of communication in case of a failure on the primary ring.

Chapter 1

23

PCI FDDI ANSI FDDI Standards

ANSI FDDI Standards Listed below are the four ANSI FDDI standards and how they combine to form a completely functional fiber optic network. The physical layer includes two pieces, the Physical Medium Dependent (PMD) layer that provides the point-to-point communications between stations in the network, and the Physical Layer Protocol (PHY) layer that handles synchronization between higher layer data and control symbols, and the code bit representation which is transmitted on the medium. The data link layer includes the Media Access Control (MAC) standard and the Logical Link Control (LLC) standard. The MAC’s primary function is the scheduling, routing and delivery of Frames, the vehicle used to transmit information on and off the ring. In a FDDI network, information is transmitted sequentially, within frames, as a stream of encoded symbols from one station to the next. The order of the symbols within the frames is predetermined by the MAC standard. The LLC provides a common protocol between the MAC and the network layer. In addition to FDDI, the LLC standard also applies to IEEE 802.3, 802.4 and 802.5 networks. The Station Management (SMT) standard is a layer management entity which interfaces with the other sublayers. It manages connections with the ring as well as station configurations and the ring configuration.

FDDI Terminology Table 1-2

24

Dual Attachment Concentrator (DAC)

A concentrator that offers two connections to the FDDI network capable of accommodating the FDDI dual ring and additional ports for other concentrators or FDDI stations.

Dual Attachment Station (DAS)

A FDDI station that offers two connections to the FDDI dual ring.

Chapter 1

PCI FDDI FDDI Terminology Table 1-2

Chapter 1

(Continued) Single Attachment Concentrator (SAC)

A concentrator that offers one S port (slave port) for attachment to the FDDI network and M ports (master port) for the attachment of stations or other concentrators.

Single Attachment Station (SAS)

A FDDI station that offers one S port (slave port) for attachment to the FDDI ring.

Optical Bypass Relay

A mechanism used to bypass a station that is turned off or disconnected, protecting against multiple faults on a dual ring.

Dual Homing

A method of cabling concentrators and stations that permits an alternate or backup path to the dual ring in case the primary connection fails.

Dual Ring

A FDDI network topology that uses two redundant rings to overcome fiber-optic failures between two nodes.

Dual Ring of Trees

A topology of concentrators and nodes that cascade from concentrators on a dual ring.

SC Connectors

Duplex-style connectors where the two fiber leads snap together to form a keyed connection.

Fiber Optic Cable

A transmission medium designed to transmit digital signals in the form of pulses of light.

25

PCI FDDI Topology

Topology Stand-alone Concentrator Topology The stand-alone topology consists of a single concentrator and its attached stations. The stations can be either single-attach or dual-attach devices. They do not require access to the dual ring. They can communicate with each other through the stand-alone concentrator. Figure 1-2

26

Chapter 1

PCI FDDI Topology

Tree of Concentrators Topology In the tree of concentrators topology, concentrators are wired in a hierarchical star topology with one concentrator serving as the root of the tree. This topology provides great flexibility in adding and removing stations, and changing the LAN without causing disruption. Figure 1-3

Dual Ring Topology The dual ring topology consists of a primary ring and a secondary ring. This topology does not easily accommodate additions, moves and changes. It is only used with dual-attached stations. If a second fault occurs, the ring will segment.

Chapter 1

27

PCI FDDI Topology Figure 1-4

Dual Ring of Trees Topology The dual ring of trees is the most flexible and the most recommended topology. It provides a high degree of fault tolerance. Concentrators form tree branches that can be extended as long as the station number or ring distance limits are not exceeded. Station removal or change can be easily done without causing disruption to the LAN.

28

Chapter 1

PCI FDDI Topology Figure 1-5

Dual Homing Topology For dual homing using two concentrators, two sets of cables are attached to the PCI FDDI adapter.

Chapter 1

•

Connect the adapter’s B-port to an M-port on one concentrator.

•

Connect the adapter’s A-port to an M-port on the second concentrator.

29

PCI FDDI PCI FDDI Adapter & Support •

The B-port functions as the active (primary) port and the A-port functions as a standby (secondary) in the event that the active concentrator or B-port link fails.

Figure 1-6

PCI FDDI Adapter & Support The following describes the HP product and part numbers for the PCI FDDI adapter, with the associated servers and workstations.

PCI FDDI Adapter Cards: The current PCI FDDI LAN adapter card is version A3739B. The A3739A version of the PCI FDDI adapter card has been obsoleted, but is fully supported by the 11i operating system.

The PCI FDDI adapter comes with 2 SC-MIC cables.

30

Chapter 1

PCI FDDI PCI FDDI Adapter & Support Figure 1-7

PCI FDDI Adapter Software Manual The Adapter Software manual is also available separtely. •

HP part Number J3628AA

PCI FDDI Adapters Supported on HP Servers The following are the servers that support PCI FDDI adapters.

Chapter 1

•

A-Class

•

N-Class

•

L-Class

•

V-Class

•

Superdome

•

rx2600

•

rx56XX

•

rx4640

•

rx8620

31

PCI FDDI PCI FDDI Adapter Features and Limitations •

SD16A

•

SD32A

•

SD64A

PCI FDDI Adapters Supported on HP Workstations The following are the PCI FDDI adapters supported on HP workstations running HP-UX 10.20, 11.0, 11i v1, or 11i v2: •

B-Class

•

C-Class

•

J-Class

•

zx2000

•

zx6000

FDDI PCI adapter version A3739B is not supported on workstations earlier than:

NOTE

•

B1000

•

C3000

•

J5000

HP 9000 EISA card has been obseleted. HP-UX 10.20 has been obseleted starting July 2003. V-class systems have been obseleted starting September 2000.

PCI FDDI Adapter Features and Limitations

32

•

Dual-attach (with single-attach capabilities)

•

Dual-homing support

•

Dual-signaling (3.3v and 5v) support (A3739B) Chapter 1

PCI FDDI PCI FDDI Adapter Features and Limitations

Chapter 1

•

928kb Packet memory

•

Optical-bypass switch support

•

MP (Multi-processor) safe

•

MP scalability

•

SAM interface configuration support

•

On Line Addition and Replacement (OLA/R)

•

DLPI Interface support

•

SMT support

•

Programmatic access to 7.3 statistics

•

Supports TCP/IP

•

Supports NFS and Internet Services

•

SNA support

•

High Availability/Service Guard Support

•

Promiscuous (link and SAP)

•

Supports STM (Support Tools Manager diagnostic tool) and other Administration Support Tools

•

Supports point-to-point connections (only two stations on a ring).

•

There are no switches or jumpers to be set on this card. Configuration is done with SAM.

•

The PCI FDDI adapter has two LEDs (B and A ports).

•

Subagent Support

33

PCI FDDI System Administration Manager (SAM)

System Administration Manager (SAM) SAM is a menu-driven utility for system administration tasks, including configuration of software. The following instructions describe how to configure the PCI FDDI adapter on HP-UX. To determine the operating system version you are using, type the following command: uname -a Once you have installed the PCI FDDI adapter and software, you can use SAM to automatically configure networking. SAM has two user interfaces, an X-Windows system interface and a text terminal interface. The primary components and functionality of SAM are the same for both interfaces. The differences are the screen appearance and navigation methods. Using the SAM Online Help System: •

Choose an item from the “Help” menu (located in the menu bar). This gives you information about the current SAM screen, keyboard navigation within SAM, using the SAM help system, and displaying the version of SAM you are currently running.

•

Activate the HELP button from a dialog or message box. This gives you information about the attributes and tasks you can do from the currently displayed window.

•

Press the F1 key. This gives you context-sensitive information for the object at the location of the cursor.

Configuring the PCI FDDI adapter can be divided into three procedures: 1. Configuring the FDDI link and specific parameters supported on HP-UX 11i only: — — — —

MAC address MTU T_Req T_Notify

2. Configuring IP address and subnet mask on the PCI FDDI link for HP-UX 10.20 and 11.x.

34

Chapter 1

PCI FDDI System Administration Manager (SAM) This step will add the IP address and any alias names if the PCI FDDI adapter card is on a subnetwork and the subnet mask for your adapter card. This procedure will automatically initialize the PCI FDDI link and attach your node to the local network (LAN). 3. Configuring remote host names and addresses and gateway default information for 10.20, 11.0 and 11i. Steps 2 and 3 will add remote system names and remote system IP addresses for network connectivity, and to specify default gateway information.

NOTE

Using SAM is the preferred method for PCI FDDI configuration. However, SAM currently does not support the domain name format. The domain name format is used with the BIND name service provided with Internet Services/9000. Using the BIND name service, the Network Interface Card can be configured, but the remote connectivity cannot. You may want to configure PCI FDDI manually. See the Installing and Administering LAN/9000 manual for detailed instructions on how to install and configure software manually. Refer to chapter 2 of this manual for PCI FDDI-specific configuration information.

Chapter 1

35

PCI FDDI Network Management Using the PCI FDDI Subagent

Network Management Using the PCI FDDI Subagent The PCI FDDI subagent is a daemon which will service the request for FDDI MIB (Management Information Base) corresponding to the PCI FDDI cards in the system. The Subagent feature is for HP-UX 10.20 and 11.x.

Important Terms and Definitions •

SNMP: Simple Network Management Protocol. See RFC1155, RFC1157, RFC1212, RFC1902.

•

Master Agent: This is the master agent which directly communicates with the management application, and decides which subagent to forward the request to. It performs authentication, packet receiving and sending.

•

SMT: Station Management. Station Management manages the three protocol layers of a FDDI station; MAC, PHY and PMD. SMT is a subset of network management that allows initialization, control and monitoring of hardware components related to the PCI FDDI protocol layers.

•

FDDI-MIB: FDDI Management Information Base. See RFC1512.

Requirements for Using Subagent The HP OpenView product is recommended, but you can use other SNMP managers to communicate with the subagent using manager applications (xnmbrowser) and commands. Use Managing HP-UX Software with SD-UX for HP-UX 11i as a reference guide for Patch installations. The HP OpenView Extensible SNMP Agent provides a good description for configuration. These documents can be obtained from http://doc.hp.com. OLA/R Specific (see next page) See the section on the following page for an explanation of OLA/R.

36

Chapter 1

PCI FDDI Network Management Using the PCI FDDI Subagent When new cards are added online with SAM, the subagent will automatically be restarted. If new cards are added using rad(1M) or olrad(1M), the PCI FDDI subagent must be manually restarted.

Chapter 1

37

PCI FDDI On Line Addition and Replacement (OLA/R)

On Line Addition and Replacement (OLA/R) This refers to the ability of a PCI I/O card to be replaced or added to an HP-UX computer system designed to support this feature without the need for completely shutting down, then re-booting the system or adversely affecting other system components. The system hardware uses the per-slot power control combined with operating system support to enable this feature. This feature is only supported on systems that run the HP-UX 11i operating system.

IMPORTANT

Certain “Classes” of hardware are not intended for access by users. HP recommends that V-Class and Superdome systems only be opened by a qualified HP engineer. Failure to observe this requirement can invalidate any support agreement or warranty to which the owner might otherwise be entitled.

The addition or replacement of an OLA/R-compatible card may be done in either of two ways: 1. Using the SAM utility. 2. Issuing command-line commands using rad(1M) or olrad(1M) (orlad (1M) is specificically for HP-UX 11i v2). Refer to Configuring HP-UX For Peripherals, HP Part Number B2355-90698. This document may be ordered from HP, or you may view, download and print it from: http://docs.hp.com

Software and Hardware Requirements •

HP-UX 11.x 64-bit operating system HP-UX 11.x 32-bit operating system

38

Chapter 1

PCI FDDI Software and Hardware Requirements HP-UX 10.20 32-bit operating system

Chapter 1

•

Fiber optic cables terminated with an SC connector

•

CD-ROM drive or website: http://software.hp.com to install/update the current version of media/drivers

•

16 MB memory, or more

•

700 KB free disk space, or more

39

PCI FDDI What’s Different in PCI FDDI

What’s Different in PCI FDDI •

Optical Bypass Relay: The OBR control port is RJ-12; this adapter uses SC connectors. The two 12-inch SC-MIC cable adapters (A4700-67073) can be ordered with the card for connecting the PCI FDDI card to a MIC device using MIC-to -MIC cables.

•

New Driver: Both A3739A and A3739B use the software driver fddi4, and the device files are: /dev/lanx. All FDDI drivers are shipped on the HP-UX Application Release (AR) CD. They can also be obtained from http://www.hp.com.

•

LEDs: The PCI FDDI adapter has two LEDs (B and A ports). When the driver is installed and the port(s) are connected to the network, the LED displays should be a follows: — Dual-Attach Station B and A: continuous green (not flashing). — Single-Attach Station The LED for the attach port: continuous green. The LED for the unused port: flashing green. — Dual-homed topology B: continuous green A: alternating green/amber (standby)

40

•

linkloop(1M): If you execute linkloop(1M) back to the local interface’s own MAC address (linkloop(1M) to self), the local driver will send a response. No hardware exercised.

•

New Diagnostics Utility: Use the utility fddipciadmin to report card, driver and network statistics. Refer to the fddipciadmin(1M) and fddi (7) man pages.

•

Logging: The PCI FDDI driver logs events using nettl (not syslog).

•

New nettl entity: You can specify the entity PCI_FDDI when enabling logging/tracing or as a netfmt filter.

Chapter 1

PCI FDDI What’s Different in PCI FDDI As with other FDDI drivers, only data packets are traced. You must use an Internet Advisor (J2173C) to view Station Management (SMT) packets.

Chapter 1

41

PCI FDDI Contacting Your HP Representative

Contacting Your HP Representative If you do not have a service contract with HP, you may follow the procedure described below, but you will be billed accordingly for time and materials. If you do 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 and symptoms leading up to the problem. Your characterization should include: HP-UX commands, communication subsystem commands, functionality of user programs, result codes and messages and data that can reproduce the problem.

•

Obtain the version, update and fix information for all software. What /stand/vmunix | grep

adapter_number

Where the adapter_number is one of the following: — A3739A (obsolete, but still supported) for PCI FDDI on servers and workstations. — A3739B for PCI FDDI on servers and workstations.

42

•

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.

•

Illustrate as clearly as possible the context of any message(s). Record all error messages and numbers that appear at the user terminal and the system console.

•

Save all network log files.

•

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

•

Prepare a listing of the HP-UX I/O configuration you are using for your HP representative to further analyze.

Chapter 1

PCI FDDI Contacting Your HP Representative

Chapter 1

•

Try to determine the general area within the software where you think the problem exists. Refer to this document to gather information on your product.

•

Document your interim or “work-a-round” 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 a copy of any PCI FDDI link trace files that were active when the problem occurred for your HP representative to further analyze.

•

In the event of a system failure, obtain a full memory dump. If the directory /var/adm/crash exists, the HP-UX utility /sbin/savecore automatically executes during reboot to save the memory dump. Hewlett-Packard recommends that you create the /tmp/syscore directory after successfully installing this product. Send the output of your system failure memory dump to your HP representative.

43

PCI FDDI Contacting Your HP Representative

44

Chapter 1

2

Installing and Configuring PCI FDDI This chapter describes how to install and configure PCI FDDI adapter software and hardware onto your HP-UX system for the 10.20 and 11x

Chapter 2

45

Installing and Configuring PCI FDDI

operating systems.

46

Chapter 2

Installing and Configuring PCI FDDI PCI FDDI Adapter Installion Overview

PCI FDDI Adapter Installion Overview This section is a brief summary of the installation and configuration procedures that follow:

IMPORTANT

This adapter is not customer-installable in V-Class or Superdome servers. All PCI controllers for V-Class and Superdome servers must be installed by qualified HP Engineers. HP recommends that these systems only be opened by a qualified HP engineer. Failure to observe this requirement can invalidate any support agreement or warranty to which the owner might otherwise be entitled.

1. Verify Prerequisites 2. Load the Software 3. Install the Adapter 4. Verify Adapter Installation 5. Connect the Adapter to the Network 6. Configure and Verify the Adapter to the Network Connection 7. Configure the Adapter and Verify Network Connectivity

Chapter 2

47

Installing and Configuring PCI FDDI 1 - Verify Prerequisites

1 - Verify Prerequisites Verify that there is an available PCI slot in the system. The system Power On Self Test (POST) messages display the occupied and unoccupied PCI slots. You can install the PCI FDDI adapter in any unoccupied PCI slot. You will need:

48

•

A #2 Phillips screwdriver.

•

One or two multimode FDDI fiber-optic cables with MIC or SC-Duplex connectors to attach the adapter to the network.

Chapter 2

Installing and Configuring PCI FDDI 2 - Load the Software

2 - Load the Software Follow the steps below to load PCI FDDI software using the HP-UX swinstall program. See the note at the end of this section for information on unloading the PCI FDDI software.

NOTE

The PCI FDDI software is part of the HP-UX software bundle and is located on the HP-UX Application Release (AR) CD.

1. Log in as root. 2. Insert the software media into the appropriate drive. 3. Run the swinstall program using the command: /usr/sbin/swinstall

This opens the Software Selection Window and Specify Source Window. 4. Change the Source Host Name if necessary, enter the mount point of the drive in the Source Depot Path field, and activate the OK button to return to the Software Selection Window. Activate the Help button to get more information. 5. Highlight the appropriate product specific software. 6. Choose Mark for Install from the “Actions” menu to choose the product 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 to confirm that you want to install the software. swinstall displays the Install Window.

Chapter 2

•

swinstall loads the fileset, runs the control scripts for the filesets, and builds the kernel. Estimated time for processing: 3 to 5 minutes.

•

View the Install Window to read processing data while the software is being installed. When the status field indicates ready, the Note Window opens. 49

Installing and Configuring PCI FDDI 2 - Load the Software 9. Activate the OK button on the Note Window to reboot. The user interface disappears and the system reboots. 10. When the system restarts, log in as root and view the /var/adm/sw/swagent.log and /var/adm/sw/swinstall.log files to view any error or warning messages that may have occurred during installation.

NOTE

50

Using the swremove command to remove the PCI FDDI filesets disables all PCI FDDI cards on the system.

Chapter 2

Installing and Configuring PCI FDDI 3 - Install the Adapter

3 - Install the Adapter This section describes the installation of the PCI FDDI adapter cards into your system. These instructions apply to the HP-UX operating system versions 10.20, 11.0 and 11i. For more detailed information, refer to the appropriate owner’s guide for each specific HP system model. You can also find information on installing PCI controllers/adapters on the HP Electronic Performance Support System for your system CD. Static Electricity Precautions PCI FDDI adapter contains electronic components that can easily be damaged by a small amount of static electricity. To avoid damage, refer to the following guidelines: •

Keep the adapters stored in their antistatic bags until ready for installation.

•

Work in a static-free area whenever possible.

•

Handle the adapters by the edges, and do not touch the electronic components or electrical traces.

•

Use the disposable grounding wrist strap provided, (HP 9300-1408) and follow the accompanying instructions.

•

Use any exposed metal surface on the computer chassis as a suitable electrical ground.

Begin Installation 1. With OLA/R on the 11i OS you need not completely shut down the system to install PCI I/O cards. See the OLA/R section in Chapter 1 for more information. 2. For 10.20 and 11.00 OS, shutdown the system and install the PCI FDDI adapter according to the instructions in the HP Service Guide for your system. 3. Attach the grounding strap to your wrist or ankle. 4. Shut down the system. /usr/sbin/shutdown -h

Chapter 2

51

Installing and Configuring PCI FDDI 3 - Install the Adapter Wait until the system responds with “OK to press reset” or “Halted, you may now cycle power”, then power off the system. 5. Disconnect the AC power cord from the system unit and from the AC power source. 6. Remove the adapter card from its antistatic bag. 7. Align the PCI FDDI connector on the PCI FDDI adapter with the PCI connector in the slot. Press the adapter firmly into place. Screw the PCI FDDI adapter into place. 8. Now the card is now ready to be attached to the network.

52

Chapter 2

Installing and Configuring PCI FDDI 4 - Verify Adapter Installation

4 - Verify Adapter Installation 1. As the system is powered on, observe the B and A port status LEDs. The PCI FDDI adapter will execute onboard diagnostics as the system is powered on. •

A flashing green LED for 1 second indicates a successful self-test.

•

A steady amber LED indicates a possible failure with that port.

2. When the system is up, execute ioscan or ioscan -c from the HP-UX prompt to verify that the system recognizes the card. Look for the description PCI FDDI Adapter for the appropriate hardware path. 3. Verify that the proper device files have been created. ls -1 /dev/lan* (list the HP device files) ls -1 /dev/nettrace /dev/netlog (lists the diagnostics device files) 4. Check that the network interface state and hardware state of the adapter is “UP”. /usr/sbin/lanscan 5. The hardware state indicates the card’s physical state. hpntch4 # lanscan Hardware Station -DLPI DLPI Path Address pport Mjr# 0/0/0 0x0060B0D690A3 s 119 0/1/0 0x0060B0069099 s 119

Crd Hdw

Net-Interface NM MAC

In# State NamePPA 0

UP

lan0

1

UP

lan1

HP

ID Type Su FDDI Ye 2

FDDI Ye

6. Verify that the system can find the FDDI adapter. /usr/sbin/dmesg Probe epic0 probe of epic0 complete 0 epic 0/0/0 fddi4

Chapter 2

53

Installing and Configuring PCI FDDI 4 - Verify Adapter Installation 0/1/0 fddi4 ... fddi4: INITIALIZING: PCI FDDI card in slot 0/0/0 fddi4: INITIALIZING: PCI FDDI card in slot 0/1/0 ... /usr/sbin/ioscan -c lan H/W Path Class Description ======================================================= 0/0/0 lan PCI FDDI Adapter 0/1/0 lan PCI FDDI Adapter

54

Chapter 2

Installing and Configuring PCI FDDI 5 - Connect the Adapter to the Network

5 - Connect the Adapter to the Network When connecting the adapter to the network, you must determine the topology you will use and the cables and connector needed. The most common topologies are shown on the following pages. Figure 2-1

Single Attach Station - Single Attach Concentrator

•

Figure 2-2

Dual-Homed Station

•

Chapter 2

You can attach the adapter as SAS (Single Attach Station) to a SAC (Single Attach Concentrator). Connect the B or A port on the adapter to an M port on the concentrator.

Or, you can attach the adapter as a dual-homed station to two concentrators for additional fault tolerance. Connect the B port of the adapter to an M port on the first concentrator. Connect the A port of the adapter to an M port on the second concentrator.

55

Installing and Configuring PCI FDDI 5 - Connect the Adapter to the Network Figure 2-3

Dual Attach Station

•

Figure 2-4

Optical Bypass Switch

•

56

You can also attach the adapter as a DAS (Dual Attach Station) directly to the adjacent stations in a dual-ring network. Connect one station’s A port to the neighboring station’s B port, and a station’s B port to a neighboring station’s A port.

With a dual-ring topology, you can also use an Optical Bypass Switch (OBS) between the adapter and the dual-ring to maintain continuity of the primary and secondary ring in case of an adapter failure. The optical bypass switch connects directly to the adapter via A and B cables pre-attached to the switch. The A cable connects to the adapter’s A port, and the B cable connects to the adapter’s B port. The OBS connection is the same as if it were a dual-attach adapter attaching directly to the dual-ring.

Chapter 2

Installing and Configuring PCI FDDI 5 - Connect the Adapter to the Network

5a - Cables and Connectors Figure 2-5

MIC-MIC Adapter Cables

•

Figure 2-6

SC-MIC Cable

•

Figure 2-7

You can also connect the card to a MIC device directly, using SC-MIC cables.

FDDI SC-SC Cable

•

Chapter 2

The PCI FDDI adapter uses SC connectors. In many networks, you will be attaching the adapter to FDDI devices with MIC connectors. Two 12-inch SC-MIC adapter cables are included so you can attach the adapter to a MIC device using standard MIC-MIC cables.

If you are attaching the PCI FDDI adapter to another device with SC connectors, use SC-SC FDDI (62.5/125 micron) cables, preferably keyed duplex cables (SC-Duplex). Each SC connector has two ports: transmit and receive. The SC connectors on the adapter are keyed for use with keyed duplex cables, which ensures that the cables are connected with the correct transmit/receive pairings.

57

Installing and Configuring PCI FDDI 5 - Connect the Adapter to the Network

5b - Handling the Cables WARNING

Never look directly into an optical-fiber port. Some fiber equipment can emit laser light that can injure your eyes. Always assume that the cable is connected to a light source.

1. Keep the dust cap(s) on the ends of the cables and on the transceivers of the adapter until you are ready to attach the cables. 2. Do not polish the connectors with cloth made of synthetic fibers; this charges the fiber and attracts dust. 3. Do not crease or bend the cables sharply. Always maintain the minimum bend radius specified by the cable manufacturer. The minimum bend radius is usually 10-20 times the cables outer diameter. 4. Do not force the connectors when attaching the cable. Most connectors are keyed connections and fit only one way. 5. Be careful when attaching/detaching cables. Many cable failures occur where the cable and connector are joined. 6. Do not stretch, puncture or crush the cables with staples or heavy equipment.

58

Chapter 2

Installing and Configuring PCI FDDI 5 - Connect the Adapter to the Network

5c - Attach the Cables Figure 2-8

Illustration of Attached Adapter Cables

•

For a SAS (Single Attach Station) topology, connect the SC-Duplex connectors (transmit and receive) of the cable to either the B port or the A port on the adapter. The cable could be an SC-MIC cable or an SC-SC cable.

•

For DAS (Dual Attach Station) and Dual-homed topologies, connect two adapter cable or cables to the adapter card, one to each port (A and B). — If you are using the SC-MIC adapter cable(s), connect the MIC receptacle of the cable adapter(s) to the MIC-MIC cable(s).

•

Chapter 2

Using the V-Class as an example, route the cable(s) into the cable channel and feed it down through the channel to the cable opening at the bottom of the chassis. Pull the cable(s) through and connect it to the network device.

59

Installing and Configuring PCI FDDI 5 - Connect the Adapter to the Network

5d - Normal LED, Ring Management and Configuration States The normal LED, Ring Management (RMT) states and Configuration (CF) states for different topologies are shown below. The RMT and CF states are reported by fddipciadmin. Figure 2-9

60

LED States

Chapter 2

Installing and Configuring PCI FDDI 6 - Configure the Adapter Using SAM

6 - Configure the Adapter Using SAM Follow the steps in the PCI FDDI Installation and Configuration card to load the FDDI software. The card gives you step-by-step instructions on using swinstall. After you have installed the software, follow the steps in the above mentioned card to configure the adapter using SAM. Check the SAM log file for errors (select “View Log” from the SAM menu or use the samlog_view utility). To manually configure PCI FDDI add entries to the /etc/rc.config.d/netconf and /etc/hosts files. Configure the PCI FDDI link with the specific parameters as required. To complete the software configuration for full network communication, you will need an IP address, subnet mask (optional) and host name alias. You will also need super-user status.

Chapter 2

•

Add IP address

•

Add any alias names

•

Add any subnet mask. This will initialize the FDDI link for IP communication and attach your node to the local area network.

61

Installing and Configuring PCI FDDI 7 - Configure the Adapter and Verify For Network Connectivity

7 - Configure the Adapter and Verify For Network Connectivity Configuring network connectivity allows your system to communicate with other systems. 1. Add remote system names 2. Add remote system IP address 3. Specify default gateway information 4. View the configured gateways and destinations reached through those gateways. netstat -r hpntch3 # netstat -r Routing Tables Destination Gateway Pmtu PmtuTime hpntcg3 127.0.0.1 4608 127.0.0.1 127.0.0.1 4608 default hpntcg3 1500 15.13.112 hpntcg3 1500 192.20.64 hpntcg3-fddi 4352

Flags

Refs

Use Interface

UH

0

1010784 io0

UH

0

112 io0

U

1

41 lan0

U

0

2870 lan0

U

0 10200657 lan2

In the above example, the local interface lan0 has been configured as the default IP gateway. IP uses the default gateway when it has to route a packet to a destination IP address that is not a member of any of the other destination IP subnets in the routing table. If the default gateway is a local interface, IP will send a broadcast ARP request via that interface to get the appropriate MAC address (typically, an intelligent router on the attached subnet will send a proxy ARP response). 5. Use lanscan on the remote system to obtain the remote station’s address.

62

Chapter 2

Installing and Configuring PCI FDDI 7 - Configure the Adapter and Verify For Network Connectivity hpother:root> lanscan Hardware Station HP-DLPI DLPI Path Address Support Mjr# 4/0/0 0x0060B0445566 Yes 119

Crd Hdw

Net-Interface NM MAC

In# State NamePPA

ID Type

2

3

UP

lan2

FDDI

6. Use the command: linkloop -i (for 11.x)

linkloop -i (for 10.20) to verify connectivity of the local node and the remote node. The PPA (Physical Point of Attachment) is the numeric portion of the interface name, NMID is the Network Management ID. In this example it is an HP-UX 11.0 system and lan1 is being tested, so specify 1 as the PPA. hpme:root> linkloop -i 1 0x0060B0445566 Link connectivity to LAN station: 0x0060B0445566 -- OK

7. Check to ensue that the ability to communicate with other systems via IP can occur: ping

NOTE

Chapter 2

If the adapter is attached as a DAS directly to a dual ring, be sure to ping each of the other nodes in the ring to ensure that a “twisted Ring” does not exsist. In a twisted ring topology, the A and B ports are not properly cross-connected and two logical rings are created.

63

Installing and Configuring PCI FDDI 7 - Configure the Adapter and Verify For Network Connectivity

64

Chapter 2

3

Troubleshooting PCI FDDI This chapter provides guidelines for troubleshooting PCI FDDI. It contains the following sections:

Chapter 3

65

Troubleshooting PCI FDDI

66

•

Troubleshooting Overview

•

Diagnostics

•

Flowcharts and Procedures

Chapter 3

Troubleshooting PCI FDDI Troubleshooting Overview

Troubleshooting Overview PCI FDDI 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 PCI FDDI network. As with any troubleshooting, a systematic approach is helpful. The following table and flowcharts provide a logical sequence of steps to follow when troubleshooting PCI FDDI. Using the diagnostic flowcharts provided in this chapter, identify whether the problem is with PCI FDDI or any of the connections to the switch, or whether it is in some other part of the network, verify your assumptions, and if it is limited to PCI FDDI software or hardware, correct the problem. If you cannot solve the problem on your own, contact your HP representative. The guidelines at the end of Chapter 1 help you effectively communicate what is wrong. The PCI FDDI adapter uses diagnostic tools compatible with the HP LAN/9000 Link product.

Man Pages While installing, configuring or troubleshooting PCI FDDI, you may need to refer to any of the online manual reference pages (man pages) for useful HP-UX operating system or PCI FDDIcommands. To display a man page, type the following at the system prompt: man The HP-UX man page references are located on the HP website: http://www.docs.hp.com/hpux/os/man_pages.html

Chapter 3

67

Troubleshooting PCI FDDI Adapter Problems

Adapter Problems Table 3-1 Symptom

Probable Cause

LED is amber (solid)

If cable is attached, there is probably a network problem.

•

Disconnect the cable. If the LED flashes Green, the adapter is OK.

•

Reconnect the cable, try a new cable or connect to a different concentrator port.

If no FDDI cable is attached, the problem could be with the adapter

•

Use lanadmin to re-set the card.

•

If the problem persists, re-boot the system.

•

If the problem persists, contact your Hewlett-Packard support contact.

•

Use a valid topology configuration.

•

Verify that you do not have your A port connected to another A port or your B port to another B port.

LED flashes amber

68

Invalid FDDI topology.

Action

Chapter 3

Troubleshooting PCI FDDI Adapter Problems Table 3-1

(Continued) Symptom LED flashes green continually and does not change to solid green when a cable is attached.

Probable Cause Faulty cable or connection.

Faulty concentrator

Chapter 3

Action •

Verify the cable and replace it if defective.

•

Verify that the FDDI cable is properly connected at both ends.

•

Verify that the SC transmit/receive ports are cross-connected.

•

You may want to try switching the individual transmit/receive fibers.

•

Verify integrity of concentrator.

69

Troubleshooting PCI FDDI Network Problems

Network Problems Table 3-2 Symptom ioscan output shows that the adapter is unclaimed

Action •

Check that the driver software is loaded: what /stand/vmunix | grep ‘PCI FDDI’ If software is loaded and the adapter is not claimed, then the adapter is not an HP OEM’d adapter.

ifconfig or netstat -i does not show interface (software state is down)

•

Use the ifconfig command to check the existence and status of the device; Example: ifconfig lan0

•

Check that /etc/rc.config.d/netconf has configuration statements for this device so the device will be initialized for IP when the system starts. If not, assign an IP address for the interfaces, then run the command: ‘/sbin/rc2.d/s329hppcifddi start’ to create PCI FDDI device files, if they are not already created.

•

Then run the command: ‘/sbin/rc2.d/s340net start’ to configure the interfaces with IP addresses.

Adapter cannot communicate with other hosts on the local network.

70

•

Use fddipciadmin to verify that upstream and downstream neighbors are correct.

•

Examine the LEDs.

•

Check the FDDI cable. Make sure the FDDI media is correctly installed. ping the failed system from another host on the network.

Chapter 3

Troubleshooting PCI FDDI Network Problems Table 3-2

(Continued) Symptom (Dual-ring only) Adapter can only communicate with a subset of hosts on the local network.

•

See “Adapter cannot communicate with other hosts on the local network.”

•

Check for twisted ring (port A cabled to port A, or B port cable to B port.

•

Use fddipciadmin to see if your are communicating with your upstream and downstream neighbors on the ring.

Cannot connect to ring.

•

For dual attach stations, check the cables to verify that the ports are connected to the appropriate ports in the neighbor stations.

Cannot reach a host on a remote network

•

Use ping to test connectivity to stations on your local ring.

•

Distinguish between an unknown host, which indicates an /etc/hosts file problem; and a non-response, which usually indicates a routing problem.

•

Use fddipciadmin to see if you are communicating with your upstream and downstream neighbors on the ring.

•

Check the arp table with arp -a.

•

Use netstat -r to check routing tables. Refer to the man pages for expected output.

•

Use fddipciadmin to check for abnormal statistics. If attribute LER is near the Alarm value, check for poor connections.

•

Verify optical power loss does not exceed 11 decibels between transmitter and receiver pairs.

Ring state is unstable.

Chapter 3

Action

71

Troubleshooting PCI FDDI Diagnostics

Diagnostics Diagnostic Utility Table 3-3

72

Diagnostic Utilities and HP-UX Administration Tools LEDs

Tests the hardware, firmware and functionality of the card. These self-test diagnostics execute at power-up or reset. In addition, you can check the LEDs using SC-SC cables in a loopback configuration.

fddipciadmin

Displays information and statistics about the interface card, driver and FDDI ring, the MAC addresses of the neighbor nodes.

arp

Maps a host’s IP address to its LAN MAC address.

dmesg

Verifies status of the interface

ifconfig

Verifies status of the interface.

ioscan

Displays status and hardware connectivity information.

lanadmin

Displays status of the LAN interface. Reset the card.

lanscan

Displays LAN device configuration and status. Shows the card’s physical path, instance number, interface name/PPA, NMID, interface state & station address and status.

linkloop

Verifies LAN connectivity with link-level loopback (TEST packet).

netstat

Shows the status of the network.

nettl, netfmt

Starts, stops and formats tracing/logging

ping

Verifies remote IP connectivity.

Chapter 3

Troubleshooting PCI FDDI Diagnostics

LEDs The PCI FDDI Adapter has two LEDs labeled A and B located on the faceplate. The LEDs indicate the status of the adapter and corresponding FDDI ports. Table 3-4

LED Status Indicator LED Port A

Color Green

PHY connection complete

Flashing

PHY connection in progress (or no cable attached)

On

If “on” after system boots, indicates port or Link Confidence Test (LCT) failure. If “on” before system boots, indicates self-test failure.

Flashing

Illegal topology

Green/Ambe r

Alternatin g

Stand-by mode when connecting in a dual-homed topology

None

Off

Port disabled by management, or LED or adapter failed

Green

On

PHY connection complete

Flashing

PHY connection in progress (or no cable attached)

On

If “on” after system boots, indicates port or Link Confidence Test (LCT) failure. If “on” before system boots, indicates self-test failure.

Flashing

Illegal topology

Off

Port disabled by management, or LED or adapter failed

Amber

None

Chapter 3

Description

On

Amber

Port B

State

73

Troubleshooting PCI FDDI Diagnostics LEDs and Hardware Loopback You can also check the LEDs using SC-SC cables in a loopback configuration. Using a keyed SC-duplex cable or two simplex SC-SC cables, cross-connect the B and A ports on a card as follows: Connect the B port transmit port to the A port receive port. Connect the B port receive port to the A port transmit port. After you cross-connect the ports, the B and A LEDs should both be solid green. Figure 3-1

fddipciadmin The fddipciadmin utility displays information about the status of the PCI FDDI interface. This utility first shows summary information about the interface. It then displays a menu that lets you refresh statistics and display other interface information. Use the utility fddipciadmin to report card, driver and network statistics. Refer to fddipciadmin(1M) and fddi(7) man pages. To use fddipciadmin, type:

74

Chapter 3

Troubleshooting PCI FDDI Diagnostics /usr/bin/fddipciadmin interface_name

For example: /usr/bin/fddipciadmin lan1 This command opens an Interface Status Summary screen that contains key information about the interface and some information about the ring. It also gives you access to the other menu screens. 1. Refresh Statistics 2. Display Summary 3. Display SMT Attributes 4. Display MAC Attributes 5. Display Port A Attributes 6. Display Port B Attributes 7. Display Path Attributes 8. Display Multicast Addresses 9. Display Link Statistics 10. Exit In HP-UX 11.00 and 11i, in addition to the above, we have options to set T_Req time and T_Notify time. fddipciadmin: Summary Field Description •

MAC Address — Media Access Control (unit) Address. Specifies the 48-bit MAC address of the node in canonical (Least Significant Bit) hexadecimal format. The “Wire Format” shows the MAC address in Most Significant Bit order.

•

Up Stream Neighbor — Upstream neighbor’s (MAC) Address. Specifies the MAC Address of the upstream neighbor in canonical hexadecimal format. The “Wire Format” shows the MAC address in Most Significant Bit order.

•

Chapter 3

Down Stream Neighbor

75

Troubleshooting PCI FDDI Diagnostics — Downstream neighbor’s (MAC) Address. Specifies the MAC Address of the downstream neighbor in canonical hexadecimal format. The “Wire Format” shows the MAC address in Most Significant Bit order. PCI FDDI NETWORK ONLINE ADMINISTRATIO N, Version 1.0 Wed. 2, 2001 09:44:53 Copyright 2001 Hewlett-PAckar d Company All right are reserve d << INTERFACE STATUS SUMMA RY >> MAC Address 0X0060B0580E19 Wire Format: 0x00060D1A7098 Up Stream Neighbor 0x080009455DD5 Wire Format: 0x00060D1A7098 Down Stream Neighbor 0x0060B0580E03 Wire Format: 0x100090A2BAAB RMT State: Ring_Op CF State: C_Wrap_B Frame Count: 00322395 Token Count: 57108118 Receive Count: 00000330 Transmit Count: 342 Lost Count: 0 Error Count: 0 RingOp Count: 1 LER Estimate A: 10**-15 Estimate B: 10**-15 T-Req (ms) : 7.9873 T_Neg (ms) : 5.0001 Number of multicast addresses configured: 0

•

RMT State: Ring Management State. Indicates whether the state is: Isolated, Non_Op, Ring_Op, Detect, Non_Op_Dup, Ring_Op_Dup, Directed, Trace or Unknown. The normal state is Ring_Op. — Isolated: usually indicates that the interface is not connected to the network. — Non_Op: the ring is in recovery and/or is not operational.

76

Chapter 3

Troubleshooting PCI FDDI Diagnostics — Ring_Op: the node and ring are operational. — Detect: ring has been non-operational for more than the default time of 1 second. The MAC is in a duplicate-address-detect state. — No_Op_Dup: ring is not operational and another node with the same MAC address was detected. — Op_Dup: ring is operational and another node with the same MAC address was detected. — Directed: this MAC is sending beacon frames to notify the ring of a stuck condition. — Trace: this MAC initiates a trace function to provide a recovery from a stuck beacon.

NOTE

Refer to the RMT ANSI FDDI/SM specifications description for more detailed information.

—

Chapter 3

CF State: Configuration State of the station indicates whether the state is: Isolated, Local_A, Local_B, Local_S, Wrap_A, Wrap_B, Wrap_AB, Wrap_S, C_Wrap_A, C_Wrap_B, C_Wrap_S, Thru or Unknown. •

The normal state for a Dual Attach Station is Thru.

•

The Wrap_A, Wrap_B, Wrap_AB, C_Wrap_A, C_Wrap_B states indicate that there is only a single data ring. Data for the ring is transmitted and received through the same port (A or B).

•

For a Dual Attach Station, a wrap state usually indicates that the dual ring is wrapped (a failure was detected and a surrounding node is “wrapping” and using either the A or B port to send and receive data) or this is a transitory start-up state indicating that the A or B port is ready to be incorporated into the ring.

•

For a Single Attach Station (the A or B port is attached to the M port of an FDDI device such as a concentrator), C_Wrap_A or C_Wrap_B is the normal operating state, depending on the port used.

77

Troubleshooting PCI FDDI Diagnostics •

NOTE

The isolated state indicates that there is no internal connection between the MAC (Media Access Control) and PHY (Physical Layer Protocol) modules. This usually indicates the card is not cabled to the ring.

Refer to the CF_State variable ANSI FDDI/SM specifications description for more detailed information.

— Frame Count: Specifies the total number of frames received with End Delimiters by the station. This count includes void frame, token frames, beacon frames, claim frames, SMT frames and LLC frames. — Token Count: The number of times a token (both restricted and non-restricted tokens) has been received. Useful for determining the network load. — Receive Count: Specifies the total number of non-MAC frames (SMT or LLC frames) with an address recognized by the station and successfully received by the station. — Transmit Count: Specifies the total number of non-MAC transmit frames originated by this station. — Lost Count: Specifies the total number of frames received with format error detected. When the station detects a frame with a format error, it strips the rest of the frame from the ring and replaces it with idle symbols. — Error Count: Specifies the total number of frames received with the End Delimiter not set (not "S”). — RingOp Count: Ring Operational Count. Indicates the number of times the ring has entered an operational state from a non-operational state. (This value is not required to be exact and the actual count may be greater that the number shown. — LER Estimate A: Link Error Rate Estimate: Specifies the estimated long term average link error rate for Port A. — LER Estimate B: Link Error Rate Estimate: Specifies the estimated long term average link error rate for Port B.

78

Chapter 3

Troubleshooting PCI FDDI Diagnostics — Requested TTRT: Specifies the requested Target Token Rotation Time (TTRT) by the local station in the claim token process in milliseconds. Refer to the T_Req value description in the ANSI FDDI/SMT specifications for more details. — T_Neg: Negotiated Target Token Rotation Time (TTRT). Specifies the target rotation time being used by all the stations on the ring. This value is negotiated during the claim token process. The value of “T_Neg” is in milliseconds. Refer to the “T_Neg” value description in the ANSI FDDI/SMT specifications for more details. — Number of multicast addresses configured: Specifies the number of link-level multicast addresses configured for this interface. fddipciadmin: Menu Options The Interface Status Summary contains the most commonly used information. Menu Option 1 causes fddipciadmin to re-read statistic from the card/driver. The other menu selections display more information about the interface and driver. •

Display SMT Attributes: Station Management attributes.

•

Display MAC Attributes: MAC attributes, including: — Config (upstream and downstream neighbors, previous neighbors). — Operation (includes timers related to the Token Rotation Timer).

Chapter 3

•

Counters (includes token count, transmit/receive counts, Ring_Op count).

•

Display Port A Attributes/Display Port B Attributes: Information related to the individual ports, including error counts.

•

Display Path Attributes: Attributes of the logical segment of the FDDI ring that passes through the station.

•

Display Multicast Addresses: The multicast MAC addresses registered with the interface (the multicast addresses recognized by the interface).

•

Display Driver Status: Transmit/receive statistics for the driver.

79

Troubleshooting PCI FDDI Diagnostics •

Display Link Status: Transmit/receive statistics for the link, including SMT packets.

dmesg After installation, verify that the adapter can be found by the system by using the dmesg command. Log in as “root” and run the following command: /usr/sbin/dmesg Probing epic0 Probe of epic0 complete 0 epic 0/0/0 fddi4 0/1/0 fddi4 ... fddi4: INITIALIZING: PCI FDDI card in slot 0/0/0 fddi4: INITIALIZING: PCI FDDI card in slot 0/1/0 ...

arp The arp (Address Resolution Protocol) command displays the Internet-to-physical address translation tables. It maps the IP address to the physical (MAC) address. The arp command gives you a list of addresses associated with the specified host. The arp -a command (in the example below) displays all current arp entries based on the kernel file system/hpux. Example: hpntc7q:root> arp -a hpindbu.cup.hp.com (15.13.104.13) at 0:0:c:0:37:bf ether ntc7f-f (192.20.100.122) at 0:60:b0:d6:90:9f snapfddi

ifconfig The ifconfig command sets or displays the current configuration of the network (IP) interface. Use the ifconfig command to verify the existence and status of the device. Example: To see the status of the lan3 interface use this command: 80

Chapter 3

Troubleshooting PCI FDDI Diagnostics hpntch4 # ifconfig lan3 lan3: flags=863 inet 192.20.40.50 netmask fffff800 broadcast 192.20.47.255

The ifconfig command can also be used to manually bring up the interface if it is down.

ioscan ioscan displays status and hardware connectivity information. By default, it lists all of the hardware found on the system. You can specify -c lan to show only the hardware in the LAN class. /usr/sbin/ioscan -c lan H/W Path Class Description ========================================== ... 0/0/0 lan PCI FDDI Adapter 0/1/0 lan PCI FDDI Adapter ...

lanadmin The lanadmin command displays the status of the LAN interface. You can also reset the card with lanadmin if necessary. To verify the hardware state, type: /usr/sbin/lanadmin At the prompt, type: lan ppa x display (for HP-UX 11.x), lan nmid x display (for HP-UX 10.20). The PPA is the numerical portion of the interface name. For example, the PPA for lan2 is 2. In HP-UX 10.20, x is the Network Management ID, which you can get from the lanscan output. Enter command: display LAN INTERFACE STATUS DISPLAY Wed, May 2, 2001 Network Management ID Description dapter Fw Rev.3.10 Type (value) MTU Size

Chapter 3

09:57:15

= 4 = lan2 Hewlett-Packard PCI FDDI A = fddi (15) = 4352

81

Troubleshooting PCI FDDI Diagnostics Speed Station Address Administration Status(value) Operation Status (value) Last Change Inbound Octets Inbound Unicast Packets Inbound Non-Unicast Packets Inbound Errors ...

= = = = = = = = =

100000000 0x0060B0d69a3 up (1) up (1) 1011981975 22404656 26 0 0

lanscan The lanscan command verifies that the link Hardware State is up. It displays information about each LAN device that has software support on the system. The Hdw State field shows the hardware state. If the state is DOWN, the driver cannot communicate with the card and may indicate: •

The driver has detected operational problems. Use lanadmin to reset the card.

•

The card may be bad. Check the LEDs.

/usr/sbin/lanscan hpntch4 # /usr/sbin/lanscan Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI Path Address In# State NamePP ID Type Support Mjr# 0/0/0 0x0060B0D690A3 0 UP lan0 1 FDDI Yes 119 0/1/0 0x0060B0069099 1 UP lan1 2 FDDI Yes 119

linkloop(1M) The linkloop(1M) command verifies LAN connectivity with link-level loopback. It tests the connectivity of the local node and the remote node specified by the hardware station address by sending a link-level TEST packet and checking for the response.

82

Chapter 3

Troubleshooting PCI FDDI Diagnostics Figure 3-2

For 11.0 and 11i OS

If you execute linkloop(1M) back to the local interface’s own MAC address, (linkloop(1M) to self) the local address will send a response. No hardware is exercised. Figure 3-3

For 11.0 and 11i OS

netstat The netstat command shows network status. It may be run with several options. The example below shows the -i option that is used to obtain inbound and outbound statistics for the IP interfaces. The Ipkts (Inbound packets) and Opkts (Outbound packets) indicate the IP packets received/sent via each interface. You can execute the netstat -i command repeatedly to determine if an interface is sending/receiving IP packets. You can also use it to get an approximation of the relative traffic loads for the interfaces. (Ipkts and Opkts shown in the following table are IP packets only) hpntch4 # netstat -i Name Mtu Network ni0* 0 none nil* 0 none

Chapter 3

Address none none

Ipkts 0 0

Opkts 0 0

83

Troubleshooting PCI FDDI Diagnostics lo0 lan2 lan4* lan3 lan0

4608 4352 4352 4352 1500

loopback 192.103.48 none 192.20.40 15.13.112

localhost h4-6w none 192.20.40.50 hpntch4

890 350002 0 14 644287

890 701564 0 14 1787

ping Use ping to test connectivity to stations on your local ring. hpntc7q:root> ping 192.20.100.112 PING 192.20.100.112: 64 byte packets 64 bytes from 192.20.100.112: icmp_seq=0. 64 bytes from 192.20.100.112: icmp_seq=1. 64 bytes from 192.20.100.112: icmp_seq=2. 64 bytes from 192.20.100.112: icmp_seq=3.

time=0 time=0 time=0 time=0

ms ms ms ms

nettl, netfmt, nettladm •

The nettl command is used to start and stop tracing. The netfmt command is used to format a trace file. The /opt/nettladm/bin/nettladm utility provides a GUI interface to nettl and netfmt.

•

Log messages for 11.0 are sent by default to the file /var/adm/nettl.LOG## and for 11i to the file /var/adm/nettl.LOG### (LOG000 or LOG001). For tracing, use the -f option to indicate where you want the trace to go. All disaster messages are sent to the console.

•

The PCI FDDI adapter card uses the nettl entity PCI FDDI

•

From the command line, you can enable tracing for all inbound, outbound and driver loopback PCI FDDI packets with the following command: nettl -traceon pduin pduout loopback -e PCI_FDDI -f my_file

•

To disable tracing: nettl -traceoff -e all

84

Chapter 3

Troubleshooting PCI FDDI Diagnostics •

To filter the formatted output so only log/trace entries for PCI FDDI are shown, create a netfmt configuration file (netfmt tries $HOME/netfmt by default) with the following entry: filter entity PCI_FDDI

•

Execute netfmt to format your trace file with the “Nice” option (format the upper layers, try to resolve host and service names), and no-inverse video: netfmt -c my_netfmt_conf_file /var/adm/nettl.LOG##

Chapter 3

85

Troubleshooting PCI FDDI Diagnostic Flowcharts

Diagnostic Flowcharts The following table summarizes the types of network tests in the diagnostic flowcharts. Follow the flowcharts in sequence beginning with Flowchart 1. Table 3-5

Flowchart Descriptions Char t

86

Type of Test

Purpose

1

Link Level Test

Checks communications between link levels on the source and target host using the linkloop(1M) command.

2

Network Level Tests

Validate arp(1M) entries and remote host availability. Check communication between network layers on source and target host.

2a

arp Test

Verifies that an entry exists for the remote host in your system's arp cache.

2b

ping Test

Checks roundtrip communication between Network Layers on the source and target host.

3

Transport Level Test

Checks communications between transport layers on the source and target host using telnet and ftp sessions.

4

Bridge/Gateway Loopback Test

Checks general network connections through a gateway.

5

Configuration Tests

Verifies the configuration of the network interface on a host using the lanscan(1M), netfmt(1M), lanadmin(1M), and ifconfig(1M) commands.

5a

lanscan, ioscan Tests

Verifies the configuration of the network interface on a host.

Chapter 3

Troubleshooting PCI FDDI Diagnostic Flowcharts Table 3-5

Flowchart Descriptions (Continued) Char t

Type of Test

Purpose

5b

netfmt, lanadmin Tests

Verifies the configuration of the network interface on a host.

5c

ifconfig Test

Verifies the configuration of the network interface on a host.

Flowchart 1: Link Level Test Checks communications between link levels on the source and target host using the linkloop(1M) command.

Chapter 3

87

Troubleshooting PCI FDDI Diagnostic Flowcharts Figure 3-4

Flowchart 1

Link Level Test

Execute linkloop(1M) to remote host

Linkoop(1M) successful ?

YES

Network Test

NO Loopback FAILED: Remote host fails to Respond

Address has bad format or not an individual address

YES

Correct the address parameter

NO Re-check remote host address or choose a different remote host and re-execute linkloop(1M)

Linkoop(1M) successful ?

NO

Link Level Test

Configuration Tests

YES Network Test

Flowchart 1 Procedures •

88

Execute the linkloop(1M) command to remote host. If linkloop(1M) is successful, continue to Network Test. If linkloop(1M) fails, note which error was returned.

Chapter 3

Troubleshooting PCI FDDI Diagnostic Flowcharts •

If loopback failed error = “Address has bad format” or “Not an individual address” then correct the link level address with the proper station address format/value and repeat the Link Level Test.

•

Otherwise, loopback failed because the remote host did not respond. Double check the remote host address or choose another remote host and re-execute linkloop(1M). If linkloop(1M) is successful, continue to Network Test. You may also want to contact the administrator of the remote that did not respond (if this was the case).

Flowchart 2: Network Level Tests Figure 3-5

Flowchart 2

Network Level Tests

arp Test

ping Test

Chapter 3

89

Troubleshooting PCI FDDI Diagnostic Flowcharts Flowchart 2 Procedures

90

•

See Flowchart 2a to validate arp(1M) entries and remote host availability.

•

See Flowchart 2b to check communication between network layers on source and target host using ping(1M)

Chapter 3

Troubleshooting PCI FDDI Diagnostic Flowcharts

Flowchart 2a: arp Test Figure 3-6

Flowchart 2a

arp Test

Is remote host entry in arp cache?

NO

Remote host up?

YES

NO YES

Bring up remote host

Is the arp entry correct and complete ?

NO

Use arp to correct and complete the entry

YES

ping Test

Chapter 3

91

Troubleshooting PCI FDDI Diagnostic Flowcharts Flowchart 2a Procedures

92

•

Use arp to verify that an entry exists for the remote host in your system's arp cache executing arp hostname.

•

If there is no arp entry for the remote host, check to see if the remote host is up. If not, bring up remote host and continue to ping Test.

•

If the arp entry is incorrect or not complete, use arp(1M) to enter the correct station address of the remote system and continue to ping Test. Otherwise, continue to ping Test.

Chapter 3

Troubleshooting PCI FDDI Diagnostic Flowcharts

Flowchart 2b: ping Test Figure 3-7

Flowchart 2b

ping Test

Execute ping remote host

ping successful?

NO

Validate network, remote host, and configuration settings

YES

Stop

Continue to 2c

Flowchart 2b Procedures

Chapter 3

•

Execute ping to remote host using ping(1M).

•

If ping is successful, stop. If not, validate network and configuration settings and ping again.

93

Troubleshooting PCI FDDI Diagnostic Flowcharts Flowchart 2c: ping Test (cont.) Figure 3-8

Flowchart 2c (cont.)

ping not successful Network unreachable error?

YES

Configuration Tests

NO

No YES response from ping?

Tests Note: Refer to Table 3.1 Adapter Problems

NO

Unknown host error?

Cable LED

YES

Correct BIND, YP, or /etc/hosts configuration ping Test

NO

No route to host error?

YES

Add route table entry

NO

Call HP

Flowchart 2c Procedures • 94

If network has unreachable error, go to the Configuration Tests. Chapter 3

Troubleshooting PCI FDDI Diagnostic Flowcharts •

If no response from ping, check network cables and LEDs on adapter.

•

If you receive an unknown host error, add the missing host name and repeat ping Test.

•

If you receive “error=SendTo: No route to host”, then using route(1M) add route table entry for the missing host and repeat ping Test, otherwise call HP.

Flowchart 3: Transport Level Test Checks communications between transport layers on the source and target host using telnet and ftp sessions.

Chapter 3

95

Troubleshooting PCI FDDI Diagnostic Flowcharts Figure 3-9

Flowchart 3 Transport Level Test

Execute telnet to remote host

telnet successful?

YES

Stop

NO

ExecuteYES ftp to remote host

YES ftp successful?

Call HP

NO

Is TCP configured on local or remote host ?

NO

Configure TCP

YES

Call HP

Transport Level Test

Flowchart 3 Procedures •

96

Execute telnet to a remote host. If successful, stop.

Chapter 3

Troubleshooting PCI FDDI Diagnostic Flowcharts

Chapter 3

•

If not successful, try to establish an ftp to a remote host. Unlike telnet, ftp does not use a pseudoterminal (pty) driver on your system. This will determine if the pty is why telnet failed. If ftp is successful, you should call HP to determine why you have a problem with pty.

•

If ftp fails, check to see if TCP is installed on both hosts by verifying the /etc/protocols file. Telnet and ftp work at the transport layer and require TCP. If TCP is not installed, install now and repeat the Transport Layer Tests.

•

If TCP is installed on both hosts, telnet to another host and/or use netstat(1M) to check for lost packets. If network is congested, you may need to reconfigure network, otherwise call HP.

97

Troubleshooting PCI FDDI Diagnostic Flowcharts

Flowchart 4: Bridge/Gateway Loopback Test Figure 3-10

Flowchart 4 Bridge Gateway Test

Execute ping from a known good host through a gateway to another known good host

YES

Successful? NO

YEStable Check route on problem host and all hosts in path and correct if necessary

YES

Examine gateway

Network Test

Refer to non-HP documentation or if HP, execute ifconfig on gateway

Network interface up?

YES

Configuration Tests

NO

Configure interface up

Network Test

98

Chapter 3

Troubleshooting PCI FDDI Diagnostic Flowcharts Flowchart 4 Procedures Checks communications between transport layers on the source and target host using telnet and ftp sessions. •

Execute a ping from a known good host through a gateway to another known good host. This will test connectivity through bridge/gateway level. If successful, execute netstat(1M) -r command and examine the route table. If the gateway is an HP9000, execute the ifconfig for all interfaces on gateway. Continue to the Network Level Test.

•

If the ping is not successful, examine whther the gateway is HP or non-HP system. If it is non-HP, refer to the networking documentation for that product. If the gateway is an HP system, execute the ifconfig for all interfaces on gateway or host. (See Configuration Tests for more details on ifconfig)

•

If ifconfig does not show the parameter as UP in the output for the gateway, then execute netstat(1M) -i to check the status of the network interfaces. An asterisk (*) indicates the interface is down. If the network interface is down, configure the interface UP and continue to the Network Test. If all interfaces are UP, go the Configuration Tests and test all interfaces on the gateway.

Flowchart 5: Configuration Tests Verifies the configuration of the network interface on a host using the lanscan(1M), ioscan, netfmt(1M), lanadmin(1M), and ifconfig(1M) commands.

Chapter 3

99

Troubleshooting PCI FDDI Diagnostic Flowcharts Figure 3-11

Flowchart 5

Configuration Tests

lanscan and ioscan Test

netfmt and lanadmin Test

ifconfig Test

Flowchart 5 Procedures •

100

Verifies the configuration of the network interface on a host using the lanscan, netfmt, lanadmin, and ifconfig commands.

Chapter 3

Troubleshooting PCI FDDI Diagnostic Flowcharts

Flowchart 5a: lanscan and ioscan Test Figure 3-12

Flowchart 5a

lanscan ioscan Test

Is your interface displayed after executing lanscan ?

Is the adapter claimed by the system as shown by executing the ioscan?

YES

Hardware Execute state up?

YES

netfmt lanadmin Test

NO

NO

Run the swinstall(1M) command regenerate kernel and reboot system.

Cale LED test

Note: Refer to Table 3.1 Adapter Problems

YES

Check hardware

YES Problem fixed?

NO

Network Test

YES

Stop

Chapter 3

101

Troubleshooting PCI FDDI Diagnostic Flowcharts Flowchart 5a Procedures

102

•

Execute lanscan command and verify your interface is displayed by the system.

•

If it is displayed, does the hardware state display show “UP”? If so, continue to the netfmt and lanadmin Test. If not, run cable LED test from Table 3.1.

•

Verify the output from the ioscan shows the adapter “CLAIMED” by the system. If it is claimed, check adapter installation and re-seat and/or reset adapter.

•

If the adapter is not claimed, the Driver and Class will indicate “unknown”. Install the PCI FDDI driver and verify or edit /stand/system to contain the swinstall keyword (see the “Installing an Administering LAN/9000 Software” manual for instructions on how to edit /stand/system and create a new kernel.) Then reboot the system and check adapter installation and re-seat and/or reset adapter.

•

If the problem is fixed, stop, else perform the Network Test.

Chapter 3

Troubleshooting PCI FDDI Diagnostic Flowcharts

Flowchart 5b: netfmt and lanadmin Test Figure 3-13

Flowchart 5b netfmt lanadmin Test

Execute netfmt. Check causes and actions in the log output

Problem solved?

YES

Network Test

NO

Call administrator and reset card.

ResetYES successful?

YES

Network Test

NO

Repeat test once Repeat more

Chapter 3

103

Troubleshooting PCI FDDI Diagnostic Flowcharts Flowchart 5b Procedures •

Execute netfmt command and view the error and disaster log messages. Example: netfmt -vf /var/adm/nettl.LOG00 It will help to use the time stamp to find the proper logs. Ensure you are looking at the PCI FDDI information.

104

•

If the problem is solved, then continue to the Network Level Test.

•

If the problem persists, run the lanadmin(1M) command to reset the adapter.

•

If the reset is successful, continue to the Network Level Test. Otherwise, repeat this test one more time.

•

If it is not successful, call HP support.

Chapter 3

Troubleshooting PCI FDDI Diagnostic Flowcharts

Flowchart 5c: ifconfig Test Figure 3-14

Flowchart 5c

ifconfig Test

Execute ifconfig up Execute ifconfig

ifconfig successful ?

NO

YES

Are flags correct?

NO

Correct ifconfig flag settings

YES

Call HP ifconfig entry in YES /etc/rc.config.d/netconf

Any error messages returned?

NO

? NO

Add network config for adapter to /etc/rc.config.d/netconf

YES

Correct problem according to message received

ifconfig Test

Network Test

Chapter 3

105

Troubleshooting PCI FDDI Diagnostic Flowcharts Flowchart 5c Procedures •

Execute ifconfig on the interface you want to configure to ensure that interface is enabled. Example: ifconfig lan1 192.6.1.17 255.255.255.0 up Next, ifconfig to test and verify the flag setting is UP and the correct IP address is displayed. Example: ifconfig lan1

106

•

If the IP and flags are correct, verify there is an entry for the PCI FDDI adapter interface in /etc/rc.config.d/netconf. If so, continue to the Network Level Test. Otherwise, add the correct interface parameters to /etc/rc.config.d/netconf file and reboot. If the flags are incorrect, correct them with ifconfig and repeat the ifconfig Test. Otherwise, if the ifconfig command is unsuccessful and error messages appear, correct them accordingly and repeat the ifconfig Test.

•

If you cannot correct the errors, call HP.

Chapter 3

Index Numerics 11i Operating System, 30 32-bit operating system, 38 64-bit operating system, 38 A A Port

, 56

A3739A, 40 A3739B, 32, 40 A4700-67073, 40 Adapters Software Manual, 31 ANSI FDDI Standard, 24 Architecture, 21 B B Port

, 56

B2355-90698, 38 C Cable Handling, 58 Customer-installable

, 47

D Data Link Layer, 21 Devices, 23 Diagnostics, 40 Dual Attach Station, 40 Dual Attachment Concentrators, 23 Dual Attachment Station, 23 Dual Homed Topology, 40 Dual Homing Topology, 29 dual ring concentrator, 23 Dual Ring of Trees Topology, 28 Dual Ring Topology, 27 F FDDI Architecture, 21 FDDI Concepts, 20 fddipciadmin, 40 Features, 32 Fibre Distributed Data Interface, 20

H Hardware Requirement, 38 I Installing the Adapter

, 51

Internet Advisor, 40 ioscan

, 53

IP Address, 61 L Laser Light, 58 LED, 40, 60 LED

, 53

LEDs, 40 Limitations, 32 linkloop(1M), 40 LLC, 24 Logging, 40 Logical Link Control, 24 M MAC, 24 man pages, 40 Media Access Control, 24 MIC-MIC, 40, 57, 59 MIC-MIC cables, 40 N nettl, 40 Network Layout, 22 New Driver, 40 New Drivers, 40 O OBR, 40 OBS

, 56

Optical Bypass Relay, 40 Optical Bypass Switch

, 56

OSI Model, 20 Overview

, 47

107

Index P Packet, 32 Packets, 40 PCI FDDI Adapter Overview, 20 PCI FDDI Adapter Products, 30 PCI FDDI Adapters Supported on HP Servers, 31 PCI LAN Adapter CArd, 30 PHY, 24 Physical and Data Link Layers, 20 Physical Layer, 20 Physical Layer Protocol, 24 Physical Medium Dependent, 24 PMD, 24 Q Qualified HP Engineer

, 47

R RJ-12, 40 S SAM, 33, 38 SAM

, 47

SAS, 59 SC connectors, 40 Scalability, 33 SC-MIC, 40, 57, 59 SC-MIC Cables, 40 SC-SC, 57 Servers, 31 Service Guard, 33 Single Attach Station, 40 Single Attachment Concentrators, 23 Single Attachment Station, 23 single ring concentrator, 23 SMT, 40 SNA, 33 Software

, 47

Software Manual, 31 Software Requirement, 38 Standalone Concentrator Topology, 26 Standby, 40 Station Management, 24 Station Manager, 40

108

STM, 33 Superdome, 24, 38 Superdome

, 47

Support Sysytem, 30 T Terminology, 24 Topologies, 22 Tree of Concentrator Topology, 27 V V class, 38 V-class, 24 W Workstations, 32 Workstations - Not Supported, 32 www.docs.hp.com, 38