{"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\/sq\/blog\/administrirovanie\/vxlan-v-nsx-v-trablshutim-underlay","title":{"rendered":"VXLAN n\u00eb NSX-V \u2014 zgjidhim problemet e underlay","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

P\u00ebrsh\u00ebndetje, dhe fillimisht pak lirike. Ndonj\u00ebher\u00eb ndjej xhelozi p\u00ebr koleg\u00ebt q\u00eb punojn\u00eb n\u00eb distanc\u00eb \u2014 sepse \u00ebsht\u00eb e mrekullueshme t\u00eb kesh mund\u00ebsin\u00eb t\u00eb punosh nga \u00e7far\u00ebdo cepi t\u00eb bot\u00ebs me Internet, pushime n\u00eb \u00e7do koh\u00eb, p\u00ebrgjegj\u00ebsi p\u00ebr projektet dhe afatet, e jo t\u00eb jesh n\u00eb zyr\u00eb nga ora 8 deri n\u00eb 17. Pozita ime dhe detyrat e pun\u00ebs praktikisht p\u00ebrjashtojn\u00eb mund\u00ebsin\u00eb e nj\u00eb mungese t\u00eb gjat\u00eb n\u00eb qendr\u00ebn e t\u00eb dh\u00ebnave. Megjithat\u00eb \u2014 ndodhin her\u00eb pas here raste interesante, si ai i p\u00ebrshkruar m\u00eb posht\u00eb \u2014 dhe kuptoj se ekzistojn\u00eb shum\u00eb pak pozita ku ka kaq shum\u00eb hap\u00ebsir\u00eb p\u00ebr shprehjen krijuese t\u00eb nj\u00eb troubleshooter-i t\u00eb brendsh\u00ebm.
\n<\/a><\/noindex>
\nNj\u00eb disklamer i vog\u00ebl - n\u00eb momentin kur po shkruhet ky artikull, rasti nuk \u00ebsht\u00eb zgjidhur plot\u00ebsisht, por duke marr\u00eb parasysh shpejt\u00ebsin\u00eb e p\u00ebrgjigjeve nga distributor\u00ebt, nj\u00eb zgjidhje e plot\u00eb mund t\u00eb k\u00ebrkoj\u00eb edhe muaj, dhe doja t\u00eb ndaja gjetjet e mia tashm\u00eb. Shpresoj, lexues t\u00eb respektuar, q\u00eb do t\u00eb m\u00eb falni p\u00ebr k\u00ebt\u00eb ngutje. Por mjaft me uj\u00eb - \u00e7far\u00eb ndodh me rastin? <\/p>\n

Fillimisht nj\u00eb hyrje: ka nj\u00eb kompani (ku punoj si inxhinier rrjeti), e cila hoston zgjidhje t\u00eb klient\u00ebve n\u00eb nj\u00eb cloud privat VMWare. Shumica e zgjidhjeve t\u00eb reja lidhen me VXLAN-segmente, t\u00eb cilat menaxhohen nga NSX-V - nuk do t\u00eb vler\u00ebsoj se sa koh\u00eb m\u00eb ka dh\u00ebn\u00eb kjo zgjidhje, p\u00ebr ta th\u00ebn\u00eb shkurt - shum\u00eb. Kam arritur t\u00eb m\u00ebsoj edhe koleg\u00ebt p\u00ebr konfigurimin e NSX ESG dhe zgjidhjet e vogla t\u00eb klient\u00ebve nd\u00ebrtohen pa pjes\u00ebmarrjen time. Nj\u00eb v\u00ebrejtje e r\u00ebnd\u00ebsishme - plani i kontrollit \u00ebsht\u00eb me replikim unicast. Hypervizor\u00ebt jan\u00eb lidhur me dy lidhje t\u00eb tejdukshme me switch-e fizike Juniper QFX5100 (t\u00eb bashkuara n\u00eb Virtual Chassis) dhe politik\u00ebn e p\u00ebrcaktimit t\u00eb rrug\u00ebve t\u00eb bazuara n\u00eb portin virtual t\u00eb origjin\u00ebs - kjo \u00ebsht\u00eb p\u00ebr plot\u00ebsin\u00eb e pamjes.<\/p>\n

Zgjidhjet e klient\u00ebve jan\u00eb shum\u00eb t\u00eb larmishme: nga Windows IIS, ku t\u00eb gjith\u00eb komponent\u00ebt e serverit web jan\u00eb t\u00eb instaluar n\u00eb nj\u00eb makin\u00eb, deri n\u00eb zgjidhje shum\u00eb t\u00eb m\u00ebdha - p\u00ebr shembull, Apache web-frontet me load balancing + LB MariaDB n\u00eb Galera + servera skedar\u00ebsh, t\u00eb sinkronizuar me GlusterFS. Praktikisht \u00e7do server duhet t\u00eb monitorohet ndaras, dhe adresat publike nuk i ka t\u00eb gjith\u00eb komponent\u00ebt - n\u00ebse e keni p\u00ebrjetuar k\u00ebt\u00eb detyr\u00eb dhe keni nj\u00eb zgjidhje m\u00eb elegante, do t\u00eb isha i lumtur p\u00ebr k\u00ebshill\u00ebn.
\nZgjidhja ime p\u00ebr monitorimin p\u00ebrfshin \"lidhen\" firewallin (Fortigate) me \u00e7do rrjet t\u00eb brendsh\u00ebm klient\u00ebsh (+SNAT dhe, sigurisht, kufizime t\u00eb rrepta n\u00eb lidhje me llojin e trafikut t\u00eb lejuar) dhe v\u00ebzhgimin e adresave t\u00eb brendshme \u2014 n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb arrijm\u00eb nj\u00eb far\u00eb unifikimi dhe thjeshtimi t\u00eb monitorimit. Monitorimi kryhet nga nj\u00eb grumbull serverash PRTG. Skema e monitorimit duket k\u00ebshtu:<\/p>\n

\"VXLAN
\n
\nDerisa po operonim vet\u00ebm me VLAN, gjith\u00e7ka ishte mjaft normale dhe parashikueshme, si or\u00ebt. Pas shpalosjes s\u00eb NSX-V dhe VXLAN, u p\u00ebrball\u00ebm me pyetjen \u2014 a mund t\u00eb vazhdojm\u00eb monitorimin si m\u00eb par\u00eb? N\u00eb momentin e k\u00ebsaj pyetje, zgjidhja m\u00eb \"t\u00eb shpejt\u00eb\" ishte t\u00eb vendosnim NSX ESG dhe t\u00eb lidhnim nd\u00ebrfaqen VXLAN trunk n\u00eb rrjetin VTEP. E shpejt\u00eb n\u00eb kuotat \u2014 sepse p\u00ebrdorimi i GUI p\u00ebr konfigurimin e rrjeteve t\u00eb klient\u00ebve, SNAT dhe rregullave t\u00eb firewall-it mund t\u00eb unifikoj\u00eb menaxhimin n\u00eb nj\u00eb nd\u00ebrfaqe t\u00eb vetme vSphere, por sipas mendimit tim \u00ebsht\u00eb mjaft e ngjeshur dhe p\u00ebr m\u00eb tep\u00ebr kufizon grupin e mjeteve p\u00ebr troubleshooting. Ata q\u00eb e kan\u00eb p\u00ebrdorur NSX ESG si z\u00ebvend\u00ebsim p\u00ebr nj\u00eb firewall \"t\u00eb v\u00ebrtet\u00eb\", mendoj se do t\u00eb bien dakord. Megjith\u00ebse, ndoshta, nj\u00eb zgjidhje e till\u00eb do t\u00eb ishte m\u00eb stabilja \u2014 sepse gjith\u00e7ka ndodh brenda nj\u00eb ofruesi.<\/p>\n

Nj\u00eb zgjidhje tjet\u00ebr \u00ebsht\u00eb t\u00eb p\u00ebrdorni NSX DLR n\u00eb modalitetin bridge midis VLAN dhe VXLAN. K\u00ebtu mendoj se gjith\u00e7ka \u00ebsht\u00eb e qart\u00eb - thjesht humb fitimi nga p\u00ebrdorimi i VXLAN - sepse n\u00eb k\u00ebt\u00eb rast edhe duhet t\u00eb t\u00ebrheqim VLAN n\u00eb instalimin e monitorimit. P\u00ebrve\u00e7 k\u00ebsaj, gjat\u00eb p\u00ebrpunimit t\u00eb k\u00ebsaj zgjidhjeje, u p\u00ebrballa me nj\u00eb problem, kur DLR bridge nuk d\u00ebrgonte paketa n\u00eb makinat virtuale me t\u00eb cilat ndodhej n\u00eb nj\u00eb host. E di, e di - n\u00eb libra dhe n\u00eb udh\u00ebzues p\u00ebr NSX-V thuhet qart\u00eb se p\u00ebr NSX Edge duhet t\u00eb jet\u00eb caktuar nj\u00eb klas\u00ebr i ve\u00e7ant\u00eb, por k\u00ebto jan\u00eb n\u00eb libra... \u00c7far\u00ebdo qoft\u00eb, pas disa muajve me suportin nuk arrit\u00ebm t\u00eb zgjidhnim problemin. N\u00eb parim, logjika e veprimit e kuptova - moduli i b\u00ebrtham\u00ebs s\u00eb hipervizorit, p\u00ebrgjegj\u00ebs p\u00ebr inkuadrimin e VXLAN-s\u00eb, nuk aktivizohej n\u00ebse DLR dhe serveri i monitoruar ndodheshin n\u00eb nj\u00eb host, pasi trafiku nuk largohet nga hosti dhe logjikisht duhet t\u00eb lidhet me segmentin VXLAN - inkuadrimi nuk nevojitet. Ne me suportin u ndal\u00ebm n\u00eb nd\u00ebrfaqen virtuale vdrPort, e cila logjikisht bashkon uplinks dhe nj\u00ebkoh\u00ebsisht realizon bridge\/integrimin - atje u v\u00ebrejt nj\u00eb mosakordim n\u00eb trafikun e ardhsh\u00ebm, q\u00eb e mora p\u00ebr p\u00ebrpunimin n\u00eb k\u00ebt\u00eb rast. Por si\u00e7 u tha, deri n\u00eb fund nuk e \u00e7ova k\u00ebt\u00eb rast, pasi u kalova n\u00eb nj\u00eb projekt tjet\u00ebr dhe kjo deg\u00eb ishte fillimisht nj\u00eb rrug\u00eb e mbyllur dhe nuk kisha d\u00ebshir\u00eb ta zhvilloja shum\u00eb. N\u00ebse nuk gaboj, problemi v\u00ebrehej n\u00eb versionet NSX 6.1.4 dhe 6.2. <\/p>\n

Dhe k\u00ebtu - bingo! Fortinet shpall mb\u00ebshtetje natyrore p\u00ebr VXLAN<\/a><\/noindex>. Dhe jo vet\u00ebm point-to-point ose VXLAN-over-IPSec, jo bridging softuerik VLAN-VXLAN - t\u00eb gjitha k\u00ebto filluan t\u00eb implementoheshin q\u00eb me versionin 5.4 (dhe jan\u00eb paraqitur tek t\u00eb tjera prodhuesit<\/a><\/noindex>), dhe mb\u00ebshtetje t\u00eb v\u00ebrtet\u00eb p\u00ebr unicast control plane. Gjat\u00eb zbatimit t\u00eb zgjidhjes u p\u00ebrballa me nj\u00eb problem tjet\u00ebr \u2014 serverat q\u00eb kontrolloja her\u00eb pas here \"zhdukeshin\" e her\u00eb pas here shfaqeshin n\u00eb monitorim, edhe pse vet\u00eb makina virtuale ishte e gjall\u00eb. Si\u00e7 duket, arsyeja ishte se harrova t\u00eb lejoja Ping n\u00eb nd\u00ebrfaqen VXLAN. Gjat\u00eb procesit t\u00eb ribalancimit t\u00eb klaster\u00ebve, makinat virtuale u zhvendos\u00ebn, nd\u00ebrsa Ping-i p\u00ebrfundonte vMotion-in, p\u00ebr t\u00eb treguar hostin e ri ESXI, n\u00eb t\u00eb cilin ishte transferuar makina. Ishte nj\u00eb gabim nga ana ime, por ky problem p\u00ebrs\u00ebri minoi besimin n\u00eb mb\u00ebshtetje \u2014 n\u00eb k\u00ebt\u00eb rast Fortinet. Nuk po flas p\u00ebr faktin q\u00eb \u00e7do rast q\u00eb lidhet me VXLAN fillon me pyetjen \"ku e keni cil\u00ebsimin e VLAN-VXLAN n\u00eb softswitch?\" K\u00ebt\u00eb her\u00eb m\u00eb k\u00ebshilluan t\u00eb ndryshoja MTU \u2014 ky \u00ebsht\u00eb p\u00ebr Ping-un, i cili \u00ebsht\u00eb 32 byte. Pas k\u00ebsaj \"luaj me\" tcp-send-mss dhe tcp-receive-mss n\u00eb politikat \u2014 p\u00ebr VXLAN-in, q\u00eb inkapsulohet n\u00eb UDP. Uf, m\u00eb falni \u2014 \u00ebsht\u00eb mbledhur. N\u00eb p\u00ebrgjith\u00ebsi, k\u00ebt\u00eb problem e zgjidhia me forcat e mia. <\/p>\n

Pasi kalova trafikun testues me sukses, u vendos t\u00eb implementohej kjo zgjidhje. Dhe n\u00eb prodhim u zbulua se pas nj\u00eb apo dy dit\u00ebsh gradualisht t\u00eb gjitha gj\u00ebrat q\u00eb monitoroheshin p\u00ebrmes VXLAN shuheshin. \u00c7aktivizimi\/aktivizimi i nd\u00ebrfaqes ndihmonte, por vet\u00ebm p\u00ebr nj\u00eb koh\u00eb. Duke pasur parasysh ngadal\u00ebsin\u00eb e mb\u00ebshtetjes s\u00eb prodhuesit, fillova t\u00eb merrem me zgjidhjen e problemeve nga ana ime \u2014 pasi n\u00eb fund t\u00eb fundit kompania ime, rrjeti im \u2014 p\u00ebrgjegj\u00ebsia ime. <\/p>\n

N under spojlerin e procesit t\u00eb zgjidhjes s\u00eb problemeve. Kush \u00ebsht\u00eb lodhur nga shkronjat dhe mburrjet \u2014 kaloni dhe shkoni tek analiza post.<\/p>\n

Procesi i zgjidhjes s\u00eb problemeve<\/b>Faleminderit q\u00eb vazhdoni t\u00eb lexoni \u2014 le t\u00eb vazhdojm\u00eb!<\/p>\n

Pra, monitorimi funksionon p\u00ebr nj\u00eb far\u00eb kohe, pastaj shuhen vet\u00eb. Do t\u00eb thot\u00eb, ndoshta nuk ka probleme n\u00eb politikat e firewall-it. Megjithat\u00eb, pasi kam pasur probleme me procese t\u00eb sistemit q\u00eb ngrihen n\u00eb Fortigate versionet 5.6+, fillimisht shohim \u2018diagnose debug flow\u2019 \u2014 si\u00e7 pritej, trafiku lejohet dhe largohet nga nd\u00ebrfaqja dhe si\u00e7 pritej, nuk merr asnj\u00eb p\u00ebrgjigje. Pjesa tjet\u00ebr do t\u00eb k\u00ebrkojm\u00eb m\u00eb thell\u00eb n\u00eb stak. Do t\u00eb kem fatkeq\u00ebsisht p\u00ebr t\u00eb fshehur adresat, edhe n\u00ebse jan\u00eb RFC1918, por shpresoj t\u00eb siguroj procesin me nj\u00eb p\u00ebrshkrim t\u00eb mjaftuesh\u00ebm p\u00ebr ta kuptuar. Serveri brenda VXLAN ka adres\u00ebn x.x.x.15, nd\u00ebrfaqja e fortigate x.x.x.254, t\u00eb gjitha adresat e tjera i p\u00ebrkasin rrjetit VTEP.<\/p>\n

P\u00ebr nj\u00eb transmetim t\u00eb suksessh\u00ebm t\u00eb pakove t\u00eb inkapsuluara VXLAN, \u00ebsht\u00eb e nevojshme q\u00eb informatat t\u00eb jen\u00eb t\u00eb sakta n\u00eb disa tabela. P\u00ebr overlay, k\u00ebto jan\u00eb ARP dhe OVSDB, nd\u00ebrsa p\u00ebr underlay, jan\u00eb ARP dhe CAM. N\u00eb rastin e Fortigate, VXLAN FDB \u00ebsht\u00eb OVSDB. Atje do t\u00eb fillojm\u00eb:<\/p>\n

 fortigate (root) #diag sys vxlan fdb list vxlan-LS\nmac=00:50:56:8f:3f:5a state=0x0002 flags=0x00 remote_ip=\u0443.\u0443.\u0443.47 port=4789 vni=5008 ifindex=7\n<\/code><\/pre>\n
\nK\u00ebtu gjith\u00e7ka \u00ebsht\u00eb mjaft e thjesht\u00eb \u2014 adresa MAC e makineris\u00eb virtuale duhet t\u00eb ndodhet n\u00eb VTEP me adres\u00eb \u0443.\u0443.\u0443.47. Duke par\u00eb p\u00ebrmbajtjen dhe konfigurimet e klasterit ESXI, gjej se MAC i makineris\u00eb virtuale \u00ebsht\u00eb i sakt\u00eb, adresa VTEP gjithashtu. Kontrolloj tabel\u00ebn CAM\/ARP n\u00eb Fortigate \u2014 p\u00ebrs\u00ebri gjith\u00e7ka p\u00ebrputhet me konfigurimet e hostit ESXI:<\/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\n<\/code><\/pre>\n
\nTabelat jan\u00eb t\u00eb sakta dhe trafiku po shkon \u2014 ndoshta problemi nuk \u00ebsht\u00eb n\u00eb Fortigate? Q\u00ebllimisht e kam kaluar analizimin e komunikimit t\u00eb trafikut n\u00eb Juniper \u2014 logjikisht, duhej t\u00eb b\u00ebja hapat e ardhsh\u00ebm t\u00eb troubleshooting-it aty, por rrjeti im \u00ebsht\u00eb i thjesht\u00eb \u2014 vet\u00ebm nj\u00eb VLAN p\u00ebr VTEP dhe t\u00eb gjith\u00eb komponent\u00ebt jan\u00eb t\u00eb lidhur drejtp\u00ebrdrejt. Plus, m\u00eb kujtohet rasti me DLR-bridge, VDR dhe trafikun q\u00eb zhdukej \u2014 shkoj t\u00eb snifoj n\u00eb hostin ESXI, p\u00ebrpara krijoj nj\u00eb rast p\u00ebr VMware. M\u00eb posht\u00eb MAC \"97:6e\" i p\u00ebrket Fortit, vmnic1 \u2014 kjo \u00ebsht\u00eb nd\u00ebrfaqja q\u00eb ka VTEP me adres\u00ebn u.u.u.47, snifoj n\u00eb t\u00eb dyja drejtime \"\u2014dir 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
\nP\u00ebrparimi \u2014 n\u00eb sniff shoh nj\u00eb k\u00ebrkes\u00eb ARP dhe p\u00ebrgjigjen q\u00eb po vjen. Po sjell vet\u00ebm p\u00ebrgjigjen ARP dhe aty gjith\u00e7ka \u00ebsht\u00eb e sakt\u00eb. Nuk e p\u00ebrmenda, por gjat\u00eb gjith\u00eb k\u00ebsaj kohe serveri i monitorimit \u00ebsht\u00eb pinguar adres\u00ebn \u0445.\u0445.\u0445.15 \u2014 ku \u00ebsht\u00eb trafiku ICMP? Kujtoj se kam dy uplink\u00eb. K\u00ebtu mund t\u00eb diskutohet dhe t\u00eb thuhet se porta virtyale e burimit \u00ebsht\u00eb e nj\u00ebjt\u00eb (politika ime e lidhjes), pra p\u00ebr t\u00eb nj\u00ebjt\u00ebn vNIC duhet t\u00eb zgjidhet t\u00eb nj\u00ebjtin uplink, por p\u00ebrderisa jam n\u00eb host, kontrollimi i uplinkut tjet\u00ebr nuk \u00ebsht\u00eb problem:<\/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
\nVijn\u00eb k\u00ebrkesa nga Fortigate, por nuk ka p\u00ebrgjigje. K\u00ebshtu q\u00eb problemi nuk \u00ebsht\u00eb te Fortigate. Epo gjith\u00e7ka \u2014 mendoj un\u00eb \u2014 p\u00ebrs\u00ebri e nj\u00ebjta problem me humbjen e trafikut n\u00eb VDR, p\u00ebrs\u00ebri disa muaj p\u00ebr t\u00eb drejtuar rastin n\u00eb drejtimin e duhur. Pas disa dit\u00ebsh duke u qet\u00ebsuar, dhe pa d\u00ebshiruar t\u00eb pajtohem me ng\u00ebr\u00e7in, vendosa t\u00eb mbledh m\u00eb shum\u00eb sniffers p\u00ebr suportin, p\u00ebr t\u00eb gjith\u00eb procesin. Dhe k\u00ebtu,<\/p>\n
fortigate (root) #get sys arp | grep u.u.u.47\nu.u.u.47 0 00:50:56:65:f6:2c dmz\nfortigate (root) #get sys arp | grep u.u.u.42\nu.u.u.42 0 00:50:56:6a:78:86 dmz\n<\/code><\/pre>\n
\nPra, \u00e7far\u00eb kemi n\u00eb fund \u2014 pas migrimit t\u00eb makin\u00ebs virtuale, Fortigate p\u00ebrpiqet t\u00eb d\u00ebrgoj\u00eb trafik n\u00eb VTEP nga (t\u00eb sakt\u00eb) VXLAN FDB, por p\u00ebrdor MAC t\u00eb gabuar DST dhe trafiku ndjer\u00eb e hedhur nga interfaci q\u00eb e merr at\u00eb t\u00eb hipervizorit. N\u00eb nj\u00eb rast nga kat\u00ebr, ky MAC i p\u00ebrkiste hipervizorit origjinal, nga i cili filluam migrimin e makin\u00ebs.<\/p>\n
Dje mora nj\u00eb email nga mb\u00ebshtetje teknike e Fortinet \u2014 p\u00ebr rastin tim hap\u00ebn nj\u00eb bug 615586. Nuk di si t\u00eb g\u00ebzohem ose t\u00eb qaj: nga nj\u00ebra an\u00eb \u2014 problemi nuk \u00ebsht\u00eb n\u00eb konfigurim, nga ana tjet\u00ebr \u2014 rregulli do t\u00eb vij\u00eb vet\u00ebm me p\u00ebrdit\u00ebsimin e firmuerit, n\u00eb rastin m\u00eb t\u00eb mir\u00eb t\u00eb ardhsh\u00ebm. EGO e nxeht\u00ebsuar gjithashtu nj\u00eb tjet\u00ebr bug q\u00eb identifikova muajin e kaluar, ndon\u00ebse k\u00ebt\u00eb her\u00eb n\u00eb HTML5 GUI vSphere. E v\u00ebrtet\u00eb nj\u00eb departament lokal QA i shit\u00ebsve...<\/p>\n
Mund t\u00ebRiskoj t\u00eb supozoj\u00eb se:<\/p>\n
1 \u2014 plani i kontrollit t\u00eb multicast, me siguri nuk do t'i n\u00ebnshtrohet problemit t\u00eb p\u00ebrshkruar \u2014 sepse MAC adresat VTEP merren nga adresa IP e grupit, n\u00eb t\u00eb cilin \u00ebsht\u00eb i regjistruar interfaci. <\/p>\n
2 \u2014 me shum\u00eb gjasa problemi i Fortigate \u00ebsht\u00eb n\u00eb ngarkes\u00ebn e seancave n\u00eb Procesorin e Rrjetit (p\u00ebr afro t\u00eb ngjash\u00ebm CEF) \u2014 n\u00ebse kalon \u00e7do paket\u00eb p\u00ebrmes CPU, do t\u00eb p\u00ebrdoren tabelat q\u00eb p\u00ebrmbajn\u00eb informacion t\u00eb sakt\u00eb \u2014 t\u00eb pakt\u00ebn vizualisht. N\u00eb favor t\u00eb k\u00ebtij supozimi \u00ebsht\u00eb se ndihmon t\u00eb mbyll\u00ebsh\/hap\u00ebsh interfacin ose t\u00eb pres\u00ebsh pak koh\u00eb \u2014 m\u00eb shum\u00eb se 5 minuta. <\/p>\n
3 \u2014 ndryshimi i politik\u00ebs s\u00eb ekipit, p.sh. n\u00eb d\u00ebshtim t\u00eb qart\u00eb, ose implementimi i LAG nuk do t\u00eb zgjidh\u00eb problemin, sepse \u00ebsht\u00eb v\u00ebrejtur \"ng\u00ebr\u00e7i\" i MAC t\u00eb hipervizorit origjinal n\u00eb paketat e inkapsuluara.<\/p>\n
N\u00eb drit\u00ebn e k\u00ebsaj mund t\u00eb ndaj se koh\u00ebt e fundit kam zbuluar p\u00ebr vete blog<\/a><\/noindex>, ku n\u00eb nj\u00ebr\u00ebn nga artikujt u tha se firewall-et stetfull dhe metodat e transferimit t\u00eb t\u00eb dh\u00ebnave t\u00eb caching jan\u00eb justifikime. Mir\u00eb, nuk kam aq shum\u00eb p\u00ebrvoj\u00eb n\u00eb IT sa t\u00eb them di\u00e7ka t\u00eb till\u00eb, p\u00ebr m\u00eb tep\u00ebr nuk pajtohem menj\u00ebher\u00eb me t\u00eb gjitha deklaratat e artikujve t\u00eb blogut. Megjithat\u00eb, di\u00e7ka m\u00eb thot\u00eb se ka nj\u00eb grimc\u00eb t\u00eb v\u00ebrtete n\u00eb fjal\u00ebt e Ivanit.<\/p>\n
Faleminderit p\u00ebr v\u00ebmendjen! Do t\u00eb jem i lumtur t\u00eb p\u00ebrgjigjem n\u00eb pyetje dhe t\u00eb d\u00ebgjoj kritik\u00ebn konstruktive.
\n
Burimi: 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\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 n\u00eb NSX-V \u2014 zgjidhim problemin underlay | ProHoster","description":"Tungjatjeta, dhe s\u00eb pari pak lirik\u00eb.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/vxlan-v-nsx-v-trablshutim-underlay","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","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\/sq\/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\/sq\/wp-json\/wp\/v2\/posts\/73232","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=73232"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/73232\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/73233"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=73232"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=73232"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=73232"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}