Page 1 of 1

NDDI registered not initialised

Posted: 24 Mar 2018 23:06
by bcmir
Hi all,
I have a problem with an ACT (2 crystal shelves) 4400:
System has an NDDI board which is REGISTERED NOT INITIALISED. I also have an INTOF board which is failing (appears to be hardware error, since when I swap INOFA & INTOFB the INTOFB board works ok in first crystal shelf)
I have tried:
Swapping out NDDI board
Rstcpl NDDI
Rebooting CPU numerous times
Deleting NDDI and re-creating all terminals.

config 0

+-------------------------------------------------------------------------+
| Cr | cpl | cpl type | coupler state | coupler ID |
|----|-----|--------------|--------------------------|--------------------|
| 0 | 0 | MMSFD | ONLY IN MAO FILE| BAD PCMS CODE |
| 0 | 1 | CPU6 | IN SERVICE| BAD PCMS CODE |
| 0 | 3 | UA32 | IN SERVICE| 3BA53050ABBC01 |
| 0 | 4 | INTOF_A |REGISTERED NOT INITIALIZED| 3BA53118AACB02 |
| 0 | 5 | PRA2 | IN SERVICE| 3BA23076AAAC03 |
| 0 | 6 | Z24_2 | IN SERVICE| 3BA53065NACF02 |
| 0 | 8 | NDDI |REGISTERED NOT INITIALIZED| BAD PCMS CODE |
| 0 | 9 | VG | IN SERVICE| 3BA53077ABAC02 |
+-------------------------------------------------------------------------+

--- Inter Crystal Topology ---

+-------------------------------------------------------------------------+
| CR | CPL Type Role Free/Tot Role Type CPL | CR |
|-------------------------------------------------------------------------|
| 00 | 04 -INTOF_A (INT_HS ) -X- 00/00 -X- ( INT_HS) INTOF_B - 01 | 01 |
|-------------------------------------------------------------------------|

Should I try upgrading to a later patch of firmware (current is R4.1-d1.311.7-i-as-c6s2) as there seems to be a glitch between CPU6 and NDDI board (Error 3001 see below)
Does anyone have a download of R4.1 available ?

Or is a new CPU board required ? .. please HELP!!

I have the follow incvisu readout (shows error 3001 with explaination below)

(1)xa000001> incvisu
25/03/18 13:45:44
25/03/18 13:45:54 000001I|--/--/-/---|=2:4351=Incoherent data: appli INITREM table No 292 cause 0 info 2000 -1 -1
25/03/18 13:46:01 000001I|--/--/-/---|=2:2199=A4400 Version : R4.1-d1.311-7-i-as-c6s2
25/03/18 13:46:07 000001I|--/--/-/---|=5:1528=Test from chorus if incidents handler is running
25/03/18 13:47:00 000001I|--/--/-/---|=2:2176=A dynamic patch has been installed for TEL
25/03/18 13:47:01 000001I|--/--/-/---|=2:2176=A dynamic patch has been installed for alb
25/03/18 13:47:02 000001I|--/--/-/---|=2:2176=A dynamic patch has been installed for main_afe
25/03/18 13:47:02 000001I|--/--/-/---|=2:2176=A dynamic patch has been installed for cstamono
25/03/18 13:47:03 000001I|--/--/-/---|=2:2176=A dynamic patch has been installed for internal_t
25/03/18 13:47:03 000001I|--/--/-/---|=2:2176=A dynamic patch has been installed for maoagent
25/03/18 13:47:06 000001I|--/--/-/---|=4:0260=Beginning of downloading binloaderio1n
25/03/18 13:47:06 000001I|--/--/-/---|=5:0261=End of downloading binloaderio1n
25/03/18 13:47:18 000001I|00/28/-/---|=4:0260=Beginning of downloading tonesnv
25/03/18 13:47:18 000001I|00/28/-/---|=5:0261=End of downloading tonesnv
25/03/18 13:47:18 000001M|--/--/-/---|=5:2009=Initialisation CPU role MAIN
25/03/18 13:47:19 000001M|--/--/-/---|=4:1367=DECT network initialization
25/03/18 13:47:21 000001M|--/--/-/---|=4:1436=Activation of the driver for the A4615, which will download the boot : boot4615.
25/03/18 13:47:22 000001M|--/--/-/---|=0:1625=4615 driver : data transmission problem number 5
25/03/18 13:47:22 000001M|00/28/-/---|=4:0260=Beginning of downloading bnvdsp0cpu6
25/03/18 13:47:23 000001M|00/28/-/---|=5:0261=End of downloading bnvdsp0cpu6
25/03/18 13:47:26 000001M|00/06/-/---|=4:0260=Beginning of downloading bindspz2cx
25/03/18 13:47:28 000001M|00/05/-/---|=4:3512=CPU ordered a reset
25/03/18 13:47:33 000001M|00/06/-/---|=5:0261=End of downloading bindspz2cx
25/03/18 13:47:33 000001M|00/06/-/---|=4:3512=CPU ordered a reset
25/03/18 13:47:38 000001M|00/03/-/---|=4:3512=CPU ordered a reset
25/03/18 13:47:43 000001M|00/03/0/005|=4:2151=Undeclared subdevice EAK present
25/03/18 13:48:21 000001M|00/09/-/---|=5:2019=USCVG coupler commissioning
25/03/18 13:48:30 000001M|00/06/-/---|=5:2019=Z coupler commissioning
25/03/18 13:48:40 000001M|00/03/-/---|=5:2019=UA coupler commissioning
25/03/18 13:48:59 000001M|00/05/0/000|=4:2113=T2 lapD not established still trying
25/03/18 13:49:07 000001M|00/01/-/---|=5:2169=Main CPU initialization completed
25/03/18 13:49:09 000001M|00/05/-/---|=3:2103=T2 access end of 75 time-out unusual
25/03/18 13:49:28 000001M|00/05/-/---|=5:2019=PRA coupler commissioning
25/03/18 13:51:03 000001M|00/28/-/---|=2:2457=IO1 coupler (0,28) not initalized yet
25/03/18 13:51:03 000001M|00/04/-/---|=2:2457=INT2A coupler (0,4) not initalized yet
25/03/18 13:51:03 000001M|00/08/-/---|=2:2457=NDDI coupler (0,8) not initalized yet
25/03/18 13:55:09 000001M|--/--/-/---|=2:2166=CPU requires Reset CPL NDDI (0,8) Cause 0
25/03/18 13:55:09 000001M|00/28/-/---|=3:3001=IO transm. fault 0 3 8 4 0 0
25/03/18 13:55:10 000001M|00/28/-/---|=3:3001=IO transm. fault 0 3 8 8 0 0
25/03/18 13:55:10 000001M|00/28/-/---|=3:3001=IO transm. fault 0 3 8 12 0 0

Incinfo 3001 :

IO transm. fault P1 P2 P3 P4 P5 P6

P1 : Sense of the transmission
0 : transmission
1 : reception
P2 : Type of error
0 : overrun
1 : underrun
2 : no error
3 : timeout in emission
4 : timeout in receipt
5 : timeout overrun
P3 : Number of CRYSTAL link
P4 : Added error number on the link
P5 : DMA counter
P6 : Control word of the DMA
Transmission incident l01
Congestion of messages on a coupler, coupler reinitialization, overrun or
underrun in transmission on the IO-processor.
Can cause a deterioration of the performances if the fault continues.
If the fault continues, the operator must verify the status of the coupler
which has a dialog problem with the CPU


incvisu -1 readout

25/03/18 13:42:05 000001M|--/--/-/---|=1:2073=Shutdown command has been called
25/03/18 13:42:07 000001M|--/--/-/---|=0:2663=IPC Chorus err: appli MAO_AGENT oper 30 err

Re: NDDI registered not initialised

Posted: 25 Mar 2018 07:20
by mdhussainvlr
bcmir wrote:Hi all,
I have a problem with an ACT (2 crystal shelves) 4400:
System has an NDDI board which is REGISTERED NOT INITIALISED. I also have an INTOF board which is failing (appears to be hardware error, since when I swap INOFA & INTOFB the INTOFB board works ok in first crystal shelf)
I have tried:
Swapping out NDDI board
Rstcpl NDDI
Rebooting CPU numerous times
Deleting NDDI and re-creating all terminals.

config 0

+-------------------------------------------------------------------------+
| Cr | cpl | cpl type | coupler state | coupler ID |
|----|-----|--------------|--------------------------|--------------------|
| 0 | 0 | MMSFD | ONLY IN MAO FILE| BAD PCMS CODE |
| 0 | 1 | CPU6 | IN SERVICE| BAD PCMS CODE |
| 0 | 3 | UA32 | IN SERVICE| 3BA53050ABBC01 |
| 0 | 4 | INTOF_A |REGISTERED NOT INITIALIZED| 3BA53118AACB02 |
| 0 | 5 | PRA2 | IN SERVICE| 3BA23076AAAC03 |
| 0 | 6 | Z24_2 | IN SERVICE| 3BA53065NACF02 |
| 0 | 8 | NDDI |REGISTERED NOT INITIALIZED| BAD PCMS CODE |
| 0 | 9 | VG | IN SERVICE| 3BA53077ABAC02 |
+-------------------------------------------------------------------------+

--- Inter Crystal Topology ---

+-------------------------------------------------------------------------+
| CR | CPL Type Role Free/Tot Role Type CPL | CR |
|-------------------------------------------------------------------------|
| 00 | 04 -INTOF_A (INT_HS ) -X- 00/00 -X- ( INT_HS) INTOF_B - 01 | 01 |
|-------------------------------------------------------------------------|

Should I try upgrading to a later patch of firmware (current is R4.1-d1.311.7-i-as-c6s2) as there seems to be a glitch between CPU6 and NDDI board (Error 3001 see below)
Does anyone have a download of R4.1 available ?

Or is a new CPU board required ? .. please HELP!!

I have the follow incvisu readout (shows error 3001 with explaination below)

(1)xa000001> incvisu
25/03/18 13:45:44
25/03/18 13:45:54 000001I|--/--/-/---|=2:4351=Incoherent data: appli INITREM table No 292 cause 0 info 2000 -1 -1
25/03/18 13:46:01 000001I|--/--/-/---|=2:2199=A4400 Version : R4.1-d1.311-7-i-as-c6s2
25/03/18 13:46:07 000001I|--/--/-/---|=5:1528=Test from chorus if incidents handler is running
25/03/18 13:47:00 000001I|--/--/-/---|=2:2176=A dynamic patch has been installed for TEL
25/03/18 13:47:01 000001I|--/--/-/---|=2:2176=A dynamic patch has been installed for alb
25/03/18 13:47:02 000001I|--/--/-/---|=2:2176=A dynamic patch has been installed for main_afe
25/03/18 13:47:02 000001I|--/--/-/---|=2:2176=A dynamic patch has been installed for cstamono
25/03/18 13:47:03 000001I|--/--/-/---|=2:2176=A dynamic patch has been installed for internal_t
25/03/18 13:47:03 000001I|--/--/-/---|=2:2176=A dynamic patch has been installed for maoagent
25/03/18 13:47:06 000001I|--/--/-/---|=4:0260=Beginning of downloading binloaderio1n
25/03/18 13:47:06 000001I|--/--/-/---|=5:0261=End of downloading binloaderio1n
25/03/18 13:47:18 000001I|00/28/-/---|=4:0260=Beginning of downloading tonesnv
25/03/18 13:47:18 000001I|00/28/-/---|=5:0261=End of downloading tonesnv
25/03/18 13:47:18 000001M|--/--/-/---|=5:2009=Initialisation CPU role MAIN
25/03/18 13:47:19 000001M|--/--/-/---|=4:1367=DECT network initialization
25/03/18 13:47:21 000001M|--/--/-/---|=4:1436=Activation of the driver for the A4615, which will download the boot : boot4615.
25/03/18 13:47:22 000001M|--/--/-/---|=0:1625=4615 driver : data transmission problem number 5
25/03/18 13:47:22 000001M|00/28/-/---|=4:0260=Beginning of downloading bnvdsp0cpu6
25/03/18 13:47:23 000001M|00/28/-/---|=5:0261=End of downloading bnvdsp0cpu6
25/03/18 13:47:26 000001M|00/06/-/---|=4:0260=Beginning of downloading bindspz2cx
25/03/18 13:47:28 000001M|00/05/-/---|=4:3512=CPU ordered a reset
25/03/18 13:47:33 000001M|00/06/-/---|=5:0261=End of downloading bindspz2cx
25/03/18 13:47:33 000001M|00/06/-/---|=4:3512=CPU ordered a reset
25/03/18 13:47:38 000001M|00/03/-/---|=4:3512=CPU ordered a reset
25/03/18 13:47:43 000001M|00/03/0/005|=4:2151=Undeclared subdevice EAK present
25/03/18 13:48:21 000001M|00/09/-/---|=5:2019=USCVG coupler commissioning
25/03/18 13:48:30 000001M|00/06/-/---|=5:2019=Z coupler commissioning
25/03/18 13:48:40 000001M|00/03/-/---|=5:2019=UA coupler commissioning
25/03/18 13:48:59 000001M|00/05/0/000|=4:2113=T2 lapD not established still trying
25/03/18 13:49:07 000001M|00/01/-/---|=5:2169=Main CPU initialization completed
25/03/18 13:49:09 000001M|00/05/-/---|=3:2103=T2 access end of 75 time-out unusual
25/03/18 13:49:28 000001M|00/05/-/---|=5:2019=PRA coupler commissioning
25/03/18 13:51:03 000001M|00/28/-/---|=2:2457=IO1 coupler (0,28) not initalized yet
25/03/18 13:51:03 000001M|00/04/-/---|=2:2457=INT2A coupler (0,4) not initalized yet
25/03/18 13:51:03 000001M|00/08/-/---|=2:2457=NDDI coupler (0,8) not initalized yet
25/03/18 13:55:09 000001M|--/--/-/---|=2:2166=CPU requires Reset CPL NDDI (0,8) Cause 0
25/03/18 13:55:09 000001M|00/28/-/---|=3:3001=IO transm. fault 0 3 8 4 0 0
25/03/18 13:55:10 000001M|00/28/-/---|=3:3001=IO transm. fault 0 3 8 8 0 0
25/03/18 13:55:10 000001M|00/28/-/---|=3:3001=IO transm. fault 0 3 8 12 0 0

Incinfo message:

IO transm. fault P1 P2 P3 P4 P5 P6

P1 : Sense of the transmission
0 : transmission
1 : reception
P2 : Type of error
0 : overrun
1 : underrun
2 : no error
3 : timeout in emission
4 : timeout in receipt
5 : timeout overrun
P3 : Number of CRYSTAL link
P4 : Added error number on the link
P5 : DMA counter
P6 : Control word of the DMA
Transmission incident l01
Congestion of messages on a coupler, coupler reinitialization, overrun or
underrun in transmission on the IO-processor.
Can cause a deterioration of the performances if the fault continues.
If the fault continues, the operator must verify the status of the coupler
which has a dialog problem with the CPU


incvisu -1 readout

25/03/18 13:42:05 000001M|--/--/-/---|=1:2073=Shutdown command has been called
25/03/18 13:42:07 000001M|--/--/-/---|=0:2663=IPC Chorus err: appli MAO_AGENT oper 30 err



Sent from my iPhone using Tapatalk

Re: NDDI registered not initialised

Posted: 25 Mar 2018 07:21
by mdhussainvlr
This was happened how?
Ai it was working earlier ?
and I can see from incidents that PRA card not came into service or only NDDI having issue ?


Sent from my iPhone using Tapatalk

Re: NDDI registered not initialised

Posted: 25 Mar 2018 17:16
by bcmir
This was working earlier and suddenly stopped working.
The PRA card is not an issue.. it is not being used.

I had performed a system reset to try and resolve the NDDI issue, which is why you can see the PRA card come back online.