Logging stops after dsl connection drops (RVS4000)

[83733h7363]

Hi, first time here to me.

Recently i bought a Cisco RVS4000, upgraded the firmware to latest stable release (Firmware Version: V2.0.2.7) and started configuring it.

Yesterday i found out that as the dsl connection drops (i'm using PPPoE with an ethernet ADSL Modem) the product stops logging, both locally and to an external configured syslog (which resides on a linux box over the LAN).

Could this be a software bug and how am i supposed to fix it?

Is this the correct place to ask this question?

Thanks.

[jasbryan]

Simone,

This is the correct place to be posting for your RVS4000. Now since you are using a DSL connection make sure you manually set your MTU size to 1492. 

Thanks,

Jasbryan

Cisco Support Engineer

.:|:.:|:.

[83733h7363]

Hi jasbryan, is this related to my question about logs? I'm asking because i've just set the MTU value to 1492 as you suggested, but as soon as the router rebooted, logs are gone again (nothing reaches my syslog).

The only solution to fix this problem seems to be disabling/reenabling logs from the panel.

Thanks,

Simone.

just to be precise i'm going to paste the last lines riceived by syslog soon after the reboot:

Jan  1 01:00:20 192.168.XX.. local  IP address XXX...

Jan  1 01:00:20 192.168.XX.. remote IP address XXX...

Jan  1 01:00:20 192.168.XX.. primary   DNS address XXX..

Jan  1 01:00:20 192.168.XX.. secondary DNS address XXX..

The time settings aren't yet applied at this stage, as you can see.

Messaggio modificato da Simone Canaletti [08/08/2011 - 18:03]

[83733h7363]

Moreover, i spent about 3 hours to figure out that windows update (on a seven machine) microsoft.com and other MS domains were unreachable after having set the MTU = 1492.

Falling back to auto (1500) problems are gone.

See You.