Expand Configuration and Management Manual (G06.24+)

Managing the Network
Expand Configuration and Management Manual523347-008
19-22
Removing Nodes From the Network
Removing Nodes From the Network
This subsection explains how to remove a node from the network using the
management commands described in the preceding subsections. This explanation is
presented in two steps.
Step 1: Stop the lines
You must stop the Expand lines at the local node and the corresponding Expand lines
at adjacent (or neighbor) nodes using one of the following Expand subsystem SCF
commands:
ABORT LINE $device_name
ABORT PATH $device_name
Step 2: Verify that the lines have stopped
You can verify that the lines have stopped by using the one of the Expand subsystem
SCF commands described in Table 19-10.
Changing System Names and Numbers
This subsection explains how to change a system name and number using the
management commands described in the preceding subsections. This explanation is
presented in eight steps. Generally, changing a system name or number is only
necessary if more than one system in the network has the same name or number,
resulting in a conflict.
Note. Use the Expand subsystem SCF ABORT PATH command for multi-line paths. The SCF
ABORT LINE command affects the specified line and its associated path logical device; it does
not affect other lines in the multi-line path.
Note. If you are permanently removing a node from the network, it is suggested that you also
remove its node (system) name and number from the network routing table (NRT) at each
remaining node in the network. This prevents name and number conflicts with future nodes.
Refer to Changing System Names and Numbers
for a description of the commands to use to
remove node names and numbers from the NRT.
Caution. If you must change a system name or number, use extreme caution. Changing a
system name or number can adversely affect products and applications that are currently using
the system name or number.
After you change a node number, you might lose access to alternate-key files, such as OSS
configuration files. Refer to the appropriate manuals describing the alternate-key files for
further information. For example, the Open System Services Management and Operations
Guide has a subsection on changing a node number.