ONEBOX V2 / MD110 intergration

[dbc4xxx]

Can anyone explain why the OneBox V2 intergration on BC12 on one of our customer sites suddenly requires the NIU to be restarted constantly.The integration works for approx 1 hr then its lost. Restarting the NIU brings it back up. When the intergration is lost, using CXSIMDIG.exe I can see the OneBox sending poll requests to the MD110 but the MD doesn't send the acknowledgement back.
NIU has been changed and also the Network card on the OneBox server has been changed to.

IONPP;
NETWORK PORT CONFIGURATION DATA
EQU IP GATE MASK ETHERNET
001-0-70-4 194.81.29.14 194.81.29.1 255.255.255.0 00.80.37.8E.57.90

IONCP;
NETWORKING CONNECTION
NODE/IODEV LIM USER TYPE/CON IP PORT PROC
SYSN 1
ONEBOX GICI-1 CLIENT 192.168.9.28 2555 TCP
END

<ICFUP;
INFORMATION COMPUTER COMMON FUNCTIONS DATA
UPDATING START TIME IS 01:30
MESSAGE WAITING FUNCTIONALITY IS ALL
INFORMATION COMPUTER EQUIPMENT DATA
IFCIND IODEV EQU RATE DFMT UPDFCN PARITY CCHECK
1 ONEBOX 4 YES
FILLER=48 ICEXG=NONE USER=GICI-01

 

[fouesnant]

Hi

Which NIU version do you have?

 

[dbc4xxx]

BPOS BOARD/BRDID PRODUCT NUMBER REVISION STATUS ADD

001-0-70 NIU ROF1375396/1 R3A
CAA 1580001 R19A EXE
CAA 1580001 R12A OLD

 

[doktor]

Please post the ALLOP; and the HIMDP;
Always use same grounding for MD110 and PC's running application for the MD110.

///doktor

 

[dbc4xxx]

HI, IP ADDRESS SHOULD
IONCP;
NETWORKING CONNECTION
NODE/IODEV LIM USER TYPE/CON IP PORT PROC
SYSN 1
ONEBOX GICI-1 CLIENT 192.168.9.28 2555 TCP

NETWORK PORT CONFIGURATION DATA
EQU IP GATE MASK ETHERNET
001-0-70-4 192.168.9.26 192.168.9.1 255.255.255.0

HIMDP;
TIME DATE ERROR CODE
21:58:28 16MAY06 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 02003440
BRANCHVALUE = 00000033
ENTER
SWSW A-LEVEL SIGNAL CTMOUTA (H'00EB)
FROM EXS (H'003) EXE A IN LIM 001
TO NIP (H'056) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 5
WITH 0 1 2 3 4 5 6 7 8 9
000 00 07 32 00 0A

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 00 27 26 02 00 27 12

TIME DATE ERROR CODE
21:55:48 16MAY06 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 02003440
BRANCHVALUE = 00000032
ENTER
SWSW A-LEVEL SIGNAL CTMOUTA (H'00EB)
FROM EXS (H'003) EXE A IN LIM 001
TO NIP (H'056) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 5
WITH 0 1 2 3 4 5 6 7 8 9
000 00 07 31 00 0A

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 00 27 26 02 00 27 12

TIME DATE ERROR CODE
21:53:07 16MAY06 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 02003440
BRANCHVALUE = 00000031
ENTER
SWSW A-LEVEL SIGNAL CTMOUTA (H'00EB)
FROM EXS (H'003) EXE A IN LIM 001
TO NIP (H'056) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 5
WITH 0 1 2 3 4 5 6 7 8 9
000 00 07 30 00 0A

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 00 27 26 02 00 27 12

TIME DATE ERROR CODE
21:50:27 16MAY06 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 02003440
BRANCHVALUE = 00000030
ENTER
SWSW A-LEVEL SIGNAL CTMOUTA (H'00EB)
FROM EXS (H'003) EXE A IN LIM 001
TO NIP (H'056) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 5
WITH 0 1 2 3 4 5 6 7 8 9
000 00 07 2F 00 0A

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 00 27 26 02 00 27 12


TIME DATE ERROR CODE
11:06:40 14JAN05 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 020075BE
ENTER
SWSW A-LEVEL SIGNAL FETMULPOSRES (H'0042)
FROM KLP1T2 (H'1CE) EXE A IN LIM 001
TO SCP (H'32F) EXE A IN LIM 002
NUMBER OF DATA BYTES IN SIGNAL = 5
WITH 0 1 2 3 4 5 6 7 8 9
000 00 05 09 00 C1

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 00 56 78

TIME DATE ERROR CODE
14:16:38 17NOV04 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 02007B4C
BRANCHVALUE = 00000000
ENTER
SWSW A-LEVEL SIGNAL CLEAR (H'0066)
FROM CMPS1 (H'2D2) EXE A IN LIM 002
TO CMPS16 (H'2E1) EXE A IN LIM 002
NUMBER OF DATA BYTES IN SIGNAL = 7
WITH 0 1 2 3 4 5 6 7 8 9
000 5F B8 00 19 02 01 01
STACK ADDRESS = 00000000
SIGNAL SEND ADDRESS = 0200246C

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 00 35 EC

TIME DATE ERROR CODE
10:33:49 16SEP04 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 020002F6
ENTER
SWSW A-LEVEL SIGNAL FETINDINFRES (H'0022)
FROM DER (H'17D) EXE A IN LIM 001
TO CLPS1 (H'20E) EXE A IN LIM 002
NUMBER OF DATA BYTES IN SIGNAL = 45
WITH 0 1 2 3 4 5 6 7 8 9
000 01 B3 97 00 04 05 02 05 0F 0F
010 0F 0F 0F 0F 0F 00 FF 00 01 FF
020 00 54 52 FF FF FF FF FF FF FF
030 FF FF FF FF FF FF FF FF FF FF
040 FF FF 00 00 00


TIME DATE ERROR CODE
13:00:34 27JAN04 H'41
INTER LIM SIGNAL LOST - MISMATCHING SEQUENCE NUMBER
BRANCHVALUE = 0000EBD8
ENTER
SWSW B-LEVEL SIGNAL *************** (H'0000)
FROM ****** (H'000) EXE A IN LIM 003
TO ****** (H'000) EXE A IN LIM 002
NO DATA IN SIGNAL


TIME DATE ERROR CODE
13:46:51 26JAN04 H'41
INTER LIM SIGNAL LOST - MISMATCHING SEQUENCE NUMBER
BRANCHVALUE = 0000ACB6
ENTER
SWSW B-LEVEL SIGNAL *************** (H'0000)
FROM ****** (H'000) EXE A IN LIM 003
TO ****** (H'000) EXE A IN LIM 002
NO DATA IN SIGNAL

IME DATE ERROR CODE
09:12:51 20OCT05 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 020002F6
ENTER
SWSW A-LEVEL SIGNAL FETINDINFRES (H'0022)
FROM DTN (H'358) EXE A IN LIM 001
TO CLPS1 (H'20E) EXE A IN LIM 003
NUMBER OF DATA BYTES IN SIGNAL = 45
WITH 0 1 2 3 4 5 6 7 8 9
000 01 A4 57 01 00 00 01 00 00 01
010 00 01 04 0F 02 FF FF 03 01 FF
020 00 10 14 24 63 72 F2 FF FF FF
030 FF 00 FF FF FF FF FF FF FF FF
040 FF FF 00 00 00

 

[doktor]

From this I can see:
Your Default gateway = 192.168.9.1
The Onebox Client = 192.168.9.28
The NIU board = 192.168.9.26
The sub net mask = 255.255.255.0
The only thing that differs from our standards is the
port number. We use port numbers over 4000, so please use
4550.
I can see that the operating system EXS and the NIU s/w
had a fault "CTMOUTA" at 21:58:28 16MAY06 and twice just before.
Try to make an ALREI; and HIREI; and post both ALLOP; and HIMDP; just after the fault óccurs next time.
/// doktor

 

[dbc4xxx]

Hi, two things that i have done
1- installed a temp NIU in another mag to run this connection as DNA is also riunning from the initial NIU.
2-changed the rport just in case to 4550.

This problem has only started within the last week.

below is the alarms and HIMDP;





<ALLIP;
DATE: 19MAY06 TIME: 00:40:12
CODE CLASS NOAF EXPLANATION
345 2 1 INFORMATION COMPUTER, FAULTY COMMUNICATION CHANNEL

END
<ALLOP;

VERSION: LZY2035152/2/CNA142GB-3.26/R1A

DATE: 19MAY06 TIME: 00:40:20
CLASS: 2
345 INFORMATION COMPUTER, FAULTY COMMUNICATION CHANNEL
DATE TIME ALP NOIF EQU BRDID
18MAY06 22:00:38 1 7 001-2-30-04 106


END
<IONPP;
NETWORK PORT CONFIGURATION DATA
EQU IP GATE MASK ETHERNET
001-0-70-4 192.168.9.26 192.168.9.1 255.255.255.0
001-2-30-4 192.168.9.31 192.168.9.1 255.255.255.0
END

<IONCP;
NETWORKING CONNECTION
NODE/IODEV LIM USER TYPE/CON IP PORT PROC
TEST1 1
ETHTEST GICI-1 CLIENT 192.168.9.28 4550 TCP
END

<ICFUP;
INFORMATION COMPUTER COMMON FUNCTIONS DATA
UPDATING START TIME IS 01:30
MESSAGE WAITING FUNCTIONALITY IS ALL
INFORMATION COMPUTER EQUIPMENT DATA
IFCIND IODEV EQU RATE DFMT UPDFCN PARITY CCHECK
1 ETHTEST 4 YES
FILLER=48 ICEXG=NONE USER=GICI-01
END

<IODDP;
I/O DEVICE DATA
NODE IODEV/SUBFS BPOS/EQU SIPOS TYPE/USAGE STATUS AUTH
SYSN - 001-0-70 - - IN SERVICE
SYSN SAFETY 001-0-70-0 0 ADTX SAFETY
SAFETY-SF
SYSN SYSDISK1 001-0-70-0 3 ADTX IN SERVICE
SYSSUBFS11
SYSSUBFS21
TMFS
SYSN SYSTERMINAL 001-0-70-1 - MML - 7
SYSN MODEM 001-0-70-2 - MML - 7
SYSN TOSH1 001-0-70-3 - MML - 7
SYSN TELNET1 001-0-70-4 - NETWORK/MML - 7
TEST1 - 001-2-30 - - IN SERVICE
TEST1 ETHTEST 001-2-30-4 - NETWORK/OUT IN SERVICE
LIM2 - 002-0-70 - - IN SERVICE
LIM2 TERM4 002-0-70-1 - MML - 7
LIM2 TERM5 002-0-70-2 - MML - 7
LIM2 TERM9 002-0-70-3 - MML - 7
LIM3 - 003-3-20 - - IN SERVICE
LIM3 TERM6 003-3-20-1 - MML - 7
LIM3 TERM7 003-3-20-2 - MML - 7
LIM3 TERM8 003-3-20-3 - MML - 7
END


<HIMDP;

DIAGNOSTICS FROM OPERATING SYSTEM
TIME DATE
00:44:22 19MAY06
DIAGNOSTICS FROM LIM 001

TIME DATE ERROR CODE
22:00:48 18MAY06 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 020031F8
BRANCHVALUE = 00000005
ENTER
SWSW A-LEVEL SIGNAL WRISIGA (H'00CF)
FROM ILNP (H'24C) EXE A IN LIM 001
TO FIP (H'04F) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 18
WITH 0 1 2 3 4 5 6 7 8 9
000 60 05 00 00 00 00 00 00 00 01
010 31 39 34 02 39 38 0D 0A

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 00 31 DA 02 00 1B 6E

TIME DATE ERROR CODE
22:00:38 18MAY06 H'24
RELOAD DATA CHANGE FORBIDDEN
LOGICAL PROGRAM ERROR ADDRESS = 0200079E
ENTER
SWSW A-LEVEL SIGNAL WRISIGARES (H'002C)
FROM FIP (H'04F) EXE A IN LIM 001
TO ILNP (H'24C) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 7
WITH 0 1 2 3 4 5 6 7 8 9
000 00 01 0E 00 03 00 08
STACK ADDRESS = 020020A4
SIGNAL SEND ADDRESS = 0200318E


TIME DATE ERROR CODE
22:00:38 18MAY06 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 020031F8
BRANCHVALUE = 00000005
ENTER
SWSW A-LEVEL SIGNAL WRISIGA (H'00CF)
FROM ILNP (H'24C) EXE A IN LIM 001
TO FIP (H'04F) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 18
WITH 0 1 2 3 4 5 6 7 8 9
000 60 05 00 00 00 00 00 00 00 01
010 31 39 34 02 39 38 0D 0A

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 00 31 DA 02 00 1B 6E

TIME DATE ERROR CODE
22:00:28 18MAY06 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 020024E0
ENTER
SWSW A-LEVEL SIGNAL WRISIGACONT (H'008E)
FROM FIP (H'04F) EXE A IN LIM 001
TO NIP (H'056) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 18
WITH 0 1 2 3 4 5 6 7 8 9
000 08 45 00 00 00 00 00 00 00 01
010 31 39 34 02 39 38 0D 0A
STACK ADDRESS = 02001C00
SIGNAL SEND ADDRESS = 0200315E





TIME DATE ERROR CODE
12:54:27 18MAY06 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 020006BC
ENTER
SWSW A-LEVEL SIGNAL FETTRUIDRES (H'0020)
FROM DTRS1 (H'35A) EXE A IN LIM 001
TO CLPS1 (H'20E) EXE A IN LIM 003
NUMBER OF DATA BYTES IN SIGNAL = 13
WITH 0 1 2 3 4 5 6 7 8 9
000 01 6F 2E 00 00 01 00 00 01 00
010 01 02 0F

 

[doktor]

What has happened since last week when the problem started?
Any visit from technicians, enginrers or electricians?
What was changed in the telephony system?.

I would restart the following programs if the problem i scoomming up again:
RFPUI:UNIT=FIP&NIP,LIM=1;
RFPUI:UNIT=ILNP&ILCP,LIM=1;
RFPUI:UNIT=DCTAP&DCTPP,LIM=1;
and the two NIU boards:
RFBOI:BPOS=001-0-70;
RFBOI:BPOS=001-2-30;
Maybe a general "pointer initialization":
SFCEI;
y;

Still it is of great importance to know what happened just before the fault was seen the first time.
Also check you grounding between the PC's and the MD.
It is often a good idea to split your applicaions in to several NIU boards, so one NIU takes care of the MML and Dump, the other takes care of the DNA and voice mail etc.
///doktor

 

[doktor]

Hello again

Please post the following:
VMPOP;
VMFUP;
ISFUP;

///doktor

 

[dbc4xxx]

<VMPOP;
VOICE MAIL PORT DATA
DIR PORT IFCIND
6001 001 1
6002 002 1
6003 003 1
6004 004 1
6005 005 1
6006 006 1
6007 007 1
6008 008 1
6009 009 1
6010 010 1
6011 011 1
6012 012 1
VOICE MAIL GROUP DATA
GRP IFCIND
4400 1
END

<VMFUP;
VOICE MAIL FUNCTION DATA
IFCIND VMF POFMT
1 EXTN2 3
END

<ICFUP;
INFORMATION COMPUTER COMMON FUNCTIONS DATA
UPDATING START TIME IS 01:30
MESSAGE WAITING FUNCTIONALITY IS ALL
INFORMATION COMPUTER EQUIPMENT DATA
IFCIND IODEV EQU RATE DFMT UPDFCN PARITY CCHECK
1 ETHTEST 4 YES
FILLER=48 ICEXG=NONE USER=GICI-01
END

<ISFUP;
NOT ACCEPTED
ICS APPLICATION
NOT ASSIGNED

 

[doktor]

Is the fault still there?

From what I have seen, I cannot see that there should be anything wrong according to the posted printouts.

I can just repeat this:
What has happened since last week when the problem started?
Any visit from technicians, engineers or electricians?
What was changed in the telephony system?.

The faults in the HIMDP; could lead one to think about a missing patch...
Anyway the firmware of the NIU is the newest, so it should not be here you should fault locate.

///doktor

 

[dbc4xxx]

thanks for your feedback,

There has been no changes to the system or visits by anyone relating to this fault.

Last thing we have done is conneted the Onebox dirctly to the NIU eth port to eliminate the LAN.

The fault didn't happen until 10 hrs since we carried that out normally it happened within 1 hr.Since I rebooted the NIU last night the system seems stable again

what I did notice however about the time of the fault last night was at 10PM the frequency dump is initiated...could this be a link??

I have changed the time of the dump and will monitor oit tonight. Any findings i will post on here.

Again thanks for the feedback.

 

[doktor]

Just another small issue...
From the ICFUP; you can see that the "UPDATING START TIME IS 01:30" of the GICI of the OneBox starts at 1:30 AM.
So your DUFQI (auto dump) should maybe not begin simultaneously.
Other automated functions should not bgin at the same time as the DUFQI and updating of GICI.
To check if your updating function of GICI works, try to send the command ICUPI;
This command updates the MEW lamps and display messages concerning the OneBox system.
///doktor