ServerNet Cluster 6780 Planning and Installation Guide (G06.29+, H06.06+, J06.03+)

Troubleshooting
ServerNet Cluster 6780 Planning and Installation Guide—527301-008
10-8
Switching the SANMAN Primary and Backup
Processes
Switching the SANMAN Primary and Backup Processes
If connectivity to a node is not restored after Steps 1 through 4 in Restoring
Connectivity to a Node on page 10-7, switching the primary and backup processes
forces a takeover of the SANMAN primary process but is not invasive. The SANMAN
process continues to run, and any ServerNet connectivity that is already up does not
go down. When the backup process becomes the new primary, it queries the switches
connected to the node and attempts to program any NNA PICs that are not
programmed.
You can switch the SANMAN primary and backup processes using either SCF or OSM.
Using SCF
At an SCF prompt:
-> PRIMARY PROCESS $ZZSMN
Using OSM
1. Log on to the OSM Service Connection.
2. From the tree pane, right-click the ServerNet Cluster resource, and select
Actions to display the Actions dialog box.
3. From the Available Actions drop-down list, select Switch SANMAN process pair.
4. Click Perform action.
Switching the SNETMON Primary and Backup Processes
When the SNETMON backup process becomes the new primary, it queries all
processors in the node to find the state of ServerNet connections to all other nodes. If
it finds any connections that are down, it initiates a sequence to bring the connections
to an online state.
If connectivity to a node is not restored after you switch the SANMAN primary and
backup processes, you can switch the SNETMON primary and backup processes
using either SCF or OSM.
Using SCF
At an SCF prompt:
-> PRIMARY PROCESS $ZZSCL