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 Routing Policy on Cisco IOS XR Software
Information About Implementing Routing Policy
RC-218
Cisco IOS XR Routing Configuration Guide
Policy four could be rewritten in an equivalent way as follows:
route-policy four-equivalent
set weight 100
set med 200
set community (2:666) additive
pass
end-policy
Note The pass statement is not required and can be removed to represent the equivalent policy in another way.
Policy Verification
Several different types of verification occur when policies are being defined and used.
Range Checking
As policies are being defined, some simple verifications, such as range checking of values, is done. For
example, the MED that is being set is checked to verify that it is in a proper range for the MED attribute.
However, this range checking cannot cover parameter specifications because they may not have defined
values yet. These parameter specifications are verified when a policy is attached to an attach point. The
policy repository also verifies that there are no recursive definitions of policy, and that parameter
numbers are correct. At attach time, all policies must be well formed. All sets and policies that they
reference must be defined and have valid values. Likewise, any parameter values must also be in the
proper ranges.
Incomplete Policy and Set References
As long as a given policy is not attached at an attach point, the policy is allowed to refer to nonexistent
sets and policies, which allows for freedom of workflow. You can build configurations that reference sets
or policy blocks that are not yet defined, and then can later fill in those undefined policies and sets,
thereby achieving much greater flexibility in policy definition. Every piece of policy you want to
reference while defining a policy need not exist in the configuration. Thus, a user can define a policy
sample that references the policy bar using an apply statement even if the policy bar does not exist.
Similarly, a user can enter a policy statement that refers to a nonexistent set.
However, the existence of all referenced policies and sets is enforced when a policy is attached. If you
attempt to attach the policy sample with the reference to an undefined policy bar at an inbound BGP
policy using the neighbor 1.2.3.4 address-family ipv4 unicast policy sample in command, the
configuration attempt is rejected because the policy bar does not exist.
Likewise, you cannot remove a route policy or set that is currently in use at an attach point because this
removal would result in an undefined reference. An attempt to remove a route policy or set that is
currently in use results in an error message to the user.
A condition exists that is referred to as a null policy in which the policy bar exists but has no statements,
actions, or dispositions in it. In other words, the policy bar does exist as follows:
route-policy bar
end-policy
This is a valid policy block. It effectively forces all routes to be dropped because it is a policy block that
never modifies a route, nor does it include the pass statement. Thus, the default action of drop for the
policy block is followed.