I'm working on seting up an IP SLA responder on a Catalyst 4948. Something has become confused, and CPU is getting hammered. There are no current probes being directed at the device.
During initial testing, I played with various configs getting control channel and authentication setup. I've ended up with two identical lines in the running config that can't be removed, and CPU is >90%. ip sla responder udp-echo port 5558 ip sla responder udp-echo port 5558 ip sla key-chain SLAK #no ip sla responder udp-echo port 5558 %Responder not found CPU utilization for five seconds: 99%/0%; one minute: 99%; five minutes: 94% PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process 133 801304 37320583 21 87.21% 87.59% 81.27% 0 IP SLAs Responde 46 5852234081373919947 425 9.82% 9.34% 9.04% 0 Cat4k Mgmt HiPri 39 18835532 514129 36635 1.11% 0.14% 0.07% 0 Per-minute Job Any suggestions for clobbering the responder? I'd rather not reboot if possible. Thanks, _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
