{"id":37940,"date":"2019-10-31T22:20:41","date_gmt":"2019-10-31T19:20:41","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-35-dinamicheskij-protokol-trankinga-dtp\/"},"modified":"2019-10-31T22:20:41","modified_gmt":"2019-10-31T19:20:41","slug":"trening-cisco-200-125-ccna-v3-0-den-35-dinamicheskij-protokol-trankinga-dtp","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-35-dinamicheskij-protokol-trankinga-dtp","title":{"rendered":"Trajnimi Cisco 200-125 CCNA v3.0. Dita 35. Protokolli dinamik i trunkingut DTP","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Sot e sot do t'i hedhim nj\u00eb v\u00ebshtrim protokollit dinamik t\u00eb dhe DTP dhe VTP \u2013 protokollit t\u00eb trashegesave VLAN. Si\u00e7 e thash\u00eb n\u00eb m\u00ebsimin e kaluar, do t\u00eb ndjekim temat e provimit ICND2 n\u00eb rendin n\u00eb t\u00eb cilin jan\u00eb p\u00ebrmendur n\u00eb faqen e Cisco.<\/p>\n

\"Trajnimi
\n
\nN\u00eb her\u00ebn e kaluar ne shqyrtuam pik\u00ebn 1.1, nd\u00ebrsa sot do t\u00eb shqyrtojm\u00eb 1.2 \u2013 konfigurimi, verifikimi dhe problematikat e lidhjeve t\u00eb switch-ave rrjetit: shtimi dhe heqja e VLAN-eve nga transheti dhe protokollet DTP dhe VTP version 1 dhe 2.<\/a><\/noindex><\/p>\n

T\u00eb gjith\u00eb portet e switch-it jan\u00eb t\u00eb konfiguruar si\u00e7 vjen nga fabrika p\u00ebr t\u00eb p\u00ebrdorur m\u00ebnyr\u00ebn Dynamic Auto t\u00eb protokollit DTP. Kjo do t\u00eb thot\u00eb se kur dy porta t\u00eb switch-ave t\u00eb ndrysh\u00ebm lidhen, automatikisht aktivizohet transheti n\u00ebse nj\u00eb nga portet \u00ebsht\u00eb n\u00eb m\u00ebnyr\u00ebn trunk ose desirable. N\u00ebse t\u00eb dy portet e switch-ave jan\u00eb n\u00eb m\u00ebnyr\u00ebn Dynamic Auto, nuk do t\u00eb formohet transheti. <\/p>\n

\"Trajnimi
\n
\nPrandaj, gjith\u00e7ka varet nga konfigurimi i m\u00ebnyrave t\u00eb pun\u00ebs s\u00eb secilit prej dy switch-ave. P\u00ebr leht\u00ebsi n\u00eb kuptim un\u00eb krijova nj\u00eb tabel\u00eb me kombinime t\u00eb mundshme t\u00eb m\u00ebnyrave DTP t\u00eb dy switch-ave. Shihni se n\u00ebse t\u00eb dy switch-ave p\u00ebrdorin Dynamic Auto, ata nuk formojn\u00eb nj\u00eb transhet, por mbeten n\u00eb m\u00ebnyr\u00ebn Access. Prandaj, n\u00ebse d\u00ebshironi q\u00eb t\u00eb krijoni nj\u00eb transhet nd\u00ebrmjet dy switch-ave, duhet t\u00eb konfiguroni t\u00eb pakt\u00ebn nj\u00eb nga switch-\u00ebt n\u00eb m\u00ebnyr\u00ebn Trunk, ose t\u00eb programoni portin e transhetit p\u00ebr t\u00eb p\u00ebrdorur m\u00ebnyr\u00ebn Dynamic Desirable. Si\u00e7 \u00ebsht\u00eb e dukshme n\u00eb tabel\u00eb, \u00e7do port i switch-it mund t\u00eb jet\u00eb n\u00eb nj\u00eb nga 4 m\u00ebnyrat: Access, Dynamic Auto, Dynamic Desirable ose Trunk. <\/p>\n

N\u00ebse t\u00eb dy portet jan\u00eb t\u00eb konfiguruar n\u00eb Access, switch-at e lidhur do t\u00eb p\u00ebrdorin m\u00ebnyr\u00ebn Access. N\u00ebse nj\u00eb port \u00ebsht\u00eb i konfiguruar n\u00eb Dynamic Auto, dhe tjetri n\u00eb Access, t\u00eb dy do t\u00eb funksionojn\u00eb n\u00eb m\u00ebnyr\u00ebn Access. N\u00ebse nj\u00eb port punon n\u00eb m\u00ebnyr\u00ebn Access, dhe tjetri n\u00eb m\u00ebnyr\u00ebn Trunk, nuk do t\u00eb mund t\u00eb lidhni switch-at, prandaj nj\u00eb kombinim i till\u00eb i m\u00ebnyrave nuk mund t\u00eb p\u00ebrdoret. <\/p>\n

Pra, p\u00ebr t\u00eb funksionuar transheti, \u00ebsht\u00eb e nevojshme q\u00eb nj\u00eb nga portet e switch-ave t\u00eb jet\u00eb i programuar n\u00eb Trunk, dhe tjetri \u2013 n\u00eb Trunk, Dynamic Auto ose Dynamic Desirable. Transheti formohet gjithashtu n\u00ebse t\u00eb dy portet jan\u00eb t\u00eb konfiguruar n\u00eb Dynamic Desirable. <\/p>\n

Dallimi midis Dynamic Desirable dhe Dynamic Auto \u00ebsht\u00eb se n\u00eb m\u00ebnyr\u00ebn e par\u00eb, porta e iniciaton automatikisht transhetin duke d\u00ebrguar kuadrot DTP te porta e switch-it t\u00eb dyt\u00eb. N\u00eb m\u00ebnyr\u00ebn e dyt\u00eb, porta e switch-it pret q\u00eb dikush t\u00eb filloj\u00eb komunikimin, dhe n\u00ebse t\u00eb dy portet e switch-ave jan\u00eb t\u00eb konfiguruar n\u00eb Dynamic Auto, mes tyre nuk do t\u00eb formohet kurr\u00eb transheti. N\u00eb rastin e Dynamic Desirable, situata \u00ebsht\u00eb e kund\u00ebrt \u2013 n\u00ebse t\u00eb dy portet jan\u00eb t\u00eb konfiguruar n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, midis tyre do t\u00eb formohet domosdoshm\u00ebrisht transheti. <\/p>\n

Un\u00eb ju k\u00ebshilloj t\u00eb mbani mend k\u00ebt\u00eb tabel\u00eb, pasi ajo do t'ju ndihmoj\u00eb t\u00eb konfiguroni sakt\u00eb switch-et q\u00eb jan\u00eb t\u00eb lidhur me nj\u00ebri-tjetrin. Le t\u00eb shqyrtojm\u00eb k\u00ebt\u00eb aspekt n\u00eb programin Packet Tracer. Un\u00eb kam lidhur s\u00eb bashku 3 switch-e dhe tani do t\u00eb shfaq n\u00eb ekran dritaret e konsol\u00ebs CLI p\u00ebr secilin nga k\u00ebto pajisje. <\/p>\n

\"Trajnimi
\n
\nN\u00ebse un\u00eb shkruaj komand\u00ebn show int trunk, ne nuk do t\u00eb shohim asnj\u00eb transhet, q\u00eb \u00ebsht\u00eb krejt\u00ebsisht normale p\u00ebr shkak t\u00eb munges\u00ebs s\u00eb konfigurimeve t\u00eb nevojshme, pasi t\u00eb gjitha switch-et jan\u00eb t\u00eb konfiguruar n\u00eb m\u00ebnyr\u00ebn Dynamic Auto. N\u00ebse k\u00ebrkoj t\u00eb tregoj parametrat e nd\u00ebrfaqes f0\/1 t\u00eb switch-it t\u00eb mes\u00ebm, do t\u00eb shihni se n\u00eb m\u00ebnyr\u00ebn e konfigurimeve administrative figuron parametri dynamic auto.<\/p>\n

\"Trajnimi
\n
\nT\u00eb nj\u00ebjtat konfigurime kan\u00eb dhe switch-i i tret\u00eb dhe ai i par\u00eb \u2013 ata gjithashtu kan\u00eb portin f0\/1 n\u00eb m\u00ebnyr\u00ebn dynamic auto. N\u00ebse e mbani mend tabel\u00ebn, p\u00ebr transhetin, t\u00eb gjitha portet duhet t\u00eb jen\u00eb n\u00eb m\u00ebnyr\u00ebn trunk ose nj\u00eb nga portet duhet t\u00eb jet\u00eb n\u00eb m\u00ebnyr\u00ebn Dynamic Desirable. <\/p>\n

T\u00eb futemi n\u00eb konfigurimin e switch-it t\u00eb par\u00eb SW0 dhe t\u00eb konfigurojm\u00eb portin f0\/1. Pas shkruajtur komand\u00ebn switchport mode, sistemi do t\u00eb jap\u00eb sugjerime p\u00ebr parametrat e mundsh\u00ebm t\u00eb m\u00ebnyr\u00ebs: access, dynamic ose trunk. Un\u00eb p\u00ebrdor komand\u00ebn switchport mode dynamic desirable, dhe n\u00eb k\u00ebt\u00eb rast mund ta v\u00ebrejt\u00eb se si porti trunk f0\/1 i switch-it t\u00eb dyt\u00eb, pas k\u00ebsaj komande fillimisht kaloi n\u00eb gjendjen down, dhe pastaj, pas marrjes s\u00eb kuadrit DTP nga switch-i i par\u00eb, kaloi n\u00eb gjendjen up. <\/p>\n

\"Trajnimi
\n
\nTani, n\u00ebse n\u00eb konsol\u00ebn CLI t\u00eb switch-it SW1 shkruaj komand\u00ebn show int trunk, do t\u00eb shohim se porta f0\/1 ndodhet n\u00eb gjendjen e trasheges\u00ebs. Un\u00eb shkruaj t\u00eb nj\u00ebjt\u00ebn komand\u00eb n\u00eb konsol\u00ebn e switch-it SW1 dhe shoh t\u00eb nj\u00ebjt\u00ebn informacion, q\u00eb do t\u00eb thot\u00eb se tani nd\u00ebrmjet switch-eve SW0 dhe SW1 \u00ebsht\u00eb vendosur transheti. N\u00eb k\u00ebt\u00eb rast, porta e switch-it t\u00eb par\u00eb \u00ebsht\u00eb n\u00eb m\u00ebnyr\u00ebn desirable, nd\u00ebrsa porta e dyt\u00eb \u00ebsht\u00eb n\u00eb m\u00ebnyr\u00ebn auto. <\/p>\n

\"Trajnimi
\n
\nNuk ka lidhje nd\u00ebrmjet switch-it t\u00eb dyt\u00eb dhe t\u00eb tret\u00eb, prandaj, un\u00eb kaloj n\u00eb konfigurimin e switch-it t\u00eb tret\u00eb dhe shkruaj komand\u00ebn switchport mode dynamic desirable. Ju shihni se n\u00eb switch-in e dyt\u00eb ndodhin ato t\u00eb nj\u00ebjtat ndryshime gjendjeje down-up, vet\u00ebm tani ata lidhen me portin f0\/2, t\u00eb cilit i jepet lidhja me switch-in 3. Tani, switch-i i dyt\u00eb ka dy transheti: nj\u00eb n\u00eb nd\u00ebrfaqen f0\/1 dhe tjetrin n\u00eb f0\/2. Kjo mund t\u00eb shihet n\u00ebse p\u00ebrdoret komanda show int trunk. <\/p>\n

\"Trajnimi
\n
\nT\u00eb dy portet e switch-it t\u00eb dyt\u00eb jan\u00eb n\u00eb gjendje auto, q\u00eb do t\u00eb thot\u00eb se p\u00ebr t\u00eb b\u00ebr\u00eb trunk me switch-at fqinj, portet e tyre duhet t\u00eb jen\u00eb n\u00eb modalitetin trunk ose desirable, sepse n\u00eb k\u00ebt\u00eb rast ekzistojn\u00eb vet\u00ebm 2 modalitete p\u00ebr t\u00eb vendosur trunkun. Me an\u00eb t\u00eb tabel\u00ebs, ju gjithmon\u00eb mund t\u00eb konfiguroni portet e switch-eve n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb organizoni trunk mes tyre. Ky \u00ebsht\u00eb kuptimi i p\u00ebrdorimit t\u00eb protokollit dinamik t\u00eb trunkingut DTP. <\/p>\n

Le t\u00eb fillojm\u00eb me p\u00ebrshkrimin e protokollit t\u00eb trunkingut VLAN, ose VTP. Ky protokoll siguron sinkronizimin e bazave t\u00eb t\u00eb dh\u00ebnave VLAN p\u00ebr pajisje t\u00eb ndryshme rrjetesh, duke transferuar baz\u00ebn e p\u00ebrdit\u00ebsuar VLAN nga nj\u00eb pajisje n\u00eb tjetr\u00ebn. T\u00eb kthehemi te skema jon\u00eb me 3 switch-e. VTP mund t\u00eb funksionoj\u00eb n\u00eb 3 modalitete: server, client dhe transparent. VTP v3 ka nj\u00eb modalitet tjet\u00ebr t\u00eb quajtur Off, megjithat\u00eb n\u00eb tematik\u00ebn e provimit Cisco shqyrtohen vet\u00ebm versionet e para dhe t\u00eb dyta t\u00eb VTP. <\/p>\n

\"Trajnimi
\n
\nModaliteti Server p\u00ebrdoret p\u00ebr t\u00eb krijuar VLAN t\u00eb reja, p\u00ebr t\u00eb hequr ose ndryshuar rrjetet n\u00ebp\u00ebrmjet komand\u00ebs s\u00eb linj\u00ebs s\u00eb komand\u00ebs s\u00eb switch-it. N\u00eb modalitetin klient nuk \u00ebsht\u00eb e mundur t\u00eb kryhen operacione mbi VLAN, n\u00eb k\u00ebt\u00eb modalitet ndodh vet\u00ebm p\u00ebrdit\u00ebsimi i baz\u00ebs s\u00eb t\u00eb dh\u00ebnave VLAN nga serveri. Modaliteti transparent vepron ashtu si\u00e7 do t\u00eb ishte protokolli VTP i \u00e7aktivizuar, q\u00eb do t\u00eb thot\u00eb se switch-i nuk d\u00ebrgon mesazhe t\u00eb veta VTP, por transmeton p\u00ebrdit\u00ebsimet nga switch-at e tjer\u00eb - po qe se p\u00ebrdit\u00ebsimi arrin n\u00eb nj\u00eb nga portet e switch-it, ai e kalon at\u00eb dhe e d\u00ebrgon m\u00eb tej n\u00eb rrjet p\u00ebrmes nj\u00eb porti tjet\u00ebr. N\u00eb modalitetin transparent, switch-i thjesht sh\u00ebrben si nj\u00eb transmetues i mesazheve t\u00eb huaja, duke mos p\u00ebrdit\u00ebsuar baz\u00ebn e tij t\u00eb t\u00eb dh\u00ebnave VLAN.
\nN\u00eb k\u00ebt\u00eb slajd ju shihni komandat e konfigurimit t\u00eb protokollit VTP, t\u00eb futur n\u00eb modalitetin e konfigurimit global. Komanda e par\u00eb mund t\u00eb ndryshoj\u00eb versionin e p\u00ebrdorur t\u00eb protokollit. Komanda e dyt\u00eb zgjidh modalitetin e funksionimit VTP.<\/p>\n

\"Trajnimi
\n
\nN\u00ebse d\u00ebshironi t\u00eb krijoni nj\u00eb domen VTP, p\u00ebrdoret komanda vtp domain , dhe p\u00ebr t\u00eb vendosur fjal\u00ebkalimin VTP duhet t\u00eb shkruani komand\u00ebn vtp password . Le t\u00eb kalojm\u00eb n\u00eb konsol\u00ebn CLI t\u00eb switch-it t\u00eb par\u00eb dhe t\u00eb shikojm\u00eb statusin e VTP, duke futur komand\u00ebn show vtp status.<\/p>\n

\"Trajnimi
\n
\nJu shihni versionin e protokollit VTP - e dyta, numri maksimal i VLAN-ve t\u00eb mb\u00ebshtetur \u00ebsht\u00eb 255, numri i VLAN-ve ekzistuese \u00ebsht\u00eb 5 dhe modaliteti i funksionimit t\u00eb VLAN \u00ebsht\u00eb server. T\u00eb gjitha k\u00ebto jan\u00eb parametra sipas parazgjedhjes. Ne tashm\u00eb e kemi diskutuar VTP n\u00eb m\u00ebsimin 'Dita 30', k\u00ebshtu q\u00eb n\u00ebse keni harruar di\u00e7ka, mund t\u00eb ktheheni dhe ta shikoni k\u00ebt\u00eb video p\u00ebrs\u00ebri. <\/p>\n

P\u00ebr t\u00eb par\u00eb baz\u00ebn e t\u00eb dh\u00ebnave VLAN, un\u00eb fut komand\u00ebn show vlan brief. K\u00ebtu shihen VLAN1 dhe VLAN1002-1005. Rrjeti i par\u00eb sipas rregullit \u00ebsht\u00eb i lidhur me t\u00eb gjitha portet e lira t\u00eb switch-it - 23 porte Fast Ethernet dhe 2 porte Gigabit Ethernet, nd\u00ebrsa 4 VLAN t\u00eb tjera nuk mb\u00ebshteten. Baza e t\u00eb dh\u00ebnave VLAN e dy switch-eve t\u00eb tjera duket sakt\u00ebsisht ashtu si\u00e7 \u00ebsht\u00eb, p\u00ebrve\u00e7 se SW1 ka 22 porte t\u00eb lira Fast Ethernet p\u00ebr VLAN, pasi f0\/1 dhe f0\/2 jan\u00eb t\u00eb z\u00ebna p\u00ebr trunking. M\u00eb lejoni t'ju kujtoj at\u00eb q\u00eb u diskutua n\u00eb m\u00ebsimin 'Dita 30' - protokolli VTP mb\u00ebshtet vet\u00ebm p\u00ebrdit\u00ebsimin e bazave t\u00eb t\u00eb dh\u00ebnave VLAN. <\/p>\n

Pra, n\u00ebse kam konfigurated disa porte p\u00ebr t\u00eb punuar me rrjetet VLAN me komandat switchport access dhe switchport mode access VLAN10, VLAN20 ose VLAN30, konfigurimi i k\u00ebtyre porteve nuk do t\u00eb riplikohet me VTP, sepse VTP p\u00ebrdit\u00ebson vet\u00ebm baz\u00ebn e t\u00eb dh\u00ebnave VLAN.
\nK\u00ebshtu, n\u00ebse nj\u00eb nga portet SW1 \u00ebsht\u00eb konfiguruar p\u00ebr t\u00eb punuar me VLAN20, por ky rrjet nuk ka qen\u00eb n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave VLAN, at\u00ebher\u00eb porti do t\u00eb \u00e7aktivizohet. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, p\u00ebrdit\u00ebsimi i bazave t\u00eb t\u00eb dh\u00ebnave ndodh vet\u00ebm me p\u00ebrdorimin e protokollit VTP. <\/p>\n

Me komand\u00ebn show vtp status un\u00eb shoh se t\u00eb 3 switch-at tani jan\u00eb n\u00eb modalitetin server. Do ta \u00e7vendos SW1 mesatar n\u00eb modalitet transparent me komand\u00ebn vtp mode transparent, nd\u00ebrsa switch-i i tret\u00eb SW2 n\u00eb modalitet klient me komand\u00ebn vtp mode client. <\/p>\n

Tani kthehemi te switch-i i par\u00eb SW0 dhe krijojm\u00eb domenin nwking.org me komand\u00ebn vtp domain . N\u00ebse tani e shikoni statusin e VTP t\u00eb switch-it t\u00eb dyt\u00eb, i cili ndodhet n\u00eb modalitet transparent, \u00ebsht\u00eb t\u00ebr\u00ebsisht e qart\u00eb se ai nuk reagoi n\u00eb krijimin e domenit - fusha VTP Domain Name mbeti e zbraz\u00ebt. Megjithat\u00eb, switch-i i tret\u00eb, q\u00eb \u00ebsht\u00eb n\u00eb modalitet klient, p\u00ebrdit\u00ebsoi baz\u00ebn e tij t\u00eb t\u00eb dh\u00ebnave dhe tani ka emrin e domenit VTP - nwking.org. K\u00ebshtu, p\u00ebrdit\u00ebsimi i baz\u00ebs s\u00eb t\u00eb dh\u00ebnave t\u00eb switch-it SW0 kaloi p\u00ebrmes SW1 dhe u reflektua n\u00eb SW2. <\/p>\n

Tani do t\u00eb p\u00ebrpiqem t\u00eb ndryshoj emrin e caktuar t\u00eb domenit, p\u00ebr k\u00ebt\u00eb do t\u00eb hyj n\u00eb cil\u00ebsimet e SW0 dhe do t\u00eb shkruaj komand\u00ebn vtp domain NetworKing. Si\u00e7 shihet, k\u00ebt\u00eb her\u00eb nuk ndodhi p\u00ebrdit\u00ebsimi - emri i domenit VTP n\u00eb switch-in e tret\u00eb mbeti i nj\u00ebjt\u00eb. Arsyeja \u00ebsht\u00eb se nj\u00eb p\u00ebrdit\u00ebsim t\u00eb till\u00eb t\u00eb emrit t\u00eb domenit ndodh vet\u00ebm 1 her\u00eb kur ndryshohet domeni sipas parazgjedhjes. N\u00ebse pas k\u00ebsaj emri i domenit VTP ndryshohet p\u00ebrs\u00ebri, ka nevoj\u00eb p\u00ebr ta ndryshuar at\u00eb manualisht n\u00eb switch-at e tjer\u00eb. <\/p>\n

Aktualisht po krijoj n\u00eb konsol\u00ebn CLI t\u00eb \u00e7switch-it t\u00eb par\u00eb rrjetin VLAN100 dhe do ta quaj at\u00eb IMRAN. Ai u shfaq n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave VLAN t\u00eb \u00e7switch-it t\u00eb par\u00eb, por nuk u shfaq n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave t\u00eb \u00e7switch-it t\u00eb tret\u00eb, sepse k\u00ebto jan\u00eb domain t\u00eb ndryshme. Mbani mend se azhurnimi i baz\u00ebs s\u00eb t\u00eb dh\u00ebnave VLAN ndodh vet\u00ebm n\u00ebse t\u00eb dy \u00e7switch-et kan\u00eb t\u00eb nj\u00ebjtin domain, ose, si\u00e7 e tregova m\u00eb par\u00eb, nj\u00eb em\u00ebr i ri dom\u00ebni vendoset n\u00eb vend t\u00eb emrit t\u00eb paracaktuar. <\/p>\n

Hyr n\u00eb cil\u00ebsimet e \u00e7switch-it t\u00eb tret\u00eb dhe fut me rend t\u00eb p\u00ebrs\u00ebritsh\u00ebm komandat vtp mode dhe vtp domain NetworKing. Vini re se futja e emrit ndjehet e ndjeshme ndaj rastit, k\u00ebshtu q\u00eb shkrimi i emrit t\u00eb domenit duhet t\u00eb p\u00ebrputhet plot\u00ebsisht p\u00ebr t\u00eb dy \u00e7switch-et. Tani, rip\u00ebrkthej SW2 n\u00eb m\u00ebnyr\u00ebn klient me komand\u00ebn vtp mode client. Le t\u00eb shohim se \u00e7far\u00eb do t\u00eb ndodh\u00eb. Si\u00e7 e shihni, tani, me p\u00ebrputhjen e emrit t\u00eb domenit, baza e t\u00eb dh\u00ebnave t\u00eb SW2 u azhurnua dhe u shfaq rrjeti i ri VLAN100 IMRAN, nd\u00ebrsa k\u00ebto ndryshime nuk kan\u00eb ndikuar n\u00eb \u00e7switch-in e mes\u00ebm, sepse ai \u00ebsht\u00eb n\u00eb m\u00ebnyr\u00eb transparente. <\/p>\n

N\u00ebse d\u00ebshironi t\u00eb mbroheni nga akseset e paautorizuara, mund t\u00eb krijoni nj\u00eb fjal\u00ebkalim VTP. N\u00eb k\u00ebt\u00eb rast, duhet t\u00eb siguroni q\u00eb pajisja n\u00eb an\u00ebn tjet\u00ebr t\u00eb ket\u00eb pik\u00ebrisht t\u00eb nj\u00ebjtin fjal\u00ebkalim, sepse vet\u00ebm k\u00ebshtu ajo do t\u00eb mund t\u00eb pranoj\u00eb azhurnimet VTP. <\/p>\n

Gjithashtu, ajo q\u00eb do t\u00eb shqyrtojm\u00eb \u00ebsht\u00eb VTP pruning, ose \"prerja\" e VLAN-ve t\u00eb pap\u00ebrdorura. N\u00ebse keni 100 pajisje n\u00eb rrjet q\u00eb p\u00ebrdorin protokollin VTP, at\u00ebher\u00eb azhurnimi i baz\u00ebs s\u00eb t\u00eb dh\u00ebnave VLAN t\u00eb nj\u00eb pajisjeje do t\u00eb riplikohet automatikisht n\u00eb 99 pajisjet e tjera. Megjithat\u00eb, jo t\u00eb gjitha k\u00ebto pajisje kan\u00eb rrjetet VLAN t\u00eb p\u00ebrmendura n\u00eb azhurnim, prandaj informacioni p\u00ebr to mund t\u00eb mos jet\u00eb i nevojsh\u00ebm. <\/p>\n

\"Trajnimi<\/p>\n

D\u00ebrgimi i azhurnimeve t\u00eb baz\u00ebs s\u00eb t\u00eb dh\u00ebnave VLAN n\u00eb pajisjet q\u00eb p\u00ebrdorin VTP, do t\u00eb thot\u00eb q\u00eb t\u00eb gjith\u00eb portat e t\u00eb gjitha pajisjeve do t\u00eb marrin informacion p\u00ebr VLAN-t\u00eb e shtuar, t\u00eb fshira dhe t\u00eb ndryshuara, p\u00ebr t\u00eb cilat ata mund t\u00eb mos ken\u00eb asnj\u00eb lidhje. Kjo sjell q\u00eb rrjeti t\u00eb mbushet me trafik t\u00eb panevojsh\u00ebm. P\u00ebr t\u00eb shmangur k\u00ebt\u00eb, p\u00ebrdoret koncepti i \"prerjes\" VTP. P\u00ebr t\u00eb aktivizuar n\u00eb \u00e7switch m\u00ebnyr\u00ebn \"prerje\" t\u00eb VLAN-ve joaktuale, p\u00ebrdoret komanda vtp pruning. Pasi kjo t\u00eb b\u00ebhet, \u00e7switch-et do t\u00eb njoftojn\u00eb automatikisht nj\u00ebri-tjetrin se cilat VLAN p\u00ebrdorin n\u00eb t\u00eb v\u00ebrtet\u00eb, duke njoftuar fqinj\u00ebt se nuk kan\u00eb nevoj\u00eb t\u00eb d\u00ebrgojn\u00eb azhurnime p\u00ebr rrjetet q\u00eb nuk jan\u00eb t\u00eb lidhura me to.<\/p>\n

P\u00ebr shembull, n\u00ebse SW2 nuk ka asnj\u00eb port VLAN10, at\u00ebher\u00eb nuk ka nevoj\u00eb q\u00eb SW1 t'i d\u00ebrgoj\u00eb trafik p\u00ebr k\u00ebt\u00eb rrjet. Nj\u00ebkoh\u00ebsisht, \u00e7switch-i SW1 ka nevoj\u00eb p\u00ebr trafik VLAN10, sepse nj\u00eb nga portat e tij \u00ebsht\u00eb i lidhur me k\u00ebt\u00eb rrjet, por nuk ka nevoj\u00eb t\u00eb d\u00ebrgoj\u00eb k\u00ebt\u00eb trafik te \u00e7switch-i SW2.
\nPrandaj, n\u00ebse SW2 p\u00ebrdor m\u00ebnyr\u00ebn vtp pruning, ai njofton SW1: \"t\u00eb lutem, mos m\u00eb d\u00ebrgo trafik p\u00ebr VLAN10, sepse ky rrjet nuk \u00ebsht\u00eb i lidhur me mua dhe asnj\u00eb nga portat e mia nuk \u00ebsht\u00eb i konfiguruar p\u00ebr t\u00eb punuar me k\u00ebt\u00eb rrjet\". Kjo \u00ebsht\u00eb ajo q\u00eb ofron p\u00ebrdorimi i komand\u00ebs vtp pruning. <\/p>\n

Ekziston gjithashtu nj\u00eb m\u00ebnyr\u00eb tjet\u00ebr p\u00ebr filtrimin e trafikut p\u00ebr nj\u00eb nd\u00ebrfaqe t\u00eb caktuar. Ajo lejon t\u00eb konfigurosh nj\u00eb port si tranzit me nj\u00eb rrjet t\u00eb caktuar VLAN. Disavantazhi i k\u00ebsaj metode \u00ebsht\u00eb se k\u00ebrkohet konfigurimi manual i \u00e7do porti tranzit, t\u00eb cilit do t'i nevojitet t\u00eb tregoj\u00eb se cilat VLAN jan\u00eb t\u00eb lejuara dhe cilat jan\u00eb t\u00eb ndaluara. P\u00ebr k\u00ebt\u00eb, p\u00ebrdoren nj\u00eb sekuenc\u00eb e 3 komandave. E para p\u00ebrcakton nd\u00ebrfaqen, e cila \u00ebsht\u00eb n\u00ebn k\u00ebto kufizime; e dyta e shnd\u00ebrron k\u00ebt\u00eb nd\u00ebrfaqe n\u00eb port tranzit, nd\u00ebrsa e treta \u2014 switchport trunk allowed vlan \u2014 tregon se cila VLAN \u00ebsht\u00eb e lejuar n\u00eb k\u00ebt\u00eb port: t\u00eb gjitha, asnj\u00eb, VLAN e shtuar ose VLAN e hequr. <\/p>\n

Var\u00ebsisht nga situata specifike, ju zgjidhni se \u00e7far\u00eb t\u00eb p\u00ebrdorni: VTP pruning ose Trunk allowed. Disa organizata preferojn\u00eb t\u00eb mos p\u00ebrdorin VTP p\u00ebr arsye sigurie, prandaj zgjidhin konfigurimin manual t\u00eb tranziteve. Duke qen\u00eb se komanda vtp pruning nuk funksionon n\u00eb Packet Tracer, do ta tregoj at\u00eb n\u00eb emulatorin GNS3. <\/p>\n

N\u00ebse hyni n\u00eb cil\u00ebsimet e SW2 dhe shkruani komand\u00ebn vtp pruning, sistemi do t'ju njoftoj\u00eb menj\u00ebher\u00eb se ky mod \u00ebsht\u00eb aktivizuar: Pruning switched on, pra \"prerja\" e VLAN aktivizohet me vet\u00ebm nj\u00eb komand\u00eb. <\/p>\n

N\u00ebse shkruani komand\u00ebn show vtp status, do t\u00eb shihni se m\u00ebnyra vtp pruning \u00ebsht\u00eb e lejuar. <\/p>\n

\"Trajnimi
\n
\nN\u00ebse jeni duke konfiguruar k\u00ebt\u00eb mod n\u00eb \u00e7switch-in server, at\u00ebher\u00eb hyni n\u00eb cil\u00ebsimet e tij dhe shkruani komand\u00ebn vtp pruning. Kjo do t\u00eb thot\u00eb q\u00eb pajisjet e lidhura me serverin do t\u00eb fillojn\u00eb automatikisht t\u00eb p\u00ebrdorin vtp pruning, p\u00ebr t\u00eb minimizuar trafik tranziti p\u00ebr VLAN-t\u00eb joaktuale. <\/p>\n

N\u00ebse nuk d\u00ebshironi t\u00eb p\u00ebrdorni k\u00ebt\u00eb mod, duhet t\u00eb hyni n\u00eb nj\u00eb nd\u00ebrfaqe specifike, p\u00ebr shembull, e0\/0, dhe pastaj t\u00eb shkruani komand\u00ebn switchport trunk allowed vlan. Sistemi do t'ju ofroj\u00eb sugjerime p\u00ebr opsionet e mundshme t\u00eb k\u00ebsaj komande: <\/p>\n

\u2014 NUMRI \u2014 VLAN, e cila do t\u00eb jet\u00eb e lejuar n\u00eb k\u00ebt\u00eb nd\u00ebrfaqe n\u00eb modalitetin trunk;
\n \u2014 shto \u2014 VLAN, q\u00eb duhet t\u00eb shtohet n\u00eb list\u00ebn e baz\u00ebs s\u00eb dh\u00ebnave VLAN;
\n \u2014 t\u00eb gjitha \u2014 t\u00eb lejoj\u00eb t\u00eb gjith\u00eb VLAN;
\n \u2014 p\u00ebrve\u00e7 \u2014 t\u00eb lejoj\u00eb t\u00eb gjith\u00eb VLAN, p\u00ebrve\u00e7 atyre t\u00eb p\u00ebrmendura;
\n \u2014 asnj\u00eb \u2013 ndalon t\u00eb gjith\u00eb VLAN;
\n \u2014 hiq \u2013 heq VLAN nga lista e baz\u00ebs s\u00eb dh\u00ebnave VLAN. <\/p>\n

P\u00ebr shembull, n\u00ebse kemi lejuar trunk p\u00ebr VLAN10 dhe d\u00ebshirojm\u00eb ta lejojm\u00eb p\u00ebr VLAN20, duhet t\u00eb japim komand\u00ebn switchport trunk allowed vlan add 20. <\/p>\n

\"Trajnimi
\n
\nDua t'ju tregoj di\u00e7ka tjet\u00ebr, prandaj p\u00ebrdor komand\u00ebn show interface trunk. Vini re se si p\u00ebr default p\u00ebr trunk jan\u00eb lejuar t\u00eb gjith\u00eb VLAN 1-1005, dhe tani u shtua edhe VLAN10. <\/p>\n

\"Trajnimi
\n
\nN\u00ebse p\u00ebrdor komand\u00ebn switchport trunk allowed vlan add 20 dhe p\u00ebrs\u00ebri k\u00ebrkoj t\u00eb tregoj statusin e trunking, ne do t\u00eb shohim se tani jan\u00eb lejuar dy VLAN \u2013 VLAN10 dhe VLAN20. <\/p>\n

\"Trajnimi
\n
\nN\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, asnj\u00eb trafik tjet\u00ebr, p\u00ebrve\u00e7 atij t\u00eb destinuar p\u00ebr VLAN e p\u00ebrmendura, nuk do t\u00eb mund t\u00eb kaloj\u00eb p\u00ebrmes k\u00ebtij trunk. Duke lejuar trafik vet\u00ebm p\u00ebr VLAN 10 dhe VLAN 20, ne ndaluam trafik p\u00ebr t\u00eb gjitha VLAN t\u00eb tjera. K\u00ebtu \u00ebsht\u00eb si mund t\u00eb konfigurohen manualisht parametrat e trunking p\u00ebr nj\u00eb VLAN t\u00eb ve\u00e7ant\u00eb n\u00eb nj\u00eb nd\u00ebrfaqe specifike t\u00eb switch-it. <\/p>\n

Vini re se deri n\u00eb fund t\u00eb dit\u00ebs m\u00eb 17 n\u00ebntor 2017, ne kemi nj\u00eb zbritje prej 90% n\u00eb \u00e7mimin e shkarkimit t\u00eb laboratorit p\u00ebr k\u00ebt\u00eb tem\u00eb. <\/p>\n

\"Trajnimi
\n
\nFaleminderit p\u00ebr v\u00ebmendjen dhe deri n\u00eb takimin ton\u00eb n\u00eb video m\u00ebsimin e ardhshem!<\/p>\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 \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0434\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b \u0442\u0440\u0430\u043d\u043a\u0438\u043d\u0433\u0430 DTP \u0438 VTP \u2013 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b \u0442\u0440\u0430\u043d\u043a\u0438\u043d\u0433\u0430 VLAN. \u041a\u0430\u043a \u044f \u0433\u043e\u0432\u043e\u0440\u0438\u043b \u043d\u0430 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0435\u043c \u0443\u0440\u043e\u043a\u0435, \u043c\u044b \u0431\u0443\u0434\u0435\u043c \u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u044c \u0442\u0435\u043c\u0430\u043c \u044d\u043a\u0437\u0430\u043c\u0435\u043d\u0430 ICND2 \u0432 \u0442\u043e\u043c \u043f\u043e\u0440\u044f\u0434\u043a\u0435, \u0432 \u043a\u043e\u0442\u043e\u0440\u043e\u043c \u043e\u043d\u0438 \u043f\u0440\u0438\u0432\u0435\u0434\u0435\u043d\u044b \u043d\u0430 \u0441\u0430\u0439\u0442\u0435 Cisco. \u0412 \u043f\u0440\u043e\u0448\u043b\u044b\u0439 \u0440\u0430\u0437 \u043c\u044b \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0435\u043b\u0438 \u043f\u0443\u043d\u043a\u0442 1.1, \u0430 \u0441\u0435\u0433\u043e\u0434\u043d\u044f \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c 1.2 \u2013 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430, \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0430 \u0438 \u043d\u0435\u043f\u043e\u043b\u0430\u0434\u043a\u0438 \u0441\u043e\u0435\u0434\u0438\u043d\u0435\u043d\u0438\u0439 \u0441\u0435\u0442\u0435\u0432\u044b\u0445 \u043a\u043e\u043c\u043c\u0443\u0442\u0430\u0442\u043e\u0440\u043e\u0432: \u0434\u043e\u0431\u0430\u0432\u043b\u0435\u043d\u0438\u0435 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28471,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37940","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 35. Protokolli dinamik i trankimit DTP | ProHoster","description":"Sot ne do t\u00eb shqyrtojm\u00eb protokollin dinamik t\u00eb trunking DTP dhe VTP \u2013 protokollin e trunking VLAN. Si\u00e7 thash\u00eb n\u00eb m\u00ebsimin e kaluar, do t\u00eb ndjekim temat e provimit ICND2 n\u00eb rendin n\u00eb t\u00eb cilin ato jan\u00eb paraqitur n\u00eb faqen e Cisco. Data e kaluar shqyrtuam pik\u00ebn 1.1, dhe sot do t\u00eb shqyrtojm\u00eb 1.2 \u2013 konfigurimin, verifikimin dhe zgjidhjen e problemeve t\u00eb lidhjeve t\u00eb switcheve rrjet\u00eb: shtimi","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-35-dinamicheskij-protokol-trankinga-dtp","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 35. \u0414\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b \u0442\u0440\u0430\u043d\u043a\u0438\u043d\u0433\u0430 DTP | ProHoster","og:description":"\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0434\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b \u0442\u0440\u0430\u043d\u043a\u0438\u043d\u0433\u0430 DTP \u0438 VTP \u2013 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b \u0442\u0440\u0430\u043d\u043a\u0438\u043d\u0433\u0430 VLAN. \u041a\u0430\u043a \u044f \u0433\u043e\u0432\u043e\u0440\u0438\u043b \u043d\u0430 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0435\u043c \u0443\u0440\u043e\u043a\u0435, \u043c\u044b \u0431\u0443\u0434\u0435\u043c \u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u044c \u0442\u0435\u043c\u0430\u043c \u044d\u043a\u0437\u0430\u043c\u0435\u043d\u0430 ICND2 \u0432 \u0442\u043e\u043c \u043f\u043e\u0440\u044f\u0434\u043a\u0435, \u0432 \u043a\u043e\u0442\u043e\u0440\u043e\u043c \u043e\u043d\u0438 \u043f\u0440\u0438\u0432\u0435\u0434\u0435\u043d\u044b \u043d\u0430 \u0441\u0430\u0439\u0442\u0435 Cisco. \u0412 \u043f\u0440\u043e\u0448\u043b\u044b\u0439 \u0440\u0430\u0437 \u043c\u044b \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0435\u043b\u0438 \u043f\u0443\u043d\u043a\u0442 1.1, \u0430 \u0441\u0435\u0433\u043e\u0434\u043d\u044f \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c 1.2 \u2013 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430, \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0430 \u0438 \u043d\u0435\u043f\u043e\u043b\u0430\u0434\u043a\u0438 \u0441\u043e\u0435\u0434\u0438\u043d\u0435\u043d\u0438\u0439 \u0441\u0435\u0442\u0435\u0432\u044b\u0445 \u043a\u043e\u043c\u043c\u0443\u0442\u0430\u0442\u043e\u0440\u043e\u0432: \u0434\u043e\u0431\u0430\u0432\u043b\u0435\u043d\u0438\u0435","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-35-dinamicheskij-protokol-trankinga-dtp","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:20:41+00:00","article:modified_time":"2019-10-31T19:20:41+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37940","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-23 19:51:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:18:22","updated":"2026-01-23 19:51: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\/37940","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=37940"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/37940\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/28471"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=37940"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=37940"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=37940"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}