MAP 5000: Start

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

If you are not familiar with these maintenance analysis procedures (MAPs), first read Using the maintenance analysis procedures.

This MAP applies to all SAN Volume Controller 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 have been sent here for one of the following reasons:

The web-based Directed Maintenance procedure sent you here
A problem occurred during the installation of a SAN Volume Controller
Another MAP sent you here
A user observed a problem that was not detected by the system

SAN Volume Controller nodes are configured in pairs. While you service one SAN Volume Controller 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 SAN Volume Controller 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 SAN Volume Controller nodes unless instructed to do so.
If a recommended action in these procedures involves removing or replacing a part, use the applicable procedure in the IBM System Storage SAN Volume Controller Hardware Maintenance Guide.
If the problem persists after performing the recommended actions in this procedure, return to step 1 of the MAP to try again to fix the problem.

Perform the following steps:

Were you sent here from a Directed Maintenance procedure?

NO

Go to step 2

YES

Go to step 8
(from step 1)
Find the IBM® System Storage® Productivity Center (SSPC) or master console server that is close to and is set up to manage the SAN Volume Controller cluster. The SSPC is normally located in the same rack as the SAN Volume Controller cluster.
(from step 2)
Log in to the SSPC or master console server using the user ID and password that is provided by the user.
(from step 3)
Log into the SAN Volume Controller Console using the user ID and password that is provided by the user and launch the SAN Volume Controller Console for the cluster that you are repairing.
(from step 4)
Does the SAN Volume Controller Console start?
NO

Go to step 8. See Troubleshooting the SAN Volume Controller Console.

YES

Go to step 6.
(from step 5)
When the SAN Volume Controller cluster that you want to service is selected, is the Welcome panel displayed?
NO

Go to step 8.

YES

Go to step 7.
(from step 6)
Start the Directed Maintenance Procedures.

Did the maintenance procedures find an error that needs to be fixed?
NO

Go to step 8.

YES

Follow the Directed Maintenance procedures.
(from steps 1, 5, 6, and 7)
Is the power indicator on any SAN Volume Controller front panel off? On the SAN Volume Controller models 2145-CF8, 2145-8A4, 2145-8G4, 2145-8F4, and 2145-8F2 check to see if the power LED 1 on the operator-information panel is off; on the SAN Volume Controller 2145-4F2, check to see if the power light 2 on the front panel is off.
Figure 1. Power LED on the SAN Volume Controller models 2145-CF8, 2145-8A4, 2145-8G4, and 2145-8F4 or 2145-8F2 operator-information panel and the power light on the SAN Volume Controller 2145-4F2 front panel
- 1 SAN Volume Controller models 2145-CF8, 2145-8A4, 2145-8G4, 2145-8F4, and 2145-8F2 Power LED
- 2 SAN Volume Controller 2145-4F2 power light
NO

Go to step 9.

YES

Try to turn on the SAN Volume Controller nodes. See Using the power control for the SAN Volume Controller node.
Note: The uninterruptible power supply unit that supplies power to the SAN Volume Controller node might also be turned off. This must be turned on before the SAN Volume Controller node is turned on.
If the SAN Volume Controller nodes are turned on, go to step 9; otherwise, go to the appropriate Power MAP: MAP 5060: Power 2145-8A4, MAP 5050: Power 2145-CF8, 2145-8G4, 2145-8F4, and 2145-8F2, or MAP 5100: Power 2145-4F2.
(from step 8)
Does the front panel of any SAN Volume Controller node show a hardware error? There is a hardware error if any of the following conditions are true for the node:
- None of the LEDs on the front panel are on and the front-panel display is blank.
- The node is a SAN Volume Controller 2145-4F2 and the check LED, which is the top LED on the front panel, is on.
- The node is a SAN Volume Controller model 2145-CF8, 2145-8A4, 2145-8G4, 2145-8F4, or 2145-8F2 and the error LED, which is the bottom LED on the front panel, is on.
  Figure 2 shows the location of the service controller check or error light.
  Figure 2. SAN Volume Controller service controller check or error light
- 1 SAN Volume Controller 2145-4F2 service controller check light (the top LED)
- 2 SAN Volume Controller models 2145-CF8, 2145-8A4, 2145-8G4, 2145-8F4, and 2145-8F2 service-controller error light (the bottom LED)
NO

Go to step 10.

YES
The service controller for the SAN Volume Controller has failed.
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.
Are you working on the SAN Volume Controller 2145-4F2?
NO

Go to step 11.

YES

Go to step 12.
(from step 10)
Is the operator-information panel error LED 1 that you see in Figure 3 illuminated or flashing?

Figure 3. Error LED on the SAN Volume Controller models 2145-CF8, 2145-8A4, 2145-8G4, and 2145-8F4 or 2145-8F2 operator-information panel

NO

Go to step 12.

YES

Go to MAP 5800: Light path.
(from step 10 and step 11)
Is the hardware boot display that you see in Figure 4 displayed on any of the SAN Volume Controller nodes?

Figure 4. Hardware boot display

NO

Go to step 14.

YES

Go to step 13.
(from step 12)
Has the hardware boot display that you see in Figure 4 displayed for more than three minutes?
NO

Go to step 14.

YES
Perform the following:
1. Go to MAP 5900: Hardware boot.
2. Go to MAP 5700: Repair verification.
(from steps 12 and 13)
Is Failed displayed on the top line of the front-panel display of any SAN Volume Controller node?
NO

Go to step 15.

YES
Perform the following:
1. Note the failure code and go to boot code Understanding the boot codes to perform the repair actions.
2. Go to MAP 5700: Repair verification.
(from step 14)
Is Booting displayed on the top line of the front-panel display of any SAN Volume Controller node?
NO

Go to step 17.

YES

Go to step 16.
(from step 15)
A progress bar and a boot code are displayed. If the progress bar does not advance for more than three minutes, it has stalled.

Has the progress bar stalled?
NO

Go to step 17.

YES
Perform the following:
1. Note the failure code and go to boot code Understanding the boot codes to perform the repair actions.
2. Go to MAP 5700: Repair verification.
(from steps 15 and step 16)
If you pressed any of the navigation buttons on the front panel, wait for 60 seconds to ensure that the display has switched to its default display.

Is Node Error displayed on the top line of the front-panel display of any SAN Volume Controller node?
NO

Go to step 18.

YES
Perform the following steps:
1. Note the failure code and go to node error code Understanding the node error codes to perform the repair actions.
2. Go to MAP 5700: Repair verification.
(from step 17)
Is Cluster Error displayed on the top line of the front-panel display of any SAN Volume Controller node?
NO

Go to step 19.

YES
A cluster error was detected. This error code is displayed on all the operational nodes in the cluster. This type of error is normally repaired using the Directed Maintenance procedures. Perform the following steps:
1. Go to step 2 to perform the Directed Maintenance procedure. If you return here, go to cluster error code Understanding cluster error codes to perform the repair actions.
2. Go to MAP 5700: Repair verification.
(from step 18)
Is Powering Off, Restarting, Shutting Down, or Power Failure displayed in the top line of the front-panel display?

NO

Go to step 21.

YES

The progress bar moves every few seconds. Wait for the operation to complete and then return to step 1 in this MAP. If the progress bar does not move for three minutes, press the power button and go to step 20.
(from step 19)
Did the SAN Volume Controller node power off?
NO
Perform 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 the power button to power-on the SAN Volume Controller node and then return to step 1 in this MAP.
YES
Perform the following steps:
1. Wait 60 seconds.
2. Click the power button to turn on the SAN Volume Controller node and then return to step 1 in this MAP.
Note: If the SAN Volume Controller 2145-4F2 is turned off and it is the only SAN Volume Controller 2145-4F2 node that is connected to the 2145 UPS, the 2145 UPS also turns off within five minutes. Before you turn on the SAN Volume Controller 2145-4F2, you must press the power-on button on the 2145 UPS. The 2145 UPS-1U turns off only when its power button is pressed, input power has been lost for more than five minutes, or the SAN Volume Controller node has shut it down following a reported loss of input power.
(from step 20)
Is Charging or Recovering displayed in the top line of the front-panel display of any SAN Volume Controller node?
NO

Go to step 22.

YES
- If Charging is displayed, the uninterruptible power supply battery is not yet charged sufficiently to support the SAN Volume Controller node. If Charging is displayed for more than two hours, go to the MAP for your uninterruptible power supply: MAP 5150: 2145 UPS-1U or MAP 5200: 2145 UPS.
- If Recovering is displayed, the uninterruptible power supply battery is not yet charged sufficiently to be able to support the SAN Volume Controller node immediately following a power supply failure. However, if Recovering is displayed, the SAN Volume Controller node can be used normally.
- If Recovering is displayed for more than two hours, go to the MAP for your specific uninterruptible power supply: MAP 5150: 2145 UPS-1U or MAP 5200: 2145 UPS.
(from step 21)
Is Validate WWNN? displayed on the front-panel display of any SAN Volume Controller node?
NO

Go to step 23.

YES
The node is indicating that its WWNN might need changing. It enters this mode when the node service controller or disk has been changed but the required service procedures have not been followed.
Note: Do not validate the WWNN until you read the following information to ensure that you choose the correct value. If you choose an incorrect value, you might find that the SAN zoning for the node is also not correct and more than one node is using the same WWNN. Therefore, it is important to establish the correct WWNN before you continue.
1. Determine which WWNN that you want to use.
  - If the service controller has been replaced, the correct value is probably the WWNN that is stored on disk (the disk WWNN).
  - If the disk has been replaced, perhaps as part of a frame replacement procedure, but has not been re-initialized, the correct value is probably the WWNN that is stored on the service controller (the panel WWNN).
2. Select the stored WWNN that you want this node to use:
  - To use the WWNN that is stored on the disk, perform the following steps:
    From the Validate WWNN? panel, press and release the select button. The Disk WWNN: panel is displayed and shows the last five digits of the WWNN that is stored on the disk.
    
    From the Disk WWNN: panel, press and release the down button. The Use Disk WWNN? panel is displayed.
    
    Press and release the select button.
  - To use the WWNN that is stored on the service controller, perform the following steps:
    From the Validate WWNN? panel, press and release the select button. The Disk WWNN: panel is displayed.
    
    From the Disk WWNN: panel, press and release the right button. The Panel WWNN: panel is displayed and shows the last five numbers of the WWNN that is stored on the service controller.
    
    From the Panel WWNN: panel, press and release the down button. The Use Panel WWNN? panel is displayed.
    
    Press and release the select button.
3. After you set the WWNN, check the front-panel display:
  - If the Node WWNN: panel is displayed on the front panel, the node is now using the selected WWNN. The Node WWNN: panel shows the last five numbers of the WWNN that you selected.
  - If the front panel shows Cluster: but does not show a cluster name, you must use the console application to delete the node from the cluster and add the node back into the cluster.
(from step 22)
Is there a node that is not a member of a cluster? You can tell if a node is not a member of a cluster by checking the front panel cluster menu. If Cluster: is displayed but no cluster name is shown, the node is not a member of a cluster. (The cluster name is on the second line of the front-panel display if the current language font allows a two-line display. Otherwise, you can press the select button to display the cluster name.)

NO

Go to step 24.

YES

The node is not a member of a cluster. The node might have been deleted from the cluster during a maintenance procedure and has not been added back into the cluster. Make sure that each I/O group in the cluster contains two nodes. If an I/O group in the cluster has only one node, add the node back into that cluster and ensure that the node is restored to the same I/O group that it was deleted from.
(from step 23)
Is the front-panel display unreadable?
NO

Go to step 25.

YES
Perform the following steps:
1. Check the language. The display might be set to another language.
2. If the language is set correctly, go to MAP 5400: Front panel.
(from step 24)
No errors were detected by the SAN Volume Controller. If you suspect that the problem that is reported by the customer is a hardware problem, perform the following tasks:
1. Perform Problem Determination procedures on your host systems, disk controllers, and fibre-channel switches.
2. Ask your hardware support center for assistance.

If you suspect that the problem is a software problem, see Upgrading the SAN Volume Controller software.

If the problem is still not fixed, collect diagnostic information and contact the IBM support center.