Alcatel Unleashed

I have a board INTIPb it restarts without warning at random. You can reset 2 times in a week or once every six months.

I've changed the board, board compressors and updated to the last release 9.1 i605.41 from the update has lasted longer, but repeated failure after 4 months without failure.

Any idea possible solution ?, The remaining shelf fails them.

Deputy error.

26/03/15 13:00:08 001001M|012/04/0/000|=3:1306=MCDU table distri gpe OPE 1, colonne Night , ligne 5 incorrect ou absent
26/03/15 13:01:03 001001M|009/01/0/254|=2:0379=Lien inter Crystal HS: 23,(19,1),131.4.254.13,00:80:9f:53:99:f3
26/03/15 13:01:03 001001M|009/--/-/---|=2:2043=Perte du CRYSTAL 9
26/03/15 13:01:03 001001M|009/01/-/---|=2:2042=Perte d'un coupleur de type INTIPB/INTIP3B
26/03/15 13:01:03 001001M|009/06/0/000|=4:2011=Plus d'IT entre CR 9 et CR 12 ouplus de ressource de conférence
26/03/15 13:01:03 001001M|009/02/-/---|=2:2042=Perte d'un coupleur de type UA
26/03/15 13:01:03 001001M|009/06/0/000|=4:2011=Plus d'IT entre CR 9 et CR 12 ouplus de ressource de conférence
26/03/15 13:01:03 001001M|009/06/0/000|=4:2011=Plus d'IT entre CR 9 et CR 12 ouplus de ressource de conférence
26/03/15 13:01:03 001001M|009/03/-/---|=2:2042=Perte d'un coupleur de type Z
26/03/15 13:01:03 001001M|009/04/-/---|=2:2042=Perte d'un coupleur de type PRA
26/03/15 13:01:03 001001M|009/05/-/---|=2:2042=Perte d'un coupleur de type UA
26/03/15 13:01:03 001001M|009/06/-/---|=2:2042=Perte d'un coupleur de type PRA
26/03/15 13:01:03 001001M|009/06/0/000|=4:2085=Arret synchronisation T2 sur coupleur (9,6)
26/03/15 13:01:03 001001M|009/07/-/---|=2:2042=Perte d'un coupleur de type PRA
26/03/15 13:01:03 001001M|009/08/-/---|=2:2042=Perte d'un coupleur de type UA
26/03/15 13:01:03 001001M|009/09/-/---|=2:2042=Perte d'un coupleur de type BRA
26/03/15 13:01:42 001001M|009/01/-/---|=4:0740=Début de téléch. d'une carte INT/IP @:00.80.9f.53.99.f3 (binintip)
26/03/15 13:01:42 001001M|009/01/-/---|=4:0740=Début de téléch. d'une carte INT/IP @:00.80.9f.53.99.f3 (binintip_app
26/03/15 13:01:42 001001M|009/01/-/---|=5:0741=Fin de téléch. d'une carte INT/IP @:00.80.9f.53.99.f3 (binintip_app
26/03/15 13:02:33 001001M|009/01/-/---|=5:0409=Le lien inter-ACT sur IP depuis (19,1) est prêt
26/03/15 13:02:34 001001M|009/01/-/---|=2:1735=Exception dans le logiciel de lacarte
26/03/15 13:02:34 001001M|009/01/-/---|=0:5857=GD/GA/INTIP/RGD : raison de redémarrage 4

(101)xacesce> incinfo GEA 0379

INCIDENT NUMBER: 379
Network indicator: Alcatel 4400
OBJECT CLASS: Dhs3Terminal
EVENT TYPE: EquipmentAlarm (4)
PROBABLE CAUSE: Unknown (0)
SEVERITY: Major

"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)."
" 24 Link out of service - following INTIPA deletion"
"no reaction of the system."
"Check IP ressources boards within intipb."
"To see timer used tabtemp tool.";

hi

why it should be the intip problem and not your network?

The network did not keep me, is the client.
The network has changed port switch and Cisco technicians say okay port.
The good thing is that the board is on the same switch that the CS and shelf with GD I have not restarted remotely.

I read in another topic, which is recommended to perform Intip to full duplex.

Is that correct?

thx

how it is possible the OXE working for 4 months and then unexpected to reboot the self?
the switch has any logs to see what is going on there?

But the error that in theory puts the PBX is "23 Link out of service - No more signaling ressources" -->"Check IP ressources boards within intipb."

So you believe that this is due to a cut of network.

What regards the error, not more signaling ressources?

Thank You

If it was a symptom that is happening often i could say there smthg wrong with intip or the pbx. but after 4 months?
the ethernet link could be up but no trafic on it..

since you changed the Board and upgrade it to the latest patch Investigate the switch i would say ...

Agree, seems more a network problem. Is that locally connected or over some WAN?
The fact that switch port is fine on HW doesn't mean there is no problem at all on network. What about delay, packet loss, QoS? Many things to check

also do not forget to think simple... maybe the network patch cable is a problem.

regards...

What about this 6/03/15 13:02:34 001001M|009/01/-/---|=2:1735=Exception dans le logiciel de lacarte
from incinfo :
"Exception in coupler's software"
"An exception has occurred in the coupler's software."
"The coupler is stopped. It has to start again. Function calls stack is"
"stored in exception file."
"Note the incident with all its information on an observation sheet"
"(problem report), specifying if possible the error context."
"From the R1.4 release recupexc or excvisu to pull out the backtrace.";

Ohhh nice one!
Assuming firmware may be corrupted...how on earth to reload it?