System won't be able to see LUNs behind this device port

sinzi76 — Thu, 12 Mar 2009 04:49:20 GMT

Hi Dear.

I used rp7420 and Overland neo4000(vtl)

FC card replace from emulex to A6826A.

But Don't show VTL autoch and tape

=======syslog.log=====

1/0/10/1/0: private loop device didn't acquire its hard address:
Hard Address is 0x0, but acquired AL_PA is 0xef.
System won't be able to see LUNs behind this device port.
It appears that there are (or were) more than one device with the
same address setting.
NOTE: Even after you change the address settings on the devices,
it may be necessary to reset or power-cycle both the
devices whose settings have been changed, and any remaining
device with the address setting which encountered the
conflict.
EXAMPLE: You see this diagnostic message and find three devices with
address setting 0x05. You change one device to address 0x06
and another to 0x07. You now may need to reset or
power-cycle ALL THREE devices.

Hard Address is 0x0, but acquired AL_PA is 0xef
What is mean???

Power-cycle is Server and VTL.
But messages is contunue...

=======fcmsutl command====

fcmsutil /dev/fcd4

Vendor ID is = 0x001077
Device ID is = 0x002312
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x0012ba
PCI Mode = PCI-X 133 MHz
ISP Code version = 3.3.175
ISP Chip version = 3
Topology = PRIVATE_LOOP
Link Speed = 2Gb
Local N_Port_id is = 0x000001
Previous N_Port_id is = 0x000001
Local Loop_id is = 125
N_Port Node World Wide Name = 0x50060b0000273a4d
N_Port Port World Wide Name = 0x50060b0000273a4c
Switch Port World Wide Name = N/A
Switch Node World Wide Name = N/A
Driver state = ONLINE
Hardware Path is = 1/0/10/1/0
Maximum Frame Size = 2048
Driver-Firmware Dump Available = NO
Driver-Firmware Dump Timestamp = N/A
Driver Version = @(#) libfcd.a HP Fibre Channel ISP 23xx & 24xx Driver B.11.11.16 /ux/kern/kisu/FCD/src/common/wsio/fcd_init.c:Jun 11 2008,13:35:21

don't show "Switch Port World Wide Name"

FC cable connect direct
- Topology = PRIVATE_LOOP
- Link Speed = 2Gb
- Driver state = ONLINE

PRIVATE_LOOP is direct mean?

- fcmsutil /dev/fcd4 get remote all
(remote info don't show..)

Re: System won't be able to see LUNs behind this device port

arun khatwani — Thu, 12 Mar 2009 10:33:29 GMT

Hello ,

The WWN number might have changed
N_Port Node World Wide Name = 0x50060b0000273a4d -- (this no have changed compare with old no.)
N_Port Port World Wide Name = 0x50060b0000273a4c (this no have changed compare with old no.)

asked the respective team to make new zonning configuration for new FC card

Re: System won't be able to see LUNs behind this device port

Torsten. — Thu, 12 Mar 2009 10:49:52 GMT

If this would be a MSL6000 I would suggest to check the NSR (network storage router) settings. This part is translating FC to SCSI.

I think the neo lib must have something similar or even the same, so check the settings of this.

Re: System won't be able to see LUNs behind this device port

Torsten. — Thu, 12 Mar 2009 11:16:40 GMT

I think this should apply:

http://support.overlandstorage.com/jive/servlet/KbServlet/download/2521-102-831/104254-102_A.pdf

You must adjust at least topology and speed.

topic Re: System won't be able to see LUNs behind this device port in Operating System - HP-UX

System won't be able to see LUNs behind this device port

Re: System won't be able to see LUNs behind this device port

Re: System won't be able to see LUNs behind this device port

Re: System won't be able to see LUNs behind this device port