10-14-2020 01:01 AM
in our environment, we have 16.9.5, and after 4 entries, our Uplinks went down:
Oct 9 2020 05:59:02.711 CEST: %IOSXE_INFRA-6-PROCPATH_CLIENT_HOG: IOS shim client 'ngwc fed bipc' has taken 10384 msec (runtime: 0 msec) to process a 'unknown' message
Oct 9 2020 06:04:22.759 CEST: %IOSXE_INFRA-6-PROCPATH_CLIENT_HOG: IOS shim client 'ngwc fed bipc' has taken 10044 msec (runtime: 0 msec) to process a 'unknown' message
Oct 9 2020 06:04:53.319 CEST: %IOSXE_INFRA-6-PROCPATH_CLIENT_HOG: IOS shim client 'ngwc fed bipc' has taken 13844 msec (runtime: 0 msec) to process a 'unknown' message
Oct 9 2020 06:05:21.073 CEST: %IOSXE_INFRA-6-PROCPATH_CLIENT_HOG: IOS shim client 'ngwc fed bipc' has taken 22132 msec (runtime: 0 msec) to process a 'unknown' message
Oct 9 2020 06:05:22.093 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/1, changed state to down
Oct 9 2020 06:05:25.052 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/1, changed state to up
Oct 9 2020 06:05:25.492 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/4, changed state to down
Oct 9 2020 06:05:49.569 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/4, changed state to up
06-11-2021 07:31 AM
I'm also on 16.9.5 and saw this recently.
This bug talks about it but there's no fix
Bug Search (cisco.com)
08-09-2023 03:49 PM
Mine too on 16.9.3. Any resolution other than a firmware upgrade?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide