Use this command to report on the user adapter (UA) state machine history for a specified association name. State machine history is kept in a circular buffer in memory. The -i and -x options are used to include or exclude groups of events from the state machine history.

Options

Options and option parameters that are underlined indicate that a value must be specified for that option or parameter. For example, the ualog command has the parameter aname. The association name must be specified for which the user adapter log will be displayed, as in the command ualog s7000. Do not enter the underlined option or parameter; enter a value for the information represented by the underlined option or parameter.

This option specifies the association name for the display.

This option displays help (usage) information for the command.

This option includes groups of events in the state machine history.

Range:

service

ua

This option excludes groups of events from the state machine history.

Range:

service

ua

Example

Dependencies

None

Notes

None

Output

    rlghncxa03w 05-07-27 08:10:00 EST  EAGLE5 34.0.0
    PASS: Command sent to card
;
    rlghncxa03w 05-07-27 08:10:00 EST  EAGLE5 34.0.0
    UALOG command in progress
;
    rlghncxa03w 05-07-27 08:10:00 EST  EAGLE5 34.0.0

    UALOG: User Adapter state history log
           UA Version: 01
           ASP ID:0x00000002
           User Adapter Implemented: M3UA RFC
           Current settings: -i service ua

    Date      Time           ASP Event
    -----------------------------------------------
    05-07-27  17:17:46.940   Management Socket Open
    05-07-27  17:17:46.940   Transition to Connecting
    05-07-27  17:17:47.500   Socket Allowed for Traffic
    05-07-27  17:17:49.375   Socket Connection Established
    05-07-27  17:17:49.375   Transition to ASP-DOWN
    05-07-27  17:17:49.390   ASPUP PDU Received (ASP ID = 0x00000002)
    05-07-27  17:17:49.390   ASPUPACK PDU Transmitted
    05-07-27  17:17:49.390   Transition to ASP-INACTIVE LOADSHARE (RC=none)
    05-07-27  17:17:49.390   AS INACTIVE NTFY PDU Transmitted (RC=none)
    05-07-27  17:17:49.405   ASPACTIVE PDU Received (RC=none)
    05-07-27  17:17:49.405   ASPACTIVEACK PDU Transmitted (RC=none)
    05-07-27  17:17:49.405   Transition to ASP-ACTIVE LOADSHARE (RC=none)
    05-07-27  17:17:49.405   AS ACTIVE NTFY PDU Transmitted (RC=none)
    05-07-27  17:17:50.405   ASP INACT NTFY PDU Transmitted (ASP ID = 0x00000005)
    05-07-27  17:17:50.405   ASP ACT NTFY PDU Transmitted (ASP ID = 0x00000005)
    05-07-27  17:17:52.730   ASP FAILURE NFY PDU Transmitted (ASP ID = 0x00000003)

    UALOG command complete
;

Command Accepted - Processing
    rlghncxa03w 05-07-27 08:10:00 EST  EAGLE5 34.0.0
    pass:loc=1105:cmd="ualog s7000"
;

    rlghncxa03w 05-07-27 08:10:00 EST  EAGLE5 34.0.0
    PASS: Command sent to card
;

    rlghncxa03w 05-07-27 08:10:00 EST  EAGLE5 34.0.0
    UALOG command in progress
;

    rlghncxa03w 05-07-27 08:10:00 EST  EAGLE5 34.0.0

    UALOG: User Adapter state history log
           UA Version: 01
           ASP ID: 0x00000007
           User Adapter Implemented: SUA RFC
           Current settings: -i service ua

    Date      Time           Event
    -----------------------------------------------
    05-07-27  19:45:33.265   CLDT PDU Transmitted(RC=0000000001)
    05-07-27  19:48:07.490   ASPINACTIVE PDU Received(RC=none)
    05-07-27  19:48:07.490   ASPINACTIVEACK PDU Transmitted(RC=0000000002)
    05-07-27  19:48:07.490   Transition to ASP-INACTIVE LOADSHARE(RC=0000000002)
    05-07-27  19:48:07.490   AS PENDING NTFY PDU Transmitted(RC=0000000002)
    05-07-27  19:48:07.500   AS INACTIVE NTFY PDU Transmitted(RC=0000000002)
    05-07-27  19:48:19.730   ASPACTIVE PDU Received(RC=0000000001)
    05-07-27  19:48:19.730   ASPACTIVEACK PDU Transmitted(RC=0000000001)
    05-07-27  19:48:19.730   Transition to ASP-ACTIVE LOADSHARE(RC=0000000001)
    05-07-27  19:48:19.730   AS ACTIVE NTFY PDU Transmitted(RC=0000000001)
    
    UALOG: command complete
;

When a M3UA or SUA PDU is received that contains one or more errors, a response error message is transmitted containing an error code. Error codes are recorded to and displayed in the UALOG only when the UA peer-to-peer message logging option is enabled (-i ua), as shown.

Command Accepted - Processing
    rlghncxa03w 05-07-27 08:10:00 EST  EAGLE5 34.0.0
    pass:loc=1315:cmd="ualog assoc1315a1"
    Command entered at terminal #3.
;

    rlghncxa03w 05-07-27 08:10:00 EST  EAGLE5 34.0.0
    PASS: Command sent to card
;

    rlghncxa03w 05-07-27 08:10:00 EST  EAGLE5 34.0.0

    UALOG command in progress
;
 
   rlghncxa03w 05-07-27 08:10:00 EST  EAGLE5 34.0.0

    UALOG: User Adapter state history log
           UA Version: 01
           ASP ID:undefined
           User Adapter Implemented: M3UA RFC
           Current settings: -i service ua
                              
    Date      Time           Socket Event
    -----------------------------------------------
    05-07-27  17:17:46.940   Management Socket Open
    05-07-27  17:17:46.940   Transition to Connecting
    05-07-27  17:17:49.375   Socket Connection Established
    05-07-27  17:17:49.375   Transition to ASP-DOWN
    05-07-27  17:17:49.390   ASPUP PDU Received (ASP ID = undefined)
    05-07-27  17:17:49.390   ASPUPACK PDU Transmitted
    05-07-27  17:17:49.390   Transition to ASP-INACTIVE LOADSHARE
    05-07-27  17:17:49.390   AS INACTIVE NTFY PDU Transmitted
    05-07-27  17:17:49.405   ASPACTIVE PDU Received
    05-07-27  17:17:49.405   ASPACTIVEACK PDU Transmitted
    05-07-27  17:17:49.405   Transition to ASP-ACTIVE LOADSHARE
    05-07-27  17:17:49.405   AS ACTIVE NTFY PDU Transmitted
    05-07-27  17:17:49.450   DAUD PDU Received
    05-07-27  17:17:49.480   ERR PDU Transmitted (0x00000015)

    UALOG command complete
;

Error Codes

Error codes that can appear in the error messages:

• 0x01—Invalid Version

  A message was received with an invalid or unsupported version. The error message contains the supported version in the Common Header.

• 0x03—Unsupported Message Class

  A message was received with an unexpected or usupported Message Class.

• 0x04—Unsupported Message Type

  A message was received with an unexpected or usupported Message Type.

• 0x05—Unsupported Traffic Handling Mode

  This error is sent by a Signaling Gateway Process (SGP) if an Application Server Process (ASP) sends an ASP Active message with an unsupported Traffic Mode Type or a Traffic Mode Type that is incomsistent with the currently configured mode for the Application Server (AS).

• 0x06—Unexpected Message

  This error message can be sent if a defined and recognized message is received that is not expected in the current state. In some cases the ASP might silently discard te message and not send an error message. Silent discard is used by an ASP if it received a DATA message from a signaling point while the ASP is in the ASP-INACTIVE state. If the unexpected message contains Routing Context, the Routing Context can be included in the error message.

• 0x07—Protocol Error

  This error message is sent for any protocol anomaly, such s rception of a parameter tha is syntactically correct but unexpected in the current situation.

• 0x09—Invalid Stream Identifier

  A message is received on an unexpected SCTP stream (for example, a Management message was received on a stream other than 0).

• 0x0d—Refused - Management Blocking

  An ASP Up or ASP Active message is received and the request is refused for management reasons (such as management lockout). If this error is in response to an ASP Active message, the Routing Context in the ASP Active message can be included in the error message.

• 0x0e—ASP Identifier Required

  This error message is sent by an SGP in response to an ASP Up message that does not contain an ASP Identifier parameter when the SGP requires one. The ASP should resend the ASP Up message with an ASP Identifier.

• 0x0f—Invalid ASP Identifier

  This error message is sent by an SGP in responseto an ASP Up message with an invalid (for example, non-unique) ASP Identifier

• 0x11—Invalid Parameter Value

  A message is received with an invalid parameter value (for example, a DUPU message was received with a Mask value other than 0).

• 0x12—Parameter Field Error

  A message is received with a parameter that has a wrong length field.

• 0x13—Unexpected Parameter

  A message contains an invalid parameter.

• 0x14—Destination Status Unknown

  This error message can be sent if a DAUD is received at a Signaling Gateway (SG) asking for the availability/congestion status of a destination, and the SG does not provide the status (as in the case when the sender is not authorized to know the status). For this error, each invalid or unauthorized Point Code is be included along with the Network Appearance and/or Routing Context associated with the Point Code.

• 0x15—Invalid Network Appearance

  This error message is sent by an SGP if an ASP sends a message with an invalid (unconfigured) Network Appearance value. For this error, the invalid (unconfigured) Network Appearance is be included in the Network Appearance parameter.

• 0x16—Missing Parameter

  A message is received, and a mandatory parameter is not included in the message.

• 0x19—Invalid Routing Context

  A message is received from a peer with an invalid (unconfigured) Routing Context value. The invalid Routing Context is included in the error message.

• 0x1a—No Configured AS for ASP

  A message is received from a peer without a Routing Context parameter, and it is not known by configuration data which Application Servers are referenced.