04-13-2010 10:04 AM - edited 02-21-2020 03:55 AM
Once the CAS is added to the CAM this process uses 100% of the CPU on the CAS. I'm using the 3315 platform for the manager and a 3350 for the CAS.
top - 13:03:21 up 8 min, 1 user, load average: 1.27, 1.06, 0.56
Tasks: 71 total, 3 running, 68 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.3%us, 53.2%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 46.5%si, 0.0%st
Mem: 1943428k total, 865304k used, 1078124k free, 635956k buffers
Swap: 4192956k total, 0k used, 4192956k free, 118224k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3076 root 25 0 0 0 0 R 99.9 0.0 6:35.33 kclick
Any idea if this is normal?
04-13-2010 10:09 AM
Hello,
That is normal and expected.
HTH,
Faisal
04-13-2010 10:11 AM
Can you tell me what this process is for?
04-13-2010 10:13 AM
Hello,
CAS uses the click router to do it's NAC magic. In pre-4.7 versions it didn't use up the whole CPU, but in this latest iteration, it does the CPU slicing for any process that might need CPU attention also. If you see any other process than kclick taking large amount of CPU time, I'd take a close look at it, but for this process it's expected.
HTH,
Faisal
04-13-2010 10:18 AM
Interesting method - I'm sure the datacentre will be complaining about a rise in ambient heat. :-)
11-07-2011 05:41 PM
I have the same problem,
In the morning,all employees just came to the company,at this time,there will be a lot of requests for verification to NAS.
Often kclick process 100% of the phenomenon, leading to the terminal can not be verified.
-----------------------------------------------------------------------------------------------------------------------------------
[root@CAS1 ~]# sar 2 100
Linux 2.6.18-cisco.nac.1 (CAS1) 11/08/2011
08:55:50 AM CPU %user %nice %system %iowait %steal %idle
08:55:52 AM all 0.00 0.00 100.00 0.00 0.00 0.00
08:55:54 AM all 0.00 0.00 100.00 0.00 0.00 0.00
08:55:56 AM all 0.50 0.00 99.50 0.00 0.00 0.00
08:55:58 AM all 0.00 0.00 100.00 0.00 0.00 0.00
08:56:00 AM all 0.00 0.00 100.00 0.00 0.00 0.00
08:56:02 AM all 0.50 0.00 99.50 0.00 0.00 0.00
-----------------------------------------------------------------------------------------------------------------------------------
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2225 root 25 0 0 0 0 R 99.9 0.0 9775:52 kclick
2435 root 21 0 1229m 134m 8492 S 0.3 7.1 58:33.43 java
30882 root -2 0 4932 4932 2012 S 0.3 0.3 6:27.78 heartbeat
1 root 15 0 2064 624 536 S 0.0 0.0 0:00.57 init
2 root 34 19 0 0 0 S 0.0 0.0 0:00.01 ksoftirqd/0
3 root RT -5 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
-----------------------------------------------------------------------------------------------------------------------------------
[root@CAS1 ~]# netstat -an | grep 10.128.17
tcp 0 0 10.128.15.2:443 10.128.17.247:1258 FIN_WAIT2
tcp 0 30 10.128.15.2:443 10.128.17.139:2194 FIN_WAIT1
tcp 0 0 10.128.15.1:80 10.128.17.217:1742 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.217:1743 TIME_WAIT
tcp 0 30 10.128.15.2:443 10.128.17.28:2058 FIN_WAIT1
tcp 0 0 10.128.15.1:80 10.128.17.242:1530 TIME_WAIT
tcp 0 38 10.128.15.2:443 10.128.17.29:49440 FIN_WAIT1
tcp 0 0 10.128.15.1:80 10.128.17.24:1067 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.24:1066 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.175:2184 TIME_WAIT
tcp 0 0 10.128.15.2:80 10.128.17.66:1805 FIN_WAIT2
tcp 0 0 10.128.15.1:80 10.128.17.70:1536 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.70:1539 TIME_WAIT
tcp 0 30 10.128.15.2:443 10.128.17.121:1343 FIN_WAIT1
tcp 0 0 10.128.15.1:80 10.128.17.70:1540 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.70:1542 TIME_WAIT
tcp 0 38 10.128.15.2:443 10.128.17.76:62769 FIN_WAIT1
tcp 0 38 10.128.15.2:443 10.128.17.76:62771 FIN_WAIT1
tcp 0 38 10.128.15.2:443 10.128.17.76:62770 FIN_WAIT1
tcp 0 0 10.128.15.1:80 10.128.17.69:1065 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.93:1079 TIME_WAIT
tcp 0 0 10.128.15.2:80 10.128.17.76:62758 FIN_WAIT2
tcp 0 0 10.128.15.1:80 10.128.17.69:1059 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.93:1083 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.93:1081 TIME_WAIT
tcp 0 0 10.128.15.1:443 10.128.17.93:1087 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.69:1060 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.93:1085 TIME_WAIT
tcp 0 0 10.128.15.2:80 10.128.17.179:1596 ESTABLISHED
tcp 0 0 10.128.15.2:80 10.128.17.70:1530 FIN_WAIT2
tcp 0 0 10.128.15.1:80 10.128.17.70:1534 TIME_WAIT
tcp 0 38 10.128.15.2:443 10.128.17.238:49231 FIN_WAIT1
tcp 0 0 10.128.15.1:80 10.128.17.149:1370 TIME_WAIT
tcp 0 38 10.128.15.2:443 10.128.17.169:49252 FIN_WAIT1
tcp 0 0 10.128.15.1:80 10.128.17.149:1368 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.149:1372 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.158:1369 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.158:1368 TIME_WAIT
tcp 0 1 10.128.15.1:80 10.128.17.104:1710 FIN_WAIT1
tcp 0 0 10.128.15.1:80 10.128.17.158:1371 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.158:1370 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.149:1366 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.158:1373 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.158:1372 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.158:1375 TIME_WAIT
tcp 0 0 10.128.15.1:80 10.128.17.158:1374 TIME_WAIT
tcp 0 30 10.128.15.1:8905 10.128.17.214:1544 FIN_WAIT1
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: