EAGLE Running 46.0 To R46.4 May Not Respond To RST Messages Coming For Eagle's INP CPC

Asset ID:	1-77-2251885.1
Update Date:	2017-08-08
Keywords:

Solution Type Sun Alert Sure

Solution 2251885.1 : EAGLE Running 46.0 To R46.4 May Not Respond To RST Messages Coming For Eagle's INP CPC

Applies to:

Oracle Communications EAGLE (Software) - Version EAGLE 46.0 to EAGLE 46.4 [Release EAGLE 46.0]
Tekelec

Description

EAGLEs running release R46.0 to R46.4 may not respond with TFA to RST messages received for INP CPC. RST messages from adjacent nodes are expected only when the route to EAGLE INP CPC is marked as prohibited on the adjacent node for some reason (not normally expected). Thus EAGLE INP CPC route status on adjacent node may remain prohibited if it gets stuck in prohibited status on adjacent node for some unknown reason.

Occurrence

This problem may occur if all of the following conditions are true.

EAGLEs running R46.0 to R46.4 release
INP CPC is defined in RTRV-SID
EAGLE receiving INP traffic to PC defined as INP CPC
INP CPC route status is stuck in prohibited status on the adjacent nodes.

Below sample capture shows INP features is tuned ON

> rtrv-ctrl-feat

    eagle 17-04-05 12:57:47 MST EAGLE5 46.0.1-65.26.26
    The following features have been permanently enabled:

    Feature Name              Partnum   Status Quantity
    Telnet                    893005701 on     ----
    EAGLE5 Product            893007101 on     ----
    HC-MIM SLK Capacity       893012707 on     64
    15 Minute Measurements    893012101 on     ----
    Spare Point Code Support 893013601 on     ----
    INP                       893017901 on     ----
    Integrated Measurements   893037301 on     ----

Below capture shows INP CPCs are defined. Here in ITUN and ITUNS domain.

> rtrv-sid

eagle 17-04-04 14:07:53 MST EAGLE5 46.0.1-65.26.26
PCA             PCI          PCN                CLLI              PCTYPE
-------------- ----------      01234              eagle             ANSI
  CPCN (INP)
00576           s-00576

Symptoms

Network cards in the system may generate "Module sccp_lim.c Line 694" severity-1 troubles.

Below trouble indicates some node is sending RST for INP CPC on the link(s) card 1204.

    eagle 17-03-18 12:25:35 AEDT EAGLE 46.0.3-65.26.29
    Card 1204   Module sccp_lim.c Line 694 Class 01c3 Severity 1
        02                                               .
    Report Date:17-03-18 Time:12:24:49
;

Note: Line number of severity can be different for different releases.

Workaround

Each execution of the procedure requires a SR. Workaround other than this not be executed without approval from EAGLE CoE. Each execution of the procedure requires a CoE collab SR.

As a workaround change any CPC provisioned as type "INP" to type "STP".

Rt-on-GT INP Queries to CPC of type “STP” when the INP local subsystem is manually inhibited (by means of user commands) will not cause a response-method TFP to be sent to the SSP.

Example

See example below for applying workaround:

Identify how many CPCs are defined in Eagle for INP service and in which domain.

> rtrv-sid

eagle 17-04-04 14:07:53 MST EAGLE5 46.0.1-65.26.26
PCA             PCI          PCN                CLLI              PCTYPE
-------------- ----------      01234              eagle             ANSI
CPCN (INP)
00576           s-00576

Here two point codes are defined as INP CPC (00576 in ITUN domain and s-00576 as ITUNS domain).

Below sample commands shows the steps to change the CPC type from INP to STP:

Take backup before and after the change.

rtrv-sid
chg-sid:CPCN=00576:ncpcn=none
chg-sid:cpcn=00576 // time between execution of these two commands CPCN 00576 will be unavailable
rtrv-sid
chg-sid:CPCN=s-00576:ncpcn=none
chg-sid:cpcn=s-00576 // time between execution of these two commands CPCN s-00576 will be unavailable
rtrv-sid

Expected sample display after applying workaround:

> rtrv-sid

     eagle 17-04-04 14:08:45 MST EAGLE5 46.0.1-65.26.26
       PCA             PCI          PCN                CLLI              PCTYPE
    -------------- ----------      01234              eagle         ANSI
       CPCN
       00576           s-00576

Follow below steps after applying the workaround to verify that necessary changes have been made successfully and RST messages for Eagle's INP CPC are being responded with TFA messages.

Run rtrv-trbl:loc=1113/1115 and see "Module sccp_lim.c Line 694" severity-1 is not occurring any more after applying the work around.

Verify in rtrv-sid INP CPC are defined as STP CPC.

Check with adjacent nodes to verify if INP CPC route status is not stuck in prohibited status.

Patches

Permanent fix for this issue will be provided in EAGLE 46.5. Planned GA 11 July 2017.

History

05-APR-2017 - KM Document Created.

06-APR-2017 - Updated Based On Review Comments

References

<BUG:25741115> - SR: EAGLE IGNORES RST FROM ADJACENT NODES FOR EAGLE'S INP CPC

Attachments

This solution has no attachment