NS3000/iX Error Messages Reference Manual (36923-90043)

Chapter 21 473
Logging Location Codes
Using Log Files
NetIPC log message. Look for the identical number called the
Socket Port ID in the NetIPC log message.
• Bytes sent/received. Shows the total number of bytes transmitted
or received by the PM.
• User pkts sent/recd. Shows the number of packets sent or
received. May be more than the number of User Sends/Receives
because TCP may need to fragment the message into link-size
packets.
• PM pkts sent/recd. Shows the number of non-data carrying
packets sent or received, such as window updates and
acknowledgments.
• Cn ass pkts sent/recd. Shows the number of connection assurance
packets sent or received. A large number of these indicate that the
connection is idle for long periods of time.
• User sends/receives. Shows the number of messages sent or
received.
• Pkts discarded/rtx’ed. The number of packets discarded or
retransmitted. If there is a problem with the connection, it may be
reflected here by an extremely high number for one of these fields.
Check for Class 3 logging messages; refer to the specific location code
for more information.
• Checksum errors. Shows the number of checksum errors for this
connection. Check for Class 3 logging messages; refer to the specific
location code for more information.
• Smooth R/T delay. Shows the observed delay (in milliseconds)
required to receive acknowledgments from the remote node. This
number is used by TCP to dynamically calculate the retransmission
timer.
• Init recv/send window. Shows the size of the window used for flow
control. The size varies for each service.
• Recv/Send burst size. Shows the burst size for the receiver and
the sender. This value is specified with the IPCCONNECT used to
initiate the connection.
• Max send/recv size. Shows the maximum message size for the
receiver and the sender. This value is specified with the IPCCONNECT
used to initiate the connection.
• Local/Remote SAP. Shows the TCP Service Access Point address
for the local and the remote node. If you do not know which
application to check on the remote node, use these numbers
(reversed) to find the matching PM in the log file for the remote
node. Specify a time range when formatting the remote node log file
to narrow the search.