Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
You may experience some slow load times, errors, and slight inconsistencies. We ask for your patience as we finalize the launch. Thank you.

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

WS-C2960X-48TS-L cpu utilization C2960X-UNIVERSALK9-M Version 15.0(2)EX5

WS-C2960X-48TS-L cpu utilization C2960X-UNIVERSALK9-M Version 15.0(2)EX5 

CPU utilization for five seconds: 79%/3%; one minute: 65%; five minutes: 64%
 PID Runtime(ms)     Invoked      uSecs   5Sec   1Min   5Min TTY Process
 190   191408173    28207523       6785 34.87% 19.24% 17.42%   0 Auth Manager                                                                                                                        
 161   178000592    24299988       7325 15.12% 14.92% 14.97%   0 Hulc LED Proces


  • LAN Switching and Routing
Everyone's tags (1)

Hey,Regarding high CPU issue


Regarding high CPU issue and the two processes you have mentioned:

1. Overview of IOS Auth Manager: The capabilities of devices connecting to a given network can be different, thus requiring that the network support different authentication methods and authorization policies. The Cisco IOS Auth Manager handles network authentication requests and enforces authorization policies, regardless of authentication method. The Auth Manager maintains operational data for all port-based network connection attempts, authentications, authorizations, and disconnections and as such, serves as a session manager. So looks like this device is managing good amount of AAA sessions.

2. Hulc LED Process: Check this bug




New Member

no aaa new-model AAA is

no aaa new-model


AAA is disabled .

Max one connection of telnet is active at a time . 

Still CPU used by this process is continuous 




Cisco Employee

can you collect "debug

can you collect "debug authentication event" and "debug authentication error" if you still see high CPU after re-enabling macro?

"macro auto monitor" enables "device-classifier".
when "macro auto monitor"/device-classifier is enabled, every new packet will be given to authmgr for creating session. as part of creating session, authmgr will udpate device-classifier about the mac then device-classifer will classify the device based on mac/OUI this is the basic flow.

if you do not want to use "device classifier", you could disable macro auto monitor.

New Member

no macro auto monitor solved

no macro auto monitor 

solved my problem for Auth Manager    , however I didn't had any macro , still I guess some bug

Did you see any tracebacks

Did you see any tracebacks alongwith high CPU as I was researching and found that device classifier is enabled by default in 15.0(2)EX5 release, as you already know there are two possible workarounds:

 a) Disable "no aaa-new model"
 b) Disable macro "no macro auto monitor"

Soon there will be a bug for it as well, alternatively you may upgrade to 15.2.2E(ED) relaese.