BGP route-map options

Greg Whynott Greg.Whynott at oicr.on.ca
Fri Jan 14 18:00:16 UTC 2011


haha…  yeah that is not a copy and paste but rather me just typing that out.

the proper spelling in the config is being used,  or the american spelling…  english is the worse language…

thanks again,
greg

On Jan 14, 2011, at 12:52 PM, Thomas Magill wrote:

> Wait...
>
> Does the router even accept 'neighbour' instead of ' neighbor'?
>
>
> -----Original Message-----
> From: Greg Whynott [mailto:Greg.Whynott at oicr.on.ca]
> Sent: Friday, January 14, 2011 9:00 AM
> To: nanog at nanog.org list
> Subject: BGP route-map options
>
> Following a few documents on how to use route-maps to set preference of routes (related to my last thread regarding asymmetrical routing) all the ones I have looked at today (about 6or so) use the below method to apply the route map under the router section:
>
> router bgp YOURAS#
> neighbour x.x.x.x remote-as AS#
> neighbour x.x.x.x route-map MAPNAME in
>
> yet in the last line,  "route-map"  is not an option on my router,  which is an ASR1004 running the version 15 line of code.
>
> is there a new way to do this?
>
> don't you love Cisco's consistency?
>
> thanks much for your time again,
> greg
>
>
>
>
> --
>
> This message and any attachments may contain confidential and/or privileged information for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this message in error, please contact the sender and delete all copies. Opinions, conclusions or other information contained in this message may not be that of the organization.
>


--

This message and any attachments may contain confidential and/or privileged information for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this message in error, please contact the sender and delete all copies. Opinions, conclusions or other information contained in this message may not be that of the organization.




More information about the NANOG mailing list