Halo, habr. Aku saiki dadi pimpinan kursus kanggo kursus Network Engineer ing OTUS.
Ing nunggu wiwitan enrollment anyar kanggo mesthi
Ana akeh materi babagan cara kerja VxLAN EVPN, mula aku pengin ngumpulake macem-macem tugas lan praktik kanggo ngrampungake masalah ing pusat data modern.
Ing bagΓ©yan pisanan saka seri ing teknologi VxLAN EVPN, Aku pengin katon ing cara kanggo ngatur konektivitas L2 antarane sarwa dumadi ing ndhuwur kain jaringan.
Kabeh conto bakal dileksanakake ing Cisco Nexus 9000v, nglumpuk ing topologi Spine-Leaf. Kita ora bakal mikir babagan nyetel jaringan Underlay ing artikel iki.
- Jaringan dhasar
- BGP peering kanggo alamat-kulawarga l2vpn evpn
- Nyetel NVE
- Suppress-arp
Jaringan dhasar
Topologi sing digunakake kaya ing ngisor iki:
Ayo nyetel alamat ing kabeh piranti:
Spine-1 - 10.255.1.101
Spine-2 - 10.255.1.102
Leaf-11 - 10.255.1.11
Leaf-12 - 10.255.1.12
Leaf-21 - 10.255.1.21
Host-1 - 192.168.10.10
Host-2 - 192.168.10.20
Ayo priksa manawa ana konektivitas IP ing antarane kabeh piranti:
Leaf21# sh ip route
<........>
10.255.1.11/32, ubest/mbest: 2/0 ! Leaf-11 Π΄ΠΎΡΡΡΠΏΠ΅Π½ ΡΠ΅Π΅ΡΠ· Π΄Π²Π° Spine
*via 10.255.1.101, Eth1/4, [110/81], 00:00:03, ospf-UNDERLAY, intra
*via 10.255.1.102, Eth1/3, [110/81], 00:00:03, ospf-UNDERLAY, intra
10.255.1.12/32, ubest/mbest: 2/0 ! Leaf-12 Π΄ΠΎΡΡΡΠΏΠ΅Π½ ΡΠ΅Π΅ΡΠ· Π΄Π²Π° Spine
*via 10.255.1.101, Eth1/4, [110/81], 00:00:03, ospf-UNDERLAY, intra
*via 10.255.1.102, Eth1/3, [110/81], 00:00:03, ospf-UNDERLAY, intra
10.255.1.21/32, ubest/mbest: 2/0, attached
*via 10.255.1.22, Lo0, [0/0], 00:02:20, local
*via 10.255.1.22, Lo0, [0/0], 00:02:20, direct
10.255.1.101/32, ubest/mbest: 1/0
*via 10.255.1.101, Eth1/4, [110/41], 00:00:06, ospf-UNDERLAY, intra
10.255.1.102/32, ubest/mbest: 1/0
*via 10.255.1.102, Eth1/3, [110/41], 00:00:03, ospf-UNDERLAY, intra
Ayo priksa manawa domain VPC wis digawe lan loro switch wis lulus mriksa konsistensi lan setelan ing loro simpul padha:
Leaf11# show vpc
vPC domain id : 1
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status : success
Per-vlan consistency status : success
Type-2 consistency status : success
vPC role : primary
Number of vPCs configured : 0
Peer Gateway : Disabled
Dual-active excluded VLANs : -
Graceful Consistency Check : Enabled
Auto-recovery status : Disabled
Delay-restore status : Timer is off.(timeout = 30s)
Delay-restore SVI status : Timer is off.(timeout = 10s)
Operational Layer3 Peer-router : Disabled
vPC status
----------------------------------------------------------------------------
Id Port Status Consistency Reason Active vlans
-- ------------ ------ ----------- ------ ---------------
5 Po5 up success success 1
BGP peering
Pungkasan, sampeyan bisa nerusake nyetel jaringan Overlay.
Minangka bagΓ©an saka artikel, perlu kanggo ngatur jaringan antarane host, minangka ditampilake ing diagram ing ngisor iki:
Kanggo ngatur jaringan Overlay, sampeyan kudu ngaktifake BGP ing Spine lan Leaf switch kanthi dhukungan kanggo kulawarga l2vpn evpn:
feature bgp
nv overlay evpn
Sabanjure, sampeyan kudu ngatur peering BGP antarane Leaf lan Spine. Kanggo nyederhanakake persiyapan lan ngoptimalake distribusi informasi rute, kita ngatur Spine minangka server Route-Reflector. Kita bakal nulis kabeh Leaf ing konfigurasi nggunakake template kanggo ngoptimalake persiyapan.
Dadi setelan ing Spine katon kaya iki:
router bgp 65001
template peer LEAF
remote-as 65001
update-source loopback0
address-family l2vpn evpn
send-community
send-community extended
route-reflector-client
neighbor 10.255.1.11
inherit peer LEAF
neighbor 10.255.1.12
inherit peer LEAF
neighbor 10.255.1.21
inherit peer LEAF
Persiyapan ing switch Leaf katon padha:
router bgp 65001
template peer SPINE
remote-as 65001
update-source loopback0
address-family l2vpn evpn
send-community
send-community extended
neighbor 10.255.1.101
inherit peer SPINE
neighbor 10.255.1.102
inherit peer SPINE
Ing Spine, ayo mriksa peering karo kabeh switch Leaf:
Spine1# sh bgp l2vpn evpn summary
<.....>
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
10.255.1.11 4 65001 7 8 6 0 0 00:01:45 0
10.255.1.12 4 65001 7 7 6 0 0 00:01:16 0
10.255.1.21 4 65001 7 7 6 0 0 00:01:01 0
Nalika sampeyan bisa ndeleng, ora ana masalah karo BGP. Ayo dadi pindhah menyang nyetel VxLAN. Konfigurasi luwih bakal ditindakake mung ing sisih Leaf switch. Spine tumindak mung minangka inti saka jaringan lan mung melu ngirimaken lalu lintas. Kabeh kerja enkapsulasi lan penentuan path mung ana ing switch Leaf.
Nyetel NVE
NVE - antarmuka virtual jaringan
Sadurunge miwiti persiyapan, ayo ngenalake sawetara terminologi:
VTEP - Vitual Tunnel End Point, piranti ing ngendi trowongan VxLAN diwiwiti utawa rampung. VTEP ora kudu piranti jaringan apa wae. Server sing ndhukung teknologi VxLAN uga bisa dadi server. Ing topologi kita, kabeh switch Leaf yaiku VTEP.
VNI - Indeks Jaringan Virtual - pengenal jaringan ing VxLAN. Analogi bisa digambar nganggo VLAN. Nanging, ana sawetara beda. Nalika nggunakake kain, VLAN dadi unik mung ing saklar Leaf lan ora ditularakΓ© liwat jaringan. Nanging saben VLAN bisa duwe nomer VNI gadhah, kang wis ditularakΓ© liwat jaringan. Apa sing katon lan carane bisa digunakake bakal dibahas luwih lanjut.
Ayo ngaktifake fitur teknologi VxLAN lan kemampuan kanggo nggandhengake nomer VLAN karo nomer VNI:
feature nv overlay
feature vn-segment-vlan-based
Ayo dadi ngatur antarmuka NVE, sing tanggung jawab kanggo operasi VxLAN. Antarmuka iki tanggung jawab kanggo encapsulating pigura ing header VxLAN. Sampeyan bisa nggambar analogi karo antarmuka Tunnel kanggo GRE:
interface nve1
no shutdown
host-reachability protocol bgp ! ΠΈΡΠΏΠΎΠ»ΡΠ·ΡΠ΅ΠΌ BGP Π΄Π»Ρ ΠΏΠ΅ΡΠ΅Π΄Π°ΡΠΈ ΠΌΠ°ΡΡΡΡΡΠ½ΠΎΠΉ ΠΈΠ½ΡΠΎΡΠΌΠ°ΡΠΈΠΈ
source-interface loopback0 ! ΠΈΠ½ΡΠ΅ΡΡΠ΅ΠΉΡ Ρ ΠΊΠΎΡΠΎΡΠΎΠ³ΠΎ ΠΎΡΠΏΡΠ°Π²Π»ΡΠ΅ΠΌ ΠΏΠ°ΠΊΠ΅ΡΡ loopback0
Ing saklar Leaf-21 kabeh digawe tanpa masalah. Nanging, yen kita mriksa output saka printah show nve peers
, banjur bakal kosong. Ing kene sampeyan kudu bali menyang konfigurasi VPC. Kita weruh yen Leaf-11 lan Leaf-12 bisa digunakake kanthi pasangan lan digabungake karo domain VPC. Iki menehi kita kahanan ing ngisor iki:
Host-2 ngirim siji pigura menyang Leaf-21 supaya ngirim liwat jaringan menyang Host-1. Nanging, Leaf-21 ndeleng manawa alamat MAC Host-1 bisa diakses liwat rong VTEP bebarengan. Apa sing kudu ditindakake Leaf-21 ing kasus iki? Sawise kabeh, iki tegese loop bisa katon ing jaringan.
Kanggo ngatasi kahanan iki, kita butuh Leaf-11 lan Leaf-12 kanggo uga minangka salah sawijining piranti ing pabrik. Solusi kasebut cukup prasaja. Ing antarmuka Loopback saka kang kita mbangun trowongan, nambah alamat secondary. Alamat Secondary kudu padha ing loro VTEPs.
interface loopback0
ip add 10.255.1.10/32 secondary
Dadi, saka sudut pandang VTEP liyane, kita entuk topologi ing ngisor iki:
Tegese, saiki trowongan bakal dibangun ing antarane alamat IP Leaf-21 lan IP virtual antarane loro Leaf-11 lan Leaf-12. Saiki ora bakal ana masalah sinau alamat MAC saka rong piranti lan lalu lintas bisa pindhah saka siji VTEP menyang liyane. Endi saka loro VTEP sing bakal ngolah lalu lintas diputusake nggunakake tabel rute ing Spine:
Spine1# sh ip route
<.....>
10.255.1.10/32, ubest/mbest: 2/0
*via 10.255.1.11, Eth1/1, [110/41], 1d01h, ospf-UNDERLAY, intra
*via 10.255.1.12, Eth1/2, [110/41], 1d01h, ospf-UNDERLAY, intra
10.255.1.11/32, ubest/mbest: 1/0
*via 10.255.1.11, Eth1/1, [110/41], 1d22h, ospf-UNDERLAY, intra
10.255.1.12/32, ubest/mbest: 1/0
*via 10.255.1.12, Eth1/2, [110/41], 1d01h, ospf-UNDERLAY, intra
Nalika sampeyan bisa ndeleng ndhuwur, alamat 10.255.1.10 kasedhiya langsung liwat loro Sabanjure-hops.
Ing tahap iki, kita wis ngrampungake konektivitas dhasar. Ayo pindhah menyang nyiyapake antarmuka NVE:
Ayo langsung ngaktifake Vlan 10 lan digandhengake karo VNI 10000 ing saben Leaf kanggo host. Ayo nyiyapake trowongan L2 antarane host
vlan 10 ! ΠΠΊΠ»ΡΡΠ°Π΅ΠΌ VLAN Π½Π° Π²ΡΠ΅Ρ
VTEP ΠΏΠΎΠ΄ΠΊΠ»ΡΡΠ΅Π½Π½ΡΡ
ΠΊ Π½Π΅ΠΎΠ±Ρ
ΠΎΠ΄ΠΈΠΌΡΠΌ Ρ
ΠΎΡΡΠ°ΠΌ
vn-segment 10000 ! ΠΡΡΠΎΡΠΈΠΈΡΡΠ΅ΠΌ VLAN Ρ Π½ΠΎΠΌΠ΅Ρ VNI
interface nve1
member vni 10000 ! ΠΠΎΠ±Π°Π²Π»ΡΠ΅ΠΌ VNI 10000 Π΄Π»Ρ ΡΠ°Π±ΠΎΡΡ ΡΠ΅ΡΠ΅Π· ΠΈΠ½ΡΠ΅ΡΡΠ΅ΠΉΡ NVE. Π΄Π»Ρ ΠΈΠ½ΠΊΠ°ΠΏΡΡΠ»ΡΡΠΈΠΈ Π² VxLAN
ingress-replication protocol bgp ! ΡΠΊΠ°Π·ΡΠ²Π°Π΅ΠΌ, ΡΡΠΎ Π΄Π»Ρ ΡΠ°ΡΠΏΡΠΎΡΡΡΠ°Π½Π΅Π½ΠΈΡ ΠΈΠ½ΡΠΎΡΠΌΠ°ΡΠΈΠΈ ΠΎ Ρ
ΠΎΡΡΠ΅ ΠΈΡΠΏΠΎΠ»ΡΠ·ΡΠ΅ΠΌ BGP
Saiki ayo mriksa kanca lan tabel kanggo BGP EVPN:
Leaf21# sh nve peers
Interface Peer-IP State LearnType Uptime Router-Mac
--------- --------------- ----- --------- -------- -----------------
nve1 10.255.1.10 Up CP 00:00:41 n/a ! ΠΠΈΠ΄ΠΈΠΌ ΡΡΠΎ peer Π΄ΠΎΡΡΡΠΏΠ΅Π½ Ρ secondary Π°Π΄ΡΠ΅ΡΠ°
Leaf11# sh bgp l2vpn evpn
Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 10.255.1.11:32777 (L2VNI 10000) ! ΠΡ ΠΊΠΎΠ³ΠΎ ΠΈΠΌΠ΅Π½Π½ΠΎ ΠΏΡΠΈΡΠ΅Π» ΡΡΠΎΡ l2VNI
*>l[3]:[0]:[32]:[10.255.1.10]/88 ! EVPN route-type 3 - ΠΏΠΎΠΊΠ°Π·ΡΠ²Π°Π΅Ρ Π½Π°ΡΠ΅Π³ΠΎ ΡΠΎΡΠ΅Π΄Π°, ΠΊΠΎΡΠΎΡΡΠΉ ΡΠ°ΠΊ ΠΆΠ΅ Π·Π½Π°Π΅Ρ ΠΎΠ± l2VNI10000
10.255.1.10 100 32768 i
*>i[3]:[0]:[32]:[10.255.1.20]/88
10.255.1.20 100 0 i
* i 10.255.1.20 100 0 i
Route Distinguisher: 10.255.1.21:32777
* i[3]:[0]:[32]:[10.255.1.20]/88
10.255.1.20 100 0 i
*>i 10.255.1.20 100 0 i
Ndhuwur kita mung ndeleng rute EVPN-jinis 3. Jinis rute iki ngomong babagan peer(Leaf), nanging ing ngendi host kita?
Masalahe yaiku informasi babagan host MAC dikirim liwat EVPN route-type 2
Kanggo ndeleng host kita, sampeyan kudu ngatur EVPN route-type 2:
evpn
vni 10000 l2
route-target import auto ! Π² ΡΠ°ΠΌΠΊΠ°Ρ
Π΄Π°Π½Π½ΠΎΠΉ ΡΡΠ°ΡΡΠΈ ΠΈΡΠΏΠΎΠ»ΡΠ·ΡΠ΅ΠΌ Π°Π²ΡΠΎΠΌΠ°ΡΠΈΡΠ΅ΡΠΊΠΈΠΉ Π½ΠΎΠΌΠ΅Ρ Π΄Π»Ρ route-target
route-target export auto
Ayo ping saka Host-2 menyang Host-1:
Firewall2# ping 192.168.10.1
PING 192.168.10.1 (192.168.10.1): 56 data bytes
36 bytes from 192.168.10.2: Destination Host Unreachable
Request 0 timed out
64 bytes from 192.168.10.1: icmp_seq=1 ttl=254 time=215.555 ms
64 bytes from 192.168.10.1: icmp_seq=2 ttl=254 time=38.756 ms
64 bytes from 192.168.10.1: icmp_seq=3 ttl=254 time=42.484 ms
64 bytes from 192.168.10.1: icmp_seq=4 ttl=254 time=40.983 ms
Lan ing ngisor iki kita bisa ndeleng manawa rute-jinis 2 kanthi alamat MAC host katon ing tabel BGP - 5001.0007.0007 lan 5001.0008.0007
Leaf11# sh bgp l2vpn evpn
<......>
Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 10.255.1.11:32777 (L2VNI 10000)
*>l[2]:[0]:[0]:[48]:[5001.0007.0007]:[0]:[0.0.0.0]/216 ! evpn route-type 2 ΠΈ mac Π°Π΄ΡΠ΅Ρ Ρ
ΠΎΡΡΠ° 1
10.255.1.10 100 32768 i
*>i[2]:[0]:[0]:[48]:[5001.0008.0007]:[0]:[0.0.0.0]/216 ! evpn route-type 2 ΠΈ mac Π°Π΄ΡΠ΅Ρ Ρ
ΠΎΡΡΠ° 2
* i 10.255.1.20 100 0 i
*>l[3]:[0]:[32]:[10.255.1.10]/88
10.255.1.10 100 32768 i
Route Distinguisher: 10.255.1.21:32777
* i[2]:[0]:[0]:[48]:[5001.0008.0007]:[0]:[0.0.0.0]/216
10.255.1.20 100 0 i
*>i 10.255.1.20 100 0 i
Sabanjure, sampeyan bisa ndeleng informasi rinci babagan Update, ing ngendi sampeyan nampa informasi babagan MAC Host. Ing ngisor iki ora kabeh output printah.
Leaf21# sh bgp l2vpn evpn 5001.0007.0007
BGP routing table information for VRF default, address family L2VPN EVPN
Route Distinguisher: 10.255.1.11:32777 ! ΠΎΡΠΏΡΠ°Π²ΠΈΠ» Update Ρ MAC Host. ΠΠ΅ Π²ΠΈΡΡΡΠ°Π»ΡΠ½ΡΠΉ Π°Π΄ΡΠ΅Ρ VPC, Π° Π°Π΄ΡΠ΅Ρ Leaf
BGP routing table entry for [2]:[0]:[0]:[48]:[5001.0007.0007]:[0]:[0.0.0.0]/216,
version 1507
Paths: (2 available, best #2)
Flags: (0x000202) (high32 00000000) on xmit-list, is not in l2rib/evpn, is not i
n HW
Path type: internal, path is valid, not best reason: Neighbor Address, no labe
led nexthop
AS-Path: NONE, path sourced internal to AS
10.255.1.10 (metric 81) from 10.255.1.102 (10.255.1.102) ! Ρ ΠΊΠ΅ΠΌ ΠΈΠΌΠ΅Π½Π½ΠΎ ΡΡΡΠΎΠΈΠΌ VxLAN ΡΠΎΠ½Π½Π΅Π»Ρ
Origin IGP, MED not set, localpref 100, weight 0
Received label 10000 ! ΠΠΎΠΌΠ΅Ρ VNI, ΠΊΠΎΡΠΎΡΡΠΉ Π°ΡΡΠΎΡΠΈΠΈΡΠΎΠ²Π°Π½ Ρ VLAN, Π² ΠΊΠΎΡΠΎΡΠΎΠΌ Π½Π°Ρ
ΠΎΠ΄ΠΈΡΡΡ Host
Extcommunity: RT:65001:10000 SOO:10.255.1.10:0 ENCAP:8 ! Π’ΡΡ Π²ΠΈΠ΄Π½ΠΎ, ΡΡΠΎ RT ΡΡΠΎΡΠΌΠΈΡΠΎΠ²Π°Π»ΡΡ Π°Π²ΡΠΎΠΌΠ°ΡΠΈΡΠ΅ΡΠΊΠΈ Π½Π° ΠΎΡΠ½ΠΎΠ²Π΅ Π½ΠΎΠΌΠ΅ΡΠΎΠ² AS ΠΈ VNI
Originator: 10.255.1.11 Cluster list: 10.255.1.102
<........>
Ayo ndeleng kaya apa pigura nalika dilewati ing pabrik:
Suppress-ARP
Apik, saiki kita duwe komunikasi L2 antarane host lan kita bisa rampung ing kana. Nanging, ora kabeh supaya prasaja. Anggere kita duwe sawetara host ora bakal ana masalah. Nanging ayo bayangake kahanan sing ana atusan lan ewonan sarwa dumadi. Masalah apa sing bisa kita adhepi?
Masalah iki yaiku lalu lintas BUM (Broadcast, Unknown Unicast, Multicast). Ing artikel iki, kita bakal nimbang opsi kanggo ngatasi lalu lintas siaran.
Generator Broadcast utama ing jaringan Ethernet yaiku host dhewe liwat protokol ARP.
Nexus ngetrapake mekanisme ing ngisor iki kanggo nglawan panjaluk ARP - suppress-arp.
Fitur iki dianggo kaya ing ngisor iki:
- Host-1 ngirim panjalukan APR menyang alamat Broadcast jaringan.
- Panjaluk kasebut tekan switch Leaf lan tinimbang ngirim panjaluk iki menyang kain menyang Host-2, Leaf nanggapi dhewe lan nuduhake IP lan MAC sing dibutuhake.
Mangkono, panyuwunan Broadcast ora menyang pabrik. Nanging kepiye carane iki bisa ditindakake yen Leaf mung ngerti alamat MAC?
Kabeh iku cukup prasaja, EVPN route-type 2, saliyane alamat MAC, bisa ngirim kombinasi MAC / IP. Kanggo nindakake iki, sampeyan kudu ngatur alamat IP ing VLAN ing Leaf. Pitakonan muncul, IP apa sing kudu diset? Ing nexus, sampeyan bisa nggawe alamat sing disebarake (padha) ing kabeh switch:
feature interface-vlan
fabric forwarding anycast-gateway-mac 0001.0001.0001 ! Π·Π°Π΄Π°Π΅ΠΌ virtual mac Π΄Π»Ρ ΡΠΎΠ·Π΄Π°Π½ΠΈΡ ΡΠ°ΡΠΏΡΠ΅Π΄Π΅Π»Π΅Π½Π½ΠΎΠ³ΠΎ ΡΠ»ΡΠ·Π° ΠΌΠ΅ΠΆΠ΄Ρ Π²ΡΠ΅ΠΌΠΈ ΠΊΠΎΠΌΠΌΡΡΠ°ΡΠΎΡΠ°ΠΌΠΈ
interface Vlan10
no shutdown
ip address 192.168.10.254/24 ! Π½Π° Π²ΡΠ΅Ρ
Leaf Π·Π°Π΄Π°Π΅ΠΌ ΠΎΠ΄ΠΈΠ½Π°ΠΊΠΎΠ²ΡΠΉ IP
fabric forwarding mode anycast-gateway ! Π³ΠΎΠ²ΠΎΡΠΈΠΌ ΠΈΡΠΏΠΎΠ»ΡΠ·ΠΎΠ²Π°ΡΡ Virtual mac
Dadi, saka sudut pandang host, jaringan bakal katon kaya iki:
Ayo mriksa BGP l2route evpn
Leaf11# sh bgp l2vpn evpn
<......>
Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 10.255.1.11:32777 (L2VNI 10000)
*>l[2]:[0]:[0]:[48]:[5001.0007.0007]:[0]:[0.0.0.0]/216
10.255.1.21 100 32768 i
*>i[2]:[0]:[0]:[48]:[5001.0008.0007]:[0]:[0.0.0.0]/216
10.255.1.10 100 0 i
* i 10.255.1.10 100 0 i
* i[2]:[0]:[0]:[48]:[5001.0008.0007]:[32]:[192.168.10.20]/248
10.255.1.10 100 0 i
*>i 10.255.1.10 100 0 i
<......>
Route Distinguisher: 10.255.1.21:32777
* i[2]:[0]:[0]:[48]:[5001.0008.0007]:[0]:[0.0.0.0]/216
10.255.1.20 100 0 i
*>i 10.255.1.20 100 0 i
* i[2]:[0]:[0]:[48]:[5001.0008.0007]:[32]:[192.168.10.20]/248
*>i 10.255.1.20 100 0 i
<......>
Saka output printah sampeyan bisa ndeleng manawa ing EVPN route-type 2, saliyane MAC, kita saiki uga ndeleng alamat IP host.
Ayo bali menyang setelan suppress-arp. Setelan iki diaktifake kanggo saben VNI kanthi kapisah:
interface nve1
member vni 10000
suppress-arp
Banjur sawetara kerumitan muncul:
- Supaya fitur iki bisa digunakake, spasi ing memori TCAM dibutuhake. Iki conto setelan kanggo suppress-arp:
hardware access-list tcam region arp-ether 256
Setelan iki mbutuhake sudhut pindho. Yaiku, yen sampeyan nyetel 256, sampeyan kudu mbebasake 512 ing TCAM. Nyetel TCAM ngluwihi ruang lingkup artikel iki, amarga nyetel TCAM mung gumantung ing tugas sing ditugasake kanggo sampeyan lan bisa uga beda-beda saka siji jaringan menyang jaringan liyane.
- Implementasi suppress-arp kudu ditindakake ing kabeh switch Leaf. Nanging, kerumitan bisa muncul nalika ngonfigurasi pasangan Leaf sing manggon ing domain VPC. Yen TCAM diganti, konsistensi antarane pasangan bakal rusak lan siji simpul bisa dijupuk metu saka operasi. Kajaba iku, urip maneh piranti bisa uga dibutuhake kanggo ngetrapake setelan pangowahan TCAM.
AkibatΓ©, sampeyan kudu nimbang kanthi teliti apa, ing kahanan sampeyan, iku worth ngleksanakake setelan iki menyang pabrik mlaku.
Iki rampung bagean pisanan saka seri. Ing sisih sabanjure kita bakal katon ing nuntun liwat kain VxLAN karo misahake jaringan menyang VRFs beda.
Lan saiki aku ngajak kabeh wong
Source: www.habr.com