Foundry Configuration Guide for the FESX, FSX, and FWSX
21 - 54 © Foundry Networks, Inc. December 2005
The metric-type internal parameter sets the route's MED to the same value as the IGP metric of the BGP4 next-
hop route. The parameter does this when advertising a BGP4 route to an EBGP neighbor.
The next-hop <ip-addr> parameter sets the IP address of the route’s next hop router.
The nlri multicast | unicast | multicast unicast parameter redistributes routes into the multicast Routing
Information Base (RIB) instead of the unicast RIB.
NOTE: Setting the NLRI type to multicast applies only when you are using the route map to redistribute directly-
connected routes. Otherwise, the set option is ignored.
The origin igp | incomplete parameter sets the route’s origin to IGP or INCOMPLETE.
The tag <tag-value> parameter sets the route’s tag. You can specify a tag value from 0 – 4294967295.
NOTE: This parameter applies only to routes redistributed into OSPF.
NOTE: You also can set the tag value using a table map. The table map changes the value only when the Layer
3 Switch places the route in the IP route table instead of changing the value in the BGP route table. See “Using a
Table Map To Set the Tag Value” on page 21-55.
The weight <num> parameter sets the weight for the route. You can specify a weight value from
0 – 4294967295.
Setting a BP4 Route’s MED to the same Value as the IGP Metric of the Next-Hop Route
To set a route's MED to the same value as the IGP metric of the BGP4 next-hop route, when advertising the route
to a neighbor, enter commands such as the following:
FESX424 Router(config)# access-list 1 permit 192.168.9.0 0.0.0.255
FESX424 Router(config)# route-map bgp4 permit 1
FESX424 Router(config-routemap bgp4)# match ip address 1
FESX424 Router(config-routemap bgp4)# set metric-type internal
The first command configures an ACL that matches on routes with destination network 192.168.9.0. The
remaining commands configure a route map that matches on the destination network in ACL 1, then sets the
metric type for those routes to the same value as the IGP metric of the BGP4 next-hop route.
Syntax: set metric-type internal
Setting the Next Hop of a BGP4 Route
To set the next hop address of a BGP4 route to a neighbor address, enter commands such as the following:
FESX424 Router(config)# route-map bgp5 permit 1
FESX424 Router(config-routemap bgp5)# match ip address 1
FESX424 Router(config-routemap bgp5)# set ip next-hop peer-address
These commands configure a route map that matches on routes whose destination network is specified in ACL 1,
and sets the next hop in the routes to the neighbor address (inbound filtering) or the local IP address of the BGP4
session (outbound filtering).
Syntax: set ip next-hop peer-address
The value that the software substitutes for peer-address depends on whether the route map is used for inbound
filtering or outbound filtering:
• When you use the set ip next-hop peer-address command in an inbound route map filter, peer-address
substitutes for the neighbor’s IP address.
• When you use the set ip next-hop peer-address command in an outbound route map filter, peer-address
substitutes for the local IP address of the BGP4 session.
NOTE: You can use this command for a peer group configuration.
To Next Page
Loading...
Need help?
General
