SCTP Link faulty, SCTP Link congestion, IP Clock link Failure

[paulus]

Hi all,

I found those kind of alarms.

These alarms could generate :1. Bad Voice & silentcall, even can't make a call or PS data
2. Drop PS

When I checked it's transmission, it's connected pass through other nodeBs before MSTP.
The physical link was not enough. Then the NodeB connection was changed to be directly connected to MSTP.

This issue cleared.

But then, after several days, this alarm came out again.

Is there any way to resolve this issue?

Here what I found in nodeB connection and some test pings.

Thanks.
Paul

[sofianonline]

Hi all,

I found those kind of alarms.

These alarms could generate :1. Bad Voice & silentcall, even can't make a call or PS data
2. Drop PS

When I checked it's transmission, it's connected pass through other nodeBs before MSTP.
The physical link was not enough. Then the NodeB connection was changed to be directly connected to MSTP.

This issue cleared.

But then, after several days, this alarm came out again.

Is there any way to resolve this issue?

Here what I found in nodeB connection and some test pings.

Thanks.
Paul

Hi Paulus,
The cause which cause SCTP link alarm could be from transmission part.
Transmission could be faulty (please check other alarm) or transmission bandwidth is not enough.
Usually, in IP mode, if congestion happened, QoS setting will be triggered to allow signaling become the first priority, but I don't know whether this setting has been configured yet or not (please check, I think not yet).
For bandwidth, please do tracing or check to transmission team for configuration in hub site.

[paulus]

Hi,

Yup, you are right.. It's mostly transmission issue. Finally, I have found out the root cause.

It's IP CONFLICT issue.

Here is LST DEVIP I got :

+++ E709G_3G_SILALAS 2012-04-04 14:49:34
O&M #37398
%%LST DEVIP:;%%
RETCODE = 0 Succeed.

Device IP address configured data
---------------------------------
Cabinet No. = Master
Subrack No. = 0
Slot No. = 7
Subboard Type = BASE_BOARD
Port Type = ETH
Port No. = 0
IP Address = 10.164.61.79 ==> THIS IP IS FOR OAM
IP Address Mask = 255.255.255.0

Cabinet No. = Master
Subrack No. = 0
Slot No. = 7
Subboard Type = BASE_BOARD
Port Type = ETH
Port No. = 0
IP Address = 10.164.144.222 ==> NOTICE THIS IP (THIS IP IS FOR SERVICES)
IP Address Mask = 255.255.255.224
(Number of results = 2)

--- END

+++ 322PC897G_3G_AKSARA_PLAZA 2012-04-04 14:47:18
O&M #34548
%%LST DEVIP:;%%
RETCODE = 0 Succeed.

Device IP address configured data
---------------------------------
Cabinet No. = Master
Subrack No. = 0
Slot No. = 7
Subboard Type = BASE_BOARD
Port Type = ETH
Port No. = 0
IP Address = 10.164.60.237 ==> THIS IS FOR OAM
IP Address Mask = 255.255.255.0

Cabinet No. = Master
Subrack No. = 0
Slot No. = 7
Subboard Type = BASE_BOARD
Port Type = ETH
Port No. = 0
IP Address = 10.164.144.222 ==> THIS IP IS AS SAME AS SILALAS IP SERVICE; THIS MAKES IP CONFLICT
IP Address Mask = 255.255.255.224
(Number of results = 2)

Herewith I Attached the result after repair the configuration.

Thanks all.

Please add my reputation if this is usefull :)

[sofianonline]

I've just already got alarm like this alarm SCTP link fault and M3UA alarm.
I do ping from router to RNC and the result is RTO (down).
You know what's the problem.....

Someone plugs out the cable (IuCS signalling) from switch to RNC board..
What a stupid engineer..