Octet

A data center VLAN flap resets EIGRP neighbors at dozens of branches

IncidentExpert

The ticket

The company has 60 branches on DMVPN. Each branch router has two tunnels: Tunnel0 to HUB1 (172.16.0.0/24) and Tunnel1 to HUB2 (172.17.0.0/24). Everything runs classic EIGRP AS 100. The hubs send the full routing table to every branch, and no branch is configured as a stub.

At 09:12 the server VLAN 10.50.8.0/24 on DSW1 in the data center flapped for a few seconds. For the next two minutes, users at more than 20 branches lost every application, not just the servers in that VLAN. HUB1's log is full of lines like this:

Output
%DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 172.16.0.27 (Tunnel0) is down: stuck in active

You are on the incident bridge. The same thing happened last month.

Gi1/0/3Gi1/0/1Gi0/0/0Gi1/0/2Gi0/0/0Tu0Tu0Tu0Tu1Tu1Tu1CORE1DSW110.50.8.0/24 flappedHUB1HUB2BR1BR27on LTE backupBR60

Book 3.4 Routing

Step 1 of 4

At 09:40 the VLAN flaps again while you are logged in to CORE1. What do you run first?