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

Configuring Expand-Over-ServerNet Lines

ServerNet Cluster 6780 Planning and Installation Guide—527301-004

7-2

Using Automatic Line-Handler Generation

Automatic line-handler generation is enabled by default. As soon as you connect the

fiber-optic cables to a node in a ServerNet cluster, Expand-over-ServerNet line-handler

processes and lines are automatically configured to and from that node to all other

nodes in the cluster. The naming convention for each line-handler process is

$SCexpand-node-number such as $SC035.

HP recommends that you use automatic line-handler generation to configure the

Expand-over-ServerNet line-handler processes and lines. If automatic line-handler

generation has been disabled, or if the lines have failed to be configured, you can

manually configure the processes by using either SCF or the Add Node to ServerNet

Cluster action from the OSM Service Connection.

Using the OSM Service Connection

If the line-handlers are not generated automatically, you can use the Add Node to

ServerNet cluster action.

Add Node to ServerNet Cluster Action

Refer to Add Node to ServerNet Cluster Action on page 9-2 for more information.

Using SCF

You must log on to each node to configure Expand-over-ServerNet line-handler

processes needed for each ServerNet node added. You must give each line-handler

process a unique name. HP recommends that you use the naming convention used for

automatic line-handler generation. If you use SCF to configure Expand-over-ServerNet

line-handler processes associated with each line, observe these configuration rules.

Note. Documentation for the procedure is contained in the online help for the procedure.

Before using the procedure to add a node, be sure to review the online help topic “Read Before

Using.”

Note. To log on to a node other than the one where your current TACL process is running, you

must first start a remote TACL process in that node. You must also set up remote passwords

between the local node and the remote node. You do this using the REMOTEPASSWORD

command. For information about configuring remote passwords, refer to the Guardian User’s

Guide.