MAP 5000: Start
MAP 5000: Start is an entry point to the maintenance analysis procedures (MAPs) for the system.
Before you begin
If you are not familiar with these maintenance analysis procedures (MAPs), first read Using the maintenance analysis procedures.
This MAP applies to all system models. Be sure that you know which model you are using before you start this procedure. To determine which model you are working with, look for the label that identifies the model type on the front of the node.
- The fix procedures sent you here
- A problem occurred during the installation of the system
- Another MAP sent you here
- A user observed a problem that was not detected by the system
System nodes are configured in pairs. While you service one node, you can access all the storage managed by the pair from the other node. With concurrent maintenance, you can remove, replace, and test all FRUs on one system while the SAN and host systems are powered on and doing productive work.
- Unless you have a particular reason, do not remove the power from both nodes unless instructed to do so.
- If an action in these procedures involves removing or replacing a part, use the applicable procedure.
- If the problem persists after you complete the actions in this procedure, return to step 1 of the MAP to try again to fix the problem.
Procedure
- Were you sent here from a fix procedure?
-
(from step 1)
Access the management GUI. See Accessing the management GUI to view events
- (from step 2)
- (from step 3)
-
(from step 4)
Log in to the management GUI. Use the user ID and password that is provided by the user.
Go to the Events page.
Start the fix procedure for the recommended action.
Did the fix procedures find an error that is to be fixed?- NO
- Go to step 6.
- YES
- Follow the fix procedures.
-
(from steps 1, 3, 4, and
5)
Is the power indicator off? Check to see whether the power LED is off.
- NO
- Go to step 7.
- YES
- Try to turn on the nodes. Note:If the nodes are turned on, go to step 7; otherwise, go to MAP 5040: Power control enclosure.
SAN Volume Controller 2145-DH8 does not have an external uninterruptible power supply unit. This system has battery modules in its front panel instead.
-
(from step 6)
Does the node show a hardware error?
- NO
- Go to step 8.
- YES
- The service controller for the system failed. (The SAN Volume Controller 2145-DH8
does
not have a service controller.)
- Check that the service controller that is indicating an error is correctly installed. If it is, replace the service controller.
- Go to MAP 5700: Repair verification.
-
(from step 7)
Is the operator-information panel error LED ( 4 in Figure 1 or 7 in Figure 2) illuminated or flashing? Or, is the check log LED ( 6 in Figure 2) illuminated or flashing?
Figure 1 shows the operator-information panel for the SAN Volume Controller 2145-SV1 .
Figure 2 shows the operator-information panel for the SAN Volume Controller 2145-DH8 .
- NO
- Go to step 9.
- YES
- Go to MAP 5800: Light path.
- (from step 8)
- (from step 9)
-
(from step 9 )
Is the node fault LED ( 8 in Figure 3) on the front panel of a SAN Volume Controller 2145-DH8 on?
Figure 3 shows the node fault LED.- NO
- Go to step 12.
- YES
- Complete these steps:
- Access the service assistant interface via the Technician port for node access and follow the service recommendation presented.
- Go to MAP 5700: Repair verification.
- (from step 11)
-
(from step 12)
If the boot progress does not advance for more than 3 minutes, the progress is stalled.
Has the boot progress stalled?
- NO
- Go to step 14.
- YES
-
(from step 12 and step
13)
Is the node fault LED, which is the middle of the three status LEDs on the front panel of a SAN Volume Controller 2145-DH8 , on? Figure 3 shows the node fault LED.
- NO
- Go to step 15.
- YES
- Complete these steps:
- Note the failure code and go to Node error code overview to complete the repair actions.
- If the node does not have a front panel display, access the service assistant interface via the Technician port for node access and follow the service recommendation presented.
- Go to MAP 5700: Repair verification.
-
(from step 14)
Is Cluster Error reported on the node?
- NO
- Go to step 16.
- YES
- A cluster error was detected. This error code is displayed on all the operational
nodes in the system. The fix procedures normally repair this type of error. Follow
these steps:
- Complete the error code repair actions.
- Go to MAP 5700: Repair verification.
- (from step 15)
-
(from step 16)
Did the node power off?
- NO
- Complete the following steps:
- Remove the power cord from the rear of the box.
- Wait 60 seconds.
- Replace the power cord.
- If the node does not power on, press power to power on the node and then return to step 1 in this MAP.
- YES
- Complete the following steps:
- Wait 60 seconds.
- Click power to turn on the node and then return to step 1 in this MAP.
-
Is there a node that is not a member of a clustered system? You can tell if a node is not a member of a system because the node status LED is off or blinking for SAN Volume Controller 2145-DH8 .
- NO
- Go to step 19.
- YES
- The node is not a member of a system. The node might have been deleted during a maintenance procedure and was not added back into the system. Make sure that each I/O group in the system contains two nodes. If an I/O group has only one node, add the node back into that system. Then, ensure that the node is restored to the same I/O group from which it was deleted.
-
No errors were detected by the system. If you suspect that the problem that is reported by the customer is a hardware problem, follow these tasks:
- Complete Problem Determination procedures on your host systems, disk controllers, and Fibre Channel switches.
- Ask IBM remote technical support for assistance.
-
(from step 10)
Can you access the service assistant interface through the 2145-DH8 technician port or service IP address, or use a USB flash drive to get satask_results.html?
- NO
- The system software might not be running. Attach a USB keyboard and VGA monitor to the 2145-DH8 to see whether the node is stuck booting.
- YES
- Go to step 21.
-
(from step 20)
Can node error 561 be seen?
- NO
- Follow the recommended action for any node error that can be seen.
- YES
- The system software might not be able to communicate with the battery backplane.
- Check the connections between the system board and the battery backplane. Then, follow the recommended action for node error 561.
Results
If you suspect that the problem is a software problem, see Updating the system
documentation
for details about how to update your
entire system environment.
If the problem is still not fixed, collect diagnostic information and contact IBM® Remote Technical Support.