- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- Re: peer persistence convert to 3DC PP
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
12-19-2018 07:05 AM
12-19-2018 07:05 AM
peer persistence convert to 3DC PP
Hi,
I met a problem in the PP converting to 3DC-PP. Three 3par systems are OS 3.3.1. A and B are currently running as peer persistence. When Adding the third storage C (cabling and zoning), the rcopy link A->C, B->C are alway down.
A:
3par_A cli% showrctransport -rcfc
N:S:P Peer_Node_WWN Peer_Port_WWN State
2:0:2 2FF70002AC021FA9 21020002AC021FA9 new
3:0:2 2FF70002AC021FA9 20010002AC021FA9 new
1:0:2 2FF70002AC01D245 21020002AC01D245 ready #This is current pp rcopy link
0:0:2 2FF70002AC01D245 20020002AC01D245 ready #This is current pp rcopy link
B:
3par_B cli% showrctransport -rcfc
N:S:P Peer_Node_WWN Peer_Port_WWN State
3:0:2 2FF70002AC021FA9 23010002AC021FA9 new
2:0:2 2FF70002AC021FA9 22020002AC021FA9 new
1:0:2 2FF70002AC01D226 21020002AC01D226 ready #This is current pp rcopy link
0:0:2 2FF70002AC01D226 20020002AC01D226 ready #This is current pp rcopy link
C:
3par_C cli% showrctransport
N:S:P Peer_Address Address State Type
3:0:1 23020002AC01D245 23010002AC021FA9 new rcfc
2:0:2 22020002AC01D245 22020002AC021FA9 new rcfc
1:0:2 22020002AC01D226 21020002AC021FA9 new rcfc
0:0:1 23020002AC01D226 20010002AC021FA9 new rcfc
From "showrctransport -rcfc", the new added rcfc links are new, not the ready status. So I do the "creatercopytarget" to establish the rc link. Do the "creatercopytarget" in A/B/C.
A: creatercopytarget 3par_C FC 2FF70002AC021FA9 2:0:2: 21020002AC021FA9 3:0:2: 20010002AC021FA9
C: creatercopytarget 3Par_A FC 2FF70002AC01D226 0:0:1:23020002AC01D226 1:0:2: 22020002AC01D226
the B &C ......
But when showrcopy links, the new rcopy links are all down. What should I do next? Thanks for the advice!
3par_A cli% showrcopy links
Remote Copy System Information
Status: Started, Normal
Link Information
Target Node Address Status Options
HIS_3PAR_B 0:0:2 20020002AC01D245 Up -
HIS_3PAR_B 1:0:2 21020002AC01D245 Up -
HIS_Backup 2:0:2 21020002AC021FA9 Down -
HIS_Backup 3:0:2 20010002AC021FA9 Down -
receive 0:0:2 20020002AC01D245 Up -
receive 1:0:2 21020002AC01D245 Up -
receive 2:0:2 21020002AC021FA9 Up -
receive 3:0:2 20010002AC021FA9 Up -
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2019 09:48 AM
01-03-2019 09:48 AM
Re: peer persistence convert to 3DC PP
Hello @dennischen,
As per your query I found below link which can be helpful for you to resolve this issue:
Documentation: Click here to access the User Guide for HPE 3PAR Remote Copy Software.
If this helps you with your issue, please click the thumb to register a Kudo.
If it resolves the issue, please consider marking it as an Accepted Solution.
Thanks and Regards,
I am an HPE Employee