{"id":78001,"date":"2020-04-15T13:42:19","date_gmt":"2020-04-15T11:42:19","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/opyt-realizaczii-setevyh-fabrik-na-baze-evpn-vxlan-i-cisco-aci-i-nebolshoe-sravnenie"},"modified":"2020-04-15T13:42:19","modified_gmt":"2020-04-15T11:42:19","slug":"opyt-realizaczii-setevyh-fabrik-na-baze-evpn-vxlan-i-cisco-aci-i-nebolshoe-sravnenie","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/opyt-realizaczii-setevyh-fabrik-na-baze-evpn-vxlan-i-cisco-aci-i-nebolshoe-sravnenie","title":{"rendered":"Eksperienc\u00eb n\u00eb implementimin e fabrikave t\u00eb rrjetit mbi EVPN VXLAN dhe Cisco ACI dhe nj\u00eb krahasim t\u00eb vog\u00ebl.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Eksperienc\u00eb
\nVler\u00ebsoni lidhjet n\u00eb mes t\u00eb diagramit. M\u00eb posht\u00eb do t'i kthehemi atyre.<\/i><\/p>\n

N\u00eb nj\u00eb moment, mund t\u00eb p\u00ebrballeni me faktin se rrjetet e m\u00ebdha dhe t\u00eb nd\u00ebrlikuara mbi L2 jan\u00eb r\u00ebnd\u00eb t\u00eb s\u00ebmura. S\u00eb pari, p\u00ebr shkak t\u00eb problemeve q\u00eb lidhen me p\u00ebrpunimin e trafikut BUM dhe pun\u00ebn e protokollit STP. S\u00eb dyti, p\u00ebr nj\u00eb arkitektur\u00eb n\u00eb t\u00ebr\u00ebsi t\u00eb vjetruar. Kjo shkakton probleme t\u00eb pak\u00ebndshme si pushime n\u00eb sh\u00ebrbim dhe v\u00ebshtir\u00ebsi n\u00eb menaxhimin e saj.<\/p>\n

Kishim dy projekte paralele, ku klient\u00ebt e vler\u00ebsuan qart\u00eb t\u00eb gjitha p\u00ebrfitimet dhe disavantazhet e mund\u00ebsive dhe zgjodh\u00ebn dy zgjidhje t\u00eb ndryshme overlay, dhe ne i implementuam ato. <\/p>\n

Ishte e mundur t\u00eb krahasohej pik\u00ebrisht implementimi. Jo operimi, p\u00ebr t\u00eb cilin vlen t\u00eb flitet pas dy-tre vjet\u00ebsh. <\/p>\n

Pra, \u00e7far\u00eb \u00ebsht\u00eb fabrika e rrjetit me rrjeta mbi t\u00eb dhe SDN?
\n<\/a><\/noindex><\/p>\n

\u00c7far\u00eb t\u00eb b\u00ebni me problemet e njohura t\u00eb arkitektur\u00ebs klasike t\u00eb rrjetit?<\/h3>\n

\n\u00c7do vit shfaqen teknologji dhe ide t\u00eb reja. N\u00eb praktik\u00eb, nevoja e nxeht\u00eb p\u00ebr t\u00eb riorganizuar rrjetet nuk ka qen\u00eb e pranishme p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb, sepse gjith\u00e7ka mund t\u00eb b\u00ebhet me duar sipas metodave tradicionale. E megjithat\u00eb, \u00e7far\u00eb ka r\u00ebnd\u00ebsi q\u00eb jemi n\u00eb shekullin e nj\u00ebzet e nj\u00eb? N\u00eb fund t\u00eb fundit, administratori duhet t\u00eb punoj\u00eb, jo t\u00eb q\u00ebndroj\u00eb n\u00eb kabin\u00ebn e tij. <\/p>\n

Pastaj filloi bum i nd\u00ebrtimit t\u00eb qendrave t\u00eb t\u00eb dh\u00ebnave n\u00eb shkall\u00eb t\u00eb madhe. Aty ku u kuptua se arriti kufirin e zhvillimit t\u00eb arkitektur\u00ebs klasike, jo vet\u00ebm n\u00eb aspektin e funksionit, q\u00ebndrueshm\u00ebris\u00eb dhe shkall\u00ebzueshm\u00ebris\u00eb. Nj\u00eb nga zgjidhjet p\u00ebr k\u00ebto probleme ishte ideja e nd\u00ebrtimit t\u00eb rrjeteve t\u00eb mbivendosura mbi nj\u00eb backbone t\u00eb ruterizuar.<\/p>\n

P\u00ebrve\u00e7 k\u00ebsaj, me rritjen e masave t\u00eb rrjeteve, \u00e7\u00ebshtja e menaxhimit t\u00eb k\u00ebtyre fabrikave u b\u00eb e ngjar\u00eb, si rezultat i t\u00eb cilave filluan t\u00eb shfaqen zgjidhjet e rrjeteve t\u00eb menaxhuara nga softueri, me mund\u00ebsin\u00eb p\u00ebr t\u00eb menaxhuar t\u00eb gjith\u00eb infrastruktur\u00ebn rrjetore si nj\u00eb entitet t\u00eb vet\u00ebm. Kur rrjeti menaxhohet nga nj\u00eb pik\u00eb e vetme, \u00ebsht\u00eb m\u00eb e leht\u00eb p\u00ebr komponent\u00ebt e tjer\u00eb t\u00eb infrastruktur\u00ebs IT t\u00eb bashk\u00ebveprojn\u00eb me t\u00eb, dhe k\u00ebto procese bashk\u00ebveprimi mund t\u00eb automatizohen m\u00eb leht\u00eb.<\/p>\n

Gati \u00e7do prodhues i njohur jo vet\u00ebm i pajisjeve rrjetore, por edhe i virtualizimit, ka n\u00eb portofolin e tij mund\u00ebsi t\u00eb tilla zgjidhjesh. <\/p>\n

Mbetej vet\u00ebm t\u00eb kuptojm\u00eb se \u00e7far\u00eb do t\u00eb p\u00ebrshtatet p\u00ebr nevojat e caktuara. P\u00ebr shembull, p\u00ebr kompanit\u00eb shum\u00eb t\u00eb m\u00ebdha q\u00eb kan\u00eb nj\u00eb ekip t\u00eb mir\u00eb zhvilluesish dhe operativ, zgjidhjet e gatshme nga furnizuesit nuk p\u00ebrmbushin gjithmon\u00eb t\u00eb gjitha nevojat, dhe ato ndihmojn\u00eb n\u00eb zhvillimin e zgjidhjeve t\u00eb veta me SD (software defined). P\u00ebr shembull, k\u00ebto jan\u00eb ofruesit e sh\u00ebrbimeve n\u00eb cloud, t\u00eb cil\u00ebt vazhdimisht zgjeruan gam\u00ebn e sh\u00ebrbimeve q\u00eb u ofrojn\u00eb klient\u00ebve t\u00eb tyre, dhe zgjidhjet e gatshme thjesht nuk arrijn\u00eb t\u00eb p\u00ebrballen me nevojat e tyre. <\/p>\n

P\u00ebr kompanit\u00eb mesatare, funksionaliteti i ofruar nga furnizuesi n\u00eb form\u00ebn e nj\u00eb zgjidhjeje t\u00eb gatshme mjafton n\u00eb 99 p\u00ebrqind t\u00eb rasteve. <\/p>\n

\u00c7far\u00eb jan\u00eb rrjetet overlay?<\/h3>\n

\n\u00c7far\u00eb q\u00ebndron pas ideve t\u00eb rrjeteve me mbivendosje. N\u00eb thelb, ju merrni nj\u00eb rrjet t\u00eb klas\u00ebs ruter dhe nd\u00ebrtoni sip\u00ebr tij nj\u00eb rrjet tjet\u00ebr, p\u00ebr t\u00eb fituar m\u00eb shum\u00eb funksionalitete. M\u00eb shpesh, ky \u00ebsht\u00eb nj\u00eb diskutim p\u00ebr shp\u00ebrndarjen e efektshme t\u00eb ngarkes\u00ebs n\u00eb pajisje dhe linjat e komunikimit, p\u00ebr nj\u00eb rritje t\u00eb konsiderueshme t\u00eb kufijve t\u00eb shkall\u00ebzueshm\u00ebris\u00eb, p\u00ebr forcimin e besueshm\u00ebris\u00eb dhe nj\u00eb mori avantazhesh p\u00ebr sigurin\u00eb (p\u00ebrmes segmentimit). Zgjidhjet SDN, p\u00ebrve\u00e7 k\u00ebsaj, ofrojn\u00eb mund\u00ebsi p\u00ebr administrim tep\u00ebr fleksib\u00ebl dhe e b\u00ebjn\u00eb rrjetin m\u00eb t\u00eb qart\u00eb p\u00ebr konsumator\u00ebt e tij. <\/p>\n

N\u00eb p\u00ebrgjith\u00ebsi, n\u00ebse rrjetet lokale do t\u00eb ishin sajuar n\u00eb vitet 2010, ato nuk do t\u00eb dukeshin aspak si ato q\u00eb trash\u00ebguam nga ushtar\u00ebt n\u00eb vitet 1970. <\/p>\n

Nga perspektiva e teknologjive p\u00ebr nd\u00ebrtimin e fabrikave duke p\u00ebrdorur rrjete t\u00eb mbivendosura, aktualisht ka shum\u00eb implementime nga prodhues dhe projekte interneti RFC (EVPN+VXLAN, EVPN+MPLS, EVPN+MPLSoGRE, EVPN+Geneve dhe t\u00eb tjera). Po, ka standarde, por realizimi i k\u00ebtyre standardeve nga prodhues t\u00eb ndrysh\u00ebm mund t\u00eb jet\u00eb i ndrysh\u00ebm, prandaj, kur krijoni k\u00ebto fabrika, \u00ebsht\u00eb e mundur t\u00eb heq\u00ebsh dor\u00eb plot\u00ebsisht nga vendori n\u00eb teori vet\u00ebm n\u00eb let\u00ebr.<\/p>\n

MeSD mjedisi \u00ebsht\u00eb edhe m\u00eb i nd\u00ebrlikuar; \u00e7do furnizues ka vizionin e vet. Ka zgjidhje plot\u00ebsisht t\u00eb hapura, t\u00eb cilat teori i mund\u00ebsojn\u00eb p\u00ebrmir\u00ebsimin nga vet\u00eb, dhe ka zgjidhje plot\u00ebsisht t\u00eb mbyllura.<\/p>\n

Cisco ofron variantin e vet SDN p\u00ebr qendrat e t\u00eb dh\u00ebnave \u2014 ACI. Natyrisht, kjo \u00ebsht\u00eb nj\u00eb zgjidhje 100% e lokalizuar e furnizuesit n\u00eb aspektin e p\u00ebrzgjedhjes s\u00eb pajisjeve rrjetike, por p\u00ebrve\u00e7 k\u00ebsaj, ajo integrohet plot\u00ebsisht me sistemet e virtualizimit, kontejnerizimit, siguris\u00eb, orkestrimit, balancuesve t\u00eb ngarkes\u00ebs dhe t\u00eb tjer\u00ebve. Por n\u00eb thelb, kjo \u00ebsht\u00eb akoma nj\u00eb kut\u00eb e zez\u00eb, pa mund\u00ebsi p\u00ebr qasje t\u00eb plot\u00eb n\u00eb t\u00eb gjitha proceset e brendshme. Nuk t\u00eb gjith\u00eb bler\u00ebsit jan\u00eb t\u00eb gatsh\u00ebm p\u00ebr k\u00ebt\u00eb variant, pasi je plot\u00ebsisht i varur nga cil\u00ebsia e kodit t\u00eb shkruar p\u00ebr zgjidhjen dhe realizimin e saj. Nga ana tjet\u00ebr, prodhuesi ka nj\u00eb nga mb\u00ebshtetje teknike m\u00eb t\u00eb mira n\u00eb bot\u00eb dhe ka nj\u00eb ekip t\u00eb dedikuar q\u00eb merret vet\u00ebm me k\u00ebt\u00eb zgjidhje. Si zgjidhje p\u00ebr projektin e par\u00eb, u zgjodh pik\u00ebrisht Cisco ACI.<\/p>\n

P\u00ebr projektin e dyt\u00eb u zgjodh zgjidhja nga Juniper. Prodhuesi gjithashtu ka SDN t\u00eb tij p\u00ebr Qendr\u00ebn e t\u00eb Dh\u00ebnave, por klienti vendosi t\u00eb heq\u00eb dor\u00eb nga implementimi i SDN. Si teknologji e nd\u00ebrtimit t\u00eb rrjetit u zgjodh fabrika EVPN VXLAN pa p\u00ebrdorimin e kontroler\u00ebve t\u00eb centralizuar.<\/p>\n

P\u00ebr \u00e7far\u00eb nevojitet<\/h3>\n

\nKrijimi i fabrik\u00ebs lejon nd\u00ebrtimin e nj\u00eb rrjeti t\u00eb leht\u00eb p\u00ebr t'u shkall\u00ebzuar, t\u00eb q\u00ebndruesh\u00ebm dhe t\u00eb besuesh\u00ebm. Arkitektura (leaf-spine) merr parasysh ve\u00e7orit\u00eb e qendrave t\u00eb p\u00ebrpunimit t\u00eb t\u00eb dh\u00ebnave<\/a> (rrug\u00ebt e kalimit t\u00eb trafikut, minimizimin e vonesave dhe ngushticave n\u00eb rrjet). Zgjidhjet SD n\u00eb Qendrat e t\u00eb Dh\u00ebnave lejojn\u00eb t\u00eb menaxhohet shum\u00eb leht\u00eb, shpejt dhe fleksib\u00ebl nj\u00eb fabrik\u00eb e till\u00eb, duke e integruar at\u00eb n\u00eb ekosistemin e Qendr\u00ebs s\u00eb t\u00eb Dh\u00ebnave. <\/p>\n

T\u00eb dy klient\u00ebt kishin nevoj\u00eb p\u00ebr nd\u00ebrtimin e Qendrave t\u00eb t\u00eb Dh\u00ebnave rezerv\u00eb p\u00ebr sigurimin e q\u00ebndrueshm\u00ebris\u00eb, p\u00ebrve\u00e7 k\u00ebsaj, trafiku midis Qendrave t\u00eb t\u00eb Dh\u00ebnave duhej t\u00eb ishte i enkriptuar.<\/p>\n

Klienti i par\u00eb tashm\u00eb kishte shqyrtuar zgjidhje pa fabrik\u00eb si nj\u00eb standard t\u00eb mundsh\u00ebm p\u00ebr rrjetet e tij, por n\u00eb provat e tyre kishin probleme me p\u00ebrputhshm\u00ebrin\u00eb STP midis disa shit\u00ebsve t\u00eb pajisjeve. Erdh\u00ebn nd\u00ebrprerje q\u00eb shkaktuan r\u00ebnien e sh\u00ebrbimeve. Dhe p\u00ebr klientin kjo ishte kritike. <\/p>\n

Cisco tashm\u00eb ishte standardi i korporatave p\u00ebr klient\u00ebt, ata shqyrtuan ACI-n\u00eb dhe opsione t\u00eb tjera dhe vendos\u00ebn se duhet t\u00eb zgjidhnin k\u00ebt\u00eb zgjidhje. U p\u00eblqeu automatizimi i menaxhimit me nj\u00eb buton p\u00ebrmes nj\u00eb kontrollori t\u00eb vet\u00ebm. Sh\u00ebrbimet konfigurohen m\u00eb shpejt, menaxhohen m\u00eb shpejt. P\u00ebr t\u00eb siguruar enkriptimin e trafikut, ata vendos\u00ebn t\u00eb aktivizojn\u00eb MACSec nd\u00ebrmjet switch-\u00ebve IPN dhe SPINE. K\u00ebshtu arrit\u00ebn t\u00eb shmangin ngushtic\u00ebn e nj\u00eb kalimi kriptografik, t\u00eb kursejn\u00eb para mbi t\u00eb dhe t\u00eb p\u00ebrdorin n\u00eb maksimum brezin e kapacitetit.<\/p>\n

Klienti i dyt\u00eb zgjodhi nj\u00eb zgjidhje pa kontrollues nga Juniper, pasi q\u00eb n\u00eb qendr\u00ebn e tyre ekzistuese t\u00eb t\u00eb dh\u00ebnave kishte nj\u00eb instalim t\u00eb vog\u00ebl me realizimin e fabrik\u00ebs EVPN VXLAN. Por aty nuk kishte q\u00ebndrueshm\u00ebri (p\u00ebrdorej nj\u00eb switch i vet\u00ebm). K\u00ebshtu, u vendos t\u00eb zgjeronin infrastruktur\u00ebn e qendr\u00ebs kryesore t\u00eb t\u00eb dh\u00ebnave dhe t\u00eb nd\u00ebrtuan fabrik\u00ebn n\u00eb qendr\u00ebn e rezerv\u00ebs. EVPN ekzistues nuk ishte p\u00ebrdorur plot\u00ebsisht: enkapsulimi VXLAN faktikisht nuk ishte aplikuar, pasi t\u00eb gjitha hostet ishin t\u00eb lidhura me nj\u00eb switch t\u00eb vet\u00ebm, dhe t\u00eb gjitha adresat MAC dhe \/32 ishin lokale, ky switch sh\u00ebrbente si gateway p\u00ebr to, dhe nuk kishte pajisje t\u00eb tjera ku nevojitej nd\u00ebrtimi i tunelieve VXLAN. U vendos t\u00eb sigurohej enkriptimi i trafikut duke p\u00ebrdorur teknologjin\u00eb IPSEC midis firewalleve (kapaciteti i M\u0421E ishte i mjaftuesh\u00ebm).<\/p>\n

Po ashtu shqyrtuam ACI-n\u00eb, por vendos\u00ebm se p\u00ebr shkak t\u00eb lokacionit t\u00eb furnizuesit do t\u00eb duhej t\u00eb blinim shum\u00eb pajisje, duke p\u00ebrfshir\u00eb z\u00ebvend\u00ebsimin e pajisjeve t\u00eb reja q\u00eb ishin bler\u00eb s\u00eb fundmi, dhe kjo thjesht nuk kishte kuptim ekonomik. Po, fabrika Cisco integrohet me t\u00eb gjitha, por brenda vet\u00eb fabrik\u00ebs mund t\u00eb p\u00ebrdoren vet\u00ebm pajisjet e saj. <\/p>\n

Nga ana tjet\u00ebr, si\u00e7 u tha m\u00eb par\u00eb, nuk mund t\u00eb p\u00ebrzjehen aq leht\u00eb fabrika EVPN VXLAN me ndonj\u00eb ofrues fqinj, sepse implementimet e protokollit ndryshojn\u00eb. \u00cbsht\u00eb si t\u00eb p\u00ebrzjeh\u00ebsh Cisco dhe Huawei n\u00eb nj\u00eb rrjet \u2014 ndon\u00ebse standardet jan\u00eb t\u00eb p\u00ebrbashk\u00ebta, do t\u00eb duhen p\u00ebrpjekje t\u00eb m\u00ebdha. Duke qen\u00eb se kjo \u00ebsht\u00eb nj\u00eb bank\u00eb dhe testet e kompatibilitetit do t\u00eb ishin shum\u00eb t\u00eb gjata, u vendos q\u00eb t\u00eb blihen pajisje nga i nj\u00ebjti ofrues tani, pa u qet\u00ebsuar shum\u00eb p\u00ebr funksionalitetin jasht\u00eb baz\u00ebs. <\/p>\n

Plani i migrimit<\/h3>\n

\nDy Qendra t\u00eb t\u00eb Dh\u00ebnave me baz\u00eb ACI:<\/p>\n

\"Eksperienc\u00eb
\n
\nOrganizimi i bashk\u00ebpunimit midis Qendrave t\u00eb t\u00eb Dh\u00ebnave. U zgjodh zgjidhja Multi-Pod \u2014 \u00e7do Qend\u00ebr t\u00eb Dh\u00ebnash \u00ebsht\u00eb nj\u00eb pod. U mor\u00ebn parasysh k\u00ebrkesat p\u00ebr shkall\u00ebzim sipas numrit t\u00eb switch-ev dhe p\u00ebr vonesat midis pod-ev (RTT m\u00eb pak se 50 ms). U vendos t\u00eb mos nd\u00ebrtohej nj\u00eb zgjidhje Multi-Site p\u00ebr leht\u00ebsin\u00eb e menaxhimit (p\u00ebr zgjidhjen Multi-Pod p\u00ebrdoret nj\u00eb nd\u00ebrfaqe menaxhimi, nd\u00ebrsa p\u00ebr Multi-Site do t\u00eb ishin dy nd\u00ebrfaqe, ose do t\u00eb duhej nj\u00eb Orkestrator Multi-Site), dhe gjithashtu p\u00ebr shkak se nuk ishte e nevojshme rezervimi gjeografik i vendeve.<\/p>\n

\"Eksperienc\u00eb
\n
\nSa i p\u00ebrket migrimit t\u00eb sh\u00ebrbimeve nga rrjeti Legacy, u zgjodh opsioni m\u00eb transparent, transferimi gradual i VLAN-eve p\u00ebrkat\u00ebse sh\u00ebrbimeve specifike.
\nP\u00ebr migrimin e \u00e7do VLAN krijohej nj\u00eb EPG (End-point-group) p\u00ebrkat\u00ebs n\u00eb fabrik\u00eb. Fillimisht, rrjeti shtrihej midis rrjetit t\u00eb vjet\u00ebr dhe fabrik\u00ebs n\u00eb L2, pastaj, pasi t\u00eb ishin migruar t\u00eb gjitha hostet, porta u transferua n\u00eb fabrik\u00eb, dhe nd\u00ebrveprimi i EPG me rrjetin ekzistues u realizua p\u00ebrmes L3OUT, nd\u00ebrsa nd\u00ebrveprimi midis L3OUT dhe EPG u p\u00ebrshkrua duke p\u00ebrdorur kontrata. Skema e p\u00ebraf\u00ebrt:<\/p>\n

\"Eksperienc\u00eb
\n
\nStruktura e p\u00ebraf\u00ebrt e politikave m\u00eb t\u00eb shumta t\u00eb fabrik\u00ebs ACI n\u00eb figur\u00ebn m\u00eb posht\u00eb. E gjith\u00eb konfigurimi nd\u00ebrtohet mbi politika, t\u00eb vendosura brenda politikave t\u00eb tjera dhe k\u00ebshtu me radh\u00eb. N\u00eb fillim \u00ebsht\u00eb shum\u00eb e v\u00ebshtir\u00eb t\u00eb kuptohet, por gradualisht, si\u00e7 tregon praktika, administrator\u00ebt e rrjetit e zakonisht e p\u00ebrshtatin veten me k\u00ebt\u00eb struktur\u00eb p\u00ebr rreth nj\u00eb muaj, dhe pastaj vet\u00ebm vjen kuptimi se sa e p\u00ebrshtatshme \u00ebsht\u00eb ajo.<\/p>\n

\"Eksperienc\u00eb
\n <\/p>\n

Krahasimi<\/h3>\n

\nN\u00eb zgjidhjen Cisco ACI duhet t\u00eb blihet m\u00eb shum\u00eb pajisje (switch-e t\u00eb ve\u00e7ant\u00eb p\u00ebr bashk\u00ebveprimin Inter-Pod dhe kontrollues APIC), p\u00ebr \u00e7ka ajo doli m\u00eb e shtrenjt\u00eb. Zgjidhja Juniper nuk k\u00ebrkoi blerjen e kontrolluesve dhe pajisjeve ndihm\u00ebse; arriti t\u00eb p\u00ebrdorte pjes\u00ebrisht pajisjet ekzistuese t\u00eb klientit. <\/p>\n

Kjo \u00ebsht\u00eb arkitektura e fabrik\u00ebs EVPN VXLAN p\u00ebr dy Qendrat e t\u00eb Dh\u00ebnave t\u00eb projektit t\u00eb dyt\u00eb:<\/p>\n

\"Eksperienc\u00eb
\n\"Eksperienc\u00eb
\n
\nN\u00eb ACI merr nj\u00eb zgjidhje t\u00eb gatshme \u2014 nuk \u00ebsht\u00eb e nevojshme t\u00eb g\u00ebrmosh, nuk \u00ebsht\u00eb e nevojshme t\u00eb optimizosh. Kur klienti fillon t\u00eb njihet me fabrik\u00ebn, nuk jan\u00eb t\u00eb nevojsh\u00ebm zhvilluesit, as njer\u00ebzit mb\u00ebshtet\u00ebs p\u00ebr kodin dhe automatizimin. Mjafton thjesht p\u00ebrdorimi, shum\u00eb nga konfigurimet mund t\u00eb b\u00ebhen n\u00ebp\u00ebrmjet nj\u00eb wizardi, q\u00eb nuk \u00ebsht\u00eb gjithmon\u00eb nj\u00eb plus, sidomos p\u00ebr ata q\u00eb jan\u00eb m\u00ebsuar me komand\u00ebn e linj\u00ebs. N\u00eb \u00e7do rast, nevojitet koh\u00eb p\u00ebr t\u00eb ristrukturuar mendjen n\u00eb binar\u00ebt e rinj, n\u00eb ve\u00e7orit\u00eb e konfigurimeve p\u00ebrmes politikave dhe operimin e nj\u00eb numri t\u00eb madh politikash t\u00eb nd\u00ebrlidhura me nj\u00ebra-tjetr\u00ebn. Shum\u00eb e d\u00ebshirueshme \u00ebsht\u00eb gjithashtu t\u00eb kesh nj\u00eb struktur\u00eb t\u00eb qart\u00eb em\u00ebrtimi t\u00eb politikave dhe objekteve. Kur t\u00eb lind ndonj\u00eb problem n\u00eb logjik\u00ebn e pun\u00ebs s\u00eb kontrolluesit, mund t\u00eb zgjidhesh vet\u00ebm p\u00ebrmes mb\u00ebshtetjes teknike.<\/p>\n

N\u00eb EVPN \u2014 konsola. P\u00ebso ose g\u00ebzo. Nj\u00eb nd\u00ebrfaqe e njohur p\u00ebr gard\u00ebn e vjet\u00ebr. Po, ka nj\u00eb konfigurim standard dhe udh\u00ebzues. Do t\u00eb duhet t\u00eb lexosh manualet. Konstruktime t\u00eb ndryshme, gjith\u00e7ka \u00ebsht\u00eb e qart\u00eb dhe e detajuar.<\/p>\n

Sigurisht, n\u00eb t\u00eb dy rastet, \u00ebsht\u00eb m\u00eb mir\u00eb q\u00eb gjat\u00eb migrimit t\u00eb filloni me sh\u00ebrbimet m\u00eb pak kritike, si\u00e7 jan\u00eb ambientet testuese, dhe vet\u00ebm pas identifikimit t\u00eb t\u00eb gjitha problemeve t\u00eb kaloni n\u00eb prodhim. Dhe mos e konfiguroni n\u00eb fundjav\u00eb. Nuk duhet t\u00eb besoni te ofruesi q\u00eb gjith\u00e7ka do t\u00eb shkoj\u00eb mir\u00eb; gjithmon\u00eb \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb jeni t\u00eb sigurt.<\/p>\n

Me ACI paguan m\u00eb shum\u00eb, megjith\u00ebse Cisco aktualisht po promovon k\u00ebt\u00eb zgjidhje dhe shpesh ofron zbritje t\u00eb mira p\u00ebr t\u00eb, por kursen n\u00eb sh\u00ebrbimin e mb\u00ebshtetjes. Menaxhimi dhe \u00e7do automatizim i fabrik\u00ebs EVPN pa nj\u00eb kontrollor k\u00ebrkon investime dhe shpenzime t\u00eb rregullta \u2014 monitorim, automatizim, implementim t\u00eb sh\u00ebrbimeve t\u00eb reja. Nd\u00ebrkoh\u00eb, nisja fillestare n\u00eb ACI zgjat 30\u201340 p\u00ebrqind m\u00eb shum\u00eb. Kjo ndodh p\u00ebr shkak se zgjat m\u00eb gjat\u00eb t\u00eb krijohet e gjith\u00eb paketa e nevojshme e profileve dhe politikave q\u00eb do t\u00eb p\u00ebrdoren. Por me rritjen e rrjetit, numri i konfigurimeve t\u00eb nevojshme zvog\u00eblohet. P\u00ebrdor politik\u00eb, profile, objekte t\u00eb krijuara paraprakisht. Mund t\u00eb konfigurosh n\u00eb m\u00ebnyr\u00eb fleksib\u00ebl segmentimin dhe sigurimin, menaxhimin q\u00ebndror t\u00eb kontratave q\u00eb p\u00ebrshkruajn\u00eb interaksionet midis EPG-ve, \u2014 volumi i pun\u00ebs bie ndjesh\u00ebm. <\/p>\n

N\u00eb EVPN duhet t\u00eb konfigurosh \u00e7do pajisje n\u00eb fabrik\u00eb, probabiliteti i gabimit \u00ebsht\u00eb m\u00eb i lart\u00eb.<\/p>\n

N\u00ebse ACI implementohet ngadal\u00eb, at\u00ebher\u00eb EVPN \u00ebsht\u00eb dyfish m\u00eb i ngadalsh\u00ebm p\u00ebr rikuperim. N\u00eb rastin e Cisco gjithmon\u00eb mund t\u00eb th\u00ebrras\u00ebsh inxhinierin e mb\u00ebshtetjes dhe t\u00eb pyes\u00ebsh p\u00ebr rrjetin n\u00eb p\u00ebrgjith\u00ebsi (sepse mbulon si nj\u00eb zgjidhje), nd\u00ebrsa me Juniper Networks blen vet\u00ebm harduerin, dhe kjo \u00ebsht\u00eb ajo \u00e7ka mbulohet. Pakot nga pajisja ik\u00ebn? Ok, tani jan\u00eb problemet tuaja. Por mund t\u00eb hapni nj\u00eb \u00e7\u00ebshtje rreth zgjedhjes s\u00eb zgjidhjes ose dizajnit t\u00eb rrjetit \u2014 dhe at\u00ebher\u00eb do t\u00eb rekomandohet t\u00eb blini nj\u00eb sh\u00ebrbim profesional, me pages\u00eb shtes\u00eb.<\/p>\n

Mb\u00ebshtetja ACI \u00ebsht\u00eb shum\u00eb e shk\u00eblqyer, sepse \u00ebsht\u00eb e ve\u00e7ant\u00eb: nj\u00eb ekip i ve\u00e7ant\u00eb \u00ebsht\u00eb aty vet\u00ebm p\u00ebr k\u00ebt\u00eb. Ka gjithashtu dhe specialist\u00eb q\u00eb flasin rusisht. Udh\u00ebzuesi \u00ebsht\u00eb i detajuar, zgjidhjet jan\u00eb t\u00eb paracaktuara. Ata shqyrtojn\u00eb dhe japin sugjerime. Shpejt validojn\u00eb dizajnin, gj\u00eb q\u00eb shpesh \u00ebsht\u00eb e r\u00ebnd\u00ebsishme. Juniper Networks b\u00ebn t\u00eb nj\u00ebjt\u00ebn gj\u00eb, por me shum\u00eb ngadal\u00eb (ne e kemi p\u00ebrjetuar, tani duhet t\u00eb jet\u00eb m\u00eb mir\u00eb sipas thashethemeve), gj\u00eb q\u00eb t\u00eb detyron t\u00eb b\u00ebsh gjith\u00e7ka vet\u00eb, aty ku mund t\u00eb kishte k\u00ebshilluar inxhinieri i zgjidhjeve. <\/p>\n

Cisco ACI mb\u00ebshtet integrimin me sistemet e virtualizimit dhe kontejnerizimit (VMware, Kubernetes, Hyper-V) dhe menaxhimin e centralizuar. Ka sh\u00ebrbime rrjeti dhe sh\u00ebrbime sigurie \u2014 balancimi, firewall, WAF, IPS dhe t\u00eb tjera... Mikrosektorizimi i mir\u00eb nga kutia. N\u00eb zgjidhjen e dyt\u00eb, integrimi me sh\u00ebrbimet rrjetore b\u00ebhet me v\u00ebshtir\u00ebsi, dhe \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb hulumtoni p\u00ebrpara n\u00eb forume me ata q\u00eb e kan\u00eb b\u00ebr\u00eb k\u00ebt\u00eb. <\/p>\n

P\u00ebrfundimi<\/h3>\n

\nP\u00ebr \u00e7do rast t\u00eb ve\u00e7ant\u00eb, \u00ebsht\u00eb e nevojshme t\u00eb zgjidhet nj\u00eb zgjidhje, jo vet\u00ebm n\u00eb baz\u00eb t\u00eb kostos s\u00eb pajisjeve, por gjithashtu duhet t\u00eb merren parasysh shpenzimet e ardhshme t\u00eb operimit dhe problemet kryesore me t\u00eb cilat p\u00ebrballet klienti tani, si dhe planet p\u00ebr zhvillimin e infrastruktur\u00ebs IT. <\/p>\n

ACI, p\u00ebr shkak t\u00eb pajisjeve shtes\u00eb, doli m\u00eb e kushtueshme, por zgjidhja \u00ebsht\u00eb e gatshme pa nevoj\u00ebn p\u00ebr p\u00ebrmir\u00ebsime, zgjidhja e dyt\u00eb \u00ebsht\u00eb m\u00eb komplekse dhe e shtrenjt\u00eb n\u00eb aspektin e operimit, por m\u00eb e lir\u00eb. <\/p>\n

N\u00ebse d\u00ebshironi t\u00eb diskutoni se sa mund t\u00eb kushtoj\u00eb zbatimi i nj\u00eb fabrike rrjetesh me ofrues t\u00eb ndrysh\u00ebm dhe cila \u00ebsht\u00eb e nevojshme arkitektura, mund t\u00eb takohemi dhe t\u00eb flasim. Para skic\u00ebs p\u00ebrfundimtare t\u00eb arkitektur\u00ebs (me t\u00eb cil\u00ebn mund t\u00eb llogariten buxhetet), do t'ju ndihmojm\u00eb falas; p\u00ebrpunimi m\u00eb i detajuar, sigurisht, do t\u00eb jet\u00eb me pages\u00eb.<\/p>\n

Vladimir Klepche, rrjetet korporative.<\/p><\/blockquote>\n

Burimi: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041e\u0446\u0435\u043d\u0438\u0442\u0435 \u0441\u0432\u044f\u0437\u043a\u0438 \u0432 \u0441\u0440\u0435\u0434\u043d\u0435\u0439 \u0447\u0430\u0441\u0442\u0438 \u0441\u0445\u0435\u043c\u044b. \u041d\u0438\u0436\u0435 \u043a \u043d\u0438\u043c \u0432\u0435\u0440\u043d\u0451\u043c\u0441\u044f \u0412 \u043a\u0430\u043a\u043e\u0439-\u0442\u043e \u043c\u043e\u043c\u0435\u043d\u0442 \u0432\u044b \u043c\u043e\u0436\u0435\u0442\u0435 \u0441\u0442\u043e\u043b\u043a\u043d\u0443\u0442\u044c\u0441\u044f \u0441 \u0442\u0435\u043c, \u0447\u0442\u043e \u0431\u043e\u043b\u044c\u0448\u0438\u0435 \u0441\u043b\u043e\u0436\u043d\u044b\u0435 \u0441\u0435\u0442\u0438 \u043d\u0430 \u0431\u0430\u0437\u0435 L2 \u043d\u0435\u0438\u0437\u043b\u0435\u0447\u0438\u043c\u043e \u0431\u043e\u043b\u044c\u043d\u044b. \u0412 \u043f\u0435\u0440\u0432\u0443\u044e \u043e\u0447\u0435\u0440\u0435\u0434\u044c \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430\u043c\u0438, \u0441\u0432\u044f\u0437\u0430\u043d\u043d\u044b\u043c\u0438 \u0441 \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u043e\u0439 BUM \u0442\u0440\u0430\u0444\u0438\u043a\u0430 \u0438 \u0441 \u0440\u0430\u0431\u043e\u0442\u043e\u0439 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 STP. \u0412\u043e \u0432\u0442\u043e\u0440\u0443\u044e \u2014 \u0432 \u0446\u0435\u043b\u043e\u043c \u043c\u043e\u0440\u0430\u043b\u044c\u043d\u043e \u0443\u0441\u0442\u0430\u0440\u0435\u0432\u0448\u0435\u0439 \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u043e\u0439. \u042d\u0442\u043e \u0432\u044b\u0437\u044b\u0432\u0430\u0435\u0442 \u043d\u0435\u043f\u0440\u0438\u044f\u0442\u043d\u044b\u0435 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u0432 \u0432\u0438\u0434\u0435 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":78002,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-78001","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\udd47Eksperienca e realizimit t\u00eb fabrikave rrjetesh mbi EVPN VXLAN dhe Cisco ACI dhe nj\u00eb krahasim i vog\u00ebl | ProHoster","description":"Vler\u00ebsoni lidhjet n\u00eb pjes\u00ebn qendrore t\u00eb skem\u00ebs. M\u00eb posht\u00eb do t\u00eb kthehemi te ato. N\u00eb nj\u00eb moment, mund t\u00eb p\u00ebrballeni me nj\u00eb situat\u00eb ku rrjetet e m\u00ebdha dhe t\u00eb nd\u00ebrlikuara mbi L2 jan\u00ebthell\u00ebsisht t\u00eb s\u00ebmura. N\u00eb radh\u00eb t\u00eb par\u00eb p\u00ebr problemet e lidhura me p\u00ebrpunimin e trafikut BUM dhe funksionimin e protokollit STP. N\u00eb t\u00eb dyt\u00ebn\u2014 n\u00eb p\u00ebrgjith\u00ebsi me nj\u00eb arkitektur\u00eb t\u00eb vjet\u00ebr n\u00eb moral. Kjo shkakton probleme t\u00eb pak\u00ebndshme n\u00eb form\u00ebn e","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/opyt-realizaczii-setevyh-fabrik-na-baze-evpn-vxlan-i-cisco-aci-i-nebolshoe-sravnenie","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\udd47\u041e\u043f\u044b\u0442 \u0440\u0435\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u0441\u0435\u0442\u0435\u0432\u044b\u0445 \u0444\u0430\u0431\u0440\u0438\u043a \u043d\u0430 \u0431\u0430\u0437\u0435 EVPN VXLAN \u0438 Cisco ACI \u0438 \u043d\u0435\u0431\u043e\u043b\u044c\u0448\u043e\u0435 \u0441\u0440\u0430\u0432\u043d\u0435\u043d\u0438\u0435 | ProHoster","og:description":"\u041e\u0446\u0435\u043d\u0438\u0442\u0435 \u0441\u0432\u044f\u0437\u043a\u0438 \u0432 \u0441\u0440\u0435\u0434\u043d\u0435\u0439 \u0447\u0430\u0441\u0442\u0438 \u0441\u0445\u0435\u043c\u044b. \u041d\u0438\u0436\u0435 \u043a \u043d\u0438\u043c \u0432\u0435\u0440\u043d\u0451\u043c\u0441\u044f \u0412 \u043a\u0430\u043a\u043e\u0439-\u0442\u043e \u043c\u043e\u043c\u0435\u043d\u0442 \u0432\u044b \u043c\u043e\u0436\u0435\u0442\u0435 \u0441\u0442\u043e\u043b\u043a\u043d\u0443\u0442\u044c\u0441\u044f \u0441 \u0442\u0435\u043c, \u0447\u0442\u043e \u0431\u043e\u043b\u044c\u0448\u0438\u0435 \u0441\u043b\u043e\u0436\u043d\u044b\u0435 \u0441\u0435\u0442\u0438 \u043d\u0430 \u0431\u0430\u0437\u0435 L2 \u043d\u0435\u0438\u0437\u043b\u0435\u0447\u0438\u043c\u043e \u0431\u043e\u043b\u044c\u043d\u044b. \u0412 \u043f\u0435\u0440\u0432\u0443\u044e \u043e\u0447\u0435\u0440\u0435\u0434\u044c \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430\u043c\u0438, \u0441\u0432\u044f\u0437\u0430\u043d\u043d\u044b\u043c\u0438 \u0441 \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u043e\u0439 BUM \u0442\u0440\u0430\u0444\u0438\u043a\u0430 \u0438 \u0441 \u0440\u0430\u0431\u043e\u0442\u043e\u0439 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 STP. \u0412\u043e \u0432\u0442\u043e\u0440\u0443\u044e \u2014 \u0432 \u0446\u0435\u043b\u043e\u043c \u043c\u043e\u0440\u0430\u043b\u044c\u043d\u043e \u0443\u0441\u0442\u0430\u0440\u0435\u0432\u0448\u0435\u0439 \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u043e\u0439. \u042d\u0442\u043e \u0432\u044b\u0437\u044b\u0432\u0430\u0435\u0442 \u043d\u0435\u043f\u0440\u0438\u044f\u0442\u043d\u044b\u0435 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u0432 \u0432\u0438\u0434\u0435","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/opyt-realizaczii-setevyh-fabrik-na-baze-evpn-vxlan-i-cisco-aci-i-nebolshoe-sravnenie","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-04-15T11:42:19+00:00","article:modified_time":"2020-04-15T11:42:19+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"78001","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 17:07:26","updated":"2022-09-27 21:24:29"},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/78001","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=78001"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/78001\/revisions"}],"predecessor-version":[{"id":164511,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/78001\/revisions\/164511"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/78002"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=78001"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=78001"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=78001"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}