{"id":33142,"date":"2019-10-31T21:50:58","date_gmt":"2019-10-31T18:50:58","guid":{"rendered":"https:\/\/prohoster.info\/blog\/printsipy-raboty-protokola-pim\/"},"modified":"2019-10-31T21:50:58","modified_gmt":"2019-10-31T18:50:58","slug":"printsipy-raboty-protokola-pim","status":"publish","type":"post","link":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/printsipy-raboty-protokola-pim","title":{"rendered":"PIM protokola darb\u012bbas principi","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>PIM protokols ir protokolu kopums multikasta p\u0101rs\u016bt\u012b\u0161anai t\u012bkl\u0101 starp mar\u0161rut\u0113t\u0101jiem. Kaimi\u0146attiec\u012bbas tiek veidotas l\u012bdz\u012bgi k\u0101 dinamiskiem mar\u0161rut\u0113\u0161anas protokoliem. PIMv2 katras 30 sekundes s\u016bta Hello zi\u0146ojumus uz rezerv\u0113to multikasta adresi 224.0.0.13 (All-PIM-Routers). Zi\u0146ojums satur Hold Timers - parasti vien\u0101ds ar 3.5*Hello Timer, tas ir, 105 sekundes p\u0113c noklus\u0113juma.<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/AqjQmPR.jpg\"><img decoding=\"async\" alt=\"PIM protokola darb\u012bbas principi\" src=\"\/wp-content\/uploads\/2019\/05\/f2e0c7dbdb8d7640671440289fbcd91f.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n PIM izmanto divus galvenos darb\u012bbas re\u017e\u012bmus \u2014 Dense un Sparse mode. S\u0101ksim ar Dense mode. <noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\n<b>Avota balst\u012btas sadales koki.<\/b><br \/>\nDense-mode re\u017e\u012bms ir piem\u0113rots lieto\u0161anai, ja ir liels klientu skaits da\u017e\u0101d\u0101s multikasta grup\u0101s. Kad mar\u0161rut\u0113t\u0101js sa\u0146em multikasta trafiku, vispirms tas p\u0101rbauda to pret RPF noteikumu. RPF \u2014 \u0161is noteikums tiek izmantots, lai p\u0101rbaud\u012btu multikasta avotu pret unicast mar\u0161rutiz\u0101cijas tabulu. Trafikam ir j\u0101ierodas taj\u0101 interfeis\u0101, kur\u0101 sl\u0113pjas \u0161is host saska\u0146\u0101 ar unicast mar\u0161rutiz\u0101cijas tabulu. \u0160is meh\u0101nisms nov\u0113r\u0161 aplamu ap\u013cainu s\u016bt\u012b\u0161anu multikast\u0101.<br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/RE54lnP.png\"><img decoding=\"async\" alt=\"PIM protokola darb\u012bbas principi\" src=\"\/wp-content\/uploads\/2019\/05\/4d855ea59c6329c7e727cc70a79367b2.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nR3 no multikasta zi\u0146ojuma uzzina multikasta avotu (Source IP) un p\u0101rbauda divus pl\u016bsmus no R1 un R2 p\u0113c savas unicast mar\u0161rutiz\u0101cijas tabulas. Pl\u016bsma no t\u0101 interfeisa, uz kuru nor\u0101da tabula (R1 uz R3), tiks nodota t\u0101l\u0101k, bet pl\u016bsma no R2 tiks noraid\u012bta, jo, lai sasniegtu multikasta avotu, j\u0101nos\u016bta paketes pa S0\/1.<br \/>\nJaut\u0101jums: kas notiek, ja jums ir divi ekvivalentu mar\u0161rutu ar vien\u0101du metrikas? \u0160aj\u0101 gad\u012bjum\u0101 mar\u0161rut\u0113t\u0101js izv\u0113l\u0113sies p\u0113c next-hop attiec\u012bb\u0101 uz \u0161iem mar\u0161rutiem. Kam ir augst\u0101ks IP adrese, tas uzvar. Ja nepiecie\u0161ams main\u012bt \u0161o uzved\u012bbu, var izmantot ECMP. Las\u012bt vair\u0101k. <noindex><a rel=\"nofollow\" href=\"https:\/\/drive.google.com\/file\/d\/1yiam4-OwlDoXrfdfdienMN_nQaOJGi29\/view?usp=sharing\">\u0161eit<\/a><\/noindex>.<br \/>\nP p\u0113c RPF noteikuma p\u0101rbaudes mar\u0161rut\u0113t\u0101js nos\u016bta multikasta paketi visiem saviem PIM kaimi\u0146iem, iz\u0146emot to, no kura tika sa\u0146emta \u0161\u012b pakete. P\u0101r\u0113jie PIM mar\u0161rut\u0113t\u0101ji atk\u0101rto \u0161o procesu. Ce\u013c\u0161, pa kuru multikasta pakete virz\u012bj\u0101s no avota l\u012bdz gal\u012bgajiem sa\u0146\u0113m\u0113jiem, veido koku, kas saucas \u2014 avota balst\u012bta sadales koks, \u012bs\u0101k\u0101 ce\u013ca koks (SPT), avota koks. Tr\u012bs da\u017e\u0101di nosaukumi, izv\u0113lieties jebkuru.<br \/>\nK\u0101 risin\u0101t jaut\u0101jumu, kad da\u017ei mar\u0161rut\u0113t\u0101ji nesa\u0146em k\u0101du multikasta pl\u016bsmu un nevienam to nos\u016bt\u012bt nav, bet augst\u0101ks mar\u0161rut\u0113t\u0101js to s\u016bta? Tam ir izstr\u0101d\u0101ts Prune meh\u0101nisms. <br \/>\n<b>Prune zi\u0146ojums.<\/b><br \/>\nPiem\u0113ram, R2 turpin\u0101s s\u016bt\u012bt R3 multicast, lai gan R3 saska\u0146\u0101 ar RPF noteikumu to noraida. K\u0101p\u0113c slodzes kan\u0101ls? R3 nos\u016bta PIM Prune zi\u0146ojumu, un R2, sa\u0146emot \u0161o zi\u0146ojumu, izdz\u0113s\u012bs S0\/1 interfeisu no izn\u0101kuma interfeisu saraksta attiec\u012bgajam pl\u016bsmam, interfeisu sarakstu, no kuriem j\u0101nos\u016bta \u0161is saturs. <\/p>\n<blockquote><p>\u0160eit ir form\u0101l\u0101ka PIM Prune zi\u0146ojuma defin\u012bcija:<br \/>\nPIM Prune zi\u0146ojums tiek nos\u016bt\u012bts no viena mar\u0161rut\u0113t\u0101ja uz otro mar\u0161rut\u0113t\u0101ju, lai liktu otrajam mar\u0161rut\u0113t\u0101jam iz\u0146emt saiti, uz kuras tiek sa\u0146emts Prune, no konkr\u0113t\u0101 (S,G) SPT.<\/p><\/blockquote>\n<p>\nP\u0113c Prune zi\u0146ojuma sa\u0146em\u0161anas R2 iestata Prune taimeri uz 3 min\u016bt\u0113m. P\u0113c trim min\u016bt\u0113m tas s\u0101ks atkal s\u016bt\u012bt satiksmi, l\u012bdz sa\u0146ems n\u0101kamo Prune zi\u0146ojumu. Tas ir PIMv1.<br \/>\nSavuk\u0101rt PIMv2 ir pievienots State Refresh taimeris (noklus\u0113ti 60 sekundes). Tikl\u012bdz tiek nos\u016bt\u012bts Prune zi\u0146ojums no R3, \u0161is taimeris tiek aktiviz\u0113ts uz R3. Kad \u0161is taimeris beidzas, R3 nos\u016bt\u012bs State Refresh zi\u0146ojumu, kas resete 3 min\u016b\u0161u Prune taimeri uz R2 attiec\u012bb\u0101 uz grupu. <br \/>\nPrun\u0113\u0161anas zi\u0146ojuma s\u016bt\u012b\u0161anas iemesli:<\/p>\n<ul>\n<li> Kad multicast pakete nav iztur\u0113jusi RPF p\u0101rbaudi.<\/li>\n<li> Ja nav lok\u0101li piesl\u0113gtu klientu, kuri piepras\u012bja multicast grupu (IGMP Join), un nav PIM kaimi\u0146u, kuriem var s\u016bt\u012bt multicast satiksmi (Non-prune Interface).<\/li>\n<\/ul>\n<p>\n<b>Graft zi\u0146ojums.<\/b><br \/>\nIedom\u0101simies, ka R3 nev\u0113l\u0113j\u0101s sa\u0146emt satiksmi no R2, nos\u016bt\u012bja Prune un sa\u0146\u0113ma multicast no R1. Bet p\u0113k\u0161\u0146i sabruka saite starp R1 un R3, un R3 palika bez multicast. Var gaid\u012bt 3 min\u016btes, kam\u0113r uz R2 beigsies Prune taimeris. 3 min\u016btes gaid\u012b\u0161ana ir ilga, t\u0101p\u0113c, lai nesagaid\u012btu, ir nepiecie\u0161ams nos\u016bt\u012bt zi\u0146ojumu, kas t\u016bl\u012bt iz\u0146ems S0\/1 interfeisu uz R2 no pruned st\u0101vok\u013ca. \u0160\u0101ds zi\u0146ojums b\u016bs Graft zi\u0146ojums. P\u0113c Graft zi\u0146ojuma sa\u0146em\u0161anas R2 atbild\u0113s ar Graft-ACK.<br \/>\n<b>Prune Override.<\/b><br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/zfo0Dx5.png\"><img decoding=\"async\" alt=\"PIM protokola darb\u012bbas principi\" src=\"\/wp-content\/uploads\/2019\/05\/72e368905d2e37ba9b9d46101ebcd8ae.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nApskat\u012bsim \u0161o sh\u0113mu. R1 izs\u016bta multicast datu pl\u016bsmu segment\u0101 ar diviem mar\u0161rut\u0113t\u0101jiem. R3 sa\u0146em un izplata trafiku, bet R2 sa\u0146em, ta\u010du tam nav, kam izplat\u012bt trafiku. Tas nos\u016bta Prune zi\u0146ojumu R1 \u0161aj\u0101segment\u0101. R1 ir j\u0101izn\u012bcina Fa0\/0 no saraksta un j\u0101p\u0101rtrauc izplat\u012b\u0161ana \u0161aj\u0101 segment\u0101, bet kas notiks ar R3? R3 atrodas taj\u0101 pa\u0161\u0101 segment\u0101, ar\u012b sa\u0146\u0113ma \u0161o Prune zi\u0146ojumu un saprata visas situ\u0101cijas nopietn\u012bbu. Pirms R1 p\u0101rtrauc izplat\u012b\u0161anu, tas iestata taimeri 3 sekundes un p\u0101rtrauks izplat\u012b\u0161anu p\u0113c 3 sekund\u0113m. 3 sekundes \u2014 tie\u0161i tik ilgi R3 nevajadz\u0113tu zaud\u0113t savu multicast datu pl\u016bsmu. T\u0101d\u0113\u013c R3, cik dr\u012bz vien iesp\u0113jams, nos\u016bta Pim Join zi\u0146ojumu \u0161aj\u0101 grup\u0101, un R1 vairs nedom\u0101 p\u0101rtraukt izplat\u012b\u0161anu. Par Join zi\u0146ojumiem zem\u0101k.<br \/>\n<b>Assert zi\u0146ojums.<\/b><br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/rliwmNF.png\"><img decoding=\"async\" alt=\"PIM protokola darb\u012bbas principi\" src=\"\/wp-content\/uploads\/2019\/05\/f7cc9c247cd26a8f9567b170f9b61bbb.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nIedom\u0101simies \u0161\u0101du situ\u0101ciju: vien\u0101 t\u012bkl\u0101 izplata divi mar\u0161rut\u0113t\u0101ji. Vi\u0146i sa\u0146em vienu un to pa\u0161u pl\u016bsmu no avota un abi to izplata vien\u0101 t\u012bkl\u0101 aiz interfeisa e0. T\u0101d\u0113\u013c vi\u0146iem j\u0101nosaka, kur\u0161 b\u016bs vien\u012bgais izplat\u012bt\u0101js \u0161im t\u012bklam. Tam tiek izmantoti Assert zi\u0146ojumi. Kad R2 un R3 atkl\u0101j, ka notiek multicast datu pl\u016bsmu dubl\u0113\u0161ana, proti, R2 un R3 sa\u0146em multicast datu pl\u016bsmu, kuru pa\u0161i izplata, mar\u0161rut\u0113t\u0101ji saprot, ka kaut kas nav k\u0101rt\u012bb\u0101. \u0160aj\u0101 gad\u012bjum\u0101 mar\u0161rut\u0113t\u0101ji nos\u016bta Assert zi\u0146ojumus, kuros iek\u013cauta Administrat\u012bv\u0101 att\u0101luma un mar\u0161rutu metrikas inform\u0101cija, k\u0101 sasniegt multicast avotu \u2014 10.1.1.10. Uzvar\u0113t\u0101js tiek noteikts t\u0101:<\/p>\n<ol>\n<li>Tam, kam ir zem\u0101kais AD.<\/li>\n<li>Ja AD ir vien\u0101di, tad tam kam ir zem\u0101ka metrika.<\/li>\n<li>Ja \u0161aj\u0101 gad\u012bjum\u0101 ar\u012b ir vien\u0101d\u012bba, tad tam, kam ir augst\u0101ks IP adres\u0113 t\u012bkl\u0101, kur\u0101 tie izplata \u0161o multicast datu pl\u016bsmu.<\/li>\n<\/ol>\n<p>\nUzvar\u0113t\u0101js \u0161aj\u0101 balsojum\u0101 k\u013c\u016bst par Designated Router. DR izv\u0113l\u0113\u0161anai tiek izmantoti ar\u012b Pim Hello. Raksta s\u0101kum\u0101 tika par\u0101d\u012bts PIM Hello zi\u0146ojums, tur var nov\u0113rot DR lauku. Uzvar tas, kam ir augst\u0101k\u0101 IP adrese \u0161aj\u0101 savienojum\u0101.<br \/>\nNoder\u012bga tabula:<br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/Et1kP7h.png\"><img decoding=\"async\" alt=\"PIM protokola darb\u012bbas principi\" src=\"\/wp-content\/uploads\/2019\/05\/d450c9fac2b6d74c5b7414d85910bca4.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n<b>MROUTE Tabula.<\/b><br \/>\nP\u0113c s\u0101kotn\u0113j\u0101s PIM protokola darb\u012bbas apskates mums ir j\u0101izskata, k\u0101 str\u0101d\u0101t ar multicast mar\u0161rut\u0113\u0161anas tabulu. Mroute tabul\u0101 glab\u0101jas inform\u0101cija par to, kuri pl\u016bsmas ir piepras\u012btas no klientiem un kuras pl\u016bsmas pl\u016bst no multicast serveriem. <br \/>\nPiem\u0113ram, sa\u0146emot IGMP Membership Report vai PIM Join uz k\u0101da interfeisa, mar\u0161rut\u0113\u0161anas tabul\u0101 tiek pievienota ieraksts ar tipu ( *, G ):<br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/ufXsgnR.jpg\"><img decoding=\"async\" alt=\"PIM protokola darb\u012bbas principi\" src=\"\/wp-content\/uploads\/2019\/05\/094d96f36512c3b1b8d179044f354ac1.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n\u0160is ieraksts noz\u012bm\u0113, ka ir sa\u0146emts piepras\u012bjums par datpl\u016bsmu no adreses 238.38.38.38. DC karogs noz\u012bm\u0113, ka multicast darbosies bl\u012bv\u0101 re\u017e\u012bm\u0101, un C noz\u012bm\u0113, ka sa\u0146\u0113m\u0113js ir tie\u0161i piesl\u0113gts mar\u0161rut\u0113t\u0101jam, t.i., mar\u0161rut\u0113t\u0101js sa\u0146\u0113ma IGMP Membership Report, un PIM Join.<br \/>\nJa ir ieraksts tipa (S,G), tas noz\u012bm\u0113, ka mums ir multicast pl\u016bsma:<br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/QJCZZwf.jpg\"><img decoding=\"async\" alt=\"PIM protokola darb\u012bbas principi\" src=\"\/wp-content\/uploads\/2019\/05\/56f2e8376a7f89f3fd3082a098ce42e5.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nS lauk\u0101 \u2014 192.168.1.11, mums ir nor\u0101d\u012bta multicast avota IP adrese, tie\u0161i t\u0101 tiks p\u0101rbaud\u012bta RPF noteikum\u0101. Probl\u0113mu gad\u012bjum\u0101 vispirms j\u0101p\u0101rbauda unik\u0101lo tabula saist\u012bb\u0101 ar avota mar\u0161rutu. Ien\u0101ko\u0161\u0101 saskarne nor\u0101da interfeisu, caur kuru n\u0101k multicast. Unik\u0101lo mar\u0161rutu tabul\u0101 mar\u0161ruts uz avotu j\u0101nor\u0101da uz interfeisu, kas nor\u0101d\u012bts \u0161eit. Izv\u0113rsto interfeisu nor\u0101da, uz kurieni tiks novirz\u012bts multicast. Ja tas ir tuk\u0161s, tas noz\u012bm\u0113, ka mar\u0161rut\u0113t\u0101jam nebija piepras\u012bjumu par \u0161o datpl\u016bsmu. S\u012bk\u0101ku inform\u0101ciju par visiem karogiem var atrast. <noindex><a rel=\"nofollow\" href=\"https:\/\/drive.google.com\/file\/d\/1ArBLFJdyN8tCangB5GL2JaS47FEZaad-\/view?usp=sharing\">\u0161eit<\/a><\/noindex>.<br \/>\n<b>PIM Sparse-mode.<\/b><br \/>\nSparse-mode strat\u0113\u0123ija ir pret\u0113ja bl\u012bvajam re\u017e\u012bmam. Kad Sparse-mode sa\u0146em multicast datpl\u016bsmu, tas s\u016bt\u012bs datpl\u016bsmu tikai caur tiem interfeisiem, kur ir biju\u0161i piepras\u012bjumi par \u0161o pl\u016bsmu, piem\u0113ram, PIM Join vai IGMP Report zi\u0146ojumi ar piepras\u012bjumu par \u0161o datpl\u016bsmu.<br \/>\nL\u012bdz\u012bgi elementi SM un DM:<\/p>\n<ul>\n<li> Ka neighbors attiec\u012bbas veidojas t\u0101pat k\u0101 PIM DM.<\/li>\n<li> Darbojas RPF noteikums.<\/li>\n<li> DR izv\u0113le ir l\u012bdz\u012bga.<\/li>\n<li> Prune Overrides meh\u0101nisms un assert zi\u0146ojumi ir l\u012bdz\u012bgi.<\/li>\n<\/ul>\n<p>\nLai kontrol\u0113tu, kam, kur un k\u0101da multicast datpl\u016bsma ir nepiecie\u0161ama t\u012bkl\u0101, ir nepiecie\u0161ams kop\u012bgs inform\u0101cijas centrs. \u0160\u0101ds centrs b\u016bs Rendezvous Point (RP). Visi, kas v\u0113las k\u0101du multicast datpl\u016bsmu vai kas s\u0101k sa\u0146emt multicast datpl\u016bsmu no avota, to nos\u016bta uz RP.<br \/>\nKad RP sa\u0146ems multicast datpl\u016bsmu, tas to nos\u016bt\u012bs tiem mar\u0161rut\u0113t\u0101jiem, kuri iepriek\u0161 bija piepras\u012bju\u0161i \u0161o datpl\u016bsmu. <br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/5AErtbS.jpg\"><img decoding=\"async\" alt=\"PIM protokola darb\u012bbas principi\" src=\"\/wp-content\/uploads\/2019\/05\/35646434f8b80a8a05253111864de2da.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nIedom\u0101simies \u0161\u0101du topolo\u0123iju, kur RP ir R3. Tikl\u012bdz R1 sa\u0146ems datpl\u016bsmu no S1, tas iesai\u0146os \u0161o multicast paketi unik\u0101lo PIM Register zi\u0146ojum\u0101 un nos\u016bt\u012bs to uz RP. No kurienes vi\u0146\u0161 zina, kur\u0161 ir RP? \u0160aj\u0101 gad\u012bjum\u0101 tas ir konfigur\u0113ts statiski, bet par dinamikas RP konfigur\u0101ciju run\u0101sim v\u0113l\u0101k. <\/p>\n<blockquote><p>ip pim rp-address 3.3.3.3<\/p><\/blockquote>\n<p>\nRP p\u0101rbaud\u012bs, vai ir bijusi inform\u0101cija no k\u0101da, kas v\u0113l\u0113tos sa\u0146emt \u0161o trafiku? Pie\u0146emsim, ka nav bijis. Tad RP nos\u016bt\u012bs R1 zi\u0146ojumu PIM Register-Stop, kas noz\u012bm\u0113 \u2014 neviens negrib \u0161o multicast, re\u0123istr\u0101cija noraid\u012bta. R1 nes\u016bt\u012bs multicast. Bet host-izcelsmes multicast b\u016bs j\u0101nos\u016bta, t\u0101p\u0113c R1 p\u0113c Register-Stop sa\u0146em\u0161anas uzs\u0101ks Register-Suppression timer, kas ir 60 sekundes. 5 sekundes pirms \u0161\u012b taimeris izbeig\u0161an\u0101s, R1 nos\u016bt\u012bs tuk\u0161u Register zi\u0146ojumu ar Null-Register bit (t.i., bez iepakota multicast paketa) uz RP. RP savuk\u0101rt r\u012bkosies t\u0101:<\/p>\n<ul>\n<li> Ja sa\u0146\u0113m\u0113ju nebija, tad tas atbild\u0113s ar Register-Stop zi\u0146ojumu.<\/li>\n<li> Ja sa\u0146\u0113m\u0113ji ir par\u0101d\u012bju\u0161ies, tad tas uz to nek\u0101di neatbild\u0113s. R1, nesa\u0146emot atteikumu par savu re\u0123istr\u0101ciju 5 sekun\u017eu laik\u0101, priec\u0101sies un nos\u016bt\u012bs Register zi\u0146ojumu ar iepakotu multicast uz RP.<\/li>\n<\/ul>\n<p>\nK\u0101 multicast non\u0101k l\u012bdz RP, \u0161\u0137iet, m\u0113s saprat\u0101m, tagad m\u0113\u0123in\u0101sim atbild\u0113t uz jaut\u0101jumu, k\u0101 RP nog\u0101d\u0101 trafiku l\u012bdz sa\u0146\u0113m\u0113jiem. \u0160eit ir nepiecie\u0161ams ieviest jaunu j\u0113dzienu \u2014 root-path tree (RPT). RPT \u2014 tas ir koks ar sakni RP, kas aug virzien\u0101 uz sa\u0146\u0113m\u0113jiem, sazarojoties katr\u0101 PIM-SM mar\u0161rut\u0113t\u0101j\u0101. RP to izveido, sa\u0146emot PIM Join zi\u0146ojumus un pievienojot nozares koks. Un t\u0101 dara katrs apak\u0161\u0113jais mar\u0161rut\u0113t\u0101js. Kop\u0113jais noteikums izskat\u0101s \u0161\u0101di:<\/p>\n<ul>\n<li> Kad PIM-SM mar\u0161rut\u0113t\u0101js sa\u0146em PIM Join zi\u0146ojumu k\u0101d\u0101 saskarn\u0113, iz\u0146emot to saskarni, aiz kuras sl\u0113pjas RP, tas pievieno jaunus zaru kokam.<\/li>\n<li> Ar\u012b zars tiek pievienots, kad PIM-SM mar\u0161rut\u0113t\u0101js sa\u0146em IGMP Membership Report no tie\u0161i piesl\u0113gta hosta. <\/li>\n<\/ul>\n<p>\nIedom\u0101simies, ka mums ir multicast klients mar\u0161rut\u0113t\u0101j\u0101 R5 grupai 228.8.8.8. Tikl\u012bdz R5 sa\u0146ems IGMP Membership Report no hosta, R5 nos\u016bt\u012bs PIM Join virzien\u0101 uz RP un pats pievienos zaru koks saskarnei, kas skat\u0101s uz hostu. P\u0113c tam R4 sa\u0146em PIM Join no R5, pievieno zaru koks saskarnei Gi0\/1 un nos\u016bt\u012bs PIM Join virzien\u0101 uz RP. Visbeidzot, RP (R3) sa\u0146em PIM Join un pievieno Gi0\/0 koks. T\u0101d\u0113j\u0101di izveidojas sa\u0146\u0113m\u0113ja multicast re\u0123istr\u0101cija. Mums tiek veidots koks ar sakni R3-Gi0\/0 \u2192 R4-Gi0\/1 \u2192 R5-Gi0\/0.<br \/>\nP\u0113c tam tiks nos\u016bt\u012bts PIM Join uz R1, un R1 s\u0101ks s\u016bt\u012bt multicast trafiku. Svar\u012bgi atz\u012bm\u0113t, ka, ja hosts ir piepras\u012bjis trafiku pirms multicast p\u0101rraides uzs\u0101k\u0161anas, RP nes\u016bt\u012bs PIM Join un visp\u0101r nes\u016bt\u012bs neko uz R1.<br \/>\nJa gad\u012bjum\u0101, kam\u0113r notiek multicast nos\u016bt\u012b\u0161ana, hosts p\u0101rtrauks v\u0113l\u0113ties to sa\u0146emt, tikl\u012bdz RP sa\u0146ems PIM Prune interfeis\u0101 Gi0\/0, tas t\u016bl\u012bt nos\u016bt\u012bs PIM Register-Stop tie\u0161i uz R1 un p\u0113c tam PIM Prune zi\u0146ojumu caur interfeisu Gi0\/1. PIM Register-stop tiek nos\u016bt\u012bts unikast\u0101 uz adresi, no kuras tika sa\u0146emts PIM Register.<br \/>\nK\u0101 jau iepriek\u0161 nor\u0101d\u012bj\u0101m, tikl\u012bdz mar\u0161rut\u0113t\u0101js nos\u016bta PIM Join citam, piem\u0113ram, R5 uz R4, tad R4 tiek pievienota ieraksts:<br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/msZjbr8.jpg\"><img decoding=\"async\" alt=\"PIM protokola darb\u012bbas principi\" src=\"\/wp-content\/uploads\/2019\/05\/d1d621bee37e4b912a672690c581617a.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nUn tiek uzs\u0101kts taimeris, ka R5 \u0161im taimerim past\u0101v\u012bgi j\u0101s\u016bta PIM Join zi\u0146ojumi, cit\u0101di R4 izsl\u0113gs no outgoing list. R5 s\u016bt\u012bs PIM Join zi\u0146ojumus ik p\u0113c 60 sekund\u0113m.<br \/>\n<b>Shortest-Path Tree p\u0101rsl\u0113g\u0161ana.<\/b><br \/>\nM\u0113s pievienosim interfeisu starp R1 un R5, skat\u012bsim, k\u0101 pl\u016bd\u012bs trafiks \u0161\u0101d\u0101 topolo\u0123ij\u0101. <br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/wLKEyyg.jpg\"><img decoding=\"async\" alt=\"PIM protokola darb\u012bbas principi\" src=\"\/wp-content\/uploads\/2019\/05\/4b15057a1d30f3b2d6246b8f3b6263eb.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nPie\u0146emot, ka trafiks tika s\u016bt\u012bts un sa\u0146emts p\u0113c vec\u0101s sh\u0113mas R1-R2-R3-R4-R5, un tagad m\u0113s piesl\u0113dzam un konfigur\u0113jam interfeisu starp R1 un R5.<br \/>\nPirmk\u0101rt, mums p\u0101rb\u016bv\u0113sies unikasta mar\u0161rut\u0113\u0161anas tabula R5, un tagad t\u012bkls 192.168.1.0\/24 tiek sasniegts caur interfeisu R5 Gi0\/2. Tagad R5 sa\u0146emot multicast interfeis\u0101 Gi0\/1, saprot, ka RPF noteikums netiek apmierin\u0101ts un b\u016btu lo\u0123isk\u0101k sa\u0146emt multicast caur Gi0\/2. Vi\u0146am j\u0101atvienojas no RPT un j\u0101uzb\u016bv\u0113 \u012bs\u0101ks koks, ko sauc par Shortest-Path Tree (SPT). T\u0101d\u0113\u013c vi\u0146\u0161 caur Gi0\/2 nos\u016bta PIM Join uz R1, un R1 s\u0101k s\u016bt\u012bt multicast ar\u012b caur Gi0\/2. Tagad R5 ir j\u0101atvienojas no RPT, lai nesa\u0146emtu divas kopijas. T\u0101d\u0113\u013c vi\u0146\u0161 nos\u016bta Prune zi\u0146ojumu, nor\u0101dot avota IP adresi un ievietojot \u012bpa\u0161u bitu \u2014 RPT-bit. Tas noz\u012bm\u0113, ka man nevajag s\u016bt\u012bt trafiku, man te ir lab\u0101ks koks. RP ar\u012b s\u016bta PIM Prune zi\u0146ojumus uz R1, bet nes\u016bta Register-Stop zi\u0146ojumu. V\u0113l viena \u012bpatn\u012bba: R5 tagad past\u0101v\u012bgi s\u016bta PIM Prune uz RP, jo R1 turpina s\u016bt\u012bt PIM Register uz RP katru min\u016bti. RP, l\u012bdz neb\u016bs jaunu v\u0113l\u0113t\u0101ju \u0161\u012b trafika, atbild\u0113s ar atteikumu. R5 inform\u0113 RP, ka turpina sa\u0146emt multicast caur SPT.<br \/>\n<b>Dinamisks RP mekl\u0113jums. <br \/>\nAuto-RP.<\/b><br \/>\n\u0160\u012b tehnolo\u0123ija ir Cisco patent\u0113ta un nav \u012bpa\u0161i popul\u0101ra, ta\u010du t\u0101 joproj\u0101m past\u0101v. Auto-RP darb\u012bba sast\u0101v no div\u0101m galvenaj\u0101m stadij\u0101m:<br \/>\n1) RP s\u016bta RP-Announce zi\u0146ojumus uz rezerv\u0113to adresi \u2014 224.0.1.39, pazi\u0146ojot par sevi k\u0101 RP vai nu vis\u0101m, vai da\u017e\u0101m grup\u0101m. \u0160is zi\u0146ojums tiek s\u016bt\u012bts katru min\u016bti.<br \/>\n2) Nepiecie\u0161ams RP mapping agent, kur\u0161 s\u016bt\u012bs RP-Discovery zi\u0146ojumus ar nor\u0101d\u012bjumu, kur\u0101m grup\u0101m kur\u0161 RP ir j\u0101uzklausa. Tie\u0161i no \u0161\u012b zi\u0146ojuma parastie PIM mar\u0161rut\u0113t\u0101ji noteiks savu RP. Mapping Agent var b\u016bt gan pats RP mar\u0161rut\u0113t\u0101js, gan k\u0101ds atsevi\u0161\u0137s PIM mar\u0161rut\u0113t\u0101js. RP-Discovery tiek s\u016bt\u012bts uz adresi 224.0.1.40 ar taimeri vien\u0101 min\u016bt\u0113.<br \/>\nPaskat\u012bsimies procesu s\u012bk\u0101k:<br \/>\nIestat\u012bsim R3 k\u0101 RP:<\/p>\n<blockquote><p>ip pim send-rp-announce loopback 0 scope 10<\/p><\/blockquote>\n<p>\nR2 k\u0101 mapping agent:<\/p>\n<blockquote><p>ip pim send-rp-discovery loopback 0 scope 10<\/p><\/blockquote>\n<p>\nUn visos p\u0101r\u0113jos gaid\u012bsim RP caur Auto-RP:<\/p>\n<blockquote><p>ip pim autorp listener<\/p><\/blockquote>\n<p>\nTikl\u012bdz m\u0113s iestat\u012bsim R3, tas s\u0101ks s\u016bt\u012bt RP-Announce:<br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/6c4WucN.jpg\"><img decoding=\"async\" alt=\"PIM protokola darb\u012bbas principi\" src=\"\/wp-content\/uploads\/2019\/05\/3077778bb47731bb02a8e7fc6945aa63.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nUn R2, p\u0113c mapping agent iestat\u012b\u0161anas, s\u0101ks gaid\u012bt RP-Announce zi\u0146ojumus. Tikai tad, kad tas atrad\u012bs vismaz vienu RP, tas s\u0101ks s\u016bt\u012bt RP-Discovery:<br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/lw2JuDD.jpg\"><img decoding=\"async\" alt=\"PIM protokola darb\u012bbas principi\" src=\"\/wp-content\/uploads\/2019\/05\/37eff65f3c359cd3091c47af22220a6b.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nT\u0101d\u0113j\u0101di, tikl\u012bdz parastie mar\u0161rut\u0113t\u0101ji (PIM RP Listener) sa\u0146ems \u0161o zi\u0146ojumu, tie zin\u0101s, kur mekl\u0113t RP.<br \/>\nViens no galvenajiem Auto-RP tr\u016bkumiem ir tas, ka, lai sa\u0146emtu RP-Announce un RP-Discovery zi\u0146ojumus, nepiecie\u0161ams s\u016bt\u012bt PIM Join uz adres\u0113m 224.0.1.39-40, bet lai to s\u016bt\u012btu, j\u0101zina, kur atrodas RP. Klasiskais vistas un olu jaut\u0101jums. \u0160ai probl\u0113mai tika izstr\u0101d\u0101ts PIM Sparse-Dense-Mode. Ja mar\u0161rut\u0113t\u0101js nezina RP, tas darbojas Dense-mode re\u017e\u012bm\u0101, ja zina, tad Sparse-mode. Kad parasto mar\u0161rut\u0113t\u0101ju saskarn\u0113s ir iestat\u012bts PIM Sparse-mode un komanda ip pim autorp listener, mar\u0161rut\u0113t\u0101js darbosies Dense-mode tikai multividei tie\u0161i Auto-RP protokola ietvaros (224.0.1.39-40).<br \/>\n<b>BootStrap Router (BSR).<\/b><br \/>\n\u0160\u012b funkcija darbojas l\u012bdz\u012bgi k\u0101 Auto-RP. Katrs RP s\u016bta zi\u0146ojumu mapping agent, kur\u0161 apkopo mape\u0161anas inform\u0101ciju un t\u0101l\u0101k to zi\u0146o visiem p\u0101r\u0113jiem mar\u0161rut\u0113t\u0101jiem. Aprakst\u012bsim procesu l\u012bdz\u012bgi Auto-RP:<br \/>\n1) Tikl\u012bdz m\u0113s iestat\u0101m R3 par kandid\u0101tu b\u016bt RP, izmantojot komandu:<\/p>\n<blockquote><p>ip pim rp-candidate loopback 0<\/p><\/blockquote>\n<p>\nTad R3 neko nedar\u012bs, lai s\u0101ktu s\u016bt\u012bt \u012bpa\u0161us zi\u0146ojumus, tam vispirms j\u0101atrod mapping agent. T\u0101d\u0113j\u0101di p\u0101rejam uz otro posmu.<br \/>\n2) Iestat\u0101m R2 k\u0101 mapping agent:<\/p>\n<blockquote><p>ip pim bsr-candidate loopback 0<\/p><\/blockquote>\n<p>\nR2 s\u0101k izs\u016bt\u012bt PIM Bootstrap zi\u0146ojumus, nor\u0101dot sevi k\u0101 mapping agent:<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/uAj49oT.jpg\"><img decoding=\"async\" alt=\"PIM protokola darb\u012bbas principi\" src=\"\/wp-content\/uploads\/2019\/05\/2b05ffd64bd33ee5380aa24d5f76df67.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n\u0160is zi\u0146ojums tiek nos\u016bt\u012bts uz adresi 224.0.0.13, kuru PIM protokols izmanto ar\u012b cit\u0101s sav\u0101s zi\u0146ojumu nos\u016bt\u012b\u0161anas reiz\u0113s. Tas nos\u016bta tos vis\u0101s pus\u0113s, t\u0101p\u0113c nav vistas un ola probl\u0113mas, k\u0101 tas bija Auto-RP.<br \/>\n3) Tikl\u012bdz RP sa\u0146ems zi\u0146ojumu no BSR mar\u0161rut\u0113t\u0101ja, tas t\u016bl\u012bt nos\u016bt\u012bs unik\u0101lo zi\u0146ojumu uz BSR mar\u0161rut\u0113t\u0101ja adresi:<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/qwtXY88.jpg\"><img decoding=\"async\" alt=\"PIM protokola darb\u012bbas principi\" src=\"\/wp-content\/uploads\/2019\/05\/38547a114a2bca74131c95b95e535fdc.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nP\u0113c tam, kad BSR sa\u0146ems inform\u0101ciju par RP, tas izplat\u012bs to multicasting uz adresi 224.0.0.13, kuru klaus\u0101s visi PIM mar\u0161rut\u0113t\u0101ji. T\u0101d\u0113j\u0101di nav analoga komandas <i>ip pim autorp listener<\/i> par parastajiem mar\u0161rut\u0113t\u0101jiem BSR.<br \/>\n<b>Anycast RP ar Multicast Source Discovery Protocol (MSDP).<\/b><br \/>\nAuto-RP un BSR \u013cauj sadal\u012bt slodzi uz RP \u0161\u0101di: katrai multicasting grupai ir tikai viens akt\u012bvs RP. Nav iesp\u0113jams veidot slodzes sadal\u012bjumu vienai multicasting grupai ar vair\u0101kiem RP. MSDP to paveic, izsniedzot RP mar\u0161rut\u0113t\u0101jiem vien\u0101du IP adresi ar masku 255.255.255.255. MSDP ieg\u016bst inform\u0101ciju ar vienu no metod\u0113m: statiku, Auto-RP vai BSR.<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/U4aDz5H.png\"><img decoding=\"async\" alt=\"PIM protokola darb\u012bbas principi\" src=\"\/wp-content\/uploads\/2019\/05\/c0352b5fbc5780f667c6c97ea6dde26d.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nAtt\u0113l\u0101 redzam Auto-RP konfigur\u0101ciju ar MSDP. Abi RP ir konfigur\u0113ti ar IP adresi 172.16.1.1\/32 uz Loopback 1 interfeisa un tiek izmantoti vis\u0101m grup\u0101m. Pie RP-Announce abi mar\u0161rut\u0113t\u0101ji st\u0101sta par sevi, atsaucoties uz \u0161o adresi. Auto-RP mapping agent, sa\u0146emot inform\u0101ciju, izs\u016bta RP-Discovery par RP ar adresi 172.16.1.1\/32. Par t\u012bklu 172.16.1.1\/32 mar\u0161rut\u0113t\u0101jiem m\u0113s st\u0101st\u0101m, izmantojot IGP un attiec\u012bgi. T\u0101d\u0113j\u0101di PIM mar\u0161rut\u0113t\u0101ji pieprasa vai re\u0123istr\u0113 pl\u016bsmas no t\u0101 RP, kuru ir nor\u0101d\u012bjusi k\u0101 next-hop mar\u0161rutam uz t\u012bklu 172.16.1.1\/32. Pats MSDP protokols ir paredz\u0113ts RP, lai apmain\u012btos ar zi\u0146ojumiem par inform\u0101ciju par multicasting.<br \/>\nApskat\u012bsim \u0161\u0101du topolo\u0123iju:<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/zgkGDOP.jpg\"><img decoding=\"async\" alt=\"PIM protokola darb\u012bbas principi\" src=\"\/wp-content\/uploads\/2019\/05\/e4823362e7a2abc9b4ee9ba954d709b8.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nSwitch6 izs\u016bta satiksmi uz adresi 238.38.38.38, un par to pagaid\u0101m zina tikai RP-R1. \u0160eit Switch7 un Switch8 ir piepras\u012bju\u0161i \u0161o grupu. Mar\u0161rut\u0113t\u0101ji R5 un R4 nos\u016bt\u012bs PIM Join uz R1 un R3, attiec\u012bgi. K\u0101p\u0113c? Mar\u0161ruts uz 13.13.13.13 R5 nor\u0101d\u012bs uz R1 ar IGP metrikas pal\u012bdz\u012bbu, t\u0101pat k\u0101 R4.<br \/>\nRP-R1 zina par pl\u016bsmu un s\u0101ks to izs\u016bt\u012bt uz R5, bet R4 par to neko nezina, jo R1 vienk\u0101r\u0161i to nes\u016bt\u012bs. T\u0101p\u0113c nepiecie\u0161ams MSDP. Konfigur\u0113jam to uz R1 un R5:<\/p>\n<blockquote><p>ip msdp peer 3.3.3.3 connect-source Loopback1 uz R1<\/p><\/blockquote>\n<p><\/p>\n<blockquote><p>ip msdp peer 1.1.1.1 connect-source Loopback3 uz R3<\/p><\/blockquote>\n<p>\nVi\u0146i izveidos sesiju starp sevi un, sa\u0146emot k\u0101du pl\u016bsmu, inform\u0113s par to savu RP kaimi\u0146u.<br \/>\nKad RP-R1 sa\u0146ems straumi no Switch6, tas nekav\u0113joties nos\u016bt\u012bs MSDP Source-Active zi\u0146ojumu, kur\u0101 b\u016bs inform\u0101cija par avotu un m\u0113r\u0137i (S, G) \u2014 inform\u0101cija par multicast avotu un galam\u0113r\u0137i. Tagad, kad RP-R3 zin\u0101s, ka t\u0101ds avots k\u0101 Switch6 eksist\u0113, sa\u0146emot piepras\u012bjumu no R4 par \u0161o straumi, tas nos\u016bt\u012bs PIM Join uz Switch6, balstoties uz mar\u0161rut\u0113\u0161anas tabulu. T\u0101d\u0113j\u0101di, sa\u0146emot \u0161o PIM Join, R1 s\u0101ks s\u016bt\u012bt satiksmi uz RP-R3.<br \/>\nMSDP darbojas, izmantojot TCP, RP sav\u0101 starp\u0101 s\u016bta keepalive zi\u0146ojumus, lai p\u0101rbaud\u012btu dz\u012bvotsp\u0113ju. Taimeris ir 60 sekundes.<br \/>\nNav skaidra MSDP pu\u0161u sadal\u012b\u0161anas funkcija da\u017e\u0101dos dom\u0113nos, jo Keepalive un SA zi\u0146ojumos nav nor\u0101d\u012bta pieder\u012bba k\u0101dam dom\u0113nam. Ar\u012b \u0161aj\u0101 topolo\u0123ij\u0101 tika test\u0113ta konfigur\u0101cija ar da\u017e\u0101du dom\u0113nu nor\u0101d\u012bjumiem \u2014 darba rezult\u0101ti neizmain\u012bj\u0101s. <br \/>\nJa k\u0101ds var sniegt skaidrojumu, labpr\u0101t izlas\u012b\u0161u koment\u0101ros.<br \/>\n<br \/>Avots: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/450582\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0440\u043e\u0442\u043e\u043a\u043e\u043b PIM \u2014 \u044d\u0442\u043e \u043d\u0430\u0431\u043e\u0440 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u0432 \u0434\u043b\u044f \u043f\u0435\u0440\u0435\u0434\u0430\u0447\u0438 \u043c\u0443\u043b\u044c\u0442\u0438\u043a\u0430\u0441\u0442\u0430 \u0432 \u0441\u0435\u0442\u0438 \u043c\u0435\u0436\u0434\u0443 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0442\u043e\u0440\u0430\u043c\u0438. \u041e\u0442\u043d\u043e\u0448\u0435\u043d\u0438\u044f \u0441\u043e\u0441\u0435\u0434\u0441\u0442\u0432\u0430 \u0441\u0442\u0440\u043e\u0438\u0442\u0441\u044f \u0430\u043d\u0430\u043b\u043e\u0433\u0438\u0447\u043d\u043e \u043a\u0430\u043a \u0438 \u0432 \u0441\u043b\u0443\u0447\u0430\u0435 \u0434\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u0432 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438. PIMv2 \u043e\u0442\u043f\u0440\u0430\u0432\u043b\u044f\u0435\u0442 \u043a\u0430\u0436\u0434\u044b\u0435 30 \u0441\u0435\u043a\u0443\u043d\u0434 Hello \u0441\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u044f \u043d\u0430 \u0437\u0430\u0440\u0435\u0437\u0435\u0440\u0432\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0439 \u043c\u0443\u043b\u044c\u0442\u0438\u043a\u0430\u0441\u0442 \u0430\u0434\u0440\u0435\u0441 224.0.0.13 ( All-PIM-Routers ). \u0421\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u0435 \u0441\u043e\u0434\u0435\u0440\u0436\u0438\u0442 \u0432 \u0441\u0435\u0431\u0435 Hold Timers \u2014 \u043e\u0431\u044b\u0447\u043d\u043e \u0440\u0430\u0432\u0435\u043d 3.5*Hello Timer, \u0442\u043e \u0435\u0441\u0442\u044c 105 \u0441\u0435\u043a\u0443\u043d\u0434 \u043f\u043e [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":24886,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-33142","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u0440\u043e\u0442\u043e\u043a\u043e\u043b PIM \u2014 \u044d\u0442\u043e \u043d\u0430\u0431\u043e\u0440 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u0432 \u0434\u043b\u044f \u043f\u0435\u0440\u0435\u0434\u0430\u0447\u0438 \u043c\u0443\u043b\u044c\u0442\u0438\u043a\u0430\u0441\u0442\u0430 \u0432 \u0441\u0435\u0442\u0438 \u043c\u0435\u0436\u0434\u0443 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0442\u043e\u0440\u0430\u043c\u0438. \u041e\u0442\u043d\u043e\u0448\u0435\u043d\u0438\u044f \u0441\u043e\u0441\u0435\u0434\u0441\u0442\u0432\u0430 \u0441\u0442\u0440\u043e\u0438\u0442\u0441\u044f \u0430\u043d\u0430\u043b\u043e\u0433\u0438\u0447\u043d\u043e \u043a\u0430\u043a \u0438 \u0432 \u0441\u043b\u0443\u0447\u0430\u0435 \u0434\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u0432 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/printsipy-raboty-protokola-pim\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5\" \/>\n\t\t<meta property=\"og:locale\" content=\"lv_LV\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041f\u0440\u0438\u043d\u0446\u0438\u043f\u044b \u0440\u0430\u0431\u043e\u0442\u044b \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 PIM | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0440\u043e\u0442\u043e\u043a\u043e\u043b PIM \u2014 \u044d\u0442\u043e \u043d\u0430\u0431\u043e\u0440 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u0432 \u0434\u043b\u044f \u043f\u0435\u0440\u0435\u0434\u0430\u0447\u0438 \u043c\u0443\u043b\u044c\u0442\u0438\u043a\u0430\u0441\u0442\u0430 \u0432 \u0441\u0435\u0442\u0438 \u043c\u0435\u0436\u0434\u0443 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0442\u043e\u0440\u0430\u043c\u0438. \u041e\u0442\u043d\u043e\u0448\u0435\u043d\u0438\u044f \u0441\u043e\u0441\u0435\u0434\u0441\u0442\u0432\u0430 \u0441\u0442\u0440\u043e\u0438\u0442\u0441\u044f \u0430\u043d\u0430\u043b\u043e\u0433\u0438\u0447\u043d\u043e \u043a\u0430\u043a \u0438 \u0432 \u0441\u043b\u0443\u0447\u0430\u0435 \u0434\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u0432 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/printsipy-raboty-protokola-pim\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T18:50:58+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:50:58+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47PIM protokola darb\u012bbas principi | ProHoster","description":"PIM protokols ir protokolu kopums, kas paredz\u0113ts multicast datu p\u0101rraidei t\u012bkl\u0101 starp mar\u0161rut\u0113t\u0101jiem. Ka neighbor attiec\u012bbas tiek veidotas l\u012bdz\u012bgi k\u0101 dinamisko mar\u0161rut\u0113\u0161anas protokolu gad\u012bjum\u0101.","canonical_url":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/printsipy-raboty-protokola-pim","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"lv_LV","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\u041f\u0440\u0438\u043d\u0446\u0438\u043f\u044b \u0440\u0430\u0431\u043e\u0442\u044b \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 PIM | ProHoster","og:description":"\u041f\u0440\u043e\u0442\u043e\u043a\u043e\u043b PIM \u2014 \u044d\u0442\u043e \u043d\u0430\u0431\u043e\u0440 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u0432 \u0434\u043b\u044f \u043f\u0435\u0440\u0435\u0434\u0430\u0447\u0438 \u043c\u0443\u043b\u044c\u0442\u0438\u043a\u0430\u0441\u0442\u0430 \u0432 \u0441\u0435\u0442\u0438 \u043c\u0435\u0436\u0434\u0443 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0442\u043e\u0440\u0430\u043c\u0438. \u041e\u0442\u043d\u043e\u0448\u0435\u043d\u0438\u044f \u0441\u043e\u0441\u0435\u0434\u0441\u0442\u0432\u0430 \u0441\u0442\u0440\u043e\u0438\u0442\u0441\u044f \u0430\u043d\u0430\u043b\u043e\u0433\u0438\u0447\u043d\u043e \u043a\u0430\u043a \u0438 \u0432 \u0441\u043b\u0443\u0447\u0430\u0435 \u0434\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u043e\u0432 \u043c\u0430\u0440\u0448\u0440\u0443\u0442\u0438\u0437\u0430\u0446\u0438\u0438.","og:url":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/printsipy-raboty-protokola-pim","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T18:50:58+00:00","article:modified_time":"2019-10-31T18:50:58+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"33142","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-21 14:06:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:46:23","updated":"2026-01-21 14:06:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts\/33142","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/comments?post=33142"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts\/33142\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media\/24886"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media?parent=33142"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/categories?post=33142"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/tags?post=33142"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}