reason of reboot GD2

Post Reply
ritchi67

reason of reboot GD2

Post by ritchi67 »

Hi all,

I would like to know the cause of the reboot "5857 = GD / GA / INTIP / RGD: reason of reboot 3"

thank you for your reply
User avatar
enio.eltz
Senior Member
Posts: 1058
Joined: 28 Jul 2009 09:48
Location: Taquara - RS - Brazil

Re: reason of reboot GD2

Post by enio.eltz »

Hi

"Soft reset on loss of DL IP". It probably has lost CS communication.
Enio Eltz Filho
ACFE OXE R12
ACFE OXO C R3
ritchi67

Re: reason of reboot GD2

Post by ritchi67 »

Hi,
is that the keep-alive has been exceeded or that the GD has lost network
User avatar
enio.eltz
Senior Member
Posts: 1058
Joined: 28 Jul 2009 09:48
Location: Taquara - RS - Brazil

Re: reason of reboot GD2

Post by enio.eltz »

Hi

It can be both.
Enio Eltz Filho
ACFE OXE R12
ACFE OXO C R3
ritchi67

Re: reason of reboot GD2

Post by ritchi67 »

HI

thanks for your answer.
Klink
Member
Posts: 36
Joined: 19 Mar 2011 12:17

Re: reason of reboot GD2

Post by Klink »

Just increase the UDP lost and it should be fine.
User avatar
stefanc
Member
Posts: 129
Joined: 19 Jan 2010 17:09
Location: Sweden
Contact:

Re: reason of reboot GD2

Post by stefanc »

Where can I do that, in the GD or ...
User avatar
stefanc
Member
Posts: 129
Joined: 19 Jan 2010 17:09
Location: Sweden
Contact:

Re: reason of reboot GD2

Post by stefanc »

Found it , i´m so tired, (IP-QOS)

:-)
FN_DK
Member
Posts: 126
Joined: 13 Aug 2009 08:00

Re: reason of reboot GD2

Post by FN_DK »

Did it help to increase the UDP lost timer??

Regards
Klink
Member
Posts: 36
Joined: 19 Mar 2011 12:17

Re: reason of reboot GD2

Post by Klink »

I hope it did. :-)

INCIDENT NUMBER: 5857
Network indicator: Alcatel 4400
OBJECT CLASS: Dhs3Board
EVENT TYPE: ProcessingErrorAlarm (10)
PROBABLE CAUSE: Unknown (0)
SEVERITY: Indeterminate

"GD/GA/INTIP/RGD: reason of reboot P1"
"P1 Error state"
"P1 :"
"GD/GA code :"
"- 3 : Soft reset on loss of DL IP"

DL IP means the tftp server add(usually OXE add - use command "lanpbxbuild -auto") from which the GD/INTIP etc will download it's binaries.

The incident is generated because the keep alive timer + the UDP lost timer have both been exceeded. Thus if U increase the value of the UDP lost timer, OXE will behave as if a network downtime which does not last long is transparent to it. Please note that you should never modify the keep alive or re-init timer. Only the UDP lost timer can be modified.

If the problem persists after modifying this value maybe you could post the topology of the installation here, + GD logs, + infocollect containing time of reboot.
Post Reply

Return to “Media Gateway”