{"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":"Trajnim 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 ruterizimit n\u00ebp\u00ebrmjet protokollit OSPF. Kjo tem\u00eb, ashtu si shqyrtimi i protokollit EIGRP, \u00ebsht\u00eb shum\u00eb e r\u00ebnd\u00ebsishme p\u00ebr t\u00eb gjith\u00eb kursin CCNA. Si\u00e7 e shihni, kapitulli 2.4 quhet \u00abKonfigurimi, verifikimi dhe problemet n\u00eb nj\u00eb zon\u00eb t\u00eb vetme dhe disa zona OSPFv2 p\u00ebr protokollin IPv4 (p\u00ebrve\u00e7 autentifikimit, filtrimit, p\u00ebrmbledhjes manuale t\u00eb rrug\u00ebve, riorganizimit, zon\u00ebs t\u00eb vdekur, rrjetit virtual dhe LSA)\u00bb. <\/p>\n

\"Trajnim
\n
\nTematika OSPF \u00ebsht\u00eb e gjer\u00eb, prandaj do t\u00eb zgjas\u00eb 2, ndoshta 3 video-m\u00ebsime. M\u00ebsimi i sot\u00ebm do t\u00eb jet\u00eb dedikuar an\u00ebs teorike, do t'ju flas p\u00ebr at\u00eb se \u00e7far\u00eb \u00ebsht\u00eb ky protokoll n\u00eb terma t\u00eb p\u00ebrgjithsh\u00ebm dhe si funksionon. N\u00eb videon e ardhshme do t\u00eb kalojm\u00eb n\u00eb modin e konfigurimit t\u00eb OSPF me Packet Tracer.<\/a><\/noindex><\/p>\n

Pra, n\u00eb k\u00ebt\u00eb m\u00ebsim ne 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 fol\u00ebm q\u00eb OSPF \u00ebsht\u00eb nj\u00eb protokoll ruterizimi tipi Link State, i cili shqyrton kanalet e komunikimit midis ruterave dhe merr vendime n\u00eb baz\u00eb t\u00eb shpejt\u00ebsis\u00eb s\u00eb k\u00ebtyre kanaleve. Nj\u00eb kanal i gjat\u00eb me shpejt\u00ebsi t\u00eb lart\u00eb, pra me bandwidth m\u00eb t\u00eb madhe, do t\u00eb preferohet n\u00eb krahasim me nj\u00eb kanal t\u00eb shkurt\u00ebr me bandwidth m\u00eb t\u00eb vog\u00ebl.<\/p>\n

Protokolli RIP, duke qen\u00eb nj\u00eb protokoll me vektor t\u00eb larg\u00ebt, do t\u00eb zgjedh\u00eb nj\u00eb rrug\u00eb me nj\u00eb hop, edhe n\u00ebse ky kanal ka nj\u00eb shpejt\u00ebsi t\u00eb ul\u00ebt, nd\u00ebrsa protokolli OSPF do t\u00eb zgjedh\u00eb nj\u00eb rrug\u00eb m\u00eb t\u00eb gjat\u00eb me disa hops, 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

\"Trajnim
\n
\nM\u00eb von\u00eb do t\u00eb shqyrtojm\u00eb algoritmin e marrjes s\u00eb vendimeve, p\u00ebr tani duhet t\u00eb mbani mend se OSPF \u00ebsht\u00eb nj\u00eb protokoll i gjendjes s\u00eb kanalit Link State. Ky standard i hapur u krijua n\u00eb vitin 1988, k\u00ebshtu q\u00eb \u00e7do prodhues pajisjesh rrjetesh dhe \u00e7do ofrues sh\u00ebrbimi rrjeti mund ta p\u00ebrdor\u00eb at\u00eb. Prandaj, OSPF \u00ebsht\u00eb shum\u00eb m\u00eb i popullarizuar 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 1989, zhvilluesit shpall\u00ebn l\u00ebshimin e versionit 3, i cili mb\u00ebshtet IPv6. Megjithat\u00eb, versioni i plot\u00eb i tret\u00eb OSPF p\u00ebr IPv6 u shfaq vet\u00ebm n\u00eb vitin 2008. Pse u zgjodh pik\u00ebrisht OSPF? N\u00eb m\u00ebsimin e fundit m\u00ebsuam se ky protokoll i derit\u00ebsit brenda b\u00ebhet konvergjenca e rrug\u00ebve shum\u00eb m\u00eb shpejt se RIP. Ky \u00ebsht\u00eb nj\u00eb protokoll pa klasa. <\/p>\n

N\u00ebse e mbani mend, RIP \u00ebsht\u00eb nj\u00eb protokoll klasik, q\u00eb do t\u00eb thot\u00eb se ai nuk d\u00ebrgon informacionin p\u00ebr mask\u00ebn e n\u00ebndelb\u00ebs, dhe n\u00ebse ai p\u00ebrballet me nj\u00eb adres\u00eb IP t\u00eb klas\u00ebs A\/24, nuk do ta pranoj\u00eb at\u00eb. P\u00ebr shembull, n\u00ebse i paraqitni nj\u00eb adres\u00eb IP t\u00eb formatit 10.1.1.0\/24, ai do ta perceptoj\u00eb si rrjetin 10.0.0.0, sepse nuk kupton kur rrjeti ndahet n\u00eb n\u00ebndele n\u00ebp\u00ebrmjet p\u00ebrdorimit t\u00eb m\u00eb shum\u00eb se nj\u00eb maske n\u00ebndelb\u00ebs.
\nOSPF \u00ebsht\u00eb nj\u00eb protokoll i sigurt. P\u00ebr shembull, n\u00ebse dy rrug\u00ebzues ndajn\u00eb informacion OSPF, mund t\u00eb konfigurosh autentikimin n\u00eb nj\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb ndash informacionin me rrug\u00ebzuesin fqinj vet\u00ebm pas futjes s\u00eb fjal\u00ebkalimit. Si\u00e7 e kemi th\u00ebn\u00eb, ky \u00ebsht\u00eb nj\u00eb standard i hapur, k\u00ebshtu q\u00eb OSPF p\u00ebrdoret nga shum\u00eb prodhues t\u00eb pajisjeve rrjet\u00eb.<\/p>\n

N\u00eb nj\u00eb kuptim global, OSPF paraqet nj\u00eb mekaniz\u00ebm p\u00ebr ndarjen e shpalljeve t\u00eb gjendjes s\u00eb kanalit Link State Advertisement, ose LSA. Mesazhet LSA gjenerohen nga rrug\u00ebzuesi dhe p\u00ebrmbajn\u00eb shum\u00eb informacion: identifikues unik t\u00eb rrug\u00ebzuesit router-id, t\u00eb dh\u00ebnat mbi rrjetet q\u00eb jan\u00eb t\u00eb njohura p\u00ebr rrug\u00ebzuesin, t\u00eb dh\u00ebnat mbi koston e tyre dhe k\u00ebshtu me radh\u00eb. I gjith\u00eb ky informacion i nevojitet rrug\u00ebzuesit p\u00ebr t\u00eb marr\u00eb nj\u00eb vendim mbi p\u00ebrcjelljen. <\/p>\n

\"Trajnim
\n
\nRrug\u00ebzuesi R3 d\u00ebrgon informacionin e tij LSA tek rrug\u00ebzuesi R5, nd\u00ebrsa rrug\u00ebzuesi R5 ndan informacionin e tij LSA me R3. K\u00ebto LSA paraqesin nj\u00eb struktur\u00eb t\u00eb dh\u00ebnash q\u00eb formojn\u00eb baz\u00ebn e t\u00eb dh\u00ebnave t\u00eb gjendjes s\u00eb kanaleve Link State Data Base, ose LSDB. Rrug\u00ebzuesi mbledh t\u00eb gjitha LSA-t\u00eb e marra dhe i vendos n\u00eb LSDB-n\u00eb e tij. Pas krijimit t\u00eb bazave t\u00eb t\u00eb dh\u00ebnave, t\u00eb dy rrug\u00ebzuesit ndajn\u00eb mesazhe Hello, t\u00eb cilat sh\u00ebrbejn\u00eb p\u00ebr zbulimin e fqinj\u00ebve, dhe fillojn\u00eb procedur\u00ebn e krahasimit t\u00eb LSDB-ve t\u00eb tyre.<\/p>\n

Rrug\u00ebzuesi R3 d\u00ebrgon nj\u00eb mesazh DBD, ose \"p\u00ebrshkrimi i baz\u00ebs s\u00eb t\u00eb dh\u00ebnave\", tek rrug\u00ebzuesi R5, nd\u00ebrsa R5 i d\u00ebrgon DBD-n\u00eb e tij rrug\u00ebzuesit R3. K\u00ebto mesazhe p\u00ebrmbajn\u00eb indekset LSA q\u00eb jan\u00eb t\u00eb pranishme n\u00eb bazat e secilit rrug\u00ebzues. Pas marrjes s\u00eb DBD, rrug\u00ebzuesi R3 d\u00ebrgon nj\u00eb k\u00ebrkes\u00eb p\u00ebr gjendjen e rrjetit LSR tek rrug\u00ebzuesi R5, q\u00eb thot\u00eb: \"un\u00eb tashm\u00eb kam mesazhet 3, 4 dhe 9, prandaj m\u00eb d\u00ebrgo vet\u00ebm 5 dhe 7\". <\/p>\n

Po t\u00eb nj\u00ebjt\u00ebn m\u00ebnyr\u00eb vepron R5, i cili i raporton routerit t\u00eb tret\u00eb: \u00abkam informacionin 3, 4 dhe 9, prandaj m\u00eb d\u00ebrgoni 1 dhe 2\u00bb. Pasi t\u00eb marr\u00eb k\u00ebrkesat LSR, routerat kthejn\u00eb paketat e p\u00ebrdit\u00ebsimeve t\u00eb gjendjes s\u00eb rrjetit LSU, q\u00eb do t\u00eb thot\u00eb se n\u00eb p\u00ebrgjigje t\u00eb LSR-s\u00eb, routeri i tret\u00eb merr LSU nga routeri R5. Pas p\u00ebrdit\u00ebsimit t\u00eb bazave t\u00eb t\u00eb dh\u00ebnave nga routerat, t\u00eb gjith\u00eb, edhe n\u00ebse keni 100 routera, do t\u00eb ken\u00eb t\u00eb nj\u00ebjtat baza LSDB. Sapo t\u00eb krijohen bazat e t\u00eb dh\u00ebnave LSDB n\u00eb routera, secili prej tyre do t\u00eb dij\u00eb p\u00ebr t\u00eb gjith\u00eb rrjetin n\u00eb t\u00ebr\u00ebsi. Protokolli OSPF p\u00ebrdor algoritmin Shortest Path First p\u00ebr t\u00eb krijuar tabel\u00ebn e rrug\u00ebve, prandaj kushti m\u00eb i r\u00ebnd\u00ebsish\u00ebm p\u00ebr funksionimin e sakt\u00eb t\u00eb tij \u00ebsht\u00eb sinkronizimi i LSDB-s\u00eb s\u00eb t\u00eb gjith\u00eb pajisjeve n\u00eb rrjet. <\/p>\n

\"Trajnim
\n
\nN\u00eb diagramin e dh\u00ebn\u00eb jan\u00eb vendosur 9 routera, secili prej t\u00eb cil\u00ebve shk\u00ebmben mesazhe LSR, LSU dhe k\u00ebshtu me radh\u00eb me fqinj\u00ebt. T\u00eb gjith\u00eb ata jan\u00eb t\u00eb lidhur me nj\u00ebri-tjetrin n\u00ebp\u00ebrmjet nd\u00ebrfaqeve t\u00eb tipit p2p, ose \u00abpik\u00eb n\u00eb pik\u00eb\u00bb, q\u00eb mb\u00ebshtesin funksionimin e protokollit OSPF dhe nd\u00ebrveprojn\u00eb me nj\u00ebri-tjetrin me q\u00ebllim krijimin e LSDB-ve t\u00eb nj\u00ebjta. <\/p>\n

\"Trajnim
\n
\nSapo bazat t\u00eb jen\u00eb sinkronizuar, secili router, duke p\u00ebrdorur algoritmin e rrug\u00ebs m\u00eb t\u00eb shkurt\u00ebr, formon tabel\u00ebn e tij t\u00eb rrug\u00ebve. K\u00ebto tabela do t\u00eb jen\u00eb t\u00eb ndryshme p\u00ebr routera t\u00eb ndrysh\u00ebm. Kjo do t\u00eb thot\u00eb se t\u00eb gjith\u00eb routerat p\u00ebrdorin LSDB t\u00eb nj\u00ebjta, por krijojn\u00eb tabela rrug\u00ebve bazuar n\u00eb arsyetimet e tyre mbi rrug\u00ebt m\u00eb t\u00eb shkurtra. 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 LSDB. <\/p>\n

Pra, p\u00ebr t\u00eb funksionuar, OSPF duhet s\u00eb pari t\u00eb siguroj\u00eb 3 kushte: t\u00eb gjej\u00eb fqinj\u00ebt, t\u00eb krijoj\u00eb dhe p\u00ebrdit\u00ebsoj\u00eb LSDB-n\u00eb dhe t\u00eb formoj\u00eb tabel\u00ebn e rrug\u00ebve. P\u00ebr t\u00eb p\u00ebrmbushur kushtin e par\u00eb, administratori i rrjetit mund t\u00eb ket\u00eb nevoj\u00eb t\u00eb konfiguroj\u00eb manualisht router-id, koh\u00ebt ose mask\u00ebn wildcard. N\u00eb videon tjet\u00ebr do t\u00eb shqyrtojm\u00eb konfigurimin e pajisjes p\u00ebr t'u lidhur me OSPF, p\u00ebr tani duhet t\u00eb dini se ky protokoll p\u00ebrdor mask\u00ebn e kthimit dhe n\u00ebse ajo nuk p\u00ebrputhet, n\u00ebse n\u00ebnrrjetet tuaja nuk p\u00ebrputhen, ose n\u00ebse autentikimi nuk p\u00ebrputhet, fqinj\u00ebsia e router\u00ebve nuk do t\u00eb mund t\u00eb formohet. Prandaj, gjat\u00eb riparimit t\u00eb problemeve me OSPF, duhet t\u00eb zbulojm\u00eb pse kjo fqinj\u00ebsi nuk formohet, pra t\u00eb kontrollojm\u00eb p\u00ebrputhjen e parametrave t\u00eb p\u00ebrmendur m\u00eb sip\u00ebr.<\/p>\n

Si ju administratori i rrjetit, ju nuk merrni pjes\u00eb n\u00eb procesin e krijimit t\u00eb LSDB. 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 ndodh nd\u00ebrtimi i tabelave t\u00eb routing-ut. T\u00eb gjitha k\u00ebto i kryen vet\u00eb pajisja, e cila \u00ebsht\u00eb e konfiguruar 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\u00ebsim u kam dh\u00ebn\u00eb identifikues RID 1.1.1.1 dhe 2.2.2.2. Sa her\u00eb q\u00eb i lidhim, kanali link menj\u00ebher\u00eb kalon n\u00eb gjendjen up, sepse fillimisht i kam konfiguruar k\u00ebta router\u00eb p\u00ebr t\u00eb punuar me OSPF. Pasi t\u00eb krijohet kanali i komunikimit, routeri A menj\u00ebher\u00eb do t\u2019i d\u00ebrgoj\u00eb routerit t\u00eb dyt\u00eb nj\u00eb paket\u00eb Hello. Kjo paket\u00eb do t\u00eb p\u00ebrmbaj\u00eb informacionin se ky router nuk ka <\/p>\n

\"Trajnim
\n
\nPas marrjes s\u00eb k\u00ebsaj pakete, routeri B do t\u00eb thot\u00eb: \"Shoh se n\u00eb k\u00ebt\u00eb kanal komunikimi ka nj\u00eb kandidat t\u00eb mundsh\u00ebm p\u00ebr fqinj\u00ebsi me protokollin OSPF\" dhe do t\u00eb kaloj\u00eb n\u00eb gjendjen e inicializimit Init state. Paketa Hello \u2013 kjo nuk \u00ebsht\u00eb nj\u00eb mesazh unicast ose broadcast, por nj\u00eb paket\u00eb multicast, e d\u00ebrguar n\u00eb adres\u00ebn IP multicasting OSPF 224.0.0.5. Disa njer\u00ebz pyesin se cila \u00ebsht\u00eb maska e n\u00ebnrrjetit p\u00ebr multicasting. \u00c7\u00ebshtja \u00ebsht\u00eb se multicast nuk ka mask\u00eb n\u00ebnrrjeti, ai p\u00ebrhapet si nj\u00eb sinjal radiosh q\u00eb d\u00ebgjohet nga t\u00eb gjitha pajisjet t\u00eb cilat jan\u00eb t\u00eb konfiguruara p\u00ebr frekuenc\u00ebn e tij. P\u00ebr shembull, n\u00ebse doni t\u00eb d\u00ebgjoni FM radio q\u00eb transmeton n\u00eb frekuenc\u00ebn 91,0, at\u00ebher\u00eb konfiguroni receptorin tuaj t\u00eb radios n\u00eb k\u00ebt\u00eb frekuenc\u00eb. <\/p>\n

Po k\u00ebshtu, routeri B \u00ebsht\u00eb i konfiguruar p\u00ebr t\u00eb pranuar mesazhe p\u00ebr adres\u00ebn multicast 224.0.0.5. Duke p\u00ebrgjuar k\u00ebt\u00eb kanal, ai merr paket\u00ebn Hello q\u00eb d\u00ebrgoi routeri A dhe i p\u00ebrgjigjet me mesazhin e tij. <\/p>\n

\"Trajnim
\n
\nN\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, fqinj\u00ebsia mund t\u00eb krijohet vet\u00ebm n\u00ebse p\u00ebrgjigjja e routerit B plot\u00ebson nj\u00eb grup kriteresh. Kriteri i par\u00eb \u00ebsht\u00eb q\u00eb frekuenca e d\u00ebrgimit t\u00eb mesazheve Hello dhe intervali i pritjes s\u00eb p\u00ebrgjigjes p\u00ebr k\u00ebt\u00eb mesazh, Dead Interval, duhet t\u00eb jen\u00eb t\u00eb nj\u00ebjta p\u00ebr t\u00eb dy router\u00ebt. Zakonisht, Dead Interval \u00ebsht\u00eb i barabart\u00eb me disa vlera t\u00eb timer-it Hello. Pra, n\u00ebse Hello Timer i routerit A \u00ebsht\u00eb 10 sekonda, dhe routeri B i d\u00ebrgon nj\u00eb mesazh pas 30 sekondash, nd\u00ebrkoh\u00eb q\u00eb Dead Interval \u00ebsht\u00eb 20 sekonda, fqinj\u00ebsia nuk do t\u00eb formohet. <\/p>\n

Kriteri i dyt\u00eb \u2013 t\u00eb dy routerat duhet t\u00eb p\u00ebrdorin t\u00eb nj\u00ebjtin tip autenticimi. Prandaj, fjal\u00ebt kaluese t\u00eb autenticimit gjithashtu duhet t\u00eb jen\u00eb t\u00eb nj\u00ebjta. <\/p>\n

Kriteri i tret\u00eb \u2013 p\u00ebrputhja e identifikuesve t\u00eb zon\u00ebs Arial ID, i kat\u00ebrti \u2013 p\u00ebrputhja e gjat\u00ebsi s\u00eb prefiksit t\u00eb rrjetit. N\u00ebse routeri A njofton prefiksin \/24, at\u00ebher\u00eb routeri B gjithashtu duhet t\u00eb ket\u00eb prefiksin e rrjetit \/24. N\u00eb videon e ardhshme do t\u00eb shqyrtojm\u00eb k\u00ebt\u00eb m\u00eb n\u00eb detaje, deri at\u00ebher\u00eb do t\u00eb theksoj se kjo nuk \u00ebsht\u00eb nj\u00eb mask\u00eb n\u00ebnrrjeti, k\u00ebtu routerat p\u00ebrdorin mask\u00ebn e kund\u00ebrt Wildcard mask. Dhe natyrisht, flamujt e zon\u00ebs Stub area gjithashtu duhet t\u00eb p\u00ebrputhen, n\u00ebse routerat jan\u00eb brenda k\u00ebsaj zone. <\/p>\n

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

\"Trajnim
\n
\nN\u00eb p\u00ebrgjigje t\u00eb k\u00ebtij mesazhi, routeri A s\u00ebrish i d\u00ebrgon nj\u00eb Hello routerit B, ku konfirmon 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 vet\u00eb ai \u00ebsht\u00eb pajisja 1.1.1.1. Kjo \u00ebsht\u00eb nj\u00eb faz\u00eb shum\u00eb e r\u00ebnd\u00ebsishme n\u00eb krijimin e fqinj\u00ebsis\u00eb. N\u00eb k\u00ebt\u00eb rast, p\u00ebrdoret nj\u00eb lidhje dyansh\u00ebm 2-WAY, por \u00e7far\u00eb do t\u00eb ndodhte n\u00ebse kemi nj\u00eb switch me nj\u00eb rrjet t\u00eb shp\u00ebrndar\u00eb prej 4 routerash? N\u00eb nj\u00eb ambient t\u00eb till\u00eb \"t\u00eb shp\u00ebrndar\u00eb\", nj\u00eb nga routerat duhet t\u00eb luaj\u00eb rolin e routerit t\u00eb dedikuar Designated router D.R, dhe t\u00eb tjetri \u2013 routerit t\u00eb dedikuar rezerv\u00eb Backup designated router B.D.R.<\/p>\n

\"Trajnim
\n
\n\u00c7do nj\u00eb nga k\u00ebto pajisje do t\u00eb formoj\u00eb nj\u00eb lidhje t\u00eb plot\u00eb Full connection, ose gjendjen e plot\u00eb t\u00eb fqinj\u00ebsis\u00eb, m\u00eb von\u00eb do t\u00eb shikojm\u00eb \u00e7far\u00eb \u00ebsht\u00eb kjo, megjithat\u00eb ky tip lidhjeje do t\u00eb vendoset vet\u00ebm me D.R. dhe B.D.R, nd\u00ebrsa dy routerat e poshtme D dhe B do t\u00eb komunikojn\u00eb ende sipas skem\u00ebs s\u00eb lidhjes dyansh\u00ebm 'point-to-point'. <\/p>\n

Pra, me D.R. dhe B.D.R, t\u00eb gjitha routerat krijojn\u00eb nj\u00eb marr\u00ebdh\u00ebnie t\u00eb fqinj\u00ebsis\u00eb s\u00eb plot\u00eb, nd\u00ebrsa me nj\u00ebri-tjetrin \u2013 nj\u00eb lidhje t\u00eb tipit point-to-point. Kjo \u00ebsht\u00eb shum\u00eb e r\u00ebnd\u00ebsishme, sepse n\u00eb nj\u00eb lidhje dyansh\u00ebm t\u00eb pajisjeve fqinj\u00eb, t\u00eb gjitha parametrat e paket\u00ebs Hello duhet t\u00eb p\u00ebrputhen. N\u00eb rastin ton\u00eb, gjith\u00e7ka \u00ebsht\u00eb n\u00eb p\u00ebrputhje, prandaj pajisjet krijojn\u00eb fqinj\u00ebsin\u00eb pa asnj\u00eb problem. <\/p>\n

Sa shpejt t\u00eb instalohet lidhja dy-an\u00ebshe, routeri A d\u00ebrgon routerit B paket\u00ebn Database Description, ose \"p\u00ebrshkrimi i baz\u00ebs s\u00eb t\u00eb dh\u00ebnave\", dhe kalon n\u00eb gjendjen ExStart - fillimi i shk\u00ebmbimit, ose pritja e ngarkes\u00ebs. Database Descriptor p\u00ebrfaq\u00ebson informacionin, t\u00eb ngjash\u00ebm me p\u00ebrmbajtjen e nj\u00eb libri \u2013 kjo \u00ebsht\u00eb nj\u00eb list\u00eb e t\u00eb gjitha gj\u00ebrave q\u00eb ndodhen n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave t\u00eb routingut. N\u00eb p\u00ebrgjigje, routeri B d\u00ebrgon p\u00ebrshkrimin e tij t\u00eb baz\u00ebs s\u00eb t\u00eb dh\u00ebnave routerit A dhe kalon n\u00eb gjendjen e shk\u00ebmbimit t\u00eb t\u00eb dh\u00ebnave p\u00ebr kanalet Exchange. N\u00ebse n\u00eb gjendjen Exchange, routeri zbulon 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 mesazhe LSR, LSU dhe LSA me fqinjin.<\/p>\n

\"Trajnim
\n
\nK\u00ebshtu, routeri A do t\u00eb d\u00ebrgoj\u00eb nj\u00eb LSR fqinjit, i cili do t'i kthej\u00eb nj\u00eb paket\u00eb LSU dhe p\u00ebr k\u00ebt\u00eb routeri A do t'i p\u00ebrgjigjet routerit B me nj\u00eb mesazh LSA. Ky shk\u00ebmbim do t\u00eb ndodh\u00eb sa her\u00eb q\u00eb pajisjet duan t\u00eb ndajn\u00eb mesazhe LSA. Gjendja LOADING do t\u00eb thot\u00eb se 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 gjitha t\u00eb dh\u00ebnave, t\u00eb dy pajisjet do t\u00eb kalojn\u00eb n\u00eb gjendjen e plota t\u00eb fqinj\u00ebsis\u00eb FULL.<\/p>\n

V\u00ebrej se me nj\u00eb lidhje dy-an\u00ebshe pajisjet thjesht jan\u00eb n\u00eb gjendjen e fqinj\u00ebsis\u00eb, nd\u00ebrsa gjendja e fqinj\u00ebsis\u00eb s\u00eb plot\u00eb \u00ebsht\u00eb e mundur vet\u00ebm midis router\u00ebve, D.R. dhe B.D.R. Kjo do t\u00eb thot\u00eb se \u00e7do router njofton D.R. p\u00ebr ndryshimet n\u00eb rrjet, dhe t\u00eb gjitha router\u00ebt e tjer\u00eb e m\u00ebsojn\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 ambient t\u00eb zakonsh\u00ebm. Supozojm\u00eb se n\u00eb skem\u00ebn ton\u00eb ka tre router\u00eb dhe nj\u00eb switch. Fillimisht, pajisjet OSPF krahasojn\u00eb prioritetin n\u00eb mesazhet Hello, pastaj krahasojn\u00eb Router ID. <\/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 nj\u00ebjta, at\u00ebher\u00eb nga ato dy do t\u00eb zgjidhet pajisja me Router ID m\u00eb t\u00eb lart\u00eb, e cila do t\u00eb b\u00ebhet D.R.<\/p>\n

Rrezervari B.D.R q\u00ebndron si pajisja me prioritetin e dyt\u00eb m\u00eb t\u00eb r\u00ebnd\u00ebsish\u00ebm ose me Router ID t\u00eb dyt\u00eb m\u00eb t\u00eb r\u00ebnd\u00ebsish\u00ebm. N\u00ebse D.R. d\u00ebshton, ai do t\u00eb z\u00ebvend\u00ebsohet menj\u00ebher\u00eb nga B.D.R. Ai do t\u00eb filloj\u00eb t\u00eb luaj\u00eb rolin e D.R, nd\u00ebrsa sistemi do t\u00eb zgjedh\u00eb nj\u00eb B.D.R tjet\u00ebr.<\/p>\n

\"Trajnim
\n
\nShpresoj q\u00eb t\u00eb keni kuptuar se si t\u00eb zgjidhni D.R. dhe B.D.R, n\u00ebse jo, un\u00eb do t\u00eb kthehem p\u00ebrs\u00ebri n\u00eb k\u00ebt\u00eb \u00e7\u00ebshtje n\u00eb nj\u00ebrin nga videot e ardhshme dhe do ta shpjegoj k\u00ebt\u00eb proces. <\/p>\n

Pra ndaj, ne shqyrtuam se \u00e7far\u00eb jan\u00eb Hello, p\u00ebrshkrimi i baz\u00ebs s\u00eb t\u00eb dh\u00ebnave Database Descriptor dhe mesazhet LSR, LSU dhe LSA. Para se t\u00eb kalojm\u00eb n\u00eb tem\u00ebn tjet\u00ebr, le t\u00eb flasim pak p\u00ebr koston e OSPF. <\/p>\n

\"Trajnim
\n
\nN\u00eb Cisco, kostoja e rrug\u00ebs llogaritet sipas formul\u00ebs s\u00eb marr\u00ebdh\u00ebnies s\u00eb kapacitetit Reference bandwidth, e cila zakonisht merret si 100 Mbps, ndaj kostos s\u00eb kanalit. P\u00ebr shembull, kur lidhen pajisjet p\u00ebrmes portit serial, shpejt\u00ebsia \u00ebsht\u00eb 1.544 Mbps, dhe kostoja do t\u00eb jet\u00eb 64. Kur p\u00ebrdoret lidhja Ethernet me shpejt\u00ebsi 10 Mbps, kostoja \u00ebsht\u00eb 10, nd\u00ebrsa kostoja e lidhjes FastEthernet me shpejt\u00ebsi 100 Mbps do t\u00eb jet\u00eb 1. <\/p>\n

Kur p\u00ebrdorim Gigabit Ethernet, kemi shpejt\u00ebsin\u00eb 1000 Mbps, megjithat\u00eb n\u00eb k\u00ebt\u00eb rast shpejt\u00ebsia gjithmon\u00eb merret si 1. Pra, n\u00ebse keni n\u00eb rrjet Gigabit Ethernet, duhet ta ndryshoni vler\u00ebn e parazgjedhur 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 riheshohet me rritjen e 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\u00ebtimit. <\/p>\n

\"Trajnim
\n
\nPas marrjes s\u00eb LSDB, \u00e7do router 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 veten e tij. P\u00ebr shembull, ai llogarit kostot e rrug\u00ebs A-R1 dhe e p\u00ebrcakton at\u00eb si 10. P\u00ebr t\u00eb thjeshtuar kuptimin e skem\u00ebs, le t\u00eb supozojm\u00eb se routeri A p\u00ebrcakton rrug\u00ebn optimale p\u00ebr routerin B. Kostoja e lidhjes A-R1 \u00ebsht\u00eb 10, kostoja e lidhjes A-R2 \u00ebsht\u00eb 100, nd\u00ebrsa kostoja e rrug\u00ebs A-R3 \u00ebsht\u00eb 11, pra shuma e rrug\u00ebs A-R1(10) dhe R1-R3(1).<\/p>\n

N\u00ebse routeri A d\u00ebshiron t\u00eb arrij\u00eb tek routeri R4, ai mund ta b\u00ebj\u00eb k\u00ebt\u00eb ose p\u00ebrmes rrug\u00ebs A-R1-R4, ose p\u00ebrmes rrug\u00ebs A-R2-R4, me t\u00eb dyja rastet q\u00eb kostoja e rrug\u00ebve do t\u00eb jet\u00eb e nj\u00ebjt\u00eb: 10+100 = 100+10=110. Rruga A-R6 do t\u00eb ket\u00eb koston 100+1= 101, q\u00eb \u00ebsht\u00eb m\u00eb e mir\u00eb. M\u00eb pas shqyrtohet rruga p\u00ebr n\u00eb routerin R5 p\u00ebrmes rrug\u00ebs A-R1-R3-R5, kostoja e s\u00eb cil\u00ebs do t\u00eb jet\u00eb 10+1+100 = 111. <\/p>\n

Rruga p\u00ebr n\u00eb routerin R7 mund t\u00eb nd\u00ebrtohet p\u00ebrmes dy rrug\u00ebve: A-R1-R4-R7 ose A-R2-R6-R7. Kostoja e s\u00eb par\u00ebs do t\u00eb jet\u00eb 210, e s\u00eb dyt\u00ebs \u2013 201, k\u00ebshtu q\u00eb duhet t\u00eb zgjidhet 201. Pra, p\u00ebr t\u00eb arritur n\u00eb routerin B, routeri A mund t\u00eb p\u00ebrdor\u00eb 4 rrug\u00eb.<\/p>\n

\"Trajnim
\n
\nKostoja 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 nj\u00eb kosto prej 211. Nga kjo, rrjeti A do t\u00eb zgjedh\u00eb rrug\u00ebn me koston m\u00eb t\u00eb vog\u00ebl, e cila \u00ebsht\u00eb 121, dhe do ta vendos\u00eb at\u00eb n\u00eb tabel\u00ebn e routing. Kjo \u00ebsht\u00eb nj\u00eb skem\u00eb shum\u00eb e thjesht\u00eb se si funksionon algoritmi SPF. N\u00eb t\u00eb v\u00ebrtet\u00eb, n\u00eb tabel\u00eb nuk vendosen vet\u00ebm emrat e router-ave p\u00ebrmes t\u00eb cil\u00ebve kalon rruga optimale, por edhe emrat e porteve q\u00eb i lidhin ata dhe t\u00eb gjith\u00eb informacionin e nevojsh\u00ebm. <\/p>\n

Le t\u00eb shqyrtojm\u00eb nj\u00eb tem\u00eb tjet\u00ebr q\u00eb lidhet me zonat e routing. Zakonisht, kur konfigurojm\u00eb pajisjet OSPF, t\u00eb gjitha ato jan\u00eb n\u00eb nj\u00eb zon\u00eb t\u00eb p\u00ebrbashk\u00ebt. <\/p>\n

\"Trajnim
\n
\n\u00c7far\u00eb do t\u00eb ndodh\u00eb n\u00ebse nj\u00eb pajisje e lidhur me router-in R3 papritmas d\u00ebshtBrown? Router-i R3 menj\u00ebher\u00eb do t\u00eb filloj\u00eb t\u00eb d\u00ebrgoj\u00eb mesazhe drejt router-ave R5 dhe R1 p\u00ebr t\u00eb lajm\u00ebruar se kanali me k\u00ebt\u00eb pajisje nuk funksionon m\u00eb, dhe t\u00eb gjith\u00eb router-at do t\u00eb fillojn\u00eb t\u00eb shk\u00ebmbejn\u00eb p\u00ebrdit\u00ebsime rreth k\u00ebtij ngjarjeje. <\/p>\n

\"Trajnim
\n
\nN\u00ebse keni 100 router-a, t\u00eb gjith\u00eb do t\u00eb p\u00ebrdit\u00ebsojn\u00eb informacionin p\u00ebr gjendjen e kanaleve, sepse jan\u00eb n\u00eb nj\u00eb zon\u00eb t\u00eb p\u00ebrbashk\u00ebt. E nj\u00ebjta gj\u00eb do t\u00eb ndodh\u00eb kur nj\u00eb nga router-at fqinj d\u00ebshton \u2013 t\u00eb gjitha pajisjet n\u00eb zon\u00eb do t\u00eb shk\u00ebmbejn\u00eb p\u00ebrdit\u00ebsime LSA. Pas shk\u00ebmbimit t\u00eb k\u00ebtyre mesazheve, topologjia e rrjetit do t\u00eb ndryshoj\u00eb. Sa m\u00eb shpejt q\u00eb t\u00eb ndodh\u00eb kjo, SPF do t\u00eb rikalkuloj\u00eb tabelat e routing n\u00eb p\u00ebrputhje me kushtet e reja. Ky \u00ebsht\u00eb nj\u00eb proces shum\u00eb i madh, dhe n\u00ebse keni nj\u00eb mij\u00eb pajisje n\u00eb nj\u00eb zon\u00eb, duhet t\u00eb kontrolloni madh\u00ebsin\u00eb e memorjes s\u00eb router-ave p\u00ebr t\u00eb siguruar q\u00eb ajo t\u00eb jet\u00eb e mjaftueshme p\u00ebr t\u00eb ruajtur t\u00eb gjitha LSA-t\u00eb dhe databaz\u00ebn e madhe t\u00eb gjendjes s\u00eb kanaleve LSDB. Sa her\u00eb q\u00eb ndodhin ndryshime n\u00eb ndonj\u00eb pjes\u00eb t\u00eb zon\u00ebs, algoritmi SPF menj\u00ebher\u00eb do t\u00eb rizgjedh\u00eb rrug\u00ebt. Me rregull, LSA p\u00ebrdit\u00ebsohet \u00e7do 30 minuta. Ky proces ndodh n\u00eb t\u00eb gjitha pajisjet, por jo nj\u00ebkoh\u00ebsisht; megjithat\u00eb, \u00e7do router p\u00ebrdit\u00ebson me nj\u00eb frekuenc\u00eb prej 30 minutash. Sa m\u00eb shum\u00eb pajisje rrjeti, aq m\u00eb shum\u00eb memorie dhe koh\u00eb nevojitet p\u00ebr p\u00ebrdit\u00ebsimin e LSDB.<\/p>\n

Ky k\u00ebt\u00eb problem mund ta zgjidhni n\u00ebse e ndani nj\u00eb zon\u00eb t\u00eb p\u00ebrbashk\u00ebt n\u00eb disa zona t\u00eb ve\u00e7anta, pra duke p\u00ebrdorur multizunimin. P\u00ebr k\u00ebt\u00eb, duhet t\u00eb keni nj\u00eb plan ose nj\u00eb skem\u00eb t\u00eb gjith\u00eb rrjetit q\u00eb po menaxhoni. Zona zero AREA 0 \u00ebsht\u00eb zona juaj kryesore. Kjo \u00ebsht\u00eb vendi ku b\u00ebhet lidhja me rrjetin e jasht\u00ebm, p\u00ebr shembull, dilja 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 kufiri ABR, Area Border Router. Ruteri kufiri ka nj\u00eb nd\u00ebrfaqe n\u00eb nj\u00eb zon\u00eb dhe nj\u00eb nd\u00ebrfaqe tjet\u00ebr n\u00eb zon\u00eb tjet\u00ebr. P\u00ebr shembull, ruteri R5 ka nd\u00ebrfaqe n\u00eb zon\u00ebn 1 dhe zon\u00ebn 0. Si\u00e7 e thash\u00eb, \u00e7do zon\u00eb duhet t\u00eb jet\u00eb e lidhur me zon\u00ebn e zeros, pra t\u00eb ket\u00eb nj\u00eb ruter kufiri, nj\u00eb nga nd\u00ebrfaqet e t\u00eb cilit \u00ebsht\u00eb e lidhur me AREA 0. <\/p>\n

\"Trajnim
\n
\nSupozoni se lidhja R6-R7 ka d\u00ebshtuar. N\u00eb k\u00ebt\u00eb rast, p\u00ebrdit\u00ebsimi LSA do t\u00eb shp\u00ebrndahet vet\u00ebm n\u00eb zon\u00ebn AREA 1 dhe do t\u00eb ket\u00eb t\u00eb b\u00ebj\u00eb vet\u00ebm me k\u00ebt\u00eb zon\u00eb. Pajisjet n\u00eb zon\u00ebn 2 dhe n\u00eb zon\u00ebn 0 nuk do ta din\u00eb as q\u00eb ka ndodhur di\u00e7ka. Ruteri kufiri R5 b\u00ebn p\u00ebrmbledhjen e informacionit mbi at\u00eb q\u00eb ndodh n\u00eb zon\u00ebn e tij dhe d\u00ebrgon n\u00eb zon\u00ebn kryesore AREA 0 informacionin e p\u00ebrmbledhur mbi statusin 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 ruteri ABR do t\u00eb d\u00ebrgoj\u00eb informacionin e p\u00ebrmbledhur t\u00eb rrug\u00ebve nga nj\u00eb zon\u00eb n\u00eb tjetr\u00ebn. <\/p>\n

N\u00ebse nuk jeni plot\u00ebsisht t\u00eb sigurt p\u00ebr konceptin e zonave, mund t\u00eb merrni m\u00eb shum\u00eb informacione n\u00eb m\u00ebsimet n\u00eb vazhdim, kur do t\u00eb merremi me konfigurimin e rrug\u00ebs OSPF dhe do t\u00eb shqyrtojm\u00eb disa shembuj. <\/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":"

\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. Hyrja n\u00eb OSPF | ProHoster","description":"Sot do t\u00eb fillojm\u00eb studimin e rrug\u00ebs p\u00ebrmes protokollit OSPF. Ky tem\u00eb, ashtu si shqyrtimi i protokollit EIGRP, \u00ebsht\u00eb shum\u00eb e r\u00ebnd\u00ebsishme n\u00eb t\u00eb gjith\u00eb kursin CCNA.","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.","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","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\/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}]}}