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

[Greg Whynott]

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.