GreenLake Administration
- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- EVA 4400 autopath
Disk Enclosures
1850507
Members
2560
Online
104054
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
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
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
06-02-2008 01:10 AM
06-02-2008 01:10 AM
Hello,
At our customer, they have an EVA 4400 with HP-UX 11.11 and Secure path A.3.0F.02F.02F
After an ioscan, I see the LUNs like:
disk 17 0/4/1/0.1.6.0.0.0.1 sdisk CLAIMED DEVICE HP HSV300
/dev/dsk/c9t0d1 /dev/rdsk/c9t0d1
disk 18 0/4/1/0.1.7.0.0.0.1 sdisk CLAIMED DEVICE HP HSV300
/dev/dsk/c11t0d1 /dev/rdsk/c11t0d1
But for some reason, autopath doesn't see the new LUNs. I already tried "autopath discover", but no luck.
What am I missing?
I know I can use pvlinks, but I wonder why autopath doesn't see the EVA 4400 LUNs. There is also connected an HSV101, for which autopath sees the LUNs.
At our customer, they have an EVA 4400 with HP-UX 11.11 and Secure path A.3.0F.02F.02F
After an ioscan, I see the LUNs like:
disk 17 0/4/1/0.1.6.0.0.0.1 sdisk CLAIMED DEVICE HP HSV300
/dev/dsk/c9t0d1 /dev/rdsk/c9t0d1
disk 18 0/4/1/0.1.7.0.0.0.1 sdisk CLAIMED DEVICE HP HSV300
/dev/dsk/c11t0d1 /dev/rdsk/c11t0d1
But for some reason, autopath doesn't see the new LUNs. I already tried "autopath discover", but no luck.
What am I missing?
I know I can use pvlinks, but I wonder why autopath doesn't see the EVA 4400 LUNs. There is also connected an HSV101, for which autopath sees the LUNs.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2008 02:36 AM
06-02-2008 02:36 AM
Solution
I think you need Secure Path 3.0F Service Pack 3 to recognize the EVA4400:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?&swItem=co-58128-1
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?&swItem=co-58128-1
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2008 06:03 AM
06-02-2008 06:03 AM
Re: EVA 4400 autopath
Thanks, this was the solution.
I had verified the SPOCK information, and it stated that HP:SecurePath for HP-UX (3.0F SP1, SP2) was sufficient.
After installing SP3, the deviced showed up in autopath!
I had verified the SPOCK information, and it stated that HP:SecurePath for HP-UX (3.0F SP1, SP2) was sufficient.
After installing SP3, the deviced showed up in autopath!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2008 06:04 AM
06-02-2008 06:04 AM
Re: EVA 4400 autopath
Install SP 3.0F service pack 3
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 2026 Hewlett Packard Enterprise Development LP