Replacing the SAN Volume Controller 2145-8G4 service controller

Use the following information to replace the SAN Volume Controller 2145-8G4 service controller.

About this task

To replace the service controller, complete the following steps:

Procedure

  1. Gently push the service controller (shown in Figure 1) into the frame until the rear connectors are fully seated and the service controller front metal work is up to the frame.
    Figure 1. SAN Volume Controller 2145-8G4 service controller
    This photo shows the SAN Volume Controller 2145-8G4 service controller
  2. Slide the SAN Volume Controller 2145-8G4 back into the rack and check that all cables are still firmly in place.
  3. Connect the power cable to the node and replace the cable-retention bracket. See Replacing the cable-retention bracket.
    Note: The worldwide port names (WWPNs) of the Fibre Channel ports are derived from the worldwide node name (WWNN) of the service controller. If you do not perform step 4, you might have to re-zone the Fibre Channel switches if the switch zoning uses WWPN. You must restart the host systems before they are able to access disks through this node.
  4. If you replaced the service controller as part of concurrent maintenance, you must rewrite the WWNN on the new service controller. If you do not, and the Fibre Channel switch zoning uses WWPNs, you cannot add the node back into the cluster until the Fibre Channel switches in the SAN are re-zoned. Also, the host systems cannot access the Fibre Channel ports on that node until the host systems are rebooted.

    You must choose either the WWNN stored on disk or the WWNN stored on the service controller to allow the node to start. If neither of these options is suitable, see the Change WWNN? option from the front panel Actions options for instructions on changing the value.

What to do next

Wait one minute. If Cluster: is displayed on the front panel, the node is ready to be added to the system. If Cluster: does not display, see MAP 5000: Start to determine how to solve this problem or contact the IBM® support center.