HPlogo NS 3000/iX Operations & Maintenance Reference Manual: HP 3000 MPE/iX Computer Systems > Chapter 7 Commands

NETCONTROL STATUS

» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

 » Glossary

 » Index

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

STATUS[=ALL]

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

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

NET=niName

Specifies the name of a configured network interface which is not a gatehalf. Enter any valid NI name, as configured with NMMGR.

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

PROT=gProt PROT=niProt

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

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
LANIP, PROBE, ARP
TOKENIP, ARP
FDDIIP, ARP
100VG-AnyLANIP, PROBE, ARP
100Base-TIP, PROBE, ARP
ROUTERIP, DIAL
X.25IP, X25
GATEHALFIP, DIAL
LOOPIP

Discussion

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

Example 1 is a sample of the output that is displayed when the NETCONTROL STATUS command is issued without specifying a network interface or general protocol.

:NETCONTROL STATUS
GENERAL TRANSPORT STATUS : MON, FEB 17, 1992, 8:49 AM
TRANSPORT STARTED : MON, FEB 3, 1992, 2:25 PM

FLAGS : $000014C0
MAX NETWORK INTERFACES : 32
MAX NODE NAMES : 360
LOG ID : $00040003
TRACE ID : $00000000
CONTROL PROCESS PORT ID : $FFFFFF37

HOME NETWORK : LAN1
CONFIGURATION FILE : NMCONFIG.PUB.SYS
TRACE MASK : $00000000
NODE NAME : NODEA.XLNET.ACCTG

Example 2

Example 2 is a sample of the output that is displayed when you issue the NETCONTROL STATUS command specifying the LAN1 network interface via the NI= parameter.

:NETCONTROL STATUS;NI=LAN1

NETWORK INTERFACE REPORT : MON, FEB 17, 1992, 8:52 AM
NETWORK INTERFACE STARTED : MON, FEB 3, 1992, 2:33 PM
FLAGS : $00000006
NIB - PCB LINK INFO : FIRST $452C4290
NIB - NIB LINK INFO : NEXT $00000000
NI PROTOCOLS : CURRENT $00000000 MAXIMUM $00000004
MAPPING TABLE SIZE : $00000400
MAPPING TABLE ID : $C8B80250
OUTBOUND BUFFERS : SIZE $000005EA NUMBER $00000100
NETWORK INTERFACE TYPE : LAN
PORT ID : $FFFFFF21
WRITE BUFFER INFO : POOL $0000000A
STORE/FORWARD BUFFER INFO : POOL $0000000A
TRACE ID'S : TRACE $00000000
NAME : LAN1
NETWORK IP ADDRESS : $0F0D7033 15.13.112.51
NETWORK SUBNET MASK : $FFFFF800 255.255.248.0
TRACE MASK : $00000000

DEVICE INFORMATION :

DEVICE : SYSLINK (# 0)
DEVICE TYPE :
LINK BUFFER SIZE : $000005EA
PROTOCOLS CONNECTED : $00000004
PHONE NUMBER INDEX : $00000000
TRAN PORT INFO : PORT ID $FFFFFF20

Example 3

Example 3 is a sample of the output that is displayed when the NETCONTROL STATUS command is issued and the LAN1 network interface and the PROBE protocol are specified.

:NETCONTROL STATUS;NI=LAN1;PROT=PROBE
NETWORK INTERFACE PROTOCOL STATUS : WED, JAN 19, 1994, 3:31 PM
PROTOCOL STARTED : WED, JAN 19, 1994 4:23 PM

PROTOCOL NAME : PROBE
PROTOCOL ID : $00000503
PROTOCOL FLAGS : $00000000
TRACE MASK : $00000000

PCB LINK INFO : NEXT $4533FA58
TRACE ID'S : TRACE $00000000
PORT ID : $FFFFC77
NETWORK NAME : LAN1

Example 4

Example 4 is a sample of the output that is displayed when the NETCONTROL STATUS command is used specifying the LAN1 network interface via the NET= parameter.

:NETCONTROL STATUS;NET=LAN1
NETWORK STATUS : WED, JAN 19, 1994, 3:31 PM
PROTOCOL STARTED : WED, JAN 19, 1994, 4:23 AM

PROTOCOL NAME : IP
PROTOCOL ID : $00000500
PROTOCOL FLAGS : $00000000
TRACE MASK : $00000000

PCB LINK INFO : NEXT $00000000
TRACE ID'S : TRACE $00000000
PORT ID : $FFFFFC78
NETWORK NAME : LAN1
NETOWRK IP ADDRESS : $0C0E84A6 12.14.132.166
NETWORK SUBNET MASK : $FF000000 255.0.0.0

Example 5

Example 5 is a sample of the output that is displayed when the NETCONTROL STATUS command is issued and the LAN1 network interface and the ARP protocol is specified.

:NETCONTROL STATUS; NI=LAN1; PROT=ARP

NETWORK INTERFACE PROTOCOL STATUS : WED, JAN 26,
1994, 1:55 PM
PROTOCOL STARTED : WED, JAN 26, 1994, 1:55 PM

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

PCB LINK INFO : NEXT $4533FDC0
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 : WED, JAN 26, 1994, 9:12 AM
TRANSPORT STARTED : WED, JAN 26, 1994, 3:57 AM

FLAGS : $000014C0
MAX NETWORK INTERFACES : 32
MAX NODE NAMES : 360
LOG ID : $00000003
TRACE ID : $00010081
CONTROL PROCESS PORT ID : $FFFFFC8E

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

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

:NETCONTROL STOP
: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.
Feedback to webmaster