{"id":37271,"date":"2019-10-31T22:16:41","date_gmt":"2019-10-31T19:16:41","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trening-cisco-200-125-ccna-v3-0-den-18-osnovy-marshrutizatsii\/"},"modified":"2019-10-31T22:16:41","modified_gmt":"2019-10-31T19:16:41","slug":"trening-cisco-200-125-ccna-v3-0-den-18-osnovy-marshrutizatsii","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-18-osnovy-marshrutizatsii","title":{"rendered":"Trajnimi Cisco 200-125 CCNA v3.0. Dita 18. Bazat e routing-ut.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Sot do t'ju paraqesim sot ruter\u00ebt. N\u00ebse keni kaluar kursin tim t\u00eb videove nga m\u00ebsimi i par\u00eb deri n\u00eb m\u00ebsimin e 17-t\u00eb, tashm\u00eb keni m\u00ebsuar bazat e switch-\u00ebve. Tani ne po kalojm\u00eb n\u00eb pajisjen tjet\u00ebr \u2013 ruterin. Si\u00e7 e dini nga videon e m\u00ebparshme, nj\u00eb nga temat e kursit CCNA quhet Cisco Switching & Routing.<\/p>\n

N\u00eb k\u00ebt\u00eb seri, ne nuk do t\u00eb studiojm\u00eb ruter\u00ebt Cisco, por do t\u00eb shqyrtojm\u00eb konceptin e \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0458\u0430\u0442\u0430 n\u00eb p\u00ebrgjith\u00ebsi. Ne do t\u00eb kemi tre tema. E para \u2013 nj\u00eb p\u00ebrmbledhje t\u00eb asaj q\u00eb tashm\u00eb e dini p\u00ebr ruter\u00ebt dhe nj\u00eb bised\u00eb mbi m\u00ebnyr\u00ebn se si mund ta zbatojm\u00eb k\u00ebt\u00eb s\u00eb bashku me njohurit\u00eb q\u00eb keni fituar gjat\u00eb studimit t\u00eb switch-\u00ebve. Ne duhet t\u00eb kuptojm\u00eb si funksionon sistemi i bashk\u00ebveprimit midis switch-\u00ebve dhe ruter\u00ebve.<\/p>\n

\"Trajnimi
\n
\nM\u00eb pas do t\u00eb shqyrtojm\u00eb se \u00e7far\u00eb \u00ebsht\u00eb \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u044f\u0442\u0430, \u00e7far\u00eb do t\u00eb thot\u00eb dhe si funksionon, dhe pastaj do t\u00eb kalojm\u00eb n\u00eb tipet e protokolleve t\u00eb \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0458\u0435. Sot un\u00eb po p\u00ebrdor topologjin\u00eb q\u00eb e keni par\u00eb n\u00eb m\u00ebsimet e m\u00ebparshme. <\/a><\/noindex><\/p>\n

Ne kemi shqyrtuar se si t\u00eb dh\u00ebnat l\u00ebvizin p\u00ebrmes rrjetit dhe si kryhet dor\u00ebzim tre fazash TCP. Mesazhi i par\u00eb q\u00eb d\u00ebrgohet p\u00ebrmes rrjetit \u00ebsht\u00eb nj\u00eb paket\u00eb SYN. Le t\u00eb shohim se si ndodh dor\u00ebzimi tre fazash kur kompjuteri me adres\u00ebn IP 10.1.1.10 d\u00ebshiron t\u00eb lidhet me serverin 30.1.1.10, dmth. p\u00ebrpiqet t\u00eb krijoj\u00eb nj\u00eb lidhje FTP.
\nP\u00ebr t\u00eb filluar lidhjen, kompjuteri krijon nj\u00eb port burimi me nj\u00eb num\u00ebr t\u00eb rast\u00ebsish\u00ebm 25113. N\u00ebse e keni harruar se si ndodh kjo, ju rekomandoj t\u00eb shikoni s\u00ebrish videon e m\u00ebparshme q\u00eb trajton k\u00ebt\u00eb \u00e7\u00ebshtje. <\/p>\n

\"Trajnimi
\n
\nM\u00eb pas, ai vendos n\u00eb frame numrin e port\u00ebs s\u00eb destinacionit, sepse e di se duhet t\u00eb lidhet me portin 21, pastaj shton informacionin e nivelit t\u00eb tret\u00eb t\u00eb OSI, dmth. adres\u00ebn e tij IP dhe adres\u00ebn IP t\u00eb destinacionit. T\u00eb dh\u00ebnat, t\u00eb sh\u00ebnuara me vij\u00eb t\u00eb nd\u00ebrprer\u00eb, nuk ndryshojn\u00eb derisa t\u00eb arrijn\u00eb pik\u00ebn p\u00ebrfundimtare. Pasi arrijn\u00eb n\u00eb server, ato gjithashtu nuk ndryshojn\u00eb, por serveri shton n\u00eb frame informacionin e nivelit t\u00eb dyt\u00eb, dmth. adres\u00ebn MAC. Kjo \u00ebsht\u00eb p\u00ebr shkak se switch-\u00ebt perceptojn\u00eb vet\u00ebm informacionin e nivelit t\u00eb dyt\u00eb t\u00eb OSI. N\u00eb k\u00ebt\u00eb skenar, router-i \u00ebsht\u00eb pajisja e vetme e rrjetit q\u00eb shqyrton informacionin e nivelit t\u00eb tret\u00eb, natyrisht, kompjuteri gjithashtu punon me k\u00ebt\u00eb informacion. Pra, switch-i punon vet\u00ebm me informacionin e nivelit t\u00eb dyt\u00eb, nd\u00ebrsa router-i me at\u00eb t\u00eb tret\u00eb. <\/p>\n

Switch-i njeh adres\u00ebn MAC origjinale XXXX:XXXX:1111 dhe d\u00ebshiron t\u00eb dij\u00eb adres\u00ebn MAC t\u00eb serverit, me t\u00eb cilin po komunikon kompjuteri. Ai e krahaso adres\u00ebn IP origjinale me adres\u00ebn e caktuar, kupton se k\u00ebto pajisje ndodhen n\u00eb subnet t\u00eb ndrysh\u00ebm dhe merr vendimin t\u00eb p\u00ebrdor\u00eb nj\u00eb gateway p\u00ebr t\u00eb hyr\u00eb n\u00eb subnet tjet\u00ebr.<\/p>\n

M\u00eb shpesh m\u00eb b\u00ebhet pyetja, kush vendos se cili duhet t\u00eb jet\u00eb adresa IP e gateway-it. S\u00eb pari, kjo p\u00ebrcaktohet nga administratori i rrjetit, i cili krijon rrjetin dhe cakton nj\u00eb adres\u00eb IP p\u00ebr \u00e7do pajisje. Si administrator, ju mund t\u00eb caktoni router-it \u00e7do adres\u00eb brenda gam\u00ebs s\u00eb adresave t\u00eb lejuara t\u00eb subnet-it tuaj. Zakonisht \u00ebsht\u00eb adresa e par\u00eb ose e fundit e lejuar, por nuk ka rregulla strikte p\u00ebr caktimin e saj. N\u00eb rastin ton\u00eb, administratori e caktoi adres\u00ebn e gateway-it, ose router-it, 10.1.1.1 dhe ia dha portit F0\/0. <\/p>\n

Kur konfiguroni nj\u00eb rrjet n\u00eb kompjuter me adres\u00eb IP statike 10.1.1.10, ju caktoni mask\u00ebn e subnet-it 255.255.255.0 dhe gateway-n\u00eb e paracaktuar 10.1.1.1. N\u00ebse nuk po p\u00ebrdorni nj\u00eb adres\u00eb statike, at\u00ebher\u00eb kompjuteri po p\u00ebrdor DHCP, i cili cakton nj\u00eb adres\u00eb dinamike. Pavar\u00ebsisht n\u00ebse kompjuteri p\u00ebrdor nj\u00eb adres\u00eb IP statike apo dinamike, duhet t\u00eb ket\u00eb nj\u00eb adres\u00eb gateway p\u00ebr t\u00eb dal\u00eb n\u00eb nj\u00eb rrjet tjet\u00ebr. <\/p>\n

K\u00ebshtu, kompjuteri 10.1.1.10 e di se duhet t\u00eb d\u00ebrgoj\u00eb nj\u00eb frame te router-i 10.1.1.1. Ky transferim ndodh brenda rrjetit lokal, ku adresa IP nuk ka r\u00ebnd\u00ebsi; k\u00ebtu r\u00ebnd\u00ebsi ka vet\u00ebm adresa MAC. Le t\u00eb supozojm\u00eb se kompjuteri m\u00eb par\u00eb nuk ka komunikuar kurr\u00eb me router-in dhe nuk e di adres\u00ebn e tij MAC, prandaj ai duhet s\u00eb pari t\u00eb d\u00ebrgoj\u00eb nj\u00eb k\u00ebrkes\u00eb ARP, me t\u00eb cil\u00ebn i pyet t\u00eb gjitha pajisjet e subnet-it: \"Hej, kush prej jush ka adres\u00ebn 10.1.1.1? Ju lutem, m\u00eb tregoni adres\u00ebn tuaj MAC!\". Duke qen\u00eb se ARP \u00ebsht\u00eb nj\u00eb mesazh i shp\u00ebrndar\u00eb, ai arrin n\u00eb t\u00eb gjitha portet e t\u00eb gjitha pajisjeve, duke p\u00ebrfshir\u00eb edhe router-in. <\/p>\n

Kompiuteri 10.1.1.12, pasi duke marr\u00eb ARP, mendon: \u00abjo, adresa ime nuk \u00ebsht\u00eb 10.1.1.1\u00bb, dhe e hodh posht\u00eb k\u00ebrkes\u00ebn, nj\u00ebsoj vepron edhe kompjuteri 10.1.1.13. Ruter, pasi merr k\u00ebrkes\u00ebn, kupton se \u00ebsht\u00eb sakt\u00ebsisht p\u00ebr t\u00eb q\u00eb po pyesin dhe d\u00ebrgon adres\u00ebn MAC t\u00eb portit F0\/0 \u2013 t\u00eb gjitha portet kan\u00eb adres\u00eb MAC t\u00eb ndryshme \u2013 kompjuterit 10.1.1.10. Tani, duke e ditur adres\u00ebn e gateway XXXX:AAAA, e cila n\u00eb k\u00ebt\u00eb rast \u00ebsht\u00eb adresa e destinacionit, kompjuteri e shton at\u00eb n\u00eb fund t\u00eb flet\u00ebs s\u00eb d\u00ebrguar tek serveri. Nj\u00ebkoh\u00ebsisht, ai vendos n\u00eb titullin e flet\u00ebs FCS\/CRC, e cila \u00ebsht\u00eb nj\u00eb mekaniz\u00ebm i kontrollit t\u00eb gabimeve t\u00eb transmetimit. <\/p>\n

\"Trajnimi
\n
\nPas k\u00ebsaj, fletta e kompjuterit 10.1.1.10 d\u00ebrgohet p\u00ebrmes kabllove drejt ruterit 10.1.1.1. Pasi merr flet\u00ebn, ruteri heq FCS\/CRC, duke p\u00ebrdorur t\u00eb nj\u00ebjtin algorit\u00ebm p\u00ebr verifikimin q\u00eb p\u00ebrdori kompjuteri. T\u00eb dh\u00ebnat p\u00ebrb\u00ebjn\u00eb asgj\u00eb m\u00eb shum\u00eb se nj\u00eb grumbull zerosh dhe nj\u00ebsish. N\u00ebse t\u00eb dh\u00ebnat jan\u00eb d\u00ebmtuar, dmth 1 b\u00ebhet 0 ose 0 b\u00ebhet 1, ose ka nj\u00eb rrjedhje t\u00eb dh\u00ebnash q\u00eb ndodhi shpesh gjat\u00eb p\u00ebrdorimit t\u00eb hub-it, at\u00ebher\u00eb pajisja duhet ta d\u00ebrgoj\u00eb p\u00ebrs\u00ebri flet\u00ebn. <\/p>\n

N\u00ebse verifikimi i FCS\/CRC kalon me sukses, ruteri shikon adresat MAC t\u00eb burimit dhe destinacionit dhe i heq ato, pasi \u00ebsht\u00eb informat\u00eb e nivelit t\u00eb dyt\u00eb, dhe kalon n\u00eb trupin e flet\u00ebs, ku p\u00ebrmban informacionin e nivelit t\u00eb tret\u00eb. Nga kjo ai m\u00ebson se informacioni q\u00eb p\u00ebrmban fletta \u00ebsht\u00eb p\u00ebr pajisjen me adres\u00ebn IP 30.1.1.10. <\/p>\n

Ruteri n\u00eb nj\u00ebfar\u00eb m\u00ebnyre e di se ku ndodhet kjo pajisje. Ne nuk e diskutuam k\u00ebt\u00eb \u00e7\u00ebshtje kur shqyrtuam pun\u00ebn e switches, prandaj ta shqyrtojm\u00eb tani. Ruteri ka 4 porte, k\u00ebshtu q\u00eb un\u00eb i kam shtuar disa lidhje. Pra, nga e di ruteri se t\u00eb dh\u00ebnat p\u00ebr pajisjen me adres\u00ebn IP 30.1.1.10 duhen d\u00ebrguar p\u00ebrmes portit F0\/1? Pse nuk i d\u00ebrgon ato p\u00ebrmes portit F0\/3 ose F0\/2?<\/p>\n

Ajo q\u00eb ndodh \u00ebsht\u00eb se ruteri punon me nj\u00eb tabel\u00eb rrug\u00ebzimi. \u00c7do ruter ka nj\u00eb tabel\u00eb t\u00eb till\u00eb q\u00eb i lejon t\u00eb marr\u00eb vendim se p\u00ebrmes cilit port duhet t\u00eb d\u00ebrgoj\u00eb nj\u00eb flett\u00eb t\u00eb caktuar. <\/p>\n

\"Trajnimi
\n
\nN\u00eb k\u00ebt\u00eb rast, porta F0\/0 \u00ebsht\u00eb konfiguruar me adres\u00ebn IP 10.1.1.1 dhe kjo do t\u00eb thot\u00eb se ajo \u00ebsht\u00eb e lidhur me rrjetin 10.1.1.10\/24. Po ashtu, porta F0\/1 \u00ebsht\u00eb e konfiguruar me adres\u00ebn 20.1.1.1, q\u00eb do t\u00eb thot\u00eb se \u00ebsht\u00eb e lidhur me rrjetin 20.1.1.0\/24. Routeri di p\u00ebr k\u00ebto dy rrjete, sepse ato jan\u00eb t\u00eb lidhura direkt me portat e tij. K\u00ebshtu, informacioni q\u00eb trafik p\u00ebr rrjetin 10.1.10\/24 duhet t\u00eb kaloj\u00eb p\u00ebrmes port\u00ebs F0\/0, nd\u00ebrsa p\u00ebr rrjetin 20.1.1.0\/24 - p\u00ebrmes port\u00ebs F0\/1, \u00ebsht\u00eb i njohur si parazgjedhje. Nga e di routeri se p\u00ebr cilat porte t\u00eb punoj\u00eb p\u00ebr rrjetet e tjera?<\/p>\n

Ne shohim se rrjeti 40.1.1.0\/24 \u00ebsht\u00eb i lidhur me port\u00ebn F0\/2, rrjeti 50.1.1.0\/24 - me port\u00ebn F0\/3, dhe rrjeti 30.1.1.0\/24 lidh routern e dyt\u00eb me serverin. Routeri i dyt\u00eb gjithashtu ka nj\u00eb tabel\u00eb rutesh, ku thuhet se rrjeti 30. \u00ebsht\u00eb i lidhur me port\u00ebn e tij, le t\u00eb e quajm\u00eb 0\/1, dhe me routerin e par\u00eb \u00ebsht\u00eb i lidhur p\u00ebrmes port\u00ebs 0\/0. Ky router e di se porta e tij 0\/0 \u00ebsht\u00eb e lidhur me rrjetin 20., nd\u00ebrsa porta 0\/1 \u00ebsht\u00eb e lidhur me rrjetin 30., dhe nuk di m\u00eb asgj\u00eb.<\/p>\n

Po ashtu routeri i par\u00eb di p\u00ebr rrjetet 40. dhe 50., t\u00eb lidhura me portat 0\/2 dhe 0\/3, por nuk di asgj\u00eb p\u00ebr rrjetin 30. Protokolli i rutesh ofron router\u00ebve informacionin q\u00eb ata nuk e kan\u00eb si parazgjedhje. Mekanizmi me t\u00eb cilin k\u00ebta router\u00eb integrohen me nj\u00ebri-tjetrin \u00ebsht\u00eb themeli i rutesh, duke pasur nj\u00eb rutesh dinamik dhe statik. <\/p>\n

Rutesh statik p\u00ebrfshin q\u00eb routerit t\u00eb par\u00eb t'i jepet informacioni: n\u00ebse duhet t\u00eb lidhet me rrjetin 30.1.1.0\/24, at\u00ebher\u00eb duhet t\u00eb p\u00ebrdor\u00eb port\u00ebn F0\/1. Por kur routeri i dyt\u00eb merr trafik nga serveri q\u00eb \u00ebsht\u00eb i destinuar p\u00ebr kompjuterin 10.1.1.10, ai nuk di \u00e7far\u00eb t\u00eb b\u00ebj\u00eb, sepse n\u00eb tabel\u00ebn e tij t\u00eb rutesh ka vet\u00ebm t\u00eb dh\u00ebna p\u00ebr rrjetet 30. dhe 20. Prandaj, k\u00ebtij routeri i nevojitet gjithashtu t\u00eb konfiguroj\u00eb rutesh statik: n\u00ebse merr trafik p\u00ebr rrjetin 10., at\u00ebher\u00eb duhet ta d\u00ebrgoj\u00eb p\u00ebrmes port\u00ebs 0\/0. <\/p>\n

Problemi me rutesh statik \u00ebsht\u00eb se duhet ta konfiguroni manualisht routerin e par\u00eb p\u00ebr t\u00eb punuar me rrjetin 30., nd\u00ebrsa routerin e dyt\u00eb p\u00ebr t\u00eb punuar me rrjetin 10. Kjo \u00ebsht\u00eb e thjesht\u00eb n\u00ebse kam vet\u00ebm 2 router\u00eb, por kur kam 10 router\u00eb, konfigurimi i rutesh statik merr shum\u00eb koh\u00eb. N\u00eb k\u00ebt\u00eb rast, ka kuptim t\u00eb p\u00ebrdorim rutesh dinamik.
\nPra t\u00eb pranuar nj\u00eb kad\u00ebr nga kompjuteri, rruga e par\u00eb shikon n\u00eb tabel\u00ebn e saj t\u00eb ruteve dhe merr nj\u00eb vendim p\u00ebr ta d\u00ebrguar at\u00eb p\u00ebrmes portit F0\/1. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, ajo shton n\u00eb kad\u00ebr adres\u00ebn MAC t\u00eb burimit XXXX.BBBB dhe adres\u00ebn MAC t\u00eb destinacionit XXXX.CCCC. <\/p>\n

\"Trajnimi
\n
\nPasi merr k\u00ebt\u00eb kad\u00ebr, rruga e dyt\u00eb \"prenton\" adresat MAC q\u00eb i p\u00ebrkasin nivelit t\u00eb dyt\u00eb OSI dhe kalon n\u00eb informacionin e nivelit t\u00eb tret\u00eb. Ajo sheh se adresa IP e destinacionit 30.1.1.10 i p\u00ebrket s\u00eb nj\u00ebjt\u00ebs rrjet si porta 0\/1 e rrug\u00ebs, shton n\u00eb kad\u00ebr adres\u00ebn MAC t\u00eb burimit dhe adres\u00ebn MAC t\u00eb pajisjes destinacion dhe d\u00ebrgon kad\u00ebr n\u00eb server. <\/p>\n

\"Trajnimi
\n
\nSi\u00e7 e thash\u00eb m\u00eb par\u00eb, procesi i ngjash\u00ebm p\u00ebrs\u00ebritet n\u00eb drejtimin e kund\u00ebrt, pra ndodh faza e dyt\u00eb e dor\u00ebzimit, ku serveri d\u00ebrgon p\u00ebrs\u00ebri nj\u00eb mesazh SYN ACK. Para k\u00ebsaj, ai heq t\u00eb gjith\u00eb informacionin e tep\u00ebrt dhe l\u00eb vet\u00ebm paket\u00ebn SYN.<\/p>\n

\"Trajnimi
\n
\nPasi merr k\u00ebt\u00eb paket\u00eb, rruga e dyt\u00eb shqyrton informacionin e pranuar, e plot\u00ebson at\u00eb dhe e d\u00ebrgon m\u00eb tej. <\/p>\n

Pra, n\u00eb m\u00ebsimet e m\u00ebparshme ne studiuam si funksionon switch-i, nd\u00ebrsa tani mor\u00ebm nj\u00eb njohuri se si funksionojn\u00eb rrug\u00ebt. Le t\u00eb p\u00ebrgjigjemi n\u00eb pyetjen, \u00e7far\u00eb p\u00ebrfaq\u00ebson ristrukturimi n\u00eb nj\u00eb sens global. Supozoni se keni hasur nj\u00eb shenj\u00eb rrugore t\u00eb till\u00eb, e vendosur n\u00eb nj\u00eb kryq\u00ebzim me qarkullim rrethor. Ju shihni se deg\u00ebn e par\u00eb e \u00e7on n\u00eb baz\u00ebn ajrore t\u00eb Mbret\u00ebris\u00eb s\u00eb Bashkuar n\u00eb Fairfax, e dyta n\u00eb aeroport, e treta n\u00eb jug. N\u00ebse zgjidhni daljen e kat\u00ebrt, do t\u00eb arrini n\u00eb nj\u00eb pik\u00eb pa dalje, nd\u00ebrsa p\u00ebrmes t\u00eb pest\u00ebs mund t\u00eb kaloni n\u00eb qend\u00ebr t\u00eb qytetit drejt kalas\u00eb Breksbi. <\/p>\n

\"Trajnimi
\n
\nN\u00eb thelb, ristrukturimi \u00ebsht\u00eb ajo q\u00eb b\u00ebn rrug\u00ebn t\u00eb marr\u00eb vendime se ku t\u00eb d\u00ebrgoj\u00eb trafik. N\u00eb k\u00ebt\u00eb rast, ju si vozit\u00ebs duhet t\u00eb merrni nj\u00eb vendim se cil\u00ebn dalje nga kryq\u00ebzimi duhet t\u00eb zgjidhni. N\u00eb rrjete, rrug\u00ebt duhet t\u00eb marrin vendime se ku t\u00eb d\u00ebrgojn\u00eb paketa ose kadra. Duhet t\u00eb kuptoni se ristrukturimi lejon krijimin e tabelave mbi baz\u00ebn e t\u00eb cilave rrug\u00ebt marrin k\u00ebto vendime. <\/p>\n

Si\u00e7 e thash\u00eb, ekziston ristrukturimi statik dhe dinamik. Le t\u00eb shqyrtojm\u00eb ristrukturimin statik, p\u00ebr k\u00ebt\u00eb do t\u00eb vizatoj 3 pajisje t\u00eb lidhura me nj\u00ebra-tjetr\u00ebn, ku pajisja e par\u00eb dhe e tret\u00eb jan\u00eb t\u00eb lidhura me rrjete. Supozoni se nj\u00eb rrjet 10.1.1.0 d\u00ebshiron t\u00eb lidhet me rrjetin 40.1.1.0, nd\u00ebrsa midis rrug\u00ebve ndodhen rrjetet 20.1.1.0 dhe 30.1.1.0.<\/p>\n

\"Trajnimi
\n
\nN\u00eb k\u00ebt\u00eb rast, portet e routers duhet t\u00eb p\u00ebrkasin n\u00eb subnet-e t\u00eb ndryshme. Routeri 1 n\u00ebnkupton vet\u00ebm rrjetin 10. dhe 20. dhe nuk di asgj\u00eb p\u00ebr rrjetet e tjera. Routeri 2 di vet\u00ebm p\u00ebr rrjetet 20. dhe 30., sepse ato jan\u00eb t\u00eb lidhura me t\u00eb, nd\u00ebrsa routeri 3 di vet\u00ebm p\u00ebr rrjetet 30. dhe 40. N\u00ebse rrjeti 10. d\u00ebshiron t\u00eb lidh\u00eb me rrjetin 40., un\u00eb duhet t'i tregoj routerit 1 p\u00ebr rrjetin 30. dhe se n\u00ebse ai d\u00ebshiron t\u00eb d\u00ebrgoj\u00eb nj\u00eb frame t\u00eb rrjetit 40., duhet t\u00eb p\u00ebrdor\u00eb nd\u00ebrfaqen p\u00ebr rrjetin 20. dhe ta d\u00ebrgoj\u00eb frame-n n\u00ebp\u00ebrmjet k\u00ebtij rrjeti 20.<\/p>\n

Routerit t\u00eb dyt\u00eb un\u00eb duhet t'i caktoj 2 rrug\u00eb: n\u00ebse ai d\u00ebshiron t\u00eb d\u00ebrgoj\u00eb nj\u00eb paket\u00eb nga rrjeti 40. n\u00eb rrjetin 10., at\u00ebher\u00eb duhet t\u00eb p\u00ebrdor\u00eb portin e rrjetit 20., dhe p\u00ebr d\u00ebrgimin e paket\u00ebs nga rrjeti 10. n\u00eb rrjetin 40. \u2013 portin e rrjetit 30. Nj\u00ebsoj, un\u00eb duhet ta furnizoj routerin 3 me informacion p\u00ebr rrjetet 10. dhe 20.<\/p>\n

N\u00ebse keni rrjete t\u00eb vogla, at\u00ebher\u00eb konfigurimi i ruterizimit statik \u00ebsht\u00eb shum\u00eb i leht\u00eb. Megjithat\u00eb, me rritjen e rrjetit, shqet\u00ebsimet me ruterizimin statik rriten gjithashtu. Imagjinoni se jeni krijuar nj\u00eb lidhje t\u00eb re q\u00eb lidh drejtp\u00ebrdrejt router\u00ebt e par\u00eb dhe t\u00eb tret\u00eb. N\u00eb k\u00ebt\u00eb rast, protokolli i ruterizimit dinamik do t\u00eb p\u00ebrdit\u00ebsoj\u00eb automatikisht tabel\u00ebn e ruterizimit t\u00eb routerit 1, duke treguar: \u201cn\u00ebse ju duhet t\u00eb lidheni me routerin 3, p\u00ebrdorni rrug\u00eb t\u00eb drejtp\u00ebrdrejt\u00eb\u201d!<\/p>\n

\"Trajnimi
\n
\nEkzistojn\u00eb dy lloje protokollesh ruterizimi: protokolli i gateway t\u00eb brendsh\u00ebm IGP dhe protokolli i gateway t\u00eb jasht\u00ebm EGP. Protokolli i par\u00eb funksionon me nj\u00eb sistem t\u00eb ve\u00e7ant\u00eb, t\u00eb vet\u00eb-k\u00ebrcyesh\u00ebm, t\u00eb njohur si domene ruterizimi. Imagjinoni se keni nj\u00eb organizat\u00eb t\u00eb vog\u00ebl, e cila ka vet\u00ebm 5 routera. N\u00ebse flasim vet\u00ebm p\u00ebr lidhjet midis k\u00ebtyre router\u00ebve, n\u00ebnkuptojm\u00eb IGP, nd\u00ebrsa n\u00ebse p\u00ebrdorni rrjetin tuaj p\u00ebr t\u00eb lidhur me internetin, si\u00e7 b\u00ebjn\u00eb ofruesit e sh\u00ebrbimeve ISP, at\u00ebher\u00eb p\u00ebrdorni EGP. <\/p>\n

\"Trajnimi
\n
\nIGP p\u00ebrdor 3 protokolle t\u00eb njohura: RIP, OSPF dhe EIGRP. Kurrikula CCNA p\u00ebrmend vet\u00ebm dy protokollet e fundit, sepse RIP \u00ebsht\u00eb i vjetruar. Ky \u00ebsht\u00eb protokolli m\u00eb i thjesht\u00eb i ruterizimit, i cili ende p\u00ebrdoret n\u00eb disa raste, megjithat\u00eb nuk ofron sigurin\u00eb e nevojshme rrjet\u00ebsore. Kjo \u00ebsht\u00eb nj\u00eb nga arsyet pse Cisco e hoqi RIP nga plani m\u00ebsimor. Megjithat\u00eb, un\u00eb do t'ju flas p\u00ebr t\u00eb, sepse studimi i tij ndihmon n\u00eb kuptimin e bazave t\u00eb ruterizimit. <\/p>\n

\"Trajnimi
\n
\nKlasifikimi i protokolleve EGP p\u00ebrdor dy protokolle: BGP dhe protokollin e vet\u00eb EGP. Gjat\u00eb studimit t\u00eb kursit CCNA ne do t\u00eb shqyrtojm\u00eb vet\u00ebm BGP, OSPF dhe EIGRP. Diskutimi rreth RIP mund t\u00eb merret si informacion shtes\u00eb, i cili do t\u00eb reflektohet n\u00eb nj\u00eb nga video-m\u00ebsimet.
\nEkzistojn\u00eb edhe 2 tipa protokollesh rute: protokolle t\u00eb distanc\u00ebs s\u00eb vektorit Distance Vector dhe protokolle t\u00eb gjendjes s\u00eb kanalit Link State. <\/p>\n

\"Trajnimi
\n
\nProtokolli i par\u00eb shqyrton vektor\u00ebt e distanc\u00ebs dhe drejtimit. P\u00ebr shembull, mund t\u00eb vendos nj\u00eb lidhje direkt mes router R1 dhe R4, ose mund ta realizoj lidhjen p\u00ebrmes R1-R2-R3-R4. Kur flasim p\u00ebr protokollet e ruterizimit q\u00eb p\u00ebrdorin metod\u00ebn e vektorit t\u00eb distanc\u00ebs, n\u00eb k\u00ebt\u00eb rast lidhja gjithmon\u00eb do t\u00eb realizohet p\u00ebrmes rrug\u00ebs m\u00eb t\u00eb shkurt\u00ebr. Nuk ka r\u00ebnd\u00ebsi se lidhja do t\u00eb ket\u00eb shpejt\u00ebsi minimale. N\u00eb rastin ton\u00eb, kjo \u00ebsht\u00eb 128 kbit\/s, q\u00eb \u00ebsht\u00eb shum\u00eb m\u00eb e ngadalt\u00eb se lidhja p\u00ebrmes rrug\u00ebs R1-R2-R3-R4, ku shpejt\u00ebsia arrin n\u00eb 100 mbit\/s. <\/p>\n

Le t\u00eb shqyrtojm\u00eb protokollin e distanc\u00ebs s\u00eb vektorit RIP. Un\u00eb do t\u00eb vizatoja p\u00ebrpara router R1 rrjetin 10., dhe pas router R4 \u2013 rrjetin 40. Supozojm\u00eb se n\u00eb k\u00ebto rrjete ndodhen shum\u00eb kompjuter\u00eb. N\u00ebse d\u00ebshiroj t\u00eb realizoj lidhjen midis rrjetit 10. R1 dhe rrjetit 40. R4, do t\u00eb em\u00ebroj R1 nj\u00eb ruterizim statik q\u00eb thot\u00eb: \"n\u00ebse duhet t\u00eb lidhesh me rrjetin 40., p\u00ebrdor lidhjen direkte me router R4\". Nj\u00ebkoh\u00ebsisht, n\u00eb t\u00eb kat\u00ebr routerat un\u00eb duhet t\u00eb konfiguroj manualisht RIP. K\u00ebshtu, tabela e ruterizimit t\u00eb R1 do t\u00eb informoj\u00eb automatikisht se n\u00ebse rrjeti 10. d\u00ebshiron t\u00eb lidh\u00eb me rrjetin 40., duhet t\u00eb p\u00ebrdoret lidhja direkte R1-R4. Edhe n\u00ebse nj\u00eb rrug\u00eb alternative del t\u00eb jet\u00eb m\u00eb e shpejt\u00eb, protokolli Distance Vector gjithmon\u00eb do t\u00eb zgjedh\u00eb rrug\u00ebn m\u00eb t\u00eb shkurt\u00ebr me distanc\u00ebn m\u00eb t\u00eb vog\u00ebl. <\/p>\n

OSPF \u00ebsht\u00eb nj\u00eb protokoll ruterizimi t\u00eb gjendjes s\u00eb kanalit, i cili gjithmon\u00eb shqyrton gjendjen e segmenteve t\u00eb rrjetit. N\u00eb k\u00ebt\u00eb rast, ai vler\u00ebson shpejt\u00ebsin\u00eb e kanaleve dhe, n\u00ebse sheh se shpejt\u00ebsia e transmetimit t\u00eb trafikut p\u00ebrmes kanalit R1-R4 \u00ebsht\u00eb shum\u00eb e ul\u00ebt, zgjedh rrug\u00ebn me shpejt\u00ebsi m\u00eb t\u00eb lart\u00eb R1-R2-R3-R4, edhe n\u00ebse gjat\u00ebsa e saj \u00ebsht\u00eb m\u00eb e madhe se ajo e rrug\u00ebs m\u00eb t\u00eb shkurt\u00ebr. Pra, n\u00ebse un\u00eb e konfiguroj OSPF n\u00eb t\u00eb gjith\u00eb routerat, kur p\u00ebrpiqem t\u00eb lidh rrjetin 40. me rrjetin 10., trafiku do t\u00eb d\u00ebrgohet p\u00ebrmes rrug\u00ebs R1-R2-R3-R4. Pra, RIP \u00ebsht\u00eb nj\u00eb protokoll i distanc\u00ebs s\u00eb vektorit, nd\u00ebrsa OSPF \u00ebsht\u00eb nj\u00eb protokoll ruterizimi t\u00eb gjendjes s\u00eb kanalit.<\/p>\n

Ekziston edhe nj\u00eb protokoll \u2013 EIGRP, nj\u00eb protokoll rrug\u00ebzimi pronar i Cisco. Kur flasim p\u00ebr pajisje rrjetesh nga prodhues t\u00eb tjer\u00eb, p\u00ebr shembull, Juniper, ato nuk e mb\u00ebshtesin EIGRP. Ky \u00ebsht\u00eb nj\u00eb protokoll rrug\u00ebzimi i shk\u00eblqyer, shum\u00eb m\u00eb efektiv se RIP dhe OSPF, por mund t\u00eb p\u00ebrdoret vet\u00ebm n\u00eb rrjete t\u00eb bazuara n\u00eb pajisje t\u00eb prodhuara nga Cisco. m\u00eb von\u00eb do t\u00eb flas m\u00eb shum\u00eb p\u00ebr at\u00eb se \u00e7far\u00eb e b\u00ebn k\u00ebt\u00eb protokoll kaq t\u00eb shk\u00eblqyer. P\u00ebr momentin, do t\u00eb v\u00eb n\u00eb dukje se EIGRP kombinon karakteristikat e protokolleve t\u00eb distanc\u00ebs nj\u00ebj\u00ebsore dhe protokolleve t\u00eb gjendjes s\u00eb kanalit, duke p\u00ebrfaq\u00ebsuar nj\u00eb protokoll hibrid. <\/p>\n

N\u00eb videon e ardhshme ne do t\u00eb afrojm\u00eb nga af\u00ebr me shqyrtimin e router\u00ebve Cisco, do t'ju jap disa informacione mbi sistemin operativ Cisco IOS, i cili \u00ebsht\u00eb i destinuar p\u00ebr switch-e dhe router-e. Shpresoj q\u00eb n\u00eb m\u00ebsimet e dit\u00ebs 19 ose 20 t\u00eb fillojm\u00eb studimin e detajuar t\u00eb protokolleve t\u00eb rrug\u00ebzimit, dhe un\u00eb do t\u00eb tregoj se si t\u00eb konfiguroni routerat Cisco me shembuj t\u00eb rrjeteve t\u00eb vogla.<\/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 \u043f\u0440\u0438\u0441\u0442\u0443\u043f\u0438\u043c \u043a \u0438\u0437\u0443\u0447\u0435\u043d\u0438\u044e \u0440\u043e\u0443\u0442\u0435\u0440\u043e\u0432. \u0415\u0441\u043b\u0438 \u0432\u044b \u043f\u0440\u043e\u0448\u043b\u0438 \u043c\u043e\u0439 \u0432\u0438\u0434\u0435\u043e\u043a\u0443\u0440\u0441 \u0441 \u043f\u0435\u0440\u0432\u043e\u0433\u043e \u043f\u043e 17-\u0439 \u0443\u0440\u043e\u043a, \u0442\u043e \u0443\u0436\u0435 \u0438\u0437\u0443\u0447\u0438\u043b\u0438 \u043e\u0441\u043d\u043e\u0432\u044b \u0441\u0432\u0438\u0442\u0447\u0435\u0439. \u0421\u0435\u0439\u0447\u0430\u0441 \u043c\u044b \u043f\u0435\u0440\u0435\u0445\u043e\u0434\u0438\u043c \u043a \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0435\u043c\u0443 \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0443 \u2013 \u0440\u043e\u0443\u0442\u0435\u0440\u0443. \u041a\u0430\u043a \u0432\u044b \u0437\u043d\u0430\u0435\u0442\u0435 \u0438\u0437 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u0433\u043e \u0432\u0438\u0434\u0435\u0443\u0440\u043e\u043a\u0430, \u043e\u0434\u043d\u0430 \u0438\u0437 \u0442\u0435\u043c \u043a\u0443\u0440\u0441\u0430 CCNA \u0442\u0430\u043a \u0438 \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u2013 Cisco Switching & Routing. \u0412 \u044d\u0442\u043e\u0439 \u0441\u0435\u0440\u0438\u0438 \u043c\u044b \u043d\u0435 \u0441\u0442\u0430\u043d\u0435\u043c \u0438\u0437\u0443\u0447\u0430\u0442\u044c […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":27956,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37271","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 18. Thelb\u00ebsit\u00eb e Routing-ut | ProHoster","description":"Sot do t\u00eb fillojm\u00eb studimin e routerave. N\u00ebse keni ndjekur kursin tim video nga ndarja e par\u00eb deri n\u00eb at\u00eb t\u00eb 17-t\u00eb, at\u00ebher\u00eb tashm\u00eb keni studiuar bazat e switch-eve. Tani po kalojm\u00eb n\u00eb pajisjen tjet\u00ebr \u2013 routerin.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-18-osnovy-marshrutizatsii","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 18. \u041e\u0441\u043d\u043e\u0432\u044b \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438 | ProHoster","og:description":"\u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u043f\u0440\u0438\u0441\u0442\u0443\u043f\u0438\u043c \u043a \u0438\u0437\u0443\u0447\u0435\u043d\u0438\u044e \u0440\u043e\u0443\u0442\u0435\u0440\u043e\u0432. \u0415\u0441\u043b\u0438 \u0432\u044b \u043f\u0440\u043e\u0448\u043b\u0438 \u043c\u043e\u0439 \u0432\u0438\u0434\u0435\u043e\u043a\u0443\u0440\u0441 \u0441 \u043f\u0435\u0440\u0432\u043e\u0433\u043e \u043f\u043e 17-\u0439 \u0443\u0440\u043e\u043a, \u0442\u043e \u0443\u0436\u0435 \u0438\u0437\u0443\u0447\u0438\u043b\u0438 \u043e\u0441\u043d\u043e\u0432\u044b \u0441\u0432\u0438\u0442\u0447\u0435\u0439. \u0421\u0435\u0439\u0447\u0430\u0441 \u043c\u044b \u043f\u0435\u0440\u0435\u0445\u043e\u0434\u0438\u043c \u043a \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0435\u043c\u0443 \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0443 \u2013 \u0440\u043e\u0443\u0442\u0435\u0440\u0443.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/trening-cisco-200-125-ccna-v3-0-den-18-osnovy-marshrutizatsii","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:16:41+00:00","article:modified_time":"2019-10-31T19:16:41+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37271","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 17:03:35","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:30:00","updated":"2026-01-23 17:03:35","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\/37271","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=37271"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/37271\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/27956"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=37271"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=37271"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=37271"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}