Alcatel OmniPCX duplicated Packets

[lagcat]

Hi All

I am not a telephone engineer so ill put that there out now

we have 2x sites one with a master and the other with a slave/gateway
in the middle we have MPLS with latency around 16-50ms
sites are connected with 2x mpls lines on each site at 10mb each
we send duplicated packets between sites to ensure uptime and no packet loss between telephone systems

our guy who know some of the system said this:
site 2 is only a Gateway all calls are processing in site 1. That means without site 1, site 2 can‘t work and will allways reboot until site 1 overtake the Management of the Communication. site 1 is Alcatel OmniPCX with an old Rel. It‘s the Rel. 8.x. Actual Alcatel Rel. is 12


my belief has always been if the slave loses 3 pings it would reboot in hope the connection returns

the issue we are having is the slave is rebooting as we have 0 packet loss due to the duplicated packets - but my question is could the duplicated packets be the thing causing the problem if the slave system sees them? the packet duplication is a newer feature for us that we were expecting to solve the odd outage but potentially creating upto 4 restarts an hour

as only the Alcatel is effected and the site is reporting all systems are 100x better than before I want to resolve just this phone issue without degrading other services it has increased

any ideas? or suggestions would be 1000% appreciated

Cheers

Jake

[alexeik]

i think you talk about OXE (OmniPCX Enterprise) because OXO has no slave shelfs.

normally you will see such errors in incvisu when the shelf is going out of service:

Code: Select all

09/01/18 08:24:45 001001M|003/01/-/---|=3:2490=Loss of a virtual coupler UA (3,10) of the associated coupler MIX (3,1)
09/01/18 08:24:45 001001M|003/01/-/---|=3:2490=Loss of a virtual coupler Z (3,11) of the associated coupler MIX (3,1)
09/01/18 08:24:45 001001M|003/27/-/---|=3:2490=Loss of a virtual coupler GPA (3,27) of the associated coupler GD/GD3 (3,0)

if its coming back online you will see:

Code: Select all

09/01/18 08:26:31 001001M|003/00/-/---|=4:0740=Beginning of an INT/IP downloading @:00.80.9f.f3.67.30 (binmg3)
09/01/18 08:26:31 001001M|003/00/-/---|=5:0741=End of downloading of an INT/IP board @:00.80.9f.f3.67.30 (binmg3)
09/01/18 08:27:04 001001M|003/00/-/---|=4:0740=Beginning of an INT/IP downloading @:00.80.9f.f3.67.30 (binmg3)
09/01/18 08:27:04 001001M|003/00/-/---|=5:0741=End of downloading of an INT/IP board @:00.80.9f.f3.67.30 (binmg3)
09/01/18 08:27:11 001001M|003/00/-/---|=4:0740=Beginning of an INT/IP downloading @:00.80.9f.f3.67.30 (binamcvb642x
09/01/18 08:27:11 001001M|003/00/-/---|=5:0741=End of downloading of an INT/IP board @:00.80.9f.f3.67.30 (binamcvb642x
09/01/18 08:27:12 001001M|003/00/-/---|=4:0740=Beginning of an INT/IP downloading @:00.80.9f.f3.67.30 (bin642xconf.
09/01/18 08:27:12 001001M|003/00/-/---|=5:0741=End of downloading of an INT/IP board @:00.80.9f.f3.67.30 (bin642xconf.
09/01/18 08:27:16 001001M|003/00/-/---|=5:0409=The inter-ACT link over IP from (19 1) is up
09/01/18 08:27:16 001001M|003/00/-/---|=3:5874=telnet service closed
09/01/18 08:27:17 001001M|003/00/-/---|=3:5874=telnet service closed
09/01/18 08:27:17 001001M|003/00/-/---|=0:5857=GD/GA/INTIP/RGD: reason of reboot 2
09/01/18 08:27:17 001001M|003/00/-/---|=3:5874=telnet service closed

so i highlighted the message which tell you the reason

09/01/18 08:27:17 001001M|003/00/-/---|=0:5857=GD/GA/INTIP/RGD: reason of reboot 2

with incinfo you will see that my fault is:

"- 2 : Hardware reset on loss of DL IP"

because i pulled the lan plug on my lab system

so this is the first step to solve this