HP OpenVMS Systems Documentation

To record events from a Phase IV system on a DECnet-Plus system, you need to define the relay entity and its logging subentities. The relay entity receives the events from a Phase IV node, encapsulates them, and posts them in the DECnet-Plus system event dispatcher.

To see the relayed events, you must also have created and enabled the event dispatcher entity, an outbound stream, and a sink on the DECnet-Plus system.

12.7.1 Creating and Enabling the Relay Entity

The following example creates and enables the relay entity. (See Figure 12-4 for the relationship of the relay subentity in the event dispatcher entity hierarchy.)

ncl> create event dispatcher relay
ncl> enable event dispatcher relay

To set the relay entity's state status to OFF, use the disable command:

ncl> disable event dispatcher relay

To delete the relay entity, use the delete command:

ncl> delete event dispatcher relay

logging entity types can be console, file, or monitor logging. They are created and enabled by the relay. You can also explicitly enable them by using the enable command, as the following example shows:

ncl> enable event dispatcher relay logging console

logging entities are disabled and deleted by the parent relay entity. You can also explicitly disable them by using the disable command. See the following example:

ncl> disable event dispatcher relay logging console

Use Phase IV NCP commands (from the Phase IV local system, or from a DECnet Phase V system) to direct the event messages from a Phase IV source node to a DECnet Phase V sink node. For example:

ncp> set logging console known events sink node decnet-osi-system

For information about using NCP event logging, refer to your Phase IV documentation.

12.7.5 Sample Relayed Phase IV Event

The following example shows a typical event relayed from a Phase IV system.

Event: Event Relayed from: Node ADMIN:.NetMgr Event Dispatcher RELAY
LOGGING Console, (1)
        at: 1995-02-28-15:33:11.909-05:00I0.405 (2)

        Formatted NICE Data=
DECnet event 0.9, counters zeroed (3)
From node 1.234 (PHASE4), 28-FEB-1992 16:31:18.08
Circuit QNA-0,
     65535  seconds since last zeroed
    977346  arriving packets received
   1087487  departing packets sent
         0  arriving congestion loss
         0  transit packets received
         0  transit packets sent
         0  transit congestion loss
         2  line down
         0  initialization failure
       309  Unknown counter type 822
         1  Unknown counter type 900
   2432065  data blocks sent
 536847580  bytes sent
   2552820  data blocks received
 221074963  bytes received
         0  Multicast received for disabled protocol
       541  user buffer unavailable

        eventUid   96486342-D6F5-CA11-8043-AA000400804D (4)
        entityUid  B677CFE1-D5F5-CA11-8042-AA000400804D
        streamUid  0691473F-D3F5-CA11-8042-AA000400804D

1. Specifies the event and entity instance.
2. Specifies when the event occurred.
3. Specifies the event generated by the Phase IV system.
4. Specifies unique identification (UID) values for the various components involved.

Table A-1 lists the Phase IV components and parameters with their corresponding DECnet Phase V entities and attributes.

DECnet-Plus supports the circuit devices listed in Table B-1, providing multi-access connections among many nodes on the same CSMA-CD circuit.

DECnet-Plus supports the devices listed in Table B-2, providing multi-access connections among many nodes on the same FDDI circuit.

B.3 Synchronous Devices