{"id":38332,"date":"2019-10-31T22:23:01","date_gmt":"2019-10-31T19:23:01","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-44-vvedenie-v-ospf\/"},"modified":"2019-10-31T22:23:01","modified_gmt":"2019-10-31T19:23:01","slug":"trening-cisco-200-125-ccna-v3-0-den-44-vvedenie-v-ospf","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-44-vvedenie-v-ospf","title":{"rendered":"Trajnimi Cisco 200-125 CCNA v3.0. Dita 44. Hyrje n\u00eb OSPF","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Sot do t\u00eb fillojm\u00eb studimin e rrug\u00ebzimit p\u00ebrmes protokollit OSPF. Ky tem\u00eb, ashtu si shqyrtimi i protokollit EIGRP, \u00ebsht\u00eb tep\u00ebr e r\u00ebnd\u00ebsishme n\u00eb t\u00eb gjith\u00eb kursin CCNA. Si\u00e7 e shihni, kapitulli 2.4 quhet \"Konfigurimi, verifikimi dhe zgjidhja e problemeve t\u00eb zon\u00ebs s\u00eb vetme dhe shum\u00ebzonave OSPFv2 p\u00ebr protokollin IPv4 (p\u00ebrjashtuar autentifikimin, filtrimin, grumbullimin manual t\u00eb rrug\u00ebve, rikthimin, zonat e verbra, rrjetin virtual dhe LSA)\". <\/p>\n

\"Trajnimi
\n
\nTematika OSPF \u00ebsht\u00eb mjaft e gjer\u00eb, prandaj do t\u00eb zgjas\u00eb 2, ndoshta 3 video m\u00ebsimore. M\u00ebsimi i sot\u00ebm do t\u00eb p\u00ebrqendrohet n\u00eb an\u00ebn teorike, do t'ju tregoj se \u00e7far\u00eb p\u00ebrfaq\u00ebson ky protokoll n\u00eb m\u00ebnyr\u00eb t\u00eb p\u00ebrgjithshme dhe si funksionon. N\u00eb videon e ardhshme do t\u00eb kalojm\u00eb n\u00eb modalitetin e konfigurimit OSPF duke p\u00ebrdorur Packet Tracer.<\/a><\/noindex><\/p>\n

Pra k\u00ebtij m\u00ebsimi, do t\u00eb shqyrtojm\u00eb tri gj\u00ebra: \u00e7far\u00eb \u00ebsht\u00eb OSPF, si funksionon dhe \u00e7far\u00eb jan\u00eb zonat OSPF. N\u00eb m\u00ebsimin e kaluar, ne diskutuan se OSPF \u00ebsht\u00eb nj\u00eb protokoll routing i tipit Link State, i cili shqyrton kanalet e komunikimit midis router-ve dhe merr vendime t\u00eb bazuara n\u00eb shpejt\u00ebsin\u00eb e k\u00ebtyre kanaleve. Nj\u00eb kanal i gjat\u00eb me shpejt\u00ebsi m\u00eb t\u00eb madhe, pra me kapacitet m\u00eb t\u00eb madh do t\u00eb ket\u00eb prioritet mbi nj\u00eb kanal t\u00eb shkurt\u00ebr me kapacitet m\u00eb t\u00eb ul\u00ebt.<\/p>\n

Protokolli RIP, si nj\u00eb protokoll distanc\u00eb-vektori, do t\u00eb zgjedh\u00eb rrug\u00ebn me nj\u00eb hop, edhe n\u00ebse ky kanal ka shpejt\u00ebsi t\u00eb ul\u00ebt, nd\u00ebrsa protokolli OSPF do t\u00eb zgjedh\u00eb nj\u00eb rrug\u00eb t\u00eb gjat\u00eb me disa hop, n\u00ebse shpejt\u00ebsia totale n\u00eb k\u00ebt\u00eb rrug\u00eb \u00ebsht\u00eb m\u00eb e lart\u00eb se shpejt\u00ebsia e trafikut n\u00eb rrug\u00ebn e shkurt\u00ebr. <\/p>\n

\"Trajnimi
\n
\nM\u00eb von\u00eb do t\u00eb shqyrtojm\u00eb algoritmin e vendimmarrjes, p\u00ebr momentin duhet t\u00eb mbani mend se OSPF \u00ebsht\u00eb nj\u00eb protokoll i gjendjes s\u00eb kanaleve Link State. Ky standard i hapur u krijua n\u00eb vitin 1988, k\u00ebshtu q\u00eb \u00e7do prodhues pajisjesh rrjeti dhe \u00e7do ofrues sh\u00ebrbimi rrjeti mund ta p\u00ebrdor\u00eb. Prandaj, OSPF \u00ebsht\u00eb shum\u00eb m\u00eb i njohur se EIGRP. <\/p>\n

Protokolli OSPF versioni 2 mb\u00ebshtet vet\u00ebm protokollin IPv4, nd\u00ebrsa nj\u00eb vit m\u00eb von\u00eb, n\u00eb vitin 1989, zhvilluesit shpall\u00ebn l\u00ebshimin e versionit 3, i cili mb\u00ebshtet IPv6. Megjithat\u00eb, versi i plot\u00eb i tret\u00eb i OSPF p\u00ebr IPv6 u shfaq vet\u00ebm n\u00eb vitin 2008. Pse u zgjodh OSPF? N\u00eb m\u00ebsimin e fundit ne m\u00ebsuam se ky protokoll i brendsh\u00ebm i kalimit realizon konvergjenc\u00ebn e rrug\u00ebve shum\u00eb m\u00eb shpejt se RIP. Ky \u00ebsht\u00eb nj\u00eb protokoll pa klas\u00eb. <\/p>\n

N\u00ebse e mbani mend, RIP \u00ebsht\u00eb nj\u00eb protokoll me klas\u00eb, q\u00eb do t\u00eb thot\u00eb se nuk d\u00ebrgon informacion p\u00ebr mask\u00ebn e n\u00ebnrrjetit dhe n\u00ebse has nj\u00eb adres\u00eb IP t\u00eb klas\u00ebs A\\\/24, ai nuk do ta pranoj\u00eb at\u00eb. P\u00ebr shembull, n\u00ebse i paraqisni atij nj\u00eb adres\u00eb IP si 10.1.1.0\\\/24, ai do ta interpretoj\u00eb si rrjet 10.0.0.0, sepse nuk e kupton kur rrjeti ndahet n\u00eb n\u00ebnrrjeta duke p\u00ebrdorur m\u00eb shum\u00eb se nj\u00eb mask\u00eb n\u00ebnrrjeti.
\nOSPF \u00ebsht\u00eb nj\u00eb protokoll t\u00eb sigurt. P\u00ebr shembull, kur dy routera shk\u00ebmbejn\u00eb informacion OSPF, ju mund ta konfiguroni autentikimin n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb ndani informacionin me routerin fqinj vet\u00ebm pas futjes s\u00eb fjal\u00ebkalimit. Si\u00e7 e p\u00ebrmend\u00ebm, ky \u00ebsht\u00eb nj\u00eb standard i hapur, ndaj shum\u00eb prodhues t\u00eb pajisjeve rrjetin e p\u00ebrdorin OSPF.<\/p>\n

N\u00eb nj\u00eb kuptim global, OSPF \u00ebsht\u00eb nj\u00eb mekaniz\u00ebm p\u00ebr shk\u00ebmbimin e njoftimeve mbi gjendjen e lidhjes, t\u00eb njohura si Link State Advertisements, ose LSA. Mesazhet LSA gjenerohen nga router-i dhe p\u00ebrmbajn\u00eb shum\u00eb informacione: nj\u00eb identifikues unik t\u00eb router-it (router-id), t\u00eb dh\u00ebna mbi rrjetet q\u00eb i jan\u00eb t\u00eb njohura router-it, t\u00eb dh\u00ebna mbi koston e tyre dhe k\u00ebshtu me radh\u00eb. T\u00eb gjitha k\u00ebto informacione nevojiten p\u00ebr q\u00eb router-i t\u00eb marr\u00eb vendime p\u00ebr rrug\u00ebzimin. <\/p>\n

\"Trajnimi
\n
\nRouter-i R3 d\u00ebrgon informacionin e tij LSA tek router-i R5, nd\u00ebrsa router-i R5 ndan informacionin e tij LSA me R3. K\u00ebto LSA p\u00ebrfaq\u00ebsojn\u00eb nj\u00eb struktur\u00eb t\u00eb dh\u00ebnash q\u00eb formojn\u00eb baz\u00ebn e t\u00eb dh\u00ebnave t\u00eb gjendjes s\u00eb lidhjeve, t\u00eb njohur si Link State Data Base, ose LSDB. Router-i grumbullon t\u00eb gjitha LSA-t\u00eb e marra dhe i vendos ato n\u00eb LSDB-n\u00eb e tij. Pas krijimit t\u00eb bazave t\u00eb dh\u00ebnave nga t\u00eb dy router-at, ata shk\u00ebmbejn\u00eb mesazhe Hello, t\u00eb cilat sh\u00ebrbejn\u00eb p\u00ebr zbulimin e fqinj\u00ebve dhe fillojn\u00eb procedur\u00ebn p\u00ebr krahasimin e LSDB-ve t\u00eb tyre.<\/p>\n

Routeri R3 i d\u00ebrgon routerit R5 nj\u00eb mesazh DBD, ose \"p\u00ebrshkrim t\u00eb baz\u00ebs s\u00eb t\u00eb dh\u00ebnave\", dhe R5 i kthen DBD-n\u00eb routerit R3. K\u00ebto mesazhe p\u00ebrmbajn\u00eb indekset LSA q\u00eb jan\u00eb n\u00eb bazat e secilit router. Pas marrjes s\u00eb DBD-s\u00eb, routeri R3 d\u00ebrgon nj\u00eb k\u00ebrkes\u00eb p\u00ebr gjendjen e rrjetit LSR routerit R5, ku thot\u00eb: \"\u00ebsht\u00eb e qart\u00eb q\u00eb kam mesazhet 3, 4 dhe 9, k\u00ebshtu q\u00eb m\u00eb d\u00ebrgoni vet\u00ebm 5 dhe 7.\" <\/p>\n

Po ashtu vepron R5, duke i njoftuar routerit t\u00eb tret\u00eb: \"kam informacionin 3, 4 dhe 9, k\u00ebshtu q\u00eb m\u00eb d\u00ebrgoni 1 dhe 2.\" Pas marrjes s\u00eb k\u00ebrkesave LSR, router\u00ebt d\u00ebrgojn\u00eb paketa p\u00ebr azhurnimin e gjendjes s\u00eb rrjetit LSU, q\u00eb do t\u00eb thot\u00eb se n\u00eb p\u00ebrgjigje t\u00eb LSR-s\u00eb s\u00eb tyre, routeri i tret\u00eb merr LSU nga routeri R5. Pas azhurnimit t\u00eb bazave t\u00eb dh\u00ebnave nga router\u00ebt, t\u00eb gjith\u00eb ata, edhe n\u00ebse keni 100 router\u00eb, do t\u00eb ken\u00eb t\u00eb nj\u00ebjtat baza LSDB. Sa her\u00eb q\u00eb n\u00eb router\u00eb krijohen bazat e t\u00eb dh\u00ebnave LSDB, secili prej tyre do t\u00eb dij\u00eb p\u00ebr t\u00ebr\u00eb rrjetin si nj\u00eb t\u00ebr\u00ebsi. Protokolli OSPF p\u00ebrdor algoritmin e Rrug\u00ebtimit m\u00eb t\u00eb Shkurt\u00ebr p\u00ebr t\u00eb krijuar tabel\u00ebn e rrug\u00ebve, prandaj kushti m\u00eb i r\u00ebnd\u00ebsish\u00ebm p\u00ebr funksionimin e tij t\u00eb sakt\u00eb \u00ebsht\u00eb sinkronizimi i LSDB t\u00eb t\u00eb gjith\u00eb pajisjeve n\u00eb rrjet. <\/p>\n

\"Trajnimi
\n
\nN\u00eb skem\u00ebn e dh\u00ebn\u00eb jan\u00eb t\u00eb vendosura 9 router\u00eb, secili prej t\u00eb cil\u00ebve shk\u00ebmben mesazhe LSR, LSU dhe k\u00ebshtu me radh\u00eb me fqinj\u00ebt e tij. T\u00eb gjith\u00eb ata jan\u00eb t\u00eb lidhur me nj\u00ebri-tjetrin me interface p2p, ose \"pik\u00eb-pik\u00eb\", q\u00eb mb\u00ebshtesin funksionimin sipas protokollit OSPF dhe bashk\u00ebveprojn\u00eb me nj\u00ebri-tjetrin p\u00ebr t\u00eb krijuar nj\u00eb LSDB t\u00eb nj\u00ebjt\u00eb. <\/p>\n

\"Trajnimi
\n
\nSapan e bazat t\u00eb jen\u00eb sinkronizuar, \u00e7do router, duke p\u00ebrdorur algoritmin e rrug\u00ebs m\u00eb t\u00eb shkurt\u00ebr, formon tabel\u00ebn e tij t\u00eb rrug\u00ebtimit. T\u00eb gjitha router\u00ebt e ndrysh\u00ebm do t\u00eb ken\u00eb tabela t\u00eb ndryshme. K\u00ebshtu, t\u00eb gjith\u00eb router\u00ebt p\u00ebrdorin t\u00eb nj\u00ebjt\u00ebn LSDB, por krijojn\u00eb tabela rrug\u00ebtimi n\u00eb p\u00ebrputhje me arsyetimet e tyre p\u00ebr rrug\u00ebt m\u00eb t\u00eb shkurt\u00ebra. P\u00ebr t\u00eb p\u00ebrdorur k\u00ebt\u00eb algorit\u00ebm, OSPF ka nevoj\u00eb p\u00ebr p\u00ebrdit\u00ebsimin e rregullt t\u00eb baz\u00ebs s\u00eb LSDB. <\/p>\n

Pra ndaj, p\u00ebr t\u00eb funksionuar vet\u00eb, OSPF duhet s\u00eb pari t\u00eb siguroj\u00eb 3 kushte: t\u00eb gjej\u00eb fqinj\u00ebt, t\u00eb krijoj\u00eb dhe t\u00eb p\u00ebrdit\u00ebsoj\u00eb LSDB-n\u00eb dhe t\u00eb formoj\u00eb tabel\u00ebn e rutimit. P\u00ebr t\u00eb p\u00ebrmbushur kushtin e par\u00eb, admini rrjetit mund t\u00eb ket\u00eb nevoj\u00eb t\u00eb konfiguroj\u00eb manualisht router-id, koh\u00ebt ose wildcard mask. N\u00eb videon tjet\u00ebr do t\u00eb shqyrtojm\u00eb konfigurimin e pajisjes p\u00ebr t\u00eb punuar me OSPF, p\u00ebr tani duhet t\u00eb dini se ky protokoll p\u00ebrdor mask\u00ebn inverse, dhe n\u00ebse ajo nuk p\u00ebrputhet, n\u00ebse subnetet tuaja nuk p\u00ebrputhen, ose nuk p\u00ebrputhet autentikimi, fqinj\u00ebsia e router\u00ebve nuk do t\u00eb mund t\u00eb formohet. Prandaj, kur zgjidhni problemet e pun\u00ebs s\u00eb OSPF, duhet t\u00eb zbuloj\u00eb se p\u00ebrse kjo fqinj\u00ebsi nuk formohet, dometh\u00ebn\u00eb t\u00eb kontrolloni p\u00ebrputhshm\u00ebrin\u00eb e parametrave t\u00eb m\u00ebsip\u00ebrm.<\/p>\n

Si admin i rrjetit, nuk merrni pjes\u00eb n\u00eb procesin e krijimit t\u00eb LSDB-s\u00eb. P\u00ebrdit\u00ebsimi i bazave t\u00eb t\u00eb dh\u00ebnave ndodh automatikisht pas krijimit t\u00eb fqinj\u00ebsis\u00eb s\u00eb router\u00ebve, ashtu si\u00e7 \u00ebsht\u00eb nd\u00ebrtimi i tabelave t\u00eb rutimit. T\u00eb gjitha k\u00ebto b\u00ebhen nga pajisja vet\u00eb, e cila \u00ebsht\u00eb konfigurur p\u00ebr t\u00eb punuar me protokollin OSPF.
\nLe t\u00eb shqyrtojm\u00eb nj\u00eb shembull. Ne kemi 2 router\u00eb, t\u00eb cil\u00ebve p\u00ebr thjesht\u00ebsi u kam caktuar identifikuesit RID 1.1.1.1 dhe 2.2.2.2. Sapo t'i lidhim, kanali link do t\u00eb kaloj\u00eb menj\u00ebher\u00eb n\u00eb gjendjen up, sepse m\u00eb par\u00eb i kam konfiguruar k\u00ebta router\u00eb p\u00ebr t\u00eb punuar me OSPF. Sapo t\u00eb formohet kanali i lidhjes, routeri A do t'i d\u00ebrgoj\u00eb menj\u00ebher\u00eb routerit t\u00eb dyt\u00eb nj\u00eb paket\u00eb Hello. Kjo paket\u00eb do t\u00eb p\u00ebrmbaj\u00eb informacionin se ky router ende nuk ka \"pare\" ask\u00ebnd n\u00eb k\u00ebt\u00eb kanal, sepse e d\u00ebrgon Hello p\u00ebr her\u00eb t\u00eb par\u00eb, si dhe identifikuesin e tij, t\u00eb dh\u00ebnat p\u00ebr rrjetin e lidhur me t\u00eb dhe informacione t\u00eb tjera q\u00eb mund t\u00eb ndaj\u00eb me fqinjin. <\/p>\n

\"Trajnimi
\n
\nPasi e merr k\u00ebt\u00eb paket\u00eb, ruter B do t\u00eb thot\u00eb: \u00abpo shoh se n\u00eb k\u00ebt\u00eb kanalin e komunikimit ka nj\u00eb kandidat t\u00eb mundsh\u00ebm p\u00ebr fqinj\u00ebsi sipas protokollit OSPF\u00bb dhe do t\u00eb kaloj\u00eb n\u00eb gjendjen e inicializimit t\u00eb quajtur Init state. Paketa Hello \u00ebsht\u00eb nj\u00eb paket\u00eb multicast, e d\u00ebrguar n\u00eb adres\u00ebn multicast OSPF IP 224.0.0.5. Disa njer\u00ebz pyesin p\u00ebr mask\u00ebn e n\u00ebnrrjetit p\u00ebr multicast. E v\u00ebrteta \u00ebsht\u00eb se multicast nuk ka mask\u00eb n\u00ebnrrjeti, ai shp\u00ebrndahet si nj\u00eb sinjal radio q\u00eb e d\u00ebgjojn\u00eb t\u00eb gjitha pajisjet q\u00eb jan\u00eb t\u00eb konfiguruara p\u00ebr k\u00ebt\u00eb frekuenc\u00eb. P\u00ebr shembull, n\u00ebse d\u00ebshironi t\u00eb d\u00ebgjoni radio FM q\u00eb transmeton n\u00eb frekuenc\u00ebn 91,0, duhet ta rregulloni pranuesin tuaj radio n\u00eb k\u00ebt\u00eb frekuenc\u00eb. <\/p>\n

Po ashtu, ruter B \u00ebsht\u00eb i konfiguruar p\u00ebr t\u00eb pranuar mesazhe p\u00ebr adres\u00ebn multicast 224.0.0.5. Nd\u00ebrsa d\u00ebgjon k\u00ebt\u00eb kanal, ai pranon paket\u00ebn Hello, e cila \u00ebsht\u00eb d\u00ebrguar nga ruter A, dhe i p\u00ebrgjigjet me mesazhin e tij. <\/p>\n

\"Trajnimi
\n
\nDhe, fqia e p\u00ebrfshir\u00eb mund t\u00eb vendoset vet\u00ebm n\u00ebse p\u00ebrgjigjja B p\u00ebrmbush nj\u00eb grup kriteresh. Kriteri i par\u00eb \u00ebsht\u00eb frekuenca e d\u00ebrgimit t\u00eb mesazheve Hello dhe intervali i pritjes p\u00ebr p\u00ebrgjigje n\u00eb k\u00ebt\u00eb mesazh, Dead Interval, duhet t\u00eb p\u00ebrputhen p\u00ebr t\u00eb dy ruter\u00ebt. Zakonisht, Dead Interval \u00ebsht\u00eb i barabart\u00eb me disa vlera t\u00eb timer-it Hello. K\u00ebshtu, n\u00ebse Hello Timer i ruteri A \u00ebsht\u00eb 10 s dhe ruteri B i d\u00ebrgon nj\u00eb mesazh pas 30 s, nd\u00ebrsa Dead Interval \u00ebsht\u00eb 20 s, fqia nuk do t\u00eb ngushtohet. <\/p>\n

Kriteri i dyt\u00eb \u00ebsht\u00eb q\u00eb t\u00eb dy ruter\u00ebt duhet t\u00eb p\u00ebrdorin llojin e nj\u00ebjt\u00eb t\u00eb autentifikimit. K\u00ebshtu, fjal\u00ebkalimet e autentifikimit gjithashtu duhet t\u00eb p\u00ebrputhen. <\/p>\n

Kriteri i tret\u00eb \u00ebsht\u00eb p\u00ebrputhja e identifikator\u00ebve t\u00eb zon\u00ebs Arial ID, kriteri i kat\u00ebrt \u2013 p\u00ebrputhja e gjat\u00ebsi t\u00eb prefiksit t\u00eb rrjetit. N\u00ebse ruteri A raporton nj\u00eb prefiks \/24, at\u00ebher\u00eb ruteri B gjithashtu duhet t\u00eb ket\u00eb nj\u00eb prefiks rrjeti \/24. N\u00eb videon e m\u00ebposhtme do ta shqyrtojm\u00eb k\u00ebt\u00eb m\u00eb n\u00eb detaje, p\u00ebr tani v\u00ebrej se kjo nuk \u00ebsht\u00eb mask\u00eb n\u00ebnrrjeti, k\u00ebtu ruter\u00ebt p\u00ebrdorin mask\u00ebn inverse Wildcard mask. Dhe sigurisht, flamujt e zon\u00ebs stub Stub area gjithashtu duhet t\u00eb p\u00ebrputhen, n\u00ebse ruter\u00ebt ndodhen n\u00eb k\u00ebt\u00eb zon\u00eb. <\/p>\n

Pas shqyrtimit t\u00eb k\u00ebtyre kritereve, n\u00ebse ato p\u00ebrputhen, routeri B i d\u00ebrgon routerit A paket\u00ebn e tij Hello. Ndryshe nga mesazhi A, routeri B njofton se ka par\u00eb routerin A dhe paraqitet vet\u00eb. <\/p>\n

\"Trajnimi
\n
\nN\u00eb p\u00ebrgjigje t\u00eb k\u00ebtij mesazhi, routeri A p\u00ebrs\u00ebri d\u00ebrgon Hello routerit B, duke konfirmuar se gjithashtu e ka par\u00eb routerin B, kanali i komunikimit midis tyre p\u00ebrb\u00ebhet nga pajisjet 1.1.1.1 dhe 2.2.2.2, dhe ai vet\u00eb \u00ebsht\u00eb pajisja 1.1.1.1. Kjo \u00ebsht\u00eb nj\u00eb faz\u00eb shum\u00eb e r\u00ebnd\u00ebsishme p\u00ebr vendosjen e fqinj\u00ebsis\u00eb. N\u00eb k\u00ebt\u00eb rast p\u00ebrdoret nj\u00eb lidhje e dyanshme 2-WAY, por \u00e7far\u00eb do t\u00eb ndodh\u00eb n\u00ebse kemi nj\u00eb switch me nj\u00eb rrjet t\u00eb shp\u00ebrndar\u00eb prej 4 routerash? N\u00eb nj\u00eb mjedis t\u00eb till\u00eb \"t\u00eb ndar\u00eb\", nj\u00eb nga routerat duhet t\u00eb luaj\u00eb rolin e routerit t\u00eb caktuar Designated router D.R, nd\u00ebrsa tjetri \u2013 routerit rezerv\u00eb t\u00eb caktuar Backup designated router B.D.R.<\/p>\n

\"Trajnimi
\n
\nSecila nga k\u00ebto pajisje do t\u00eb krijoj\u00eb nj\u00eb lidhje t\u00eb plot\u00eb, ose nj\u00eb gjendje t\u00eb plot\u00ebsis\u00eb fqinj\u00ebsore, m\u00eb von\u00eb do ta shqyrtojm\u00eb \u00e7far\u00eb \u00ebsht\u00eb kjo, megjithat\u00eb lidhja e till\u00eb do t\u00eb vendoset vet\u00ebm me D.R. dhe B.D.R, nd\u00ebrsa dy routerat e posht\u00ebm D dhe B do t\u00eb vazhdojn\u00eb t\u00eb komunikojn\u00eb n\u00eb skem\u00ebn e lidhjes dyanshme \"point-to-point\". <\/p>\n

Kjo do t\u00eb thot\u00eb se me D.R. dhe B.D.R. t\u00eb gjith\u00eb routerat krijojn\u00eb nj\u00eb marr\u00ebdh\u00ebnie fqinj\u00ebsie t\u00eb plot\u00eb, nd\u00ebrsa mes tyre \u2013 nj\u00eb lidhje lloj point-to-point. Kjo \u00ebsht\u00eb shum\u00eb e r\u00ebnd\u00ebsishme, sepse gjat\u00eb nj\u00eb lidhjeje dypal\u00ebshe t\u00eb pajisjeve fqinje, t\u00eb gjitha parametrat e paket\u00ebs Hello duhet t\u00eb p\u00ebrputhen. N\u00eb rastin ton\u00eb, t\u00eb gjitha p\u00ebrputhen, prandaj pajisjet krijojn\u00eb fqinj\u00ebsi pa asnj\u00eb problem. <\/p>\n

Sa her\u00eb q\u00eb lidhja dypal\u00ebshe \u00ebsht\u00eb krijuar, routeri A i d\u00ebrgon routerit B nj\u00eb paket\u00eb p\u00ebrshkrimi t\u00eb baz\u00ebs s\u00eb t\u00eb dh\u00ebnave, ose 'p\u00ebrshkrimi i baz\u00ebs s\u00eb t\u00eb dh\u00ebnave', dhe kalon n\u00eb gjendjen ExStart \u2014 fillimi i shk\u00ebmbimit, ose pritja p\u00ebr ngarkes\u00eb. P\u00ebrshkruesi i Baz\u00ebs s\u00eb Dh\u00ebnave p\u00ebrb\u00ebn informacion t\u00eb ngjash\u00ebm me p\u00ebrmbajtjen e nj\u00eb libri \u2013 \u00ebsht\u00eb nj\u00eb renditje e t\u00eb gjitha atyre q\u00eb ka n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave t\u00eb rrug\u00ebs. N\u00eb p\u00ebrgjigje, routeri B d\u00ebrgon p\u00ebrshkrimin e tij t\u00eb baz\u00ebs s\u00eb t\u00eb dh\u00ebnave p\u00ebr routerin A dhe kalon n\u00eb gjendjen e shk\u00ebmbimit t\u00eb t\u00eb dh\u00ebnave mbi kanalet Exchange. N\u00ebse n\u00eb gjendjen Exchange routeri ka zbuluar se i mungon ndonj\u00eb informacion n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave, ai do t\u00eb kaloj\u00eb n\u00eb gjendjen e ngarkes\u00ebs LOADING dhe do t\u00eb filloj\u00eb t\u00eb shk\u00ebmbej\u00eb mesazhet LSR, LSU dhe LSA me fqinj\u00ebn.<\/p>\n

\"Trajnimi
\n
\nK\u00ebshtu, ruteri A do t\u00eb d\u00ebrgoj\u00eb nj\u00eb LSR te fqinj\u00ebt, ata do t\u00eb p\u00ebrgjigjen me nj\u00eb paket\u00eb LSU, dhe pastaj ruteri A do t'i d\u00ebrgoj\u00eb ruteri B nj\u00eb mesazh LSA. Ky shk\u00ebmbim do t\u00eb ndodh\u00eb sa her\u00eb q\u00eb pajisjet duan t\u00eb shk\u00ebmbejn\u00eb mesazhe LSA. Shteti LOADING do t\u00eb thot\u00eb q\u00eb p\u00ebrdit\u00ebsimi i plot\u00eb i baz\u00ebs s\u00eb t\u00eb dh\u00ebnave LSA ende nuk ka ndodhur. Pas ngarkimit t\u00eb t\u00eb dh\u00ebnave, t\u00eb dy pajisjet do t\u00eb kalojn\u00eb n\u00eb nj\u00eb gjendje t\u00eb plot\u00eb ngusht\u00ebsie FULL.<\/p>\n

V\u00ebrej se n\u00eb nj\u00eb lidhje dyanshmerr\u00ebse, pajisjet ndodhen thjesht n\u00eb nj\u00eb gjendje fqinj\u00ebsie, nd\u00ebrsa gjendja e plot\u00eb ngusht\u00ebsie \u00ebsht\u00eb e mundur vet\u00ebm midis ruter\u00ebve, D.R. dhe B.D.R. Kjo do t\u00eb thot\u00eb se \u00e7do ruter njofton D.R. p\u00ebr ndryshimet n\u00eb rrjet, dhe t\u00eb gjith\u00eb ruter\u00ebt e din\u00eb p\u00ebr k\u00ebto ndryshime nga D.R.<\/p>\n

Zgjedhja e D.R. dhe B.D.R \u00ebsht\u00eb nj\u00eb \u00e7\u00ebshtje e r\u00ebnd\u00ebsishme. Le t\u00eb shohim se si ndodh zgjedhja e D.R. n\u00eb nj\u00eb mjedis t\u00eb zakonsh\u00ebm. Supozoni se n\u00eb skem\u00ebn ton\u00eb ka tre ruter\u00eb dhe nj\u00eb switch. S\u00eb pari, pajisjet OSPF krahasojn\u00eb prioritetin n\u00eb mesazhet Hello, pastaj krahasojn\u00eb Router ID-n\u00eb. <\/p>\n

Pajisja me prioritetin m\u00eb t\u00eb lart\u00eb b\u00ebhet D.R. N\u00ebse prioritetet e dy pajisjeve jan\u00eb t\u00eb barabarta, at\u00ebher\u00eb prej tyre do t\u00eb zgjidhet pajisja me Router ID-n\u00eb m\u00eb t\u00eb lart\u00eb, e cila do t\u00eb b\u00ebhet D.R.<\/p>\n

Ruter i rezerv\u00ebs B.D.R \u00ebsht\u00eb pajisja me prioritetin e dyt\u00eb m\u00eb t\u00eb lart\u00eb ose me Router ID me r\u00ebnd\u00ebsi t\u00eb dyt\u00eb. N\u00ebse D.R. d\u00ebshton, B.D.R. do ta z\u00ebvend\u00ebsoj\u00eb menj\u00ebher\u00eb. Ai do t\u00eb filloj\u00eb t\u00eb luaj\u00eb rolin e D.R, nd\u00ebrsa sistemi do t\u00eb zgjedh\u00eb nj\u00eb tjet\u00ebr B.D.R.<\/p>\n

\"Trajnimi
\n
\nShpresoj se keni kuptuar se si t\u00eb zgjidhni D.R. dhe B.D.R, n\u00ebse jo, do t\u00eb ri-kthehem te ky \u00e7\u00ebshtje n\u00eb nj\u00eb nga videot e ardhshme dhe do ta shpjegoj k\u00ebt\u00eb proces. <\/p>\n

Pra, ne shqyrtuam se \u00e7far\u00eb p\u00ebrfaq\u00ebson Hello, p\u00ebrshkrimi i databaz\u00ebs Database Descriptor dhe mesazhet LSR, LSU dhe LSA. Para se t\u00eb kalojm\u00eb n\u00eb tem\u00ebn e ardhshme, le t\u00eb flasim pak p\u00ebr koston OSPF. <\/p>\n

\"Trajnimi
\n
\nN\u00eb Cisco, kostoja e rrug\u00ebs llogaritet sipas formul\u00ebs s\u00eb raportit t\u00eb shpejt\u00ebsis\u00eb s\u00eb referenc\u00ebs bandwidth, e cila pranohet si 100 mbit\/s si parazgjedhje, ndaj kostos s\u00eb kanalit. P\u00ebr shembull, kur pajisjet lidhen p\u00ebrmes nj\u00eb porte seriale me shpejt\u00ebsi 1.544 mbit\/s, kostoja do t\u00eb jet\u00eb 64. Nd\u00ebrsa, p\u00ebr nj\u00eb lidhje Ethernet me shpejt\u00ebsi 10 mbit\/s, kostoja \u00ebsht\u00eb 10, dhe kostoja e lidhjes FastEthernet me shpejt\u00ebsi 100 mbit\/s do t\u00eb jet\u00eb 1. <\/p>\n

Kur p\u00ebrdorni Gigabit Ethernet, ne kemi nj\u00eb shpejt\u00ebsi prej 1000 Mbit\/s, megjithat\u00eb n\u00eb k\u00ebt\u00eb rast, shpejt\u00ebsia gjithmon\u00eb pranohet t\u00eb jet\u00eb 1. Prandaj, n\u00ebse keni Gigabit Ethernet n\u00eb rrjet, duhet t\u00eb ndryshoni vler\u00ebn e paracaktuar Ref. BW n\u00eb 1000. N\u00eb k\u00ebt\u00eb rast, kostoja do t\u00eb jet\u00eb 1 dhe e gjith\u00eb tabela do t\u00eb ripohohet me rritje t\u00eb vlerave t\u00eb kostos 10 her\u00eb. Pasi t\u00eb kemi formuar fqinj\u00ebsin\u00eb dhe nd\u00ebrtuar baz\u00ebn e t\u00eb dh\u00ebnave LSDB, kalojm\u00eb n\u00eb nd\u00ebrtimin e tabel\u00ebs s\u00eb rrug\u00ebs. <\/p>\n

\"Trajnimi
\n
\nPasi t\u00eb ket\u00eb marrur LSDB, secili nga router\u00ebt menj\u00ebher\u00eb fillon t\u00eb formoj\u00eb list\u00ebn e rrug\u00ebve duke p\u00ebrdorur algoritmin SPF. N\u00eb skem\u00ebn ton\u00eb, routeri A do t\u00eb krijoj\u00eb nj\u00eb tabel\u00eb t\u00eb till\u00eb p\u00ebr vete. P\u00ebr shembull, ai llogarit kostot e rrug\u00ebs A-R1 dhe e p\u00ebrcakton at\u00eb t\u00eb barabart\u00eb me 10. P\u00ebr ta simplifikuar kuptimin e skem\u00ebs, le t\u00eb supozojm\u00eb se routeri A p\u00ebrcakton rrug\u00ebn optimale drejt routerit B. Kostoja e lidhjes A-R1 \u00ebsht\u00eb 10, lidhja A-R2 \u00ebsht\u00eb 100, dhe kostoja e rrug\u00ebs A-R3 \u00ebsht\u00eb 11, e cila \u00ebsht\u00eb shuma e rrug\u00ebs A-R1(10) dhe R1-R3(1).<\/p>\n

N\u00ebse routeri A d\u00ebshiron t\u00eb arrijn\u00eb n\u00eb routerin R4, ai mund ta b\u00ebj\u00eb k\u00ebt\u00eb ose n\u00ebp\u00ebrmjet rrug\u00ebs A-R1-R4, ose n\u00eb rrug\u00ebn A-R2-R4, dhe n\u00eb t\u00eb dy rastet kosto e rrug\u00ebve do t\u00eb jet\u00eb e nj\u00ebjt\u00eb: 10+100 =100+10=110. Rruga A-R6 do t\u00eb kushtoj\u00eb 100+1= 101, q\u00eb \u00ebsht\u00eb m\u00eb mir\u00eb. M\u00eb pas shqyrtohet rruga drejt routerit R5 n\u00ebp\u00ebrmjet rrug\u00ebs A-R1-R3-R5, kosto e s\u00eb cil\u00ebs do t\u00eb jet\u00eb 10+1+100 = 111. <\/p>\n

Rruga drejt routerit R7 mund t\u00eb kaloj\u00eb n\u00ebp\u00ebr dy rruge: A-R1-R4-R7 ose A-R2-R6-R7. Kosto e s\u00eb par\u00ebs do t\u00eb jet\u00eb 210, nd\u00ebrsa e dyt\u00ebs 201, k\u00ebshtu q\u00eb duhet t\u00eb zgjidhet 201. Pra, p\u00ebr t\u00eb arritur routerin B, routeri A mund t\u00eb p\u00ebrdor\u00eb 4 rrug\u00eb.<\/p>\n

\"Trajnimi
\n
\nKosto e rrug\u00ebs A-R1-R3-R5-B do t\u00eb jet\u00eb 121. Rruga A-R1-R4-R7-B do t\u00eb kushtoj\u00eb 220. Rruga A-R2-R4-R7-B kushton 210, nd\u00ebrsa A-R2-R6-R7-B ka kosto 211. Duke u bazuar n\u00eb k\u00ebt\u00eb, routeri A do t\u00eb zgjedh\u00eb rrug\u00ebn me koston m\u00eb t\u00eb ul\u00ebt, e barabart\u00eb me 121, dhe do ta vendos\u00eb at\u00eb n\u00eb tabel\u00ebn e rutimit. Kjo \u00ebsht\u00eb nj\u00eb skem\u00eb shum\u00eb e thjeshtuar e m\u00ebnyr\u00ebs se si funksionon algoritmi SPF. N\u00eb t\u00eb v\u00ebrtet\u00eb, n\u00eb tabel\u00eb vendoset jo vet\u00ebm emrat e router\u00ebve p\u00ebrmes t\u00eb cil\u00ebve kalon rruga optimale, por edhe emrat e porteve q\u00eb i lidhin ata dhe gjith\u00eb informacionin tjet\u00ebr t\u00eb nevojsh\u00ebm. <\/p>\n

Le t\u00eb shqyrtojm\u00eb nj\u00eb tem\u00eb tjet\u00ebr q\u00eb ka t\u00eb b\u00ebj\u00eb me zonat e ruterit. Zakonisht, gjat\u00eb konfigurimit t\u00eb pajisjeve OSPF, t\u00eb gjitha ato ndodhen n\u00eb nj\u00eb zon\u00eb t\u00eb p\u00ebrbashk\u00ebt. <\/p>\n

\"Trajnimi
\n
\n\u00c7far\u00eb do t\u00eb ndodh\u00eb n\u00ebse nj\u00eb pajisje e lidhur me routerin R3 papritur d\u00ebshton? Routeri R3 do t\u00eb filloj\u00eb menj\u00ebher\u00eb t\u00eb d\u00ebrgoj\u00eb mesazhe n\u00eb adres\u00eb t\u00eb router\u00ebve R5 dhe R1 duke njoftuar se kanali me k\u00ebt\u00eb pajisje nuk funksionon m\u00eb, dhe t\u00eb gjith\u00eb router\u00ebt do t\u00eb fillojn\u00eb t\u00eb shk\u00ebmbejn\u00eb p\u00ebrdit\u00ebsime n\u00eb lidhje me k\u00ebt\u00eb ngjarje. <\/p>\n

\"Trajnimi
\n
\nN\u00ebse keni 100 routera, t\u00eb gjith\u00eb do t\u00eb p\u00ebrdit\u00ebsojn\u00eb informacionin mbi statusin e kanaleve, pasi ndodhen n\u00eb nj\u00eb zon\u00eb t\u00eb p\u00ebrbashk\u00ebt. E nj\u00ebjta gj\u00eb do t\u00eb ndodh\u00eb n\u00eb rast se nj\u00eb nga routerat fqinj d\u00ebshton \u2013 t\u00eb gjitha pajisjet n\u00eb zon\u00eb do t\u00eb shk\u00ebmbejn\u00eb azhurnimet LSA. Pas shk\u00ebmbimit t\u00eb atyre mesazheve, topologjia e rrjetit do t\u00eb ndryshoj\u00eb. Sa her\u00eb q\u00eb kjo ndodh, SPF p\u00ebrratanon tabelat e routing-ut sipas kushteve t\u00eb ndryshuara. Ky \u00ebsht\u00eb nj\u00eb proces shum\u00eb i madhe, dhe n\u00ebse keni nj\u00eb mij\u00eb pajisje n\u00eb nj\u00eb zon\u00eb, duhet t\u00eb kontrolloni madh\u00ebsin\u00eb e memories s\u00eb routerave p\u00ebr t\u00eb siguruar q\u00eb ajo \u00ebsht\u00eb e mjaftueshme p\u00ebr t\u00eb ruajtur t\u00eb gjitha LSA-t\u00eb dhe baz\u00ebn e dh\u00ebnave t\u00eb gjendjes s\u00eb kanaleve LSDB. Sa her\u00eb q\u00eb ndodhin ndryshime n\u00eb nj\u00eb pjes\u00eb t\u00eb zon\u00ebs, algoritmi SPF menj\u00ebher\u00eb p\u00ebrratanon rrug\u00ebt. N\u00eb m\u00ebnyr\u00eb default, LSA p\u00ebrdit\u00ebsohet \u00e7do 30 minuta. Ky proces ndodh n\u00eb t\u00eb gjitha pajisjet jo nj\u00ebkoh\u00ebsisht, megjithat\u00eb n\u00eb \u00e7do rast azhurnimet b\u00ebhen nga \u00e7do router me nj\u00eb interval prej 30 minutash. Sa m\u00eb shum\u00eb pajisje rrjetesh t\u00eb keni, aq m\u00eb shum\u00eb memorie dhe koh\u00eb k\u00ebrkohet p\u00ebr t\u00eb p\u00ebrdit\u00ebsuar LSDB.<\/p>\n

Problemi mund t\u00eb zgjidhet duke ndar\u00eb nj\u00eb zon\u00eb t\u00eb p\u00ebrbashk\u00ebt n\u00eb disa zona t\u00eb ve\u00e7anta, q\u00eb do t\u00eb thot\u00eb t\u00eb p\u00ebrdorni multi-zonimin. P\u00ebr k\u00ebt\u00eb, duhet t\u00eb keni nj\u00eb plan ose skem\u00eb t\u00eb t\u00ebr\u00eb rrjetit q\u00eb menaxhoni. Zona zero AREA 0 \u00ebsht\u00eb zona juaj kryesore Main area. Kjo \u00ebsht\u00eb ajo ku ndodh lidhja me rrjetin e jasht\u00ebm, p\u00ebr shembull, dalja n\u00eb Internet. Kur krijoni zona t\u00eb reja, duhet t\u00eb drejtoheni nga rregulli: n\u00eb \u00e7do zon\u00eb duhet t\u00eb ket\u00eb nj\u00eb ruter kufitar ABR, Area Border Router. Ruteri kufitar ka nj\u00eb nd\u00ebrfaqe n\u00eb nj\u00eb zon\u00eb dhe nd\u00ebrfaqen tjet\u00ebr n\u00eb nj\u00eb zon\u00eb tjet\u00ebr. P\u00ebr shembull, ruteri R5 ka nd\u00ebrfaqe n\u00eb zon\u00ebn 1 dhe zon\u00ebn 0. Si\u00e7 thash\u00eb, \u00e7do zon\u00eb duhet t\u00eb lidh\u00eb me zon\u00ebn zero, pra t\u00eb ket\u00eb nj\u00eb ruter kufitar, nj\u00eb nga nd\u00ebrfaqet e t\u00eb cilit \u00ebsht\u00eb e lidhur me AREA 0. <\/p>\n

\"Trajnimi
\n
\nSupozoni se lidhja R6-R7 ka d\u00ebshtuar. N\u00eb k\u00ebt\u00eb rast, p\u00ebrdit\u00ebsimi LSA do t\u00eb p\u00ebrhapen vet\u00ebm n\u00eb zon\u00ebn AREA 1 dhe do t\u00eb lidhet vet\u00ebm me k\u00ebt\u00eb zon\u00eb. Pajisjet n\u00eb zon\u00ebn 2 dhe n\u00eb zon\u00ebn 0 as q\u00eb do ta din\u00eb se ndodhi kjo. Routeri kufitar R5 p\u00ebrmbledh informacionin p\u00ebr at\u00eb q\u00eb po ndodh n\u00eb zon\u00ebn e tij dhe d\u00ebrgon n\u00eb zon\u00ebn kryesore AREA 0 informacionin e p\u00ebrmbledhur mbi gjendjen e rrjetit. Pajisjet n\u00eb nj\u00eb zon\u00eb nuk kan\u00eb nevoj\u00eb t\u00eb din\u00eb p\u00ebr t\u00eb gjitha ndryshimet LSA brenda zonave t\u00eb tjera, sepse routeri ABR do t\u00eb p\u00ebrcjell\u00eb informacionin e p\u00ebrmbledhur mbi rrug\u00ebt nga nj\u00eb zon\u00eb n\u00eb tjetr\u00ebn. <\/p>\n

N\u00ebse nuk po e kuptoni plot\u00ebsisht konceptin e zonave, mund t\u00eb m\u00ebsoni m\u00eb shum\u00eb n\u00eb m\u00ebsimet e ardhshme, kur do t\u00eb merremi me konfigurimin e rrug\u00ebzimit OSPF dhe do t\u00eb shqyrtojm\u00eb disa shembuj. <\/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 \u043d\u0430\u0447\u043d\u0435\u043c \u0438\u0437\u0443\u0447\u0435\u043d\u0438\u0435 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438 \u043f\u043e \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0443 OSPF. \u042d\u0442\u0430 \u0442\u0435\u043c\u0430, \u043a\u0430\u043a \u0438 \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0435\u043d\u0438\u0435 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 EIGRP, \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0432\u0430\u0436\u043d\u0435\u0439\u0448\u0435\u0439 \u0432\u043e \u0432\u0441\u0435\u043c \u043a\u0443\u0440\u0441\u0435 CCNA. \u041a\u0430\u043a \u0432\u0438\u0434\u0438\u0442\u0435, \u0440\u0430\u0437\u0434\u0435\u043b 2.4 \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u00ab\u041d\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 \u0435\u0434\u0438\u043d\u0438\u0447\u043d\u043e\u0439 \u0437\u043e\u043d\u044b \u0438 \u043c\u0443\u043b\u044c\u0442\u0438\u0437\u043e\u043d\u044b OSPFv2 \u0434\u043b\u044f \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 IPv4 (\u0437\u0430 \u0438\u0441\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u0435\u043c \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438, \u0444\u0438\u043b\u044c\u0442\u0440\u0430\u0446\u0438\u0438, \u0440\u0443\u0447\u043d\u043e\u0433\u043e \u0441\u0443\u043c\u043c\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u043e\u0432, \u043f\u0435\u0440\u0435\u0440\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u0438\u044f, \u0442\u0443\u043f\u0438\u043a\u043e\u0432\u043e\u0439 \u043e\u0431\u043b\u0430\u0441\u0442\u0438, \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0439 \u0441\u0435\u0442\u0438 \u0438 LSA)\u00bb. \u0422\u0435\u043c\u0430 OSPF \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28774,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-38332","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 44. Hyrje n\u00eb OSPF | ProHoster","description":"Sot \u00ebn do t\u00eb fillojm\u00eb studimin e rrug\u00ebs p\u00ebrmes protokollit OSPF. Ky tem\u00eb, ashtu si shqyrtimi i protokollit EIGRP, \u00ebsht\u00eb nj\u00eb nga m\u00eb t\u00eb r\u00ebnd\u00ebsishmet n\u00eb t\u00eb gjith\u00eb kursin CCNA. Si\u00e7 e shihni, seksioni 2.4 quhet \"Konfigurimi, verifikimi dhe zgjidhja e problemeve t\u00eb zon\u00ebs unike dhe shum\u00ebzonale OSPFv2 p\u00ebr protokollin IPv4 (p\u00ebrve\u00e7 autentifikimit, filtrimit, p\u00ebrmbledhjes manuale t\u00eb rrug\u00ebve, rip\u00ebrcaktimit, zon\u00ebs t\u00eb verb\u00ebr, rrjetit virtual dhe LSA)\". Tema OSPF mjaft","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-44-vvedenie-v-ospf","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 44. \u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u0432 OSPF | ProHoster","og:description":"\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u043d\u0430\u0447\u043d\u0435\u043c \u0438\u0437\u0443\u0447\u0435\u043d\u0438\u0435 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438 \u043f\u043e \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0443 OSPF. \u042d\u0442\u0430 \u0442\u0435\u043c\u0430, \u043a\u0430\u043a \u0438 \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0435\u043d\u0438\u0435 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 EIGRP, \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0432\u0430\u0436\u043d\u0435\u0439\u0448\u0435\u0439 \u0432\u043e \u0432\u0441\u0435\u043c \u043a\u0443\u0440\u0441\u0435 CCNA. \u041a\u0430\u043a \u0432\u0438\u0434\u0438\u0442\u0435, \u0440\u0430\u0437\u0434\u0435\u043b 2.4 \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u00ab\u041d\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 \u0435\u0434\u0438\u043d\u0438\u0447\u043d\u043e\u0439 \u0437\u043e\u043d\u044b \u0438 \u043c\u0443\u043b\u044c\u0442\u0438\u0437\u043e\u043d\u044b OSPFv2 \u0434\u043b\u044f \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 IPv4 (\u0437\u0430 \u0438\u0441\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u0435\u043c \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438, \u0444\u0438\u043b\u044c\u0442\u0440\u0430\u0446\u0438\u0438, \u0440\u0443\u0447\u043d\u043e\u0433\u043e \u0441\u0443\u043c\u043c\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u043e\u0432, \u043f\u0435\u0440\u0435\u0440\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u0438\u044f, \u0442\u0443\u043f\u0438\u043a\u043e\u0432\u043e\u0439 \u043e\u0431\u043b\u0430\u0441\u0442\u0438, \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0439 \u0441\u0435\u0442\u0438 \u0438 LSA)\u00bb. \u0422\u0435\u043c\u0430 OSPF \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-44-vvedenie-v-ospf","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:23:01+00:00","article:modified_time":"2019-10-31T19:23:01+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"38332","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 21:32:21","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:11:22","updated":"2026-01-23 21:32:21"},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/38332","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=38332"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/38332\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/28774"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=38332"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=38332"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=38332"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}