[c-nsp] 6500 troubles. What caused these packets to be punted? Isthat even what went wrong?

[Jim Devane]

James,

I learned the TCAM lesson the hard way on other boxes! No, this box only
holds about 150 routes or so. The BGP is really just there for them to
pass me routes instead of using OSPF. 
The routing is pretty straight forward so I looped for a recursive
lookup or route loop that might have caused a problem or CPU to go up
and didn't find anything that would have caused a problem. 
Although, I think if it were a route problem the CPU would have risen to
much higher than the 25% or so that it did.

Thank you for responding. I really do appreciate it.

Thanks,
Jim
 

-----Original Message-----
From: James Jun [mailto:james at towardex.com] 
Sent: Thursday, November 09, 2006 12:26 PM
To: Jim Devane PP; cisco-nsp at puck.nether.net
Subject: RE: [c-nsp] 6500 troubles. What caused these packets to be
punted? Isthat even what went wrong?

>     I have a 6509, SUP 2A, PFC2, MSFC2, running 12.1.22 and a few 
> 6408A and
> 6348 modules.
> 
> I turned up a customer on a gig port on a 6408.
> The only config on the port was a description and ip addr.
> Running BGP to the customer.

Are you maintaining full internet routing table in your box?  Note that
if you are out of FIB TCAM space, resort to software switching occurs.

james


The information in this e-mail and in any attachments is confidential and intended solely for the attention and use of the named addressee(s). This information may be subject to legal, professional, or other privilege, or may otherwise be protected by work product, immunity or other legal rules. It must not be disclosed to any person without the sender's authority. If you are not the intended recipient, or are not authorized to receive it for the intended recipient, you are not authorized to, and must not, disclose, copy, distribute, or retain this message or any part of it.

Thank you very much.

Switch Communications Group LLC