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. And see here for current known issues.

New Member

L3Aging cause on a 6500 a load of 100.00% over hours

How is wrong to cause this output on two parallel Backbone Switch?

The entire network works still and no users calling, after a boot was all again well

sh proc cpu

CPU utilization for five seconds: 99.24%

one minute: 100.00%

five minutes: 100.00% . . .. . . . .

34 982835122 405584219 110000 86.64% 87.84% 87.96% -2 L3Aging

5 REPLIES
Cisco Employee

Re: L3Aging cause on a 6500 a load of 100.00% over hours

What software version are you running on the Supervisor and the MSFC. Take a look at the following bug

http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdr10379

New Member

Re: L3Aging cause on a 6500 a load of 100.00% over hours

Yes, we are currently using a relative old version and Netflow is active.

On the same customer we have already Cat OS 6.3(5) on SUP-1A and IOS 12.1(11) on MSFC running and until now no similar bad effects.

Question: is there something changed in the Software to eliminate the problem?

esw05300> (enable) sh ver

WS-C6506 Software, Version NmpSW: 5.5(3)

NMP S/W compiled on Sep 8 2000, 17:39:10

Cisco Employee

Re: L3Aging cause on a 6500 a load of 100.00% over hours

Yes, this bug has been resolved. If you want to stay in 5.5(x), 5.5(16) which is our latest GD should be good code to run. If you want to upgrade to 6.x, 6.3(9) should be good. Make sure you read the release notes for known issues

New Member

Re: L3Aging cause on a 6500 a load of 100.00% over hours

Hi, The Customer has Cat OS 6.3(5) and IOS 12.1.11 on the MSFC.

Is there the fix also implemented?

The Customer is very conservative because the system has first to work and has some bad experience with too new releases.

Cisco Employee

Re: L3Aging cause on a 6500 a load of 100.00% over hours

This bug was fixed in 6.1(1). However, 6.3(9) should be the way to go

110
Views
0
Helpful
5
Replies
CreatePlease login to create content