ASR1002 unable to use BGP route-map match next-hop on inbound

goncalo_gil · ‎03-01-2011

Hi Team,

I am running ASR1002 with latest XE IOS version asr1000rp1-adventerprisek9.03.02.01.S.151-1.S1.bin

configuration bellow

router bgp 65000
bgp router-id 1.1.1.1
bgp log-neighbor-changes
timers bgp 5 15
!
address-family ipv4 vrf LABR01-VRF
bgp router-id 1.1.1.1
neighbor bgprrclient peer-group
neighbor bgprrclient remote-as 65001
neighbor bgprrclient password 7 1234
neighbor bgprrclient update-source Loopback0
neighbor bgprrclient version 4
neighbor bgprrclient route-reflector-client
neighbor bgprrclient route-map set_weight in

I then tried to create new route-map and get error that match next-hop can not be used on inbound

route-map set_weight permit 10
match ip next-hop prefix-list thirdparty
match as-path 1
set weight 1000

LAB-ASR1002(config)#route-map set_weight permit 10
LAB-ASR1002(config-route-map)# match ip next-hop prefix-list thirdparty
% "set_weight" used as BGP inbound route-map, nexthop match not supported
% not supported match will behave as route-map with no match
% "set_weight" used as BGP inbound route-map, nexthop match not supported
% not supported match will behave as route-map with no match
% "set_weight" used as BGP inbound route-map, nexthop match not supported
% not supported match will behave as route-map with no match
% "set_weight" used as BGP inbound route-map, nexthop match not supported
% not supported match will behave as route-map with no match
% "set_weight" used as BGP inbound route-map, nexthop match not supported
% not supported match will behave as route-map with no match

Not sure why Cisco is not supporting a pretty basic feature for BGP route maps.

I tried looking into matching other variables but I am unable to get same result as I have same routes on bgp table from multible inbound peers.

I also get this message when configuring tacacs. I looked for "new" cli but no luck:

LAB-ASR1002(config)#tacacs-server host 2.2.2.2

This cli will be deprecated soon. Use new server cli

Any ideas how to get around this two issues?

Many thanks

Gonz.

Laurent Aubert · ‎03-01-2011

Hi,

Unfortunately this combinaison is not supported.

If you share your BGP design and requirement, we could come up with another way to do it.

Regarding the tacacs configuration, the template changed to support both IPv4 and IPv6 Tacacs server:

http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-adsl_dial.html#wp1102027

Here is an example:

tacacs server S1
 address ipv4 x.x.x.x
 key 7 key1
 timeout 1
tacacs server S2
 address ipv4 y.y.y.y
 key 7 key2
 timeout 1

aaa group server tacacs+ GROUP
 server name S1
 server name S2
 ip tacacs source-interface GigabitEthernet0/0/1
!

HTH

Laurent.