Cisco Nexus 3548 series, Справочник по командам

Страница: 333 / 556

313
Cisco Nexus 3548 Switch NX-OS Unicast Routing Command Reference
OL-27852-01
Chapter Unicast Routing Commands
route-map
The match route-map configuration command has multiple formats. The match commands can be given
in any order, and all match commands must pass to cause the route to be redistributed according to the
set actions given with the set commands. The no forms of the match commands remove the specified
match criteria.
Use route maps when you want detailed control over how routes are redistributed between routing
processes. The destination routing protocol is the one you specify with the
router global configuration
command. The source routing protocol is the one you specify with the redistribute router configuration
command. See the “Examples” section for an illustration of how route maps are configured.
When you are passing routes through a route map, a route map can have several parts. Any route that
does not match at least one
match clause that relates to a route-map command is ignored; that is, the
route is not advertised for outbound route maps and is not accepted for inbound route maps. If you want
to modify some particular data, you must configure a second route map section with an explicit match
specified.
This command requires the LAN Enterprise Services license.
Examples This example shows how to redistribute Routing Information Protocol (RIP) routes with a hop count
equal to 1 into Open Shortest Path First (OSPF). These routes are redistributed into OSPF as external
link-state advertisements (LSAs) with a metric type of Type 1, and a tag equal to 1.
switch# configure terminal
switch(config)# router ospf 109
switch(config-route-map)# redistribute rip route-map rip-to-ospf
switch(config-route-map)# route-map rip-to-ospf permit
switch(config-route-map)# set metric 5
switch(config-route-map)# set metric-type type1
switch(config-route-map)# set tag 1
switch(config-route-map)#
This example shows how to set the autonomous system path to match BGP autonomous system path
access list 20:
switch# configure terminal
switch(config)# route-map IGP2BGP
switch(config-route-map)# match as-path 20
switch(config-route-map)#
This example shows how to configure that the routes matching community list 1 have the weight set to
100. Any route that has community 109 has the weight set to 100.
switch# configure terminal
switch(config)# ip community-list 1 permit 109
switch(config)# route-map set_weight
switch(config-route-map)# match community 1
switch(config-route-map)# set weight 100
switch(config-route-map)#
This example shows how to configure that the routes matching community list 1 have the weight set to
200. Any route that has community 109 alone has the weight set to 200.
switch# configure terminal
switch(config)# ip community-list 1 permit 109
switch(config)# route-map set_weight
switch(config-route-map)# match community 1 exact
switch(config-route-map)# set weight 200
switch(config-route-map)#