You can use EEM to run commands on other routers, it's not the best at doing remote telnet/ssh but it can do it to some extent, its the interactive stuff that seemed to really kill it last time I tried but a simple command would work, it may be better for that now.
So essentially you would create your app on R1 based on the event of BGP peer going down, then the action would be to open a session to R0 and change that route-map for your communities and execute a clear ip bgp x.x.x.x out, whether you can do all of that via EEM remotely i'm not sure, on the same router would be no problem. You could just write an expect script if you have a unix host somewhere there for management and have the EEM trigger that if it's easier, I could even write you the expect script if you want, it's pretty simple. Ben -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Sunday, 26 October 2008 3:25 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; cisco-nsp@puck.nether.net Subject: RE: [c-nsp] BGP Multihomed Selective/Conditional Advertisement In this particular setup the router R0 wouldn't be peering with ATT's router, it would get the default router from R1 with is my other router, so I would not get the neighbor down alert. (ISP Cogent) (ISP ATT) | | RO ------------------- R1 Is there a way to use event manager to track a default route with communities set on it or defaul route with next hop to monitor as an event and take action based on that? Thank you, ________________________________ From: Ben Steele [mailto:[EMAIL PROTECTED] Sent: Fri 10/24/2008 8:55 PM To: 'Ben Steele'; Kacprzynski, Tomasz; [EMAIL PROTECTED]; cisco-nsp@puck.nether.net Subject: RE: [c-nsp] BGP Multihomed Selective/Conditional Advertisement Ah my apologies I should have read your original email, your problem is a little more trickier than that. After having read your original one though I believe you could probably do this with an event manager task used to watch logging for bgp neighbour failure you could trigger it to modify your export community and do a "clear ip bgp x.x.x.x out" Ben -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ben Steele Sent: Saturday, 25 October 2008 10:44 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] BGP Multihomed Selective/Conditional Advertisement If it's purely just for failover (ie you don't want to get billed for traffic down your failover link while your active is up) then why not just send the community: "174:70 70 Set customer route local preference to 70" This will make them use ATT's path until the ATT link goes down. Ben -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Saturday, 25 October 2008 9:48 AM To: [EMAIL PROTECTED]; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] BGP Multihomed Selective/Conditional Advertisement Arie, Thank you for your response. In my situation, where everything is normal, I am actually sending their specific communities for them not to advertise my route to their peers. My only problem is how to change that automatically when my default route from ATT goes away (ATT circuit does down and I'm in a failover situation)? Thank you, -----Original Message----- From: Arie Vayner (avayner) [mailto:[EMAIL PROTECTED] Sent: Fri 10/24/2008 6:03 PM To: Kacprzynski, Tomasz; cisco-nsp@puck.nether.net Subject: RE: [c-nsp] BGP Multihomed Selective/Conditional Advertisement Tom, Instead of not advertising a certain prefix, there is another alternative using BGP communities which are recognized by your upstream providers. Take a look for what Cogent supports for example (better ask them for the official list...): http://www.onesc.net/communities/as174/ You could play with the local pref communities or the no-export ones Its not the full answer, but just another idea... Let me know if you are still stuck... Arie -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, October 24, 2008 23:07 PM To: cisco-nsp@puck.nether.net Subject: [c-nsp] BGP Multihomed Selective/Conditional Advertisement I have been trying to figure out how to do this and maybe someone will be able to help me out. I have two ISP connections ISP ATT and ISP Cogent. (ISP Cogent) (ISP ATT) | | RO ------------------- R1 ATT would be used for primarily internet and access to our webservers. Cogent would be primarily used to access Cognet's network that use VPN for incoming connections only. I do not want to have other networks besides Cogent's network using this path to access our webserver. I would like to have each other act as a backup for one another. For instance if ATT fails I want everyone on the internet use Cogent to access me. If Cogent fails I want everyone on the internet and the VPN connections on Cogent's network to use ATT. So basically what I was thinking to setup is to accept a default router from ATT and Cogent. Lower the local preference of Cogent and that way I would accomplish using ATT as primary internet access. The tricky part is with Cogent and using then to only access their local networks. Looking through communities I found out Cogent's communities that would not export my route to their peers and keep it internal within their AS. This works fine but the problem now is how do I failover if ATT fails? How do I automatically change my not-export community I'm sending to Cogent to start adverting the route to its peers? I looked at conditional advertisement, I was able to basically send the route map with not-export communities to Cogent if the default route from ATT is present. The problem with this is that once the default router disappears it doesn't advertise anything to Cogent, none of my routes are advertised to Cogent. I'm not sure if I could do this sort of a double condition such as if ATT's default route is present send out to Cogent a route map with prefixes to not-export my routes if ATT's default route is not present sent to Cogent a route map without any communities on my routes Basically I'm trying to figure out how I can have multihoming, but with the constrains that I want 1 ISP to be used for internet and the other to only access their AS, but still have the capability to automatically failover in case one of the circuits dies. Thank you for any input or help. Tom Kacprzynski Network Engineer _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ No virus found in this incoming message. Checked by AVG - http://www.avg.com <http://www.avg.com/> Version: 8.0.175 / Virus Database: 270.8.2/1742 - Release Date: 24/10/2008 6:08 PM _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ No virus found in this incoming message. Checked by AVG - http://www.avg.com <http://www.avg.com/> Version: 8.0.175 / Virus Database: 270.8.2/1742 - Release Date: 24/10/2008 6:08 PM No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.175 / Virus Database: 270.8.2/1742 - Release Date: 25/10/2008 5:55 PM _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/