During boot of R5.0Ux-d2.313-7-b-gr-c5s2 on a CPU6 I have the following errors :
timed run as effective root user-id.
29/06/07 07:28:09 000001I|00/28/-/---|=4:0260=Beginning of downloading binio1n
29/06/07 07:28:16 000001I|00/28/-/---|=5:0261=End of downloading binio1n
29/06/07 07:28:16 000001I|00/28/-/---|=4:0260=Beginning of downloading tonesnv
29/06/07 07:28:16 000001I|00/28/-/---|=5:0261=End of downloading tonesnv
29/06/07 07:28:16 000001M|--/--/-/---|=5:2009=Initialisation CPU role MAIN
(000226:000017) dl_id 8 appli_cap.ui 77825
(000226:000018) dl_id 34 appli_cap.ui 77825
(000226:000019) dl_id 83 appli_cap.ui 77825
(000226:000020) dl_id 84 appli_cap.ui 77825
(000226:000021) dl_id 94 appli_cap.ui 77825
spbmgr: The SPB board has not been detected
Command "SPBMGR" (pid 397) exited with status 1.
(000257:000022) Illegal coupler-type
(000257:000023) Dump: .04.03.0d.00.02.00.00.04.00.fe.f9.00.01
29/06/07 07:28:20 000001M|--/--/-/---|=0:1603=IO1 driver error, wrong telephone msg received, line 4793, length 13
29/06/07 07:28:20 000001M|--/--/-/---|=3:1607=04.03.0d.00.00.00.00.04.00.fe.f9.00.01.ff.ff
--> ACCOUNTING 0 tickets stored in database
29/06/07 07:28:29 000001M|--/--/-/---|=0:1625=4615 driver : data transmission problem number 5
29/06/07 07:28:29 000001M|00/28/-/---|=4:0260=Beginning of downloading bnvdsp0cpu6
29/06/07 07:28:29 000001M|00/28/-/---|=5:0261=End of downloading bnvdsp0cpu6
29/06/07 07:28:29 000001M|00/28/-/---|=4:0260=Beginning of downloading bnvdsp1cpu6
29/06/07 07:28:30 000001M|00/28/-/---|=5:0261=End of downloading bnvdsp1cpu6
29/06/07 07:28:33 000001M|00/28/-/---|=2:3853=Message buffer full (Inc 3 File 39 Line 408 Stat1 0)
29/06/07 07:28:33 000001M|00/28/-/---|=2:3853=Message buffer full (Inc 3 File 39 Line 408 Stat1 0)
29/06/07 07:28:34 000001M|00/28/-/---|=2:3853x072=Message buffer full (Inc 3 File 39 Line 408 Stat1 0)
29/06/07 07:28:34 000001M|00/28/-/---|=2:3853=Message buffer full (Inc 3 File 39 Line 408 Stat1 0)
29/06/07 07:28:34 000001M|00/28/-/---|=2:3853x024=Message buffer full (Inc 3 File 39 Line 408 Stat1 0)
29/06/07 07:28:54 000001M|--/--/-/---|=0:1609=2098 incidents sent by coupler (0, 28)
29/06/07 07:28:54 000001M|00/28/-/---|=2:3853=Message buffer full (Inc 3 File 39 Line 408 Stat1 0)
29/06/07 07:30:30 000001M|00/28/-/---|=2:2457=IO1 coupler (0,28) not initalized yet
The incidents 1609 & 3853 are repeated almost every 5 seconds but the system works fine. I am also a little worried about incident 2457.
These incidents appeared only when I restore the OPS files
Errors and incidents 1609 & 3853 on R5.0Ux-d2.313-7-b-gr-c5s
-
et
Re: Errors and incidents 1609 & 3853 on R5.0Ux-d2.313-7-b-gr-c5s
May be you have wrong CPU type in OPS files? For example, CPU3 instead of CPU6.
(000257:000022) Illegal coupler-type - may be this?
(000257:000022) Illegal coupler-type - may be this?
- frank
- Alcatel Unleashed Certified Guru

- Posts: 3386
- Joined: 06 Jul 2004 00:18
- Location: New York
- Contact:
Re: Errors and incidents 1609 & 3853 on R5.0Ux-d2.313-7-b-gr-c5s
wwoohhaaa, I would open a ticket with France for this, if
CPU duplication
System shutdown
System restart
does not fix it ..
CPU duplication
System shutdown
System restart
does not fix it ..
Code Free Or Die
-
Eliott_DUP
Re: Errors and incidents 1609 & 3853 on R5.0Ux-d2.313-7-b-gr-c5s
Which board is plugged at position 0-4?wizzy wrote:Code: Select all
(000257:000022) Illegal coupler-type (000257:000023) Dump: .04.03.0d.00.02.00.00.04.00.fe.f9.00.01 29/06/07 07:28:20 000001M|--/--/-/---|=0:1603=IO1 driver error, wrong telephone msg received, line 4793, length 13 29/06/07 07:28:20 000001M|--/--/-/---|=3:1607=04.03.0d.00.00.00.00.04.00.fe.f9.00.01.ff.ff ACT--------------------------------------------------------------^ ^ ^ Board---------------------------------------------------------------' ' Terminal------------------------------------------------------------------'
Post the results of:
config 0
uhwconf
cplstat 0 28
and try
rstcpl 0 6 or 0 20 (CPU position) to reset IO1
-
Boobalan Subramani
- Member
- Posts: 2
- Joined: 20 Feb 2025 21:14
Re: Errors and incidents 1609 & 3853 on R5.0Ux-d2.313-7-b-gr-c5s
We got the same error while running t3
Illegal coupler-type 0
Illegal physical terminal
Site has one way audio for all incoming and outgoing calls after power failure.
Illegal coupler-type 0
Illegal physical terminal
Site has one way audio for all incoming and outgoing calls after power failure.
