- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: who owns w/c LUN
Disk Enclosures
1748129
Members
3680
Online
108758
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
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО01-27-2005 07:18 AM
тАО01-27-2005 07:18 AM
I ran armdsp -a and got a list ans status of the LUNS. I am working on a VA 7410.
How would I know which LUNs went to (1) Which server? (2) Which file system ? I'm trying to document our setup.
Thanks,
f. halili
How would I know which LUNs went to (1) Which server? (2) Which file system ? I'm trying to document our setup.
Thanks,
f. halili
derekh
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-27-2005 06:27 PM
тАО01-27-2005 06:27 PM
Solution
Hi ,
in order to know the relation between which hosts can access which LUNs you would need to read the LUN security table from the array and somehow manually figure out which WWN is from which server/HBA.
- to read the LUN security table run this command on the station that has CommandView installed (CVSDM).
armsecure -r -f 'file1.txt' -p 'password' 'array-id'
This way that 'file1.txt' will contain a list like the one below i.e. :
DEFAULT 0 WC
NODEWWN 10000000c9363f03 7 WC
NODEWWN 10000000c9363f03 8 WC
NODEWWN 10000000c9363f03 9 WC
NODEWWN 10000000c93b6718 30 WC
NODEWWN 10000000c93b6718 31 WC
NODEWWN 10000000c93b6718 32 WC
NODEWWN 10000000c93b6718 33 WC
NODEWWN 10000000c93b6718 34 WC
NODEWWN 10000000c93b69dc 30 WC
NODEWWN 10000000c93b69dc 31 WC
NODEWWN 10000000c93b69dc 32 WC
NODEWWN 10000000c93b69dc 33 WC
NODEWWN 10000000c93b69dc 34 WC
NODEWWN 50060b00000158f9 1 WC
NODEWWN 50060b00000158f9 2 WC
NODEWWN 50060b00000158f9 3 WC
NODEWWN 50060b0000017ee0 4 WC
NODEWWN 50060b0000017ee0 11 WC
NODEWWN 50060b0000017ee0 20 WC
NODEWWN 50060b0000017ee0 21 WC
NODEWWN 50060b0000017ee0 22 WC
NODEWWN 50060b00000208f7 1 WC
NODEWWN 50060b00000208f7 2 WC
NODEWWN 50060b00000208f7 3 WC
NODEWWN 50060b0000020a48 4 WC
NODEWWN 50060b0000020a48 11 WC
NODEWWN 50060b0000020a48 20 WC
NODEWWN 50060b0000020a48 21 WC
NODEWWN 50060b0000020a48 22 WC
NODEWWN 50060b0000100f92 10 WC
NODEWWN 50060b00001047b8 10 WC
DEFAULT 1 0
DEFAULT 2 0
DEFAULT 3 0
.....
Up to you then here to check what HBA in which server has this WWN, this should be part of your SAN documentation really, if not then hopefully you have the switch ports documented and with switchshow (in case of Brocade) you can then link the WWN in the VA security table with the switch ports and work further from their to get the whole puzzle documented.
The filesystem type will have to be determined once you know which LUN is on which host and look at it via the host.
HTH
Kris
in order to know the relation between which hosts can access which LUNs you would need to read the LUN security table from the array and somehow manually figure out which WWN is from which server/HBA.
- to read the LUN security table run this command on the station that has CommandView installed (CVSDM).
armsecure -r -f 'file1.txt' -p 'password' 'array-id'
This way that 'file1.txt' will contain a list like the one below i.e. :
DEFAULT 0 WC
NODEWWN 10000000c9363f03 7 WC
NODEWWN 10000000c9363f03 8 WC
NODEWWN 10000000c9363f03 9 WC
NODEWWN 10000000c93b6718 30 WC
NODEWWN 10000000c93b6718 31 WC
NODEWWN 10000000c93b6718 32 WC
NODEWWN 10000000c93b6718 33 WC
NODEWWN 10000000c93b6718 34 WC
NODEWWN 10000000c93b69dc 30 WC
NODEWWN 10000000c93b69dc 31 WC
NODEWWN 10000000c93b69dc 32 WC
NODEWWN 10000000c93b69dc 33 WC
NODEWWN 10000000c93b69dc 34 WC
NODEWWN 50060b00000158f9 1 WC
NODEWWN 50060b00000158f9 2 WC
NODEWWN 50060b00000158f9 3 WC
NODEWWN 50060b0000017ee0 4 WC
NODEWWN 50060b0000017ee0 11 WC
NODEWWN 50060b0000017ee0 20 WC
NODEWWN 50060b0000017ee0 21 WC
NODEWWN 50060b0000017ee0 22 WC
NODEWWN 50060b00000208f7 1 WC
NODEWWN 50060b00000208f7 2 WC
NODEWWN 50060b00000208f7 3 WC
NODEWWN 50060b0000020a48 4 WC
NODEWWN 50060b0000020a48 11 WC
NODEWWN 50060b0000020a48 20 WC
NODEWWN 50060b0000020a48 21 WC
NODEWWN 50060b0000020a48 22 WC
NODEWWN 50060b0000100f92 10 WC
NODEWWN 50060b00001047b8 10 WC
DEFAULT 1 0
DEFAULT 2 0
DEFAULT 3 0
.....
Up to you then here to check what HBA in which server has this WWN, this should be part of your SAN documentation really, if not then hopefully you have the switch ports documented and with switchshow (in case of Brocade) you can then link the WWN in the VA security table with the switch ports and work further from their to get the whole puzzle documented.
The filesystem type will have to be determined once you know which LUN is on which host and look at it via the host.
HTH
Kris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-27-2005 06:29 PM
тАО01-27-2005 06:29 PM
Re: who owns w/c LUN
VA7410 does not support "present" feature. so all connected host can see all available LUN on VA (If zoning on switches is allow). Have you install SecurePath on host?. pls take following command on each host.
#ioscan -fnC disk
#strings /etc/lvmtab
base on those information We can say to you what host LUN is belong to?
You cat see and gues your self.
tienna.
#ioscan -fnC disk
#strings /etc/lvmtab
base on those information We can say to you what host LUN is belong to?
You cat see and gues your self.
tienna.
HP is simple
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-27-2005 06:39 PM
тАО01-27-2005 06:39 PM
Re: who owns w/c LUN
Tienna,
the VA7xxx arrays do have a build in feature called "LUN security" which is available for free by default but with a limited capacity. If you need to "secure" more LUNs (more capacity then the default) you have to install a license key of i.e. 500 GByte to 1 TByte.
So the VA7xxx is perfectly capable to selectively "present" LUNs if you want to use that terminology, however the term normally used in VA7xxx land is "LUN security".
SecurePath is not relevant here and only needed if their are multiple paths from the same hosts going to the VA7xxx array.
Kris
the VA7xxx arrays do have a build in feature called "LUN security" which is available for free by default but with a limited capacity. If you need to "secure" more LUNs (more capacity then the default) you have to install a license key of i.e. 500 GByte to 1 TByte.
So the VA7xxx is perfectly capable to selectively "present" LUNs if you want to use that terminology, however the term normally used in VA7xxx land is "LUN security".
SecurePath is not relevant here and only needed if their are multiple paths from the same hosts going to the VA7xxx array.
Kris
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP