[c-nsp] Long list of route-maps

Andy B. globichen at gmail.com
Thu Mar 11 12:59:13 EST 2010


I could mention that if I do a

clear ip bgp <transit> soft

if I am very unlucky my router starts dropping bgp sessions at that point.

A short desription of my route-maps:

FRA#sh route-map PEER-DECIX-5588-IN
route-map PEER-DECIX-5588-IN, deny, sequence 10
  Match clauses:
    community (community-list filter): LOCAL
  Set clauses:
  Policy routing matches: 0 packets, 0 bytes
route-map PEER-DECIX-5588-IN, permit, sequence 11
  Match clauses:
  Set clauses:
    local-preference 100
  Policy routing matches: 0 packets, 0 bytes


FRA#sh route-map PEER-DECIX-5588-OUT
route-map PEER-DECIX-5588-OUT, deny, sequence 10
  Match clauses:
    community (community-list filter): 5588-PP0
  Set clauses:
  Policy routing matches: 0 packets, 0 bytes
route-map PEER-DECIX-5588-OUT, permit, sequence 11
  Match clauses:
    community (community-list filter): 5588-PP1
  Set clauses:
    as-path prepend 1234
    comm-list UNWANTED-OUT delete
  Policy routing matches: 0 packets, 0 bytes
route-map PEER-DECIX-5588-OUT, permit, sequence 12
  Match clauses:
    community (community-list filter): 5588-PP2
  Set clauses:
    as-path prepend 1234 1234
    comm-list UNWANTED-OUT delete
  Policy routing matches: 0 packets, 0 bytes
route-map PEER-DECIX-5588-OUT, permit, sequence 13
  Match clauses:
    community (community-list filter): 5588-PP3
  Set clauses:
    as-path prepend 1234 1234 1234
    comm-list UNWANTED-OUT delete
  Policy routing matches: 0 packets, 0 bytes
route-map PEER-DECIX-5588-OUT, permit, sequence 14
  Match clauses:
    community (community-list filter): 5588-PP4
  Set clauses:
    as-path prepend 1234 1234 1234 1234
    comm-list UNWANTED-OUT delete
  Policy routing matches: 0 packets, 0 bytes
route-map PEER-DECIX-5588-OUT, permit, sequence 15
  Match clauses:
    community (community-list filter): TO-PEERING
  Set clauses:
    comm-list UNWANTED-OUT delete
  Policy routing matches: 0 packets, 0 bytes


The transit route-map is a little bit different. in my example it
would be telia:

FRA#sh route-map TRANSIT-1299-IN
route-map TRANSIT-1299-IN, deny, sequence 10
  Match clauses:
    community (community-list filter): LOCAL
  Set clauses:
  Policy routing matches: 0 packets, 0 bytes
route-map TRANSIT-1299-IN, permit, sequence 15
  Match clauses:
    community (community-list filter): TELIA-US
  Set clauses:
    metric 0
    local-preference 50
    as-path prepend 1234
    origin igp
  Policy routing matches: 0 packets, 0 bytes
route-map TRANSIT-1299-IN, permit, sequence 999
  Match clauses:
  Set clauses:
    metric 0
    local-preference 50
    origin igp
  Policy routing matches: 0 packets, 0 bytes



FRA#sh route-map TRANSIT-1299-OUT
route-map TRANSIT-1299-OUT, deny, sequence 10
  Match clauses:
    community (community-list filter): TRANSIT-ALL-PP0
  Set clauses:
  Policy routing matches: 0 packets, 0 bytes
route-map TRANSIT-1299-OUT, deny, sequence 11
  Match clauses:
    community (community-list filter): TRANSIT-TELIA-PP0
  Set clauses:
  Policy routing matches: 0 packets, 0 bytes
route-map TRANSIT-1299-OUT, permit, sequence 20
  Match clauses:
    community (community-list filter): TRANSIT-ALL-PP1
  Set clauses:
    as-path prepend 1234
    comm-list UNWANTED-OUT delete
  Policy routing matches: 0 packets, 0 bytes
route-map TRANSIT-1299-OUT, permit, sequence 21
  Match clauses:
    community (community-list filter): TRANSIT-ALL-PP2
  Set clauses:
    as-path prepend 1234 1234
    comm-list UNWANTED-OUT delete
  Policy routing matches: 0 packets, 0 bytes
route-map TRANSIT-1299-OUT, permit, sequence 22
  Match clauses:
    community (community-list filter): TRANSIT-ALL-PP3
  Set clauses:
    as-path prepend 1234 1234 1234
    comm-list UNWANTED-OUT delete
  Policy routing matches: 0 packets, 0 bytes
route-map TRANSIT-1299-OUT, permit, sequence 23
  Match clauses:
    community (community-list filter): TRANSIT-ALL-PP4
  Set clauses:
    as-path prepend 1234 1234 1234 1234
    comm-list UNWANTED-OUT delete
  Policy routing matches: 0 packets, 0 bytes
route-map TRANSIT-1299-OUT, permit, sequence 30
  Match clauses:
    community (community-list filter): TRANSIT-TELIA-PP1
  Set clauses:
    as-path prepend 1234
    comm-list UNWANTED-OUT delete
  Policy routing matches: 0 packets, 0 bytes
route-map TRANSIT-1299-OUT, permit, sequence 31
  Match clauses:
    community (community-list filter): TRANSIT-TELIA-PP2
  Set clauses:
    as-path prepend 1234 1234
    comm-list UNWANTED-OUT delete
  Policy routing matches: 0 packets, 0 bytes
route-map TRANSIT-1299-OUT, permit, sequence 32
  Match clauses:
    community (community-list filter): TRANSIT-TELIA-PP3
  Set clauses:
    as-path prepend 1234 1234 1234
    comm-list UNWANTED-OUT delete
  Policy routing matches: 0 packets, 0 bytes
route-map TRANSIT-1299-OUT, permit, sequence 33
  Match clauses:
    community (community-list filter): TRANSIT-TELIA-PP4
  Set clauses:
    as-path prepend 1234 1234 1234 1234
    comm-list UNWANTED-OUT delete
  Policy routing matches: 0 packets, 0 bytes
route-map TRANSIT-1299-OUT, permit, sequence 40
  Match clauses:
    community (community-list filter): TO-TRANSIT
  Set clauses:
    comm-list UNWANTED-OUT delete
  Policy routing matches: 0 packets, 0 bytes




Communities:

FRA#sh ip community-list TELIA-US
Named Community standard list TELIA-US
    permit 1299:25000
    permit 1299:35000




On Thu, Mar 11, 2010 at 6:50 PM, Paul Stewart <paul at paulstewart.org> wrote:
> Hmmm.. that's definitely strange.  Have a pair of 7600's with 720-3BXL's in
> them doing similar (roughly 250 public peers per box, a few transit
> connections per box, dozen downstream customers per box rough) and even
> though the boxes are loaded down pretty good we don't see what you describe.
> Our CPU sits around 40% most of the time on 5 min average.
>
> We're running 12.2(33)SRA7 if that helps at all...
>
> Paul
>



More information about the cisco-nsp mailing list