成长值: 25540
|
CCIE EI 中DNA centre 能否可以用EVE-NG5 h8 }# }$ o) Z/ p( d" [" y% y$ Q
2 E8 x L1 ?5 I. S1 v& z& L8 j5 e
需求:
4 ~$ |% y: r, g% z" _0 C* Q
2 U( n! ?% l% F2.1: Correcting the IP addresses of Managed switches in DNA center
2 c1 p$ X% Y' w: sAfter Cisco DNA center first achieves IP connectivity with the managed switches in Branches #1 and #2, 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 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 the DNA center settings.
3 F y }8 [" k% j& B \& UCorrect the IP addresses of managed switches in the DNA center according to the following requirements:
/ E# b* N2 k" w. h Use any host, such as host11, to access the DNA Center GUI website at https://203.0.113.11 URL., G% l2 w5 D7 o
 Execute the provision-Devices- Inventory- Global- Actions-Inventory- Resync Device action in DNA Center on all switches before proceeding further.2 x$ s0 \0 O8 C9 ~2 f3 Y
 DNA Center API reference and sandbox is available at http://203.0.113.11/dna/apitester URL.$ w3 z6 t. i. |0 m, n+ f9 l
 The /network/device/update-maintenance-device-ip-address API call description and sandbox are available in the Inventory section of the API reference.# ~$ f0 g1 Q' X2 Y) Q
 Use the /network-device/update-maintenance-device-ip address API call to correct the IP addresses of the switches in Branches #1 and #2 by removing the appended text.( R# T, s- k* H* p1 D
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.
$ c" C: e& Y; e( b9 N$ I% H, O& W# Z, i0 j6 r2 j
9 L% n7 v6 b5 c2.2: Completing VN Configuration in DNA center
1 M9 q! g2 [9 m. S# ZUsing the DNA Center GUI, perform configuration tasks according to these requirements:% z- x- U" t1 [$ `: O, j
3 y8 l9 y% e+ V+ P0 o Add new virtual Network named IoT for the internet-of-things network on the Branches #1 and #2
i; G0 B1 h# q: h- X" Z Create new address pools for the IoT VN named Branch1- ForIoT and Branch2-ForIoT on the global level, and branch1-IoT and Branch2-IoT on the Branch level.
! S% U/ q* `& J; A For Branch #1 loT VN, allocate the subnet 10.4.198.0/24 and the gateway IP address 10.4.198.1.
+ ^" h% B# _) h7 c% _, v* B For Branch #2 loT VN, allocate the subnet 10.5.198.0/24, and the gateway IP address 10.5.198.1.
% V; { N: w3 G Associate the Branch1-loT and Branch2-loT pools with the loT VN on the respective branches.% b* M, v* K1 L& S( U
 Complete the configuration of the address pools for the Guest VN in the DNA Center so that 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.( B+ Z, q9 q# f: |. ^
 Correct the addressing information currently defined for the Branch2- For Employees and Branch2- Employees address pool.
$ y. J7 B# d+ `9 D( B7 @, {* Z3 } For all address pools, use the DHCP server 10.2.255.211 to allocate addresses to clients.
+ m) P0 t: j$ H7 a9 ]# t, T% E( t8 ~
On sw211, complete the DHCP server configuration according to these requirements:2 T/ d0 d+ i$ O1 {0 O) q
; R. H! H) U3 I$ L( N
 Create four new DHCP pools for the loT and Employees VNs on respective branches
5 u' M; {2 @9 |9 ~0 j Pool named br1_iot for Branch #1 loT VN$ q1 Y, F0 E1 q d
 Pool named br1_emp for Branch #1 Employees VN
& @) y8 }+ F# U: n) J Pool named br2_iot for Branch #2 loT VN
# S9 `! l" F% g Pool named br2_emp for Branch #2 Employees VN
6 `9 T4 g! B9 B/ O. c/ l* B8 ~: D7 O3 C In each subet, assign addresses from .101 up to .254 inclusively, and the appropriate gateway to clients.
2 ]3 S6 m( J$ `( x( k+ h
, U* {/ d5 o2 V+ ] M* B |
|