Laptop User Manual
Table Of Contents
- Cisco IOS XR Routing Configuration Guide
- Contents
- Preface
- Document Revision History
- Obtaining Documentation
- Documentation Feedback
- Cisco Product Security Overview
- Obtaining Technical Assistance
- Obtaining Additional Publications and Information
- Implementing BGP on Cisco IOS XR Software
- Contents
- Prerequisites for Implementing BGP on CiscoIOSXR Software
- Information About Implementing BGP on CiscoIOSXR Software
- BGP Functional Overview
- BGP Router Identifier
- BGP Default Limits
- BGP Validation of Local Next-Hop Addresses
- BGP Configuration
- No Default Address Family
- Routing Policy Enforcement
- Table Policy
- Update Groups
- BGP Best Path Algorithm
- Multiprotocol BGP
- Route Dampening
- BGP Routing Domain Confederation
- BGP Route Reflectors
- Default Address Family for show Commands
- How to Implement BGP on CiscoIOSXR Software
- Enabling BGP Routing
- Configuring a Routing Domain Confederation for BGP
- Resetting eBGP Session Immediately Upon Link Failure
- Logging Neighbor Changes
- Adjusting BGP Timers
- Changing the BGP Default Local Preference Value
- Configuring the MED Metric for BGP
- Configuring BGP Weights
- Tuning the BGP Best Path Calculation
- Indicating BGP Backdoor Routes
- Configuring Aggregate Addresses
- Redistributing iBGP Routes into IGP
- Redistributing Prefixes into Multiprotocol BGP
- Configuring BGP Route Dampening
- Applying Policy When Updating the Routing Table
- Setting BGP Administrative Distance
- Configuring a BGP Neighbor Group
- Configuring a BGP Neighbor
- Configuring a Route Reflector for BGP
- Configuring BGP Route Filtering by Route Policy
- Disabling Next Hop Processing on BGP Updates
- Configuring BGP Community and Extended-Community Filtering
- Configuring Software to Store Updates from a Neighbor
- Disabling a BGP Neighbor
- Resetting Neighbors Using BGP Dynamic Inbound Soft Reset
- Resetting Neighbors Using BGP Outbound Soft Reset
- Resetting Neighbors Using BGP Hard Reset
- Clearing Caches, Tables and Databases
- Displaying System and Network Statistics
- Monitoring BGP Update Groups
- Configuration Examples for Implementing BGP on CiscoIOSXR Software
- Where to Go Next
- Additional References
- Implementing IS-IS on Cisco IOS XR Software
- Contents
- Prerequisites for Implementing IS-IS on CiscoIOSXR Software
- Restrictions for Implementing IS-IS on CiscoIOSXR Software
- Information About Implementing IS-IS on CiscoIOSXR Software
- IS-IS Functional Overview
- Key Features Supported in the CiscoIOSXR IS-IS Implementation
- IS-IS Configuration Grouping
- IS-IS Interfaces
- Multitopology Configuration
- IPv6 Routing and Configuring IPv6 Addressing
- Limit LSP Flooding
- Maximum LSP Lifetime and Refresh Interval
- Overload Bit Configuration During Multitopology Operation
- Single-Topology IPv6 Support
- Multitopology IPv6 Support
- Nonstop Forwarding
- Multi-Instance IS-IS
- Multiprotocol Label Switching Traffic Engineering
- Overload Bit on Router
- Default Routes
- Attached Bit on an IS-IS Instance
- Multicast-Intact Feature
- How to Implement IS-IS on CiscoIOSXR Software
- Enabling IS-IS and Configuring Level 1 or Level 2 Routing
- Configuring Single Topology for IS-IS
- Configuring Multitopology for IS-IS
- Controlling LSP Flooding for IS-IS
- Configuring Nonstop Forwarding for IS-IS
- Configuring Authentication for IS-IS
- Configuring MPLS Traffic Engineering for IS-IS
- Tuning Adjacencies for IS-IS on Point-to-Point Interfaces
- Setting SPF Interval for a Single-Topology IPv4 and IPv6 Configuration
- Enabling Multicast-Intact for IS-IS
- Customizing Routes for IS-IS
- Configuration Examples for Implementing IS-IS on CiscoIOSXR Software
- Where to Go Next
- Additional References
- Implementing OSPF on Cisco IOS XR Software
- Contents
- Prerequisites for Implementing OSPF on CiscoIOSXR Software
- Information About Implementing OSPF on CiscoIOSXR Software
- OSPF Functional Overview
- Key Features Supported in the CiscoIOSXR OSPF Implementation
- Comparison of CiscoIOSXR OSPFv3 and OSPFv2
- Importing Addresses into OSPFv3
- OSPF Hierarchical CLI and CLI Inheritance
- OSPF Routing Components
- OSPF Process and Router ID
- Supported OSPF Network Types
- Route Authentication Methods for OSPF Version 2
- Neighbors and Adjacency for OSPF
- Designated Router (DR) for OSPF
- Default Route for OSPF
- Link-State Advertisement Types for OSPF Version 2
- Link-State Advertisement Types for OSPFv3
- Virtual Link and Transit Area for OSPF
- Route Redistribution for OSPF
- OSPF Shortest Path First Throttling
- Nonstop Forwarding for OSPF Version 2
- Load Balancing in OSPF Version 2 and OSPFv3
- Graceful Restart for OSPFv3
- Multicast-Intact Feature
- How to Implement OSPF on CiscoIOSXR Software
- Enabling OSPF
- Configuring Stub and Not-so-Stubby Area Types
- Configuring Neighbors for Nonbroadcast Networks
- Configuring Authentication at Different Hierarchical Levels for OSPF Version 2
- Controlling the Frequency that the Same LSA Is Originated or Accepted for OSPF
- Creating a Virtual Link with MD5 Authentication to Area 0 for OSPF
- Summarizing Subnetwork LSAs on an OSPF ABR
- Redistributing Routes from One IGP into OSPF
- Configuring OSPF Shortest Path First Throttling
- Configuring Nonstop Forwarding for OSPF Version 2
- Configuring OSPF Version 2 for MPLS Traffic Engineering
- Verifying OSPF Configuration and Operation
- Configuring OSPFv3 Graceful Restart
- Enabling Multicast-Intact for OSPFv2
- Configuration Examples for Implementing OSPF on CiscoIOSXR Software
- CiscoIOSXR for OSPF Version 2 Configuration: Example
- CLI Inheritance and Precedence for OSPF Version 2: Example
- MPLS TE for OSPF Version 2: Example
- ABR with Summarization for OSPFv3: Example
- ABR Stub Area for OSPFv3: Example
- ABR Totally Stub Area for OSPFv3: Example
- Route Redistribution for OSPFv3: Example
- Virtual Link Configured Through Area 1 for OSPFv3: Example
- Virtual Link Configured with MD5 Authentication for OSPF Version 2: Example
- Where to Go Next
- Additional References
- Implementing and Monitoring RIB on CiscoIOSXR Software
- Contents
- Prerequisites for Implementing RIB on CiscoIOSXR Software
- Information About RIB Configuration
- How to Deploy and Monitor RIB
- Configuration Examples for RIB Monitoring
- Output of show route Command: Example
- Output of show route backup Command: Example
- Output of show route best-local Command: Example
- Output of show route connected Command: Example
- Output of show route local Command: Example
- Output of show route longer-prefixes Command: Example
- Output of show route next-hop Command: Example
- Where to Go Next
- Additional References
- Implementing Routing Policy on Cisco IOS XR Software
- Implementing Static Routes on Cisco IOS XR Software
- Index

Implementing IS-IS on Cisco IOS XR Software
Information About Implementing IS-IS on Cisco IOS XR Software
RC-88
Cisco IOS XR Routing Configuration Guide
When single-topology support for IPv6 is used, only narrow link metrics, also known as old-style type,
length, and value (TLV) arguments, may be employed. During single-topology operation, one shortest
path first (SPF) computation for each level is used to compute both IPv4 and IPv6 routes. Using a single
SPF is possible because both IPv4 IS-IS and IPv6 IS-IS routing protocols share a common link topology.
Because multitopology is the default behavior in the software, you must explicitly configure IPv6 to use
the same topology as IPv4 enable single-topology IPv6. Configure the single-topology command in
IPv6 router address family configuration submode of the IS-IS router stanza.
Multitopology IPv6 Support
Multitopology IPv6 support on Cisco IOS XR software for IS-IS assumes that multitopology support is
required as soon as it detects interfaces configured for both IPv6 and IPv4 within the IS-IS stanza.
Nonstop Forwarding
On Cisco IOS XR software, NSF minimizes the amount of time a network is unavailable to its users
following a route processor (RP) failover. The main objective of NSF is to continue forwarding IP
packets and perform a graceful restart following an RP failover.
When a router restarts, all routing peers of that device usually detect that the device went down and then
came back up. This transition results in what is called a routing flap, which could spread across multiple
routing domains. Routing flaps caused by routing restarts create routing instabilities, which are
detrimental to the overall network performance. NSF helps to suppress routing flaps in NSF-aware
devices, thus reducing network instability.
NSF allows for the forwarding of data packets to continue along known routes while the routing protocol
information is being restored following an RP failover. When the NSF feature is configured, peer
networking devices do not experience routing flaps. Data traffic is forwarded through intelligent line
cards or dual forwarding processors (FPs) while the standby RP assumes control from the failed active
RP during a failover. The ability of line cards and FPs to remain up through a failover and to be kept
current with the Forwarding Information Base (FIB) on the active RP is key to NSF operation.
When the Cisco IOS XR router running IS-IS routing performs an RP failover, the router must perform
two tasks to resynchronize its link-state database with its IS-IS neighbors. First, it must relearn the
available IS-IS neighbors on the network without causing a reset of the neighbor relationship. Second,
it must reacquire the contents of the link-state database for the network.
The IS-IS NSF feature offers two options when configuring NSF:
• IETF NSF
• Cisco NSF
If neighbor routers on a network segment are NSF aware, meaning that neighbor routers are running a
software version that supports the IETF Internet draft for router restartability, they assist an IETF NSF
router that is restarting. With IETF NSF, neighbor routers provide adjacency and link-state information
to help rebuild the routing information following a failover.
In Cisco IOS XR software, Cisco NSF checkpoints (stores persistently) all the state necessary to recover
from a restart without requiring any special cooperation from neighboring routers. The state is recovered
from the neighboring routers, but only using the standard features of the IS-IS routing protocol. This
capability makes Cisco NSF suitable for use in networks in which other routers have not used the IETF
standard implementation of NSF.