{"id":37066,"date":"2019-10-31T22:15:33","date_gmt":"2019-10-31T19:15:33","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-14-vtp-pruning-i-native-vlan\/"},"modified":"2019-10-31T22:15:33","modified_gmt":"2019-10-31T19:15:33","slug":"trening-cisco-200-125-ccna-v3-0-den-14-vtp-pruning-i-native-vlan","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-14-vtp-pruning-i-native-vlan","title":{"rendered":"Trajnimi Cisco 200-125 CCNA v3.0. Dita 14. VTP, Pruning dhe VLAN i Native.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Sot \u00ebsht\u00eb e nevojshme t\u00eb vazhdojm\u00eb shqyrtimin e VLAN dhe t\u00eb diskutojm\u00eb protokollin VTP, si dhe konceptet e VTP Pruning dhe Native VLAN. N\u00eb nj\u00eb nga video t\u00eb m\u00ebparshme, ne fol\u00ebm tashm\u00eb p\u00ebr VTP, dhe gj\u00ebja e par\u00eb q\u00eb duhet t'ju vij\u00eb n\u00eb mendje, kur d\u00ebgjoni p\u00ebr VTP, \u00ebsht\u00eb se Ai nuk \u00ebsht\u00eb nj\u00eb protokoll p\u00ebr trunching, megjith\u00ebse quhet \"protokoll p\u00ebr trunching VLAN\".<\/p>\n

\"Trajnimi
\n
\nSi\u00e7 e dini, ekzistojn\u00eb dy protokolle t\u00eb njohura p\u00ebr trunching \u2013 protokolli pronar Cisco ISL, i cila nuk p\u00ebrdoret m\u00eb sot, dhe protokolli 802.q, i cili p\u00ebrdoret n\u00eb pajisje rrjeti t\u00eb prodhuesve t\u00eb ndrysh\u00ebm p\u00ebr inkapsulimin e trafikut t\u00eb trunching. Ky protokoll gjithashtu aplikohet n\u00eb switch-at Cisco. Tashm\u00eb kemi folur se VTP \u00ebsht\u00eb nj\u00eb protokoll sinkronizimi VLAN, dometh\u00ebn\u00eb ai \u00ebsht\u00eb i destinuar p\u00ebr t\u00eb sinkronizuar baz\u00ebn e t\u00eb dh\u00ebnave VLAN n\u00eb t\u00eb gjitha switch-at e rrjetit. <\/p>\n

\"Trajnimi
\n
\nKemi p\u00ebrmendur m\u00ebnyrat e ndryshme t\u00eb VTP \u2013 server, klient, transparent. N\u00ebse pajisja p\u00ebrdor modalitetin e serverit, kjo lejon t\u00eb b\u00ebhen ndryshime, t\u00eb shtohen ose t\u00eb hiqen VLAN. Modaliteti i klientit nuk lejon t\u00eb b\u00ebhen ndryshime n\u00eb konfigurimin e switch-it, ju mund t\u00eb konfiguroni baz\u00ebn e t\u00eb dh\u00ebnave VLAN vet\u00ebm p\u00ebrmes VTP-serverit, dhe ajo do t\u00eb riprodhohet n\u00eb t\u00eb gjith\u00eb VTP-klient\u00ebt. Switch-i n\u00eb modalitetin transparent nuk b\u00ebn ndryshime n\u00eb vet\u00eb baz\u00ebn e t\u00eb dh\u00ebnave VLAN, por thjesht kalon dhe transmeton ndryshimet n\u00eb pajisjen tjet\u00ebr q\u00eb ndodhet n\u00eb modalitetin klient. Ky modalitet \u00ebsht\u00eb i ngjash\u00ebm me shk\u00ebputjen e protokollit VTP n\u00eb nj\u00eb pajisje t\u00eb caktuar, duke e kthyer at\u00eb n\u00eb nj\u00eb transportues informacioni p\u00ebr ndryshimet VLAN. <\/a><\/noindex><\/p>\n

Le t\u00eb kthehemi n\u00eb programin Packet Tracer dhe n\u00eb topologjin\u00eb e rrjetit t\u00eb shqyrtuar n\u00eb m\u00ebsimin e m\u00ebparsh\u00ebm. Ne kemi konfigurimin e rrjetit VLAN10 p\u00ebr departamentin e shitjeve dhe rrjetin VLAN20 p\u00ebr departamentin e marketingut, duke i kombinuar ato me tre switch-a. <\/p>\n

\"Trajnimi
\n
\nNd\u00ebrmjet switch-eve SW0 dhe SW1 ndodh lidhja p\u00ebrmes rrjetit VLAN20, nd\u00ebrsa mids SW0 dhe SW2 ndodh lidhja p\u00ebrmes rrjetit VLAN10 fal\u00eb faktit se kemi shtuar VLAN10 n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave VLAN t\u00eb switch-it SW1.
\nP\u00ebr t\u00eb shqyrtuar funksionimin e protokollit VTP, le t\u00eb p\u00ebrdorim nj\u00eb nga switch-at si VTP-server, le t\u00eb jet\u00eb SW0. N\u00ebse e mbani mend, si rregull t\u00eb gjith\u00eb switch-at punojn\u00eb n\u00eb modalitetin e VTP-serverit. Le t\u00eb hyjm\u00eb n\u00eb terminalin e komand\u00ebs s\u00eb switch-it dhe t\u00eb shkruajm\u00eb komand\u00ebn show vtp status. Ju shihni versionin aktual t\u00eb protokollit VTP \u2013 2 dhe numrin e revizionit t\u00eb konfigurimit 4. N\u00ebse e mbani mend, \u00e7do her\u00eb q\u00eb b\u00ebhen ndryshime n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave VTP, numri i revizionit rritet me nj\u00eb. <\/p>\n

\"Trajnimi
\n
\nNumri maksimal i rrjeteve VLAN t\u00eb mb\u00ebshtetura \u00ebsht\u00eb 255. Ky num\u00ebr varet nga marka e konkretit switch Cisco, pasi switches t\u00eb ndryshme mund t\u00eb mb\u00ebshtesin nj\u00eb num\u00ebr t\u00eb ndrysh\u00ebm t\u00eb rrjeteve lokale virtuale. Numri i rrjeteve VLAN ekzistuese \u00ebsht\u00eb 7, dhe pas nj\u00eb minute ne do t\u00eb shohim se \u00e7far\u00eb rrjetesh jan\u00eb k\u00ebto. Re\u017eimi i menaxhimit VTP \u00ebsht\u00eb server, emri i domain-it nuk \u00ebsht\u00eb caktuar, dhe rezhimi VTP Pruning \u00ebsht\u00eb \u00e7aktivizuar, ne do t\u00eb kthehemi te ky m\u00eb von\u00eb. Edhe rezhimet VTP V2 dhe VTP Traps Generation jan\u00eb \u00e7aktivizuar. P\u00ebr t\u00eb kaluar provimin 200-125 CCNA, nuk ju nevojitet t\u00eb dini p\u00ebr dy rezhimet e fundit, k\u00ebshtu q\u00eb mund t\u00eb mos shqet\u00ebsoheni p\u00ebr to. <\/p>\n

Le t\u00eb shqyrtojm\u00eb baz\u00ebn e t\u00eb dh\u00ebnave VLAN, p\u00ebr k\u00ebt\u00eb do t\u00eb p\u00ebrdorim komand\u00ebn show vlan. Si\u00e7 e pam\u00eb n\u00eb videon e kaluar, kemi 4 rrjete t\u00eb papranuara: 1002, 1003, 1004 dhe 1005.<\/p>\n

\"Trajnimi
\n
\nK\u00ebtu gjithashtu jan\u00eb p\u00ebrmendur 2 rrjete VLAN10 dhe 20 q\u00eb ne krijuam dhe rrjeti i paracaktuar VLAN1. Tani, le t\u00eb kalojm\u00eb n\u00eb nj\u00eb switch tjet\u00ebr dhe t\u00eb japim t\u00eb nj\u00ebjt\u00ebn komand\u00eb p\u00ebr t\u00eb marr\u00eb statusin e VTP-s\u00eb. Ju shihni q\u00eb numri i rishikimit t\u00eb k\u00ebtij switch-i \u00ebsht\u00eb 3, ai \u00ebsht\u00eb n\u00eb rezhimin VTP-server dhe gjith\u00eb informacioni tjet\u00ebr \u00ebsht\u00eb i ngjash\u00ebm me switch-in e par\u00eb. Kur t\u00eb jap komand\u00ebn show VLAN, do t\u00eb shoh se ne kemi b\u00ebr\u00eb 2 ndryshime n\u00eb konfigurim, nj\u00eb m\u00eb pak se switch-i SW0, kjo \u00ebsht\u00eb arsyeja se pse numri i rishikimit SW1 \u00ebsht\u00eb 3. Ne b\u00ebm\u00eb 3 ndryshime n\u00eb konfigurimet e zakonshme t\u00eb switch-it t\u00eb par\u00eb, k\u00ebshtu q\u00eb numri i tij i rishikimit u rrit n\u00eb 4. <\/p>\n

\"Trajnimi
\n
\nTani le t\u00eb shikojm\u00eb statusin e SW2. Numri i rishikimit k\u00ebtu \u00ebsht\u00eb 1, dhe kjo \u00ebsht\u00eb e \u00e7uditshme. Ne duhet t\u00eb kemi rishikimin e dyt\u00eb, sepse \u00ebsht\u00eb b\u00ebr\u00eb 1 ndryshim n\u00eb konfigurim. Le t\u00eb shohim n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave VLAN.<\/p>\n

\"Trajnimi
\n
\nNe kemi b\u00ebr\u00eb nj\u00eb ndryshim t\u00eb vet\u00ebm duke krijuar rrjetin VLAN10, dhe nuk e di pse kjo informacion nuk u p\u00ebrmbush. Ndoshta kjo ndodhi p\u00ebr shkak se nuk kemi nj\u00eb rrjet t\u00eb v\u00ebrtet\u00eb, por nj\u00eb simulator t\u00eb softuerit, ku mund t\u00eb ket\u00eb gabime. Kur t\u00eb keni mund\u00ebsin\u00eb t\u00eb punoni me pajisje t\u00eb v\u00ebrteta gjat\u00eb praktik\u00ebs n\u00eb nj\u00eb deg\u00eb t\u00eb kompanis\u00eb Cisco, do t'ju ndihmoj\u00eb m\u00eb shum\u00eb sesa simulatori Packet Tracer. Nj\u00eb gj\u00eb tjet\u00ebr e dobishme n\u00eb munges\u00eb t\u00eb pajisjeve reale do t\u00eb jet\u00eb GNC3, ose simulatori grafik i rrjetit Cisco. Ky \u00ebsht\u00eb nj\u00eb emulator q\u00eb p\u00ebrdor sistemin operativ real t\u00eb pajisjes, si p.sh. nj\u00eb router. Ka nj\u00eb diferenc\u00eb midis simulatorit dhe emulatorit - i pari \u00ebsht\u00eb nj\u00eb program q\u00eb duket si nj\u00eb router i v\u00ebrtet\u00eb, por nuk \u00ebsht\u00eb ai. Emulatori krijon programikisht vet\u00ebm pajisjen, por p\u00ebr funksionimin e saj p\u00ebrdor softuerin real. Por n\u00ebse nuk keni mund\u00ebsin\u00eb t\u00eb punoni me softuerin real Cisco IOS, mund\u00ebsia m\u00eb e mir\u00eb do t\u00eb jet\u00eb Packet Tracer. <\/p>\n

Pra, na nevojitet t\u00eb konfiguroni SW0 si server VTP, p\u00ebr k\u00ebt\u00eb un\u00eb hy n\u00eb modin e konfigurimit global dhe fut komand\u00ebn vtp version 2. Si\u00e7 thash\u00eb, ne mund t\u00eb vendosim versionin e protokollit q\u00eb na nevojitet - 1 ose 2, n\u00eb k\u00ebt\u00eb rast na nevojitet versioni i dyt\u00eb. N\u00eb vazhdim, me komand\u00ebn vtp mode ne p\u00ebrcaktojm\u00eb modalitetin VTP t\u00eb switch-it - server, klient ose transparent. N\u00eb k\u00ebt\u00eb rast na nevojitet moda e serverit, dhe pas futjes s\u00eb komand\u00ebs vtp mode server, sistemi jep nj\u00eb mesazh q\u00eb pajisja \u00ebsht\u00eb tashm\u00eb n\u00eb mod\u00ebn e serverit. M\u00eb tej duhet t\u00eb konfigurojm\u00eb domenin VTP, p\u00ebr t\u00eb cilin p\u00ebrdorim komand\u00ebn vtp domain nwking.org. Pse \u00ebsht\u00eb e nevojshme kjo? N\u00ebse n\u00eb rrjet ka nj\u00eb pajisje tjet\u00ebr me nj\u00eb num\u00ebr m\u00eb t\u00eb madh revizioni, t\u00eb gjitha pajisjet e tjera me nj\u00eb num\u00ebr m\u00eb t\u00eb vog\u00ebl fillojn\u00eb t\u00eb replikojn\u00eb baz\u00ebn e t\u00eb dh\u00ebnave VLAN nga kjo pajisje. Megjithat\u00eb, kjo ndodh vet\u00ebm n\u00ebse pajisjet kan\u00eb t\u00eb nj\u00ebjtin em\u00ebr domene. P\u00ebr shembull, n\u00ebse punoni n\u00eb nwking.org, ju tregoni k\u00ebt\u00eb domen, n\u00ebse n\u00eb Cisco, at\u00ebher\u00eb domeni cisco.com dhe k\u00ebshtu me radh\u00eb. Emri i domenit t\u00eb pajisjeve t\u00eb kompanis\u00eb tuaj lejon q\u00eb t'i dalloni ato nga pajisjet e kompanive t\u00eb tjera ose nga \u00e7do pajisje t\u00eb jashtme t\u00eb rrjetit. N\u00ebse i atribuoni pajisjes nj\u00eb em\u00ebr domene t\u00eb kompanis\u00eb, at\u00ebher\u00eb e b\u00ebni at\u00eb pjes\u00eb t\u00eb rrjetit t\u00eb k\u00ebsaj kompanie. <\/p>\n

Hapi i ardhsh\u00ebm q\u00eb duhet t\u00eb b\u00ebni \u00ebsht\u00eb t\u00eb vendosni fjal\u00ebkalimin VTP. Kjo \u00ebsht\u00eb e nevojshme p\u00ebr t\u00eb siguruar q\u00eb nj\u00eb hakues, duke pasur nj\u00eb pajisje me nj\u00eb num\u00ebr revizioni m\u00eb t\u00eb lart\u00eb, nuk mund t\u00eb kopjoj\u00eb cil\u00ebsimet e tij VTP n\u00eb switch-in tuaj. Un\u00eb vendos fjal\u00ebkalimin cisco duke p\u00ebrdorur komand\u00ebn vtp password cisco. Pas k\u00ebsaj, replikimi i t\u00eb dh\u00ebnave VTP midis switch-eve do t\u00eb jet\u00eb i mundur vet\u00ebm kur fjal\u00ebkalimet p\u00ebrkojn\u00eb. N\u00ebse p\u00ebrdoret nj\u00eb fjal\u00ebkalim i gabuar, p\u00ebrdit\u00ebsimi i baz\u00ebs s\u00eb t\u00eb dh\u00ebnave VLAN nuk do t\u00eb ndodh\u00eb. <\/p>\n

Le t\u00eb p\u00ebrpiqemi t\u00eb krijojm\u00eb disa VLAN tjera. P\u00ebr k\u00ebt\u00eb, un\u00eb p\u00ebrdor komand\u00ebn config t, me komand\u00ebn vlan 200 krijoj rrjetin me num\u00ebr 200, i jep emrin TEST dhe ruaj ndryshimet me komand\u00ebn exit. Pastaj krijoj nj\u00eb rrjet tjet\u00ebr vlan 500 dhe e quaj TEST1. N\u00ebse tani shkruaj komand\u00ebn show vlan, mund t\u00eb shihni n\u00eb tabel\u00ebn e rrjeteve virtuale t\u00eb switch-it k\u00ebto dy rrjete t\u00eb reja, t\u00eb cilave nuk u \u00ebsht\u00eb caktuar asnj\u00eb port. <\/p>\n

\"Trajnimi
\n
\nLe t\u00eb kalojm\u00eb tek SW1 dhe t\u00eb shohim statusin e tij VTP. Shihni, k\u00ebtu nuk ka patur ndryshime, p\u00ebrve\u00e7 emrit t\u00eb domainit, numri i rrjeteve VLAN mbetet 7. Nuk shohim shfaqjen e rrjeteve q\u00eb krijuam, sepse fjal\u00ebkalimi VTP nuk p\u00ebrkon. Le t\u00eb vendosim fjal\u00ebkalimin VTP n\u00eb k\u00ebt\u00eb switch, duke futur komandat conf t, vtp pass dhe vtp password cisco. Sistemi dha nj\u00eb mesazh q\u00eb baza e t\u00eb dh\u00ebnave VLAN t\u00eb pajisjes tani p\u00ebrdor fjal\u00ebkalimin cisco. Le t\u00eb hedhim nj\u00eb sy p\u00ebrs\u00ebri n\u00eb statusin VTP p\u00ebr t\u00eb kontrolluar n\u00ebse replikimi i informacionit ka ndodhur. Si\u00e7 e shihni, numri i VLAN e ekzistueshme u rrit automatikisht n\u00eb 9. <\/p>\n

N\u00ebse shikoni baz\u00ebn e t\u00eb dh\u00ebnave VLAN t\u00eb k\u00ebtij switch-i, do t\u00eb shihni se rrjetet VLAN200 dhe VLAN500 q\u00eb krijuam automatikisht jan\u00eb shfaqur. <\/p>\n

T\u00eb nj\u00ebjt\u00ebn gj\u00eb duhet t\u00eb b\u00ebjm\u00eb edhe me switch-in e fundit SW2. Do ta japim komand\u00ebn show vlan \u2013 shihni, nuk ka ndodhur asnj\u00eb ndryshim. Po ashtu, nuk ka asnj\u00eb ndryshim n\u00eb statusin VTP. P\u00ebr q\u00eb ky switch t\u00eb p\u00ebrdit\u00ebsoj\u00eb informacionin, duhet gjithashtu t\u00eb konfigurohet fjal\u00ebkalimi, pra t\u00eb jepen t\u00eb nj\u00ebjtat komanda si p\u00ebr SW1. Pas k\u00ebsaj, numri i rrjeteve VLAN n\u00eb statusin SW2 do t\u00eb rritet n\u00eb 9.<\/p>\n

Kjo \u00ebsht\u00eb arsyeja pse protokolli VTP \u00ebsht\u00eb i nevojsh\u00ebm. Ky \u00ebsht\u00eb nj\u00eb mjet i shk\u00eblqyer q\u00eb siguron p\u00ebrdit\u00ebsimin automatik t\u00eb informacionit n\u00eb t\u00eb gjitha pajisjet rrjet\u00ebsore t\u00eb klient\u00ebve pas ndryshimeve n\u00eb pajisjen-server. Nuk keni nevoj\u00eb t\u00eb b\u00ebni manualisht ndryshime n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave VLAN t\u00eb t\u00eb gjith\u00eb switch-eve \u2013 riplikimi ndodh automatikisht. N\u00ebse keni 200 pajisje rrjet\u00ebsore, ndryshimet e vendosura do t\u00eb ruhen n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb n\u00eb t\u00eb gjitha dyqind pajisjet. N\u00eb rast se, gjithsesi, duhet t\u00eb sigurohemi q\u00eb SW2 \u00ebsht\u00eb gjithashtu nj\u00eb VTP-klient, prandaj do t\u00eb shkojm\u00eb n\u00eb cil\u00ebsimet me komand\u00ebn config t dhe do t\u00eb shkruajm\u00eb komand\u00ebn vtp mode client. <\/p>\n

Pra, n\u00eb rrjetin ton\u00eb vet\u00ebm switch-i i par\u00eb \u00ebsht\u00eb n\u00eb modin VTP Server, dy t\u00eb tjer\u00ebt funksionojn\u00eb n\u00eb modin VTP Client. N\u00ebse tani hyj n\u00eb cil\u00ebsimet e SW2 dhe shkruaj komand\u00ebn vlan 1000, do t\u00eb marr nj\u00eb mesazh: \"konfigurimi VTP VLAN nuk lejohet kur pajisja \u00ebsht\u00eb n\u00eb modin klient\". Pra, nuk mund t\u00eb b\u00ebj asnj\u00eb ndryshim n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave VLAN n\u00ebse switch-i \u00ebsht\u00eb n\u00eb modin VTP-klient. N\u00ebse dua t\u00eb b\u00ebj ndonj\u00eb ndryshim, duhet t\u00eb kaloj n\u00eb switch-in server. <\/p>\n

Hyj n\u00eb cil\u00ebsimet e terminalit SW0 dhe shkruaj komandat vlan 999, name IMRAN dhe exit. Kjo rrjet e re u shfaq n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave VLAN t\u00eb k\u00ebtij switch-i, dhe n\u00ebse tani kaloj n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave t\u00eb switch-it-klient SW2, do t\u00eb shoh q\u00eb k\u00ebtu ka ardhur e nj\u00ebjta informacion, pra ka ndodhur riplikimi. <\/p>\n

Si\u00e7 e thash\u00eb, VTP \u00ebsht\u00eb nj\u00eb pjes\u00eb e shk\u00eblqyer e softuerit, por n\u00ebse p\u00ebrdoret gabim, ky protokoll mund t\u00eb d\u00ebmtoj\u00eb t\u00ebr\u00eb rrjetin. Prandaj, duhet t\u00eb jeni shum\u00eb t\u00eb kujdessh\u00ebm me rrjetin e kompanis\u00eb, n\u00ebse emri i domain dhe fjal\u00ebkalimi VTP nuk jan\u00eb t\u00eb vendosura. N\u00eb k\u00ebt\u00eb rast, gjith\u00e7ka q\u00eb i nevojitet hakerit \u00ebsht\u00eb t\u00eb vendos\u00eb kabllon e switch-it t\u00eb tij n\u00eb priz\u00ebn rrjet\u00ebsore n\u00eb mur, t\u00eb lidh\u00eb me ndonj\u00eb switch zyre p\u00ebrmes protokollit DTP dhe pastaj, duke p\u00ebrdorur trunk-un e krijuar, t\u00eb p\u00ebrdit\u00ebsoj\u00eb t\u00eb gjitha informacionet p\u00ebrmes protokollit VTP. K\u00ebshtu, hakeri mund t\u00eb fshij\u00eb t\u00eb gjitha VLAN-t\u00eb e r\u00ebnd\u00ebsishme, duke p\u00ebrfituar nga fakti q\u00eb numri i revizionit t\u00eb pajisjes s\u00eb tij \u00ebsht\u00eb m\u00eb i lart\u00eb se numri i revizionit t\u00eb switch-eve t\u00eb tjer\u00eb. N\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, switch-et e kompanis\u00eb do t\u00eb z\u00ebvend\u00ebsojn\u00eb automatikisht t\u00eb gjith\u00eb informacionin e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave VLAN me informacionin q\u00eb \u00ebsht\u00eb riplikuar nga switch-i i d\u00ebmsh\u00ebm, dhe e gjith\u00eb rrjeta juaj do t\u00eb bjer\u00eb. <\/p>\n

Kjo lidhet me faktin se kompjuter\u00ebt jan\u00eb lidhur me nj\u00eb port specifik t\u00eb kalueseve p\u00ebrmes nj\u00eb kablli rrjeti, t\u00eb cilit i \u00ebsht\u00eb lidhur rrjeti VLAN 10 ose rrjeti VLAN 20. N\u00ebse k\u00ebto rrjete i hiqen nga databaza LAN e kalueseve, ai do t\u00eb \u00e7 Aktivizoj\u00eb automatikisht portin e lidhur me rrjetin q\u00eb nuk ekziston. Zakonisht, rrjeti i kompanis\u00eb mund t\u00eb kolapsoj\u00eb pik\u00ebrisht sepse kaluesit thjesht do t\u00eb \u00e7aktivizojn\u00eb portet e lidhura me VLAN-et q\u00eb jan\u00eb hequr gjat\u00eb p\u00ebrdit\u00ebsimit t\u00eb radh\u00ebs. <\/p>\n

P\u00ebr t\u00eb parandaluar ndodhin e k\u00ebtij problemi, duhet t\u00eb vendosni emrin e domenit dhe fjal\u00ebkalimin VTP, ose t\u00eb p\u00ebrdorni funksionin Cisco Port Security, i cili lejon menaxhimin e MAC-adresave t\u00eb porteve t\u00eb kalueseve duke vendosur kufizime t\u00eb ndryshme p\u00ebr p\u00ebrdorimin e tyre. P\u00ebr shembull, n\u00ebse dikush i huaj p\u00ebrpiqet t\u00eb ndryshoj\u00eb MAC-adres\u00ebn, porta do t\u00eb \u00e7aktivizohet menj\u00ebher\u00eb. Shum\u00eb shpejt do t\u00eb njihemi m\u00eb af\u00ebr me k\u00ebt\u00eb funksion t\u00eb kalueseve Cisco, por tani mjafton t\u00eb dini se Port Security siguron q\u00eb VTP t\u00eb jet\u00eb i mbrojtur nga sulmuesit.<\/p>\n

T\u00eb p\u00ebrmbledhim se \u00e7far\u00eb p\u00ebrfaq\u00ebson konfigurimi i VTP. Ky \u00ebsht\u00eb zgjedhja e versionit t\u00eb protokollit \u2013 1 ose 2, cakton modin e VTP \u2013 server, klient ose transparent. Si\u00e7 e thash\u00eb, modu i fundit nuk p\u00ebrdit\u00ebson databaz\u00ebn VLAN t\u00eb vet\u00eb pajisjes, por thjesht transmeton t\u00eb gjitha ndryshimet te pajisjet fqinj. M\u00eb posht\u00eb jan\u00eb komandat p\u00ebr t\u00eb caktuar emrin e domenit dhe fjal\u00ebkalimin: vtp domain dhe vtp password . <\/p>\n

\"Trajnimi
\n
\nTani le t\u00eb flasim p\u00ebr konfigurimet e VTP Pruning. N\u00ebse shikoni topologjin\u00eb e rrjetit, mund t\u00eb shihni se t\u00eb tre kaluesit kan\u00eb t\u00eb nj\u00ebjt\u00ebn databaz\u00eb VLAN, q\u00eb do t\u00eb thot\u00eb se rrjetet VLAN10 dhe VLAN20 jan\u00eb pjes\u00eb e t\u00eb tre kaluesve. Teknikisht, kaluesi SW2 nuk e ka nevoj\u00ebn p\u00ebr rrjetin VLAN20, sepse nuk ka porte t\u00eb lidhura me k\u00ebt\u00eb rrjet. Megjithat\u00eb, pavar\u00ebsisht k\u00ebsaj, t\u00eb gjith\u00eb trafiku q\u00eb d\u00ebrgohet nga kompjuteri Laptop0 n\u00eb rrjetin VLAN20 kalon n\u00eb kaluesin SW1 dhe prej tij, p\u00ebrmes trunk-ut, shkon n\u00eb portet SW2. Detyra juaj kryesore si specialist i rrjetit \u00ebsht\u00eb ta b\u00ebni q\u00eb n\u00eb rrjet t\u00eb kaloj\u00eb sa m\u00eb pak t\u00eb dh\u00ebna t\u00eb tep\u00ebrta. Duhet t\u00eb siguroheni p\u00ebr transmetimin e t\u00eb dh\u00ebnave t\u00eb nevojshme, por si t\u00eb kufizoni d\u00ebrgimin e informacionit q\u00eb nuk \u00ebsht\u00eb i nevojsh\u00ebm p\u00ebr k\u00ebt\u00eb pajisje?<\/p>\n

Ju duhet t\u00eb siguroheni q\u00eb trafiku i destinuar p\u00ebr pajisjet e rrjetit VLAN20 t\u00eb mos kaloj\u00eb n\u00eb portet SW2 p\u00ebrmes trunk-it kur nuk \u00ebsht\u00eb e nevojshme. Pra, trafiku Laptop0 duhet t\u00eb arrij\u00eb n\u00eb SW1 dhe m\u00eb pas n\u00eb kompjuter\u00ebt e rrjetit VLAN20, por nuk duhet t\u00eb dal\u00eb p\u00ebrtej portit t\u00eb djatht\u00eb trunk SW1. Kjo mund t\u00eb sigurohet p\u00ebrmes VTP Pruning. <\/p>\n

P\u00ebr k\u00ebt\u00eb, na duhet t\u00eb hyjm\u00eb n\u00eb konfigurimin e serverit VTP SW0, pasi si\u00e7 e kam th\u00ebn\u00eb m\u00eb par\u00eb, konfigurimet e VTP mund t\u00eb b\u00ebhen vet\u00ebm p\u00ebrmes serverit, t\u00eb hyjm\u00eb n\u00eb konfigurimin global dhe t\u00eb shkruajm\u00eb komand\u00ebn vtp pruning. Duke pasur parasysh q\u00eb Packet Tracer \u00ebsht\u00eb vet\u00ebm nj\u00eb program-simulator, n\u00eb ndihm\u00ebn e saj p\u00ebr komandat nuk ka nj\u00eb t\u00eb till\u00eb. Megjithat\u00eb, kur t\u00eb shkruaj vtp pruning dhe t\u00eb shtyp \u00abEnter\u00bb, sistemi do t\u00eb m\u00eb informoj\u00eb se moda vtp pruning nuk \u00ebsht\u00eb e aksesueshme.<\/p>\n

Duke p\u00ebrdorur komand\u00ebn show vtp status, ne do t\u00eb shohim q\u00eb moda VTP Pruning \u00ebsht\u00eb n\u00eb gjendje t\u00eb \u00e7aktivizuar, prandaj duhet ta b\u00ebjm\u00eb at\u00eb t\u00eb aksesueshme duke e \u00e7uar n\u00eb pozitiv. Duke b\u00ebr\u00eb k\u00ebt\u00eb, ne aktivizojm\u00eb mod\u00ebn VTP Pruning n\u00eb t\u00eb tre switch-et e rrjetit ton\u00eb brenda domenit t\u00eb rrjetit.
\nM\u00eb lejoni t'ju kujtoj se \u00e7far\u00eb \u00ebsht\u00eb VTP Pruning. Kur e aktivizojm\u00eb k\u00ebt\u00eb mod\u00eb, switch-serveri SW0 i raporton switch-it SW2 se vet\u00ebm rrjeti VLAN10 \u00ebsht\u00eb konfiguruar n\u00eb portet e tij. M\u00eb pas, switch-i SW2 i raporton switch-it SW1 se nuk ka nevoj\u00eb p\u00ebr ndonj\u00eb trafik tjet\u00ebr p\u00ebrve\u00e7 trafikut t\u00eb destinuar p\u00ebr rrjetin VLAN10. Tani, fal\u00eb VTP Pruning, switch-i SW1 ka informacionin se nuk ka nevoj\u00eb t\u00eb d\u00ebrgoj\u00eb trafik VLAN20 p\u00ebrmes trunk SW1-SW2. <\/p>\n

P\u00ebr ju si administrator t\u00eb rrjetit, kjo \u00ebsht\u00eb shum\u00eb e k\u00ebndshme. Nuk keni nevoj\u00eb t\u00eb hyni manualisht n\u00eb komandat, pasi switch-i \u00ebsht\u00eb mjaft inteligjent p\u00ebr t\u00eb d\u00ebrguar vet\u00ebm at\u00eb q\u00eb k\u00ebrkohet nga nj\u00eb pajisje specifike t\u00eb rrjetit. N\u00ebse nes\u00ebr vendosni nj\u00eb tjet\u00ebr departament marketingu n\u00eb ndonj\u00eb nd\u00ebrtes\u00eb fqinje dhe lidheni rrjetin e tij VLAN20 me switch-in SW2, ky switch do t'i raportoj\u00eb menj\u00ebher\u00eb switch-it SW1 se tani ka rrjetet VLAN10 dhe VLAN20 dhe do t\u00eb k\u00ebrkoj\u00eb t\u00eb d\u00ebrgoj\u00eb trafik p\u00ebr t\u00eb dyja rrjetet. Kjo informacion vazhdimisht p\u00ebrdit\u00ebsohet n\u00eb t\u00eb gjitha pajisjet, duke e b\u00ebr\u00eb komunikimin m\u00eb efikas. <\/p>\n

\"Trajnimi
\n
\nKa nj\u00eb m\u00ebnyr\u00eb tjet\u00ebr p\u00ebr t\u00eb specifikuar transmetimin e trafik t\u00eb cil\u00ebn mund ta p\u00ebrdorim - \u00ebsht\u00eb t\u00eb p\u00ebrdorim komand\u00ebn q\u00eb lejon kalimin e t\u00eb dh\u00ebnave vet\u00ebm p\u00ebr VLAN-n\u00eb e specifikuar. Un\u00eb hy n\u00eb cil\u00ebsimet e switch-it SW1, ku m\u00eb intereson porta Fa0\/4, dhe fut komandat int fa0\/4 dhe switchport trunk allowed vlan. Duke ditur q\u00eb SW2 ka vet\u00ebm VLAN10, mund t\u2019i tregoj switch-it SW1 q\u00eb porta e tij trunk t\u00eb lejoj\u00eb vet\u00ebm trafik p\u00ebr k\u00ebt\u00eb rrjet duke aplikuar komand\u00ebn allowed vlan. K\u00ebshtu, e kam programuar port\u00ebn trunk Fa0\/4 p\u00ebr t\u00eb transmetuar trafik vet\u00ebm p\u00ebr VLAN10. Kjo do t\u00eb thot\u00eb se kjo port\u00eb nuk do t\u00eb kaloj\u00eb trafik nga VLAN1, VLAN20 ose ndonj\u00eb rrjet tjet\u00ebr p\u00ebrve\u00e7 atij t\u00eb specifikuar. <\/p>\n

Mund t\u00eb pyesni, \u00e7far\u00eb \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb p\u00ebrdoret - VTP Pruning apo komand\u00ebn allowed vlan. P\u00ebrgjigjja \u00ebsht\u00eb subjektive, sepse n\u00eb disa raste ka kuptim t\u00eb p\u00ebrdoret m\u00ebnyra e par\u00eb, dhe n\u00eb disa - e dyta. Si nj\u00eb administrator rrjeti, ju duhet t\u00eb zgjidhni vet\u00eb zgjidhjen optimale. N\u00eb disa raste, vendimi p\u00ebr t\u00eb programuar port\u00ebn p\u00ebr t\u00eb lejuar trafik nga nj\u00eb VLAN e caktuar mund t\u00eb jet\u00eb i mir\u00eb, ndonj\u00ebher\u00eb - i keq. N\u00eb rastin ton\u00eb, p\u00ebrdorimi i komand\u00ebs allowed vlan mund t\u00eb jet\u00eb i arsyesh\u00ebm n\u00ebse nuk planifikojm\u00eb t\u00eb ndryshojm\u00eb topologjin\u00eb e rrjetit. Por n\u00ebse ndokush m\u00eb von\u00eb do t\u00eb doj\u00eb t\u00eb shtoj\u00eb n\u00eb SW2 nj\u00eb grup pajisjesh q\u00eb p\u00ebrdorin VLAN20, do t\u00eb ishte m\u00eb e arsyeshme t\u00eb aplikohej moda VTP Pruning. <\/p>\n

\"Trajnimi
\n
\nPra, konfigurimi i VTP Pruning p\u00ebrfshin p\u00ebrdorimin e komandave t\u00eb m\u00ebposhtme. Komanda vtp pruning siguron p\u00ebrdorimin automatik t\u00eb k\u00ebsaj mode. N\u00ebse doni t\u00eb konfiguroni manualisht VTP Pruning t\u00eb port\u00ebs trunk p\u00ebr t\u00eb lejuar kalimin e trafik t\u00eb nj\u00eb VLAN t\u00eb caktuar, at\u00ebher\u00eb p\u00ebrdorni komand\u00ebn p\u00ebr t\u00eb zgjedhur numrin e port\u00ebs trunk interface , aktivizoni modin trunk switchport mode trunk dhe lejoni kalimin e trafik t\u00eb rrjetit t\u00eb caktuar me komand\u00ebn switchport trunk allowed vlan .<\/p>\n

N\u00eb komand\u00ebn e fundit, mund t\u00eb p\u00ebrdoren 5 parametra. All do t\u00eb thot\u00eb se lejohet kalimi i trafik t\u00eb t\u00eb gjitha rrjeteve VLAN, none - kalimi i trafik p\u00ebr t\u00eb gjitha VLAN \u00ebsht\u00eb i ndaluar. N\u00ebse p\u00ebrdorni parametrin add, mund t\u00eb shtoni lejen e kalimit t\u00eb trafik nj\u00eb rrjeti tjet\u00ebr. P\u00ebr shembull, n\u00ebse na lejohet trafik VLAN10, me komand\u00ebn add mund t\u00eb lejohet gjithashtu kalimi i trafik t\u00eb rrjetit VLAN20. Komanda remove lejon q\u00eb t\u00eb hiqet nj\u00eb nga rrjetet, p\u00ebr shembull, n\u00ebse p\u00ebrdorni parametrin remove 20, do t\u00eb mbetet vet\u00ebm kalimi i trafik VLAN10. <\/p>\n

Tani e shqyrtojm\u00eb VLAN-in native. Ne tashm\u00eb kemi folur se VLAN-i native p\u00ebrfaq\u00ebson nj\u00eb rrjet virtual p\u00ebr kalimin e trafikut t\u00eb pa-etiketuar p\u00ebrmes nj\u00eb porte t\u00eb caktuar trun. <\/p>\n

\"Trajnimi
\n
\nUn\u00eb hy n\u00eb cil\u00ebsimet e nj\u00eb porte specifike, q\u00eb tregon titulli i komand\u00ebs SW(config-if)#, dhe p\u00ebrdor komand\u00ebn switchport trunk native vlan , p\u00ebr shembull, VLAN10. Tani, gjith\u00eb trafiku i rrjetit VLAN10 do t\u00eb kaloj\u00eb n\u00ebp\u00ebr trun pa etiketa. <\/p>\n

Le t\u00eb kthehemi te topologjia logjike e rrjetit n\u00eb dritaren e Packet Tracer. N\u00ebse p\u00ebrdor komand\u00ebn switchport trunk native vlan 20 p\u00ebr portin e switch-it Fa0\/4, at\u00ebher\u00eb gjith\u00eb trafiku i rrjetit VLAN20 do t\u00eb kaloj\u00eb n\u00ebp\u00ebr trun Fa0\/4 \u2013 SW2 pa etiketa. Kur switch-i SW2 t\u00eb marr\u00eb k\u00ebt\u00eb trafik, ai do t\u00eb mendoj\u00eb: \"kjo \u00ebsht\u00eb trafik pa etiketa, pra un\u00eb duhet ta drejtoj at\u00eb n\u00eb rrjetin VLAN-in native.\" P\u00ebr k\u00ebt\u00eb switch, VLAN-i native \u00ebsht\u00eb rrjeti VLAN1. Rrjetet 1 dhe 20 nuk kan\u00eb asnj\u00eb lidhje, por duke p\u00ebrdorur modalitetin VLAN-it native, ne kemi mund\u00ebsin\u00eb t\u00eb drejtojm\u00eb trafik VLAN20 n\u00eb nj\u00eb rrjet krejt tjet\u00ebr. Megjithat\u00eb, ky trafik do t\u00eb jet\u00eb pa kapsulim, dhe rrjetet gjithsesi duhet t\u00eb p\u00ebrputhen. <\/p>\n

Le t\u00eb shqyrtojm\u00eb k\u00ebt\u00eb me nj\u00eb shembull. Un\u00eb do t\u00eb hy n\u00eb cil\u00ebsimet e SW1 dhe do t\u00eb p\u00ebrdor komand\u00ebn switchport trunk native vlan 10. Tani \u00e7do trafik VLAN10 do t\u00eb dal\u00eb nga porta trun pa etiketa. Kur ai t\u00eb arrij\u00eb n\u00eb portin trun SW2, switch-i do t\u00eb kuptoj\u00eb se duhet ta drejtoj\u00eb at\u00eb n\u00eb VLAN1. Si rezultat i k\u00ebtij vendimi, trafiku nuk do t\u00eb arrij\u00eb n\u00eb kompjuter\u00ebt PC2, 3 dhe 4, pasi ata jan\u00eb lidhur n\u00eb portat e aksesit t\u00eb switch-it, t\u00eb destinuara p\u00ebr VLAN10. <\/p>\n

Teknikisht, kjo do t\u00eb shkaktoj\u00eb shfaqjen e nj\u00eb mesazhi sistemi q\u00eb tregon se VLAN-i native i portit Fa0\/4, i cili \u00ebsht\u00eb pjes\u00eb e VLAN10, nuk p\u00ebrputhet me portin Fa0\/1, i cili p\u00ebrfaq\u00ebson pjes\u00ebn e VLAN1. Ky do t\u00eb thot\u00eb se portet e cituara nuk do t\u00eb jen\u00eb n\u00eb gjendje t\u00eb punojn\u00eb n\u00eb modalitetin trun p\u00ebr shkak t\u00eb mos p\u00ebrputhjes s\u00eb VLAN-it native. <\/p>\n

\"Trajnimi
\n
\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":"

\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u043f\u0440\u043e\u0434\u043e\u043b\u0436\u0438\u043c \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0435\u043d\u0438\u0435 VLAN \u0438 \u043e\u0431\u0441\u0443\u0434\u0438\u043c \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b VTP, \u0430 \u0442\u0430\u043a\u0436\u0435 \u043f\u043e\u043d\u044f\u0442\u0438\u044f VTP Pruning \u0438 Native VLAN. \u0412 \u043e\u0434\u043d\u043e\u043c \u0438\u0437 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0438\u0445 \u0432\u0438\u0434\u0435\u043e \u043c\u044b \u0443\u0436\u0435 \u0433\u043e\u0432\u043e\u0440\u0438\u043b\u0438 \u043e VTP, \u0438 \u043f\u0435\u0440\u0432\u043e\u0435, \u0447\u0442\u043e \u0434\u043e\u043b\u0436\u043d\u043e \u043f\u0440\u0438\u0439\u0442\u0438 \u0432\u0430\u043c \u043d\u0430 \u0443\u043c, \u043a\u043e\u0433\u0434\u0430 \u0432\u044b \u0441\u043b\u044b\u0448\u0438\u0442\u0435 \u043e VTP, \u044d\u0442\u043e \u0442\u043e, \u0447\u0442\u043e \u043e\u043d \u043d\u0435 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u043c \u0442\u0440\u0430\u043d\u043a\u0438\u043d\u0433\u0430, \u043d\u0435\u0441\u043c\u043e\u0442\u0440\u044f \u043d\u0430 \u0442\u043e, \u0447\u0442\u043e \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u00ab\u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u043c \u0442\u0440\u0430\u043d\u043a\u0438\u043d\u0433\u0430 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":27786,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37066","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Trajnimi Cisco 200-125 CCNA v3.0. Dita e 14. VTP, Pruning dhe VLAN-i Native | ProHoster","description":"Sot do t\u00eb vazhdojm\u00eb shqyrtimin e VLAN-\u00ebve dhe do t\u00eb diskutojm\u00eb protokollin VTP, si dhe konceptet VTP Pruning dhe VLAN-in Native.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-14-vtp-pruning-i-native-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 14. VTP, Pruning \u0438 Native VLAN | ProHoster","og:description":"\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u043f\u0440\u043e\u0434\u043e\u043b\u0436\u0438\u043c \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0435\u043d\u0438\u0435 VLAN \u0438 \u043e\u0431\u0441\u0443\u0434\u0438\u043c \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b VTP, \u0430 \u0442\u0430\u043a\u0436\u0435 \u043f\u043e\u043d\u044f\u0442\u0438\u044f VTP Pruning \u0438 Native VLAN.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-14-vtp-pruning-i-native-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:15:33+00:00","article:modified_time":"2019-10-31T19:15:33+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37066","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 05:57:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:34:24","updated":"2026-01-22 05: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\/37066","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=37066"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/37066\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/27786"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=37066"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=37066"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=37066"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}