changing ip of cs and sp failing

this is the output from the nas_cs -info

[root@ATL nasadmin]# nas_cs -info

Host Name               = ATL

Version                 = 7.0.51-3

Location                = system:VNX5300:APM001205013462007|controlStation::0

Status                  = OK

Standby Location        =

Standby Status          =

IPv4 Address            = 192.168.12.160

IPv4 Netmask            = 255.255.255.0

IPv4 Gateway            = 192.168.12.1

IPv6 Address            =

IPv6 Gateway            =

DNS Domain              = us.bis.local

DNS Domain search order = us.bis.local

DNS Servers             = 10.10.103.40

Session Monitor Timeout = 0 Days

Session Idle Timeout    = 0 Minutes

NTP Servers             = 192.168.11.31

System Time             = Thu Jun 07 09:15:20 EDT 2012

tried support chat yesterday, they looked at it for hours.  they dispatched it to field engineer.  last time we had to do this we had to wait a few weeks for someone to come out.  that is why i reached out to the community.

Get them on webex , I had similar issues when VNX first came out and we had to change SPs IP addresses.

this odd ..can you try support chat, we are missing something (hopefully simple)

they were on a webex, you think i should try opening another case and get a new engineer?

i started looking at article   emc275841  but still having problems, hopefully not causing any additional issues.

Was a /nas/sbin/clariion_mgmt -stop run before you shut down and then tried to change the IPs?

definitely

yes it was and it completed successfully

i did want to let you both know i can log into unisphere under the management ip but get a bunch of errors saying it cannot contact the sp's and the data is corrupt.

What a PITA , thank you for sharing the steps to resolve this.

yes that is correct, richmond still things its 10.10.103.X  the atlanta one that i moved connected to richmond just find b/c the ip didnt change from that direction.

thanks,  one last question.  on my richmond vnx, its still seeing the old atlanta vnx ip's is there a command i can run to get it to update?

ISSUE RESOLVED!!!!!!!!!!!!!!!!!!!

After a long battle with this yesterday I was able to resolve the issue on my own.  (im still waiting on that call from the field engineer) it was a combination of things that allowed me to fix it.

Emc279637 is the article I started with to change my cs and s pip addresses.  Step 6 is where I was having a problem.  The Clariion_mgmt –start command was failing.

From there these are the things I needed to do in order to get the array back in a stable state

• - Default route was missing with new gateway - /sbin/route is the command to help with this
• - Ran the following command on each sp(replacing with correct ip’s) –(emc article emc275841 helped me with this)
  • /nasmcd/sbin/naviseccli -t 60 -user sysadmin -password sysadmin -scope 0 -h 128.221.253.201 networkadmin -set -ipv4 -address 10.6.12.81 -subnetmask 255.255.252.0 -gateway 10.6.12.1
• - After the above command was run I still I was still not able to get the clarion_mgmt – start command to run it still failed with same error
• - after a lot of troubleshooting, it became clear that my /sbin/route table and my /etc/host file were not correct.
• - I tried modifying them to the correct settings but something kept resetting them back to the old ip’s, after a reboot I quickely changed them to the correct setttings
  • /etc/hosts – spa and spb entries had incorrect ip address
  • /sbin/route table was missing the host entries for spa and spb.  (A_serialnumber  * 255.255.255.255) is what it should look like in the table,  just replace the A with B for other entry)
• - At this point I was able to run the following command to update the sym database directly(the following community discussion helped with the next few commands https://community.emc.com/message/433372)
  • /nas/bin/nas_storage -modify id=1 -network -spa 192.168.12.161 -spb 192.168.12.162
• - Next I ran
  • nas_storage -m id=1 –security
• - next I ran
  • nas_storage –c –a
• - ALL OF THE ABOVE COMMANDS WHICH WERE FAILING NOW RAN SUCCESSFULLY
• - Ran the following on both sp’s to verify its working
  • /nasmcd/sbin/naviseccli -t 60 -user sysadmin -password sysadmin -scope 0 -h 192.168.12.161 getagent
• - Then ran the following 2 commands to reboot both sp’s
  • /nasmcd/sbin/naviseccli -t 60 -user sysadmin -password sysadmin -scope 0 -h 192.168.12.161 setcache -wc 0
  • /nasmcd/sbin/naviseccli -t 60 -user sysadmin -password sysadmin -scope 0 -h 192.168.12.161 rebootsp –both
• - Once the sp’s rebooted I was able to log into unisphere and all of the errors I was seeing before with no communication with the sp’s had been resolved.  Everything is now functioning properly.

Thanks dynamox for your help with this, you helped to point me in the right direction.