 |
» |
|
|
|
Dynamically updates selected network transport parameters
and configuration information. Syntax | |
{INTERNET}
{MAPPING }
NETCONTROL UPDATE= {NETDIR }; {NET=niName }
{X25 } {GATE=gatehalfName}
{ALL } |
Parameters | |
{INTERNET}
{MAPPING } Specifies which configuration areas will be dynamically
UPDATE = {NETDIR } updated. The areas possible depends on the network type.
{X25 }
{ALL } |
- 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. 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. 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, 100VG-AnyLAN,
100Base-T and Token Ring NI types only. - X25
Adds all currently configured Network Directory
(NSDIR.NET.SYS) entries having
X.25 or IP address types and matching entries in the NMMGR X.25
SVC Address Key Paths screen, 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.
- NET=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. - GATE=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.
Discussion | |
The update function updates transport with certain configuration
changes already made through NMMGR. In this way, those kinds of
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.
Table 7-2 “NETCONTROL Update ” summarizes the applicability
of the various UPDATE options to each NI type. Table 7-2 NETCONTROL Update NI Type | Valid Update Options |
|---|
LAN | INTERNET, NETDIR, ALL | TOKEN | INTERNET, NETDIR, ALL | FDDI | INTERNET, NETDIR, ALL | | 100VG-AnyLAN | INTERNET, NETDIR, ALL | | 100Base-T | INTERNET, NETDIR, ALL | ROUTER | INTERNET, MAPPING, ALL | X.25 | INTERNET, X25, ALL | | GATEHALF | INTERNET, ALL | LOOP | 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 |
