Dean,
Probably good to move this over to cisco-...@puck.nether.net and answer
the questions below over there.
What code is it?
Looks like a bug where the IDB counters are not being bumped on the SVI.
Is it L3 switching traffic through the SVI or L2 (intra vlan traffic
between L2 ports)?
Sherwin,
Let's move this specific crash/code question over to
cisco-...@puck.nether.net.
Try the 12.2(33)XNF1 release.
If you would like to try and find the matching bug for what you are
seeing before you upgrade email me offline with the crashinfo file and
the full logs and I'll get
On Mon, May 11, 2009 at 10:37:25AM -0400, Andrey Gordon wrote:
Hey folks, I'm sure to you it's peanuts, but I'm a bit puzzled (most likely
because of the lack of knowledge, I bet).
I'm buying an IP backbone from VNZ (presumably MPLS). I get a MLPPP hand off
on all sites, so I don't do the
Stuppi for pointing it out.
Rodney
On Thu, Feb 19, 2009 at 03:15:02PM -0500, Rodney Dunn wrote:
We are working on a document for Cisco.com but in the interim
here is the bug that will fix the issue of a Cisco IOS device
sending an incorrectly formatted BGP update when as a result
longer than 255 per Section 5.1.2 of RFC4271
Thanks to those that worked offline with us to verify the field results
reported.
Rodney
On Tue, Feb 17, 2009 at 05:27:01PM -0500, Rodney Dunn wrote:
If you want to take this offline send it unicast or we could
move it to cisco-nsp.
What
Ivan,
It is confusing but from what I have tested you have it correct.
The confusing part comes from multiple issues.
a) The documentation about the default maxas limit being 75 appears to be
incorrect. I'll get that fixed.
b) Prior to CSCee30718 there was a hard limit of 255. After that
, German Martinez wrote:
On Tue Feb 17, 2009, Rodney Dunn wrote:
Hello Rodney,
It will be great if you can share with us your findings. It seems
like we are hitting different bugs in different platforms.
Thanks
German
Ivan,
It is confusing but from what I have tested you have
7 matches
Mail list logo
