Hello,
I need help on understanding the problem we are facing with one of our 3850 stack. The stack is currently supporting 4 switches.
We have a high CPU utilization for the past one week and I am trying to find the reason. I couldn't get any solution so far. The best one I got was rebooting the entire stack.
I have provided below the CPU utilization for all 4 cores its running on. And also the logs I have.
History information for system:
555555555555555555555555555555555555555555555555555555555555
555333333333344444444444444444444333333333333333444445555544
100
90
80
70
60 *** *****
50 ************************************************************
40 ************************************************************
30 ************************************************************
20 ************************************************************
10 ************************************************************
0....5....1....1....2....2....3....3....4....4....5....5....
0 5 0 5 0 5 0 5 0 5
CPU% per second (last 60 seconds)
556785665565555655565565565555555565555555655555565556565555
570905025445657245499706537545455455569797344744687775705455
100
90
80 **
70 ** * * * *
60 ***##**#* ****** * #******#* * ** #******** * *#**##*** **
50 ############################################################
40 ############################################################
30 ############################################################
20 ############################################################
10 ############################################################
0....5....1....1....2....2....3....3....4....4....5....5....
0 5 0 5 0 5 0 5 0 5
CPU% per minute (last 60 minutes)
* = maximum CPU% # = average CPU%
676666668886676767777668667766666687676678767676667667666676676668786667
907878860078909182002982864088999711829912282808971990988688807972018982
100
90 *
80 *** * * * * * *
70 ************************************************************************
60 ***********************#************************************************
50 ########################################################################
40 ########################################################################
30 ########################################################################
20 ########################################################################
10 ########################################################################
0....5....1....1....2....2....3....3....4....4....5....5....6....6....7.
0 5 0 5 0 5 0 5 0 5 0 5 0
CPU% per hour (last 72 hours)
* = maximum CPU% # = average CPU%
History information for core 0:
111 111111111111111 1111111111111111111111
333777777777799999222222222222222999990000000000222224444422
100
90
80
70
60
50
40
30
20
10 ************************************************************
0....5....1....1....2....2....3....3....4....4....5....5....
0 5 0 5 0 5 0 5 0 5
CPU% per second (last 60 seconds)
11 1 111
112591191141911911195129100919311121199921311911099900021112
460531373272934912398438300929244443398928310953099700033234
100 * * * * * *** * *** * ****##*
90 * * * * * * *** * *** * ****##*
80 * * * * * * *## * *** * ****##*
70 * * * * * * *## * **# * #***##*
60 ** * * * ** * *## * **# * #*#*##*
50 ** * * * * ** * *## * ### * ###*##*
40 ** * * * * ** * *## * ### * ###*###
30 ** * * # # #* # *## #* ### * # ###*###
20 **## # * # # ## *# ### #* * ###*** #* #######* *
10 ############################################################
0....5....1....1....2....2....3....3....4....4....5....5....
0 5 0 5 0 5 0 5 0 5
CPU% per minute (last 60 minutes)
* = maximum CPU% # = average CPU%
111111111111111111111111111111111111111111111111111111111 11
000000000000000000000000000000000000000000000000000000000900
000000000000000000000000000000000000000000000000000000000900
100 ************************************************************************
90 ************************************************************************
80 ************************************************************************
70 ************************************************************************
60 ************************************************************************
50 ******#***************************************#*************************
40 ******#***##***********#****#****#**##********##*##*#*********#*****#***
30 ##**########*#####*###*##*#################*#######*#*###*##############
20 ########################################################################
10 ########################################################################
0....5....1....1....2....2....3....3....4....4....5....5....6....6....7.
0 5 0 5 0 5 0 5 0 5 0 5 0
CPU% per hour (last 72 hours)
* = maximum CPU% # = average CPU%
History information for core 1:
999777777777799999666665555555555555556666666666888889999944
100
90
80
70
60
50
40
30
20
10 **********************************************************
0....5....1....1....2....2....3....3....4....4....5....5....
0 5 0 5 0 5 0 5 0 5
CPU% per second (last 60 seconds)
11111 11 11 11111111111
19900000 9009921 199999932199 1900999211299919900000000000
969900000990099919199998572489881900987057399918900000000000
100 ***###* *#**# ***#** ** *###** *#* ****#########
90 #*####* *#*## ***#** ** *###** *#* #***#########
80 #*####* *#*## ***#** *# *###** *#* #***#########
70 ######* *#*## ***#** ## *###** *#* #***#########
60 ####### *#*## ***#** ## *###*# *## #**##########
50 ####### *#*## ***#** ## ###### *## #############
40 ####### ##### *#*#*** ## ###### ### #############
30 ####### #####* #####** ## ###### ### #############
20 *####### #####* ######** ## ######****### #############
10 ############################################################
0....5....1....1....2....2....3....3....4....4....5....5....
0 5 0 5 0 5 0 5 0 5
CPU% per minute (last 60 minutes)
* = maximum CPU% # = average CPU%
111111111111111111111111111111111111111111111111111111111111
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
100 **************************##********************************************
90 **********#***************###******#*****#*********#********************
80 **********#*#*******##****###******#*#***#***#***###********#****#******
70 ***#**#***#*###****###*#*####****#*####**##**#*#*###***#***##*####*#****
60 ***##*##*#######***#####*####*#**#*####*######*#########**##########**#*
50 #*######################*#########*###########*######################*##
40 ########################################################################
30 ########################################################################
20 ########################################################################
10 ########################################################################
0....5....1....1....2....2....3....3....4....4....5....5....6....6....7.
0 5 0 5 0 5 0 5 0 5 0 5 0
CPU% per hour (last 72 hours)
* = maximum CPU% # = average CPU%
History information for core 2:
999999999999999999999999999999999999999999999999999999999999
888888888888888888888889999988888999998888899999999998888899
100 ************************************************************
90 ************************************************************
80 ************************************************************
70 ************************************************************
60 ************************************************************
50 ************************************************************
40 ************************************************************
30 ************************************************************
20 ************************************************************
10 ************************************************************
0....5....1....1....2....2....3....3....4....4....5....5....
0 5 0 5 0 5 0 5 0 5
CPU% per second (last 60 seconds)
1 1111111111111111111 1 11
99990 39000000000000000000099 99994119290999 999 91123999009
999909090000000000000000000969998810160909889997927806999009
100 ##*** **##################** ###* * *###* *#* *####*
90 ##*** **##################** ###* * *###* *#* * *####*
80 ##*** **##################** ###* * *###* *#* * *#####
70 ##*** **##################** ###* * *###* *#* * ######
60 ##*** **##################** ###* * *#### *#* * ######
50 ##*** *###################** #### * *#### *#* * ######
40 ##**# *####################* ####* * ##### *#* * *######
30 ##*## *###################### ####* * ##### ##* * *######
20 ##### *###################### ####* #*##### ### #**########
10 ############################################################
0....5....1....1....2....2....3....3....4....4....5....5....
0 5 0 5 0 5 0 5 0 5
CPU% per minute (last 60 minutes)
* = maximum CPU% # = average CPU%
1111111111111111111111111111111111111111111111111111111111 1
000000000000000000000000000000000000000000000000000000000090
000000000000000000000000000000000000000000000000000000000090
100 *##****###********#*****#******##*#************************************#
90 *##****###*****#*##*****#****#*##*#*****************#*************#****#
80 *##****###*****#*###****#****#*##*#*******##********#***#*********#***##
70 *##**#####*#***#*###**#*#****#*#####**#***##***#**#*#*#*#***##****#***##
60 ###**#####*#####*###*##*#***##*########*####**##*##*#*#*#**###****#*#*##
50 ###*######*#####*######*#**###*#############**##*####*###**###*#*##*#*##
40 ############################################*###*#############*#########
30 ########################################################################
20 ########################################################################
10 ########################################################################
0....5....1....1....2....2....3....3....4....4....5....5....6....6....7.
0 5 0 5 0 5 0 5 0 5 0 5 0
CPU% per hour (last 72 hours)
* = maximum CPU% # = average CPU%
History information for core 3:
11111
999999999999999999999999999999999000009999999999999999999999
999999999999999999999999999999999000009999999999999999999999
100 ************************************************************
90 ************************************************************
80 ************************************************************
70 ************************************************************
60 ************************************************************
50 ************************************************************
40 ************************************************************
30 ************************************************************
20 ************************************************************
10 ************************************************************
0....5....1....1....2....2....3....3....4....4....5....5....
0 5 0 5 0 5 0 5 0 5
CPU% per second (last 60 seconds)
1111 1 1 11111111111 111 11111111
000099909991981999999029999000000000009000900000000912121 19
000099909990925999899078998000000000009000900000000917000909
100 ####*##*##* * *###*** *****######################** *
90 #######*##* * *###*** **#**######################## *
80 #######*##* ** *###**# *##*######################### *
70 ##########* ** ####**# *##*######################### *
60 ########### ** ####### ###*######################### *
50 ########### ** ####### ###*######################### *
40 ########### #* ####### ###*######################### *
30 ########### #* #######*############################# * *
20 ########### ##*#######*############################# * * #
10 ############################################################
0....5....1....1....2....2....3....3....4....4....5....5....
0 5 0 5 0 5 0 5 0 5
CPU% per minute (last 60 minutes)
* = maximum CPU% # = average CPU%
1111111 1 1111111111111111111111 111111111111111111111111111
000000090900000000000000000000009000000000000000000000000000
000000090900000000000000000000009000000000000000000000000000
100 ****************#***************************#************##**********#**
90 ***#************#***************************#***#****#***##**********#**
80 ***##***********#********#****#********#****#***#****#***##*****#**#*#**
70 #**##***********#******#*#****#********##***#*#*#****#*#*##***#*#**###**
60 #**###*******##*#*****##*#****#********##***###*#**#*###*###*#####*###**
50 ##*###****#*###*###*#*#####**##*****#*####*######**#*#######*#####*###**
40 ######****#########################*##############*#*###################
30 #######*#*##############################################################
20 ########################################################################
10 ########################################################################
0....5....1....1....2....2....3....3....4....4....5....5....6....6....7.
0 5 0 5 0 5 0 5 0 5 0 5 0
CPU% per hour (last 72 hours)
* = maximum CPU% # = average CPU%
Logs:
Feb 21 10:51:42.385 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/45, changed state to down
Feb 21 10:51:43.385 Central: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/45, changed state to down
Feb 21 10:53:05.266 Central: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/45, changed state to up
Feb 21 10:53:06.264 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/45, changed state to up
Feb 21 10:53:27.444 Central: %DOT1X-5-FAIL: Authentication failed for client (009c.0206.13a9) on Interface Gi3/0/45 AuditSessionID AC14FFA10000483281A4389C
Feb 21 10:54:20.956 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/45, changed state to down
Feb 21 10:54:21.966 Central: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/45, changed state to down
Feb 21 10:55:38.908 Central: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/45, changed state to up
Feb 21 10:55:39.906 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/45, changed state to up
Feb 21 10:56:00.998 Central: %DOT1X-5-FAIL: Authentication failed for client (009c.0206.13a9) on Interface Gi3/0/45 AuditSessionID AC14FFA10000483381A69074
Feb 21 11:11:13.485 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/45, changed state to down
Feb 21 11:11:14.499 Central: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/45, changed state to down
Feb 21 11:11:21.740 Central: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/45, changed state to up
Feb 21 11:11:22.740 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/45, changed state to up
Feb 21 11:11:35.017 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/45, changed state to down
Feb 21 11:11:36.015 Central: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/45, changed state to down
Feb 21 11:11:39.109 Central: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/45, changed state to up
Feb 21 11:11:40.111 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/45, changed state to up
Feb 21 11:11:57.764 Central: %DOT1X-5-FAIL: Authentication failed for client (34e6.d70a.745f) on Interface Gi1/0/45 AuditSessionID AC14FFA10000483481B529E0
Feb 21 11:11:58.178 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 21 11:11:58.178 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 21 11:11:58.178 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 21 11:11:58.178 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 21 11:11:58.178 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 21 11:11:58.178 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 21 11:11:58.178 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 21 11:11:58.178 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 21 11:11:58.178 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 21 12:04:38.105 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/15, changed state to down
Feb 21 12:04:39.109 Central: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/15, changed state to down
Feb 21 12:23:54.454 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/45, changed state to down
Feb 21 12:23:55.465 Central: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/45, changed state to down
Feb 21 12:25:20.854 Central: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/45, changed state to up
Feb 21 12:25:21.860 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/45, changed state to up
Feb 21 12:25:40.468 Central: %DOT1X-5-FAIL: Authentication failed for client (009c.0206.13a9) on Interface Gi3/0/45 AuditSessionID AC14FFA10000483581F8A616
Feb 21 12:58:17.604 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/40, changed state to down
Feb 21 12:58:18.608 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/40, changed state to down
Feb 21 12:58:26.195 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/40, changed state to up
Feb 21 12:58:27.194 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/40, changed state to up
Feb 21 12:58:34.974 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/40, changed state to down
Feb 21 12:58:36.976 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/40, changed state to up
Feb 21 12:58:57.157 Central: %DOT1X-5-FAIL: Authentication failed for client (0030.c15e.b980) on Interface Gi2/0/40 AuditSessionID AC14FFA10000483782171D9E
Feb 21 14:56:03.675 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/19, changed state to down
Feb 21 14:56:04.676 Central: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/19, changed state to down
Feb 21 16:19:34.198 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/7, changed state to down
Feb 21 16:19:35.208 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/7, changed state to down
Feb 21 16:19:39.377 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/7, changed state to up
Feb 21 16:19:40.379 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/7, changed state to up
Feb 21 16:25:07.438 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/38, changed state to down
Feb 21 16:25:08.439 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/38, changed state to down
Feb 21 16:25:11.127 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/38, changed state to up
Feb 21 16:25:12.126 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/38, changed state to up
Feb 21 16:25:45.796 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/38, changed state to down
Feb 21 16:25:46.798 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/38, changed state to down
Feb 21 16:51:31.824 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/33, changed state to down
Feb 21 16:51:32.825 Central: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/33, changed state to down
Feb 22 03:04:53.506 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/14, changed state to down
Feb 22 03:04:54.518 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/14, changed state to down
Feb 22 03:05:01.208 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/14, changed state to up
Feb 22 03:05:02.210 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/14, changed state to up
Feb 22 03:17:25.455 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/14, changed state to down
Feb 22 03:17:26.454 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/14, changed state to down
Feb 22 03:17:33.189 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/14, changed state to up
Feb 22 03:17:34.189 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/14, changed state to up
Feb 22 03:19:18.285 Central: %DOT1X-5-FAIL: Authentication failed for client (9c93.4e5c.9aa2) on Interface Gi2/0/14 AuditSessionID AC14FFA100004846852ACA9E
Feb 22 06:25:53.567 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/41, changed state to down
Feb 22 06:25:56.685 Central: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/41, changed state to down
Feb 22 06:25:59.887 Central: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/41, changed state to up
Feb 22 06:26:00.888 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/41, changed state to up
Feb 22 06:26:24.076 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/41, changed state to down
Feb 22 06:26:25.086 Central: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/41, changed state to down
Feb 22 06:26:28.258 Central: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/41, changed state to up
Feb 22 06:26:29.256 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/41, changed state to up
Feb 22 06:50:30.516 Central: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/19, changed state to up
Feb 22 06:50:33.067 Central: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/19, changed state to down
Feb 22 06:50:36.216 Central: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/19, changed state to up
Feb 22 06:50:37.214 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/19, changed state to up
Feb 22 06:51:13.149 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/19, changed state to down
Feb 22 06:51:14.144 Central: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/19, changed state to down
Feb 22 06:51:17.276 Central: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/19, changed state to up
Feb 22 06:51:18.277 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/19, changed state to up
Feb 22 07:05:48.257 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/7, changed state to down
Feb 22 07:05:51.385 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/7, changed state to down
Feb 22 07:05:54.680 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/7, changed state to up
Feb 22 07:05:55.678 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/7, changed state to up
Feb 22 07:06:33.215 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/7, changed state to down
Feb 22 07:06:34.225 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/7, changed state to down
Feb 22 07:06:37.387 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/7, changed state to up
Feb 22 07:06:38.384 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/7, changed state to up
Feb 22 07:06:56.236 Central: %DOT1X-5-FAIL: Authentication failed for client (ecf4.bb4d.aebc) on Interface Gi2/0/7 AuditSessionID AC14FFA10000484A85FB3206
Feb 22 07:06:56.506 Central: %IOSXE-5-PLATFORM: 2 process fed: Logging is not supported for Client/Group ACL
Feb 22 07:06:56.506 Central: %IOSXE-5-PLATFORM: 2 process fed: Logging is not supported for Client/Group ACL
Feb 22 07:06:56.506 Central: %IOSXE-5-PLATFORM: 2 process fed: Logging is not supported for Client/Group ACL
Feb 22 07:06:56.506 Central: %IOSXE-5-PLATFORM: 2 process fed: Logging is not supported for Client/Group ACL
Feb 22 07:06:56.506 Central: %IOSXE-5-PLATFORM: 2 process fed: Logging is not supported for Client/Group ACL
Feb 22 07:06:56.506 Central: %IOSXE-5-PLATFORM: 2 process fed: Logging is not supported for Client/Group ACL
Feb 22 07:06:56.506 Central: %IOSXE-5-PLATFORM: 2 process fed: Logging is not supported for Client/Group ACL
Feb 22 07:06:56.506 Central: %IOSXE-5-PLATFORM: 2 process fed: Logging is not supported for Client/Group ACL
Feb 22 07:06:56.506 Central: %IOSXE-5-PLATFORM: 2 process fed: Logging is not supported for Client/Group ACL
Feb 22 07:20:25.847 Central: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/15, changed state to up
Feb 22 07:20:26.846 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/15, changed state to up
Feb 22 07:20:43.426 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/15, changed state to down
Feb 22 07:20:44.428 Central: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/15, changed state to down
Feb 22 07:20:47.505 Central: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/15, changed state to up
Feb 22 07:20:48.510 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/15, changed state to up
Feb 22 08:26:52.275 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/38, changed state to up
Feb 22 08:26:53.280 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/38, changed state to up
Feb 22 08:27:26.394 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/38, changed state to down
Feb 22 08:27:27.398 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/38, changed state to down
Feb 22 08:27:30.644 Central: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/38, changed state to up
Feb 22 08:27:31.648 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/38, changed state to up
Feb 22 09:01:49.866 Central: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/33, changed state to up
Feb 22 09:01:50.867 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/33, changed state to up
Feb 22 09:02:11.567 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/33, changed state to down
Feb 22 09:02:12.565 Central: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/33, changed state to down
Feb 22 09:02:19.786 Central: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/33, changed state to up
Feb 22 09:02:20.788 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/33, changed state to up
Feb 22 09:02:22.016 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/33, changed state to down
Feb 22 09:02:23.015 Central: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/33, changed state to down
Feb 22 09:02:26.194 Central: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/33, changed state to up
Feb 22 09:02:27.198 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/33, changed state to up
Feb 22 09:03:32.608 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/33, changed state to down
Feb 22 09:03:33.608 Central: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/33, changed state to down
Feb 22 09:03:36.767 Central: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/33, changed state to up
Feb 22 09:03:37.773 Central: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/33, changed state to up
Feb 22 09:03:55.747 Central: %DOT1X-5-FAIL: Authentication failed for client (f01f.af21.905e) on Interface Gi1/0/33 AuditSessionID AC14FFA10000485186664DF2
Feb 22 09:03:55.914 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 22 09:03:55.914 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 22 09:03:55.914 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 22 09:03:55.914 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 22 09:03:55.915 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 22 09:03:55.915 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 22 09:03:55.915 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 22 09:03:55.915 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 22 09:03:55.915 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Some of the logs are repeating at irregular interval. is this something to do with this high CPU utilization. Couple the cores are at 100% almost all the time.
Feb 22 09:03:55.914 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 22 09:03:55.914 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 22 09:03:55.914 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 22 09:03:55.914 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 22 09:03:55.915 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 22 09:03:55.915 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 22 09:03:55.915 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 22 09:03:55.915 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Feb 22 09:03:55.915 Central: %IOSXE-5-PLATFORM: STANDBY:1 process fed: Logging is not supported for Client/Group ACL
Any help on this issue is much appreciated.