{"id":35830,"date":"2019-10-31T22:06:40","date_gmt":"2019-10-31T19:06:40","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-11-osnovy-vlan\/"},"modified":"2019-10-31T22:06:40","modified_gmt":"2019-10-31T19:06:40","slug":"trening-cisco-200-125-ccna-v3-0-den-11-osnovy-vlan","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-11-osnovy-vlan","title":{"rendered":"Trajnimi Cisco 200-125 CCNA v3.0. Dita 11. Thelbi i VLAN","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Para se fillojm\u00eb me bazat e VLAN, do t'ju k\u00ebrkoja t\u00eb gjith\u00ebve q\u00eb ta ndalni k\u00ebt\u00eb video, t\u00eb klikoni n\u00eb ikon\u00ebn n\u00eb pjes\u00ebn e poshtme t\u00eb majt\u00eb, ku shkruan Konsulent Rrjeti, t\u00eb shkoni n\u00eb faqen ton\u00eb t\u00eb Facebook-ut dhe t\u00eb na jepni nj\u00eb like. Pastaj kthehuni n\u00eb video dhe klikoni n\u00eb ikon\u00ebn King n\u00eb k\u00ebndin e posht\u00ebm t\u00eb djatht\u00eb p\u00ebr t\u00eb u abonuar n\u00eb kanalin ton\u00eb zyrtar n\u00eb YouTube. Ne vazhdimisht shtojm\u00eb serit\u00eb e reja, aktualisht kemi t\u00eb b\u00ebjm\u00eb me kursin CCNA, pastaj planifikojm\u00eb t\u00eb fillojm\u00eb kursin e video-leksioneve CCNA Security, Network+, PMP, ITIL, Prince2 dhe t\u00eb publikojm\u00eb k\u00ebto serira t\u00eb mrekullueshme n\u00eb kanalin ton\u00eb. <\/p>\n

Sot do t\u00eb flasim p\u00ebr bazat e VLAN dhe do t\u00eb p\u00ebrgjigjemi n\u00eb 3 pyetje: \u00c7far\u00eb \u00ebsht\u00eb VLAN, p\u00ebrse na nevojitet VLAN dhe si ta konfigurojm\u00eb at\u00eb. Shpresoj q\u00eb pas shikimit t\u00eb k\u00ebtij video-leksioni t\u00eb jeni n\u00eb gjendje t\u00eb p\u00ebrgjigjeni n\u00eb t\u00eb tri pyetjet.<\/a><\/noindex><\/p>\n

\u00c7far\u00eb \u00ebsht\u00eb VLAN? VLAN \u00ebsht\u00eb nj\u00eb akronim p\u00ebr \"rrjetin lokal virtual\". N\u00eb vazhdim t\u00eb m\u00ebsimit ton\u00eb do ta shqyrtojm\u00eb se pse ky rrjet \u00ebsht\u00eb virtual, por para se t\u00eb kalojm\u00eb te VLAN, na nevojitet t\u00eb kuptojm\u00eb si funksionon swit\u00e7i. Do t'i rib\u00ebjm\u00eb disa nga pyetjet q\u00eb diskutuam n\u00eb leksionet e m\u00ebparshme. <\/p>\n

\"Trajnimi
\n
\nS\u00eb pari, le t\u00eb diskutojm\u00eb se \u00e7far\u00eb \u00ebsht\u00eb Multiple Collision Domain, ose domen kolizioni. Ne e dim\u00eb se ky swit\u00e7 me 48 porta ka 48 domen kolizioni. Kjo do t\u00eb thot\u00eb se \u00e7do nj\u00eb nga k\u00ebto porta ose pajisje t\u00eb lidhura me k\u00ebto porta mund t\u00eb bashk\u00ebveproj\u00eb me nj\u00eb pajisje tjet\u00ebr n\u00eb nj\u00eb port tjet\u00ebr n\u00eb m\u00ebnyr\u00eb t\u00eb pavarur, pa ndikuar nj\u00ebra-tjetr\u00ebn.<\/p>\n

T\u00eb gjith\u00eb 48 portat e k\u00ebtij swit\u00e7i jan\u00eb pjes\u00eb e nj\u00eb domeni t\u00eb transmetimit t\u00eb gjer\u00eb, ose Broadcast Domain. Kjo do t\u00eb thot\u00eb se n\u00ebse disa pajisje jan\u00eb t\u00eb lidhura me disa porta dhe nj\u00ebra prej tyre b\u00ebn nj\u00eb transmetim t\u00eb gjer\u00eb, at\u00ebher\u00eb ai do t\u00eb shfaqet n\u00eb t\u00eb gjitha portat t\u00eb cilat jan\u00eb lidhur me pajisjet e tjera. K\u00ebshtu funksionon swit\u00e7i.<\/p>\n

Kjo \u00ebsht\u00eb sikur njer\u00ebzit t\u00eb ishin ulur n\u00eb nj\u00eb dhom\u00eb af\u00ebr nj\u00ebri-tjetrit, dhe kur nj\u00eb nga ta flet me z\u00eb t\u00eb lart\u00eb, t\u00eb gjith\u00eb t\u00eb tjer\u00ebt e d\u00ebgjojn\u00eb at\u00eb. Megjithat\u00eb, kjo \u00ebsht\u00eb shum\u00eb e paefektshme \u2013 sa m\u00eb shum\u00eb njer\u00ebz t\u00eb shfaqen n\u00eb dhom\u00eb, aq m\u00eb e fort\u00eb do t\u00eb b\u00ebhet zhurma dhe ata n\u00eb mes nuk do t\u00eb d\u00ebgjojn\u00eb nj\u00ebri-tjetrin. Nj\u00eb situat\u00eb e ngjashme ndodh me kompjuter\u00ebt \u2013 sa m\u00eb shum\u00eb pajisje q\u00eb lidhen me nj\u00eb rrjet, aq m\u00eb e lart\u00eb b\u00ebhet \"z\u00ebri\" i transmetimit t\u00eb gjer\u00eb, duke mos lejuar q\u00eb lidhja t\u00eb b\u00ebhet efektive. <\/p>\n

Ne e di\u00e7ka q\u00eb e dim\u00eb se n\u00ebse nj\u00eb nga k\u00ebto pajisje \u00ebsht\u00eb e lidhur me rrjetin 192.168.1.0\/24, t\u00eb gjitha pajisjet e tjera jan\u00eb pjes\u00eb e k\u00ebtij rrjeti. Switch-i gjithashtu duhet t\u00eb jet\u00eb i lidhur me nj\u00eb rrjet me t\u00eb nj\u00ebjtin IP adres\u00eb. Por k\u00ebtu switch-i si pajisje n\u00eb nivelin 2 t\u00eb OSI mund t\u00eb has\u00eb nj\u00eb problem. N\u00ebse dy pajisje jan\u00eb t\u00eb lidhura me nj\u00eb rrjet t\u00eb nj\u00ebjt\u00eb, ato mund t\u00eb lidhin leht\u00ebsisht me kompjuter\u00ebt e nj\u00ebra-tjetr\u00ebs. Le t\u00eb supozojm\u00eb se n\u00eb kompanin\u00eb ton\u00eb punon nj\u00eb \"djal\u00eb i keq\", nj\u00eb haker, q\u00eb e pikturoj lart. Posht\u00eb tij \u00ebsht\u00eb kompjuteri im. Epo, ky haker ka shum\u00eb leht\u00ebsi p\u00ebr t\u00eb hyr\u00eb n\u00eb kompjuterin tim, pasi kompjuter\u00ebt tan\u00eb jan\u00eb pjes\u00eb e nj\u00ebjtit rrjet. K\u00ebtu q\u00ebndron problemi. <\/p>\n

\"Trajnimi
\n
\nN\u00ebse un\u00eb i p\u00ebrkas menaxhmentit administrativ, dhe ky djal\u00eb i ri arrin t\u00eb ket\u00eb qasje n\u00eb skedar\u00ebt n\u00eb kompjuterin tim, nuk do t\u00eb ishte aspak mir\u00eb. Sigurisht, kompjuteri im ka nj\u00eb firewall q\u00eb mbron nga shum\u00eb k\u00ebrc\u00ebnime, por hakerit nuk do t'i duhej shum\u00eb p\u00ebr ta tejkaluar at\u00eb. <\/p>\n

Rreziku tjet\u00ebr q\u00eb ekziston p\u00ebr t\u00eb gjith\u00eb ata q\u00eb jan\u00eb an\u00ebtar\u00eb t\u00eb k\u00ebtij domeni t\u00eb transmetimit t\u00eb gjer\u00eb \u00ebsht\u00eb se n\u00ebse dikush ka probleme me transmetimin e gjer\u00eb, kjo nd\u00ebrhyrje do t\u00eb ndikoj\u00eb n\u00eb pajisjet e tjera t\u00eb rrjetit. Megjith\u00ebse t\u00eb 48 portat mund t\u00eb jen\u00eb t\u00eb lidhura me hoste t\u00eb ndrysh\u00ebm, nj\u00eb d\u00ebshtim n\u00eb funksionimin e nj\u00eb hosti do t\u00eb ndikoj\u00eb n\u00eb 47 t\u00eb tjer\u00ebt, gj\u00eb q\u00eb nuk na nevojitet aspak.
\nP\u00ebr t\u00eb zgjidhur k\u00ebt\u00eb problem ne p\u00ebrdorim konceptin e VLAN, ose rrjetin lokal virtual. Ai funksionon shum\u00eb thjesht\u00eb, duke e ndar\u00eb k\u00ebt\u00eb switch t\u00eb madh 48-port\u00ebsh n\u00eb disa switch-e m\u00eb t\u00eb vogla. <\/p>\n

\"Trajnimi
\n
\nE dim\u00eb se subnetet ndajn\u00eb nj\u00eb rrjet t\u00eb madh n\u00eb disa rrjete m\u00eb t\u00eb vogla, dhe VLAN funksionon n\u00eb m\u00ebnyr\u00eb t\u00eb ngjashme. Ajo e ndan switch-in 48-port\u00ebsh, p\u00ebr shembull, n\u00eb 4 switch-e me nga 12 port, secili prej t\u00eb cil\u00ebve \u00ebsht\u00eb pjes\u00eb e nj\u00eb rrjeti t\u00eb ri t\u00eb lidhur. N\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, ne mund t\u00eb p\u00ebrdorim 12 porta p\u00ebr menaxhim, 12 porta p\u00ebr pun\u00eb me telefonin\u00eb IP dhe k\u00ebshtu me radh\u00eb, dmth t\u00eb ndajm\u00eb switch-in jo fizikisht, por logjikisht, virtulisht. <\/p>\n

Kam\u00eb kam ndar\u00eb tre porte t\u00eb switch-it t\u00eb sip\u00ebrm, t\u00eb sh\u00ebnuara me ngjyr\u00eb blu, p\u00ebr rrjetin \"blu\" VLAN10, dhe tre porte t\u00eb portokallta p\u00ebr VLAN20. K\u00ebshtu, \u00e7do trafik nga nj\u00eb prej k\u00ebtyre porteve blu do t\u00eb shkoj\u00eb vet\u00ebm n\u00eb porte t\u00eb tjera blu, pa prekur portet e tjera t\u00eb k\u00ebtij switch-i. N\u00eb t\u00eb nj\u00ebjt\u00ebn m\u00ebnyr\u00eb, trafiku nga portet portokallta do t\u00eb shp\u00ebrndahet, dmth ne duket se po p\u00ebrdorim dy switch-e fizikisht t\u00eb ndrysh\u00ebm. Prandaj, VLAN \u00ebsht\u00eb nj\u00eb m\u00ebnyr\u00eb p\u00ebr t\u00eb ndar\u00eb switch-in n\u00eb disa switch-e p\u00ebr rrjete t\u00eb ndryshme. <\/p>\n

Kam vizatuar lart dy switch-e, ku kemi nj\u00eb situat\u00eb kur n\u00eb switch-in e majt\u00eb jan\u00eb angazhuar lidhjet vet\u00ebm nga portet blu p\u00ebr nj\u00eb rrjet, nd\u00ebrsa n\u00eb t\u00eb djatht\u00ebn jan\u00eb vet\u00ebm portet portokalle p\u00ebr nj\u00eb rrjet tjet\u00ebr, dhe k\u00ebto switch-e nuk jan\u00eb lidhur me nj\u00ebri-tjetrin. <\/p>\n

Supozoni se d\u00ebshironi t\u00eb angazhoni m\u00eb shum\u00eb porte. Le t\u00eb imagjinojm\u00eb se kemi 2 nd\u00ebrtesa, \u00e7do nj\u00ebra me stafin e saj menaxhues, dhe dy porte portokalle t\u00eb switch-it t\u00eb posht\u00ebm p\u00ebrdoren p\u00ebr menaxhimin. Prandaj, na nevojitet q\u00eb k\u00ebto porte t\u00eb lidh\u00ebn me t\u00eb gjitha portet portokalle t\u00eb switch-eve t\u00eb tjera. Situata \u00ebsht\u00eb e ngjashme me portet blu \u2013 t\u00eb gjitha portet blu t\u00eb switch-it t\u00eb sip\u00ebrm duhet t\u00eb ken\u00eb lidhje me portet e tjera t\u00eb ngjashme. P\u00ebr k\u00ebt\u00eb, na nevojitet q\u00eb t\u00eb lidhim fizikisht k\u00ebto dy switch-e n\u00eb nd\u00ebrtesa t\u00eb ndryshme me nj\u00eb linj\u00eb lidhjeje t\u00eb ve\u00e7ant\u00eb, si\u00e7 \u00ebsht\u00eb linja midis dy porteve t\u00eb gjelb\u00ebrta n\u00eb vizatim. Si\u00e7 e dim\u00eb, n\u00ebse dy switch-e jan\u00eb t\u00eb lidhur fizikisht, krijohet nj\u00eb magistral\u00eb, ose trunk. <\/p>\n

Cili \u00ebsht\u00eb diferenca midis nj\u00eb switchi standard dhe nj\u00eb switchi VLAN? Nuk ka ndonj\u00eb ndryshim t\u00eb madh. Kur blini nj\u00eb switch t\u00eb ri, t\u00eb gjitha portet jan\u00eb t\u00eb konfiguruara n\u00eb modalitetin VLAN dhe b\u00ebjn\u00eb pjes\u00eb n\u00eb nj\u00eb rrjet, i quajtur VLAN1, si\u00e7 \u00ebsht\u00eb standarde. Prandaj, kur lidhni nj\u00eb pajisje n\u00eb nj\u00eb port, ajo lidhet me t\u00eb gjith\u00eb portet e tjera, sepse t\u00eb 48 portet i p\u00ebrkasin nj\u00eb rrjeti virtual VLAN1. Por n\u00ebse konfiguroni portet blu t\u00eb punojn\u00eb n\u00eb rrjetin VLAN10, portet portokalli n\u00eb rrjetin VLAN20 dhe portet e gjelbra n\u00eb VLAN1, at\u00ebher\u00eb kemi 3 switch-e t\u00eb ndrysh\u00ebm. K\u00ebshtu, p\u00ebrdorimi i modalitetit t\u00eb rrjetit virtual na lejon t\u00eb grupojm\u00eb logjikisht portet sipas rrjeteve specifike, t\u00eb ndarim transmetimin e transmetimeve t\u00eb gjera n\u00eb pjes\u00eb dhe t\u00eb krijojm\u00eb subnet-e. K\u00ebshtu, \u00e7do port i nj\u00eb ngjyre t\u00eb caktuar i p\u00ebrket nj\u00eb rrjeti t\u00eb ve\u00e7ant\u00eb. N\u00ebse portet blu punojn\u00eb n\u00eb rrjetin 192.168.1.0 dhe portet portokalli n\u00eb rrjetin 192.168.1.0, at\u00ebher\u00eb megjith\u00ebse kan\u00eb adres\u00ebn IP t\u00eb nj\u00ebjt\u00eb, ato nuk do t\u00eb lidheshin me nj\u00ebra-tjetr\u00ebn, sepse do t\u00eb p\u00ebrkisnin logjikisht n\u00eb switch-e t\u00eb ndrysh\u00ebm. Si\u00e7 e dim\u00eb, switch-et e ndrysh\u00ebm fizikisht nuk komunikohet me nj\u00ebri-tjetrin, n\u00ebse nuk jan\u00eb t\u00eb lidhur me nj\u00eb linj\u00eb t\u00eb p\u00ebrbashk\u00ebt komunikimi. K\u00ebshtu, krijojm\u00eb subnet-e t\u00eb ndryshme p\u00ebr VLAN t\u00eb ndrysh\u00ebm. <\/p>\n

\"Trajnimi
\n
\nDua t\u00eb theksoj se koncepti i VLAN zgjerohet vet\u00ebm n\u00eb switch-e. Ai q\u00eb \u00ebsht\u00eb njohur me protokollet e inkapsulimit, si\u00e7 jan\u00eb .1Q ose ISL, di se as rrutat as kompjuter\u00ebt nuk kan\u00eb VLAN. Kur lidhni kompjuterin tuaj n\u00eb nj\u00eb nga portet blu, p\u00ebr shembull, nuk b\u00ebni asnj\u00eb ndryshim n\u00eb kompjuter, t\u00eb gjitha ndryshimet ndodhin vet\u00ebm n\u00eb nivelin e dyt\u00eb OSI, nivelin e switch-it. Kur konfiguroni portet p\u00ebr t\u00eb punuar me nj\u00eb rrjet specifik VLAN10 ose VLAN20, switch-i krijon nj\u00eb baz\u00eb t\u00eb dh\u00ebnash VLAN. Ai \"shkruan\" n\u00eb kujtes\u00ebn e tij se portet 1, 3 dhe 5 i p\u00ebrkasin VLAN10, portet 14, 15 dhe 18 jan\u00eb pjes\u00eb e rrjetit VLAN20, nd\u00ebrsa portet e tjera t\u00eb angazhuara jan\u00eb pjes\u00eb e rrjetit VLAN1. Prandaj, n\u00ebse ndonj\u00eb trafik buron nga porta blu 1, ai arrin vet\u00ebm n\u00eb portet 3 dhe 5 t\u00eb k\u00ebtij rrjeti VLAN10. Switch-i \"shikon\" n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave t\u00eb tij dhe sheh se n\u00ebse trafiku buron nga ndonj\u00eb nga portet portokalli, ai duhet t\u00eb shkoj\u00eb vet\u00ebm n\u00eb portet portokalli t\u00eb rrjetit VLAN20. <\/p>\n

Megjithat\u00eb, kompjuteri nuk di asgj\u00eb p\u00ebr k\u00ebto rrjete VLAN. Kur lidhim 2 switch-e, krijohet nj\u00eb trunk midis porteve t\u00eb gjelbra. Termi \"trunk\" \u00ebsht\u00eb i r\u00ebnd\u00ebsish\u00ebm vet\u00ebm p\u00ebr pajisjet e kompanis\u00eb Cisco, nd\u00ebrsa prodhuesit e tjer\u00eb t\u00eb pajisjeve rrjetore, si Juniper, p\u00ebrdorin termin Tag port, ose \"port i etiketuar\". Un\u00eb mendoj se emri Tag port \u00ebsht\u00eb m\u00eb i p\u00ebrshtatsh\u00ebm. Kur nga kjo rrjet del trafiku, trunk e kalon at\u00eb n\u00eb t\u00eb gjitha portet e switch-it tjet\u00ebr, duke e lidhur dy switch-e me 48 porte dhe duke marr\u00eb nj\u00eb switch me 96 porte. N\u00eb k\u00ebt\u00eb rast, kur d\u00ebrgojm\u00eb trafikun nga VLAN10, ai b\u00ebhet i etiketuar, pra merr nj\u00eb etiket\u00eb q\u00eb tregon se \u00ebsht\u00eb dedikuar vet\u00ebm p\u00ebr portet e rrjetit VLAN10. Switch-i i dyt\u00eb, pasi merr k\u00ebt\u00eb trafik, lexon etiket\u00ebn dhe kupton se ky \u00ebsht\u00eb trafik p\u00ebr rrjetin VLAN10 dhe duhet t\u00eb shkoj\u00eb vet\u00ebm n\u00eb portet blu. Po ashtu, trafiku \"portokalli\" p\u00ebr VLAN20 ka nj\u00eb etiket\u00eb q\u00eb tregon se ai \u00ebsht\u00eb dedikuar p\u00ebr portet VLAN20 t\u00eb switch-it t\u00eb dyt\u00eb. <\/p>\n

Ne gjithashtu p\u00ebrmend\u00ebm inkapsulimin, dhe k\u00ebtu ka dy metoda inkapsulimi. E para \u00ebsht\u00eb .1Q, q\u00eb do t\u00eb thot\u00eb se kur organizojm\u00eb nj\u00eb trunk, duhet t\u00eb sigurojm\u00eb inkapsulim. Protokolli i inkapsulimit .1Q \u00ebsht\u00eb nj\u00eb standard i hapur, q\u00eb p\u00ebrshkruan procedur\u00ebn e etiketimit t\u00eb trafikut. Ekziston edhe nj\u00eb protokoll tjet\u00ebr i quajtur ISL, Inter-Switch Link, i zhvilluar nga Cisco, q\u00eb tregon p\u00ebrkat\u00ebsin\u00eb e trafikut n\u00eb nj\u00eb VLAN t\u00eb caktuar. T\u00eb gjith\u00eb switch-et modern\u00eb punojn\u00eb me protokollin .1Q, k\u00ebshtu q\u00eb, kur e merrni nj\u00eb switch t\u00eb ri nga kutia, nuk keni nevoj\u00eb t\u00eb p\u00ebrdorni komandat e inkapsulimit, sepse n\u00eb parimin e tij, inkapsulimi realizohet nga protokolli .1Q. K\u00ebshtu, pas krijimit t\u00eb trunk-ut, inkapsulimi i trafikut ndodh automatikisht, duke lejuar leximin e etiketave. <\/p>\n

Tani le t\u00eb fillojm\u00eb t\u00eb konfigurojm\u00eb rrjetin VLAN. Do t\u00eb krijojm\u00eb nj\u00eb rrjet, ku do t\u00eb ket\u00eb 2 switch-e dhe dy pajisje p\u00ebrfundimtare \u2013 kompjuter\u00ebt PC1 dhe PC2, t\u00eb cilat do t'i lidhim me kabuj me switch-in #0. T\u00eb fillojm\u00eb me cil\u00ebsimet bazike t\u00eb switch-it, Konfigurimi Baz\u00eb.<\/p>\n

\"Trajnimi
\n
\nP\u00ebr k\u00ebt\u00eb, do t\u00eb klikojm\u00eb mbi switch-in dhe do t\u00eb hyjm\u00eb n\u00eb nd\u00ebrfaqen e komandave dhe pastaj do t\u00eb caktojm\u00eb emrin e hostit, duke e quajtur k\u00ebt\u00eb switch sw1. Tani do t\u00eb kalojm\u00eb te cil\u00ebsimet e kompjuterit t\u00eb par\u00eb dhe do t\u00eb caktojm\u00eb nj\u00eb adres\u00eb IP statike 192.168.1.1 dhe mask\u00ebn e n\u00ebnrrjetit 255.255.255.0. Adresa e der\u00ebs s\u00eb zakonshme nuk \u00ebsht\u00eb e nevojshme, sepse t\u00eb gjitha pajisjet tona ndodhen n\u00eb t\u00eb nj\u00ebjt\u00ebn rrjet. M\u00eb pas, ne do t\u00eb b\u00ebjm\u00eb t\u00eb nj\u00ebjt\u00ebn gj\u00eb p\u00ebr kompjuterin e dyt\u00eb, duke i caktuar nj\u00eb adres\u00eb IP 192.168.1.2. <\/p>\n

Tani kthehemi te kompjuteri i par\u00eb p\u00ebr t\u00eb pinguar kompjuterin e dyt\u00eb. Si\u00e7 e shohim, pingimi arriti sukses sepse t\u00eb dy k\u00ebta kompjuter\u00eb jan\u00eb t\u00eb lidhur me t\u00eb nj\u00ebjtin switch dhe jan\u00eb pjes\u00eb e t\u00eb nj\u00ebjtit rrjet t\u00eb zakonsh\u00ebm VLAN1. N\u00ebse tani shohim nd\u00ebrfaqet e switch-it, do t\u00eb shohim q\u00eb t\u00eb gjitha portet FastEthernet nga 1 deri n\u00eb 24 dhe dy portet GigabitEthernet jan\u00eb konfiguruar p\u00ebr VLAN #1. Megjithat\u00eb, nj\u00eb disponueshm\u00ebri e till\u00eb e tep\u00ebrt nuk \u00ebsht\u00eb e nevojshme, prandaj hyjm\u00eb n\u00eb cil\u00ebsimet e switch-it dhe fusim komand\u00ebn show vlan, p\u00ebr t\u00eb par\u00eb baz\u00ebn e t\u00eb dh\u00ebnave t\u00eb rrjeteve virtuale. <\/p>\n

\"Trajnimi
\n
\nK\u00ebtu shihni emrin e rrjetit VLAN1 dhe se t\u00eb gjitha portet e switch-it i p\u00ebrkasin k\u00ebtij rrjeti. Kjo do t\u00eb thot\u00eb se mund t\u00eb lidheni me \u00e7do port dhe t\u00eb gjith\u00eb ata do t\u00eb mund t\u00eb \"komunikohet\" mes tyre, sepse jan\u00eb pjes\u00eb e t\u00eb nj\u00ebjtit rrjet.<\/p>\n

Ne do ta ndryshojm\u00eb k\u00ebt\u00eb situat\u00eb, p\u00ebr k\u00ebt\u00eb fillimisht do t\u00eb krijojm\u00eb dy rrjete virtuale, pra do t\u00eb shtojm\u00eb VLAN10. P\u00ebr t\u00eb krijuar nj\u00eb rrjet virtual p\u00ebrdoret komanda e formatit \"vlan numri i rrjetit\".
\nSi\u00e7 e shihni, gjat\u00eb p\u00ebrpjekjes p\u00ebr t\u00eb krijuar rrjetin, sistemi dha nj\u00eb mesazh me nj\u00eb list\u00eb komandash konfigurimi VLAN q\u00eb duhen p\u00ebrdorur p\u00ebr k\u00ebt\u00eb veprimin: <\/p>\n

exit \u2013 zbato ndryshimet dhe dil nga cil\u00ebsimet;
\nname \u2013 fut emrin e p\u00ebrdoruesit p\u00ebr VLAN;
\nno \u2013 anulo komand\u00ebn ose vendose at\u00eb n\u00eb parazgjedhje. <\/p>\n

Kjo do t\u00eb thot\u00eb se para se t\u00eb fusni komand\u00ebn p\u00ebr t\u00eb krijuar VLAN, duhet t\u00eb futni komand\u00ebn name, e cila aktivizon modin e menaxhimit t\u00eb emrave, dhe pastaj t\u00eb kaloni n\u00eb krijimin e nj\u00eb rrjeti t\u00eb ri. Gjat\u00eb k\u00ebsaj kohe, sistemi jep nj\u00eb sugjerim se numri i rrjetit VLAN mund t\u00eb caktohet brenda gam\u00ebs nga 1 deri n\u00eb 1005.
\nPra, tani ne fusim komand\u00ebn p\u00ebr t\u00eb krijuar nj\u00eb rrjet VLAN me numrin 20 \u2013 vlan 20, dhe pastaj i caktojm\u00eb nj\u00eb em\u00ebr p\u00ebr p\u00ebrdoruesin q\u00eb tregon se \u00e7far\u00eb lloji rrjeti \u00ebsht\u00eb. N\u00eb rastin ton\u00eb, p\u00ebrdorim komand\u00ebn name Employees, ose rrjeti p\u00ebr punonj\u00ebsit e kompanis\u00eb. <\/p>\n

\"Trajnimi
\n
\nTani \u00ebsht\u00eb e nevojshme t\u00eb em\u00ebrojm\u00eb nj\u00eb port specifik p\u00ebr k\u00ebt\u00eb VLAN. Ne hyjm\u00eb n\u00eb modalitetin e konfigurimit t\u00eb switch-it int f0\/1, pastaj e \u00e7ojm\u00eb manualisht portin n\u00eb modalitetin Access me komand\u00ebn switchport mode access dhe p\u00ebrcaktojm\u00eb se cili port duhet t\u00eb kaloj\u00eb n\u00eb k\u00ebt\u00eb modalitet - ky \u00ebsht\u00eb porti p\u00ebr rrjetin VLAN10. <\/p>\n

\"Trajnimi
\n
\nNe shohim se pas k\u00ebsaj, ngjyra e pik\u00ebs s\u00eb lidhjes PC0 dhe switch-it, ngjyra e portit, ndryshoi nga e gjelb\u00ebr n\u00eb portokalli. Ai do t\u00eb b\u00ebhet s\u00ebrish i gjelb\u00ebr sapo ndryshimet e konfigurimit t\u00eb hyjn\u00eb n\u00eb fuqi. Do t\u00eb mundohemi ta pingojm\u00eb kompjuterin e dyt\u00eb. Ne nuk b\u00ebm\u00eb ndonj\u00eb ndryshim n\u00eb konfigurimin e rrjetit p\u00ebr kompjuter\u00ebt, ata ende kan\u00eb adresat IP 192.168.1.1 dhe 192.168.1.2. Por n\u00ebse p\u00ebrpiqemi nga kompjuteri PC0 t\u00eb pingojm\u00eb kompjuterin PC1, nuk do t\u00eb arrijm\u00eb asgj\u00eb, sepse tani k\u00ebta kompjuter\u00eb i p\u00ebrkasin rrjeteve t\u00eb ndryshme: i pari t\u00eb VLAN10, i dyti - t\u00eb VLAN1 native. <\/p>\n

Le t\u00eb kthehemi te nd\u00ebrfaqja e switch-it dhe t\u00eb konfigurojm\u00eb portin e dyt\u00eb. P\u00ebr k\u00ebt\u00eb, un\u00eb do t\u00eb p\u00ebrdor komand\u00ebn int f0\/2 dhe do t\u00eb p\u00ebrs\u00ebris p\u00ebr rrjetin VLAN 20 hap pas hapi t\u00eb nj\u00ebjtat q\u00eb kemi b\u00ebr\u00eb p\u00ebr rrjetin virtual t\u00eb m\u00ebparsh\u00ebm.
\nNe shohim se tani porti i posht\u00ebm i switch-it, t\u00eb cilit i \u00ebsht\u00eb lidhur kompjuteri i dyt\u00eb, gjithashtu ndryshoi ngjyr\u00ebn e tij nga e gjelb\u00ebr n\u00eb portokalli - duhet t\u00eb kalojn\u00eb disa sekonda para se ndryshimet n\u00eb konfigurim t\u00eb hyjn\u00eb n\u00eb fuqi dhe ai t\u00eb b\u00ebhet s\u00ebrish i gjelb\u00ebr. N\u00ebse e fillojm\u00eb s\u00ebrish pingimin e kompjuterit t\u00eb dyt\u00eb, nuk do t\u00eb arrijm\u00eb asgj\u00eb, sepse kompjuter\u00ebt ende i p\u00ebrkasin rrjeteve t\u00eb ndryshme, vet\u00ebm se tani PC1 \u00ebsht\u00eb pjes\u00eb e VLAN20 dhe jo m\u00eb e VLAN1.
\nN\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, ju ndat\u00eb nj\u00eb switch fizik n\u00eb dy switch-e logjik\u00eb t\u00eb ndryshme. Ju shihni se tani ngjyra e portit ndryshoi nga portokalli n\u00eb t\u00eb gjelb\u00ebr, porti filloi t\u00eb funksionoj\u00eb, por ende nuk pingon, sepse i p\u00ebrket nj\u00eb rrjeti tjet\u00ebr. <\/p>\n

T\u00eb b\u00ebjm\u00eb disa ndryshime n\u00eb diagramin ton\u00eb - do ta \u00e7m\u00ebngjisim kompjuterin PC1 nga switch-i i par\u00eb dhe do ta lidhim me switch-in e dyt\u00eb, nd\u00ebrsa ne do t'i lidhim switch-at me nj\u00eb kabllo.<\/p>\n

\"Trajnimi
\n
\nP\u00ebr t\u00eb vendosur lidhjen nd\u00ebrmjet tyre, do t\u00eb hyj n\u00eb cil\u00ebsimet e switch-it t\u00eb dyt\u00eb dhe do t\u00eb krijoj VLAN10, duke i dh\u00ebn\u00eb emrin Menaxhimi, q\u00eb do t\u00eb thot\u00eb rrjeti i menaxhimit. Pastaj do ta aktivizoj modalitetin Access dhe do t\u00eb caktoj se ky modalitet \u00ebsht\u00eb p\u00ebr rrjetin VLAN10. Tani ngjyra e porteve, p\u00ebrmes t\u00eb cilave jan\u00eb lidhur switch-\u00ebt, ndryshoi nga portokalli n\u00eb jeshile, sepse t\u00eb dy jan\u00eb t\u00eb konfiguruar p\u00ebr VLAN10. Tani na nevojitet t\u00eb krijojm\u00eb nj\u00eb trunk nd\u00ebrmjet t\u00eb dy switch-\u00ebve. T\u00eb dy k\u00ebto porta jan\u00eb Fa0\/2, prandaj duhet t\u00eb krijojm\u00eb nj\u00eb trunk p\u00ebr portin Fa0\/2 t\u00eb switch-it t\u00eb par\u00eb, duke p\u00ebrdorur komand\u00ebn switchport mode trunk. E nj\u00ebjta gj\u00eb duhet t\u00eb b\u00ebhet p\u00ebr switch-in e dyt\u00eb, pas s\u00eb cil\u00ebs do t\u00eb formohet nj\u00eb trunk nd\u00ebrmjet k\u00ebtyre dy porteve.<\/p>\n

Tani, n\u00ebse d\u00ebshiroj t\u00eb pingoj nga kompjuteri i par\u00eb kompjuterin PC1, gjith\u00e7ka do t\u00eb shkoj\u00eb mir\u00eb, sepse lidhja nd\u00ebrmjet PC0 dhe switch-it #0 \u00ebsht\u00eb rrjeti VLAN10, nd\u00ebrmjet switch-it #1 dhe PC1 gjithashtu VLAN10, dhe t\u00eb dy switch-\u00ebt jan\u00eb t\u00eb lidhur me nj\u00eb trunk. <\/p>\n

Pra, n\u00ebse pajisjet ndodhen n\u00eb rrjete t\u00eb ndryshme VLAN, ato nuk jan\u00eb t\u00eb lidhura me nj\u00ebra-tjetr\u00ebn, nd\u00ebrsa n\u00ebse ndodhen n\u00eb nj\u00eb rrjet, at\u00ebher\u00eb mund t\u00eb realizohet shk\u00ebmbimi i lir\u00eb i trafikut nd\u00ebrmjet tyre. Le t\u00eb p\u00ebrpiqemi t\u00eb shtojm\u00eb nj\u00eb pajisje tjet\u00ebr n\u00eb secilin switch. <\/p>\n

\"Trajnimi
\n
\nN\u00eb konfigurimin rrjetor t\u00eb kompjuterit t\u00eb shtuar PC2, do t\u00eb vendos ip adres\u00ebn 192.168.2.1, dhe n\u00eb konfigurimin e PC3 \u2013 adres\u00ebn 192.168.2.2. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, portet ku lidhen k\u00ebto dy PC do t\u00eb ken\u00eb emrin Fa0\/3. N\u00eb konfigurimin e switch-it #0, do ta vendosim modalitetin Access dhe do t\u00eb caktojm\u00eb se ky port \u00ebsht\u00eb p\u00ebr VLAN20, dhe e nj\u00ebjta do t\u00eb b\u00ebhet p\u00ebr switch-in #1.<\/p>\n

N\u00ebse p\u00ebrdor komand\u00ebn switchport access vlan 20, dhe rrjeti VLAN20 ende nuk \u00ebsht\u00eb krijuar, sistemi do t\u00eb jap\u00eb nj\u00eb gabim t\u00eb tipit \"Access VLAN does not exist\", sepse switch-\u00ebt jan\u00eb t\u00eb konfiguruar vet\u00ebm p\u00ebr t\u00eb punuar me VLAN10.<\/p>\n

Le t\u00eb krijojm\u00eb VLAN20. Do t\u00eb p\u00ebrdor komand\u00ebn \"show vlan\" p\u00ebr t\u00eb shqyrtuar baz\u00ebn e t\u00eb dh\u00ebnave t\u00eb rrjeteve virtuale. <\/p>\n

\"Trajnimi
\n
\nShihni, rrjeti i paracaktuar \u00ebsht\u00eb VLAN1, n\u00eb t\u00eb cilin jan\u00eb t\u00eb lidhur portet nga Fa0\/4 deri n\u00eb Fa0\/24 dhe Gig0\/1, Gig0\/2. Rrjeti virtual me num\u00ebr 10 me emrin Menaxhimi \u00ebsht\u00eb i lidhur n\u00eb portin Fa0\/1, nd\u00ebrsa rrjeti VLAN me num\u00ebr 20 me emrin e paracaktuar VLAN0020 lidhet n\u00eb portin Fa0\/3. <\/p>\n

N\u00eb parim, emri i rrjetit nuk ka r\u00ebnd\u00ebsi, r\u00ebnd\u00ebsi ka q\u00eb ai t\u00eb mos p\u00ebrs\u00ebritet p\u00ebr rrjete t\u00eb ndryshme. N\u00ebse dua t\u00eb ndryshoj emrin e rrjetit, q\u00eb sistemi i cakton nga ana default, p\u00ebrdor komand\u00ebn vlan 20 dhe name Employees. Mund ta ndryshoj k\u00ebt\u00eb em\u00ebr p\u00ebr n\u00eb nj\u00eb tjet\u00ebr, p\u00ebr shembull n\u00eb IPphones, dhe n\u00ebse pingojm\u00eb adres\u00ebn IP 192.168.2.2, do t\u00eb shohim se emri i VLAN-it nuk ka asnj\u00eb r\u00ebnd\u00ebsi.
\nE fundit q\u00eb dua t\u00eb p\u00ebrmend \u00ebsht\u00eb caktimi i Management IP, p\u00ebr t\u00eb cilin fol\u00ebm n\u00eb m\u00ebsimin e fundit. P\u00ebr k\u00ebt\u00eb, p\u00ebrdorim komand\u00ebn int vlan1 dhe futim adres\u00ebn IP 10.1.1.1 dhe mask\u00ebn e n\u00ebnshtres\u00ebs 255.255.255.0, dhe pastaj shtojm\u00eb komand\u00ebn no shutdown. Ne caktuam Management IP-n\u00eb jo p\u00ebr t\u00eb gjith\u00eb switch-in, por vet\u00ebm p\u00ebr portet VLAN1, q\u00eb do t\u00eb thot\u00eb se kemi caktuar nj\u00eb adres\u00eb IP nga e cila b\u00ebhet menaxhimi i rrjetit VLAN1. N\u00ebse duam t\u00eb menaxhojm\u00eb VLAN2, duhet t\u00eb krijojm\u00eb nj\u00eb nd\u00ebrfaqe p\u00ebrkat\u00ebse p\u00ebr VLAN2. N\u00eb rastin ton\u00eb kemi porte blu VLAN10 dhe porte portokalli VLAN20, t\u00eb cilave iu p\u00ebrkasin adresat 192.168.1.0 dhe 192.168.2.0.
\nVLAN10 duhet t\u00eb ket\u00eb adresa q\u00eb ndodhen brenda k\u00ebtij diapazoni, n\u00eb m\u00ebnyr\u00eb q\u00eb pajisjet p\u00ebrkat\u00ebse t\u00eb mund t\u00eb lidheshin me t\u00eb. Nj\u00eb konfigurim i ngjash\u00ebm duhet t\u00eb b\u00ebhet edhe p\u00ebr VLAN20. <\/p>\n

N\u00eb k\u00ebt\u00eb dritare t\u00eb komand\u00ebs s\u00eb switch-it jan\u00eb treguar cil\u00ebsimet e nd\u00ebrfaqes p\u00ebr VLAN1, q\u00eb do t\u00eb thot\u00eb VLAN-i native. <\/p>\n

\"Trajnimi
\n
\nP\u00ebr t\u00eb konfiguruar Management IP p\u00ebr VLAN10, ne duhet t\u00eb krijojm\u00eb nd\u00ebrfaqen int vlan 10, dhe pastaj t\u00eb shtojm\u00eb adres\u00ebn IP 192.168.1.10 dhe mask\u00ebn e n\u00ebnshtres\u00ebs 255.255.255.0. <\/p>\n

P\u00ebr konfigurimin e VLAN20, ne duhet t\u00eb krijojm\u00eb nd\u00ebrfaqen int vlan 20, dhe pastaj t\u00eb shtojm\u00eb adres\u00ebn IP 192.168.2.10 dhe mask\u00ebn e n\u00ebnshtres\u00ebs 255.255.255.0. <\/p>\n

\"Trajnimi
\n
\nPse \u00ebsht\u00eb e nevojshme kjo? N\u00ebse kompjuteri PC0 dhe porti i sip\u00ebrm t\u00eb majt\u00eb i switch-it #0 i p\u00ebrkasin rrjetit 192.168.1.0, PC2 i p\u00ebrket rrjetit 192.168.2.0 dhe \u00ebsht\u00eb i lidhur me portin native VLAN1, i cili i p\u00ebrket rrjetit 10.1.1.1, at\u00ebher\u00eb PC0 nuk mund t\u00eb krijoj\u00eb marr\u00ebdh\u00ebnie me k\u00ebt\u00eb switch p\u00ebrmes protokollit SSH, sepse ata i p\u00ebrkasin rrjeteve t\u00eb ndryshme. Prandaj, q\u00eb PC0 t\u00eb mund t\u00eb lidhet me switch-in p\u00ebrmes protokollit SSH ose Telnet, ne duhet t'i ofrojm\u00eb atij akses. Kjo \u00ebsht\u00eb arsyeja pse na nevojitet menaxhimi i rrjetit. <\/p>\n

Ne duhet t\u00eb kemi mund\u00ebsin\u00eb t\u00eb lidhemi me PC0 p\u00ebrmes SSH ose Telnet me adres\u00ebn IP t\u00eb nd\u00ebrfaqes VLAN20 dhe t\u00eb b\u00ebjm\u00eb \u00e7do ndryshim q\u00eb na nevojitet p\u00ebrmes SSH. K\u00ebshtu, Management IP \u00ebsht\u00eb e nevojshme pik\u00ebrisht p\u00ebr konfigurimin e VLAN, sepse secila rrjet virtual duhet t\u00eb ket\u00eb menaxhimin e saj t\u00eb aksesit. <\/p>\n

N\u00eb videon e sotme, ne diskutuam shum\u00eb \u00e7\u00ebshtje: konfigurimet themelore t\u00eb switch-it, krijimin e rrjeteve VLAN, caktimin e porteve VLAN, caktimin e IP-s\u00eb menaxhuese p\u00ebr rrjetet VLAN dhe konfigurimin e trunk-\u00ebve. Mos u shqet\u00ebsoni n\u00ebse nuk kuptoni ndonj\u00eb gj\u00eb, \u00ebsht\u00eb normale, sepse VLAN \u00ebsht\u00eb nj\u00eb tem\u00eb shum\u00eb e nd\u00ebrlikuar dhe e gjer\u00eb, n\u00eb t\u00eb cil\u00ebn do t\u00eb kthehemi n\u00eb m\u00ebsimet e ardhshme. Jam i sigurt se me ndihm\u00ebn time do t\u00eb b\u00ebheni \"mastera\" t\u00eb VLAN, por kuptimi i k\u00ebtij m\u00ebsimi ishte t\u00eb ju sqaronte 3 \u00e7\u00ebshtje: \u00e7far\u00eb jan\u00eb rrjetet VLAN, p\u00ebrse i nevojiten dhe si t'i konfigurojm\u00eb. <\/p>\n

\r\n \"Luaj\r\n
<\/div>\r\n <\/div><\/center>
\nFaleminderit q\u00eb q\u00ebndroni me ne. Ju p\u00eblqejn\u00eb artikujt tan\u00eb? D\u00ebshironi t\u00eb shihni m\u00eb shum\u00eb materiale interesante? Na mb\u00ebshtetni duke b\u00ebr\u00eb nj\u00eb porosi ose duke na rekomanduar miqve tuaj. 30% zbritje p\u00ebr p\u00ebrdoruesit e Habra n\u00eb nj\u00eb analog unik t\u00eb server\u00ebve entry-level, t\u00eb cilin e kemi shpikur p\u00ebr ju:<\/b> E gjith\u00eb e v\u00ebrteta p\u00ebr VPS (KVM) E5-2650 v4 (6 B\u00ebrthama) 10GB DDR4 240GB SSD 1Gbps nga $20 ose si t\u00eb ndajm\u00eb sakt\u00ebsisht serverin?<\/a><\/noindex> (opcionet me RAID1 dhe RAID10, deri n\u00eb 24 b\u00ebrthama dhe deri n\u00eb 40GB DDR4 jan\u00eb t\u00eb disponueshme).<\/p>\n

Dell R730xd p\u00ebr dy her\u00eb m\u00eb lir\u00eb?<\/b> Vet\u00ebm te ne 2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100 TB nga $199<\/a><\/noindex> n\u00eb Holand\u00eb! Dell R420 \u2014 2x E5-2430 2.2Ghz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 nga $99!<\/b><\/b> Lexoni rreth Si t\u00eb nd\u00ebrtoni nj\u00eb infrastruktur\u00eb t\u00eb klas\u00ebs korporative me p\u00ebrdorimin e server\u00ebve Dell R730xd E5-2650 v4 me \u00e7mim 9000 euro p\u00ebr pak para?<\/a><\/noindex>
\n
Burimi: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u043c\u044b \u043f\u0440\u0438\u0441\u0442\u0443\u043f\u0438\u043c \u043a \u043e\u0441\u043d\u043e\u0432\u0430\u043c VLAN, \u044f \u0431\u044b \u043f\u043e\u043f\u0440\u043e\u0441\u0438\u043b \u0432\u0441\u0435\u0445 \u0432\u0430\u0441 \u043f\u043e\u0441\u0442\u0430\u0432\u0438\u0442\u044c \u044d\u0442\u043e \u0432\u0438\u0434\u0435\u043e \u043d\u0430 \u043f\u0430\u0443\u0437\u0443, \u043d\u0430\u0436\u0430\u0442\u044c \u043d\u0430 \u0438\u043a\u043e\u043d\u043a\u0443 \u0432 \u043d\u0438\u0436\u043d\u0435\u043c \u043b\u0435\u0432\u043e\u043c \u0443\u0433\u043b\u0443, \u0433\u0434\u0435 \u043d\u0430\u043f\u0438\u0441\u0430\u043d\u043e Networking consultant, \u0437\u0430\u0439\u0442\u0438 \u043d\u0430 \u043d\u0430\u0448\u0443 \u0441\u0442\u0440\u0430\u043d\u0438\u0447\u043a\u0443 Facebook \u0438 \u043f\u043e\u0441\u0442\u0430\u0432\u0438\u0442\u044c \u0442\u0430\u043c \u043b\u0430\u0439\u043a. \u0417\u0430\u0442\u0435\u043c \u0432\u0435\u0440\u043d\u0438\u0442\u0435\u0441\u044c \u043a \u0432\u0438\u0434\u0435\u043e \u0438 \u043d\u0430\u0436\u043c\u0438\u0442\u0435 \u043d\u0430 \u0438\u043a\u043e\u043d\u043a\u0443 King \u0432 \u043f\u0440\u0430\u0432\u043e\u043c \u043d\u0438\u0436\u043d\u0435\u043c \u0443\u0433\u043b\u0443, \u0447\u0442\u043e\u0431\u044b \u043f\u043e\u0434\u043f\u0438\u0441\u0430\u0442\u044c\u0441\u044f \u043d\u0430 \u043d\u0430\u0448 \u043e\u0444\u0438\u0446\u0438\u0430\u043b\u044c\u043d\u044b\u0439 […]<\/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-35830","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\udd47Trajnimi Cisco 200-125 CCNA v3.0. Dita 11. Bazat e VLAN | ProHoster","description":"Para se t\u00eb fillojm\u00eb me bazat e VLAN, do t'ju k\u00ebrkoja t\u00eb gjith\u00eb q\u00eb ta ndalni k\u00ebt\u00eb video p\u00ebr disa \u00e7aste, t\u00eb klikoni n\u00eb ikon\u00ebn n\u00eb pjes\u00ebn e poshtme t\u00eb majt\u00eb ku shkruan Konsulent Rrjetesh, t\u00eb hyni n\u00eb faqen ton\u00eb n\u00eb Facebook dhe t\u00eb regjistroni nj\u00eb p\u00eblqim aty.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-11-osnovy-vlan","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\u0422\u0440\u0435\u043d\u0438\u043d\u0433 Cisco 200-125 CCNA v3.0. \u0414\u0435\u043d\u044c 11. \u041e\u0441\u043d\u043e\u0432\u044b VLAN | ProHoster","og:description":"\u041f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u043c\u044b \u043f\u0440\u0438\u0441\u0442\u0443\u043f\u0438\u043c \u043a \u043e\u0441\u043d\u043e\u0432\u0430\u043c VLAN, \u044f \u0431\u044b \u043f\u043e\u043f\u0440\u043e\u0441\u0438\u043b \u0432\u0441\u0435\u0445 \u0432\u0430\u0441 \u043f\u043e\u0441\u0442\u0430\u0432\u0438\u0442\u044c \u044d\u0442\u043e \u0432\u0438\u0434\u0435\u043e \u043d\u0430 \u043f\u0430\u0443\u0437\u0443, \u043d\u0430\u0436\u0430\u0442\u044c \u043d\u0430 \u0438\u043a\u043e\u043d\u043a\u0443 \u0432 \u043d\u0438\u0436\u043d\u0435\u043c \u043b\u0435\u0432\u043e\u043c \u0443\u0433\u043b\u0443, \u0433\u0434\u0435 \u043d\u0430\u043f\u0438\u0441\u0430\u043d\u043e Networking consultant, \u0437\u0430\u0439\u0442\u0438 \u043d\u0430 \u043d\u0430\u0448\u0443 \u0441\u0442\u0440\u0430\u043d\u0438\u0447\u043a\u0443 Facebook \u0438 \u043f\u043e\u0441\u0442\u0430\u0432\u0438\u0442\u044c \u0442\u0430\u043c.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-11-osnovy-vlan","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:06:40+00:00","article:modified_time":"2019-10-31T19:06:40+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"35830","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-01-22 00:57:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:55:26","updated":"2026-01-22 00:57:19","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\/35830","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=35830"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/35830\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=35830"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=35830"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=35830"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}