______________________________________________ DEC Network Integration Server Event Messages Software Version: DECNIS V3.1 __________________________________________________________ While Digital believes the information included in this publication is correct as of the date of publication, it is subject to change without notice. Possession, use, or copying of the software described in this documentation is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. © Digital Equipment Corporation 1992, 1995. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: DDCMP, DEC, DECmcc, DECnet, DECNIS, OpenVMS and the DIGITAL Logo. AppleTalk is a registered trademark of Apple Computer, Inc. MS-DOS is a registered trademark of Microsoft Corporation. NetWare is a registered trademark of Novell, Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. The Digital implementation of OSPF is an adaptation of the OSPF implementation developed by the University of Maryland, College Park, Maryland. Copyright (c) 1989, 1990, 1991, 1992, University of Maryland. Permission to use, copy and modify the software and its documentation is granted provided that this copyright notice and these terms shall appear in all copies of the software and its supporting documentation. The origin of this software may not be misrepresented, either by explicit claim or by omission. The Software is provided "AS IS" and without any express or implied warranties, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT, Version 2.1. 1 Introduction Throughout this document, the DEC[TM] Network Integration Server is referred to as the DECNIS[TM]. This document lists the event messages that can be generated by the DECNIS. For each event, there is a brief description which includes: o The name of the module entity that produces the event message. o Why the event was logged. o What to do when the event is logged (for events indicating problems). Many of the event descriptions refer you to sections of the DEC Network Integration Server Problem Solving manual. For more information about events and event arguments, see the NCL reference documentation for your load-host operating system. For information about using the Common Trace Facility (CTF), see the Common Trace Facility (CTF) Use manual. The event messages are listed in alphabetical order. 1 2 Event Messages Access Control Violation ------------------------ This event is generated by a SESSION CONTROL entity when session control detects an access control violation. An inbound connection is rejected if the specified username and password do not match those set up either for the SESSION CONTROL entity or for the target application. See the DEC Network Integration Server Configuration and Loading manual for details of how to set the username and password. Active Link Deleted ------------------- This event is generated by an ATM MULTIPROTOCOL ENCAPSULATION entity when an active link is deleted due to a management request. The name of the link which was deleted is supplied. This event is for information only. Activation Failure ------------------ This event is generated by a SUPERVISOR GROUP entity when an attempt to establish a backup circuit fails. Activation State Change ------------------------ This event is generated by a SUPERVISOR GROUP entity when a backup circuit is activated or deactivated. A backup circuit is activated when a primary circuit fails. 2 Address Changed --------------- This event is generated by a NODE entity when a Tower set representing the node's address changes. This occurs during the normal operation of session control. The old and new addresses are displayed. The node automatically attempts to update DNS with the new address. Note however, some applications may fail until the new address is updated in DNS. Address Unreachable Packet Discard ---------------------------------- This event is generated by a ROUTING NETWORK PROTOCOL entity when an AppleTalk or IPX packet is discarded because the destination is unreachable. Compare the DESTINATION and the PATH attributes of the DECNIS and the system that originated the packets. If you are using AppleTalk[R], refer to Chapter 10 of the DEC Network Integration Server Problem Solving manual for more details. If you are using NetWare[R] IPX, refer to Chapter 11 of the DEC Network Integration Server Problem Solving manual for more details. Address Unreachable PDU Discard ------------------------------- This event is generated by a ROUTING entity when a PDU (Protocol Data Unit) is discarded because the destination node is unreachable. Follow the procedures in Chapter 4 of the DEC Network Integration Server Problem Solving manual. 3 Adjacency State Change ---------------------- This event is generated by a ROUTING CIRCUIT entity when the state of a ROUTING CIRCUIT ADJACENCY entity belonging to the circuit changes from Up to Down, or from Down to Up. The new state of the node (Up or Down) is displayed with the event. If the state of an adjacency changes from Up to Down, there may be problems reaching destination nodes. Perform the loopback tests described in Chapter 12 of the DEC Network Integration Server Problem Solving manual. Aged IP Packet Discard ---------------------- This event is generated when an IP packet is discarded because the maximum number of hops has been exceeded. That is, the packet has passed through the maximum number of routers allowed to reach its destination. 4 Aged Packet Discard ------------------- This event is generated by a ROUTING NETWORK PROTOCOL entity when an AppleTalk or IPX packet is discarded. This occurs because the time-to-live or the hop count of the packet has been exceeded. This can occur because of a routing loop or because a network has grown too large. Setting up virtual circuits may reduce the number of hops on the network. However, care must be taken as this could result in more routing loops. Aged PDU Discard ---------------- This event is generated by a ROUTING entity when the lifetime of a data PDU (Protocol Data Unit) has expired. This event is displayed when: o The value of the LIFETIME attribute of a ROUTING entity is set too low for originating PDUs. The lifetime value of the PDUs must be greater than the maximum number of hops in any path in the network, plus the maximum lifetime. To reset the lifetime value of the PDUs, refer to the NCL reference documentation for your load-host operating system or NCL online help. o The manual routing information is defined incorrectly for the destination path. This may result in the PDU looping. Alignment Error --------------- This event is generated by a CSMA-CD STATION entity 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). 5 Attempt to Exceed Maximum Sequence Number ----------------------------------------- This event is generated by a ROUTING entity when an attempt is made to increase the sequence number of a Link State PDU beyond the maximum allowed sequence number. Report the event to Digital (refer to Chapter 14 of the DEC Network Integration Server Problem Solving manual). Backtranslation Deletion ------------------------ This event is generated by a SESSION CONTROL entity when an attempt to create or update a backtranslation soft link has failed. This may occur for one of the following reasons: o The backtranslation directory does not exist. o The backtranslation directory is protected by access rights. If you do not have access rights, you cannot create a directory or soft link in the backtranslation directory. This event also displays details of the DECdns error that caused the event. Refer to the DECdns documentation for your load-host operating system for details of the error and more information. 6 Bad Hello Limit Exceeded ------------------------ This event is generated by the BRIDGE entity. It occurs when the threshold for incorrect spanning tree messages is exceeded. That is, the DECNIS has received too many incorrect spanning tree messages. The event indicates which bridge sent the message that caused the threshold to be exceeded. If this event is generated, the problem could be with either of the following: o The configuration of the bridges in the extended LAN. o A hardware fault on a bridge connected to the LAN of the DECNIS. Use CTF to find details of the spanning tree messages causing the LAN topology to change. Bad Packet Received ------------------- This event is generated by the ROUTING CONTROL PROTOCOL LOGICAL CIRCUIT entity when the DECNIS receives a badly formatted OSPF packet. If the packet is not too badly formatted, the Neighbor IP Address argument may state which system sent the faulty packet. Became Root ----------- This event is generated by a BRIDGE entity when the DECNIS is elected as the root bridge. If this event occurs frequently, there may be a problem with the configuration of the bridges on the extended LAN. Use CTF to find details of the spanning tree messages causing the LAN topology to change. Block Check Error ----------------- This event is generated by an FDDI STATION LINK entity when a frame is received with a bad frame check sequence. 7 Buffer Too Small ---------------- This event is generated by a DDCMP LINK LOGICAL STATION entity each time a message is received whose Data field is larger than the buffers available on the local station. This event indicates a communications problem between the remote station and local station. This could be caused by a noisy communications line. However, if the problem persists, contact the system manager of the remote station to check that it is running the DDCMP[TM] protocol. If this is not causing the problem, check that the data link clients are compatible. Buffer Unavailable Error ------------------------ This event is generated by an HDLC LINK entity or a LAPB LINK entity when a frame is discarded because there is no receive buffer available. This indicates an overload on the point-to-point connection to the remote station. If this event is generated, increase the value of the RECEIVE BUFFERS attribute. See the NCL reference documentation for your load-host operating system or NCL online help for more information. Cable Detected -------------- This event is generated by a MODEM CONNECT LINE entity when an adapter cable is connected to the DECNIS. The cable type is displayed. This event is purely for information and no action is required. Cable Fault ----------- This event is generated by a MODEM CONNECT LINE entity when the adapter cable connected to the DECNIS has been removed, or when the wrong adapter cable is fitted. Replace the adapter cable, or see the Installation and Service Manual for your hardware system for more information on adapter cables. 8 Card Removed ------------ This event is generated by a DEVICE UNIT entity when a card is removed from the system. This event is purely for information and no action is required. Carrier Check Failure --------------------- This event is generated by a CSMA-CD STATION entity when a transmission fails for one of the following reasons: o The data link did not sense the receive carrier signal that must accompany transmission of a frame. o 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 the transceiver cable. See the Installation and Service Manual for your hardware system for details of hardware problem solving procedures. 9 Change Confidence ----------------- This event is generated by an EVENT DISPATCHER OUTBOUND STREAM entity or an EVENT DISPATCHER SINK INBOUND STREAM entity. It is issued with a value of TRUE or FALSE. o If the displayed value is FALSE then the transport protocol has lost its connection to the sink node. The sink node will automatically try to recover the connection. If it cannot recover it will log a Disconnect event. o If the displayed value is TRUE then a lost connection from the transport protocol to the sink node has been recovered. Change Filter ------------- This event is generated by an EVENT DISPATCHER OUTBOUND STREAM entity or an EVENT DISPATCHER SINK entity. It occurs when a filter on the outbound stream has been changed. It displays the old and new values for the filter. This event is purely for information and no action is required. Channel State Transition ------------------------ This event is generated by an FRBS CHANNEL entity when the channel is enabled or disabled. The new state is displayed with the event. This event is purely for information and no action is required. 10 Checksum Failure ---------------- This event is generated by an OSI TRANSPORT LOCAL NSAP REMOTE NSAP entity whenever there is a checksum error in a call confirm packet. This event is purely for information and no action is required. Circuit Change -------------- This event is generated by a ROUTING CIRCUIT entity when the state of the circuit changes from On to Off or from Off to On. The new circuit state is displayed with the event. If the state of the circuit changes from On to Off unexpectedly, follow the procedures in Chapter 4 of the DEC Network Integration Server Problem Solving manual. Client Connect Failed --------------------- This event is generated by an X25 SERVER entity when the X.25 Server is unable to make a connection to an X.25 Client. See Chapter 7 of the DEC Network Integration Server Problem Solving manual. Client Unreachable Packet Discard --------------------------------- This event is generated by a ROUTING NETWORK PROTOCOL entity when an AppleTalk or IPX packet is discarded. This occurs when there is no client on the local system of the type specified in the packet header. The header describes the protocol, port or socket type required. This might occur if a system has been misconfigured and is sending packets to the DECNIS of a protocol type that the DECNIS does not support. The socket address in the event message should indicate which protocol is required. This may help you to determine which system has been misconfigured and is sending the packets to the DECNIS. 11 Configuration Change -------------------- This event is generated by an FDDI STATION entity when the internal configuration of the station changes. This occurs when a physical port on a dual attachment station (DAS) changes to or from the "In Use" state. If the state changes from In Use to another state, there may be a fault with the connection on that port. If the state changes to In Use, a connection has been established on the port and the event is purely for information. To check the state of the port, enter the following command: NCL> SHOW NODE decnis FDDI STATION station-name PHY PORT - _NCL> port-name STATE Configuration Error ------------------- This event is generated by a ROUTING entity when a configuration error is detected. The error is usually due to insufficient internal resource allocation. The event indicates the reason for the error, for example, Insufficient Endsystem Adjacencies. To allocate more resources, look at the Peak characteris- tic for the resource by entering the following command: NCL> SHOW NODE decnis ROUTING ALL STATUS Now set the Maximum characteristic to a higher value than the Peak value by entering the following command: NCL> SET NODE decnis ROUTING max-chara value where max-chara is the Maximum resource characteristic and value is the new value. For example, NCL> SET NODE decnis ROUTING MAXIMUM ENDSYSTEM ADJACENCIES 900 12 Note, the following resources are set manually and therefore have no Peak characteristic: o Manual Adjacencies o Reachable Destinations o IP Reachable Destinations Check with the system manager to determine the values for these resources. 13 Connection Failed ----------------- This event is generated by an X25 RELAY CLIENT entity when the DECNIS could not make a connection to a remote DTE. The reasons for the failure are indicated. Refer to Section 7.4 of the DEC Network Integration Server Problem Solving manual for a description of the reasons and the next action to take. 14 Connection Lost --------------- This event is generated by an X.25 RELAY CLIENT entity or an X.25 RELAY PVC entity. It is generated when a connection is broken between the DECNIS and a remote DTE. This event is purely for information. Connection State Transition --------------------------- This event is generated by an FRBS CHANNEL CONNECTION entity when the state of the connection changes. The new state is displayed with the event. This event is purely for information and no action is required. Control Protocol Reject Message Received ---------------------------------------- This event is generated by a PPP PORT entity when a control protocol transferred through the port is not supported by the remote system. The event specifies the protocol rejected. Check that the configuration of the local and remote systems are compatible. Control Protocol State Change ----------------------------- This event is generated by a PPP PORT entity when the control protocol used by the port changes state. The new control protocol state is displayed with the event. Corrupted Hello PDU Received ---------------------------- This event is generated by a ROUTING CIRCUIT entity when an ES-IS or IS-IS Hello PDU is received that either cannot be parsed or contains an incorrect checksum. Check the PDU Header argument for details of the node sending the corrupt PDU. 15 Corrupted LSP Detected ----------------------- This event is generated by a ROUTING entity when a corrupted Link State Packet (LSP) is detected in memory. Report the event to Digital (refer to Chapter 14 of the DEC Network Integration Server Problem Solving manual). Corrupted LSP Received ----------------------- This event is generated by a ROUTING CIRCUIT entity when a corrupt Link State Packet (LSP) is received. The following information is displayed with the event: o Adjacent Node-the node IDs of the adjacent node If this event is generated frequently, the node sending the corrupted LSP may have a fault. Check the node ID from the information displayed. Corrupted Phase IV Routing Packet Received ------------------------------------------ This event is generated by a ROUTING CIRCUIT entity when a corrupt Phase IV routing packet is received. The following information is displayed with the event: o Phase IV ID-the Phase IV ID of the Phase IV routing message that caused the event to be generated. If these events are generated frequently, there may be a fault on the node sending the corrupt packet. DA Adjacency Change ------------------- This event is generated by a ROUTING CIRCUIT entity when the adjacency of a dynamically assigned circuit changes. This event is purely for information and no action is required. 16 Dangling Link ------------- This event is generated by a SESSION CONTROL entity. It is generated when the DECNIS attempts to access a soft link that does not point to anything. Usually, a soft link provides a logical link to, or an alternative name for, an entry in the DECdns namespace. Refer to the Guide to Managing DECdns and the DECdns documentation for your load-host operating system for more information. DCE Not Ready ------------- This event is generated by a MODEM CONNECT LINE entity when the modem's signal sequencing has failed. Redial the link to establish a connection. If this fails, check the modem's connections and perform loopback tests to isolate the problem (refer to Section 12.1 of the DEC Network Integration Server Problem Solving manual). Deleted Maintained Object ------------------------- This event is generated by a SESSION CONTROL entity each time that a tower maintenance entity is discarded because of an irrecoverable error. The following information is displayed with the event: o Name-the full name of the deleted object. o Reason-the DECdns error that caused the deletion. Follow the procedures in Section 2.3 of the DEC Network Integration Server Problem Solving manual. 17 Deleted Remote NSAP ------------------- This event is generated by an NSP LOCAL NSAP entity or the OSI TRANSPORT LOCAL NSAP entity whenever a remote NSAP address is deleted. A remote NSAP address will be deleted if the maximum number of stored remote NSAPs is reached, and another remote NSAP needs to be added to the store. This event is purely for information and no action is required. Destination Address Error Packet Discard ---------------------------------------- This event is generated by a ROUTING NETWORK PROTOCOL entity when an AppleTalk or IPX packet is discarded because the destination address is invalid. This indicates that a system is originating badly formed packets. Device Failure -------------- This event is generated by a DEVICE UNIT entity when a device fails. Report the problem to Digital, with the dump file (as described in Chapter 14 of the DEC Network Integration Server Problem Solving manual). Diagnostic Packet Received -------------------------- This event is generated by an X25 PROTOCOL DTE entity when the DTE receives a diagnostic packet from the network. If the LCN on which the packet is received is nonzero, this event message is an informational message and no action is required. If the LCN is zero, the PSDN is sending notification of a protocol error. In this case, this event will shortly be followed by an SVC Failed or PVC Failed event; see Chapter 4 of the DEC Network Integration Server Problem Solving manual. 18 Directed Beacon Received ------------------------ This event is generated by an FDDI STATION LINK entity when a link receives directed beacon information from another station. This indicates that there is an error on the ring and the trace process will probably be started to determine which station is at fault. Disable Stream -------------- This event is generated by an EVENT DISPATCHER OUTBOUND STREAM entity when the outbound stream has been suc- cessfully disabled. You can enable the outbound stream using NCL commands; for details of this, refer to the DEC Network Integration Server Management manual. Disconnect ---------- This event is generated by an EVENT DISPATCHER OUTBOUND STREAM entity or an EVENT DISPATCHER SINK INBOUND STREAM entity. It occurs when the DECnet[TM] logical link to the sink node has been disconnected. It tells you why the link has been disconnected and that attempts are being made to reconnect the link. The sink node automatically attempts to reconnect the link. DTE Down -------- This event is generated by an X25 PROTOCOL DTE event when the DTE status attribute STATE changes from On to Off, Synchronizing, or Unsynchronized. See Section 7.3 of the DEC Network Integration Server Problem Solving manual. 19 DTE Up ------ This event is generated by an X25 PROTOCOL DTE event when the DTE status attribute STATE changes from Off, Synchronizing, or Unsynchronized, to On. This event is purely for information and no action is required. Dump Request Completed ---------------------- This event is generated by a MOP CIRCUIT entity when the DECNIS has completed an upline dump to a load host. This event is purely for information and no action is required. 20 Dump Request Failed ------------------- This event is generated by a MOP CIRCUIT entity when the DECNIS fails to complete an upline dump to a load host. This may indicate a failure of the connection between the DECNIS and the load host. Duplicate Address Test Failure ------------------------------ This event is generated by an FDDI STATION LINK entity when an FDDI station is detected using the same link address as this link. 21 Duplicate Token Detected ------------------------ This event is generated by an FDDI STATION LINK entity when a duplicate token is detected. This could indicate that there are two stations on the ring with the same link address. Check the event log for the Duplicate Address Test Failure event. DXI Protocol State Transition ----------------------------- This event is generated by an SMDS STATION entity when the state of the DXI protocol changes. There are three possible states: o Off o On o Broken Cannot IO A reason for the state change is indicated. The reason can be any of the following: o Management Directive o Lower Layer Entity State Change o Heartbeat Response Received o Heartbeat-Failure Threshold Reached If the state changes to Broken Cannot IO and the reason is Lower Layer Entity State Change, this could indicate a problem with the modem or cable connections. If the state changes to Broken Cannot IO and the reason is Heartbeat-Failure Threshold Reached, this could indicate a problem with the CRC communications. For more help with an SMDS circuit problem, follow the procedures in Chapter 4 of the DEC Network Integration Server Problem Solving manual. 22 EGP Message Discard ------------------- This event is generated by the ROUTING entity when an EGP message is received from a neighbor system which is either defined in the EGP management but is in the Off state, or is not known to the DECNIS. Enable Stream ------------- This event is generated by an EVENT DISPATCHER OUTBOUND STREAM entity when the outbound stream has been success- fully enabled. It displays the values of the filters on the outbound stream. This event is purely for information and no action is required. 23 Error Message Received ---------------------- This event is generated by the ROUTING EGP GROUP EGP NEIGHBOR entity when an EGP message is rejected by a remote system. The event indicates a reason for the rejection. The reason could be any of the following: o Unspecified: the reason is not indicated. o BAD EGP Header Format-This could be due to: - Incorrect message length - Invalid Type field - Invalid Code field - Invalid Status field o BAD EGP Data Field Format-This could be due to: - Nonsense polling rates - Invalid update message format - Response IP Net address field does not match the Update command o Reachability Information Unavailable: this occurs when there is no response to Poll requests. It could be due to a configuration error. o Excessive Polling Rate: this is caused when the number of commands, per second, exceeds the agreed limit. The commands could be Poll commands, Hello commands or Request commands. o No Response: this occurs when the neighbor system is not responding to Poll requests. o Stop Event: this occurs when a neighbor system is disabled. o Neighbor Timed Out: this occurs when an Update has not been received for a long interval. o Request Message Received: this occurs when a Request message is received while the DECNIS is in the Up state. This causes a State change from Up to either Down or Idle. 24 o Cease: this occurs when a Cease command is received from a neighbor system. Error Message Sent ------------------ This event is generated by the ROUTING EGP GROUP EGP NEIGHBOR entity when an EGP message is rejected and an error message is sent to the remote system. The reason for the rejection is given. Refer to the Error Message Received event for a description of the reason codes. 25 Events Lost ----------- This event is generated by an EVENT DISPATCHER entity, an EVENT DISPATCHER SINK entity, or an EVENT DISPATCHER OUTBOUND STREAM entity. It is produced when the sink node runs out of memory and cannot log events correctly. The event displays how many events have been lost. If generated by an EVENT DISPATCHER OUTBOUND STREAM entity you should increase the MAXIMUM DATA SIZE allocated to the outbound stream to fix the problem. For details of how to do this, refer to the NCL reference documentation for your load-host operating system or NCL online help. Exceeded Maximum Call Attempts ------------------------------ This event is generated by a ROUTING CIRCUIT entity when the number of attempts to establish a call over an X.25 Static Outgoing circuit exceeds the maximum allowed. Follow the procedures in Section 7.2 of the DEC Network Integration Server Problem Solving manual. Exceeded Maximum SVC Adjacencies -------------------------------- This event is generated by a ROUTING CIRCUIT entity when there is no free adjacency on which to establish an SVC for a new destination. Wait for a few minutes before trying to use the DECNIS again. If this problem occurs frequently, reset the number of Maximum SVC Adjacencies. For more information, see the NCL reference documentation for your load-host operating system or NCL online help. Excessive Collision ------------------- This event is generated by a CSMA-CD STATION entity when a transmission fails because the medium access algorithm reached the maximum number of allowable retransmission attempts resulting from collisions. 26 This error can occur when too many systems are trying to transmit at the same time or when there are cable problems. Failed Dump ----------- This event is generated by a DEVICE UNIT entity when the Network Interface Card dump operation has failed. This may indicate a failure of the connection between the DECNIS and the load host. Failed Load ----------- This event is generated by a DEVICE UNIT entity when a Network Interface Card has failed to load correctly. A failure reason is indicated. Run a module self-test to obtain more information about the failure (refer to the Installation and Service Manual for your hardware system for details). FCI Strip Error --------------- This event is generated by an FDDI STATION LINK entity when a station is prevented from completing the Frame Content Independent (FCI) strip process. This process removes frames which the station transmitted from the ring. The process is interrupted when a new token arrives at the station. This fault could be caused by another station on the ring having the same address as this station. Check the event log for the Duplicate Address Test Failure event. 27 Fragmentation Failure Discard ----------------------------- This event is generated by a ROUTING CIRCUIT NETWORK PROTOCOL entity when an AppleTalk or IPX packet is discarded. The packet is discarded because it required fragmentation but fragmentation is not supported by the network protocol. Frame Check Error ----------------- This event is generated by a CSMA-CD STATION entity 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). FRMR Generated -------------- This event is generated by an HDLC LINK LOGICAL STATION entity when an FRMR (frame reject) frame is generated and transmitted to the remote station. This indicates a link protocol error. Contact the system manager of the remote station to check that it is implementing the HDLC protocol to the DEC-HDLC specifications. Alternatively, the event may be caused by noise on the communications line. If the problem persists, report it to Digital; see Chapter 14 of the DEC Network Integration Server Problem Solving manual. 28 FRMR Received ------------- This event is generated by an HDLC LINK LOGICAL STATION entity, a LAPB LINK entity, or an LLC2 SAP LINK entity. It is produced when an FRMR (frame reject) frame is received from the remote station. This indicates a link protocol error. If the event is generated by an HDLC LINK LOGICAL STATION, check that the remote station is implementing the DEC- HDLC protocol by contacting the system manager of the remote station. Alternatively, the event may be caused by noise on the communications line. If the problem persists, report it to Digital; see Chapter 14 of the DEC Network Integration Server Problem Solving manual. If the event is generated by a LAPB LINK entity, the DTE may fail and a DTE Down event will be logged; see Section 7.3 of the DEC Network Integration Server Problem Solving manual. FRMR Sent --------- This event is generated by a LAPB LINK entity or an LLC2 SAP LINK entity. It occurs when the receipt of a frame causes an FRMR (frame reject) frame to be generated and transmitted to the remote station. This indicates a link protocol error of some kind. When this event is generated, the DTE may fail and a DTE Down event will be logged; see Section 7.3 of the DEC Network Integration Server Problem Solving manual. 29 Frame Size Error ---------------- This event is generated by a CSMA-CD STATION entity whenever a transmission fails because the MAC (Medium Access Control) frame was not within the range of valid frame sizes. This error indicates a problem with the local system or a user error. Frame Status Error ------------------- This event is generated by an FDDI STATION LINK entity when a frame is received with the frame status error bit set or missing. Frame Too Long -------------- This event is generated by a CSMA-CD STATION entity whenever a remote system sends a frame that exceeds the CSMA-CD MAC (Medium Access Control) maximum length. The following information is displayed with the event: o Header-the Data Link Header fields of the received frame, including the source and destination individual addresses and the protocol type or identifier. If the problem persists, contact the system manager at the remote system. ID Reachability Change ---------------------- This event is generated by a ROUTING CIRCUIT entity when the adjacency of an end node changes. This event is purely for information and no action is required. 30 Illegal Packet Received ----------------------- This event is generated by an X25 PROTOCOL DTE entity when the DTE receives an illegal packet from the network. This indicates some type of protocol error; the Failure Reason argument explains the nature of the error. If the Failure Reason is one of the following, the DTE will fail: Invalid State Unrecognized Invalid GFI Header Error This will cause the DTE Down event to be logged. See Section 7.3 of the DEC Network Integration Server Problem Solving manual for more information. If the Failure Reason is one of the following, the virtual circuit will fail: No Interrupt Sent Too Long Too Short Unacknowledged Interrupt This will cause either the SVC Failed or PVC Failed event to be logged. See Chapter 4 of the DEC Network Integration Server Problem Solving manual for more information. Incoming Call Blocked --------------------- This event is generated by an X25 ACCESS entity when an incoming call is blocked by the X25 access module's security mechanisms. This does not indicate an error unless the call came from an authorized caller. If this occurs then the security has been set up incorrectly. To alter the security you should either: o Edit the NCL script o Rerun the configuration procedures 31 Incoming Call Failed -------------------- This event is generated by an X25 ACCESS entity when an incoming call fails. The Failure Reason argument could be any of the following: o No Filters o Security Filter Not Found o Security DTE Class Not Found o Insufficient Resources "No Filters" and "Security Filter Not Found" indicate that the parameters in the filter do not match the parameters in the incoming call packet. "Security DTE Class Not Found" indicates that the DTE class specified in the incoming call packet is not available. Rerun the DECNIS configurator as described in the DEC Network Integration Server Configuration and Loading manual. "Insufficient Resources" indicates that you need to free some memory on your system. For more detail about this event, refer to Section 7.1.1 of the DEC Network Integration Server Problem Solving manual. Initialization Failure ---------------------- This event is generated by the ROUTING CIRCUIT, PPP PORT and BRIDGE PORT entities: o ROUTING CIRCUIT entity The ROUTING CIRCUIT entity generates this event when an attempt to initialize with the adjacent node fails. One of the following reason codes will be displayed: - Version Skew This indicates that the remote system is running an invalid version of the routing protocol. Contact the system manager of the remote system. 32 - Area Mismatch The remote system is in an invalid area. Contact the system manager of the remote system. - Wrong Neighbor Node The remote system has an invalid neighbor IP address. Contact the system manager of the remote system. If the Common Trace Facility (CTF) is available, use the PPP LINK trace point to obtain more information about the protocol exchange between the DECNIS and the remote system. - Configuration Fault This indicates that the PPP link minimum SDU size should be increased. The minimum SDU size depends on the type of data that is routed. Set the SDU size to the minimum or larger. The minimum values are shown below: Data type Minimum SDU size (bytes) IP 128 OSI 512 Phase IV 578 o PPP PORT and BRIDGE PORT entities These entities generate this event when the protocol options negotiated between the DECNIS and the remote system are incompatible. Check the configuration of the local and remote systems. If the Common Trace Facility (CTF) is available on your network, use the PPP LINK trace point to obtain more information about the protocol exchange between the two systems. 33 Inlink Change ------------- This event is generated by a BRIDGE entity when the path changes between the DECNIS and the root bridge. The inlink is the port on a bridge which provides the path to the root bridge. The event indicates the names of the old inlink and the new inlink. Interface State Change ---------------------- This event is generated by a MULTIPLEXED INTERFACE LINE entity when the state of an interface changes. The event indicates the new state and the reason for the change. Interface Type Error ---------------------- This event is generated by a MULTIPLEXED INTERFACE LINE entity. It occurs when a Network Interface Card is Live Inserted into the DECNIS which does not match the specified Interface Type attribute. If this occurs, you should create a new MULTIPLEXED INTERFACE LINE entity with the correct Interface Type attribute. In Use Filter Deleted --------------------- This event is generated by an X25 ACCESS entity when a filter in the "In Use" state is deleted. This event is purely for information and no action is required. In-Use PVC Deleted ------------------ This event is generated by an ATM CONNECTION MANAGEMENT LINE entity when a PVC in the state "In Use" is deleted. This event is for information only. 34 Invalid Address Field Message Received -------------------------------------- This event is generated by the CHDLC LINK and PPP LINK entities when the address field of the received message is invalid. Check that the data link options set up on the local and remote systems are compatible. Invalid Community Operation PDU Discard --------------------------------------- This event is generated by an SNMP entity when an operation is requested which is invalid for the community name in the request. Each community name is set up with one type of access (read only, read-write, or no access). If a community name is set up with read-only access, then any SNMP write operations are invalid for that community name. For example, a DECNIS is configured with a community name "public" which is associated with read-only access. If the DECNIS receives an SNMP write request that contains the community name "public", the request is will fail and this event will be generated. The event indicates the type of operation and the community name specified in the request. Invalid Control Field Message Received -------------------------------------- This event is generated by a PPP LINK entity when the control field of the message received is invalid. Check that the data link options set up on the local and remote systems are compatible. Invalid Protocol Message Received --------------------------------- This event is generated by a PPP LINK entity or an ATM MULTIPROTOCOL ENCAPSULATION LINK ENTITY when an invalid protocol message is received. Check that the data link options set up on the local and remote systems are compatible. 35 Invalid SLARP Message Received ------------------------------ This event is generated by a CHDLC LINK entity when a packet is received with an invalid SLARP message. This indicates that the remote station is running an incompatible SLARP. IP Address Unreachable Packet Discard ------------------------------------- This event is generated by the ROUTING entity when an IP packet is discarded because the destination is unreachable. IP Adjacency State Change ------------------------- This event is generated by the ROUTING CIRCUIT entity when the status attribute of a ROUTING CIRCUIT IP ADJACENCY entity belonging to this circuit changes, in one of the following ways: o From Up (or Up/Dormant) to some other value o To Up (or Up/Dormant) from some other value 36 IP Destination Address Error Packet Discard ------------------------------------------- This event is generated by a ROUTING entity when an IP datagram with an invalid destination address is received. The datagram could have a "martian" address or a multi- cast address. A "martian" address is any of the following: o An address which does not fit into any of the address classes: A, B, C or D. o An address with a network ID of 0. o An address with a network ID of 127 over a nonloopback interface. Use CTF to find out more about the problem. IP Fragmentation Failure ------------------------ This event is generated by a ROUTING CIRCUIT entity. It occurs when an IP packet needs to be fragmented in order to be transmitted, but the packet has an IP header that requests "do not fragment". The packet is not transmitted. This indicates that the system originating the packets is using a data size that is too large for this path through the network. The originating system should either use a smaller data size, or specify a different path through the network. 37 IP Packet Discard ----------------- This event is generated by a ROUTING entity when an IP packet is discarded because the packet was too small or it had one of the following faults: An invalid Header Length field An invalid checksum An invalid IP version number An invalid Total Length field An invalid source address IP Packet Format Error ---------------------- This event is generated by a ROUTING entity when an IP packet is discarded because the IP option contains a format error. The format error is indicated by the IP Discard Reason, as follows: o Header Syntax Error indicates one of: There is an invalid Length field There is an invalid Pointer field o Duplicate Option indicates that the option is a duplicate (each option can occur only once within a packet). o Option Error occurs when the option is a Timestamp option and there is one of the following faults: The Overflow field is nonzero and will overflow if it is incremented. The Flag field contains an invalid value. 38 IP Protocol Unreachable Packet Discard -------------------------------------- This event is generated by a ROUTING entity when an IP packet is discarded because there was either no port or no protocol on the local system for the protocol type specified in the IP header. The reason code should indicate whether the port was unreachable or the protocol was unreachable. IP Source Address Error Packet Discard -------------------------------------- This event is generated by a ROUTING entity when an IP datagram with an invalid source address is received. The invalid address could be a "martian" address. A "martian" address is any of the following: o An IP broadcast address. o An address which does not fit into any of the address classes: A, B, C or D. o An address with a network ID of 0. o An address with a network ID of 127 over a nonloopback interface. Use the Common Trace Facility (CTF) utility to find out more about the problem. 39 Irrecoverable SVC Failure ------------------------- This event is generated by a ROUTING CIRCUIT entity when the number of recall attempts becomes equal to the value of the characteristic MAXIMUM CALL ATTEMPTS. Follow the procedures in Section 7.2 of the DEC Network Integration Server Problem Solving manual. LAN L1 Designated Router Change ------------------------------- This event is generated by a ROUTING CIRCUIT entity when the local node either elects itself or resigns as the LAN Level 1 Designated Router on this circuit. The following information is displayed with the event: o Designated Router Change-specifies the new state of the designated router (Elected or Resigned). This event is purely for information and no action is required. 40 LAN L2 Designated Router Change ------------------------------- This event is generated by a ROUTING CIRCUIT entity when the local node either elects itself or resigns as being the LAN Level 2 Designated Router on this circuit. The following information is displayed with the event: o Designated Router Change-specifies the new state of the designated router (Elected or Resigned). This event is purely for information and no action is required. LAN Phase IV Designated Router Change ------------------------------------- This event is generated by a ROUTING CIRCUIT entity when the local node either elects itself or resigns as being the LAN Phase IV designated router on this circuit. The new state of the designated router (Elected or Resigned) is displayed. This event is purely for information and no action is required. Late Collision -------------- This event is generated by a CSMA-CD STATION entity 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. 41 LCP Initialization Failure -------------------------- This event is generated by a PPP LINK entity when there is an initialization problem with the data link. Check the event reason for more information: o Control Protocol Reject Message Received This indicates that the remote system does not support the protocol used. Check the configuration of the remote system. o Negotiation Not Converging The configuration options set up on the local and remote systems are not compatible. Check the configuration of both systems. o No Response There is no recognized response from the remote system. This could be caused by incompatible configuration options set up on the local and remote systems, or there may be a hardware problem. To isolate the problem, set up a loopback path. Refer to Section 4.5.2 of the DEC Network Integration Server Problem Solving manual for more information. LCP State Change ---------------- This event is generated by a PPP LINK entity when the LCP State has changed on the data link. The new state is displayed with the event. 42 Line State Change ----------------- This event is generated by the CHDLC LINK and PPP LINK entities when the Line State has changed on the data link. The new state is displayed with the event. Link Buffer Unavailable ----------------------- This event is generated by an FDDI STATION LINK entity when a frame is discarded because no link buffers were available. This could be due to frames being received at a higher rate than the Network Interface Card can process them. Link Confidence Test Reject --------------------------- This event is generated by an FDDI STATION PHY PORT entity when an initialization of a physical port was refused because of excessive noise events on the connection. The noise could be caused by a fault on the physical port, the neighboring physical port or the cable. After a connection has been rejected, the physical port will attempt to establish another connection. Check the state of the port by entering the following command: NCL> SHOW NODE decnis FDDI STATION station-name PHY PORT - _NCL> port-name STATE, REJECT REASON If the state of the port is Failed or Watch, the connection attempt has failed. The reject reason should indicate the reason for the last failure. If the state of the port is Starting and the reject reason is None, the neighbor port has become inactive. If the state of the port is In Use, the reconnection has succeeded. For information about checking the hardware, refer to the Problem Solving Card for the Network Interface card. 43 Link Down --------- This event is generated by an HDLC LINK entity when it is disabled. The STATE attribute changes from On to Off. For details of how to enable the link again, refer to the NCL reference documentation for your load-host operating system or NCL online help. If the problem persists, follow the procedures in Chapter 4 of the DEC Network Integration Server Problem Solving manual. Link Elasticity Buffer Error ---------------------------- This event is generated by an FDDI STATION PHY PORT entity when there is a transmit clock error somewhere in the network. 44 Link Error Monitor Reject ------------------------- This event is generated by an FDDI STATION PHY PORT entity when a connection on a physical port is disconnected. The disconnection occurs when the Link Error Monitor (LEM) detects too much noise on the connection. Occasionally, the removal of the cable can cause this event to be generated. After a disconnection, the physical port will attempt to establish another connection. Check the state of the port by entering the following command: NCL> SHOW NODE decnis FDDI STATION station-name PHY PORT - _NCL> port-name STATE, REJECT REASON If the state of the port is Failed or Watch, the connection attempt has failed. The reject reason should indicate the reason for the last failure. If the state of the port is Starting and the reject reason is None, the neighbor port has become inactive. If the state of the port is In Use, the reconnection has succeeded. Link Halted ----------- This event is generated by a LAPB LINK entity or an LLC2 SAP LINK entity. It occurs when the status attribute PROTOCOL STATE is Halted. This event will shortly be followed by the DTE Down event. See Section 7.3 of the DEC Network Integration Server Problem Solving manual for more information. 45 Link Initializing ----------------- This event is generated by a LAPB LINK entity or an LLC2 SAP LINK entity. It occurs when the protocol has been successfully initialized or reinitialized. This event will shortly be followed by the DTE Up event. This event is purely for information and no action is required. Link Inoperative ---------------- This event is generated by a LAPB LINK entity or an LLC2 SAP LINK entity. It occurs when the status attribute PROTOCOL STATE is Inoperative. This event will shortly be followed by the DTE Down event. See Section 7.3 of the DEC Network Integration Server Problem Solving manual for more information. Link Maintenance ---------------- This event is generated by a LAPB LINK entity when the status attribute PROTOCOL STATE of the LAPB LINK entity is Maintenance, indicating that the link has been taken over by MOP. This event will shortly be followed by the DTE Down event. See Section 7.3 of the DEC Network Integration Server Problem Solving manual for more information. 46 Link Resetting -------------- This event is generated by a LAPB LINK entity or an LLC2 SAP LINK entity when the protocol is being reset. If the reset causes the DTE to fail, the DTE Down event will also be logged; see Section 7.3 of the DEC Network Integration Server Problem Solving manual. Otherwise, no further action is required. Link Running ------------ This event is generated by a LAPB LINK entity or an LLC2 SAP LINK entity. It occurs when the protocol has been successfully initialized and the status attribute PROTOCOL STATE is Running. This event is purely for information and no action is required. Link Setup Failed ----------------- This event is generated by a LAPB LINK entity or an LLC2 SAP LINK entity. It occurs when the protocol has failed to initialize correctly after the maximum number of allowed attempts. See Section 7.3 of the DEC Network Integration Server Problem Solving manual for more information. 47 Link State Changed ------------------ This event is generated by an ATM MULTIPROTOCOL ENCAPSULATION LINK entity, a CHDLC LINK entity, a LAPB LINK entity or an LLC2 SAP LINK entity. For the ATM MULTIPROTOCOL ENCAPSULATION LINK entity and the CHDLC LINK entity, it occurs when the STATE attribute changes. The new state and reason for the change is indicated. For LAPB LINK and LLC2 SAP LINK entities, it occurs when the status attribute PROTOCOL STATE changes from Off to On, or from On to Off. If the state change is from On to Off, this event will shortly be followed by the DTE Down event; see Section 7.3 of the DEC Network Integration Server Problem Solving manual. 48 Link Up ------- This event is generated by an HDLC LINK entity when it is enabled. The state of the link changes from Off to On. Note that this does not indicate that the link is operational. This event is purely for information and no action is required. Load Request Completed ---------------------- This event is generated by a MOP CIRCUIT entity when the DECNIS has successfully downloaded a system. This event message is purely for information and no action is required. Load Request Failed ------------------- This event is generated by a MOP CIRCUIT entity when the DECNIS has failed to download a system. Local Protocol Error -------------------- This event is generated by an OSI TRANSPORT LOCAL NSAP REMOTE NSAP entity when the remote NSAP sends notification of a protocol error. An error is caused whenever the local NSAP transmits a message of an invalid protocol type. 49 Locally Initiated State Change ------------------------------ This event is generated by a DDCMP LINK LOGICAL STATION entity when the station changes state. The following information is displayed with the event: o New State-the new value of the station's PROTOCOL STATE attribute. o Old State-the previous value of the station's PROTOCOL STATE attribute. Check the following table for the New State and Old State values shown with the event. 50 __________________________________________________________ Old State_____New_State____Action_____________________________ Halted Starting The event is informational and requires no action. Starting Running The event is informational and requires no action. Running Halted If the local station has been halted by a management request, the event is informational and requires no action. If there is a problem on the link, the local station halts and the event is generated as a warning message. Run the loopback tests described in Chapter 12 of the DEC Network Integration Server Problem Solving manual to check the link. If the tests are successful, check that the DDCMP LINK and LOGICAL STATION STATE attributes on the remote node are set to On. Running Maintenance The event is informational and requires no action. Either the local station or remote station is running maintenance tests. Running Starting Check the link between the local station and remote station. Run the loopback tests described in Chapter 12 of the DEC Network Integration Server Problem Solving manual. If the tests are successful, check that the DDCMP LINK and LOGICAL STATION STATE attributes on the remote node are set to On. __________________________________________________________ 51 Logical Channel Deleted In Use ------------------------------ This event is generated by a MULTIPLEXED INTERFACE LINE entity when a logical channel which has a Client is deleted. This event is for information only. Loss of Carrier --------------- This event is generated by a MODEM CONNECT LINE entity when the Carrier Detect, modem interchange circuit, is deasserted during data transfer. Redial the link. If the problem persists, check the modem's connections and run the loopback tests described in Section 12.1 of the DEC Network Integration Server Problem Solving manual. LSP L1 Database Overload ------------------------ This event is generated by a ROUTING entity when the status attribute L1 STATE changes from On to Waiting, or from Waiting to On. Usually, state changes indicate that the DECNIS is running to the limit of its capacity as specified in the DEC Network Integration Server Software Product Description. LSP L2 Database Overload ------------------------ This event is generated by a ROUTING entity when the status attribute L2 STATE has changed from On to Waiting, or from Waiting to On. Usually, state changes indicate that the DECNIS is running to the limit of its capacity as specified in the DEC Network Integration Server Software Product Description. 52 Management Protocol Transition ------------------------------ This event is generated by the FRBS CHANNEL entity when the state of the management protocol changes. This protocol provides the interface between the DECNIS and the frame relay network. The new state is displayed with the event: o If the new state is Running, the DECNIS and frame relay network device are exchanging information about the network through the management protocol. o If the new state is Initializing, there may be a problem with the DECNIS hardware or cables (refer to the Installation and Service Manual for your DECNIS) or there may be a configuration problem. The DECNIS and frame relay device must use the same management protocol over the channel. Refer to the DEC Network Integration Server Configuration and Loading manual to check that the correct protocol was set up during configuration. o If the new state is Stopped, there may be a problem with the DECNIS hardware or cables. Refer to the Installation and Service Manual for your DECNIS. If the problem persists, refer to Section 4.5 of the DEC Network Integration Server Problem Solving manual. Manual Address Dropped From Area -------------------------------- This event is generated by a ROUTING entity when an address in the Manual Area Address set is ignored because the maximum number of area addresses has been reached. This event is generated once for each address that is dropped. 53 Negotiation Failed ------------------ This event is generated by an HDLC LINK LOGICAL STATION entity when an attempt to negotiate with the remote station has failed. This event does not indicate a problem if the remote system is loading or dumping, and the event will continue to be generated until the load or dump is complete. Check the negotiation failure reason displayed with the event. If the remote system is loading or dumping, the reason should be Incompatible Protocol ID. This is because MOP is using a circuit that has been set up for routing. If the remote system is not loading or dumping, or a different failure reason is indicated, disable the link. Now reset the parameter used by one or both links, and reenable the link. Network Initiated Reset ----------------------- This event is generated by an X25 PROTOCOL DTE entity when the DTE receives a Reset packet from the network. If the DTE fails as a result, the DTE Down event will also be logged; see Section 7.3 of the DEC Network Integration Server Problem Solving manual. 54 Network Initiated Restart ------------------------- This event is generated by an X25 PROTOCOL DTE entity. It may be generated for one of the following reasons: o The DTE receives a Restart packet from the network. This indicates that the PSDN has failed and has been restarted. In this case, the event may be preceded by a number of LAPB events indicating that the link has been halted and restarted. No action is required. o A link protocol error has occurred. In this case, the event will shortly be followed by a DTE Down event. See Section 7.3 of the DEC Network Integration Server Problem Solving manual for more information. 55 No Unit ------- This event is generated by a DEVICE entity when a physical device is inserted into the DECNIS but there is no network management available. Refer to the DEC Network Integration Server Management manual for details of how to start network management. OSPF Authentication Failure --------------------------- This event is generated by the ROUTING CONTROL PROTOCOL LOGICAL CIRCUIT entity. It occurs when the DECNIS receives an OSPF packet with an incorrect OSPF Authentication type or OSPF Authentication key. The OSPF Authentication type specifies whether OSPF passwords are enabled for an OSPF area. The OSPF Authentication key specifies the OSPF password for the area (if OSPF passwords are enabled). If OSPF passwords are enabled on the DECNIS, the sending system must also have OSPF passwords enabled. Enter the following command to check whether an OSPF area has OSPF passwords enabled: NCL> SHOW NODE decnis ROUTING CONTROL PROTOCOL - _NCL> ospf-area-name ALL If the OSPF Authentication type is set to Simple Password, then passwords are enabled. If the OSPF Authentication type is set to None, then passwords are disabled. If passwords are enabled, the sending system must supply the correct OSPF Authentication key (password). To check the OSPF Authentication key that is set up for the OSPF area on the DECNIS, look at the user NCL script file (NIS- mop-client-name_EXTRA_SET.NCL). The Neighbor IP Address argument to this event should specify which system sent the OSPF packet. 56 OSPF Configuration Error ------------------------ This event is generated by the ROUTING CONTROL PROTOCOL LOGICAL CIRCUIT entity when the DECNIS receives an OSPF packet from a router with conflicting configuration parameters. The reason argument should identify the configuration parameter that is causing the problem. The reason could be one of the following: o Invalid Version The system that sent the packet was running a different version of OSPF. The DECNIS runs V2.0 of OSPF. o Area Mismatch The packet was sent by a system in a different OSPF area to the DECNIS. o Unknown Neighbor This reason only applies when the DECNIS is using NBMA circuits and is eligible to be a Designated Router (OSPF Priority > 0). It indicates that the router that sent the packet has not been set up on the DECNIS as an NBMA neighbor. o Unknown Virtual Neighbor The router that sent the packet is not the virtual neighbor. o Authentication Type Mismatch The system that sent the packet was using a different Authentication type to the DECNIS. See the description of the OSPF Authentication Failure event. o Authentication Failure The packet did not contain the correct OSPF password. See the description of the OSPF Authentication Failure event. o Network Mask Mismatch The system that sent the packet is not using the same network mask as the DECNIS. o Hello Interval Mismatch 57 The system that sent the packet is not using the same Hello Interval timer value as the DECNIS. The Hello Interval is the number of seconds between transmission of Hello packets. o Dead Interval Mismatch The system that sent the packet is not using the same Dead Interval timer value as the DECNIS. The Dead Interval is the number of seconds to detect that an OSPF router is inactive. That is, the time that a system waits for a Hello packet before presuming that a neighbor is no longer up and running. o Option Mismatch The system that sent the packet was configured with a different option to the DECNIS. Both the sending and receiving system must use the same options. If the DECNIS has been configured to support the External Routes option, the sending system must also support the External routes option. To solve the problem you need to change the configuration parameters in either the DECNIS or the sending system. The Neighbor IP Address argument of the event should specify which system sent the OSPF packet. OSPF Protocol State Change -------------------------- This event is generated by the ROUTING CONTROL PROTOCOL LOGICAL CIRCUIT entity when the state of an OSPF interface changes. The interface state could change from Designated router to Down or from Down to Point to Point, Designated Router, Other Router or Backup. OSPF Maximum Age LSA --------------------- This event is generated by the ROUTING CONTROL PROTOCOL entity when an OSPF LSA (Link State Advertisement) in the link state database reaches MaxAge. This event is purely for information and no action is required. 58 OSPF New LSA Sent ----------------- This event is generated by the ROUTING CONTROL PROTOCOL entity when the DECNIS generates a new LSA (Link State Advertisement). The DECNIS generates a new LSA whenever the OSPF interface changes, for example, if the interface is enabled or disabled, or if the Cost of the interface is changed. This event is purely for information and no action is required. Outgoing Call Blocked --------------------- This event is generated by an X25 ACCESS entity when the security mechanisms prevent a client from making an outgoing call. This event does not indicate an error unless the client is one that should actually be authorized to make the call. If this occurs then the security has been set up incorrectly. To alter the security you need to either: o Edit the NCL script o Rerun the configurator Refer to the X.25 security section in the DEC Network Integration Server Management manual for details about altering the security set up. 59 Outgoing Call Configuration Error --------------------------------- This event is generated by an X25 ACCESS entity when a call is rejected by X.25 security. This event indicates that security has been set up incorrectly by changes made to the NCL script. To alter the security you need to either: o Edit the NCL script to give each X25 ACCESS DTE CLASS entity a valid SECURITY DTE CLASS o Rerun the configurator Refer to the DEC Network Integration Server Management manual for details about altering the security set up. See Section 7.2 of the DEC Network Integration Server Problem Solving manual for more information. Own LSP Purged -------------- This event is generated by a ROUTING entity 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. If this event is returned frequently, report the problem to Digital (refer to Chapter 14 of the DEC Network Integration Server Problem Solving manual for details). Packet Discard -------------- This event is generated by a ROUTING NETWORK PROTOCOL entity when an AppleTalk or IPX packet is discarded for one of the following reasons: o The checksum is invalid. o The version number does not match. Packet Format Error ------------------- This event is generated by a ROUTING NETWORK PROTOCOL entity when an AppleTalk or IPX packet is discarded because its header is not valid. 60 Parsing Error PDU Discard ------------------------- This event is generated by the SNMP module entity when a corrupted PDU is received. This could indicate a problem with the SNMP network management station. PDU Format Error ---------------- This event is generated by a ROUTING entity when a data Protocol Data Unit (PDU) is discarded because of a format error. This event usually results from an error made by the adjacent node in programming the PDU format, or it could be due to a circuit error that was not detected by the circuit protocol. If this event occurs frequently, report the problem to Digital (refer to Chapter 14 of the DEC Network Integration Server Problem Solving manual for details). PDU Length Error ---------------- This event is generated by an FDDI STATION LINK entity when a frame that is too long or too short is received. PDU Receive Overrun ------------------- This event is generated by a LAPB LINK entity or an HDLC LINK entity when an overrun condition is detected by the underlying framing level. If this event is generated frequently, check that the line is configured at the required line speed. Refer to the DEC Network Integration Server Configuration and Loading manual for details of the DECNIS configuration procedures. 61 PDU Received With Header Format Error ------------------------------------- This event is generated by a DDCMP LINK entity when the logical station receives a Protocol Data Unit (PDU) with an invalid header format. Check that the remote station is running the DDCMP protocol. The event may also be returned if there is noise on the communications line. PDU Transmit Failed ------------------- This event is generated by a LAPB LINK entity or an HDLC LINK entity. It occurs when a call to transmit a frame at the Physical layer, through the internal framing interface, fails. Check the Failure Reason displayed with the event: o If the Failure Reason is Disabled, the line has been disabled by network management action. This event is purely for information and no action is required. o If the Failure Reason is Line Down or No Service, take one of the following actions: - If the event is generated by an HDLC LINK entity, follow the procedures in Section 4.3 of the DEC Network Integration Server Problem Solving manual. - If the event is generated by a LAPB LINK entity, follow the procedures in Section 7.3.5 of the DEC Network Integration Server Problem Solving manual. 62 PhaseIV Translation Failure --------------------------- This event is generated by a ROUTING entity when a Protocol Data Unit (PDU) is discarded because it cannot be translated to PhaseIV format. Port State Change ------------------ This event is generated by a BRIDGE entity when a port on the DECNIS changes state. The event indicates the old and new states. Port Terminated --------------- This event is generated by an X25 ACCESS entity when an SVC is terminated. It indicates the reason for the termination. This event is purely for information and no action is required. 63 Protocol Error Detected ----------------------- This event is generated by an X25 PROTOCOL DTE entity when a protocol error is detected. The nature of the protocol error is given by the Failure Reason argument. o If the Failure Reason is Invalid LCN, the call or PVC connection will fail (in which case, the SVC Failed or PVC Failed event will also be logged). If the call is an incoming call, see Section 7.1 of the DEC Network Integration Server Problem Solving manual. If the call is an outgoing call, see Section 7.2 of the DEC Network Integration Server Problem Solving manual. o For other values of Failure Reason, the DTE will fail (in which case, the DTE Down event will also be logged). See Section 7.3 of the DEC Network Integration Server Problem Solving manual for more information. Protocol Reject Message Received -------------------------------- This event is generated by a PPP PORT entity when the remote system rejects a protocol type used. The protocol type is specified. Check the configuration options set up on the remote and local systems. Protocol State Change --------------------- This event is generated by a ROUTING CIRCUIT IP STANDBY entity when the protocol state changes. The new protocol state is supplied. This event is for information only. 64 PVC Access Blocked ------------------ This event is generated by an X25 ACCESS entity when a client of the X25 access module is denied access to a PVC. This event does not indicate an error unless the client is one that should actually be authorized to access the PVC. If this occurs then the security has been set up incorrectly. To alter the security you should either: o Edit the NCL script o Rerun the configurator Refer to the DEC Network Integration Server Management manual for details about altering the security set up. PVC Failed ---------- This event is generated by an X25 PROTOCOL DTE PVC entity when the PVC fails during the data phase. The reason for the failure is also displayed: o If the Failure Reason is DTE Disabled or Restart, this event will shortly be followed by the DTE Down event; see Section 7.3 of the DEC Network Integration Server Problem Solving manual. o For other failure reasons, see Chapter 4 of the DEC Network Integration Server Problem Solving manual. 65 PVC State Transition -------------------- This event is generated by an FRBS CHANNEL CONNECTION entity when the state of the Permanent Virtual Circuit (PVC) associated with a connection changes. The new state is displayed with the event: o If the state is Active, the frame relay connection is available for use. o If the state is Inactive, the PVC associated with the connection is configured within the frame relay network but it is not available. Report the problem to the network manager for your frame relay network. o If the state is Invalid, there may be a problem with the state of the channel or the management protocol. To isolate the problem, refer to Section 4.5 of the DEC Network Integration Server Problem Solving manual. 66 Rebooted -------- This event is generated by a NODE entity when the system has successfully rebooted. The event describes what caused the system to crash and reboot. This could be one of the following: o Unknown o Software crash o Power failure o System overtemperature o Ambient air temperature too high o System overtemperature with ambient air temperature too high o Operator requested o MOP trigger o Dump button pressed o System reset o Director could not read the initialization script file 67 Receive Data Length Error ------------------------- This event is generated by a CSMA-CD STATION entity when an incorrect length frame is received. Receive Error Threshold Reached ------------------------------- This event is generated by a DDCMP LINK LOGICAL STATION entity when the number of consecutive receive-related errors reaches the Receive Error Threshold limit of 7. The Locally Initiated State Change event is generated with this event. Run the loopback tests described in Chapter 12 of the DEC Network Integration Server Problem Solving manual to check the link. Received Message Discard ------------------------ This event is generated by the ROUTING EGP GROUP EGP NEIGHBOR entity when an EGP message is discarded. The event indicates why the message was discarded. Refer to the Error Message Received event for a description of the reason codes. This event may be associated with the Error Message Received event. Reject Packet Received ---------------------- This event is generated by an X25 PROTOCOL DTE entity when the DTE receives a Reject packet from the network. This event will shortly be followed by an SVC Failed event. See Chapter 4 of the DEC Network Integration Server Problem Solving manual for more information. 68 Reject Received --------------- This event is generated by an NSP LOCAL NSAP REMOTE NSAP entity or an OSI TRANSPORT LOCAL NSAP REMOTE NSAP entity. It occurs when an attempt to connect to a remote node has been rejected by the remote NSAP. A reason for the rejection is indicated. Reject Sent ----------- This event is generated by an NSP LOCAL NSAP REMOTE NSAP entity or an OSI TRANSPORT LOCAL NSAP REMOTE NSAP entity. It occurs when the DECNIS rejects an inbound connection attempt. A reason for the rejection is given. Rejected Adjacency ------------------ This event is generated by a ROUTING CIRCUIT entity when an attempt to create a new adjacency fails because of insufficient resources. Check the capacity of the router as specified in the DEC Network Integration Server Software Product Description. Rejected IP Adjacency --------------------- This event is generated by a ROUTING CIRCUIT entity. It occurs when an attempt to create a new IP adjacency to an IP router fails because of insufficient resources. Check the capacity of the router as specified in the DEC Network Integration Server Software Product Description. 69 Remotely Initiated State Change ------------------------------- This event is generated by a DDCMP LINK LOGICAL STATION entity when the station has changed state because of an incoming frame. The following information is generated with the event: o New State-the new value of the station's PROTOCOL STATE attribute. o Old State-the previous value of the logical station's PROTOCOL STATE attribute. If the New State is Halted, the link cannot transfer data. If the New State is Running, the link can transfer data. Remote Protocol Error --------------------- This event is generated by an NSP LOCAL NSAP REMOTE NSAP entity or an OSI TRANSPORT LOCAL NSAP REMOTE NSAP entity. It occurs when the protocol type of a received message is invalid and therefore the DECNIS cannot make a connection. Renamed ------- This event is generated by a NODE entity when a rename directive is issued. It displays the old and the new name. 70 Retry Failed ------------ This event is generated by an X25 PROTOCOL DTE entity when one of the DTE's maximum retry counts has been reached. The Retry argument indicates the type of packet to which the event refers. If the packet type is: o Clear - this event will shortly be followed by the DTE Down event. See Section 7.3 of the DEC Network Integration Server Problem Solving manual for more information. o Reset - this event will shortly be followed by the SVC Failed or PVC Failed event. See Chapter 4 of the DEC Network Integration Server Problem Solving manual for more information. o Restart - see Section 7.3 of the DEC Network Integration Server Problem Solving manual for more information. Retry Limit Exceeded -------------------- This event is generated by an X25 RELAY PVC entity when an attempt to set up a PVC connection fails. The reason for the failure could be any of the following: o No Such PVC o PVC Already In Use o Transit Not Allowed o DTE Class Not Available o DTE Class Not Type Remote o Security Failure o Remote Procedure Error Refer to Section 7.4.3 of the DEC Network Integration Server Problem Solving manual for details about the reason codes. 71 Ring Beacon Initiated --------------------- This event is generated by an FDDI STATION LINK entity when this link initiates a Beacon process. The Beacon process is initiated to announce that there is an error on the ring and to check if any stations are faulty. If the error on the ring is not corrected, the station will start a trace process to determine which station is at fault. Ring Initialization Initiated ----------------------------- This event is generated by an FDDI STATION LINK entity when the ring is reinitialized by this link. This indicates that this link initiated a claim process. The claim process is used to provide a new token for the ring after a station has finished transmitting frames. This event is purely for information. Ring Initialization Received ---------------------------- This event is generated by an FDDI STATION LINK entity when the ring is reinitialized. It indicates that another link initiated a claim process. The claim process is used to provide a new token for the ring after a station has finished transmitting frames. This event is purely for information. However, if this event occurs very frequently, there may be a problem on the ring. 72 Ring Purge Error ---------------- This event is generated by an FDDI STATION LINK entity when the ring purger process is prevented from completing. The ring purger process removes frames (and fragments of frames) that have not been removed by their originating data link. The ring purger process is prevented from completing if a token is received in the middle of the process. This may be caused by another station on the ring having the same address as this station. Check the event log for the Duplicate Address Test Failure event. RIP Error Received ------------------ This event is generated when any kind of error is detected in a received RIP packet. The event indicates a reason for the error. SAP State Changed ----------------- This event is generated by an LLC2 SAP entity when the Protocol State of the LLC2 SAP entity changes from Off to On, or On to Off. If the state change is from On to Off, this event will shortly be followed with the Link Halted event and the DTE Down event. See Section 7.3 of the DEC Network Integration Server Problem Solving manual. 73 Script Exception ---------------- This event is generated by a NODE entity each time that an NCL command fails during the compilation of the CMIP script file. The failing NCL command could be in either the master NCL script file or one of the user NCL script files. Check the contents of the user NCL script files for any errors. If no errors are apparent in the user NCL script files, rerun the DECNIS configurator in modify mode and check for errors in the configuration information. In particular, check the Network Interface Card (NIC) information to see that the correct card is assigned to the correct slot. Look at your DECNIS hardware if you are not sure which card is in which slot. Correct any errors you find and create a new CMIP script file either using the configurator or the following command: (OpenVMS[TM]) $ @SYS$MANAGER:NIS$SCRIPT_COMPILE NIS_mop-client-name (Digital UNIX[TM] ) # /usr/lib/dnet/nis_script_compile nis_mop-client-name (MS-DOS[R]) c:\ install-directory\NIS\NIS_SCPL.EXE mop-client-name For more details about running the configurator and cre- ating CMIP scripts, refer to the DEC Network Integration Server Configuration and Loading manual. If the Script Exception event is still logged, delete all the commands in the user NCL script files and then create a new CMIP script file. If you still have a problem, report it to Digital as described in Chapter 14 of the DEC Network Integration Server Problem Solving manual. 74 Selection Error Threshold Reached --------------------------------- This event is generated by a DDCMP LINK LOGICAL STATION entity when the number of consecutive selection-related errors reaches the Selection Error Threshold limit of 7. The Locally Initiated State Change event is also generated with this event. Run the loopback tests described in Chapter 12 of the DEC Network Integration Server Problem Solving manual to check the link. Also check that the remote station is working. Selftest Failure ---------------- This event is generated by an FDDI STATION entity when a self-test of the station detected an error. The reason code of the event will indicate the reason for the failure. Send Error Threshold Reached ---------------------------- This event is generated by a DDCMP LINK LOGICAL STATION entity when the number of consecutive, transmit errors reaches the Transmit Error Threshold limit of 7. The Locally Initiated State Change event is also generated with this event. Run the loopback tests described in Chapter 12 of the DEC Network Integration Server Problem Solving manual to check the link. Also check that the remote station is working. Send Message Discard -------------------- This event is generated by the ROUTING EGP GROUP EGP NEIGHBOR entity when an EGP message is discarded rather than transmitted. This may be caused by an internal code error. Refer to the Error Message Received event for a description of the reason codes. Report the event to Digital, as described in Chapter 14 of the DEC Network Integration Server Problem Solving manual. 75 Sequence Number Skipped ----------------------- This event is generated by a ROUTING entity when the sequence number of a Link State Packet (LSP) is incremented by more than one. This usually occurs when a router is reenabled while its previous Link State Packets are still stored in the network. Server Connect Rejected ----------------------- This event is generated by an X25 CLIENT entity when a requested connection to an X.25 gateway system is rejected. See Section 7.2 of the DEC Network Integration Server Problem Solving manual. 76 Session Control Unavailable --------------------------- This event is generated by an X25 CLIENT entity or an X25 SERVER entity when an absence of the session control module is detected. When this is detected the X25 SERVER and X25 CLIENT set their own states to off. To reenable the modules, use the Enable directive. Refer to the DEC Network Integration Server Management manual for details. Shutdown -------- This event is generated by an EVENT DISPATCHER OUTBOUND STREAM entity when an event stream has been successfully shutdown. The shutdown could be due to a shutdown directive or a disable directive. This event is purely for information and no action is required. Source Address Error Packet Discard ----------------------------------- This event is generated by a ROUTING NETWORK PROTOCOL entity when an AppleTalk or IPX packet is discarded because the source address is invalid. Spanning Tree Mode Changed -------------------------- This event is generated by a BRIDGE entity when the spanning tree algorithm changes. It can change from LAN Bridge 100 mode to IEEE 802.1d mode or from IEEE 802.1d mode to LAN Bridge 100 mode. 77 State Change ------------ This event is generated by the following entities: o ATM CONNECTION MANAGEMENT LINE. This entity generates the event when the state of the line changes from "On", "Off" or "Initializing". The new state and the reason for the change is indicated. o CIRCUIT NETWORK PROTOCOL. This entity generates the event when the state of the Circuit Network Protocol changes to or from "On". o CONTROL PROTOCOL. This entity generates the event when the state of the Control Protocol changes to or from "On". o CONTROL PROTOCOL LOGICAL CIRCUIT. This entity generates the event when the state of the Control Protocol Logical Circuit changes to or from "On". If the state unexpectedly changes from On to another state, it could be due to a lack of resources. Try to free some resources, for example: o Disable some other circuits. o Reduce the network size. o Configure L1 only routing. o Turn off IP routing. o EGP GROUP EGP NEIGHBOR. This entity generates the event when the EGP state changes to or from "Up". If the state changes from Up, a reason for the change is indicated. This could occur if a neighbor system is manually deleted. Refer to the Error Message Received event for a description of the reason codes. o SUPERVISOR GROUP. This entity generates the event when the state of a group changes to or from "On". If the state changes to "Off", it can be a result of a direct management action or an indirect result of a primary circuit being deleted. 78 Station Halted -------------- This event is generated by an HDLC LINK LOGICAL STATION entity when the protocol has halted. Check the reason displayed with the event: o If one of the following reasons is displayed, the remote station may have restarted: DISC DM XID Disable the HDLC LOGICAL STATION entity and then reenable it again. See the NCL documentation for your load-host operating system or NCL online help for more information. o If one of the following reasons is displayed, there is a protocol error: Fbit Error FRMR Window Error Unsolicited UA Check that the remote station is implementing the HDLC protocol to the DEC-HDLC specifications. o If the reason is Local, the station has been halted by a management operation. This event is purely for information, and no further action is required. o If the reason is Physical, a Physical layer event will be generated. o If the reason is User, the client of the link has been disabled or stopped. 79 Station Initializing -------------------- This event is generated by an HDLC LINK LOGICAL STATION entity when the protocol has initialized. The reason for the initialization is displayed with the event. When initialization is complete, the protocol enters the running state. If the state does not change to running, complete the problem solving procedures in Chapter 4 of the DEC Network Integration Server Problem Solving manual. Station Inoperative ------------------- This event is generated by an HDLC LINK LOGICAL STATION entity when the protocol is inoperative. The protocol enters the inoperative state because the Physical layer cannot supply a service. Until the Physical layer can restore a service, no further data can be transmitted. Check the connections to the modem, and run loopback tests described in Section 12.1 of the DEC Network Integration Server Problem Solving manual. Station Maintenance ------------------- This event is generated by an HDLC LINK LOGICAL STATION entity when the protocol is in Maintenance state. No data transfer will be available in the state but the link may be used for maintenance operations. This event is purely for information and no action is required. 80 Station Resetting ----------------- This event is generated by an HDLC LINK LOGICAL STATION entity when the protocol has been reset. The Station Resetting Reason is displayed: o If one of the following reasons is displayed, there is a protocol error: Fbit Error FRMR Window Error Unsolicited UA Check that the remote station is implementing the HDLC protocol to DEC-HDLC specifications. o If Maximum Retry is displayed, there is no response at the remote end. Follow the procedures in Chapter 6 of the DEC Network Integration Server Problem Solving manual. o If SABM is displayed, the Station Resetting event is generated because the remote station has set the state of the line to Off. In this case, the event is for information and requires no further action. Station Running --------------- This event is generated by an HDLC LINK LOGICAL STATION entity when the protocol has successfully initialized and is now able to transmit data. This event is purely for information and no action is required. 81 Streaming Tributary ------------------- This event is generated by the DDCMP LINK entity and records the potential jamming of a line by a remote station. This occurs if the remote station is transmitting for too long. If this event occurs with a type 1 in the field, do the following: o Increase the local babble timer on the logical station. Note that the babble timer should be larger than the retransmit timer (typically twice the value). o Decrease the amount of data the remote station is transmitting in a selection interval by reducing its TRANSMIT WINDOW attribute on the logical station. If the event is logged with a type 3 in the field, the remote station has stopped jamming. This is for information only. STRT Received While in Maintenance ---------------------------------- This event is generated by a DDCMP LINK LOGICAL STATION entity each time a STRT message is received while the value of the Protocol State of the local station is Maintenance. The STRT frames are sent by the remote station when the station is not in maintenance mode. This indicates that there is a mismatch in the operational mode of the two ends of the link. Change the mode so that the value of the PROTOCOL STATE attribute at both ends of the link match. For more information, refer to the NCL reference documentation for your load-host operating system or NCL online help. Successful Load --------------- This event is generated by a DEVICE UNIT entity when the DECNIS has completed a successful load. This event is purely for information and no action is required. 82 SVC Failed ---------- This event is generated by an X25 PROTOCOL DTE entity when an incoming or outgoing call fails in the setup or data phase. The reason for the failure is given by the Failure Reason argument: o If the call is an incoming call, see Section 7.1 of the DEC Network Integration Server Problem Solving manual. o If the call is an outgoing call, see Section 7.2 of the DEC Network Integration Server Problem Solving manual. Temperature Alarm ----------------- This event is generated by a HARDWARE entity when the temperature of the system increases. The severity of the temperature increase is indicated with one of the following descriptions: o Warning o Critical o Cleared (this occurs when a normal temperature is resumed) The event may also indicate a specific problem caused by the temperature increase. 83 Test Indication ---------------- This event is generated by a MODEM CONNECT LINE entity when the remote station initiates a modem test function. The link will fail shortly after this event is generated. To reenable the link and ensure that the Test Indicator (TI) signal does not cause the link to fail, enter the following commands: NCL> DISABLE NODE server MODEM CONNECT LINE line-name NCL> SET NODE server MODEM CONNECT LINE line-name SUPPRESS - _NCL> TEST INDICATOR TRUE NCL> ENABLE NODE server MODEM CONNECT LINE line-name where server is the name for the DECNIS and line-name is the name of the line. Test Requested -------------- This event is generated by an EVENT DISPATCHER entity when a test directive has been issued. This event is purely for information and no action is required. Too Long Message Received ------------------------- This event is generated by a PPP LINK entity, a CHDLC LINK entity or an ATM MULTIPROTOCOL ENCAPSULATION LINK entity when a message is received that is too long. Check that the data link options set up on the local and remote systems are compatible. Topology Change Detected ------------------------ This event is generated by a BRIDGE entity when the DECNIS, acting as a root bridge, is notified of a topology change in the extended LAN. It occurs when a bridge port in the network changes to or from a forwarding state. 84 Trace Initiated --------------- This event is generated by an FDDI STATION LINK entity when the station initiates a trace process to isolate a fault on the ring. A station will initiate a trace process after it has announced an error using the beacon process and the ring is still in an error state. If a fault with a station is found, a Selftest Failure event will also be logged. Traces Received --------------- This event is generated by an FDDI STATION entity when the station receives a trace signal. The trace signal tells the station to run a self-test to determine if it has a fault. If the station detects a fault, it will generate a Selftest Failure event. Transmit Enable Timeout ----------------------- This event is generated by a MODEM CONNECT LINE entity when the modem interchange circuit CTS is not asserted within the limit set by the MAXIMUM TRANSMIT ENABLE TIMER attribute. Redial the connection. If the problem persists, check the modem connections and run the loopback tests described in Chapter 12 of the DEC Network Integration Server Problem Solving manual. 85 Transmit Failure ----------------- This event is generated by an FDDI STATION LINK entity when a transmit error occurs. The error could be caused if the ring develops a fault while the station is trying to transmit a frame. Unavailable Station Buffer -------------------------- This event is generated by a CSMA-CD STATION entity whenever an incoming frame is discarded because there is no station buffer available to receive it. This event is generated when network traffic is heavy. If the problem persists, reconfigure your network. Unknown Community Name PDU Discard --------------------------------- This event is generated by the SNMP module entity when the community name supplied in the PDU (Protocol Data Unit) has not been configured as a community name on the DECNIS. This could indicate that the SNMP network management station is supplying an incorrect community name or that the DECNIS has been configured incorrectly. For information about configuring the DECNIS, refer to the DEC Network Integration Server Configuration and Loading manual. Unknown PDU Type Discard ------------------------ This event is generated by the SNMP module entity when the DECNIS receives an SNMP request of an unknown type. The DECNIS recognises the following request types: o GET o GET NEXT o SET If another type of request is being sent it could indicate a problem with your SNMP network management station. 86 Unknown Protocol Message Received --------------------------------- This event is generated by a PPP LINK, a CHDLC LINK entity or an ATM MULTIPROTOCOL ENCAPSULATION LINK entity when a message is received with an unknown protocol field. Check that the data link options set up on the local and remote systems are compatible. Unknown UI PDU Received ----------------------- This event is generated by an HDLC LINK LOGICAL STATION entity when a remote station sends a frame with a protocol identifier that does not correspond to a data link client. This event may be generated if a MOP (Maintenance Operations Protocol) message is sent when MOP is not enabled on the DECNIS. Refer to the DEC Network Integration Server Management manual for more information about enabling the MOP module. Unrecognized Dump Client ------------------------ This event is generated by a MOP CIRCUIT entity when the DECNIS rejects a dump request because the required client database entry cannot be found. This may indicate a load host configuration error. See Section 2.1 of the DEC Network Integration Server Problem Solving manual. 87 Unrecognized Individual PDU Destination --------------------------------------- This event is generated by an FDDI STATION LINK entity. It occurs whenever an incoming frame that matches an enabled individual MAC (Medium Access Control) address is discarded. The frame will be discarded if it does not satisfy the filter criteria of any port. This could indicate one of the following: o The local system has not enabled the required protocol type, protocol identifier, or LLC SAP address. o The remote system is using a protocol that is not supported locally. Unrecognized Load Client ------------------------ This event is generated by a MOP CIRCUIT entity when the DECNIS rejects a load request because the client database entry cannot be found. See Section 2.1 of the DEC Network Integration Server Problem Solving manual. 88 Unsupported Option ------------------ This event is generated by a ROUTING entity when a data PDU is discarded because the source node requests an option not supported by the DECNIS. The following information is displayed with the event: o Discard Reason-the reason why the event was generated. o PDU Header-the contents of the header of the data PDU that caused the event. o Receiving Adjacency-the name of the adjacency on which the PDU was received. Unsupported Version PDU Discard -------------------------------- This event is generated by the SNMP module entity when the DECNIS receives a PDU (Protocol Data Unit) with an invalid SNMP version number. This indicates a problem with the SNMP network management station. For more problem solving information, refer to the documentation for your management station. Update Failure -------------- This event is generated by a SESSION CONTROL TOWER MAINTENANCE entity each time that an attempt to update a DNA$TOWERS attribute fails. Follow the procedures in Section 2.3 of the DEC Network Integration Server Problem Solving manual. User Buffer Unavailable ----------------------- This event is generated by an FDDI STATION LINK entity when a frame is discarded because no user buffers were available. 89 Verification Failure -------------------- This event is generated by a SESSION CONTROL entity when the local NSAP cannot verify that a remote NSAP belongs to the remote node attempting to make a connection. Consequently, the connection fails. This is a security mechanism and does not indicate an error unless you want to receive calls from this remote node. If you want to receive calls from this remote node you need to rerun the configuration procedures (see the DEC Network Integration Server Configuration and Loading manual for details). Verification Reject ------------------- This event is generated by a ROUTING CIRCUIT entity when a verification attempt fails. Either the DECNIS expected the wrong NODE RECEIVE PASSWORD, or the adjacent node sent the wrong NODE TRANSMIT PASSWORD. The name of the circuit to which the event applies is displayed, along with the address of the adjacent node that failed to initialize. Refer to Chapter 4 of the DEC Network Integration Server Problem Solving manual for more information. 90