Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Beginner's BGP route map question

Unanswered Question
Aug 21st, 2008
User Badges:
  • Bronze, 100 points or more

I imagine this is a beginner's-calibre; bonk-me-over-the-head-with-a-saucepan-for-asking kind of question, but here it is anyway:

When I was troubleshooting my other BGP issue that y'all were so helpful with, I tried configuring a route-map to set the weight to 100 for incoming routes. I created a route-map named "Toby" (Toby is my nephew!) like this here:

Sethtek-G#conf term

Enter configuration commands, one per line. End with CNTL/Z.

Sethtek-G(config)#route-map Toby

Sethtek-G(config-route-map)#match next-hop 1

Sethtek-G(config-route-map)#set weight 100


Sethtek-G(config)#access-list 1 permit host

Sethtek-G(config)#router bgp 190

Sethtek-G(config-router)#neighbor route-map Toby

% Incomplete command.

Sethtek-G(config-router)#neighbor route-map Toby in

% "Toby" used as BGP inbound route-map, nexthop match not supported


Dumb question: Why is nexthop match not supported for INBOUND routes? Aren't those the only routes for which the next-hop attribute is even interesting?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Harold Ritter Thu, 08/21/2008 - 18:32
User Badges:
  • Cisco Employee,


As the messages indicated, you can use the match next next-hop statement on an inbound bgp route-map. You don't really need the match statement as you probably want to set the weight for all updates coming from that neighbor.

You could also just do:

neighbor weight 100


CriscoSystems Mon, 08/25/2008 - 13:42
User Badges:
  • Bronze, 100 points or more

Well no, the message indicated that you CAIN'T use the next-hop for an inbound route map, and I don't understand why.

In a multiaccess IBGP network, plenty of routes with different next-hops could be coming in from a single neighbor. And "probably" doesn't cut it, because if you want to adjust the weights on a per-route basis (isn't that the whole point of the weight attribute anyway), I don't see why you shouldn't be able to.


This Discussion