{"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\/cs\/blog\/administrirovanie\/printsipy-raboty-protokola-pim","title":{"rendered":"Principy pr\u00e1ce protokolu PIM","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Protokol PIM je soubor protokol\u016f pro p\u0159enos multicastu v s\u00edti mezi sm\u011brova\u010di. Vztahy sousedstv\u00ed se vytv\u00e1\u0159ej\u00ed podobn\u011b jako v p\u0159\u00edpad\u011b dynamick\u00fdch sm\u011brovac\u00edch protokol\u016f. PIMv2 pos\u00edl\u00e1 ka\u017ed\u00fdch 30 sekund zpr\u00e1vy Hello na rezervovanou multicastovou adresu 224.0.0.13 (All-PIM-Routers). Zpr\u00e1va obsahuje Hold Timers \u2014 obvykle roven 3.5 * Hello Timer, tedy 105 sekund ve v\u00fdchoz\u00edm nastaven\u00ed.<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/AqjQmPR.jpg\"><img decoding=\"async\" alt=\"Principy pr\u00e1ce protokolu PIM\" src=\"\/wp-content\/uploads\/2019\/05\/f2e0c7dbdb8d7640671440289fbcd91f.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n PIM pou\u017e\u00edv\u00e1 dva hlavn\u00ed re\u017eimy pr\u00e1ce \u2014 Dense a Sparse mode. Za\u010dn\u011bme s re\u017eimem Dense. <noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\n<b>Stromy distribuce na z\u00e1klad\u011b zdroje.<\/b><br \/>\nRe\u017eim Dense mode je vhodn\u00e9 pou\u017e\u00edt v p\u0159\u00edpad\u011b velk\u00e9ho po\u010dtu klient\u016f r\u016fzn\u00fdch multicastov\u00fdch skupin. Kdy\u017e sm\u011brova\u010d obdr\u017e\u00ed multicastov\u00fd provoz, nejprve kontroluje jeho pravidlo RPF. RPF \u2014 toto pravidlo se pou\u017e\u00edv\u00e1 ke kontrole zdroje multicastu s tabulkou sm\u011brov\u00e1n\u00ed unicast. Je nutn\u00e9, aby provoz p\u0159ich\u00e1zel na ten interface, za kter\u00fdm se skr\u00fdv\u00e1 dan\u00fd host podle tabulky sm\u011brov\u00e1n\u00ed unicast. Tento mechanismus \u0159e\u0161\u00ed probl\u00e9m vzniku smy\u010dky p\u0159i p\u0159enosu multicastu.<br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/RE54lnP.png\"><img decoding=\"async\" alt=\"Principy pr\u00e1ce protokolu PIM\" src=\"\/wp-content\/uploads\/2019\/05\/4d855ea59c6329c7e727cc70a79367b2.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nR3 z multicastov\u00e9 zpr\u00e1vy zjist\u00ed zdroj multicastu (Source IP) a zkontroluje dva proudy od R1 a R2 podle sv\u00e9 tabulky unicast. Proud z toho interface, na kter\u00fd ukazuje tabulka (R1 k R3), bude p\u0159ed\u00e1n d\u00e1le, zat\u00edmco proud od R2 bude zam\u00edtnut, proto\u017ee pro dosa\u017een\u00ed zdroje multicastu je nutn\u00e9 pos\u00edlat pakety p\u0159es S0\/1.<br \/>\nCo se stane, pokud m\u00e1te dva ekvivalentn\u00ed sm\u011bry s identickou metrikou? V tomto p\u0159\u00edpad\u011b sm\u011brova\u010d vybere podle next-hop t\u011bchto sm\u011br\u016f. Kter\u00fd m\u00e1 vy\u0161\u0161\u00ed IP adresu, ten vyhr\u00e1l. Pokud je pot\u0159eba zm\u011bnit toto chov\u00e1n\u00ed, lze pou\u017e\u00edt ECMP. V\u00edce informac\u00ed zde. <noindex><a rel=\"nofollow\" href=\"https:\/\/drive.google.com\/file\/d\/1yiam4-OwlDoXrfdfdienMN_nQaOJGi29\/view?usp=sharing\">tady<\/a><\/noindex>.<br \/>\nPo kontrole pravidla RPF sm\u011brova\u010d pos\u00edl\u00e1 multicastov\u00fd paket v\u0161em sv\u00fdm PIM soused\u016fm, krom\u011b toho, od kter\u00e9ho byl tento paket p\u0159ijat. Ostatn\u00ed PIM sm\u011brova\u010de opakuj\u00ed tento proces. Cesta, kterou multicastov\u00fd paket pro\u0161el od zdroje k kone\u010dn\u00fdm p\u0159\u00edjemc\u016fm, tvo\u0159\u00ed strom, kter\u00fd se naz\u00fdv\u00e1 \u2014 source-based distribution tree, shortest-path tree (SPT), source tree. T\u0159i r\u016fzn\u00e9 n\u00e1zvy, vyberte si jak\u00fdkoliv.<br \/>\nJak vy\u0159e\u0161it probl\u00e9m s t\u00edm, \u017ee n\u011bkter\u00e9 sm\u011brova\u010de nezpracovaly n\u011bjak\u00fd multicastov\u00fd proud a nikdo ho nepos\u00edl\u00e1, a p\u0159esto jejich nad\u0159\u00edzen\u00fd sm\u011brova\u010d ho pos\u00edl\u00e1. Pro to byl vymy\u0161len mechanismus Prune. <br \/>\n<b>Prune Message.<\/b><br \/>\nNap\u0159\u00edklad R2 bude nad\u00e1le pos\u00edlat R3 multicast, a\u010dkoliv R3 podle pravidla RPF jej zavrhuje. Pro\u010d zat\u011b\u017eovat kan\u00e1l? R3 pos\u00edl\u00e1 PIM Prune zpr\u00e1vu a R2, po obdr\u017een\u00ed t\u00e9to zpr\u00e1vy, odstran\u00ed rozhran\u00ed S0\/1 ze seznamu (outgoing interface list) pro tento tok, seznam rozhran\u00ed, ze kter\u00fdch je t\u0159eba tento provoz pos\u00edlat. <\/p>\n<blockquote><p>N\u00e1sleduje form\u00e1ln\u011bj\u0161\u00ed definice zpr\u00e1vy PIM Prune:<br \/>\nZpr\u00e1va PIM Prune je odes\u00edl\u00e1na jedn\u00edm routerem druh\u00e9mu routeru, aby druh\u00fd router odstranil spojen\u00ed, na kter\u00e9m je Prune p\u0159ijato, z konkr\u00e9tn\u00edho (S,G) SPT.<\/p><\/blockquote>\n<p>\nPo obdr\u017een\u00ed zpr\u00e1vy Prune nastav\u00ed R2 Prune \u010dasova\u010d na 3 minuty. Po t\u0159ech minut\u00e1ch za\u010dne op\u011bt pos\u00edlat provoz, dokud neobdr\u017e\u00ed dal\u0161\u00ed zpr\u00e1vu Prune. To plat\u00ed pro PIMv1.<br \/>\nA v PIMv2 byl p\u0159id\u00e1n \u010dasova\u010d State Refresh (ve v\u00fdchoz\u00edm nastaven\u00ed 60 sekund). Jakmile byla odesl\u00e1na zpr\u00e1va Prune z R3, spust\u00ed se tento \u010dasova\u010d na R3. Po uplynut\u00ed tohoto \u010dasova\u010de R3 ode\u0161le zpr\u00e1vu State Refresh, kter\u00e1 resetuje 3-minutov\u00fd Prune timer na R2 pro tuto skupinu. <br \/>\nD\u016fvody pro odesl\u00e1n\u00ed zpr\u00e1vy Prune:<\/p>\n<ul>\n<li> Kdy\u017e multicastov\u00fd paket nepro\u0161el kontrolou RPF.<\/li>\n<li> Kdy\u017e nejsou m\u00edstn\u011b p\u0159ipojeni klienti, kte\u0159\u00ed by po\u017e\u00e1dali o multicastovou skupinu (IGMP Join), a nejsou PIM soused\u00e9, kter\u00fdm by bylo mo\u017en\u00e9 pos\u00edlat multicastov\u00fd provoz (Non-prune Interface).<\/li>\n<\/ul>\n<p>\n<b>Graft Message.<\/b><br \/>\nP\u0159edstavme si, \u017ee R3 necht\u011bl provoz od R2, odeslal Prune a p\u0159ij\u00edmal multicast od R1. Ale najednou, do\u0161lo k v\u00fdpadku kan\u00e1lu mezi R1-R3 a R3 z\u016fstal bez multicastu. M\u016f\u017eeme \u010dekat 3 minuty, ne\u017e na R2 vypr\u0161\u00ed Prune Timer. \u010cek\u00e1n\u00ed 3 minuty je dlouh\u00e9, abychom ne\u010dekali, je t\u0159eba poslat zpr\u00e1vu, kter\u00e1 okam\u017eit\u011b vyvede toto rozhran\u00ed S0\/1 na R2 ze stavu pruned. Takovou zpr\u00e1vou bude Graft zpr\u00e1va. Po obdr\u017een\u00ed zpr\u00e1vy Graft ode\u0161le R2 v odpov\u011bdi 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=\"Principy pr\u00e1ce protokolu PIM\" src=\"\/wp-content\/uploads\/2019\/05\/72e368905d2e37ba9b9d46101ebcd8ae.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nPod\u00edvejme se na tuto sch\u00e9ma. R1 vys\u00edl\u00e1 multicast do segmentu se dv\u011bma routery. R3 p\u0159ij\u00edm\u00e1 a vys\u00edl\u00e1 provoz, R2 p\u0159ij\u00edm\u00e1, ale nem\u00e1 koho obsluhovat. Pos\u00edl\u00e1 zpr\u00e1vu Prune k R1 do tohoto segmentu. R1 by m\u011bl odstranit Fa0\/0 ze seznamu a p\u0159estat vys\u00edlat do tohoto segmentu, ale co se stane s R3? R3 je ve stejn\u00e9m segmentu a tak\u00e9 obdr\u017eel zpr\u00e1vu Prune a pochopil trag\u00e9dii situace. P\u0159ed t\u00edm, ne\u017e R1 p\u0159estane vys\u00edlat, nastav\u00ed \u010dasova\u010d na 3 sekundy a p\u0159estane vys\u00edlat za 3 sekundy. 3 sekundy \u2014 pr\u00e1v\u011b tolik \u010dasu m\u00e1 R3, aby neztratil sv\u016fj multicast. Proto R3 co nejd\u0159\u00edve pos\u00edl\u00e1 zpr\u00e1vu Pim Join pro tuto skupinu a R1 u\u017e nep\u0159em\u00fd\u0161l\u00ed o tom, \u017ee by p\u0159estal vys\u00edlat. O zpr\u00e1v\u00e1ch Join n\u00ed\u017ee.<br \/>\n<b>Assert zpr\u00e1va.<\/b><br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/rliwmNF.png\"><img decoding=\"async\" alt=\"Principy pr\u00e1ce protokolu PIM\" src=\"\/wp-content\/uploads\/2019\/05\/f7cc9c247cd26a8f9567b170f9b61bbb.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nP\u0159edstavme si situaci: do jedn\u00e9 s\u00edt\u011b vys\u00edlaj\u00ed dva routery. Dost\u00e1vaj\u00ed stejn\u00fd tok od zdroje a oba ho vys\u00edlaj\u00ed do jedn\u00e9 s\u00edt\u011b za rozhran\u00edm e0. Mus\u00ed tedy zjistit, kdo bude jedin\u00fdm vys\u00edlatelem pro tuto s\u00ed\u0165. K tomu slou\u017e\u00ed zpr\u00e1vy Assert. Kdy\u017e R2 a R3 detekuj\u00ed duplikaci multicastov\u00e9ho provozu, tedy na R2 a R3 p\u0159ich\u00e1z\u00ed multicast, kter\u00fd sami vys\u00edlaj\u00ed, routery ch\u00e1pou, \u017ee n\u011bco nen\u00ed v po\u0159\u00e1dku. V tomto p\u0159\u00edpad\u011b routery pos\u00edlaj\u00ed zpr\u00e1vy Assert, kter\u00e9 obsahuj\u00ed Administrative Distance a metriky trasy, pomoc\u00ed kter\u00e9 se dosahuje zdroje multicastu \u2014 10.1.1.10. V\u00edt\u011bz je ur\u010den takto:<\/p>\n<ol>\n<li>Ten, kdo m\u00e1 ni\u017e\u0161\u00ed AD.<\/li>\n<li>Pokud jsou AD stejn\u00e9, pak ten, kdo m\u00e1 ni\u017e\u0161\u00ed metriku.<\/li>\n<li>Pokud je i zde rovnost, tak ten, kdo m\u00e1 vy\u0161\u0161\u00ed IP v s\u00edti, do kter\u00e9 vys\u00edlaj\u00ed tento multicast.<\/li>\n<\/ol>\n<p>\nV\u00edt\u011bz t\u00e9to volby se st\u00e1v\u00e1 Designated Routerem. Pro v\u00fdb\u011br DR se tak\u00e9 pou\u017e\u00edvaj\u00ed Pim Hello. Na za\u010d\u00e1tku \u010dl\u00e1nku bylo uk\u00e1z\u00e1no zpr\u00e1vu PIM Hello, kde je vid\u011bt pole DR. V\u00edt\u011bz\u00ed ten, kdo m\u00e1 vy\u0161\u0161\u00ed IP adresy na tomto odkazu.<br \/>\nU\u017eite\u010dn\u00e1 tabulka:<br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/Et1kP7h.png\"><img decoding=\"async\" alt=\"Principy pr\u00e1ce protokolu PIM\" src=\"\/wp-content\/uploads\/2019\/05\/d450c9fac2b6d74c5b7414d85910bca4.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n<b>MROUTE Tabulka.<\/b><br \/>\nPo po\u010d\u00e1te\u010dn\u00edm p\u0159ezkoum\u00e1n\u00ed fungov\u00e1n\u00ed protokolu PIM je t\u0159eba se zam\u011b\u0159it na to, jak pracovat s multicastovou sm\u011brovac\u00ed tabulkou. V tabulce mroute je ulo\u017een\u00e1 informace o tom, kter\u00e9 toky byly po\u017eadov\u00e1ny ze strany klient\u016f a kter\u00e9 toky proud\u00ed z multicastov\u00fdch server\u016f. <br \/>\nNap\u0159\u00edklad, p\u0159i obdr\u017een\u00ed IGMP Membership Report nebo PIM Join na n\u011bjak\u00e9m rozhran\u00ed se do sm\u011brovac\u00ed tabulky p\u0159id\u00e1v\u00e1 z\u00e1znam typu (*, G):<br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/ufXsgnR.jpg\"><img decoding=\"async\" alt=\"Principy pr\u00e1ce protokolu PIM\" src=\"\/wp-content\/uploads\/2019\/05\/094d96f36512c3b1b8d179044f354ac1.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nTento z\u00e1znam znamen\u00e1, \u017ee byla p\u0159ijata \u017e\u00e1dost o provoz z adresy 238.38.38.38. P\u0159\u00edznak DC znamen\u00e1, \u017ee multicast bude fungovat v re\u017eimu Dense mode a C znamen\u00e1, \u017ee p\u0159\u00edjemce je p\u0159\u00edmo p\u0159ipojen k routeru, co\u017e znamen\u00e1, \u017ee router obdr\u017eel IGMP Membership Report a PIM Join.<br \/>\nPokud existuje z\u00e1znam typu (S,G), znamen\u00e1 to, \u017ee m\u00e1me multicast stream:<br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/QJCZZwf.jpg\"><img decoding=\"async\" alt=\"Principy pr\u00e1ce protokolu PIM\" src=\"\/wp-content\/uploads\/2019\/05\/56f2e8376a7f89f3fd3082a098ce42e5.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nV poli S \u2014 192.168.1.11, m\u00e1me uvedenou IP adresu zdroje multicastu, pr\u00e1v\u011b ta bude zkontrolov\u00e1na pravidlem RPF. V p\u0159\u00edpad\u011b probl\u00e9m\u016f je nutn\u00e9 nejprve zkontrolovat unicastovou tabulku na trasu k zdroji. V poli Incoming Interface se uv\u00e1d\u00ed rozhran\u00ed, na kter\u00e9 p\u0159ich\u00e1z\u00ed multicast. V unicastov\u00e9 tabulce sm\u011brov\u00e1n\u00ed by m\u011bla trasa k zdroji odkazovat na rozhran\u00ed uveden\u00e9 zde. V Outgoing Interface se uv\u00e1d\u00ed, kam bude multicast p\u0159esm\u011brov\u00e1n. Pokud je pr\u00e1zdn\u00e9, znamen\u00e1 to, \u017ee k routeru nebyly p\u0159ijaty \u017e\u00e1dosti o tento provoz. Podrobn\u011bj\u0161\u00ed informace o v\u0161ech p\u0159\u00edznac\u00edch lze naj\u00edt <noindex><a rel=\"nofollow\" href=\"https:\/\/drive.google.com\/file\/d\/1ArBLFJdyN8tCangB5GL2JaS47FEZaad-\/view?usp=sharing\">zde<\/a><\/noindex>.<br \/>\n<b>PIM Sparse-mode.<\/b><br \/>\nStrategie Sparse-mode je opakem Dense-mode. Kdy\u017e Sparse-mode p\u0159ijme multicastov\u00fd provoz, bude odes\u00edlat provoz pouze p\u0159es ta rozhran\u00ed, kde byly \u017e\u00e1dosti o tento stream, nap\u0159\u00edklad Pim Join nebo zpr\u00e1vy IGMP Report s \u017e\u00e1dost\u00ed o tento provoz.<br \/>\nPodobn\u00e9 prvky mezi SM a DM:<\/p>\n<ul>\n<li> Vztahy sousedstv\u00ed se buduj\u00ed stejn\u011b jako v PIM DM.<\/li>\n<li> Pravidlo RPF funguje.<\/li>\n<li> Volba DR je podobn\u00e1.<\/li>\n<li> Mechanismus Prune Overrides a zpr\u00e1vy Assert jsou analogick\u00e9.<\/li>\n<\/ul>\n<p>\nPro kontrolu toho, komu, kde a jak\u00fd multicastov\u00fd provoz je v s\u00edti pot\u0159eba, je nezbytn\u00fd spole\u010dn\u00fd informa\u010dn\u00ed st\u0159edisko. Tento st\u0159edisko bude na\u0161\u00edm Rendezvous Point (RP). V\u0161ichni, kdo cht\u011bj\u00ed n\u011bjak\u00fd multicastov\u00fd provoz nebo n\u011bkdo za\u010dal p\u0159ij\u00edmat multicastov\u00fd provoz od zdroje, jej pos\u00edl\u00e1 na RP.<br \/>\nKdy\u017e RP obdr\u017e\u00ed multicastov\u00fd provoz, ode\u0161le jej t\u011bm router\u016fm, kter\u00e9 o tento provoz p\u0159edt\u00edm \u017e\u00e1daly. <br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/5AErtbS.jpg\"><img decoding=\"async\" alt=\"Principy pr\u00e1ce protokolu PIM\" src=\"\/wp-content\/uploads\/2019\/05\/35646434f8b80a8a05253111864de2da.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nP\u0159edstavme si takovou topologii, kde RP je R3. Jakmile R1 obdr\u017e\u00ed provoz od S1, inkapsuluje tento multicastov\u00fd paket do unicastov\u00e9ho PIM Register zpr\u00e1vy a ode\u0161le jej na RP. Odkud v\u00ed, kdo je RP? V tomto p\u0159\u00edpad\u011b je nastaven staticky, o dynamick\u00e9m nastaven\u00ed RP si pov\u00edme pozd\u011bji. <\/p>\n<blockquote><p>ip pim rp-address 3.3.3.3<\/p><\/blockquote>\n<p>\nRP zkontroluje, zda byla informace od n\u011bkoho, kdo m\u011bl z\u00e1jem o p\u0159\u00edjem t\u00e9to komunikace. P\u0159edpokl\u00e1dejme, \u017ee nebyla. Pak RP ode\u0161le R1 zpr\u00e1vu PIM Register-Stop, co\u017e znamen\u00e1, \u017ee nikdo o tento multicast nem\u00e1 z\u00e1jem, registrace byla zam\u00edtnuta. R1 nepo\u0161le multicast. Ale hostitel multicastu jej bude st\u00e1le pos\u00edlat, tak\u017ee po obdr\u017een\u00ed Register-Stop R1 spust\u00ed \u010dasova\u010d Register-Suppression timer nastaven\u00fd na 60 sekund. 5 sekund p\u0159ed vypr\u0161en\u00edm tohoto \u010dasova\u010de za\u0161le R1 pr\u00e1zdnou Register zpr\u00e1vu s Null-Register bitem (tj. bez zabalen\u00e9ho multicast paketu) sm\u011brem k RP. RP na to bude reagovat takto:<\/p>\n<ul>\n<li> Pokud p\u0159\u00edjemci jak nebyli, tak nejsou, odpov\u00ed na to zpr\u00e1vou Register-Stop.<\/li>\n<li> Pokud se p\u0159\u00edjemci objevili, na toto nijak nezareaguje. R1, pokud b\u011bhem 5 sekund neobdr\u017e\u00ed zam\u00edtnut\u00ed sv\u00e9 registrace, se pot\u011b\u0161\u00ed a ode\u0161le zpr\u00e1vu Register se zabalen\u00fdm multicastem k RP.<\/li>\n<\/ul>\n<p>\nJak jsme si vyjasnili, jak multicast doch\u00e1z\u00ed k RP, nyn\u00ed se pokus\u00edme odpov\u011bd\u011bt na ot\u00e1zku, jak RP p\u0159iv\u00e1d\u00ed p\u0159enos k p\u0159\u00edjemc\u016fm. Zde je t\u0159eba zav\u00e9st nov\u00fd pojem \u2014 root-path tree (RPT). RPT je strom s ko\u0159enem v RP, kter\u00fd roste sm\u011brem k p\u0159\u00edjemc\u016fm a v\u011btv\u00ed se na ka\u017ed\u00e9m PIM-SM routeru. RP jej vytv\u00e1\u0159\u00ed, kdy\u017e p\u0159ij\u00edm\u00e1 PIM Join zpr\u00e1vy, a p\u0159id\u00e1v\u00e1 do stromu novou v\u011btev. A tak pokra\u010duje ka\u017ed\u00fd ni\u017e\u0161\u00ed router. Obecn\u00e9 pravidlo zn\u00ed:<\/p>\n<ul>\n<li> Kdy\u017e PIM-SM router obdr\u017e\u00ed PIM Join zpr\u00e1vu na jak\u00e9mkoli rozhran\u00ed, krom\u011b rozhran\u00ed, za kter\u00fdm se skr\u00fdv\u00e1 RP, p\u0159id\u00e1 do stromu novou v\u011btev.<\/li>\n<li> V\u011btev je tak\u00e9 p\u0159id\u00e1na, kdy\u017e PIM-SM router obdr\u017e\u00ed IGMP Membership Report od p\u0159\u00edmo p\u0159ipojen\u00e9ho hostitele. <\/li>\n<\/ul>\n<p>\nP\u0159edstavme si, \u017ee m\u00e1me klienta multicastu na routeru R5 na skupin\u011b 228.8.8.8. Jakmile R5 obdr\u017e\u00ed IGMP Membership Report od hostitele, R5 ode\u0161le PIM Join sm\u011brem k RP a sama p\u0159id\u00e1 do stromu rozhran\u00ed sm\u011b\u0159uj\u00edc\u00ed k hostiteli. D\u00e1le R4 obdr\u017e\u00ed PIM Join od R5, p\u0159id\u00e1 do stromu rozhran\u00ed Gi0\/1 a ode\u0161le PIM Join sm\u011brem k RP. Nakonec RP (R3) obdr\u017e\u00ed PIM Join a p\u0159id\u00e1 Gi0\/0 do stromu. Takto se zaregistruje p\u0159\u00edjemce multicastu. Vytvo\u0159\u00edme strom s ko\u0159enem R3-Gi0\/0 \u2192 R4-Gi0\/1 \u2192 R5-Gi0\/0.<br \/>\nPo t\u00e9to f\u00e1zi bude odesl\u00e1n PIM Join k R1 a R1 za\u010dne pos\u00edlat multicastov\u00fd provoz. Je d\u016fle\u017eit\u00e9 si pov\u0161imnout, \u017ee pokud host po\u017e\u00e1dal o provoz, ne\u017e za\u010dalo vys\u00edl\u00e1n\u00ed multicastu, RP nebude odes\u00edlat PIM Join a vlastn\u011b nebude nic pos\u00edlat k R1.<br \/>\nPokud se n\u00e1hodou b\u011bhem odes\u00edl\u00e1n\u00ed multicastu host rozhodne, \u017ee ho u\u017e nechce p\u0159ij\u00edmat, jakmile RP obdr\u017e\u00ed PIM Prune na rozhran\u00ed Gi0\/0, okam\u017eit\u011b ode\u0161le PIM Register-Stop p\u0159\u00edmo na R1 a pot\u00e9 PIM Prune zpr\u00e1vu p\u0159es rozhran\u00ed Gi0\/1. PIM Register-Stop je odes\u00edl\u00e1n unicastem na tu adresu, ze kter\u00e9 p\u0159i\u0161el PIM Register.<br \/>\nJak jsme zm\u00ednili d\u0159\u00edve, jakmile router ode\u0161le PIM Join jin\u00e9mu, nap\u0159\u00edklad R5 na R4, na R4 se p\u0159id\u00e1 z\u00e1znam:<br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/msZjbr8.jpg\"><img decoding=\"async\" alt=\"Principy pr\u00e1ce protokolu PIM\" src=\"\/wp-content\/uploads\/2019\/05\/d1d621bee37e4b912a672690c581617a.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nA spust\u00ed se \u010dasova\u010d, kter\u00fd resetuje tento \u010dasova\u010d, R5 mus\u00ed nep\u0159etr\u017eit\u011b pos\u00edlat PIM Join zpr\u00e1vy, jinak R4 vylou\u010d\u00ed z outgoing list. R5 bude pos\u00edlat ka\u017ed\u00fdch 60 PIM Join zpr\u00e1vy.<br \/>\n<b>P\u0159epnut\u00ed Shortest-Path Tree.<\/b><br \/>\nP\u0159id\u00e1me rozhran\u00ed mezi R1 a R5 a pod\u00edv\u00e1me se, jak bude proudit provoz p\u0159i takov\u00e9 topologii. <br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/wLKEyyg.jpg\"><img decoding=\"async\" alt=\"Principy pr\u00e1ce protokolu PIM\" src=\"\/wp-content\/uploads\/2019\/05\/4b15057a1d30f3b2d6246b8f3b6263eb.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nP\u0159edpokl\u00e1dejme, \u017ee provoz byl odes\u00edl\u00e1n a p\u0159ij\u00edm\u00e1n podle star\u00e9ho sch\u00e9matu R1-R2-R3-R4-R5 a te\u010f jsme p\u0159ipojili a nastavili rozhran\u00ed mezi R1 a R5.<br \/>\nNejprve se n\u00e1m obnov\u00ed unicastov\u00e1 tabulka sm\u011brov\u00e1n\u00ed na R5 a nyn\u00ed je s\u00ed\u0165 192.168.1.0\/24 dosa\u017eena p\u0159es rozhran\u00ed R5 Gi0\/2. Nyn\u00ed, kdy\u017e R5 p\u0159ij\u00edm\u00e1 multicast na rozhran\u00ed Gi0\/1, si uv\u011bdomuje, \u017ee pravidlo RPF nen\u00ed spln\u011bno a multicast by m\u011bl b\u00fdt logi\u010dt\u011bj\u0161\u00ed p\u0159ij\u00edmat na Gi0\/2. M\u011bl by se odpojit od RPT a postavit krat\u0161\u00ed strom, kter\u00fd se naz\u00fdv\u00e1 Shortest-Path Tree (SPT). K tomu pos\u00edl\u00e1 p\u0159es Gi0\/2 PIM Join na R1 a R1 za\u010dne pos\u00edlat multicast tak\u00e9 p\u0159es Gi0\/2. Nyn\u00ed se mus\u00ed R5 odhl\u00e1sit z RPT, aby nedost\u00e1val dv\u011b kopie. K tomu pos\u00edl\u00e1 zpr\u00e1vu Prune, uv\u00e1d\u011bj\u00edc\u00ed IP adresu zdroje a vkl\u00e1d\u00e1 speci\u00e1ln\u00ed bit \u2014 RPT-bit. To znamen\u00e1, \u017ee mi nemus\u00edte pos\u00edlat provoz, m\u00e1m tady strom lep\u0161\u00ed. RP tak\u00e9 pos\u00edl\u00e1 sm\u011brem k R1 zpr\u00e1vy PIM Prune, ale nepos\u00edl\u00e1 zpr\u00e1vu Register-Stop. Je\u0161t\u011b jedna zvl\u00e1\u0161tnost: R5 nyn\u00ed bude neust\u00e1le pos\u00edlat PIM Prune na RP, proto\u017ee R1 pokra\u010duje v odes\u00edl\u00e1n\u00ed PIM Register na RP ka\u017edou minutu. RP zat\u00edm nebude m\u00edt nov\u00e9 z\u00e1jemce o tento provoz, a tak mu bude odpov\u00eddat odm\u00edtnut\u00edm. R5 informuje RP, \u017ee st\u00e1le p\u0159ij\u00edm\u00e1 multicast p\u0159es SPT.<br \/>\n<b>Dynamick\u00e9 hled\u00e1n\u00ed RP. <br \/>\nAuto-RP.<\/b><br \/>\nTato technologie je propriet\u00e1rn\u00ed od Cisco a nen\u00ed zvl\u00e1\u0161\u0165 popul\u00e1rn\u00ed, ale st\u00e1le existuje. Pr\u00e1ce Auto-RP se skl\u00e1d\u00e1 ze dvou z\u00e1kladn\u00edch f\u00e1z\u00ed:<br \/>\n1) RP pos\u00edl\u00e1 zpr\u00e1vy RP-Announce na vyhrazenou adresu \u2014 224.0.1.39, oznamuj\u00edc\u00ed se jako RP bu\u010f pro v\u0161echny, nebo pro ur\u010dit\u00e9 skupiny. Tato zpr\u00e1va se pos\u00edl\u00e1 ka\u017edou minutu.<br \/>\n2) Je t\u0159eba RP mapping agent, kter\u00fd bude pos\u00edlat zpr\u00e1vy RP-Discovery s informac\u00ed, pro jak\u00e9 skupiny je kter\u00fd RP t\u0159eba poslouchat. Pr\u00e1v\u011b z t\u00e9to zpr\u00e1vy standardn\u00ed PIM sm\u011brova\u010de zjist\u00ed, kter\u00fd RP maj\u00ed poslouchat. Mapping agent m\u016f\u017ee b\u00fdt bu\u010f samotn\u00fd RP sm\u011brova\u010d, nebo jin\u00fd nez\u00e1visl\u00fd PIM sm\u011brova\u010d. RP-Discovery je odes\u00edl\u00e1no na adresu 224.0.1.40 s \u010dasova\u010dem jedn\u00e9 minuty.<br \/>\nPod\u00edvejme se na proces podrobn\u011bji:<br \/>\nNastav\u00edme R3 jako RP:<\/p>\n<blockquote><p>ip pim send-rp-announce loopback 0 scope 10<\/p><\/blockquote>\n<p>\nR2 jako mapping agent:<\/p>\n<blockquote><p>ip pim send-rp-discovery loopback 0 scope 10<\/p><\/blockquote>\n<p>\nA na v\u0161ech ostatn\u00edch budeme \u010dekat na RP p\u0159es Auto-RP:<\/p>\n<blockquote><p>ip pim autorp listener<\/p><\/blockquote>\n<p>\nJakmile nastav\u00edme R3, za\u010dne pos\u00edlat RP-Announce:<br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/6c4WucN.jpg\"><img decoding=\"async\" alt=\"Principy pr\u00e1ce protokolu PIM\" src=\"\/wp-content\/uploads\/2019\/05\/3077778bb47731bb02a8e7fc6945aa63.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nA R2 po nastaven\u00ed jako mapping agent za\u010dne \u010dekat na zpr\u00e1vy RP-Announce. Pouze kdy\u017e najde alespo\u0148 jeden RP, za\u010dne pos\u00edlat RP-Discovery:<br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/lw2JuDD.jpg\"><img decoding=\"async\" alt=\"Principy pr\u00e1ce protokolu PIM\" src=\"\/wp-content\/uploads\/2019\/05\/37eff65f3c359cd3091c47af22220a6b.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nTak t\u00edmto zp\u016fsobem, jakmile standardn\u00ed sm\u011brova\u010de (PIM RP Listener) obdr\u017e\u00ed tuto zpr\u00e1vu, budou v\u011bd\u011bt, kde hledat RP.<br \/>\nJedn\u00edm z hlavn\u00edch probl\u00e9m\u016f Auto-RP je, \u017ee pro p\u0159\u00edjem zpr\u00e1v RP-Announce a RP-Discovery je t\u0159eba poslat PIM Join na adresy 224.0.1.39-40, a aby bylo mo\u017en\u00e9 poslat, je nutn\u00e9 v\u011bd\u011bt, kde se RP nach\u00e1z\u00ed. Klasick\u00fd probl\u00e9m slepice a vejce. Pro \u0159e\u0161en\u00ed tohoto probl\u00e9mu byl vymy\u0161len re\u017eim PIM Sparse-Dense-Mode. Pokud sm\u011brova\u010d nezn\u00e1 RP, pracuje v re\u017eimu Dense-mode, pokud v\u00ed, pak v re\u017eimu Sparse-mode. Kdy\u017e jsou na rozhran\u00edch standardn\u00edch sm\u011brova\u010d\u016f nastaveny PIM Sparse-mode a p\u0159\u00edkaz ip pim autorp listener, sm\u011brova\u010d bude pracovat v re\u017eimu Dense-mode pouze pro multicast Auto-RP protokolu (224.0.1.39-40).<br \/>\n<b>BootStrap Router (BSR).<\/b><br \/>\nTato funkce funguje podobn\u011b jako Auto-RP. Ka\u017ed\u00fd RP pos\u00edl\u00e1 zpr\u00e1vu mapping agentovi, kter\u00fd shroma\u017e\u010fuje mappingov\u00e9 informace a pot\u00e9 je sd\u011bluje v\u0161em ostatn\u00edm sm\u011brova\u010d\u016fm. Popi\u0161me proces obdobn\u011b jako u Auto-RP:<br \/>\n1) Jakmile nastav\u00edme R3 jako kandid\u00e1ta na RP, p\u0159\u00edkazem:<\/p>\n<blockquote><p>ip pim rp-candidate loopback 0<\/p><\/blockquote>\n<p>\nPak R3 nic ned\u011bl\u00e1, aby za\u010dal pos\u00edlat speci\u00e1ln\u00ed zpr\u00e1vy, mus\u00ed nejprve naj\u00edt mapping agenta. P\u0159ech\u00e1z\u00edme proto k druh\u00e9mu kroku.<br \/>\n2) Nastavujeme R2 jako mapping agent:<\/p>\n<blockquote><p>ip pim bsr-candidate loopback 0<\/p><\/blockquote>\n<p>\nR2 za\u010d\u00edn\u00e1 vys\u00edlat PIM Bootstrap zpr\u00e1vy, ve kter\u00fdch se ozna\u010duje jako mapping agent:<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/uAj49oT.jpg\"><img decoding=\"async\" alt=\"Principy pr\u00e1ce protokolu PIM\" src=\"\/wp-content\/uploads\/2019\/05\/2b05ffd64bd33ee5380aa24d5f76df67.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nTato zpr\u00e1va je pos\u00edl\u00e1na na adresu 224.0.0.13, kterou protokol PIM pou\u017e\u00edv\u00e1 i pro dal\u0161\u00ed sv\u00e9 zpr\u00e1vy. Odes\u00edl\u00e1 je do v\u0161ech sm\u011br\u016f, a proto nevznik\u00e1 probl\u00e9m s ku\u0159etem a vejcem, jak to bylo u Auto-RP.<br \/>\n3) Jakmile RP obdr\u017e\u00ed zpr\u00e1vu od BSR routeru, okam\u017eit\u011b ode\u0161le unicast zpr\u00e1vu na adresu BSR routeru:<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/qwtXY88.jpg\"><img decoding=\"async\" alt=\"Principy pr\u00e1ce protokolu PIM\" src=\"\/wp-content\/uploads\/2019\/05\/38547a114a2bca74131c95b95e535fdc.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nPo obdr\u017een\u00ed informace o RP, BSR je roze\u0161le multicast na adresu 224.0.0.13, kterou poslouchaj\u00ed v\u0161echny PIM routery. Proto neexistuje ekvivalent p\u0159\u00edkazu <i>ip pim autorp listener<\/i> pro b\u011b\u017en\u00e9 routery v BSR.<br \/>\n<b>Anycast RP s protokolem Multicast Source Discovery (MSDP).<\/b><br \/>\nAuto-RP a BSR n\u00e1m umo\u017e\u0148uj\u00ed rozlo\u017eit z\u00e1t\u011b\u017e na RP n\u00e1sleduj\u00edc\u00edm zp\u016fsobem: Ka\u017ed\u00e1 multicast skupina m\u00e1 jen jedno aktivn\u00ed RP. Nen\u00ed mo\u017en\u00e9 rozlo\u017eit z\u00e1t\u011b\u017e pro jednu multicast skupinu mezi v\u00edce RP. MSDP to d\u011bl\u00e1 poskytov\u00e1n\u00edm RP router\u016fm stejn\u00e9 ip adresy s maskou 255.255.255.255. MSDP z\u00edsk\u00e1v\u00e1 informace pomoc\u00ed jednoho z metod: statiky, Auto-RP nebo BSR.<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/U4aDz5H.png\"><img decoding=\"async\" alt=\"Principy pr\u00e1ce protokolu PIM\" src=\"\/wp-content\/uploads\/2019\/05\/c0352b5fbc5780f667c6c97ea6dde26d.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nNa obr\u00e1zku m\u00e1me konfiguraci Auto-RP s MSDP. Oba RP jsou nastaveny s ip adresou 172.16.1.1\/32 na rozhran\u00ed Loopback 1 a pou\u017e\u00edvaj\u00ed se pro v\u0161echny skupiny. P\u0159i RP-Announce oba routery informuj\u00ed o sob\u011b, odkazuj\u00edc na tuto adresu. Auto-RP mapping agent, po obdr\u017een\u00ed informac\u00ed, vys\u00edl\u00e1 RP-Discovery o RP s adresou 172.16.1.1\/32. O s\u00edti 172.16.1.1\/32 informujeme routery pomoc\u00ed IGP a t\u00edmto zp\u016fsobem. PIM routery requestuj\u00ed nebo registruj\u00ed toky od RP, kter\u00fd je uveden jako next-hop v cest\u011b k s\u00edti 172.16.1.1\/32. Samotn\u00fd protokol MSDP slou\u017e\u00ed pro RP, aby si vym\u011b\u0148ovaly informace o multicastu.<br \/>\nPod\u00edvejme se na takovou topologii:<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/i.imgur.com\/zgkGDOP.jpg\"><img decoding=\"async\" alt=\"Principy pr\u00e1ce protokolu PIM\" src=\"\/wp-content\/uploads\/2019\/05\/e4823362e7a2abc9b4ee9ba954d709b8.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\nSwitch6 vys\u00edl\u00e1 provoz na adresu 238.38.38.38 a prozat\u00edm o n\u011bm v\u00ed pouze RP-R1. Tady Switch7 a Switch8 po\u017e\u00e1dali o tuto skupinu. Routery R5 a R4 ode\u0161lou PIM Join na R1 a R3, respektive. Pro\u010d? Cesta k 13.13.13.13 u R5 bude odkazovat na R1 podle metriky IGP, stejn\u011b jako u R4.<br \/>\nRP-R1 v\u00ed o toku a za\u010dne ho vys\u00edlat sm\u011brem k R5, ale R4 o n\u011bm nic nev\u00ed, proto\u017ee R1 ho za norm\u00e1ln\u00edch podm\u00ednek nebude pos\u00edlat. Proto je nezbytn\u00fd MSDP. Nastavujeme ho na R1 a R5:<\/p>\n<blockquote><p>ip msdp peer 3.3.3.3 connect-source Loopback1 na R1<\/p><\/blockquote>\n<p><\/p>\n<blockquote><p>ip msdp peer 1.1.1.1 connect-source Loopback3 na R3<\/p><\/blockquote>\n<p>\nNav\u00e1\u017e\u00ed mezi sebou relaci a po obdr\u017een\u00ed jak\u00e9hokoli toku budou informovat sv\u00e9ho souseda RP.<br \/>\nRP-R1, jakmile p\u0159ijme tok od Switch6, okam\u017eit\u011b ode\u0161le unicast zpr\u00e1vu MSDP Source-Active, kter\u00e1 bude obsahovat informace typu (S, G) \u2014 informace o zdroji a c\u00edli multicastu. Nyn\u00ed, kdy\u017e RP-R3 v\u00ed, \u017ee existuje takov\u00fd zdroj jako Switch6, p\u0159i obdr\u017een\u00ed \u017e\u00e1dosti od R4 o tento tok, ode\u0161le sm\u011brem k Switch6 PIM Join podle sm\u011brovac\u00ed tabulky. T\u00edm p\u00e1dem R1, kter\u00fd obdr\u017e\u00ed tento PIM Join, za\u010dne sm\u011brovat provoz sm\u011brem k RP-R3.<br \/>\nMSDP funguje p\u0159es TCP, RP si vz\u00e1jemn\u011b pos\u00edlaj\u00ed keepalive zpr\u00e1vy pro kontrolu \u017eivotaschopnosti. \u010casova\u010d je nastaven na 60 sekund.<br \/>\nFunkce rozd\u011blen\u00ed MSDP peer\u016f do r\u016fzn\u00fdch dom\u00e9n z\u016fst\u00e1v\u00e1 nejasn\u00e1, proto\u017ee v keepalive a SA zpr\u00e1v\u00e1ch nen\u00ed uvedena p\u0159\u00edslu\u0161nost k jak\u00e9koli dom\u00e9n\u011b. V t\u00e9to topologii byla tak\u00e9 testov\u00e1na konfigurace s uveden\u00edm r\u016fzn\u00fdch dom\u00e9n \u2014 nebyl zaznamen\u00e1n \u017e\u00e1dn\u00fd rozd\u00edl v provozu. <br \/>\nPokud n\u011bkdo m\u016f\u017ee objasnit, r\u00e1d si p\u0159e\u010dtu v koment\u00e1\u0159\u00edch.<br \/>\n<br \/>Zdroj: <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.3 - 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\/cs\/blog\/administrirovanie\/printsipy-raboty-protokola-pim\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\n\t\t<meta property=\"og:locale\" content=\"cs_CZ\" \/>\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\/cs\/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\udd47Principy fungov\u00e1n\u00ed protokolu PIM | ProHoster","description":"Protokol PIM je soubor protokol\u016f pro p\u0159enos multicastu v s\u00edti mezi sm\u011brova\u010di. Vztahy sousedstv\u00ed se vytv\u00e1\u0159ej\u00ed podobn\u011b jako v p\u0159\u00edpad\u011b dynamick\u00fdch sm\u011brovac\u00edch protokol\u016f.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/printsipy-raboty-protokola-pim","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","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\/cs\/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\/cs\/wp-json\/wp\/v2\/posts\/33142","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=33142"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/33142\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/24886"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=33142"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=33142"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=33142"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}