HTTP CORE process is related to HTTP request destined to the switch itself. You would want to check "show tcp brief" and "show ip http server all" commands to see the originators from those request when the CPU goes high again.
Use the following steps to manually clera htt/https hung up sessions:
1) Issue the command "clear ip http client cache all"
2) If this does not help, issue the command "show tcp brief"
3) Take the output "TCB" addresses from the previous command and place them instead of the brackets in the following command:
clear tcp tcb
4) If you are using http and if the issue was due to HTTP request to the switch, the command "no ip http secure-server" would work out avoiding from re-ocurring.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...