Interfaces and Hardware Component Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

PDF

Interfaces and Hardware Component Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

Prerequisites for configuring Ethernet interfaces

Want to summarize with AI?

Log in

Lists the prerequisites that must be met before you configure Ethernet interfaces on Cisco 8000 Series Routers, including access to supported hardware, knowledge of the interface IP address, and the generalized interface naming notation.


Before configuring Ethernet interfaces, ensure that you meet the following conditions:

  • Access to Cisco 8200 series routers or Cisco 8800 series routers with at least one of the supported line cards installed.

  • Know the interface IP address.

  • Starting with Cisco IOS XR Release 24.1.1, the openconfig-if-ip.yang open config model supports a new leaf, oc-if:interfaces/oc-if:interface/oc-if:subinterfaces/oc-if:subinterface/ipv4/addresses/address[ip]/config/type. When using the openconfig-if-ip.yang model to update or revise the IP address for an interface, you must specify the IP address as either primary or secondary. You can have only one IP address as primary, but you can have multiple addresses configured as secondary.

  • Specify the generalized interface name with the standard notation of rack/slot/module/port.

An ACL-dependent feature refers to a capability in network systems that relies on Access Control Lists (ACLs) for its operation. These features include:

  • global configuration, such as Lawful Intercept (LI) and BGP Flow Specification (BGPFS)

  • interface-level configurations, such as Quality of Service with ACL (QoS-ACL), Security ACL, SPAN ACL, Qos Policy Propagation via BGP (QPPB), Policy Based Routing (PBR), Peering QoS, and L2 ACL for packets with L3 payload.

An interface, whether physical or virtual, supports the configuration of up to four ACL dependent features, such as ACLs, QoS with ACL, BGP Flow Specification, SPAN ACL, and Lawful Intercept. To add a new feature, such as Policy-Based Routing, you must first remove one of the existing features and then configure the new feature.