NETCONTROL STOP [ NS3000/iX Operations & Maintenance Reference Manual ] MPE/iX 5.0 Documentation
NS3000/iX Operations & Maintenance Reference Manual
NETCONTROL STOP
Terminates individual network interfaces on an active transport, or the
entire transport and all its network interfaces.
Syntax
NETCONTROL STOP [;{NET=niName }]
{GATE=gatehalfName}
Parameters
STOP This function, if issued without parameters when
transport is active, irrecoverably stops the entire
transport. When NET or GATE is specified, only that
one network interface and its attached protocols are
terminated; all other network interfaces and
protocols will continue to operate.
NET=niName Specifies the name of a configured network interface
to be terminated, which was previously started. All
protocols and links configured under that NI will
also be terminated. Enter any valid NI name from the
NMMGR Network Interface screen which is not a gateway
half. If neither NET nor GATE are specified, the
entire transport will be terminated, including all
links, NIs, protocols, and the control process. If
transport or the specified NI was not running, a "NOT
STARTED" error will occur.
GATE=gatehalfName Specifies the name of a configured gateway half
network interface to be terminated, and which was
previously started. All protocols and links
configured under that NI will also be terminated.
Enter any valid gatehalf NI name from the NMMGR
Network Interface Configuration screen. The niName
discussion for NET and GATE applies to gatehalf name
also.
Discussion
If STOP is issued without the NET or GATE keyword, all entities of the
network transport are terminated. If STOP is combined with the keyword
NET, only the specified non-gatehalf network interface is terminated. If
STOP is combined with the keyword GATE, only the specified gateway half
is terminated.
When this command is entered with an X.25 NI name, the system accesses
the DTC/X.25 Network Access Subsystem to disable the X.25 address that is
associated with this system. The DTC/X.25 Network Access then no longer
accepts connections for this system. There is no impact on the
connections established between any other systems and the DTC/X.25
Network Access.
Example 1
Example 1 shows how NETCONTROL fits into the process of terminating a
node. In example 1, the node has an NS3000/iX Link. The NSCONTROL
command prevents users or programs from accessing any network services.
(Refer to the NSCONTROL command page in this section for a complete
description of NSCONTROL.) NETCONTROL STOP terminates all active entities
of the network transport.
NOTE When multiple NETCONTROL or NSCONTROL commands are embedded in
UDC's, commandfiles, or batch jobs, HP recommends the use of :PAUSE
commands between commands, to give each time to execute before
starting the next command.
:NSCONTROL STOP
:NSCONTROL ABORT
:NETCONTROL STOP
Example 2
Example 2 shows which network transport entities are affected by the STOP
function. As will be shown in examples 3 and 4, the keywords included
with the STOP function determine which entities are affected.
:NETCONTROL STOP
** NETXPORT ARP; Protocol stop
- Loc: 27; Class: 4; Parm= $00000000; PortID: $FFFFFE89
** NETXPORT Probe; Protocol stop
- Loc: 37; Class: 4; Parm= $00000000; PortID: $FFFFFE89
** NETXPORT IP; Protocol stop
- Loc: 105; Class: 4; Parm= $00000000; PortID: $FFFFFE89
** NETXPORT Control Process; Device Shutdown Warning
- Loc: 283; Class: 3; Parm= $04F502E6; PortID: $FFFFFE8A
** NETXPORT LAN NI; Network interface stop
- Loc: 29; Class: 4; Parm= $96430000; PortID: $FFFFFE81
** NETXPORT Map Tbl; Mapping Table Deleted
- Loc: 2; Class: 4; Parm= $D5208250; PortID: $D5208250
** NETXPORT IP Update; General protocol stop
- Loc: 19; Class: 4; Parm= $00000000; PortID: $FFFFFE88
** NETXPORT UDP; General protocol stop
- Loc: 25; Class: 4; Parm= $00000000; PortID: $FFFFDFF3
** NETXPORT Net Timers; Stopping
- Loc: 4040; Class: 4; Parm= $96430000; PortID: $FFFFFE81
** NETXPORT Control Process; Transport stop
- Loc: 51; Class: 4; Parm= $00000000; PortID: $FFFFDFF0
Example 3
Example 3 shows what happens if the general transport and both network
interfaces are active, and the user specifies the Loopback NI. Notice
that the STOP function acts only on the Loopback NI entity. The general
transport is still active.
:NETCONTROL STOP;NET=LOOP
** NETXPORT IP; Protocol stop
- Loc: 105; Class: 4; Parm= $00000000; PortID: $FFFFFE7F
** NETXPORT Loopback NI; Network interface stop
- Loc: 29; Class: 4; Parm= $96F80000; PortID: $FFFFFE88
** NETXPORT Map Tbl; Mapping Table Deleted
- Loc: 2; Class: 4; Parm= $96F78250; Pin: 0
Example 4
In Example 4, only the general transport and the LAN are active. The
STOP function terminates the LAN NI entity. The general transport is
still active.
:NETCONTROL STOP;NET=LAN1
** NETXPORT ARP; Protocol stop
- Loc: 27; Class: 4; Parm= $00000000; PortID: $FFFFFF04
** NETXPORT Probe; Protocol stop
- Loc: 37; Class: 4; Parm= $00000000; PortID: $FFFFDFF0
** NETXPORT IP; Protocol stop
- Loc: 105; Class: 4; Parm= $00000000; PortID: $FFFFFE84
** NETXPORT Control Process; Device Shutdown Warning
- Loc: 283; Class: 3; Parm= $04F502E6; PortID: $FFFFFE8A
** NETXPORT LAN NI; Network interface stop
- Loc: 29; Class: 4; Parm= $D8020000; PortID: $FFFFFE85
** NETXPORT Map Tbl; Mapping Table Deleted
- Loc: 2; Class: 4; Parm= $97480250; PortID: $97480250
MPE/iX 5.0 Documentation