zNetLaB › Guided labs › Data Center
Troubleshoot: EOS MLAG that stays inactive
Data Center Advanced 3 devices 2 checked tasks 100 points Plan lab
The peer-link and the local VLAN are up and the peers ping each other, but MLAG never becomes active. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This lab is part of the full simulator: open it free for 7 days with a new account, then with a plan. It needs an account, which keeps your progress.
The scenario
The peer-link and the local VLAN are up and the peers ping each other, but MLAG never becomes active.
Your role: a network engineer. Level: Advanced Done when: all 2 goals show as passed (100 points).
Network status
Devices: 3 routers, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. A1 starts with and VLAN 10, VLAN 4094, EtherChannel, OSPF 1, BGP 65001 already configured. A2 starts with and VLAN 10, VLAN 4094, EtherChannel, OSPF 1 already configured. A3 starts with and BGP 65003 already configured.
Known problems
The network worked and now does not: the scenario above says what users report. The cause is a configuration fault, not a cable. Find it with show commands (interfaces, routes, neighbours, running-config) before you change anything; fix only what is wrong.
Goals
MLAG is active on A1 (50 pts) A2 shows negotiation Connected (50 pts)
The activity, in order
MLAG is active on A1 A2 uses domain-id MLAG2. Set domain-id MLAG1 under mlag configuration on A2.Why: Each goal is a state the lab can check on the running device. Verify with: show mlag A2 shows negotiation Connected Both sides agree once the domain matches.Why: Each goal is a state the lab can check on the running device. Verify with: show mlag
Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong.
Why this matters
The peer-link and the local VLAN are up and the peers ping each other, but MLAG never becomes active.
What you will be able to do
MLAG is active on A1
A2 shows negotiation Connected
The network
Arista vEOS Switch — 3 devices in all, already cabled.
Eth1 Eth1 Eth2 Eth2 Eth3 Eth1 A1 A2 A3 Drawn from this lab: devices, cables, ports and the addresses already set.
Device Model Address already set
A1 Arista vEOS Switch configure it
A2 Arista vEOS Switch configure it
A3 Arista vEOS Switch configure it
Cabling
A1 Ethernet1 ↔ A2 Ethernet1
A1 Ethernet2 ↔ A2 Ethernet2
A1 Ethernet3 ↔ A3 Ethernet1
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
A1 configure
vlan 10
name Sales
vlan 4094
interface Ethernet2
switchport mode trunk
interface Vlan4094
ip address 10.99.0.1/30
interface Port-Channel10
switchport mode trunk
interface Ethernet2
channel-group 10 mode active
mlag configuration
domain-id MLAG1
local-interface Vlan4094
peer-address 10.99.0.2
peer-link Port-Channel10
ip routing
interface Ethernet1
no switchport
ip address 10.12.0.1/24
ip ospf area 0.0.0.0
interface Ethernet3
no switchport
ip address 10.13.0.1/24
interface Loopback0
ip address 1.1.1.1/32
ip ospf area 0.0.0.0
router ospf 1
router-id 1.1.1.1
router bgp 65001
router-id 1.1.1.1
neighbor 10.13.0.3 remote-as 65003
network 1.1.1.1/32
A2 configure
vlan 10
name Sales
vlan 4094
interface Ethernet2
switchport mode trunk
interface Vlan4094
ip address 10.99.0.2/30
interface Port-Channel10
switchport mode trunk
interface Ethernet2
channel-group 10 mode active
mlag configuration
domain-id MLAG2
local-interface Vlan4094
peer-address 10.99.0.1
peer-link Port-Channel10
ip routing
interface Ethernet1
no switchport
ip address 10.12.0.2/24
ip ospf area 0.0.0.0
interface Loopback0
ip address 2.2.2.2/32
ip ospf area 0.0.0.0
router ospf 1
router-id 2.2.2.2
A3 configure
ip routing
interface Ethernet1
no switchport
ip address 10.13.0.3/24
interface Loopback0
ip address 3.3.3.3/32
router bgp 65003
router-id 3.3.3.3
neighbor 10.13.0.1 remote-as 65001
network 3.3.3.3/32
Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 MLAG is active on A1 50 On A1: show mlag output matches state\s+:\s+Active.
2 A2 shows negotiation Connected 50 On A2: show mlag output matches negotiation status\s+:\s+Connected.
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
A2 configure
mlag configuration
domain-id MLAG1
Related labs
Where to start
The lessons are open to everyone, all guided labs are listed by track, and
plans explains what is free and what is not.
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.
Try the simulator in your browser, no sign-up