Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

RVS4000 stops logging after DSL connection drops

Hi there,

each time my dsl connection drops i lose logging functionality from the router: i have enabled a syslog server on my subnet and i have local logs enabled too. The only thing i'm able to do is stop logging and start it over; this is the only way to make it work again.

There's no need to say that connection may drop any time, day and night, and i can't be always here to look at it.

I simulated a connection drop right now by shutting off the modem and my logs show the following:

Jan 23 11:16:06 192.168.77.254 Configuration changed!

Jan 23 11:25:07 192.168.77.254 Serial link appears to be disconnected.

Jan 23 11:25:07 192.168.77.254 IPSEC EVENT: KLIPS device ipsec0 shut down.

Jan 23 11:25:13 192.168.77.254 Connection terminated.

Jan 23 11:25:13 192.168.77.254 Connect time 23174544.7 minutes.

Jan 23 11:25:13 192.168.77.254 Sent 16407141 bytes, received 1654960 bytes.

Jan 23 11:25:13 192.168.77.254 Doing disconnect

Jan 23 11:25:13 192.168.77.254 Exit.

Jan 23 11:25:26 192.168.77.254 Plugin pppoe loaded.

Jan 23 11:25:26 192.168.77.254 PPPoE Plugin Initialized

Jan 23 11:25:26 192.168.77.254 Plugin pppoe called.

Jan 23 11:25:26 192.168.77.254 pppd 2.4.1 started by root, uid 0

Jan 23 11:25:26 192.168.77.254 Sending PADT

Jan 23 11:25:29 192.168.77.254 Sending PADI

Jan 23 11:25:37 192.168.77.254 HOST_UNIQ mismatch: RECV:30303031 SENT:000006bb

Jan 23 11:25:37 192.168.77.254 Failed to negotiate PPPoE connection: 2

Jan 23 11:25:37 192.168.77.254 Exit.

Jan 23 11:25:56 192.168.77.254 Plugin pppoe loaded.

Jan 23 11:25:56 192.168.77.254 PPPoE Plugin Initialized

Jan 23 11:25:56 192.168.77.254 Plugin pppoe called.

Jan 23 11:25:56 192.168.77.254 pppd 2.4.1 started by root, uid 0

Jan 23 11:25:56 192.168.77.254 Sending PADT

Jan 23 11:25:59 192.168.77.254 Sending PADI

Jan 23 11:25:59 192.168.77.254 HOST_UNIQ successful match

Jan 23 11:25:59 192.168.77.254 HOST_UNIQ successful match

Jan 23 11:25:59 192.168.77.254 Got connection: 44f

Jan 23 11:25:59 192.168.77.254 Connecting PPPoE socket: 00:90:1a:a4:xx:xx 4f04 eth1 0x42640

Jan 23 11:25:59 192.168.77.254 Configuration changed!

Jan 23 11:26:01 192.168.77.254 using channel 2

Jan 23 11:26:01 192.168.77.254 ppp0 Using interface ppp0

Jan 23 11:26:01 192.168.77.254 ppp0 Connect: ppp0 <--> eth1

Jan 23 11:26:01 192.168.77.254 PAP authentication success

Jan 23 11:26:01 192.168.77.254 local  IP address 79.46.xxx.xxx

Jan 23 11:26:01 192.168.77.254 remote IP address 192.168.100.1

Jan 23 11:26:01 192.168.77.254 primary   DNS address 85.37.17.57

Jan 23 11:26:01 192.168.77.254 secondary DNS address 85.38.28.80

Here it ends until i manually stop/restart logging functionality.

Thanks

Everyone's tags (2)
2 REPLIES
Gold

RVS4000 stops logging after DSL connection drops

Simone,

We saw a lot of issues related to logging with the 'legacy' Small Business routers. We checked with the development team at the time and were told that logging should only be enabled when troubleshooting a specific issue, and only for a short time. Basically the routers do a lot of things well and logging isn't one of them. In some cases (WRV200, WRV210) enabling constant logging caused stability issues (internet drops, wireless stopped working until reboot).

I have not heard of as many issues related to logging with the newer routers, although I can assure you that it is still not perfect.

- Marty

New Member

RVS4000 stops logging after DSL connection drops

Thanks Marty,

i didn't know it was a widespread issue, however logging (here) does not seems to create problems on the normal behaviour of the router. I can't really say if logging and connection dropping would be related one to another, i'll just follow your advice and turn off logging for some time, see how it goes.

Best Regards,

Simone

284
Views
0
Helpful
2
Replies
CreatePlease to create content