This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Internet Uplink Down/Up

Seit ein paar Tagen erhalten wir auf einer SG330 auf einem WAN-Interface mehrmals täglich down/up notification:

2023:12:15-08:43:08 deviceXXX middleware[4527]: T main::top-level:213() => starting cycle 35767, caught 1 signals
2023:12:15-08:43:08 deviceXXX middleware[4527]: T core::Config::Changed:198() => configversion=37680
2023:12:15-08:43:08 deviceXXX middleware[4527]: T core::Config::Changed:208() => nodes=0 objects=1 triggers=0
2023:12:15-08:43:08 deviceXXX middleware[4527]: T core::Config::load:351() => modules=12,51
2023:12:15-08:43:09 deviceXXX middleware[4527]: T modules::up2date::load:109() => iaas_deployment=
2023:12:15-08:43:09 deviceXXX middleware[4527]: [WARN-032] Internet uplink is down
2023:12:15-08:43:09 deviceXXX middleware[4527]: T modules::IPTables::Adapters::packetfilter::clearNatCache:83() => Clear out AUTO-RULE NAT Cache
2023:12:15-08:43:09 deviceXXX middleware[4527]: T core::Config::load:394() => core::Config: wrote crontab
2023:12:15-08:43:10 deviceXXX middleware[4527]: T modules::ipset::deleteUnused:342() => auto#=37/682 confd#=1/341
2023:12:15-08:43:10 deviceXXX middleware[4527]: T main::top-level:264() => ending cycle 35767, caught 0 signals, 0 children still running
2023:12:15-08:43:21 deviceXXX middleware[4527]: T main::top-level:213() => starting cycle 35768, caught 1 signals
2023:12:15-08:43:22 deviceXXX middleware[4527]: T core::Config::Changed:198() => configversion=37681
2023:12:15-08:43:22 deviceXXX middleware[4527]: T core::Config::Changed:208() => nodes=0 objects=1 triggers=0
2023:12:15-08:43:22 deviceXXX middleware[4527]: T core::Config::load:351() => modules=12,51
2023:12:15-08:43:22 deviceXXX middleware[4527]: T modules::up2date::load:109() => iaas_deployment=
2023:12:15-08:43:22 deviceXXX middleware[4527]: [WARN-033] Internet uplink is up again
2023:12:15-08:43:22 deviceXXX middleware[4527]: T modules::IPTables::Adapters::packetfilter::clearNatCache:83() => Clear out AUTO-RULE NAT Cache
2023:12:15-08:43:22 deviceXXX middleware[4527]: T core::Config::load:394() => core::Config: wrote crontab
2023:12:15-08:43:23 deviceXXX middleware[4527]: T modules::ipset::deleteUnused:342() => auto#=37/682 confd#=1/341
2023:12:15-08:43:23 deviceXXX middleware[4527]: T main::top-level:264() => ending cycle 35768, caught 0 signals, 0 children still running

Der Switchport, an dem das interface angeschlossen ist bleibt während dieser Zeit up, d.h. die physische Verbindung ist da. Auch können wir in diesem Zeitraum keine Einschränkungen feststellen, die Bandbreitennutzung liegt zu diesem Zeitpunkt <50%.

Jemand eine Idee?



This thread was automatically locked due to age.
Parents Reply
  • After disabled "Automatic Monitoring" both WAN Interface got an link error and 2nd WAN interface no longer worked. All traffic was routed over 1st WAN interface. Activating "Automatic Monitoring" again the error was immedeatily gone and 2nd WAN interface worked like usual.

Children