- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - HP-UX
- >
- System Administration
- >
- System won't be able to see LUNs behind this devic...
-
- Forums
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- Infrastructure Solutions German
- L’Avenir de l’IT
- IT e Trasformazione Digitale
- Enterprise Topics
- ИТ для нового стиля бизнеса
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Forums
-
Blogs
-
InformationEnglish
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-11-2009 09:49 PM
03-11-2009 09:49 PM
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..)
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-12-2009 03:33 AM
03-12-2009 03:33 AM
SolutionThe 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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-12-2009 03:49 AM
03-12-2009 03:49 AM
Re: System won't be able to see LUNs behind this device port
I think the neo lib must have something similar or even the same, so check the settings of this.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-12-2009 04:16 AM
03-12-2009 04:16 AM
Re: System won't be able to see LUNs behind this device port
http://support.overlandstorage.com/jive/servlet/KbServlet/download/2521-102-831/104254-102_A.pdf
You must adjust at least topology and speed.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP