- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- SLD with VMware hosts (no peer persistence support...
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
04-19-2015 07:50 AM
04-19-2015 07:50 AM
SLD with VMware hosts (no peer persistence supported)
Having trouble with SLD on 3.2.1 and VMware.
It seems the # setrcopygroup pol path_management <group> allows ALUA to detect active paths for SYNC volumes, but not SLD volumes.
For some reason, this policy is not supported on SLD volumes, but it doesn’t say why. If it was supported I would be able to manually failover between my two head office 7400's. Without it, my ESXi hosts cannot detect active paths.
Page 151-152
http://h20565.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c03618143
Only options I can think of are:
A: Change the ESXi policy to Active Active (VMW_SATP_DEFAULT_AA ), and the hosts to Persona 6 (No ALUA), and then disable the paths to the standby system from the host via ‘esxcli storage copre path set –state off… commands
B: Unexport the volumes from the standby system, and represent them when failing over. Problem with this is that the commands (createvlun/removevlun) don’t appear to support pattern matching so big change control issue as new volumes are created.
Is anyone else using SLD with VMware, and if so, how are you handling the paths to each SYNC site?
(The ASYNC site has different hosts so not an issue, plus SRM handles the presentation of the VV's there.)
If my post was useful, clik on my KUDOS! "White Star"