Start a Conversation

Unsolved

This post is more than 5 years old

1178

February 28th, 2014 06:00

NX4 Change SP and CS IP failure - cannot continue

I have an NX4 that I am trying to change the IP on.  I have read all the discussions/blogs about this procedure but even though I followed them it has failed and I'm in a state where I can't stop the clariion management anymore. I tried the clariion_mgmt -stop command and it appeared to be working and changing the IPs back to the default but at some point it failed and the IPs are still what they were before the command was issued.

Some info:

[root@Chn-nas-1C nas]# nas_cs -i

Host Name               = Chn-nas-1C

Version                 = 6.0.40-8

Location                = system:NX4FC:SL7E91007000950000|controlStation::0

Status                  = OK

Standby Location        =

Standby Status          =

IPv4 Address            = 172.30.11.20

IPv4 Netmask            = 255.255.255.0

IPv4 Gateway            = 172.30.11.129

IPv6 Address            =

IPv6 Gateway            =

DNS Domain              = domain.com.com

DNS Domain search order = domain.com

DNS Servers             = 172.30.11.151,192.168.196.20,192.168.194.20

Session Monitor Timeout = 0 Days

Session Idle Timeout    = 0 Minutes

NTP Servers             = 172.30.11.151.

System Time             = Fri Feb 28 20:08:25 GMT+05:30 2014

   

[root@Chn-nas-1C nas]# /nas/sbin/clariion_mgmt -info

Public IP address for SPA: 172.30.11.240

Public IP address for SPB: 172.30.11.241

Start on boot            : yes

Current implementation   : Proxy-ARP

Status                   : Started

[root@Chn-nas-1C nas]# /nas/sbin/clariion_mgmt -info

Public IP address for SPA: 172.30.11.240

Public IP address for SPB: 172.30.11.241

Start on boot            : yes

Current implementation   : Proxy-ARP

Status                   : Started

It would appear that I should be in a state that I can stop the Clariion services but this is the result:

[root@Chn-nas-1C nas]# /nas/sbin/clariion_mgmt -stop

Checking if running as root...yes

Checking if model is supported...yes

Checking for integrated system...yes

Checking if interface eth3 is configured...yes

Checking if SP (172.30.11.240) is up...no

Checking if SP (172.30.11.241) is up...yes

Error 22: Could not find SPA

[root@Chn-nas-1C nas]#

I can ping both SPs from the CS so I don't know why it's saying SPA is down.

Any ideas about where to go next or should I just throw in the towel and give support a call?

Edit: I should also add that I can log into Navisphere Express if I hit the SPA IP with a browser.

Message was edited by: jay_scovill

4 Operator

 • 

8.6K Posts

February 28th, 2014 13:00

I would suggest to open a service request

No Events found!

Top