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

Sot m\u00eb e r\u00ebnd\u00ebsishme, ne do t\u00eb vazhdojm\u00eb me shqyrtimin e VLAN dhe do t\u00eb diskutojm\u00eb p\u00ebr protokollin VTP, si dhe konceptet VTP Pruning dhe Native VLAN. N\u00eb nj\u00eb nga videot e m\u00ebparshme, kemi folur p\u00ebr VTP, dhe gj\u00ebja e par\u00eb q\u00eb duhet t\u00eb vij\u00eb n\u00eb mendje kur d\u00ebgjoni p\u00ebr VTP \u00ebsht\u00eb se ai nuk \u00ebsht\u00eb nj\u00eb protokoll trankimi, pavar\u00ebsisht se quhet \"protokoll trankimi VLAN\".<\/p>\n

\"Trajnimi
\n
\nSi\u00e7 e dini, ekzistojn\u00eb dy protokolle t\u00eb njohura trankimi \u2013 protokolli pron\u00ebsor Cisco ISL, i cili nuk p\u00ebrdoret m\u00eb, dhe protokolli 802.q, i cili p\u00ebrdoret n\u00eb pajisjet rrjet t\u00eb prodhuesve t\u00eb ndrysh\u00ebm p\u00ebr t\u00eb inkapsuluar trafikun e trankimit. Ky protokoll aplikohet gjithashtu n\u00eb nd\u00ebrprer\u00ebsit Cisco. Ne kemi folur se VTP \u00ebsht\u00eb nj\u00eb protokoll p\u00ebr sinkronizimin e VLAN, q\u00eb do t\u00eb thot\u00eb se ai \u00ebsht\u00eb i destinuar p\u00ebr sinkronizimin e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave VLAN n\u00eb t\u00eb gjitha nd\u00ebrprer\u00ebsit e rrjetit. <\/p>\n

\"Trajnimi
\n
\nKemi p\u00ebrmendur m\u00ebnyrat e ndryshme t\u00eb VTP \u2013 server, klient, transparent. N\u00ebse nj\u00eb pajisje p\u00ebrdor m\u00ebnyr\u00ebn server, kjo lejon t\u00eb b\u00ebhen ndryshime, si shtimi ose heqja e VLAN. M\u00ebnyra klient nuk lejon t\u00eb b\u00ebhen ndryshime n\u00eb konfigurimin e nd\u00ebrprer\u00ebsit, mund t\u00eb konfigurohet baza e t\u00eb dh\u00ebnave VLAN vet\u00ebm p\u00ebrmes serverit VTP, dhe ajo do t\u00eb riplikohet n\u00eb t\u00eb gjitha klient\u00ebt VTP. Nd\u00ebrpr\u00ebsi n\u00eb m\u00ebnyr\u00ebn transparent nuk b\u00ebn ndryshime n\u00eb baz\u00ebn e tij t\u00eb t\u00eb dh\u00ebnave VLAN, por thjesht kalon informacionin dhe transferon ndryshimet n\u00eb pajisjen tjet\u00ebr q\u00eb \u00ebsht\u00eb n\u00eb m\u00ebnyr\u00ebn klient. Kjo m\u00ebnyr\u00eb \u00ebsht\u00eb e ngjashme me \u00e7aktivizimin e protokollit VTP n\u00eb nj\u00eb pajisje t\u00eb caktuar, duke e b\u00ebr\u00eb at\u00eb nj\u00eb transportues t\u00eb informacionit 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 kaluar. Ne kemi konfiguruar rrjetin VLAN10 p\u00ebr departamentin e shitjeve dhe rrjetin VLAN20 p\u00ebr departamentin e marketingut, duke i lidhur ato me tre nd\u00ebrprer\u00ebs. <\/p>\n

\"Trajnimi
\n
\nMidis nd\u00ebrprersave SW0 dhe SW1 zbaton lidhja p\u00ebrmes rrjetit VLAN20, nd\u00ebrsa midis SW0 dhe SW2 zbaton lidhja p\u00ebrmes rrjetit VLAN10 fal\u00eb faktit se ne shtuam VLAN10 n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave VLAN t\u00eb nd\u00ebrprer\u00ebsit SW1.
\nP\u00ebr t\u00eb shqyrtuar funksionimin e protokollit VTP, le t\u00eb p\u00ebrdorim nj\u00eb nga nd\u00ebrprersat si VTP-server, le t\u2019i japim emrin SW0. N\u00ebse e mbani mend, q\u00eb t\u00eb gjitha nd\u00ebrprer\u00ebsit punojn\u00eb fillimisht n\u00eb m\u00ebnyr\u00ebn VTP-server. Hyni n\u00eb terminalin e komand\u00ebs s\u00eb nd\u00ebrprersit dhe shkruani komand\u00ebn show vtp status. Ju shihni versionin aktual t\u00eb protokollit VTP \u2013 2 dhe numrin e rishikimit 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 rishikimit 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 specifike e nd\u00ebrprersit Cisco, pasi nd\u00ebrprer\u00ebs t\u00eb ndrysh\u00ebm mund t\u00eb mb\u00ebshtesin numra t\u00eb ndrysh\u00ebm t\u00eb rrjeteve virtuale lokale. Numri i rrjeteve VLAN q\u00eb ekzistojn\u00eb aktualisht \u00ebsht\u00eb 7, dhe pas pak do t\u00eb shqyrtojm\u00eb se \u00e7far\u00eb jan\u00eb k\u00ebto rrjete. M\u00ebnyra e menaxhimit VTP \u00ebsht\u00eb server, emri i domainit nuk \u00ebsht\u00eb caktuar, m\u00ebnyra VTP Pruning \u00ebsht\u00eb \u00e7aktivizuar, do t\u00eb kthehemi n\u00eb k\u00ebt\u00eb m\u00eb von\u00eb. Po ashtu, m\u00ebnyrat VTP V2 dhe VTP Traps Generation jan\u00eb \u00e7aktivizuar. P\u00ebr t\u00eb kaluar provimin 200-125 CCNA, nuk keni nevoj\u00eb t\u00eb dini p\u00ebr dy m\u00ebnyrat e fundit, k\u00ebshtu q\u00eb mund t\u00eb mos shqet\u00ebsoheni p\u00ebr to. <\/p>\n

Le t\u00eb shohim 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 m\u00ebparshme, kemi 4 rrjete t\u00eb papajtueshme: 1002, 1003, 1004 dhe 1005.<\/p>\n

\"Trajnimi
\n
\nK\u00ebtu gjithashtu listohen 2 rrjete q\u00eb krijuam ne VLAN10 dhe 20 dhe rrjeti i parazgjedhur VLAN1. Tani, le t\u00eb kalojm\u00eb n\u00eb nj\u00eb nd\u00ebrpr\u00ebs tjet\u00ebr dhe t\u00eb p\u00ebrdorim t\u00eb nj\u00ebjt\u00ebn komand\u00eb p\u00ebr t\u00eb par\u00eb statusin e VTP. Ju shihni se numri i rishikimit t\u00eb k\u00ebtij nd\u00ebrprer\u00ebsi \u00ebsht\u00eb 3, ai \u00ebsht\u00eb n\u00eb m\u00ebnyr\u00ebn VTP-server dhe e gjith\u00eb informata tjet\u00ebr \u00ebsht\u00eb e ngjashme me nd\u00ebrprersin 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 sa nd\u00ebrpr\u00ebsi SW0, kjo \u00ebsht\u00eb arsyeja pse numri i rishikimit t\u00eb SW1 \u00ebsht\u00eb 3. Ne kemi b\u00ebr\u00eb 3 ndryshime n\u00eb konfigurimin e parazgjedhur t\u00eb nd\u00ebrprersit 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 shohim statusin e SW2. Numri i rishikimit k\u00ebtu \u00ebsht\u00eb 1, dhe kjo \u00ebsht\u00eb e \u00e7uditshme. Ne duhet t\u00eb kemi nj\u00eb rishikim t\u00eb dyt\u00eb, sepse \u00ebsht\u00eb b\u00ebr\u00eb 1 ndryshim n\u00eb konfigurim. Le t\u00eb shohim baz\u00ebn e t\u00eb dh\u00ebnave VLAN.<\/p>\n

\"Trajnimi
\n
\nNe b\u00ebm\u00eb nj\u00eb ndryshim, duke krijuar rrjetin VLAN10, dhe nuk e di pse kjo informacion nuk u p\u00ebrdit\u00ebsua. Ndoshta ka ndodhur p\u00ebr shkak se nuk kemi nj\u00eb rrjet real, por nj\u00eb simulator rrjeti softuerik, q\u00eb mund t\u00eb ket\u00eb gabime. Kur t\u00eb keni mund\u00ebsin\u00eb t\u00eb punoni me pajisje reale gjat\u00eb praktik\u00ebs n\u00eb departamentin e kompanis\u00eb Cisco, kjo do t'ju ndihmoj\u00eb m\u00eb shum\u00eb se 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, i cili p\u00ebrdor sistemin operativ real t\u00eb pajisjes, p\u00ebr shembull, t\u00eb nj\u00eb routeri. Ekziston nj\u00eb ndryshim 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. Emulatori krijon softuerikisht vet\u00ebm pajisjen e vet, por p\u00ebrdor softuerin real p\u00ebr t\u00eb funksionuar. Por n\u00ebse nuk keni mund\u00ebsi t\u00eb punoni me softuerin real Cisco IOS, zgjidhja m\u00eb e mir\u00eb do t\u00eb ishte Packet Tracer. <\/p>\n

Pra, na duhet t\u00eb konfigurojm\u00eb SW0 si server VTP, p\u00ebr k\u00ebt\u00eb un\u00eb hy n\u00eb modin e konfiguraimit global dhe fut komand\u00ebn vtp version 2. Si\u00e7 thash\u00eb, ne mund t\u00eb caktom\u00eb at\u00eb version t\u00eb protokollit q\u00eb na nevojitet - 1 ose 2, n\u00eb k\u00ebt\u00eb rast na nevojitet versioni i dyt\u00eb. M\u00eb pas me komand\u00ebn vtp mode ne p\u00ebrcaktojm\u00eb m\u00ebnyr\u00ebn VTP t\u00eb switch-it - server, klient ose transparent. N\u00eb k\u00ebt\u00eb rast, na nevojitet m\u00ebnyra e serverit, dhe pas futjes s\u00eb komand\u00ebs vtp mode server, sistemi jep nj\u00eb mesazh q\u00eb pajisja tashm\u00eb \u00ebsht\u00eb n\u00eb modin server. M\u00eb pas duhet t\u00eb konfiguroni domenin VTP, p\u00ebr \u00e7far\u00eb p\u00ebrdorim komand\u00ebn vtp domain nwking.org. Pse \u00ebsht\u00eb e nevojshme? N\u00ebse ka nj\u00eb pajisje tjet\u00ebr n\u00eb rrjet me nj\u00eb num\u00ebr m\u00eb t\u00eb lart\u00ebRevisioni, t\u00eb gjitha pajisjet e tjera me nj\u00eb num\u00ebr m\u00eb t\u00eb ul\u00ebt fillojn\u00eb t\u00eb riprodhojn\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 domain. P\u00ebr shembull, n\u00ebse po punoni n\u00eb nwking.org, ju caktosh k\u00ebt\u00eb domain, n\u00ebse n\u00eb Cisco, at\u00ebher\u00eb domenin cisco.com dhe k\u00ebshtu me radh\u00eb. Emri i domenit t\u00eb pajisjeve tuaja t\u00eb kompanis\u00eb lejon q\u00eb ato t\u00eb dallohet nga pajisjet e kompanive t\u00eb tjera ose \u00e7do pajisje tjet\u00ebr t\u00eb jashtme t\u00eb rrjetit. N\u00ebse i caktoni pajisjes nj\u00eb em\u00ebr domaini t\u00eb kompanis\u00eb, at\u00ebher\u00eb e b\u00ebni at\u00eb pjes\u00eb t\u00eb rrjetit t\u00eb k\u00ebsaj kompanie. <\/p>\n

Gj\u00ebja tjet\u00ebr q\u00eb duhet t\u00eb b\u00ebni \u00ebsht\u00eb t\u00eb vendosni fjal\u00ebkalimin VTP. Ai \u00ebsht\u00eb i nevojsh\u00ebm q\u00eb nj\u00eb hacker, duke pasur nj\u00eb pajisje me nj\u00eb num\u00ebr m\u00eb t\u00eb lart\u00eb revisioni, t\u00eb mos mund t\u00eb kopjoj\u00eb cil\u00ebsimet e tij VTP n\u00eb switch-in tuaj. Un\u00eb fut fjal\u00ebkalimin cisco me komand\u00ebn vtp password cisco. Pas k\u00ebsaj, riprodhimi i t\u00eb dh\u00ebnave VTP midis switch-eve do t\u00eb jet\u00eb i mundur vet\u00ebm n\u00ebse fjal\u00ebkalimet p\u00ebrputhen. 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 provojm\u00eb t\u00eb krijojm\u00eb disa VLAN t\u00eb tjera. P\u00ebr k\u00ebt\u00eb un\u00eb p\u00ebrdor komand\u00ebn config t, me komand\u00ebn vlan 200 krijoj rrjetin me numrin 200, i jap emrin TEST dhe i ruaj ndryshimet me komand\u00ebn exit. M\u00eb pas krijoj nj\u00eb tjet\u00ebr rrjet vlan 500 dhe e quaj TEST1. N\u00ebse tani fut komand\u00ebn show vlan, at\u00ebher\u00eb n\u00eb tabel\u00ebn e rrjeteve virtuale t\u00eb switch-it mund t\u00eb shihni k\u00ebto dy rrjete t\u00eb reja, t\u00eb cilave nuk u \u00ebsht\u00eb caktuar asnj\u00eb port. <\/p>\n

\"Trajnimi
\n
\nTani le t\u00eb kalojm\u00eb te SW1 dhe t\u00eb shohim statusin e tij VTP. Ne shohim se k\u00ebtu nuk ka ndryshuar asgj\u00eb, p\u00ebrve\u00e7 emrit t\u00eb domenit, numri i rrjeteve VLAN mbetet 7. Ne nuk shohim shfaqjen e rrjeteve q\u00eb krijuam, sepse fjal\u00ebkalimi VTP nuk p\u00ebrputhet. Le t\u00eb vendosim fjal\u00ebkalimin VTP n\u00eb k\u00ebt\u00eb switch, duke futur nj\u00eb pas nj\u00ebr\u00ebs tjet\u00ebr 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 n\u00eb statusin VTP, p\u00ebr t\u00eb kontrolluar n\u00ebse p\u00ebrdit\u00ebsimi i informacionit kaloi. Si\u00e7 e shihni, numri i VLAN-ve t\u00eb ekzistuese automatikisht u rrit n\u00eb 9. <\/p>\n

N\u00ebse shikoni n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave VLAN t\u00eb k\u00ebtij switch-i, mund t\u00eb shihni se aty automatikisht u shfaq\u00ebn rrjetet e krijuara VLAN200 dhe VLAN500. <\/p>\n

E nj\u00ebjta gj\u00eb duhet t\u00eb b\u00ebhet me switch-in p\u00ebrfundimtar SW2. T\u00eb futim komand\u00ebn show vlan \u2013 shihni se nuk ka pasur asnj\u00eb ndryshim. N\u00eb m\u00ebnyr\u00eb t\u00eb ngjashme, 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 futen 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. \u00cbsht\u00eb nj\u00eb gj\u00eb e shk\u00eblqyer, e cila siguron p\u00ebrdit\u00ebsimin automatik t\u00eb informacionit n\u00eb t\u00eb gjitha pajisjet e rrjetit klient pas ndryshimeve n\u00eb pajisjen server. Nuk keni nevoj\u00eb t\u00eb b\u00ebni ndryshime manuale n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave VLAN t\u00eb t\u00eb gjith\u00eb kall\u00ebpave \u2013 replikimi ndodh automatikisht. N\u00ebse keni 200 pajisje rrjeti, ndryshimet e b\u00ebr\u00eb do t\u00eb ruajn\u00eb n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb n\u00eb t\u00eb gjitha dyqind pajisjet. P\u00ebr siguri, duhet t\u00eb sigurohemi q\u00eb SW2 gjithashtu t\u00eb jet\u00eb nj\u00eb klient VTP, prandaj do t\u00eb hyjm\u00eb n\u00eb konfigurim me komand\u00ebn config t dhe do t\u00eb shkruajm\u00eb komand\u00ebn vtp mode client. <\/p>\n

K\u00ebshtu, n\u00eb rrjetin ton\u00eb, vet\u00ebm kall\u00ebpi i par\u00eb ndodhet n\u00eb modin VTP Server, dy t\u00eb tjer\u00ebt punojn\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\u00eb nj\u00eb mesazh: \"caktimi VTP VLAN nuk lejohet kur pajisja ndodhet n\u00eb modin client\". K\u00ebshtu, nuk mund t\u00eb b\u00ebj asnj\u00eb ndryshim n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave VLAN, n\u00ebse kall\u00ebpi ndodhet n\u00eb modin VTP-client. N\u00ebse dua t\u00eb b\u00ebj ndonj\u00eb ndryshim, duhet t\u00eb kaloj n\u00eb kall\u00ebpin-server. <\/p>\n

Hyni n\u00eb cil\u00ebsimet e terminalit SW0 dhe shkruani 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 kall\u00ebpi, dhe n\u00ebse tani kaloj n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave t\u00eb kall\u00ebpit klient SW2, do t\u00eb shoh q\u00eb informacioni i nj\u00ebjt\u00eb \u00ebsht\u00eb shfaqur k\u00ebtu, kjo do t\u00eb thot\u00eb q\u00eb \u00ebsht\u00eb realizuar replikimi. <\/p>\n

Si\u00e7 e thash\u00eb, VTP \u00ebsht\u00eb nj\u00eb pjes\u00eb e shk\u00eblqyer e software-it, por kur p\u00ebrdoret gabim, ky protokoll mund t\u00eb prish\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 domenit dhe fjal\u00ebkalimi VTP nuk jan\u00eb caktuar. N\u00eb k\u00ebt\u00eb rast, gjith\u00e7ka q\u00eb i nevojitet nj\u00eb hakuesi \u00ebsht\u00eb q\u00eb t\u00eb lidh\u00eb kabllin e kall\u00ebpit t\u00eb tij n\u00eb priz\u00ebn e rrjetit n\u00eb mur, t\u00eb lidh\u00ebt me ndonj\u00eb kall\u00ebp zyre n\u00ebp\u00ebrmjet protokollit DTP dhe pastaj, duke p\u00ebrdorur k\u00ebt\u00eb lidhje, t\u00eb p\u00ebrdit\u00ebsoj\u00eb t\u00eb gjitha informacionet p\u00ebrmes protokollit VTP. N\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, hakuesi mund t\u00eb fshij\u00eb t\u00eb gjitha rrjetet VLAN t\u00eb r\u00ebnd\u00ebsishme, duke e shfryt\u00ebzuar faktin q\u00eb numri i revizionit t\u00eb pajisjes s\u00eb tij \u00ebsht\u00eb m\u00eb i lart\u00eb se numri i revizionit t\u00eb kall\u00ebpeve t\u00eb tjera. Duke e b\u00ebr\u00eb k\u00ebt\u00eb, kall\u00ebpat e kompanis\u00eb automatikisht do t\u00eb z\u00ebvend\u00ebsojn\u00eb t\u00ebr\u00eb informacionin e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave VLAN me informacionin e rekuperuar nga kall\u00ebpi keqdash\u00ebs dhe e gjith\u00eb rrjeti juaj do t\u00eb p\u00ebrfundoj\u00eb. <\/p>\n

Kjo ndodh, pasi kompjuter\u00ebt jan\u00eb lidhur me nj\u00eb kabllo rrjeti n\u00eb nj\u00eb port specifik t\u00eb kall\u00ebpit, t\u00eb cilit i p\u00ebrket rrjeti VLAN 10 ose rrjeti VLAN20. N\u00ebse k\u00ebto rrjete fshihen nga baza e t\u00eb dh\u00ebnave LAN t\u00eb kall\u00ebpit, ai automatikisht do t\u00eb \u00e7aktivizoj\u00eb portin q\u00eb i p\u00ebrket rrjetit t\u00eb paekzistuesh\u00ebm. Zakonisht, rrjeti i kompanis\u00eb mund t\u00eb p\u00ebrfundoj\u00eb pik\u00ebrisht p\u00ebr shkak se kall\u00ebpat thjesht do t\u00eb \u00e7aktivizojn\u00eb portet q\u00eb lidhen me VLAN, t\u00eb cilat jan\u00eb fshir\u00eb gjat\u00eb p\u00ebrdit\u00ebsimeve t\u00eb radh\u00ebs. <\/p>\n

P\u00ebr t\u00eb parandaluar shfaqjen 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 adresave MAC t\u00eb porteve t\u00eb kall\u00ebpeve, 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 adres\u00ebn MAC, porta do t\u00eb \u00e7aktivizohet menj\u00ebher\u00eb. Shpejt do t\u00eb njohim k\u00ebt\u00eb funksion t\u00eb kall\u00ebpeve Cisco, nd\u00ebrsa tani mjafton t\u00eb dini se Port Security garanton q\u00eb VTP t\u00eb jet\u00eb i mbrojtur nga keqb\u00ebr\u00ebsit.<\/p>\n

Le t\u00eb p\u00ebrmbledhim se \u00e7far\u00eb p\u00ebrfaq\u00ebson konfigurimi VTP. Kjo \u00ebsht\u00eb zgjedhja e versionit t\u00eb protokollit \u2013 1 ose 2, caktimi i modit VTP \u2013 server, klient ose transparent. Si\u00e7 e thash\u00eb, ky i fundit nuk p\u00ebrdit\u00ebson baz\u00ebn e t\u00eb dh\u00ebnave VLAN t\u00eb pajisjes vet\u00eb, por thjesht transmeton t\u00eb gjitha ndryshimet te pajisjet fqinj. M\u00eb posht\u00eb jan\u00eb komandat p\u00ebr caktimin e emrit t\u00eb domenit dhe fjal\u00ebkalimit: vtp domain dhe vtp password . <\/p>\n

\"Trajnimi
\n
\nTani t\u00eb flasim p\u00ebr konfigurimet VTP Pruning. N\u00ebse shohim topologjin\u00eb e rrjetit, mund t\u00eb shohim se t\u00eb tri kall\u00ebpat kan\u00eb t\u00eb nj\u00ebjt\u00ebn baz\u00eb t\u00eb dh\u00ebnash VLAN, \u00e7ka do t\u00eb thot\u00eb se rrjetet VLAN10 dhe VLAN20 jan\u00eb pjes\u00eb e t\u00eb tre kall\u00ebpeve. Teknikisht, kall\u00ebpit SW2 nuk i nevojitet rrjeti VLAN20, sepse nuk ka porte t\u00eb lidhura me k\u00ebt\u00eb rrjet. Megjithat\u00eb, pavar\u00ebsisht k\u00ebsaj, t\u00ebr\u00eb trafiku q\u00eb vjen nga kompjuteri Laptop0 n\u00eb rrjetin VLAN20, arrin n\u00eb kall\u00ebpin SW1 dhe nga aty kalon n\u00eb porte t\u00eb SW2. Detyra juaj kryesore si nj\u00eb specialist i rrjetit \u00ebsht\u00eb t\u00eb b\u00ebni q\u00eb n\u00eb rrjet t\u00eb kaloj\u00eb sa m\u00eb pak informacion t\u00eb panevojsh\u00ebm. Duhet t\u00eb siguroheni q\u00eb t\u00eb dh\u00ebnat e nevojshme t\u00eb kalojn\u00eb, por si t\u00eb kufizoni transmetimin e informacionit q\u00eb nuk \u00ebsht\u00eb i nevojsh\u00ebm p\u00ebr k\u00ebt\u00eb pajisje?<\/p>\n

Duhet t\u00eb siguroheni q\u00eb trafiku i destinuar p\u00ebr pajisjet e rrjetit VLAN20 t\u00eb mos kaloj\u00eb n\u00ebp\u00ebr portet SW2 p\u00ebrmes kall\u00ebpit, kur kjo nuk \u00ebsht\u00eb e nevojshme. K\u00ebshtu, trafiku Laptop0 duhet t\u00eb arrij\u00eb te SW1 dhe m\u00eb tej te kompjuter\u00ebt e rrjetit VLAN20, por nuk duhet t\u00eb dal\u00eb p\u00ebrtej portit t\u00eb djatht\u00eb t\u00eb kall\u00ebpit SW1. Kjo mund t\u00eb sigurohet p\u00ebrmes VTP Pruning. <\/p>\n

P\u00ebr k\u00ebt\u00eb, na nevojitet t\u00eb hyjm\u00eb n\u00eb konfigurimin e serverit VTP SW0, sepse si\u00e7 e thash\u00eb, konfigurimet e VTP mund t\u00eb b\u00ebhen vet\u00ebm p\u00ebrmes serverit, duke hyr\u00eb n\u00eb configurimin global dhe duke futur komand\u00ebn vtp pruning. Duke qen\u00eb se Packet Tracer \u00ebsht\u00eb thjesht nj\u00eb program simulator, n\u00eb ndihm\u00ebn e tij p\u00ebr komandat nuk ekziston nj\u00eb komand\u00eb e till\u00eb. Megjithat\u00eb, kur t\u00eb fut komand\u00ebn vtp pruning dhe t\u00eb shtyp \u00abEnter\u00bb, sistemi do t\u00eb informoj\u00eb se moda vtp pruning nuk \u00ebsht\u00eb e disponueshme.<\/p>\n

Duke p\u00ebrdorur komand\u00ebn show vtp status, do t\u00eb shohim q\u00eb moda VTP Pruning \u00ebsht\u00eb n\u00eb gjendje t\u00eb \u00e7aktivizuar, prandaj na nevojitet ta b\u00ebjm\u00eb at\u00eb t\u00eb disponueshme duke e kaluar n\u00eb pozita aktivizuar. Duke e b\u00ebr\u00eb k\u00ebt\u00eb, ne aktivizojm\u00eb mod\u00ebn VTP Pruning n\u00eb t\u00eb tri kalimtar\u00ebt e rrjetit ton\u00eb brenda domenit t\u00eb rrjetit.
\nM\u00eb lejoni t\u00eb ju kujtoj se \u00e7far\u00eb \u00ebsht\u00eb VTP Pruning. Kur ne aktivizojm\u00eb k\u00ebt\u00eb modalitet, serveri SW0 informon kalimtarin SW2 se n\u00eb portet e tij \u00ebsht\u00eb konfigurimi vet\u00ebm i rrjetit VLAN10. M\u00eb pas, kalimtari SW2 informon kalimtarin SW1 se nuk i nevojitet asnj\u00eb trafik p\u00ebrve\u00e7 atij q\u00eb \u00ebsht\u00eb p\u00ebr rrjetin VLAN10. Tani, fal\u00eb VTP Pruning, kalimtari SW1 ka informacionin se nuk i nevojitet t\u00eb d\u00ebrgoj\u00eb trafik VLAN20 p\u00ebrmes kalimit SW1-SW2. <\/p>\n

Kjo \u00ebsht\u00eb shum\u00eb e p\u00ebrshtatshme p\u00ebr ju si administrator t\u00eb rrjetit. Nuk keni nevoj\u00eb t\u00eb futni manualisht komandat, pasi kalimtari \u00ebsht\u00eb mjaft i men\u00e7ur p\u00ebr t\u00eb d\u00ebrguar sakt\u00ebsisht at\u00eb q\u00eb k\u00ebrkon nj\u00eb pajisje t\u00eb caktuar. N\u00ebse nes\u00ebr vendosni t\u00eb instaloni nj\u00eb nj\u00ebsi tjet\u00ebr t\u00eb departamentit t\u00eb marketingut n\u00eb nd\u00ebrtes\u00ebn p\u00ebrball\u00eb dhe t\u00eb lidhni rrjetin e tij VLAN20 me kalimtarin SW2, ky kalimtar do t\u2019i informoj\u00eb menj\u00ebher\u00eb kalimtarin SW1 se tani ka rrjetet VLAN10 dhe VLAN20, dhe do t\u00eb k\u00ebrkoj\u00eb t\u00eb d\u00ebrgoj\u00eb trafikun p\u00ebr t\u00eb dy rrjetet. Ky informacion \u00ebsht\u00eb vazhdimisht i p\u00ebrdit\u00ebsuar n\u00eb t\u00eb gjitha pajisjet, duke e b\u00ebr\u00eb komunikimin m\u00eb efikas. <\/p>\n

\"Trajnimi
\n
\nKa nj\u00eb tjet\u00ebr m\u00ebnyr\u00eb p\u00ebr t\u00eb specifikuar transmetimin e trafikut - \u00ebsht\u00eb t\u00eb p\u00ebrdorim nj\u00eb komand\u00eb q\u00eb lejon d\u00ebrgimin e t\u00eb dh\u00ebnave vet\u00ebm p\u00ebr VLAN e specifikuar. Un\u00eb hyj n\u00eb konfigurimin e kalimtarit SW1, ku m\u00eb intereson porta Fa0\/4, dhe fus komandat int fa0\/4 dhe switchport trunk allowed vlan. Duke qen\u00eb se tashm\u00eb e di se SW2 ka vet\u00ebm VLAN10, mund ta informoj kalimtarin SW1 q\u00eb porta e tij trunk t\u00eb lejoj\u00eb vet\u00ebm trafikun p\u00ebr k\u00ebt\u00eb rrjet, duke aplikuar komand\u00ebn allowed vlan. N\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, e kam programuar portin trunk Fa0\/4 p\u00ebr t\u00eb d\u00ebrguar trafik vet\u00ebm p\u00ebr VLAN10. Kjo do t\u00eb thot\u00eb se ky port nuk do t\u00eb lejoj\u00eb q\u00eb trafik VLAN1, VLAN20 ose ndonj\u00eb rrjeti tjet\u00ebr p\u00ebrve\u00e7 atij t\u00eb cituar t\u00eb kaloj\u00eb m\u00eb tej. <\/p>\n

Mund t\u00eb pyesni se \u00e7far\u00eb t\u00eb p\u00ebrdorni m\u00eb mir\u00eb - VTP Pruning ose komand\u00ebn allowed vlan. P\u00ebrgjigja \u00ebsht\u00eb subjektive, sepse n\u00eb disa raste ka kuptim t\u00eb p\u00ebrdor\u00ebsh m\u00ebnyr\u00ebn e par\u00eb, nd\u00ebrsa n\u00eb disa t\u00eb tjera m\u00ebnyr\u00ebn e dyt\u00eb. Si administrator i rrjetit, duhet ta zgjidhni vet\u00eb zgjidhjen optimale. N\u00eb disa raste, zgjidhja p\u00ebr t\u00eb programuar portin p\u00ebr t\u00eb lejuar trafik t\u00eb nj\u00eb VLAN t\u00eb caktuar mund t\u00eb jet\u00eb e mir\u00eb, nd\u00ebrsa n\u00eb disa raste \u00ebsht\u00eb e keqe. N\u00eb rastin e rrjetit ton\u00eb, p\u00ebrdorimi i komand\u00ebs allowed vlan mund t\u00eb jet\u00eb i drejt\u00eb n\u00ebse nuk planifikojm\u00eb t\u00eb ndryshojm\u00eb topologjin\u00eb e rrjetit. Por n\u00ebse dikush m\u00eb von\u00eb d\u00ebshiron 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 p\u00ebrdorim modalitetin VTP Pruning. <\/p>\n

\"Trajnimi
\n
\nPra, konfigurimi i VTP Pruning p\u00ebrfshin p\u00ebrdorimin e komanda t\u00eb m\u00ebposhtme. Komanda vtp pruning siguron p\u00ebrdorimin automatik t\u00eb k\u00ebsaj \u00ebsht\u00eb. N\u00ebse d\u00ebshironi t\u00eb konfiguroni manualisht VTP Pruning t\u00eb portit trunk p\u00ebr t\u00eb lejuar d\u00ebrgimin e trafikut p\u00ebr nj\u00eb VLAN t\u00eb caktuar, at\u00ebher\u00eb p\u00ebrdorni komand\u00ebn e zgjedhjes s\u00eb numrit t\u00eb portit trunk interface , aktivizoni modalitetin trunk switchport mode trunk dhe lejoni d\u00ebrgimin e trafikut p\u00ebr nj\u00eb rrjet t\u00eb caktuar p\u00ebrmes komand\u00ebs 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 d\u00ebrgimi i trafikut t\u00eb t\u00eb gjitha rrjeteve VLAN, none do t\u00eb thot\u00eb se d\u00ebrgimi i trafikut p\u00ebr t\u00eb gjitha VLAN \u00ebsht\u00eb i ndaluar. N\u00ebse p\u00ebrdorni parametrin add, mund t\u00eb shtoni lejen p\u00ebr t\u00eb d\u00ebrguar trafik p\u00ebr nj\u00eb rrjet tjet\u00ebr. P\u00ebr shembull, ne kemi t\u00eb lejuar trafikun VLAN10, dhe me komand\u00ebn add mund t\u00eb lejojm\u00eb gjithashtu d\u00ebrgimin e trafikut t\u00eb rrjetit VLAN20. Komanda remove lejon q\u00eb t\u00eb hiqni nj\u00eb nga rrjetet, p\u00ebr shembull, n\u00ebse p\u00ebrdorni parametrin remove 20, do t\u00eb mbetet vet\u00ebm d\u00ebrgimi i trafikut VLAN10. <\/p>\n

Tani le t\u2019i hedhim nj\u00eb sy VLAN native. Ne tashm\u00eb kemi folur se VLAN native paraqet nj\u00eb rrjet virtual p\u00ebr t\u00eb kaluar trafik t\u00eb padiskrikuar p\u00ebrmes nj\u00eb porti t\u00eb caktuar trunk. <\/p>\n

\"Trajnimi
\n
\nUn\u00eb hyj n\u00eb konfigurimin e nj\u00eb porti t\u00eb caktuar, t\u00eb cilin e tregon titulli i komand\u00ebs SW(config-if)#, dhe p\u00ebrdor komand\u00ebn switchport trunk native vlan , p\u00ebr shembull, VLAN10. Tani, t\u00eb gjith\u00eb trafiku i rrjetit VLAN10 do t\u00eb kaloj\u00eb p\u00ebrmes trunk pa etiketa. <\/p>\n

Do t\u00eb kthehemi te topologjia logjike e rrjetit n\u00eb dritaren 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 p\u00ebrmes trunk-ut Fa0\/4 \u2013 SW2 pa etiketa. Kur switch-i SW2 t\u00eb marr\u00eb k\u00ebt\u00eb trafik, do t\u00eb mendoj\u00eb: \"ky \u00ebsht\u00eb trafik pa etiket\u00eb, p\u00ebrkundrazi, \u00e7ka do t\u00eb thot\u00eb se duhet ta drejtoj n\u00eb rrjetin native VLAN\". P\u00ebr k\u00ebt\u00eb switch, native VLAN \u00ebsht\u00eb rrjeti VLAN1. Rrjetet 1 dhe 20 nuk jan\u00eb t\u00eb lidhura, por p\u00ebrderisa p\u00ebrdoret moda native VLAN, ne kemi mund\u00ebsin\u00eb ta drejtojm\u00eb trafikun e VLAN20 n\u00eb nj\u00eb rrjet krejt\u00ebsisht tjet\u00ebr. Megjithat\u00eb, ky trafik do t\u00eb jet\u00eb pa kapsulim, dhe rrjetet e vet\u00eb duhet t\u00eb p\u00ebrputhen. <\/p>\n

Le ta shqyrtojm\u00eb k\u00ebt\u00eb me nj\u00eb shembull. Do t\u00eb hyj n\u00eb konfigurimin e SW1 dhe do t\u00eb p\u00ebrdor komand\u00ebn switchport trunk native vlan 10. Tani \u00e7do trafik nga VLAN10 do t\u00eb d\u00ebrgohet nga porti trunk pa etiket\u00eb. Kur t\u00eb arrij\u00eb n\u00eb portin trunk SW2, switch-i do t\u00eb kuptoj\u00eb se duhet ta drejtoj\u00eb n\u00eb VLAN1. Si pasoj\u00eb e k\u00ebsaj vendimmarrjeje, trafiku nuk do t\u00eb arrij\u00eb tek kompjuter\u00ebt PC2, 3 dhe 4, pasi ata jan\u00eb t\u00eb lidhur n\u00eb portet akses t\u00eb switch-it, t\u00eb dedikuara p\u00ebr VLAN10. <\/p>\n

Teknikisht, kjo do t\u00eb shkaktoj\u00eb shfaqjen e nj\u00eb mesazhi n\u00eb sistem q\u00eb thot\u00eb se native VLAN i portit Fa0\/4, i cili \u00ebsht\u00eb pjes\u00eb e VLAN10, nuk p\u00ebrputhet me portin Fa0\/1, i cili \u00ebsht\u00eb pjes\u00eb e VLAN1. Kjo do t\u00eb thot\u00eb se k\u00ebta porte nuk do t\u00eb mund t\u00eb punojn\u00eb n\u00eb modalitetin trunk p\u00ebr shkak t\u00eb mos p\u00ebrputhjes s\u00eb native VLAN. <\/p>\n

\"Trajnimi
\n
\n

\r\n \"Luaj\r\n
<\/div>\r\n <\/div><\/center>
\nFaleminderit q\u00eb jeni me ne. Ju p\u00ebrqejn\u00eb artikujt tan\u00eb? Doni t\u00eb shihni m\u00eb shum\u00eb materiale interesante? Na mb\u00ebshtesni me nj\u00eb porosi ose duke na rekomanduar miqve tuaj, 30% zbritje p\u00ebr p\u00ebrdoruesit e Habra p\u00ebr nj\u00eb alternativ\u00eb unike t\u00eb server\u00ebve entry-level, e cila \u00ebsht\u00eb krijuar nga ne p\u00ebr ju:<\/b> E gjith\u00eb e v\u00ebrteta rreth VPS (KVM) E5-2650 v4 (6 Ndot\u00ebs) 10GB DDR4 240GB SSD 1Gbps nga $20, ose si ta ndash n\u00eb m\u00ebnyr\u00eb t\u00eb duhur serverin?<\/a><\/noindex> (disponohen variante me RAID1 dhe RAID10, deri n\u00eb 24 b\u00ebrthama dhe deri n\u00eb 40GB DDR4).<\/p>\n

Dell R730xd p\u00ebr dy her\u00eb m\u00eb lir\u00eb?<\/b> Vet\u00ebm k\u00ebtu 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\u00ebrtosh nj\u00eb infrastruktur\u00eb t\u00eb klas\u00ebs korporative me p\u00ebrdorimin e server\u00ebve Dell R730xd E5-2650 v4 me \u00e7mim prej 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 14. VTP, Pruning dhe Native VLAN | ProHoster","description":"Sot do t\u00eb vazhdojm\u00eb shqyrtimin e VLAN dhe do t\u00eb diskutojm\u00eb mbi protokollin VTP, si dhe konceptet VTP Pruning dhe Native VLAN. N\u00eb nj\u00eb nga video-t e m\u00ebparshme, ne kemi folur tashm\u00eb p\u00ebr VTP, dhe e para q\u00eb duhet t'ju vie n\u00eb mendje kur d\u00ebgjoni p\u00ebr VTP, \u00ebsht\u00eb se nuk \u00ebsht\u00eb nj\u00eb protokoll trunkingu, p\u00ebrkundrazi, quhet \"protokoll trunkingu\".","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. \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","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}]}}