DECnet-Plus for OpenVMS
Network Management

When a transport connection is being set up, the initial value for an actual sample of round-trip delay is provided by the initial retransmit time attribute of the transport template used to set up the connection.

The value of the weighting factor is given by the delay weight attribute. Basically, delay weight determines how quickly the retransmission timer responds to variations in actual round-trip delay times. A low value of delay weight means that the retransmission timer responds very quickly to each sample of round-trip delay time; a delay weight of 0 means that an estimate will be nearly the same as the last actual sample of round-trip delay. A high value for delay weight reduces the impact of recent variations in network delay; the higher the value, the closer each estimate of round-trip delay will be to the average of all estimates.

The default value of delay weight should be suitable for most networks. However, consider increasing its value if there are wide variations in round-trip delay times on your network.

Appendix D
decnet_migrate Commands

This appendix provides an alphabetical command reference for the following decnet_migrate commands:

collect
convert
convert dcl_file
convert ncp_file
create_ipl_initialization_file
edit
report
show path

D.1 Running decnet_migrate on Your System

Invoke decnet_migrate by entering the following command:

$ run sys$update:decnet_migrate

collect

The collect command collects information from network nodes and places that information in a data file, which is later used by the report command. The collect command collects information from only those nodes that are currently reachable.
You can use this command to determine the current configuration of the network, or to track the configuration changes during transition.
You must have network management privileges that allow you to display information about remote systems.
Each time you use the collect command, a data file is created. To consolidate multiple data files into one data file, use the convert system utility command as follows:
$ convert /merge input_file_1[,input_file_n] output_file   
The input_files argument specifies the files to be consolidated, and the output_file argument specifies the name of the consolidated file. Doing this is most useful when you are consolidating data from different areas.

Syntax

ARGUMENTS

data_file
Specifies the name of the collection data file.
The disk and directory names default to their current values, and the file extension defaults to .DAT.
routing_type=routing_type
Optional. Specifies the routing type of the nodes from which you want to collect information. You can specify one or more of the following:

L1_routers Only level 1 routers

L2_routers Only level 2 routers

routers All routers

all All nodes, including routers and end nodes (the default)

areas=area_id
Optional. Specifies the area or areas from which you want to collect information. You can specify one or more of the following:

node
node_name The area containing the node you specify by node_name. Use either the node's full name or its Phase IV synonym. If you do not want to use the default namespace, specify a namespace name before the node name. If you do not use the default namespace, the tool may not be able to determine the correct full name for every node.

local The area in which your node resides.

all All areas (the default)

The use of all is not recommended for large networks.
If you specify areas, you cannot also specify the nodes parameter. If you specify neither areas nor nodes, the default is areas=all.
nodes=node_list_file
Optional. Names a file with a list of specific nodes from which you want to collect information. Format this file so that:

1. The nodes are listed one node per line.

2. For each node, you can use its full name, its Phase IV synonym, its network entity title (NET), or its Phase IV address.

The disk and directory for the node-list-file parameter default to the same disk and directory you specify for the collection file. The file extension defaults to .INP.
If you specify nodes, you cannot also specify the areas parameter. If you specify neither nodes nor areas, the default is areas=all.
status=status_report_count
Optional. Specifies the number of nodes from which to collect information before displaying a collection status message. The collection status message provides information on the number of areas and nodes from which collect is obtaining information.
By default, collect provides a status message after every node. If you do not want a status report, specify status=none for this parameter.
retry=connection_retry_count
Optional. Specifies the number of times the collect command attempts to connect to a node.
By default, collect makes two connection attempts. If you do not want the collect command to retry connections, specify retry=none for this parameter.
Retrying connections is most useful when nodes might have network resource constraints. When collect retries connections, it waits one minute between connect attempts. If a connection cannot be made within the specified number of attempts, collect assumes that it cannot connect to the node. The collect command retries a connection only if the connection error might be transient in nature, such as resource errors. Other types of errors, such as privilege violations, are not retried.
recover
Optional. Continues an interrupted collection operation. Any parameters for nodes and areas that you specified for the interrupted operation are still in effect.
You must specify the data_file, and you cannot specify any of the other parameters.
Some interrupted collection operations cannot be recovered because the interruption corrupted the output file. In this case, you receive an error message and the recovery does not complete.

Examples

The following command collects information on all nodes in all areas of the network and puts the information in a file called netinfo.dat.
decnet_migrate> collect netinfo.dat   
The following command collects information on all level 2 routers in the area containing the node boston and puts the information into a file called netinfo.dat.
decnet_migrate> collect netinfo.dat routing_type=l2 -   
_decnet_migrate> area=node:boston   
The following command continues a collecting operation that was previously interrupted.
decnet_migrate> collect netinfo.dat recover   
The following command collects information on the nodes listed in a file called decnet_vax_nodes.inp.
decnet_migrate> collect config_1_2_92.dat nodes=decnet_vax_nodes.inp   
The contents of decnet_vax_nodes.inp is as follows:
net:.123.boeham   
netman   
fafnir   
.123.zamphir   
NET:.123.amaze   
49::00-0C:AA-00-04-00-1D-30:00   
49::00-0C:AA-00-04-00-22-30:00   
49::00-0C:AA-00-04-00-0B-30:00   
NET:.123.skgns1   
NET:.123.mipsbx   
NET:.123.mouans   
4.56    

convert command

Converts a specified NCP command to its closest NCL equivalent. The output might consist of one or more NCL commands. See Table 2-1 for a list of the NCP commands that the decnet_migrate convert commands can convert to NCL.

Syntax

decnet_migrate> convert command "ncp-command "

ARGUMENTS

"ncp-command"
Specifies the NCP command you are converting. Specify the command exactly as if it were entered at an NCP> prompt and enclose the command in quotation marks.

Examples

In the following example, the convert command converts the NCP command show executor characteristics to its NCL equivalent:
decnet_migrate> convert command "show executor char"   
   
! * Converting the command:   
!      show executor char   
show node 0 session all char   
show node 0 nsp all char   
show node 0 routing all char   
The following example shows how to convert a command for setting a circuit's cost:
decnet_migrate> convert command "set circuit una-0 cost 20"   
   
! *** Converting the following NCP command to NCL:   
!     set circuit una-0 cost 20   
create node 0 session control   
enable node 0 session control   
create node 0 nsp   
enable node 0 nsp   
create node 0 routing   
enable node 0 routing   
create node 0 routing circuit {{{una-0}}}   
enable node 0 routing circuit {{{una-0}}}   
set node 0 routing circuit {{{una-0}}} l1 cost=20   
The first create and enable commands are included to show how the DECnet Phase V circuit would be created and enabled. Usually, circuits are created and enabled when you bring up a DECnet Phase V node.

convert dcl_file

Converts NCP commands in a DCL command file to their closest NCL equivalents. Both the NCP and NCL commands are written to an output file.
The NCP commands in your DCL command file must appear in one of these formats:
$ ncp ncp-command   
   
   
$ mcr ncp ncp-command   
   
   
$ run device:[directory]ncp   
ncp-command   
.   
.   
.   
ncp-command   
$   
   
   
$ ncp   
ncp-command   
.   
.   
.   
ncp-command   
$   
   
   
$ mcr ncp   
ncp-command   
.   
.   
.   
ncp-command   
$   
Anything else in your DCL command file is copied directly to the output file.

Syntax

decnet_migrate> convert dcl_file input_file [to output_file]

ARGUMENTS

input_file
Specifies the name of the DCL command file you are converting. The disk and directory names default to their current values. If you do not give a file extension, it defaults to .COM.
output_file
Optional. Specifies the name of the command file to contain the converted commands. If you do not specify an output file, the disk, directory name, file name, and file extension all default to those specified for input_file.

Examples

The following command converts the NCP commands in ncpsetup.com to their nearest NCL equivalents and puts the results in a file called nclsetup.com. See the convert command description for examples of how the converted commands appear in the output file.
decnet_migrate> convert dcl_file ncpsetup.com to nclsetup.com   
The following command converts the NCP commands in netstart.com to their nearest NCL equivalents and puts the results in a file with the same name:
decnet_migrate> convert dcl_file netstart.com    

convert ncp_file

Converts NCP commands in an NCP command file to their nearest NCL equivalents. Each NCP command is converted to an NCL command and both the NCP and NCL commands are written to an output file. The NCP commands are included as comments.
The commands in your NCP command file must appear exactly as they would be entered at the NCP> prompt.

Syntax

decnet_migrate> convert ncp_file input_file [to output_file]

ARGUMENTS

input_file
Specifies the name of the command file you are converting. The disk and directory names default to their current values. The file extension defaults to .COM.
output_file
Optional. Specifies the name of the command file to contain the converted commands. The disk, directory name, file name, and file extension all default to those of input_file.

Examples

The following command converts the NCP commands in the file ncpsetup.com to their nearest NCL equivalents and puts the results in a new file called nclsetup.com. See the convert command description for examples of how the converted commands appear in the output file.
decnet_migrate> convert ncp_file ncpsetup.com to nclsetup   
The following command converts the NCP commands in netstart.com to their nearest NCL equivalents and puts the results in a new file with the same name:
decnet_migrate> convert ncp_file netstart    

create ipl_initialization_file

Creates a command file that the manager of a DECnet Phase V router product can use to create interphase link entries in the DECnet Phase V router's reachable address table. Interphase links enable a DECnet Phase V router running the DECnet Phase V link state protocol at level 2 to communicate with adjacent routers running the Phase IV routing vector protocol at level 2.
Whenever the level 2 network configuration changes, use this command to update the reachable address table on every DECnet Phase V level 2 router that has interphase links.
When you issue create ipl_initialization_file, the target DECnet Phase V routing node must be accessible and have a communication path to all areas in the level 2 link-state network. Additionally, the adjacent level 2 routers running the Phase IV routing vector protocol must have communication paths to all areas in their respective level 2 routing-vector networks.
The create ipl_initialization_file command creates three files:

A DCL command file (named output_file) that contains a description of all the routing information gathered when you ran the create ipl_initialization_file command. When you run this command file, you are asked if you want to create or delete interphase link entries. Depending on your answer, the command file executes one of the other two files.
An NCL command file that creates interphase link entries in the reachable address table on the target routing node. This file is named output_file_cre.
An NCL command file that deletes interphase link entries from the reachable address table on the target routing node. This file is named output_file_del.

The following is one method for using the resulting NCL command file to set up interphase links on, for example, a DECnet Phase V router product:

Run the DECnet-Plus router configuration program to create the NCL script for the router's configuration.
Run the create ipl_initialization_file to create the NCL script for setting up interphase links.
Append the second NCL file to the first.
Compile the resulting NCL file into a CMIP file for loading into the router at reboot.

Before running the command file, you can edit output_file_cre to modify which interphase links are created. If you do this, you should make equivalent changes in output_file_del.

Syntax

decnet_migrate> create ipl_initialization_file output_file for node_name

ARGUMENTS

output_file
Specifies the name of the command file you are creating.
The disk and directory names default to their current values; the file extension defaults to .COM.
node_name
Specifies the full name (including any directories) or the Phase IV synonym of the level 2 routing node on which the interphase link entries are to be created.

Example

In the following example, the create ipl_initialization_file command creates files called router_ini.com, router_ini.com_cre, and router_ini.com_del for the area09 router.
decnet_migrate> create ipl_init router_ini for area09    

edit

Edits a command file containing NCL commands, using the Language-Sensitive Editor (LSE) with an NCL template. The LSE layered product must be installed and licensed on your system. For more information about LSE, see the Guide to Language-Sensitive Editor.
You automatically set up the language-sensitive editing features by specifying .COM or .NCL as the file extension of the file your are editing. If you do not specify one of these file extensions, you can use the LSE command set language ncl to set up the language-sensitive editing features.
Syntax support is included for verbs, entities, attributes, arguments, and prepositional clauses. Menu support is included for frequently used verb, entity, attribute, argument, and preposition keywords. This support is limited to the keywords used with the DECnet Phase V NODE global entity.
Some semantic support is provided in that the keywords listed in a menu depend on the previous keywords selected. If you manually enter a keyword instead of selecting from a menu, the semantic capability is lost.
The initial placeholder used to start expanding a command is {NCL_SCRIPT}.

Syntax

decnet_migrate> edit ncl-command-file

ARGUMENTS

ncl-command-file
Specifies the name of the NCL command file to edit. The disk and directory names default to their current values; the file extension defaults to .NCL.

Example

In the following example, the edit command invokes LSE to edit the NCL command file nclcommands.ncl.
decnet_migrate> edit nclcommands.ncl   

report

Reports information that was collected with the collect command.
To generate one report from multiple collect data files, combine the data files into one file and run report on that one file. You can use the convert system utility command as follows to merge multiple data files:
$ convert /merge input_file_1[,input_file_n] output_file   
where the input_files are the files to be combined, and the output_file is the name of the resulting data file. Doing this is most useful when you are consolidating data from different areas.

Syntax

report report_file data=data_file [types=node_types | routing_type=routing_type | areas=area_id | information=info_types | format=format_type]

For OpenVMS systems, data=data_file is optional.

ARGUMENTS

report_file
Specifies the name of the output file to contain the network configuration report.
The disk and directory default to their current values. If you do not give a file extension, it defaults to .LIS.
data=data_file
Specifies the name of the file that contains the collected network configuration data, as created by the collect command.
The disk, directory, and file names default to the values specified for report_file. The file extension defaults to .DAT.
types=node_types
Optional. Specifies the types of nodes to be contained in report_file. You can specify one or more of the following:

phase_v Reports DECnet Phase V nodes

phase_iv Reports Phase IV nodes

phase_iii Reports Phase III nodes

all Reports all node types (the default)

You can abbreviate (by typing v, iv, or iii) to indicate your choice.
You can specify more than one node_type by placing the types in parentheses and separating them with commas.
routing_type=routing_type
Optional. Specifies the routing type of the nodes to be contained in report_file. You can specify one or more of the following:

L1_routers Only level 1 routers

L2_routers Only level 2 routers

routers All routers

all All nodes, including routers and end nodes (the default)

If you specify a routing type for which the collect command collected no information, the report contains a "no information" error message.
areas=area_id
Optional. Specifies the area or areas to be contained in report_file. You can specify one or more of the following:

node
node_name The area containing the node you specify by node_name. Use either the node's full name or its Phase IV synonym. If you do not want to use the default namespace, specify a namespace name before the node name.

local The area in which your node resides

all All areas (the default)

information=info_types
Optional. Specifies the information to report for each node. You can specify one or more of the following:

basic Reports the name, address, phase, routing type, and node identification string for each node. The report command always reports this information whether or not you specify basic (the default).

adjacencies Reports adjacent nodes for each node.

applications Called objects in Phase IV terminology. Reports defined target network applications for each node.

circuits Reports circuit IDs and circuit costs for each node.

routing Reports maximum hops, maximum cost, and network buffer size.

areas Reports areas that are known to the level 2 routers. This information is reported once for the network as a whole and not for each node.

all Reports information from all info_types.

You can specify more than one info_types by placing the info_types in parentheses and separating them with commas.
This parameter defaults to basic.
format=format_type
Optional. Specifies the format for the report. You can specify either of two formats:

full Formats the data using multiple lines for each node (the default).

brief Formats the data using one line for each node, putting the reported information in columns.

The full format provides the most information, whereas the brief format is useful for quick searches and sorting. If you specify brief, only basic information can be reported; you cannot use the brief format if you have specified, for example, routing.

Examples

The following command reports, in a file called netinfo.lis, all information contained in the collect data file netinfo.dat:
decnet_migrate> report netinfo.lis   
The following command reports information from the collect data file netinfo_1_19_92.dat; the resulting report file is named netinfo.txt. The report covers all level 2 routers. The format and information parameters default to full and basic.
decnet_migrate> report netinfo.txt data=netinfo_1_19_92.dat -   
_decnet_migrate> routing_type=l2_routers   
The following command uses the brief format to report only basic information gathered with the collect command. The report has information about two nodes, a DECnet Phase V intermediate system and a Phase IV end node.
decnet_migrate> report netinfo.lis format=brief data=netinfo.dat   
decnet_migrate> exit   
   
$ type netinfo.lis   
   
MCNS:.Nodes.Crumb   49::00-0C:AA-00-04-00-05-30:00 12.0005 Ph5 L2 ""   
BREAD               49::00-0C:AA-00-04-00-0A-30:00 12.0010 Ph4 NR "VMS 5.4"   
The following example creates a report file node_info.lis from information previously collected from the collect data file netinfo_1_19_92.dat. The report provides selected information on all nodes in all areas that were specified in the collect command.
decnet_migrate> report node_info.lis data=netinfo_1_19_92.dat -   
_decnet_migrate> format=full info=(adjacencies,circuits,routing)   
The following example shows a typical default report:
Network Configuration Report - Generated 8-AUG-1995 11:14:46.85   
   
Collection Data File: $DISK1:[NET_MANAGER]NETINFO.DAT;1   
   
   
Parameters Applied:   
   
COLLECTION   
Nodes       = ALL   
Areas       = LOCAL (49::00-0C)   
   
REPORT   
Information = BASIC   
Nodes       = ALL (Phase III) (Phase IV) (Phase V)   
Areas       = ALL   
   
===================================================   
Node information as of 8-AUG-1995 11:14:09.72   
   
Node MEK_NS:.zzz.phase5   
   
 Phase:                V   
 Description:             
 Type:                 Level 2 Router   
   
Routing   
 Address:              41:45418715:00-41:08-00-2B-0F-31-8D:20   
 Address:              49::00-0C:AA-00-04-00-05-30:20  (12.5)   
   
===================================================   
Node information as of 8-AUG-1995 11:14:23.29   
   
Node COOCOO   
 Phase:                IV   
 Description:          DECnet-VAX V5.5,  VMS V5.5             
   
Routing   
 Address:              49::00-0C:AA-00-04-00-0A-30:20  (12.10)   
 Type:                 Non-Routing   
   
===================================================    

show path

The show path command displays the possible paths that node-to-node communication might take through the network. This information helps determine the effect of the transition from DECnet Phase IV to DECnet Phase V on the network's communication paths.

Previous | Next | Contents | [Home] | [Comments] | [Ordering info] | [Help]
  PROFILE_VMS_021.HTML
  OSSG Documentation
   2-DEC-1996 12:35:20.69
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.

Legal

L1_routers	Only level 1 routers
L2_routers	Only level 2 routers
routers	All routers
all	All nodes, including routers and end nodes (the default)

node node_name	The area containing the node you specify by node_name. Use either the node's full name or its Phase IV synonym. If you do not want to use the default namespace, specify a namespace name before the node name. If you do not use the default namespace, the tool may not be able to determine the correct full name for every node.
local	The area in which your node resides.
all	All areas (the default)

1.	The nodes are listed one node per line.
2.	For each node, you can use its full name, its Phase IV synonym, its network entity title (NET), or its Phase IV address.

phase_v	Reports DECnet Phase V nodes
phase_iv	Reports Phase IV nodes
phase_iii	Reports Phase III nodes
all	Reports all node types (the default)

basic	Reports the name, address, phase, routing type, and node identification string for each node. The report command always reports this information whether or not you specify basic (the default).
adjacencies	Reports adjacent nodes for each node.
applications	Called objects in Phase IV terminology. Reports defined target network applications for each node.
circuits	Reports circuit IDs and circuit costs for each node.
routing	Reports maximum hops, maximum cost, and network buffer size.
areas	Reports areas that are known to the level 2 routers. This information is reported once for the network as a whole and not for each node.
all	Reports information from all info_types.

full	Formats the data using multiple lines for each node (the default).
brief	Formats the data using one line for each node, putting the reported information in columns.

DECnet-Plus for OpenVMSNetwork Management

Appendix Ddecnet_migrate Commands

D.1 Running decnet_migrate on Your System

collect

Syntax

ARGUMENTS

data_file

routing_type=routing_type

areas=area_id

nodes=node_list_file

status=status_report_count

retry=connection_retry_count

recover

Examples

convert command

Syntax

ARGUMENTS

"ncp-command"

Examples

convert dcl_file

Syntax

ARGUMENTS

input_file

output_file

Examples

convert ncp_file

Syntax

ARGUMENTS

input_file

output_file

Examples

create ipl_initialization_file

Syntax

ARGUMENTS

output_file

node_name

Example

edit

Syntax

ARGUMENTS

ncl-command-file

Example

report

Syntax

ARGUMENTS

report_file

data=data_file

types=node_types

routing_type=routing_type

areas=area_id

information=info_types

format=format_type

Examples

show path

DECnet-Plus for OpenVMS
Network Management

Appendix D
decnet_migrate Commands