BGP offloading (fixing legacy router BGP scalability issues)

Thu Apr 2 08:06:47 UTC 2015

163data is announced as Chinanet, a China Telecom brand.

Dropping 4134 (http://bgp.he.net/AS4134) globally will get my customers 
up at my doors with pitchforks fairly fast, I dunno about yours....

Simply too big to do anything that drastic against.

On 4/2/2015 午後 05:04, Colin Johnston wrote:
>> On 2 Apr 2015, at 08:40, Paul S. <contact at winterei.se> wrote:
>>
>> Do you have data on '100% of the traffic' being bad?
>>
> as a example anything in 163data.com.cn is bad
>
> Colin
>
>> I happen to have a large Chinese clientbase, and this is not the case on my network.
>>
>> On 4/2/2015 午後 04:35, Colin Johnston wrote:
>>> or ignore/block russia and north korea and china network blocks
>>> takes away 5% of network ranges for memory headroom, especially the large number of smaller china blocks.
>>> Some may say this is harsh but is the network contacts refuse to co-operate with abuse and 100% of the traffic is bad then why not
>>>
>>> Colin
>>>
>>>
>>>> On 2 Apr 2015, at 07:59, Mark Tinka <mark.tinka at seacom.mu> wrote:
>>>>
>>>>
>>>>
>>>> On 1/Apr/15 19:01, Frederik Kriewitz wrote:
>>>>> We're wondering if anyone has experience with such a setup?
>>>> Cisco have a feature called BGP-SD (BGP Selective Download).
>>>>
>>>> With BGP-SD, you can hold millions of entries in RAM, but decide what
>>>> gets downloaded into the FIB. By doing this, you can still export a full
>>>> BGP table to customers directly connected to your 6500, and only have a
>>>> 0/0 + ::/0 (and some more customer routes) in the FIB to do forwarding
>>>> to a bigger box.
>>>>
>>>> BGP-SD started shipping in IOS XE, but I now understand that the feature
>>>> is on anything running IOS 15.
>>>>
>>>> This would be my recommendation.
>>>>
>>>> Mark.