1. Unsolicited Alarm and Information Messages Reference
  2. UAM and UIM Troubleshooting Procedures
  3. UIMs
  4. 1332 - Invalid Initial M2PA FSN Received

1332 - Invalid Initial M2PA FSN Received

The Eagle received an initial M2PA DATA message with an invalid FSN (Forward Sequence Number). The expected FSN in M2PA for the first DATA message received after link alignment is 0 for M2PA RFC. Older versions of M2PA (before Draft 9) used an initial FSN of 1. This UIM indicates that the two ends of the link have mismatched configurations.

  • Eagle versions prior to 34.3 support M2PA Draft 6 but do not support M2PA RFC.

  • If both ends of the M2PA association are on Eagle release 34.3 or later, verify that both ends have the VER parameter set to match on the M2PA association (VER=D6 or VER=M2PA must be the same on both ends).

  • If one end of the M2PA association is on an Eagle release prior to 34.3 and the other is 34.3 or greater, verify that the association VER parameter in the later release is set to D6 for backward compatibility.

Example 
RLGHNCXA21W 00-04-18 19:09:14 EST EAGLE 34.3.0
5781.1332 CARD 1301,A INFO Invalid Initial M2PA FSN Received
Legend
FSN
Forward Sequence Number
M2PA
SS7 MTP2 - User Peer-to-Peer Adaptation Layer

Alarm Level: No alarm condition. The message is informational only. However, the link will not stay aligned and a link alarm will be present.

Recovery

  1. To change the M2PA version used by the signaling link at the Eagle perform the following commands:
    1. Use the dact-slk:loc=xxxx:link=yy command to deactivate the signaling link.
    2. Use the chg-assoc:open=no command to close the M2PA association used by the signaling link.
    3. Use the chg-assoc:ver=<d6/rfc> command to change the M2PA version on the association used by the signaling link to match the configured M2PA version of the M2PA peer.
    4. Use the chg-assoc:open=yes command to activate the M2PA association used by the signaling link.
    5. Activate the signaling using the act-slk:loc=xxxx:link=yy command.
  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 My Oracle Support (MOS).