Skip to main content

OSPF Adjacency Stuck in EXSTART on Cisco IOS XR – Issue and Solution

In a recent lab setup using Cisco IOS XR on EVE-NG, I faced a common but frustrating issue with OSPF adjacencies getting stuck in the EXSTART state. After spending considerable time troubleshooting interface MTUs and configurations, I discovered that the root cause was related to the virtual network interface type being used. This post outlines the issue, troubleshooting steps, and the eventual solution that got everything working.

Issue:

While configuring OSPF between two routers running Cisco IOS XR in my lab, OSPF adjacencies were getting stuck in the EXSTART state. I verified that interface configurations, MTU settings, and OSPF parameters were correct, but the problem persisted. I tried adjusting the MTU size, using the mtu-ignore command, and even checked for ACLs, but nothing seemed to resolve the issue.

Troubleshooting Steps:

  1. MTU Settings: I started by verifying that both sides of the OSPF adjacency had matching MTUs. I used the default MTU and even tried different values with mtu-ignore, but the issue remained.

  2. OSPF Configuration: I ensured that the OSPF network type was set to point-to-point and double-checked the OSPF process configurations, but still no luck.

  3. Logs & Debugs: I ran debug ip ospf to trace the OSPF process, which consistently showed that the neighbor was stuck in EXSTART due to DBD retransmissions.

  4. Interface Type: Finally, I looked into the type of virtual network interface being used in the EVE-NG topology. By default, the interfaces were set to virtio-net-pc, which I suspected could be causing some compatibility issues with Cisco IOS XR.

Solution:

After several hours of troubleshooting, the breakthrough came from changing the interface type in EVE-NG. I switched the interfaces from virtio-net-pc to e1000, which is widely supported and stable. Once the change was made, the OSPF adjacency came up immediately, and everything worked as expected.

Conclusion:

This issue highlights the importance of considering all aspects of virtual environments, including the type of interfaces in use. If you're using Cisco IOS XR in EVE-NG and facing similar OSPF adjacency issues, make sure to check the interface type and switch to e1000. This simple change saved me a lot of time and solved the problem instantly.

Key Takeaway: Always consider the interface type when working with virtual labs in EVE-NG, especially with Cisco IOS XR. It might save you hours of troubleshooting!

Labels:

Comments

Post a Comment

Popular posts from this blog

Basic MPLS BGP and L3VPN Lab Setup

In this lab, we’ve set up a basic MPLS, BGP, and L3VPN environment, which is a great foundation for understanding how service providers build scalable networks. The lab uses the EVE-NG simulator along with Router IOS C7200-ADVENTERPRISEK9-M, Version 15.2(4)M8 to emulate a realistic MPLS environment. Below is a summary of the key components and roles of each router in the lab. MPLS Core Routers : The MPLS core consists of the routers responsible for label switching and forwarding customer traffic through the network: PE1 (Provider Edge 1) : Connects customer networks to the MPLS core and handles both MPLS and BGP routing. It also hosts VRF (Virtual Routing and Forwarding) instances for customers. PE2 (Provider Edge 2) : Functions similarly to PE1, connecting another customer network to the MPLS core. P1 (Core Router 1) and P2 (Core Router 2) : These routers serve as MPLS core routers and handle label switching but do not store or process customer routes directly. They simply f
Post a Comment
Read more

How to Properly Clone an EVE-NG Lab with Configurations

Cloning labs in EVE-NG is a great way to duplicate setups and expand or experiment on a new copy without affecting the original lab. However, if not done correctly, the cloned lab may only copy the topology without configurations. In this guide, I’ll show you how to properly clone a lab in EVE-NG with all configurations using the EVE-NG GUI . Follow these steps to ensure that both the topology and router configurations are retained when cloning your lab. Steps to Clone an EVE-NG Lab with Configurations Save Running Configuration on All Devices In your original lab, make sure all devices have their configurations saved to NVRAM. Go into the CLI of each router and run the command: copy running-config startup-config Export All Configurations (CFGs) On the left sidebar in the EVE-NG Web UI , click on the "More Actions" option. Then select "Export all CFGs" . This step exports the configurations of all devices in the lab. Shutdown All Devices After exporting the confi
Post a Comment
Read more