reason of reboot GD2
-
ritchi67
reason of reboot GD2
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
I would like to know the cause of the reboot "5857 = GD / GA / INTIP / RGD: reason of reboot 3"
thank you for your reply
Re: reason of reboot GD2
Hi
"Soft reset on loss of DL IP". It probably has lost CS communication.
"Soft reset on loss of DL IP". It probably has lost CS communication.
Enio Eltz Filho
ACFE OXE R12
ACFE OXO C R3
ACFE OXE R12
ACFE OXO C R3
-
ritchi67
Re: reason of reboot GD2
Hi,
is that the keep-alive has been exceeded or that the GD has lost network
is that the keep-alive has been exceeded or that the GD has lost network
Re: reason of reboot GD2
Just increase the UDP lost and it should be fine.
Re: reason of reboot GD2
Where can I do that, in the GD or ...
Re: reason of reboot GD2
Found it , i´m so tired, (IP-QOS)

Re: reason of reboot GD2
Did it help to increase the UDP lost timer??
Regards
Regards
Re: reason of reboot GD2
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.
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.
