Switch 3500-High utilization

[vipinrajrc]

Hi

I have a switch cisco3500, which is connected to another switch2950. 2950is a new one, and 3500 is an old switch. ASA and most of the interal hosts are connectd to the 2950 switch, it shows a 4% CPU utilization. A trunk line from 2950 to 3500 is connected. 3500 has no other function, just connected to one or two hosts. but it shows about 37%CPU utilization. could anyone tell me what is the reason. How can i reduce this usage to below 5%. How can i optimize the performance..  "show process" output is given below.. please reply techies.......... its an urgent... Please reply ASAP...

Thanks&Regards

Vipin Raj

Load Meter
Virtual Exec
Check heaps
Chunk Manager
Pool Manager
Timers
Entity MIB API
ARP Input
RAM Access (dm 0
Critical Bkgnd
Net Background
Logger
TTY Background
Per-Second Jobs
Net Input
Compute load avg
Per-minute Jobs
LED Control Proc
Frank Aging
Port Status Proc
VM Prune Events
IP NAT Ager
Process
GDS Frame Ager
RAM Access (gi0/
RAM Access (gi0/
Broadcast Storm
Port Group Chang
Address Learning
RAM Access (dm 1
RAM Access (dm 2
Enet Aging
IP Input
Address Deletion
Address Sorting
CDP Protocol
UDLD
CGMP Forwarding
Switch CGMP Prot
VLAN Manager
STP STACK TOPOLO
STP FAST TRANSIT
TCP Timer
TCP Protocols
Socket Timers
HTTP Timer
Process
Cluster L2
Cluster RARP
Cluster Base
Spanning Tree
STP Hello
STP Queue Handle
Malibu STP Adjus
Time Range Proce
Router Autoconf
SNMP ConfCopyPro
Bridge MIB traps
Inline Power
Runtime diags

[Shashank Singh]

Hi Vipin,

Please attach following outputs from the 3500 switch to this thread:

show proc cpu | ex 0.0

show proc cpu hist

show span det  | i from|topo

show controllers cpu-interface

show version

sh int  | i line|rate|drops

Cheers,

Shashank

P.S. Please rate helpful posts.

[vipinrajrc]

Hi,

Please see the below details

NOCME_SW2#sh processes cpu | ex 0.0
CPU utilization for five seconds: 37%/4%; one minute: 38%; five minutes: 38%
PID  Runtime(ms)  Invoked  uSecs    5Sec   1Min   5Min TTY Process
  14     2690085   4905990    548   0.16%  0.12%  0.12%   0 Per-Second Jobs
  18    14018726 113227754    123   0.81%  0.72%  0.63%   0 LED Control Proc
  20   161350680 166475853    969   5.14%  5.84%  5.76%   0 Port Status Proc
  30    22662550  36994662    612   0.94%  0.89%  0.89%   0 Broadcast Storm
  36    21790973   5771776   3775   0.69%  0.70%  0.72%   0 Enet Aging

NOCME_SW2#sh spanning-tree | i from|topo
  Times:  hold 1, topology change 35, notification 2
  Timers: hello 0, topology change 0, notification 0

NOCME_SW2#sh controllers | include cpu
           sc_cpu_buffer = 0x576680, sc_regs = 0x576684
    0x710004AC:cpu_buffer_control = 0x0
    0x71000508:pci_cpu_buffer_base = 0x70000000
    0x7100050C:pci_cpu_notify_ram_base = 0x71010000
    0x71000570:cpu_buffer_diagnostics[0] = 0x0
    0x71000574:cpu_buffer_diagnostics[1] = 0x0
    0x71000578:cpu_buffer_diagnostics[2] = 0x0
    0x7100057C:cpu_buffer_diagnostics[3] = 0x0

NOCME_SW2#sh ver
Cisco Internetwork Operating System Software
IOS (tm) C3500XL Software (C3500XL-C3H2S-M), Version 12.0(5.3)WC(1), MAINTENANC
INTERIM SOFTWARE
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Mon 30-Apr-01 07:51 by devgoyal
Image text-base: 0x00003000, data-base: 0x003331F4

ROM: Bootstrap program is C3500XL boot loader

NOCME_SW2 uptime is 2 weeks, 2 days, 8 hours, 58 minutes
System returned to ROM by power-on
System image file is "flash:c3500XL-c3h2s-mz-120-5.3.WC.1.bin"
cisco WS-C3524-PWR-XL (PowerPC403) processor (revision 0x01) with 8192K/1024K b
tes of memory.
Processor board ID FAA0604Y0D4, with hardware revision 0x00
Last reset from power-on

Processor is running Enterprise Edition Software
Cluster command switch capable
Cluster member switch capable
24 FastEthernet/IEEE 802.3 interface(s)
2 Gigabit Ethernet/IEEE 802.3 interface(s)

32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 00:08:21:D9:5D:80
Motherboard assembly number: 73-4033-07
Power supply part number: 34-0968-01
Motherboard serial number: FAA0550JO8D
Power supply serial number: LIT06022221
Model revision number: A0
Motherboard revision number: B0
Model number: WS-C3524-PWR-XL-EN
System serial number: FAA0604Y0D4
Configuration register is 0xF

NOCME_SW2#sh int | i line|rate|drops
VLAN1 is up, line protocol is up
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 2000 bits/sec, 5 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
VLAN2 is administratively down, line protocol is down
FastEthernet0/1 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
FastEthernet0/2 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
FastEthernet0/3 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
FastEthernet0/4 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops

   5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
astEthernet0/5 is down, line protocol is down
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
astEthernet0/6 is down, line protocol is down
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
astEthernet0/7 is up, line protocol is up
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 3000 bits/sec, 4 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
astEthernet0/8 is down, line protocol is down
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
astEthernet0/9 is down, line protocol is down
Queueing strategy: fifo

   Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
FastEthernet0/10 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
FastEthernet0/11 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
FastEthernet0/12 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
FastEthernet0/13 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
FastEthernet0/14 is down, line protocol is down

   Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
FastEthernet0/15 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
FastEthernet0/16 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
FastEthernet0/17 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
FastEthernet0/18 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec

FastEthernet0/19 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
FastEthernet0/20 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
FastEthernet0/21 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
FastEthernet0/22 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
FastEthernet0/23 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec

   5 minute output rate 0 bits/sec, 0 packets/sec
FastEthernet0/24 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
GigabitEthernet0/1 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
GigabitEthernet0/2 is down, line protocol is down
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec

show controllers cpu-interface &

show proc cpu hist

didnt work.....

Hope this will help you to resolve my issue....

Thanks&Regards

Vipin Raj

[glen.grant · Accepted solution]

   Thats normal for the old 3500 series, they will register over 30% with nothing attached to them , same with the old 2924's .  Don't worry about it.  The cpu has very  little to do with switching packets which is mostly handled in hardware.   Right out of a high cpu doc for 3500xl's .

"Therefore, it is normal for a 2900XL or 3500XL  switch to indicate a CPU utilization value of 30 percent to 50 percent,  even under minimal load."

[vipinrajrc]

glen.grant wrote:
   Thats normal for the old 3500 series, they will register over 30% with nothing attached to them , same with the old 2924's .  Don't worry about it.  The cpu has very  little to do with switching packets which is mostly handled in hardware.   Right out of a high cpu doc for 3500xl's .
"Therefore, it is normal for a 2900XL or 3500XL  switch to indicate a CPU utilization value of 30 percent to 50 percent,  even under minimal load."

Hi Glen,

Thanks for your kind reply.... Thank you very very much.....

Regards,

Vipin Raj

[Patrick McHenry · Accepted solution]

In our enviroment, the 3500 hundreds are sometimes running at 80 and 90 percent. When they get that high we usually can't even log into them but, they seem to forward traffic.After a reboot they are normally fine and we can log into them. Can't wait to get rid of them though.

Pat.

[vipinrajrc]

Hi Pat,

I think that may be the problem.. there is no other reason...

Thanks for your reply......

Cheers  

Vipin Raj