3par 8200 unable to access management network

[shang1983]

I have a 8200 connected with 2 management network connected. When i test the redundancy management network. it fails. 
How can I bring back the management IP up without halting the storage?

[Torsten.]

How did you test this?

[shang1983]

I open the command prompt to continuous ping the management ip. Then I unplug the node 0 management cable. I checked the command prompt the ping result is the ip still pingable, I plug back the node 0 management cable.
After 2minutes, I unplug the node1 management cable. The command prompt result request time out. After 1minute waiting, the result still request time out. I plug back node1 management cable.
The ping result still request timeout.

[Dennis Handly]

You can use shownet to show the active node.  And setnet to change it.

[shang1983]

I do not want to change the IP. I just need to bring back the management network up. Last time I tried before is to halt the storage and power back on. 

But now the storage is live. Not sure reboot one node at a time can resolve this or not

[Torsten.]

switching the node may take a few minutes, wait 5 minutes.

i have seen the same scenario as yours before, the other node has a link, but the switch was wrongly confifured, hence no ping. consider to check this and swap the LAN cable between nodes. as said, be patient between changes.

[Sheldon Smith]

While each controller node can have a management cable connection, the system has only one IP address which moves from controller node management port to controller node management port. The other ports are inactive.

You can change which node has the active Ethernet interface using the
"setnet changenode [<node_ID>]" command.

(From the HPE 3PAR OS Command Line Interface Reference, "setnet")
changenode
"Forces the system to change which node has an active Ethernet interface.
If a node ID is specified, it switches to that node. Otherwise, any node with a connected Ethernet interface is chosen."

And then, as was written above, be patient.

[Dennis Handly]

> I do not want to change the IP.

As Sheldon and I said, you can just change the active node.

[shang1983 · Accepted solution]

I reboot one node at a time to resolve the issue.