Documente Academic
Documente Profesional
Documente Cultură
OPERATIONAL INSTRUCTION
Page 1 of 16
Introduction
Scope
2
2.1
2.2
Procedure
Prerequisites
Actions
3
3.1
3.2
3.3
Additional Information
Update AM FW
Delete customer data on the faulty node
Update RAID FW
Glossary
5
5.1
5.2
References
Operational Instructions
Printout Descriptions
file://C:\Program Files\ALEX\Lib\ALEX_TMP\1005\alex0285.htm
2/5/2016
Page 2 of 16
1 Introduction
1.1 Scope
This Operational Instruction describes the procedure to change a node in the Adjunct Processor
(AP) cluster. This procedure must be performed on site.
file://C:\Program Files\ALEX\Lib\ALEX_TMP\1005\alex0285.htm
2/5/2016
Page 3 of 16
2 Procedure
2.1 Prerequisites
2.1.1
Conditions
The following conditions must apply before this procedure can be completed:
2.1.2
Data
Special Aids
A VGA monitor.
A keyboard with PS/2 or USB connector.
A mouse with PS/2 or USB connector.
An adapter to connect the keyboard and monitor to the same cable.
A grounding strap. To be used when exchanging the equipment.
file://C:\Program Files\ALEX\Lib\ALEX_TMP\1005\alex0285.htm
2/5/2016
Page 4 of 16
2.2 Actions
Find out which Node to Replace
1. Find out which node to replace by examining the alarm printout from AP FAULT or the
work order.
Logon to Faulty Node
2. Connect to the faulty node by inserting the adapter to the mouse/keyboard input on the
AP. Connect the keyboard and the mouse to the adapter and connect the monitor to the
monitor input. Logon as a user with administrative rights.
Note:
If it is not possible to login to the faulty node then proceed with Step 6. In that case
stopping the cluster server is not possible as in steps from Step 3 to Step 5.
Stop Cluster Service
3. Stop ACS_PRC_EventAnalyser on the faulty node. Enter the following command in a
Command Prompt window:
cluster res ACS_PRC_EventAnalyser_<0/1> /off /wait
Note:
Select either '0' or '1' depending on the last letter of the faulty AP node's hostname.
If the last letter is 'a' select '0' and if the last letter is 'b' select '1'.
4. Stop acs_prc_clustercontrol on the faulty node. Enter the following command in a
Command Prompt window:
net stop acs_prc_clustercontrol
5. Stop Cluster Service on the faulty node. Enter the following command in a Command
Prompt window:
net stop clussvc
Note:
Confirm the question, cluster service will also stop "ACS_FCH_Server" service with
"yes".
Logon to Active Node
6. Connect to the active node by inserting the adapter to the mouse/keyboard input on the
AP. Connect the keyboard and the mouse to the adapter and connect the monitor to the
monitor input. Logon as a user with administrative rights.
Check Drive Status
7. Ensure that all the drives residing in the active node have the status optimal and also
check their capacity. Enter the following command in a Command Prompt window:
megarc -dispcfg -a0
Note:
file://C:\Program Files\ALEX\Lib\ALEX_TMP\1005\alex0285.htm
2/5/2016
Page 5 of 16
All three of them should be in the state optimal. Under the column Capacity you can
see the capacity. Take a note of this value. If the drives on the active node have a
status other than optimal then this Operational Instruction cannot correct the
problem.
8. Are all the drives in the active node optimal?
Yes
Go to Step 9.
No
Go to Step 69.
9. Check which firmware version that is installed. Enter the following command in a
Command Prompt window:
megarc -ctlrinfo -a0
Note:
Under the column firmware version you can see the version. Note this down.
Note down Heartbeat IP addresses
10. Enter the following command in a Command Prompt window:
ipconfig
11. Note down the IP addresses of Heartbeat 1 and Heartbeat 2.
Bring Cluster into Safe State
12. Set cluster's hardware and software in a state that allows replacement of the faulty node.
Enter the following command in the active node:
fcc_save_to_remove other
Note:
Confirm the question with "yes".
Note:
If you were unable to perform the steps from Step 3 to Step 5 the command may
give an error message since the command will try to stop the cluster service on the
faulty node.
Note:
If the fcc_save_to_remove command hang (for more than 10 minutes) or does not
shut down the node properly then log on to the faulty (passive) node and shut it
down with START->Shut Down and select Shut down.
Disconnect Faulty Node
13.
Warning!
file://C:\Program Files\ALEX\Lib\ALEX_TMP\1005\alex0285.htm
2/5/2016
Page 6 of 16
In case of a suspected hardware fault, the node shall be exchanged. It's not
allowed to exchange boards since that will violate any warranties.
Warning!
There is a special procedure for removing the SCSI cables. This procedure must
be followed to ensure that the SCSI bus will be terminated correctly.
Wait until the Manual Intervention Allowed (MIA) LED is lit and then disconnect the faulty
node. Disconnect the cables from the faulty node in the following order:
Table 1
1
2
3
4
5
6
7
8
9
Power cable
Public ethernet cable
IPN ethernet cable
External alarms cable
Alarm panel cable
Both Heartbeat ethernet cables
Both Serial cables (to CPU board and AM board)
Monitor cable
Keyboard/Mouse adapter cable
Note:
The SCSI cables should be removed in the correct order. See next step.
Disconnect SCSI Cables
14. Always disconnect the SCSI connectors of the active node before removing the SCSI
connectors of the powered-down (faulty) node. Disconnect the SCSI cables in the
following order:
Table 2
1
2
3
4
Disconnect
Disconnect
Disconnect
Disconnect
the
the
the
the
Replace Node
15. Replace the faulty node with the replacement node.
16. Connect the cables in the following order:
Table 3
1
2
3
4
5
file://C:\Program Files\ALEX\Lib\ALEX_TMP\1005\alex0285.htm
2/5/2016
Page 7 of 16
file://C:\Program Files\ALEX\Lib\ALEX_TMP\1005\alex0285.htm
2/5/2016
Page 8 of 16
24. This spare part cannot be used. The disks in the spare part must have equal or bigger
capacity than the disks in the active node. Go to Step 69.
Unpack Backup to System Disk
25. On which media do you have a valid backup?
DAT Tape
Go to Step 26.
FTP site
Go to Step 34.
The shared disk M:\Images\node(a/b)
Go to Step 35.
26. In the active node, insert a tape containing the backup.
27. Check that the correct backup is inserted in the tape drive. Enter the following command in
a Command Prompt window:
emfls
28. Is the backup valid?
YES
Go to Step 29.
NO
Go to Step 25.
29. Copy the backup file to be restored from the tape containing the backup file to M:\Images.
Enter the following command in a Command Prompt window:
emfcopy -m FROMTAPE <BACKUPFILENAME>.zip M:\Images\node(a/b)
Note:
The backup should be valid for the node to be restored.
Note:
Select either a or b in (a/b) depending on the last letter of the replaced AP node's
hostname.
30. Enter the following command in a Command Prompt window:
emfinfo -n <NODENAME>
Note:
<NODENAME> is the name of the node on which the copy operation was initiated.
31. Is the copy operation finished?
YES
Go to Step 32.
NO
Go to Step 30.
32. When copying is finished, eject the tape.
file://C:\Program Files\ALEX\Lib\ALEX_TMP\1005\alex0285.htm
2/5/2016
Page 9 of 16
file://C:\Program Files\ALEX\Lib\ALEX_TMP\1005\alex0285.htm
2/5/2016
Page 10 of 16
41. Was the RAID firmware (FW) version in the replaced node equal to the one in the active
node?
YES
Go to Step 43.
NO
Go to Section 3.3 and then return to Step 42.
Note:
Refer to Step 9 for the RAID FW version in the active node.
42. In a Command Prompt window, enter the following command:
shutdown /r /t 1
Check AM FW
43. Check which AM FW version is used on the active node. Enter the following command in
the active node:
fcc_amversion own
44. Check which AM FW version is used on the replaced node. Enter the following command in
the replaced node:
fcc_amversion own
45. Are the AM FW versions identical on the active and on the replaced node?
YES
Go to Step 50.
NO
Go to Step 46.
Note:
Compare the printouts received in Step 43 and Step 44.
46. Enter the following command:
dir /d c:\Program Files\Force\am_services
47. Is the correct version available on the replaced node?
YES
Go to Section 3.1 and return to Step 50.
NO
Go to Step 48.
Note:
The file used when upgrading the AM FW should be named
<lbb_am_appl_x_y_r.bin> where 'x' and 'y' is the AM FW version and should
correspond to the printout received in Step 43.
48. Copy the correct 'lbb_am_appl_x_y_r.bin' file from the active node. Enter the following
command:
file://C:\Program Files\ALEX\Lib\ALEX_TMP\1005\alex0285.htm
2/5/2016
Page 11 of 16
1
2
3
4
Connect
Connect
Connect
Connect
the
the
the
the
Note:
The SCSI cables must be crossconnected (i.e. SCSI 1 on one node to SCSI 0 on the
other. The same for SCSI 0 to SCSI 1).
Reconnect Other Cables
55. Reconnect the remaining cables in the following order:
Table 5
1
2
3
4
5
file://C:\Program Files\ALEX\Lib\ALEX_TMP\1005\alex0285.htm
2/5/2016
Page 12 of 16
file://C:\Program Files\ALEX\Lib\ALEX_TMP\1005\alex0285.htm
2/5/2016
Page 13 of 16
file://C:\Program Files\ALEX\Lib\ALEX_TMP\1005\alex0285.htm
2/5/2016
Page 14 of 16
3 Additional Information
3.1 Update AM FW
1. Start the AM configuration tool by using START->Programs->AM Configuration->AM
Configuration.
2. Select the tab Installation.
3. Press UpgradeAMgo.. button.
4. In the AMgo Upgrade window press the Browse button.
5. Select the file lbb_am_appl_x_y_r.bin (where 'x' and 'y' is the AM FW version).
6. Press the Open button.
7. Press the Start button.
8. Answer OK on the pop up menu and wait until the firmware is upgraded.
9. When the upgrade status has changed to Success the upgrade is finished.
10. Press OK to exit the AM configuration tool.
11. The AM firmware is now updated.
file://C:\Program Files\ALEX\Lib\ALEX_TMP\1005\alex0285.htm
2/5/2016
Page 15 of 16
4 Glossary
-
file://C:\Program Files\ALEX\Lib\ALEX_TMP\1005\alex0285.htm
2/5/2016
Page 16 of 16
5 References
5.1 Operational Instructions
AP, System Backup and Verify, Initiate
Report of Finished Work
file://C:\Program Files\ALEX\Lib\ALEX_TMP\1005\alex0285.htm
2/5/2016