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

Table 17 Subsystem Task Comparison (continued)
In CIP, Use...In Parallel Library TCP/IP and
NonStop TCP/IPv6, Use...
In Conventional TCP/IP, Use...Task
CLIMCMD clim-name ifstop
command
SCF STOP SUBNET commandSCF STOP SUBNET commandStop a network
interface
None, delete route with
CLIMCMD climconfig route
-delete command
SCF STOP ROUTE commandSCF STOP ROUTE commandStop a network
route
SCF STOP CLIM if no open
sockets, otherwise, ABORT
CLIM, FORCED command
SLSA SCF STOP ADAPTER
command
SLSA SCF STOP ADAPTER
command
Stop an adapter
(or module)
SCF STOP PROCESS CIPSAM
process-name. If persistent,
SCF STOP PROCESS
TCP6SAM process-name
SCF STOP PROCESS TCP/IP
process-name
Stop
a transport-
SCF ABORT PROCESS
service-
$ZZKRN.#CIPSAM. If
persistent and you only want
provider
to stop one CIPSAM process,
process
you can stop it implicitly by
stopping the PROVIDER object
upon which the CIPSAM
process depends.
SCF STOP PROVIDER if no
open sockets, otherwise,
No equivalentNo equivalentStop a PROVIDER
object
ABORT PROVIDER, FORCED
command
SCF SWITCH CLIM commandNo equivalentNo equivalentSwitch the CLIM
CLIMCMD clim-name
tcpdump (See the man page
SCF TRACE SUBNET
command
SCF TRACE SUBNET
command
Trace IP interfaces
for information about
tcpdump.)
SCF TRACE PROCESS
command (traces the Manager
process)
SCF TRACE PROCESS
command
SCF TRACE PROCESS
command
Trace a process
SCF TRACE MON commandSCF TRACE MON commandNo equivalentTrace a MON
process activities
SCF TRACE PROVIDER
command (only one provider
in a processor can be traced)
No equivalentNo equivalentTrace PROVIDER
object
SCF TRACE CLIM commandNo equivalentNo equivalentTrace CLIM object
SCF VERSION PROCESS
command
SCF VERSION PROCESS
command
No equivalentGet Version level
of MAN process
SCF VERSION CLIM commandNo equivalentNo equivalentGet Version of
the CLIM software
SCF VERSION MON
command
SCF VERSION MON
command
No equivalentGet Version level
of the MON
object
SLSA Subsystem
CIP does not use the SLSA subsystem. In conventional TCP/IP, Parallel Library TCP/IP and NonStop
TCP/IPv6, there were two things you needed to do with the SLSA subsystem: Ensure that it was
running before you started using TCP/IP and associate a specific network interface with your
TCP/IP transport-provider process. In the previous subsystems, you could use the SLSA DEVICENAME
Operational Differences Between Previous TCP/IP Subsystems and CIP 181