Same as in Jonos use the "aggregate" cmd:
2. router bgp as-number
3. address-family { ipv4 | ipv6 } unicast
4. aggregate-address address/mask-length [ as-set ] [ as-confed-set ] [
summary-only ] [ route-policy route-policy-name ]
The as-set keyword generates autonomous system set path information and
community information from contributing paths.
The as-confed-set keyword generates autonomous system confederation set path
information from contributing paths.
The summary-only keyword filters all more specific routes from updates.
The route-policy route-policy-name keyword and argument specify the route
policy used to set the attributes of the aggregate route.
adam
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Nick Ryce
Sent: Thursday, November 24, 2011 11:49 AM
To: [email protected]
Subject: [c-nsp] IOS XR BGP
Hi,
I am moving from Juniper to Cisco ( IOS XR ) and am looking to emulate a
certain feature ( aggregate addressing for BGP )
In Junos I can set routing-options aggregate route x.x.x.x/19 . If there is a
less specific contributing route from IGP then the aggregate is announced
through BGP.
In BGP on IOS XR you use the network statement network x.x.x.x/19 now you need
to have an exact route for this ( normally setting a static route ). This will
not suit my requirements as if we lose IGP on that router I would like to stop
announcing the ranges via BGP but the static route will still be there and I
will theoretically blackhole traffic.
Any ideas how to allow BGP to announce an aggregate route when there is less
specific in IGP would be a great help.
Thanks
Nick
________________________________
--
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the sender. Any
offers or quotation of service are subject to formal specification.
Errors and omissions excepted. Please note that any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Lumison.
Finally, the recipient should check this email and any attachments for the
presence of viruses. Lumison accept no liability for any
damage caused by any virus transmitted by this email.
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
