- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Proper way to configure SecurePath (clients)
ProLiant Servers (ML,DL,SL)
1820895
Members
3772
Online
109628
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
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
02-06-2008 09:40 PM
02-06-2008 09:40 PM
Proper way to configure SecurePath (clients)
Hi.
We have Proliant DL380 or DL385 servers with two HBAs connected to MSA1000.
I usually just install SecurePath 4.0c Workgroup Edition and that's it. I do not add any clients. The server name where SecurePath is installed is automatically entered as a client upon installation.
Someone is telling me that in case of a Windows cluster, I should add both cluster node names as clients in the SecurePath configuration. I think they are wrong. They tell me that doing it my way the fail-over will not work properly. I think they are confusing HBA failover with cluster failover.
But I never had a formal education with SecurePath.
So am I doing it right? Or should I add both cluster node names?
We have Proliant DL380 or DL385 servers with two HBAs connected to MSA1000.
I usually just install SecurePath 4.0c Workgroup Edition and that's it. I do not add any clients. The server name where SecurePath is installed is automatically entered as a client upon installation.
Someone is telling me that in case of a Windows cluster, I should add both cluster node names as clients in the SecurePath configuration. I think they are wrong. They tell me that doing it my way the fail-over will not work properly. I think they are confusing HBA failover with cluster failover.
But I never had a formal education with SecurePath.
So am I doing it right? Or should I add both cluster node names?
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
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP