 |
» |
|
|
|
X.25 logging falls under the transport subsystem (SUB0006).
It logs 4 different classes of errors. They are: Class 2 — Internal Errors. This usually means a bug
somewhere. Class 3 — Resource Errors. These should be recoverable,
but a configuration adjustment may be a good idea. Class 4 — Nodal information. This is just information
about Phobos being started and stopped. Links going up and down
etc. Class 5 — Informative. Usually just a commentary
on good things happening. If problems are occurring it is good to
examine these to help. In several of the CLAS0005 informative messages, the PARM
contains the Device ID, VC number, cause, and diagnostic. The Device
ID is in the first 4 bits. This number differentiates between different
cards when multiple cards per network ar used. If only one card
is configured for the network, the Device ID is 0. The VC number
is in the next 12 bits, the cause is in the third byte, and the
diagnostic is in the fourth byte. MESSAGE: None | CAUSE: X.25 tried
to send a message, but the send_msg
call failed (PARM = status from send_msg). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: A packet
smaller than the minimum packet length (4 bytes) was received from
the DTC (PARM = length of packet). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: X.25 received
an outbound data packet from IP, but the connection is not in the
correct state to send the message. This can occur when a connection
is closing. If this happens consistently, it means that the X.25
and TCP tables are inconsistent (PARM = connection points). ACTION: Issue a NETCONTROL STOP
followed by a NETCONTROL START
to clear this condition. If this happens frequently, see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: An ALCP
packet was received with an incorrect trailer byte. The trailer
should be 1 or 3 (PARM = trailer). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: Internal
Error. Netfc_delete_pool failed.
A resource was lost. If this happens frequently, the transport will
not be able to open new connections (PARM = status from Netfc_delete_pool). ACTION: If this happens frequently,
see Appendix A “Submitting an SR ” of this
manual. |
MESSAGE: None | CAUSE: Internal
Error. Netfc_delete_pool failed.
A resource was lost. If this happens frequently, the transport will
not be able to open new connections (PARM = status from Netfc_delete_pool). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: X.25 received
an unexpected event for a particular connection's state
(PARM = state and event) ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: An incoming
connection request was rejected because the local facility does
not have a Closed User Group number configured, but the connection
request contains a Closed User Group number. ACTION: Informative message.
If you want the system to accept connection requests from members
of the Closed User Group, modify the facility set to contain the
CUG number. |
MESSAGE: None | CAUSE: A bad socket
pointer was sent by IPC after an IPShutdown
intrinsic was called (PARM = socket pointer). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: An inactivity
timer expired for the specified VC number. ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: X.25 module
has finished. ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: A failure
occurred during a read from the configuration buffer (PARM = status
and length). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: The configuration
file contains more than the allowed number of facility sets (PARM
= number of facility sets). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: An error
occurred while reading a facility set from the configuration file
(PARM = length). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: The configuration
file contains more than the allowed number of SVC paths (PARM =
number of SVC paths). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: An error
occurred while reading an SVC path from the configuration file (PARM
= length). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: Link brought
down with open connections. This is a result of either the user
doing a NETCONTROL DELLINK, or
the link failed (PARM = Connections in use on this link). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: Could not
create the Control buffer pool for this network (PARM = status from
Bmgr_create_pool). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: X.25 received
an unknown type of Information message from the Control Process
(PARM = information message type). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: X.25 received
an unknown type of Restart message from the Control Process (PARM
= restart message type). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: X.25 received
an unknown type of transport message (PARM = transport message function
code). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: X.25 received
an unknown type of IPC Control request message (PARM = IPC Control
request type). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: X.25 received
an initialization message from the Control Process when its port
data area was non zero (PARM = control server state). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: An attempt
to open a new socket has failed because the socket table is full
(PARM = number of sockets in use). ACTION: Close some of the
sockets which are no longer useful and try again. |
MESSAGE: None | CAUSE: A socket
was opened (PARM = socket's address). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: A socket
was closed (PARM = socket's address). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An operator
issued a NETCONTROL STOP command, but there are
sockets or connections currently in use. These sockets are aborted
before X.25 terminates (PARM = number of sockets and connections
in use). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An outbound
IPC connection was opened (PARM = Device ID, VC number). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An inbound
TCP/IP connection was opened (PARM = Device ID, VC number). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An inbound
IPC connection was opened (PARM = Device ID, VC number). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: A connection
was closed (PARM = Device ID, VC number). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: A connection
cannot be opened as X.25 has reached its limit for the number of
connections (PARM = number of connections in use). ACTION: Close the connections
which are no longer being used and try again. |
MESSAGE: None | CAUSE: X.25 is
out of outbound buffers. ACTION: The transport will
still work but at a reduced speed and increased CPU overhead. You
might want to increase the number of outbound buffers configured. |
MESSAGE: None | CAUSE: An incoming
connection request was rejected because it has requested reverse
charging, and this facility set does not accept reverse charge calls
(PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an
informative message. If you want to accept reverse charge calls,
modify the facility set. |
MESSAGE: None | CAUSE: An incoming
connection request was rejected because it requested packet size
negotiation, and this facility set does not negotiate packet size
(PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an
informative message. If you want to negotiate packet size, modify
the facility set. |
MESSAGE: None | CAUSE: An incoming
connection request was rejected because it requested window size
negotiation, and this facility set does not negotiate window size
(PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an
informative message. If you want to negotiate window size, modify
the facility set. |
MESSAGE: None | CAUSE: An incoming
connection request was rejected because it requested throughput
class negotiation, and this facility set does not negotiate throughout
class (PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an
informative message. If you want to negotiate throughput class,
modify the facility set. |
MESSAGE: None | CAUSE: An incoming
connection request was rejected because the address of the calling
node was not in the SVC path table and the address key POOL was
not configured (PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an
informative message. If you want to accept this call, either enter
this node's X.25 address in the SVC path screen, or enter
"POOL" as the address key. |
MESSAGE: None | CAUSE: An incoming
connection request was rejected because the security flag in the
SVC path table specified that inbound calls from this address are
not allowed (PARM = Device ID, VC number, cause, diagnostic). ACTION: This is an informative
message. If you want to accept this call, set the security flag
to IN for this the SVC path. |
MESSAGE: None | CAUSE: An incoming
connection request was rejected because the facility set associated
with this address does not exist (PARM = Device ID, VC number, cause,
diagnostic). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An incoming
connection request was rejected because the Closed User Group number
in the packet does not match the number in the facility set (PARM
= Device ID, VC number, cause, diagnostic). ACTION: None. This is an
informative message. If you want the system in the Closed User Group,
modify the facility set. |
MESSAGE: None | CAUSE: An incoming
connection request was rejected because the TCP/IP protocol was
requested but the call packet contained the fast select with restriction
facility (PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an
informative message. If you want to accept this call, modify the
remote machine so that fast select restriction is not set. |
MESSAGE: None | CAUSE: An incoming
connection request was rejected because the IPC socket with the
protocol relative address specified in the call has not been created
(PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an
informative message. Check that the program with this socket address
is running. |
MESSAGE: None | CAUSE: An incoming
connection request was rejected by the IPC user or application program
(PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An incoming
connection request was rejected because there are no outbound buffers
available. ACTION: Try again later.
Or increase the number of buffers configured and try again. |
MESSAGE: None | CAUSE: An outgoing
IPC connection request was rejected because the path report did
not contain an IP address that is in the same IP network as this
node. ACTION: Check the IP addresses
of the local and remote nodes. The network portion of the IP addresses
should be the same. |
MESSAGE: None | CAUSE: An AFCP
connection could not be opened to the DTC. The DTC card could be
fully utilized by another MPE/iX host (PARM = status from MCM). ACTION: Try again later. |
MESSAGE: None | CAUSE: An outgoing
IPC connection request was rejected. The rejection may have come
from the local DTC, the network, or the remote node (PARM = Device
ID, VC number, cause, diagnostic). ACTION: Check the diagnostic
code returned. Verify that all components are operational. |
MESSAGE: None | CAUSE: An outgoing
TCP/IP connection request was rejected. The rejection may have come
from the local DTC, the network, or the remote node (PARM = Device
ID, VC number, cause, diagnostic). ACTION: Check the diagnostic
code returned. Verify that all components are operational. |
MESSAGE: None | CAUSE: An outgoing
connection request was rejected because the AFCP connection was
closed. ACTION: Check that the DTC
is operational. Try again later. |
MESSAGE: None | CAUSE: An incoming
IPC connection request was rejected by the DTC (PARM = Device ID,
VC number, cause, diagnostic). ACTION: Check that the DTC
is still operational. |
MESSAGE: None | CAUSE: An incoming
IPC connection request was rejected by the local IPC user or application
program (PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An outgoing
connection request was rejected because the security field in the
SVC path table specifies that outgoing calls to this address are
not allowed. ACTION: If outgoing calls
to this address are desired, the security field of the SVC path
must be set to OU. |
MESSAGE: None | CAUSE: An outgoing
connection request was rejected because the specified facility set
for this address key could not be found. ACTION: Define a new facility
set for this configuration, or assign an existing facility set to
the configuration. |
MESSAGE: None | CAUSE: An outgoing
TCP/IP connection request was rejected because the connection was
requested over a PVC. ACTION: Modify the configuration
to use an SVC. |
MESSAGE: None | CAUSE: An outgoing
TCP/IP connection request was rejected because there are no outbound
buffers currently available. ACTION: Try again later,
or increase the number of buffers configured. |
MESSAGE: None | CAUSE: An outgoing
IPC connection request was rejected because the specified facility
set does not exist. ACTION: Define a new facility
set for this configuration, or assign an existing facility set. |
MESSAGE: None | CAUSE: An outgoing
IPC connection request was rejected because the specified Call User
Data field is too long. ACTION: Either decrease the
size of the call user data field or use the fast select facility,
or use the "no address" flag. |
MESSAGE: None | CAUSE: An outgoing
IPC connection request was rejected because the specified destination
node does not have an X.25 address in the configuration file. ACTION: Make sure that the
SVC path for the destination node in the configuration file matches
the Network Directory. The address keys must be the same. |
MESSAGE: None | CAUSE: An outgoing
IPC connection request was rejected because no outbound buffers
are currently available. ACTION: Try again later,
or increase the number of outbound buffers configured. |
MESSAGE: None | CAUSE: A connection
cannot be opened because no free semaphore resources are available
to create an expedited semaphore pool. Either the system is at its
limit of 1024 connections, or semaphores were steadily lost and
the supply is exhausted (PARM = status from Netfc_create_pool). ACTION: Try again later.
If the maximum number of VCs are not open, submit and SR. Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: A connection
cannot be opened because no free semaphore resources are available
to create a regular semaphore pool. Either the system is at its
limit of 1024 connections, or semaphores were steadily lost and
the supply is exhausted (PARM = status from Netfc_create_pool). ACTION: Try again later. |
MESSAGE: Internal
Error. | CAUSE: Netfc_Delete_Pool
failed on expedited semaphore pool (PARM = status from Netfc_delete_pool). ACTION: A resource was lost.
If this happens frequently, the transport will not be able to open
new connections. See Appendix A “Submitting an SR ”
of this manual. |
MESSAGE: Internal
Error. | CAUSE: Netfc_Delete_Pool
failed on regular semaphore pool (PARM = status from Netfc_delete_pool). ACTION: If this happens frequently,
the transport will not be able to open new connections. See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: Internal
Error. | CAUSE: Netfc_Create_Pool
failed right after a Netfc_Delete_Pool
(PARM = status from Netfc_create_pool). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: The link
for the X.25 network was started. ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An N-Connect
indication packet was received (PARM = Device ID, VC number). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An N-Connect
confirmation packet was received (PARM = Device ID, VC number). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An N-Disconnect
packet was received (PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An N-Disconnect
packet was sent because an IP connection's inactivity timer expired
(PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An N-Disconnect
packet was sent because an incoming connection request was rejected
(PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An N-Disconnect
packet was sent because an IPC user or application program called
an IPCShutdown intrinsic (PARM
= Device ID, VC number, cause, diagnostic). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An N-Disconnect
packet was sent because an IPC user or application rejected an incoming
connection request (PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An N-Disconnect
packet was sent because an IPC user or application has terminated
with an incoming connection request pending (PARM = Device ID, VC
number, cause, diagnostic). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An N-Disconnect
packet was sent because an IPC connection's inactivity timer expired
(PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An N-Connect
request packet was sent. ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An N-Connect
confirmation packet was sent (PARM = Device ID, VC number). ACTION: None. This is an
informative message. |
MESSAGE: None | CAUSE: An N-Connect
confirmation packet was sent (PARM = Device ID, VC number). ACTION: None. This is an
informative message. |
MESSAGE: Internal
Error. | CAUSE: A Buffer
could not be obtained from the control buffer pool (PARM = status
from Bmgr_get_buffer). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: Reading
the configuration buffer failed on a Netcontrol Update
(PARM = status and length). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: There are
more facility sets in the configuration file than allowed (PARM
= number of facility sets). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: An error
occurred while reading a facility set from the configuration file
(PARM = length). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: An N-Disconnect
packet was sent because a message arrived that was greater than
30 kilobytes (PARM = Device ID, VC number, cause, diagnostic). ACTION: Change the remote
application to send less than 30 kilobytes of data at a time. |
MESSAGE: Internal
Error. | CAUSE: Netfc_create_pool
failed right after a Netfc_delete_pool
(PARM = status from Netfc_create_pool). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: Internal
Error. | CAUSE: Netfc_delete_pool
failed on expedited semaphore pool (PARM = status from Netfc_delete_pool). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: Internal
Error. | CAUSE: Netfc_delete_pool
failed on regular semaphore pool (PARM = status from Netfc_delete_pool). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: An incoming
connection request was rejected because it requests Fast Select
and the facility does not allow Fast Select (PARM = Device ID, VC
number, cause, diagnostic). ACTION: None. This is an
informative message. If you want Fast Select, modify the facility
set. |
MESSAGE: None | CAUSE: An incoming
connection request was rejected because the local facility set has
a Closed User Group number configured, but the packet does not contain
a Closed User Group number (PARM = status from map_get_device_info). ACTION: None. This is an
informative message. If you want the remote system to be able to
establish a connection with this system, modify the remote system's
facility set to contain the Closed User Group number. |
MESSAGE: None | CAUSE: An inbound
connection request has been rejected because the device entry in
Map has been deleted. Occasionally, this can be a normal event indicating
that the link between the system and the DTC went down just after
a connection request was received by the system (PARM = Status from
map_get_device_info). ACTION: Verify that the link
between the system and the DTC is up: From the system, check for
a non-zero LDEV in the NETCONTROL STATUS;NI=x25niname>
display. From OpenView DTC Manager, check the host entries at the
end of the X.25 level 3 status display. If the link is up, try the
connection again. If this message is logged consistently, see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: An inbound
connection request has been rejected because the device state in
Map is disconnected. Occasionally, this can be a normal event indicating
that the link between the system and the DTC went down just after
a connection request was received by the system. ACTION: Verify that level
3 on the DTC\X.25 Network Access card is up. From OpenView
DTC Manager, check the level 3 status display. If level 3 is up,
try the connection again. If this message is logged consistently,
see Appendix A “Submitting an SR ” of this
manual. |
MESSAGE: Internal
Error. | CAUSE: Map_X25_Update
failed on inbound connection establishment (PARM = Status from Map_X25_Update). ACTION: See Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: Map_find_best_device
failed on outbound level 3 connection establishment Occasionally,
this can be a normal event indicating that the link between the
system and the DTC went down just after a connection request was
received by the system. (PARM = Status from Map_find_best_device). ACTION: Verify that the link
between the system and the DTC is up: From the system, check for
a non-zero LDEV in the NETCONTROL STATUS;NI=x25niname> display.
From OpenView DTC Manager, check the host entries at the end of
the X.25 level 3 status display. If the link is up, try the connection
again. If this message is logged consistently, see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: X.25 tried
to send a message to X25STAT but
the call failed. (PARM = status from send_msg). ACTION: Try running X25STAT
again. If this logging message is logged consistently, see Appendix A “Submitting an SR ” of this manual. |
MESSAGE: None | CAUSE: Link brought
down with open connections. This is a result of a Netcontrol Stop
on this X.25 network. (PARM = Connections in use on this link). ACTION: None. This is an
informative message. |
MESSAGE: Internal
Error. | CAUSE: BMGR_DELETE_POOL
call failed while start sequence was aborting. (PARM= status from
call). ACTION: See Appendix A “Submitting an SR ” of this manual. |
|
