cisco 2911-k9 нагрузка на интерфейсе

[Muller]

Есть несколько маршрутизаторов cisco 2911 k9 которые подключены по отказоустойчивой схеме и держат BGP (default route). На одном из роутеров мониторинг показывает обрыв. Зашел в лог и увидел подозрительное сообщение:

000038: *May 20 12:14:14.067 Moscow: %TRACKING-5-STATE: 220 list boolean and Down->Up
000039: *May 20 12:14:14.067 Moscow: %TRACKING-5-STATE: 1 ip sla 1 reachability Down->Up
000040: *May 20 12:14:14.067 Moscow: %TRACKING-5-STATE: 200 ip route 0.0.0.0/0 metric threshold Down->Up
000041: *May 20 12:14:15.067 Moscow: %TRACKING-5-STATE: 220 list boolean and Up->Down
000042: *May 20 12:14:19.067 Moscow: %TRACKING-5-STATE: 5 ip sla 5 reachability Down->Up
000043: *May 20 12:14:19.067 Moscow: %TRACKING-5-STATE: 6 ip sla 6 reachability Down->Up
000044: *May 20 12:14:19.067 Moscow: %TRACKING-5-STATE: 9 ip sla 9 reachability Down->Up
000045: *May 20 12:14:19.067 Moscow: %TRACKING-5-STATE: 15 list boolean or Down->Up
[COLOR=#FFA500][B]000046: *May 20 12:14:19.071 Moscow: %PARSER-5-CFGLOG_LOGGEDCMD: User:unknown user  logged command:!exec: enable[/B][/COLOR]
000047: *May 20 12:14:33.019 Moscow: %HSRP-5-STATECHANGE: Port-channel1.306 Grp 1 state Standby -> Listen
000048: *May 20 12:15:12.763 Moscow: %HSRP-5-STATECHANGE: Port-channel1.306 Grp 1 state Speak -> Standby
000049: *May 20 12:15:14.067 Moscow: %TRACKING-5-STATE: 200 ip route 0.0.0.0/0 metric threshold Up->Down
000050: *May 20 12:15:14.135 Moscow: %TRACKING-5-STATE: 220 list boolean and Down->Up
000051: *May 20 12:15:15.135 Moscow: %TRACKING-5-STATE: 20 list boolean and Down->Up
000052: *May 20 12:15:16.247 Moscow: %HSRP-5-STATECHANGE: Port-channel1.306 Grp 1 state Standby -> Active

cisco спецы подскажите что означает

 

[RG45]

настроено журналирование и аудит событий в syslog сервер, похоже еще трэкинг работает

 

[Muller]

это да. Но как понять почему пропадает сеть?
Я вижу что линк падает но не пойму почему.. или это у провайдера что то:kaktus:

[COLOR=#FF0000][B]000029: *May 20 12:13:54.699 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to down[/B][/COLOR]
000030: *May 20 12:13:54.751 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
000031: *May 20 12:13:54.887 Moscow: %SYS-6-LOGGINGHOST_STARTSTOP: [B][COLOR=#006400]Logging to host syslog-SRV port 514 started[/COLOR][/B] - CLI initiated
000032: *May 20 12:13:55.755 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
000033: *May 20 12:13:56.071 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
000034: *May 20 12:13:57.071 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to up
000035: *May 20 12:13:57.871 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to up

 

[Muller]

Вот еще самое начало лога. Похоже все таки что обрыв у провайдера

*May 20 09:13:28.631: [COLOR=#FF0000][B]c3600_scp_set_dstaddr2_idb(184)add = 80 name is Embedded-Service-Engine0/0[/B][/COLOR]
*May 20 09:13:45.715: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to up
*May 20 09:13:45.715: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
*May 20 09:13:45.715: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
*May 20 09:13:46.883: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to up
*May 20 09:13:46.883: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
*May 20 09:13:46.883: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to up
000011: *May 20 12:13:47.931 Moscow: %SYS-6-CLOCKUPDATE: [COLOR=#FF0000]System clock has been updated from 09:13:47 UTC Mon May 20 2019 to 12:13:47 Moscow Mon[/COLOR] May 20 2019, configured from console by console.
000012: *May 20 12:13:48.195 Moscow: %PARSER-5-CFGLOG_PERSIST_OPER_UP: [COLOR=#FF0000][B]Configuration logger persistency is operationally up[/B][/COLOR]
000013: *May 20 12:13:48.663 Moscow: %PARSER-3-CFGLOG_NOMEM: User:console    command: