ServerNet Cluster 6780 Planning and Installation Guide (G06.24+, H06.03+)

Starting and Stopping ServerNet Cluster Processes

and Subsystems

ServerNet Cluster 6780 Planning and Installation Guide—527301-004

11-4

Starting the ServerNet Cluster Subsystem

You can also configure the ServerNet cluster subsystem to start automatically. Refer to

Appendix E, Configuring MSGMON, SANMAN, and SNETMON for more information.

1. To start the ServerNet cluster subsystem using SCF or OSM, either:

•

Type this command at an SCF prompt:

-> START SUBSYS $ZZSCL

•

Use the OSM Service Connection to perform the Start ServerNet Cluster

Services action on the ServerNet Cluster resource. For more information

about starting ServerNet cluster services, refer to OSM online help.

2. Check that the ServerNet cluster subsystem is started. Refer to Checking the

ServerNet Cluster Subsystem on page 8-14.

3. Use SCF to check for connectivity problems. Refer to Checking for Problems

Between Nodes on page 8-4.

4. If you continue to have problems, contact your service provider.

Starting the External ServerNet Fabric

1. Use the OSM Service Connection to verify that the switch is operational.

2. On all affected nodes, use SCF to start the ServerNet fabric:

-> START SERVERNET $ZSNET.FABRIC.*

To avoid having to log in directly to each node:

-> START SERVERNET \remotenode.$ZSNET.FABRIC.*

Starting SANMAN

If SANMAN is configured but not started:

1. Use SCF to start SANMAN:

-> START PROCESS $ZZKRN.#ZZSMN

2. Check that the SANMAN is started.

3. If SANMAN does not start, check the configuration of SANMAN.

4. If you continue to have problems, contact your service provider.

Note. After a hard reset of the switch or after communications through an external ServerNet

fabric have been disrupted for any reason, direct ServerNet connectivity is automatically

restored after an interval of approximately 25 seconds times the number of nodes in the

cluster. You can use this command for faster recovery.