Information Technology Reference
In-Depth Information
Configuring a DECnet Node to Log DECnet Events
In addition to the diagnostic tools available on your router, DECnet environments provide a wealth of
diagnostic information. DECnet nodes can use the DECnet Event Logging Facility (EVL) to track
DECnet events. EVL allows you to monitor significant network events, such as lost packets and circuit
failures.
The following steps outline the basic tasks required to enable event logging on a VMS system:
Determine whether the OPCOM process is running:
Step 1
$
show system
If OPCOM does not appear in the list of running processes, enter the following command to start it:
Step 2
$
@sys$system:STARTUP.com OPCOM
Use the NCP to enable event logging:
Step 3
$
MCR NCP
NCP> SET logging MONITOR KNOWN Events
NCP> DEFINE logging MONITOR KNOWN Events
NCP> SET logging MONITOR STATE ON
NCP> DEFINE logging MONITOR STATE ON
Exit NCP:
Step 4
NCP>
Exit
To monitor network events from a console terminal, enter the following command at the VMS system
prompt:
Step 5
$
REPLY/ENABLE = NETWORK
(This command is equivalent to the
terminal monitor privileged exec
command.)
DECnet: Connections to DEC Hosts Fail over Router (Router Problem)
Symptom:
DECnet nodes cannot communicate when attempting to make connections over routers.
This section focuses on problems in the router. For end node-related problems and
solutions, see the section “DECnet: Connections to DEC Hosts Fail over Router (End Node
Problem)” earlier in this chapter.
Note
