Updated: 24 May 2001

DECnet-Plus for OpenVMS
Network Management

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

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

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

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

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

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)

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

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.

Using information obtained from the starting node and from the routers in the path, show path dynamically determines what nodes might be traversed when a packet is sent from a source node to a destination node. The command then displays the identified list or lists of nodes, as more than one possible path might be displayed.

All the nodes in the path must be able to respond to either NICE or DNA CMIP network management requests.

You must have network management privileges that allow you to display information about remote systems.

Syntax

show path {from=start_node | to=terminating_node} [format=format_type | output_file=file_name]

Arguments

from=start_node

Specifies the starting node for when the command determines paths. As start_node, you can specify one of the following:

1.	The name of the node. You can specify either the node's full DECdns name or its Phase IV synonym name, for example: .usa.boston boston
2.	One of the node's network entity titles (NETs), entered in the format: afi:idi:predsp-locarea:node-id:sel. Example: 43:15084745192:00-0C:aa-00-04-00-50-30:00
3.	One of the node's network areas. The first node found in the area becomes the starting node. Enter the area in the format: afi:idi:predsp-locarea. Example: 43:15084745192:00-0C
4.	The node's Phase IV network address, entered in the format: area.node-id. Example: 12.102
5.	The node's Phase IV network area. The first node that the command finds in the area becomes the starting node. Use this format: area.*. Example: 12.*

If you do not specify from, show path uses the local node as the starting node. You must specify at least from or to; you can specify both.

to=terminating_node

Specifies the terminating node for when the command determines paths. As the terminating node, you can specify one of the following:

1.	The name of the node. You can specify either the node's full DECdns name or its Phase IV synonym name, for example: .usa.boston boston
2.	One of the node's network entity titles (NETs), entered in the format: afi:idi:predsp-locarea:node-id:sel. Example: 43:15084745192:00-0C:aa-00-04-00-50-30:00
3.	One of the node's network areas. The first node found in the area becomes the starting node. Enter the area in the format: afi:idi:predsp-locarea. Example: 43:15084745192:00-0C
4.	The node's Phase IV network address, entered in the format: area.node-id. Example: 12.102
5.	The node's Phase IV network area. The first node that the command finds in the area becomes the starting node. Use this format: area.*. Example: 12.*

If you do not specify to, the command uses the local node as the terminating node. You must specify at least from or to; you can specify both.

format=format_type

Optional. Specifies the format of the output. You can specify one of these:

brief	Displays only the names of the nodes in the path (the default).
full	Displays the node type and the NETs for each node in the path.

output_file=file_name

Optional. Specifies a file in which to output the path information, in place of a terminal display.

Examples

1. The following command produces a display of possible paths for packets, starting with node .USA.Boston and ending with node .FR.Cannes. These two nodes are specified by node name.

   decnet_migrate> show path from .USA.Boston to .FR.Cannes

2. The following command produces a display of possible paths for packets, starting with a specified node and, by default, ending with the local node. The start node is specified by using one of the node's network entity titles (NETs).

   decnet_migrate> show path from - _decnet_migrate> 43:15084745192:00-0C:AA-00-04-00-50-30:00

3. The following command produces a display of possible paths for packets, starting with the local node and ending with the node specified by using one of the node's network areas. The first node found in the area becomes the terminating node.

   decnet_migrate> show path to 43:15084745192:00-0C

4. The following command produces a display of possible paths for packets, starting with the local node and ending with the node specified by using the node's Phase IV area. The first node found in the area becomes the terminating node.

   decnet_migrate> show path to 63.*

5. The following command produces a display of possible paths for packets, starting with node metrix and ending with node book. The format of the display (shown) is full.

   % /usr/bin/decnet_migrate decnet_migrate> show path from metrix to book format full Obtaining local Phase IV address prefix Communication opened (node NET:.skg.book) Communication opened (node NET:.skg.metrix) Communication opened (node NET:.skg.phz5g8) Communication opened (node NET:.skg.phz4g8) Communication opened (node NET:.skg.lktnr7) Communication opened (node NET:.skg.lktnr4) Path Number 1 (path to last node is complete) First node: NET:.skg.metrix (METRIX) DECnet-Plus end node 49::00-0C:AA-00-04-00-50-30:00 (12.80) 41:45418715:00-41:08-00-2B-16-A8-72:00 Next node: NET:.skg.phz5g8 DECnet-Plus router (level 2) 41:45418715:00-41:08-00-2B-0F-31-8D:00 49::00-0C:AA-00-04-00-05-30:00 (12.5) Next node: NET:.skg.phz4g8 (PHZ4G8) DECnet Phase IV router (level 2) 49::00-04:AA-00-04-00-04-10:00 (4.4) Last node: NET:.skg.book (BOOK) DECnet Phase IV end node 49::00-04:AA-00-04-00-3A-11:00 (4.314) Path Number 2 (path to last node is complete) First node: NET:.skg.metrix (METRIX) DECnet-Plus end node 49::00-0C:AA-00-04-00-50-30:00 (12.80) 41:45418715:00-41:08-00-2B-16-A8-72:00 Next node: NET:.skg.lktnr7 DECnet-Plus router (level 1) 41:45418715:00-41:08-00-2B-06-9E-D7:00 49::00-0C:AA-00-04-00-62-30:00 (12.98) Next node: NET:.skg.lktnr4 DECnet-Plus router (level 2) 49::00-0C:AA-00-04-00-60-30:00 (12.96) 41:45418715:00-41:08-00-2B-0D-CA-F4:00 Next node: NET:.skg.phz5g8 DECnet-Plus router (level 2) 41:45418715:00-41:08-00-2B-0F-31-8D:00 49::00-0C:AA-00-04-00-05-30:00 (12.5) Next node: NET:.skg.phz4g8 (PHZ4G8) DECnet Phase IV router (level 2) 49::00-04:AA-00-04-00-04-10:00 (4.4) Last node: NET:.skg.book (BOOK) DECnet Phase IV end node 49::00-04:AA-00-04-00-3A-11:00 (4.314) Path Number 3 (path to last node is complete) First node: NET:.skg.metrix (METRIX) DECnet-Plus end node 49::00-0C:AA-00-04-00-50-30:00 (12.80) 41:45418715:00-41:08-00-2B-16-A8-72:00 Next node: NET:.skg.lktnr4 DECnet-Plus router (level 2) 49::00-0C:AA-00-04-00-60-30:00 (12.96) 41:45418715:00-41:08-00-2B-0D-CA-F4:00 Next node: NET:.skg.phz5g8 DECnet-Plus router (level 2) 41:45418715:00-41:08-00-2B-0F-31-8D:00 49::00-0C:AA-00-04-00-05-30:00 (12.5) Next node: NET:.skg.phz4g8 (PHZ4G8) DECnet Phase IV router (level 2) 49::00-04:AA-00-04-00-04-10:00 (4.4) Last node: NET:.skg.book (BOOK) DECnet Phase IV end node 49::00-04:AA-00-04-00-3A-11:00 (4.314) decnet_migrate> exit %

6. The following command produces lists of possible paths for packets, starting with node metrix and ending with node book. The format is brief by default. Instead of a terminal display, the lists are placed in a text file called pages_path.txt.

   decnet_migrate> show path from metrix to book output=pages_path.txt Communication opened (node NET:.skg.book) Communication opened (node NET:.skg.metrix) Communication opened (node NET:.skg.phz5g8) Communication opened (node NET:.skg.phz4g8) Communication opened (node NET:.skg.lktnr7) Communication opened (node NET:.skg.lktnr4) decnet_migrate> exit $ type pages_path.txt Path Number 1 (path to last node is complete) First node: NET:.skg.metrix (METRIX) Next node: NET:.skg.phz5g8 Next node: NET:.skg.phz4g8 (PHZ4G8) Last node: NET:.skg.book (BOOK) Path Number 2 (path to last node is complete) First node: NET:.skg.metrix (METRIX) Next node: NET:.skg.lktnr7 Next node: NET:.skg.lktnr4 Next node: NET:.skg.phz5g8 Next node: NET:.skg.phz4g8 (PHZ4G8) Last node: NET:.skg.book (BOOK) Path Number 3 (path to last node is complete) First node: NET:.skg.metrix (METRIX) Next node: NET:.skg.lktnr4 Next node: NET:.skg.phz5g8 Next node: NET:.skg.phz4g8 (PHZ4G8) Last node: NET:.skg.book (BOOK)

Copyright © Compaq Computer Corporation 1998. All rights reserved. Legal

6499PRO_027.HTML