Alarm on Ericsson BSC : SCTP failure with reason PPP not used AS APP

Hello Experts,

I have encountered an alarm on Ericsson BSC for association path with reason PPP not used AS APP. Please support.

Hi. @Sooraj, I didn’t find it in ELEX. Maybe you have a newer SW. Can you share full text, how exactly it looks.

Hi, @Sooraj

Alarm raised with reason PPP NOT USED AS APP means PPP is not used as Active Primary Path (APP) for this association and is ceased if any of the following happens:

  • Association state changes to DOWN (higher level alarm “SCTP ON CP ASSOCIATION STATUS CHANGE” is then issued),
  • Switchback to PPP is performed,
  • PPP changed by the operator,
  • SM is disabled.

Hi @vlr9999

Please find below details:

Hi @JustDoit Thanks, we have two AOIP for this BSC. All sctp connection works fine with one IP, whereas with another IP we are getting this alarm

Please provide this print:

ihclp:said=xxx; ! ‘said’ get from alarm !

Hi,

Please find below details

IHSSP:SAID=…,STAT;

IHSAP:said=…;
Check from MSS side for differences in the values of the parameters, i.e. BUF and THR. They must be the same on both sides!
Also, the following recommends to Check the patch cords + SFP on the transport hardware side.

For the issue AoIP, I can see IPPST NOT ACTIVE. Please suggest what does it mean.

IP path is unable to carry traffic. The value of the T3 error counter on the IP path has exceeded PMR.
Check from MSS side also. And check IHSAP from both sides.

Also, check in the IHAPP:SAID=…; values for RTOMI, RTOMA, RTOI. Recommended values are 200, 800 and 400 respectively.

I checked RTOMI/RTOMA/RTOI. Values are 100/400/200. SCTP is good with APRIP/APLIP. Problem is with PRIP PLIP IP

Ok. I see that values are “Default”, but not recommended…
Check from MSS side. Maybe they can reset from MSS side this SAID (RIP).

How can I check from when this alarm has been observed?

RIP is Remote IP - this is from MSS side
LIP - Local IP - BSC side

I would like to know how to check at what time and date this alarm might have occurred from BSC like alarm history.

U can see date/time on the Header of the alarm. But if u want to see history, you can do this on the monitoring server - OSS/ENM.

As a result, there is no such alarm in allip; command right now? Is she not active?

Yes we still have in allip;.