{"id":31067,"date":"2019-10-31T21:39:16","date_gmt":"2019-10-31T18:39:16","guid":{"rendered":"https:\/\/prohoster.info\/blog\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-vtoraya-chistka-i-dokumentirovanie\/"},"modified":"2019-10-31T21:39:16","modified_gmt":"2019-10-31T18:39:16","slug":"kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-vtoraya-chistka-i-dokumentirovanie","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-vtoraya-chistka-i-dokumentirovanie","title":{"rendered":"Si ta kontrolloni infrastruktur\u00ebn tuaj rrjetore. Kreu i dyt\u00eb. Pastrimi dhe dokumentimi","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><i>Ky kjo artikull \u00ebsht\u00eb i dyti n\u00eb ciklin e artikujve \"Si ta mbani n\u00ebn kontroll infrastruktur\u00ebn tuaj rrjet\u00eb.\" P\u00ebrmbajtja e t\u00eb gjith\u00eb artikujve n\u00eb cik\u00ebl dhe lidhjet mund t\u00eb gjenden <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/447008\/\">k\u00ebtu<\/a><\/noindex><\/i>.<\/p>\n<p><img decoding=\"async\" alt=\"Si ta kontrolloni infrastruktur\u00ebn tuaj rrjetore. Kreu i dyt\u00eb. Pastrimi dhe dokumentimi\" src=\"\/wp-content\/uploads\/2019\/04\/7b8e020272ed52ef0a119714b0a5d58b.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nQ\u00ebllimi yn\u00eb n\u00eb k\u00ebt\u00eb faz\u00eb \u00ebsht\u00eb t\u00eb vendosim rend n\u00eb dokumentacion dhe konfigurim. <br \/>\nN\u00eb p\u00ebrfundim t\u00eb k\u00ebtij procesi, duhet t\u00eb keni nj\u00eb paket\u00eb dokumentesh t\u00eb nevojshme dhe nj\u00eb rrjet t\u00eb konfiguruar p\u00ebrkat\u00ebsisht.<\/p>\n<p>Tani nuk do t\u00eb flasim p\u00ebr auditet e siguris\u00eb \u2013 kjo do t'i kushtohet pjes\u00ebs s\u00eb tret\u00eb. <\/p>\n<p>V\u00ebshtir\u00ebsia e realizimit t\u00eb detyr\u00ebs s\u00eb vendosur n\u00eb k\u00ebt\u00eb faz\u00eb, sigurisht, variason shum\u00eb nga kompania n\u00eb kompani.<\/p>\n<p>Situata ideale \u00ebsht\u00eb kur<\/p>\n<ul>\n<li>rrjeti juaj \u00ebsht\u00eb nd\u00ebrtuar sipas projektit dhe keni nj\u00eb paket\u00eb t\u00eb plot\u00eb dokumentacioni<\/li>\n<li>n\u00eb kompanin\u00eb tuaj \u00ebsht\u00eb zbatuar <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/433614\/\">procesi i kontrollit dhe menaxhimit t\u00eb ndryshimeve<\/a><\/noindex> p\u00ebr rrjetin<\/li>\n<li>sipas k\u00ebtij procesi keni dokumentet (p\u00ebrfshir\u00eb t\u00eb gjitha diagramet e nevojshme), q\u00eb ofrojn\u00eb informacion t\u00eb plot\u00eb mbi situat\u00ebn aktuale<\/li>\n<\/ul>\n<p>\nN\u00eb k\u00ebt\u00eb rast, detyra juaj \u00ebsht\u00eb mjaft e thjesht\u00eb. Duhet t\u00eb shqyrtoni dokumentet dhe t\u00eb rishikoni t\u00eb gjitha ndryshimet q\u00eb jan\u00eb b\u00ebr\u00eb. <\/p>\n<p>N\u00eb rastin m\u00eb t\u00eb keq, do t\u00eb keni<\/p>\n<ul>\n<li>nj\u00eb rrjet t\u00eb nd\u00ebrtuar pa projekt, pa plan, pa pajtim, nga inxhinier\u00eb q\u00eb nuk kan\u00eb nivele t\u00eb mjaftueshme kualifikimi,<\/li>\n<li>me ndryshime t\u00eb haotuara, t\u00eb pa dokumentuara, me shum\u00eb \"mbeturina\" dhe zgjidhje jo optimale<\/li>\n<\/ul>\n<p>\nNatyrisht, situata juaj ndodhet diku midis, por fatkeq\u00ebsisht, n\u00eb k\u00ebt\u00eb shkall\u00eb t\u00eb mir\u00eb-keqe, me nj\u00eb probabilitet t\u00eb lart\u00eb, do t\u00eb jeni m\u00eb af\u00ebr fundit m\u00eb t\u00eb keq.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>N\u00eb k\u00ebt\u00eb rast, nga ju do t\u00eb k\u00ebrkohet gjithashtu aft\u00ebsia p\u00ebr t\u00eb lexuar mendimet, sepse do t\u00eb duhet t\u00eb m\u00ebsoni t\u00eb kuptoni \u00e7far\u00eb do t\u00eb b\u00ebjn\u00eb \"dizajner\u00ebt\", t\u00eb riktheni logjik\u00ebn e tyre, t\u00eb p\u00ebrfundoni at\u00eb q\u00eb nuk \u00ebsht\u00eb p\u00ebrfunduar dhe t\u00eb hiqni \"mbeturinat\". <br \/>\nDhe, sigurisht, do t'ju nevojitet t\u00eb riktakoni gabimet e tyre, t\u00eb ndryshoni (n\u00eb k\u00ebt\u00eb faz\u00eb sa m\u00eb pak t\u00eb jet\u00eb e mundur) dizajnin dhe t\u00eb ndryshoni ose t\u00eb krijoni n\u00eb m\u00ebnyr\u00eb t\u00eb re diagramet. <\/p>\n<p>Ky artikull n\u00eb asnj\u00eb m\u00ebnyr\u00eb nuk pretendon p\u00ebr plot\u00ebsin\u00eb. K\u00ebtu do t\u00eb p\u00ebrshkruaj vet\u00ebm parimet e p\u00ebrgjithshme dhe do t\u00eb ndalem n\u00eb disa probleme t\u00eb zakonshme q\u00eb duhet t\u00eb zgjidhen.<\/p>\n<h2>Grupi i dokumenteve<\/h2>\n<p><\/p>\n<blockquote><p>Le t\u00eb fillojm\u00eb me nj\u00eb shembull.<\/p>\n<p>M\u00eb posht\u00eb jan\u00eb disa dokumente q\u00eb zakonisht krijohen n\u00eb kompanin\u00eb Cisco Systems gjat\u00eb projektimit.<\/p>\n<p><b>CR<\/b> \u2013 K\u00ebrkesat e klientit, k\u00ebrkesat e klientit (detyr\u00eb teknike).<br \/>\nKrijohet s\u00eb bashku me porosit\u00ebsin dhe p\u00ebrcakton k\u00ebrkesat p\u00ebr rrjetin.<\/p>\n<p><b>HLD<\/b> \u2013 Dizajni i Nivelit t\u00eb Lart\u00eb, dizajn i nivelit t\u00eb lart\u00eb bazuar n\u00eb k\u00ebrkesat e rrjetit (CR). Dokumenti shpjegon dhe justifikon vendimet arkitekturore t\u00eb marra (topologjia, protokollet, zgjedhja e pajisjeve, ...). HLD nuk p\u00ebrmban detaje t\u00eb dizajnit, si\u00e7 jan\u00eb nd\u00ebrfaqet e p\u00ebrdorura dhe adresat IP. Po ashtu, k\u00ebtu nuk diskutohet rreth konfigurimit t\u00eb ve\u00e7ant\u00eb t\u00eb pajisjeve. Ky dokument \u00ebsht\u00eb m\u00eb shum\u00eb p\u00ebr t\u00eb shpjeguar menaxhmentit teknik t\u00eb klientit konceptet ky\u00e7e t\u00eb dizajnit.<\/p>\n<p><b>LLD<\/b> \u2013 Dizajni n\u00eb Nivel t\u00eb Ul\u00ebt, dizajn i nivelit t\u00eb ul\u00ebt i bazuar n\u00eb dizajnin n\u00eb nivel t\u00eb lart\u00eb (HLD). <br \/>\nAi duhet t\u00eb p\u00ebrmbaj\u00eb t\u00eb gjitha detajet e nevojshme p\u00ebr realizimin e projektit, si\u00e7 \u00ebsht\u00eb informacioni mbi m\u00ebnyr\u00ebn e lidhjes dhe konfigurimit t\u00eb paisjeve. Ky \u00ebsht\u00eb nj\u00eb udh\u00ebzues i plot\u00eb p\u00ebr zbatimin e dizajnit. Ky dokument duhet t\u00eb ofroj\u00eb informacion t\u00eb mjaftuesh\u00ebm p\u00ebr zbatimin e tij edhe p\u00ebr personelin jo shum\u00eb t\u00eb kualifikuar. <\/p>\n<p>Disa gj\u00ebra, p\u00ebr shembull, adresat IP, numrat AS, skema e lidhjes fizike (cabling), mund t\u00eb \"shk\u00ebputen\" n\u00eb dokumente t\u00eb ve\u00e7anta, t\u00eb tilla si <b>NIP<\/b> (Plani p\u00ebr Zbatimin e Rrjetit).<\/p>\n<p>Nd\u00ebrtimi i rrjetit fillon pas krijimit t\u00eb k\u00ebtyre dokumenteve dhe ndodh n\u00eb p\u00ebrputhje t\u00eb plot\u00eb me to dhe m\u00eb pas kontrollohet nga porosit\u00ebsi (testet) p\u00ebr p\u00ebrputhshm\u00ebrin\u00eb me dizajnin.<\/p><\/blockquote>\n<p>\nSigurisht, k\u00ebrkesat p\u00ebr dokumentacionin e projektit mund t\u00eb jen\u00eb t\u00eb ndryshme p\u00ebr integrator\u00eb t\u00eb ndrysh\u00ebm, p\u00ebr klient\u00eb t\u00eb ndrysh\u00ebm, n\u00eb vende t\u00eb ndryshme. Por do t\u00eb d\u00ebshironim t\u00eb shmangnim formalitetet dhe t\u00eb shqyrtonim \u00e7\u00ebshtjen n\u00eb thelb. Ky etap\u00eb nuk \u00ebsht\u00eb p\u00ebr dizajnimin, por p\u00ebr vendosjen n\u00eb rregull dhe na nevojitet nj\u00eb grup dokumentesh t\u00eb mjaftueshme (skema, tabela, p\u00ebrshkrime \u2026) p\u00ebr t\u00eb plot\u00ebsuar detyrat tona. <\/p>\n<p>Dhe sipas mendimit tim, ekziston nj\u00eb minimum absolut, pa t\u00eb cilin \u00ebsht\u00eb e pamundur t\u00eb kontrollohet n\u00eb m\u00ebnyr\u00eb efektive rrjeti.<\/p>\n<p>K\u00ebto jan\u00eb dokumentet e m\u00ebposhtme:<\/p>\n<ul>\n<li>skema (d\u00ebftesa) e lidhjes fizike (cabling)<\/li>\n<li>skema ose skemat e rrjetit me informacion t\u00eb r\u00ebnd\u00ebsish\u00ebm L2\/L3<\/li>\n<\/ul>\n<p><\/p>\n<h2>Skema e lidhjes fizike<\/h2>\n<p>\nN\u00eb disa kompani t\u00eb vogla, pun\u00ebt n\u00eb lidhje me instalimin e paisjeve dhe lidhjen fizike (cabling) jan\u00eb n\u00eb zon\u00ebn e p\u00ebrgjegj\u00ebsis\u00eb s\u00eb inxhinier\u00ebve t\u00eb rrjetit. <\/p>\n<p>N\u00eb k\u00ebt\u00eb rast, detyra zgjidhet pjes\u00ebrisht duke p\u00ebrdorur qasjen e m\u00ebposhtme. <\/p>\n<ul>\n<li>p\u00ebrdorni p\u00ebrshkrimin n\u00eb nd\u00ebrfaqe p\u00ebr t\u00eb p\u00ebrshkruar at\u00eb q\u00eb \u00ebsht\u00eb lidhur me t\u00eb.<\/li>\n<li>administrativisht \u00e7aktivizoni (shutdown) t\u00eb gjith\u00eb portet e pajisjeve rrjet\u00ebrore t\u00eb pap\u00ebrfshira<\/li>\n<\/ul>\n<p>\nKjo do t'ju mund\u00ebsoj\u00eb, edhe n\u00eb rast problemi me lidhjen (kur n\u00eb k\u00ebt\u00eb nd\u00ebrfaqe nuk funksionon cdp ose lldp), t\u00eb p\u00ebrcaktoni shpejt se \u00e7far\u00eb \u00ebsht\u00eb e lidhur me k\u00ebt\u00eb port.<br \/>\nPo ashtu, do t\u00eb jeni n\u00eb gjendje t\u00eb shihni leht\u00ebsisht cilat porte jan\u00eb t\u00eb z\u00ebna dhe cilat jan\u00eb t\u00eb lira, gj\u00eb q\u00eb \u00ebsht\u00eb e nevojshme p\u00ebr planifikimin e lidhjeve t\u00eb pajisjeve t\u00eb reja rrjet\u00ebrore, server\u00ebve ose stacioneve t\u00eb pun\u00ebs. <\/p>\n<p>Por \u00ebsht\u00eb e qart\u00eb se n\u00ebse humbni qasjen n\u00eb pajisje, do t\u00eb humbni edhe qasjen n\u00eb k\u00ebt\u00eb informacion. P\u00ebr m\u00eb tep\u00ebr, n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb nuk do t\u00eb mund t\u00eb regjistroni informacionin kaq t\u00eb r\u00ebnd\u00ebsish\u00ebm si\u00e7 \u00ebsht\u00eb cili ekip, me cil\u00ebn fuqi konsumimi, sa porte ka, n\u00eb cilin raft ndodhet, cilat jan\u00eb panelat e patch-it dhe ku (n\u00eb cilin raft\/panel patch) jan\u00eb t\u00eb lidhura. Prandaj, dokumentimi shtes\u00eb (jo vet\u00ebm p\u00ebrshkrimet n\u00eb pajisje) \u00ebsht\u00eb shum\u00eb i dobish\u00ebm.<\/p>\n<p>Opsioni ideal \u00ebsht\u00eb p\u00ebrdorimi i aplikacioneve t\u00eb krijuara p\u00ebr t\u00eb punuar me k\u00ebt\u00eb lloj informacioni. Por mund t\u00eb kufizoheni edhe me tabela t\u00eb thjeshta (p.sh., n\u00eb Excel) ose t\u00eb shfaqni informacionin q\u00eb e shqyrtoni t\u00eb nevojsh\u00ebm n\u00eb skemat L1\/L2.<\/p>\n<blockquote><p>\u00cb r\u00ebnd\u00ebsishme!<\/p>\n<p>Inxhinieri rrjetor, natyrisht, mund t\u00eb dij\u00eb mjaft mir\u00eb holl\u00ebsit\u00eb dhe standardet e SCS, llojet e rafteve, llojet e burimeve t\u00eb energjis\u00eb pa nd\u00ebrprerje, \u00e7far\u00eb \u00ebsht\u00eb korridori i ftoht\u00eb dhe i ngroht\u00eb, t\u00eb b\u00ebj\u00eb nj\u00eb zbatim t\u00eb duhur,... ashtu si\u00e7 n\u00eb princip ai mund t\u00eb dij\u00eb fizik\u00ebn e grimcave elementare ose C++. Por duhet t\u00eb kuptoni q\u00eb gjith\u00eb kjo nuk \u00ebsht\u00eb fusha e njohurive t\u00eb tij. <\/p>\n<p>Prandaj, nj\u00eb praktik\u00eb e mir\u00eb \u00ebsht\u00eb q\u00eb p\u00ebr t\u00eb zgjidhur detyrat e lidhura me instalimin, lidhjen, mb\u00ebshtetje t\u00eb funksionalitetit t\u00eb pajisjeve, si dhe komunikimin fizik t\u00eb ket\u00eb ose departamente t\u00eb dedikuara ose individ\u00eb t\u00eb dedikuar. Zakonisht p\u00ebr qendrat e t\u00eb dh\u00ebnave jan\u00eb inxhinier\u00ebt e qendr\u00ebs s\u00eb t\u00eb dh\u00ebnave, nd\u00ebrsa p\u00ebr zyr\u00ebn \u2014 help-desk. <\/p>\n<p>N\u00ebse k\u00ebto n\u00ebnt\u00ebndarje jan\u00eb t\u00eb parashikuara n\u00eb kompanin\u00eb tuaj, at\u00ebher\u00eb \u00e7\u00ebshtjet e mbajtjes s\u00eb regjistrit t\u00eb komunikimit fizik nuk jan\u00eb detyra juaj, dhe ju mund t\u00eb kufizoheni vet\u00ebm me p\u00ebrshkrimin n\u00eb nd\u00ebrfaqe dhe \u00e7aktivizimin administrativ t\u00eb porteve t\u00eb pap\u00ebrdorura.<\/p><\/blockquote>\n<h2>Skemat e rrjetit<\/h2>\n<p>\nNuk ka nj\u00eb qasje universale p\u00ebr t\u00eb vizatuar skema.<\/p>\n<p>E r\u00ebnd\u00ebsishme \u00ebsht\u00eb q\u00eb skemat t\u00eb ofrojn\u00eb nj\u00eb comprendim se si do t\u00eb kaloj\u00eb trafiku, p\u00ebrmes cilave elemente logjike dhe fizike t\u00eb rrjetit tuaj.<\/p>\n<p>Me elementet fizike n\u00ebnkuptojm\u00eb<\/p>\n<ul>\n<li>pajisjet aktive<\/li>\n<li>interface\/t\u00eb porta t\u00eb pajisjeve aktive<\/li>\n<\/ul>\n<p>\nMe logjike \u2014 <\/p>\n<ul>\n<li>pajisjet logjike (N7K VDC, Palo Alto VSYS, \u2026)<\/li>\n<li>VRF <\/li>\n<li>VLAN-et<\/li>\n<li>subinterface<\/li>\n<li>tunelet<\/li>\n<li>zonat<\/li>\n<li>\u2026<\/li>\n<\/ul>\n<p>\nPo ashtu, n\u00ebse rrjeti juaj nuk \u00ebsht\u00eb krejt\u00ebsisht elementar, ai do t\u00eb p\u00ebrb\u00ebhet nga segmente t\u00eb ndryshme. <br \/>\nP\u00ebr shembull<\/p>\n<ul>\n<li>qend\u00ebr t\u00eb dh\u00ebnash<\/li>\n<li>internet<\/li>\n<li>WAN<\/li>\n<li>qasje t\u00eb larg\u00ebt<\/li>\n<li>LAN zyrtare<\/li>\n<li>DMZ<\/li>\n<li>\u2026<\/li>\n<\/ul>\n<p>\nDo t\u00eb ishte e arsyeshme t\u00eb kishim disa skema q\u00eb ofrojn\u00eb si nj\u00eb pamje t\u00eb p\u00ebrgjithshme (si kalon trafiku midis t\u00eb gjith\u00eb k\u00ebtyre segmenteve), ashtu edhe nj\u00eb shpjegim t\u00eb detajuar p\u00ebr secilin segment t\u00eb ve\u00e7ant\u00eb.<\/p>\n<p>Duke qen\u00eb se n\u00eb rrjetet moderne mund t\u00eb ket\u00eb shum\u00eb nivele logjike, nj\u00eb qasje e mir\u00eb (por jo e detyrueshme) \u00ebsht\u00eb t\u00eb b\u00ebhen skema t\u00eb ndryshme p\u00ebr nivele t\u00eb ndryshme, p\u00ebr shembull, n\u00eb rastin e nj\u00eb qasjeje overlay, skemat mund t\u00eb ishin si m\u00eb posht\u00eb:<\/p>\n<ul>\n<li>overlay<\/li>\n<li>L1\/L2 underlay<\/li>\n<li>L3 underlay<\/li>\n<\/ul>\n<p>\nSigurisht, skema m\u00eb e r\u00ebnd\u00ebsishme, pa t\u00eb cil\u00ebn nuk \u00ebsht\u00eb e mundur t\u00eb kuptohet ideja e dizajnit tuaj \u00ebsht\u00eb skema e rutimit.<\/p>\n<h4>Skema e rutimit<\/h4>\n<p>\nT\u00eb pakt\u00ebn n\u00eb k\u00ebt\u00eb skem\u00eb duhet t\u00eb reflektohet<\/p>\n<ul>\n<li>cilat protokollet e rutimit p\u00ebrdoren dhe ku<\/li>\n<li>informacioni i p\u00ebrgjithsh\u00ebm mbi cil\u00ebsimet e protokollit t\u00eb rutimit (area\/AS number\/router-id\/\u2026)<\/li>\n<li>n\u00eb cilat pajisje ndodh redistribucioni<\/li>\n<li>ku ndodh filtrimi dhe agregimi i rrug\u00ebve<\/li>\n<li>informacioni n\u00eb lidhje me rrug\u00ebn default <\/li>\n<\/ul>\n<p>\nPo ashtu, shpesh e dobishme \u00ebsht\u00eb skema L2 (OSI).<\/p>\n<h4>Skema L2 (OSI)<\/h4>\n<p>\nN\u00eb k\u00ebt\u00eb skem\u00eb mund t\u00eb reflektohet informacioni n\u00eb vijim:<\/p>\n<ul>\n<li>cilat VLAN<\/li>\n<li>cilat porta jan\u00eb porta trunk<\/li>\n<li>cilat porta jan\u00eb t\u00eb agreguara n\u00eb ether-channel (port channel), virtual port channel<\/li>\n<li>cilat protokolle STP dhe n\u00eb cilat pajisje p\u00ebrdoren<\/li>\n<li>cil\u00ebsimet kryesore t\u00eb STP: root\/root backup, STP cost, port priority<\/li>\n<li>konfigurime shtes\u00eb STP: BPDU guard\/filter, root guard ...<\/li>\n<\/ul>\n<p><\/p>\n<h2>Gabimet karakteristike gjat\u00eb projektimit<\/h2>\n<p><\/p>\n<blockquote><p>Shembulli i nj\u00eb qasjeje t\u00eb keqe p\u00ebr nd\u00ebrtimin e rrjetit.<\/p>\n<p>Le ta marrim nj\u00eb shembull t\u00eb thjesht\u00eb t\u00eb nd\u00ebrtimit t\u00eb nj\u00eb rrjeti lokal zyrtar.<\/p>\n<p>Duke pasur p\u00ebrvoj\u00eb n\u00eb m\u00ebsimdh\u00ebnien e telekomunikacioneve p\u00ebr student\u00ebt, mund t\u00eb them se n\u00eb fakt \u00e7do student, deri n\u00eb mes t\u00eb semestrit t\u00eb dyt\u00eb, ka njohurit\u00eb e nevojshme (brenda kursit q\u00eb un\u00eb kam m\u00ebsuar) p\u00ebr t\u00eb konfiguruar nj\u00eb LAN t\u00eb thjesht\u00eb zyre.<\/p>\n<p>\u00c7far\u00eb ka t\u00eb keqe n\u00eb lidhjen e switch-ev, konfigurimin e VLAN, interfeset SVI (n\u00eb rastin e switch-eve L3) dhe konfigurimin e routing-ut statik?<\/p>\n<p>T\u00eb gjitha do t\u00eb funksionojn\u00eb.<\/p>\n<p>Por n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb mbeten n\u00eb an\u00eb pyetje t\u00eb lidhura me <\/p>\n<ul>\n<li>sigurin\u00eb.<\/li>\n<li>rezervimin<\/li>\n<li>shk\u00ebmbimin e rrjetit<\/li>\n<li>performanc\u00ebn<\/li>\n<li>kapacitetin e kanalit<\/li>\n<li>besueshm\u00ebrin\u00eb.<\/li>\n<li>\u2026<\/li>\n<\/ul>\n<p>\nNdonj\u00ebher\u00eb d\u00ebgjoj pohimin se LAN-i i zyr\u00ebs \u00ebsht\u00eb di\u00e7ka shum\u00eb e thjesht\u00eb dhe zakonisht e d\u00ebgjoj k\u00ebt\u00eb nga inxhinier\u00eb (dhe menaxher\u00eb) q\u00eb merren me gjith\u00e7ka tjet\u00ebr, por jo me rrjetet, dhe e thon\u00eb k\u00ebt\u00eb me aq siguri sa t\u00eb mos habiteni n\u00ebse LAN-i do t\u00eb b\u00ebhet nga persona me praktik\u00eb dhe njohuri t\u00eb pamjaftueshme duke e b\u00ebr\u00eb at\u00eb af\u00ebrsisht me gabimet q\u00eb do t\u00eb p\u00ebrshkruaj m\u00eb posht\u00eb.<\/p><\/blockquote>\n<p><\/p>\n<h4>Gabimet e zakonshme t\u00eb dizajnit n\u00eb nivelin L1 (OSI)<\/h4>\n<p><\/p>\n<ul>\n<li>N\u00ebse megjithat\u00eb jeni p\u00ebrgjegj\u00ebs edhe p\u00ebr SCS-n\u00eb, nj\u00eb nga trash\u00ebgimit\u00eb m\u00eb t\u00eb pak\u00ebndshme q\u00eb mund t'ju vie \u2013 \u00ebsht\u00eb komutimi efikas dhe i menduar keq.<\/li>\n<\/ul>\n<p>\nPo ashtu do t\u00eb p\u00ebrfshija gabimet n\u00eb nivelin L1 t\u00eb lidhura me burimet e pajisjeve t\u00eb p\u00ebrdorura, p\u00ebr shembull,<\/p>\n<ul>\n<li>kapaciteti i pamjaftuesh\u00ebm<\/li>\n<li>TCAM-i i pamjaftuesh\u00ebm n\u00eb pajisje (ose p\u00ebrdorimi i tij i paefektsh\u00ebm)<\/li>\n<li>performanca e pamjaftueshme (shpesh lidhet me firewall-at)<\/li>\n<\/ul>\n<p><\/p>\n<h4>Gabimet e zakonshme t\u00eb dizajnit n\u00eb nivelin L2 (OSI)<\/h4>\n<p>\nM\u00eb shpesh, kur nuk ka nj\u00eb kuptim t\u00eb mir\u00eb se si funksionon STP, cilat probleme t\u00eb mundshme sjell me vete, switch-et lidhen n\u00eb m\u00ebnyr\u00eb kaotike, me konfigurime default, pa tuninga shtes\u00eb p\u00ebr STP. <\/p>\n<p>Si rezultat shpesh kemi t\u00eb m\u00ebposhtmet<\/p>\n<ul>\n<li>nj\u00eb diamet\u00ebr t\u00eb madh t\u00eb STP-s\u00eb n\u00eb rrjet, q\u00eb mund t\u00eb \u00e7oj\u00eb n\u00eb stuhira brodcast-esh <\/li>\n<li>rr\u00ebnja e STP-s\u00eb do t\u00eb p\u00ebrcaktohet rast\u00ebsisht (bazuar n\u00eb adres\u00ebn MAC) dhe rruga e trafikimit do t\u00eb jet\u00eb jo optimale<\/li>\n<li>portet e lidhura me host-et nuk do t\u00eb konfigurohen si edge (portfast), gj\u00eb q\u00eb do t\u00eb \u00e7oj\u00eb n\u00eb rip\u00ebrcaktimin e STP-s\u00eb kur ndizni\/ndizni stacionet e fundit<\/li>\n<li>rrjeti nuk do t\u00eb segmentizohet n\u00eb nivelin L1\/L2, duke rezultuar q\u00eb \u00e7do problem me nj\u00eb switch (p\u00ebr shembull, mbingarkesa me energji) do t\u00eb \u00e7oj\u00eb n\u00eb rip\u00ebrcaktimin e topologjis\u00eb STP dhe ndalimin e trafikut n\u00eb t\u00eb gjitha VLAN-et n\u00eb t\u00eb gjitha switch-et (p\u00ebrfshir\u00eb n\u00eb segmentin kritik p\u00ebr vazhdim\u00ebsin\u00eb e sh\u00ebrbimit)<\/li>\n<\/ul>\n<p><\/p>\n<h4>Shembuj t\u00eb gabimeve n\u00eb projektimin L3 (OSI)<\/h4>\n<p>\nDisa gabime t\u00eb zakonshme t\u00eb fillestar\u00ebve n\u00eb rrjet\u00eb:<\/p>\n<ul>\n<li>p\u00ebrdorimi i shpesht\u00eb (ose p\u00ebrdorimi i vet\u00ebm) i routing-ut statik<\/li>\n<li>p\u00ebrdorimi i protokolleve t\u00eb routingut t\u00eb pap\u00ebrshtatshme p\u00ebr k\u00ebt\u00eb dizajn<\/li>\n<li>segmentimi i pap\u00ebrshtatsh\u00ebm logjik i rrjetit<\/li>\n<li>p\u00ebrdorimi i pap\u00ebrshtatsh\u00ebm i hap\u00ebsir\u00ebs adresuese, q\u00eb nuk lejon agregimin e rrug\u00ebve<\/li>\n<li>mungesa e rrug\u00ebve rezerv\u00eb<\/li>\n<li>mungesa e rezervimit p\u00ebr default gateway<\/li>\n<li>routing asimetrik gjat\u00eb rind\u00ebrtimit t\u00eb rrug\u00ebve (mund t\u00eb jet\u00eb kritik n\u00eb rastin e NAT\/PAT, firewall-e statefull)<\/li>\n<li>problemet me MTU<\/li>\n<li>gjat\u00eb rind\u00ebrtimit t\u00eb rrug\u00ebve, trafikumi kalon p\u00ebrmes zonave t\u00eb tjera t\u00eb siguris\u00eb ose madje edhe firewall-eve t\u00eb tjera, gj\u00eb q\u00eb b\u00ebhet shkak p\u00ebr bllokimin e k\u00ebtij trafiku<\/li>\n<li>p\u00ebrkeq\u00ebsimi i shkallueshm\u00ebris\u00eb s\u00eb topologjis\u00eb<\/li>\n<\/ul>\n<p><\/p>\n<h2>Kriteret p\u00ebr vler\u00ebsimin e cil\u00ebsis\u00eb s\u00eb dizajnit<\/h2>\n<p>\nKur flasim p\u00ebr optimalitetin\/pak\u00ebson optimalitetin, duhet t\u00eb kuptojm\u00eb nga k\u00ebndv\u00ebshtrimi i cilave kritere mund ta vler\u00ebsojm\u00eb k\u00ebt\u00eb. Sipas mendimit tim, kriteret m\u00eb t\u00eb r\u00ebnd\u00ebsishme (por jo t\u00eb gjitha) jan\u00eb:<\/p>\n<ul>\n<li>shkallueshm\u00ebria (scalability)<br \/>\n P\u00ebr shembull, vendos\u00ebt t\u00eb shtoni nj\u00eb qend\u00ebr t\u00eb re t\u00eb t\u00eb dh\u00ebnave. Sa leht\u00eb mund ta b\u00ebni k\u00ebt\u00eb.<\/li>\n<li>p\u00ebrshtatshm\u00ebria n\u00eb menaxhim (manageability)<br \/>\n Sa leht\u00eb dhe n\u00eb m\u00ebnyr\u00eb t\u00eb sigurt b\u00ebhen ndryshime operative, p\u00ebr shembull, shpallja e nj\u00eb rrjeti t\u00eb ri ose filtrimi i rrug\u00ebve<\/li>\n<li>disponueshm\u00ebria (availability)<br \/>\n Cfar\u00eb p\u00ebrqindje e koh\u00ebs ofron sistemi juaj nivelin e k\u00ebrkuar t\u00eb sh\u00ebrbimit<\/li>\n<li>siguria (security)<br \/>\n Sa t\u00eb mbrojtura jan\u00eb t\u00eb dh\u00ebnat e transmetuara<\/li>\n<li>\u00e7mimi<\/li>\n<\/ul>\n<p><\/p>\n<h2>Ndryshimet<\/h2>\n<p>\nPrincipi kryesor n\u00eb k\u00ebt\u00eb faz\u00eb mund t\u00eb shprehet me formul\u00ebn \u00abmos b\u00ebj d\u00ebm\u00bb.<br \/>\nPrandaj, edhe n\u00ebse nuk jeni plot\u00ebsisht dakord me dizajnin dhe realizimin e zgjedhur (konfigurimin), nuk \u00ebsht\u00eb gjithmon\u00eb e arsyeshme t\u00eb b\u00ebni ndryshime. Qasja m\u00eb e arsyeshme \u00ebsht\u00eb renditja e t\u00eb gjitha problemeve t\u00eb identifikuara sipas dy parametrave: <\/p>\n<ul>\n<li>sa leht\u00eb mund t\u00eb zgjidhet ky problem<\/li>\n<li>sa i madh \u00ebsht\u00eb rreziku q\u00eb ajo p\u00ebrmban<\/li>\n<\/ul>\n<p>\nS\u00eb pari, duhet t\u00eb eliminoni at\u00eb q\u00eb aktualisht zvog\u00eblon nivelin e ofruar t\u00eb sh\u00ebrbimit n\u00ebn t\u00eb pranuar\u00ebn, p\u00ebr shembull, problemet q\u00eb \u00e7ojn\u00eb n\u00eb humbjen e paketave. Pastaj, eliminoni ato q\u00eb jan\u00eb m\u00eb t\u00eb lehta dhe m\u00eb t\u00eb sigurta p\u00ebr t'u eliminuar n\u00eb rendin e zvog\u00eblimit t\u00eb rrezikut (nga problemet n\u00eb dizajn ose konfigurim q\u00eb bartin rreziqe t\u00eb m\u00ebdha n\u00eb ato t\u00eb vogla).<\/p>\n<p>Perfeksioni n\u00eb k\u00ebt\u00eb faz\u00eb mund t\u00eb jet\u00eb d\u00ebmprur\u00ebs. Sillni dizajnin n\u00eb nj\u00eb gj \uc0c1\ud0dc t\u00eb k\u00ebnaqsh\u00ebm dhe sinkronizoni konfigurimin e rrjetit n\u00eb p\u00ebrputhje me t\u00eb.<br \/>\n<br \/>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/434750\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u042d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0432\u0442\u043e\u0440\u043e\u0439 \u0432 \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u00ab\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u00bb. \u0421\u043e\u0434\u0435\u0440\u0436\u0430\u043d\u0438\u0435 \u0432\u0441\u0435\u0445 \u0441\u0442\u0430\u0442\u0435\u0439 \u0446\u0438\u043a\u043b\u0430 \u0438 \u0441\u0441\u044b\u043b\u043a\u0438 \u043c\u043e\u0436\u043d\u043e \u043d\u0430\u0439\u0442\u0438 \u0437\u0434\u0435\u0441\u044c. \u041d\u0430\u0448\u0430 \u0446\u0435\u043b\u044c \u043d\u0430 \u0434\u0430\u043d\u043d\u043e\u043c \u044d\u0442\u0430\u043f\u0435 \u2014 \u043d\u0430\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u043f\u043e\u0440\u044f\u0434\u043a\u0430 \u0432 \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u0438 \u0438 \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u0438. \u041d\u0430 \u0432\u044b\u0445\u043e\u0434\u0435 \u044d\u0442\u043e\u0433\u043e \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u0430 \u0443 \u0432\u0430\u0441 \u0434\u043e\u043b\u0436\u0435\u043d \u0431\u044b\u0442\u044c \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u044b\u0439 \u043a\u043e\u043c\u043f\u043b\u0435\u043a\u0442 \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u043e\u0432 \u0438 \u0441\u0435\u0442\u044c, \u0441\u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u0430\u044f \u0432 \u0441\u043e\u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0438\u0438 \u0441 \u043d\u0438\u043c\u0438. \u0421\u0435\u0439\u0447\u0430\u0441 \u043c\u044b [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":23042,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-31067","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u042d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0432\u0442\u043e\u0440\u043e\u0439 \u0432 \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u00ab\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u00bb.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-vtoraya-chistka-i-dokumentirovanie\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\n\t\t<meta property=\"og:site_name\" content=\"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\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c. \u0413\u043b\u0430\u0432\u0430 \u0432\u0442\u043e\u0440\u0430\u044f. \u0427\u0438\u0441\u0442\u043a\u0430 \u0438 \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u042d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0432\u0442\u043e\u0440\u043e\u0439 \u0432 \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u00ab\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u00bb.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-vtoraya-chistka-i-dokumentirovanie\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T18:39:16+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:39:16+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Si ta kontrolloni infrastruktur\u00ebn tuaj rrjetore. Kapitulli i dyt\u00eb. Past\u00ebrtia dhe dokumentimi | ProHoster","description":"Ky kjo artikull \u00ebsht\u00eb e dyta n\u00eb ciklin e artikujve \"Si ta kontrolloni infrastruktur\u00ebn tuaj rrjetore.\"","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-vtoraya-chistka-i-dokumentirovanie","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\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c. \u0413\u043b\u0430\u0432\u0430 \u0432\u0442\u043e\u0440\u0430\u044f. \u0427\u0438\u0441\u0442\u043a\u0430 \u0438 \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 | ProHoster","og:description":"\u042d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0432\u0442\u043e\u0440\u043e\u0439 \u0432 \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u00ab\u041a\u0430\u043a \u0432\u0437\u044f\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043f\u043e\u0434 \u0441\u0432\u043e\u0439 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u00bb.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-vtoraya-chistka-i-dokumentirovanie","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-31T18:39:16+00:00","article:modified_time":"2019-10-31T18:39:16+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"31067","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-21 04:22:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 03:24:13","updated":"2026-01-21 04:22: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\/31067","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=31067"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/31067\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/23042"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=31067"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=31067"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=31067"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}