System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

private loop device didn't acquire hard address on msl

S. Ney
Trusted Contributor

private loop device didn't acquire hard address on msl

I have a msl2024 fiber direct attached to a hpux rx4640. It has a scsi cable run to the ultrium 3 tape drive. We had a system power event awhile back and when the system came back up the tape drive isn't seen. syslog and dmesg provide the familar output:
vmunix: 0/3/2/1: private loop device didn't acquire its hard address:
vmunix: Hard Address is 0x0, but acquired AL_PA is 0x1.
vmunix: System won't be able to see LUNs behind this device port.
vmunix: It appears that there are (or were) more than one device with the
vmunix: same address setting.
vmunix: NOTE: Even after you change the address settings on the devices,
vmunix: it may be necessary to reset or power-cycle both the
vmunix: devices whose settings have been changed, and any remaining
vmunix: device with the address setting which encountered the
vmunix: conflict.
vmunix: EXAMPLE: You see this diagnostic message and find three devices with
vmunix: address setting 0x05. You change one device to address 0x06
vmunix: and another to 0x07. You now may need to reset or
vmunix: power-cycle ALL THREE devices.
also ioscan now omits fcp address and below.

H/W Path Class Description
==========================================================
root
0 ioa System Bus Adapter (1229)
0/0 ba Local PCI-X Bus Adapter (122e)
0/0/1/0 tty PCI SimpleComm (103c1290)
0/0/1/1 tty PCI Serial (103c1048)
0/0/2/0 OO USB OHCI Interface
0/0/2/1 OO USB OHCI Interface
0/0/2/2 OO USB EHCI Interface
0/0/3/0 sideba CMD IDE controller
0/0/3/0.0 ext_bus IDE Primary Channel
0/0/3/0.0.0 target
0/0/3/0.0.0.0 disk TEAC DV-28E-N
0/0/3/0.0.7 target
0/0/3/0.0.7.0 ctl Initiator
0/0/3/0.1 ext_bus IDE Secondary Channel
0/0/3/0.1.7 target
0/0/3/0.1.7.0 ctl Initiator
0/0/4/0 graphics PCI Display (10025159)
0/1 ba Local PCI-X Bus Adapter (122e)
0/1/1/0 ba PCItoPCI Bridge
0/1/1/0/4/0 ext_bus PCI-X SmartArray 6402 RAID Controller
0/1/1/0/4/0.0 target
0/1/1/0/4/0.0.0 disk HP LOGICAL VOLUME
0/1/1/0/4/0.0.1 disk HP LOGICAL VOLUME
0/1/1/0/4/0.0.2 disk HP LOGICAL VOLUME
0/1/1/0/4/0.0.3 disk HP LOGICAL VOLUME
0/1/1/0/4/0.7 target
0/1/1/0/4/0.7.0 ctl Initiator
0/1/2/0 lan HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core
0/1/2/1 lan HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core
0/2 ba Local PCI-X Bus Adapter (122e)
0/2/1/0 lan HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter
0/2/1/1 lan HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter
0/3 ba Local PCI-X Bus Adapter (122e)
0/3/2/0 fc HP A6826-60001 2Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 1)
0/3/2/1 fc HP A6826-60001 2Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 2)
0/4 ba Local PCI-X Bus Adapter (122e)
0/4/1/0 fc HP A6826-60001 2Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 1)
0/4/1/1 fc HP A6826-60001 2Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 2)
0/4/2/0 lan HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter
0/4/2/1 lan HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter
0/5 ba Local PCI-X Bus Adapter (122e)
0/5/1/0 ext_bus SCSI Ultra320 A6961-60011
0/5/1/0.7 target
0/5/1/0.7.0 ctl Initiator
0/5/1/1 ext_bus SCSI Ultra320 A6961-60011
0/5/1/1.7 target
0/5/1/1.7.0 ctl Initiator
120 processor Processor
121 processor Processor
122 processor Processor
123 processor Processor
250 ba Core I/O Adapter
250/0 ipmi IPMI Controller
250/1 acpi_node Acpi Hardware

I have an old ioscan that shows:
Class I H/W Path Driver S/W State H/W Type Description
==============================================================================
root 0 root CLAIMED BUS_NEXUS
ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapter (1229)
ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
tty 0 0/0/1/0 asio0 CLAIMED INTERFACE PCI SimpleComm (103c1290)
/dev/diag/mux0 /dev/mux0 /dev/tty0p0
tty 1 0/0/1/1 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag1 /dev/diag/mux1 /dev/mux1 /dev/tty1p0 /dev/tty1p2 /dev/tty1p4
OO 0 0/0/2/0 UsbOhci CLAIMED INTERFACE USB OHCI Interface
OO 1 0/0/2/1 UsbOhci CLAIMED INTERFACE USB OHCI Interface
OO 2 0/0/2/2 UsbEhci CLAIMED INTERFACE USB EHCI Interface
sideba 0 0/0/3/0 side_multi CLAIMED INTERFACE CMD IDE controller
ext_bus 0 0/0/3/0.0 side CLAIMED INTERFACE IDE Primary Channel
target 0 0/0/3/0.0.0 tgt CLAIMED DEVICE
disk 0 0/0/3/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-N
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
target 1 0/0/3/0.0.7 tgt CLAIMED DEVICE
ctl 0 0/0/3/0.0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
ext_bus 1 0/0/3/0.1 side CLAIMED INTERFACE IDE Secondary Channel
target 2 0/0/3/0.1.7 tgt CLAIMED DEVICE
ctl 1 0/0/3/0.1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t7d0
graphics 0 0/0/4/0 gvid_core CLAIMED INTERFACE PCI Display (10025159)
ba 1 0/1 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
ba 2 0/1/1/0 PCItoPCI CLAIMED BUS_NEXUS PCItoPCI Bridge
ext_bus 2 0/1/1/0/4/0 ciss CLAIMED INTERFACE PCI-X SmartArray 6402 RAID Controller
/dev/ciss2
target 3 0/1/1/0/4/0.0 tgt CLAIMED DEVICE
disk 1 0/1/1/0/4/0.0.0 sdisk CLAIMED DEVICE HP LOGICAL VOLUME
/dev/dsk/c2t0d0 /dev/dsk/c2t0d0s2 /dev/rdsk/c2t0d0 /dev/rdsk/c2t0d0s2
/dev/dsk/c2t0d0s1 /dev/dsk/c2t0d0s3 /dev/rdsk/c2t0d0s1 /dev/rdsk/c2t0d0s3
disk 2 0/1/1/0/4/0.0.1 sdisk CLAIMED DEVICE HP LOGICAL VOLUME
/dev/dsk/c2t0d1 /dev/dsk/c2t0d1s2 /dev/rdsk/c2t0d1 /dev/rdsk/c2t0d1s2
/dev/dsk/c2t0d1s1 /dev/dsk/c2t0d1s3 /dev/rdsk/c2t0d1s1 /dev/rdsk/c2t0d1s3
disk 3 0/1/1/0/4/0.0.2 sdisk CLAIMED DEVICE HP LOGICAL VOLUME
/dev/dsk/c2t0d2 /dev/rdsk/c2t0d2
disk 4 0/1/1/0/4/0.0.3 sdisk CLAIMED DEVICE HP LOGICAL VOLUME
/dev/dsk/c2t0d3 /dev/rdsk/c2t0d3
target 4 0/1/1/0/4/0.7 tgt CLAIMED DEVICE
ctl 2 0/1/1/0/4/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c2t7d0
lan 0 0/1/2/0 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core
lan 1 0/1/2/1 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core
ba 3 0/2 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
lan 2 0/2/1/0 iether CLAIMED INTERFACE HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter
lan 3 0/2/1/1 iether CLAIMED INTERFACE HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter
ba 4 0/3 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
fc 0 0/3/2/0 fcd CLAIMED INTERFACE HP A6826-60001 2Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 1)
/dev/fcd0
fc 1 0/3/2/1 fcd CLAIMED INTERFACE HP A6826-60001 2Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 2)
/dev/fcd1
fcp 0 0/3/2/1.8 fcd_fcp CLAIMED INTERFACE FCP Protocol Adapter
ext_bus 5 0/3/2/1.8.0.255.7 fcd_vbus CLAIMED INTERFACE FCP Device Interface
target 7 0/3/2/1.8.0.255.7.13 tgt CLAIMED DEVICE
tape 0 0/3/2/1.8.0.255.7.13.0 stape CLAIMED DEVICE HP Ultrium 3-SCSI
/dev/rmt/0m /dev/rmt/0mn /dev/rmt/c5t13d0BEST /dev/rmt/c5t13d0BESTn
/dev/rmt/0mb /dev/rmt/0mnb /dev/rmt/c5t13d0BESTb /dev/rmt/c5t13d0BESTnb
unknown -1 0/3/2/1.8.0.255.7.13.1 UNCLAIMED UNKNOWN HP MSL G3 Series
ba 5 0/4 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
fc 2 0/4/1/0 fcd CLAIMED INTERFACE HP A6826-60001 2Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 1)

So the question is how/where do I fix the hardware conflict? I've changed the al_pa on the OCP of the tape drive however the error remains the same after numerous attempts.I have also have tried to change the alpa in the efi shell with the drvcfg utility. So I'd like to see if I can get some of the guru's here to help resolve this issue. I'd like to be able to use the tape drive again and there really isn't a resolution to any previous hardware conflict threads on the itrc.