Specifications

Implementing Static Routes on Cisco IOS XR Software
Contents
RC-404
Cisco IOS XR Routing Configuration Guide
Contents
• Prerequisites for Implementing Static Routes on Cisco IOS XR Software, page RC-404
• Information About Implementing Static Routes on Cisco IOS XR Software, page RC-404
• How to Implement Static Routes on Cisco IOS XR Software, page RC-408
• Configuration Examples, page RC-416
• Where to Go Next, page RC-417
• Additional References, page RC-417
Prerequisites for Implementing Static Routes on Cisco IOS XR
Software
You must be in a user group associated with a task group that includes the proper task IDs for static
routing commands. For detailed information about user groups and task IDs, see the Configuring AAA
Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Information About Implementing Static Routes on Cisco IOS XR
Software
To implement static routes you need to understand the following concepts:
• Static Route Functional Overview, page RC-404
• Default Administrative Distance, page RC-405
• Directly Connected Routes, page RC-405
• Recursive Static Routes, page RC-406
• Fully Specified Static Routes, page RC-406
• Floating Static Routes, page RC-407
• Default VRF, page RC-407
• IPv4 and IPv6 Static VRF Routes, page RC-407
• IPv6/IPv6 VPN Provider Edge Transport over MPLS, page RC-407
Static Route Functional Overview
Static routes are entirely user configurable and can point to a next-hop interface, next-hop IP address, or
both. In Cisco IOS XR software, if an interface was specified, then the static route is installed in the
Routing Information Base (RIB) if the interface is reachable. If an interface was not specified, the route
is installed if the next-hop address is reachable. The only exception to this configuration is when a static
route is configured with the permanent attribute, in which case it is installed in RIB regardless of
reachability.