- 3PAR SSMC CHANGE IP HOW TO
- 3PAR SSMC CHANGE IP INSTALL
- 3PAR SSMC CHANGE IP FULL
- 3PAR SSMC CHANGE IP LICENSE
- 3PAR SSMC CHANGE IP OFFLINE
Note that monitoring apparently cannot be enabled when WWNs per Port exceeds the maximum of 32. Note this configuration option do not have to be in place on all modes or firmwares, you might ignore it if you do not find it on your storage.
3PAR SSMC CHANGE IP LICENSE
The HDS Performance Monitor License must exist for each array and monitoring must be enabled. runUnix.bat show interval -ip -login ĭirectory /opt/hds is optional, it is configurable in /home/stor2rrd/stor2rrd/etc/stor2rrd.cfg : VSP_CLIDIR=/opt/hds
3PAR SSMC CHANGE IP INSTALL
Install each version of the Export Tool into separate directory named as firmware of your storage (just 6 numbers like in this example firmware 83-01-28) under root user: Unless you make sure all of the storage are running on the same firmware version then you will need to obtain the appropriate version of the Export Tool to meet the firmware version you are running at the site.įind our firmware release of your storage (like 83-01-28/00).Įxport Tool version must match the SVP firmware version. There is a new Export Tool build for each release of the firmware. The Export Tool can also be obtained by contacting HPE support. It is typically located on a CD that comes packaged with the Service Processor on the HPE XP7/XP8 Array. You can also follow this docu to fully prepare storage for monitoring $ perl /home/stor2rrd/stor2rrd/bin/ 192.168.1.1 443Ĭonnection to "192.168.1.3" on port "443" is okĬreate user stor2rrd on the storage, read only accessĭo not use shell special characters like #!?|$*\`"'& in the password, use instead. I did not validate this with real data and it really could worth to test it.Īn other way to do your PRA could be to let the remote copy started and create snapshot of vvset on secondary site to export them to your PRA hosts.$ perl /home/stor2rrd/stor2rrd/bin/ 192.168.1.1 1099Ĭonnection to "192.168.1.3" on port "1099" is ok
3PAR SSMC CHANGE IP FULL
I think that if you don't try to force a full synchronisation you will face some hard stuff when the real PRA happen because both volume won't be really synchronous : during your PRA blocks have changed on the secondary array but the primary array does not anything of it. So, before restarting on primary site i will run a dismissrcopyvv on any volume involved in PRA and then admit then again and start the remote copy group again. with my 10G empty VV.Īnd that is very embarrassing because blocks have changed on the secondary array. Then the remote copy group is started and. > Secondary RCGroup status goes from primary to secondary > Secondary RCGroup status goes from primary-rev to primaryĪrray B : setrcopygroup reverse -local -f Here is what i ve tested on 322 MU4, a few minutes ago.Īrray B : setrcopygroup reverse -natural -local -f I was quite suprised reading that a simple reverse on the failovered array was enough to run a startrcopygroup on the primary array.
3PAR SSMC CHANGE IP HOW TO
I know how to do the promote operation with the CLI, but the problem is that I don't find the exact command for the reverse operation.Īs far as I remember, when I was working with IMC instead of SSMC, it was possible to find exact commands in the task logs ? Or am I dreaming ? 15:34:37 CEST Completed promote of snapshot rcpy.6.61.1 to VV ESC_TEST_FA.r. 15:34:37 CEST Starting promote of snapshot rcpy.6.61.1 to VV ESC_TEST_FA.r. followed by a promote of the snapshot of the VV on the target side : 15:34:37 CEST Completed Group RC_ESC_TEST_FA.r118630 reverse completed.
15:34:37 CEST Switched Group RC_ESC_TEST_FA.r118630 was switched from primary to secondary. 15:34:37 CEST Stopped Stopped remote copy of group RC_ESC_TEST_FA.r118630.
15:34:37 CEST Begin Reverse operation on group RC_ESC_TEST_FA.r118630 started. I have tried to track the tasks realized on the 3Par when I do a "Reverse failover" from the SSMC.
I am just looking for the right way to do a "Reverse failover" with CLI instead of SSMC. All of them are compatible with Peer Persistence.īut the problem is not there. Last edited by Eric SAUBIGNAC on Fri 3:25 am, edited 1 time in total. I didn't found any dr_operation like "Revert" with setrcopygroup command. Well, the point I am stuck on is how to do a "Revert failover" with the CLI. Restart applications on primary site with original data Start applications on secondary site and do the tests RCG goes automatically in "stopped" status
3PAR SSMC CHANGE IP OFFLINE
Put all RC ports between primary and secondary site offline With SSMC, operations are done this way : The idea in this scenario is just to test that we can transfert activity of the main site to a secondary site, then come back to the primary site and forget all modifications and tests done on the secondary site. We have a scenario that works pretty well with SSMC. I am currently working on some DR scenarios with 3Par CLI vs 3Par SSMC