Q: BGP Aggregate

From: Victor Cappuccio (cvictor@protokolgroup.com)
Date: Wed May 10 2006 - 19:39:14 ART


Hello List..

 

Why using the as-set and the advertise-map in aggregate, the Route becomes
Atomic Aggregate? Why the attributes of the specific route, is not preserved
the aggregate routes ??

 

Thanks

Victor.

 

 

Rack1R3#show ip bgp 112.0.0.00

BGP routing table entry for 112.0.0.0/5, version 34

Paths: (2 available, best #1, table Default-IP-Routing-Table)

  Advertised to non peer-group peers:

  10.5.5.5 10.8.8.8

  100 54, (aggregated by 100 10.1.1.1)

    10.1.1.1 (metric 540160) from 10.1.1.1 (10.1.1.1)

      Origin IGP, metric 0, localpref 100, valid, external,
atomic-aggregate, best

      Community: 54

  100 54, (aggregated by 100 10.1.1.1)

    10.8.8.8 (metric 409600) from 10.8.8.8 (10.8.8.8)

      Origin IGP, metric 0, localpref 100, valid, internal, atomic-aggregate

      Community: 54

 

 

 

Rack1R1#show ip bgp | in 0.0.0.0

*> 28.119.16.0/23 0.0.0.0 200 32768 54 i

*> 112.0.0.0/5 0.0.0.0 200 32768 54 i

*> 172.168.0.0/19 0.0.0.0 32768 i

*> 199.198.0.0/20 0.0.0.0 32768 i

Rack1R1#show run | be router bgp 100

router bgp 100

 no synchronization

 bgp router-id 10.1.1.1

 bgp log-neighbor-changes

 aggregate-address 28.119.16.0 255.255.254.0 as-set summary-only

 aggregate-address 112.0.0.0 248.0.0.0 as-set summary-only advertise-map
AVER

 aggregate-address 172.168.0.0 255.255.224.0 summary-only

 aggregate-address 199.198.0.0 255.255.240.0 summary-only

 neighbor 10.2.2.2 remote-as 100

 neighbor 10.2.2.2 update-source Loopback0

 neighbor 10.2.2.2 next-hop-self

 neighbor 10.2.2.2 send-community

 neighbor 10.3.3.3 remote-as 300

 neighbor 10.3.3.3 ebgp-multihop 255

 neighbor 10.3.3.3 update-source Loopback0

 neighbor 10.3.3.3 send-community

 neighbor 10.8.8.8 remote-as 300

 neighbor 10.8.8.8 ebgp-multihop 255

 neighbor 10.8.8.8 update-source Loopback0

 neighbor 10.8.8.8 send-community

 no auto-summary

!

ip http server

 

Rack1R1#show route-map

route-map AVER, permit, sequence 10

  Match clauses:

    ip address prefix-lists: EMITE

  Set clauses:

  Policy routing matches: 0 packets, 0 bytes

route-map SOLOLO0, permit, sequence 10

  Match clauses:

    interface Loopback0

  Set clauses:

  Policy routing matches: 0 packets, 0 bytes

route-map OSPF->EIGRP, permit, sequence 10

  Match clauses:

  Set clauses:

    tag 1110

  Policy routing matches: 0 packets, 0 bytes

Rack1R1#show ip prefix

ip prefix-list EMITE: 1 entries

   seq 10 deny 113.0.0.0/8

Rack1R1#



This archive was generated by hypermail 2.1.4 : Thu Jun 01 2006 - 06:33:21 ART