{"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":"P\u00ebrvoja n\u00eb zbatimin e network fabrics mbi baz\u00ebn e EVPN VXLAN dhe Cisco ACI, si edhe nj\u00eb krahasim i shkurt\u00ebr","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"P\u00ebrvoja
\nVler\u00ebsoni lidhjet n\u00eb pjes\u00ebn qendrore t\u00eb skem\u00ebs. M\u00eb posht\u00eb do t'u kthehemi atyre.<\/i><\/p>\n

N\u00eb nj\u00eb moment mund t\u00eb p\u00ebrballeni me faktin se rrjetet e m\u00ebdha dhe komplekse t\u00eb nd\u00ebrtuara mbi L2 jan\u00eb t\u00eb d\u00ebmtuara n\u00eb m\u00ebnyr\u00eb t\u00eb pakthyeshme. S\u00eb pari, p\u00ebr shkak t\u00eb problemeve q\u00eb lidhen me p\u00ebrpunimin e trafikut BUM dhe funksionimin e protokollit STP. S\u00eb dyti, p\u00ebr shkak t\u00eb nj\u00eb arkitekture q\u00eb, n\u00eb t\u00ebr\u00ebsi, \u00ebsht\u00eb moralisht e vjet\u00ebruar. Kjo sjell probleme t\u00eb pak\u00ebndshme si nd\u00ebrprerje t\u00eb sh\u00ebrbimit dhe v\u00ebshtir\u00ebsi n\u00eb menaxhim.<\/p>\n

Kishim dy projekte paralele, ku klient\u00ebt vler\u00ebsuan me realiz\u00ebm t\u00eb gjitha avantazhet dhe disavantazhet e opsioneve dhe zgjodh\u00ebn dy zgjidhje t\u00eb ndryshme overlay, nd\u00ebrsa ne i implementuam ato. <\/p>\n

Kishte mund\u00ebsi t\u00eb krahasonim pik\u00ebrisht implementimin. Jo funksionimin n\u00eb prodhim, p\u00ebr t\u00eb cilin ia vlen t\u00eb flitet pas dy ose tre vitesh. <\/p>\n

Pra, \u00e7far\u00eb \u00ebsht\u00eb nj\u00eb fabrik\u00eb rrjeti me rrjete overlay dhe SDN?
\n<\/a><\/noindex><\/p>\n

\u00c7far\u00eb duhet b\u00ebr\u00eb me problemet e kahershme 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 urgjente p\u00ebr t\u00eb rind\u00ebrtuar rrjetet nuk u ndje p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb, sepse shum\u00eb gj\u00ebra mund t\u00eb b\u00ebheshin ende manualisht, me metodat e vjetra t\u00eb provuara. Po \u00e7'r\u00ebnd\u00ebsi ka 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 rrij\u00eb n\u00eb zyr\u00ebn e vet. <\/p>\n

M\u00eb pas filloi bumi i nd\u00ebrtimit t\u00eb qendrave t\u00eb m\u00ebdha t\u00eb t\u00eb dh\u00ebnave. At\u00ebher\u00eb u b\u00eb e qart\u00eb se arkitektura klasike kishte arritur kufijt\u00eb e saj t\u00eb zhvillimit jo vet\u00ebm p\u00ebr sa i p\u00ebrket funksionimit, q\u00ebndrueshm\u00ebris\u00eb ndaj d\u00ebshtimeve dhe shkall\u00ebzueshm\u00ebris\u00eb. Dhe nj\u00eb nga m\u00ebnyrat p\u00ebr t'i zgjidhur k\u00ebto sfida u b\u00eb ideja e nd\u00ebrtimit t\u00eb rrjeteve overlay mbi nj\u00eb backbone t\u00eb routuar.<\/p>\n

P\u00ebrve\u00e7 k\u00ebsaj, me rritjen e shkall\u00ebs s\u00eb rrjeteve, u shfaq me mpreht\u00ebsi problemi i menaxhimit t\u00eb fabrikave t\u00eb tilla, si rezultat i t\u00eb cilit nis\u00ebn t\u00eb shfaqeshin zgjidhje t\u00eb rrjeteve t\u00eb p\u00ebrcaktuara me softuer, me mund\u00ebsin\u00eb p\u00ebr t\u00eb menaxhuar t\u00eb gjith\u00eb infrastruktur\u00ebn e rrjetit si nj\u00eb t\u00ebr\u00ebsi t\u00eb vetme. Dhe kur rrjeti menaxhohet nga nj\u00eb pik\u00eb e vetme, komponent\u00ebt e tjer\u00eb t\u00eb infrastruktur\u00ebs IT e kan\u00eb m\u00eb t\u00eb leht\u00eb t\u00eb nd\u00ebrveprojn\u00eb me t\u00eb, nd\u00ebrsa procese t\u00eb tilla nd\u00ebrveprimi automatizohen m\u00eb leht\u00eb.<\/p>\n

Pothuajse \u00e7do prodhues i madh, jo vet\u00ebm i pajisjeve t\u00eb rrjetit por edhe i virtualizimit, ka n\u00eb portofolin e vet variante t\u00eb tilla zgjidhjesh. <\/p>\n

Mbetet vet\u00ebm t\u00eb kuptohet se \u00e7far\u00eb i p\u00ebrshtatet secil\u00ebs nevoj\u00eb. P\u00ebr shembull, p\u00ebr kompani shum\u00eb t\u00eb m\u00ebdha me nj\u00eb ekip t\u00eb fort\u00eb zhvillimi dhe operimi, zgjidhjet standarde nga vendor\u00ebt jo gjithmon\u00eb i mbulojn\u00eb t\u00eb gjitha k\u00ebrkesat, ndaj ato kalojn\u00eb n\u00eb zhvillimin e zgjidhjeve t\u00eb veta SD (software defined). Kjo ndodh, p\u00ebr shembull, te ofruesit cloud q\u00eb e zgjerojn\u00eb vazhdimisht gam\u00ebn e sh\u00ebrbimeve p\u00ebr klient\u00ebt e tyre, nd\u00ebrsa zgjidhjet standarde thjesht nuk arrijn\u00eb t\u00eb ecin me ritmin e nevojave t\u00eb tyre. <\/p>\n

P\u00ebr kompanit\u00eb e mesme, funksionaliteti q\u00eb ofrohet nga vendori si zgjidhje standarde mjafton n\u00eb 99 p\u00ebr qind t\u00eb rasteve. <\/p>\n

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

\nCila \u00ebsht\u00eb ideja e rrjeteve overlay? N\u00eb thelb, merret nj\u00eb rrjet klasik i rutuesh\u00ebm dhe mbi t\u00eb nd\u00ebrtohet edhe nj\u00eb rrjet tjet\u00ebr p\u00ebr t\u00eb p\u00ebrfituar m\u00eb shum\u00eb funksione. M\u00eb shpesh b\u00ebhet fjal\u00eb p\u00ebr shp\u00ebrndarje m\u00eb efikase t\u00eb ngarkes\u00ebs n\u00eb pajisje dhe linja komunikimi, rritje t\u00eb ndjeshme t\u00eb kufirit t\u00eb shkall\u00ebzueshm\u00ebris\u00eb, rritje t\u00eb besueshm\u00ebris\u00eb dhe shum\u00eb p\u00ebrfitime n\u00eb siguri (fal\u00eb segmentimit). Nd\u00ebrsa zgjidhjet SDN, p\u00ebrve\u00e7 k\u00ebsaj, ofrojn\u00eb administrim shum\u00eb, shum\u00eb, shum\u00eb t\u00eb p\u00ebrshtatsh\u00ebm dhe fleksib\u00ebl, si edhe e b\u00ebjn\u00eb rrjetin m\u00eb transparent p\u00ebr p\u00ebrdoruesit e tij. <\/p>\n

Me pak fjal\u00eb, sikur rrjetet lokale t\u00eb ishin shpikur diku n\u00eb vitet 2010, ato do t\u00eb dukeshin krejt ndryshe nga ajo q\u00eb na ka mbetur trash\u00ebgim nga ushtria e viteve 1970. <\/p>\n

Nga pik\u00ebpamja e teknologjive p\u00ebr nd\u00ebrtimin e fabric me p\u00ebrdorimin e rrjeteve overlay, aktualisht ekzistojn\u00eb shum\u00eb implementime nga prodhues t\u00eb ndrysh\u00ebm dhe projekte interneti RFC (EVPN+VXLAN, EVPN+MPLS, EVPN+MPLSoGRE, EVPN+Geneve dhe t\u00eb tjera). Po, ka standarde, por zbatimi i k\u00ebtyre standardeve nga prodhues t\u00eb ndrysh\u00ebm mund t\u00eb ndryshoj\u00eb, prandaj gjat\u00eb nd\u00ebrtimit t\u00eb k\u00ebtyre fabric-ve, heqja dor\u00eb plot\u00ebsisht nga vendor lock-in p\u00ebr momentin mbetet e mundur vet\u00ebm teorikisht, n\u00eb let\u00ebr.<\/p>\n

Me zgjidhjet SD, situata \u00ebsht\u00eb edhe m\u00eb e nd\u00ebrlikuar, sepse \u00e7do vendor ka vizionin e vet. Ka zgjidhje plot\u00ebsisht t\u00eb hapura, q\u00eb teorikisht mund t\u2019i p\u00ebrshtatni dhe zhvilloni vet\u00eb, si dhe ka zgjidhje plot\u00ebsisht t\u00eb mbyllura.<\/p>\n

Cisco ofron variantin e vet t\u00eb SDN p\u00ebr qendrat e t\u00eb dh\u00ebnave \u2014 ACI. Natyrisht, nga k\u00ebndv\u00ebshtrimi i zgjedhjes s\u00eb pajisjeve t\u00eb rrjetit, kjo \u00ebsht\u00eb nj\u00eb zgjidhje 100% e mbyllur nga nj\u00eb prodhues i vet\u00ebm, por nj\u00ebkoh\u00ebsisht integrohet plot\u00ebsisht me sistemet e virtualizimit, containerizimit, siguris\u00eb, orkestrimit, balancuesit e ngarkes\u00ebs etj. Megjithat\u00eb, n\u00eb thelb mbetet nj\u00eb lloj black box, pa mund\u00ebsi p\u00ebr qasje t\u00eb plot\u00eb n\u00eb t\u00eb gjitha proceset e brendshme. Jo t\u00eb gjith\u00eb klient\u00ebt pajtohen me k\u00ebt\u00eb qasje, sepse b\u00ebhesh plot\u00ebsisht i varur nga cil\u00ebsia e kodit t\u00eb zgjidhjes dhe m\u00ebnyra si \u00ebsht\u00eb zbatuar, por nga ana tjet\u00ebr prodhuesi ka nj\u00eb nga ekipet m\u00eb t\u00eb mira t\u00eb mb\u00ebshtetjes teknike n\u00eb bot\u00eb dhe 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 nj\u00eb zgjidhje nga Juniper. Edhe ky prodhues ka SDN-n\u00eb e vet p\u00ebr qendrat e t\u00eb dh\u00ebnave, por klienti vendosi t\u00eb heq\u00eb dor\u00eb nga implementimi i SDN. Si teknologji p\u00ebr nd\u00ebrtimin e rrjetit u zgjodh EVPN VXLAN fabric pa p\u00ebrdorimin e kontrollor\u00ebve t\u00eb centralizuar.<\/p>\n

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

\nKrijimi i nj\u00eb fabric b\u00ebn t\u00eb mundur nd\u00ebrtimin e nj\u00eb rrjeti leht\u00ebsisht t\u00eb shkall\u00ebzuesh\u00ebm, rezistent ndaj d\u00ebshtimeve dhe t\u00eb besuesh\u00ebm. Arkitektura (leaf-spine) merr parasysh ve\u00e7orit\u00eb qendrat e t\u00eb dh\u00ebnave<\/a> (rrug\u00ebt e kalimit t\u00eb trafikut, minimizimin e vonesave dhe t\u00eb pikave t\u00eb ngushta n\u00eb rrjet). Nd\u00ebrsa zgjidhjet SD n\u00eb qendrat e t\u00eb dh\u00ebnave lejojn\u00eb administrim shum\u00eb t\u00eb p\u00ebrshtatsh\u00ebm, t\u00eb shpejt\u00eb dhe fleksib\u00ebl t\u00eb nj\u00eb fabric t\u00eb till\u00eb, si dhe integrimin e saj n\u00eb ekosistemin e qendr\u00ebs s\u00eb t\u00eb dh\u00ebnave. <\/p>\n

T\u00eb dy klient\u00ebt kishin nevoj\u00eb t\u00eb nd\u00ebrtonin qendra rezerv\u00eb t\u00eb t\u00eb dh\u00ebnave p\u00ebr t\u00eb siguruar rezistenc\u00eb ndaj d\u00ebshtimeve; p\u00ebrve\u00e7 k\u00ebsaj, trafiku midis qendrave t\u00eb t\u00eb dh\u00ebnave duhej t\u00eb enkriptohej.<\/p>\n

Klienti i par\u00eb kishte shqyrtuar tashm\u00eb zgjidhje pa fabric si standard t\u00eb mundsh\u00ebm p\u00ebr rrjetet e veta, por gjat\u00eb testeve pati probleme me p\u00ebrputhshm\u00ebrin\u00eb e STP midis pajisjeve t\u00eb disa prodhuesve. Kjo shkaktonte nd\u00ebrprerje q\u00eb sillnin r\u00ebnien e sh\u00ebrbimeve. Dhe p\u00ebr klientin kjo ishte kritike. <\/p>\n

Cisco ishte tashm\u00eb standardi korporativ i klientit. Ata shqyrtuan ACI dhe opsione t\u00eb tjera dhe vendos\u00ebn se pik\u00ebrisht kjo zgjidhje ia vlente. U p\u00eblqeu automatizimi i menaxhimit me nj\u00eb klikim p\u00ebrmes nj\u00eb kontrolluesi t\u00eb unifikuar. Sh\u00ebrbimet konfigurohen m\u00eb shpejt dhe menaxhohen m\u00eb shpejt. Enkriptimin e trafikut vendos\u00ebn ta siguronin duke aktivizuar MACSec midis komutator\u00ebve IPN dhe SPINE. N\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb arrit\u00ebn t\u00eb shmangnin ngushtic\u00ebn n\u00eb form\u00ebn e nj\u00eb crypto gateway, t\u00eb kursenin n\u00eb to dhe t\u00eb shfryt\u00ebzonin maksimalisht gjer\u00ebsin\u00eb e brezit.<\/p>\n

Klienti i dyt\u00eb zgjodhi nj\u00eb zgjidhje pa kontrollues nga Juniper, sepse n\u00eb qendr\u00ebn e tyre ekzistuese t\u00eb t\u00eb dh\u00ebnave kishte tashm\u00eb nj\u00eb instalim t\u00eb vog\u00ebl me implementim t\u00eb fabric\u00ebs EVPN VXLAN. Por aty ajo nuk ishte fault-tolerant (p\u00ebrdorej nj\u00eb komutator i vet\u00ebm). U mor vendimi t\u00eb zgjerohej infrastruktura e qendr\u00ebs kryesore t\u00eb t\u00eb dh\u00ebnave dhe t\u00eb nd\u00ebrtohej nj\u00eb fabric\u00eb edhe n\u00eb qendr\u00ebn rezerv\u00eb t\u00eb t\u00eb dh\u00ebnave. EVPN ekzistues nuk p\u00ebrdorej plot\u00ebsisht: encapsulation VXLAN n\u00eb praktik\u00eb nuk aplikohej, pasi t\u00eb gjith\u00eb host-et ishin t\u00eb lidhur me nj\u00eb komutator t\u00eb vet\u00ebm dhe t\u00eb gjitha adresat MAC dhe adresat \/32 t\u00eb host-eve ishin lokale; gateway p\u00ebr to ishte po ai komutator dhe nuk kishte pajisje t\u00eb tjera drejt t\u00eb cilave duhej t\u00eb nd\u00ebrtoheshin tunelet VXLAN. Enkriptimin e trafikut vendos\u00ebn ta siguronin duke p\u00ebrdorur teknologjin\u00eb IPSEC midis firewall-eve (performanca e firewall-eve ishte e mjaftueshme).<\/p>\n

Edhe ACI e testuan, por vendos\u00ebn se p\u00ebr shkak t\u00eb vendor lock-in do t'u duhej t\u00eb blinin tep\u00ebr shum\u00eb pajisje, p\u00ebrfshir\u00eb z\u00ebvend\u00ebsimin e pajisjeve t\u00eb reja t\u00eb blera s\u00eb fundmi, dhe kjo thjesht nuk kishte kuptim ekonomik. Po, fabrica e Cisco integrohet me gjith\u00e7ka, por brenda vet\u00eb fabric\u00ebs mund t\u00eb p\u00ebrdoren vet\u00ebm pajisjet e saj. <\/p>\n

Nga ana tjet\u00ebr, si\u00e7 u p\u00ebrmend m\u00eb her\u00ebt, nj\u00eb fabric\u00eb EVPN VXLAN nuk mund t\u00eb p\u00ebrzihet leht\u00ebsisht me \u00e7do vendor fqinj, sepse implementimet e protokollit ndryshojn\u00eb. \u00cbsht\u00eb si t\u00eb bashkosh Cisco dhe Huawei n\u00eb t\u00eb nj\u00ebjtin rrjet: n\u00eb dukje standardet jan\u00eb t\u00eb p\u00ebrbashk\u00ebta, por n\u00eb praktik\u00eb do t\u00eb duhet shum\u00eb pun\u00eb shtes\u00eb. Meqen\u00ebse b\u00ebhej fjal\u00eb p\u00ebr nj\u00eb bank\u00eb dhe testet e p\u00ebrputhshm\u00ebris\u00eb do t\u00eb zgjatnin shum\u00eb, u vendos q\u00eb p\u00ebr momentin t\u00eb blihej pajisje nga i nj\u00ebjti vendor dhe t\u00eb mos ndiqeshin shum\u00eb funksionalitete p\u00ebrtej bazikes. <\/p>\n

Plani i migrimit<\/h3>\n

\nDy qendra t\u00eb t\u00eb dh\u00ebnave t\u00eb bazuara n\u00eb ACI:<\/p>\n

\"P\u00ebrvoja
\n
\nOrganizimi i nd\u00ebrveprimit midis qendrave t\u00eb t\u00eb dh\u00ebnave. U zgjodh zgjidhja Multi-Pod \u2014 \u00e7do qend\u00ebr e t\u00eb dh\u00ebnave \u00ebsht\u00eb nj\u00eb pod. U mor\u00ebn parasysh k\u00ebrkesat p\u00ebr shkall\u00ebzim sipas numrit t\u00eb switch-eve dhe p\u00ebr vonesat midis pod-eve (RTT m\u00eb pak se 50 ms). U vendos t\u00eb mos nd\u00ebrtohej nj\u00eb zgjidhje Multi-Site p\u00ebr leht\u00ebsi menaxhimi (p\u00ebr zgjidhjen Multi-Pod p\u00ebrdoret nj\u00eb nd\u00ebrfaqe e vetme menaxhimi, nd\u00ebrsa p\u00ebr Multi-Site do t\u00eb kishte dy nd\u00ebrfaqe ose do t\u00eb k\u00ebrkohej Multi-Site Orchestrator), si edhe sepse nuk k\u00ebrkohej rezervim gjeografik i lokacioneve.<\/p>\n

\"P\u00ebrvoja
\n
\nNga k\u00ebndv\u00ebshtrimi i migrimit t\u00eb sh\u00ebrbimeve nga rrjeti Legacy, u zgjodh opsioni m\u00eb transparent: transferimi gradual i VLAN-ve q\u00eb p\u00ebrputhen me sh\u00ebrbime t\u00eb caktuara.
\nP\u00ebr migrim, p\u00ebr secilin VLAN krijohej EPG-ja p\u00ebrkat\u00ebse (End-point-group) n\u00eb fabric. Fillimisht rrjeti shtrihej midis rrjetit t\u00eb vjet\u00ebr dhe fabric p\u00ebrmes L2, m\u00eb pas, pasi migroheshin t\u00eb gjith\u00eb host\u00ebt, gateway kalonte n\u00eb fabric dhe nd\u00ebrveprimi i EPG me rrjetin ekzistues realizohej p\u00ebrmes L3OUT; nd\u00ebrkoh\u00eb, nd\u00ebrveprimi midis L3OUT dhe EPG p\u00ebrshkruhej duke p\u00ebrdorur kontrata. Skema e p\u00ebraf\u00ebrt:<\/p>\n

\"P\u00ebrvoja
\n
\nStruktura e p\u00ebraf\u00ebrt e shumic\u00ebs s\u00eb politikave t\u00eb fabric ACI paraqitet n\u00eb figur\u00ebn m\u00eb posht\u00eb. I gjith\u00eb konfigurimi nd\u00ebrtohet mbi politika t\u00eb p\u00ebrfshira n\u00eb politika t\u00eb tjera, dhe k\u00ebshtu me radh\u00eb. N\u00eb fillim \u00ebsht\u00eb mjaft e v\u00ebshtir\u00eb t\u00eb kuptohet, por me kalimin e koh\u00ebs, si\u00e7 tregon praktika, administrator\u00ebt e rrjetit m\u00ebsohen me k\u00ebt\u00eb struktur\u00eb brenda rreth nj\u00eb muaji dhe vet\u00ebm at\u00ebher\u00eb e kuptojn\u00eb sa e p\u00ebrshtatshme \u00ebsht\u00eb ajo.<\/p>\n

\"P\u00ebrvoja
\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\u00e7anta p\u00ebr nd\u00ebrveprimin Inter-Pod dhe kontrollor\u00eb APIC), prandaj ajo doli m\u00eb e kushtueshme. Zgjidhja Juniper nuk k\u00ebrkoi blerjen e kontrollor\u00ebve dhe pajisjeve ndihm\u00ebse; ishte e mundur t\u00eb p\u00ebrdorej pjes\u00ebrisht edhe pajisja ekzistuese e klientit. <\/p>\n

Ja arkitektura e fabric EVPN VXLAN p\u00ebr dy qendra t\u00eb t\u00eb dh\u00ebnave t\u00eb projektit t\u00eb dyt\u00eb:<\/p>\n

\"P\u00ebrvoja
\n\"P\u00ebrvoja
\n
\nMe ACI merr nj\u00eb zgjidhje t\u00eb gatshme: nuk ka nevoj\u00eb t\u00eb g\u00ebrmosh n\u00eb konfigurime dhe as t\u00eb optimizosh gjith\u00e7ka vet\u00eb. N\u00eb faz\u00ebn e par\u00eb t\u00eb njohjes s\u00eb klientit me fabric-un, nuk duhen zhvillues dhe as specialist\u00eb p\u00ebr mb\u00ebshtetjen e kodit apo automatizimit. Mjafton ekipi i operimit; shum\u00eb konfigurime mund t\u00eb b\u00ebhen edhe p\u00ebrmes wizard-it, gj\u00eb q\u00eb nuk \u00ebsht\u00eb gjithmon\u00eb avantazh, sidomos p\u00ebr ata q\u00eb jan\u00eb m\u00ebsuar me komand\u00ebn nga console. Sidoqoft\u00eb, duhet koh\u00eb p\u00ebr t\u2019iu p\u00ebrshtatur qasjes s\u00eb re, ve\u00e7an\u00ebrisht logjik\u00ebs s\u00eb konfigurimit p\u00ebrmes politikave dhe menaxhimit t\u00eb shum\u00eb politikave t\u00eb nd\u00ebrlidhura mes tyre. P\u00ebrve\u00e7 k\u00ebsaj, \u00ebsht\u00eb shum\u00eb e k\u00ebshillueshme t\u00eb keni nj\u00eb struktur\u00eb t\u00eb qart\u00eb p\u00ebr em\u00ebrtimin e politikave dhe objekteve. N\u00ebse shfaqet ndonj\u00eb problem n\u00eb logjik\u00ebn e funksionimit t\u00eb controller-it, zgjidhja mund t\u00eb b\u00ebhet vet\u00ebm p\u00ebrmes mb\u00ebshtetjes teknike.<\/p>\n

N\u00eb EVPN gjith\u00e7ka b\u00ebhet nga console. Vuaj ose k\u00ebnaqu. \u00cbsht\u00eb nj\u00eb nd\u00ebrfaqe e njohur p\u00ebr gard\u00ebn e vjet\u00ebr. Po, ka konfigurime standarde dhe udh\u00ebzues. Do t\u00eb duhet t\u00eb studiosh dokumentacionin. Ka nd\u00ebrtim t\u00eb ndrysh\u00ebm t\u00eb konfigurimeve, por gjith\u00e7ka \u00ebsht\u00eb e qart\u00eb dhe e detajuar.<\/p>\n

Natyrisht, n\u00eb t\u00eb dyja rastet, gjat\u00eb migrimit \u00ebsht\u00eb m\u00eb mir\u00eb q\u00eb fillimisht t\u00eb kalohen sh\u00ebrbimet m\u00eb pak kritike, p\u00ebr shembull mjediset testuese, dhe vet\u00ebm pasi t\u00eb zbulohen e t\u00eb korrigjohen t\u00eb gjitha problemet t\u00eb kalohet te production. Dhe jo t\u00eb premten n\u00eb mbr\u00ebmje. Nuk duhet t\u2019i besosh verb\u00ebrisht vendor-it kur thot\u00eb se gjith\u00e7ka do t\u00eb shkoj\u00eb mir\u00eb; \u00ebsht\u00eb gjithmon\u00eb m\u00eb mir\u00eb t\u00eb kesh nj\u00eb plan rezerv\u00eb.<\/p>\n

Me ACI paguan m\u00eb shum\u00eb, megjith\u00ebse aktualisht Cisco e promovon n\u00eb m\u00ebnyr\u00eb aktive k\u00ebt\u00eb zgjidhje dhe shpesh ofron zbritje t\u00eb mira p\u00ebr t\u00eb, por kursen n\u00eb mir\u00ebmbajtje dhe support. Menaxhimi dhe \u00e7do lloj automatizimi i nj\u00eb EVPN fabric pa controller k\u00ebrkon investime dhe kosto t\u00eb vazhdueshme: monitorim, automatizim, implementim t\u00eb sh\u00ebrbimeve t\u00eb reja. Nga ana tjet\u00ebr, nisja fillestare me ACI zakonisht zgjat 30\u201340 p\u00ebr qind m\u00eb shum\u00eb. Kjo ndodh sepse k\u00ebrkon m\u00eb shum\u00eb koh\u00eb krijimi i t\u00eb gjith\u00eb grupit t\u00eb profileve dhe politikave t\u00eb nevojshme, t\u00eb cilat m\u00eb pas do t\u00eb p\u00ebrdoren vazhdimisht. Por me rritjen e rrjetit, numri i konfigurimeve t\u00eb reja q\u00eb duhen zvog\u00eblohet. P\u00ebrdor politika, profile dhe objekte t\u00eb krijuara paraprakisht. Mund t\u00eb konfigurosh n\u00eb m\u00ebnyr\u00eb fleksibile segmentimin dhe sigurin\u00eb, si edhe t\u00eb menaxhosh n\u00eb m\u00ebnyr\u00eb t\u00eb centralizuar kontratat q\u00eb p\u00ebrcaktojn\u00eb se cilat nd\u00ebrveprime lejohen mes EPG-ve \u2014 dhe volumi i pun\u00ebs bie ndjesh\u00ebm. <\/p>\n

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

N\u00ebse ACI po implementohet m\u00eb ngadal\u00eb, EVPN k\u00ebrkoi pothuajse dy her\u00eb m\u00eb shum\u00eb koh\u00eb p\u00ebr t\u2019u rregulluar dhe optimizuar. Me Cisco gjithmon\u00eb mund t\u00eb th\u00ebrrisni nj\u00eb inxhinier t\u00eb support-it dhe t\u00eb pyesni p\u00ebr rrjetin n\u00eb t\u00ebr\u00ebsi, sepse mbulohet si zgjidhje e plot\u00eb. Nd\u00ebrsa te Juniper Networks blini vet\u00ebm pajisjen, dhe mbulimi vlen pik\u00ebrisht p\u00ebr t\u00eb. Paketat dol\u00ebn nga pajisja? Mir\u00eb, q\u00eb aty e tutje jan\u00eb problemet tuaja. Megjithat\u00eb, mund t\u00eb hapni nj\u00eb k\u00ebrkes\u00eb p\u00ebr zgjedhjen e zgjidhjes ose dizajnin e rrjetit \u2014 dhe at\u00ebher\u00eb do t\u2019ju rekomandojn\u00eb t\u00eb blini professional services, me pages\u00eb shtes\u00eb.<\/p>\n

Support-i i ACI \u00ebsht\u00eb shum\u00eb i fort\u00eb, sepse \u00ebsht\u00eb i dedikuar: nj\u00eb ekip i ve\u00e7ant\u00eb merret vet\u00ebm me k\u00ebt\u00eb. Ka edhe specialist\u00eb rusishtfol\u00ebs. Dokumentacioni \u00ebsht\u00eb i detajuar, zgjidhjet jan\u00eb t\u00eb parap\u00ebrcaktuara. E shqyrtojn\u00eb situat\u00ebn dhe japin rekomandime. E validojn\u00eb shpejt dizajnin, gj\u00eb q\u00eb shpesh \u00ebsht\u00eb shum\u00eb e r\u00ebnd\u00ebsishme. Juniper Networks b\u00ebn t\u00eb nj\u00ebjt\u00ebn gj\u00eb, por shum\u00eb her\u00eb m\u00eb ngadal\u00eb (t\u00eb pakt\u00ebn k\u00ebshtu ishte n\u00eb rastin ton\u00eb; sipas asaj q\u00eb d\u00ebgjohet, tani duhet t\u00eb jet\u00eb m\u00eb mir\u00eb), gj\u00eb q\u00eb ju detyron t\u2019i b\u00ebni vet\u00eb ato pun\u00eb ku nj\u00eb solution engineer mund t\u2019ju kishte orientuar. <\/p>\n

Cisco ACI mb\u00ebshtet integrimin me sistemet e virtualizimit dhe kontejnerizimit (VMware, Kubernetes, Hyper-V), si edhe menaxhim t\u00eb centralizuar. Ka integrim edhe me sh\u00ebrbimet e rrjetit dhe t\u00eb siguris\u00eb \u2014 load balancing, firewall, WAF, IPS dhe t\u00eb tjera. Ofron mikrosegmentim t\u00eb mir\u00eb q\u00eb n\u00eb standard. Te zgjidhja e dyt\u00eb, integrimi me sh\u00ebrbimet e rrjetit k\u00ebrkon shum\u00eb m\u00eb tep\u00ebr p\u00ebrpjekje, ndaj \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb lexoni paraprakisht forumet e atyre q\u00eb e kan\u00eb b\u00ebr\u00eb tashm\u00eb k\u00ebt\u00eb. <\/p>\n

P\u00ebrfundimi<\/h3>\n

\nP\u00ebr \u00e7do rast konkret, zgjidhja duhet t\u00eb p\u00ebrzgjidhet jo vet\u00ebm mbi baz\u00ebn e kostos s\u00eb pajisjeve, por duke marr\u00eb parasysh edhe shpenzimet e m\u00ebtejshme t\u00eb operimit, problemet kryesore me t\u00eb cilat p\u00ebrballet klienti aktualisht, si dhe planet p\u00ebr zhvillimin e m\u00ebtejsh\u00ebm t\u00eb infrastruktur\u00ebs IT. <\/p>\n

ACI doli m\u00eb i kushtuesh\u00ebm p\u00ebr shkak t\u00eb pajisjeve shtes\u00eb, por \u00ebsht\u00eb nj\u00eb zgjidhje e gatshme pa nevoj\u00eb p\u00ebr p\u00ebrshtatje t\u00eb m\u00ebtejshme. Zgjidhja e dyt\u00eb \u00ebsht\u00eb m\u00eb komplekse dhe m\u00eb e kushtueshme nga pik\u00ebpamja e operimit, por m\u00eb e lir\u00eb. <\/p>\n

N\u00ebse d\u00ebshironi t\u00eb diskutoni sa mund t\u00eb kushtoj\u00eb implementimi i nj\u00eb fabric rrjeti me vendor\u00eb t\u00eb ndrysh\u00ebm dhe \u00e7far\u00eb arkitekture nevojitet, mund t\u00eb takohemi dhe t\u00eb bisedojm\u00eb. Deri te nj\u00eb skic\u00eb paraprake e arkitektur\u00ebs (me t\u00eb cil\u00ebn mund t\u00eb llogariten buxhetet) do t\u2019ju k\u00ebshillojm\u00eb pa pages\u00eb; p\u00ebrpunimi i detajuar, natyrisht, \u00ebsht\u00eb tashm\u00eb me pages\u00eb.<\/p>\n

Vladimir Klep\u00e7e, rrjete 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\udd47P\u00ebrvoj\u00eb n\u00eb zbatimin e fabricave t\u00eb rrjetit me EVPN VXLAN dhe Cisco ACI, si dhe nj\u00eb krahasim i shkurt\u00ebr | ProHoster","description":"Vler\u00ebsojeni.","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.","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","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\/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}]}}