DrayTek UK Users' Community Forum

Help, Advice and Solutions from DrayTek Users

2950 rebooting regularly

  • wibleh
  • Topic Author
  • Offline
  • New Member
  • New Member
More
12 Jul 2011 10:37 #68558 by wibleh
2950 rebooting regularly was created by wibleh
Hi all, we have a 2950 (latest firmware 3.3.0) which appears to be rebooting regularly. Other than restoring the firmware to factory settings and setting it up again, does anyone have any hints/tips/pearls of wisdom why this may be happening?

Sorry for the long post but to show the freqnency:

Line 596576: 2011-07-10 15:57:44 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 598020: 2011-07-10 16:32:33 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 598077: 2011-07-10 16:33:20 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 598137: 2011-07-10 16:34:04 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 598222: 2011-07-10 16:34:51 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 599656: 2011-07-10 17:09:44 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 617977: 2011-07-11 01:39:10 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 618014: 2011-07-11 01:39:56 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 618061: 2011-07-11 01:40:43 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 618116: 2011-07-11 01:41:25 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 618175: 2011-07-11 01:42:13 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 629504: 2011-07-11 06:58:27 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 629559: 2011-07-11 06:59:09 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 629613: 2011-07-11 06:59:48 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 629670: 2011-07-11 07:00:35 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 633920: 2011-07-11 08:59:52 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 633975: 2011-07-11 09:00:34 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 634250: 2011-07-11 09:08:20 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 638021: 2011-07-11 11:32:41 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 638190: 2011-07-11 11:37:24 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 638247: 2011-07-11 11:38:11 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 638754: 2011-07-11 11:53:52 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 647894: 2011-07-11 17:55:31 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 649963: 2011-07-11 18:58:10 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!
Line 687003: 2011-07-12 10:07:33 Local1.Notice 192.168.2.1 Jan 1 00:00:03 Vigor: System has reboot!

Please Log in or Create an account to join the conversation.

More
12 Jul 2011 13:37 #68566 by admin
Replied by admin on topic Re: 2950 rebooting regularly
Seems unusual. Not sure if the V2950 supports it, but check "sys ver dbg" from telnet and raise a support ticket with the output.



Forum Administrator

Please Log in or Create an account to join the conversation.

  • wibleh
  • Topic Author
  • Offline
  • New Member
  • New Member
More
12 Jul 2011 13:58 #68567 by wibleh
Replied by wibleh on topic Re: 2950 rebooting regularly
Thanks for the reply, the command worked and I'll raise a ticket :)

P.S. Great work with the Draytek equipment, 1st problem I've had out of 2 modems, 1 load balancer, 4 routers!

Please Log in or Create an account to join the conversation.

More
12 Jul 2011 14:49 #68570 by voodle
Replied by voodle on topic Re: 2950 rebooting regularly
Try unplugging the WAN connections from it, rebooting like that can be caused by VPN connections potentially and taking down the WAN connections will stop that going up so you can check the config for anything that might have put it into that state - that's only useful when it's doing it frequently though, sys ver dbg will be more useful normally.

Please Log in or Create an account to join the conversation.

Moderators: ChrisSami