Operating System - HP-UX
1834599 Members
4415 Online
110069 Solutions
New Discussion

HBA's not communicating with DMX-3

 
David P. Waters
Occasional Contributor

HBA's not communicating with DMX-3

Okay, I have a good one!!

Env: I have a HP SuperDome (SD32A from 'model') directly connected to a DMX-3 through FC-AL. The SuperDome is divided up into 2 nPar each has 4 fibre connections to 8 FA ports on the DMX. The HBA's are A6795A, driver B.11.11.12. nPars are running 11.11

Issue: I can only see LUNS down one FA port on the DMX no matter which cable I use or which card out of the 8 I use........done only one FA port on the DMX. 'fcmsutil /dev/td#' on each of the hba's displays the following:

/opt/fcms/bin/fcmsutil /dev/td0

Vendor ID is = 0x00103c
Device ID is = 0x001029
XL2 Chip Revision No is = 2.3
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x00128c
Topology = PRIVATE_LOOP
Link Speed = 2Gb
Local N_Port_id is = 0x000001
Local Loop_id is = 125
N_Port Node World Wide Name = 0x500110a000118f65
N_Port Port World Wide Name = 0x500110a000118f64
Driver state = ONLINE
Hardware Path is = 0/0/2/1/0
Number of Assisted IOs = 867
Number of Active Login Sessions = 0
Dino Present on Card = NO
Maximum Frame Size = 2048
Driver Version = @(#) libtd.a HP Fibre Channel Tachyon TL/TS/XL2 Driver B.11.11.12 PATCH_11.11 (PHSS_31326) /ux/kern/kisu/TL/src/common/wsio/td_glue.c: Sep 5 2005, 10:14:40

Each of the hba's displays the same. However, the 'fcmsutil /dev/td# get remote all' only works on the hba that is plugged into the good FA on the DMX. It display the following:

/opt/fcms/bin/fcmsutil /dev/td0 get remote all

Target N_Port_id is = 0x0000da
Target Loop_id is = 7
Target state = DVS_UNOPENED
Symbolic Name =
Port Type = NL_PORT
SLER Capable (supports Retry & TRID) = NO
Target Port World Wide Name = 0x50060482d52e0e07
Target Node World Wide Name = 0x50060482d52e0e07

Common Service parameters (all values shown in hex):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Version_Hi: 9 Version_Low: 9
BB_Credit: 0 Ciro: 1
Alt_BBcred: 1 Rxsz: 800
Conseq: ff RO_Bitmap: 2
Resolution: 0 EDTOV(ms): 3e8

Vendor version (in hex) 0 0 0 0
-------------------------------------------------------------

Notice the "Target State". The other hba's return "No Device Found" when I run the same command on them.

##### NOTE #####
Here's the catch (pay attention): I can run any cable from any FA port on the DMX that is NOT visible to the above mentioned nPars to a totally different HP SuperDome (older model) HBA......LUNS are visible down the FA.

Any ideas? It seems as if the newer SuperDome is not allowing multiple hba logins to the DMX-3.

NOTE: HP and EMC are looking into the case.

2 REPLIES 2
Christian Tremblay
Trusted Contributor

Re: HBA's not communicating with DMX-3

Topology = PRIVATE_LOOP

Shouldn't that be FABRIC ?
David P. Waters
Occasional Contributor

Re: HBA's not communicating with DMX-3

Not for a direct connect. A switched topology would show FABRIC.