{"id":37988,"date":"2019-10-31T22:21:01","date_gmt":"2019-10-31T19:21:01","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-37-stp-vybor-root-bridge-funktsii-portfast-i-bpdu-guard-chast-2\/"},"modified":"2019-10-31T22:21:01","modified_gmt":"2019-10-31T19:21:01","slug":"trening-cisco-200-125-ccna-v3-0-den-37-stp-vybor-root-bridge-funktsii-portfast-i-bpdu-guard-chast-2","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-37-stp-vybor-root-bridge-funktsii-portfast-i-bpdu-guard-chast-2","title":{"rendered":"Trajnimi Cisco 200-125 CCNA v3.0. Dita 37. STP: zgjedhja e Root Bridge, funksionet PortFast dhe BPDU guard. Pjesa 2","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Supozoni q\u00eb STP \u00ebsht\u00eb n\u00eb nj\u00eb gjendje konvergjence. \u00c7far\u00eb do t\u00eb ndodh\u00eb n\u00ebse un\u00eb marr nj\u00eb kabllo dhe lidh switchin N direkt me switchin rr\u00ebnj\u00eb A? Root Bridge do t\u00eb \"shoh\u00eb\" se ka nj\u00eb port t\u00eb ri t\u00eb angazhuar dhe do t\u00eb d\u00ebrgoj\u00eb BPDU p\u00ebrmes tij. <\/p>\n

\"Trajnimi
\n
\nSwitchi N, pasi merr k\u00ebt\u00eb frame me kosto zero, do t\u00eb p\u00ebrcaktoj\u00eb kostot e rrug\u00ebs p\u00ebrmes portit t\u00eb ri si 0+19 = 19, nd\u00ebrsa kostoja e portit t\u00eb tij rr\u00ebnj\u00eb \u00ebsht\u00eb 76. Pas k\u00ebsaj, porti i switchit N, i cili m\u00eb par\u00eb ishte n\u00eb gjendje disabled, do t\u00eb kaloj\u00eb t\u00eb gjitha fazat e kalimit dhe do t\u00eb kaloj\u00eb n\u00eb modin e transmetimit vet\u00ebm pas 50 sekondash. N\u00ebse ky switch ka pajisje t\u00eb tjera t\u00eb lidhura, ato do t\u00eb humbasin t\u00eb gjitha lidhjen me switchin rr\u00ebnj\u00eb dhe me rrjetin n\u00eb t\u00ebr\u00ebsi p\u00ebr 50 sekonda. <\/a><\/noindex><\/p>\n

N\u00eb m\u00ebnyr\u00eb t\u00eb ngjashme vepron switchi G, pasi merr nga switchi N nj\u00eb frame BPDU me nj\u00eb njoftim p\u00ebr kosto 19. Ai ndryshon kostot e portit t\u00eb tij t\u00eb caktuar n\u00eb 19+19= 38 dhe e ridestinon at\u00eb si portin e ri rr\u00ebnj\u00eb, sepse kostoja e portit t\u00eb tij t\u00eb m\u00ebparsh\u00ebm rr\u00ebnj\u00eb \u00ebsht\u00eb 57, q\u00eb \u00ebsht\u00eb m\u00eb e madhe se 38. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, fillojn\u00eb s\u00ebrish t\u00eb gjitha fazat e ridestinatimit t\u00eb porteve q\u00eb zgjasin 50 sekonda, dhe p\u00ebrfundimisht, e gjith\u00eb rrjeta shembet. <\/p>\n

\"Trajnimi
\n
\nTani le t\u00eb shqyrtojm\u00eb se \u00e7far\u00eb do t\u00eb ndodh\u00eb n\u00eb nj\u00eb situat\u00eb t\u00eb ngjashme duke p\u00ebrdorur RSTP. Switchi rr\u00ebnj\u00eb do t\u00eb d\u00ebrgoj\u00eb gjithashtu BPDU switchit N q\u00eb i \u00ebsht\u00eb lidhur, por menj\u00ebher\u00eb pas k\u00ebsaj do t\u00eb bllokoj\u00eb portin e tij. Duke marr\u00eb k\u00ebt\u00eb frame, switchi N do t\u00eb p\u00ebrcaktoj\u00eb se ky rrug\u00eb ka nj\u00eb kosto m\u00eb t\u00eb vog\u00ebl se porti i tij rr\u00ebnj\u00eb dhe menj\u00ebher\u00eb do ta bllokoj\u00eb. Pas k\u00ebsaj, N do t\u00eb d\u00ebrgoj\u00eb nj\u00eb Proposal k\u00ebrkes\u00eb p\u00ebr t\u00eb hapur portin e ri, sepse kostoja e tij \u00ebsht\u00eb m\u00eb e vog\u00ebl se kostoja e portit rr\u00ebnj\u00eb ekzistues. Pas marr\u00ebveshjes s\u00eb switchit rr\u00ebnj\u00eb, ai do t\u00eb \u00e7blokoj\u00eb portin e tij dhe do t\u00eb d\u00ebrgoj\u00eb Agreement switchit N, pas t\u00eb cilit ky i fundit do ta b\u00ebj\u00eb portin e ri portin e tij rr\u00ebnj\u00eb. <\/p>\n

\"Trajnimi
\n
\nN\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, fal\u00eb mekanizmit Proposal\/Agreement, ridestinimi i portit rr\u00ebnj\u00eb do t\u00eb ndodhi praktikisht menj\u00ebher\u00eb, dhe t\u00eb gjitha pajisjet e lidhura me switchin N nuk do t\u00eb humbasin lidhjen me rrjetin.
\nDuke caktuar nj\u00eb port t\u00eb ri rr\u00ebnj\u00eb, switchi N do ta kthente portin e tij t\u00eb m\u00ebparsh\u00ebm rr\u00ebnj\u00eb n\u00eb nj\u00eb port alternativ. E nj\u00ebjta gj\u00eb do t\u00eb ndodh\u00eb me switchin G \u2013 ai do t\u00eb shk\u00ebmbej\u00eb mesazhe Proposal\/Agreement me switchin N, do t\u00eb caktoj\u00eb nj\u00eb port t\u00eb ri rr\u00ebnj\u00eb dhe do t\u00eb bllokoj\u00eb portet e tjera. M\u00eb pas procesi do t\u00eb vazhdoj\u00eb n\u00eb segmentin tjet\u00ebr t\u00eb rrjetit me switchin F. <\/p>\n

\"Trajnimi
\n
\nSwitch F, pas analizuar kostot, do t\u00eb kuptoj\u00eb se ruta te switch-i kryesor p\u00ebrmes portit t\u00eb posht\u00ebm do t\u00eb kushtoj\u00eb 57, nd\u00ebrsa ruta ekzistuese p\u00ebrmes portit t\u00eb sip\u00ebrm kushton 38, dhe do ta l\u00ebr\u00eb gjith\u00e7ka si\u00e7 \u00ebsht\u00eb. Pas m\u00ebsimit p\u00ebr k\u00ebt\u00eb, switch G do t\u00eb bllokoj\u00eb portin q\u00eb i drejtohet F-s\u00eb dhe do t\u00eb d\u00ebrgoj\u00eb trafikun te switch-i kryesor p\u00ebrmes nj\u00eb rute t\u00eb re G-H-A. <\/p>\n

Derisa switch F t\u00eb marr\u00eb Proposal\/Agreement nga switch G, ai do ta mbaj\u00eb portin e tij t\u00eb posht\u00ebm t\u00eb bllokuar p\u00ebr t\u00eb parandaluar formimin e cikleve. Prandaj, shihni q\u00eb RSTP \u00ebsht\u00eb nj\u00eb protokoll shum\u00eb t\u00eb shpejt\u00eb, i cili nuk krijon probleme n\u00eb rrjet, si\u00e7 ndodh me STP.
\nTani le t\u00eb kalojm\u00eb n\u00eb shqyrtimin e komandave. Ju nevojitet t\u00eb hyni n\u00eb modin e konfigurimit global t\u00eb switch-it dhe t\u00eb zgjidhni modin PVST ose RPVST me komand\u00ebn spanning-tree mode . Pastaj, ju duhet t\u00eb vendosni se si t\u00eb ndryshoni prioritetin e VLAN specifike. P\u00ebr k\u00ebt\u00eb p\u00ebrdoret komanda spanning-tree vlan priority . Nga m\u00ebsimi i fundit, duhet t\u00eb mbani mend se prioriteti \u00ebsht\u00eb nj\u00eb num\u00ebr q\u00eb \u00ebsht\u00eb e shum\u00ebfish t\u00eb 4096 dhe sipas parazgjedhjes ky num\u00ebr \u00ebsht\u00eb 32768 plus numri i VLAN-it. N\u00ebse zgjodh\u00ebt VLAN1, at\u00ebher\u00eb prioriteti sipas parazgjedhjes do t\u00eb jet\u00eb 32768+1= 32769. <\/p>\n

\"Trajnimi
\n
\nPse mund t\u00eb jet\u00eb e nevojshme t\u00eb ndryshohet prioriteti i rrjeteve? Ne e dim\u00eb q\u00eb BID p\u00ebrb\u00ebhet nga nj\u00eb vler\u00eb numerike e prioritetit dhe MAC-adresa. MAC-adresa e pajisjes nuk mund t\u00eb ndryshohet, ajo ka nj\u00eb vler\u00eb t\u00eb p\u00ebrhershme, k\u00ebshtu q\u00eb vet\u00ebm vler\u00ebn e prioritetit mund ta ndryshojm\u00eb.<\/p>\n

Supozoni se ekziston nj\u00eb rrjet i madh, ku t\u00eb gjitha pajisjet Cisco jan\u00eb t\u00eb lidhura n\u00eb nj\u00eb schem\u00eb rrethore. N\u00eb k\u00ebt\u00eb rast, sipas parazgjedhjes \u00ebsht\u00eb aktivizuar PVST, prandaj sistemi do t\u00eb zgjedh\u00eb switch-in kryesor. N\u00ebse t\u00eb gjitha pajisjet kan\u00eb t\u00eb nj\u00ebjtin prioritet, at\u00ebher\u00eb avantazhi do t\u00eb ket\u00eb switch-i me MAC-adres\u00ebn m\u00eb t\u00eb vjet\u00ebr. Megjithat\u00eb, kjo mund t\u00eb jet\u00eb nj\u00eb switch 10-12 vje\u00e7ar i modelit t\u00eb vjetruar, i cili nuk ka p\u00ebrputhshm\u00ebri dhe performanc\u00eb p\u00ebr \"t\u00eb udh\u00ebhequr\" nj\u00eb rrjet kaq t\u00eb gjer\u00eb.
\nN\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, mund t\u00eb keni n\u00eb rrjet nj\u00eb switch t\u00eb ri q\u00eb kushton disa mij\u00ebra dollar\u00eb, i cili p\u00ebr shkak t\u00eb vler\u00ebs m\u00eb t\u00eb madhe t\u00eb MAC-adres\u00ebs \u00ebsht\u00eb i detyruar t\u00eb \"p\u00ebrkulet\" para nj\u00eb switch-i t\u00eb vjet\u00ebr q\u00eb kushton disa qindra dollar\u00eb. N\u00ebse switch-i i vjet\u00ebr b\u00ebhet switch kryesor, kjo tregon nj\u00eb gabim t\u00eb r\u00ebnd\u00ebsish\u00ebm n\u00eb projektimin e rrjetit.<\/p>\n

Prandaj, duhet t\u00eb hyni n\u00eb cil\u00ebsimet e switch-it t\u00eb ri dhe t'i jepni atij nj\u00eb vler\u00eb minimale prioriteti, p\u00ebr shembull, 0. Kur p\u00ebrdoret VLAN1, vlera totale e prioritetit do t\u00eb jet\u00eb 0+1=1, dhe t\u00eb gjith\u00eb pajisjet e tjera do ta konsiderojn\u00eb at\u00eb gjithmon\u00eb si switch-in rr\u00ebnj\u00eb.<\/p>\n

Tani imagjinoni nj\u00eb situat\u00eb t\u00eb till\u00eb. N\u00ebse switch-i rr\u00ebnj\u00eb p\u00ebr ndonj\u00eb arsye b\u00ebhet i paarritsh\u00ebm, mund t\u00eb d\u00ebshironi q\u00eb switch-i i ri rr\u00ebnj\u00eb t\u00eb jet\u00eb jo ndonj\u00eb switch me prioritet m\u00eb t\u00eb ul\u00ebt, por nj\u00eb switch i caktuar me funksione m\u00eb t\u00eb mira rrjetore. N\u00eb k\u00ebt\u00eb rast, n\u00eb cil\u00ebsimet e Root Bridge p\u00ebrdoret urdhri q\u00eb cakton switches rr\u00ebnj\u00eb kryesore dhe dyt\u00ebsore: spanning-tree vlan root . Vlera e prioritetit p\u00ebr switch-in kryesor do t\u00eb jet\u00eb 32768 \u2013 4096 \u2013 4096 = 24576. P\u00ebr switch-in dyt\u00ebsor, ajo llogaritet sipas formul\u00ebs 32768 \u2013 4096 = 28672.<\/p>\n

Ju nuk mund ta b\u00ebni k\u00ebt\u00eb ndaljen e numrave manualisht - sistemi do ta b\u00ebj\u00eb k\u00ebt\u00eb p\u00ebr ju automatikisht. N\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, switch-i me prioritet 24576 do t\u00eb jet\u00eb rr\u00ebnj\u00eb, dhe n\u00ebse ai b\u00ebhet i paarritsh\u00ebm - switch-i me prioritet 28672, duke pasur parasysh q\u00eb prioriteti i t\u00eb gjith\u00eb switches t\u00eb tjer\u00eb, sipas parazgjedhjes, nuk \u00ebsht\u00eb m\u00eb i vog\u00ebl se 32768. K\u00ebshtu duhet vepruar n\u00ebse nuk d\u00ebshironi q\u00eb sistemi t\u00eb caktoj\u00eb nj\u00eb switch rr\u00ebnj\u00eb automatikisht. <\/p>\n

N\u00ebse d\u00ebshironi t\u00eb shikoni cil\u00ebsimet e protokollit STP, duhet t\u00eb p\u00ebrdorni komand\u00ebn show spanning-tree summary. Tani le t\u00eb shqyrtojm\u00eb t\u00eb gjitha temat e studiuara sot duke p\u00ebrdorur Packet Tracer. Un\u00eb po p\u00ebrdor nj\u00eb topologji rrjeti me 4 switches model 2690, kjo nuk ka r\u00ebnd\u00ebsi, pasi t\u00eb gjitha modelet e switches Cisco mb\u00ebshtesin STP. Ato jan\u00eb t\u00eb lidhura nj\u00ebra me tjetr\u00ebn n\u00eb nj\u00eb m\u00ebnyr\u00eb q\u00eb rrjeti formon nj\u00eb rreth. <\/p>\n

P\u00ebr parazgjedhje, pajisjet Cisco funksionojn\u00eb n\u00eb modin PSTV+, dometh\u00ebn\u00eb p\u00ebr konvergjenc\u00ebn \u00e7do porte do t'i duhen jo m\u00eb shum\u00eb se 20 sekonda. Paneli i simulimit lejon q\u00eb t\u00eb ilustrohet d\u00ebrgimi i trafikut dhe t\u00eb shihen parametrat e funksionimit t\u00eb rrjetit t\u00eb krijuar.<\/p>\n

\"Trajnimi
\n
\nJu shihni se \u00e7far\u00eb p\u00ebrb\u00ebn nj\u00eb frame STP BPDU. N\u00ebse shihni shenj\u00ebn e versionit 0, at\u00ebher\u00eb p\u00ebrpara jush \u00ebsht\u00eb STP, sepse p\u00ebr RSTP p\u00ebrdoret versioni 2. Ky \u00ebsht\u00eb gjithashtu vlera e Root ID, e p\u00ebrb\u00ebr\u00eb nga prioriteti dhe adresa MAC e switch-it rr\u00ebnj\u00eb, dhe vlera e barabart\u00eb Bridge ID. <\/p>\n

\"Trajnimi
\n
\nK\u00ebto vlera jan\u00eb t\u00eb barabarta, pasi kostoja e rrug\u00ebs p\u00ebr switch-in rr\u00ebnj\u00ebsor SW0 \u00ebsht\u00eb 0, rrjedhimisht, ai vet\u00eb \u00ebsht\u00eb switch-i rr\u00ebnj\u00ebsor. K\u00ebshtu, pas aktivizimit t\u00eb switch-eve fal\u00eb p\u00ebrdorimit t\u00eb STP-s\u00eb, u b\u00eb automatikisht zgjedhja e Root Bridge dhe rrjeti filloi t\u00eb funksionoj\u00eb. Ju shihni se p\u00ebr t\u00eb parandaluar ciklin, porta e sip\u00ebrme Fa0\/2 e switch-it SW2 u kalua n\u00eb gjendjen Blocking, por \u00e7far\u00eb tregon ngjyra portokalli e marker-it. <\/p>\n

\"Trajnimi
\n
\nT\u00eb kalojm\u00eb te consola e konfigurimit t\u00eb switch-it SW0 dhe t\u00eb p\u00ebrdorim nj\u00eb \u00e7ift komandash. E para \u00ebsht\u00eb komanda show spanning-tree, pas shkrimit t\u00eb s\u00eb cil\u00ebs n\u00eb ekran na do t\u00eb shfaqet informacioni mbi modin PSTV+ p\u00ebr rrjetin VLAN1. N\u00ebse do t\u00eb p\u00ebrdorim disa VLAN, n\u00eb fund t\u00eb dritares do t\u00eb shfaqet nj\u00eb bllok informacionesh p\u00ebr rrjetet e tjera t\u00eb p\u00ebrdorura. <\/p>\n

\"Trajnimi
\n
\nJu shihni se protokolli STP \u00ebsht\u00eb n\u00eb dispozicion sipas standardit IEEE, q\u00eb do t\u00eb thot\u00eb p\u00ebrdorimin e PVSTP+. Teknikisht, kjo nuk \u00ebsht\u00eb nj\u00eb standard .1d. K\u00ebtu jepet gjithashtu informacioni Root ID: prioriteti 32769, adresa MAC e pajisjes rr\u00ebnj\u00eb, kostoja 19, etj. M\u00eb pas vijon informacioni Bridge ID, ku shpjegohet vlera e prioritetit 32768 +1, dhe jepet nj\u00eb adres\u00eb MAC tjet\u00ebr. Si\u00e7 e shihni, gabova - switch-i SW0 nuk \u00ebsht\u00eb switch-i rr\u00ebnj\u00ebsor, switch-i rr\u00ebnj\u00ebsor ka nj\u00eb adres\u00eb MAC tjet\u00ebr, e cila jepet n\u00eb parametrat e Root ID. Mendoj se kjo \u00ebsht\u00eb p\u00ebr shkak se SW0 mori nj\u00eb kuad\u00ebr BPDU q\u00eb tregon se ndonj\u00eb switch n\u00eb rrjet ka m\u00eb shum\u00eb baza p\u00ebr t\u00eb luajtur rolin e rr\u00ebnj\u00ebs.<\/p>\n

(Sh\u00ebnim i p\u00ebrkthyesit: Root ID \u2013 identifikuesi i switch-it rr\u00ebnj\u00ebsor, i njejt\u00eb p\u00ebr t\u00eb gjitha pajisjet n\u00eb t\u00eb nj\u00ebjtin rrjet VLAN, q\u00eb punon me protokollin STP, Bridge ID \u2013 identifikuesi i switch-it lokal n\u00eb p\u00ebrb\u00ebrje t\u00eb Root Bridge, q\u00eb mund t\u00eb jet\u00eb i ndrysh\u00ebm p\u00ebr switch-e t\u00eb ndrysh\u00ebm dhe VLAN t\u00eb ndryshme).<\/p>\n

Nj\u00eb tjet\u00ebr rrethan\u00eb q\u00eb tregon se SW0 nuk \u00ebsht\u00eb switch-i rr\u00ebnj\u00ebsor \u00ebsht\u00eb se switch-i rr\u00ebnj\u00ebsor nuk ka Root Port, nd\u00ebrsa n\u00eb k\u00ebt\u00eb rast ka si Root Port ashtu edhe Designated Port, t\u00eb cilat jan\u00eb n\u00eb gjendjen forwarding. Ju gjithashtu shihni llojin e lidhjes p2p, ose \"pik\u00eb n\u00eb pik\u00eb\". Kjo do t\u00eb thot\u00eb se portat fa0\/1 dhe fa0\/2 jan\u00eb t\u00eb lidhura drejtp\u00ebrdrejt me switch-et fqinj.
\nN\u00ebse ndonj\u00eb port do t\u00eb ishte i lidhur me hub-in, tipi i lidhjes do t\u00eb sh\u00ebnohej si shared, k\u00ebt\u00eb do ta shqyrtojm\u00eb m\u00eb von\u00eb. N\u00ebse un\u00eb jap komand\u00ebn p\u00ebr t\u00eb par\u00eb informacionin p\u00ebrmbledh\u00ebs show spanning-tree summary, ne do t\u00eb shohim se ky switch ndodhet n\u00eb modalitetin PVSTP, m\u00eb pas ndjek lista e funksioneve t\u00eb pap\u00ebrshtatshme t\u00eb portit. <\/p>\n

\"Trajnimi
\n
\nM\u00eb posht\u00eb \u00ebsht\u00eb gjendja dhe numri i porteve q\u00eb sh\u00ebrbejn\u00eb VLAN1: blocking 0, listening 0, learning 0, n\u00eb gjendje forwarding ndodhen 2 porte n\u00eb modalitetin STP.
\nPara se t\u00eb kalojm\u00eb te switch SW2, le t\u00eb shohim konfigurimet e switch SW1. P\u00ebr k\u00ebt\u00eb, do t\u00eb p\u00ebrdorim t\u00eb nj\u00ebjt\u00ebn komand\u00eb show spanning-tree.<\/p>\n

\"Trajnimi
\n
\nJu shihni se adresa MAC e Root ID p\u00ebr switch SW1 \u00ebsht\u00eb e nj\u00ebjt\u00eb me at\u00eb t\u00eb SW0, sepse t\u00eb gjitha pajisjet n\u00eb rrjet kur bashkohen marrin t\u00eb nj\u00ebjt\u00ebn adres\u00eb t\u00eb pajisjes Root Bridge, pasi besojn\u00eb n\u00eb zgjedhjen e b\u00ebr\u00eb nga protokolli STP. Si\u00e7 e shihni, SW1 \u00ebsht\u00eb switch-i root, sepse adresat Root ID dhe Bridge ID p\u00ebrputhen. Gjithashtu, k\u00ebtu ka nj\u00eb mesazh \"ky switch \u00ebsht\u00eb root.\" <\/p>\n

Nj\u00eb tjet\u00ebr tregues i switch-it root \u00ebsht\u00eb se ai nuk ka Root-porte, t\u00eb dy portet sh\u00ebnohen si Designated. N\u00ebse t\u00eb gjitha portet jan\u00eb t\u00eb treguara si Designated dhe jan\u00eb n\u00eb gjendje forwarding, at\u00ebher\u00eb ju keni nj\u00eb switch root. <\/p>\n

Switch SW3 p\u00ebrmban informacion t\u00eb ngjash\u00ebm, dhe tani po kaloj te SW2, sepse nj\u00eb nga portet e tij ndodhet n\u00eb gjendje Blocking. Po p\u00ebrdor komand\u00ebn show spanning-tree dhe ne shohim se informacioni Root ID dhe vlera e prioritetit jan\u00eb t\u00eb nj\u00ebjta si p\u00ebr switch-t\u00eb e tjer\u00eb.
\nM\u00eb posht\u00eb \u00ebsht\u00eb sh\u00ebnuar se nj\u00eb nga portet \u00ebsht\u00eb Alternative. Mos u shqet\u00ebsoni nga kjo, standardi 802.1d e quan k\u00ebt\u00eb Blocking Port, nd\u00ebrsa n\u00eb PVSTP, porti i bllokuar gjithmon\u00eb sh\u00ebnohet si Alternative. Pra, ky port alternativ Fa0\/2 \u00ebsht\u00eb n\u00eb gjendje t\u00eb bllokuar, nd\u00ebrsa porti Fa0\/1 sh\u00ebrben si Root Port. <\/p>\n

Porti i bllokuar ndodhet n\u00eb segmentin e rrjetit midis switch-it SW0 dhe switch-it SW2, duke ndihmuar n\u00eb parandalimin e formimit t\u00eb nj\u00eb cikli. Si\u00e7 e shihni, switch-at p\u00ebrdorin lidhjen p2p, sepse nuk kan\u00eb lidhur asnj\u00eb pajisje tjet\u00ebr. <\/p>\n

\"Trajnimi
\n
\nNe kemi nj\u00eb rrjet q\u00eb bashkohet p\u00ebrmes protokollit STP. Tani do t\u00eb marr nj\u00eb kabll\u00eb dhe do ta lidh direkt switch-in SW2 me switch-in root SW1. Pas k\u00ebsaj, t\u00eb gjitha portet e SW2 do t\u00eb sh\u00ebnohen me tregues portokalli. <\/p>\n

\"Trajnimi
\n
\nN\u00ebse p\u00ebrdorim komand\u00ebn show spanning-tree summary, do t\u00eb shohim se fillimisht dy portet jan\u00eb n\u00eb gjendje Listening, pastaj kalojn\u00eb n\u00eb gjendje Learning dhe pas disa sekondash n\u00eb gjendje Forwarding, nd\u00ebrkoh\u00eb q\u00eb ngjyra e treguesit ndryshon n\u00eb t\u00eb gjelb\u00ebr. N\u00ebse tani japim komand\u00ebn show spanning-tree, duket se Fa0\/1, i cili m\u00eb par\u00eb ishte Root-port, tani ka kaluar n\u00eb gjendje bllokimi dhe \u00ebsht\u00eb quajtur Alternative-port. <\/p>\n

\"Trajnimi
\n
\nPorti Fa0\/3, i cili \u00ebsht\u00eb lidhur me kabllon e nd\u00ebrprer\u00ebsit rr\u00ebnjor, \u00ebsht\u00eb b\u00ebr\u00eb Root-port, nd\u00ebrsa porti Fa0\/2 \u00ebsht\u00eb shnd\u00ebrruar n\u00eb portin e caktuar Designated-port. Le t\u00eb shikojm\u00eb p\u00ebrs\u00ebri procesin e konvergjenc\u00ebs. Un\u00eb do t\u00eb shk\u00ebput kabllon SW2-SW1 dhe do t\u00eb kthehem n\u00eb topologjin\u00eb e m\u00ebparshme. P\u00ebreni se portet SW2 fillimisht bllokohen dhe b\u00ebhen s\u00ebrish portet portokalli, pastaj kalojn\u00eb p\u00ebr radh\u00eb n\u00ebp\u00ebr gjendjet Listening dhe Learning dhe p\u00ebrfundojn\u00eb n\u00eb gjendje Forwarding. Gjat\u00eb k\u00ebsaj, nj\u00eb port b\u00ebhet i gjelb\u00ebr, nd\u00ebrsa tjetri, i lidhur me nd\u00ebrprer\u00ebsin SW0, mbetet portokalli. Procesi i konvergjenc\u00ebs zgjati nj\u00eb koh\u00eb t\u00eb gjat\u00eb, k\u00ebto jan\u00eb kostot e pun\u00ebs STP.<\/p>\n

\"Trajnimi
\n
\nTani le t\u00eb shohim se si funksionon RSTP. T\u00eb fillojm\u00eb me nd\u00ebrprer\u00ebsin SW2 dhe t\u00eb japim n\u00eb cil\u00ebsimet e tij komand\u00ebn spanning-tree mode rapid-pvst. Kjo komand\u00eb ka dy variante parametrat: pvst dhe rapid-pvst, un\u00eb po p\u00ebrdor t\u00eb dytin. Pas p\u00ebrfundimit t\u00eb komand\u00ebs, nd\u00ebrprer\u00ebsi kalon n\u00eb modalitetin RPVST, dhe kjo mund t\u00eb verifikohet me komand\u00ebn show spanning-tree. <\/p>\n

\"Trajnimi
\n
\nN\u00eb fillim shihni nj\u00eb mesazh q\u00eb tani jemi n\u00eb protokollin RSTP. Gjith\u00e7ka tjet\u00ebr ka mbetur pa ndryshim. Pastaj un\u00eb duhet t\u00eb b\u00ebj t\u00eb nj\u00ebjt\u00ebn gj\u00eb p\u00ebr t\u00eb gjitha pajisjet e tjera, dhe k\u00ebshtu konfigurimi i RSTP p\u00ebrfundon. Le t\u00eb shqyrtojm\u00eb pun\u00ebn e k\u00ebtij protokolli ashtu si\u00e7 e b\u00ebm\u00eb me STP.<\/p>\n

Un\u00eb p\u00ebrs\u00ebri lidhem me kabllon nd\u00ebrprer\u00ebsin SW2 direkt me nd\u00ebrprer\u00ebsin rr\u00ebnjor SW1 \u2013 le t\u00eb shohim se sa shpejt do t\u00eb ndodhi konvergjenca. Un\u00eb jap komand\u00ebn show spanning-tree summary dhe shoh se dy portet e nd\u00ebrprer\u00ebsit jan\u00eb n\u00eb gjendje Blocking, 1 n\u00eb gjendje Forwarding. <\/p>\n

\"Trajnimi
\n
\nShihni se konvergjenca ndodhi praktikisht menj\u00ebher\u00eb, k\u00ebshtu q\u00eb mund t\u00eb gjykoni se sa m\u00eb shpejt \u00ebsht\u00eb RSTP sesa STP. M\u00eb pas mund t\u00eb p\u00ebrdorim komand\u00ebn spanning-tree portfast default, e cila do t\u00eb kaloj\u00eb t\u00eb gjith\u00eb portet e nd\u00ebrprer\u00ebsit n\u00eb modalitetin portfast si parazgjedhje. Kjo \u00ebsht\u00eb n\u00ebfuqi n\u00eb rast se shumica e porteve t\u00eb nd\u00ebrprer\u00ebsit jan\u00eb Edge-port, t\u00eb lidhura drejtp\u00ebrdrejt me hostet. N\u00ebse kemi ndonj\u00eb port q\u00eb nuk \u00ebsht\u00eb Edge, ne e kthejm\u00eb at\u00eb p\u00ebrs\u00ebri n\u00eb modalitetin spanning-tree. <\/p>\n

P\u00ebr t\u00eb konfiguruar funksionimin me VLAN, mund t\u00eb p\u00ebrdorim komand\u00ebn spanning-tree vlan me parametra priority (cakton prioritetin e switch-it p\u00ebr spanning-tree) ose root (em\u00ebron switch-in si korner). Ne p\u00ebrdorim komand\u00ebn spanning-tree vlan 1 priority, duke caktuar si prioritet nj\u00eb num\u00ebr t\u00eb gjitha t\u00eb shum\u00ebfishueshme me 4096, n\u00eb intervalin nga 0 deri n\u00eb 61440. K\u00ebshtu mund t\u00eb ndryshojm\u00eb manualisht prioritetin e \u00e7do VLAN. <\/p>\n

Mund t\u00eb shkruani komand\u00ebn spanning-tree vlan 1 root me parametrat primary ose secondary p\u00ebr t\u00eb konfiguruar portin e root-it kryesor ose rezerv\u00eb p\u00ebr nj\u00eb rrjet t\u00eb caktuar. N\u00ebse p\u00ebrdor spanning-tree vlan 1 root primary, ky port do t\u00eb jet\u00eb porti kryesor i root-it p\u00ebr rrjetin VLAN1. <\/p>\n

Do t\u00eb jap komand\u00ebn show spanning-tree dhe do t\u00eb shohim se ky switch SW2 ka prioritet 24577, MAC-adresat Root ID dhe Bridge ID p\u00ebrkojn\u00eb, k\u00ebshtu q\u00eb tani ai \u00ebsht\u00eb b\u00ebr\u00eb switch-i root. <\/p>\n

\"Trajnimi
\n
\nShihni sa shpejt ndodhi konvergjenca dhe ndryshimi i rolit t\u00eb switch-eve. Tani do ta anulloj m\u00ebnyr\u00ebn e switch-it kryesor me komand\u00ebn no spanning-tree vlan 1 root primary, pas s\u00eb cil\u00ebs prioriteti i tij do t\u00eb kthehet n\u00eb vler\u00ebn e m\u00ebparshme 32769, dhe roli i switch-it root do t\u00eb kaloj\u00eb p\u00ebrs\u00ebri n\u00eb SW1. <\/p>\n

Le t\u00eb shohim si funksionon portfast. Do t\u00eb jap komand\u00ebn int f0\/1, do t\u00eb hyj n\u00eb konfigurimin e k\u00ebtij porti dhe do t\u00eb p\u00ebrdor komand\u00ebn spanning-tree, pas s\u00eb cil\u00ebs sistemi do t\u00eb jap\u00eb sugjerime p\u00ebr vlerat e parametrave. <\/p>\n

\"Trajnimi
\n
\nM\u00eb pas do t\u00eb p\u00ebrdor komand\u00ebn spanning-tree portfast, t\u00eb cil\u00ebn mund ta jap me parametrat disable (\u00e7aktivizon funksionin portfast p\u00ebr k\u00ebt\u00eb port) ose trunk (aktivizon funksionin portfast p\u00ebr k\u00ebt\u00eb port edhe n\u00eb modalitetin e trunk-ut). <\/p>\n

N\u00ebse jepni spanning-tree portfast, funksioni vet\u00ebm do t\u00eb aktivizohet n\u00eb k\u00ebt\u00eb port. P\u00ebr t\u00eb aktivizuar funksionin BPDU Guard, duhet t\u00eb p\u00ebrdorni komand\u00ebn spanning-tree bpduguard enable, komanda spanning-tree bpduguard disable \u00e7aktivizon k\u00ebt\u00eb funksion. <\/p>\n

Do t\u00eb flas shpejt p\u00ebr nj\u00eb gj\u00eb tjet\u00ebr. N\u00ebse p\u00ebr VLAN1, nd\u00ebrfaqja e switch-it SW2 n\u00eb drejtim t\u00eb SW3 \u00ebsht\u00eb bllokuar, at\u00ebher\u00eb me parametra t\u00eb ndrysh\u00ebm konfigurimi p\u00ebr nj\u00eb VLAN tjet\u00ebr, p\u00ebr shembull, VLAN2, ajo nd\u00ebrfaqe mund t\u00eb b\u00ebhet porti root. K\u00ebshtu, n\u00eb sistem mund t\u00eb implementohet mekanizmi i balancimit t\u00eb ngarkes\u00ebs s\u00eb trafikut \u2013 n\u00eb nj\u00eb rast ky segment i rrjetit nuk p\u00ebrdoret, n\u00eb rastin tjet\u00ebr \u2013 p\u00ebrdoret. <\/p>\n

Do t\u00eb tregoj se \u00e7far\u00eb ndodh kur, gjat\u00eb lidhjes s\u00eb nj\u00eb hub-i, kemi nj\u00eb nd\u00ebrfaqe shared. Do t\u00eb shtoj hub-in n\u00eb diagram dhe do ta lidhem me switch-in SW2 me dy kabllo. <\/p>\n

\"Trajnimi
\n
\nKomanda show spanning-tree do t\u00eb reflektoj\u00eb pamjen e m\u00ebposhtme. <\/p>\n

\"Trajnimi
\n
\nFa0\/5 (porta e poshtme e majt\u00eb e switch-it) b\u00ebhet port backup, nd\u00ebrsa porta Fa0\/4 (porta e poshtme e djatht\u00eb e switch-it) b\u00ebhet port i caktuar designated-port. Lloji i t\u00eb dy portave \u00ebsht\u00eb i p\u00ebrbashk\u00ebt, ose shared. Kjo do t\u00eb thot\u00eb se segmenti i interfecave t\u00eb switch-it hub \u00ebsht\u00eb nj\u00eb rrjet i p\u00ebrbashk\u00ebt. <\/p>\n

Me p\u00ebrdorimin e RSTP ne arrit\u00ebm ndarjen n\u00eb porte alternative dhe rezerv\u00eb. N\u00ebse e kalojm\u00eb switch-in SW2 n\u00eb modalitetin pvst me komand\u00ebn spanning-tree mode pvst, do t\u00eb shohim se interfe\u00e7i Fa0\/5 p\u00ebrs\u00ebri kalon n\u00eb gjendjen Alternative, sepse tani nuk ka dallim midis portit backup dhe portit alternative. <\/p>\n

\"Trajnimi
\n
\nIshte nj\u00eb m\u00ebsim shum\u00eb i gjat\u00eb, dhe n\u00ebse nuk kuptuat di\u00e7ka, ju rekomandoj ta rishikoni p\u00ebrs\u00ebri. <\/p>\n

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

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

\u041f\u0440\u0435\u0434\u043f\u043e\u043b\u043e\u0436\u0438\u043c, \u0447\u0442\u043e STP \u043d\u0430\u0445\u043e\u0434\u0438\u0442\u0441\u044f \u0432 \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0438 \u0441\u0445\u043e\u0434\u0438\u043c\u043e\u0441\u0442\u0438. \u0427\u0442\u043e \u043f\u0440\u043e\u0438\u0437\u043e\u0439\u0434\u0435\u0442, \u0435\u0441\u043b\u0438 \u044f \u0432\u043e\u0437\u044c\u043c\u0443 \u043a\u0430\u0431\u0435\u043b\u044c \u0438 \u0441\u043e\u0435\u0434\u0438\u043d\u044e \u0441\u0432\u0438\u0442\u0447 \u041d \u043d\u0430\u043f\u0440\u044f\u043c\u0443\u044e \u0441 \u043a\u043e\u0440\u043d\u0435\u0432\u044b\u043c \u0441\u0432\u0438\u0442\u0447\u0435\u043c \u0410? Root Bridge \u00ab\u0443\u0432\u0438\u0434\u0438\u0442\u00bb, \u0447\u0442\u043e \u0443 \u043d\u0435\u0433\u043e \u043f\u043e\u044f\u0432\u0438\u043b\u0441\u044f \u043d\u043e\u0432\u044b\u0439 \u0437\u0430\u0434\u0435\u0439\u0441\u0442\u0432\u043e\u0432\u0430\u043d\u043d\u044b\u0439 \u043f\u043e\u0440\u0442, \u0438 \u043e\u0442\u043e\u0448\u043b\u0435\u0442 \u043f\u043e \u043d\u0435\u043c\u0443 BPDU. \u0421\u0432\u0438\u0442\u0447 \u041d, \u043f\u043e\u043b\u0443\u0447\u0438\u0432 \u044d\u0442\u043e\u0442 \u0444\u0440\u0435\u0439\u043c \u0441 \u043d\u0443\u043b\u0435\u0432\u043e\u0439 \u0441\u0442\u043e\u0438\u043c\u043e\u0441\u0442\u044c\u044e, \u043e\u043f\u0440\u0435\u0434\u0435\u043b\u0438\u0442 \u0441\u0442\u043e\u0438\u043c\u043e\u0441\u0442\u044c \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0430 \u0447\u0435\u0440\u0435\u0437 \u043d\u043e\u0432\u044b\u0439 \u043f\u043e\u0440\u0442 \u043a\u0430\u043a 0+19 =19 \u043f\u0440\u0438 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28511,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37988","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 37. STP: zgjedhja e Root Bridge, funksionet PortFast dhe BPDU guard. Pjesa 2 | ProHoster","description":"Supozoni se STP \u00ebsht\u00eb n\u00eb gjendje konvergjence. \u00c7far\u00eb do t\u00eb ndodhte n\u00ebse merrja nj\u00eb kabll dhe e lidhja switch-in N drejtp\u00ebrdrejt me switch-in rr\u00ebnj\u00eb A?","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-37-stp-vybor-root-bridge-funktsii-portfast-i-bpdu-guard-chast-2","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 37. STP: \u0432\u044b\u0431\u043e\u0440 Root Bridge, \u0444\u0443\u043d\u043a\u0446\u0438\u0438 PortFast \u0438 BPDU guard. \u0427\u0430\u0441\u0442\u044c 2 | ProHoster","og:description":"\u041f\u0440\u0435\u0434\u043f\u043e\u043b\u043e\u0436\u0438\u043c, \u0447\u0442\u043e STP \u043d\u0430\u0445\u043e\u0434\u0438\u0442\u0441\u044f \u0432 \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0438 \u0441\u0445\u043e\u0434\u0438\u043c\u043e\u0441\u0442\u0438. \u0427\u0442\u043e \u043f\u0440\u043e\u0438\u0437\u043e\u0439\u0434\u0435\u0442, \u0435\u0441\u043b\u0438 \u044f \u0432\u043e\u0437\u044c\u043c\u0443 \u043a\u0430\u0431\u0435\u043b\u044c \u0438 \u0441\u043e\u0435\u0434\u0438\u043d\u044e \u0441\u0432\u0438\u0442\u0447 \u041d \u043d\u0430\u043f\u0440\u044f\u043c\u0443\u044e \u0441 \u043a\u043e\u0440\u043d\u0435\u0432\u044b\u043c \u0441\u0432\u0438\u0442\u0447\u0435\u043c \u0410?","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-37-stp-vybor-root-bridge-funktsii-portfast-i-bpdu-guard-chast-2","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:21:01+00:00","article:modified_time":"2019-10-31T19:21:01+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37988","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 20:01:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:17:22","updated":"2026-01-23 20:01: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\/37988","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=37988"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/37988\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/28511"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=37988"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=37988"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=37988"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}