AB379B Fibre Channel Mass Storage Adapter Installation Guide, February 2007
Table Of Contents
- AB379B Fibre Channel Mass Storage Adapter Installation Guide
- 1 Fibre Channel Adapter Installation for HP-UX
- Prerequisites
- Important Patches and Updates
- Installing Driver Software
- Installing Adapter Hardware
- Attaching the Adapter to Other Fibre Channel Devices
- Verifying the Fibre Channel Adapter Installation
- LED Interpretation
- Obtaining Card Information after Installation
- Verifying Connectivity
- Interpreting Legacy Hardware Paths (HP-UX 11i v1 and 11i v2)
- Interpreting Lunpath Hardware Paths (HP-UX 11i v3)
- Components of Lunpath Hardware Paths
- Fibre Channel
- 2 Fibre Channel Adapter Installation for OpenVMS
- Prerequisites
- Installing Driver Software
- Installing Adapter Hardware
- Attaching the Adapter to Other Fibre Channel Devices
- Verifying the Fibre Channel Adapter Installation
- Additional Configuration Information
- LED Interpretation
- A Technical Specifications and Regulatory Information
- AB379B Technical Specifications
- FCC Statement (For U.S.A.)
- Canada
- EMI (Australia and New Zealand)
- VCCI (Japan) (PCI Card Only)
- EMI Statement (European Community)
- Laser Safety Statements
- AB379B Declaration of Conformity
Fibre Channel Adapter Installation for HP-UXInterpreting Lunpath Hardware Paths (HP-UX 11i v3)Chapter 117Interpreting Lunpath Hardware Paths (HP-UX 11i v3)Lunpath hardware paths are a new representation of hardware paths introduced on HP-UX 11i v3, as part ofthe new agile representation of mass storage devices. For more details, please refer to the Next GenerationMass Storage Stack HP-UX 11i v3 white paper athttp://docs.hp.com/en/netsys.html#Storage%20Area%20Management .This section describes how to interpret address elements in lunpath hardware paths. It also shows how tomap between the legacy hardware path and lunpath hardware path formats.Components of Lunpath Hardware PathsThe lunpath hardware path has three parts:1. The HBA path is composed of a series of bus-nexus addresses, separated by a slash (/). It is identical to theHBA portion of a legacy hardware path.2. The target address is transport-specific. With Fibre Channel, it is a port identifier. When printed by I/Ocommands like ioscan, the target address is separated from the HBA path by a period (.) and is printed inhexadecimal notation.3. The LUN address is a SCSI 64-bit LUN indentifier, built from the address method and the LUN number.When printed by I/O commands, it is separated from the target address by a period (.) and is printed inhexadecimal notation.The following table provides four examples:Fibre ChannelThe target address for a Fibre Channel device is the target port’s worldwide port name (WWPN). Thefcmsutil command with the get remote option displays the WWPN as the Target Port World Wide Name. Inthis example, the WWPN is 0x500805f300083899:# fcmsutil /dev/td0 get remote allTarget N_Port_id is = 0x010700Target state = DVS_READYSymbolic Name =Port Type = N_PORTSLER Capable (supports Retry & TRID) = NOTarget Port World Wide Name = 0x500805f300083899Table 1-5Lunpath Hardware pathHBApathTarget address LUN address0/5/1/0.0x50060e8004276e12.0x40000000000000000/5/1/0 0x50060e8004276e12 0x40000000000000000/4/1/0.0x500805f300083899.0x40100000000000000/4/1/0 0x500805f300083899 0x4010000000000000
- A Technical Specifications and Regulatory Information
- Interpreting Lunpath Hardware Paths (HP-UX 11i v3)