CCIE Lab Center

CLC - CCIE Data Center

v3.1: Real Lab1-DOO
CLC

Website Telegram CCIE Data Center

https://ccielabcenter.com https://t.me/ccielabcenter Real Lab1: Module2-DOO
Module2-DOO-Demo2 CLC CCIE Data Center v3.1 Real Lab1 - DOO Released: January 15, 2025

CLC
CCIE Data Center v3.1
Real Lab1: DOO-Demo2

Web: https://ccielabcenter.com | Mail: care@ccielabcenter.com | Telegram: t.me/ccielabcenter Page 1

Module2-DOO-Demo2 CLC CCIE Data Center v3.1 Real Lab1 - DOO Released: January 15, 2025

Workbook Description
Author: CCIE Lab Center (CLC)
Focus: Exam
Level: Expert (CCIE)
Stream: CCIE Data Center v3.1
Lab Version: Lab1_Module2_DOO_Demo
Document Revision: Demo2
Document Revision Date: January 15, 2025
Content: Topology | Questions | Solution | Verification
Format: PDF
Protection: Password
Website: https://ccielabcenter.com

Web: https://ccielabcenter.com | Mail: care@ccielabcenter.com | Telegram: t.me/ccielabcenter Page 2

Module2-DOO-Demo2 CLC CCIE Data Center v3.1 Real Lab1 - DOO Released: January 15, 2025

CCIE Data Center v3.1 Lab1: Module2: DOO

DOO-Demo2

Web: https://ccielabcenter.com | Mail: care@ccielabcenter.com | Telegram: t.me/ccielabcenter Page 3

Module2-DOO-Demo2 CLC CCIE Data Center v3.1 Real Lab1 - DOO Released: January 15, 2025

Lab Details
ACI Cluster Config Value
Fabric Name DC2-ACI-Pod1
Fabric ID 1
Infra VLAN ID 3967
BD Multicast (GIPO) 225.0.0.0/15
Internal TEP Pool (POD-1) **********
Internal TEP Pool (POD-2) **********
External TEP Pool (POD-1) **********
External TEP Pool (POD-2) **********

Lab Introduction
The international health care corporation, Xandar, has dramatically expanded its business over the last
couple of years through a series of acquisitions. Along with these acquisitions, they inherited the data
centers of the acquired companies, which introduced complexity and headaches for their network
***************omitted

The final design is expected to be a Cisco Nexus VXLAN EVPN Multi-Site architecture for the recently
***************omitted

The project's first phase involves migrating from and decommissioning some smaller data centers that
***************omitted

You are requested to help them meet the objectives of this initial POC phase, where they intend to test
***************omitted

The POC devices have been repurposed from a discontinued R D project, and the customer has
already configured some settings.

Web: https://ccielabcenter.com | Mail: care@ccielabcenter.com | Telegram: t.me/ccielabcenter Page 4

Module2-DOO-Demo2 CLC CCIE Data Center v3.1 Real Lab1 - DOO Released: January 15, 2025

Section-1 Guidelines:

• Unless specified in the particular task, all configurations must be completed using the Cisco
Nexus Dashboard Fabric Controller (NDFC). Manual configurations on the devices are not
permitted.
• ***************omitted

Web: https://ccielabcenter.com | Mail: care@ccielabcenter.com | Telegram: t.me/ccielabcenter Page 5

Module2-DOO-Demo2 CLC CCIE Data Center v3.1 Real Lab1 - DOO Released: January 15, 2025

Section 1.1: Introduction

Welcome to the Deploy, Operate, Optimize (DOO) module for

XANDER.

The topology you will be working on this module will be similar, but not necessarily identical, to the
network that you helped design in the previous module.

It may also include technologies and feature sets not touched upon previously.

Web: https://ccielabcenter.com | Mail: care@ccielabcenter.com | Telegram: t.me/ccielabcenter Page 6

Module2-DOO-Demo2 CLC CCIE Data Center v3.1 Real Lab1 - DOO Released: January 15, 2025

Section 1.2: Layer-2 Switching

Configure the Layer 2 connectivity for DC1-N7K-1 and DC1-N7K-2, which have been imported into the
Enhanced Classic LAN fabric named LEGACY-DC:

• Cisco Nexus Dashboard Fabric Controller (NDFC) must be used.

• STP must be at high chances for all the N7K’s during failover
• Use proper interfaces to make sure of connectivity
• Create back-to-back vPC toward the N5K-1 and N5K-2:
o All four links drawn into the topology must be used.
o Make sure that DC1-N7K-1 and DC1-N7K-2 will disable the link if a better BPDU is
received from that vPC.
▪ Use the freeform section inside the interface policy.
o Port-Channel and vPC IDs on both switches must be 101.
o Configuration on both Nexus 5000 is already deployed and you are not allowed to edit
any configuration on those devices.

Configure a back-to-back vPC toward the vPC border gateways DC1-N9K-BGW1 and DC1-N9K-BGW2
imported into the VXLAN EVPN fabric named LEGACY-DC_GATEWAY:
o Only four links must be used fo*******************ommited

Solution
Step 1: On ND-NDFC: Adding configuration in LEGACY-DC Fabric

• Go to NDFC Fabric Settings in LEGACY_DC

→ Spanning Tree → Spanning Tree Bridge Priority = 0
• Now on NDFC create two new vPC interfaces
o EnableBPDU Guard: False
o Enable Port Type Fast: Unchecked
o Interface Freeform: spanning-tree guard root
o Finally attach all the networks to vPC101 towards Nexus5000

Step 2: On ND-NDFC: Creating interface in LEGACY_DC - 101

• Go to NDFC Interfaces → Actions → Create Interface

o vPC 101 (N7K-1, N7K-2)
o eth 3/4-5; 3/12-13
STP settings
BPDU guard:false
Port Fast: Not enabled
spanning-tree guard root: Enabled
o Finally: Save & Deploy

Web: https://ccielabcenter.com | Mail: care@ccielabcenter.com | Telegram: t.me/ccielabcenter Page 7

Module2-DOO-Demo2 CLC CCIE Data Center v3.1 Real Lab1 - DOO Released: January 15, 2025

Step 3: On ND-NDFC: Attaching the networks in LEGACY_DC

• Go to NDFC Networks → Select the below → Actions → Multi-Attach → Port-channel 101

✓ backup_media_server
✓ shared_mysql
✓ backup_controller
✓ snmp_pollers
✓ external_gateways
✓ prod_frontend
✓ staging_frontend
• Next: Proceed to Full Switch Deployment
• Finally: Deploy All

Step 4: On ND-NDFC: LEGACY_DC - 201

• VPC-201 (Eth 4/6-7; Eth 4/15-16)

Web: https://ccielabcenter.com | Mail: care@ccielabcenter.com | Telegram: t.me/ccielabcenter Page 8

Module2-DOO-Demo2 CLC CCIE Data Center v3.1 Real Lab1 - DOO Released: January 15, 2025

Section 1.3: VXLAN EVPN Shared Borders

The DC-2 Nexus 9000s must provide Layer 2 (with BUM flooding) and Layer 3 extensions to the entire
Multi-Site domain. They must operate as vPC External VTEPs and not as border gateways.

• Create a new data center VXLAN EVPN fabric and name it SHARED-BORDERS
o Use Autonomous Systems 65058.
o Do not change any resource pool (subnets/VLANs/VNIs).
o Optional: Ensure that devices will not be reloaded when imported; this might save you a
few minutes.
• Import the devices using their management IP.
• Define the role of each switch and create a vPC domain between them.
• Create a vPC interface that will connect toward DCX-N7K-X:
o Port-Channel and vPC IDs on both shared borders must be 301.
o Only DC2-N9K-1/2 Eth1/1 must be used for this vPC. Eth1/2 will be used for a different
task.
o Ensure that you are using the appropriate interface options for interconnecting different
switches.
o vPC is already configured on the other side.
• Recalculate and deploy.

Solution
Step 1: On ND-NDFC:

• Create a new fabric and name it as SHARED-BORDERS

o Autonomous System: 65058
o Replication/Replication Mode: Ingress
o Greenfield Cleanup Option (optional) = Enable
o Finally attach all the networks to vPC101 towards Nexus5000
• Click on Import:
o Select: Nexus 9K Swicthes
✓ 10.1.1.93
✓ 10.1.1.94
o Role: Border Leaf
o Pairing into vPC domain → Actions → vPC Pairing
• Create a new vPC 301 towards DCX-N7K-X

Web: https://ccielabcenter.com | Mail: care@ccielabcenter.com | Telegram: t.me/ccielabcenter Page 9

Module2-DOO-Demo2 CLC CCIE Data Center v3.1 Real Lab1 - DOO Released: January 15, 2025

Module2: DOO-Demo2
CLC CCIE Data Center v3.1: Lab1
*****************The End*****************

100% Real | 100% Pass

Visit: www.ccielabcenter.com

Web: https://ccielabcenter.com | Mail: care@ccielabcenter.com | Telegram: t.me/ccielabcenter Page 10