MAP 5000: Start

MAP 5000: Start is an entry point to the maintenance analysis procedures (MAPs) for the system.

Before you begin

Note: The service assistant interface must be used if there is no front panel display, for example on the SAN Volume Controller 2145-DH8.

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.

You might be sent here for one of the following reasons:

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.

Notes:

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?
NO

Go to step 2

YES

Go to step 6
(from step 1)
Access the management GUI. See Accessing the management GUI
(from step 2)
Does the management GUI start?
NO

Go to step 6.

YES

Go to step 4.
(from step 3)
Is the Welcome window displayed?
NO

Go to step 6.

YES

Go to step 5.
(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:
SAN Volume Controller 2145-DH8 does not have an external uninterruptible power supply unit. This system has battery modules in its front panel instead.

If the nodes are turned on, go to step 7; otherwise, go to MAP 5040: Power SAN Volume Controller 2145-DH8.
(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.)
1. Check that the service controller that is indicating an error is correctly installed. If it is, replace the service controller.
2. 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 1. SAN Volume Controller 2145-SV1 operator-information panel
- 1 Power-control button and power-on LED
- 2 Identify LED
- 3 Node status LED
- 4 Node fault LED
- 5 Battery status LED
Figure 2 shows the operator-information panel for the SAN Volume Controller 2145-DH8.
Figure 2. SAN Volume Controller 2145-DH8 operator-information panel
- 1 Power-control button and power-on LED
- 2 Ethernet icon
- 3 System-locator button and LED
- 4 Release latch for the light path diagnostics panel
- 5 Ethernet activity LEDs
- 6 Check log LED
- 7 System-error LED
Note: If the node has more than four Ethernet ports, activity for ports 5 and above is not indicated by the Ethernet activity LEDs on the operator-information panel.
NO

Go to step 9.

YES

Go to MAP 5800: Light path.
(from step 8)
For a 2145-DH8 model, is the node status LED, node fault LED, and battery status LED that you see in Figure 3 all off?

NO

Go to step 11.

YES

Go to step 10.
(from step 9)
For 2145-DH8, has the node status LED, node fault LED, and battery status LED that you see in Figure 3 all been off for more than 3 minutes?
NO

Go to step 11.

YES
For 2145-DH8, go to step 20. Otherwise:
1. Go to Resolving a problem with failure to boot
2. Go to MAP 5700: Repair verification.
(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.
Figure 3. SAN Volume Controller 2145-DH8 front panel
- 7 Node status LED
- 8 Node fault LED
- 9 Battery status LED
NO

Go to step 12.

YES
Complete these steps:
1. Access the service assistant interface via the Technician port for node access and follow the service recommendation presented.
2. Go to MAP 5700: Repair verification.
(from step 11)
Is Booting indicated on the node?
NO

Go to step 14.

YES

Go to step 13.
(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
1. Go to MAP 5700: Repair verification.
(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:
1. Note the failure code and go to Node error code overview to complete the repair actions.
2. 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.
3. 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:
1. Complete the error code repair actions.
2. Go to MAP 5700: Repair verification.
(from step 15)
Is Powering Off, Restarting, Shutting Down, or Power Failure reported on the node?

NO

Go to step 17.

YES

Wait for the operation to complete and then return to step 1 in this MAP. If the progress is stalled after 3 minutes, press power and go to step 17.
(from step 16)
Did the node power off?
NO
Complete the following steps:
1. Remove the power cord from the rear of the box.
2. Wait 60 seconds.
3. Replace the power cord.
4. 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:
1. Wait 60 seconds.
2. 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:
1. Complete Problem Determination procedures on your host systems, disk controllers, and Fibre Channel switches.
2. 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.