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 |
|
- START
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.
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.
- NET=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.
- GATE=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. The niName discussion for NET
and GATE applies to gatehalf name
also.
Discussion |
|
In order for internetwork communications to be possible, you
must activate at least one network interface using the NET
keyword.
When this command is entered with an X.25 NI name, the system
accesses the DTC/X.25 Network Access subsystem to verify that the
X.25 line is started. If the line is not started, the command fails.
If the X.25 line is started, the command is successfully completed
if everything is correct. This enables the X.25 address that is
associated with this system in the DTC/X.25 Network Access, and
connections can be generated or accepted from this system.
Example 1 |
|
In Example 1, the node has one LAN link configured (LAN1)
plus loopback (LOOP). Starting the network requires issuing a NETCONTROL
START
for each configured network interface (NET=niName).
Once both network interfaces (and related entities) of the network
transport have been successfully initiated, as indicated by the
lack of error messages, any other related subsystems installed on
the node can be initiated. This node, as is typically the case,
has NS 3000/iX Services installed.
:NETCONTROL START;NET=LAN1 :NETCONTROL START;NET=LOOP :NSCONTROL START
Refer to the NSCONTROL
command pages in this section for more information.
Be aware that to successfully initialize a node, the commands
must be issued in the order shown: first all required NETCONTROL
commands, then any NSCONTROL
commands.
This first example provides an overview of initializing a
node, showing where NETCONTROL
fits into the process. The next five examples examine the START
function and how it affects the entities defined for initialization
(Figure 7-1 “The NETCONTROL Entities”). As will be shown
in the examples, the keywords included with the START
function and the entities affected determine which events occur
at initialization. To understand this relationship, it is helpful
to see the events that occur when the network transport is initialized.
Example 2 |
|
Example 2 shows the events associated with the START
function at initiation. As indicated in the status report, the general
transport is not active. Therefore, the first events of initiation
are to initialize the control process (CP) and the general protocols.
Compare the displayed events to the defined entities of Figure 7-1 “The NETCONTROL Entities”. The events displayed
in this example show creation of the general protocols. The START
function always creates the control process and the general protocols,
if they do not already exist, before acting on any of the other
entities.
:NETCONTROL STATUS
TRANSPORT NOT ACTIVE. (NETXPORTWARN 0001)
ENCOUNTERED ONE OR MORE WARNINGS WHILE PROCESSING COMMAND. (CIWARN 4437)
:NETCONTROL START
** NETXPORT Control Process; Transport start
- Loc: 50; Class: 4; Parm= $0000002C; PIN: 44
** NETXPORT TCP; General protocol start
- Loc: 18501; Class: 4; Parm= $00865910; PortID: $FFFFDFF1
** NETXPORT UDP; General protocol start
- Loc: 19; Class: 4; Parm= $00000000; PortID: $FFFFDFF2
** NETXPORT IP Update; General protocol start
- Loc: 3; Class: 4; Parm= $00000000; PortID: $FFFFDFF4
** NETXPORT Net Timers; Starting
- Loc: 4440; Class: 4; Parm= $00000000; PortID: $FFFFDFED |
The initiation events shown in this example are always executed
for the first NETCONTROL START
command, whether or not a network interface is specified. However,
once the general transport is initialized, subsequent NETCONTROL START
commands do not change the modules of the general transport.
Example 3 |
|
Example 3 displays the error message that will appear if you
issue a NETCONTROL START command
when the control process is already initialized.
:NETCONTROL START
ALREADY STARTED. (NETXPORTERR 4045)
ENCOUNTERED ONE OR MORE ERRORS WHILE PROCESSING COMMAND. (CIERR 4436) |
Example 4 |
|
In Example 4, the LAN NI, configured as LAN1, is started on
the first NETCONTROL START
command. Notice that the initiation events to initialize the general
protocols are immediately followed by the start of the LAN NI with
its associated protocols: IP, probe, and ARP. Compare the displayed
events to the defined entities of Figure 7-1 “The NETCONTROL Entities”. The events displayed show creation of
the control process, the general protocols, and the LAN NI entities.
:NETCONTROL START;NET=LAN1
** NETXPORT Control Process; Transport start
- Loc: 50; Class: 4; Parm= $0000002C; PIN: 44
** NETXPORT TCP; General protocol start
- Loc: 18501; Class: 4; Parm= $00865910; PortID: $FFFFDFF1
** NETXPORT UDP; General protocol start
- Loc: 19; Class: 4; Parm= $00000000; PortID: $FFFFDFF2
** NETXPORT IP Update; General protocol start
- Loc: 3; Class: 4; Parm= $00000000; PortID: $FFFFDFF4
** NETXPORT Net Timers; Starting
- Loc: 4440; Class: 4; Parm= $00000000; PortID: $FFFFDFED
** NETXPORT Map Tbl; Mapping Table Created
- Loc: 1; Class: 4; Parm= $95C80250; PortID: $95C80250
** NETXPORT LAN NI; Network interface start
- Loc: 28; Class: 4; Parm= $95CC8000; PortID: $FFFFFE88
** NETXPORT IP; Protocol start
- Loc: 102; Class: 4; Parm= $D4FD8000; PortID: $FFFFFE84
** NETXPORT Probe; Protocol start
- Loc: 35; Class: 4; Parm= $00000000; PortID: $FFFFDFF3
** NETXPORT ARP; Protocol start
- Loc: 3; Class: 4; Parm= $00000000; PortID: $FFFFDFF5 |
Example 5 |
|
Example 5 shows the initiation events for the loopback network
interface. For this example, the loopback NI is configured as LOOP
and the general protocols are already active.
:NETCONTROL START;NET=LOOP
** NETXPORT Map Tbl; Mapping Table Created
- Loc: 1; Class: 4; Parm= $D5208250; Pin: 0
** NETXPORT Loopback NI; Network interface start
- Loc: 28; Class: 4; Parm= $96038000; PortID: $FFFFFE8A
** NETXPORT IP; Protocol start
- Loc: 102; Class: 4; Parm= $D5218000; PortID: $FFFFFE89 |
Notice that only the Loopback NI and its associated protocol,
Internet Protocol (IP), are started; there was a previously issued
NETCONTROL START command. Compare
the displayed events to the defined entities of Figure 7-1 “The NETCONTROL Entities”. The events displayed show creation of
the Loopback NI entity.
Example 6 |
|
Starting the LAN NI, configured as LAN1, when the general
protocols are already active, gives you the following:
:NETCONTROL START;NET=LAN1
** NETXPORT Map Tbl; Mapping Table Created
- Loc: 1; Class: 4; Parm= $D5C80250; Pin: 0
** NETXPORT LAN NI; Network interface start
- Loc: 28; Class: 4; Parm= $96430000; PortID: $FFFFFE81
** NETXPORT IP; Protocol start
- Loc: 102; Class: 4; Parm= $D5CD0000; PortID: $FFFFFE88
** NETXPORT Probe; Protocol start
- Loc: 35; Class: 4; Parm= $00000000; PortID: $FFFFDFF3
** NETXPORT ARP; Protocol start
- Loc: 3; Class: 4; Parm= $00000000; PortID: $FFFFDFF5 |
Notice that only the LAN NI and its associated protocols are
started. Compare the displayed events to the defined entities of
Figure 7-1 “The NETCONTROL Entities”. The events displayed
show creation of the LAN NI entity.
