{"id":73232,"date":"2020-03-08T08:42:18","date_gmt":"2020-03-08T05:42:18","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/vxlan-v-nsx-v-trablshutim-underlay"},"modified":"2020-03-08T08:42:18","modified_gmt":"2020-03-08T05:42:18","slug":"vxlan-v-nsx-v-trablshutim-underlay","status":"publish","type":"post","link":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/vxlan-v-nsx-v-trablshutim-underlay","title":{"rendered":"VXLAN NSX-V \u2014 nov\u0113r\u0161am underlay probl\u0113mas.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Sveiki, vispirms nedaudz lirikas. Da\u017ereiz es skaudu kol\u0113\u0123iem, kuri str\u0101d\u0101 att\u0101lin\u0101ti - jo tas ir lieliski, ka var str\u0101d\u0101t no jebkuras pasaules vietas, kas savienota ar internetu, br\u012bvdienas jebkur\u0101 laik\u0101, atbild\u012bba par projektiem un termi\u0146iem, nevis atrasties biroj\u0101 no 8 l\u012bdz 17. Mana poz\u012bcija un darba pien\u0101kumi praktiski izsl\u0113dz iesp\u0113ju ilgi neb\u016bt datu centr\u0101. Tom\u0113r - periodiski notiek interesanti gad\u012bjumi, l\u012bdz\u012bgi zem\u0101k aprakst\u012btajam - un es saprotu, ka ir maz poz\u012bciju, kur ir tik liels pla\u0161ums rado\u0161\u0101 iek\u0161\u0113j\u0101 troubleshooter izteiksm\u0113.
\n<\/a><\/noindex>
\nNeliels disklejms \u2014 raksta br\u012bd\u012b gad\u012bjums v\u0113l nav piln\u012bb\u0101 atrisin\u0101ts, bet \u0146emot v\u0113r\u0101 pieg\u0101d\u0101t\u0101ju atbildes \u0101trumu, piln\u012bga risin\u0101juma ieg\u016b\u0161ana var aiz\u0146emt v\u0113l m\u0113ne\u0161us, bet es v\u0113los dal\u012bties sav\u0101s atzi\u0146\u0101s jau tagad. Ceru, cien\u012bjamie las\u012bt\u0101ji, j\u016bs piedosiet man \u0161o steig\u0161anu. Bet pietiek atv\u0113rta \u016bdens \u2014 k\u0101 tur ir ar gad\u012bjumu? <\/p>\n

S\u0101kum\u0101 ievads: ir uz\u0146\u0113mums (kur es str\u0101d\u0101ju k\u0101 t\u012bkla in\u017eenieris), kas host\u0113 klientu risin\u0101jumus priv\u0101taj\u0101 VMWare m\u0101ko\u0146\u0101. Liel\u0101k\u0101 da\u013ca jauno risin\u0101jumu piesl\u0113dzas VXLAN segmentiem, kurus p\u0101rvalda NSX-V \u2014 nenov\u0113rt\u0113\u0161u, cik daudz laika man \u0161is risin\u0101jums ir devis, \u012bsi sakot \u2014 daudz. Pat izdev\u0101s apm\u0101c\u012bt kol\u0113\u0123us NSX ESG konfigur\u0113\u0161an\u0101, un da\u017ei mazie klientu risin\u0101jumi tiek izv\u0113rsti bez manas iejauk\u0161an\u0101s. Svar\u012bgs piez\u012bm\u0113 \u2014 kontrol\u0113jo\u0161\u0101 sist\u0113ma mums ir ar unicast replik\u0101ciju. Hiperizv\u0113l\u0113t\u0101ji ir piesl\u0113gti lieki ar div\u0101m saskarn\u0113m pie da\u017e\u0101diem fiziskiem Juniper QFX5100 sl\u0113d\u017eiem (salikti Virtual Chassis) un route based on originating virtual port timinga politiku \u2014 tas ir, lai sniegtu piln\u012bgu ainu.<\/p>\n

Klientu risin\u0101jumi ir \u013coti da\u017e\u0101di: no Windows IIS, kur visi komponents web-servera ir uz viena datora, l\u012bdz diezgan lieliem \u2014 piem\u0113ram, load-balanced Apache web frontiem + LB MariaDB Galera + koplieto\u0161anas serveriem, kas sinhroniz\u0113ti ar GlusterFS. Praktiski katru serveri ir j\u0101monitor\u0113 atsevi\u0161\u0137i, un ne visiem komponentiem ir publiskie adreses \u2014 ja j\u016bs esat sask\u0101ru\u0161ies ar \u0161o uzdevumu un jums ir elegant\u0101ks risin\u0101jums, b\u016b\u0161u priec\u012bgs par padomu.
\nMans uzraudz\u012bbas risin\u0101jums sast\u0101v no ugunsm\u016bra (Fortigate) 'pievienojuma' katrai iek\u0161\u0113jai klienta t\u012bklam (+SNAT un, protams, stingri ierobe\u017eojumi attiec\u012bb\u0101 uz at\u013cauto trafiku) un iek\u0161\u0113jo adresu uzraudz\u012bbas \u2014 t\u0101d\u0113j\u0101di tiek pan\u0101kta zin\u0101ma vienveid\u012bba un uzraudz\u012bbas vienk\u0101r\u0161o\u0161ana. Pats uzraudz\u012bbas process notiek no PRTG serveru klastera. Uzraudz\u012bbas sh\u0113ma ir aptuveni \u0161\u0101da:<\/p>\n

\"VXLAN
\n
\nKam\u0113r m\u0113s str\u0101d\u0101j\u0101m tikai ar VLAN, viss bija piln\u012bgi parasts un paredzami darboj\u0101s, k\u0101 pulkstenis. P\u0113c NSX-V un VXLAN ievie\u0161anas sask\u0101r\u0101mies ar jaut\u0101jumu \u2014 vai var turpin\u0101t uzraudz\u012bbu pa vecam? Uz \u0161\u012b jaut\u0101juma br\u012bdi vis\u0101tr\u0101k\u0101 risin\u0101juma bija NSX ESG izsnieg\u0161ana un VXLAN trunk saskarnes piesl\u0113g\u0161ana VTEP t\u012bklam. \u0100tri ar '''' \u2014 jo izmantot GUI klientu t\u012bklu, SNAT un ugunsm\u016bra noteikumu konfigur\u0113\u0161anai varb\u016bt vienk\u0101r\u0161o p\u0101rvald\u012bbu vien\u0101 vSphere saskarn\u0113, bet manupr\u0101t, tas ir diezgan smagn\u0113js un ierobe\u017eo r\u012bku kl\u0101stu, kas pieejams probl\u0113mu risin\u0101\u0161anai. Tie, kas izmantoja NSX ESG k\u0101 '\u012bst\u0101' ugunsm\u016bra aizst\u0101j\u0113ju, dom\u0101ju, piekrit\u012bs. Lai gan, j\u0101dom\u0101, \u0161\u0101ds risin\u0101jums b\u016btu stabil\u0101ks \u2014 galu gal\u0101 viss norisin\u0101s viena pieg\u0101d\u0101t\u0101ja ietvaros.<\/p>\n

V\u0113l viens risin\u0101jums ir izmantot NSX DLR brid\u017ea re\u017e\u012bm\u0101 starp VLAN un VXLAN. \u0160eit viss ir saprotams - vienk\u0101r\u0161i tiek zaud\u0113ta VXLAN izmanto\u0161anas j\u0113ga, jo \u0161aj\u0101 gad\u012bjum\u0101 tom\u0113r j\u0101velk VLAN uz uzraudz\u012bbas instal\u0101ciju. Starp citu, str\u0101d\u0101jot pie \u0161\u012b risin\u0101juma, es sask\u0101ros ar probl\u0113mu, kad DLR tilts nes\u016bt\u012bja paketes virtu\u0101lajai ma\u0161\u012bnai, kura atrad\u0101s uz viena hosta. Zinu, zinu - gr\u0101mat\u0101s un vadl\u012bnij\u0101s par NSX-V tie\u0161i ir teikts, ka NSX Edge ir j\u0101izveido atsevi\u0161\u0137s klasteris, bet tas ir gr\u0101mat\u0101s... Tom\u0113r p\u0113c p\u0101ris m\u0113ne\u0161iem ar atbalsta dienestu m\u0113s probl\u0113mu neatrisin\u0101j\u0101m. Princip\u0101 es sapratu darb\u012bbas lo\u0123iku - hipervizora kodola modulis, kas atbild par VXLAN iepako\u0161anu, netika aktiviz\u0113ts, ja DLR un nov\u0113rotais serveris atrad\u0101s uz viena hosta, jo satiksme nepameta hostu un lo\u0123iski b\u016btu j\u0101piesl\u0113dzas VXLAN segmentam - iepako\u0161ana nav nepiecie\u0161ama. Ar atbalsta dienestu m\u0113s apst\u0101j\u0101mies pie virtu\u0101l\u0101 interfeisa vdrPort, kur\u0161 lo\u0123iski apvieno uplinkus un veic brid\u017eo\u0161anu\/iepako\u0161anu - tur tika paman\u012bts neatbilst\u012bba ien\u0101ko\u0161aj\u0101 satiksm\u0113, kuru es \u0146\u0113mu uz apstr\u0101di \u0161aj\u0101 gad\u012bjum\u0101. Bet, k\u0101 tika teikts, l\u012bdz galam es \u0161o gad\u012bjumu nenovedu, jo tiku p\u0101rcelts uz citu projektu, un ar\u012b fili\u0101le s\u0101kotn\u0113ji bija bezizejas un \u012bpa\u0161i nebija v\u0113lmes to att\u012bst\u012bt. Ja nemaldos, probl\u0113ma nov\u0113rota NSX versij\u0101s 6.1.4 un 6.2. <\/p>\n

Un \u0161eit - bingo! Fortinet pazi\u0146o par nat\u012bvu VXLAN atbalstu<\/a><\/noindex>. Un ne tikai point-to-point vai VXLAN-over-IPSec, ne programmat\u016bras tiltu VLAN-VXLAN - tas viss s\u0101ka tikt ieviests v\u0113l no versijas 5.4 (un pied\u0101v\u0101ts pie citiem pieg\u0101d\u0101t\u0101jiem<\/a><\/noindex>), bet patieso atbalstu unicast control plane. Ievie\u0161ot risin\u0101jumu, es sastapos ar v\u0113l vienu probl\u0113mu - p\u0101rbaud\u012btie serveri periodiski <\/p>\n

Veiksm\u012bgi test\u0113jot trafiku, tika nolemts ieviest \u0161o risin\u0101jumu. Un ra\u017eo\u0161an\u0101 izr\u0101d\u012bj\u0101s, ka p\u0113c dienas vai div\u0101m pak\u0101peniski atsl\u0113dzas viss, kas monitor\u0113ts caur VXLAN. Interfeisa deaktiviz\u0101cija\/aktiviz\u0101cija bija noder\u012bga, ta\u010du tikai uz br\u012bdi. Atceroties ra\u017eot\u0101ja atbalsta l\u0113n\u012bgumu, es \u0137\u0113ros pie probl\u0113mu nov\u0113r\u0161anas no savas puses \u2014 galu gal\u0101, mana uz\u0146\u0113muma, mana t\u012bkla \u2014 mana atbild\u012bba. <\/p>\n

Probl\u0113mu nov\u0113r\u0161anas gaita. Ja j\u016bs esat noguru\u0161i no burtiem un lepn\u012bbas \u2014 izlai\u017eiet un p\u0101rejiet pie p\u0113capstr\u0101des.<\/p>\n

Probl\u0113mu nov\u0113r\u0161anas gaita<\/b>Paldies, ka turpin\u0101j\u0101t las\u012bt \u2014 turpin\u0101sim!<\/p>\n

T\u0101tad, monitorings darbojas k\u0101du laiku, p\u0113c tam pats sevi atsl\u0113dz. Tas noz\u012bm\u0113, ka ugunsm\u016bri politik\u0101s, visticam\u0101k, nav probl\u0113mu. Tom\u0113r, t\u0101 k\u0101 esmu pieredz\u0113jis ar probl\u0113m\u0101m, kas saist\u012btas ar iesald\u0113t\u0101m sist\u0113mas procesu Fortigate versij\u0101s 5.6+, vispirms skat\u0101mies 'diagnose debug flow' \u2014 k\u0101 sagaid\u0101ms, trafiks tiek at\u013cauts un izn\u0101k caur interfeisu, un sagaid\u0101ms, ka nekas neatn\u0101k atpaka\u013c. T\u0101tad, turpin\u0101m izp\u0113ti t\u0101l\u0101k pa steku. Diem\u017e\u0113l, b\u016bs j\u0101sl\u0113pj pat RFC1918 adreses, bet es ceru sniegt procesam pietiekamu aprakstu izpratnei. Serveris iek\u0161\u0101 VXLAN ir ar adresi \u0445.\u0445.\u0445.15, Fortigate interfeiss \u0445.\u0445.\u0445.254, visas p\u0101r\u0113j\u0101s adreses pieder VTEP t\u012bklam.<\/p>\n

Lai veiksm\u012bgi p\u0101rs\u016bt\u012btu VXLAN iesai\u0146otos paketus, ir nepiecie\u0161ama pareiza inform\u0101cija vair\u0101k\u0101s tabul\u0101s. Overlay gad\u012bjum\u0101 tas ir ARP un OVSDB, bet underlay gad\u012bjum\u0101 tas ir ARP un CAM. Fortigate gad\u012bjum\u0101 VXLAN FDB ir OVSDB. S\u0101ksim tur:<\/p>\n

 fortigate (root) #diag sys vxlan fdb list vxlan-LS\nmac=00:50:56:8f:3f:5a state=0x0002 flags=0x00 remote_ip=u.u.u.47 port=4789 vni=5008 ifindex=7\n<\/code><\/pre>\n
\n\u0160eit viss ir pietiekami vienk\u0101r\u0161i \u2014 virtu\u0101la datora MAC adrese j\u0101atrodas uz VTEP ar adresi u.u.u.47. P\u0101rbaudot ESXI klastera saturu un iestat\u012bjumus, es redzu, ka virtu\u0101la datora MAC adrese ir pareiza, ar\u012b VTEP adrese. P\u0101rbaudu CAM\/ARP tabulu fortigate \u2014 atkal viss sakr\u012bt ar ESXI hosta iestat\u012bjumiem:<\/p>\n
fortigate (root) #get sys arp | grep u.u.u.47\nu.u.u.47 0 00:50:56:65:f6:2c dmz\n<\/code><\/pre>\n
\nTabulas ir pareizas un trafiks aiziet - varb\u016bt probl\u0113ma nav fortigate? Es apzin\u0101ti izlaidu trafika sl\u0113g\u0161anas anal\u012bzi uz Juniper - lo\u0123iski tas ir j\u0101dara n\u0101kamaj\u0101 so\u013c\u012b troubleshooter, bet t\u012bkls man ir vienk\u0101r\u0161s - tikai viens VLAN VTEP un visi komponenti ir piesl\u0113gti tie\u0161i. Plus atceros gad\u012bjumu ar DLR-tiltu, VDR un paz\u016bdo\u0161o trafiku - eju sniff uz ESXI host, pa ce\u013cam izveidoju gad\u012bjumu jau VMware. Zem\u0101k MAC \"97:6e\" pieder fortikam, vmnic1 - tas ir interfeiss, kuram ir VTEP ar adresi u.u.u.47 sniff\u0113jam abos virzienos \"-dir 2\"<\/p>\n
pktcap-uw --uplink vmnic1 --vni 5008  --mac 90:6c:ac:a9:97:6e --dir 2 -o \/tmp\/monitor.pcap\n<\/code><\/pre>\n
\n\"VXLAN
\n
\nProgress \u2014 sniff\u0101 redzu ARP piepras\u012bjumu un n\u0101ko\u0161o atbildi. Izv\u0113los tikai ARP atbildi, un tur viss ir pareizi. Neesmu piemin\u0113jis, bet visu \u0161o laiku uzraudz\u012bbas serveris ping\u0113 adresi h.h.h.15 \u2014 kur palika ICMP trafiks? Atceros, ka man ir divi uplin\u0137i. \u0160eit var\u0113tu diskut\u0113t un teikt, ka virtu\u0101lais avota ports ir viens un tas pats (m\u0101jas t\u012bkla politika), t\u0101tad vienai un tai pa\u0161ai vNIC j\u0101izv\u0113las viens un tas pats uplink, bet, ja jau esmu host\u0101, p\u0101rbaud\u012bt citu uplink nav probl\u0113ma:<\/p>\n
pktcap-uw --uplink vmnic4 --vni 5008  --mac 90:6c:ac:a9:97:6e --dir 2 -o \/tmp\/monitor.pcap\n<\/code><\/pre>\n
\n\"VXLAN
\n
\nSa\u0146em piepras\u012bjumus no Fortigate, bet atbildes nav. T\u0101tad probl\u0113ma nav Fortigate. Nu, viss \u2014 es dom\u0101ju \u2014 atkal t\u0101 pati probl\u0113ma ar pazudu\u0161o satiksmi uz VDR, atkal p\u0101ris m\u0113ne\u0161i j\u0101virza gad\u012bjums pareizaj\u0101 virzien\u0101. P\u0101ris dienu laik\u0101 atdziestot un nev\u0113loties samierin\u0101ties ar kav\u0113\u0161anos, nol\u0113mu sav\u0101kt v\u0113l sniffus atbalstam, lai pa\u0101trin\u0101tu procesu. Un te \u201enejau\u0161i\u201d mans skatiens uzkr\u012bto\u0161i kr\u012bt uz Ethernet kapsul\u0101ciju underlay. \u0136\u0113ni\u0146\u0161 nav \u012bsts, un VTEP MAC adrese nesakr\u012bt ar t\u0101 IP. Noll\u0113ju, sniffoju, izp\u0113tu \u2014 pareizi, kas nav pareizi. Priek\u0161\u0101 blakus ierakstu ARP tabulu, lai b\u016btu \u0113rt\u0101k sal\u012bdzin\u0101t. Piev\u0113rsiet uzman\u012bbu pirmajai Ethernet kapsul\u0101cijai att\u0113l\u0101 aug\u0161\u0101:<\/p>\n
fortigate (root) #get sys arp | grep \u0443.\u0443.\u0443.47\n\u0443.\u0443.\u0443.47 0 00:50:56:65:f6:2c dmz\nfortigate (root) #get sys arp | grep \u0443.\u0443.\u0443.42\n\u0443.\u0443.\u0443.42 0 00:50:56:6a:78:86 dmz\n<\/code><\/pre>\n
\nT\u0101tad, ko m\u0113s beigu beig\u0101s ieg\u016bstam \u2014 p\u0113c virtu\u0101l\u0101s ma\u0161\u012bnas migr\u0101cijas, Fortigate m\u0113\u0123ina nos\u016bt\u012bt satiksmi uz VTEP no (pareiz\u0101s) VXLAN FDB, bet izmanto nepareizu DST MAC un satiksme, k\u0101 gaid\u012bts, tiek noraid\u012bta no hipervizora sa\u0146emo\u0161\u0101 saskarnes. Turkl\u0101t vien\u0101 no \u010detriem gad\u012bjumiem \u0161is MAC pieder\u0113ja s\u0101kotn\u0113jam hipervizoram, no kura s\u0101ka migr\u0101ciju.<\/p>\n
Vakar sa\u0146\u0113mu v\u0113stuli no Fortinet tehnisk\u0101 atbalsta \u2014 man\u0101 gad\u012bjum\u0101 tika atkl\u0101ts k\u013c\u016bda 615586. Tie\u0161\u0101m nezinu, vai priec\u0101ties vai skumt: no vienas puses \u2014 probl\u0113ma nav iestat\u012bjumos, no otras \u2014 labojums n\u0101ks tikai ar programmat\u016bras atjaunin\u0101jumu, vislab\u0101kaj\u0101 gad\u012bjum\u0101 n\u0101kamaj\u0101. Pa\u0161apzi\u0146u ar\u012b uztur v\u0113l viena k\u013c\u016bda, kuru es atkl\u0101ju pag\u0101ju\u0161\u0101 m\u0113nes\u012b, tom\u0113r taj\u0101 reiz\u0113 HTML5 GUI vSphere. Tie\u0161\u0101m, tie\u0161i viet\u0113jais QA noda\u013ca pieg\u0101d\u0101t\u0101jiem...<\/p>\n
Risks pie\u0146emt sekojo\u0161o:<\/p>\n
1 \u2014 multicast kontrolsist\u0113ma, visticam\u0101k, neb\u016bs pak\u013cauta aprakst\u012btajai probl\u0113mai \u2014 jo VTEP MAC adreses tiek ieg\u016btas no grupas IP adreses, uz kuru pievienojas saskarne. <\/p>\n
2 \u2014 visticam\u0101k, probl\u0113ma ir Fortigate s\u0113rijas samazin\u0101jum\u0101 uz T\u012bkla Procesoru (aptuveni l\u012bdz\u012bgs CEF) \u2014 ja katrs pakets tiek nos\u016bt\u012bts caur CPU, tiks izmantotas tabulas, kuras satur pareizu \u2014 vismaz vizu\u0101li \u2014 inform\u0101ciju. \u0160\u012bs pie\u0146\u0113muma lab\u0101 run\u0101 tas, ka pal\u012bdz aizv\u0113rt\/atv\u0113rt saskarni vai gaid\u012bt zin\u0101mu laiku \u2014 vair\u0101k nek\u0101 5 min\u016btes. <\/p>\n
3 \u2014 izmai\u0146as komandas politik\u0101, piem\u0113ram, uz explicit failover, vai LAG ievie\u0161ana probl\u0113mu neatrisin\u0101s, jo tika nov\u0113rota \u201eiestr\u0113g\u0161ana\u201d MAC no s\u0101kotn\u0113j\u0101 hipervizora inkapsul\u0113tajos pakotn\u0113s.<\/p>\n
\u0160\u012b kontekst\u0101 varu dal\u012bties, ka nesen atkl\u0101ju, ka blog\u0101<\/a><\/noindex>, kur vien\u0101 no rakstiem tika apgalvots, ka stetfull ugunsm\u016bri un ke\u0161ot\u0101ji datu p\u0101rs\u016bt\u012b\u0161anas veidi ir tikai pagaidu risin\u0101jumi. Nu, es neesmu tik pieredz\u0113jis IT jom\u0101, lai apgalvotu ko t\u0101du, turkl\u0101t ne visiem emu\u0101ra rakstu apgalvojumiem es piekr\u012btu uzreiz. Tom\u0113r kaut kas man liek dom\u0101t, ka Ivanam ir da\u013ca taisn\u012bbas.<\/p>\n
Paldies par uzman\u012bbu! B\u016b\u0161u priec\u012bgs atbild\u0113t uz jaut\u0101jumiem un uzklaus\u012bt konstrukt\u012bvu kritiku.
\n
Avots: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\u041f\u0440\u0438\u0432\u0435\u0442\u0441\u0442\u0432\u0443\u044e, \u0438 \u0441\u043f\u0435\u0440\u0432\u0430 \u043d\u0435\u043c\u043d\u043e\u0433\u043e \u043b\u0438\u0440\u0438\u043a\u0438. \u042f \u0438\u043d\u043e\u0433\u0434\u0430 \u0437\u0430\u0432\u0438\u0434\u0443\u044e \u043a\u043e\u043b\u043b\u0435\u0433\u0430\u043c, \u0440\u0430\u0431\u043e\u0442\u0430\u044e\u0449\u0438\u043c \u0443\u0434\u0430\u043b\u0451\u043d\u043d\u043e \u2014 \u0432\u0435\u0434\u044c \u044d\u0442\u043e \u043f\u0440\u0435\u043a\u0440\u0430\u0441\u043d\u043e \u0438\u043c\u0435\u0442\u044c \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c \u0440\u0430\u0431\u043e\u0442\u0430\u0442\u044c \u0438\u0437 \u043b\u044e\u0431\u043e\u0433\u043e \u043a\u043e\u043d\u0446\u0430 \u043f\u043e\u0434\u043a\u043b\u044e\u0447\u0451\u043d\u043d\u043e\u0433\u043e \u043a Internet \u043c\u0438\u0440\u0430, \u043a\u0430\u043d\u0438\u043a\u0443\u043b\u044b \u0432 \u043b\u044e\u0431\u043e\u0435 \u0432\u0440\u0435\u043c\u044f, \u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0435\u043d\u043d\u043e\u0441\u0442\u044c \u0437\u0430 \u043f\u0440\u043e\u0435\u043a\u0442\u044b \u0438 \u0434\u0435\u0434\u043b\u0430\u0439\u043d\u044b, \u0430 \u043d\u0435 \u043d\u0430\u0445\u043e\u0436\u0434\u0435\u043d\u0438\u0435 \u0432 \u043e\u0444\u0438\u0441\u0435 \u0441 8 \u0434\u043e 17. \u041c\u043e\u044f \u043f\u043e\u0437\u0438\u0446\u0438\u044f \u0438 \u0440\u0430\u0431\u043e\u0447\u0438\u0435 \u043e\u0431\u044f\u0437\u0430\u043d\u043d\u043e\u0441\u0442\u0438 \u043f\u0440\u0430\u043a\u0442\u0438\u0447\u0435\u0441\u043a\u0438 \u0438\u0441\u043a\u043b\u044e\u0447\u0430\u044e\u0442 \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c \u0434\u043e\u043b\u0433\u043e\u0433\u043e \u043e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u044f \u0432 \u0434\u0430\u0442\u0430\u0446\u0435\u043d\u0442\u0440\u0435. […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":73233,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-73232","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47VXLAN NSX-V \u2014 risin\u0101m underlay probl\u0113mas | ProHoster","description":"Sveicin\u0101ti, un vispirms nedaudz lirikas.","canonical_url":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/vxlan-v-nsx-v-trablshutim-underlay","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"lv_LV","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47VXLAN \u0432 NSX-V \u2014 \u0442\u0440\u0430\u0431\u043b\u0448\u0443\u0442\u0438\u043c underlay | ProHoster","og:description":"\u041f\u0440\u0438\u0432\u0435\u0442\u0441\u0442\u0432\u0443\u044e, \u0438 \u0441\u043f\u0435\u0440\u0432\u0430 \u043d\u0435\u043c\u043d\u043e\u0433\u043e \u043b\u0438\u0440\u0438\u043a\u0438.","og:url":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/vxlan-v-nsx-v-trablshutim-underlay","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-03-08T05:42:18+00:00","article:modified_time":"2020-03-08T05:42:18+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"73232","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 18:36:23","updated":"2022-09-27 15:26:08","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts\/73232","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/comments?post=73232"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts\/73232\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media\/73233"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media?parent=73232"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/categories?post=73232"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/tags?post=73232"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}