Cluster I/O Protocols (CIP) Configuration and Management Manual (H06.16+, J06.05+)

Restarting CIP on the NonStop Host System
To restart the NonStop host system side of the CIP subsystem, you can stop and restart all the
objects subordinate to CIPMAN. This is like a reboot of the subsystem; all active connections are
stopped.
CAUTION: If you are not running an alternative TCP/IP subsystem, connect to CLCI by using the
OSM Low Level Link. (CLCI provides a primitive terminal emulation when no other TCP/IP subsystem
is available, but has limited functionality.) To connect to CLCI using OSM Low Level Link:
From the File menu, select Start Terminal Emulator > For Startup TACL.
This launches a CLCI TACL session.
1. Stop the subordinate objects by using the SCF command:
> ABORT PROCESS $ZZCIP, SUB ONLY, FORCED
2. Restart the subordinate objects by using the SCF command:
> START PROCESS $ZZCIP, SUB ONLY
Restarting CIP on the CLIM
To restart the CLIM, issue these CLIMCMD commands:
> CLIMCMD {clim-name | ip-address} clim abort
> CLIMCMD {clim-name | ip-address} clim start
You can also reboot a CLIM using the Reboot action in the OSM Service Connection.
For information about using the clim command, see “Troubleshooting Tools and Tips” (page 119).
Controlling Interface States (IP CIP)
To bring an interface up or down, use the ifstart and ifstop CLIMCMD commands. Use these
commands under these circumstances:
• If you want to delete an interface once the CLIM is started; for example, if you want to change
physical interfaces to bonded interfaces. (You need to bring the interface down before doing
so.)
• If you want to delete the only remaining slave of a bond. (You need to use ifstop on the bond
and then delete that slave.)
• If you want to perform maintenance of the CLIM interfaces. (For example, when changing the
cables of an interface, you can do so without bringing down the entire CLIM. First issue an
ifstop command. This notifies the host that the interface is being intentionally brought down
for maintenance by the operator. The host does not take any action (such as failover) for that
interface. After you are done with the maintenance, issue an ifstart on the interface to
activate it for use.
NOTE: Sockets are not affected by ifstop but some socket operations that require the interface
state to be up may receive an error. For example, a connect may receive an unreachable
error.
Activating an Interface
Use the ifstart command to activate an interface if you stopped using the ifstop command. For all
data interfaces (eth1 – ethn, ib0–ibn, bonding and tunnel interfaces), this command informs the
NonStop host system to start using the specified interface. You execute the ifstart command on the
CLIM by using the CLIMCMD tool as described under “Entering CIP Commands” (page 71). Only
use the ifstart command to restart the interface after using ifstop command.
The ifstart command syntax is:
102 CIP Configuration and Management