ELS Messages for LAN Network Manager (LNM)

LNM.001

Level:
C-INFO
Short Syntax:
LNM.001 Configuring port port_number
Long Syntax:
LNM.001 Configuring port port_number
Description:
LNM is beginning Configuration of the specified port.

LNM.002

Level:
C-INFO
Short Syntax:
LNM.002 Configuration complete port port_number nt network
Long Syntax:
LNM.002 Configuration complete port port_number network network
Description:
LNM has completed the Configuration of the specified port.

LNM.003

Level:
U-INFO
Short Syntax:
LNM.003 LNM configured for port port_number , port does not exist in Bridge Configuration
Long Syntax:
LNM.003 LNM configured for port port_number , but the port is not configured in the Bridge Configuration
Description:
The port is configured in the LNM configuration, but not in the SRT configuration.
Cause:
User configuration error.
Action:
Reconfigure LNM or SRT. Ensure Bridge is enabled.

LNM.004

Level:
U-INFO
Short Syntax:
LNM.004 LNM configured for port port_number , is not SRB port
Long Syntax:
LNM.004 LNM configured for port port_number , is not configured for SRB
Description:
The port is configured in the LNM configuration, but is not configured as an SRB port in the SRT configuration.
Cause:
User configuration error.
Action:
Reconfigure LNM or SRT.

LNM.005

Level:
U-INFO
Short Syntax:
LNM.005 LNM configured for port port_number , is not token ring
Long Syntax:
LNM.005 LNM configured for port port_number , is not a token ring interface
Description:
The port is configured in the LNM configuration, but the interface is not a Token-Ring interface.
Cause:
User configuration error.
Action:
Reconfigure LNM or the interface.

LNM.006

Level:
UI-ERROR
Short Syntax:
LNM.006 No iorb to transmit packet
Long Syntax:
LNM.006 No buffer available to copy one or more packets
Description:
No buffer available to copy one or more packets in order to send through LLC.
Cause:
Severe packet buffer shortage.
Action:
Check memory statistics in GWCON to verify packet buffer level.
Cause:
Traffic peak using all available buffers.
Action:
This is the problem if this message occurs very infrequently. a bug where buffers are being lost. You can look at this with DDT. Look at BFRLST, if 0 (NULL) there are still no free buffers. Then look at NBFREE, if zero there was a slow buffer leak, if non-zero then there has been a double-free of a buffer freeing the free list.

LNM.007

Level:
C-INFO
Short Syntax:
LNM.007 Initializing port port_number nt network
Long Syntax:
LNM.007 Initializing port port_number network network
Description:
LNM is beginning initialization of the specified port.

LNM.008

Level:
C-INFO
Short Syntax:
LNM.008 Initialization complete port port_number nt network
Long Syntax:
LNM.008 Initialization complete port port_number network network
Description:
LNM has completed the initialization of the specified port.

LNM.009

Level:
C-INFO
Short Syntax:
LNM.009 Activating LLC for port port_number nt network
Long Syntax:
LNM.009 Activating LLC for port port_number network network
Description:
LNM is activating the connection to LLC for the specified port.

LNM.010

Level:
C-INFO
Short Syntax:
LNM.010 Activating REM for port port_number nt network
Long Syntax:
LNM.010 Activating REM for port port_number network network
Description:
LNM is activating the Ring Error Monitor on the specified port.

LNM.011

Level:
C-INFO
Short Syntax:
LNM.011 Activating RPS for port port_number nt network
Long Syntax:
LNM.011 Activating RPS for port port_number network network
Description:
LNM is activating the Ring Parameter Server on the specified port.

LNM.012

Level:
C-INFO
Short Syntax:
LNM.012 Activating CRS for port port_number nt network
Long Syntax:
LNM.012 Activating CRS for port port_number network network
Description:
LNM is activating the Configuration Report Server for the specified port.

LNM.013

Level:
C-INFO
Short Syntax:
LNM.013 Activating LRM for port port_number nt network
Long Syntax:
LNM.013 Activating LRM for port port_number network network
Description:
LNM is activating the LAN Reporting Mechanism for the specified port.

LNM.014

Level:
C-INFO
Short Syntax:
LNM.014 Activating MAC frame int for port port_number nt network
Long Syntax:
LNM.014 Activating MAC frame interface for port port_number network network
Description:
LNM is activating the interface to the Token-Ring for the transfer of MAC frames to and from the specified port.

LNM.015

Level:
C-INFO
Short Syntax:
LNM.015 Proc net up ind for port port_number nt network
Long Syntax:
LNM.015 Processing network up indication for port port_number network network
Description:
LNM received an indication that an interface that LNM has been enabled on is now up. LNM will perform processing necessary to start processing requests to or from the interface.

LNM.016

Level:
C-INFO
Short Syntax:
LNM.016 Proc net dwn ind for port port_number nt network
Long Syntax:
LNM.016 Processing network down indication for port port_number network network
Description:
LNM received an indication that an interface that LNM has been enabled on is now down. LNM will terminate processing requests to or from the interface.

LNM.017

Level:
UI-ERROR
Short Syntax:
LNM.017 No memory to queue event
Long Syntax:
LNM.017 No memory available to create an LNM event queue block
Description:
No memory available to create an LNM event queue block. This is a fatal condition and in all probability indicates a memory leak.

LNM.018

Level:
C-INFO
Short Syntax:
LNM.018 Rem cn req refused port port_number nt network
Long Syntax:
LNM.018 Remote connection request refused for port port_number network network
Description:
LNM received an indication that a connection request initiated by a remote station was received. LNM does not accept remote connection requests, so the connection request will be refused.

LNM.019

Level:
C-INFO
Short Syntax:
LNM.019 cn cnfm rcvd but not cnctg link link port port_number nt network
Long Syntax:
LNM.019 A connect confirm indication was received but the link is not in connecting state for link link port port_number network network
Description:
LNM received an indication that a previously issued connection request has been confirmed by LLC, but the state of the link indicates that no connection request is outstanding.
Cause:
The outstanding connection request may have been cancelled due to a netdown condition.

LNM.020

Level:
C-INFO
Short Syntax:
LNM.020 disc rcvd when cnctg link link port port_number nt network
Long Syntax:
LNM.020 A disconnect indication was received while the link is in connecting state for link link port port_number network network
Description:
LNM received a disconnect indication while a previously issued connection request is outstanding.

LNM.021

Level:
C-INFO
Short Syntax:
LNM.021 disc rcvd but conn not act port port_number nt network
Long Syntax:
LNM.021 A disconnect indication was received but the connection is not active on port port_number network network
Description:
LNM received an indication that the specified link has been disconnected, but the state of the link indicates that the connection is not active.
Cause:
The connection may have been closed due to a netdown condition.

LNM.022

Level:
C-INFO
Short Syntax:
LNM.022 reset rcvd link link port port_number nt network
Long Syntax:
LNM.022 A reset indication was received for link link port port_number network network
Description:
LNM received a reset indication for the specified link. LNM will return a reset response.

LNM.023

Level:
C-INFO
Short Syntax:
LNM.023 cannot open conn SAP clsd port port_number nt network
Long Syntax:
LNM.023 Cannot open a connection SAP closed on port port_number network network
Description:
LNM attempted to open a connection, but found that the LNM SAP had been closed.
Cause:
The SAP may have been closed due to a netdown condition.

LNM.024

Level:
C-INFO
Short Syntax:
LNM.024 cannot open conn lnk in use lnk link port port_number nt network
Long Syntax:
LNM.024 Cannot open a connection link in use link link port port_number network network
Description:
LNM attempted to open a connection, but found that the requested link is already in use.

LNM.025

Level:
C-INFO
Short Syntax:
LNM.025 open sta fld rtn = retval lnk link port port_number nt network
Long Syntax:
LNM.025 Open station failed return = retval link link port port_number network network
Description:
LNM attempted to open a station, but LLC rejected the operation.

LNM.026

Level:
C-INFO
Short Syntax:
LNM.026 conn req fld rtn = retval lnk link port port_number nt network
Long Syntax:
LNM.026 Connect req failed return = retval link link port port_number network network
Description:
LNM attempted to open a connection, but LLC rejected the operation.

LNM.027

Level:
C-INFO
Short Syntax:
LNM.027 disc req fld rtn = retval lnk link port port_number nt network
Long Syntax:
LNM.027 Disconnect req failed return = retval link link port port_number network network
Description:
LNM attempted to disconnect a connection, but LLC rejected the operation.

LNM.028

Level:
C-INFO
Short Syntax:
LNM.028 netdwn rcvd clsg LNM SAP port port_number nt network
Long Syntax:
LNM.028 Netdown received closing LNM SAP port port_number network network
Description:
LNM received a network down indication for the specified port. LNM is closing the LNM SAP X'F4' as a result.

LNM.029

Level:
C-INFO
Short Syntax:
LNM.029 netup rcvd opening LNM SAP port port_number nt network
Long Syntax:
LNM.029 Netup received, opening LNM SAP port port_number network network
Description:
LNM received a network up indication for the specified port. LNM is opening the LNM SAP X'F4' as a result.

LNM.030

Level:
C-INFO
Short Syntax:
LNM.030 No rsrc for open LNM SAP port port_number nt network
Long Syntax:
LNM.030 No resources for opening LNM SAP port port_number network network
Description:
LLC indicated that not enough resources exist for opening the LNM SAP X'F4'. LNM will not be enabled as a result.

LNM.031

Level:
C-INFO
Short Syntax:
LNM.031 LNM UI frm not sent rsn = reason port port_number nt network
Long Syntax:
LNM.031 LNM UI LLC frame not sent reason = reason port port_number network network
Description:
LNM attempted to send a UI frame via LLC, but the frame could not be sent for the indicated reason.

LNM.032

Level:
C-INFO
Short Syntax:
LNM.032 LNM UI frm not sent net dwn port port_number nt network
Long Syntax:
LNM.032 LNM UI LLC frame not sent network down port port_number network network
Description:
LNM attempted to send a UI frame via LLC, but the frame could not be sent because the network interface is down.

LNM.033

Level:
C-INFO
Short Syntax:
LNM.033 LNM I frm not sent conn clsd port port_number nt network
Long Syntax:
LNM.033 LNM I frame not sent connection closed port port_number network network
Description:
LNM attempted to send an I frame via LLC, but the frame could not be sent because the connection has been closed.
Cause:
The connection may have been closed because the network interface went down.

LNM.034

Level:
C-INFO
Short Syntax:
LNM.034 LNM I frm not sent rsn = reason link link port port_number nt network
Long Syntax:
LNM.034 LNM I frame not sent reason = reason link link port port_number network network
Description:
LNM attempted to send an I frame via LLC, but the frame could not be sent for the indicated reason.

LNM.035

Level:
C-INFO
Short Syntax:
LNM.035 packet rcvd but no connection on link link port port_number nt network
Long Syntax:
LNM.035 An LLC packet was received but no connection exists for link number: link port port_number net network
Description:
LNM received an LLC packet for an inactive link, possibly indicating that a previously activated link has become inactive.
Cause:
The previous connection request may have been cancelled due to a netdown condition.

LNM.036

Level:
C-INFO
Short Syntax:
LNM.036 server PARSE error, code = error port port nt network msgptr
Long Syntax:
LNM.036 server LLC parsing error, code = error port port nt network msgptr
Description:
LNM received a LLC packet which contained a architectural syntax error and could not be parsed properly. The code defines the specific parsing failure.
Cause:
Implementation error.

LNM.037

Level:
C-INFO
Short Syntax:
LNM.037 server EXECUTION error, code = error port port nt network msgptr
Long Syntax:
LNM.037 server EXECUTION error, code = error port port nt network msgptr
Description:
LNM received a LLC packet which, although syntactically correct, could not be executed.
Cause:
The request in the packet cannot be executed or is not supported.

LNM.038

Level:
C-INFO
Short Syntax:
LNM.038 server PCK_ALLOC error, code = error port port nt network msgptr
Long Syntax:
LNM.038 server packet allocation error, code = error port port nt network msgptr
Description:
The indicated server component was unable to allocate a packet buffer.
Cause:
Either the system is very busy, or more packet buffers need to be allocated.

LNM.039

Level:
C-INFO
Short Syntax:
LNM.039 server GET_CHAR error, code = error port port nt network msgptr
Long Syntax:
LNM.039 server error, code = error port port nt network msgptr
Description:
The indicated server component was unable to obtain the next character from a LLC packet.
Cause:
Implementation error.

LNM.040

Level:
C-INFO
Short Syntax:
LNM.040 server error, code = error port port nt network msgptr
Long Syntax:
LNM.040 server error, code = error port port nt network msgptr
Description:
The indicated server component was unable to perform a packet character operation.
Cause:
Implementation error.

LNM.041

Level:
C-INFO
Short Syntax:
LNM.041 server error, code = error port port nt network msgptr
Long Syntax:
LNM.041 server error, code = error port port nt network msgptr
Description:
The indicated server component was unable to perform a buffer operation.
Cause:
Implementation error.

LNM.042

Level:
C-INFO
Short Syntax:
LNM.042 server error, code = error port port nt network msgptr
Long Syntax:
LNM.042 server error, code = error port port nt network msgptr
Description:
The indicated server component was unable to perform a timer operation.
Cause:
Implementation error.

LNM.043

Level:
C-INFO
Short Syntax:
LNM.043 server error, code = error port port nt network msgptr
Long Syntax:
LNM.043 server error, code = error port port nt network msgptr
Description:
The indicated server component was unable to perform a socket operation.
Cause:
Implementation error.

LNM.044

Level:
C-INFO
Short Syntax:
LNM.044 server error, code = error port port nt network msgptr
Long Syntax:
LNM.044 server error, code = error port port nt network msgptr
Description:
The indicated server component was unable to perform memory list.
Cause:
Implementation error.

LNM.045

Level:
C-INFO
Short Syntax:
LNM.045 server error, code = error port port nt network msgptr
Long Syntax:
LNM.045 server error, code = error port port nt network msgptr
Description:
The indicated server component was unable to perform an LSS parse operation.
Cause:
The TRD sent a bad packet.

LNM.046

Level:
C-INFO
Short Syntax:
LNM.046 server error, code = error port port nt network msgptr
Long Syntax:
LNM.046 server error, code = error port port nt network msgptr
Description:
The indicated server component received an error return status from LLC2.
Cause:
Implementation or execution error.

LNM.047

Level:
C-INFO
Short Syntax:
LNM.047 server error, code = error port port nt network msgptr
Long Syntax:
LNM.047 server error, code = error port port nt network msgptr
Description:
The indicated server component was unable to perform an LSCM operation.
Cause:
Configuration error.

LNM.048

Level:
C-INFO
Short Syntax:
LNM.048 server error, code = error port port nt network msgptr
Long Syntax:
LNM.048 server error, code = error port port nt network msgptr
Description:
The indicated server component received an error return status from LRM.
Cause:
Implementation or execution error.

LNM.049

Level:
C-INFO
Short Syntax:
LNM.049 server error, code = error port port nt network msgptr
Long Syntax:
LNM.049 server error, code = error port port nt network msgptr
Description:
The indicated server component received an error return status from LBS.
Cause:
Implementation or execution error.

LNM.050

Level:
C-INFO
Short Syntax:
LNM.050 server error, code = error port port nt network msgptr
Long Syntax:
LNM.050 server error, code = error port port nt network msgptr
Description:
The indicated server component received an error return status from CRS.
Cause:
Implementation or execution error.

LNM.051

Level:
C-INFO
Short Syntax:
LNM.051 server error, code = error port port nt network msgptr
Long Syntax:
LNM.051 server error, code = error port port nt network msgptr
Description:
The indicated server component received an error return status from REM.
Cause:
Implementation or execution error.

LNM.052

Level:
C-INFO
Short Syntax:
LNM.052 server error, code = error port port nt network msgptr
Long Syntax:
LNM.052 server error, code = error port port nt network msgptr
Description:
The indicated server component received an error return status from RPS.
Cause:
Implementation or execution error.

LNM.053

Level:
C-INFO
Short Syntax:
LNM.053 server error, code = error port port nt network msgptr
Long Syntax:
LNM.053 server error, code = error port port nt network msgptr
Description:
The indicated server component received an error return status from TRD.
Cause:
Implementation or execution error.

LNM.054

Level:
C-INFO
Short Syntax:
LNM.054 server error, code = error port port nt network msgptr
Long Syntax:
LNM.054 server error, code = error port port nt network msgptr
Description:
The indicated server component received a system error return status.
Cause:
Implementation error.

LNM.055

Level:
C-INFO
Short Syntax:
LNM.055 packet rcvd but no connection nt network
Long Syntax:
LNM.055 An LLC packet was received but no connection exists for net network
Description:
LNM received a LLC packet for an inactive link, possibly indicating that a previously activated link has become inactive. The data is discarded.
Cause:
The previous connection request may have been cancelled due to a netdown condition.

LNM.056

Level:
C-INFO
Short Syntax:
LNM.056 packet rcvd but SAP not open nt network
Long Syntax:
LNM.056 AN llC packet was received but the LNM SAP is not open for net network
Description:
LNM received an LLC packet, but the LNM SAP is not open, possibly indicating that the interface has gone down. The data is discarded.
Cause:
The LNM SAP may have been closed due to a netdown condition.

LNM.057

Level:
U-INFO
Short Syntax:
LNM.057 This LNM release supports only one LAN to one WAN bridge
Long Syntax:
LNM.057 This LNM release supports only one LAN to one WAN bridge
Description:
The first release of LNM (14.0a) is restricted to DNX 300 with LAN to WAN only.
Cause:
User configuration error.
Action:
Reconfigure bridge to be LAN to WAN or use any later release.

LNM.058

Level:
C-TRACE
Short Syntax:
LNM.058 LNM- major-vector direction , link link , port port , nt network
Long Syntax:
LNM.058 LNM protocol message major-vector direction , link link , port port , network network
Description:
This message traces all incoming and outgoing IBM LAN Network Manager protocol messages. Major-vectors values are described in the IBM Token-Ring Architecture Manual SC30-3374. Message direction, rcvd or sent, is indicated in the message. The link values are as follows: 0-3, if LINK is established; 242, for non-LINK messages (UNITDATA messages).

LNM.059

Level:
C-TRACE
Short Syntax:
LNM.059 MAC- MAC-vector direction , port port , nt network
Long Syntax:
LNM.059 MAC protocol message MAC-vector direction , port port , network network
Description:
This message traces all incoming and outgoing MAC messages. MAC-vector values are described in the IBM Token-Ring Architecture Manual, SC30-3370. Message direction rcvd or sent is indicated in the message.

LNM.060

Level:
UI-ERROR
Short Syntax:
LNM.060 Drp LNM frm, len frame-length , nt network
Long Syntax:
LNM.060 Dropping LNM frame, length frame-length , network network
Description:
The router is dropping an incoming message for one of two reasons: (1) The length of the frame is zero and LNM is defensively discarding the packet, or (2) LNM cannot obtain an internal LNM buffer, which is never expected to happen. The length of the frame appears so you can tell if it is reason (1) or (2). Customer service should be informed whether it is (1) or (2).