The installation of a VNX2
The first day is the toughest and easiest. Like baking a cake you need to make sure all the ingredients are there and ready to go. You verify what was ordered is installed and is in working order. Sounds simple enough?
As it turns out the initial VNX “Rack and Stack” was correct.
- All cables were plugged in correctly
- No amber lights on the system.
- The DAE (Disk Assembly Enclosures) were recognized.
- No faults in Unisphere
Ok. Good to go? No? Why. Mr. Customer provided a duplicate IP for one of the control stations. The correct IP is the same subnet and mask but needs to be changed.
Here are the steps
- Log onto Unisphere confirm IP information for Control Station
- Log onto Control station via ssh
Use root/nasadmin (default)
3. Verify status of Control station. You can make changes to the primary not standby.
In this case the primary Control station was IP’d correctly. I need to change the secondary Control station, the standby.
/nasmcd/getreason <<– run this command as root
Here is what you will see:
output:10 – slot_0 primary control station11 – slot_1 secondary control station5 – slot_2 contacted5 – slot_3 contacted
output:11 – slot_0 secondary control station10 – slot_1 primary control station5 – slot_2 contacted5 – slot_3 contacted
6. Log into Unisphere
Normally you login to the VNX with using the primary Control Station IP. However since it is in failover mode use the secondary IP. In this case I am using the duplicate IP and will change it to the correct IP by using the Unisphere GUI
Log into the Unisphere GUI as root. Make sure you choose scope “local” not Global
Navigate to the “Control station Properties Tab”
Change the IP of the Control Station
In Confirm Action, click OK.
Modifying the Control Station hostname, IP address, subnet mask, or gateway may disrupt the Unisphere software connection and any other client access to the Control Station. It may be necessary to reconnect to continue administrative activities. If you make a mistake changing the network, the Control Station may no longer be reachable remotely.
7. ssh to the primary Control station and failback. Verify that the primary control station is in slot 0
# /nasmcd/getreason10 – slot_0 primary control station11 – slot_1 secondary control station5 – slot_2 contacted5 – slot_3 contacted
That is it.
Remember when you login to Unisphere you connect via the Primary Control Station IP, if you are failed over you will connect to the secondary Control Station.
Thanks for reading! If you have a more efficient way please share. Yes, you can ssh in and do all of this via cli. 😉