hi
i am facing the GD-3 continuous reboot issue whenever we connect the OXE (rel 9.1) to the customer LAN network pls advice the solution
traces are pasted below
23/02/11 14:02:50 000001M|002/00/0/254|=2:0379=Inter ACT link HS: 23,(19,1),10.0.61.198,00:80:9f:8e:8c:9a
23/02/11 14:02:50 000001M|002/--/-/---|=2:2043=Loss of the 2 CRYSTAL
23/02/11 14:02:50 000001M|002/00/-/---|=2:2042=Loss of a GD/GD3 type cpl
23/02/11 14:02:50 000001M|002/01/-/---|=2:2042=Loss of a UA type cpl
23/02/11 14:02:50 000001M|002/02/-/---|=2:2042=Loss of a Z type cpl
23/02/11 14:02:50 000001M|002/03/-/---|=2:2042=Loss of a Z type cpl
23/02/11 14:02:50 000001M|002/04/-/---|=2:2042=Loss of a Z type cpl
23/02/11 14:02:50 000001M|002/05/-/---|=2:2042=Loss of a Z type cpl
23/02/11 14:02:50 000001M|002/07/-/---|=2:2042=Loss of a PRA type cpl
23/02/11 14:02:50 000001M|---/--/-/---|=2:2140=Alarm : TRUNK resources quantity critical
23/02/11 14:02:50 000001M|003/--/-/---|=2:2043=Loss of the 3 CRYSTAL
23/02/11 14:02:50 000001M|002/27/-/---|=3:2490=Loss of a virtual coupler GPA (2,27) of the associated coupler GD/GD3 (2,0)
23/02/11 14:02:50 000001M|003/00/-/---|=3:2490=Loss of a virtual coupler GPA (3,0) of the associated coupler MEX (3,0)
23/02/11 14:02:50 000001M|003/01/-/---|=2:2042=Loss of a Z type cpl
23/02/11 14:02:50 000001M|003/02/-/---|=2:2042=Loss of a Z type cpl
23/02/11 14:02:50 000001M|003/03/-/---|=2:2042=Loss of a Z type cpl
23/02/11 14:02:50 000001M|003/04/-/---|=2:2042=Loss of a Z type cpl
23/02/11 14:02:50 000001M|003/05/-/---|=2:2042=Loss of a Z type cpl
23/02/11 14:04:19 000001M|002/00/-/---|=4:0740=Beginning of an INT/IP downloading @:00.80.9f.8e.8c.9a (binmg3)
23/02/11 14:04:19 000001M|002/00/-/---|=5:0741=End of downloading of an INT/IP board @:00.80.9f.8e.8c.9a (binmg3)
23/02/11 14:04:45 000001M|002/00/-/---|=4:0740=Beginning of an INT/IP downloading @:00.80.9f.8e.8c.9a (binmg3)
23/02/11 14:04:45 000001M|002/00/-/---|=5:0741=End of downloading of an INT/IP board @:00.80.9f.8e.8c.9a (binmg3)
23/02/11 14:04:51 000001M|002/00/-/---|=4:0740=Beginning of an INT/IP downloading @:00.80.9f.8e.8c.9a (binamcvb642x
23/02/11 14:04:51 000001M|002/00/-/---|=5:0741=End of downloading of an INT/IP board @:00.80.9f.8e.8c.9a (binamcvb642x
23/02/11 14:04:52 000001M|002/00/-/---|=4:0740=Beginning of an INT/IP downloading @:00.80.9f.8e.8c.9a (bin642xconf.
23/02/11 14:04:52 000001M|002/00/-/---|=5:0741=End of downloading of an INT/IP board @:00.80.9f.8e.8c.9a (bin642xconf.
23/02/11 14:04:57 000001M|002/00/-/---|=5:0409=The inter-ACT link over IP from (19 1) is up
23/02/11 14:04:57 000001M|002/00/-/---|=3:5874=telnet service closed
23/02/11 14:04:57 000001M|002/00/-/---|=3:5874=telnet service closed
23/02/11 14:04:57 000001M|002/00/-/---|=0:5857=GD/GA/INTIP/RGD: reason of reboot 2
GD-3 reboot issue
Re: GD-3 reboot issue
>whenever we connect the OXE (rel 9.1) to the customer LAN network
How it was connected before? Spanning tree disabled?
Not easy to say why it doesn't work anymore without a Network capture.
Reason 2 means "Hardware reset on loss of DL IP" - IP Data Link lost - no IP connection between OXE and GD.
Try to make a telnet connection from OXE to GD and check, whether it's still there when connecting the customer LAN.
How it was connected before? Spanning tree disabled?
Not easy to say why it doesn't work anymore without a Network capture.
Reason 2 means "Hardware reset on loss of DL IP" - IP Data Link lost - no IP connection between OXE and GD.
Try to make a telnet connection from OXE to GD and check, whether it's still there when connecting the customer LAN.
Re: GD-3 reboot issue
Make test - connect CS and GD in separated simple switch (f.e. SLANX4 on CS board).
Re: GD-3 reboot issue
thanx for support the problem got resolved after creating seperate VLan for OXE
-
- Member
- Posts: 44
- Joined: 03 Nov 2013 02:20
Re: GD-3 reboot issue
Hi ;
which command allows me to make traces on the GD
thanks
which command allows me to make traces on the GD
thanks
ACFE R10.0
mokhtar.belkhiati@gmail.com
mokhtar.belkhiati@gmail.com
Re: GD-3 reboot issue
telnet_al
or via serial directly in that board