On Tue, Mar 17, 2009 at 08:46:06PM -0700, Andy Vance wrote:
Richard,
Appears these are the releases that it has been fixed in.
8-1-4p0-4, 8-2-4p0-7, 9-0-2p0-1, 9-1-2p0-1, 9-2-1p0-1, 9-3-0p0-1, 10-0-0
Now that things have calmed down, I've got a few more updates on this
incident and some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
1) Routers shouldn't be leaking confederation information
into AS4_PATH.
This is the issue that Juniper covers under PSN-2009-01-200,
and all code built after 2009-01-26 appears to be fixed in
this regard. This is the same issue that was
Does anyone know what Junos revisions for the M series will fix this?
We ended up just filtering out the offending announcement but would
prefer to update and avoid future ones. Richard's list looks like all E
series releases.
Bryan Socha
___
Who else just noticed Juniper bgp sessions all over the place flapping
with:
code 3 (Update Message Error) subcode 1 (invalid attribute list)
code 3 (Update Message Error) subcode 11 (AS path attribute problem)
Received BAD update for family inet-unicast(1), prefix 193.5.68.0/23
etc?
--
4 matches
Mail list logo
