1333 - UA RCVD MSG DISCARDED

When processing a received PDU at the UA L2 layer, various errors can be detected which cause the MSU to be pegged and discarded. The SG responds to a number of these MSU’s with error messages and transmits them to the customer. Some scenarios exist where a received PDU causes an error to be pegged, the message to be discarded, and the SG to not respond with an error message. A new UIM is issued when a PDU excluding UA ERROR messages is received at the UA L2 layer and results in the SG discarding the message plus pegging an error count. The generation of this UIM is paced (every 30 seconds), and in situations where multiple messages are discarded within a 30 second window of time, a UIM is only generated for the first message discarded.

Example 
    RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 38.0.0 
    0003.1333    CARD 1305,A   INFO    UA RCVD MSG DISCARDED
                 IP CONNECTION NAME=LONGCONNECTNAME ADPTR=M3UA
                 REASON=Large MSU for IP Sig Not Supported
                 SIO=0D OPC=1-1-1          DPC=2-2-2
                 Report Date:yy-mm-dd  Time:hh:mm:ss

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. The following table summarizes why the UIM was issued.

    The “reason” text in the UIM identifies why the UIM was displayed. Look at the reason and take action based on that field. Most of the time, to correct the issue, the customer needs to stop issuing the message. The UIM’s diagnostic field usually indicates which message was received.
    SG Received Messages Discarded

    REASON MSG DISCARDED AND PEGGED

    UIM ’REASON’ TEXT

    UIM ‘DIAGNOSTIC’ TEXT

    PDU received with invalid version

    Invalid Version (Error Code=0x01)

    <msg rcvd> Rcvd; Version=<version value rcvd>

    Ex. ASP-Inactive Rcvd; Version=0x02

    1. PDU has unsupported class

    3. PDU received was SUA CLDT/CLDR on an M3UA Association

    Unsupported Message Class (Error Code=0x03)

    Class=<Message Class Value>; Type=<Message Type Value> Ex: Class=0x09; Type=0x01

    PDU has unsupported type

    Unsupported Message Type (Error Code=0x04)

    Type=<Msg Type Value >; Class=<Message Class Value >

    Ex: Type=0x15; Class=0x02

    ASP-ACTIVE contains an unsupported traffic mode Type.

    Unsupported Traffic Mode (Error Code=0x05)

    <MSG> Rcvd; Mode=<traffic mode received >

    Ex : ASP-Active Rcvd; Mode=0x03

    1. PDU received was DAVA/DUNA/DRST/DUPU in the ASP-Inactive/ASP-Active States(end nodes shouldn’t generate these)

    2. ASP-UP received while in ASP-ACTIVE state

    3. ASP-ACTIVE received while in ASP-DOWN state

    Unexpected Message (Error Code=0x06)

    1. DUNA Msg Rcvd

    2. DAVA Msg Rcvd

    3. DRST Msg Rcvd

    4. DUPU Msg Rcvd

    5. ASP-UP Rcvd while in ASP-Act State

    6. ASP-Act Rcvd while in ASP-Down State

    1. PDU could not be decoded or invalid length.

    2. ASP-UP-ACK/ASP-DOWN-ACK/

    ASP-ACTIVE-ACK/ASP-INACTIVE-ACK received in the ASP-Inactive/ASP-Active States while in server mode (not client)

    3. ASP-INACTIVE-ACK received while in client mode and in ASP-ACTIVE state

    4. DATA contains multiple routing contexts

    Protocol Error (Error Code=0x07)

    1. <Message> Decode Failed

    2. <Message> Encode Failed

    3. <Message> Length Invalid

    4. ASP-UP-Ack Rcvd

    5. ASP-Down-Ack Rcvd

    6. ASP-Active-Ack Rcvd

    7. ASP-Inactive-Ack Rcvd

    8. M3UA to MTP3 Conversion Failed

    ASP-UP received on a connection this is Deactivated or Blocked.

    Refused Managment Blocking (Error Code=0x0d)

    ASP-Active Rcvd when SLK OOS-MT-DSBLD

    Sent if a UA Message is received with an invalid parameter value.

    Invalid Parameter Value (Error Code=0x11)

    <msg rcvd> Rcvd; Value=<parameter value rcvd >

    Ex. ASP-Inactive Rcvd; Value=0x00000009

    PDU has fixed length parameters of incorrect size

    Parameter Field Error (Error Code=0x12)

    <msg rcvd> Rcvd; Length=<invalid parameter length >

    Ex. ASP-Inactive Rcvd; Length=0x0200

    Sent if a UA message received contains an invalid parameter.

    Unexpected Parameter (Error Code=0x13)

    <msg rcvd> Rcvd; Parm Tag=<parameter tag rcvd >

    Ex. DATA Rcvd; Parm Tag=0x0500

    Invalid Network Appearance value received in a M3UA message

    Invalid Network Appearance (Error Code=0x15)

    <Msg Type> Rcvd; NA=<NA value rcvd >

    Ex: DAUD Rcvd; NA=0x00000011

    1. PDU is missing one or more mandatory parameters

    2. DATA contains no routing context and the association the PDU was received on is configured with more than 1 routing context

    Missing Parameter (Error Code=0x16)

    1. <Msg Type> Rcvd; Missing Tag=<tag value >

    2. Hdr Len Invalid

    1. ASP-ACTIVE received with routing context but no routing key(s) are provisioned for linkset

    2. PDU contains one or more routing contexts that could not be matched to one associated with the connection the PDU was received on

    Invalid Routing Context (Error Code=0x19)

    For this error code, use existing UIM “Mismatched UA Routing Context” only if the message is still processed. If the message is discarded, issue UIM format 62.

    <msg rcvd> Rcvd; RC=<routing context value>

    Ex: DAUD Rcvd; RC=0x00000008

    DATA received while in the ASP-Inactive State (server mode)

    Invalid ASP State

    DATA Rcvd while in ASP-Inact State

    A message was discarded and there is no error code.

    No ERR Received

    Reason Unknown

  2. Otherwise change the M2PA version at the M2PA peer to match the version configured for the signaling link/association at the Eagle.
  3. If the fault is not cleared contact the My Oracle Support (MOS).
Parent topic: UIMs