NETCONTROL


NETCONTROL

     Command used to initialize, terminate, and control the
operation of the NS3000/iX Transport software. (CM)

SYNTAX


NETCONTROL {function[=parms] [;entity]}
{[entity;] function[=parms]}

function may be

ADDLINK STATUS TRACEOFF
DELLINK STOP UPDATE
START TRACEON VERSION

entity may be

NET=niname
GATE=gatehalfname
PROT=gprot
NI=niname [;PROT=niprot]

together these may used in the following forms

ADDLINK=linkname; {NET=niname }
{GATE=gatehalfname}

DELLINK=linkname; {NET=niname }
{GATE=gatehalfname}

START [;{NET=niname }]
{GATE=gatehalfname}

STATUS[=ALL] [;{NI=niname [;PROT=niprot]} ]
{NET=niname }
{GATE=gatehalfname }
{PROT=gprot }

STOP [;{NET=niname }]
{GATE=gatehalfname}

{TRACEON=type[,options]} [;{NI=niname [;PROT=niprot]} ]
{TRACEOFF } {NET=niname }
{GATE=gatehalfname }
{PROT=gprot }
"options" may be

[DISC][,[filename][,[recsize][,filesize] ]]


UPDATE={INTERNET}; {NET=niname }
{MAPPING } {GATE=gatehalfname}
{NETDIR }
{X25 }
{ALL }

VERSION[=MOD]


PARAMETERS


NET=niname Specifies a group entity consisting of a network
interface which is not a gateway half, and all the
protocol modules configured for that network
interface. Not all functions may be applied as a
group; refer to the individual command function
for details.

GATE= Specifies a group entity consisting of a configured
gatehalfname gateway half network interface, and all protocol
modules configured for that network interface. Not
all functions may be applied as a group; refer to
the individual command function for details.
NOTE: this keyword cannot be used to select true
"gateways" as configured in the INTERNET subtree
under a network interface.

PROT=gprot Specifies a particular general protocol module upon
which a function will act. Valid inputs include
TCP, UDP, PXP, or IPU. See individual command
functions for details.

PROT=niprot Specifies a particular network interface protocol
module upon which a function will act. Valid inputs
include IP, PROBE, ARP, X25 and DIAL, though actual
inputs depend on the type of network interface
(LAN, etc.). Must be further qualified by the NI=
keyword to select a network interface. Refer to
individual command functions for details.

NI=niname Specifies a particular network interface upon
which a function will act. Usually used in
conjunction with the PROT= keyword to select a
particular network interface protocol. See the
individual command functions for details.

linkname Specifies the name of a configured link to be
dynamically added to or deleted from the active
transport; see ADDLINK or DELLINK for details.

type Specifies the type of data the specified protocol
module--or other entity--should trace. This field
is made up of one or more concatenated key letters;
valid inputs include M,H,D,S,B, and/or N; refer to
TRACEON for details.

options: Specifies additional information about where to put
DISC, filename, collected trace data; see TRACEON for details.
recsize, filesize


OPERATION

     The NETCONTROL command provides specific control capabilities over
the NS3000/iX Transport and all its configured networks on the host
system. Typical use is to start or stop NS transport after the
system boots up or prior to a system backup. Other control
functions provide additional utility and maintenance features. See
the examples which follow below for sample uses.

Node Manager (NM) capability is required to use this command.

Some NETCONTROL commands produce output at the user session which
issued the command. For others, logging messages may appear at the
system console, but there will be no output at the user terminal.
The amount of logging output depends on the settings in the NMMGR
Netxport Log Configuration screen for subsystem 3, Network Transport.

Most NETCONTROL commands are interpreted by the system, then sent
to the transport control process (NETCP) for execution, after which
the NETCONTROL interpreter awaits command completion. Only one
command at a time can be executed by the control process, so if
multiple users issue commands, all commands must wait their turn to
use the control process, at which point they will execute.

NS3000/iX Transport utilizes a hierarchical, modular structure
which begins with a control process and the general protocols TCP,
UDP, PXP, and IPU at the highest level. These either communicate
directly with link drivers, or with network interface modules
(NIs), which in turn communicate with the drivers, depending on
NI type and configuration. Each NI also has NI-specific protocols
bound to it: Point-to-point router NIs may bind a DIAL security
protocol; LAN NIs always bind at least one address resolution
protocol, ARP and/or PROBE; X.25 NIs have the X.25 protocol; and
all NIs bind the IP protocol.

Each NI operates in a mode specific to the type of link driver
operating under its control, such as LAN, Token Ring, FDDI, X.25,
or LAPB. A loopback NI type is also provided, allowing NS3000
Services to talk between themselves on the same host system without
actually going through a driver.

The hierarchical NS structure is reflected in NETCONTROL commands
for a specific protocol module attached to a specific NI. Care
should be taken to enter all the proper parameters to avoid acting
on the wrong module, though in most cases an error will simply
be reported if parameters are incorrect. If unfamiliar with your
system's network configuration, you should refer to configuration
data in the NMCONFIG.PUB.SYS file, when selecting a module for a
NETCONTROL command to act on. Often this is best done under the
guidance of your Network Manager or an HP support representative.

When using X.25 networks, the DTC (Distributed Terminal Controller)
may also be involved. A valid DTC configuration will be required
in NMCONFIG, and :DTCCNTRL commands may also be needed, depending
on the whether the X.25 network is host-based.

This command may be issued from a session, job, program, UDC, command-
file, or in BREAK. Pressing [Break] has no effect on this command.

NOTE: The NETCONTROL command interpreter accepts multiple functions
on the same command line (for instance, NETCONTROL START;STATUS)
however HP does not recommend use of this feature because the
behavior is not always predictable under all network conditions.
Separate commands should be used instead whenever possible.

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.


EXAMPLE

     To check the level of transport software installed, enter

:NETCONTROL VERSION

To start a transport having a LAN network named "LAN1" plus a
loopback network named "LOOP" and a router network named "ROUTER1",
having links "PSI40" and "PSI48" under it, enter

:NETCONTROL START; NET=LAN1
:NETCONTROL START; NET=ROUTER1
:NETCONTROL START; NET=LOOP

To then enable the NS3000/iX Services (DSCOPY, etc.), enter

:NSCONTROL START

To now take down the "PSI40" link on the "ROUTER1" network because
someone wants to use that link for RJE/iX access, (the other
link "PSI48" is still available to the router), enter

:NETCONTROL DELLINK=PSI40; NET=ROUTER1

To check if the PROBE protocol is running on the "LAN1" network, enter

:NETCONTROL STATUS=ALL; NI=LAN1; PROT=PROBE

To bring the PSI link "PSI40" back online after RJE/iX users have
finished with it, enter

:NETCONTROL ADDLINK=PSI40; NET=ROUTER1

To update the "ROUTER1" network with new node mappings added to the
NMCONFIG file without stopping that network, enter

:NETCONTROL UPDATE=MAPPING; NET=ROUTER1

To start TCP message and data tracing for all networks (since TCP
is a general protocol), enter

:NETCONTROL TRACEON=MHD; PROT=TCP

To stop the NS3000/iX Services, enter

:NSCONTROL STOP

To stop all networks, tracing, and the entire transport, enter

:NETCONTROL STOP

ADDITIONAL DISCUSSION

Commands:   NSCONTROL, LINKCONTROL, DTCCNTRL

Manuals : NS3000/iX Operations & Maintenance Reference Manual
(36922-90035) --for :NETCONTROL and tools--
NS3000/iX NMMGR Screens Reference Manual
(36922-61003) --for NMMGR Unguided Config--
HP3000/iX Network Planning and Configuration Guide
(36922-90033) --for NMMGR Guided Config--
Using the Node Management Services (NMS) Utilities
(32022-90009) --for NMMGR Maintenance Mode--
NS3000/iX Error Messages Reference Manual
(36923-90021) --for Errors--


NETCONTROL ADDLINK

     Dynamically adds a configured network link to an active network
interface.

SYNTAX

     NETCONTROL ADDLINK=linkname; {NET=niname       }
{GATE=gatehalfname}

PARAMETERS

linkname           Specifies the name of the link to be dynamically
added to the specified active NI. The linkname
must be a valid NI link name configured in the NMMGR
Link Selection screen and also in the Network
Interface Links screen under the specified "niname"
or "gatehalfname" NI. If already active, an "ALREADY
STARTED" error will occur, or if the linkname is not
valid, a "NOT CONFIGURED" error will occur.

niname Specifies the name of an active network interface
under which the specified linkname is configured.
Enter any valid NI name from the NMMGR Network
Interface Configuration screen which is not a gateway
half. If this NI is not active, a "NOT STARTED"
error will occur.

gatehalfname Specifies the name of an active gateway half network
interface under which the specified linkname is
configured. Enter any valid gatehalf NI name from
the NMMGR Network Interface Configuration screen.
If this NI is not active, a "NOT STARTED" error
will occur.

OPERATION

     This command adds an already configured link to an active network
interface without having to first bring down and then restart the
network interface or the entire transport. This can be a link for
a newly-configured node mapping, a link which was configured to not
start on network initialization, a link being shared with another
subsystem such as RJE/iX or SNA/iX, or a link being restarted after
an earlier failure due to link errors. Note that some link errors
are so serious that an ADDLINK cannot restore use of the link.

The control process will create a new link driver for the specified
link (unless the driver already exists and is shared) and bind it
to the existing network interface and active network interface protocols.

This function is mainly used with router NI types.

EXAMPLE

     To add the linkname "PSI48" to the active NI "ROUTER1", enter

:NETCONTROL ADDLINK=PSI48; NET=ROUTER1


NETCONTROL DELLINK

     Dynamically deletes a configured network link from an active
network interface.

SYNTAX

     NETCONTROL DELLINK=linkname; {NET=niname       }
{GATE=gatehalfname}

PARAMETERS

linkname           Specifies the name of the link to be dynamically
deleted from the specified active NI. The linkname
must be a valid NI link name configured in the NMMGR
Link Selection screen and also in the Network
Interface Links screen under the specified "niname"
or "gatehalfname" NI. If already deleted, a "NOT
STARTED" error will occur, or if the linkname is not
valid, a "NOT CONFIGURED" error will occur.

niname Specifies the name of an active network interface
under which the specified linkname is configured.
Enter any valid NI name from the NMMGR Network
Interface Configuration screen which is not a gateway
half. If this NI is not active, a "NOT STARTED"
error will occur.

gatehalfname Specifies the name of an active gateway half network
interface under which the specified linkname is
configured. Enter any valid gatehalf NI name from
the NMMGR Network Interface Configuration screen.
If this NI is not active, a "NOT STARTED" error
will occur.

OPERATION

     This command deletes a previously configured and started link from
an active network interface without having to bring down the entire
network interface or transport. This command is particularly
useful when making cabling or modem changes, to make a device
unusable for security reasons, or when sharing a device with other
subsystems such as RJE/iX or SNA/iX. Certain types of errors can
also sometimes be cleared by a DELLINK followed by an ADDLINK.

The control process will unbind the network interface protocols and
network interface from the existing link driver, then terminate
that link driver. Depending on the link type, the link driver may
not actually terminate if other users are still bound. The network
interface and its protocols remain active until that NI is stopped
using the NETCONTROL STOP command.

This function is mainly used with router NI types.

EXAMPLE

     To delete the linkname "PSI48" from the active NI "ROUTER1", enter

:NETCONTROL DELLINK=PSI48; NET=ROUTER1


NETCONTROL START

     Initiates the network transport, including the control process,
general protocols, network interfaces, and their protocols. Also
initiates individual network interfaces on an active transport.

SYNTAX

     NETCONTROL START [;{NET=niname       }]
{GATE=gatehalfname}

PARAMETERS

niname             Specifies the name of a configured network interface
to be started. All protocols and links configured to
initially start for that NI will also be started.
Enter any valid NI name from the NMMGR Network
Interface Configuration screen which is not a gateway
half. If neither NET nor GATE are specified, only
the control process and general protocols will start.
Otherwise if this is the first START, those will be
started before the specified NET or GATE. If the
specified entity is already running, an "ALREADY
STARTED" error will occur.

gatehalfname Specifies the name of a configured gateway half
network interface to be started. All protocols and
links configured to initially start for that NI will
also be started. Enter any valid gatehalf NI name
from the NMMGR Network Interface Configuration
screen. If neither NET nor GATE are specified, only
the control process and general protocols will start.
Otherwise if this is the first START, those will be
started before the specified NET or GATE. If the
specified entity is already running, an "ALREADY
STARTED" error will occur.

OPERATION

     This function, if issued when transport is not active, initializes
the control process and general protocols. When NET or GATE is
also used, all configured protocols and associated modules for the
specified network interface will be initialized as well, however
only one such keyword may be specified per command. If you are
starting several network interfaces, several commands will be
required, one per network interface.

Unless you start network interfaces, no internetwork communications
will be possible.

If the general protocols fail to start, a NETCONTROL STOP command
may be required before another start can be attempted.

EXAMPLE

     To start only the "LAN1" network interface, enter this command.  If
the control process and general protocols are not already started,
they will start also

:NETCONTROL START; NET=LAN1

To start loopback on the LOOP network interface, enter this
command. If the control process and general protocols are not
already started, they will start also

:NETCONTROL START; NET=LOOP

To start only the control process and general protocols, enter
enter

:NETCONTROL START


NETCONTROL STATUS

     Displays status and configuration information for the transport
entity specified.

SYNTAX

     NETCONTROL STATUS[=ALL] [;{NI=niname [;PROT=niprot]} ]
{NET=niname }
{GATE=gatehalfname }
{PROT=gprot }

PARAMETERS

ALL                Specifies that any additional status information
should be displayed, if additional data is
available beyond the default.

niname Specifies the name of a configured network interface
to display the status of. Enter any valid NI name
from the NMMGR Network Interface screen which is not
a gateway half. If the specified NI was not
previously configured and started, an "ENTITY NOT
ACTIVE" error will occur. If transport was not
previously started, a "TRANSPORT NOT ACTIVE" warning
will occur.

Specifying "NI=niname" without the ";PROT=" option
displays status for the network interface itself.

gatehalfname Specifies the name of a configured gateway half
network interface to display the status of. Enter
any valid gatehalf NI name from the NMMGR Network
Interface Configuration screen. If the specified
gatehalf NI was not previously configured and
started, an "ENTITY NOT ACTIVE" error will occur.
If transport was not previously started, a "TRANSPORT
NOT ACTIVE" warning will occur.

gprot Specifies the name of one transport general protocol
to display the status of. Valid inputs are TCP, UDP,
PXP, or IPU. If the specified protocol did not start
or is not one of these inputs, an "ENTITY NOT ACTIVE"
error will occur. If transport was not previously
started, a "TRANSPORT NOT ACTIVE" warning will occur.

niprot Specifies the name of one network interface protocol
to display the status of; must be used in conjunction
with the NI=niname parameter. Valid inputs depend on
the NI type, according to the table below. If the
specified protocol did not start, is not configured,
or is not one of these inputs, an "ENTITY NOT ACTIVE"
error will occur. If transport was not previously
started, a "TRANSPORT NOT ACTIVE" warning will occur.

NI Type Valid Network Interface Protocol Names
-------- --------------------------------------
FDDI IP, ARP |
GATEHALF IP, DIAL
LAN IP, PROBE, ARP
LOOP IP
ROUTER IP, DIAL
TOKEN IP, ARP
X.25 IP, X25

OPERATION

     This command displays status and configuration data for the active
transport, using several different output formats depending on
the keywords specified. Some of the formats are specific to the
control process, a network interface, or a specific protocol. Any
entities which are not active cannot have their status displayed.

This command differs from other NETCONTROL commands in that it
produces warnings, not errors, if transport is not active. This
is often used to determine if transport as a whole is running or
not.

NOTE: HP does not recommend combining this function on the same
command line as other functions, in an attempt to determine if
the other function worked.

NOTE: The output format of all NETCONTROL commands is subject to
change without notice. Programs which are developed to
postprocess NETCONTROL output should not depend on the exact
format (spacing, alignment, number of lines, upper or lower
case, or spelling) of any NETCONTROL command output.

EXAMPLE

     To report the status of the ARP protocol on the "LAN1" NI, enter

:NETCONTROL STATUS; NI=LAN1; PROT=ARP

NETWORK INTERFACE PROTOCOL STATUS : TUE, JUN 14, 1994, 11:10 AM
PROTOCOL STARTED : SAT, JUN 11, 1994, 8:25 PM

PROTOCOL NAME : ARP
PROTOCOL ID : $00000508
PROTOCOL FLAGS : $00000000
TRACE MASK : $00000000

PCB ADDR INFO : ENTRY $45342AF8
TRACE ID'S : TRACE $00000000
PORT ID : $FFFFFF10
NETWORK NAME : LAN1

To report the status of the control process, enter

:NETCONTROL STATUS

GENERAL TRANSPORT STATUS : TUE, JUN 14, 1994, 11:10 AM
TRANSPORT STARTED : SAT, JUN 11, 1994, 8:24 PM

FLAGS : $00002640
MAX NETWORK INTERFACES : 32
MAX NODE NAMES : 360
LOG ID : $00000003
TRACE ID : $00070101
CONTROL PROCESS PORT ID : $FFFFFEDE PIN : 60

HOME NETWORK : LAN1
CONFIGURATION FILE : NMCONFIG.PUB.SYS
TRACE MASK : $00000000
NODE NAME : NODE.DOMAIN.ORG

If the control process is not active, you will see a warning

:NETCONTROL STATUS
TRANSPORT NOT ACTIVE. (NETXPORTWARN 0001)


NOTE: The output format of all NETCONTROL commands is subject to
change without notice. Programs which are developed to
postprocess NETCONTROL output should not depend on the exact
format (spacing, alignment, number of lines, upper or lower
case, or spelling) of any NETCONTROL command output.


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

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.

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. 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.

OPERATION

     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 is terminated; all
other network interfaces and protocols will continue to operate.

If the network being stopped is an X.25 network, the DTC is also
informed the network is stopped, causing it to refuse new inbound
connections for that system. Other systems will not be affected.

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.

EXAMPLE

     To stop only the "LAN1" network interface, enter

:NETCONTROL STOP; NET=LAN1

To stop loopback on the LOOP network interface, enter

:NETCONTROL STOP; NET=LOOP

To stop the entire transport including all network interfaces,
enter

:NETCONTROL STOP

NETCONTROL TRACEON and TRACEOFF


 Enables or disables tracing for the specified transport entity.

SYNTAX

     NETCONTROL {TRACEON=type[,options]} [;{NI=niname [;PROT=niprot]} ]
{TRACEOFF } {NET=niname }
{GATE=gatehalfname }
{PROT=gprot }

"options" may be

[DISC][,[filename][,[recsize][,filesize] ]]

PARAMETERS

TRACEON            Enables tracing for the one entity specified by the
NI, PROT, NET, or GATE keywords, or for the control
process if none of those keywords are specified.
The control process will be started if it is not
already running. This function cannot be used to
modify any parameters of tracing which has already
been enabled. If tracing is already enabled for the
specified entity, a "PREVIOUSLY ENABLED" error will
occur.

type (Required). Specifies the type of data to trace
from the specified entity. This field is made up of
one or more of the following key letters,
concatenated, and entered in any order:

M Trace Messages
H Trace Packet Header Data
D Trace Packet Data
S Trace State Transitions
B Trace Buffers or Resources
N Trace Nodal Management Events

Recommended type setting is MHD. There is no default.
Not all transport entities recognize all types; the
following table may be used as a guide, however these
types may change without notice:

Entity Recognized Trace Types
----------------- ------------------
ARP M H D
Control Process M B N
DIAL M H D S N
IP M H D B
IPU M S B
Network Interface M D
PROBE M H D B
PXP M H D S
TCP M D S B
UDP M H D S
X25 M H D S B

options Specifies additional information about where to put
the collected trace data. There are several
parameters. NOTE: a comma MUST precede a parameter
whenever (a)that parameter is included or (b)that
parameter is omitted but but any OTHER parameter
which follows it is included.

DISC (Optional). Trace information will be
written to a disc file, specified by
the filename parameter. DISC is the
default and the only valid input.
NOTE: tracing to tape or internal
memory is not available on MPE/iX.

filename (Optional). The name of the file to
which trace data will be written. The
default is to automatically create the
next highest numbered NMTCnnnn.PUB.SYS
file, where nnnn is a 4-digit number,
for each TRACEON command entered.

If you wish several TRACEON commands to
trace to the same file, you must specify
that filename using this parameter. You
may choose an automatically created file
for this purpose.

recsize (Optional). Logical record size of the
records in the file to which trace data
will be written, in number of 16-bit
words. This is an internal limit for
the tracing facility; the physical
record size is always 128. Valid range
is 5<=recsize<=1024. Default is 128.

filesize (Optional). Maximum number of records
in the trace file. When this limit is
reached, the file "wraps", and tracing
continues. The valid range is
32<=filesize<=32000. Default is 1024.

TRACEOFF Disables tracing for one entity, for which tracing
was previously enabled, and which is specified by the
NI, PROT, NET, or GATE keywords, or the control
process if none of those keywords are specified. The
control process will be started if it is not already
running. If tracing is not enabled for the specified
entity, a "NOT TRACING" error will occur.

NI=niname Specifies the name of a configured network interface
the trace will apply to. Enter any valid NI name
from the NMMGR Network Interface screen which is not
a gateway half. If the specified NI was not
previously configured and started, a "NOT STARTED"
error will occur.

Specifying "NI=niname" without the ";PROT=" option
starts or stops tracing for the network interface
itself. Otherwise, use the "PROT= option also.

NET=niname Specifies the name of a configured network interface
which is not a gatehalf. Enter any valid NI name, as
configured with NMMGR. Using this parameter, the
function applies only to the IP protocol on that NI,
the same as using "NI=niname;PROT=IP". If the
specified NI was not previously configured and
started, a "NOT STARTED" error will occur.

GATE=gatehalfname Specifies the name of a configured gateway half
network interface. Enter any valid gatehalf NI name,
as configured with NMMGR. Using this parameter, the
function applies only to the IP protocol on that NI.
If the specified gatehalf NI was not previously
configured and started, a "NOT STARTED" error will
occur.

PROT=gprot Specifies that a protocol is the pertinent entity for
PROT=niprot each specified function to act on. Enter the name of
the protocol, as follows:

gprot Specifies the name of one transport general
protocol to start or stop tracing on. Valid
inputs are TCP, UDP, PXP, or IPU. If the
specified protocol did not start or is not
one of these inputs, a "NOT ACTIVE" error
will occur.

niprot Specifies the name of one network interface
protocol to start or stop tracing on; must
be used in conjunction with the NI=niname
parameter. Valid inputs depend on the NI
type, according to the table below. If the
specified protocol did not start, is not
configured, or is not one of these inputs,
a "NOT ACTIVE" error will occur.

NI Type Valid Network Interface Protocol Names
-------- --------------------------------------
FDDI IP, ARP
GATEHALF IP, DIAL
LAN IP, PROBE, ARP
LOOP IP
ROUTER IP, DIAL
TOKEN IP, ARP
X.25 IP, X25

OPERATION

     The tracing functions allow you to enable collection of internal
information about what the various transport modules are doing, or
what packets are being sent and received at the transport level.
Using TRACEON you instruct a specific module not only to begin
tracing, but also what kind of data to trace and what file to put
it in. Tracing continues until explicitly stopped via a matching
TRACEOFF command, or until the specified module, or all of
transport, is stopped. If multiple modules had tracing enabled to
capture a problem, stopping transport is the usual way to stop all tracing.

For most problems you will need to enable TCP tracing, and for IP
store-and-forward problems you should enable IP tracing; see the
examples for sample commands. For link-related problems you
should enable link tracing (see the LINKCONTROL command). Other
NS tracing can be enabled under the the guidance of your HP
support representative.

When tracing is enabled successfully, the name of the active trace
file is displayed. You should write this down as it will not be
repeated at TRACEOFF time; otherwise, to determine which trace
file contains the desired data, check trace file creation times by
using :LISTF NMTC####.PUB.SYS,3.

As soon as your problem has been duplicated, you should stop
tracing to avoid having the file "wrap" and overwrite the data.
At completion of tracing, a trace file may be formatted using the
NMDUMP.PUB.SYS utility. Much of the information traced will be
meaningful only to HP support personnel.

EXAMPLE

     To enable TCP tracing, enter

:NETCONTROL TRACEON=MHD; PROT=TCP
TRACE FILE IS NMTC0128.PUB.SYS. (NETXPORT 2000)

To disable TCP tracing, enter

:NETCONTROL TRACEOFF; PROT=TCP

To enable TCP tracing, control process tracing, and IP tracing on
the "LAN1" NI, all to the same file, enter

:NETCONTROL START; NET=LAN1
:NETCONTROL TRACEON=MHDSBN
TRACE FILE IS NMTC0129.PUB.SYS. (NETXPORT 2000)
:NETCONTROL TRACEON=MHD,DISC,NMTC0129.PUB.SYS; PROT=TCP
TRACE FILE IS NMTC0129.PUB.SYS. (NETXPORT 2000)
:NETCONTROL TRACEON=MHD,DISC,NMTC0129.PUB.SYS; NI=LAN1; PROT=IP
TRACE FILE IS NMTC0129.PUB.SYS. (NETXPORT 2000)

To disable all this tracing once enabled, enter

:NETCONTROL TRACEOFF; NI=LAN1; PROT=IP
:NETCONTROL TRACEOFF; PROT=TCP
:NETCONTROL TRACEOFF


NETCONTROL UPDATE

     Dynamically updates selected network transport configuration information.

SYNTAX

     NETCONTROL UPDATE={INTERNET}; {NET=niname       }
{MAPPING } {GATE=gatehalfname}
{NETDIR }
{X25 }
{ALL }

PARAMETERS

INTERNET           Adds to IPU all gateway data currently configured for
the specified network interface or gateway half,
meaning all gateways appearing in the NMMGR Neighbor
Gateways screen (subtree NETXPORT.NI.niname.INTERNET)
and all Reachable Network data configured under each
of those gateways. These screens contain information
describing the gateways for all directly connected
networks and gateway halves, as well as all networks
the gateways can reach. The specified NI must have
been previously started. Valid for all NI types
except Loopback.

MAPPING Adds all router mappings currently configured for the
specified router network interface, to that NI's
mapping table, meaning all mappings appearing in that
NI's NMMGR Point-to-Point Mapping Configuration
screen and the Point-to-Point Reachable Nodes screens
under it. Information will be overlaid based on
matching IP-Device mapping records. This allows
changing routes as well as adding new reachable
nodes. The specified NI must have been previously
started. Valid for router NI types only.

NETDIR Adds all currently configured Network Directory
(NSDIR.NET.SYS) entries whose address types apply to
the specified network interface's type, to the
mapping table for that NI. Valid for LAN, FDDI, and
Token Ring NI types only.

X25 Adds all currently configured Network Directory
(NSDIR.NET.SYS) entries having X.25 or IP address
types, to the specified X.25 network interface's
mapping table and X.25 protocol module. This allows
adding new SVC destinations or adding a new node to
the L.U.G. (Local User Group) table. Valid for X.25
NI types only.

ALL The control process will update all areas which apply
to the specified network interface or gateway half's
type. Areas not supported for that NI type will not
be updated. Updating will occur in this order:
INTERNET, MAPPING, NETDIR, X25.

niname Specifies the name of a configured network interface
to be updated, which has already been started. Enter
any valid NI name from the NMMGR Network Interface
Configuration screen which is not a gateway half. If
the specified NI is not configured and started, a
"NOT STARTED" error will occur.

gatehalfname Specifies the name of a configured gateway half
network interface to be updated, which has already
been started. Enter any valid gatehalf NI name from
the NMMGR Network Interface Configuration screen. If
the specified NI is not configured and started, a
"NOT STARTED" error will occur.

OPERATION

     The update function updates transport with certain configuration
changes already made through NMMGR. In this way, those kinds of
configuration changes can become active without having to first
take down and then restart the network or the entire transport.

The types of changes which can be updated are those concerned with
addresses of reachable nodes and networks ONLY; others, such as
timeout changes, require stopping and restarting transport to take
effect. UPDATE's keywords (NETDIR, INTERNET, etc.) localize which
kind of configuration data will be updated. This command can be
entered at any time after the specified NI has been started.

Not all options are valid for all network interface types.
The following table summarizes the applicability of the various
UPDATE options to each NI type:

NI Type Valid Update Options
-------- --------------------
FDDI INTERNET, NETDIR, ALL
GATEHALF INTERNET, ALL
LAN INTERNET, NETDIR, ALL
LOOP ALL
ROUTER INTERNET, MAPPING, ALL
TOKEN INTERNET, NETDIR, ALL
X.25 INTERNET, X25, ALL

NOTE: Dynamic updating is additive, so obsolete data can accumulate,
possibly resulting in table overflows. If table overflows do
occur which prevent access to the desired nodes, transport must
be stopped and restarted to clear the condition.

EXAMPLE

     To update the "LAN1" network with new node addresses just added to
the Network Directory (NSDIR.NET.SYS), enter

:NETCONTROL UPDATE=NETDIR; NET=LAN1


NETCONTROL VERSION

     Displays the version numbers for the network transport software.

SYNTAX

     NETCONTROL VERSION[=MOD]

PARAMETERS

MOD                Displays a complete list of the version number for
each module of the NS3000/iX Transport software, plus
the overall version level. If not specified, the
default is to only display the overall version.

OPERATION

     This function allows you to check the version numbers of the
network transport modules to ensure they are compatible and up to
date, or simply to confirm which version is installed on your
system. Unlike most NETCONTROL commands, transport does not need
to be started to use this command.

Output from this command is the same as that produced by the
NMMAINT.PUB.SYS utility.

EXAMPLE

     To display the overall transport software version, enter

:NETCONTROL VERSION
NS3000/iX Transport 32098-20033 overall version = B.05.08