Page 1 of 1

3PAR 8440 Node Rescue Problem

Posted: Sun Oct 25, 2020 3:21 am
by AMINHETFIELD
Hello Dear Friends

I want some guidance
I had a problem with one 3PAR last night
I was doing Node Rescue on one 3PAR 8440
The operating system version was 3.2.2 MU6
First, I erased the hard disk with ahci init and ahci erase commands, and then restarted
I tested the network connection both directly and inside the switch
After the restart, the necessary instructions to start working were applied automatically, but the error that I am sending you the picture was shown.
I tried this several times with a few Nodes, but the error did not go away
Can you guide us what could be the cause of this error and what is the solution?
Thank You

Re: 3PAR 8440 Node Rescue Problem

Posted: Sun Oct 25, 2020 10:21 am
by MammaGutt
When using a switch, what type was it? If it is managed, check spanning tree.

Re: 3PAR 8440 Node Rescue Problem

Posted: Sun Oct 25, 2020 10:25 am
by AMINHETFIELD
MammaGutt wrote:When using a switch, what type was it? If it is managed, check spanning tree.



A simple Network HUB without any Config

Re: 3PAR 8440 Node Rescue Problem

Posted: Mon Nov 30, 2020 5:23 pm
by senate014
Completely disable the Firewall on the VSP that's performing the Node Rescue... Login to the VSP with:

Username = 3parcust
Password = 3parInServ

Then I think it's Option 2, Option 3 and then the Option to "Turn Off Firewall"

Enter Node Rescue IP address details manually at Whack Prompt as instracuted by the VSP:

net addr x.x.x.x (give this node an IP address on the same subnet as the VSP)
net netmask x.x.x.x (same netmask as the VSP)
net gateway x.x.x.x (same gateway as the VSP)
net server x.x.x.x (IP Address of the VSP)
boot net install ipaddr=(net addr IP Address your set above) nm=(net mask you set above) rp=(net server address you set above)::rescue
Hit enter and it should start downloading the 3PAR InformOS you mounted to your VSP, from your VSP :)

Re: 3PAR 8440 Node Rescue Problem

Posted: Fri Dec 04, 2020 3:24 pm
by Silver Arrow
You tried different nodes?

Where the system serial and node ID set to match the system.

Or unset to and default FF?

Have you tried seriel connection, to the rescueing node, and a crossed lan cable
Between the rescueing node and the node to be rescued?