Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

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

cisco 3550 switch CPU Load 100 %

i have a cisco 3550 with 8 gig port and 2 gig ethernet.

on 2 gig there are two vlans saperate and on the ethernet gig there is a third vlan which is connected to internal company network.both the fiber gig are connected to other 6509.

ple problem is that

from internal network which i ping to the fiber vlan network it works fine but when i ping to the ethernet port which is the third vlan it is not replying.

when i check the utilization it is 100%,

i chek the process

PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process

3 28 108 259 0.08% 0.03% 0.01% 1 Virtual Exec

9 5532 10269 538 0.40% 0.65% 0.56% 0 ARP Input

24 3888 2112 1840 0.40% 0.33% 0.32% 0 Vegas Statistics

33 1556 3411 456 94.08% 90.12% 90.12% 0 VUR_MGR bg proce

35 6428 9933 647 0.40% 0.57% 0.52% 0 IP Input

75 33560 1853 18111 30.96% 35.05% 30.70% 0 CEF process

Please reply me with a suggestion

i am restarting the switch everytime.

  • Other Network Infrastructure Subjects
1 REPLY
VIP Purple

Re: cisco 3550 switch CPU Load 100 %

Hello,

you could be suffering from bug CSCdx31480:

High CPU Utilization VUR_MGR (3550)

Problem:

CPU utilization is stuck near 100% and the VUR_MGR bg process is

responsible for almost all of that CPU time. Any routing protocols

being run have converged and few if any routes are being added or

deleted.

This problem results from a relatively uncommon race condition involving

two related routes being added in close succession and the less specific

of the two routes being deleted before the add processing has completed.

Workaround:

Issue the clear ip route * command in exec mode

to clear the condition. This will not prevent the condition from

recurring, however.

A fix is planned for the next release.

Affected versions are:

12.1(12c)EA1

12.1(12c)EA1a

12.1(13)AY

12.1(13)EA1a

12.1(13)EA1b

12.1(13)EA1c

12.1(13)EA1

12.1(14)EA1

12.1(14)EA1a

12.1(14)EA1b

12.1(8)EA1

12.1(8)EA1b

12.1(8)EA1c

First fixed in version:

12.1(9)EA1

12.1(11)EA01

HTH,

Georg

145
Views
0
Helpful
1
Replies