{"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 administruesit.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

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

Fabrika rrjet\u00ebsore p\u00ebr Qendrat e t\u00eb Dh\u00ebnave Cisco ACI ekziston p\u00ebr pes\u00eb vjet, por nuk \u00ebsht\u00eb folur shum\u00eb p\u00ebr t\u00eb n\u00eb Habr\u00eb, k\u00ebshtu q\u00eb vendosa ta korrigjoj k\u00ebt\u00eb pak. Do t\u00eb flas nga p\u00ebrvoja ime se \u00e7far\u00eb \u00ebsht\u00eb, cila \u00ebsht\u00eb p\u00ebrfitimi i saj dhe ku ndodhen pengesat. <\/p>\n

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

\nN\u00eb momentin e njoftimit t\u00eb ACI (Application Centric Infrastructure) n\u00eb vitin 2013, konkurent\u00ebt e qendrave t\u00eb t\u00eb dh\u00ebnave po i qasnin qasjeve tradicionale t\u00eb rrjetit nga tri an\u00ebt. <\/p>\n

Nga nj\u00ebra an\u00eb, zgjidhjet SDN \"t\u00eb gjenerat\u00ebs s\u00eb par\u00eb\" t\u00eb bazuara n\u00eb OpenFlow premtonin t\u00eb b\u00ebnin rrjetet m\u00eb fleksib\u00ebl dhe m\u00eb t\u00eb p\u00ebrballueshme nj\u00ebher\u00ebsh. Ideja ishte q\u00eb t\u00eb transferohej marrja e vendimeve, e cila tradicionalisht p\u00ebrfaq\u00ebsohej nga softi i pronar\u00ebve t\u00eb p\u00ebrSwitch-ave, n\u00eb nj\u00eb kontroler qendror. <\/p>\n

Ky kontroler do t\u00eb kishte nj\u00eb pamje t\u00eb vetme t\u00eb gjith\u00e7kaje q\u00eb ndodhte dhe, duke u bazuar n\u00eb k\u00ebt\u00eb, do t\u00eb programonte pajisjet e t\u00eb gjitha switch-ave n\u00eb nivelin e rregullave p\u00ebr trajtimin e flukseve specifike. <\/a><\/noindex>
\nNga ana tjet\u00ebr, zgjidhjet rrjet\u00ebsore me ovelay ofronin mund\u00ebsin\u00eb p\u00ebr t\u00eb arritur lidhshm\u00ebri dhe politika sigurie pa b\u00ebr\u00eb ndryshime n\u00eb rrjetin fizik, duke nd\u00ebrtuar tunel\u00eb programor\u00eb mes hosteve t\u00eb virtualizuara. Nj\u00eb shembull i njohur i nj\u00eb qasjeje t\u00eb till\u00eb ishte zgjidhja nga Nicira, e cila n\u00eb at\u00eb koh\u00eb ishte bler\u00eb nga VMWare p\u00ebr 1.26 miliard\u00eb dollar\u00eb dhe dha fillimin e VMWare NSX. Nj\u00eb pik\u00eb k\u00ebndore e situat\u00ebs ishte se bashk\u00ebthemeluesit e Nicira ishin ata t\u00eb nj\u00ebjtit q\u00eb m\u00eb par\u00eb ishin n\u00eb fillimet e OpenFlow, tani duke th\u00ebn\u00eb se p\u00ebr nd\u00ebrtimin e fabrikave t\u00eb Qendrave t\u00eb t\u00eb Dh\u00ebnave OpenFlow nuk ishte i p\u00ebrshtatsh\u00ebm. OpenFlow nuk \u00ebsht\u00eb i p\u00ebrshtatsh\u00ebm.<\/a><\/noindex>.<\/p>\n

Dhe, p\u00ebrfundimisht, \u00e7ipat e switch-ave n\u00eb treg (ato q\u00eb quhen merchant silicon) arrit\u00ebn nj\u00eb shkall\u00eb pjekurie, duke u b\u00ebr\u00eb nj\u00eb k\u00ebrc\u00ebnim real p\u00ebr prodhuesit tradicional\u00eb t\u00eb switch-ave. N\u00ebse m\u00eb par\u00eb \u00e7do ofrues zhvillonte vet\u00eb \u00e7ipat e tij p\u00ebr switch-at, me kalimin e koh\u00ebs, \u00e7ipat nga prodhues t\u00eb jasht\u00ebm, kryesisht nga Br\u043eadcom, filluan t\u00eb ngushtojn\u00eb distanc\u00ebn me \u00e7ipat e ofruesve p\u00ebr funksionalitetet, nd\u00ebrsa p\u00ebr raportin \u00e7mim\/p\u00ebrformanc\u00eb i tejkalonin ata. Prandaj, shum\u00eb mendonin se dit\u00ebt e switch-ave me \u00e7ipa t\u00eb zhvilluar vet\u00eb i ishin count.<\/p>\n

ACI u b\u00eb \"p\u00ebrgjigjja asimetrike\" e Cisco (m\u00eb sakt\u00ebsisht, e kompanis\u00eb Insieme, e cila ishte themeluar nga ish-punonj\u00ebsit e saj) ndaj gjith\u00e7kaje t\u00eb p\u00ebrmendur m\u00eb par\u00eb. <\/p>\n

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

\nN\u00eb aspektin e shp\u00ebrndarjes s\u00eb funksioneve, ACI \u00ebsht\u00eb faktikisht e kund\u00ebrta e OpenFlow.
\nN\u00eb arkitektur\u00ebn OpenFlow, kontrolluesi \u00ebsht\u00eb p\u00ebrgjegj\u00ebs p\u00ebr shkrimin e rregullave t\u00eb detajuara (flukseve)
\nn\u00eb pajisjet e t\u00eb gjitha switch-ave, dometh\u00ebn\u00eb n\u00eb nj\u00eb rrjet t\u00eb madh, ai mund t\u00eb ket\u00eb p\u00ebrgjegj\u00ebsin\u00eb p\u00ebr mbajtjen dhe, m\u00eb e r\u00ebnd\u00ebsishmja, ndryshimin e dhjet\u00ebra miliona regjistrimeve n\u00eb qindra pika n\u00eb rrjet, prandaj performanca dhe besueshm\u00ebria e saj n\u00eb nj\u00eb implementim t\u00eb madh b\u00ebhen nj\u00eb ngushtic\u00eb.<\/p>\n

N\u00eb ACI, p\u00ebrdoret nj\u00eb qasje e kund\u00ebrt: ka gjithashtu nj\u00eb kontroler, por switch-avat marrin nga ai politika deklarative t\u00eb niveleve t\u00eb larta, nd\u00ebrsa realizimi i detajeve t\u00eb konfigurimeve specifike n\u00eb pajisje kryhet nga vet\u00eb switch-i. Kontrolluesi mund t\u00eb rib\u00ebhet ose madje t\u00eb fiket, dhe nuk do ndodhi asgj\u00eb e keqe me rrjetin, p\u00ebrve\u00e7, natyrisht, munges\u00ebs n\u00eb at\u00eb moment t\u00eb mund\u00ebsis\u00eb p\u00ebr menaxhim. \u00cbsht\u00eb e interesant\u00eb se n\u00eb ACI ekzistojn\u00eb situata ku OpenFlow ende p\u00ebrdoret, por lokalizuar brenda hostit p\u00ebr programimin e Open vSwitch.<\/p>\n

ACI \u00ebsht\u00eb plot\u00ebsisht e nd\u00ebrtuar mbi transportin ovelay t\u00eb bazuar n\u00eb VXLAN, por p\u00ebrfshin gjithashtu transportin IP t\u00eb posht\u00ebm brenda nj\u00eb zgjidhje t\u00eb vetme. Cisco e quajti k\u00ebt\u00eb termin \"ovelaj i integruar\". P\u00ebr pik\u00ebn e terminimit t\u00eb ovelave n\u00eb ACI, n\u00eb shumic\u00ebn e rasteve p\u00ebrdoren switch-avat e fabrik\u00ebs (e b\u00ebjn\u00eb k\u00ebt\u00eb me shpejt\u00ebsi kanali). Hostet nuk duhet t\u00eb din\u00eb asgj\u00eb p\u00ebr fabrik\u00ebn, inkapsulimet etj., por n\u00eb disa raste (p\u00ebr shembull, p\u00ebr t\u00eb lidhur hostet OpenStack) trafiku VXLAN mund t\u00eb arrij\u00eb tek ta.<\/p>\n

Ovelat p\u00ebrdoren n\u00eb ACI jo vet\u00ebm p\u00ebr t\u00eb siguruar lidhshm\u00ebri fleksibile p\u00ebrmes rrjetit t\u00eb transportit, por edhe p\u00ebr t\u00eb transmetuar meta-informacion (ai p\u00ebrdoret, p\u00ebr shembull, p\u00ebr zbatimin e politikave t\u00eb sigurise). <\/p>\n

\u00c7ipat nga Broadcom jan\u00eb p\u00ebrdorur m\u00eb par\u00eb nga Cisco n\u00eb nd\u00ebrprer\u00ebsit e seris\u00eb Nexus 3000. N\u00eb familjen Nexus 9000, e cila u l\u00ebshua posa\u00e7\u00ebrisht p\u00ebr t\u00eb mb\u00ebshtetur ACI, u zbatua fillimisht nj\u00eb model hibrid, t\u00eb cilin e quajt\u00ebn Merchant+. N\u00eb nd\u00ebrprer\u00ebs, u p\u00ebrdor\u00ebn nj\u00ebkoh\u00ebsisht \u00e7ipi i ri Broadcom Trident 2 dhe nj\u00eb \u00e7ip mb\u00ebshtetje nga Cisco, i cili realizon t\u00eb gjith\u00eb magjin\u00eb e ACI. Duket se kjo ka lejuar p\u00ebrshpejtimin e daljes s\u00eb produktit dhe uljen e \u00e7mimeve t\u00eb nd\u00ebrprer\u00ebsit n\u00eb nj\u00eb nivel t\u00eb af\u00ebrt me modelet q\u00eb p\u00ebrdorin vet\u00ebm 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 l\u00ebshoi n\u00eb treg brezin e ardhsh\u00ebm t\u00eb Nexus 9000, tashm\u00eb n\u00eb \u00e7ipat e saj me performanc\u00eb m\u00eb t\u00eb lart\u00eb dhe nj\u00eb set funksionesh, por me t\u00eb nj\u00ebjtin nivel \u00e7mimi. Specifikimet e jashtme n\u00eb aspektin e nd\u00ebrveprimit n\u00eb fabrik\u00eb kan\u00eb mbetur plot\u00ebsisht t\u00eb pandryshuar. Nd\u00ebrkoh\u00eb, brend\u00ebsia e saj ka ndryshuar plot\u00ebsisht: nj\u00eb lloj refaktorizimi, por p\u00ebr harduerin.<\/p>\n

Si \u00ebsht\u00eb struktura e arkitektur\u00ebs Cisco ACI <\/h3>\n

\nN\u00eb rastin m\u00eb t\u00eb thjesht\u00eb, ACI nd\u00ebrtohet mbi nj\u00eb topologji t\u00eb rrjetit Clos, ose, si\u00e7 quhet shpesh, Spine-Leaf. Numri i nd\u00ebrprer\u00ebsve t\u00eb nivelit Spine mund t\u00eb jet\u00eb nga dy (ose nj\u00eb, n\u00ebse nuk na intereson disponueshm\u00ebria) n\u00eb gjasht\u00eb. Prandaj, sa m\u00eb shum\u00eb t\u00eb jen\u00eb, aq m\u00eb e lart\u00eb \u00ebsht\u00eb disponueshm\u00ebria (m\u00eb pak ulje e brezit t\u00eb dh\u00ebnash dhe besueshm\u00ebris\u00eb gjat\u00eb d\u00ebshtimeve ose mir\u00ebmbajtjes s\u00eb nj\u00eb Spine) dhe performanca totale. T\u00eb gjitha lidhjet e jashtme shkojn\u00eb n\u00eb nd\u00ebrprer\u00ebsit e nivelit Leaf: k\u00ebtu b\u00ebjn\u00eb pjes\u00eb server\u00ebt, lidhjet me rrjetet e jashtme p\u00ebrmes L2 ose L3, dhe lidhja e kontroler\u00ebve APIC. N\u00eb p\u00ebrgjith\u00ebsi, me ACI jo vet\u00ebm konfigurimi, por edhe mbledhja e statistikave, monitorimi i d\u00ebshtimeve dhe gj\u00ebrat e tjera \u2014 gjith\u00e7ka b\u00ebhet p\u00ebrmes nd\u00ebrfaqeve t\u00eb kontroler\u00ebve, t\u00eb cil\u00ebt n\u00eb vendosjet e zakonshme jan\u00eb tre. <\/p>\n

K\u00ebto nd\u00ebrprer\u00ebs nuk lidhin kurr\u00eb me konsol\u00eb, as p\u00ebr t\u00eb filluar rrjetin: kontroleri vet\u00eb zbulon nd\u00ebrprer\u00ebsit dhe krijon fabrik\u00ebn prej tyre, duke p\u00ebrfshir\u00eb konfigurimet e t\u00eb gjitha protokolleve sh\u00ebrbimi, prandaj, \u00ebsht\u00eb shum\u00eb e r\u00ebnd\u00ebsishme q\u00eb gjat\u00eb montimit t\u00eb regjistrohen numrat serial t\u00eb pajisjeve q\u00eb instalohet, n\u00eb m\u00ebnyr\u00eb q\u00eb m\u00eb von\u00eb t\u00eb mos hamend\u00ebsojm\u00eb se cili nd\u00ebrprer\u00ebs \u00ebsht\u00eb n\u00eb cilin raft. P\u00ebr zgjidhjen e problemeve, n\u00ebse \u00ebsht\u00eb e nevojshme, mund t\u00eb lidhemi me nd\u00ebrprer\u00ebsit p\u00ebrmes SSH: n\u00eb to jan\u00eb t\u00eb riprodhuara t\u00ebr\u00ebsisht komandat e zakonshme show t\u00eb Cisco. <\/p>\n

Brenda fabrik\u00ebs p\u00ebrdor transportin IP, k\u00ebshtu q\u00eb nuk ka Spanning Tree dhe katastrofat e tjera t\u00eb t\u00eb kaluar\u00ebs: t\u00eb gjitha lidhjet jan\u00eb aktivizuar dhe konvergjenca gjat\u00eb d\u00ebshtimeve \u00ebsht\u00eb shum\u00eb e shpejt\u00eb. Trafiku n\u00eb fabrik\u00eb d\u00ebrgohet p\u00ebrmes tuneleve t\u00eb bazuara n\u00eb VXLAN. N\u00ebse sakt\u00ebsisht, Cisco e quan incapsulimin 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, s\u00eb pari - n\u00eb lidhje me lidhjen e trafikut me grupin EPG. Kjo lejon realizimin e rregullave t\u00eb nd\u00ebrveprimit midis grupeve n\u00eb harduer, duke p\u00ebrdorur numrat e tyre ashtu si\u00e7 p\u00ebrdoren adresat n\u00eb listat e zakonshme t\u00eb aksesit. <\/p>\n

Tunelet lejojn\u00eb shtrirjen p\u00ebrmes transportit t\u00eb brendsh\u00ebm IP dhe segmenteve L2 dhe L3 (dometh\u00ebn\u00eb VRF). N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, gateway i paracaktuar \u00ebsht\u00eb i shp\u00ebrndar\u00eb. Kjo do t\u00eb thot\u00eb se \u00e7do nd\u00ebrprer\u00ebs merret me rrug\u00ebtimin e trafikut q\u00eb hyn n\u00eb fabrik\u00eb. 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 \u00ebsht\u00eb k\u00ebshtu, at\u00ebher\u00eb \u00e7far\u00eb dallimesh ka? <\/h3>\n

\nDallimi num\u00ebr nj\u00eb, me t\u00eb cilin p\u00ebrballeni n\u00eb ACI, \u00ebsht\u00eb se si server\u00ebt lidhen n\u00eb rrjet. N\u00eb rrjetet tradicionale, lidhja e server\u00ebve fizik\u00eb dhe virtual\u00ebve b\u00ebhet n\u00eb VLAN, dhe nga ata gjith\u00e7ka tjet\u00ebr rrjedh: lidhshm\u00ebria, siguria etj. N\u00eb ACI p\u00ebrdoret nj\u00eb konstrukcion q\u00eb Cisco e quan EPG (Grupi i Pikave p\u00ebrfundimtare), i cili \u00ebsht\u00eb i paevituesh\u00ebm. A mund t\u00eb barazohet ajo me VLAN? Po, por n\u00eb k\u00ebt\u00eb rast ka nj\u00eb shans t\u00eb humbas\u00ebsh nj\u00eb pjes\u00eb t\u00eb madhe t\u00eb asaj q\u00eb ofron ACI. <\/p>\n

T\u00eb gjitha rregullat e aksesit formulohen n\u00eb lidhje me EPG, dhe n\u00eb ACI, sipas parazgjedhjes, p\u00ebrdoret parimi i \"list\u00ebs s\u00eb bardh\u00eb\", do t\u00eb thot\u00eb se vet\u00ebm trafiku, kalimi i t\u00eb cilit \u00ebsht\u00eb lejuar n\u00eb m\u00ebnyr\u00eb t\u00eb qart\u00eb, \u00ebsht\u00eb i lejuar. Dometh\u00ebn\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\u00ebrmes portit 3306. Kjo do t\u00eb funksionoj\u00eb pa iu referuar adresave t\u00eb rrjetit dhe madje brenda nj\u00eb n\u00ebndeshme! <\/p>\n

Kemi klient\u00eb q\u00eb kan\u00eb zgjedhur ACI p\u00ebr shkak t\u00eb k\u00ebsaj ve\u00e7ori, pasi ajo lejon kufizimin e qasjeve midis server\u00ebve (virtual\u00eb apo fizik\u00eb - nuk ka r\u00ebnd\u00ebsi), pa i zhvendosur ato midis n\u00ebndeshmeve, pra pa prekur adresimin. Po, e dim\u00eb, askush nuk i shkruan me dor\u00eb adresat 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 m\u00eb shum\u00eb grupe ose nivele n\u00eb nj\u00eb aplikacion multi-tier b\u00ebhen ofrues t\u00eb sh\u00ebrbimit (le t\u00eb themi, sh\u00ebrbimi i baz\u00ebs s\u00eb t\u00eb dh\u00ebnave), nd\u00ebrsa t\u00eb tjer\u00ebt jan\u00eb konsumator\u00eb. Kontrata mund thjesht t\u00eb kaloj\u00eb trafikun, apo t\u00eb b\u00ebj\u00eb di\u00e7ka m\u00eb t\u00eb sofistikuar, si\u00e7 \u00ebsht\u00eb drejtuar n\u00eb nj\u00eb firewall ose balancues trafiku, si dhe t\u00eb ndryshoj\u00eb vler\u00ebn e QoS.<\/p>\n

Si arrijn\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 kemi krijuar nj\u00eb VLAN trunk, at\u00ebher\u00eb p\u00ebr t'i futur n\u00eb EPG duhet t\u00eb ceket porta e switch-it dhe VLAN-i p\u00ebrdorur aty. Si\u00e7 e shohim, VLAN-et shfaqen aty ku nuk mund t\u00eb veprohet pa to.<\/p>\n

N\u00ebse serverat jan\u00eb virtual\u00eb, mjafton t\u00eb referohet mjedisi i virtualizimit t\u00eb lidhur, dhe m\u00eb pas gjith\u00e7ka ndodhi vet\u00eb: krijohet nj\u00eb grup porte (n\u00ebse flasim n\u00eb terma - VMWare) p\u00ebr lidhjen e VM, i caktohen VLAN-et ose VXLAN-et e nevojshme, shkruhen n\u00eb portat e nevojshme t\u00eb switch-\u00ebve etj. Pra, edhe pse ACI \u00ebsht\u00eb nd\u00ebrtuar rreth nj\u00eb rrjeti fizik, lidhjet p\u00ebr serverat virtual\u00eb duken shum\u00eb m\u00eb t\u00eb thjeshta se p\u00ebr ata fizik\u00eb. ACI ka tashm\u00eb t\u00eb nd\u00ebrthurur integrimin me VMWare dhe MS Hyper-V, si dhe mb\u00ebshtetje p\u00ebr OpenStack dhe RedHat Virtualization. Q\u00eb nga nj\u00eb moment i caktuar, u shfaq edhe mb\u00ebshtetje e integruar p\u00ebr platforma konteiner\u00ebsh: Kubernetes, OpenShift, Cloud Foundry, nd\u00ebrsa kjo ndikon gjithashtu n\u00eb aplikimin e politikave dhe monitorimin, dmth, administrator\u00ebt e rrjetit mund t\u00eb shohin menj\u00ebher\u00eb se n\u00eb cilat hoste cilat pods punojn\u00eb dhe n\u00eb cilat grupe kan\u00eb p\u00ebrfunduar.<\/p>\n

P\u00ebrve\u00e7 p\u00ebrfshirjes n\u00eb nj\u00eb grup porte ose tjet\u00ebr, serverat virtual\u00eb kan\u00eb vlera shtes\u00eb: emri, atributet etj., t\u00eb cilat mund t\u00eb p\u00ebrdoren si kritere p\u00ebr t'i kaluar n\u00eb nj\u00eb grup tjet\u00ebr, le t\u00eb themi, kur VM riem\u00ebrohet ose kur merr nj\u00eb etiket\u00eb shtes\u00eb. Cisco e quan k\u00ebt\u00eb grupe mikrosigmentimi, megjithat\u00eb, n\u00eb thelb, struktura vet\u00eb me mund\u00ebsin\u00eb p\u00ebr t\u00eb krijuar shum\u00eb segmente sigurie n\u00eb form\u00ebn e EPG n\u00eb t\u00eb nj\u00ebjtin subnet - \u00ebsht\u00eb gjithashtu mikrosigmentim. Epo, \u00ebsht\u00eb m\u00eb mir\u00eb q\u00eb kjo t'i takoj\u00eb ofruesit. <\/p>\n

EPG-t\u00eb jan\u00eb struktura krejt logjike, t\u00eb pap\u00ebrthyera me switch-e specifik\u00eb, server\u00eb etj., k\u00ebshtu q\u00eb me to dhe struktura q\u00eb krijohen mbi to (aplikacionet dhe qira) mund t\u00eb b\u00ebjm\u00eb 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, \u00ebsht\u00eb shum\u00eb e leht\u00eb t\u00eb krijosh nj\u00eb klon t\u00eb mjedisit produktiv p\u00ebr t\u00eb marr\u00eb nj\u00eb mjedis testimi q\u00eb \u00ebsht\u00eb garantsht identik me produktivin. Mund t\u00eb b\u00ebhet manualisht, por \u00ebsht\u00eb m\u00eb mir\u00eb (dhe m\u00eb e thjesht\u00eb) p\u00ebrmes API. <\/p>\n

Logjika e menaxhimit n\u00eb ACI \u00ebsht\u00eb krejt ndryshe nga ajo q\u00eb zakonisht haset
\nn\u00eb rrjetet tradicionale nga Cisco e p\u00ebr t\u00eb cilat zakonisht ka p\u00ebrvoj\u00eb: 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 orientohet n\u00eb modelin objektit q\u00eb p\u00ebrdoret p\u00ebr menaxhim, dhe t\u00eb automatizoj\u00eb di\u00e7ka sipas nevojave t\u00eb tij. \u00cbsht\u00eb m\u00eb e leht\u00eb t\u00eb b\u00ebhet nga Python: p\u00ebr t\u00eb ka mjete t\u00eb gatshme dhe t\u00eb p\u00ebrshtatshme. <\/p>\n

Gropa t\u00eb premtuara<\/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 ri-edukohemi. Kjo vlen ve\u00e7an\u00ebrisht p\u00ebr ekipet e operimit t\u00eb rrjetit te klient\u00ebt e m\u00ebdhenj, ku inxhinier\u00ebt punojn\u00eb p\u00ebr vite me radh\u00eb me \"p\u00ebrshkrimin e VLAN-eve\" sipas k\u00ebrkesave. Ajo q\u00eb tani \u00ebsht\u00eb VLAN - nuk \u00ebsht\u00eb m\u00eb VLAN, dhe p\u00ebr t\u00eb krijuar rrjete t\u00eb reja n\u00eb hostet e virtualizuar nuk \u00ebsht\u00eb e nevojshme t\u00eb krijohen VLAN-e me dor\u00eb, kjo po e \"shkat\u00ebrron\" mendjen e rrjetar\u00ebve tradicional\u00eb dhe i detyron ata t\u00eb mbahen pas qasjeve t\u00eb zakonshme. Duhet t\u00eb theksohet se Cisco ka p\u00ebrpiqur t\u00eb \u00ebmb\u00eblsoj\u00eb disi pilul\u00ebn dhe ka shtuar nj\u00eb CLI \"NXOS-p\u00ebrjash\u00eb\", q\u00eb lejon konfigurimin nga nj\u00eb nd\u00ebrfaqe q\u00eb ngjan me switch-et tradicionale. Por gjithsesi, p\u00ebr t\u00eb filluar t\u00eb p\u00ebrdor\u00eb ACI n\u00eb m\u00ebnyr\u00eb normale, do t\u00eb jet\u00eb e nevojshme t\u00eb kuptohet si funksionon ajo. <\/p>\n

Sa i p\u00ebrket \u00e7mimit n\u00eb rrjetet ACI n\u00eb shkall\u00ebt e m\u00ebdha dhe t\u00eb mesme, ato faktikisht nuk ndryshojn\u00eb nga ato tradicionale n\u00eb pajisjet Cisco, pasi p\u00ebr nd\u00ebrtimin e tyre p\u00ebrdoren switch-e t\u00eb nj\u00ebjt\u00eb (Nexus 9000 mund t\u00eb punojn\u00eb si n\u00eb ACI ashtu edhe n\u00eb modin tradicional dhe tani jan\u00eb \"kuaj pune\" kryesor p\u00ebr projektet e reja t\u00eb qendrave t\u00eb t\u00eb dh\u00ebnave). Nga ana tjet\u00ebr, p\u00ebr Qendrat e T\u00eb Dh\u00ebnave nga dy switch-e, prania e kontrollor\u00ebve dhe arkitektur\u00ebs Spine-Leaf sigurisht q\u00eb ndihen. S\u00eb fundmi, u shfaq Mini ACI-fabrika, n\u00eb t\u00eb cil\u00ebn dy kontrollor\u00eb nga tre jan\u00eb z\u00ebvend\u00ebsuar me makina virtuale. Kjo lejon t\u00eb reduktohet diferenca n\u00eb kostos, por ajo mbetet gjithsesi. Pra, p\u00ebr klientin, zgjedhja p\u00ebrcaktohet nga sa i interesuar \u00ebsht\u00eb ai p\u00ebr funksionalitetin e siguris\u00eb, integrimin me virtualizimin, pik\u00ebn e vetme t\u00eb menaxhimit dhe gj\u00ebra 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 Data Qendrat Cisco ACI \u2014 n\u00eb ndihm\u00eb t\u00eb administratorit | ProHoster","description":"Me ndihm\u00ebn e k\u00ebtij kodi magjik t\u00eb Cisco ACI, mund t\u00eb konfiguroni shpejt rrjetin. Fabrika e rrjetit p\u00ebr Data Qendrat Cisco ACI ekziston prej pes\u00eb vjet\u00ebsh, por n\u00eb Habr\u00eb nuk \u00ebsht\u00eb folur shum\u00eb p\u00ebr t\u00eb, k\u00ebshtu q\u00eb vendosa ta ndihmoj pak k\u00ebt\u00eb. Do t\u00eb flas nga p\u00ebrvoja ime, se \u00e7far\u00eb \u00ebsht\u00eb, \u00e7far\u00eb p\u00ebrfitimi sjell dhe ku ka pengesa. \u00c7far\u00eb","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 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","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}]}}