RV320 router keeps restarting (probably crashing)

[dzentai]

Since we have installed the router with very simple configuration a few weeks ago, the router keeps rebooting at random interval, usually twice or more a day. We tried hard reseting it, and I also found a new firmware to which I upgraded the router a few days ago (from 1.1.0.09 to 1.1.1.06), but it still does the same thing.

I have logging turned on, but the only relevant messages I see in the logs are those when it already restarts (rv320 : System is up). So I don't know how or why it crashes.

The only features we use are Site-to-site IPSEC VPN termination and DHCP server. It is in gateway mode, so firewall and NAT is active. But I turned off or unconfigured basically everything else.

What could I do to have this solved?

Is there any way to extract more information, probably some kind of trace or crashdump, or debug logs from the router?

[dzentai]

Opened case through chat.

SUPPORT CASE:628673667

SUPPORT CASE TITLE:Chat: RV320: Device crashes continuously

SEVERITY:3

STATUS: OPEN

We have discussed with the support engineer that there is not too much we can do about it, since besides the System Logs there are no other ways to trace down this issue. So went for the 30 days hardware replacement to my distributor.

I hope it is really a hardware issue, and not a software bug.

I'll come back with the results.

[Marc Nagao]

I trust a resolution will come quickly.

Good luck.

Marc

[luca.vasini]

Marc i have same (?) problem... check this if is possible: https://supportforums.cisco.com/discussion/12226606/cisco-rv320-timeout-problem

Thanks!!

[Marc Nagao]

Luca - please get a case started with our support team.

Thanks!

Marc

[luca.vasini]

Hello,

thanks for the reply, can you give me a link?

thanks Marc!

[luca.vasini · Accepted solution]

In order to use this tool you must associate your service contracts with your Cisco.com account.
You can add service contracts to your profile using the Cisco Profile Manager or have your service access management administrator do this for you.
For urgent issues or products covered under warranty, please contact the Cisco Technical Assistance Center by phone.

I'm an end user.

:(

[dzentai]

Hi Marc,

Replacing the router didn't solve the problem.

[dzentai]

We have just replaced the router with the same type.

Uploaded same firmware, same config.

The router still keeps on rebooting!

In the system log there is nothing about why it is rebooting, I only see "System is up" message.

However I've just noticed that in the Incoming Log Table I have these messages, which I don't really understand:

2013-07-24, 13:47:48	Kernel	kernel: i2c i2c-0: Failed to register i2c client rs5c372b at 0x32 (-16)
2013-07-24, 13:47:48	Kernel	kernel: i2c i2c-0: Can't create device at 0x32
2013-07-24, 13:47:48	Kernel	kernel: gre: can't add protocol
2013-07-24, 13:55:31	Kernel	kernel: i2c i2c-0: Failed to register i2c client rs5c372b at 0x32 (-16)
2013-07-24, 13:55:31	Kernel	kernel: i2c i2c-0: Can't create device at 0x32
2013-07-24, 13:55:31	Kernel	kernel: gre: can't add protocol
2013-07-24, 14:07:21	Kernel	kernel: i2c i2c-0: Failed to register i2c client rs5c372b at 0x32 (-16)
2013-07-24, 14:07:21	Kernel	kernel: i2c i2c-0: Can't create device at 0x32
2013-07-24, 14:07:21	Kernel	kernel: gre: can't add protocol
2013-07-24, 14:15:10	Kernel	kernel: i2c i2c-0: Failed to register i2c client rs5c372b at 0x32 (-16)
2013-07-24, 14:15:10	Kernel	kernel: i2c i2c-0: Can't create device at 0x32
2013-07-24, 14:15:10	Kernel	kernel: gre: can't add protocol
2013-07-25, 00:23:50	Kernel	kernel: i2c i2c-0: Failed to register i2c client rs5c372b at 0x32 (-16)
2013-07-25, 00:23:50	Kernel	kernel: i2c i2c-0: Can't create device at 0x32
2013-07-25, 00:23:50	Kernel	kernel: gre: can't add protocol
2014-01-20, 11:33:16	Kernel	kernel: i2c i2c-0: Failed to register i2c client rs5c372b at 0x32 (-16)
2014-01-20, 11:33:16	Kernel	kernel: i2c i2c-0: Can't create device at 0x32
2014-01-20, 11:33:16	Kernel	kernel: gre: can't add protocol

The internet connection is a 120Mbps/25Mbps leased line. I know that some users have torrent running, even though it is forbidden.

Is it possible that this "high performance" router still has the good old problem of open connections count limit, so because of a lot of half open and established connections caused by torrent make the router deplete its resources and thus reboots?

Rebooting happens more often during working hours, this might indicate that it could be related to resource usage.

What is the theoretical connection count this router should be able to handle?

Do any of you have similar problems?

[dzentai]

I've set up a syslog server, and turned on all possible log categories. Let's see what we get out of it.

[Marc Nagao]

dzentai - what's the latest from the support team?

Marc

[dzentai]

Hi Marc,

I was told to setup a syslog server and keep collecting logs of 2-3 restarts.

[Marc Nagao]

Ok - the support team is actively working with you.

Good to hear and i trust they will find a resolution.

Marc

[David Pilcher]

We get those same log files at boot on our unit:

kernel: i2c i2c-0: Failed to register i2c client rs5c372b at 0x32 (-16)

I believe they are to do with failed communication with a RTC (Real Time Clock) chip... probably not an issue and unrelated to your reboots since the time is correct as it syncs with a time server.

I thought it odd that production firmware would have errors in the boot log though...

[dzentai]

Hi David,

Thanks for the info!