{"id":35291,"date":"2019-10-31T22:03:28","date_gmt":"2019-10-31T19:03:28","guid":{"rendered":"https:\/\/prohoster.info\/blog\/setevaya-fabrika-dlya-tsoda-cisco-aci-v-pomoshh-adminu\/"},"modified":"2019-10-31T22:03:28","modified_gmt":"2019-10-31T19:03:28","slug":"setevaya-fabrika-dlya-tsoda-cisco-aci-v-pomoshh-adminu","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/setevaya-fabrika-dlya-tsoda-cisco-aci-v-pomoshh-adminu","title":{"rendered":"Fabrika e rrjetit p\u00ebr Qendrat e t\u00eb Dh\u00ebnave Cisco ACI \u2014 n\u00eb ndihm\u00eb t\u00eb administrator\u00ebve","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Fabrika
\nMe ndihm\u00ebn e k\u00ebtij skripti magical Cisco ACI, mund t\u00eb konfigurohet shpejt rrjeti.<\/i><\/p>\n

Fabrika e rrjetit p\u00ebr qendrat e t\u00eb dh\u00ebnave Cisco ACI ekziston prej pes\u00eb vjet\u00ebsh, por n\u00eb Habra nuk \u00ebsht\u00eb folur asgj\u00eb p\u00ebr t\u00eb, k\u00ebshtu q\u00eb vendosa ta rregullojn\u00eb pak. Do t\u00eb flas nga p\u00ebrvoja ime, se \u00e7far\u00eb \u00ebsht\u00eb, \u00e7far\u00eb p\u00ebrfitimi ka dhe ku ka pengesa. <\/p>\n

\u00c7far\u00eb \u00ebsht\u00eb dhe nga erdhi?<\/h3>\n

\nN\u00eb momentin e shpalljes s\u00eb ACI (Infrastructure e Fokusuar n\u00eb Aplikacione) n\u00eb vitin 2013, p\u00ebr qendrat e t\u00eb dh\u00ebnave washin duke u sulmuar nga tre an\u00eb. <\/p>\n

Nga nj\u00ebra an\u00eb, zgjidhjet SDN \"t\u00eb gjenerat\u00ebs s\u00eb par\u00eb\" bazuar n\u00eb OpenFlow premtuan t\u00eb b\u00ebnin rrjetet m\u00eb fleksibile dhe m\u00eb t\u00eb lira n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb. Ideja ishte q\u00eb t\u00eb kalonte marrjen e vendimeve, q\u00eb tradicionalisht ishte realizuar nga softi pronar i switch-ave, n\u00eb nj\u00eb kontrollues qendror. <\/p>\n

Ky kontrollues do t\u00eb kishte nj\u00eb pamje t\u00eb vetme p\u00ebr t\u00eb gjith\u00eb at\u00eb q\u00eb ndodhte dhe, duke u bazuar n\u00eb k\u00ebt\u00eb, do t\u00eb programonte pajisjet e t\u00eb gjith\u00eb switch-ave n\u00eb nivelin e rregullave t\u00eb p\u00ebrpunimit t\u00eb flukseve specifike. <\/a><\/noindex>
\nNga ana tjet\u00ebr, zgjidhjet rrjet\u00eboresh ofronin mund\u00ebsin\u00eb p\u00ebr t\u00eb realizuar lidhshm\u00ebri dhe politika t\u00eb siguris\u00eb pa ndonj\u00eb ndryshim n\u00eb rrjetin fizik, duke nd\u00ebrtuar tunel\u00eb programor\u00eb mes hosteve t\u00eb virtualizuara. Nj\u00eb nga shembujt m\u00eb t\u00eb njohur t\u00eb k\u00ebtij qasjeje ishte zgjidhja nga Nicira, e cila n\u00eb at\u00eb koh\u00eb ishte bler\u00eb nga VMWare p\u00ebr 1.26 miliard dollar\u00eb dhe hodhi themelet e VMWare NSX t\u00eb tanish\u00ebm. Nj\u00eb nuanc\u00eb e situat\u00ebs ishte se bashk\u00ebthemeluesit e Nicira ishin ata t\u00eb nj\u00ebjt\u00ebt q\u00eb m\u00eb par\u00eb ishin t\u00eb angazhuar n\u00eb krijimin e OpenFlow, tani thoshin se p\u00ebr nd\u00ebrtimin e fabrik\u00ebs s\u00eb Qendr\u00ebs s\u00eb t\u00eb Dh\u00ebnave, OpenFlow nuk \u00ebsht\u00eb i p\u00ebrshtatsh\u00ebm.<\/a><\/noindex>.<\/p>\n

M\u00eb n\u00eb fund, \u00e7ipat e switch-eve, t\u00eb disponuesh\u00ebm n\u00eb tregun e hapur (ajo q\u00eb quhet merchant silicon), arrit\u00ebn nj\u00eb nivel t\u00eb pjekuris\u00eb, p\u00ebr t\u00eb cilin ata u b\u00ebn\u00eb nj\u00eb k\u00ebrc\u00ebnim real p\u00ebr prodhuesit tradicional\u00eb t\u00eb switch-eve. N\u00ebse m\u00eb par\u00eb secili prodhues zhvillonte vet\u00eb \u00e7ipat p\u00ebr switch-at e tij, me kalimin e koh\u00ebs \u00e7ipat nga prodhues t\u00eb tret\u00eb, kryesisht nga Broadcom, filluan t\u00eb reduktonin distanc\u00ebn me \u00e7ipat e prodhuesve p\u00ebr funksionalitetet, nd\u00ebrsa n\u00eb raportin \u00e7mim\/p\u00ebrformanc\u00eb i kalonin ato. Prandaj, shum\u00eb mendonin se dit\u00ebt e switch-eve me \u00e7ipa t\u00eb zhvilluar vet\u00eb ishin num\u00ebruar.<\/p>\n

ACI u b\u00eb \"p\u00ebrgjigjja asimetrike\" e Cisco (n\u00eb fakt, e kompanis\u00eb Insieme, e cila ishte themeluar nga ish-punonj\u00ebsit e saj) ndaj gjith\u00eb asaj q\u00eb \u00ebsht\u00eb p\u00ebrmendur. <\/p>\n

Cila \u00ebsht\u00eb dallimi me OpenFlow?<\/h3>\n

\nNga pik\u00ebpamja e ndarjes s\u00eb funksioneve, ACI \u00ebsht\u00eb n\u00eb fakt e kund\u00ebrta e OpenFlow.
\nN\u00eb arkitektur\u00ebn OpenFlow, kontroluesi \u00ebsht\u00eb p\u00ebrgjegj\u00ebs p\u00ebr shkruan rregullat e detajuara (rrjedhat) n\u00eb pajisjet e t\u00eb gjitha switcheve, pra n\u00eb nj\u00eb rrjet t\u00eb madh, ai mund t\u00eb ket\u00eb p\u00ebrgjegj\u00ebsin\u00eb p\u00ebr t\u00eb mbajtur dhe, m\u00eb e r\u00ebnd\u00ebsishmja, p\u00ebr t\u00eb ndryshuar dhjet\u00ebra milion\u00eb regjistrime n\u00eb qindra pika n\u00eb rrjet, k\u00ebshtu q\u00eb performanca dhe q\u00ebndrueshm\u00ebria e tij n\u00eb nj\u00eb zbatim t\u00eb madh b\u00ebhen nj\u00eb ngushtic\u00eb.
\nN\u00eb ACI p\u00ebrdoret nj\u00eb qasje e kund\u00ebrt: ka gjithashtu nj\u00eb kontrolues, por switchet e marrin prej tij politika deklaruese m\u00eb t\u00eb nivelit t\u00eb lart\u00eb, dhe renderimi n\u00eb detaje t\u00eb konfigurimeve specifike n\u00eb pajisje kryhet nga vet\u00eb switchi. Kontroluesi mund t\u00eb ri-ngarkohet ose madje t\u00eb fikohet, dhe asgj\u00eb e keqe nuk do t'i ndodh\u00eb rrjetit, p\u00ebrve\u00e7, natyrisht, munges\u00ebs n\u00eb at\u00eb moment t\u00eb mund\u00ebsis\u00eb s\u00eb menaxhimit. \u00cbsht\u00eb interesante q\u00eb n\u00eb ACI ka situata ku OpenFlow p\u00ebrdoret ndonj\u00ebher\u00eb, por lokalisht brenda hostit p\u00ebr programimin e Open vSwitch.<\/p>\n

ACI \u00ebsht\u00eb nd\u00ebrtuar plot\u00ebsisht mbi transportin overlay t\u00eb bazuar n\u00eb VXLAN, por gjithashtu p\u00ebrfshin transportin IP t\u00eb posht\u00ebm brenda nj\u00eb zgjidhjeje t\u00eb vetme. Cisco e quajti k\u00ebt\u00eb termin \u00aboverlay i integruar\u00bb. Si nj\u00eb pik\u00eb terminimi p\u00ebr overlay-t n\u00eb ACI, n\u00eb shumic\u00ebn e rasteve p\u00ebrdoren switche t\u00eb fabrik\u00ebs (t\u00eb cilat e b\u00ebjn\u00eb k\u00ebt\u00eb me shpejt\u00ebsin\u00eb e kanalit). Hostet nuk kan\u00eb nevoj\u00eb t\u00eb din\u00eb gj\u00eb p\u00ebr fabrik\u00ebn, inkapsulimet etj., megjithat\u00eb, n\u00eb disa raste (p\u00ebr shembull, p\u00ebr lidhjen e hosteve OpenStack) trafik VXLAN mund t\u00eb d\u00ebrgohet edhe atyre.<\/p>\n

Overlay-t p\u00ebrdoren n\u00eb ACI jo vet\u00ebm p\u00ebr t\u00eb siguruar lidhje elastike p\u00ebrmes rrjetit t\u00eb transportit, por gjithashtu p\u00ebr transmetimin e metainformacionit (ai p\u00ebrdoret, p\u00ebr shembull, p\u00ebr t\u00eb aplikuar politikat e siguris\u00eb).<\/p>\n

Overlay-t p\u00ebrdoren n\u00eb ACI jo vet\u00ebm p\u00ebr t\u00eb siguruar lidhshm\u00ebrin\u00eb fleksib\u00ebl p\u00ebrmes rrjetit t\u00eb transportit, por edhe p\u00ebr t\u00eb kaluar meta-informacione (ato p\u00ebrdoren, p\u00ebr shembull, p\u00ebr t\u00eb aplikuar politikat e siguris\u00eb). <\/p>\n

\u00c7ipat e Broadcom jan\u00eb p\u00ebrdorur m\u00eb par\u00eb nga Cisco n\u00eb switch-at e seris\u00eb Nexus 3000. N\u00eb familjen Nexus 9000, e cila \u00ebsht\u00eb nxjerr\u00eb posa\u00e7\u00ebrisht p\u00ebr t\u00eb mb\u00ebshtetur ACI, fillimisht u implementua nj\u00eb model hibrid i quajtur Merchant+. N\u00eb switch-in, ishin p\u00ebrdorur nj\u00ebkoh\u00ebsisht \u00e7ipi i ri Broadcom Trident 2 dhe nj\u00eb \u00e7ip shtes\u00eb i zhvilluar nga Cisco, i cili realizonte gjith\u00eb magjin\u00eb e ACI. Duket se kjo ka lejuar t\u00eb p\u00ebrshpejtohet dalja n\u00eb treg e produktit dhe t\u00eb ulet \u00e7mimi i switch-it n\u00eb nj\u00eb nivel af\u00ebr modele t\u00eb thjeshta me Trident 2. Ky qasje ishte e mjaftueshme p\u00ebr dy-tre vitet e para t\u00eb shp\u00ebrndarjeve t\u00eb ACI. Gjat\u00eb k\u00ebsaj kohe, Cisco zhvilloi dhe nxori n\u00eb treg gjenerat\u00ebn e ardhshme t\u00eb Nexus 9000 e cila p\u00ebrdorte \u00e7ipat e saj me performanc\u00eb m\u00eb t\u00eb lart\u00eb dhe nj\u00eb set funksionesh, por n\u00eb t\u00eb nj\u00ebjtin nivel \u00e7mimi. Specifikimet e jashtme p\u00ebrsa i p\u00ebrket nd\u00ebrveprimit n\u00eb fabrik\u00eb kan\u00eb mbetur krejt\u00ebsisht t\u00eb pandryshuara. N\u00eb k\u00ebt\u00eb kuptim, brend\u00ebsia \u00ebsht\u00eb ndryshuar krejt\u00ebsisht: di\u00e7ka si nj\u00eb refaktorizim, por p\u00ebr harduerin.<\/p>\n

Si \u00ebsht\u00eb nd\u00ebrtuar arkitektura Cisco ACI <\/h3>\n

\nN\u00eb rastin m\u00eb t\u00eb thjesht\u00eb, ACI nd\u00ebrtohet sipas topologjis\u00eb s\u00eb rrjetit Clos, ose, si\u00e7 quhet shpesh, Spine-Leaf. Numri i switch-ave t\u00eb nivelit Spine mund t\u00eb varioj\u00eb nga dy (ose nj\u00eb, n\u00ebse nuk na intereson q\u00ebndrueshm\u00ebria) deri n\u00eb gjasht\u00eb. Prandaj, sa m\u00eb shum\u00eb t\u00eb jen\u00eb, aq m\u00eb e lart\u00eb \u00ebsht\u00eb q\u00ebndrueshm\u00ebria (m\u00eb pak humbje t\u00eb kapacitetit dhe besueshm\u00ebris\u00eb gjat\u00eb d\u00ebshtimit ose mir\u00ebmbajtjes s\u00eb nj\u00eb Spine) dhe performanca totale. T\u00eb gjitha lidhjet e jashtme shkojn\u00eb n\u00eb switch-at e nivelit Leaf: k\u00ebtu kemi server\u00ebt, kalimin me rrjetet e jashtme p\u00ebrmes L2 ose L3, dhe lidhjen e kontrollor\u00ebve APIC. N\u00eb t\u00eb v\u00ebrtet\u00eb, me ACI jo vet\u00ebm q\u00eb konfigurimi, por edhe mbulimi i statistikave, monitorimi i d\u00ebshtimeve dhe t\u00eb tjera \u2013 gjith\u00e7ka b\u00ebhet p\u00ebrmes nd\u00ebrfaqes s\u00eb kontrollor\u00ebve, t\u00eb cil\u00ebt n\u00eb implementimet e zakonshme jan\u00eb tre. <\/p>\n

K\u00ebshilla e lidhjes me switch-at kurr\u00eb nuk \u00ebsht\u00eb e nevojshme, as edhe p\u00ebr nisjen e rrjetit: kontrollori vet\u00eb i zbulohet switch-at dhe formon fabrik\u00ebn prej tyre, p\u00ebrfshir\u00eb konfigurimet e t\u00eb gjitha protokolleve sh\u00ebrbimi, prandaj, p\u00ebr k\u00ebt\u00eb arsye, \u00ebsht\u00eb shum\u00eb e r\u00ebnd\u00ebsishme gjat\u00eb montimit t\u00eb regjistrohen numrat serial t\u00eb pajisjeve q\u00eb po instalohen, n\u00eb m\u00ebnyr\u00eb q\u00eb m\u00eb pas t\u00eb mos mendohet se cili switch ndodhet n\u00eb cilin raft. P\u00ebr troubleshooting, n\u00ebse \u00ebsht\u00eb e nevojshme, mund t\u00eb lidheni me switch-at p\u00ebrmes SSH: ata kan\u00eb zbatuar me kujdes komandat e zakonshme show t\u00eb Cisco. <\/p>\n

Brenda p\u00ebrdor transport IP, k\u00ebshtu q\u00eb nuk ka asnj\u00eb Spanning Tree dhe tmerrin e s\u00eb kaluar\u00ebs: t\u00eb gjitha lidhjet jan\u00eb n\u00eb p\u00ebrdorim, dhe konvergjenca n\u00eb rast d\u00ebshtimi \u00ebsht\u00eb shum\u00eb e shpejt\u00eb. Trafiku n\u00eb brend\u00ebsi transmetohet p\u00ebrmes tunelesh t\u00eb bazuara n\u00eb VXLAN. M\u00eb sakt\u00eb, Cisco e quan encapsulimin iVXLAN, dhe ndryshon nga VXLAN i zakonsh\u00ebm n\u00eb at\u00eb q\u00eb fushat e rezervuara n\u00eb titullin rrjetor p\u00ebrdoren p\u00ebr t\u00eb transmetuar informacione sh\u00ebrbimi, kryesisht p\u00ebr marr\u00ebdh\u00ebnien e trafikut me grupin EPG. Kjo lejon implementimin e rregullave t\u00eb bashk\u00ebpunimit midis grupeve n\u00eb harduer, duke p\u00ebrdorur numrat e tyre ashtu si\u00e7 p\u00ebrdoren adresat n\u00eb listat aksesi. <\/p>\n

Tunelat lejojn\u00eb shtrirjen e L2-segmenteve dhe L3 (dmth VRF) p\u00ebrmes transportit t\u00eb brendsh\u00ebm IP. N\u00eb k\u00ebt\u00eb rast, gateway i paracaktuar \u00ebsht\u00eb i shp\u00ebrndar\u00eb. Kjo do t\u00eb thot\u00eb se \u00e7do switch merret me route-n e trafikut q\u00eb hyn n\u00eb brend\u00ebsi. N\u00eb aspektin e logjik\u00ebs s\u00eb transmetimit t\u00eb trafikut, ACI \u00ebsht\u00eb e ngjashme me nj\u00eb fabrik\u00eb t\u00eb bazuar n\u00eb VXLAN\/EVPN. <\/p>\n

N\u00ebse po, at\u00ebher\u00eb \u00e7far\u00eb dallon? N\u00eb \u00e7do gj\u00eb tjet\u00ebr! <\/h3>\n

\nDallimi i par\u00eb, me t\u00eb cilin p\u00ebrballesh n\u00eb ACI, \u00ebsht\u00eb se si aktivizohen server\u00ebt n\u00eb rrjet. N\u00eb rrjetet tradicionale, aktivizimi i server\u00ebve fizik\u00eb dhe t\u00eb virtualizuar shkon n\u00eb VLAN dhe nga k\u00ebtu rrjedhin t\u00eb gjitha n\u00eb lidhje, siguria etj. Por n\u00eb ACI p\u00ebrdoret nj\u00eb struktur\u00eb, q\u00eb Cisco e quan EPG (Grupi i Pikave p\u00ebrfundimtare), nga e cila nuk ka shp\u00ebtime. A mund ta barazosh at\u00eb me VLAN? Po, por n\u00eb k\u00ebt\u00eb rast ka mund\u00ebsi t\u00eb humbas\u00ebsh pjes\u00ebn m\u00eb t\u00eb madhe t\u00eb asaj q\u00eb ofron ACI. <\/p>\n

N\u00eb lidhje me EPG formulohet e gjith\u00eb politika e aksesit, dhe n\u00eb ACI, n\u00eb parim, p\u00ebrdoret principi 'list\u00ebs s\u00eb bardh\u00eb', do t\u00eb thot\u00eb se lejohet vet\u00ebm trafiku, t\u00eb cilit i \u00ebsht\u00eb lejuar kalimi n\u00eb m\u00ebnyr\u00eb t\u00eb qart\u00eb. K\u00ebshtu q\u00eb ne mund t\u00eb krijojm\u00eb grupe EPG 'Web' dhe 'MySQL' dhe t\u00eb p\u00ebrcaktojm\u00eb nj\u00eb rregull q\u00eb lejon bashk\u00ebpunimin midis tyre vet\u00ebm p\u00ebr portin 3306. Kjo do t\u00eb funksionoj\u00eb pa u lidhur me adresat rrjetore dhe madje edhe brenda nj\u00eb n\u00ebnrrjeti! <\/p>\n

Kemi klient\u00eb q\u00eb zgjodh\u00ebn ACI pik\u00ebrisht p\u00ebr k\u00ebt\u00eb funksion, pasi ai lejon kufizimin e aksesit midis server\u00ebve (virtuel apo fizik - nuk ka r\u00ebnd\u00ebsi), pa i l\u00ebvizur ata midis n\u00ebnrrjetesh, duke mos ndryshuar k\u00ebshtu adresimin. Po, ne e dim\u00eb, askush nuk i shkruan ato manualisht Adresa IP<\/a> n\u00eb konfigurimet e aplikacioneve, apo jo?<\/p>\n

Rregullat e kalimit t\u00eb trafikut n\u00eb ACI quhen kontrata. N\u00eb nj\u00eb kontrat\u00eb, nj\u00eb ose disa grupe ose nivele n\u00eb nj\u00eb aplikacion me shum\u00eb nivele b\u00ebhen ofrues sh\u00ebrbimi (t\u00eb themi, sh\u00ebrbimi i DB), t\u00eb tjer\u00ebt jan\u00eb konsumator\u00eb. Kontrata mund t\u00eb kaloj\u00eb thjesht trafikun, ose mund t\u00eb b\u00ebj\u00eb di\u00e7ka m\u00eb t\u00eb sofistikuar, si\u00e7 \u00ebsht\u00eb t\u00eb drejtosh trafik n\u00eb nj\u00eb firewall ose balancues ngarkese, si dhe t\u00eb ndryshosh vler\u00ebn e QoS.<\/p>\n

Si p\u00ebrfundojn\u00eb serverat n\u00eb k\u00ebto grupe? N\u00ebse jan\u00eb servera fizik\u00eb ose di\u00e7ka e p\u00ebrfshir\u00eb n\u00eb nj\u00eb rrjet ekzistues, n\u00eb t\u00eb cilin ne krijuam nj\u00eb VLAN trunk, at\u00ebher\u00eb p\u00ebr t'i vendosur n\u00eb EPG do t\u00eb nevojitet t\u00eb tregojm\u00eb portin e switch-it dhe VLAN-in q\u00eb po p\u00ebrdoret atje. Si\u00e7 e shohim, VLAN-et shfaqen aty ku nuk mund t\u00eb kalosh pa to.<\/p>\n

N\u00ebse server\u00ebt jan\u00eb virtual\u00eb, mjafton t\u00eb referohesh n\u00eb mjedisin e virtualizimit t\u00eb lidhur, pastaj gjith\u00e7ka do t\u00eb ndodh\u00eb vet\u00eb: do t\u00eb krijohet nj\u00eb grup porti (n\u00ebse flasim n\u00eb terminologji VMWare) p\u00ebr lidhjen e VM, do t'i caktohen VLAN-e ose VXLAN-e t\u00eb nevojshme, do t\u00eb regjistrohen n\u00eb portat e nevojshme t\u00eb switch-it, etj. Pra, megjith\u00ebse ACI \u00ebsht\u00eb nd\u00ebrtuar p\u00ebrreth rrjetit fizik, lidhjet p\u00ebr server\u00ebt virtual\u00eb duken shum\u00eb m\u00eb t\u00eb thjeshta se p\u00ebr ato fizik\u00eb. ACI tashm\u00eb ka integruar lidhjen me VMWare dhe MS Hyper-V, si dhe mb\u00ebshtetje p\u00ebr OpenStack dhe RedHat Virtualization. Nga nj\u00eb moment i caktuar, u shfaq dhe mb\u00ebshtetje e integruar p\u00ebr platformat e kontejner\u00ebve: Kubernetes, OpenShift, Cloud Foundry, e cila ka t\u00eb b\u00ebj\u00eb si me zbatimin e politikave, ashtu edhe me monitorimin, dometh\u00ebn\u00eb administratori i rrjetit mund t\u00eb shoh\u00eb menj\u00ebher\u00eb se n\u00eb cilat host-e punojn\u00eb cilat pods dhe n\u00eb cilat grupe kan\u00eb p\u00ebrfunduar.<\/p>\n

P\u00ebrve\u00e7 p\u00ebrfshirjes n\u00eb nj\u00eb grup-porti t\u00eb caktuar, server\u00ebt virtual\u00eb kan\u00eb cil\u00ebsi t\u00eb tjera: emri, atributet, etj., q\u00eb mund t\u00eb p\u00ebrdoren si kritere p\u00ebr t'i Transferuar ata n\u00eb nj\u00eb grup tjet\u00ebr, p\u00ebr shembull, gjat\u00eb rinominimit t\u00eb VM-s\u00eb ose kur ajo merr nj\u00eb etiket\u00eb shtes\u00eb. Cisco e quan k\u00ebt\u00eb grupe mikrosektoriale, megjithat\u00eb, n\u00eb thelb, struktura me mund\u00ebsin\u00eb e krijimit t\u00eb shum\u00eb segmenteve t\u00eb siguris\u00eb n\u00eb form\u00ebn e EPG-s\u00eb n\u00eb t\u00eb nj\u00ebjt\u00ebn n\u00ebnrrjet\u00eb \u00ebsht\u00eb n\u00eb fakt mikrosektorizim. Mir\u00eb, \u00ebsht\u00eb m\u00eb mir\u00eb p\u00ebr ofruesin. <\/p>\n

EPG-t\u00eb jan\u00eb strukturat e pastra logjike, t\u00eb paarritura p\u00ebr komutator\u00eb, server\u00eb, etj., k\u00ebshtu q\u00eb me to dhe me strukturat e bazuara mbi to (aplikacione dhe qiramarr\u00ebs) mund t\u00eb b\u00ebni gj\u00ebra q\u00eb jan\u00eb t\u00eb v\u00ebshtira p\u00ebr t'u realizuar n\u00eb rrjetet tradicionale, si\u00e7 \u00ebsht\u00eb klonimi. Si rezultat, p\u00ebr shembull, \u00ebsht\u00eb shum\u00eb e leht\u00eb t\u00eb krijoni nj\u00eb klon t\u00eb nj\u00eb mjedisi prodhimi p\u00ebr t\u00eb marr\u00eb nj\u00eb ambient testi, t\u00eb garantuar identik me prodhimin. Mund ta b\u00ebni manualisht, por \u00ebsht\u00eb m\u00eb mir\u00eb (dhe m\u00eb e leht\u00ebsuar) p\u00ebrmes API-s\u00eb. <\/p>\n

N\u00eb p\u00ebrgjith\u00ebsi, logjika e menaxhimit n\u00eb ACI \u00ebsht\u00eb krejt\u00ebsisht ndryshe nga ajo q\u00eb zakonisht hasni
\nn\u00eb rrjetet tradicionale nga Cisco: nd\u00ebrfaqja programore \u00ebsht\u00eb primare, nd\u00ebrsa GUI ose CLI jan\u00eb sekondare, pasi punojn\u00eb p\u00ebrmes t\u00eb nj\u00ebjtit API. Prandaj, pothuajse \u00e7do person q\u00eb merret me ACI pas nj\u00eb kohe fillon t\u00eb orientoj\u00eb n\u00eb modelin e objektit q\u00eb p\u00ebrdoret p\u00ebr menaxhim dhe t\u00eb automatizoj\u00eb di\u00e7ka sipas nevojave t\u00eb tij. M\u00eb s\u00eb lehti \u00ebsht\u00eb t\u00eb b\u00ebhet nga Python: p\u00ebr t\u00eb ka mjete t\u00eb gatshme dhe t\u00eb p\u00ebrshtatshme. <\/p>\n

Grapat e premtimeve<\/h3>\n

\nProblemi kryesor \u00ebsht\u00eb se shum\u00eb gj\u00ebra n\u00eb ACI jan\u00eb b\u00ebr\u00eb ndryshe. P\u00ebr t\u00eb filluar t\u00eb punoni normalisht me t\u00eb, duhet t\u00eb rikonceptoni veten. Kjo \u00ebsht\u00eb ve\u00e7an\u00ebrisht e v\u00ebrtet\u00eb p\u00ebr ekipet e operacioneve rrjet\u00ebrore n\u00eb bler\u00ebs t\u00eb m\u00ebdhenj, ku inxhinier\u00ebt kan\u00eb kaluar vite duke b\u00ebr\u00eb \u00abshkrime VLAN\u00ebsh\u00bb sipas k\u00ebrkesave. Ajo q\u00eb tani VLAN nuk \u00ebsht\u00eb m\u00eb VLAN, dhe p\u00ebr t\u00eb krijuar rrjete t\u00eb reja n\u00eb server\u00ebt e virtualizuar, nuk \u00ebsht\u00eb e nevojshme t\u00eb krijoni VLAN me dor\u00eb, kjo p\u00ebrfundimisht \u00ab\u00e7mend\u00bb specialist\u00ebt e rrjeteve tradicionale dhe i detyron ata t\u00eb ngjiten pas qasjeve t\u00eb njohura. Duhet t\u00eb theksohet se Cisco p\u00ebrpiqet t\u00eb leht\u00ebsoj\u00eb pak gj\u00ebrat dhe ka shtuar n\u00eb kontrollues nj\u00eb CLI \u201cNXOS-p\u00ebrputhsh\u00ebm\u201d, i cili lejon konfigurimin nga nj\u00eb nd\u00ebrfaqe, e ngjashme me komutator\u00ebt tradicional\u00eb. Megjithat\u00eb, p\u00ebr t\u00eb filluar t\u00eb shfryt\u00ebzoni normalisht ACI-n\u00eb, do t\u00eb duhet t\u00eb kuptoni se si funksionon. <\/p>\n

Nga pik\u00ebpamja e \u00e7mimit n\u00eb shkall\u00eb t\u00eb madhe dhe mesatare, rrjeti ACI nga rrjetet tradicionale n\u00eb pajisjet Cisco n\u00eb fakt nuk dallon, pasi p\u00ebr nd\u00ebrtimin e tyre p\u00ebrdoren t\u00eb nj\u00ebjtat switch-e (Nexus 9000 mund t\u00eb funksionoj\u00eb si n\u00eb ACI ashtu edhe n\u00eb m\u00ebnyr\u00eb tradicionale dhe tani jan\u00eb b\u00ebr\u00eb \"kali i pun\u00ebs\" p\u00ebr projektet e reja t\u00eb Qendr\u00ebs s\u00eb T\u00eb Dh\u00ebnave). Megjithat\u00eb, p\u00ebr Qendrat e T\u00eb Dh\u00ebnave me dy switch-e, prania e kontrollor\u00ebve dhe arkitektur\u00ebs Spine-Leaf v\u00ebrtet hahet. S\u00eb fundi u shfaq Mini ACI-fabrika, n\u00eb t\u00eb cil\u00ebn dy kontrollor\u00eb nga tre jan\u00eb z\u00ebvend\u00ebsuar me makinat virtuale. Kjo lejon t\u00eb reduktohet ndryshimi n\u00eb kosto, por ai ende ekziston. Prandaj, p\u00ebr klientin, zgjedhja \u00ebsht\u00eb e diktuar nga sa shum\u00eb \u00ebsht\u00eb i interesuar p\u00ebr funksionalitetet e siguris\u00eb, integrimit me virtualizimin, pik\u00ebs s\u00eb vetme t\u00eb menaxhimit dhe t\u00eb tjera.
\n
Burimi: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u0421 \u043f\u043e\u043c\u043e\u0449\u044c\u044e \u0432\u043e\u0442 \u044d\u0442\u043e\u0433\u043e \u0432\u043e\u043b\u0448\u0435\u0431\u043d\u043e\u0433\u043e \u043a\u0443\u0441\u043a\u0430 \u0441\u043a\u0440\u0438\u043f\u0442\u0430 Cisco ACI \u043c\u043e\u0436\u043d\u043e \u0431\u044b\u0441\u0442\u0440\u043e \u043d\u0430\u0441\u0442\u0440\u043e\u0438\u0442\u044c \u0441\u0435\u0442\u044c. \u0421\u0435\u0442\u0435\u0432\u0430\u044f \u0444\u0430\u0431\u0440\u0438\u043a\u0430 \u0434\u043b\u044f \u0426\u041e\u0414\u0430 Cisco ACI c\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u0435\u0442 \u0443\u0436\u0435 \u043f\u044f\u0442\u044c \u043b\u0435\u0442, \u043d\u043e \u043d\u0430 \u0425\u0430\u0431\u0440\u0435 \u043f\u0440\u043e \u043d\u0435\u0451 \u0442\u043e\u043b\u043a\u043e\u043c \u043d\u0438\u0447\u0435\u0433\u043e \u043d\u0435 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u043d\u043e, \u0432\u043e\u0442 \u0438 \u0440\u0435\u0448\u0438\u043b \u044d\u0442\u043e \u043d\u0435\u043c\u043d\u043e\u0433\u043e \u0438\u0441\u043f\u0440\u0430\u0432\u0438\u0442\u044c. \u0420\u0430\u0441\u0441\u043a\u0430\u0436\u0443 \u043d\u0430 \u0441\u0432\u043e\u0451\u043c \u043e\u043f\u044b\u0442\u0435, \u0447\u0442\u043e \u044d\u0442\u043e \u0442\u0430\u043a\u043e\u0435, \u043a\u0430\u043a\u0430\u044f \u043e\u0442 \u043d\u0435\u0451 \u043f\u043e\u043b\u044c\u0437\u0430 \u0438 \u0433\u0434\u0435 \u0443 \u043d\u0435\u0451 \u0433\u0440\u0430\u0431\u043b\u0438. \u0427\u0442\u043e […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-35291","post","type-post","status-publish","format-standard","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\udd47Fabrika e rrjetit p\u00ebr Qendr\u00ebn e T\u00eb Dh\u00ebnave Cisco ACI - p\u00ebr ndihm\u00ebn e administratorit | ProHoster","description":"Me k\u00ebt\u00eb cop\u00eb skripti magjik.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/setevaya-fabrika-dlya-tsoda-cisco-aci-v-pomoshh-adminu","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\u0421\u0435\u0442\u0435\u0432\u0430\u044f \u0444\u0430\u0431\u0440\u0438\u043a\u0430 \u0434\u043b\u044f \u0426\u041e\u0414\u0430 Cisco ACI \u2014 \u0432 \u043f\u043e\u043c\u043e\u0449\u044c \u0430\u0434\u043c\u0438\u043d\u0443 | ProHoster","og:description":"\u0421 \u043f\u043e\u043c\u043e\u0449\u044c\u044e \u0432\u043e\u0442 \u044d\u0442\u043e\u0433\u043e \u0432\u043e\u043b\u0448\u0435\u0431\u043d\u043e\u0433\u043e \u043a\u0443\u0441\u043a\u0430 \u0441\u043a\u0440\u0438\u043f\u0442\u0430.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/setevaya-fabrika-dlya-tsoda-cisco-aci-v-pomoshh-adminu","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":"2019-10-31T19:03:28+00:00","article:modified_time":"2019-10-31T19:03:28+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"35291","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":"2026-02-08 20:27:18","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:06:24","updated":"2026-02-08 20:27:18","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\/35291","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=35291"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/35291\/revisions"}],"predecessor-version":[{"id":157819,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/35291\/revisions\/157819"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=35291"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=35291"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=35291"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}