CCIE EI v1.0 - Deploy - Seventh Release - 04-Jun-21
CCIE EI v1.0 - Deploy - Seventh Release - 04-Jun-21
www.passenterpriselabs.com 1 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
1. We highly discourage sharing of the workbook hence the workbooks are mapped to Laptop/Desktop
w
MAC address. If one tries to open the workbook on other desktop or laptop than the registered MAC
address; account will get locked and we will not unlock it for any reasons.
w
2. The workbook does not have print access; kindly do not request to enable to print access. However
w
you will have perpetual access to the workbook which you have purchased.
.p
3. One will be provided with free updates up to 120 days from the date of purchase, post that one
need to renew his/her account to access the latest update. However one will continue to have access
as
to their existing workbooks. If you pass the lab within 120 days, you are not eligible for further
updates.
se
4. If one wish to renew their subscription/account, you need to renew within 120 days or before the
account gets expired. Post 120 days one can renew their account however the renewal will be
considered has a new purchase. Hence we encourage one to renew within 120 days of the purchase.
nt
5. The renewal cost is 999 USD if one pay within 120 days, if one fail to renew then the cost will be
er
equivalent of a new purchase. (The renewal price can be changed at any time, without informing the
client)
pr
6. Every workbook is uniquely identified for each user with hidden words. If one shares his/her
is
workbooks with others, and if the system detects the share, the account will be banned and we will not
entertain any explanation of any sort.
el
8. We do require CISCO ID and Official email id for security purposes. We do not sell without these
details. We do background verification of the details provided, so request to give us the correct CISCO
.c
9. The workbooks are in secured pdc format and delivered via email within 24 hours after payment is
received.
10. License is provided for only one Device. And we don’t give license again if the device crashes or
company security policies. Please install license on the device cautiously as the license will not be
provided again.
www.passenterpriselabs.com 2 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
11. We do support devices running Windows OS, Mac OS, Android and Mac iOS only
12. We do not provide Refund in any circumstances once the product is sold.
w
13. This policy is in effect from 23 November 2016 and in immediate effect for new clients and new
w
renewals. Old clients will continue with the old Policies until the accounts get expired.
w
14. If there is any update, one will receive the update automatically on their registered email id.
.p
15. Design Module will be given only 3 days before the CCIE exam
as
16. For any future update you can check our 'updates' page.
17. Labs are always published in phases. For e.g. if there is a new lab we publish it as First, Second,
se
18. Client who have purchased our worbooks and services and wishes to attempt the lab, need to
nt
www.passenterpriselabs.com 3 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
1. The network that you will deploy, operate and optimize in this module will be similar, but not
w
necessarily identical, to the network designed in the previous module. All relevant information
that is needed to successfully complete this module can be found in this module itself and
.p
2. Before you start, confirm that all devices in your rack are accessible. During the exam, if any
device becomes locked or inaccessible, you must recover it.
se
3. Your equipment is partially preconfigured. Do not change any of the preconfigured parameters
unless you are specifically told to.
nt
4. The partial configuration on the devices may deliberately contain mistakes and errors which
may need to be corrected, or workarounds applied, in order to complete specific tasks.
er
5. Points are awarded only for fully working configurations. No partial scoring is provided. It is
recommended that toward the end of the exam, you go back and test the functionality as per
is
6. If you need clarification on any of the questions, or if you suspect that there might be an issue
with your equipment or exam environment, contact the lab proctor as soon as possible.
ab
7. Item-level feedback can be provided at the question level. Feedback will be processed, but
Cisco will not reach out to you to discuss any feedback provided. You will not be compensated
s
8. Access to select Cisco online documentation is available from your desktop. Access to select 3rd
party product documentation (such as Python) is available from the Resources window under
om
9. When you finish the lab exam, make sure that all devices are accessible for the grading proctor
by having them in EXEC mode and closing the console windows. A device that is not accessible
for grading cannot be graded and this may cause you to lose substantial points.
www.passenterpriselabs.com 4 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
10. You have 5 hours to complete this module. Upon finishing the exam, ensure that all devices are
accessible. Any device that is not accessible for grading purposes may cause you to lose
substantial points.
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 5 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
1. There are several end hosts present in the lab topology, named hostXY (for example, host11).
w
They are all identical and they can all be used at your full discretion, including accessing the GUI
of DNA Center, vManage and ISE through Firefox, performing IP connectivity tests, generating
w
2. All hostXY devices are configured as DHCP clients. Should it be necessary to force the host to
release and renew its DHCP lease, right-click on the icon of the network manager located
.p
between CPU utilization and check applets in the bottom task bar, then unselects “Enable
Networking”, right-click on it again and select “Enable Networking”.
as
3. The web-based GUI of DNA center, vManage and ISE can only be accessed from the hostXY end
hosts, using firefox installed on these end hosts. These servers cannot be accessed directly from
se
the desktop you are just now working with. You must always connect to hostXY as a jump host
and access the DNA center, vManage or ISE from there. Always ignore any SSL/TLS certificate
warnings in Firefox that may be displayed.
nt
4. Devices in the topology may have more interfaces, addresses and routes configured than what
er
is shown in the diagrams and accompanying tables. Ignore such interfaces addresses and routes
entirely, unless a task explicitly requires you to use or modify them.
pr
new configuration, is allowed only if the task allows or requires it explicitly, or if there is no
other way of accomplishing the task.
el
ab
s .c
om
www.passenterpriselabs.com 6 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 7 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 8 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
1.1: Introduction
You will deploy, operate, and optimize our network. The topology you will be working with will be
w
similar, but not necessarily identical to the network that was designed in the previous module and may
include technologies and feature sets not touches upon previously.
w
www.passenterpriselabs.com 9 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Complete and correct the EtherChannel configuration between switches sw101, sw102, sw110
w
At the end of the task, all EtherChannels between switches sw101, sw102, sw110 must be up
and operational including all their physical member links.
w
Do not create new Port-channel interface; reuse those that already exist on the switches.
.p
When resolving existing issues, do not change the preconfigured negotiation protocol (if any)
On EtherChannels that use a negotiation protocol, tune its mode of operation for the shortest
as
Configure spanning tree protocol on switches sw101, sw102, sw110 according to these
se
requirements:
nt
On the three switches, use the Rapid STP version and ensure that it can achieve rapid
convergence on all interconnections between the switches.
is
On Sw110, prevent all current and future access mode interfaces from being affected by the
proposal/ Agreement process.
el
ab
2 Points
s .c
om
www.passenterpriselabs.com 10 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Solution:
Chinese_dumps_sw110:
w
en
w
sw110#conf t
sw110(config)#spanning-tree mode rapid
w
Chinese_dumps_sw101:
en
nt
sw101#config t
sw101(config)#spanning-tree mode rapid
er
sw101(config-if-range)#channel-group 1 mode on
el
Chinese_dumps_sw102:
ab
en
sw102#conf t
sw102(config)#spanning-tree mode rapid
s
www.passenterpriselabs.com 11 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Verification:
www.passenterpriselabs.com 12 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 13 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 14 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Chinese_dumps_sw110#sh spanning-tree
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 15 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 16 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 17 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 18 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
For IPv4, implement an FHRP mechanism on sw101 and sw102 for VLANs 2000 and 2001 according to
w
these requirements:
w
Use Group number 100 for VLAN 2000 and group number 101 for VLAN 2001.
Use the first available IPV4 address in the subnet for the address of the virtual router.
w
For VLAN 2000, sw101 must be preferred gateway; for VLAN 2001, sw102 must be the
.p
preferred gateway. Do not rely on the IPv4 addresses of the switches as role tiebreakers. The
role must determine by an explicit configuration solely on the intended preferred gateway.
as
Each preferred gateway must monitor the reachability of both routers r11 and r12 using the
loopback IPv4 addresses of the routers by an ICMP Echo. The reachability is to be verified every
5 seconds with a timeout of 400 msec. A router must be declared unreachable as soon as it
se
does not respond to three probes in a row. If both r11 and r12 are declared unreachable from a
preferred gateway, the other switch must be allowed to assume the gateway role.
nt
Use the FHRP protocol that allows the virtual IPv4 address to match the IPv4 address of a
member router.
er
pr
2 Points
is
el
ab
s .c
om
www.passenterpriselabs.com 19 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Solution:
Chinese_dumps_sw101:
w
sw101#en
w
sw101#conf t
sw101(config)#int vlan 2000
w
sw101(config-if)#exit
se
sw101(config-if)#exit
er
sw101(config)#ip sla 1
sw101(config-ip-sla)#icmp-echo 10.1.255.11 source-interface vlan 2000
pr
sw101(config-ip-sla-echo)#threshold 400
sw101(config-ip-sla-echo)#timeout 400
sw101(config-ip-sla-echo)#frequency 5
is
sw101(config-ip-sla-echo)#exit
sw101(config)#ip sla schedule 1 start-time now life forever
el
sw101(config)#ip sla 2
ab
sw101(config-ip-sla-echo)#frequency 5
.c
sw101(config-ip-sla-echo)#exit
sw101(config)#ip sla schedule 2 start-time now life forever
om
sw101(config)#track 1 ip sla 1
sw101(config-track)#delay down 10
sw101(config)#exit
sw101(config)#track 2 ip sla 2
sw101(config-track)#delay down 10
www.passenterpriselabs.com 20 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
sw101(config)#router ospf 1
w
Chinese_dumps_sw102:
as
sw102>en
sw102#conf t
sw102(config)#int vlan 2000
se
sw102(config-if)#exit
er
sw102(config)#ip sla 1
ab
sw102(config-ip-sla-echo)#timeout 400
.c
sw102(config-ip-sla-echo)#frequency 5
sw102(config)#exit
om
www.passenterpriselabs.com 21 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
sw102(config)#ip sla 2
sw102(config-ip-sla-echo)#icmp-echo 10.1.255.12 source-interface vlan 2001
sw102(config-ip-sla-echo)#threshold 400
w
sw102(config-ip-sla-echo)#timeout 400
w
sw102(config-ip-sla-echo)#frequency 5
sw102(config-ip-sla-echo)#exit
w
sw102(config)#track 1 ip sla 1
as
sw102(config-track)#delay down 10
sw102(config-track)#exit
se
sw102(config)#track 2 ip sla 2
sw102(config-track)#delay down 10
nt
sw102(config-track)#exit
er
sw102(config-track)#object 1
sw102(config-track)#object 2
is
el
sw102(config)#router ospf 1
sw102(config-router)#passive-interface vlan 2000
sw102(config-router)#passive-interface vlan 2001
ab
s .c
om
www.passenterpriselabs.com 22 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Verification:
Chinese_dumps_sw101#sh vrrp
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 23 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Chinese_dumps_sw101#sh track
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 24 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 25 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 26 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Chinese_dumps_sw102#sh vrrp
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 27 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Chinese_dumps_sw102#sh track
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 28 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 29 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 30 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
sw101:
w
- Make the int g0/0 , g0/1 down (shutdown) and check "sh vrrp" , sw102 should be master for
w
sw102: sh vrrp
.p
as
se
nt
er
pr
is
el
ab
s .c
om
Note : If you make the interface of sw101 up , again it should retain its original role
www.passenterpriselabs.com 31 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
sw102:
- Make the int g0/0 , g0/1 down (shutdown) and check "sh vrrp" , sw101 should be master for
w
sw101: sh vrrp
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
Note : If you make the interfaces of sw102 up , again it should retain its original role
www.passenterpriselabs.com 32 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Complete and correct the OSPF configuration on the switches sw101, sw102, sw201 and sw202
w
Enable OSPFv2 on the redundant interconnections between the DC and HQ sites. Make sure
that OSPF establishes adjacencies on these interconnections and exchanges routing information
w
Protect the authenticity and integrity of the OSPFv2 sessions on the redundant
interconnections between DC and HQ with the SHA-384 mechanism. Use key ID 1 and a shared
as
probes being sent every 100 msec. it is not allowed to modify OSPF timers to accomplish this
requirement.
nt
er
3 Points
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 33 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Solution:
Note: Try making the interface default if the interface showing not connect
w
Chinese_dumps_sw201:
w
sw201>en
w
sw201#conf t
sw201(config)#key chain DCHQ
.p
sw201(config-keychainn)#key 1
sw201(config-keychain-key)#key-string cci3
as
sw201(config-keychain-key)#cryptographic-algorithm hmac-sha-384
sw201(config)#exit
sw201(config)#exit
se
sw201(config)#int g1/2
sw201(config-if)#ip ospf authentication key-chain DCHQ
nt
sw201(config-if)#exit
pr
sw201#config t
sw201(config)#router ospf 1
sw201(config-router)#no passive-interface g1/2
is
Chinese_dumps_sw202:
el
sw202>en
ab
sw202#conf t
sw202(config)#key chain DCHQ
sw202(config)#key 1
s
sw202(config-keychain)#key-string cci3
.c
sw202(config-keychain)#cryptographic-algorithm hmac-sha-384
sw202(config-keychain)#exit
om
sw202(config)#exit
sw202(config)#int g1/2
sw202(config-if)#ip ospf authentication key-chain DCHQ
sw202(config-if)#ip ospf bfd
sw202(config-if)#bfd interval 100 min_rx 100 multiplier 3
sw202(config)#exit
www.passenterpriselabs.com 34 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
sw202#config t
sw202(config)#router ospf 1
sw202(config)#no passive-interface g1/2
w
Chinese_dumps_sw101:
w
sw101>en
w
sw101#conf t
sw101(config)#key chain HQDC
.p
sw101(config-keychain)#key 1
sw101(config-keychain-key)#key-string cci3
as
sw101(config-keychain-key)#cryptographic-algorithm hmac-sha-384
sw101(config-keychain-key)#exit
sw101(config)#exit
se
sw101(config)#int g0/2
sw101(config-if)#ip ospf authentication key-chain HQDC
nt
Chinese_dumps_sw102 :
pr
sw102>en
sw102#conf t
is
sw102(config-keychain-key)#key-string cci3
sw102(config-keychain-key)#cryptographic-algorithm hmac-sha-384
ab
sw102(config-keychain)#exit
sw102(config)#exit
s
sw102(config)#int g0/2
.c
www.passenterpriselabs.com 35 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Verification:
www.passenterpriselabs.com 36 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 37 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 38 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 39 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 40 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 41 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 42 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 43 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Enable hosts in HQ VLAN 2000 and VLAN 2001 to obtain their IP configuration via DHCP according to
w
these requirements:
w
On sw211, create IPv4 DHCP pools named hq_v2000 and hq_v2001 for HQ VLANs 2000 and
2001, respectively. In each subnet, assign addresses from .101 upto .254 inclusively, and the
w
Enable DHCP snooping on sw110 in VLANs 2000 and 2001 to protect against DHCP-related
attacks.
as
VLANs2000 and 2001 to obtain IPv4 configuration through DHCP. The DHCP server running at
sw211 in the DC must be referred to by its loopback IPv4 address 10.2.255.211. Do not disable
nt
the Option 82 insertion, and do not enable DHCP snooping on other switches.
Verify that host11 and host12 have IP connectivity to the Cisco DNA Center, vManage and ISE
er
2 Points
is
el
ab
s .c
om
www.passenterpriselabs.com 44 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Solution:
Chinese_dumps_sw110:
w
sw110>en
w
sw110#conf t
sw110(config)#ip dhcp snooping
w
sw110(config)#int g0/0
sw110(config-if)#switchport mode access
se
sw110(config)#int g0/1
sw110(config-if)#switchport mode access
er
Chinese_dumps_sw101:
is
sw101>en
sw101#conf t
el
sw101(config)#exit
www.passenterpriselabs.com 45 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Chinese_dumps_sw102:
sw102>en
w
sw102#conf t
sw102(config)#int vlan 2000
w
sw102(config-if)#exit
.p
Chinesedumps.com-sw211:
se
sw211>en
sw211#conf t
nt
sw211(config-dhcp)#exit
sw211(config-dhcp)#default-router 10.1.101.1
sw211(config)#exit
ab
s .c
om
www.passenterpriselabs.com 46 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Verification:
www.passenterpriselabs.com 47 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 48 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 49 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 50 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 51 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Host 11:
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 52 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Host 12:
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 53 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
1.6: IPv6 in HQ
Implement IPv6 on sw101 and sw102 for switch virtual interfaces (SVIs) Vlan 2000 and Vlan 2001
w
Sw101
Interface Vlan2000: 2001:db8:1:100::1/64
w
The configuration must enable hosts in these VLANs to obtain their IPv6 configuration via
SLAAC and keep a stable connectivity with other IPv6 networks.
se
Use native IPv6 means to provide gateway redundancy, with sw101 being the preferred
gateway in VLAN 2000 and sw102 being the preferred gateway in VLAN 2001. The role must be
determined by an explicit configuration solely on the intended preferred gateway.
nt
Hosts must be able to detect the failure of the preferred gateway in as little as 3 seconds.
er
1 Point
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 54 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Solution:
Chinese_dumps_sw101:
w
sw101>en
w
sw101#conf t
sw101(config)#int vlan 2000
w
sw101(config-if)#ipv6 enable
sw101(config-if)#ipv6 address 2001:db8:1:100::1/64
.p
sw101(config-if)#ipv6 enable
sw101(config-if)#ipv6 address 2001:db8:1:101::1/64
sw101(config-if)#ipv6 nd ra lifetime 3
nt
Chinese_dumps_sw102:
pr
sw102>en
sw102(config)#conf t
is
www.passenterpriselabs.com 55 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Verification:
www.passenterpriselabs.com 56 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 57 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 58 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 59 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
- Ping from host-11 to both the ipv6 vlan 2000 and 2001(2001:db8:1:100::1 , 2001:db8:1:101::1 )
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 60 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
- Ping from host-12 to both the ipv6 vlan 2000 and 2001(2001:db8:1:100::1 , 2001:db8:1:101::1 )
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 61 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
- Traceroute from both host-11 & host-12 to ipv6 loopback address of r11 (2001:db8:1:255::11)
w
w
w
.p
as
se
nt
er
In the above output you can see host11 is using sw101 – vlan 2000 to reach r11
pr
is
el
ab
s .c
om
In the above output you can see host12 is using sw102 – vlan 2001 to reach r11
www.passenterpriselabs.com 62 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
- After we shutdown the vlan 2000 on sw101 , the host11 will switch its gateway to sw102 – vlan
2000
w
w
w
.p
as
se
nt
er
pr
is
- After we shutdown the vlan 2001 on sw102 , the host12 will switch its gateway to sw101 – vlan 2001
el
ab
s .c
om
www.passenterpriselabs.com 63 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 64 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
In HQ, enable EIGRP for IPv6 on r11, r12, sw101 and sw102 according to these requirements:
w
IPv6 EIGRP may form adjacencies only over the physical Layer3 interfaces between r11, r12,
sw101 and sw102.
.p
Prevent IPv6 EIGRP from automatically running on, or advertising attached prefixes from, new
IPv6-enabled interfaces in the future unless allowed explicitly.
as
Ensure that the attached IPv6 prefixes on SVIs Vlan2000 and Vlan2001 onsw101 and sw102 are
advertised in IPv6 EIGRP and learned on r11 and r12.
se
2 Points
er
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 65 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Solution:
Chinese_dumps_sw101:
w
sw101>en
w
sw101#conf t
sw101(config)#router eigrp ccie
w
sw101(config-router)#shutdown
sw101(config-router)#exit-af-interface
as
sw101(config-router-interface)#af-interface g0/0
sw101(config-router-interface)#no shutdown
er
sw101(config-router-interface)#af-interface g0/1
sw101(config-router-interface)#no shutdown
pr
Chinese_dumps_sw102:
is
sw102>en
el
sw102#conf t
sw102(conifg)#router eigrp ccie
ab
sw102(conifg-router-af)#no shutdown
sw102(conifg-router-af)#passive
om
www.passenterpriselabs.com 66 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Chinese_dumps_r11:
r11>en
w
r11#conf t
r11(config)#router eigrp ccie
w
r11(config-router-af)#shutdown
r11(config-router-af)#exit-af-interface
.p
r11(config-router)#af-interface g0/2
as
r11(config-router-af)#no shutdown
r11(config-router-af)#af-interface g0/1
r11(config-router-af)#no shutdown
se
r11(config-router-af)#exit-af-interface
r11(config-router)#af-interface g0/3
nt
r11(config-router-af)#no shutdown
er
Chinesedumps.com-r12:
pr
r12>en
r12#conf t
r12(config)#router eigrp ccie
is
r12(config-router-af)#shutdown
r12(config-router-af)#exit-af-interface
ab
r12(config-router)#af-interface g0/2
r12(config-router-af)#no shutdown
s
r12(config-router)#af-interface g0/1
.c
r12(config-router-af)#no shutdown
r12(config-router)#af-interface g0/3
om
r12(config-router-af)#no shutdown
www.passenterpriselabs.com 67 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Verification:
www.passenterpriselabs.com 68 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 69 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 70 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 71 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 72 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 73 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 74 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 75 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
- As you can see in the above screenshots for sw101 and sw 102 , there are routes advertised in
w
eigrp because only the physical links are advertised in eigrp on r11 and r12
- To get the routes in eigrp on sw101 and sw102 , add the loopback interface on r11 to eigrp (just
w
On r11 :
.p
af-interface Loopback0
no shutdown
exit-af-interface
nt
er
Output:
pr
Sw101:
is
el
ab
s .c
om
- In the above output you can see there is a route present in the eigrp routing table
www.passenterpriselabs.com 76 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Sw102:
w
w
w
.p
as
se
nt
- In the above output you can see there is a route present in the eigrp routing table
er
pr
NOTE : After testing please remove the loopback 0 on r11 from eigrp
is
On r11 :
el
af-interface Loopback0
.c
shutdown
exit-af-interface
om
www.passenterpriselabs.com 77 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
1.8: OSPFv2 in DC
Switches sw201 and sw202 must establish a stable OSPF adjacency in the FULL state with
w
vedge21 and vedge22 on interface Vlan3999. Any configuration changes and corrections
necessary to meet this requirement may be performed only on the switches, and any
w
mismatched parameters causing the issue must be changed to exactly match the configuration
.p
of the vEdges.
All OSPF speakers in the DC running Cisco IOS and IOS-XE software must be configured to keep
as
the number of advertised internal routes to an absolute minimum while not impacting the
reachability of the services. This included the reachability of ISE, DNA center, vManage, vBond
and vSmart on their internal (in Band Connectivity) addresses, as well as any existing and future
se
devices in VLAN 4000 on sw201 and sw202. The configuration of this requirement must be
completed exclusively within the “router ospf” and “interface vlan” contexts without causing
nt
OSPFv2 to provide HQ and DC with the reachability to the DMVPN tunnel and branches #3 and
#4. The configuration of this requirement must be completed exclusively within the “router
pr
ospf” context.
Any route from the 10.2.0.0/16 range that keeps being advertised in OSPF must continue being
is
4 Points
s .c
om
www.passenterpriselabs.com 78 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Solution:
-------------------------------------
router ospf 1
w
prefix-suppression
w
Chinese_Dumps_sw201, sw202
.p
#conf t
as
Chinese_Dumps_ r24
er
r24#conf t
pr
r24(config)#router ospf 1
r24(config-router)#redistribute eigrp 65006 subnets
r24(config-router)#summary-address 10.6.0.0 255.254.0.0 tag 123
is
el
Chinese_Dumps_SW211:
ab
sw211#conf t
sw211(config)#router ospf 1
sw211(config-router)#passive-interface gi1/1
s
sw211(config-router)#passive-interface gi1/2
.c
sw211(config-router)#passive-interface gi1/3
om
Chinese_Dumps_SW212:
sw212#conf t
sw212(config)#router ospf 1
sw212(config-router)#passive-interface gi1/1
sw212(config-router)#passive-interface gi1/2
www.passenterpriselabs.com 79 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Verification:
www.passenterpriselabs.com 80 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 81 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 82 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Configure the BGP peerings between HQ/DC and Global SP#1 and Global SP#2 according to these
w
requirements:
w
Ensure that the routes learned over eBGP sessions and further advertised in iBGP will be
considered reachable even if the networks on inter-AS links are not advertised in OSPF. The
as
configuration of this requirement must be completed exclusively within the “router bgp”
context.
On r11, r21 and r22 perform mutual redistribution between OSPFv2 and BGP. However,
se
prevent routes that were injected into OSPF from BGP to be reinjected back into BGP. This
requirement must be solved on r11, r21 and r22 using only a single route-map on each of the
nt
routers and without any reference to ACLs, prefix lists, or route types.
Prevent HQ and DC from ever communicating through SP#1 r3. All communication between HQ
er
and DC must occur only over the direct sw101/sw201 and sw102/sw202 interconnections. Any
other communication must remain unaffected. This requirement must be solved on r21 and r22
pr
by route filtering based on a well-known mandatory attribute without the use of route maps.
No command may be removed from the configuration on r11 to accomplish this entire task.
is
It is allowed to modify existing configuration commands on r21 and r22 to accomplish this
entire task.
el
ab
3 Points
s .c
om
www.passenterpriselabs.com 83 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Solution:
Chinesedumps-r11:
w
r11(config-router)#address-family ipv4
r11(config-router)#neighbor 100.3.11.1 remote-as 10000
w
r11(config)#router ospf 1
as
Chinesedumps-r21:
is
r21#conf t
r21(config)#route-map DENY deny 10
el
www.passenterpriselabs.com 84 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Chinesedumps-r22:
r22#conf t
w
r22(config)#router ospf 1
.p
www.passenterpriselabs.com 85 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Verification:
www.passenterpriselabs.com 86 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 87 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 88 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 89 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
To verify 5th point, we will use the previously created loopback on r3 (int lo1 – 3.3.3.3/24)
- From above output you can see the route is just showing as an ibgp route and also it is not
present in the routing table of bgp
www.passenterpriselabs.com 90 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
From the above output you can see that the 3.3.3.0 loopback is showing as best route and also it is
installed in the routing table.
Note: After performing the verification, please remove the loopback from r3
www.passenterpriselabs.com 91 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
6th point :
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
From above output you can see the HQ devices are preferring links between sw101 – sw201 & sw102
– sw202 to reach any subnet in DC
om
www.passenterpriselabs.com 92 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
- Shutdown the link between sw101 – sw201 & sw102 – sw202 and check if you are having
w
From above output you can see the HQ device host 11 cannot reach as the direct link between the
switches sw101 – sw201 & sw102 – sw202
www.passenterpriselabs.com 93 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Configure r3 through r6 for mutual VPNv4 and VPNv6 route exchange without the use of a
w
Configure r3 through r6 to assign (allocate/bind) as few unique MPLS labels to all existing and
future VPNv4 and VPNv6 routes as possible.
.p
On Routers r3 through r6, prevent any existing and future customer from discovering details
about the inner topology of SP#1. It is not allowed to use ACLs to accomplish this requirement.
as
3 Point
se
nt
er
pr
is
el
ab
s .c
om
www.passenterpriselabs.com 94 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Solution:
Chinesedumps.com-r3:
w
r3>en
w
r3#conf t
r3(config)#router bgp 10000
w
r3(config-router)#address-family vpnv6
r3(config-router)#neighbor 100.255.254.4 activate
er
Chinesedumps.com-r4:
is
r4>en
el
r4#conf t
r4(config)#router bgp 10000
ab
r4(config-router)#address-family vpnv4
r4(config-router)#neighbor 100.255.254.3 activate
r4(config-router)#neighbor 100.255.254.5 activate
r4(config-router)#neighbor 100.255.254.6 activate
r4(config-router)#address-family vpnv6
r4(config-router)#neighbor 100.255.254.3 activate
r4(config-router)#neighbor 100.255.254.5 activate
r4(config-router)#neighbor 100.255.254.6 activate
www.passenterpriselabs.com 95 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Chinesedumps.com-r5:
w
r5>en
r5#conf t
w
Chinesedumps.com-r6:
r6>en
is
r6#conf t
r6(config)#router bgp 10000
el
r6(config-router)#address-family vpnv4
r6(config-router)#neighbor 100.255.254.3 activate
om
www.passenterpriselabs.com 96 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
#conf t
#mpls label mode all-vrfs protocol bgp-vpnv4 per-vrf
w
www.passenterpriselabs.com 97 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Verification:
w
www.passenterpriselabs.com 98 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
www.passenterpriselabs.com 99 www.ccieenterpriselabs.com
www.passenterpriselabs.com Final Release Lab 1:04-Jun-2021
Correct the configuration issues resulting in broken DMVPN tunnel connectivity between DC, Branch3
w
On Spokes, do not add new BGP neighbors; reuse those that are currently up while changing
their VRF membership as needed.
se
3 Point
er
pr
is
el
ab
s .c
om
Solution:
Chinesedumps.com-r61:
w
r61>en
w
r61#conf t
w
r61(config)#int lo 0
r61(config-if)#vrf forwarding WAN
.p
r61(config)#int g0/0
as
r61(config)#interface tunnel 0
pr
r61(config-af-interface)#passive-interface
r61(config-router)#exit-af-interface
w
r61(config-af-interface)#af-interface Tunnel0
r61(config-af-interface)#no passive-interface
w
r61(config-af-interface)#exit-af-interface
.p
Chinesedumps.com-r62:
as
r62>en
r62#conf t
r62(config)#int lo 0
se
r62(config)#int g0/0
r62(config-if)#vrf forwarding WAN
er
r62(config)#int tunnel 0
el
r61(config-af-interface)#passive-interface
r61(config-router)#exit-af-interface
w
r61(config-af-interface)#af-interface Tunnel0
r61(config-af-interface)#no passive-interface
w
r61(config-af-interface)#exit-af-interface
.p
Chinesedumps.com-r70:
as
r70>en
r70#conf t
r70(config)#int tunnel 0
se
r70(config-af-interface)#no passive-interface
r70(config-router)#exit-af-interface
s .c
om
Solution Steps:
Match the crypto configs on r24 and then configure the spokes (r70 , r61 ,r62)
w
Faults On Spoke :
w
configuration
crypto isakmp policy 10
.p
no hash md5
as
2.
a. On r24 legacy key is configured
b. on spokes we will need to complete the key ring configuration for isakmp
se
a. On hub (r24)" ip nhrp redirect " : - This command says that we are running phase 3 mode
b. On Spokes (r61,r62,r70) “ ip nhrp shortcut ”
er
pr
is
el
ab
s .c
om
Verification:
Chinesedumps.com-r61#sh dmvpn
is
el
ab
s .c
om
Chinesedumps.com-r61#ping 10.200.0.70
s .c
om
Chinesedumps.com-r61#traceroute 10.200.0.70
w
w
w
.p
as
se
Chinesedumps.com-r62#sh dmvpn
w
w
w
.p
as
se
nt
er
pr
is
Chinesedumps.com-r70#sh dmvpn
pr
is
el
ab
s .c
om
Ensure that Branches #3 and #4 receive only a default route over EIGRP in DMVPN.
w
The default route origination must be done on DC r24 without the use of any static routes,
w
It is allowed to add commands to the configuration of r70 in branch #4 to accomplish this task;
none of the existing configuration on r70 may be removed to accomplish this task.
as
Routers r61 and r62 must not send EIGRP queries to sw601 and sw602.
Switches sw601 and sw602 must allow advertising any current or future directly connected
nt
and r62 to each other. To select the default route, use a prefix list with a “permit”- type entry
only.
pr
Switches sw601 and sw602 must not propagate the default route back to r61 and r62.
If the prefix list that allows the propagation of selected EIGRP-learned networks between
is
sw601 and sw602 is modified in the future, the same set of networks must be disallowed from
being advertised back to r61 and r62 automatically, without any additional commands
el
ab
3 Points
s .c
om
Solution:
Chinesedumps-r24:
w
r24>en
w
r24#conf t
r24(config)#router eigrp ccie
w
r24(config-router)#af-interface tunnel 0
r24(config-router)#summary-address 0.0.0.0/0
as
r24(config-router)#topology base
se
Chinesedumps-r70:
r70#conf t
nt
r70(config-router)#af-interface tunnel 0
r70(config-router)#no passive
pr
sw>en
el
sw#conf t
sw(config)#ip prefix-list ALLOW-DEF seq 5 permit 0.0.0.0/0
ab
sw (config-if)#topology base
sw (config-if)#distribute-list route-map BLOCK-DEF out GigabitEthernet0/1
.p
Verification:
Chinesedumps-r61:
w
w
w
.p
as
se
nt
er
pr
Chinesedumps-r62:
is
el
ab
s .c
om
Chinesedumps-r70:
w
w
w
.p
as
se
nt
While checking the default route information is present on sw601 & sw602
er
Chinesedumps-sw601:sh ip route
pr
is
el
ab
s .c
om
Found that r61 was not sending default route on sw601 (same for sw602)
Issue :
w
- Found that there was no neighborship between r61 and sw601 , sw602
w
.p
as
se
nt
er
- From the above output you can see that sw 601 is only neighbor with sw 602
pr
- From above output you can see that in eigrp af-interface default is made passive and only
tunnel interface is removed from passive state
NOTE : Whenever we make an interface passive in eigrp the router stops sending eigrp messages
including Hello messages and the devices need Hello messages for neighborship
w
af-interface GigabitEthernet0/2
no passive-interface
as
exit-af-interface
af-interface GigabitEthernet0/3
se
no passive-interface
exit-af-interface
nt
- After removing the connected interface on r61 and r62 to the downstream switches from
passive-interface we are getting the default route information on sw601 and sw602
er
pr
is
el
ab
s .c
om
To verify “Switches sw601 and sw602 must not propagate the default route back to r61 and
r62.”
- Shutdown the interface on r62 that is connected to r6 in SP 1
w
On r62:
w
Int g0/0
w
Shutdown
.p
as
se
nt
er
pr
is
el
ab
s .c
- After shutting down the interface on r62 we can see from the above output that there is no
om
- If we check on sw601 or sw602 they should have the default route present in the routing table
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
On sw211 in DC, complete the DHCP server configuration according to these requirements:
w
Create IPv4 DHCP pools named br3_v2000 and br3_v2001 for Branch #3 VLANs 2000
w
Create IPv4 DHCP pool named br4_v1 for the subnet 10.7.1.0/24 on branch #4.
In each subnet, assign addresses from .101 up to .254 inclusively, and the appropriate gateway
.p
to clients.
as
On Branch #3, Complete and correct the configuration on switches sw601, sw602 and sw610 to allow
HSRP and DHCP relay operation in VLANs 2000 and 2001 according to these requirements:
se
HSRP must implicitly use the vMAC address range of 0000.0c9f.f000 through 0000.0c9f.ffff
The group member must be 100 for VLAN 2000 and 101 for VLAN 2001
nt
Sw601 must be the Active gateway for VLAN 2000 with a priority of 110; the Active role
ownership must be deterministic
er
Sw602 must be the Active gateway for VLAN 2001 with a priority of 110; the Active role
ownership must be deterministic
pr
Each active switch must track its uplink interfaces gi0/1 and gi0/2 if either of these interfaces
goes down; the active switch must allow the other switch to become Active. However, it is not
is
allowed for the tracking to modify the HSRP priority to accomplish this requirement.
Both sw601 and sw602 must be configured as DHCP relay agents in both VLANs 2000 and 2001,
el
pointing toward the DHCP server 10.2.255.211 at sw211. However, at any time, only the Active
router in the particular VLAN should relay the DHCP messages.
ab
Place host61 and host62 into VLANs 2000 and 2001, respectively, and make sure they are
assigned their correct IPv4 configuration.
s
On Branch #4, complete the configuration of the router r70 according to these requirements;
om
Solution:
Chinesedumps.com-sw211:
w
sw211>en
w
sw211#conf t
sw211(config-dhcp)#ip dhcp excluded-address 10.6.100.1 10.6.100.100
w
sw211(config-dhcp)#default-router 10.6.100.1
as
sw211(config-dhcp)#default-router 10.6.101.1
sw211(config-dhcp)#default-router 10.7.1.1
pr
Chinesedumps.com-sw601:
is
sw601>en
sw601#conf t
el
Chinesedumps.com-sw602:
w
sw602>en
w
sw602#conf t
sw602 (config)#int vlan 2001
.p
Chinesedumps.com-sw610:
sw610>en
s
sw610#conf t
.c
sw610(config)#int g0/0
sw610(config-if)#switchport mode access
sw610(config-if)#switchport access vlan 2000
sw610(config)#int g0/1
sw610(config-if)#switchport mode access
sw610(config-if)#switchport access vlan 2001
Chinesedumps.com-r70:
r70>en
w
r70#conf t
r70(config)#interface GigabitEthernet0/2
w
Verification:
Chinesedumps.com-r211:
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
Chinesedumps.com-sw601:
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
Chinesedumps.com-sw602:
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
Chinesedumps-host61:
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
Chinesedumps-host62:
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
To verify “Each active switch must track its uplink interfaces gi0/1 and gi0/2/ if either of these
interfaces goes down; the active switch must allow the other switch to become Active.
However,, it is not allowed for the tracking to modify the HSRP priority to accomplish this
w
requirement. “
w
- Go on sw601 and shutdown the interface g0/2 or g0/1 , and then check on sw602 that it should
w
- Go on sw602 and shutdown the interface g0/2 or g0/1, and then check on sw601 that it should
become the gateway now for vlan 2001
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
Chinesedumps-host71:
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
Chinesedumps-host72:
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
FABD2 is preparing to enable PIM Sparse mode multicast routing in its network. As a part of validating
w
the runbooks, FABD2 requires a sanity check to prevent inappropriate use of multicast-related
configuration commands on different router types:
w
Last Hop Routers- routers where multicast receivers (subscribers) are connected
.p
Intermediary Hop Routers- routers on the path between First Hop and Last Hop routers
In the Table below, for each configuration command, select all router type where the use of the
as
Router Type
Command Intermediary Hop
First Hop Router Last Hop Router
Router
nt
ip pim register-source
ip igmp version
er
ip pim spt-threshold
ip pim rp-address
pr
ip pim sparse-mode
is
2 points
el
ab
Answer:
Router Type
s
Router
ip pim register-source
om
ip igmp version
ip pim spt-threshold
ip pim rp-address
ip pim sparse-mode
Extend the IPv6 connectivity from HQ through the SP into the giosk VRF on the laaS site according to
w
these requirements:
w
Enable the existing IPv4 BGP session between r11 and r3 to also advertise IPv6 prefixes. Do not
configure a standalone IPv6 BGP session between these two routers.
as
Perform bidirectional route redistribution between the IPv6 EIGRP and BGP processes on r11
Ensure that all current and future IPv6 prefixes advertised between r11 and r3 will be installed
se
into the RIB of these routers with the next hop address set to the proper global unicast address
on their interconnection. Any policy that accomplishes this requirement must be applied in the
nt
inbound direction.
The giosk VRF on r4 that extends the IPv6 connectivity from r4 to r30 on the laaS site is a
er
separate VRF independent of fabd2 VRF. Any route leaking from fabd2 VRF into giosk VRF must
be done on per-site basis and only for those FABD2 sites that need connectivity in the laaS site.
pr
By configuring r3 and r4 only, ensure that the HQ FABD2 site will have mutual visibility with the
laaS site while preventing
is
Any other FABD2 site from possibly learning about the routes on the laaS site
The laaS site from possibly learning about the routes on any other FABD2 site
el
Use the minimum amount of commands necessary to accomplish this requirement. Do not
remove any existing configuration. If necessary, you are allowed to use an additional route
ab
modify one existing configuration command on one of the SP routers to meet this requirement
.c
om
3 Points
Solution:
Chinese_Dumps_r11:
w
r11(config-if)#int gi0/0
w
r11(config-router)#address-family ipv6
r11(config-router)#address-family ipv6 unicast
r11(config-router)#neighbor 100.3.11.1 remote-as 10000
se
r11(config-router)#topology base
r11(config-router)#redistribute bgp 65001 metric 100 50 255 1 1500
pr
Chinese_Dumps_r4:
is
r4(config)#int lo0
ab
Chinese_Dumps_r3:
s .c
r3(config)#int g1
r3(config-if)#ipv6 address 2001:2710:311::1/64
r3(config-if)#route-map NH-IPV6 per 10
w
------------------------------------------------------------------------
as
interface Loopback414
no ip address
ipv6 address 2001:DB8:14::1/128
nt
ipv6 enable
er
pr
NOTE : On r4 there is loopback in pre-configs with /31 mask , we need to correct the loopback mask
to /32
is
el
ab
s .c
om
Verification:
- From above output we can see that the giosk network (100.4.30.5) is present on r3 in fabd2
er
- And in the below output on r5 we can see that the giosk network (100.4.30.5) is not present in
fabd2
pr
is
el
ab
s .c
om
Verify that host11 and host12 can ping 2001:db8:14::1 located at the laaS site.
Chinesedumps-sw101:
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
Chinesedumps-host11:
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
Chinesedumps-host12:
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
Enable highly available internet access for the FABD2 company network according to these
w
requirements:
w
On routers r12, r23 and r24, bring up IPv4 BGP peerings with the ISP, make sure that a default
route is received over these peerings
w
On router r12 and r23, inject default route into OSPF if it present in the routing table from a
.p
different routing source than the OSPFv2 process 1. On each router, this requirement must be
completed using the minimum possible number of commands
as
On route r24, inject default route into OSPF if any only if it is learned from ISP over BGP. To
accomplish this requirement, it is allowed to use a route-map that referenced both a prefix-list
and tag. This requirement must be completed using the minimum possible number of
se
commands
Router r12 may be used as an internet exit for the FABD2 company network only if neither r23
nt
nor r24 are advertising the default route in OSPF. This requirement must be accomplished
exclusively in “router ospf” mode on router r12 without changing the default parameters on
er
10.0.0.0/8 to the router address on the link toward the ISP. Create a standard ACL named NAT
for this purpose. Do not use NAT pools
is
Ensure that the internet connectivity of the FABD2 company network makes use of the highly
availability provided by r12, r23 and r24.
el
ab
1 Point
s .c
om
Solution:
Chinesedumps.com-r12:
w
r12(config)#router ospf 1
as
r12(config-router)#default-information originate
r12(config)#int g0/0
se
r12(config)#int lo0
r12(config-if)#ip nat inside
er
Chinesedumps.com-r23:
is
r23(config)#int g1
s
r23(config)#int lo0
r23(config-if)#ip nat inside
r23(config-if)#ip access-list standard NAT
r23(config-if)#permit 10.0.0.0 0.255.255.255
r23(config-if)#ip nat inside source list NAT interface g1 overload
Chinesedumps.com-r24:
r24(config)#router ospf 1
r24(config-router)#default-information originate route-map ISP metric-type 1
se
r24(config)#interface g1
r24(config-if)#ip nat outside
r24(config-if)#int range g2-4,tunnel 0
nt
r24(config-router-af)#topology base
r24(config-router-af)#summary-metric 0.0.0.0/0 distance 254
ab
s .c
om
Verification:
Chinesedumps.com-r24:sh ip route
w
w
w
.p
as
se
nt
er
pr
Chinesedumps.com-r23:sh ip route
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
Chinesedumps.com-r24: sh ip route
pr
is
el
ab
s .c
om
it will place them into maintenance mode due to their serial number being different from the one DNA
center remember. In addition, their management IP addresses in DNA Center will be automatically
w
changed by appending them with the “.dummy.com” string. As a result, after an initial contact, DNA
Center will lose connectivity with the switches unless their management IP addresses are corrected in
w
Correct the IP addresses of managed switches in the DNA center according to the following
requirements:
as
Use any host, such as host11, to access the DNA Center GUI website at https://203.0.113.11
se
URL.
Execute the Provision – Devices – Inventory – Global – Actions – Inventory - Resync Device
action in DNA Center on all switches before proceeding further.
nt
Note: These IP addresses cannot be changed from DNA Center GUI directly because they will become
automatically invalidated again. This is a built-in DNA Center behavior.
el
ab
3 points
s .c
om
Solution:
Step 1:
w
Above Output will be displayed for all the 3 switches (sw400 , sw501 , sw502 )
er
Step 2:
pr
https://10.2.254.11/dna/apitester
el
ab
s .c
om
Step 3:
Step 4:
Step 5:
- Scroll down and at the right hand side you will see Model Schema
w
Step 6:
{
ab
"newMgmtIpAddress": "10.4.1.2",
"existMgmtIpAddress": "10.4.255.11dummy.com"
}
s .c
om
Step 7:
nt
Using the DNA Center GUI, perform configuration tasks according to these requirements:
w
Add new virtual Network named IoT for the internet-of-things network on the Branches #1 & #2
w
Create new address pools for the IoT VN named Branch1-For IoT and Branch2-For IoT on the
w
For Branch #2 loT VN, allocate the subnet 10.5.198.0/24, and the gateway IP address
10.5.198.1.
as
Associate the Branch1-loT and Branch2-loT pools with the loT VN on the respective branches.
Complete the configuration of the address pools for the Guest VN in the DNA Center so that
se
Branch #1 and Branch #2 can accommodate guest connections. If a new address pool needs to
be created and an address range allocated to it, follow the established addressing plan.
Correct the addressing information currently defined for the Branch2-For Employees and
nt
Create four new DHCP pools for the loT and Employees VNs on respective branches
is
In each subset, assign addresses from .101 up to .254 inclusively, and the appropriate gateway
to clients.
s .c
3 Points
om
Solution:
Step 1:
w
w
www.chinesedumps.com
w
.p
as
Note: The pools that will be pre-configured will not have DHCP server attached with them , so we
se
need to add DHCP server before moving forward to create other pools
e. Select Branch1_Emp pool and add DHCP server and reserve it to Fabric again
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
f. Edit the Branch1_Emp pool and add DHCP as shown and then save it
g. Just again add the pool to fabric
Step 2:
Click Add
w
w
.p
as
www.chinesedumps.com
se
nt
IP 10.4.198.0/24
pr
Step 3:
ab
www.chinesedumps.com
www.chinesedumps.com
w
w
.p
as
se
Click reserve.
is
(Verify that the employee IP pool have the DHCP server selected and have the correct gateway and is
ab
(If a new Guest IP pool is needed to be created. Configure them in the same way as IoT but different
.c
IP range)
om
Step 4:
www.chinesedumps.com
Step 5:
w
Select Host Onboarding > Virual Networks and click Add Virtual Network
.p
www.chinesedumps.com
as
se
nt
www.chinesedumps.com
er
pr
Select the VN IoT and click update. The click on the Grey VN Iot
is
www.chinesedumps.com
el
ab
www.chinesedumps.com
s .c
om
www.chinesedumps.com
w
w
w
.p
as
www.chinesedumps.com
se
Step 6:
pr
exit
.c
Use any host, such as host11, to access the vManage GUI website at https://203.0.113.21 URL.
w
o Create a new sub-interface on the interface toward the SDA border switch. Align the
VLAN ID and IP address on the sub interface with the configuration generated by DNA
se
4 Points
pr
is
el
ab
s .c
om
Solution:
Step 1:
w
Select the device template where the Branch Vedges are attached. Click the Three dots <…> and Edit
w
Device Template.
w
.p
www.chinesedumps.com
as
se
www.chinesedumps.com
is
el
ab
www.chinesedumps.com
.c
om
Give the template a name and add the VPN number 198
w
www.chinesedumps.com
w
w
.p
as
www.chinesedumps.com
se
www.chinesedumps.com
is
el
Step 2:
www.chinesedumps.com
w
.p
as
se
www.chinesedumps.com
pr
is
www.chinesedumps.com
el
Press the BGP drop down bar and press create template.
ab
Under Unicast Address Family click New Redistribute and under Protocol choose OMP and click Add.
om
www.chinesedumps.com
w
w
.p
www.chinesedumps.com
as
Change Address to device specific and click Add. Then Click Save
nt
er
www.chinesedumps.com
pr
is
el
Step 3:
ab
www.chinesedumps.com
w
www.chinesedumps.com
w
w
.p
as
se
www.chinesedumps.com
er
pr
Under Advanced change the MTU to be Global 1496 and click Save.
is
www.chinesedumps.com
el
ab
Add both template that was created and click Add and the press Update\
s .c
om
www.chinesedumps.com
Click the three dots on the right to add the deivces values <…> For branch1 Router vEdge 40 Set BGP AS
number to 65004 and Vedge 51 and 52 AS 65005
w
www.chinesedumps.com
w
w
.p
Then click Update and Next and push the config to the devices.
.c
Step 4:
om
*DNA center should have generated VRFs for Employee VN, Guest VN and IoT VN.
Under Sw 400
Add Network statement of the IP pools that was created in DNAC in question 2.1
Repeat this configuration for switch 501 and 502
s .c
om
To allow the traditional parts of the FABD2 network to communication with the employees and IoT
w
Prefixes in the IoT VPN 198 must be imported into the existing SDA Underlay VPN 999 and
w
range must be rejected. Other prefixes in the SDA underlay VPN 999 advertise from DC must be
accepted and also imported into IoT VPN 198 and Employees VPN 200
se
Redistribution from OMP into OSPF on Branches #1 and #2 in VPN 999 must exclude vRoutes
tagged with values 198 or 200.
Place host41 into Employees VN. Place host51 into IoT VN. Make sure both hosts receive their
nt
#3 and #4. It is allowed to modify the VPN 999 OMP settings to accomplish this requirement.
pr
3 Points
is
el
ab
s .c
om
Solution:
Step 1:
w
Step 2:
Step 3:
is
Now under centralized Policy check in the site tab which sites are pre-configured then hit NEXT at the
bottom of the page
el
ab
s .c
om
Step 5:
Step 6:
el
Step 7:
Select VPN list under Match Conditions and add a new VPN list
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
Step 8:
Go to Actions Tab
w
Select Accept
w
Select Export to and create a New VPN list VPN 999 (If not present already)
.p
as
se
nt
er
pr
is
el
ab
s .c
om
Step 9:
Step 10:
ab
Step 11:
Step 12:
er
Step 13:
Click on Add Topology and select Custom Control to add another Policy
w
w
w
.p
as
se
nt
er
pr
is
Step 14:
el
Step 15:
Select Prefix-list
w
Add New-Prefix-list
w
.p
as
se
nt
er
pr
is
el
ab
s .c
om
Step 16:
Go to Actions
Select Accept
w
Select VPN list 198-200 under Export To and Save Match and Actions
Step 17:
nt
Step 18:
er
Policy Name
is
Description
el
Under Import-DC
ab
Under Import-Branch
om
Step 19:
Add Description
nt
Hit NEXT
as
se
nt
er
pr
is
el
ab
s .c
om
Step 20:
Add Policy
.p
as
se
nt
er
pr
is
el
ab
s .c
om
Go to Branch 1 OSPF VPN 999 Feature Template and add the tag under New redistribution
w
w
w
.p
as
se
nt
er
pr
is
el
ab
s .c
Click on Update
om
The guest VN/VPN on Branches #1 and #2 must remain isolated from the rest of the company network.
w
It is only allowed to reach internet through r23 and r24 in the DC. Enable internet connectivity for the
Guest VPN according to these requirements:
w
On vedge21 and vedge22, place the ge0/2 interfaces into the Guest VPN 199.
On r23 and r24, create a new VRF named Guest using the RD of 65002:199, and place the gi4
w
Ensure that r23 and r24 learn the routes in the Guest VRF/VPN over iBGP.
On r23 and r24, configure a static default route in the Guest VRF and point it to the ISP’s IP
er
On r23 and r24, configure PAT to allow the Guest VPN to access internet by translating it to the
router address on the link toward the ISP. Reuse the NAT ACL already created on the router. Do
is
Configure r23 as the DHCP server for Guest VPN according to these requirements:
ab
Create Loopback1 interface on r23 associated with the Guest VRF and having the IP address
10.2.255.211/32
s
Solution:
r23
w
rd 65002:199
address-fam ipv4
.p
exit
as
int gi 4
vrf for Guest
ip add 10.2.123.1 255.255.255.0
se
ip nat inside
int gi 1
nt
ip nat out
exit
er
int loo1
vrf for Guest
ip add 10.2.255.211
exit
default-router 10.4.199.1
class branch1
w
default-router 10.5.199.1
class branch2
address range 10.5.199.101 10.5.199.254
nt
r24
pr
address-fam ipv4
exit
el
int gi 4
ab
int gi 1
ip nat out
om
Step 1:
as
In DC Device Templates
se
Click SAVE
is
Step 2:
ab
Go Under DNAC
s
Select Branch 1
w
w
w
.p
as
se
nt
er
Go to Host Onboarding
pr
is
el
ab
s .c
om
This item consists of multiple questions. You may need to scroll down to be able to see all questions.
w
In future, Branch #2 will be equipped with IP-based IoT endpoints operating in speak-when-spoken-to
mode, also called silent hosts. Which of the following SDA features enables a working connectivity with
w
o Native Multicast
o Endpoint Mobility
.p
o Layer 2 Flooding
o Layer 2 Extension
as
In the statement below, select one of the options from the drop-down list to complete the sentence
se
Options:
o IP multicast routing with PIM-SM must be enabled
pr
3 Points
s
There is no direct console access provided to the router r30. Moreover, r30 does not accept any
w
remote connections because its VTY lines are configured with transport input none. Using RESTCONF,
enable remote access to r30 for all remote access protocols, according to these requirements:
w
You can use host31 to access router r30 using IP address 10.3.11.1
w
You can use any method of accessing the RESTCONF API on r30 from host31, including curl,
.p
Python, or Postman
You must change the input transport protocol on all configurable VTY lines
as
The input transport protocol value setting must be changed from none to all
Important parameters:
se
URL
er
https://10.3.11.1:443/restconf/data/Cisco-IOS-XE-native/line/vty
HTTP method to retrieve the configuration
pr
GET
HTTP method to modify the configuration
is
PATCH
HTTP headers
el
Content-Type: application/yang-data+json
Accept: application/yang-data+json
ab
2 Points
om
Solution:
On Chinesedumps.com-r30:
w
Chinesedumps.com-r30#conf t
w
Chinesedumps.com-r30(config)# restconf
Chinesedumps.com-r30(config)#interface GigabitEthernet2
se
Chinesedumps.com-r30(config-if)#no shutdown
Chinesedumps.com-r30(config-if)#ip address 10.3.11.1 255.255.255.0
Chinesedumps.com-r30(config-if)#negotiation auto
nt
er
Step 1:
pr
Open Linux machine host31 and check reachability for r30 , also check restconf reachability
is
el
ab
s .c
om
Step 2:
Step 3:
www.chinesedumps.com
as
www.chinesedumps.com
se
nt
er
www.chinesedumps.com
pr
Step 4:
is
www.chinesedumps.com
om
www.chinesedumps.com
Step 5:
www.chinesedumps.com
.p
as
se
nt
er
pr
is
www.chinesedumps.com
el
ab
Step 6:
www.chinesedumps.com
om
Step 7:
www.chinesedumps.com
as
se
Step 8:
nt
www.chinesedumps.com
is
el
ab
s .c
om
Step 9:
HTTP headers
w
Content-Type: application/yang-data+json
Accept: application/yang-data+json
w
.p
www.chinesedumps.com
as
se
nt
Step 10:
er
URL
is
https://10.3.11.1:443/restconf/data/Cisco-IOS-XE-native:native/line/vty
el
ab
s .c
www.chinesedumps.com
om
Step 11:
www.chinesedumps.com
as
se
www.chinesedumps.com
nt
er
Step 12:
pr
www.chinesedumps.com
s .c
om
Step 13:
www.chinesedumps.com
.p
as
se
www.chinesedumps.com
nt
er
pr
is
el
ab
s .c
om
Verification:
www.chinesedumps.com
se
nt
er
pr
is
el
www.chinesedumps.com
ab
s .c
om
these requirements:
w
If an additional IP network is necessary to start guestshell, you are allowed to use addresses
w
from the range 192.168.255.0/24. This range must not be advertised in any routing protocol.
The python script must be saved under the name ribdump.py in the home directory of the
.p
guestshell user.
The purpose of the script is to display the complete contents of all routing tables in non-default
as
non default VRF created on the router, depending on what address families are enabled in that
VRF.
The script must determine the list of created VRFs and enabled address families dynamically
nt
every time it is run using, for example, show vrf brief | include ipv
The script must not attempt to display the VRF routing table for an address family that is not
er
3 Points
el
ab
s .c
om
Solution:
- Intent of script
- Execute command "show vrf brief | include ipv" and store output in a variable named vrf
w
- And execute the "show ipvx route vrf x" command per vrf, keep the output in variable and print
the variable
.p
as
Chinesedumps.com-r30
r30#conf t
se
r30(config)#iox
r30(config)#interface VirtualPortGroup0
nt
r30(config)#name-server0 8.8.8.8
r30(config)#end
el
*Block this prefix to get advertised out in case connected redistribute or network statement is
ab
r30#guestshell enable
om
*you will get its Linux BASH shell (most of linux bash shell commands will run)
*create a file named rib dump using vi editor (better learn the shortcut/commands to use vi editor)
w
vi ribdump.py
w
import sys
se
import cli
ipv6 = False
vrfString = line.split()
pr
if(vrfString[2] == "ipv4"):
ipv4 = True
elif(vrfString[2] == "ipv6"):
is
ipv6 = True
elif(vrfString[2] == "ipv4,ipv6"):
el
ipv4 = True
ipv6 = True
ab
if(ipv4 == True):
vrfv4 = cli.execute('show ip route vrf ' + vrfString[0])
print(vrfv4)
s
if(ipv6 == True):
.c
guestshell ls
.p
as
se
nt
er
pr
is
el
ab
s .c
om
Alternate Solution:
Chinesedumps.com-r30
w
conf t
w
iox
w
interface VirtualPortGroup0
ip address 192.168.255.1 255.255.255.0
.p
ip nat inside
exit
as
end
int gi1.100
is
ip nat outside
el
guestshell enable
guestshell run bash
ab
vi ripdump.py
s
import sys
w
import cli
w
ipv4 = False
ipv6 = False
.p
vrfString = line.split()
if(vrfString[2] == "ipv4"):
as
ipv4 = True
elif(vrfString[2] == "ipv6"):
ipv6 = True
se
elif(vrfString[2] == "ipv4,ipv6"):
ipv4 = True
ipv6 = True
nt
if(ipv4 == True):
vrfv4 = cli.execute('show ip route vrf ' + vrfString[0])
er
print(vrfv4)
if(ipv6 == True):
pr
You are tasked with writing a python script to back up the configuration of a number of IOS-XE devices
through RESTCONF, and store the configurations in text files. The starting section of this script has
w
#!/usr/bin/python3
.p
import requests
as
This script needs to be completed by dragging the individual’s command lines below into their correct
order to allow the script to correctly accomplish its purpose. Indicate the ends of the for block and of
er
the while block by properly placing the “- -End of for” and “- - End of while” symbols.
pr
Drag the lines into their correct order to complete the script as required. Make sure to also properly
place the “- - End of for” and “- - End of with” symbols to indicate the end of the respective blocks in
is
code.
el
There are plans to extend the script to display a list of known IOS-XE devices by their IP addresses and
allow the administrator to select which devices to backup. Aside from other necessary changes in the
script, which of the following storage options for the credentials would allow for the most straight
w
forward implementation?
w
o Credentials = “192.168.1.1,admin,s3cr3t,” \
“192.168.1.2,netadmin,oth3rs3cr3t”
as
2 Points
nt
er
pr
is
el
ab
s .c
om
Solution:
URL=f"https://{ip}:443/restconf/data/cisco-IOS-XE-native:native"
Response=request.get(URL,auth=(login,Password),headers=Headers,verify=false)
w
file.write(reponse.text)let
end of with
.p
end of for
as
se
Answer: B
nt
er
pr
is
el
ab
s .c
om