Unsolved
This post is more than 5 years old
16 Posts
0
637
March 25th, 2013 01:00
VMAX Masking Issue
Hi,
I have this weird scenario on my VMAX which I need to resolve. Appreciate any help/ideas from anyone.
I have a port group with two ports in it, that is shared between 9 production servers. The port group is named after the ports - PG_7e0_10e0 . During a new allocation somebody uses the same port group for a server and adds two new ports to the port group (not sure why he/she did it!). So the port group PG_7e0_10e0 now has ports 7e0,10e0,6g1,11g1. How do we clean this up without disrupting any of the servers?
We need to provision the 10th server with ports 6g1 and 11g1 on a different port group, but without bringing down the application or server. We thought of an idea to create a new Masking view, using a new port group PG_6g1_11g1 , and the existing initiator and storage groups. Then delete the old masking view and remove the ports from PG_7e0_10e0. But I am not sure if the host would have any impact if two masking views exist for the same host and same devices??!!
Any ideas?
Thanks
Mumshad
jet_pilot
2 Posts
0
March 25th, 2013 08:00
Do the original 9 production servers have PowerPath installed? If so you should be able to set the additional paths to standby in each of the production servers then remove the extra ports from the port group (PG). Afterwards clean up the ensuing path dead alerts on the 9 servers but there shouldn't be any outage. Unfortunately this approach will cause the new 10th server to take an outage.
In our shop we create a dedicated PG for each server. This isolates servers from erroneous PG changes but does lead to having just as my port groups as there are masking views.