1 Event_Messages 2 csma-cd_station o alignment error This event is generated whenever an incoming frame does not contain an integral number of octets. This error can be caused by several conditions, such as electromagnetic interference, late collisions, or improperly set hardware parameters (for example, receiver squelch). o carrier check failure This event is generated on a transmission that failed, either because the data link did not sense the receive carrier signal that must accompany transmission of a frame, or because the data link did not detect an error. This error indicates a failure in either the transmitting or receiving hardware, such as the transceiver or transceiver cable. o data overrun This event is generated whenever an incoming frame is lost because of a hardware resource failure such as insufficient hardware buffers or insufficient CPU time. o excessive collision This event is generated whenever a transmission fails because the medium access algorithm reached the maximum number of allowable retransmission attempts resulting from collisions. This error can occur when too many systems are trying to transmit at the same time or when there are cable problems. o frame check error This event is generated whenever an incoming frame fails the Frame Check Sequence test. This error can be caused by several conditions, such as electromagnetic interference, late collisions, or improperly set hardware parameters (for example, receiver squelch). o frame too long This event is generated whenever a remote system sends a frame that exceeds the CSMA/CD MAC maximum length. o late collision This event is generated whenever a transmission fails because a collision was detected after the allowed window for collisions had elapsed. This error indicates either a problem with another system's carrier sense or a weak local transmitter. o receive data length error This event is generated whenever a remote system sends an 802.3 frame having a length field value that is not valid for the number of octets actually received by the MAC. o unavailable station buffer This event is generated whenever an incoming frame is discarded because there is no station buffer available to receive it. This error indicates a lack of local station buffers; that is, a lack of buffers between the cable and the user buffers. On OpenVMS, this event is blocked by default. If you wish to unblock this event, you may do so using the NET$EVENT_LOCAL script. For more information about that script, refer to HELP NETWORK_MANAGEMENT EVENT_DISPATCHER. o unavailable user buffer This event is generated whenever an incoming frame is discarded because there is no user buffer queued to the appropriate port to receive it. This error indicates a lack of buffers in the user process; that is, the buffers supplied by the user for the Receive function. This event is one that network managers commonly select to be blocked. If you wish to block this event, you may do so using the NET$EVENT_LOCAL script. For more information about that script, refer to HELP NETWORK_MANAGEMENT EVENT_DISPATCHER. o unrecognized individual destination pdu This event is generated whenever an incoming frame that matches an enabled individual MAC address is discarded because the frame does not satisfy the filter criteria of any port. This error indicates that a remote system is using a protocol that is locally unsupported or that the local system has not enabled a protocol type, protocol identifier, or LLC SAP address that it should have. o unrecognized multicast destination pdu This event is generated whenever an incoming frame that matches an enabled multicast MAC address is discarded because the frame does not satisfy the filter criteria of any port. This error indicates that the local system has not enabled an Ethernet protocol type, SNAP identifier, or LLC SAP address that it should have, or that a remote system is sending traffic that is invalid for the combination of multicast and the currently specified protocol type, SNAP identifier, or LLC SAP. On OpenVMS, this event is blocked by default. If you wish to unblock this event, you may do so using the NET$EVENT_LOCAL script. For more information about that script, refer to HELP NETWORK_MANAGEMENT EVENT_DISPATCHER. 2 ddcmp_link_(OpenVMS_VAX) o pdu received with header format error Generated each time the local station detects invalid fields in a received message, even though the message's CRC was correct. The errors that can generate this event are: o Invalid select flag o Invalid addr value o Fill fields not zero o Invalid control type or subtype fields Arguments: address Specifies the address of the remote station that caused the event. message Specifies the message header that contains the error. header o selection address error Generated each time the controller of a multipoint link receives a message that contains an address other than that of the currently selected tributary. This event is supported only on half-duplex point-to-point links, or if the protocol characteristic is set to tributary. Arguments: current Specifies the address of the currently selected address tributary station. previous Specifies the address of the previously selected address tributary station. received Specifies the address contained in the received address message. o streaming tributary Records potential jamming of a line by a remote station. It is generated: o When a remote station exceeds a maximum transmission interval without releasing the channel. o When a remote station fails to release a channel after sending a message with the select flag set. o When the jamming condition is cleared. Arguments: previous Specifies the address of the previously selected address tributary station. received Specifies the address contained in the message address received after transmission should have ended. This argument is not present if no message is received. type Specifies the type of jamming that the local station detected, or indicates that jamming has now cleared. Continued The remote station continued to send transmis- information after it sent a message with sion after the select flag set. deselec- tion Continued The remote station continued to send transmis- information after exceeding the maximum sion after transmission interval. timeout Streaming A previous streaming tributary error has cleared been cleared. Streaming The remote station continued to send tributary valid control messages or headers to data message after exceeding the maximum transmission interval. 3 logical_station o buffer too small Generated each time a message is received whose data field is larger than the buffers available on the local station. Arguments: buffer Specifies the size of the receive buffer at the local size station. count Specifies the size of the received data message as specified in the message header. o locally initiated state change Generated each time the state of the local station changes as a result of action on the local node. Arguments: new state New value of the logical station's protocol state attribute. old state Previous value of the logical station's protocol state attribute. o receive error threshold reached Generated each time the number of consecutive receive-related errors reaches the receive error threshold limit of 7. o remotely initiated state change Generated each time the state of the link changes as a result of action on the remote node. Arguments: new state New value of the logical station's protocol state attribute. old state Previous value of the logical station's protocol state attribute. o selection error threshold reached This event is generated each time the number of consecutive selection-related errors reaches the selection error threshold limit of 7. This event is supported only when the protocol characteristic of the owning ddcmp link entity is set to control, or when the link is half-duplex point-to-point. o send error threshold reached This event is generated each time the number of consecutive transmit related errors reaches the transmit error threshold limit of 7. o strt received while in maintenance This event is generated each time a strt message is received while the value of the status attribute protocol state of the local station is set to maintenance. 2 device_unit o device failure Generated each time a failure is detected on a device. Arguments: failure Reason for the device failure. The values of this reason argument are implementation specific. firmware Identifier of the device's microcode. identifier next state Next state of the device. This depends on the values of the auto load and dump on error characteristics. dumping The entity will try to dump the device's microcode. loading The entity will try to load the device's microcode. stopped The entity will stop, awaiting a dump or load command. o failed dump Generated each time there is a failure to dump the device's microcode. Arguments: dump des- Destination that the dump operation used. tination dump Reason for the dump failure. reason directive In response to a dump command. failure In response to a device failure while in the running state. failure Reason why the dump failed. The values of this reason argument are device specific. o failed load Generated each time there is a failure to load the device's microcode. Arguments: failure Reason for the load failure. The values of this reason argument are device dependent. load Reason for the load operation. reason directive In response to a load command. dump After completion of a dump operation. failure After a device failure. initial Initial loading of the device at device unit enable when auto load is true. load Source used to retrieve the microcode during the load source operation. o successful load Generated each time the device's microcode is successfully loaded. Arguments: firmware Firmware identifier of the loaded microcode. identifier load Reason for the load operation. reason directive In response to a load command. dump After completion of a dump operation. failure After a device failure. initial Initial loading of the device at device unit enable when auto load is true. load Source used to retrieve the microcode during the load source operation. 2 dtss o clock set This event is generated each time that a DECdts process sets its local clock. Arguments: new time Specifies the corrected clock setting. old time Specifies the faulty time before the clock was set. o different epoch detected This event is generated each time the local node receives a time value that has an epoch number different from its own. This event normally occurs after a node's epoch has been changed. Arguments: local epoch Specifies the local node's epoch number. number server [id] Specifies the known servers and their epoch numbers. o disable completed This event is generated each time that a disable command is executed to stop DECdts. o enable completed This event is generated each time that an enable command is executed to start DECdts. o epoch change completed This event is generated each time that the epoch is set for the local node. Arguments: new epoch Specifies the epoch number after the epoch was declared. old epoch Specifies the epoch number before the epoch was declared. o insufficient resources detected This event is generated each time that the node's virtual memory is full. The event is displayed on all nodes and is usually followed by a system abort. o invalid message detected This event is generated each time that the local node receives a corrupted or incorrect message. Invalid messages are normally retransmitted, but the hexadecimal contents of the invalid message are supplied for troubleshooting. Arguments: message Specifies the hexadecimal contents of the invalid message. node [id] Specifies the full name of the node that generated the invalid message. o local time does not intersect This event is generated each time that the time interval of the local node does not intersect with the values received from other servers. If this event is frequently generated, you may wish to decrease the setting for the characteristic synchronization hold down or increase the settings for the characteristics error tolerance or maximum inaccuracy. Arguments: clock set Specifies whether or not the clock was automatically set to correct the local fault. If false, the clock was not set to correct the local fault. computed Specifies the intersection of the majority of server time times. local time Specifies the local time interval that does not intersect with the computed time. o no global server This event is generated at a courier server when it cannot locate a global server. o protocol version mismatch detected This event is generated each time that the DECdts protocol version of a received message does not match the protocol in force at the local node. Argument: node [id] Specifies the full name of the node that generated the message with the incompatible protocol version. o server not responding This event is generated at a courier server when it attempts to synchronize with the listed global server, but the server does not respond. The event may be caused by a low characteristic setting for wan timeout. Argument: node [id] Specifies the node name of the server not responding. o server time does not intersect This event is generated each time that the local node receives a potentially faulty time value from a server. If the event is repeatedly generated for the same node, examine the node's settings for these characteristics: error tolerance, synchronization hold down, and maximum inaccuracy. Argument: server [id] Specifies the list of servers used in the synchronization. o synchronization completed This event is generated each time that a synchronization is completed for the local node. Arguments: clock Specifies the relative time that the local clock adjustment needs to be adjusted to match the computed time. computed Specifies the time computed from the intersection of time all server time intervals. This event is one that network managers commonly select to be blocked. If you wish to block this event, you may do so using the NET$EVENT_LOCAL script. For more information about that script, refer to HELP NETWORK_MANAGEMENT EVENT_DISPATCHER. o system error detected This event is generated each time that the operating system has a system error relevant to DECdts operation. See the system documentation for an explanation of the report text. Argument: error text Specifies the system error report. o time provider failure detected This event is generated each time that an external time provider returns an invalid time or does not respond. o time representation version mismatch detected This event is generated each time that the local node receives a response indicating that it is using an invalid time representation version. Argument: node [id] Specifies the name of the node that is running the incompatible time representation version. o too few servers detected This event is generated each time that the number of servers specified by the servers required characteristic are not available for synchronization with the local node. Arguments: number Specifies the number of servers that responded to detected the synchronization request. number Specifies the number of servers required for required synchronization. o too many servers detected This event is generated each time that server responses overflow the synchronization list buffer of the local node. The difference between the maximum delivered and number accepted arguments is the number of responses that overflowed the buffer. Arguments: number Specifies the number of server responses that were accepted accepted by the node. number Specifies the number of servers responding to a detected solicitation. o update initiated This event confirms an attempt to change the system time resulting from the update command. Arguments: current time Specifies the current system time. update time Specifies the new, updated system time. 2 event_dispatcher o events lost Generated whenever the event dispatcher cannot allocate resources to queue more events for processing. The event-logging function guarantees that this event cannot be lost. Also, you cannot block this event unless all events for all modules are blocked. This event is placed at the end of the queue. If another event cannot be queued because of resource limitations while this event is still the last event in the queue, the number argument is updated to reflect the latest total of lost events. Argument: number Number of consecutive events lost. o test requested Logged when the test directive is issued. 3 outbound_stream o change confidence Generated each time the transport service detects a change in the connection's confidence value. (The confidence value indicates whether the Transport layer expects a transmit operation to succeed.) This event suggests a change in the connectivity between the outbound stream and the sink. Argument: confidence New transport confidence value. false It is unlikely that a transmit operation would succeed under the current circumstances. true It is likely that a transmit operation would succeed under the current circumstances. o change filter Generated each time that the filter for a stream is changed, whether it is changed by a block, ignore, or pass command or by using set to change the value of the catch all filter characteristic. The initial values of the filters for a stream are reported as arguments in the enable stream event. A filter change event is filtered according to its new values. Arguments: (OpenVMS) new catch Specifies the current catch all filter setting. all filter new global Specifies the current global filter setting. filter new Specifies the current specific filter setting. specific filter old catch Specifies the previous catch all filter setting. all filter old global Specifies the previous global filter setting. filter old Specifies the previous specific filter setting. specific filter o disable Generated each time an outbound stream is disabled by a disable command. o disconnect Generated each time a connection is closed on an outbound stream. The disconnect can be caused by the event dispatcher closing idle connections, a management command, a network failure, a sink crash, or a sink disconnect. Arguments: disconnect Identifies the cause of the disconnect. data 0 remote disconnect 2 shutdown requested (OpenVMS) 3 management directive reason Session Control layer reason for the disconnect. o enable Generated each time an outbound stream is enabled by an enable command. Arguments: catch all Value of the catch all filter when the stream is filter enabled. global Value of the global filter when the stream is filter enabled. (optional) specific Value of the specific filter when the stream is filter enabled. (optional) o events lost Generated whenever the outbound stream cannot allocate resources for event transmission. The event-logging function guarantees that this event cannot be lost. Also, you cannot block this event unless all events for all modules are blocked. This event is placed at the end of the queue. If another event cannot be queued because of resource limitations while this event is still the last event in the queue, the number argument is updated to reflect the latest total of lost events. Argument: number Number of consecutive events lost. o shutdown Generated each time that a shutdown operation results in an orderly disconnect. You cannot block shutdown events for an outbound stream. Arguments: reason cancelled The shutdown was "neutralized" by an intervening disconnect; therefore, the receiver should not shut down. disconnect The shutdown was caused by the timer disconnect timer. disable The shutdown was caused by a disable directive command that specified an orderly shutdown. shutdown The shutdown was caused by a shutdown directive command. 3 relay_logging o event relayed Generated whenever a Phase IV event is received. It relays the Phase IV event into the DECnet-Plus Event Logging Architecture. The entire DECnet NICE message is encapsulated into the NICE data argument. Argument: NICE data Phase IV event display 3 sink o change filter Generated each time that the filter for a sink is changed, whether it is changed by a block, ignore, or pass command or by using set to change the value of the catch all filter characteristic. The intitial values of the filters for a sink may be reported as arguments in the enable sink event. A filter change event is filtered according to its new values. Arguments: (OpenVMS) new catch Current catch all filter setting. all filter new global Current global filter setting. filter new Current specific filter setting. specific filter old catch Previous catch all filter setting. all filter old global Previous global filter setting. filter old Previous specific filter setting. specific filter o events lost Generated whenever the sink cannot allocate resources for event transmission. The event-logging function guarantees that this event cannot be lost. Also, you cannot block this event unless all events for all modules are blocked. This event is placed at the end of the queue. If another event cannot be queued because of resource limitations while this event is still the last event in the queue, the number argument is updated to reflect the latest total of lost events. Argument: number Number of consecutive events lost. 4 inbound_stream o change confidence Generate when the underlying transport service detects that the connection's confidence variable has changed to the new value reported by the confidence parameter. This suggests a change in the connectivity between the outbound stream and the sink. Argument: confidence Specifies the new transport confidence value. false It is unlikely that a transmit operation would succeed under the current circumstances. true It is likely that a transmit operation would succeed under the current circumstances. o disconnect Generated each time the sink detects that an inbound stream connection has been closed. The disconnect can be caused by a management command, a sink disconnect, a network failure, or by receiving notice that the associated outbound stream entity has been shut down. Arguments: disconnect Identifies the cause of the disconnect. data reason Specifies the Session Control layer reason for the disconnect. shutdown Inbound stream disconnected because of a shutdown received event. 2 fddi_station o configuration change Internal configuration of the station changed. o selftest failure An implementation specific code giving the reason for the station failure. Values are listed in the DNA registry. o trace received ECM state machine of the station entered the trace state due to a trace signal received on any PHY port. 3 link o block check error Frame with FCS error was received. On OpenVMS, this event cannot be logged due to VMS device driver restrictions. However, if such an event occurs, its corresponding counter will be incremented. o directed beacon received A directed beacon was received. On OpenVMS, this event cannot be logged due to VMS device driver restrictions. However, if such an event occurs, its corresponding counter will be incremented. o duplicate address test failure Duplicate address algorithm detected a duplicate. On OpenVMS, this event cannot be logged due to VMS device driver restrictions. However, if such an event occurs, its corresponding counter will be incremented. o duplicate token detected Duplicate token is detected. On OpenVMS, this event cannot be logged due to VMS device driver restrictions. However, if such an event occurs, its corresponding counter will be incremented. o fci strip error Frame content independent strip was terminated by a token. On OpenVMS, this event cannot be logged due to VMS device driver restrictions. However, if such an event occurs, its corresponding counter will be incremented. o frame status error Frame with good FCS, but E indicator set was received. On OpenVMS, this event cannot be logged due to VMS device driver restrictions. However, if such an event occurs, its corresponding counter will be incremented. o link buffer unavailable No buffer was available to to receive a frame. On OpenVMS, this event cannot be logged due to VMS device driver restrictions. However, if such an event occurs, its corresponding counter will be incremented. o pdu length error Frame of invalid length or odd number of symbols was received. On OpenVMS, this event cannot be logged due to VMS device driver restrictions. However, if such an event occurs, its corresponding counter will be incremented. o receive data overrun A receive overrun hardware error was detected. On OpenVMS, this event cannot be logged due to VMS device driver restrictions. However, if such an event occurs, its corresponding counter will be incremented. o ring beacon initiated Link started the beacon process. On OpenVMS, this event cannot be logged due to VMS device driver restrictions. However, if such an event occurs, its corresponding counter will be incremented. o ring initialization initiated Ring is reinitialized by this link. On OpenVMS, this event can only be logged by certain versions of the VMS device drivers. Even in those cases where the drivers support this event, it will not be logged on a one-to-one basis with increases in its corresponding counter. Instead, only one error report will be issued for any number of these events that occur within a sampling period. This is intended to prevent the possibility of flooding OPCOM with these events. o ring initialization received Ring is reinitialized by some other link. On OpenVMS, this event can only be logged by certain versions of the VMS device drivers. Even in those cases where the drivers support this event, it will not be logged on a one-to-one basis with increases in its corresponding counter. Instead, only one error report will be issued for any number of these events that occur within a sampling period. This is intended to prevent the possibility of flooding OPCOM with these events. o ring purge error Ring purger received a token while purging. On OpenVMS, this event cannot be logged due to VMS device driver restrictions. However, if such an event occurs, its corresponding counter will be incremented. o trace initiated PC-trace was initiated by this link. On OpenVMS, this event cannot be logged due to VMS device driver restrictions. However, if such an event occurs, its corresponding counter will be incremented. o transmit failure Failure to transmit operation other than underrun. On OpenVMS, this event cannot be logged due to VMS device driver restrictions. However, if such an event occurs, its corresponding counter will be incremented. o transmit underrun Transmit failed due to underrun. On OpenVMS, this event cannot be logged due to VMS device driver restrictions. However, if such an event occurs, its corresponding counter will be incremented. o unrecognized individual pdu destination Frame with unrecognized DSAP or port-id. o unrecognized multicast pdu destination Frame with unrecognized DSAP or port-id. On OpenVMS, this event is blocked by default. If you wish to unblock this event, you may do so using the NET$EVENT_LOCAL script. For more information about that script, refer to HELP NETWORK_MANAGEMENT EVENT_DISPATCHER. o user buffer unavailable Data link user did not supply a receive buffer. 3 phy_port o link confidence test reject Counted as LCT rejects. o link elasticity buffer error Counted as elasticity buffer errors. o link error monitor reject Counted as LEM rejects. 2 hdlc_link o buffer unavailable error Generated each time a frame is discarded because there is no receive buffer available. o link down Generated each time the entity is disabled. o link up Generated each time the entity is enabled. o pdu receive overrun Generated each time the Physical layer entity reports a receive overrun. o pdu transmit failed Generated each time an attempt to send a frame fails. Argument: pdu transmit Failure reason received from the Physical layer failed entity. reason disabled The network manager has disabled the line. line down The line is in the failed state. no service The Physical layer service is not available. 3 logical_station o frmr generated Generated each time the logical station rejected a received frame. Arguments: frmr Contents of the frame reject frame that is returned to the remote station. frmr Reason for rejecting the frame. reason control One of the control fields is undefined or not implemented by the local station. format The frame's control field is invalid because the frame contained information that is not allowed, the frame is supervisory, or the frame is unnumbered and has the wrong length. length The information field of the frame exceeds the maximum capacity. nonspecific The received frame contains an unspecified number or type of error. nr The frame's control field contains an invalid N(R). received Header of the frame that caused the generation of the pdu event. o frmr received Generated each time the remote station rejected a frame. Arguments: frmr Contents of the frame reject frame that is returned to the remote station. frmr Reason for rejecting the frame. reason control One of the control fields is undefined or not implemented by the local station. format The frame's control field is invalid because the frame contained information that is not allowed, the frame is supervisory, or the frame is unnumbered and has the wrong length. length The information field of the frame exceeds the maximum capacity. nonspecific The received frame contains an unspecified number or type of error. nr The frame's control field contains an invalid N(R). received Received FRMR that caused the generation of the pdu event. o negotiation failed Generated each time XID negotiation fails. Arguments: negotiation Reason that negotiation with the remote station failure failed. reason address id The preferred addresses and the address- not unique negotiation unique IDs were identical. incompatible The remote station wanted to use HDLC's address extended addressing which the Digital modes Network Architecture's implementation does not support. incompatible Incompatible CRC types were specified by crc types the two stations. incompatible Incompatible sequence moduli were sequence specified by the two stations. moduli link type There has been an attempt to initialize mismatch using classes of procedures that are not appropriate for the specified link type. maximum The negotiated maximum frame size pdu size is less than the value of the hdlc too small link entity's minimum data size characteristic. negotiation The remote station performed an illegal error negotiation operation. no There has been no valid reponse from response the remote station to the generated XID within the number of times specified by the hdlc link entity's retry maximum characteristic. parameter The parameter IDs that should be unique id not are not so. unique protocol An attempt has been made to initialize id sequenced data ports with different mismatch protocol IDs. transmission Mismatch in the sync/async bit in the type XID. mismatch ui not An attempt has been made to initialize supported without the UI optional function, which is required when running MOP over an HDLC link. local xid The XID that the local station used during the failed negotiation. remote xid The XID that the remote station used (if any) during the failed negotiation. o station halted Generated each time the logical station's status attribute protocol state becomes halted. Argument: station Reason for the logical station to halt its protocol. halted reason disc A DISC frame was received from the remote station. dm A DM frame was received from the remote station. fbit error A frame was received from the remote station with an error in the F-bit. frmr An FRMR frame was received from the remote station. local The initialization was as a result of the enable command. maximum The number of times that a frame has retry been sent has exceeded the value of the hdlc link entity's retry maximum characteristic. physical There was a failure in the Physical layer. unsolicited An unsolicited UA frame was received ua from the remote station. user The initialization was as a result of local user action. window The initialization occurred as part of error the recovery from a windowing error. o station initializing Generated each time the logical station's protocol is successfully initialized or reinitialized. Argument: station Reason for the logical station to initialize its initial- protocol. izing reason disc A DISC frame was received from the remote station. dm A DM frame was received from the remote station. fbit error A frame was received from the remote station with an error in the F-bit. frmr An FRMR frame was received from the remote station. local The initialization was as a result of the enable command. maximum The number of times that a frame has retry been sent has exceeded the value of the hdlc link entity's retry maximum characteristic. physical There was a failure in the Physical layer. unsolicited An unsolicited UA frame was received ua from the remote station. user The initialization was as a result of local user action. window The initialization occurred as part of error the recovery from a windowing error. xid An XID frame was received from the remote station. o station inoperative Generated each time the status attribute protocol state becomes inoperative. o station maintenance Generated each time the status attribute protocol state becomes maintenance. o station resetting Generated each time the status attribute protocol state becomes resetting. Argument: station Reason for the logical station to perform a reset resetting operation. reason fbit error A frame was received from the remote station with an error in the F-bit. frmr An FRMR frame was received from the remote station. maximum The number of times that a frame has retry been sent has exceeded the value of the entity's retry maximum characteristic. sabm A SABM frame was received from the remote station. unsolicited An unsolicited UA frame was received ua from the remote station. window The initialization occurred as part of error the recovery from a windowing error. o station running Generated each time the logical station's protocol has been successfully initialized. In addition, the status attribute protocol state changes to running. o station setup failed Generated each time the logical station's protocol fails to be initialized following either: o The expiration of the entity's maximum retry characteristic when in the initializing state o A forced disconnection from the remote station o unknown ui pdu received Generated each time an unsequenced frame is received specifying a protocol ID to which a port has not been opened on this station. Argument: received Received UI frame which caused this event to be pdu generated. 2 lapb_link o buffer unavailable error (OpenVMS) Generated when a frame is discarded because there is no buffer available. o frmr received Generated when an FRMR (frame reject) frame is received from the remote station. Arguments: frmr Contents of the header of the FRMR frame. frmr Reason why the FRMR frame was generated. See possible reason reasons described under the frame reject generated event. o frmr sent Generated when the receipt of a frame causes an FRMR (frame reject) frame to be generated and transmitted to the remote station. Arguments: received Header of the frame that caused the event to be pdu generated. frmr Contents of the generated FRMR frame. frmr Reason why the FRMR frame was generated. reason control A received control field is either undefined or is not implemented. format The received control field is invalid either because the frame contained an unallowed information field, or because the frame is a supervisory or unnumbered frame of incorrect length. length The received information field is longer than the maximum established capacity. nonspecific The received frame has an unspecified number or types of errors. nr The received control field contains an invalid N(R). o link halted Generated when the status attribute protocol state is set to halted. Argument: link Reason why the LAPB protocol entered the halted halted state. reason disc Link halt caused by remote end. dm Link halt caused by remote end. fbit error Link halt caused by remote end. frmr Link halt caused by remote end. implementation Link halt caused by implementation- specific specific error. local Link halt due to local management action. maximum Link halt due to the number of retries retry reaching the maximum specified in the characteristic retry maximum. physical Link halt due to failure of the Physical Layer. unsolicited ua Link halt caused by remote end. user Initialization was result of local user action. window Link halt caused by remote end. error o link initializing Generated when the protocol has been successfully initialized or reinitialized. Argument: link ini- Reason why the LAPB protocol entered the initializing tializing state. reason The reasons are the same as described for the link halted reason argument for the link halted event. o link inoperative Generated when the status attribute protocol state is set to inoperative. o link maintenance Generated when the status attribute protocol state is set to maintenance. o link resetting Generated when the LAPB protocol is being successfully reset. Argument: link Reason why the link is resetting. resetting reason fbit error Link reset caused by remote end. frmr Link reset caused by remote end. implementation Link reset is due to implementation- specific specific error. maximum Link reset due to the number of retries retry reaching the value specified in the characteristic retry maximum. sabm Link reset caused by remote end. unsolicited ua Link reset caused by remote end. window Link reset caused by remote end. error o link running Generated when the LAPB protocol has been successfully initialized and the status attribute protocol state has been set to running. o link setup failed Generated when the LAPB protocol has failed to initialize correctly after the maximum number of allowed attempts. o link state changed Generated for each link state transition. The link state shows the new link state. Argument: final state The new setting of the state attribute (on or off). o pdu receive overrun Generated each time the underlying physical layer indicates that a receive overrun has been detected. o pdu transmit failed Generated when a call to transmit a frame at the Physical layer via the internal framing interface fails. Argument: pdu Failure reason returned by the Physical layer. transmit failure reason disabled The line has been disabled by network management action. line down The line is in the failed state. no service The Physical layer service is not available. 2 llc2_sap o sap state changed This event is generated when the status attribute STATE changes from On to Off, or from Off to On. Argument: New SAP State Specifies the new state of the SAP. 3 link o frame reject generated This event is generated when the receipt of a frame causes an FRMR (frame reject) frame to be generated and transmitted to the remote station. Arguments: frame Specifies the contents of the header of the frame that caused the FRMR frame to be generated. frame reject Specifies why the FRMR frame was rejected. reason control A received control field is undefined or is not implemented. format The frame contains an unallowed information field, or contains a supervisory or unnumbered field of incorrect length. length A received information field exceeds the maximum length. nr A received control field contains an invalid n(r). ns A received control field contains an invalid n(s). nonspecific The frame contains an unspecified number or type of errors. generated Specifies the contents of the generated frmr frame frmr that is sent to the remote station. o frame reject received This event is generated when an FRMR (frame reject) frame is received from the remote station. Arguments: frame Specifies the contents of the header of the received FRMR frame. frame reject Specifies why the frame was rejected. See possible reason reasons described under the Frame Reject Reason argument of the Frame Reject Generated event. o link halted This event is generated when the status attribute protocol state is set to halted. Argument: link halted Specifies why the protocol halted. reason disc A DISC frame was received. The remote end has disconnected the link. dm A DM frame was received. The remote end has disconnected the link. frmr A FRMR frame was received. The remote end has detected a frame error. implementation The cause is unknown. Specific lan The LAN station has failed. local Local management action on the sap or link entities has halted the link. maximum retry A PDU had to be retransmitted the maximum number of times without response from the remote end. User Local client action has halted the link. o link initializing This event is generated when the protocol has been successfully initialized or reinitialized. Argument: link initializing Specifies why the protocol was initialized or reason reinitialized. See possible reasons described under the Link Halted Reason argument of the link halted event. o link inoperative This event is generated when the status attribute protocol state is set to inoperative. o link resetting This event is generated when the status attribute protocol state is set to resetting. Argument: link Specifies why the protocol is being reset. resetting reason frmr A FRMR frame was received. The remote end has detected a frame error. implementation The reason is unknown. specific maximum retry A PDU had to be retransmitted the maximum number of times without response from the remote end. sabme A SABME frame was received. The remote end has reset the link. o link running This event is generated when the status attribute protocol state is set to Running. This means that the protocol has been successfully initialized or reset. o link setup failure This event is generated when llc2 protocol initialization has failed after the maximum number of retries. o link state changed This event is generated when the status attribute state changes from On to Off, or from Off to On. 2 modem_connect_line o cable detected Generated when a valid communication cable is detected following a cable fault event. Arguments: current Type of cable detected. interface type loopback A loopback connector has been detected. null modem A null modem has been detected. rs232c A cable conforming to the RS-232-C standard has been detected. rs449 A cable conforming to the RS449 standard has been detected. rs422 A cable conforming to the RS422 standard has been detected. rs423-v24 A cable is attached, but the connector cannot distinguish whether it conforms to RS423 or V.24 standards. v28 A cable conforming to any of the CCITT V.24, CCITT V.28, IS2110, or EIA-232-D standards has been detected. v35 A cable conforming to the V.35 standard has been detected. x.21 A cable conforming to the X.21 standard has been detected. previous Previous type of cable detected. interface type no cable No cable was attached to the interface. unknown A cable was attached, but its type was unknown. o cable fault Generated each time the communications cable is detected as missing or invalid. Arguments (The call reference argument is present only if the characteristic connection type is switched.): call The call reference number of the call that was reference disconnected because of the fault. previous Type of cable that was connected before the error interface was detected. type loopback A loopback connector. null Modem A null modem cable. rs232c A cable conforming to the RS-232-C standard. rs422 A cable conforming to the RS422 standard. rs423-v24 A cable is attached, but the connector cannot distinguish whether it conforms to RS423 or V.24 standards. rs449 A cable conforming to the RS449 standard. unknown A cable was connected but its type was unknown. v28 A cable conforming to any of the CCITT V.24, CCITT V.28, IS2110, or EIA-232-D standards. v35 A cable conforming to the V.35 standard. x.21 A cable conforming to the X.21 standard. reason Reason that caused the event to occur. invalid A cable is attached but it is not one cable of those recognized no cable No cable can be detected o clock loss Generated each time a loss of the transmit or receive clock is detected. Once this event occurs, the value of the interface state attribute changes to pending dte ready. o dce not ready Generated each time a dce not ready condition is detected. Once this event occurs, the value of the interface state attribute changes to dte ready. This event is not supported if the characteristic modem control is none. o device error A potential device error has been detected. This may be a temporary condition that means the device can continue to be used. Argument: reason Reason for the failure. This is device specific. o framing error Generated each time an asynchronous framing error occurs. o incoming call failed Generated each time an incoming call is detected but the connection fails to complete. This event is supported only if the characteristic connection type is switched. Arguments: call Call Reference of the call that failed to connect. reference reason Reason for the failure to complete the connection. initial hold The time set by the characteristic time expired initial hold timer has expired. line The line has been disabled. disabled line failure There has been a communications failure. local The entity has disconnected the line. disconnect no call There is no client assigned to handle control the call. client remote or The remote system has disconnected the network line disconnect remote test The remote system is in test mode. active o loss of carrier Generated each time the carrier frequency is lost while receiving data. This event is not supported if the characteristic modem control is none. o outgoing call failed Generated each time an attempt to complete an outgoing call fails. This event is supported only if the characteristic connection type is switched. Arguments: Additional Any extra information on the call failure above that information given in other arguments. call Call reference of the call that failed. reference dial Dialing sequence used to make the call. sequence reason Reason that the call could not be completed. call The call attempt occurred at the same collision time as an incoming call was received. call The call initiation failed. initiation failed call not The remote system did not answer answered the call within the time set by the characteristic successful call indication timer. incoming An incoming call has already been call answered. answered line The line is disabled. disabled line failure There has been a communications line failure. local The local system has disconnected the disconnect line. remote or The remote system has disconnected the network line. disconnect remote test The remote system is in test mode. active o rate fallback Generated each time the DCE indicates that it is changing from the high data rate (as indicated by the speed characteristic) to the low data rate (as indicated by the alternate speed characteristic. This can occur if there is excessive noise when operating at the high data rate. This event is supported only when the modem has a rate selection capability. o test indication Generated each time the remote system tests the DCE. When this event occurs, the value of the interface state attribute changes to dte ready. This event is not supported id the characteristic modem control is none. o transmit enable timeout Generated whenever the time to assert the clear to send signal (after receiving the request to send signal) is greater that that specified in the maximum enable transmit timer characteristic. This event is not supported id the characteristic modem control is none. 2 mop_circuit o dump request completed This event is generated each time a remote dump service request completes successfully. Arguments: See the address, client, and file arguments described under the load request failed event. o dump request failed This event is generated each time a remote dump request tries and fails. When a request is never started because of insufficient client information, the unrecognized dump client event is reported. Arguments: See the address, client, file, and reason arguments described under the load request failed event. o load request completed This event is generated each time a remote load service request completes successfully. Arguments: See the address, client, file, and program type arguments described under the load request failed event. o load request failed This event is generated each time a remote load request tries and fails. When a request is never started because of insufficient client information, the unrecognized load client event is reported. Arguments: address Data Link address of the remote system. This argument is supplied only for LAN data links. client Name of the client that corresponds to the remote system. file Name of the file being dumped or loaded. program Program type requested by the remote system on a load type operation. cmip A file containing initialization data script encoded as network management directives in CMIP form. diagnostic A file containing diagnostic test procedures. management A file containing initialization data encoded in a product-specific format. secondary A secondary file containing software to loader be downline loaded. system The primary file containing the system image to be downline loaded. tertiary A third file containing software to be loader downline loaded. reason Reason for the failure. file i/o Unable to read load file or write dump error file. file open Unable to open load or dump file error requested. no Insufficient network management or resources system resources. operation Unexpected error prevents completion of aborted request. protocol A violation of the MOP protocol error occurred. receive Error or timeout receiving data from the error network. transmit Error reading data to the network. error unknown Client requesting load or dump is not client found in MOP client database. o unrecognized dump client This event is generated each time a remote dump service request was not accepted because a required client database entry could not be found. Argument: See the address argument described under the load request failed event. o unrecognized load client This event is generated each time a remote load service request was not accepted because a required client database entry could not be found. Arguments: See the address and program type arguments described under the load request failed event. 2 node The following event messages only apply to Tru64 UNIX: o address changed Generated each time the node address changes. Arguments: old address Protocol tower set that constituted the old node address. new address Protocol tower set that constitutes the new node address. o id changed Generated each time the node's ID status attribute changes value. Arguments: old id Node's old 48-bit ID. new id Node's new 48-bit ID. o idrom check failure Generated each time that an IDROM was checked and failed the test. Arguments: contents Value of the failed IDROM. owner Name of the device on which the failed IDROM address exists. o renamed Generated each time the node's name changes. Arguments: old name Old full name of the node. new name New full name of the node. 2 nsp 3 local_nsap o deleted remote nsap Generated each time a remote NSAP is deleted. Arguments: The event message lists all attributes for the deleted entity. 4 remote_nsap o reject received Generated when a connection attempt initiated by the local NSAP is rejected by the remote NSAP. Arguments: additional If applicable, contains additional information from information the variable part of the PDU. reason Reason why the event was generated. no resources Transport rejected the connection attempt because of insufficient resources. o reject sent Generated when a connection attempt initiated by the remote NSAP is rejected by the local NSAP. Arguments: See the arguments for the reject received event. o remote protocol error Generated when a transport PDU received from the remote NSAP violates NSP protocol. Arguments: erroneous Includes some, none, or all of the PDUs causing the transport event. data unit reason Reason why the event was generated. invalid flow A PDU was discarded because it control contained flow control information that, when used to compute the request count, would produce a result that exceeds the limits. The entire PDU is provided in the erroneous transport data unit argument. invalid A PDU was discarded because reserved message bits or values were used in the PDU. format The beginning of the PDU is provided in the erroneous transport data unit argument. 2 osak o unknown ae title Generated when an inbound association request specifies an unknown application entity title. Increments the unknown ae-titles counter. Arguments: ae title The unknown application entity title. o unknown invocation Generated when an inbound association request specifies an unknown application process invocation identifier or an unknown application entity invocation identifier. Increments the unknown invocations counter. Arguments: invocation The unknown application process or application entity invocation identifier. o unknown paddress Generated when an inbound association request specifies an unknown presentation address. Increments the unknown paddresses counter. Arguments: paddress The unknown presentation address. 3 application o invalid mode Generated when an inbound connection request is rejected due to a mismatch of modes. Increments the invalid mode failures counter. 2 osi_transport 3 local_nsap o deleted remote nsap This event is generated each time a remote NSAP is deleted. Arguments: The event message lists all attributes for the deleted entity. 4 remote_nsap o checksum failure Generated each time a checksum validation fails on a received TPDU. o invalid tpdu received Generated when a TPDU received from the remote NSAP is in violation of the OSI transport protocol. If the error occurred during connection establishment, a DR (disconnect request) TPDU will be sent in response to the protocol error. If the error occurred on an established transport connection, an ER (error) TPDU will be sent in response to the protocol error. The remote protocol error counter will be incremented. Arguments: reject If an ER TPDU was transmitted or received, this is cause the value of the reject cause parameter. If a DR was transmitted, this is the value of the reason parameter. erroneous The portion of the invalid TPDU transmitted or received trans- in the invalid TPDU parameter of the ER or DR TPDU. port PDU (OpenVMS only) DNA The unique error number used to unambiguously error distinguish between different errors. This number is completely independent of the reason and reject cause values defined by the OSI Transport protocol, the set of which is too sparse to provide useful information. o er tpdu received Generated whenever an ER (error) TPDU is received from the remote NSAP. The local protocol error counter will be incremented. Arguments: reject The value of the reject cause parameter in the received cause ER TPDU. erroneous The portion of the invalid TPDU received in the invalid trans- TPDU parameter of the ER TPDU. port PDU DNA The unique error number used to unambiguously error distinguish between different errors. This number is completely independent of the reason and reject cause values defined by the OSI Transport protocol, the set of which is too sparse to provide useful information. (OpenVMS only) o local transport disconnection Generated each time a connection attempt initiated by the remote NSAP is rejected by the local NSAP. This does not include rejects generated by the local user of the transport service. Thus, this event is generated on the transmission of a DR TPDU in which the reason parameter has a value other than 128. The reject sent counter will be incremented. Argument: DNA error This is the value transmitted in the additional information parameter of the DR TPDU. o remote transport disconnection This event is generated each time a connection attempt initiated from the local NSAP is rejected by the remote NSAP. This does not include rejects requested by the remote user of the transport service. Thus, this event is generated on the receipt of a DR TPDU in which the reason parameter has a value other than 128 (which is a normal disconnect). The reject received counter will be incremented. Arguments: reason Reason why the event was generated and it is the value received in the reason parameter of the DR TPDU. additional The value received in the additional information informa- parameter of the DR TPDU. If the remote NSAP is a tion DNA OSI Transport implementation, the additional information parameter will have one of the following values: '01'H Too much user data in CR (connection request) or CC (connection confirm) TPDU '02'H Proposed TPDU size invalid '05'H Invalid protocol class requested '07'H Illegal negotiation attempted '08'H Invalid parameter in TPDU '09'H TPDU header length invalid '0A'H Parameter length error in TPDU header '0B'H TPDU longer than negotiated maximum '0C'H Segmentation of expedited data illegal '0D'H Invalid parameter value '10'H Invalid TPDU type '12'H Expedited data out of sequence '40'H Unknown transport selector '41'H Proposed protocol class(es) unavailable '42'H Insufficient resources '43'H Maximum connections already active '80'H Unknown reference '81'H Connection timed out '82'H Idle connection timed out '83'H Unacknowledged ER TPDU 2 routing o address unreachable pdu discard Support: All Generated when a data PDU is discarded because the destination address is unreachable. Arguments: discard Reason why the PDU was discarded. reason destination The destination address is unknown. address unknown destination The destination address is address currently unreachable. unreachable duplicate An optional PDU field occurs twice. option header syntax There is a format error in the PDU error header. incomplete The received data did not contain a pdu complete PDU. received incorrect The checksum is incorrect. checksum lifetime The PDU's lifetime expired while it was expired being reassembled. during reassembly lifetime The PDU's lifetime expired while it was expired in transit. while data unit in transit pdu No buffers were available to forward the discarded packet. due to congestion protocol Unable to translate a DECnet-Plus format procedure PDU into a Phase IV format PDU. error reason not No further information available. specified reassembly Insufficient memory available to interference reassemble a PDU. segmentation The PDU requires fragmentation, but the required, but originator did not permit this. not permitted unsupported The PDU contained an unrecognized and option not unsupported PDU option. specified unsupported The PDU version is not supported. protocol version unsupported The sender requested an unsupported form recording of of route recording. route option unsupported The sender requested an unsupported form source of source routing. routing option phase iv Phase IV destination address of the forwarding Phase IV data packet. address phase iv Phase IV source address of the Phase IV source data packet. address forwarding Destination NSAP address. address receiving Name of the adjacency on which the PDU adjacency was received. For an end node, only the circuit may be specified. source Source NSAP address of the data NPDU. address o aged ip packet discard Support: IP Generated when an IP packet is discarded because the interval specified in its time to live field has expired. o aged pdu discard Support: L1,L2 Generated when a data PDU is discarded because its lifetime has expired. Arguments: discard Reason why the PDU was discarded. See possible reason reasons described under the discard reason argument of the address unreachable pdu discard event. (Not all of these argument values can be generated by this event.) phase iv Phase IV header of the Phase IV packet causing this pdu header event. pdu header Contents of the header of the data PDU that was discarded. o attempt to exceed maximum sequence number Support: L1,L2 Generated when an attempt is made to increase the sequence number of a link-state packet beyond the maximum allowed sequence number. o corrupted lsp detected Support: L1,L2 Generated when a corrupted link-state packet is detected in memory. o egp message discard Support: All Generated when EGP Message is discarded. o ip address unreachable packet discard Support: IP Generated when an IP packet is discarded because its destination is unreachable. Arguments: forwarding IP address on which the forwarding decision for the IP address IP packet was taken. This is usually the destination IP address. icmp Value of the code field of the corresponding ICMP discard destination unreachable message. reason host unreachable network unreachable source route failed LAN Data link address of the broadcast circuit that address is the previous hop for the packet. This argument is present only if the receiving entity argument identifies a broadcast circuit entity. receiving Local name of the circuit entity corresponding to the entity previous hop for the packet. source ip Source IP address of the IP packet. address o ip destination address packet error discard Support: IP Generated when an IP packet is discarded because the destination IP address is invalid (that is, it has an invalid format, or it refers to an unsupported network class). Arguments: destination Destination IP address in the IP packet. ip address LAN Data link address of the broadcast circuit that address is the previous hop for the packet. This argument is present only if the receiving entity argument identifies a broadcast circuit entity. receiving Local name of the circuit entity corresponding to the entity previous hop for the packet. source ip Source IP address of the IP packet. address o ip packet discard Support: IP Generated when an IP packet is discarded because of version number mismatch or bad checksum. Arguments: ip discard Reason why the IP packet was discarded. See the ip reason discard reason argument of the IP Packet Format Error event. ip header IP header of the PDU that caused the event. receiving Local name of the circuit entity corresponding to the entity previous hop for the packet. o ip packet format error Support: IP Generated when an IP packet is discarded because it contains a format error. Arguments: ip discard Reason why the IP packet was discarded. reason duplicate option header syntax error incomplete packet received incorrect checksum incorrect header length incorrect total length option error protocol procedure error reason not specified received via broadcast unsupported option not specified unsupported protocol version unsupported security option ip header IP header of the PDU that caused the event. LAN Data link address of the broadcast circuit that address is the previous hop for the packet. This argument is present only if the receiving entity argument identifies a broadcast circuit entity. pointer Offset of the octet in the IP header that caused the format error. receiving Local name of the circuit entity corresponding to the entity previous hop for the packet. o ip protocol unreachable packet discard Support: IP Generated when an IP packet is discarded because there was no port on the local system for the protocol type specified in the IP header. Arguments: destination Value of the protocol field in the IP packet. protocol icmp Value of the code field of the corresponding ICMP discard destination unreachable message. reason Port Unreachable Protocol Unreachable LAN Data link address of the broadcast circuit that address is the previous hop for the packet. This argument is present only if the Receiving Entity argument identifies a broadcast circuit entity. receiving Local name of the circuit entity corresponding to the entity previous hop for the packet. source ip Source IP address of the IP packet. address o ip source address packet error discard Support: IP Generated when an IP packet is discarded because the source IP address is invalid (that is, it has an invalid format, or it refers to an unsupported network class). Arguments: destination Destination IP address in the IP packet. ip address LAN Data link address of the broadcast circuit that address is the previous hop for the packet. This argument is present only if the Receiving Entity argument identifies a broadcast circuit entity. receiving Local name of the circuit entity corresponding to the entity previous hop for the packet. source ip Source IP address of the IP packet. address o lsp L1 database overload Support: L1,L2 Generated when the status attribute L1 state changes from on to waiting, or vice versa. Arguments: source id Source ID of the link-state packet. state Current state. change recovered Router operating normally. waiting Router has failed to store a link-state packet, and is operating in restricted mode. o lsp L2 database overload Support: L2 Generated when the status attribute L2 state changes from on to waiting, or vice versa. Arguments: source id Source ID of the link-state packet. state Current state. change recovered Router is operating normally. waiting Router has failed to store a link-state packet, and is operating in restricted mode. o manual address dropped from area Support: L1,L2 Generated when one of the addresses in the manual area addresses set is ignored when computing an area address. The event is generated once for each address that is dropped. Argument: area Area address that caused the maximum number of area address addresses to be exceeded. o own lsp purged Support: L1,L2 Generated when a zero-aged copy of a node's own link-state packet is received from some other node. This represents an invalid attempt to purge the local node's link-state packet. o pdu format error Support: All Generated when a data PDU is discarded because of a format error. Arguments: discard Reason why the PDU was in error. See possible reasons reason described under the discard reason argument of the address unreachable pdu discard event. (Not all of these argument values are generated by this event.) phase iv Phase IV header of the Phase IV packet causing this pdu header event. pdu header Contents of the header of the data PDU that was discarded. receiving Name of the adjacency on which the PDU was received. adjacency For an end node on a LAN, only the circuit may be specified for Tru64 UNIX. o phaseiv translation failure Support: All Generated when a PDU is discarded because it cannot be translated to Phase IV format. Arguments: receiving Local entity name of the adjacency upon which the adjacency PDU was received. For an end node on a LAN, only the circuit may be specified for Tru64 UNIX. pdu header Data PDU header causing the event. o sequence number skipped Support: L1,L2 Generated when the sequence number of a link-state packet is incremented by more than 1. This usually occurs when a router is reenabled while its previous link-state packets are still stored in the network. o unsupported option Generated when a data packet is received that contains an unsupported option in its header. Arguments: discard Reason why the event was generated. See possible reason reasons described under the discard reason argument of the address unreachable pdu discard event. (Not all of these argument values are generated by this event.) pdu header Contents of the header of the data PDU that caused the event. receiving Name of the adjacency on which the PDU was received. adjacency For an end node on a LAN, only the circuit may be specified. 3 circuit o adjacency state change Support: All Generated when the status attribute state of a routing circuit adjacency entity belonging to the circuit changes from up to down, or vice versa. For the purposes of this event, the state up/dormant is considered to be the same as up, and the state initializing is considered to be the same as down. For end nodes, this event is generated for point-to-point links only. Arguments: adjacency The name of the adjacency to which the event refers. name adjacent Node IDs of the adjacent node. node new Current state of the adjacency. adjacency state down Adjacency state is now down. up Adjacency state is now up. reason Reason why the adjacency state changed to down. address out The adjacency address is invalid. of range configura- The adjacency has been incorrectly tion fault configured. exceeded The value of the characteristic maximum maximum call attempts has been exceeded. call attempts area The adjacent node's area address is mismatch incorrect. call An X.25 call to the adjacent node rejected failed. checksum A PDU's checksum was invalid. error circuit The circuit has been disabled by network disabled management. datalink Exceeded maximum call attempts; failure configuration fault. holding No Hello traffic has been received timer during the period of the Hello timer. expired maximum There are more adjacent nodes than can broadcast be supported on a LAN. end nodes exceeded maximum There are more adjacent nodes than can broadcast be supported on a LAN. routers exceeded neighbor The address(es) in the hello has/have node changed. change one way The connectivity between two LAN connectiv- routers appears to permit traffic in ity one direction only. reserve This may occur temporarily during a timer change of designated router. Repeated expired occurrences indicate a configuration or hardware error. version The adjacent node is the wrong version. skew wrong node The adjacent routing node is of the type wrong type. o authentication failure Support: L1,L2,IP Generated when a PDU is received that contains an Authentication Information field that is incompatible with the PDU type. Arguments: adjacent Node ID of the adjacent node. node authentication Authentication level of the PDU: area, circuit, level domain. pdu type Type of the PDU. L1 LSP L2 PSNP L1 CSNP LAN L1 Hello L1 PSNP LAN L2 Hello L2 LSP PtPt Hello L2 CSNP o circuit change Support: All Generated when the status attribute state of the circuit changes from off to on, or vice versa. Argument: disable The reason that the circuit status changed from on to reason off. If the disable occurred because of a management circuit disable action, the reason is a Management Action (1). If the disable occurs for any other reason, it is a Protocol Action (0). new Current state of the circuit. circuit state off Circuit state is now off. on Circuit state is now on. o corrupted hello pdus received Support: All Generated when an ES-IS (end system to intermediate system) or IS-IS (intermediate system to intermediate system) Hello PDU is received that either cannot be parsed or contains an incorrect checksum. o corrupted lsp received Support: L1,L2 Generated when a corrupted link-state packet is received. Argument: adjacent Node IDs of adjacent nodes. node o corrupted phaseiv routing packet received Support: L1,L2 Generated when a corrupted Phase IV routing packet is received. Argument: phase iv Phase IV ID of the Phase IV routing message that id caused the event to be generated. o da adjacency change Support: All Generated when the state of a DA adjacency on the circuit changes from up to down or from down to up. For these purposes, the states up and up/dormant are considered up and any other state is considered down. This attribute is supported only if the circuit type is x25 da. Arguments: adjacency Name of the adjacency to which the event refers. name new Current state of the adjacency. adjacency state down Adjacency state is now down. up Adjacency state is now up. reason Reason why the adjacency state changed to down. o exceeded maximum svc adjacencies Support: End,L2 (DA circuits only) Generated when there is no free adjacency on which to establish an SVC for a new destination. o id reachability change Support: All Generated when an ID is added to or removed from the endnodeID status of an adjacency on this circuit. For end nodes this event is generated for point-to-point links only. Arguments: adjacency Name of the adjacency to which the event refers. name adjacent Node IDs of the adjacent node. node reason Reason why the adjacency state changed to down. o initialization failure Support: All Generated when an attempt to initialize with an adjacent node fails, either because of version skew or area mismatch. Arguments: adjacent Node IDs of adjacent nodes. node reason Reason why the event was generated. See possible reasons described under the adjacency state change event. o ip adjacency state change Support: IP Generated when the status attribute state of a routing circuit ip adjacency entity belonging to this circuit changes from up (or up/dormant) to some other value, or the reverse. Arguments: neighbor IP address of the neighbor. IP address new IP New state of the IP adjacency. adjacency state up Either up or up/dormant down Any other state reason Reason for the state change. o ip fragmentation failure Support: IP Generated when an IP packet that requires fragmentation in order to be transmitted has an IP header that requests "do not fragment." Arguments: destination Destination IP address of the IP packet. IP address source IP Source IP address of the IP packet. address o irrecoverable svc failure Support: All Generated when recall count becomes equal to maximum call attempts. This attribute is supported only if the circuit type is x25 static outgoing. reason Reason why the adjacency state changed to down. o LAN L1 designated router change Support: L1,L2 Generated when the local node either elects itself or resigns as the LAN level 1 designated router on this circuit. Argument: designated New state of the designated router. router change elected Router state is now elected. resigned Router state is now resigned. o LAN L2 designated router change Support: L2 Generated when the local node either elects itself or resigns as the LAN level 2 designated router on this circuit. Argument: designated New state of the designated router. router change elected Router state is now elected. resigned Router state is now resigned. o LAN phaseiv designated router change Support: L1,L2 Generated when the local node either elects itself or resigns as the LAN Phase IV designated router on this circuit. Argument: designated New state of the designated router. router change elected Router state is now elected. resigned Router state is now resigned. o redirect discard Support: End Generated when a Redirect packet is discarded because of insufficient cache space. o rejected adjacency Support: All Generated when an attempt to create a new adjacency fails because of insufficient resources. Arguments: adjacent Node IDs of adjacent nodes. node reason Reason for the failure. See possible reasons described under the adjacency state change event. o rejected ip adjacency Support: IP Generated when an attempt to automatically create an IP adjacency to an IP router fails because of lack of resources. Arguments: neighbor IP address of the neighbor. IP address reason Reason why the attempt failed. See the description of the Reason argument of the IP Adjacency State Change event. o rip error received Support: L2,IP Generated when any kind of error is detected in a received RIP packet. This event is generated only if the routing entity's characteristic routing protocols supported includes the value RIP. Arguments: neighbor IP address of the neighbor. IP address RIP reason Type of error that was detected in the RIP packet. format error version skew RIP RIP version number of the RIP packet. This argument version is present only if the RIP Reason is Version Skew. o verification reject Generated when a verification attempt fails. 3 egp_group 4 egp_neighbor o error message received Support: L2,IP Generated when an EGP error response message is received. Arguments: neighbor IP address of this neighbor. ip address reason Reason why the error message occurred. autonomous system number rejected bad EGP data field format bad EGP header format excessive polling rate no response reachability information unavailable o error message sent Support: L2,IP Generated when an EGP error response message is sent. Arguments: neighbor IP address of this neighbor. ip address reason Reason why the error message occurred. See the description of the Reason argument of the Error Message Received event. o received message discard Support: L2,IP Generated when a received EGP message is discarded for some reason. Arguments: neighbor IP address of this neighbor. ip address reason Reason why the error message occurred. See the description of the Reason argument of the Error Message Received event. o send message discard Support: L2,IP Generated when an EGP message for transmission is discarded for some reason. Arguments: neighbor IP address of this neighbor. ip address reason Reason why the error message occurred. See the description of the Reason argument of the Error Message Received event. o start Support: L2,IP Generated when a start command completes successfully. Argument: neighbor IP address of this neighbor. ip address o state change Support: L2, EGP Generated when the status attribute egp state changes to some other state. Argument: neighbor IP address of this neighbor. ip address o stop Support: L2,IP Generated when a stop command completes successfully. Argument: neighbor IP address of this neighbor. ip address 2 session_control o access control violation Generated each time that Session Control detects an access control violation. The arguments provide information about the source and destination. Arguments: destination End-user specification of the destination account. destination Destination account information. account destination Destination user name. user node name Name of the source node. nsap Network address of the source node. address source End-user specification at the source node. o backtranslation deletion Generated each time that a backward translation name is discarded because of an irrecoverable error. Arguments: name Deleted name. reason DECdns error that caused the deletion. o bad backtranslation link Generated when an attempt to access a backward translation soft link results in a clerk exception indicating that some attribute in the soft-link chain was improperly configured. Arguments: name Name improperly configured. reason Reason for the exception. o dangling link Generated each time an attempt to access an attribute of a backward translation soft link results in a clerk. Dangling exception. Argument: name Full name of the soft link. o deleted maintained object Generated each time that a tower maintenance entity is discarded because of an irrecoverable error. Arguments: client Network management name of the user who issued the keepmehere call that resulted in the creation of this entity. creation Time this entity was created. time higher Set of higher towers that was passed in the towers keepmehere that created this entity. last A DECdns error code that indicates the reason for the failure last update failure. reason last Time of the last successful update to the DNA$Towers successful attribute. update last Time that the last attempt to update the DNA$Towers update attribute completed. completed last Time that the last attempt to update the DNA$Towers update attribute was initiated. started name Full name of the deleted entity. reason DECdns error that caused the deletion. uid Entity's unique identifier, generated when the entity is created. update Generated each time that an attempt to update a failures DNA$Towers attribute fails. update Generated each time that an attempt to update a successes DNA$Towers attribute succeeds. o verification failure Generated each time that session control is unable to verify that the addresses and protocols of an incoming connection request are consistent with the DNA$Towers attribute of the source node name. Arguments: address Unverified protocol address sequence. node Full name of the source node. 3 backtranslation_softlink o deleted The given backtranslation softlink subentity instance was deleted. Argument: creation Time this subentity was created. time network Network entity title for this soft link. entity title state Status of the entity. target Target for soft link. update Times an update for this subentity failed. failures update Times an update for this subentity succeeded. success o update failure Signals an attempt to create, delete, or retarget a backtranslation has failed. Argument: reason Reason for the failure. 3 tower_maintenance o update failure Generated each time that an attempt to update a DNA$Towers attribute fails. 2 token_ring_(Tru64_UNIX) 3 station o abort transmitted Station has transmitted an abort delimiter. o auto-removal failure Self-test failed following a beacon auto-removal process. o burst error Absence of transitions on the physical media. o frame copied error This station received a frame addressed to its MAC address with the A and C bits set. o internal error Station has detected an internal error. o line error CRC error or Manchester Violation detected in a token or frame with the E bit = 0. o lobe wire fault Short or open circuit detected on cable. o lost frame error TRR timer expired while this station was transmitting. o receive data overrun A receive overrun hardware error was detected. o remove received Remove ring station MAC frame received. o ring beacon initiated The station started the beacon process. o ring beaconing Beacon MAC frames being sent or received. o ring poll error Failure to properly set A and C bits during the ring poll process. o ring recovery Station is receiving or transmitting claim token MAC frames. o route discovery failure Route discover timer expired. o selftest failure The implementation specific self-test procedures have detected a failure. o signal loss Loss of signal on the physical media. o single station The only station participating in the ring poll process. o soft errors reported Soft error report MAC frame sent to ring error monitor. o station buffer unavailable No buffer was available to receive a frame. o token error This station, as active monitor, has had to transmit a new token following an error condition. o transmit failed Failure to transmit operation other than underrun. o transmit underrun Transmit failed due to underrun. o unrecognized individual pdu destination An individually addressed frame with unrecognized DSAP or protocol ID. o unrecognized multicast pdu destination A globally addressed frame with unrecognized DSAP or protocol ID. o user buffer unavailable Data link user did not supply a receive buffer. 2 x25_access o incoming call blocked Generated when an incoming call from the X.25 Protocol module (or from the X.25 Client module in an accessing system) is blocked and cleared by the X.25 Access module's security mechanisms. Arguments: filter Name of the selected filter. group Name of the x25 protocol group entity corresponding to the BCUG that matches the CUG number specified in the Call packet. This argument is present only when the call is delivered via a bilateral closed user group. inbound Name of the DTE class associated with the incoming call by the x25 protocol dte entity. security This DTE class identifies the security dte class entity dte class to be used for remote DTE matching. remote dte Name of the remote dte entity whose remote address prefix was selected by the matching algorithm. This argument is not present when the call is delivered via a bilateral closed user group. sending DTE address of the calling DTE. This argument is not dte present when the call is delivered via a bilateral closed user group. o incoming call failed Generated when an incoming call from the X.25 Protocol module (or from the X.25 Client module in an accessing system) is cleared by the X.25 Access module. Arguments: group Name of the x25 protocol group entity corresponding to the BCUG that matches the CUG number specified in the Call packet. This argument is present only when the call is delivered via a bilateral closed user group. Since group entities do not exist at accessing systems, this argument is present only at gateway systems. reason Reason why the call failed. insufficient The X.25 Access module has insufficient resources resources to handle the call. no filters The incoming call failed to match any of the active filters. security The dte class of the incoming call has dte class an invalid security DTE class associated not found with it. security The filter on which the incoming call filter not was matched has an invalid security found filter associated with it. security Name of the security dte class entity that was dte class referenced by the selected dte class entity. This argument is present only if the reason for the event is security dte class not found. security Name of the security filter entity that was filter referenced by the selected dte class entity. This argument is present only if the reason for the event is security filter not found. sending DTE address of the remote DTE. dte o in use filter deleted Generated when an active filter has been deleted by the use of the NCL delete x25 access filter command. Arguments: filter The name of the deleted filter. listener The name of the application associated with the filter. o outgoing call blocked Generated when the X.25 Access module's security mechanisms prevent a client from making an outgoing call. Arguments: blocked by Specifies where the security blocking occurred. gateway Blocked by the gateway system. security local Blocked by the accessing system. security client Name of the entity that made the call. destination Specifies the called DTE address. This argument is dte not present if the call specifies a bilateral closed user group. dte class Name of the DTE class specified in the call. This argument is not present if the call specifies a bilateral closed user group. group Name of the x25 protocol group entity specified in the call. This argument is present only if the call specifies a bilateral closed user group. Since group entities do not exist at accessing systems, this argument is present only on gateway systems. remote DNS name of the entity that made the call. If the port call is blocked by gateway security, this identifies the X.25 access client on the accessing system. This argument is mandatory only if the client of X.25 access is the X.25 Server module. security Name of the remote dte entity whose remote address DTE class prefix was selected by the matching algorithm. This remote DTE argument is not present if the call is made to a bilateral CUG. source (OpenVMS) Name of the entity that made the call. This identifies the client of X.25 Access at the accessing system when the call is blocked by security on a gateway system. This argument is mandatory only when the client of X.25 Access is the X.25 Server module. o outgoing call configuration error Generated when a call fails because of misconfiguration of the security databases. Arguments: reason Specifies why the call failed. security The DTE class of the outgoing call dte class must have a valid security DTE class not found associated with it. security Name of the security dte class entity that was dte class referenced by the selected dte class entity. o port terminated Generated whenever a port is closed. The event arguments simply reflect the attributes of the port at the time it was terminated. Arguments: call Name of the x25 access filter entity that matched association an incoming call, or the name of the x25 access template entity used in making an outgoing call. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. call Direction of the call on an SVC. direction incoming The call is an incoming call. outgoing The call is an outgoing call. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. calling Calling NSAP address that is carried transparently address in an incoming or outgoing call packet. This attribute extension is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. calling dte Calling DTE address in a call request or incoming address call packet (depending on the value of the status attribute call direction). This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. channel Channel number of the underlying virtual circuit. This status is valid only if the port is at a gateway system and the status attribute state is not open. client Name of the entity that made or accepted the call. data octets Number of data octets received at the port. received data octets Number of data octets sent by the port. sent dte class Name of the DTE class to which the DTE of the underlying virtual circuit belongs. This attribute is supported only if the status attribute state is not set to open. fast select Specifies whether fast select is in operation for the call. fast select Fast select in operation. no fast select Fast select not in operation. not specified Facility not requested. with response Fast select with response in operation. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. group Name of the x25 protocol group entity (that is, CUG) associated with an incoming or outgoing call. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. incoming Packet size, in octets, for incoming data on a virtual packet circuit. This attribute is supported only if the status size attribute state is not set to open. incoming Throughput class for incoming data on a virtual throughput circuit. size incoming Window size for incoming data on a virtual circuit. window size local dte Name of the DTE entity associated with the call. originally If a call is redirected, this is the DTE address called from which the call was redirected; otherwise, address the address is null. This status is valid only if the status attribute redirect reason is not [not] redirected. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. outgoing Packet size, in octets, for outgoing data on a packet virtual circuit. This attribute is supported only size if the status attribute state is not set to open. outgoing Throughput class for outgoing data on a virtual throughput circuit. class outgoing Window size for outgoing data on a virtual circuit. window This attribute is supported only if the status size attribute state is not set to open. pdus Number of pdus received at the port. received pdus sent Number of pdus sent by the port. protocol First four octets of call data in the call. This identifier attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. pvc Name of the pvc to which this port belongs. This attribute is present only if the status attribute port type is set to permanent. redirect Specifies whether a call has been redirected and, reason if so, the reason for the redirection. busy The call has been redirected because the original destination was busy. not The call has not been redirected. redirected out of The call has been redirected because the order original destination was not operational. systematic The call has been redirected because all calls to the original destination have been systematically redirected. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. reference Time at which the port was created (if the time circuit is a PVC), or the time at which the port was first used to send or receive a call at the X.25 user interface (if the circuit is an SVC). remote Name of the peer entity with which this port is port communicating. reserved If the port is associated with a reserved Logical Channel Number (LCN), this specifies the name of the local DTE entity on which the LCN is reserved. A null string indicates that the port is not associated with a reserved LCN. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. reverse Specifies whether reverse charging is in operation for charging the call. This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. segments Number of segments of data sent by this port. sent segments Number of segments of data received by this port. received state Status of the x25 access port entity. called A call has been received and taken by a user. calling A user is making a call. cleared A Clear Indication or Clear Confirmation packet has been received, or the X.25 Protocol module has detected an error. cleared by The port was cleared by network management. directive clearing A user has requested that the call should be cleared. no communi- Communications with the PSDN have been lost. cation open The port is open. running The associated virtual circuit is available for data transfer. synchronizing A user has requested a reset, but the network has not yet responded with a Reset Confirmation or Reset Indication packet. unsynchronized A Reset Indication packet has been received, or the X.25 Protocol module has detected an error and the user has not yet responded with a reset request. target Called NSAP address that is transparently carried in address an incoming or outgoing call packet. This attribute is extension supported only if the status attribute port type is set to switched and the status attribute state is not set to open. target dte Called DTE address in a call request or incoming call. address This attribute is supported only if the status attribute port type is set to switched and the status attribute state is not set to open. type Specifies that the port represents an SVC. switched The circuit is an SVC. permanent The circuit is a PVC. o pvc access blocked Generated when a client of X.25 Access is not allowed to access a PVC. Arguments: blocked by Where the blocking occurred. gateway At the gateway system security local At the accessing system security client Name of the entity that attempted to use the pvc. pvc Name of the pvc. source Name of the entity that attempted to use the PVC. This identifies the client of X.25 Access module at the accessing system when the call is blocked by security on a gateway system. This argument is mandatory only when the client of the X.25 Access module is the X.25 Server module. 2 x25_client_(OpenVMS) o server connect rejected Generated when a requested connection to an X.25 gateway system is rejected. Arguments: application Address of the X.25 application that has rejected a connect request. node Address of a node that has rejected a connect request. server Address of the X.25 server that has rejected a connect request. o session control unavailable Generated when the X.25 Client module detects the absence of the Session Control module, or when it detects that Session Control is disabled. Arguments: module Whether the Session Control module is unavailable or extant merely disabled. If false, the Session Control module is unavailable; if true, it is disabled. If false, the Session Control Port State argument is null. session State of the Session Control port. control port state null The Session Control module is unavailable. off The Session Control port is in the Off state. restricted The Session Control port is in the Restricted state. shut The Session Control port is in the Shut state. 2 x25_protocol 3 dte o diagnostic packet received Generated when the DTE receives a diagnostic packet from the network. Arguments: cause Cause code provided by the DCE on reset. channel Concatenated logical channel group and logical channel number of the virtual circuit associated with the event. diagnostic Diagnostic code provided by the DCE on reset. o dte down Generated when the status attribute state changes from on to off, synchronizing, or unsychronized. Arguments: configuration Specifies whether or not there has been a error configuration error. lapb link DTE state has changed due to the deletion of the deleted underlying link service provider entity. o dte up Generated when status attribute state changes to on from off, synchronizing, or unsychronized. Argument: config- Specifies the DTE configuration. uration dce The DTE has initialized as a packet-mode DCE. dte The DTE has initialized as a packet-mode DTE. Negotiated The DTE has negotiated to operate as a dce packet-mode DCE. Negotiated The DTE has negotiated to operate as a dte packet-mode DTE. o illegal packet received Generated when the DTE receives an illegal packet from the network. Arguments: call time Time at which the call request was made. ccitt CCITT state. state channel Concatenated logical channel group and logical channel number for the virtual circuit associated with the event. direction Direction of the call. incoming The call was incoming. outgoing The call was outgoing. failure Specifies why the packet was flagged as illegal. reason header Error in the received block header. error invalid Invalid general format identifier. gfi invalid The packet is invalid in the current state state of the protocol. no No interrupt packet was sent. interrupt sent too long The packet is too long. too short The packet is too short. unacknowledgeThere is an outstanding interrupt. interrupt unrecognizedThe packet is unrecognizable to the DTE. header Header contents of the packet that caused the event. packet Type of illegal packet. type remote dte Address of the DTE that is the source of an incoming call or the destination of an outgoing call. o network initiated reset Generated when the DTE receives a Reset packet from the network. Arguments: cause Cause code provided by the DCE on reset. ccitt CCITT state. See possible reasons described under the state illegal packet received event. channel Concatenated logical channel group and logical channel number of the virtual circuit associated with the event. diagnostic Diagnostic code provided by the DCE on reset. direction Direction of the call. incoming The call was incoming. outgoing The call was outgoing. o network initiated restart Generated when the DTE receives a Restart packet from the network. Arguments: cause Cause code provided by the DCE on reset. ccitt CCITT state. See possible reasons described under the state illegal packet received event. channel Concatenated logical channel group and logical channel number of the virtual circuit associated with the event. diagnostic Diagnostic code provided by the DCE on reset. o protocol error detected Generated when a protocol error is detected. Arguments: call time Time at which the call request was made. ccitt CCITT state. See possible reasons described under the state illegal packet received event. channel Concatenated logical channel group and logical channel number for the virtual circuit associated with the event. failure Reason for the protocol error. reason bad p(r) Invalid receive packet sequence number received received. bad p(s) Invalid transmit packet sequence number received received. invalid Invalid Logical Channel Number. lcn invalid Error in negotiated or requested packet packet size. size invalid Error in negotiated or requested throughput throughput class. class invalid Error in negotiated or requested window window size. size no fast Fast Select is not supported. select receiver Data received while in receiver not not ready ready state. header Header contents tht caused the event. remote dte Address of the DTE that is the source of an incoming call or the destination of an outgoing call. o reject packet received Generated when the DTE receives a Reject packet from the network. Arguments: call time Time at which the call request was made. ccitt CCITT state. See possible reasons described under the state illegal packet received event. channel Concatenated logical channel group and logical channel number of the virtual circuit associated with the event. direction Direction of the call. incoming The call was incoming. outgoing The call was outgoing. remote dte Address of the DTE that is the source of an incoming call or the destination of an outgoing call. o retry failed Generated when one of the DTE's maximum retry counts has been reached. Arguments: ccitt CCITT state. See possible reasons described under the state illegal packet received event. channel Concatenated logical channel group and logical channel number for the virtual circuit associated with the event. remote dte Address of the DTE that is the source of an incoming call or the destination of an outgoing call. retry Specifies which retry counter has generated the event by reaching its maximum value. clear The maximum clear attempts counter. reset The maximum reset attempts counter. restart The maximum restart attempts counter. o switched virtual circuit failed Generated when an incoming or outgoing call fails in the setup or data phase. Arguments: call time Time at which the call request was made. cause Cause code provided by the DCE on reset. channel Concatenated logical channel group and logical channel number for the virtual circuit associated with the event. diagnostic Diagnostic code provided by the DCE on reset. direction Direction of the call. incoming The call was incoming. outgoing The call was outgoing. failure Reason why the circuit failed. reason call The call was cleared by an invocation of cleared the interface function. call Call collision occurred. collision call The call timer expired for an outgoing timeout call attempt. dte The local DTE was disabled by network disabled management. level 2 A failure occurred at the Frame level failure link or below. local The X.25 Access module rejected an reject incoming call attempt. network A Clear packet with a network cause code clear was received. no Insufficient resources to handle call. resources no taker Incoming call attempt rejected on timeout with no response from X.25 Access module. remote Disconnect initiated by network or reject remote DTE. restart A Restart packet was sent by the DCE. received security An implementation-specific access criterion was violated. remote dte Address of the DTE that is the source of an incoming call or the destination of an outgoing call. 3 pvc o pvc failed Generated when an allocated PVC fails during the data phase. Arguments: cause Cause code provided by some DCEs on some failures. diagnostic Diagnostic code provided by some DCEs on some failures. failure Why the PVC failed. reason DTE The local DTE was disabled by network disabled management. level 2 A failure occurred at the Frame level failure link or below. PVC The x25 protocol dte pvc entity has been deleted deleted by network management. restart Restart initiated by network or remote DTE, or sent by this DTE. 2 x25_relay_(Alpha) 3 client o connection failed Generated when a connection cannot be established. Arguments: call accept Error returned when attempting to accept the reason incoming call. This argument is present only if Reason is Call Accept Failure. cleared by directive invalid parameter no such port service not available destination DTE address of the called DTE. DTE destination Called Address Extension supplied in the Call packet. nsap outgoing Error returned when attempting to make the outgoing failure call. This argument is present only if Reason is reason Outgoing Call Failure. called address not reachable cleared by directive destination not known DTE class members not active DTE class not known DTE class not specified incompatible reserved lcn invalid parameter no such port no such template security failure service not available transit not allowed reason Whether the connection failed at the incoming or outgoing stage. call accept The client could not accept the failure incoming call. outgoing The client could not make the call failure outgoing call. sending DTE address of the calling DTE. DTE sending Calling Address Extension supplied in the Call nsap packet. o connection lost Generated when a connection that has been successfully etablished is abnormally terminated. Arguments: cause X.25 cause code provided by the clearing DTE. Only present if the Reason argument is Calling DTE Clear or Called DTE Clear. destination DTE address of the called DTE. DTE destination Called Address Extension supplied in the Call packet. nsap diagnostic X.25 diagnostic code provided by the clearing DTE. Only present if the Reason argument is Calling DTE Clear or Called DTE Clear. network Reason why the connection was lost. This argument is error present only if reason is network error. reason reason Reason for the loss of the connection. calling The local call was abnormally DTE clear terminated. network The cause of the connection loss is error given by network error reason. called DTE The remote call was abnormally clear terminated. sending Specifies the DTE address of the calling DTE. DTE sending Specifies the Calling Address Extension supplied in nsap the Call packet. 3 pvc o connection lost Generated when a successfully established PVC connection fails for some other reason than being disabled. Argument: reason Error returned by the X.25 Access module when notifying the X.25 Relay module of the disconnection. o retry limit exceeded Generated when an attempt to set up a PVC connection fails. Arguments: local pvc State of the local end of the PVC connection. status relayed State of the relayed end of the PVC connection. pvc status 2 x25_server o client connect failed Generated when the X.25 server is unable to make a connection to an X.25 client (or to any of an alternative set of X.25 clients if the service nodes characteristic is supported for the x25 server client entity). Arguments: client Full name of the x25 server client entity. nodes The node or set of nodes associated with the x25 server client entity. application Application type in the client entity. o session control unavailable Generated when the X.25 server detects the absence of the Session Control module or when it detects that the state of Session Control is not set to on. Arguments: module True or false. Set to false when the X.25 Server extent cannot detect the presence of Session Control. When set false, the value of the session control port state argument is always null. session Null, off, shut, or restricted. Reflects the state control returned by the Port State End User Interface when port state the value of the module extent argument is set true. 2 xot_(OpenVMS_Alpha) 3 sap o sap state changed The XOT SAP state has changed. The new SAP state (on, off, or connecting to PWIP) is an argument for this event. o sap inbound connect failed Indicates that an inbound connection attempt failed. The event arguments are: failure reason, remote ip address, remote port number, and pwip error code. Possible connect failure reasons are: Remote System Unreachable Connection Rejected Connection Timed Out No Match for SAP Link Maximum Connections Exceeded Not Connected to PWIP PWIP Error No Reason Specified 4 link o link state changed The XOT SAP LINK state has changed. The new XOT SAP LINK state (on or off) is an argument for this event. o outbound connect failed Occurs when an attempt to establish an outbound connection with a remote system fails. The event returns the following arguments: Failure Reason, Remote IP Address, Remote Port Number, and if the Failure Reason argument indicates a PWIP Error, PWIP Error Code. The Failure Reason agrument indicates why the connection could not be made, the argument takes one of the following values: Remote System The XOT system could not reach the Unreachable requested remote system. Connection The XOT system was able to reach the Rejected remote system. However, the remote system denied the connection request. PWIP Error During the connection establishment process the XOT system received an unexpected error from the PWIP software it uses. No Reason The XOT system could not establish a Specified connection with the requested remote system. No additional information is available. o protocol error Indicates an error occurred in the XOT protocol during a XOT protocol exchange with the remote system. The event returns the following arguments: Error Reason, Remote IP Address, Remote Port Number, and Received PDU. The Error Reason argument indicates what type of protocol error was detected; the argument takes one of the following values: Invalid XOT The XOT system received a PDU apparently Header destined for the XOT software, but the XOT header was not valid. Invalid PVC While attempting to establish a PVC Setup Packet connection with the remote system, the remote system returned an invalid response PDU. This error can also occur if the remote system attempts to establish a PVC connection with the local system and the PVC connection PDU is invalid.