[c-nsp] using BGP communitys with route-maps on ASR

Greg Whynott Greg.Whynott at oicr.on.ca
Fri Jan 14 12:02:53 EST 2011


I did not,  will it have the same affect?

thanks for your time and help Viijay!

-g


On Jan 14, 2011, at 11:52 AM, Ramcharan, Vijay A wrote:

> Did you try applying policy under the address family in question?
>
> labrtr01(config)#router bgp 65001
> labrtr01(config-router)#nei 1.1.1.1 ?
>  description              Neighbor specific description
>  disable-connected-check  one-hop away EBGP peer using loopback address
>  ebgp-multihop            Allow EBGP neighbors not on directly connected
>                           networks
>  fall-over                session fall on peer route lost
>  ha-mode                  high availability mode
>  inherit                  Inherit a template
>  local-as                 Specify a local-as number
>  password                 Set a password
>  peer-group               Member of the peer-group
>  remote-as                Specify a BGP neighbor
>  shutdown                 Administratively shut down this neighbor
>  timers                   BGP per neighbor timers
>  transport                Transport options
>  ttl-security             BGP ttl security check
>  update-source            Source of routing updates
>  version                  Set the BGP version to match a neighbor
>
> labrtr01(config-router)#addr ipv4
> labrtr01(config-router-af)#nei 1.1.1.1 ?
>  activate                Enable the Address Family for this Neighbor
>  advertise-map           specify route-map for conditional advertisement
>  advertisement-interval  Minimum interval between sending BGP routing updates
>  allowas-in              Accept as-path with my AS present in it
>  capability              Advertise capability to the peer
>  default-originate       Originate default route to this neighbor
>  distribute-list         Filter updates to/from this neighbor
>  dmzlink-bw              Propagate the DMZ link bandwidth
>  filter-list             Establish BGP filters
>  inherit                 Inherit a template
>  maximum-prefix          Maximum number of prefixes accepted from this peer
>  next-hop-self           Disable the next hop calculation for this neighbor
>  next-hop-unchanged      Propagate next hop unchanged for iBGP paths to this
>                          neighbor
>  prefix-list             Filter updates to/from this neighbor
>  remove-private-as       Remove private AS number from outbound updates
>  route-map               Apply route map to neighbor
>  route-reflector-client  Configure a neighbor as Route Reflector client
>  send-community          Send Community attribute to this neighbor
>  send-label              Send NLRI + MPLS Label to this peer
>  slow-peer               Configure slow-peer
>  soft-reconfiguration    Per neighbor soft reconfiguration
>  soo                     Site-of-Origin extended community
>  translate-update        Translate Update to MBGP format
>  unsuppress-map          Route-map to selectively unsuppress suppressed routes
>  weight                  Set default weight for routes from this neighbor
>
> labrtr01(config-router-af)#nei 1.1.1.1
>
>
> Vijay Ramcharan
>
>> -----Original Message-----
>> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
>> bounces at puck.nether.net] On Behalf Of Greg Whynott
>> Sent: Friday, January 14, 2011 11:37 AM
>> To: cisco-nsp at puck.nether.net
>> Subject: [c-nsp] using BGP communitys with route-maps on ASR
>>
>> Hello,
>>
>> I'm attempting to address a routing issue using route-maps and local-
>> preferences.  On Cisco's site and a few other sources i've found,  the
>> method is to specify the route map while in the BGP router config as such:
>>
>>
>> ip community−list 1 permit 8888:10
>>
>> route−map THISWAY permit 10
>> match community 1
>> set local−preference 200
>>
>> router bgp 1111
>> neighbour 192.168.1.2 remote-as 2222
>> neighbour 192.168.1.2 route-map THISWAY in
>>
>>
>>
>> I am working with an ASR1004 and the last line is not accepted.  route-map
>> is not an option for the neighbor attribute.
>>
>>
>> INTERNETASR1(config-router)#neighbor 192.168.1.2 ?
>>  description              Neighbor specific description
>>  disable-connected-check  one-hop away EBGP peer using loopback address
>>  ebgp-multihop            Allow EBGP neighbors not on directly connected
>> networks
>>  fall-over                session fall on peer route lost
>>  ha-mode                  high availability mode
>>  inherit                  Inherit a template
>>  local-as                 Specify a local-as number
>>  password                 Set a password
>>  peer-group               Member of the peer-group
>>  remote-as                Specify a BGP neighbor
>>  shutdown                 Administratively shut down this neighbor
>>  timers                   BGP per neighbor timers
>>  transport                Transport options
>>  ttl-security             BGP ttl security check
>>  update-source            Source of routing updates
>>  version                  Set the BGP version to match a neighbor
>>
>> ASR1004(config-router)#neighbor 192.168.1.2
>>
>>
>> did something change or have i messed up somewhere?
>>
>> thanks for your time,
>> 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.
>>
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
>> ______________________________________________________________________
>> This e-mail has been scanned by Verizon Managed Email Content Service, using
>> Skeptic™ technology powered by MessageLabs. For more information on Verizon
>> Managed Email Content Service, visit http://www.verizonbusiness.com.
>> ______________________________________________________________________


--

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 cisco-nsp mailing list