Since this isn't directly my upstream's problem I've edited them out of the log (actually, this could have come from more than one of my upstreams)
Nov 8 17:45:26 BGP RECV x.x.x.x+179 -> x.x.x.x+1161 Nov 8 17:45:26 BGP RECV message type 2 (Update) length 64 Nov 8 17:45:26 BGP RECV flags 0x40 code Origin(1): Incomplete Nov 8 17:45:26 BGP RECV flags 0x40 code ASPath(2): (0x02 0x07 0x0f 0x7f 0x02 0xbd 0x0d 0xa5 0x03 0x30 0x03 0x2f 0x03 0x2e) Nov 8 17:45:26 BGP RECV flags 0x40 code NextHop(3): x.x.x.x Nov 8 17:45:26 BGP RECV flags 0xc0 code Aggregator(7): 6218 206.53.128.254 Nov 8 17:45:26 BGP RECV 206.148.144/22 Nov 8 17:45:26 Nov 8 17:45:26 bnp_path_attr_eer: peer x.x.x.x (External AS yyyy) bad update send NOTIFY flag 0 type 0 err_subcode 11, data 0 Nov 8 17:45:26 NOTIFICATION sent to x.x.x.x (External AS yyyy): code 3 (Update Message Error) subcode 11 (AS path attribute problem) data Nov 8 17:45:26 Nov 8 17:45:26 BGP SEND x.x.x.x+1161 -> x.x.x.x+179 Nov 8 17:45:26 BGP SEND message type 3 (Notification) length 21 Nov 8 17:45:26 BGP SEND Notification code 3 (Update Message Error) subcode 11 (AS path attribute problem) Nov 8 17:45:26
(We saw the problem start around 1640 GMT tonight)
Problem at AS6218 perhaps ? (of course if this is the result of some random corruption that can't be relied on... )
Anyone else see anything ?
Another note on this, I wasn't able to stop the updates with a filter-list... perhaps because the AS path is problematic. I had to use a distribute list instead, listing each of the networks that 6218 is aggregating for... Not sure if this affects anyone else or not, but: access-list 21 deny 206.53.128.0 0.0.3.255 access-list 21 deny 206.53.128.0 0.0.0.255 access-list 21 deny 206.53.129.0 0.0.0.255 access-list 21 deny 206.53.130.0 0.0.0.255 access-list 21 deny 206.53.131.0 0.0.0.255 access-list 21 deny 206.148.144.0 0.0.3.255 access-list 21 deny 206.190.224.0 0.0.0.255 access-list 21 permit any davec
Problem at AS6218 perhaps ? (of course if this is the result of some random corruption that can't be relied on... )
Anyone else see anything ?
Dave Curado wrote:
Another note on this, I wasn't able to stop the updates with a filter-list... perhaps because the AS path is problematic. I had to use a distribute list instead, listing each of the networks that 6218 is aggregating for...
Yeah. Had that same problem when talking with one of my upstreams...
Not sure if this affects anyone else or not, but:
access-list 21 deny 206.53.128.0 0.0.3.255 access-list 21 deny 206.53.128.0 0.0.0.255 access-list 21 deny 206.53.129.0 0.0.0.255 access-list 21 deny 206.53.130.0 0.0.0.255 access-list 21 deny 206.53.131.0 0.0.0.255 access-list 21 deny 206.148.144.0 0.0.3.255 access-list 21 deny 206.190.224.0 0.0.0.255 access-list 21 permit any
You're missing 207.142/20 and 207.142.32/19 from that list. At least.. they were being aggregated by 6218 earlier tonight from my vantage point. Regards, Andrew -- Andrew Bangs, Network Engineering Manager, Demon Internet Ltd andrewb@demon.net http://www.demon.net/ http://www.demon.nl/ Network Engineering: +44 (0)181 371 1204 networks@demon.net
A friend showed me several routes with path "1239 11606 0 0 i". My guess is that these are causing problems too. --- Connected to sl-warwick-1.sprintlink.net. Escape character is '^]'. Bay Networks, Inc. and its Licensors. Copyright 1992,1993,1994,1995,1996,1997,1998. All rights reserved. --- It's a Bay -- I know that Bays will allow you to configure an AS prepend of "0" -- wonder if that's what's happening. /cah On Sun, Nov 08, 1998 at 04:06:56PM -0500, Dave Curado wrote: ==>> Since this isn't directly my upstream's problem I've edited them out of the ==>> log (actually, this could have come from more than one of my upstreams) ==>> ==>> Nov 8 17:45:26 BGP RECV x.x.x.x+179 -> x.x.x.x+1161 ==>> Nov 8 17:45:26 BGP RECV message type 2 (Update) length 64 ==>> Nov 8 17:45:26 BGP RECV flags 0x40 code Origin(1): Incomplete ==>> Nov 8 17:45:26 BGP RECV flags 0x40 code ASPath(2): (0x02 0x07 0x0f 0x7f 0x02 0xbd 0x0d 0xa5 0x03 0x30 0x03 0x2f 0x03 0x2e) ==>> Nov 8 17:45:26 BGP RECV flags 0x40 code NextHop(3): x.x.x.x ==>> Nov 8 17:45:26 BGP RECV flags 0xc0 code Aggregator(7): 6218 206.53.128.254 ==>> Nov 8 17:45:26 BGP RECV 206.148.144/22 ==>> Nov 8 17:45:26 ==>> Nov 8 17:45:26 bnp_path_attr_eer: peer x.x.x.x (External AS yyyy) bad update send NOTIFY flag 0 type 0 err_subcode 11, data 0 ==>> Nov 8 17:45:26 NOTIFICATION sent to x.x.x.x (External AS yyyy): code 3 (Update Message Error) subcode 11 (AS path attribute problem) data ==>> Nov 8 17:45:26 ==>> Nov 8 17:45:26 BGP SEND x.x.x.x+1161 -> x.x.x.x+179 ==>> Nov 8 17:45:26 BGP SEND message type 3 (Notification) length 21 ==>> Nov 8 17:45:26 BGP SEND Notification code 3 (Update Message Error) subcode 11 (AS path attribute problem) ==>> Nov 8 17:45:26 ==>> ==>> (We saw the problem start around 1640 GMT tonight) ==>> ==>> Problem at AS6218 perhaps ? (of course if this is the result of some ==>> random corruption that can't be relied on... ) ==>> ==>> Anyone else see anything ? ==> ==>Another note on this, I wasn't able to stop the updates ==>with a filter-list... perhaps because the AS path is ==>problematic. I had to use a distribute list instead, listing ==>each of the networks that 6218 is aggregating for... ==>Not sure if this affects anyone else or not, but: ==> ==>access-list 21 deny 206.53.128.0 0.0.3.255 ==>access-list 21 deny 206.53.128.0 0.0.0.255 ==>access-list 21 deny 206.53.129.0 0.0.0.255 ==>access-list 21 deny 206.53.130.0 0.0.0.255 ==>access-list 21 deny 206.53.131.0 0.0.0.255 ==>access-list 21 deny 206.148.144.0 0.0.3.255 ==>access-list 21 deny 206.190.224.0 0.0.0.255 ==>access-list 21 permit any ==> ==>davec ==>
After looking over the RFC, I see that 0 can be used for non-routed networks, so no one's implementation should be hanging up on it. (Regardless, the use of AS 0 as a prepend should be discouraged =) /cah On Sun, Nov 08, 1998 at 01:40:45PM -0800, Craig A. Huegen wrote: ==>A friend showed me several routes with path "1239 11606 0 0 i". ==> ==>My guess is that these are causing problems too. ==> ==>--- ==>Connected to sl-warwick-1.sprintlink.net. ==>Escape character is '^]'. ==> ==> ==>Bay Networks, Inc. and its Licensors. ==>Copyright 1992,1993,1994,1995,1996,1997,1998. All rights reserved. ==>--- ==> ==>It's a Bay -- I know that Bays will allow you to configure an AS prepend ==>of "0" -- wonder if that's what's happening. ==> ==>/cah ==> ==> ==>On Sun, Nov 08, 1998 at 04:06:56PM -0500, Dave Curado wrote: ==>==>> Since this isn't directly my upstream's problem I've edited them out of the ==>==>> log (actually, this could have come from more than one of my upstreams) ==>==>> ==>==>> Nov 8 17:45:26 BGP RECV x.x.x.x+179 -> x.x.x.x+1161 ==>==>> Nov 8 17:45:26 BGP RECV message type 2 (Update) length 64 ==>==>> Nov 8 17:45:26 BGP RECV flags 0x40 code Origin(1): Incomplete ==>==>> Nov 8 17:45:26 BGP RECV flags 0x40 code ASPath(2): (0x02 0x07 0x0f 0x7f 0x02 0xbd 0x0d 0xa5 0x03 0x30 0x03 0x2f 0x03 0x2e) ==>==>> Nov 8 17:45:26 BGP RECV flags 0x40 code NextHop(3): x.x.x.x ==>==>> Nov 8 17:45:26 BGP RECV flags 0xc0 code Aggregator(7): 6218 206.53.128.254 ==>==>> Nov 8 17:45:26 BGP RECV 206.148.144/22 ==>==>> Nov 8 17:45:26 ==>==>> Nov 8 17:45:26 bnp_path_attr_eer: peer x.x.x.x (External AS yyyy) bad update send NOTIFY flag 0 type 0 err_subcode 11, data 0 ==>==>> Nov 8 17:45:26 NOTIFICATION sent to x.x.x.x (External AS yyyy): code 3 (Update Message Error) subcode 11 (AS path attribute problem) data ==>==>> Nov 8 17:45:26 ==>==>> Nov 8 17:45:26 BGP SEND x.x.x.x+1161 -> x.x.x.x+179 ==>==>> Nov 8 17:45:26 BGP SEND message type 3 (Notification) length 21 ==>==>> Nov 8 17:45:26 BGP SEND Notification code 3 (Update Message Error) subcode 11 (AS path attribute problem) ==>==>> Nov 8 17:45:26 ==>==>> ==>==>> (We saw the problem start around 1640 GMT tonight) ==>==>> ==>==>> Problem at AS6218 perhaps ? (of course if this is the result of some ==>==>> random corruption that can't be relied on... ) ==>==>> ==>==>> Anyone else see anything ? ==>==> ==>==>Another note on this, I wasn't able to stop the updates ==>==>with a filter-list... perhaps because the AS path is ==>==>problematic. I had to use a distribute list instead, listing ==>==>each of the networks that 6218 is aggregating for... ==>==>Not sure if this affects anyone else or not, but: ==>==> ==>==>access-list 21 deny 206.53.128.0 0.0.3.255 ==>==>access-list 21 deny 206.53.128.0 0.0.0.255 ==>==>access-list 21 deny 206.53.129.0 0.0.0.255 ==>==>access-list 21 deny 206.53.130.0 0.0.0.255 ==>==>access-list 21 deny 206.53.131.0 0.0.0.255 ==>==>access-list 21 deny 206.148.144.0 0.0.3.255 ==>==>access-list 21 deny 206.190.224.0 0.0.0.255 ==>==>access-list 21 permit any ==>==> ==>==>davec ==>==>
Craig A. Huegen wrote:
After looking over the RFC, I see that 0 can be used for non-routed networks, so no one's implementation should be hanging up on it.
I agree. I'm not sure that that is what is happening, though.... see below.
(Regardless, the use of AS 0 as a prepend should be discouraged =)
Yup. However, I'm not seeing AS0 in the stuff I posted:
==>==>> Nov 8 17:45:26 BGP RECV flags 0x40 code ASPath(2): (0x02 0x07 0x0f 0x7f 0x02 0xbd 0x0d 0xa5 0x03 0x30 0x03 0x2f 0x03 0x2e)
John Scudder at IENG gave me the clue by decoding the above ASPath: 0x02 = AS_SEQUENCE 0x07 = 7 ASes in sequence 0x0f7f = 3967 0x02bd = 701 0x0da5 = 3493 0x0330 = 816 0x032f = 815 0x032e = 814 and I decided to take a closer look at the other's I'd logged: Nov 8 19:29:35 BGP RECV flags 0x40 code ASPath(2): (0x02 0x08 0x18 0xcb 0x0d 0xe9 0x02 0xbd 0x0d 0xa5 0x03 0x30 0x03 0x2f 0x03 0x2e) 0x02 AS_SEQUENCE 0x08 8 ASes in sequence 0x18cb 6347 0x0de9 3561 0x02bd 701 0x0da5 3493 0x0330 816 0x032f 815 0x032e 814 Nov 8 16:56:32 BGP RECV flags 0x40 code ASPath(2): (0x02 0x03 0x18 0xcb 0x0d 0xe9) 0x02 AS_SEQUENCE 0x03 3 ASes in sequence 0x18cb 6347 0x0de9 3561 In each case the ASPath attribute says it consists of an AS_SEQUENCE of N ASes, but the data only shows N-1 ASes. Could it be that your router somehow 'pads' the tail of the AS_PATH with enough zeros until it makes the right length ? I think it's hiding the truth from you. When I was talking through the problem with one of my upstreams they mentioned 'AS0' at the end of the AS_PATH. It seems that their routers were happy to pad the AS to the right length internally, but the Update that was sent to my router was definitely malformed (and not padded with AS0) which caused a (correct IMHO) NOTIFY message to be sent back. Did anyone else capture any problematic Update messages yesterday ? Do they show the same problem ? I'm beginning to believe that this is a bug in at least the Cisco BGP implementation (since that's what my upstreams use to peer with me). (I haven't seen any mention of how the bad routes got into the world in the first place. Anyone know ?) Regards, Andrew -- Andrew Bangs, Network Engineering Manager, Demon Internet Ltd andrewb@demon.net http://www.demon.net/ http://www.demon.nl/ Network Engineering: +44 (0)181 371 1204 networks@demon.net
core1.brd>sho ip bgp reg _0_ returns about 30 routes, like: Network Next Hop Metric LocPrf Weight Path *d 204.255.24.0 207.106.96.5 0 8001 8001 4969 1239 11606 0 0 i *d 204.255.25.0 207.106.96.5 0 8001 8001 4969 1239 11606 0 0 i [root@when /]# whois -h rs.arin.net 11606 Warwick Online (ASN-WOL-AS) 47 Main Street Warwick, New York 10990 USA Autonomous System Name: WOL-AS Autonomous System Number: 11606 This is a independant telephone company in northern nj / sourthern NY state. core1.brd>sho ip bgp 204.255.24.0 BGP routing table entry for 204.255.24.0/24, version 4903495 Paths: (4 available, best #3, advertised over IBGP, EBGP) 8001 8001 4969 1239 11606 0 0, (suppressed due to dampening) 207.106.96.5 from 207.106.96.5 Origin IGP, localpref 100, valid, external Community: 0:666 1:58376 4969:609 8001:666 8001:4969 Dampinfo: penalty 7270, flapped 22 times in 00:38:24, reuse in 00:49:10 6347 701 11606 209.83.160.97 from 209.83.160.97 (209.83.159.2) Origin IGP, localpref 100, valid, external, best Community: 8001:666 8001:6347 On Sun, 8 Nov 1998, Craig A. Huegen wrote:
A friend showed me several routes with path "1239 11606 0 0 i".
My guess is that these are causing problems too.
--- Connected to sl-warwick-1.sprintlink.net. Escape character is '^]'.
Bay Networks, Inc. and its Licensors. Copyright 1992,1993,1994,1995,1996,1997,1998. All rights reserved. ---
It's a Bay -- I know that Bays will allow you to configure an AS prepend of "0" -- wonder if that's what's happening.
/cah
On Sun, Nov 08, 1998 at 04:06:56PM -0500, Dave Curado wrote: ==>> Since this isn't directly my upstream's problem I've edited them out of the ==>> log (actually, this could have come from more than one of my upstreams) ==>> ==>> Nov 8 17:45:26 BGP RECV x.x.x.x+179 -> x.x.x.x+1161 ==>> Nov 8 17:45:26 BGP RECV message type 2 (Update) length 64 ==>> Nov 8 17:45:26 BGP RECV flags 0x40 code Origin(1): Incomplete ==>> Nov 8 17:45:26 BGP RECV flags 0x40 code ASPath(2): (0x02 0x07 0x0f 0x7f 0x02 0xbd 0x0d 0xa5 0x03 0x30 0x03 0x2f 0x03 0x2e) ==>> Nov 8 17:45:26 BGP RECV flags 0x40 code NextHop(3): x.x.x.x ==>> Nov 8 17:45:26 BGP RECV flags 0xc0 code Aggregator(7): 6218 206.53.128.254 ==>> Nov 8 17:45:26 BGP RECV 206.148.144/22 ==>> Nov 8 17:45:26 ==>> Nov 8 17:45:26 bnp_path_attr_eer: peer x.x.x.x (External AS yyyy) bad update send NOTIFY flag 0 type 0 err_subcode 11, data 0 ==>> Nov 8 17:45:26 NOTIFICATION sent to x.x.x.x (External AS yyyy): code 3 (Update Message Error) subcode 11 (AS path attribute problem) data ==>> Nov 8 17:45:26 ==>> Nov 8 17:45:26 BGP SEND x.x.x.x+1161 -> x.x.x.x+179 ==>> Nov 8 17:45:26 BGP SEND message type 3 (Notification) length 21 ==>> Nov 8 17:45:26 BGP SEND Notification code 3 (Update Message Error) subcode 11 (AS path attribute problem) ==>> Nov 8 17:45:26 ==>> ==>> (We saw the problem start around 1640 GMT tonight) ==>> ==>> Problem at AS6218 perhaps ? (of course if this is the result of some ==>> random corruption that can't be relied on... ) ==>> ==>> Anyone else see anything ? ==> ==>Another note on this, I wasn't able to stop the updates ==>with a filter-list... perhaps because the AS path is ==>problematic. I had to use a distribute list instead, listing ==>each of the networks that 6218 is aggregating for... ==>Not sure if this affects anyone else or not, but: ==> ==>access-list 21 deny 206.53.128.0 0.0.3.255 ==>access-list 21 deny 206.53.128.0 0.0.0.255 ==>access-list 21 deny 206.53.129.0 0.0.0.255 ==>access-list 21 deny 206.53.130.0 0.0.0.255 ==>access-list 21 deny 206.53.131.0 0.0.0.255 ==>access-list 21 deny 206.148.144.0 0.0.3.255 ==>access-list 21 deny 206.190.224.0 0.0.0.255 ==>access-list 21 permit any ==> ==>davec ==>
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Atheism is a non-prophet organization. I route, therefore I am. Alex Rubenstein, alex@nac.net, KC2BUO, ISP/C Charter Member Father of the Network and Head Bottle-Washer Net Access Corporation, 9 Mt. Pleasant Tpk., Denville, NJ 07834 Don't choose a spineless ISP; we have more backbone! http://www.nac.net -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Still seeing them... Avi
core1.brd>sho ip bgp reg _0_
returns about 30 routes, like:
Network Next Hop Metric LocPrf Weight Path *d 204.255.24.0 207.106.96.5 0 8001 8001 4969 1239 11606 0 0 i *d 204.255.25.0 207.106.96.5 0 8001 8001 4969 1239 11606 0 0 i
[root@when /]# whois -h rs.arin.net 11606 Warwick Online (ASN-WOL-AS) 47 Main Street Warwick, New York 10990 USA
Autonomous System Name: WOL-AS Autonomous System Number: 11606
This is a independant telephone company in northern nj / sourthern NY state.
core1.brd>sho ip bgp 204.255.24.0 BGP routing table entry for 204.255.24.0/24, version 4903495 Paths: (4 available, best #3, advertised over IBGP, EBGP) 8001 8001 4969 1239 11606 0 0, (suppressed due to dampening) 207.106.96.5 from 207.106.96.5 Origin IGP, localpref 100, valid, external Community: 0:666 1:58376 4969:609 8001:666 8001:4969 Dampinfo: penalty 7270, flapped 22 times in 00:38:24, reuse in 00:49:10 6347 701 11606 209.83.160.97 from 209.83.160.97 (209.83.159.2) Origin IGP, localpref 100, valid, external, best Community: 8001:666 8001:6347
On Sun, 8 Nov 1998, Craig A. Huegen wrote:
A friend showed me several routes with path "1239 11606 0 0 i".
My guess is that these are causing problems too.
--- Connected to sl-warwick-1.sprintlink.net. Escape character is '^]'.
Bay Networks, Inc. and its Licensors. Copyright 1992,1993,1994,1995,1996,1997,1998. All rights reserved. ---
It's a Bay -- I know that Bays will allow you to configure an AS prepend of "0" -- wonder if that's what's happening.
/cah
On Sun, Nov 08, 1998 at 04:06:56PM -0500, Dave Curado wrote: ==>> Since this isn't directly my upstream's problem I've edited them out of the ==>> log (actually, this could have come from more than one of my upstreams) ==>> ==>> Nov 8 17:45:26 BGP RECV x.x.x.x+179 -> x.x.x.x+1161 ==>> Nov 8 17:45:26 BGP RECV message type 2 (Update) length 64 ==>> Nov 8 17:45:26 BGP RECV flags 0x40 code Origin(1): Incomplete ==>> Nov 8 17:45:26 BGP RECV flags 0x40 code ASPath(2): (0x02 0x07 0x0f 0x7f 0x02 0xbd 0x0d 0xa5 0x03 0x30 0x03 0x2f 0x03 0x2e) ==>> Nov 8 17:45:26 BGP RECV flags 0x40 code NextHop(3): x.x.x.x ==>> Nov 8 17:45:26 BGP RECV flags 0xc0 code Aggregator(7): 6218 206.53.128.254 ==>> Nov 8 17:45:26 BGP RECV 206.148.144/22 ==>> Nov 8 17:45:26 ==>> Nov 8 17:45:26 bnp_path_attr_eer: peer x.x.x.x (External AS yyyy) bad update send NOTIFY flag 0 type 0 err_subcode 11, data 0 ==>> Nov 8 17:45:26 NOTIFICATION sent to x.x.x.x (External AS yyyy): code 3 (Update Message Error) subcode 11 (AS path attribute problem) data ==>> Nov 8 17:45:26 ==>> Nov 8 17:45:26 BGP SEND x.x.x.x+1161 -> x.x.x.x+179 ==>> Nov 8 17:45:26 BGP SEND message type 3 (Notification) length 21 ==>> Nov 8 17:45:26 BGP SEND Notification code 3 (Update Message Error) subcode 11 (AS path attribute problem) ==>> Nov 8 17:45:26 ==>> ==>> (We saw the problem start around 1640 GMT tonight) ==>> ==>> Problem at AS6218 perhaps ? (of course if this is the result of some ==>> random corruption that can't be relied on... ) ==>> ==>> Anyone else see anything ? ==> ==>Another note on this, I wasn't able to stop the updates ==>with a filter-list... perhaps because the AS path is ==>problematic. I had to use a distribute list instead, listing ==>each of the networks that 6218 is aggregating for... ==>Not sure if this affects anyone else or not, but: ==> ==>access-list 21 deny 206.53.128.0 0.0.3.255 ==>access-list 21 deny 206.53.128.0 0.0.0.255 ==>access-list 21 deny 206.53.129.0 0.0.0.255 ==>access-list 21 deny 206.53.130.0 0.0.0.255 ==>access-list 21 deny 206.53.131.0 0.0.0.255 ==>access-list 21 deny 206.148.144.0 0.0.3.255 ==>access-list 21 deny 206.190.224.0 0.0.0.255 ==>access-list 21 permit any ==> ==>davec ==>
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Atheism is a non-prophet organization. I route, therefore I am. Alex Rubenstein, alex@nac.net, KC2BUO, ISP/C Charter Member Father of the Network and Head Bottle-Washer Net Access Corporation, 9 Mt. Pleasant Tpk., Denville, NJ 07834 Don't choose a spineless ISP; we have more backbone! http://www.nac.net -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
And now, they aren't dampened. core1.brd>sho ip bgp reg _0_ BGP table version is 5010318, local router ID is 209.123.12.23 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path * 204.255.24.0 207.106.96.5 0 8001 8001 4969 1239 11606 0 0 i * 204.255.25.0 207.106.96.5 0 8001 8001 4969 1239 11606 0 0 i * 204.255.26.0 207.106.96.5 0 8001 8001 4969 1239 11606 0 0 i I guess the bigere question is why hasn't sprint filtered or wariwck fixed this? On Mon, 9 Nov 1998, Avi Freedman wrote:
Still seeing them...
Avi
core1.brd>sho ip bgp reg _0_
returns about 30 routes, like:
Network Next Hop Metric LocPrf Weight Path *d 204.255.24.0 207.106.96.5 0 8001 8001 4969 1239 11606 0 0 i *d 204.255.25.0 207.106.96.5 0 8001 8001 4969 1239 11606 0 0 i
[root@when /]# whois -h rs.arin.net 11606 Warwick Online (ASN-WOL-AS) 47 Main Street Warwick, New York 10990 USA
Autonomous System Name: WOL-AS Autonomous System Number: 11606
This is a independant telephone company in northern nj / sourthern NY state.
core1.brd>sho ip bgp 204.255.24.0 BGP routing table entry for 204.255.24.0/24, version 4903495 Paths: (4 available, best #3, advertised over IBGP, EBGP) 8001 8001 4969 1239 11606 0 0, (suppressed due to dampening) 207.106.96.5 from 207.106.96.5 Origin IGP, localpref 100, valid, external Community: 0:666 1:58376 4969:609 8001:666 8001:4969 Dampinfo: penalty 7270, flapped 22 times in 00:38:24, reuse in 00:49:10 6347 701 11606 209.83.160.97 from 209.83.160.97 (209.83.159.2) Origin IGP, localpref 100, valid, external, best Community: 8001:666 8001:6347
On Sun, 8 Nov 1998, Craig A. Huegen wrote:
A friend showed me several routes with path "1239 11606 0 0 i".
My guess is that these are causing problems too.
--- Connected to sl-warwick-1.sprintlink.net. Escape character is '^]'.
Bay Networks, Inc. and its Licensors. Copyright 1992,1993,1994,1995,1996,1997,1998. All rights reserved. ---
It's a Bay -- I know that Bays will allow you to configure an AS prepend of "0" -- wonder if that's what's happening.
/cah
On Sun, Nov 08, 1998 at 04:06:56PM -0500, Dave Curado wrote: ==>> Since this isn't directly my upstream's problem I've edited them out of the ==>> log (actually, this could have come from more than one of my upstreams) ==>> ==>> Nov 8 17:45:26 BGP RECV x.x.x.x+179 -> x.x.x.x+1161 ==>> Nov 8 17:45:26 BGP RECV message type 2 (Update) length 64 ==>> Nov 8 17:45:26 BGP RECV flags 0x40 code Origin(1): Incomplete ==>> Nov 8 17:45:26 BGP RECV flags 0x40 code ASPath(2): (0x02 0x07 0x0f 0x7f 0x02 0xbd 0x0d 0xa5 0x03 0x30 0x03 0x2f 0x03 0x2e) ==>> Nov 8 17:45:26 BGP RECV flags 0x40 code NextHop(3): x.x.x.x ==>> Nov 8 17:45:26 BGP RECV flags 0xc0 code Aggregator(7): 6218 206.53.128.254 ==>> Nov 8 17:45:26 BGP RECV 206.148.144/22 ==>> Nov 8 17:45:26 ==>> Nov 8 17:45:26 bnp_path_attr_eer: peer x.x.x.x (External AS yyyy) bad update send NOTIFY flag 0 type 0 err_subcode 11, data 0 ==>> Nov 8 17:45:26 NOTIFICATION sent to x.x.x.x (External AS yyyy): code 3 (Update Message Error) subcode 11 (AS path attribute problem) data ==>> Nov 8 17:45:26 ==>> Nov 8 17:45:26 BGP SEND x.x.x.x+1161 -> x.x.x.x+179 ==>> Nov 8 17:45:26 BGP SEND message type 3 (Notification) length 21 ==>> Nov 8 17:45:26 BGP SEND Notification code 3 (Update Message Error) subcode 11 (AS path attribute problem) ==>> Nov 8 17:45:26 ==>> ==>> (We saw the problem start around 1640 GMT tonight) ==>> ==>> Problem at AS6218 perhaps ? (of course if this is the result of some ==>> random corruption that can't be relied on... ) ==>> ==>> Anyone else see anything ? ==> ==>Another note on this, I wasn't able to stop the updates ==>with a filter-list... perhaps because the AS path is ==>problematic. I had to use a distribute list instead, listing ==>each of the networks that 6218 is aggregating for... ==>Not sure if this affects anyone else or not, but: ==> ==>access-list 21 deny 206.53.128.0 0.0.3.255 ==>access-list 21 deny 206.53.128.0 0.0.0.255 ==>access-list 21 deny 206.53.129.0 0.0.0.255 ==>access-list 21 deny 206.53.130.0 0.0.0.255 ==>access-list 21 deny 206.53.131.0 0.0.0.255 ==>access-list 21 deny 206.148.144.0 0.0.3.255 ==>access-list 21 deny 206.190.224.0 0.0.0.255 ==>access-list 21 permit any ==> ==>davec ==>
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Atheism is a non-prophet organization. I route, therefore I am. Alex Rubenstein, alex@nac.net, KC2BUO, ISP/C Charter Member Father of the Network and Head Bottle-Washer Net Access Corporation, 9 Mt. Pleasant Tpk., Denville, NJ 07834 Don't choose a spineless ISP; we have more backbone! http://www.nac.net -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Atheism is a non-prophet organization. I route, therefore I am. Alex Rubenstein, alex@nac.net, KC2BUO, ISP/C Charter Member Father of the Network and Head Bottle-Washer Net Access Corporation, 9 Mt. Pleasant Tpk., Denville, NJ 07834 Don't choose a spineless ISP; we have more backbone! http://www.nac.net -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
participants (5)
-
alex＠nac.net -
Andrew Bangs -
Avi Freedman -
Craig A. Huegen -
Dave Curado