Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
ASR-1001-x device continuously reporting high CPU due to "IP RESPONDE" process and interrupts after upgrading from 16.9.3 to 17.6.2. Router_A#show ver Cisco IOS XE Software, Version 17.06.02 Cisco IOS Software [Bengaluru], ASR1000 Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 17.6.2, RELEASE SOFTWARE (fc7) Router_A#show processes cpu sorted | exc 0.00 CPU utilization for five seconds: 93%/43%; one minute: 93%; five minutes: 91% PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process 714 2722208 4617848 589 66.95% 65.40% 63.78% 0 IP SLAs Responder >>>>>>>> 136 410407 2853071 143 7.37% 7.98% 8.09% 0 IOSXE-RP Punt Se 558 38446 769543 49 1.84% 1.92% 1.79% 0 IPv6 Input 713 9629 1140116 8 0.16% 0.10% 0.09% 0 IP SLAs Control 89 3107 15680 198 0.08% 0.04% 0.05% 0 IOSD ipc task When downgrading to 16.x train, the CPU lowers its utilization: Router_A#show ver Cisco IOS XE Software, Version 16.09.03 Cisco IOS Software [Fuji], ASR1000 Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 16.9.3, RELEASE SOFTWARE (fc2) Router_A#show processes cpu sorted | exc 0.00 CPU utilization for five seconds: 49%/13%; one minute: 43%; five minutes: 13% PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process 676 26976 240576 112 27.35% 24.09% 7.54% 0 IP SLAs Responder >>>>>>>> 125 6698 138414 48 7.03% 5.86% 1.85% 0 IOSXE-RP Punt Se 452 2275 91373 24 2.71% 1.99% 0.62% 0 IPv6 Input
IOS Version: 17.6.2 Frequency: 120s Scale: 5.08k as responder Observation: The CPU utilization goes up to 88%-90% and stays that way for 1min. Then, the CPU utilization goes down, around 13-15% of utilization and stays that way for 1min again until it goes up again. IOS Version: 16.9.2 Frequency: 120s Scale: 5.08k as responder Observation: The CPU utilization goes up to 61%-64% and stays that way for 1min. Then, the CPU utilization goes down, around 10-12% of utilization and stays that way for 1min again until it goes up again.
As of now with the current scale ie.,5.08k as responder & 120s Frequency interval, 16.9 release is reporting nominal CPU usage.
So far only the IPv6 traffic is affected as we can locate the ICMP drops while trying to ping any destinations Router_A#ping aaaa:aaaa:aaa:a::aaa rep 1000 Type escape sequence to abort. Sending 1000, 100-byte ICMP Echos to aaaa:aaaa:aaa:a::aaa, timeout is 2 seconds: !!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!....!!!!!!!.!!!!!..!!!!! !....!!!!.!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!.!!!!! !!!!!!.!!!!!!..!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!.!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!. Success rate is 90 percent (224/247), round-trip min/avg/max = 68/74/100 ms