The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the Cisco NX-OS unicast routing commands that begin with the letter R.
To inject routes from one routing domain into the Border Gateway Protocol (BGP), use the redistribute command. To remove the redistribute command from the configuration file and restore the system to its default condition in which the software does not redistribute routes, use the no form of this command.
redistribute { direct | eigrp instance-tag | isis instance-tag | ospf instance-tag | rip instance-tag | static } [ route-map map- name ]
no redistribute { direct | eigrp instance-tag | isis instance-tag | ospf instance-tag | rip instance-tag | static } [ route-map map- name ]
Address family configuration
Router configuration
Router VRF configuration
|
|
---|---|
Use the redistribute command to import routes from other routing protocols into BGP. You should always use a route map to filter these routes to ensure that BGP redistributes only the routes that you intend to redistribute.
You must configure a default metric to redistribute routes from another protocol into BGP. You can configure the default metric with the default-metric command or with the route map configured with the redistribute command.
This example shows how to redistribute BGP routes into an EIGRP autonomous system:
|
|
---|---|
To inject routes from one routing domain into the Enhanced Interior Gateway Routing Protocol (EIGRP), use the redistribute command. To remove the redistribute command from the configuration file and restore the system to its default condition in which the software does not redistribute routes, use the no form of this command.
redistribute { bgp as-number | direct | eigrp id | isis instance-tag | ospf instance-tag | rip instance-tag | static } [ route-map map- name ]
no redistribute { bgp as-number | direct | eigrp as-number | isis instance-tag | ospf instance-tag | rip instance-tag | static }
Address family configuration
Router configuration
Router VRF configuration
|
|
---|---|
Use the redistribute command to import routes from other routing protocols into EIGRP. You should always use a route map to filter these routes to ensure that EIGRP redistributes only the routes that you intend to redistribute.
You must configure a default metric to redistribute routes from another protocol into EIGRP. You can configure the default metric with the default-metric command or with the route map configured with the redistribute command.
This example shows how to redistribute cause BGP routes into an EIGRP autonomous system:
This example shows how to redistribute the specified IS-IS process routes into an EIGRP autonomous system within a virtual routing and forwarding instance (VRF). The IS-IS routes are redistributed using route map IsIsMap.
|
|
---|---|
Sets the default metrics for routes redistributed into EIGRP. |
To redistribute other protocol routes into Intermediate System-to-Intermediate System (IS-IS), use the redistribute command. To disable the redistribution, use the no form of this command.
redistribute protocol as-num [. as-num ] | process-tag route-map name
no redistribute protocol as-num [. as-num ] | process-tag route-map name
Source protocol from which routes are being redistributed ; see the “Usage Guidelines” section for additional information about valid values. |
|
Address family configuration
Router configuration
|
|
---|---|
The command syntax is supported for IPv4 and IPv6.
The valid values for the protocol argument are as follows:
This example shows how to redistribute routes from an IS-IS routing process into a BGP system:
This example shows how to disable redistribution:
|
|
---|---|
Enters the address family mode or a VRF address-family mode. |
|
To inject routes from one routing domain into Open Shortest Path First (OSPF), use the redistribute command. To remove the redistribute command from the configuration file and restore the system to its default condition in which the software does not redistribute routes, use the no form of this command.
redistribute { bgp as-number | direct | eigrp id | isis instance-tag | ospf instance-tag | rip instance-tag | static } [ route-map map- name ]
no redistribute { bgp as-number | direct | eigrp as-number | isis instance-tag | ospf instance-tag | rip instance-tag | static }
Router configuration
Router VRF configuration
|
|
---|---|
Use the redistribute command to import routes from other routing protocols into OSPF. You should always use a route map to filter these routes to ensure that OSPF redistributes only the routes that you intend.
You need to configure a default metric to redistribute routes from another protocol into OSPF. You can configure the default metric with the default-metric command or with the route map configured with the redistribute command.
Note If you redistribute static routes, Cisco NX-OS also redistributes the default static route.
This example shows how to redistribute BGP routes into an OSPF autonomous system:
This example shows how to redistribute the specified IS-IS process routes into an OSPF autonomous system within a virtual routing and forwarding instance (VRF). The IS-IS routes are redistributed using route map IsIsMap.
|
|
---|---|
Sets the default metrics for routes redistributed into OSPF. |
To inject routes from one routing domain into Open Shortest Path First version 3 (OSPFv3), use the redistribute command. To remove the redistribute command from the configuration file and restore the system to its default condition in which the software does not redistribute routes, use the no form of this command.
redistribute { bgp as-number | direct | isis instance-tag | rip instance-tag | static } [ route-map map- name ]
no redistribute { bgp as-number | direct | eigrp as-number | isis instance-tag | ospfv3 instance-tag | rip instance-tag | static }
|
|
---|---|
Use the redistribute command to import routes from other routing protocols into OSPFv3. You should always use a route map to filter these routes to ensure that OSPFv3 redistributes only the routes that you intend.
You need to configure a default metric to redistribute routes from another protocol into OSPFv3. You can configure the default metric with the default-metric command or with the route map configured with the redistribute command.
Note If you redistribute static routes, Cisco NX-OS also redistributes the default static route.
This example shows how to redistribute BGP routes into an OSPFv3 autonomous system:
|
|
---|---|
Sets the default metrics for routes redistributed into OSPFv3. |
To redistribute routes from another routing domain into the Routing Information Protocol (RIP), use the redistribute command. To restore the system to its default condition in which the software does not redistribute routes, use the no form of this command.
redistribute { bgp id | direct | eigrp id | isis id | ospf id | ospfv3 id | static } route-map map-name
Router address-family configuration
|
|
---|---|
Cisco NX-OS filters redistributed routing information using a route map. You can configure the route map to set the RIP metric used for redistributed routes. If you do not set the RIP metric with a route map, Cisco NX-OS determines the metric based on the redistributed protocol or by the default-metric command. If Cisco NX-OS cannot determine a valid metric, then it does not redistribute the routes.
This example shows how to redistribute BGP routes into a RIP process:
|
|
Generates a default route for routes redistributed into RIP. |
|
Sets default metric values for routes redistributed from other protocols into RIP. |
To limit the number of routes redistributed into Open Shortest Path First (OSPF), use the redistribute maximum-prefix command. To return to the default setting, use the no form of this command.
redistribute maximum-prefix max [ threshold ] [ warning-only | withdraw [ num-retries timeout ]]
no redistribute maximum-prefix max [ threshold ] [ warning-only | withdraw [ num-retries timeout ]
Router configuration
VRF configuration
|
|
---|---|
Use the redistribute maximum-prefix command to limit the number of routes redistributed into OSPF. Use the clear ip ospf redistribute command if all routes are withdrawn.
This example shows how to limit the number of redistributed routes into OSPF:
|
|
---|---|
To limit the number of routes redistributed into Enhanced Interior Gateway Routing Protocol (EIGRP), use the redistribute maximum-prefix command. To return to the default setting, use the no form of this command.
redistribute maximum-prefix max [ threshold ] [ warning-only | withdraw [ num-retries timeout ]]
no redistribute maximum-prefix max [ threshold ] [ warning-only | withdraw [ num-retries timeout ]
Router configuration
VRF configuration
|
|
---|---|
Use the redistribute maximum-prefix command to limit the number of routes redistributed into IEIGR. Use the clear ip eigrp redistribute command if all routes are withdrawn.
This example shows how to limit the number of redistributed routes into EIGRP:
|
|
---|---|
To limit the number of routes redistributed into Intermediate System to Intermediate System (IS-IS), use the redistribute maximum-prefix command. To return to the default setting, use the no form of this command.
redistribute maximum-prefix max [ threshold ] [ warning-only | withdraw [ num-retries timeout ]]
no redistribute maximum-prefix max [ threshold ] [ warning-only | withdraw [ num-retries timeout ]
Router configuration
VRF configuration
|
|
---|---|
Use the redistribute maximum-prefix command to limit the number of routes redistributed into IS-IS. Use the clear isis redistribute command if all routes are withdrawn.
This example shows how to limit the number of redistributed routes into IS-IS:
|
|
---|---|
To redistribute the default route, use the redistribute static route-map allow command.
redistribute static route-map allow
|
|
---|---|
This example shows how to redistributes the default route:
|
|
---|---|
Enters router map configuration mode and defines the conditions for redistributing routes. |
To change the reference bandwidth used to assign the IS-IS cost, use the reference-bandwidth command. To return to the default setting, use the no form of this command.
reference-bandwidth { gbps | mbps} [gbps | mbps ]
Reference bandwidth in gigabits per second (gbps). Range: 1 to 4000. Default: 40. |
|
Reference bandwidth in megabits per second (mbps). Range: 1 to 4000000. Default: 40000. |
|
Router configuration
VRF configuration
|
|
---|---|
If you do not enter the gbps or the mbps keyword, Mbps is the default.
The cost of interfaces is calculated by comparing the interface bandwidth with a reference bandwidth. The reference-bandwidth command configures the reference bandwidth.
This example shows how to set the reference bandwidth to 3500 Gbps:
This example shows how to return to the default reference bandwidth:
|
|
---|---|
To specify the autonomous system (AS) number for a neighbor, use the remote-as command. To remove an AS number, use the no form of this command.
AS number. The format is x for a two-byte value or x.x for a four-byte value. The range is from 1 to 65535. |
|
|
---|---|
This example shows how to configure the neighbor AS number:
|
|
To specify the time between link-state advertisement (LSA) retransmissions for adjacencies that belong to the virtual link, use the retransmit-interval command. To return to the default, use the no form of this command.
|
|
---|---|
Use the retransmit-interval command to set the LSA retransmission time. If a router receives no acknowledgment that an LSA was received, the router resends the LSA at the retransmission interval.
This example shows how to set the retransmit interval value to 8 seconds:
|
|
---|---|
To specify the time between link-state advertisement (LSA) retransmissions for adjacencies that belong to the virtual link, use the retransmit-interval command. To return to the default, use the no form of this command.
|
|
---|---|
Use the retransmit-interval command to set the LSA retransmission time. If a router receives no acknowledgment that an LSA was received, the router resends the LSA at the retransmission interval.
This example shows how to set the retransmit interval value to 8 seconds:
|
|
---|---|
To configure RFC 1583 compatibility as the method used to calculate summary route costs and select AS-external paths, use the rfc1583compatibility command. To disable RFC 1583 compatibility, use the no form of this command.
|
|
---|---|
To minimize the chance of routing loops, all Open Shortest Path First (OSPF) routers in an OSPF routing domain should have RFC compatibility set identically.
OSPFv2 on Cisco NX-OS supports RFC 2328. This RFC introduced a different method to calculate route summary costs which is not compatible with the calculation used by RFC1583. RFC 2328 also introduced different selection criteria for AS-external paths. It is important to ensure that all routers support the same RFC. Use the rfc1583compatibility command if your network includes routers that are only compliant with RFC1583. The default supported RFC standard for OSPFv2 may be different for Cisco NX-OS and Cisco IOS. You must make adjustments to set the values identically. For more OSPF RFC Compatibility Mode example, see the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x.
You must configure RFC 1583 compatibility on any virtual routing and forwarding (VRF) that connects to routers running only RFC1583 compatible OSPF.
Note The default values for Cisco NX-OS might be different from that of Cisco IOS. You should make adjustments to set the values identically.
This example shows how to specify that the router process is compatible with RFC 1583:
To create a route map, enter the route-map configuration mode, or define the conditions for redistributing routes from one routing protocol into another, use the route-map command. To delete an entry, use the no form of this command.
route-map map-tag [ deny | permit ] [ sequence-number ]
no route-map map-tag [ permit | deny ] [ sequence-number ]
|
|
---|---|
You must enter the feature pbr global configuration mode command to enable PBR before entering the route-map command.
Use the route-map command to enter route-map configuration mode. Once you enter the route-map command, the prompt changes to the following:
switch(config-route-map)#
If you make changes to a route map that is used by a client, you must exit the route-map configuration submode before the changes take effect in the client. The route-map changes are not propagated to its clients until you exit from the route-map configuration submode or 60 seconds expires since entering the submode.
Once you enter the route-map configuration mode, the following keywords are available:
– as-path name [ name ] —Specifies the autonomous system (AS) path access list to match. The name can be any alphanumeric string up to 63 characters. See the match as-path command for additional information.
– community name [ name | exact-match ]— Specifies the BGP community list name to match. See the match community command for additional information.
– ip —Configures the IPv4 features. The follow keywords and arguments are available:
address { access-list-name [ access-list-name ] | prefix-list ipv4-list-name [ ipv4-list-name ]}— Specifies the address of the route or packet to match. See the match ip address command for additional information.
multicast { group address/length | rp address/length }—Specifies the multicast attributes to match. See the match ip multicast command for additional information.
next-hop —Matches the next-hop address of route. See the match ip next-hop command for additional information.
route-source —Matches the advertising source address of route. See the match ip route-source command for additional information.
– ipv6 —Configures the IPv6 features. The follow keywords and arguments are available
address { access-list-name [ access-list-name ] | prefix-list ipv6-list-name [ ipv6-list-name ]}— Specifies the address of the route or packet to match. See the match ipv6 address prefix-list command for additional information.
Note The IPv6 access-list name is for use in route-maps for PBR only.
multicast { group address/length | rp address/length }—Specifies the multicast attributes to match. See the match ipv6 multicast command for additional information.
next-hop prefix-list —Matches the next-hop address of route. See the match ipv6 next-hop prefix-list command for additional information.
route-source —Matches the advertising source address of route. See the match ipv6 route-source prefix-list command for additional information.
– length minimum-length maximum-length —Defines the minimum and maximum packet length. See the match length command for additional information.
– route-type —Matches the route-type of the route. See the match route-type command for additional information.
– tag —Matches the metric of route. See the match tag command for additional information.
Note The default-information originate command ignores match statements in the optional route map.
– as-path —Prepends a string for a BGP AS-path attribute. See the set as-path command for additional information.
– comm-list —Sets the BGP community list (for deletion). See the set comm-list command for additional information.
– community —Sets the BGP community attribute. See the set community command for additional information.
– dampening —Sets the BGP route flap dampening parameters. See the set dampening command for additional information.
– forwarding-address —Sets the forwarding address. See the set forwarding-address command for additional information.
– ip —Configures the IP features. The following keywords and arguments are available:
set ip default next-hop —Indicates where to output packets that pass a match clause of a route map for policy routing and for which the Cisco NX-OS software has no explicit route to a destination. See the set ip default next-hop command for additional information.
set ip next-hop —Indicates where to output packets that pass a match clause of a route map for policy routing. See the set ip next-hop command for additional information.
– ipv6 —Configures the IPv6 features. The following keywords and arguments are available:
set ipv6 default next-hop —Indicates where to output packets that pass a match clause of a route map for policy routing and for which the Cisco NX-OS software has no explicit route to a destination. See the set ipv6 default next-hop command for additional information.
set ipv6 next-hop —Indicates where to output packets that pass a match clause of a route map for policy routing. See the set ipv6 next-hop command for additional information.
– level —Specifies where to import the route. See the set level command for additional information.
– local-preference —Specifies the BGP local preference path attribute. See the set local-preference command for additional information.
– metric —Sets the metric for destination routing protocol. See the set metric command for additional information.
– metric-type —Sets the type of metric for destination routing protocol. See the set metric-type command for additional information.
– origin —Specifies the BGP origin code. See the set origin command for additional information.
– tag —Specifies the tag value for destination routing protocol. See the set tag command for additional information.
– vrf —Sets the VRF for next-hop resolution. See the set vrf command for additional information.
– weight —Sets the BGP weight for the routing table. See the set weight command for additional information.
Use route maps to redistribute routes or to subject packets to policy routing. Both purposes are described in this section.
The redistribute router configuration command uses the map-tag name to reference the route map. Multiple route maps may share the same map tag name.
Use the route-map global configuration command, and the match and set route-map configuration commands, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria —the conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actions —the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the 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 relating to a route-map command will be ignored; that is, the route will not be advertised for outbound route maps and will not be accepted for inbound route maps. If you want to modify only some data, you must configure a second route map section with an explicit match specified.
Use the ip policy route-map command, in addition to the route-map command, and the match and set commands to define the conditions for policy routing packets. The match commands specify the conditions under which policy routing occurs. The set commands specify the routing actions to perform if the criteria enforced by the match commands are met. You might want to policy route packets some way other than the obvious shortest path.
The guidelines for the sequence-number argument are as follows:
1. If no entry is defined with the supplied tag, an entry is created with the sequence-number argument set to 10.
2. If only one entry is defined with the supplied tag, that entry becomes the default entry for the following route-map command. The sequence-number argument of this entry is unchanged.
3. If more than one entry is defined with the supplied tag, an error message is printed to indicate that the sequence-number argument is required.
If the no route-map map-tag command is specified (with no sequence-number argument), the whole route map is deleted.
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 will be redistributed into OSPF as external link-state advertisements (LSAs) with a metric type of Type 1, and a tag equal to 1.
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
This example for IPv6 shows how to redistribute Routing Information Protocol (RIP) routes with a hop count equal to 1 into Open Shortest Path First (OSPF). These routes will be redistributed into OSPF as external link-state advertisements (LSAs) with a tag equal to 42 and a metric type equal to type1.
switch(config
)# router 1
switch(config
-route-map)# redistribute rip one route-map ripng-to-ospfv3
switch(config
)# route-map ripng-to-ospfv3
switch(config
-route-map)# match tag 42
switch(config
-route-map)# set metric-type type1
This example sets the autonomous system path to match BGP autonomous system path access list 20:
switch(config
)# route-map IGP2BGP
switch(config
-route-map)# match as-path 20
This example shows how to configure that the routes matching community list 1 will have the weight set to 100. Any route that has community 109 will have the weight set to 100.
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
This example shows how to configure that the routes matching community list 1 will have the weight set to 200. Any route that has community 109 alone will have the weight set to 200.
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
This example shows how to configure that the routes match community list LIST_NAME will have the weight set to 100. Any route that has community 101 alone will have the weight set to 100.
switch(config
)# ip community-list 1 permit 101
switch(config
)# route-map set_weight
switch(config
-route-map)# match community LIST_NAME
switch(config
-route-map)# set weight 100
To set the Border Gateway Protocol (BGP) route dampening factors, use the route-map command. To disable this function, use the no form of this command.
half-life reuse suppress max-suppress-time
half-life reuse suppress max-suppress-time
Route-map configuration (config-route-map)
|
|
---|---|
Use the route-map command, and the match and set to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria —the conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actions —the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
When a BGP peer is reset, the route is withdrawn and the flap statistics cleared. In this instance, the withdrawal does not incur a penalty even though route flap dampening is enabled.
This example shows how to set the half life to 30 minutes, the reuse value to 1500, the suppress value to 10000; and the maximum suppress time to 120 minutes:
switch(config)#
route-map test1 10 permit
switch(config
-route-map)# 30 1500 10000 120
To enter router map configuration mode and define the conditions for redistributing routes, use the route-map allow permit command. To delete the configuration for redistributing routes, use the no form of this command.
|
|
---|---|
This example shows how to enter router map configuration mode and define the conditions for redistributing routes:
This example shows how to delete the configuration for redistributing routes:
|
|
---|---|
Enters Border Gateway Protocol (BGP) configuration mode and assigns the autonomous system number to the local BGP speaker. |
To enable policy-based statistics for a route map, use the route-map pbr statistics command. To disable statistics, use the no form of this command.
no route-map name pbr-statistics
Name of the route map. The name can be any alphanumeric string up to 63 characters. |
|
|
Use the route-map pbr-statistics command to enable policy-based routing statistics. You must enable policy-based routing with the feature pbr command before you can enable policy-based routing statistics.
Note This command may fail if the same interface is configured for some other policy such as ACLs.
This example shows how to enable the policy-based routing statistics for a route map:
|
|
---|---|
To assign an autonomous system (AS) number to a router and enter the router BGP configuration mode, use the router bgp command. To remove an AS number assignment, use the no form of this command.
router bgp as-num [ . as-num ]
no router bgp as-num [ . as-num ]
Address-family configuration
Neighbor address-family configuration
Router BGP configuration
The as-num is the number for the local BGP speaker and allows you to create a unique identifier for the BGP process on the router.
Once you enter the router BGP configuration mode, the following parameters are available:
The confederation command is used to configure a single autonomous system number to identify a group of smaller autonomous systems as a single confederation.You can use a confederation to divide a large single autonomous system into multiple subautonomous systems and then group them into a single confederation. The subautonomous systems within the confederation exchange routing information. External peers interact with the confederation as if it is a single autonomous system.
Each subautonomous system is fully meshed within itself and has a few connections to other autonomous systems within the confederation. Next hop, Multi Exit Discriminator (MED), and local preference information is preserved throughout the confederation, allowing you enables to you to retain a single Interior Gateway Protocol (IGP) for all the autonomous systems.
The fast-external-fallover command is used to disable or enable fast external fallover for BGP peering sessions with directly connected external peers. The session is immediately reset if link goes down. Only directly connected peering sessions are supported.
If BGP fast external fallover is disabled, the BGP routing process will wait until the default hold timer expires (three keepalives) to reset the peering session.
Using the log-neighbor-changes command to enable status change message logging does not cause a substantial performance impact, unlike, for example, enabling per BGP update debugging. If the UNIX syslog facility is enabled, messages are sent to the UNIX host running the syslog daemon so that the messages can be stored and archived. If the UNIX syslog facility is not enabled, the status change messages are retained in the internal buffer of the router, and are not stored to disk. You can set the size of this buffer, which is dependent upon the available RAM, using the logging buffered command.
The neighbor status change messages are not tracked if the bgp log-neighbor-changes command is not enabled, except for the reset reason, which is always available as output of the show ip bgp neighbors and show bgp ipv6 neighbors commands.
The eigrp log-neighbor-changes command enables logging of Enhanced Interior Gateway Routing Protocol (EIGRP) neighbor adjacencies, but messages for BGP neighbors are logged only if they are specifically enabled with the bgp log-neighbor-changes command.
Use the show logging command to display the log for the BGP neighbor changes.
– bestpath-limit interval —Configures the timeout for first bestpath after restart in seconds. Range: 1 to 3600. Default: 300.
– bgp interval —Configures the different BGP keepalive and holdtimes in seconds. Range: 0 to 3600. Default: 60.
– prefix-peer-timeout interval —Configures how long a prefix peer is maintained in seconds. Range: 0 to 1200. Default: 300:
This example shows how to configure a BGP process for autonomous system 120:
This example shows how to log neighbor changes for BGP in router configuration mode:
In This example, the BGP fast external fallover feature is disabled. If the link through which this session is carried flaps, the connection will not be reset.
In This example, all incoming updates from eBGP peers are examined to ensure that the first autonomous system number in the AS_PATH is the local AS number of the transmitting peer. In the follow example, updates from the 10.100.0.1 peer will be discarded if the first AS number is not 65001.
To configure a routing process and enter router configuration mode for Enhanced Interior Gateway Routing Protocol (EIGRP), use the router eigrp command. To turn off the EIGRP routing process, use the no form of this command.
Name of an EIGRP instance. The instance-tag can be any case-sensitive, alphanumeric string up to 20 characters. |
|
|
---|---|
This example shows how to configure a routing process for EIGRP:
|
|
---|---|
Configures the default metric for routes redistributed into EIGRP. |
|
To configure a routing process and enter router configuration mode for Intermediate System to Intermediate System (IS-IS), use the router isis command. To turn off the IS-IS routing process, use the no form of this command.
Instance name. The name can be any alphanumeric string up to 20 characters. |
|
|
---|---|
This example shows how to configure a routing process for IS-IS:
|
|
---|---|
To configure an Open Shortest Path First (OSPF) routing instance, use the router ospf command. To terminate an OSPF routing process, use the no form of this command.
Internally used identification parameter for an OSPF routing instance. It is locally assigned and can be any word or positive integer. The instance-tag argument can be any alphanumeric string. |
|
|
---|---|
Use the router ospf command to specify multiple OSPF routing instances in each router.
This example shows how to configure a basic OSPF instance:
To configure an Open Shortest Path First (OSPF) process tag, use the router ospf p1 command. To terminate an OSPF process tag, use the no form of this command.
|
|
---|---|
This example shows how to configure an Open Shortest Path First (OSPF) process tag:
To configure an Open Shortest Path First version 3 (OSPFv3) routing instance, use the router ospfv3 command. To terminate an OSPFv3 routing process, use the no form of this command.
Internally used identification parameter for an OSPFv3 routing instance. It is locally assigned and can be any word or positive integer. The instance-tag argument can be any alphanumeric string. |
|
|
---|---|
Use the router ospfv3 command to specify multiple OSPFv3 routing instances in each router.
This example shows how to configure a basic OSPFv3 instance:
To configure the Routing Information Protocol (RIP) routing process, use the router rip command. To turn off the RIP routing process, use the no form of this command.
|
|
---|---|
This example shows how to begin the RIP routing process:
|
|
To configure a router ID for an Enhanced Interior Gateway Routing Protocol (EIGRP) process, use the router-id command. To cause the software to use the default method of determining the router ID, use the no form of this command.
32-bit router ID value specified in four-part, dotted-decimal notation. |
If this command is not configured, EIGRP chooses an IPv4 address as the router ID from one of its interfaces.
Address family configuration
Router configuration
Router VRF configuration
|
|
---|---|
Use the router-id command to manually specify a unique 32-bit numeric value for the router ID. This action ensures that EIGRP can function regardless of the interface address configuration.
This example shows how to assign the IP address of 192.0.2.1 to the EIGRP process 1:
To use a fixed router ID for an Open Shortest Path First (OSPF) instance, use the router-id command. To revert to the previous OSPF router ID behavior, use the no form of this command.
If this command is not configured, OSPF chooses an IPv4 address as the router ID from one of its interfaces.
|
|
---|---|
Use the router-id command to manually specify a unique 32-bit numeric value for the router ID.
If this command is used on an OSPF instance that has neighbors, the connections to the neighbors are re-established and the new router ID is available immediately for use by OSPF.
This example shows how to configure the router ID:
|
|
---|---|
To use a fixed router ID for an Open Shortest Path First version 3 (OSPFv3) instance, use the router-id command. To revert to the previous OSPFv3 router ID behavior, use the no form of this command.
If this command is not configured, OSPFv3 chooses an IPv4 address as the router ID from one of its interfaces.
|
|
---|---|
Use the router-id command to manually specify a unique 32-bit numeric value for the router ID.
If this command is used on an OSPFv3 instance that has neighbors, the connections to the neighbors are re-established and the new router ID is available immediately for use by OSPFv3.
This example shows how to configure the router ID:
|
|
---|---|
To set the virtual routing and forwarding (VRF) scope for all EXEC commands, use the routing-context vrf command. To revert to default behavior, use the no form of this command.
no routing-context vrf vrf-name
Name of the VRF instance. The name can be any case-sensitive, alphanumeric string up to 63 characters. |
|
|
---|---|
Use the routing-context vrf command to set the VRF scope for all EXEC commands (for example, show commands). This automatically restricts the scope of the output of EXEC commands to the configured VRF. You can override this scope by using the VRF keywords available for some EXEC commands.
This example shows how to limit EXEC commands to the management VRF:
|
|
---|---|