Use this task to verify that interfaces configured on IOS XR are programmed into the Linux kernel and that the packet I/O infrastructure provides default reachability for off-the-shelf Linux applications.
Interfaces configured on IOS XR are programmed into the Linux kernel. These interfaces allow Linux applications to run as if they were running on a regular Linux system. This packet I/O capability ensures that off-the-shelf Linux applications can be run alongside IOS XR, allowing operators to use their existing tools and automate deployments with IOS XR.
The IP address on the Linux interfaces, MTU settings, MAC (Media Access Control) address are inherited from the corresponding settings of the IOS XR interface. Accessing the global VRF (Virtual Routing and Forwarding) network namespace ensures that when you issue the bash command, the default or the global VRF in IOS XR is reflected in the kernel. This ensures default reachability based on the routing capabilities of IOS XR and the packet I/O infrastructure.
Virtual addresses can be configured to access a router from the management network such as gRPC (Google Remote Procedure Call) using a single virtual IP address. On a device with two or more RPs (Route Processors), the virtual address refers to the management interface that is currently active. This functionality can be used across RP failover without the information of which RP is currently active. This is applicable to the Linux packet path.
Automatic synchronization of secondary IPv4 and IPv6 addresses from XR to Linux OS
The secondary IPv4 and IPv6 addresses that are configured for an XR interface are now synchronized into the Linux operating system automatically. With this secondary IPv4 and IPv6 address synchronization, the third party applications that are deployed on Cisco IOS XR can now use the secondary addresses. Prior to this release, only primary IPv4 and IPv6 addresses were supported and the secondary IPv4 and IPv6 addresses had to be configured manually in the Linux operating system.
Exposed XR interfaces (EXIs) and address-only interfaces support secondary IPv4 and IPv6 address synchronization:
EXIs have secondary IP addresses added to their corresponding Linux interface
Address-only interfaces have secondary IP addresses added to the Linux loopback device. For details about address-only interfaces, see show linux networking interfaces address-only.
The restrictions of secondary IPv4 and IPv6 addresses synchronization are:
Secondary IPv4 addresses are not synchronized from Linux to XR for Linux-managed interfaces.
The ifconfig Linux command only displays the first configured IPv4 address. To view the complete list of IPv4 and IPv6 addresses, use the ip addr show Linux command.
For details about secondary IPv4 and IPV6 addresses, see ipv4 address (network) and ipv6 address.
You can run bash commands at the IOS XR router prompt to view the interfaces and IP addresses stored in global VRF. When you access the Cisco IOS XR Linux shell, you directly enter the global VRF.
Follow these steps to verify reachability of IOS XR and Packet I/O infrastructure.
Procedure
| 1. | From your Linux box, access the IOS XR console through SSH (Secure Shell), and log in. Example:
|
|
| 2. | View the ethernet interfaces on IOS XR. Example:
This output displays the IP address and the status of the active NCS 1004 interfaces.
|
|
| 3. | Check the IP and MAC addresses of the interface that is in Up state. Example:
This output shows the configuration details of the MgmtEth0/RP0/CPU0/0 interface.
|
|
| 4. | Verify that the bash command runs in global VRF to view the network interfaces. Example:
This output shows the active network interfaces in Linux.
The to_xr interface indicates access to the global VRF. |
|
| 5. | Access the Linux shell. Example:
|
|
| 6. | (Optional) View the IP routes used by the to_xr interfaces. Example:
|