zNetLaB › Guided labs › Data Center
vPC pair to a downstream switch
Data Center Advanced 5 devices 5 checked tasks 100 points Plan lab
Two Nexus switches act as one LACP partner for an access switch. Build the keepalive in its own VRF, the peer-link, and vPC 20, then prove a host behind the access switch reaches a router on the first Nexus. 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
Two Nexus switches act as one LACP partner for an access switch. Build the keepalive in its own VRF, the peer-link, and vPC 20, then prove a host behind the access switch reaches a router on the first Nexus.
Your role: a network engineer. Level: Advanced Done when: all 5 goals show as passed (100 points).
Network status
Devices: 3 switchs, 2 routers, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. S1, S2, AC, H, RT start with an empty configuration.
Known problems
None: nothing is misconfigured. The network is simply not finished: what the goals list is what you have to build or secure.
Goals
The peers form an adjacency with a live keepalive (25 pts) S1 is the primary (15 pts) vPC 20 is up (20 pts) The access switch bundles both uplinks into one port-channel (20 pts) The host reaches the router on S1 (20 pts)
The activity, in order
The peers form an adjacency with a live keepalive Enable feature vpc and lacp, put Ethernet1/1 in VRF KA with an address, and point peer-keepalive at the other switch in that VRF; bundle Ethernet1/2-3 as port-channel1 and make it the vpc peer-link.Why: Each goal is a state the lab can check on the running device. Verify with: show vpc S1 is the primary Give S1 the lower role priority (100) and S2 a higher one (200).Why: Each goal is a state the lab can check on the running device. Verify with: show vpc role vPC 20 is up On both peers make port-channel20 a trunk with vpc 20 and put Ethernet1/4 in it with LACP active.Why: Each goal is a state the lab can check on the running device. Verify with: show vpc The access switch bundles both uplinks into one port-channel On AC put Gi1/0/1 and Gi1/0/2 in channel-group 1 mode active as a trunk; it sees the pair as one partner.Why: Each goal is a state the lab can check on the running device. Verify with: show etherchannel summary The host reaches the router on S1 VLAN 10 on every switch, the host port on AC and the router port on S1 in VLAN 10, then ping.Why: Each goal is a state the lab can check on the running device. Verify with: ping 192.168.10.1
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
Two Nexus switches act as one LACP partner for an access switch. Build the keepalive in its own VRF, the peer-link, and vPC 20, then prove a host behind the access switch reaches a router on the first Nexus.
What you will be able to do
The peers form an adjacency with a live keepalive
S1 is the primary
vPC 20 is up
The access switch bundles both uplinks into one port-channel
The network
Nexus 9300, Catalyst 9300-24, Catalyst 8000V — 5 devices in all, already cabled.
Eth1/1 Eth1/1 Eth1/2 Eth1/2 Eth1/3 Eth1/3 Eth1/4 Gi1/0/1 Eth1/4 Gi1/0/2 Gi1/0/3 Gi1 Eth1/5 Gi1 S1 S2 AC H RT Drawn from this lab: devices, cables, ports and the addresses already set.
Device Model Address already set
S1 Nexus 9300 configure it
S2 Nexus 9300 configure it
AC Catalyst 9300-24 configure it
H Catalyst 8000V configure it
RT Catalyst 8000V configure it
Cabling
S1 Ethernet1/1 ↔ S2 Ethernet1/1
S1 Ethernet1/2 ↔ S2 Ethernet1/2
S1 Ethernet1/3 ↔ S2 Ethernet1/3
S1 Ethernet1/4 ↔ AC Gi1/0/1
S2 Ethernet1/4 ↔ AC Gi1/0/2
AC Gi1/0/3 ↔ H Gi1
S1 Ethernet1/5 ↔ RT Gi1
What is configured at the start
Nothing is configured to start with beyond the addresses above: you build the configuration from a clean start.
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 The peers form an adjacency with a live keepalive 25 On S1: show vpc output matches peer adjacency formed ok. and On S1: show vpc output matches peer is alive.
2 S1 is the primary 15 On S1: show vpc output matches role\s*:\s*primary.
3 vPC 20 is up 20 On S1: show vpc output matches 20\s+Po20\s+up.
4 The access switch bundles both uplinks into one port-channel 20 On AC: show etherchannel summary output matches Gi1/0/1\(P\)\s+Gi1/0/2\(P\).
5 The host reaches the router on S1 20 On H: ping 192.168.10.1 must succeed.
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:
S1 feature vpc
feature lacp
vlan 10
exit
vrf context KA
exit
interface Ethernet1/1
no switchport
vrf member KA
ip address 10.99.0.1/24
no shutdown
exit
vpc domain 1
role priority 100
peer-keepalive destination 10.99.0.2 source 10.99.0.1 vrf KA
exit
interface port-channel1
switchport
switchport mode trunk
vpc peer-link
exit
interface Ethernet1/2-3
switchport
switchport mode trunk
channel-group 1 mode active
no shutdown
exit
interface port-channel20
switchport
switchport mode trunk
vpc 20
exit
interface Ethernet1/4
switchport
switchport mode trunk
channel-group 20 mode active
no shutdown
exit
interface Ethernet1/5
switchport
switchport access vlan 10
no shutdown
exit
S2 feature vpc
feature lacp
vlan 10
exit
vrf context KA
exit
interface Ethernet1/1
no switchport
vrf member KA
ip address 10.99.0.2/24
no shutdown
exit
vpc domain 1
role priority 200
peer-keepalive destination 10.99.0.1 source 10.99.0.2 vrf KA
exit
interface port-channel1
switchport
switchport mode trunk
vpc peer-link
exit
interface Ethernet1/2-3
switchport
switchport mode trunk
channel-group 1 mode active
no shutdown
exit
interface port-channel20
switchport
switchport mode trunk
vpc 20
exit
interface Ethernet1/4
switchport
switchport mode trunk
channel-group 20 mode active
no shutdown
exit
AC vlan 10
exit
interface range GigabitEthernet1/0/1 - 2
switchport mode trunk
channel-group 1 mode active
no shutdown
exit
interface GigabitEthernet1/0/3
switchport access vlan 10
no shutdown
exit
H interface GigabitEthernet1
ip address 192.168.10.5 255.255.255.0
no shutdown
exit
RT interface GigabitEthernet1
ip address 192.168.10.1 255.255.255.0
no shutdown
exit
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