Using Dual Port 100Base-TX and Dual Port Wide Ultra2 SCSI Version B.11.00.01 Manufacturing Part Number: E1099 U. S. A. © Copyright 1999 Hewlett-Packard Company.
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.
Contents 1. Installing and Configuring PCI 10/100 Base-TX Compatibility and Installation Requirements . . . . . . . . . . . . . . . . . . . . .10 Manual Speed and Duplex Mode Configuration . . . . . . . . . . . . . . . . . . .11 Autonegotiation and Autosensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 What Manuals are Available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 Software Availability in Native Languages . . . . . . . . . . . . . . . . . . . . . . .
Contents 6. Troubleshooting 10/100Base-TX/9000 Performance Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Corrective Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Troubleshooting Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Diagnostic Flowcharts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flowchart 1: Network Level Loopback Test . . . . . . . . . . .
Contents Cabling Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104 Cable Lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104 Dual Port 100Base-TX and Dual Port Wide Ultra 2 SCSI Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 C. Hardware Regulatory Statements FCC Statement (For U.S.A.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 Canada . . . . . . . .
Contents vi
Preface The information in this manual is intended for network managers who install and administer 10/100Base-TX networks and Wide Ultra2 SCSI devices. It is assumed the reader is experienced with the basics of local and wide area networking and SCSI technology. This manual describes how to install, configure, and troubleshoot the 10/ 100Base-TX and SCSI software and hardware product on HP 9000 PCI systems.
1 Installing and Configuring PCI 10/100 Base-TX This document contains information on the PCI 10/100Base-TX/9000 amd Wide Ultra2 SCSI cards for use with the 11.0 operating systems.
Installing and Configuring PCI 10/100 Base-TX Compatibility and Installation Requirements Compatibility and Installation Requirements Following are the limits of the current PCI 10/100Base-TX/9000: • The PCI 10/100Base-TX/9000 ports support autonegotiation and autosensing. You should not normally need to manually configure the speed, autonegotiation, or duplex mode of the card.
Installing and Configuring PCI 10/100 Base-TX Manual Speed and Duplex Mode Configuration Manual Speed and Duplex Mode Configuration Because the PCI 10/100Base-TX/9000 LAN ports support autonegotiation, you should not normally need to manually set the duplex mode. Sometimes you may need to manually set the duplex mode of the card—for example, if the switch is operating at full-duplex but does not autonegotiate.
Installing and Configuring PCI 10/100 Base-TX Manual Speed and Duplex Mode Configuration To manually set the duplex mode of the PCI ports, first ensure that your computer has the latest applicable patches installed as listed in the Required and Optional Patches section of this release note. To list the current speed and duplex mode of the PCI 10/100Base-TX/9000 ports, use the -x option (NOTE: lowercase x) of the lanadmin command.
Installing and Configuring PCI 10/100 Base-TX Manual Speed and Duplex Mode Configuration some switches may disable that switch port from doing autonegotiation. Verify that both the card and the switch port are operating in the same speed and duplex mode as desired. If you use manual configuration to change the card to a different speed and duplex mode, you may need to turn autonegotiation on first before the manual setting takes place.
Installing and Configuring PCI 10/100 Base-TX Autonegotiation and Autosensing Autonegotiation and Autosensing Autonegotiation is a mechanism defined in the IEEE 802.3u specification whereby devices sharing a link segment can exchange information and automatically configure themselves to operate at the highest capability mode shared between them.
Installing and Configuring PCI 10/100 Base-TX What Manuals are Available If a PCI 10/100Base-TX/9000 port is connected to a device, such as a switch, that is autonegotiating, the PCI card will autonegotiate with the device to mutually determine the highest possible speed and duplex settings between them.
Installing and Configuring PCI 10/100 Base-TX Software Availability in Native Languages Software Availability in Native Languages The commands used with this product are the ones supported by the Native Language Support Catalog of HP-UX.
2 Configuring Network Connectivity Using SAM This chapter describes how to configure remote connectivity using SAM.
Configuring Network Connectivity Using SAM • Step 1: Configuring Network Connectivity • Step 2: Deleting a Default Gateway (Optional) 18 Chapter 2
Configuring Network Connectivity Using SAM Step 1: Configuring Network Connectivity Step 1: Configuring Network Connectivity Your system may not be able to communicate with other systems, for example, PCs, workstations, servers, etc., until you configure system-to-system connections by adding an entry in hosts for the remote system. You can use SAM to do this automatically by completing the following steps: 1. At the HP-UX prompt, type: sam 2.
Configuring Network Connectivity Using SAM Step 1: Configuring Network Connectivity Internet Addresses window. Proceed to step 5 if a gateway is not required for this remote connection. SAM displays fields for entering gateway information if a gateway is required for this remote system connection. Use the SAM online help system for information about gateways. 5. Activate the OK button to enable your system to communicate with this system and return to the System-to-System Connectivity object list.
Configuring Network Connectivity Using SAM Step 2: Deleting a Default Gateway Step 2: Deleting a Default Gateway To delete a default gateway that you have added with SAM, do the following: 1. Enter the following command at the HP-UX prompt: route delete default gateway_hostname where gateway_hostname is the hostname of the default gateway you want to delete. 2. Edit the /etc/rc.config.d/netconf file to remove the corresponding internet routing configuration parameter values for the gateway.
Configuring Network Connectivity Using SAM Step 2: Deleting a Default Gateway 22 Chapter 2
3 SCSI Parameter and Termination Information 23
SCSI Parameter and Termination Information Configuring SCSI Parameters Configuring SCSI Parameters In order to change the SCSI ID, the path for the card of interest must first be determined. Once the path is known, the SCSI ID may be changed. The example below lists the commands used to determine the path for the card of interest, change the SCSI ID of the A5838A, and also some of the other parameters of the card. The machine should be booted to the BCH prompt before beginning this procedure.
SCSI Parameter and Termination Information SCSI Termination Information Path (dec) Initiator ID SCSI Rate ------------ -------------- ---------- Auto Term --------------- . . 0/2/0/0 7 Fast ON . . .
SCSI Parameter and Termination Information SCSI Termination Information 26 Chapter 3
4 Troubleshooting SCSI 27
Troubleshooting SCSI Troubleshooting Troubleshooting The A5838A host bus adapter is a single field-replaceable unit (FRU) and does not contain any field-serviceable parts. Troubleshooting procedures described in this section are limited to verifying that the controller is operational and a valid connection is established. General Procedure 1. Check the connection. Make sure that the correct cable is used, connected, and operating properly and that there are no bent pins in any of the connectors. 2.
Troubleshooting SCSI Troubleshooting If diagnostics determine that the controller is defective, you must replace it. Contact your local Hewlett-Packard customer representative or call the HP Response Center. SCSI Bus Compatibility Use the SCSI command to ensure SCSI controller and SCSI device compatibility by displaying and selecting SCSI bus parameters. The SCSI command is available from the boot menu displayed after the test station has booted, provided autoboot is disabled.
Troubleshooting SCSI Troubleshooting SCSI Command Use the SCSI command to ensure SCSI controller and SCSI device compatibility by displaying and selecting SCSI bus parameters. The SCSI command is available from the boot menu displayed after the test station has booted, provided autoboot is disabled. The SCSI parameters can be displayed and modified using the SCSI command.
Troubleshooting SCSI Troubleshooting command: SCSI rate 5 2 PCI device /5.2 = fast scsi Display and Set SCSI IDs 1. Display the initiator (SCSI) IDs for all controllers, buses, and slots using the SCSI command. The following example shows the SCSI ID for the controller on bus 5 slot 2. SCSI init 5 2 PCI device /5.2 = 7 Enter the command without specifying a bus or slot number to list initiator IDs for all bus and slot numbers: SCSI init 2.
Troubleshooting SCSI Troubleshooting Contacting Your HP Representative If the equipment is covered by an HP service contract, document the problem as a service request and forward it to your HP representative. Include the following information where applicable: • Describe the problem, including the events and symptoms leading up to the problem. Attempt to describe the source of the problem.
Troubleshooting SCSI Troubleshooting • 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. HP recommends that you create the /tmp/syscore directory after successfully installing this product. Send the output of the system failure memory dump to the HP representative.
Troubleshooting SCSI Troubleshooting If the equipment is not covered by an HP service contract, there may be a charge for time and materials. SCSI Sense Codes The following example shows a typical SCSI error message.
Troubleshooting SCSI Troubleshooting SCSI Status Codes SCSI Status Code Name 0x00 good 0x02 check condition 0x04 condition met 0x08 busy 0x10 intermediate 0x14 intermediate - condition met 0x18 reservation conflict 0x22 command terminated 0x28 queue full SCSI Sense Keys Sense Key Name 0 no sense 0x1 recovered error 0x2 not ready 0x3 medium error 0x4 hardware error 0x5 illegal request 0x6 unit attention 0x7 data protect 0x8 blank check 0x9 vendor-specific 0xa copy
Troubleshooting SCSI Troubleshooting SCSI Sense Keys (Continued) Sense Key Name 0xd volume overflow 0xe miscompare 0xf reserved SCSI Additional Sense and Qualifier Codes Additional Sense Code Qualifier Code Description 0x00 0x00 no additional sense information 0x00 0x01 filemark detected 0x00 0x02 end-of-partition/medium detected 0x00 0x03 setmark detected 0x00 0x04 beginning of partition/medium detected 0x00 0x05 end-of-data detected 0x00 0x06 i/o process terminated 0x00 0x
Troubleshooting SCSI Troubleshooting SCSI Additional Sense and Qualifier Codes (Continued) Additional Sense Code Qualifier Code Description 0x04 0x04 logical unit not ready, format in progress 0x05 0x00 logical unit does not respond to selection 0x06 0x00 reference position found 0x07 0x00 multiple peripheral devices selected 0x08 0x00 logical unit communication failure 0x08 0x01 logical unit communication time-out 0x08 0x02 logical unit communication parity error 0x09 0x00 track f
Troubleshooting SCSI Troubleshooting SCSI Additional Sense and Qualifier Codes (Continued) Additional Sense Code Qualifier Code Description 0x12 0x00 address mark not found for id field 0x13 0x00 address mark not found for data field 0x14 0x00 recorded entity not found 0x14 0x01 record not found 0x14 0x02 filemark or setmark not found 0x14 0x03 end-of-data not found 0x14 0x04 block sequence error 0x15 0x00 random positioning error 0x15 0x01 mechanical positioning error 0x15 0x
Troubleshooting SCSI Troubleshooting SCSI Additional Sense and Qualifier Codes (Continued) Additional Sense Code Qualifier Code Description 0x19 0x02 defect list error in primary list 0x19 0x03 defect list error in grown list 0x1a 0x00 parameter list length error 0x1b 0x00 synchronous data transfer error 0x1c 0x00 defect list not found 0x1c 0x01 primary defect list not found 0x1c 0x02 grown defect list not found 0x1d 0x00 miscompare during verify operation 0x1e 0x00 recovered id
Troubleshooting SCSI Troubleshooting SCSI Additional Sense and Qualifier Codes (Continued) Additional Sense Code Qualifier Code Description 0x2f 0x00 commands cleared by another initiator 0x30 0x00 incompatible medium installed 0x30 0x01 cannot read medium - unknown format 0x30 0x02 cannot read medium - incompatible format 0x30 0x03 cleaning cartridge installed 0x31 0x00 medium format corrupted 0x32 0x00 no defect spare location available 0x32 0x01 defect list update failure 0x33
Troubleshooting SCSI Troubleshooting SCSI Additional Sense and Qualifier Codes (Continued) Additional Sense Code Qualifier Code Description 0x3e 0x00 logical unit has not self-configured yet 0x3f 0x00 target operating conditions have changed 0x3f 0x01 microcode has been changed 0x3f 0x02 changed operating definition 0x3f 0x03 inquiry data has changed 0x40 0x00 ram failure 0x40 nn diagnostic failure on component nn 0x41 0x00 data path failure 0x42 0x00 power-on or self-test failu
Troubleshooting SCSI Troubleshooting SCSI Additional Sense and Qualifier Codes (Continued) Additional Sense Code Qualifier Code Description 0x55 0x00 system resource failure 0x56 0x00 reserved 0x57 0x00 unable to recover table of contents 0x58 0x00 generation does not exist 0x59 0x00 updated block read 0x5A 0x00 operator request or state change input (unspecified) 0x5A 0x01 operator medium removal request 0x5A 0x02 operator selected write protect 0x5A 0x030 operator selected wri
Troubleshooting SCSI Troubleshooting SCSI Additional Sense and Qualifier Codes (Continued) Additional Sense Code Qualifier Code Description 0x68 0x00 reserved 0x69 0x00 reserved 0x6A 0x00 reserved 0x6B 0x00 reserved 0x6C 0x00 reserved 0x6D 0x00 reserved 0x6E 0x00 reserved 0x6F 0x00 reserved Chapter 4 43
Troubleshooting SCSI Troubleshooting 44 Chapter 4
5 10/100Base-TX Resources In addition to this manual, use the following resources to maintain and administer PCI 10/100Base-TX/9000.
10/100Base-TX Resources HP-UX Manual Reference Pages HP-UX Manual Reference Pages While installing, configuring, or troubleshooting 10/100Base-TX, you may need to refer to any of the following online manual reference pages (man pages) for useful HP-UX operating system or 10/100Base-TX commands. To display a man page, type the following at the system prompt: man . For example, man arp.
10/100Base-TX Resources HP-UX Manual Reference Pages • swinstall(1M) loads software filesets onto 10.x systems. • swverify(1M) verifies software installation.
10/100Base-TX Resources Error Messages Error Messages PCI 10/100Base-TX comes with an online message catalog that is used to report networking problems. You must use the nettl logging and tracing utility to display the probable cause and action for a message.
10/100Base-TX Resources Logging Messages Logging Messages HP 100Base-TX/9000 uses the nettl(1M) logging and tracing facility supplied with HP-UX. You may access the logging and tracing utility using either the graphical user interface (GUI) version or the command line interface. Features of the GUI version, which are now a part of your HP 9000 system, include: • An interface which guides you through logging and tracing tasks. • An interface which allows you to create and format reports.
10/100Base-TX Resources Logging Messages <6011> HP PCI 10/100Base-T driver detected bad cable connection between the adapter in slot 2 and the hub or switch. • To examine just the log messages in the log file. netfmt -f /var/adm/nettl.LOG00 • To check network logging and tracing status. nettl -status • To start 10/100Base-TX tracing to the file /tmp/tracefile.TRC0. nettl(1m) adds the .TRC0 postfix for you. nettl -traceon all /tmp/tracefile -entity PCI100bt -file • To stop 100Base-TX tracing.
10/100Base-TX Resources Manual Installation and Configuration Manual Installation and Configuration If you want to manually install and configure your 10/100Base-TX/9000 product, refer to the detailed instructions in the Installing and Administering LAN/9000 Software manual.
10/100Base-TX Resources Contacting Your HP Representative Contacting Your HP Representative If you have no service contract with HP, you may follow the procedure described below, but you will be billed accordingly for time and materials. If you have a service contract with HP, document the problem as a Service Request (SR) and forward it to your HP representative. Include the following information where applicable: • A characterization of the problem.
10/100Base-TX Resources Contacting Your HP Representative • Save all network log files. Make sure that ERROR and DISASTER log classes are enabled when log files are collected. 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.
10/100Base-TX Resources Contacting Your HP Representative 54 Chapter 5
6 Troubleshooting 10/100Base-TX/9000 This chapter provides guidelines for troubleshooting 10/100Base-TX.
Troubleshooting 10/100Base-TX/9000 • Troubleshooting Overview. • Diagnostic Flowcharts.
Troubleshooting 10/100Base-TX/9000 Performance Troubleshooting Performance Troubleshooting This section is intended to provide system administrators or advanced users with detailed information on how to troubleshoot performance related problems with the PCI 100BT product. Below, a few key terms are defined to help in understanding the troubleshooting information.
Troubleshooting 10/100Base-TX/9000 Performance Troubleshooting are in the transmit FIFO. While the current Transmit Threshold value allows the PCI 100BT product to achieve it's best performance, it also increases the probability of Transmit Underrun errors. A large number of Transmit Underrun errors (more than 1 out of every 1000 packets) can cause a noticeable drop in networking performance.Transmit Underrun errors may occur when there is sufficient bus contention from competing I/O devices.
Troubleshooting 10/100Base-TX/9000 Performance Troubleshooting a TransmitThreshold of 1500 is conservative In all of the cases above after setting the Transmit Threshold mode as specified, the lanadmin command will echo the current speed of the interface as follows; this output may be ignored (output shown for 100 Mbits/s operation): old speed= 100000000 new speed= 100000000 After issuing the lanadmin -S you must wait at least 5 seconds before attempting to use the specified network interface.
Troubleshooting 10/100Base-TX/9000 Troubleshooting Overview Troubleshooting Overview 10/100Base-TX problems can be caused by problems in a variety of hardware and software components. The problem impacting your system may originate in another part of the 10/100Base-TX network. As with any troubleshooting, a systematic approach is helpful. The following two tables and the following flowcharts provide a logical sequence of steps to follow when troubleshooting 10/100Base-TX/9000.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Diagnostic Flowcharts Below is a summary of the types of network tests in the diagnostic flowcharts. Follow the flowcharts in sequence beginning with flowchart 1. Continue sequentially through flowcharts 2, 3, 4, 5, 6, 7, 8, and 9, referring back to flowchart 1 (ping), as indicated at the end of each flowchart, until you have corrected the problem.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Transport Level Loopback Test: Checks roundtrip communication between Transport Layers on the source and target host using ARPA services telnet and ftp commands. Bridge/Gateway Loopback Test: Checks general network connections through a gateway.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 1: Network Level Loopback Test Figure 6-1 Flowchart 1: Network Level Loopback Test 1 A Execute: ping to remote host B ping successful ? yes Stop no C Network unreachable ? yes 3 no D Command hangs ? yes 2,3,4,5 6&7 no E F Unknown host ? yes Correct BIND, YP or /etc/hosts configuration 1 no H G No route to host ? yes Add route table entry no Call HP Chapter 6 63
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 1 Procedures A. Execute: ping to remote host. Using ping(1M), send a message to the remote host to which you are having problems connecting. For example: ping spiff B. ping successful? A message is printed to stdout for each ping packet returned by the remote host. If packets are being returned, your system has network level connectivity to the remote host. Note what percentage of the total packets are lost, if any.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 2: 10/100Base-TX Connections/LED Test Figure 6-2 Flowchart 2: 10/100Base-TX Connections/LED Test 2 C A Check: Power outlet LED Display: B 100 Mbit LED=ON Test Errorport Message 10onMbit port LED=OFF Screen (dmesg ouput) Check card installation. yes Reset card. Call HP if problem persists. ? no 1 D Check status of Link LED F E yes Link LED = OFF ? Check connection to hub or switch. Ensure switch is autonegotiating.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 2 Procedures A. Check Power outlet. Ensure the power cord is plugged in to a live outlet. B. Test Error Message on Screen? At the HP-UX prompt, type the dmesg command, and look for an error message. Does the dmesg output show an error message from btlan? If not, go to step D.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 3: Configuration Test Figure 6-3 Flowchart 3: Configuration Test 3 A Execute: lanscan B D Is your interface displayed ? yes C no Run ioscan -f E Is driver in kernel ? yes no F G yes 5 Install driver. Verify or edit /stand/system to add driver keyword btlan Regen kernel.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 3 Procedures NOTE Check that your 10/100Base-TX connectors to the card and hub (or wall plug) are fully connected before beginning this flowchart. A. Execute: lanscan. Enter the lanscan command to display information about LAN cards that are successfully bound to the system. See the lanscan online manpage for more detailed information. B.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts similar to the following will be displayed: Chapter 6 69
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Class I H/W Path Driver S/W State H/W Type Description ======================================================================== bc 0 root CLAIMED BUS_NEXUS bc 1 8 ccio CLAIMED BUS_NEXUS I/O Adapter bc 2 10 ccio CLAIMED BUS_NEXUS I/O Adapter ext_bus 0 10/0 c720 CLAIMED INTERFACE GSC built-in Fast/Wide SCSI Interface bc 3 10/4 bc CLAIMED BUS_NEXUS Bus Converter tty 0 10/4/0 mux2 CLAIMED INTERFACE MUX lanmux 2
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts E. Is driver in kernel? If the driver has not been generated into the kernel, ioscan output will be: ioscan -f Class I Description H/W Path Driver S/W State H/W Type =============================================================== ==== unknown -1 10/4/4 UNKNOWN UNCLAIMED INTERFACE The class and driver fields alone will indicate “unknown” status if the kernel has not been generated. If the driver has not been generated, continue to step H.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 4: Configuration Test Figure 6-4 Flowchart 4: Configuration Test 4 A Execute: netfmt B Check causes and actions on display in the formatted log output C Problem solved ? yes 1 no D Execute: lanadmin E Select LAN from Menu F Select NMID command and enter 10/100 Base-TX nmid G Reset card H Reset successful yes 1 ? no 4A 72 Chapter 6
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 4 Procedures A. Execute: netfmt. Use the netfmt command to view log data (error and disaster messages). An example command is shown below. netfmt -v -f /var/adm/nettl.LOG00 | more B. Check causes and actions on display in the formatted log output. Use the time stamp to find the proper logs. Ensure that you are looking at the 10/100Base-TX information. C. Problem solved. If yes, go to flowchart 1. If not, continue with step D. D.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 4A: Configuration Test Figure 6-5 Flowchart 4A: Configuration Test 4A A Execute: netfmt B Check causes and actions on display in the formatted log output C Problem solved yes 1 ? no Call HP Flowchart 4A Procedures A. Execute: netfmt. Use the netfmt command to view log data (error and disaster messages). An example netfmt command is shown below: netfmt -v -f /var/adm/nettl.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts 10/100Base-TX information. C. Chapter 6 Problem solved. If yes, go to flowchart 1. If not, contact your HP representative.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 5: Configuration Test Figure 6-6 Flowchart 5: Configuration Test 5 A Execute ifconfig ... up B Execute: ifconfig E C ifconfig successful ? D no Are flags correct ? yes H Correct ifconfig flag settings 5 yes ifconfig entry in /etc/rc.config.d/netconf : ? yes F Any error messages returned no Call HP ? yes no I no G Add ifconfig command to /etc/rc.config.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Execute ifconfig on the interface you want to configure in order to ensure that the interface is enabled. For example, to configure the 10/100Base-TX interface lan1, enter: ifconfig lan1 192.6.1.17 up For more examples of the ifconfig command, refer to the ifconfig(1M) online man page. B. Execute: ifconfig . Execute ifconfig without the up parameter again on the interface you want to test to check the flag setting for the up parameter.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts I. 78 Add ifconfig command to /etc/rc.config.d/netconf file. Add the ifconfig command to /etc/rc.config.d/netconf, and reboot. For more information, refer to the ifconfig(1M) online man page. Go to flowchart 1 to verify that the problem has been solved.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 6: Network Level Loopback Test Figure 6-7 Flowchart 6: Network Level Loopback Test 6 A Host entry in ARP cache ? B no Remote host up ? yes 1 no yes C Bring up remote host 1 E D Entry complete ? no Use arp to complete entry yes F ping local host 1 Chapter 6 79
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 6 Procedures A. Host entry in ARP cache? Using arp, check that an entry exists for the remote host in your system's ARP cache. For example: arp spiff B. Remote host up? If there is no ARP cache entry for the remote host, first check that the remote host is up. If not, the remote host has not broadcast an ARP message, and that probably is why there is no entry in the ARP cache. C. Bring-up remote host.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 7: Link Level Loopback Test Figure 6-8 Flowchart 7: Link Level Loopback Test 7 A Execute: linkloop to remote host B yes linkloop successful ? 1 no D C Loopback FAILED: Address has bad format E Loopback FAILED: Not an individual address F Loopback FAILED G Choose a different remote host; re-execute linkloop Correct the link address parameter 7 H 6 no linkloop successful ? yes I Check remote host’s connectivity to 100Base-T
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 7 Procedures A. Execute: linkloop to remote host. Enter the NMID of your 10/100Base-TX card and link level address (station address) of the remote host in hexadecimal form (preceded by “0x”). Execute lanscan (1M) on the local system to find the NMID and obtain the link level address (station address) of the remote host. For more information on linkloop, refer to the linkloop(1M) online man page. B.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts flowchart 1 to verify configuration of the remote host.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 8: Transport Level Loopback Test (using ARPA) Figure 6-9 Flowchart 8: Transport Level Loopback Test (using ARPA) 8 A Execute: telnet to remote host B Successful ? yes Stop no C Execute: ftp to remote host D Successful ? yes Call HP no E TCP not configured on local or remote host ? G yes Configure TCP 8 no F Network congested ? no yes Call HP Call HP 84 Chapter 6
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 8 Procedures A. Execute: telnet to remote host. Try to establish a telnet connection to the remote host. B. Successful? If your telnet attempt was successful, stop. The connection is o.k. through the Transport Layer (OSI Layer 4). C. Execute: ftp to remote host. Unlike telnet, ftp does not go through a pseudoterminal driver (pty) on your system. This step tests to see if the pty is why telnet failed. D.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 9: Bridge/Gateway Loopback Test Figure 6-10 Flowchart 9: Bridge and Gateway Loopback Test 9 A Execute: ping from known good host through gateway to known good host C B yes Check route table on problem host and all hosts between Successful ? D no E Examine gateway Correct route tables 1 F G Non-HP 9000 or other vendors.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts Flowchart 9 Procedures A. Execute: ping from known good host through gateway to known good remote host. This will test gateway connectivity to the remote network. B. Successful? If the executing ping returned successfully, the problem may exist in the routing table for the problem host. Go to C. C. Check route table on problem host and all hosts in between. Execute netstat -r to examine a route table. D. Examine gateway.
Troubleshooting 10/100Base-TX/9000 Diagnostic Flowcharts gateway.
A 10/100Base-TX Interface Card Statistics 89
10/100Base-TX Interface Card Statistics LAN Interface Status Display LAN Interface Status Display This appendix contains descriptions of the RFC 1213 MIB II statistics fields for LAN interface cards which are displayed on the screen with the display command in lanadmin LAN Interface Test Mode. A description of each field follows the display.
10/100Base-TX Interface Card Statistics LAN Interface Status Display Deferred Transmissions Late Collisions Excessive Collisions Internal MAC Transmit Errors Carrier Sense Errors Frames Too Long Internal MAC Receive Errors Appendix A = = = = = = 0 0 0 0 0 0 = 0 91
10/100Base-TX Interface Card Statistics RFC 1213 MIB II RFC 1213 MIB II For more detailed information about the fields described below, refer to RFC 1213. Field Description Network Management ID A unique ID assigned by the system for the network management of each network interface. Description A textual string containing information about the interface.
10/100Base-TX Interface Card Statistics RFC 1213 MIB II Operation Status The current operational state of the interface. This value is the same as the hardware status displayed by lanscan(1M). It will have one of the following values. Last Change up(1) Ready to pass packets down(2) Not operative (card is down) testing(3) In test mode The value of SysUpTime at the time the interface entered its current operational state.
10/100Base-TX Interface Card Statistics RFC 1213 MIB II Outbound Non-Unicast Packets The total number of packets that higher-level protocols requested be transmitted to a non-unicast (a subnetwork-broadcast or subnetwork-multicast) address, including those that were discarded or not sent. Outbound Discards The number of outbound packets that were discarded even though no errors had been detected to prevent their being transmitted.
10/100Base-TX Interface Card Statistics RFC 1284 Ethernet-Like Interface Statistics RFC 1284 Ethernet-Like Interface Statistics Field Description Index A value that uniquely identifies an interface to an 802.3 medium. Alignment Errors A count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check.
10/100Base-TX Interface Card Statistics RFC 1284 Ethernet-Like Interface Statistics condition was lost or never asserted when attempting to transmit a frame on a particular interface. Frames Too Long A count of frames received on a particular interface that exceed the maximum permitted framer size. Internal MAC Receive Errors A count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error.
10/100Base-TX Interface Card Statistics Create a Record or Map of Your Internetwork Create a Record or Map of Your Internetwork Be sure to create or update a record of your network and internetwork before attempting 10/100Base-TX installation. You may wish to create a map showing how pieces of your internetwork are related. Your records should include: • Approximate dimensions of the building or room containing the 10/100Base-TX network.
10/100Base-TX Interface Card Statistics Create a Record or Map of Your Internetwork 98 Appendix A
B Hardware Reference Information This appendix contains information about the card LEDs, cabling specifications and card specifications.
Hardware Reference Information Basic Troubleshooting Tips Basic Troubleshooting Tips Listed below are some tips on troubleshooting common hardware problems. Refer to this information when you are trying to identify 10/100Base-TX hardware problems. • Check the network cables. Make sure the network cable connections are secure and that the cables are not damaged.
Hardware Reference Information Connector Information Connector Information This section includes pin usage information for the RJ-45 twisted pair connector. Connectors on LAN adapters adhere to appropriate standards agreed upon by various standards bodies and are widely available. Incorrectly wired or installed cabling is the most common cause of communications problems for local area networks. HP recommends that you work with a qualified cable installer for assistance in your cabling requirements.
Hardware Reference Information Connector Information Figure B-1 Pin Layout of RJ-45 Connector on PCI Card 8 1 Available HP Cables: • HP 92268A - 4 meter with attached 8-pin connectors. • HP92268B - 8-meter with attached 8-pin connectors. • HP 92268C - 16-meter with attached 8-pin connectors. • HP 92268D - 32-meter with attached 8-pin connectors. • HP 92268N- 300-meter (no connectors supplied).
Hardware Reference Information Connector Information Table B-2 IEEE 802.3u 100Base-TX Standard Pins Signal TX End Node 4 Unused 5 Unused 7 Unused 8 Unused Available HP Cables: • HP 92268A - 4 meter with attached 8-pin connectors. • HP92268B - 8-meter with attached 8-pin connectors. • HP 92268C - 16-meter with attached 8-pin connectors. • HP 92268D - 32-meter with attached 8-pin connectors. • HP 92268N- 300-meter (no connectors supplied).
Hardware Reference Information Cabling Information Cabling Information Connectors on LAN adapters adhere to appropriate standards agreed upon by various standards bodies and are widely available. Incorrectly wired or installed cabling is the most common cause of communications problems for local area networks. HP recommends that you work with a qualified cable installer for assistance in your cabling requirements. Cable Lengths Following are the maximum cable lengths from the switch to each node.
Hardware Reference Information Dual Port 100Base-TX and Dual Port Wide Ultra 2 SCSI Specifications Dual Port 100Base-TX and Dual Port Wide Ultra 2 SCSI Specifications A5838A Specifications Physical Dimensions: 7.9 in by 4.2 in Electrical Power requirement (: +15 watts max Environmental Temperature Degrees F = (1.
Hardware Reference Information Dual Port 100Base-TX and Dual Port Wide Ultra 2 SCSI Specifications Cable Interfaces • The 10/100Base-TX ports are compatible with IEEE 802.3u standard and use RJ-45 connectors. Communications Standards • The physical layer of IEEE 802.3ustandard supports Cat 5 or Cat 5E UTP cables.
C Hardware Regulatory Statements This section contains hardware regulatory statements for the Dual Port 100Base-TX and Dual Port Ultra2 SCSI product used in the United States, Canada, and the European community. Refer to your Dual Port 100Base-TX and Dual Port Ultra2 SCSI Quick Installation card for product installation instructions.
Hardware Regulatory Statements FCC Statement (For U.S.A.) FCC Statement (For U.S.A.) Federal Communications Commission Radio Frequency Interference Statement WARNING 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 received, including interference that might cause undesired operation.
Hardware Regulatory Statements EMI Statement (European Community) EMI Statement (European Community) NOTE This is a Class A product. In a domestic environment, this product may cause radio interference, in which case you may be required to take adequate measures.
Hardware Regulatory Statements EMI Statement (European Community) 110 Appendix C
Glossary 10Base-T: A 10 Mbit/s communication method specified in the IEEE 802.3u-1995 standard. 100Base-T: A 100 Mbit/s communication method specified in the IEEE 802.3u-1995 standard. The official name for Fast Ethernet. 100Base-TX: A specific implementation of 100Base-T designed to operate over Category 5 UTP cabling. Address: A specific location in memory, designated either numerically or by a symbolic name. Alias: Name of the interface that corresponds to a given Internet address on a system.
used to transmit data, status, and control signals. EISA, PCI, and SCSI are examples of buses. Bus Mastering A high-performance way to transfer data. The host adapter controls the transfer of data directly to and from system memory without bothering the computer’s microprocessor. This is the fastest way for multi-tasking operating systems to transfer data. Byte A unit of information consisting of eight bits. CSMA/CD: Carrier sense multiple access with collision detection.
message communications to STREAMS-based network interface drivers. DMA (direct memory access) A method of moving data from a storage device directly to RAM, without using the CPU’s resources. DMA Bus Master A feature that allows a peripheral to control the flow of data to and from system memory by blocks, as opposed to PIO (Programmed I/O) where the flow is byte by byte. EEPROM (electronically erasable programmable read-only memory) A memory chip typically used to store configuration information. See NVRAM.
networks whereby data can flow in only one direction at a time across the multiple wire pairs of a physical link. Hard Disk A rigid disk permanently sealed into a drive cartridge. A hard disk can store very large amounts of information. Hardware Path: An identifier assigned by the system according to the physical location (slot) of the card in the hardware backplane. On Series 800 systems, the I/O subsystem identifies each LAN card by its hardware path.
Internet Address: The network address of a computer node. This address identifies both which network the host is on and which host it is. Refer to the Installing and Administering LAN/9000 Software manual for detailed information about network addressing. IP Address: See Internet Address glossary entry. IRQ (interrupt request channel) A path through which a device can get the immediate attention of the computer’s CPU. The PCI bus assigns an IRQ path for each SCSI host adapter.
Major Number: Unique value that identifies an individual hardware device.The number for the 10/100Base-TX card floats. Maximum Transmission Unit (MTU). Largest amount of data that can be transmitted through that interface. This value does not include the LLC or MAC headers. MByte (megabyte) A measure of computer storage equal to 1024 kilobytes. Motherboard See mainboard. In some countries, the term motherboard is not appropriate.
Packet: A sequence of binary digits that is transmitted as a unit in a computer network. A packet usually contains control information plus data. Parity Checking A way to verify the accuracy of data transmitted over the SCSI bus. One bit in the transfer is used to make the sum of all the 1 bits either odd or even (for odd or even parity). If the sum is not correct, an error message appears. SCSI uses odd parity. PCI: Peripheral component interconnect.
lost when the computer is turned off. RISC Core Symbios SCSI chips contain a RISC (Reduced Instruction Set Computer) processor, programmed through microcode scripts. RJ-45: The name for the connector type used with UTP cabling. ROM (Read-Only Memory) Memory from which information can be read but not changed. The contents of ROM are not erased when the computer is turned off.
which share the same network address space. Refer to the Installing and Administering LAN/9000 Software manual for detailed information about subnetworks and subnet addressing. Subnet mask: A 32-bit mask which, when AND'd with an internet address, determines a subnetwork address. When the internet address is AND'd with the subnet mask, the ones in the host portion of the subnet mask will “overwrite” the corresponding bits of the host portion of the internet address, resulting in the subnet address.
consisting of pairs of wires twisted together without an electrically shielding jacket. VCCI Voluntary Control Council for Interference. VHDCI Very High Density Cable Interconnect. Wide SCSI A SCSI-2 feature allowing 16 or 32-bit transfers on the SCSI bus. This dramatically increases the transfer rate over the standard 8-bit SCSI bus. Wide Ultra SCSI The SCSI Trade Association term for SCSI bus width 16 bits, SCSI bus speed maximum data rate 40 MBytes/sec.
