User`s guide

System Troubleshooting and Diagnostics
5.5 Using MOP Ethernet Functions to Isolate Failures
Instead of using the physical address, you could use the assistant node’s area
address. When using the area address, system 3 is running the OpenVMS
operating system.
***system 3***
$MCR NCP
NCP>SHOW NODE KLATCH
Node Volatile Summary as of 27-FEB-1992 21:04:11
Executor node = 25.900 (KLATCH)
State = on
Identification = DECnet-VAX V5.4-1, OpenVMS V5.4-2
Active links = 2
NCP>SHOW KNOWN LINES CHARACTERISTICS
Known Line Volatile Characteristics as of 27-FEB-1992 11:20:50
Line = ISA-0
Receive buffers = 6
Controller = normal
Protocol = Ethernet
Service timer = 4000
Hardware address = 08-00-2B-1E-76-9E
Device buffer size = 1498
NCP>SET CIRCUIT ISA-0 STATE OFF
NCP>SET CIRCUIT ISA-0 SERVICE ENABLED
NCP>SET CIRCUIT ISA-0 STATE ON
NCP>EXIT
$
***system 2***
$ MCR NCP
NCP>LOOP CIRCUIT ISA-0 PHYSICAL ADDRESS 08-00-2B-28-18-2C ASSISTANT NODE 25.900
WITH MIXED COUNT 20 LENGTH 200 HELP FULL
NCP>EXIT
$
Note
The kernel’s Ethernet buffer is 1024 bytes deep for the LOOP functions
and will not support the maximum 1500-byte transfer length.
In order to verify that the address is reaching this node, a remote node can
examine the status of the periodic SYSTEM_IDs sent by the KA52/53 Ethernet
server. The SYSTEM_ID is sent every 8–12 minutes using NCP as in the
following example:
5–58 System Troubleshooting and Diagnostics