MD110 (NIU) connected to OneBox

[jeroenwijnen]

I have a OneBox connected to a MD110. The onebox is connected by using a NIU board.
A few times a day I get this alarm in the PBX:
345 INFORMATION COMPUTER, FAULTY COMMUNICATION CHANNEL
DATE TIME ALP NOIF EQU BRDID
19MAR04 10:01:15 1 1 001-0-52-01 106
RDATE RTIME
19MAR04 10:01:15
END

The solution from Ericsson is as follows:
Communibetween the MD110 and OneBox cation over TCP/IP is lost and does not automatically recover Case published
Wed Jul 09 07:19 2003


It is possible to lose the (TCP/IP) connection between OneBox and the MD110 from time to time for various reasons. For example, the OneBox server is rebooted, the NIU in the MD110 is restarted, there is a problem with the company LAN, and so on. From time to time, the connection does not automatically recover when the cause of the outage is corrected.

Solution

Restart the NIU

Since OneBox has the role of the server and the MD110 is the client, the MD110 is responsible for initiating the connection towards OneBox. When the connection is lost for a period of time, the NIU may experience difficulty re-establishing the connection. In most cases, restarting the NIU will correct the problem and cause the connection to be re-established.

In a small percentage of the cases, simply restarting the NIU does not help. If this is the case, restarting the program unit ILNP in the MD110 will usually clear the problem (refer to the MD110 O&M documentation for instructions on how to restart a program unit). If neither restarting the NIU nor restarting ILNP work, then try rebooting the OneBox server.


I would like to know if there is an other solution for this problem.

Thanx!

 

[SYAR2003]

Not even restart of ILNP ,or RFEXI helps .

Update Onebox to 2.1 and a hotfix solves the problem .
TCP port number hangs in the onebox server .

../Syar