- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Re: Secure Path 3.0D issues on Solaris 8
MSA Storage
1755758
Members
3253
Online
108838
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
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
11-06-2004 12:24 AM
11-06-2004 12:24 AM
Secure Path 3.0D issues on Solaris 8
Hi All,
Brief description of the setup:
A Sun Solaris 8 host connected to EVA 5000 with dual FCA2257P HBAs running Secure Path V3.0D
Secure Path V3.0D was successfully installed on the host.After the install, only three paths to the LUNs on the EVA were seen as one of the fibre channel cables (connecting FP2 of the bottom controller to a port on one of the fabric switches) was not installed.
I installed the missing fibre channel cable hoping that Secure Path would automatically detect the new path throughs its path verification mechanism and "spmgr display" should see 4 paths for each LUN. This did not happen even after a reboot. I ran drvconfig - no success, devfsadm - no success, config.sh to manually remove and add adapters - no success. On a subsequent reboot, the host did not see any LUNs at all and halted in single user mode trying to mount the filesystem on non-existing LUNs.
LUNs are still being presented to the host from the EVA end and zoning configuration is as expected.
Any clue anyone?
Regards,
Brief description of the setup:
A Sun Solaris 8 host connected to EVA 5000 with dual FCA2257P HBAs running Secure Path V3.0D
Secure Path V3.0D was successfully installed on the host.After the install, only three paths to the LUNs on the EVA were seen as one of the fibre channel cables (connecting FP2 of the bottom controller to a port on one of the fabric switches) was not installed.
I installed the missing fibre channel cable hoping that Secure Path would automatically detect the new path throughs its path verification mechanism and "spmgr display" should see 4 paths for each LUN. This did not happen even after a reboot. I ran drvconfig - no success, devfsadm - no success, config.sh to manually remove and add adapters - no success. On a subsequent reboot, the host did not see any LUNs at all and halted in single user mode trying to mount the filesystem on non-existing LUNs.
LUNs are still being presented to the host from the EVA end and zoning configuration is as expected.
Any clue anyone?
Regards,
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-30-2005 12:23 AM
03-30-2005 12:23 AM
Re: Secure Path 3.0D issues on Solaris 8
Hi,
I'm not sure whether your problem with the missing path is solved, but check /kernel/drv/swsp.conf
Iguess you should have four wwlid entries.
I had a similar problem installing SecurePath on Solaris8 when zoning was not done yet, and ended up where you did: paths were not seen.
After diging some time I found that those wwlid entries were missing (therefore the swsp module was not loaded into the kernel), /dev/swsp was not created, etc.
After including the entries and data regarding EVA and rebooting, everything worked as expected.
best regards, Attila
I'm not sure whether your problem with the missing path is solved, but check /kernel/drv/swsp.conf
Iguess you should have four wwlid entries.
I had a similar problem installing SecurePath on Solaris8 when zoning was not done yet, and ended up where you did: paths were not seen.
After diging some time I found that those wwlid entries were missing (therefore the swsp module was not loaded into the kernel), /dev/swsp was not created, etc.
After including the entries and data regarding EVA and rebooting, everything worked as expected.
best regards, Attila
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