Page 1 of 1
Incident.
Posted: 07 Jun 2010 06:31
by swinstation
hi please do advice or share your experience about this incident and how can I solve it.
07/06/10 11:33:15 000001M|---/--/-/---|=0:1681=Monitel: Applicative error, type 5, info 467, PC 0x096afbbc
it repeat every 30 sec
Posted: 07 Jun 2010 08:36
by alex
Code: Select all
[B][I]incinfo GEA 1681
tradeq 467
excvisu[/I][/B]
commands will help you.
Posted: 07 Jun 2010 09:07
by swinstation
thanks for quick reply.
Posted: 08 Jun 2010 03:50
by swinstation
I am Confuse how can solve this incident that comes every 30 sec.I tried your command and you can see the results at below:
(1)cpu1> 08/06/10 11:57:41 000001M|---/--/-/---|=0:1681x004=Monitel: Applicative error, type 5, info 467, PC 0x096afbbc
(1)cpu1> incinfo 08/06/10 11:58:10 000001M|---/--/-/---|=0:1681x006=Monitel: Applicative error, type 5, info 467, PC 0x096afbbc
GEA 1681
INCIDENT NUMBER: 1681
Network indicator: Alcatel 4400
OBJECT CLASS: Dhs3x_node
EVENT TYPE: ProcessingErrorAlarm (10)
PROBABLE CAUSE: Unknown (0)
SEVERITY: Indeterminate
"Monitel: Applicative error, type P1, info P2, PC 0xP3P4"
"P1 : Type of error:"
" 1 : End of transition on a half-communication that has not positioned"
" either "wait_evt" or "waitstat"""
" 2 : use of a wait array which is not in TEL's text segment"
" 3 : variable link value is -1"
" 4 : waitxxx_timer called with an empty array of wait as parameter"
" 5 : several timers defined in a array of wait"
"P2 : Additional information, in general the logical equipment number of the"
" faulty half-communication"
"P3 : Parameters P3 et P4 represent the address of the function that has been"
" called (following the reception of an event) during the creation or"
" reactivation of the faulty half- communication"
"(Erreur applicative)"
"The application has not used properly the tools provided by Monitel."
"The functioning of the system is uncertain. In the case of error type 1 on a"
"station equipment, the station might be blocked."
"In the case of error type 1 on a "station" equipment, reinitialize the station.""
"Note the incident with all its information on an observation sheet"
"(problem report), specifying if possible the error context.";
(1)cpu1> tradeq 467
Tue Jun 8 11:58:25 IRDT 2010
..............................................................
Logic coupler type : CPL_UA
MAO coupler type : eUA32
Coupler state : IN SERVICE
Terminal state : IN SERVICE
+-----------------------------------------------------------------------------+
| Cry:Cpl:ac:term | neqt |nulog| typ term | dir nb | Out of service cause |
+-----------------------------------------------------------------------------+
| 000 17 0 0 | 00467 | 456| OP 4059| A1001 | . . . . . . . . . . |
+-----------------------------------------------------------------------------+
| A: att_mserv, C: hs_defich, I: hs_isolauto, X: hs_isolman, T: hs_terdef |
| U: hs_usdef, P: hs_errparite, B: hs_bascul, Y: hs_cristisol, N: hs_inex |
+-----------------------------------------------------------------------------+
(1)cpu1> excvisu
Tue Jun 8 11:58:34 IRDT 2010
DELIVERY h1.301
34
dyn no patch
Mon Jun 7 12:32:18 2010
(001444) btracer message to get monitel time base
(1)cpu1>
Posted: 08 Jun 2010 04:01
by alex
Yeah, infamous Rel 9!:mad:
You'd better update 4059 SW and get latest patch for OXE too.
Posted: 08 Jun 2010 07:33
by swinstation
the commissioned site is very far from my city,so do you know this incident is critical or not ?if I don't solve is it possible makes a problem like system downing or .....?
Posted: 09 Jun 2010 12:46
by swinstation
no idea?
Posted: 09 Jun 2010 15:03
by alex
napo_40 wrote:the commissioned site is very far from my city,so do you know this incident is critical or not ?if I don't solve is it possible makes a problem like system downing or .....?
No system downing. Do not worry.
Just some problems with 4059.
Posted: 10 Jun 2010 04:20
by swinstation
thanks