HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Duplicate targets in HP 11.0
Operating System - HP-UX
1834657
Members
2121
Online
110069
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
02-08-2005 08:06 PM
02-08-2005 08:06 PM
Duplicate targets in HP 11.0
Hi
We have HP 11.0.
When we connect it to our target device which has one disk LUN configured for the HP,
Sometimes the HP "sees" this specific LUN 16 times as it has 16 different targets instead of one.
Here is an output of the HP :
disk 56 0/6/0/0.98.7.19.0.0.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t0d1 /dev/rdsk/c22t0d1
disk 60 0/6/0/0.98.7.19.0.1.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t1d1 /dev/rdsk/c22t1d1
disk 61 0/6/0/0.98.7.19.0.2.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t2d1 /dev/rdsk/c22t2d1
disk 62 0/6/0/0.98.7.19.0.3.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t3d1 /dev/rdsk/c22t3d1
disk 63 0/6/0/0.98.7.19.0.4.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t4d1 /dev/rdsk/c22t4d1
disk 64 0/6/0/0.98.7.19.0.5.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t5d1 /dev/rdsk/c22t5d1
disk 65 0/6/0/0.98.7.19.0.6.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t6d1 /dev/rdsk/c22t6d1
disk 66 0/6/0/0.98.7.19.0.7.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t7d1 /dev/rdsk/c22t7d1
disk 67 0/6/0/0.98.7.19.0.8.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t8d1 /dev/rdsk/c22t8d1
disk 68 0/6/0/0.98.7.19.0.9.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t9d1 /dev/rdsk/c22t9d1
disk 69 0/6/0/0.98.7.19.0.10.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t10d1 /dev/rdsk/c22t10d1
disk 70 0/6/0/0.98.7.19.0.11.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t11d1 /dev/rdsk/c22t11d1
disk 71 0/6/0/0.98.7.19.0.12.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t12d1 /dev/rdsk/c22t12d1
disk 72 0/6/0/0.98.7.19.0.13.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t13d1 /dev/rdsk/c22t13d1
disk 73 0/6/0/0.98.7.19.0.14.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t14d1 /dev/rdsk/c22t14d1
disk 74 0/6/0/0.98.7.19.0.15.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t15d1 /dev/rdsk/c22t15d1
disk 58 0/6/0/0.98.7.255.1.3.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c23t3d1 /dev/rdsk/c23t3d1
Have you encountered such a problem before?
Do you know what is the solution for it?
Is the problem in the HP side or in the Target device?
Thanks,
Michael
We have HP 11.0.
When we connect it to our target device which has one disk LUN configured for the HP,
Sometimes the HP "sees" this specific LUN 16 times as it has 16 different targets instead of one.
Here is an output of the HP :
disk 56 0/6/0/0.98.7.19.0.0.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t0d1 /dev/rdsk/c22t0d1
disk 60 0/6/0/0.98.7.19.0.1.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t1d1 /dev/rdsk/c22t1d1
disk 61 0/6/0/0.98.7.19.0.2.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t2d1 /dev/rdsk/c22t2d1
disk 62 0/6/0/0.98.7.19.0.3.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t3d1 /dev/rdsk/c22t3d1
disk 63 0/6/0/0.98.7.19.0.4.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t4d1 /dev/rdsk/c22t4d1
disk 64 0/6/0/0.98.7.19.0.5.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t5d1 /dev/rdsk/c22t5d1
disk 65 0/6/0/0.98.7.19.0.6.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t6d1 /dev/rdsk/c22t6d1
disk 66 0/6/0/0.98.7.19.0.7.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t7d1 /dev/rdsk/c22t7d1
disk 67 0/6/0/0.98.7.19.0.8.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t8d1 /dev/rdsk/c22t8d1
disk 68 0/6/0/0.98.7.19.0.9.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t9d1 /dev/rdsk/c22t9d1
disk 69 0/6/0/0.98.7.19.0.10.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t10d1 /dev/rdsk/c22t10d1
disk 70 0/6/0/0.98.7.19.0.11.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t11d1 /dev/rdsk/c22t11d1
disk 71 0/6/0/0.98.7.19.0.12.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t12d1 /dev/rdsk/c22t12d1
disk 72 0/6/0/0.98.7.19.0.13.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t13d1 /dev/rdsk/c22t13d1
disk 73 0/6/0/0.98.7.19.0.14.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t14d1 /dev/rdsk/c22t14d1
disk 74 0/6/0/0.98.7.19.0.15.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c22t15d1 /dev/rdsk/c22t15d1
disk 58 0/6/0/0.98.7.255.1.3.1 sdisk CLAIMED DEVICE StoreAgeHP_Lab01_B
/dev/dsk/c23t3d1 /dev/rdsk/c23t3d1
Have you encountered such a problem before?
Do you know what is the solution for it?
Is the problem in the HP side or in the Target device?
Thanks,
Michael
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2005 08:22 PM
02-08-2005 08:22 PM
Re: Duplicate targets in HP 11.0
Hi Micheal,
It looks like problem in ZONING. May be the zoning info on the switch is getting modified. You need to check whether it is done properly.
What HP see's is correct. This are all different LUN devices connected to controller instance no. 22.
So i don't think this is problem on HP - BOX.
Check ZONING/LUNMASKING configuration on your switch.
Regards,
It looks like problem in ZONING. May be the zoning info on the switch is getting modified. You need to check whether it is done properly.
What HP see's is correct. This are all different LUN devices connected to controller instance no. 22.
So i don't think this is problem on HP - BOX.
Check ZONING/LUNMASKING configuration on your switch.
Regards,
You need to know a lot to actually know how little you know
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2005 08:47 PM
02-08-2005 08:47 PM
Re: Duplicate targets in HP 11.0
Hi
We do not have any zoning or LUN masking modifications.
We have the HP server and our target device, each connected with one port.
Michael
We do not have any zoning or LUN masking modifications.
We have the HP server and our target device, each connected with one port.
Michael
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP