- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- hsx device question
Disk Enclosures
1752407
Members
5471
Online
108788
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
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
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-30-2005 06:19 AM
06-30-2005 06:19 AM
All,
I am running Secure Path version 3.0C_SP1 on a Solaris 8 machine. When I do a 'spmgr display' it lists a hsx device name for each path, for instance hsx-2818-33-4. I have several questions.
1. Does the hsx instance have a 1 to 1 relationship to a device file?
2. Solaris 'sar' reports devices such as hsx840; do these devices map to a specific instance?
3. Does an IO request go to a sd device and then Secure Path take that disk IO request and pass it thru the active hsx path? If not, what is the path of an IO request?
Thanks for your help!
I am running Secure Path version 3.0C_SP1 on a Solaris 8 machine. When I do a 'spmgr display' it lists a hsx device name for each path, for instance hsx-2818-33-4. I have several questions.
1. Does the hsx instance have a 1 to 1 relationship to a device file?
2. Solaris 'sar' reports devices such as hsx840; do these devices map to a specific instance?
3. Does an IO request go to a sd device and then Secure Path take that disk IO request and pass it thru the active hsx path? If not, what is the path of an IO request?
Thanks for your help!
Hey, I've got three teenage boys!
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2005 06:39 AM
06-30-2005 06:39 AM
Solution
I don't have any experience with Solaris, but after a short look into the manual and a bit of experience on other OSes (HP-UX, Linux, Windows)...
1. the output of 'spmgr' looks pretty similar to that of other operating system implementation, so I'd say: yes.
3. there is a picture in the installation manual that shows the layering. Indeed, the I/O request goes from the Solaris disk driver to the 'swsp' driver which handles all paths and is then directed to the 'hsx' driver. The 'hsx' driver contains array-specific know-how, e.g. how to fail over a device. Then the I/O goes to the driver of the fibre channel adapter.
1. the output of 'spmgr' looks pretty similar to that of other operating system implementation, so I'd say: yes.
3. there is a picture in the installation manual that shows the layering. Indeed, the I/O request goes from the Solaris disk driver to the 'swsp' driver which handles all paths and is then directed to the 'hsx' driver. The 'hsx' driver contains array-specific know-how, e.g. how to fail over a device. Then the I/O goes to the driver of the fibre channel adapter.
.
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