01-21-2014 08:15 PM - edited 03-07-2019 05:43 PM
Hi I have an unusual behavior on Catalyst 4506E switche. The cpu utilization is 35%
The process K2FibAdjMan Host Mov is consuming HIgh ressources....
Does anyone have any suggestion?
Thnaks a lot
JT-4506-1#sh proc cpu so 5se
CPU utilization for five seconds: 32%/0%; one minute: 30%; five minutes: 31%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
58 8818750353707169302 0 21.19% 17.64% 18.35% 0 Cat4k Mgmt LoPri
57 2535818316 443647374 5715 7.27% 7.83% 7.88% 0 Cat4k Mgmt HiPri
109 431437899 749682568 575 0.79% 0.93% 0.98% 0 IP Input
14 2890879741522020496 189 0.47% 0.61% 0.59% 0 ARP Input
116 103254436 378426195 272 0.39% 0.39% 0.39% 0 Spanning Tree
112 2657381781294108349 205 0.31% 1.06% 0.86% 0 ADJ resolve proc
JT-4506-1#sh pl health
%CPU %CPU RunTimeMax Priority Average %CPU Total
Target Actual Target Actual Fg Bg 5Sec Min Hour CPU
this is unusual:
K2L2 Address Table R 2.00 18.99 12 5 100 500 12 9 7 51455:59
K2FibAdjMan Host Mov 2.00 12.43 10 7 100 500 8 8 7 11238:47
JT-4506-1#sh mac add aging-time
Vlan Aging Time Configured Aging Time
---- ---------- ---------------------
Global Vlan Admin Age: 300
1 300 300
100 300 300
300 300 300
500 300 300
501 300 300
502 300 300
503 300 300
600 15 300
why vlan600 aging time is 15sec?? no edit
JT-4506-1#sh version
Cisco IOS Software, Catalyst 4500 L3 Switch Software (cat4500-ENTSERVICESK9-M), Version 12.2(54)SG, RELEASE SOFTWARE (fc3)
Technical Support:
http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Sun 27-Jun-10 00:29 by prod_rel_team
Image text-base: 0x10000000, data-base: 0x123F21AC
ROM: 12.2(31r)SGA3
Pod Revision 16, Force Revision 31, Tie Revision 32
cisco WS-C4506-E (MPC8540) processor (revision 13) with 524288K bytes of memory.
Processor board ID FOX1524GGAV
MPC8540 CPU at 800Mhz, Supervisor V-10GE
Last reset from PowerUp
6 Virtual Ethernet interfaces
106 Gigabit Ethernet interfaces
2 Ten Gigabit Ethernet interfaces
511K bytes of non-volatile configuration memory.
Configuration register is 0x2102
01-22-2014 12:44 AM
My guess would be that you have a spanning tree issue which is causing topology changes in the network, hence the MAC address moves and the short aging timer i.e., the same value as the forward delay, being seen for VLAN 600.
If you run the show spanning-tree vlan 600 detail command the first few lines of the output will indicate the number of topology changes that have occurred, when the last one was and the interface it was received from.
Regards
01-23-2014 06:10 AM
hi steve
I don't know where the problem.
show spanning-tree vlan 600 detail
VLAN0600 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 24576, sysid 600, address 0007.7dc5.cc80
Configured hello time 2, max age 20, forward delay 15
We are the root of the spanning tree
Topology change flag set, detected flag set
Number of topology changes 133150 last change occurred 00:01:55 ago
from GigabitEthernet3/11
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 1, topology change 27, notification 0, aging 15
sh spanning-tree interface gi3/11 de
Port 139 (GigabitEthernet3/11) of VLAN0600 is designated forwarding
Port path cost 4, Port priority 128, Port Identifier 128.139.
Designated root has priority 25176, address 0007.7dc5.cc80
Designated bridge has priority 25176, address 0007.7dc5.cc80
Designated port id is 128.139, designated path cost 0
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 31838426, received 441659
sh run inter gi3/11
interface GigabitEthernet3/11
switchport private-vlan host-association 600 610
switchport mode private-vlan host
end
sh mac add inter gi3/11
Unicast Entries
vlan mac address type protocols port
-------+---------------+--------+---------------------+--------------------
600 0014.5eac.777d dynamic ip GigabitEthernet3/11
600 001a.4be1.e284 dynamic ip GigabitEthernet3/11
600 001a.6c67.2a2f dynamic other GigabitEthernet3/11
Multicast Entries
vlan mac address type ports
-------+---------------+-------+--------------------------------------------
600 0100.5e05.0505 igmp Gi2/4,Gi2/6,Gi3/1,Gi3/2,Gi3/3,Gi3/4,Gi3/5
Gi3/8,Gi3/9,Gi3/10,Gi3/11,Gi3/12,Gi3/14,Gi3/16
Gi3/17,Gi3/18,Gi3/19,Gi3/20,Gi3/21,Gi3/22
Gi3/23,Gi3/24,Gi3/26,Gi3/27,Gi3/36,Gi3/39
Gi3/41,Gi3/42,Gi3/43,Gi3/44,Gi3/45,Gi5/1
Gi5/2,Gi5/3,Gi5/4,Gi5/5,Gi5/6,Gi5/7,Gi5/8
Gi5/9,Gi5/10,Gi5/11,Gi5/12,Gi5/13,Gi5/14
Gi5/16,Gi5/17,Gi5/19,Gi5/20,Gi5/21,Gi5/22
Gi5/23,Gi5/26,Gi5/28,Gi5/29,Gi5/31,Gi5/32
Gi5/33,Gi5/34,Gi5/35,Gi5/36,Gi5/37,Gi5/38
Gi5/39,Gi5/40,Gi5/41,Gi5/43,Gi5/45,Gi5/47
600 0100.5e26.4cda igmp Gi2/4,Gi2/6,Gi3/1,Gi3/2,Gi3/3,Gi3/4,Gi3/5
Gi3/8,Gi3/9,Gi3/10,Gi3/11,Gi3/12,Gi3/14,Gi3/16
Gi3/17,Gi3/18,Gi3/19,Gi3/20,Gi3/21,Gi3/22
Gi3/23,Gi3/24,Gi3/26,Gi3/27,Gi3/36,Gi3/39
Gi3/41,Gi3/42,Gi3/43,Gi3/44,Gi3/45,Gi5/1
Gi5/2,Gi5/3,Gi5/4,Gi5/5,Gi5/6,Gi5/7,Gi5/8
Gi5/9,Gi5/10,Gi5/11,Gi5/12,Gi5/13,Gi5/14
Gi5/16,Gi5/17,Gi5/19,Gi5/20,Gi5/21,Gi5/22
Gi5/23,Gi5/26,Gi5/28,Gi5/29,Gi5/31,Gi5/32
Gi5/33,Gi5/34,Gi5/35,Gi5/36,Gi5/37,Gi5/38
Gi5/39,Gi5/40,Gi5/41,Gi5/43,Gi5/45,Gi5/47
600 0100.5e6f.700c igmp Gi2/4,Gi2/6,Gi3/1,Gi3/2,Gi3/3,Gi3/4,Gi3/5
Gi3/8,Gi3/9,Gi3/10,Gi3/11,Gi3/12,Gi3/14,Gi3/16
Gi3/17,Gi3/18,Gi3/19,Gi3/20,Gi3/21,Gi3/22
Gi3/23,Gi3/24,Gi3/26,Gi3/27,Gi3/36,Gi3/39
Gi3/41,Gi3/42,Gi3/43,Gi3/44,Gi3/45,Gi5/1
Gi5/2,Gi5/3,Gi5/4,Gi5/5,Gi5/6,Gi5/7,Gi5/8
Gi5/9,Gi5/10,Gi5/11,Gi5/12,Gi5/13,Gi5/14
Gi5/16,Gi5/17,Gi5/19,Gi5/20,Gi5/21,Gi5/22
Gi5/23,Gi5/26,Gi5/28,Gi5/29,Gi5/31,Gi5/32
Gi5/33,Gi5/34,Gi5/35,Gi5/36,Gi5/37,Gi5/38
Gi5/39,Gi5/40,Gi5/41,Gi5/43,Gi5/45,Gi5/47
600 0100.5e7f.ff64 igmp Gi2/4,Gi2/6,Gi3/1,Gi3/2,Gi3/3,Gi3/4,Gi3/5
Gi3/8,Gi3/9,Gi3/10,Gi3/11,Gi3/12,Gi3/14,Gi3/16
Gi3/17,Gi3/18,Gi3/19,Gi3/20,Gi3/21,Gi3/22
Gi3/23,Gi3/24,Gi3/26,Gi3/27,Gi3/36,Gi3/39
Gi3/41,Gi3/42,Gi3/43,Gi3/44,Gi3/45,Gi5/1
Gi5/2,Gi5/3,Gi5/4,Gi5/5,Gi5/6,Gi5/7,Gi5/8
Gi5/9,Gi5/10,Gi5/11,Gi5/12,Gi5/13,Gi5/14
Gi5/16,Gi5/17,Gi5/19,Gi5/20,Gi5/21,Gi5/22
Gi5/23,Gi5/26,Gi5/28,Gi5/29,Gi5/31,Gi5/32
Gi5/33,Gi5/34,Gi5/35,Gi5/36,Gi5/37,Gi5/38
Gi5/39,Gi5/40,Gi5/41,Gi5/43,Gi5/45,Gi5/47
600 0100.5e7f.fffa igmp Gi2/4,Gi2/6,Gi3/1,Gi3/2,Gi3/3,Gi3/4,Gi3/5
Gi3/8,Gi3/9,Gi3/10,Gi3/11,Gi3/12,Gi3/14,Gi3/16
Gi3/17,Gi3/18,Gi3/19,Gi3/20,Gi3/21,Gi3/22
Gi3/23,Gi3/24,Gi3/26,Gi3/27,Gi3/36,Gi3/39
Gi3/41,Gi3/42,Gi3/43,Gi3/44,Gi3/45,Gi5/1
Gi5/2,Gi5/3,Gi5/4,Gi5/5,Gi5/6,Gi5/7,Gi5/8
Gi5/9,Gi5/10,Gi5/11,Gi5/12,Gi5/13,Gi5/14
Gi5/16,Gi5/17,Gi5/19,Gi5/20,Gi5/21,Gi5/22
Gi5/23,Gi5/26,Gi5/28,Gi5/29,Gi5/31,Gi5/32
Gi5/33,Gi5/34,Gi5/35,Gi5/36,Gi5/37,Gi5/38
Gi5/39,Gi5/40,Gi5/41,Gi5/43,Gi5/45,Gi5/47
600 0100.5e7f.fffd igmp Gi2/4,Gi2/6,Gi3/1,Gi3/2,Gi3/3,Gi3/4,Gi3/5
Gi3/8,Gi3/9,Gi3/10,Gi3/11,Gi3/12,Gi3/14,Gi3/16
Gi3/17,Gi3/18,Gi3/19,Gi3/20,Gi3/21,Gi3/22
Gi3/23,Gi3/24,Gi3/26,Gi3/27,Gi3/36,Gi3/39
Gi3/41,Gi3/42,Gi3/43,Gi3/44,Gi3/45,Gi5/1
Gi5/2,Gi5/3,Gi5/4,Gi5/5,Gi5/6,Gi5/7,Gi5/8
Gi5/9,Gi5/10,Gi5/11,Gi5/12,Gi5/13,Gi5/14
Gi5/16,Gi5/17,Gi5/19,Gi5/20,Gi5/21,Gi5/22
Gi5/23,Gi5/26,Gi5/28,Gi5/29,Gi5/31,Gi5/32
Gi5/33,Gi5/34,Gi5/35,Gi5/36,Gi5/37,Gi5/38
Gi5/39,Gi5/40,Gi5/41,Gi5/43,Gi5/45,Gi5/47
600 ffff.ffff.ffff system Gi2/4,Gi2/6,Gi3/1,Gi3/2,Gi3/3,Gi3/4,Gi3/5
Gi3/8,Gi3/9,Gi3/10,Gi3/11,Gi3/12,Gi3/14,Gi3/16
Gi3/17,Gi3/18,Gi3/19,Gi3/20,Gi3/21,Gi3/22
Gi3/23,Gi3/24,Gi3/26,Gi3/27,Gi3/36,Gi3/39
Gi3/41,Gi3/42,Gi3/43,Gi3/44,Gi3/45,Gi5/1
Gi5/2,Gi5/3,Gi5/4,Gi5/5,Gi5/6,Gi5/7,Gi5/8
Gi5/9,Gi5/10,Gi5/11,Gi5/12,Gi5/13,Gi5/14
Gi5/16,Gi5/17,Gi5/19,Gi5/20,Gi5/21,Gi5/22
Gi5/23,Gi5/26,Gi5/28,Gi5/29,Gi5/31,Gi5/32
Gi5/33,Gi5/34,Gi5/35,Gi5/36,Gi5/37,Gi5/38
Gi5/39,Gi5/40,Gi5/41,Gi5/43,Gi5/45,Gi5/47
Switch
01-23-2014 11:56 PM
The switch you captured the above commands on is the root bridge for the spanning tree, and the switch connected to interface gi3/11 is the device generating the Topology Change Notification (TCN) and then sending to the root bridge.
Can you login to the downstream switch that is connected to interface gi3/11? If so then run similar commands on that switch and see which port is causing the topology changes. It may be that you have a port that is continually changing state.
If it's an access switch, then changing the port type to an edge port i.e., enabling portfast, will stop the TCN being generated.
Regards
01-24-2014 12:58 AM
Thank you, I try.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide