HP 3PAR StoreServ 7450 4-node HP 3PAR StoreServ 7450 Storage Service Guide - Page 54

B Node Rescue, Service Processor (Physical) Node Rescue

Get HP 3PAR StoreServ 7450 4-node PDF manuals and user guides View all HP 3PAR StoreServ 7450 4-node manuals
Add to My Manuals
Save this manual to your list of manuals

Page 54 highlights

B Node Rescue Service Processor (Physical) Node Rescue The SP node rescue should be used only in cases when the storage system includes a physical SP and no nodes remain in the cluster or when all nodes are down. NOTE: For SP node rescue, you can specify whether to use the public Ethernet port (MGMT) or the private Ethernet port and a crossover cable. To perform an SP node rescue: 1. Connect the crossover cable to the SP and to the MGMT port of the node that is being rescued. 2. Connect the network cable to the MGMT port on the SP and connect the free end of the cable to the Ethernet port on the laptop. 3. Access SPmaint and in the 3PAR Service Processor Menu, select the following: • 4 InServ Product Maintenance • 11 Node Rescue • 1 Configure Node Rescue, then select the desired system • 3 Automatic Node Rescue, then enter the node number 4. Select y to confirm the correct node number. When communication from the SP to the node is established, output similar to the following appears: NOTE: This process takes approximately 15 minutes. When complete, the node reboots and becomes part of the cluster. If the process takes longer than twenty minutes, problems may exist and the node rescue process needs to be corrected. root@1200163-0 Tue Apr 01 16:53:19:~# beginning rescue function... .255.248 -s 10.255.155.54155.53 -m 255.255 Informing system manager to not autoreset node1 Resetting node 1 Attempting to contact node 1 via internal serial port Waiting for node to respond (10 seconds elapsed)... Waiting for node to respond (20 seconds elapsed)... Waiting for node to respond (30 seconds elapsed)... =Successfully started inter-node serial link communication Starting Whack, setting values, and loading image: Interacting with CBIOS on the node... . Booting from net... TFTP "install" from 10.255.155.54 complete mknbi-1.2-7/first32.c (GPL) Top of ramdisk is 0X1FFFF000 Ramdisk at 0X00800000, size 0X00500000 . Kernel on remote node has been started. Waiting for node to join cluster. This usually takes around 10 minutes, but may take 20 minutes or longer. Install kernel is running - please wait... Waiting for node to join cluster (0 minutes and 15 seconds elapsed) =Waiting for node to join cluster (0 minutes and 30 seconds elapsed) . Waiting for node to join cluster (13 minutes and 15 seconds elapsed) =Node 1 has joined the cluster; node rescue successful. . Please wait... Starting SP tasks..... 54 Node Rescue

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
B Node Rescue
Service Processor (Physical) Node Rescue
The SP node rescue should be used only in cases when the storage system includes a physical SP
and no nodes remain in the cluster or when all nodes are down.
NOTE:
For SP node rescue, you can specify whether to use the public Ethernet port (MGMT) or
the private Ethernet port and a crossover cable.
To perform an SP node rescue:
1.
Connect the crossover cable to the SP and to the MGMT port of the node that is being rescued.
2.
Connect the network cable to the MGMT port on the SP and connect the free end of the cable
to the Ethernet port on the laptop.
3.
Access SPmaint and in the 3PAR Service Processor Menu, select the following:
•
4 InServ Product Maintenance
•
11 Node Rescue
•
1 Configure Node Rescue
, then select the desired system
•
3 Automatic Node Rescue
, then enter the node number
4.
Select
y
to confirm the correct node number. When communication from the SP to the node
is established, output similar to the following appears:
NOTE:
This process takes approximately 15 minutes. When complete, the node reboots
and becomes part of the cluster. If the process takes longer than twenty minutes, problems
may exist and the node rescue process needs to be corrected.
root@1200163-0 Tue Apr 01 16:53:19:~# beginning rescue function...
.255.248 -s 10.255.155.54155.53 -m 255.255
Informing system manager to not autoreset node1
Resetting node 1
Attempting to contact node 1 via internal serial port
Waiting for node to respond (10 seconds elapsed)...
Waiting for node to respond (20 seconds elapsed)...
Waiting for node to respond (30 seconds elapsed)...
=Successfully started inter-node serial link communication
Starting Whack, setting values, and loading image:
Interacting with CBIOS on the node...
.
Booting from net...
TFTP "install" from 10.255.155.54
................................
complete
mknbi-1.2-7/first32.c (GPL)
Top of ramdisk is 0X1FFFF000
Ramdisk at 0X00800000, size 0X00500000
.
Kernel on remote node has been started.
Waiting for node to join cluster.
This usually takes around 10 minutes, but may
take 20 minutes or longer.
Install kernel is running - please wait...
Waiting for node to join cluster (0 minutes and 15 seconds elapsed)
=Waiting for node to join cluster (0 minutes and 30 seconds elapsed)
.
Waiting for node to join cluster (13 minutes and 15 seconds elapsed)
=Node 1 has joined the cluster; node rescue successful.
.
Please wait...
Starting SP tasks
.....
54
Node Rescue