- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- private loop device didn't acquire its hard addres...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2008 04:31 AM
09-05-2008 04:31 AM
private loop device didn't acquire its hard address:
I have some problems with our FC-connection from our RP3440 running hp-ux 11.v1 using FC card - AB379B.
My link was moved to Storage but experience shows there is more help under General/Sys.adm.
http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1265784
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2008 04:39 AM
09-05-2008 04:39 AM
Re: private loop device didn't acquire its hard address:
Is it point-to-point, loop or whatever?
Next is the 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!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2008 04:44 AM
09-05-2008 04:44 AM
Re: private loop device didn't acquire its hard address:
Before reading your reply I sat the state to
Topology Loop mode, no fabric.
The speed should be ok with 4GB as the AB379B card supports 4Gb but I will try to change this to 2GB.
I can now detect the volumes but not the size. I hope to get this too solved before the weekend.
regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2008 04:49 AM
09-05-2008 04:49 AM
Re: private loop device didn't acquire its hard address:
Because of the "special" of hp-ux it cannot work with each and every fc array.
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
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2008 11:27 PM
09-07-2008 11:27 PM
Re: private loop device didn't acquire its hard address:
On the office-server we have the HP AB379-60101 4Gb Dual Port card.
Both Satabeasts is set up identical.
more fcmsutil-info:
njord 49: fcmsutil /dev/fcd0 get remote all
Target N_Port_id is = 0x00005a
Target Loop_id is = 77
Target state = DSM_UNOPENED
Symbolic Name =
Port Type = NL_PORT
FCP-2 Support = NO
Target Port World Wide Name = 0x5000402001fc487f
Target Node World Wide Name = 0x2001000402fc487f
Common Service parameters (all values shown in hex):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Common Features : 8800 RO_Bitmap: fe
Total Conseq: ff
Class 3 Service parameters (all values shown in hex):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Open Sequences/Exchg: 1 Conseq: ff
Recipient Control Flags: 0 Rxsz: 800
I can see the 0/2/1/0.8.0.255.4.13.0 Unused size: 0 Nexsan SataBeast in SAM.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2008 06:12 AM
09-09-2008 06:12 AM
Re: private loop device didn't acquire its hard address:
I can see the lights go green and say FC Online when running SAM -> Disk and filesystems. but once the scanning of disks/filesystems, the lights on the RAID GUI goes off again.
Able to scan for disks and it detects Nexsan Satabeast but no size on the disks.
disk 9 0/2/1/0.8.0.255.1.1.0 sdisk CLAIMED DEVICE NEXSAN SATABeast
/dev/dsk/c8t1d0 /dev/rdsk/c8t1d0
disk 10 0/2/1/1.8.0.255.4.13.0 sdisk CLAIMED DEVICE NEXSAN SATABeast
/dev/dsk/c9t13d0 /dev/rdsk/c9t13d0
njord 67: diskinfo /dev/rdsk/c9t13d0
SCSI describe of /dev/rdsk/c9t13d0:
vendor: NEXSAN
product id: SATABeast
type: direct access
size: 0 Kbytes
bytes per sector: 0
Any tips?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2008 10:09 PM
09-14-2008 10:09 PM
Re: private loop device didn't acquire its hard address:
Once I created the LUN/Volumes to 2TB or less the hp-ux box could see them.
thanx for your attantion!
Thomas greig