Exchange reboot unusually

[Xero]

Hi all,

Today my customer`s system (release 7) crashed and i have just reconnected the cables and rebooted the CS and the system restored automatically, i have found the following incidents:


16/05/11 17:02:42 000001M|19/01/-/---|=0:0414=IP_LINK Incident 7,19,1
16/05/11 17:02:42 000001M|19/01/-/---|=0:0414=IP_LINK Incident 5,19,1
16/05/11 17:02:49 000001M|01/00/0/254|=2:0379=Inter ACT link HS: 23,(19,1),192.168.1.10,00:80:9f:65:a5:82


for incident 414 i can see that :

IP_LINK Incident P1

P1 : Error Type
P2 : IPLINK Crystal Number
P3 : IPLINK Coupler Number
Incident Format : P1,P2,P3,P4,P5
iplink process error
Several cause
Depend of the error value P1
0 The Sotware Lock of duplication is present
1 The Link of duplication is not created
2 A link of duplication was already created
3 Receive connect_ack message but the link is already established
4 Receive unknown message
5 Lose of IP Network between CPU
6 Reference Media Gateway is up MAO enable
7 Reference Media Gateway is not declared
8 After CPU switch over, one message appears before the remote



For incident 379 I can see :

Inter ACT link HS: P1

P1 : Error type
P2 : IP Inter-crystal Link out of service
P3 : Internet address of INTIP_B
P4 : MAC Address of the INTIPB if possible
Inter-crystal signaling link problems on
link establishment or existant link shutdown
Several causes
Depend of the error value:
0 Link out of service - IP Coupleur IP not initialized
1 Link out of service - MAC Address already allowed
2 Lien out of service - IPV6 not supported
3 Link out of service - IP Coupleur lack of ressources
4 Link out of service - Non existant link
5 Link out of service - Link already set
6 Link out of service - Link down
7 Link out of service - IP coupleur Internal error
8 Link out of service - Link established
9 Link out of service - Network error
10 Link out of service - Peer not connected
11 Link out of service - On peer demand
12 Link out of service - On CPU demand
13 Link out of service - INTIPA coupleur Internal error
14 Link out of service - INTIPA out of service
22 Timout in call handling at the link establishment
T_TSCIP_CFGLINK_WAIT timer may be in cause.
23 Link out of service - No more signalling ressources
(There is no INTIPA in service).



But i am not sure if the reason is due to reference media gateway not defined, according to incident 414 then how the system was running since last 1 year....and what does the incident 379 say??? how can the signaling resources be less??


and on GD i have seen the reset history it showed:

Reset reason -1 :
startemg failed
restarting at 19:30 16 May


what does startemg failed means??

Can anyone please tell me why this issue occurred and how to protect the system from this type of issue in future.

[smileyman]

Hi Xero,

the incident 379 occures if there is no IP-link between the GD and the CS.
With the standard-config the GD do a reset if the IP-link is broken for > 7-14 seconds.

The reference-gateway is the gateway to define a main-role for a callserver in double-main-situation. - Please configure a MG as reference-gateway.

Best regards
smileyman

[Xero]

thanks smiley man, but as i have seen there was no link broken between GD and CS cable was connected properly.....and for the reference gateway which rack should i define as first expansion shelf ?? the one with main CS or the one with standby CS, and what about the law?? A law or U law or default??

and what does startemg failed says?

[yoursfather]

hi,
can you please replace LANX board and its cabinet power supply?