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.
©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.
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.
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.
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.
Operating Environment The list below shows the recommended operating environment for the PCI FDDI Dual Attach Adapter.
Contents 1. PCI FDDI The PCI FDDI Adapter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FDDI Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FDDI Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCI FDDI Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 5b - Handling the Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5c - Attach the Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5d - Normal LED, Ring Management and Configuration States . . . . . . . . . . . . . . . . 6 - Configure the Adapter Using SAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Installing and Configuring PCI FDDI operating systems.
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.
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.
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.
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.
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.
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.
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.
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 ...
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).
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 ...
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.
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.
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.
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.
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.
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.
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.
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 Procedure
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.
Troubleshooting PCI FDDI Diagnostic Flowcharts Flowchart 2 Procedures 90 • See Flowchart 2a to validate arp(1M) entries and remote host availability.
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.
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.
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.
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.
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.
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.
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 Networ
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.
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.
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.
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.
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.
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.
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.
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.
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,
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 Att
