{"id":77041,"date":"2020-04-07T13:42:46","date_gmt":"2020-04-07T11:42:46","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/podrobnosti-realizaczii-protokola-sinhronizaczii-vremeni-ptpv2"},"modified":"2020-04-07T13:42:46","modified_gmt":"2020-04-07T11:42:46","slug":"podrobnosti-realizaczii-protokola-sinhronizaczii-vremeni-ptpv2","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/podrobnosti-realizaczii-protokola-sinhronizaczii-vremeni-ptpv2","title":{"rendered":"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><b>\u00davod<\/b><\/p>\n<p>Koncept budov\u00e1n\u00ed \"Digit\u00e1ln\u00ed podstanice\" v elektroenergetice vy\u017eaduje synchronizaci s p\u0159esnost\u00ed 1 \u03bcs. Pro prov\u00e1d\u011bn\u00ed finan\u010dn\u00edch transakc\u00ed je tak\u00e9 pot\u0159ebn\u00e1 p\u0159esnost v \u03bcs. V t\u011bchto aplikac\u00edch u\u017e nen\u00ed \u010dasov\u00e1 p\u0159esnost NTP dostate\u010dn\u00e1.<\/p>\n<p>Protokol synchronizace PTPv2, popsan\u00fd standardem IEEE 1588v2, umo\u017e\u0148uje dos\u00e1hnout p\u0159esnosti synchronizace na n\u011bkolik des\u00edtek nanosekund. PTPv2 umo\u017e\u0148uje pos\u00edlat synchroniza\u010dn\u00ed pakety p\u0159es L2 a L3 s\u00edt\u011b.<\/p>\n<p>Hlavn\u00edmi oblastmi, kde se PTPv2 uplat\u0148uje, jsou:<\/p>\n<ul>\n<li>energetika;<\/li>\n<li>m\u011b\u0159ic\u00ed a \u0159\u00eddic\u00ed za\u0159\u00edzen\u00ed;<\/li>\n<li>obrann\u00fd a pr\u016fmyslov\u00fd komplex;<\/li>\n<li>telekomunikace;<\/li>\n<li>finan\u010dn\u00ed sektor.<\/li>\n<\/ul>\n<p>\nV tomto p\u0159\u00edsp\u011bvku se zab\u00fdv\u00e1me t\u00edm, jak pracuje protokol synchronizace PTPv2.<\/p>\n<p>M\u00e1me v\u00edce zku\u0161enost\u00ed v pr\u016fmyslu a \u010dasto se s t\u00edmto protokolem setk\u00e1v\u00e1me v energetick\u00fdch aplikac\u00edch. Odpov\u00eddaj\u00edc\u00edm zp\u016fsobem provedeme p\u0159ehled souvisej\u00edc\u00ed <noindex><a rel=\"nofollow\" href=\"https:\/\/www.phoenixcontact.com\/online\/portal\/ru?1dmy&amp;urile=wcm%3apath%3a\/ruru\/web\/main\/products\/subcategory_pages\/Managed_switches_P-08-10-16-01\/aead25f7-3319-485d-8868-126c62b77cb1\">s energetikou<\/a><\/noindex>.<\/p>\n<p><b>Pro\u010d je to nezbytn\u00e9?<\/b><\/p>\n<p>V sou\u010dasnosti obsahuj\u00ed normy STO 34.01-21-004-2019 PAO \"Rosseti\" a STO 56947007-29.240.10.302-2020 PAO \"FSK EES\" po\u017eadavky na organizaci procesn\u00ed sb\u011brnice s zaji\u0161t\u011bn\u00edm synchronizace \u010dasu pomoc\u00ed PTPv2.<\/p>\n<p>To souvis\u00ed s t\u00edm, \u017ee k procesn\u00ed sb\u011brnici se p\u0159ipojuj\u00ed termin\u00e1ly rel\u00e9ov\u00e9 ochrany a m\u011b\u0159ic\u00ed za\u0159\u00edzen\u00ed, kter\u00e9 prost\u0159ednictv\u00edm procesn\u00ed sb\u011brnice pomoc\u00ed takzvan\u00fdch SV tok\u016f (multicast toky) p\u0159en\u00e1\u0161ej\u00ed okam\u017eit\u00e9 hodnoty proudu a nap\u011bt\u00ed.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>Termin\u00e1ly rel\u00e9ov\u00e9 ochrany pou\u017e\u00edvaj\u00ed tyto hodnoty k realizaci ochrany p\u0159ipojen\u00ed. Pokud bude p\u0159esnost m\u011b\u0159en\u00ed \u010dasu n\u00edzk\u00e1, n\u011bkter\u00e9 ochrany mohou chybn\u011b reagovat.<\/p>\n<p>Nap\u0159\u00edklad ob\u011bt\u00ed \"slab\u00e9\" synchronizace \u010dasu mohou b\u00fdt ochrany absolutn\u00ed selektivity. \u010casto je logika podobn\u00fdch ochran postavena na srovn\u00e1n\u00ed dvou hodnot. Pokud se hodnoty dostate\u010dn\u011b li\u0161\u00ed, ochrana se spust\u00ed. Pokud tyto hodnoty zm\u011b\u0159\u00edte s p\u0159esnost\u00ed 1 ms, m\u016f\u017eete z\u00edskat velk\u00fd rozd\u00edl tam, kde se hodnoty ve skute\u010dnosti nach\u00e1zej\u00ed v norm\u011b, pokud je zm\u011b\u0159\u00edte s p\u0159esnost\u00ed 1 \u03bcs.<\/p>\n<p><b>Verze PTP<\/b><\/p>\n<p>Protokol PTP byl poprv\u00e9 pops\u00e1n v roce 2002 ve standardu IEEE 1588-2002 a m\u011bl n\u00e1zev \u201eStandard pro protokol synchronizace p\u0159esn\u00e9ho \u010dasu pro s\u00ed\u0165ov\u00e9 m\u011b\u0159en\u00ed a \u0159\u00edd\u00edc\u00ed syst\u00e9my\u201c. V roce 2008 byl vyd\u00e1n aktualizovan\u00fd standard IEEE 1588-2008, kter\u00fd popisuje PTP verze 2. V t\u00e9to verzi protokolu byla vylep\u0161ena p\u0159esnost a stabilita, ale nebyla zachov\u00e1na zp\u011btn\u00e1 kompatibilita s prvn\u00ed verz\u00ed protokolu. Tak\u00e9 v roce 2019 vy\u0161la verze standardu IEEE 1588-2019, kter\u00e1 popisuje PTP v2.1. Tato verze p\u0159id\u00e1v\u00e1 drobn\u00e1 vylep\u0161en\u00ed k PTPv2 a je zp\u011btn\u011b kompatibiln\u00ed s PTPv2.<\/p>\n<p>Jin\u00fdmi slovy, m\u00e1me n\u00e1sleduj\u00edc\u00ed obr\u00e1zek s verzemi:<\/p>\n<p>PTPv1<br \/>\n(IEEE 1588-2002)<\/p>\n<p>PTPv2<br \/>\n(IEEE 1588-2008)<\/p>\n<p>PTPv2.1<br \/>\n(IEEE 1588-2019)<\/p>\n<p>PTPv1 (IEEE 1588-2002)<\/p>\n<p> \u2014<br \/>\nNejsou kompatibiln\u00ed<\/p>\n<p>Nejsou kompatibiln\u00ed<\/p>\n<p>PTPv2 (IEEE 1588-2008)<\/p>\n<p>Nejsou kompatibiln\u00ed<\/p>\n<p> \u2014<br \/>\nJsou kompatibiln\u00ed<\/p>\n<p>PTPv2.1 (IEEE 1588-2019)<\/p>\n<p>Nejsou kompatibiln\u00ed<\/p>\n<p>Jsou kompatibiln\u00ed<\/p>\n<p> \u2014 <\/p>\n<p>\nAle, jak u\u017e to b\u00fdv\u00e1, jsou tu nuance.<\/p>\n<p>Nekompatibilita mezi PTPv1 a PTPv2 znamen\u00e1, \u017ee za\u0159\u00edzen\u00ed podporuj\u00edc\u00ed PTPv1 se nebude moci synchronizovat s p\u0159esn\u00fdmi hodinami, kter\u00e9 b\u011b\u017e\u00ed na PTPv2. Pro synchronizaci pou\u017e\u00edvaj\u00ed r\u016fzn\u00e9 form\u00e1ty zpr\u00e1v.<\/p>\n<p>Ale propojit za\u0159\u00edzen\u00ed s PTPv1 a za\u0159\u00edzen\u00ed s PTPv2 v jedn\u00e9 s\u00edti je p\u0159esto mo\u017en\u00e9. N\u011bkte\u0159\u00ed v\u00fdrobci umo\u017e\u0148uj\u00ed na portech hrani\u010dn\u00edch hodin vyb\u00edrat verzi protokolu. To znamen\u00e1, \u017ee hrani\u010dn\u00ed hodiny se mohou synchronizovat pomoc\u00ed PTPv2 a z\u00e1rove\u0148 synchronizovat dal\u0161\u00ed p\u0159ipojen\u00e9 hodiny jak s PTPv1, tak s PTPv2.<\/p>\n<p><b>Za\u0159\u00edzen\u00ed PTP. Jak\u00e9 jsou a v \u010dem se li\u0161\u00ed?<\/b><\/p>\n<p>Standard IEEE 1588v2 popisuje n\u011bkolik typ\u016f za\u0159\u00edzen\u00ed. V\u0161echna jsou uvedena v tabulce.<\/p>\n<p>Za\u0159\u00edzen\u00ed vz\u00e1jemn\u011b komunikuj\u00ed p\u0159es LAN pomoc\u00ed PTP.<\/p>\n<p>Za\u0159\u00edzen\u00ed PTP se naz\u00fdvaj\u00ed hodiny. V\u0161echny hodiny z\u00edsk\u00e1vaj\u00ed p\u0159esn\u00fd \u010das od grandmaster hodin.<\/p>\n<p>Existuje 5 typ\u016f hodin:<\/p>\n<p>Grandmaster clock (Grandmaster hodiny)<\/p>\n<p>Hlavn\u00ed zdroj p\u0159esn\u00e9ho \u010dasu. \u010casto jsou vybaveny rozhran\u00edm pro p\u0159ipojen\u00ed GPS.<\/p>\n<p>Ordinary Clock (B\u011b\u017en\u00e9 hodiny)<\/p>\n<p>Za\u0159\u00edzen\u00ed s jedn\u00edm portem, kter\u00e9 m\u016f\u017ee b\u00fdt mistrem (vedouc\u00edmi hodinami) nebo sl\u00e1vou (pod\u0159\u00edzen\u00fdmi hodinami)<\/p>\n<p>Mistr (vedouc\u00ed hodiny)<\/p>\n<p>Jsou zdrojem p\u0159esn\u00e9ho \u010dasu, podle kter\u00e9ho se synchronizuj\u00ed dal\u0161\u00ed hodiny<\/p>\n<p>Pod\u0159\u00edzen\u00e9 hodiny (slave)<\/p>\n<p>Kone\u010dn\u00e9 za\u0159\u00edzen\u00ed, kter\u00e9 se synchronizuje s mistrovsk\u00fdmi hodinami<\/p>\n<p>Boundary Clock (Hrani\u010dn\u00ed hodiny)<\/p>\n<p>Za\u0159\u00edzen\u00ed s n\u011bkolika porty, kter\u00e9 m\u016f\u017ee b\u00fdt mistrem nebo slavn\u00fdm.<\/p>\n<p>To znamen\u00e1, \u017ee tyto hodiny se mohou synchronizovat s vy\u0161\u0161\u00edmi mistrovsk\u00fdmi hodinami a synchronizovat ni\u017e\u0161\u00ed pod\u0159\u00edzen\u00e9 hodiny.<\/p>\n<p>Pr\u016fhledn\u00e9 hodiny funguj\u00edc\u00ed v re\u017eimu End-to-End<\/p>\n<p>Za\u0159\u00edzen\u00ed s n\u011bkolika porty, kter\u00e9 nen\u00ed ani hlavn\u00edmi hodinami, ani pod\u0159\u00edzen\u00fdmi hodinama. P\u0159en\u00e1\u0161\u00ed data PTP mezi dv\u011bma hodinami. <\/p>\n<p>P\u0159i p\u0159enosu dat pr\u016fhledn\u00e9 hodiny opravuj\u00ed v\u0161echny PTP zpr\u00e1vy. <\/p>\n<p>Oprava prob\u00edh\u00e1 p\u0159id\u00e1n\u00edm \u010dasov\u00e9ho zpo\u017ed\u011bn\u00ed na tomto za\u0159\u00edzen\u00ed do pole korekce v hlavi\u010dce p\u0159en\u00e1\u0161en\u00e9 zpr\u00e1vy.<\/p>\n<p>Pr\u016fhledn\u00e9 hodiny funguj\u00edc\u00ed v re\u017eimu Peer-to-Peer<\/p>\n<p>Za\u0159\u00edzen\u00ed s n\u011bkolika porty, kter\u00e9 nen\u00ed ani hlavn\u00edmi hodinami, ani pod\u0159\u00edzen\u00fdmi hodinama. <br \/>\nP\u0159en\u00e1\u0161\u00ed data PTP mezi dv\u011bma hodinami. <\/p>\n<p>P\u0159i p\u0159enosu dat pr\u016fhledn\u00e9 hodiny opravuj\u00ed v\u0161echny PTP zpr\u00e1vy Sync a Follow_Up (o kter\u00fdch bude podrobn\u011bji \u0159e\u010d n\u00ed\u017ee).<\/p>\n<p>Oprava se dosahuje p\u0159id\u00e1n\u00edm zpo\u017ed\u011bn\u00ed na p\u0159ed\u00e1vaj\u00edc\u00edm za\u0159\u00edzen\u00ed a zpo\u017ed\u011bn\u00ed na datov\u00e9m kan\u00e1lu do pole korekce p\u0159en\u00e1\u0161en\u00e9ho bal\u00ed\u010dku.<\/p>\n<p>\u0158\u00eddic\u00ed uzel<\/p>\n<p>Za\u0159\u00edzen\u00ed, kter\u00e9 konfiguruje a diagnostikuje ostatn\u00ed hodiny<\/p>\n<p>Hlavn\u00ed a pod\u0159\u00edzen\u00e9 hodiny se synchronizuj\u00ed pomoc\u00ed \u010dasov\u00fdch zna\u010dek v PTP zpr\u00e1v\u00e1ch. Existuj\u00ed dva typy zpr\u00e1v v PTP protokolu:<\/p>\n<ul>\n<li>Event Messages \u2013 jedn\u00e1 se o synchronizovan\u00e9 zpr\u00e1vy, kter\u00e9 p\u0159edpokl\u00e1daj\u00ed vygenerov\u00e1n\u00ed \u010dasov\u00e9 zna\u010dky p\u0159i odesl\u00e1n\u00ed zpr\u00e1vy a p\u0159i jej\u00edm p\u0159ijet\u00ed<\/li>\n<li>General Messages \u2013 tyto zpr\u00e1vy nemus\u00ed obsahovat \u010dasov\u00e9 zna\u010dky, ale mohou obsahovat \u010dasov\u00e9 zna\u010dky pro souvisej\u00edc\u00ed zpr\u00e1vy<\/li>\n<\/ul>\n<p><\/p>\n<p>Event Messages<\/p>\n<p>General Messages<\/p>\n<p>Sync<br \/>\nDelay_Req<br \/>\nPdelay_Req<br \/>\nPdelay_Resp<\/p>\n<p>Announce<br \/>\nFollow_Up<br \/>\nDelay_Resp<br \/>\nPdelay_Resp_Follow_Up<br \/>\nManagement<br \/>\nSignaling<\/p>\n<p>Nyn\u00ed budou podrobn\u011bji probr\u00e1ny v\u0161echny typy zpr\u00e1v.<\/p>\n<p><b>Hlavn\u00ed probl\u00e9my synchronizace<\/b><\/p>\n<p>P\u0159i p\u0159enosu synchroniza\u010dn\u00edho bal\u00ed\u010dku p\u0159es m\u00edstn\u00ed s\u00ed\u0165 je zpo\u017ed\u011bn na p\u0159ep\u00edna\u010di a v datov\u00e9m kan\u00e1lu. Ka\u017ed\u00fd p\u0159ep\u00edna\u010d vytvo\u0159\u00ed zpo\u017ed\u011bn\u00ed okolo 10 \u03bcs, co\u017e je pro PTPv2 nep\u0159ijateln\u00e9. Na koncov\u00e9m za\u0159\u00edzen\u00ed pot\u0159ebujeme dos\u00e1hnout p\u0159esnosti 1 \u03bcs. (To se vztahuje na energetiku. Jin\u00e1 aplikace mohou vy\u017eadovat i v\u011bt\u0161\u00ed p\u0159esnost.)<\/p>\n<p>V IEEE 1588v2 je pops\u00e1no n\u011bkolik pracovn\u00edch algoritm\u016f, kter\u00e9 umo\u017e\u0148uj\u00ed m\u011b\u0159it \u010dasov\u00e9 zpo\u017ed\u011bn\u00ed a opravovat jej.<\/p>\n<p><b>Algoritmus pr\u00e1ce<\/b><br \/>\nP\u0159i norm\u00e1ln\u00edm chodu protokol pracuje ve dvou f\u00e1z\u00edch.<\/p>\n<ul>\n<li>F\u00e1ze 1 \u2014 stanoven\u00ed hierarchie \u201eHlavn\u00ed hodiny \u2013 Pod\u0159\u00edzen\u00e9 hodiny\u201c.<\/li>\n<li>F\u00e1ze 2 \u2014 synchronizace hodin pomoc\u00ed mechanismu End-to-End nebo Peer-to-Peer.<\/li>\n<\/ul>\n<p>\n<i>F\u00e1ze 1 \u2014 Instalace hierarchie \u201eMaster-Slave\u201c<\/i><\/p>\n<p>Ka\u017ed\u00fd port b\u011b\u017en\u00fdch nebo hrani\u010dn\u00edch hodin m\u00e1 ur\u010dit\u00e9 mno\u017estv\u00ed stav\u016f (pod\u0159\u00edzen\u00e9 hodiny a vedouc\u00ed hodiny). Standard definuje algoritmus p\u0159echodu mezi t\u011bmito stavy. V programov\u00e1n\u00ed se tento algoritmus naz\u00fdv\u00e1 kone\u010dn\u00fd automat nebo stavov\u00fd stroj (v\u00edce v Wiki).<\/p>\n<p>Tento kone\u010dn\u00fd automat pou\u017e\u00edv\u00e1 algoritmus Best Master Clock Algorithm (BMCA) na ur\u010den\u00ed mistra p\u0159i spojen\u00ed dvou hodin.<\/p>\n<p>Tento algoritmus umo\u017e\u0148uje hodin\u00e1m p\u0159evz\u00edt povinnosti grandsmaster hodin, kdy\u017e vy\u0161\u0161\u00ed grandsmaster hodin ztr\u00e1c\u00ed sign\u00e1l GPS, odpojuje se od s\u00edt\u011b atd.<\/p>\n<p>P\u0159echody mezi stavy podle BMCA jsou stru\u010dn\u011b zn\u00e1zorn\u011bny na n\u00e1sleduj\u00edc\u00ed sch\u00e9matu:<br \/>\n<img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/add811d60135de3be9c6865a5e4493c1.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nInformace o hodin\u00e1ch na druh\u00e9m konci \u201ekabelu\u201c jsou zas\u00edl\u00e1ny ve speci\u00e1ln\u00ed zpr\u00e1v\u011b (Announce message). Jakmile jsou tyto informace obdr\u017eeny, algoritmus stavov\u00e9ho stroje vyhodnocuje a porovn\u00e1v\u00e1, kter\u00e9 hodiny jsou lep\u0161\u00ed. Port na nejlep\u0161\u00edch hodin\u00e1ch se st\u00e1v\u00e1 vedouc\u00edmi hodinami.<\/p>\n<p>Jednoduch\u00e1 hierarchie je zn\u00e1zorn\u011bna na sch\u00e9matu n\u00ed\u017ee. Cesty 1, 2, 3, 4, 5 mohou obsahovat transparentn\u00ed hodiny (Transparent clock), ale ne\u00fa\u010dastn\u00ed se ustaven\u00ed hierarchie \u201eVedouc\u00ed hodiny \u2013 Pod\u0159\u00edzen\u00e9 hodiny\u201c.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/05831c032a2d4df286ef41c531c949a3.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>F\u00e1ze 2 \u2014 Synchronizace b\u011b\u017en\u00fdch a hrani\u010dn\u00edch hodin<\/b><\/p>\n<p>Ihned po instalaci hierarchie \u201eVedouc\u00ed hodiny \u2013 Pod\u0159\u00edzen\u00e9 hodiny\u201c za\u010d\u00edn\u00e1 f\u00e1ze synchronizace b\u011b\u017en\u00fdch a hrani\u010dn\u00edch hodin.<\/p>\n<p>Pro synchronizaci vedouc\u00ed hodiny pos\u00edlaj\u00ed pod\u0159\u00edzen\u00fdm hodin\u00e1m zpr\u00e1vu obsahuj\u00edc\u00ed \u010dasovou zna\u010dku.<\/p>\n<p>Vedouc\u00ed hodiny mohou b\u00fdt:<\/p>\n<ul>\n<li>jednostup\u0148ov\u00e9;<\/li>\n<li>dvoustup\u0148ov\u00e9.<\/li>\n<\/ul>\n<p>\nJednostup\u0148ov\u00e9 hodiny pos\u00edlaj\u00ed pro synchronizaci jednu zpr\u00e1vu Sync.<\/p>\n<p>Dvoustup\u0148ov\u00e9 hodiny pro synchronizaci pou\u017e\u00edvaj\u00ed dv\u011b zpr\u00e1vy \u2013 Sync a Follow_Up.<\/p>\n<p>Pro f\u00e1zi synchronizace mohou b\u00fdt pou\u017eity dva mechanizmy:<\/p>\n<ul>\n<li>Mechanismus \u017e\u00e1dosti-o-v\u011bt\u0161inu zpo\u017ed\u011bn\u00ed (Delay request-response mechanism).<\/li>\n<li>Mechanismus m\u011b\u0159en\u00ed zpo\u017ed\u011bn\u00ed sousedn\u00edho uzlu (Peer delay measurement mechanism).<\/li>\n<\/ul>\n<p>\nNejprve se pod\u00edv\u00e1me na tyto mechanizmy v nejjednodu\u0161\u0161\u00edm p\u0159\u00edpad\u011b \u2013 kdy\u017e nejsou pou\u017eity transparentn\u00ed hodiny.<\/p>\n<p>Mechanismus \u017e\u00e1dosti-o-v\u011bt\u0161inu zpo\u017ed\u011bn\u00ed (Delay request-response mechanism)<\/p>\n<p>Mechanismus p\u0159edpokl\u00e1d\u00e1 dva kroky:<\/p>\n<ol>\n<li>M\u011b\u0159en\u00ed zpo\u017ed\u011bn\u00ed p\u0159i p\u0159enosu zpr\u00e1vy mezi vedouc\u00edmi a pod\u0159\u00edzen\u00fdmi hodinami. To se prov\u00e1d\u00ed pomoc\u00ed mechanizmu \u017e\u00e1dosti-o-v\u011bt\u0161inu zpo\u017ed\u011bn\u00ed.<\/li>\n<li>Prov\u00e1d\u00ed se korekce posunu p\u0159esn\u00e9ho \u010dasu.<\/li>\n<\/ol>\n<p>\n<i>M\u011b\u0159en\u00ed zpo\u017ed\u011bn\u00ed<\/i><br \/>\n<img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/3a0d534384329c6232259736995eb0bd.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nt1 \u2013 \u010cas odesl\u00e1n\u00ed zpr\u00e1vy Sync vedouc\u00edmi hodinami; t2 \u2013 \u010cas p\u0159ijet\u00ed zpr\u00e1vy Sync pod\u0159\u00edzen\u00fdmi hodinami; t3 \u2013 \u010cas odesl\u00e1n\u00ed dotazu na zpo\u017ed\u011bn\u00ed (Delay_Req) pod\u0159\u00edzen\u00fdmi hodinami; t4 \u2013 \u010cas p\u0159ijet\u00ed Delay_Req vedouc\u00edmi hodinami.<\/p>\n<p>Kdy\u017e pod\u0159\u00edzen\u00e9 hodiny znaj\u00ed \u010dasy t1, t2, t3 a t4, mohou vypo\u010d\u00edtat pr\u016fm\u011brn\u00e9 zpo\u017ed\u011bn\u00ed p\u0159i p\u0159enosu zpr\u00e1vy synchronizace (tmpd). Vypo\u010d\u00edt\u00e1v\u00e1 se n\u00e1sleduj\u00edc\u00edm zp\u016fsobem:<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/513eb7352a143073835fe36aedd9cb98.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nP\u0159i p\u0159enosu zpr\u00e1vy Sync a Follow_Up se vypo\u010d\u00edt\u00e1v\u00e1 zpo\u017ed\u011bn\u00ed \u010dasu od masteru k slaveovi \u2013 t-ms.<\/p>\n<p>P\u0159i p\u0159enosu zpr\u00e1v Delay_Req a Delay_Resp se vypo\u010d\u00edt\u00e1v\u00e1 zpo\u017ed\u011bn\u00ed \u010dasu od slavea k masteru \u2013 t-sm.<\/p>\n<p>Pokud mezi t\u011bmito dv\u011bma hodnotami vznikne n\u011bjak\u00e1 asymetrie, objev\u00ed se chyba v korekci odchylek p\u0159esn\u00e9ho \u010dasu. Chyba je zp\u016fsobena t\u00edm, \u017ee vypo\u010d\u00edtan\u00e9 zpo\u017ed\u011bn\u00ed je pr\u016fm\u011brem zpo\u017ed\u011bn\u00ed t-ms a t-sm. Pokud se zpo\u017ed\u011bn\u00ed neshoduj\u00ed, budeme \u010das korigovat nep\u0159esn\u011b.<\/p>\n<p><i>Korekce odchylky p\u0159esn\u00e9ho \u010dasu<\/i><\/p>\n<p>Jakmile je zpo\u017ed\u011bn\u00ed mezi vedouc\u00edmi hodinami a pod\u0159\u00edzen\u00fdmi hodinami zn\u00e1mo, pod\u0159\u00edzen\u00e9 hodiny prov\u00e1d\u011bj\u00ed korekci \u010dasu.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/27f230252126a768273b40e8c8e7cc4e.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPod\u0159\u00edzen\u00e9 hodiny pou\u017e\u00edvaj\u00ed zpr\u00e1vu Sync a volitelnou zpr\u00e1vu Follow_Up k v\u00fdpo\u010dtu odchylky p\u0159esn\u00e9ho \u010dasu p\u0159i p\u0159enosu paketu od vedouc\u00edch hodin k pod\u0159\u00edzen\u00fdm. Odchylka se vypo\u010d\u00edt\u00e1v\u00e1 podle n\u00e1sleduj\u00edc\u00edho vzorce:<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/190604a9287f285e191eb26381fca52c.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Mechanismus m\u011b\u0159en\u00ed zpo\u017ed\u011bn\u00ed sousedn\u00edho uzlu (Peer delay measurement mechanism)<\/b><\/p>\n<p>Tento mechanismus tak\u00e9 vyu\u017e\u00edv\u00e1 dva kroky pro synchronizaci:<\/p>\n<ol>\n<li>Za\u0159\u00edzen\u00ed m\u011b\u0159\u00ed zpo\u017ed\u011bn\u00ed \u010dasu do v\u0161ech soused\u016f p\u0159es v\u0161echny porty. K tomu vyu\u017e\u00edvaj\u00ed mechanizmus m\u011b\u0159en\u00ed zpo\u017ed\u011bn\u00ed soused\u016f.<\/li>\n<li>Korekce odchylky p\u0159esn\u00e9ho \u010dasu.<\/li>\n<\/ol>\n<p>\n<i>M\u011b\u0159en\u00ed zpo\u017ed\u011bn\u00ed mezi za\u0159\u00edzen\u00edmi, kter\u00e1 podporuj\u00ed re\u017eim Peer-to-Peer<\/i><\/p>\n<p>Zpo\u017ed\u011bn\u00ed mezi porty, kter\u00e9 podporuj\u00ed mechanismus peer-to-peer, je m\u011b\u0159eno pomoc\u00ed n\u00e1sleduj\u00edc\u00edch zpr\u00e1v:<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/897c9914110e9a56f98f4fa835f524cd.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKdy\u017e portu 1 je zn\u00e1mo \u010das t1, t2, t3 a t4, m\u016f\u017ee vypo\u010d\u00edtat pr\u016fm\u011brn\u00e9 zpo\u017ed\u011bn\u00ed (tmld). Vypo\u010d\u00edt\u00e1v\u00e1 se podle n\u00e1sleduj\u00edc\u00edho vzorce:<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/17416bf3b60f86136002b27cf4987b27.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nN\u00e1sledn\u011b port pou\u017e\u00edv\u00e1 tuto hodnotu p\u0159i v\u00fdpo\u010dtu pole korekce pro ka\u017edou zpr\u00e1vu Sync nebo volitelnou zpr\u00e1vu Follow_Up, kter\u00e9 proch\u00e1zej\u00ed p\u0159es toto za\u0159\u00edzen\u00ed. <\/p>\n<p>Kone\u010dn\u00e9 zpo\u017ed\u011bn\u00ed bude rovno sou\u010dtu zpo\u017ed\u011bn\u00ed p\u0159i p\u0159enosu p\u0159es toto za\u0159\u00edzen\u00ed, pr\u016fm\u011brn\u00e9mu zpo\u017ed\u011bn\u00ed p\u0159i p\u0159enosu p\u0159es datov\u00fd kan\u00e1l a ji\u017e existuj\u00edc\u00edmu zpo\u017ed\u011bn\u00ed v t\u00e9to zpr\u00e1v\u011b, zahrnut\u00e9mu na vy\u0161\u0161\u00edch za\u0159\u00edzen\u00edch.<\/p>\n<p>Zpr\u00e1vy Pdelay_Req, Pdelay_Resp a voliteln\u00fd Pdelay_Resp_Follow_Up umo\u017e\u0148uj\u00ed z\u00edskat zpo\u017ed\u011bn\u00ed od masteru k slave a od slave k masteru (kruhov\u00e9).<\/p>\n<p>Jak\u00e1koli asymetrie mezi t\u011bmito dv\u011bma hodnotami povede k chyb\u011b v korekci posunu p\u0159esn\u00e9ho \u010dasu.<\/p>\n<p><i>Korekce posunu p\u0159esn\u00e9ho \u010dasu<\/i><\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/c9cdedffd98db044718b8bc0eef156b9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPod\u0159\u00edzen\u00e9 hodiny pou\u017e\u00edvaj\u00ed zpr\u00e1vu Sync a volitelnou zpr\u00e1vu Follow_Up k v\u00fdpo\u010dtu posunu p\u0159esn\u00e9ho \u010dasu p\u0159i p\u0159enosu paketu od hlavn\u00edch hodin k pod\u0159\u00edzen\u00fdm. Posun se vypo\u010d\u00edt\u00e1v\u00e1 podle n\u00e1sleduj\u00edc\u00edho vzorce:<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/dff497d0f5644c3591f05f99e4c8c23a.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nV\u00fdhody korek\u010dn\u00edho mechanismu peer-to-peer \u2013 zpo\u017ed\u011bn\u00ed ka\u017ed\u00e9 zpr\u00e1vy Sync nebo Follow_Up se vypo\u010d\u00edt\u00e1v\u00e1 b\u011bhem jej\u00edho p\u0159enosu v s\u00edti. Proto zm\u011bna cesty p\u0159enosu neovlivn\u00ed p\u0159esnost korekce jak\u00fdmikoliv zp\u016fsobem.<\/p>\n<p>P\u0159i pou\u017eit\u00ed tohoto mechanismu synchronizace \u010dasu nen\u00ed pot\u0159eba vypo\u010d\u00edt\u00e1vat zpo\u017ed\u011bn\u00ed \u010dasu na cest\u011b, kterou paket synchronizace pro\u0161el, jak je to obvykl\u00e9 p\u0159i z\u00e1kladn\u00ed v\u00fdm\u011bn\u011b. Tzn. zpr\u00e1vy Delay_Req a Delay_Resp se nepos\u00edlaj\u00ed. V t\u00e9to metod\u011b se zpo\u017ed\u011bn\u00ed mezi hlavn\u00edmi hodinami a pod\u0159\u00edzen\u00fdmi jednodu\u0161e s\u010d\u00edt\u00e1 do pole korekce ka\u017ed\u00e9 zpr\u00e1vy Sync nebo Follow_Up.<\/p>\n<p>Dal\u0161\u00ed v\u00fdhodou je, \u017ee hlavn\u00ed hodiny jsou zbaveny pot\u0159eby zpracov\u00e1vat zpr\u00e1vy Delay_Req.<\/p>\n<p><b>Re\u017eimy pr\u00e1ce transparentn\u00edch hodin<\/b><\/p>\n<p>Odpov\u00eddaj\u00edc\u00edm zp\u016fsobem jsme rozebrali jednoduch\u00e9 p\u0159\u00edklady. A nyn\u00ed p\u0159edpokl\u00e1dejme, \u017ee na cest\u011b synchronizace se objevuj\u00ed switche.<\/p>\n<p>Pokud pou\u017eijete switche bez podpory PTPv2, paket synchronizace bude zpo\u017ed\u011bn na switchi p\u0159ibli\u017en\u011b o 10 \u03bcs.<\/p>\n<p>Switche s podporou PTPv2 v terminologii IEEE 1588v2 se naz\u00fdvaj\u00ed transparentn\u00ed hodiny. Transparentn\u00ed hodiny se nesynchronizuj\u00ed od hlavn\u00edch hodin a ne\u00fa\u010dastn\u00ed se hierarchie \u201eHlavn\u00ed hodiny \u2013 Pod\u0159\u00edzen\u00e9 hodiny\u201c, ale p\u0159i p\u0159enosu synchroniza\u010dn\u00edch zpr\u00e1v si pamatuj\u00ed, o kolik se zpr\u00e1va na nich zpozdila. To umo\u017e\u0148uje korigovat zpo\u017ed\u011bn\u00ed \u010dasu.<\/p>\n<p>Transparentn\u00ed hodiny mohou pracovat ve dvou re\u017eimech:<\/p>\n<ul>\n<li>End-to-End.<\/li>\n<li>Peer-to-Peer.<\/li>\n<\/ul>\n<p>\n<b>End-to-End (E2E)<\/b><\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/94e5d2f343d1657f1458adcbb344d024.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTransparentn\u00ed hodiny E2E p\u0159en\u00e1\u0161ej\u00ed zpr\u00e1vy Sync a souvisej\u00edc\u00ed zpr\u00e1vy Follow_Up na v\u0161echny porty. I na ty, kter\u00e9 jsou blokov\u00e1ny jak\u00fdmikoli protokoly (nap\u0159\u00edklad RSTP).<\/p>\n<p>P\u0159ep\u00edna\u010d si pamatuje \u010dasovou zna\u010dku, kdy byl paket Sync (Follow_Up) p\u0159ijat na portu a kdy byl odesl\u00e1n z portu. Na z\u00e1klad\u011b t\u011bchto dvou \u010dasov\u00fdch zna\u010dek se vypo\u010d\u00edt\u00e1 doba zpracov\u00e1n\u00ed zpr\u00e1vy p\u0159ep\u00edna\u010dem. Ve standardu se tato doba naz\u00fdv\u00e1 residence time.<\/p>\n<p>Doba zpracov\u00e1n\u00ed se p\u0159id\u00e1v\u00e1 do pole correctionField zpr\u00e1vy Sync (jednostup\u0148ov\u00e9 hodiny) nebo Follow_Up (dvoustup\u0148ov\u00e9 hodiny).<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/b04cfa6cd1a93f25222079d5bb864a6d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTransparentn\u00ed hodiny E2E m\u011b\u0159\u00ed dobu zpracov\u00e1n\u00ed pro zpr\u00e1vy Sync a Delay_Req, kter\u00e9 proch\u00e1zej\u00ed p\u0159ep\u00edna\u010dem. Je v\u0161ak d\u016fle\u017eit\u00e9 pochopit, \u017ee zpo\u017ed\u011bn\u00ed mezi hlavn\u00edmi hodinami a pod\u0159\u00edzen\u00fdmi hodinami se vypo\u010d\u00edt\u00e1v\u00e1 pomoc\u00ed mechanismu po\u017eadavku-odezvy zpo\u017ed\u011bn\u00ed. Pokud se m\u011bn\u00ed hlavn\u00ed hodiny nebo cesta od hlavn\u00edch hodin k pod\u0159\u00edzen\u00fdm, zpo\u017ed\u011bn\u00ed se m\u011b\u0159\u00ed znovu. To zvy\u0161uje dobu p\u0159echodn\u00e9ho stavu v p\u0159\u00edpad\u011b zm\u011bn v s\u00edti.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/5bcb72a639accf802ffba7a1fa9a4767.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTransparentn\u00ed hodiny P2P, krom\u011b m\u011b\u0159en\u00ed doby zpracov\u00e1n\u00ed zpr\u00e1vy p\u0159ep\u00edna\u010dem, m\u011b\u0159\u00ed zpo\u017ed\u011bn\u00ed na kan\u00e1lu p\u0159enosu dat k nejbli\u017e\u0161\u00edmu sousedovi pomoc\u00ed mechanismu m\u011b\u0159en\u00ed zpo\u017ed\u011bn\u00ed sousedn\u00edho uzlu.<\/p>\n<p>Zpo\u017ed\u011bn\u00ed se m\u011b\u0159\u00ed na ka\u017ed\u00e9m kan\u00e1lu v obou sm\u011brech, v\u010detn\u011b kan\u00e1l\u016f, kter\u00e9 jsou blokov\u00e1ny n\u011bjak\u00fdm protokolem (nap\u0159. RSTP). To umo\u017e\u0148uje okam\u017eit\u00e9 vypo\u010d\u00edt\u00e1n\u00ed nov\u00e9ho zpo\u017ed\u011bn\u00ed na cest\u011b synchronizace, pokud se zm\u011bnily hlavn\u00ed hodiny nebo topologie s\u00edt\u011b.<\/p>\n<p>Doba zpracov\u00e1n\u00ed zpr\u00e1v p\u0159ep\u00edna\u010di a doba zpo\u017ed\u011bn\u00ed se akumuluj\u00ed p\u0159i p\u0159enosu zpr\u00e1v Sync nebo Follow_Up.<\/p>\n<p><b>Typy podpory PTPv2 p\u0159ep\u00edna\u010di<\/b><\/p>\n<p>P\u0159ep\u00edna\u010de mohou podporovat PTPv2:<\/p>\n<ul>\n<li>softwarov\u011b;<\/li>\n<li>hardwarov\u011b.<\/li>\n<\/ul>\n<p>\nP\u0159i softwarov\u00e9 implementaci protokolu PTPv2 p\u0159ep\u00edna\u010d po\u017eaduje \u010dasovou zna\u010dku od firmwaru. Probl\u00e9m spo\u010d\u00edv\u00e1 v tom, \u017ee firmware pracuje cyklicky, a bude nutn\u00e9 po\u010dkat, a\u017e dokon\u010d\u00ed aktu\u00e1ln\u00ed cyklus, vezme po\u017eadavek k zpracov\u00e1n\u00ed a po uplynut\u00ed dal\u0161\u00edho cyklu vyd\u00e1 \u010dasovou zna\u010dku. To v\u0161e tak\u00e9 zabere \u010das a my dostaneme zpo\u017ed\u011bn\u00ed, i kdy\u017e ne tak v\u00fdrazn\u00e9 jako bez softwarov\u00e9 podpory PTPv2.<\/p>\n<p>Zaru\u010dit pot\u0159ebnou p\u0159esnost umo\u017e\u0148uje pouze hardwarov\u00e1 podpora PTPv2. V tomto p\u0159\u00edpad\u011b se vyd\u00e1n\u00ed \u010dasov\u00e9 zna\u010dky prov\u00e1d\u00ed speci\u00e1ln\u00edm ASICem, kter\u00fd je nainstalov\u00e1n na portu.<\/p>\n<p><b>Form\u00e1t zpr\u00e1vy<\/b><\/p>\n<p>V\u0161echny zpr\u00e1vy PTP se skl\u00e1daj\u00ed z n\u00e1sleduj\u00edc\u00edch pol\u00ed:<\/p>\n<ul>\n<li>Header \u2013 34 byt\u016f.<\/li>\n<li>Body \u2013 velikost z\u00e1vis\u00ed na typu zpr\u00e1vy.<\/li>\n<li>Suffix \u2013 voliteln\u011b.<\/li>\n<\/ul>\n<p>\n<img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/99086e6601dcdf8f41c10f273c4ebfdc.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Header<\/b><\/p>\n<p>Pole Header je stejn\u00e9 pro v\u0161echny zpr\u00e1vy PTP. Jeho velikost je 34 bajt\u016f.<\/p>\n<p>Form\u00e1t pole Header:<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/e4500d7e9026d9d059b1dcd668a44e5f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>messageType <\/b>\u2013 obsahuje typ p\u0159en\u00e1\u0161en\u00e9 zpr\u00e1vy, nap\u0159\u00edklad Sync, Delay_Req, PDelay_Req atd.<\/p>\n<p><b>messageLength<\/b> \u2013 obsahuje celkovou velikost zpr\u00e1vy PTP, v\u010detn\u011b hlavi\u010dky, t\u011bla a suffixu (ale bez vypl\u0148uj\u00edc\u00edch bajt\u016f).<\/p>\n<p><b>domainNumber<\/b> \u2013 ur\u010duje, ke kter\u00e9mu <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/cs\/domain\/\"   title=\"domain\" data-wpil-keyword-link=\"linked\"  data-wpil-monitor-id=\"1225\">domain<\/a> PTP zpr\u00e1va pat\u0159\u00ed.<\/p>\n<p><b>Dom\u00e9na<\/b> \u2013 to je n\u011bkolik r\u016fzn\u00fdch hodin seskupen\u00fdch do jedn\u00e9 logick\u00e9 skupiny, synchronizovan\u00fdch z jednoho hlavn\u00edho hodin, ale nen\u00ed nutn\u00e9, aby byly synchronizov\u00e1ny s hodinami pat\u0159\u00edc\u00edmi k jin\u00e9mu dom\u00e9n\u011b.<\/p>\n<p><b>flags<\/b> \u2013 toto pole obsahuje r\u016fzn\u00e9 p\u0159\u00edznaky pro identifikaci stavu zpr\u00e1vy.<\/p>\n<p><b>correctionField<\/b> \u2013 obsahuje \u010das zpo\u017ed\u011bn\u00ed v nanosekund\u00e1ch. \u010cas zpo\u017ed\u011bn\u00ed zahrnuje zpo\u017ed\u011bn\u00ed p\u0159i p\u0159enosu p\u0159es transparentn\u00ed hodiny, stejn\u011b jako zpo\u017ed\u011bn\u00ed p\u0159i p\u0159enosu p\u0159es kan\u00e1l p\u0159i pou\u017eit\u00ed re\u017eimu Peer-to-Peer.<\/p>\n<p><b>sourcePortIdentity<\/b> \u2013 toto pole obsahuje informace o tom, z jak\u00e9ho portu byla tato zpr\u00e1va p\u016fvodn\u011b odesl\u00e1na.<\/p>\n<p><b>sequenceID<\/b> \u2013 obsahuje identifika\u010dn\u00ed \u010d\u00edslo pro jednotliv\u00e9 zpr\u00e1vy.<\/p>\n<p><b>controlField<\/b> \u2013 artefakt pole =). Z\u016fstalo z prvn\u00ed verze standardu a obsahuje informace o typu t\u00e9to zpr\u00e1vy. V podstat\u011b je to tot\u00e9\u017e jako messageType, ale s men\u0161\u00edm po\u010dtem mo\u017enost\u00ed.<\/p>\n<p><b>logMessageInterval<\/b> \u2013 toto pole je ur\u010deno typem zpr\u00e1vy.<\/p>\n<p><b>T\u011blo<\/b><\/p>\n<p>Jak bylo uvedeno v\u00fd\u0161e, existuje n\u011bkolik typ\u016f zpr\u00e1v. Tyto typy jsou pops\u00e1ny n\u00ed\u017ee:<\/p>\n<p><b>Zpr\u00e1va Announce<\/b><br \/>\nZpr\u00e1va Announce se pou\u017e\u00edv\u00e1 k tomu, aby \"\u0159ekla\" ostatn\u00edm hodin\u00e1m uvnit\u0159 jednoho dom\u00e9ny o sv\u00fdch parametrech. Tato zpr\u00e1va umo\u017e\u0148uje nastavit hierarchii \"Hlavn\u00ed hodiny \u2013 Pod\u0159\u00edzen\u00e9 hodiny.\"<br \/>\n<img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/054b35f0c74757d531205fa352b90f4e.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Zpr\u00e1va Sync<\/b><br \/>\nZpr\u00e1va synchronizace (Sync) je odes\u00edl\u00e1na hlavn\u00edmi hodinami a obsahuje \u010das hlavn\u00edch hodin v okam\u017eiku, kdy byla zpr\u00e1va Sync vytvo\u0159ena. Pokud jsou hlavn\u00ed hodiny dvoustup\u0148ov\u00e9, bude \u010dasov\u00e1 zna\u010dka ve zpr\u00e1v\u011b Sync nastavena na 0 a aktu\u00e1ln\u00ed \u010dasov\u00e1 zna\u010dka bude odesl\u00e1na v p\u0159ipojen\u00e9 zpr\u00e1v\u011b Follow_Up. Zpr\u00e1va Sync se pou\u017e\u00edv\u00e1 pro oba mechanismy m\u011b\u0159en\u00ed zpo\u017ed\u011bn\u00ed.<\/p>\n<p>Zpr\u00e1va se p\u0159en\u00e1\u0161\u00ed pomoc\u00ed Multicast. Voliteln\u011b je mo\u017en\u00e9 pou\u017e\u00edt Unicast.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/38268221aa5663ba021f225c9de01df9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Zpr\u00e1va Delay_Req<\/b><\/p>\n<p>Form\u00e1t zpr\u00e1vy Delay_Req je shodn\u00fd se zpr\u00e1vou Sync. Pod\u0159\u00edzen\u00e9 hodiny pos\u00edlaj\u00ed Delay_Req. Obsahuje \u010das odesl\u00e1n\u00ed Delay_Req pod\u0159\u00edzen\u00fdmi hodinami. Tato zpr\u00e1va se pou\u017e\u00edv\u00e1 pouze pro mechanismus \u017e\u00e1dosti o zpo\u017ed\u011bn\u00ed.<\/p>\n<p>Zpr\u00e1va se p\u0159en\u00e1\u0161\u00ed pomoc\u00ed Multicast. Voliteln\u011b je mo\u017en\u00e9 pou\u017e\u00edt Unicast.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/1e64f3902ff3364b968581ff6b6a6573.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Zpr\u00e1va Follow_Up<\/b><\/p>\n<p>Zpr\u00e1va Follow_Up je voliteln\u011b odes\u00edl\u00e1na hlavn\u00edmi hodinami a obsahuje \u010das odesl\u00e1n\u00ed <b>zpr\u00e1vy Sync<\/b> mistrem. Zpr\u00e1vu Follow_Up odes\u00edlaj\u00ed pouze dvoustup\u0148ov\u00e9 hlavn\u00ed hodiny.<\/p>\n<p>Zpr\u00e1va Follow_Up se pou\u017e\u00edv\u00e1 pro oba mechanizmy m\u011b\u0159en\u00ed zpo\u017ed\u011bn\u00ed.<\/p>\n<p>Zpr\u00e1va se p\u0159en\u00e1\u0161\u00ed pomoc\u00ed Multicast. Voliteln\u011b je mo\u017en\u00e9 pou\u017e\u00edt Unicast.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/00917743466b8a331922d18e0928d3db.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Zpr\u00e1va Delay_Resp<\/b><\/p>\n<p>Zpr\u00e1va Delay_Resp je odes\u00edl\u00e1na hlavn\u00edmi hodinami. Obsahuje \u010das p\u0159ijet\u00ed Delay_Req hlavn\u00edmi hodinami. Tato zpr\u00e1va se pou\u017e\u00edv\u00e1 pouze pro mechanizmus dotaz-odpov\u011b\u010f zpo\u017ed\u011bn\u00ed.<\/p>\n<p>Zpr\u00e1va se p\u0159en\u00e1\u0161\u00ed pomoc\u00ed Multicast. Voliteln\u011b je mo\u017en\u00e9 pou\u017e\u00edt Unicast.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/b9d0bc41f94ceee560c0c593dd9e4afd.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Zpr\u00e1va Pdelay_Req<\/b><\/p>\n<p>Zpr\u00e1va Pdelay_Req je odes\u00edl\u00e1na za\u0159\u00edzen\u00edm, kter\u00e9 po\u017eaduje zpo\u017ed\u011bn\u00ed. Obsahuje \u010das odesl\u00e1n\u00ed zpr\u00e1vy z portu tohoto za\u0159\u00edzen\u00ed. Pdelay_Req se pou\u017e\u00edv\u00e1 pouze pro mechanizmus m\u011b\u0159en\u00ed zpo\u017ed\u011bn\u00ed sousedn\u00edho uzlu.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/7eef44a2655158758cdbcfbc25fc2e48.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Zpr\u00e1va Pdelay_Resp<\/b><\/p>\n<p>Zpr\u00e1va Pdelay_Resp je odes\u00edl\u00e1na za\u0159\u00edzen\u00edm, kter\u00e9 obdr\u017eelo \u017e\u00e1dost o zpo\u017ed\u011bn\u00ed. Obsahuje \u010das p\u0159ijet\u00ed zpr\u00e1vy Pdelay_Req t\u00edmto za\u0159\u00edzen\u00edm. Zpr\u00e1vy Pdelay_Resp se pou\u017e\u00edvaj\u00ed pouze pro mechanizmus m\u011b\u0159en\u00ed zpo\u017ed\u011bn\u00ed sousedn\u00edho uzlu.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/6a3bb44c70fc09db3025df93c4d58a3f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Zpr\u00e1va Pdelay_Resp_Follow_Up<\/b><\/p>\n<p>Zpr\u00e1va Pdelay_Resp_Follow_Up je voliteln\u011b odes\u00edl\u00e1na za\u0159\u00edzen\u00edm, kter\u00e9 obdr\u017eelo \u017e\u00e1dost o zpo\u017ed\u011bn\u00ed. Obsahuje \u010das p\u0159ijet\u00ed zpr\u00e1vy Pdelay_Req t\u00edmto za\u0159\u00edzen\u00edm. Zpr\u00e1va Pdelay_Resp_Follow_Up se odes\u00edl\u00e1 pouze dvoustup\u0148ov\u00fdmi hlavn\u00edmi hodinami.<\/p>\n<p>Tato zpr\u00e1va m\u016f\u017ee b\u00fdt tak\u00e9 pou\u017eita pro \u010das vykon\u00e1n\u00ed m\u00edsto \u010dasov\u00e9 zna\u010dky. \u010cas vykon\u00e1n\u00ed je \u010das od okam\u017eiku p\u0159ijet\u00ed Pdelay-Req po odesl\u00e1n\u00ed Pdelay_Resp.<\/p>\n<p>Pdelay_Resp_Follow_Up se pou\u017e\u00edvaj\u00ed pouze pro mechanizmus m\u011b\u0159en\u00ed zpo\u017ed\u011bn\u00ed sousedn\u00edho uzlu.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/523043f7a880030474098fcdc1c5822d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>\u0158\u00eddic\u00ed zpr\u00e1vy (Zpr\u00e1va Management)<\/b><\/p>\n<p>\u0158\u00eddic\u00ed zpr\u00e1vy PTP jsou nezbytn\u00e9 pro p\u0159enos informac\u00ed mezi jedn\u011bmi nebo v\u00edce hodinami a \u0159\u00eddic\u00ed uzlem.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/4388d9f4b6b12f3a2cdc764c20597499.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>P\u0159enos v LV<\/b><\/p>\n<p>PTP-zpr\u00e1va m\u016f\u017ee b\u00fdt p\u0159en\u00e1\u0161ena na dvou \u00farovn\u00edch:<\/p>\n<ul>\n<li>S\u00ed\u0165ov\u00e9 \u2013 jako sou\u010d\u00e1st IP dat.<\/li>\n<li>Linkov\u00e9 \u2013 jako sou\u010d\u00e1st Ethernetov\u00e9ho r\u00e1mce.<\/li>\n<\/ul>\n<p>\nP\u0159enos zpr\u00e1vy PTP p\u0159es UDP p\u0159es IP p\u0159es Ethernet<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/361e008fc48396915e5e9c23cc52bd63.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPTP p\u0159es UDP p\u0159es Ethernet<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/1862a5d27931a744e75e3c5bc63d7091.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Profily<\/b><\/p>\n<p>PTP m\u00e1 dostatek \u201eflexibiln\u00edch\u201c parametr\u016f, kter\u00e9 je t\u0159eba nastavit. Nap\u0159\u00edklad:<\/p>\n<ul>\n<li>Mo\u017enosti BMCA.<\/li>\n<li>Mechanismus m\u011b\u0159en\u00ed zpo\u017ed\u011bn\u00ed.<\/li>\n<li>Intervaly a po\u010d\u00e1te\u010dn\u00ed hodnoty v\u0161ech konfigurovateln\u00fdch parametr\u016f atd.<\/li>\n<\/ul>\n<p>\nA p\u0159esto\u017ee jsme ji\u017e d\u0159\u00edve \u0159\u00edkali, \u017ee za\u0159\u00edzen\u00ed PTPv2 jsou vz\u00e1jemn\u011b kompatibiln\u00ed, tak to \u00fapln\u011b nen\u00ed pravda. Za\u0159\u00edzen\u00ed mus\u00ed m\u00edt shodn\u00e1 nastaven\u00ed, aby mohla vz\u00e1jemn\u011b komunikovat.<\/p>\n<p>Proto existuj\u00ed takzvan\u00e9 profily PTPv2. Profily jsou skupiny nakonfigurovan\u00fdch nastaven\u00ed a specifikovan\u00fdch omezen\u00ed protokolu, kter\u00e9 umo\u017e\u0148uj\u00ed implementaci \u010dasov\u00e9 synchronizace pro konkr\u00e9tn\u00ed aplikaci.<\/p>\n<p>Samotn\u00fd standard IEEE 1588v2 popisuje pouze jeden profil \u2013 \u201eDefault Profile\u201c. V\u0161echny ostatn\u00ed profily byly vytvo\u0159eny a pops\u00e1ny r\u016fzn\u00fdmi organizacemi a asociacemi.<\/p>\n<p>Nap\u0159\u00edklad profil pro elektroenergetiku nebo PTPv2 Power Profile byl vytvo\u0159en v\u00fdborem Power Systems Relaying Committee a v\u00fdborem Substation Committee spole\u010dnosti IEEE Power and Energy Society. Tento profil nese n\u00e1zev IEEE C37.238-2011.<\/p>\n<p>Profil popisuje, jak m\u016f\u017ee b\u00fdt PTP p\u0159en\u00e1\u0161en:<\/p>\n<ul>\n<li>Pouze p\u0159es L2 s\u00edt\u011b (tj. Ethernet, HSR, PRP, nikoli IP).<\/li>\n<li>Zpr\u00e1vy se p\u0159en\u00e1\u0161ej\u00ed pouze pomoc\u00ed Multicast distribuce.<\/li>\n<li>Jako mechanismus pro m\u011b\u0159en\u00ed zpo\u017ed\u011bn\u00ed se pou\u017e\u00edv\u00e1 mechanismus m\u011b\u0159en\u00ed zpo\u017ed\u011bn\u00ed Peer.<\/li>\n<\/ul>\n<p>\nV\u00fdchoz\u00ed dom\u00e9na je 0, doporu\u010den\u00e1 dom\u00e9na je 93.<\/p>\n<p>V filozofii tvorby C37.238-2011 st\u00e1lo p\u0159\u00e1n\u00ed sn\u00ed\u017eit po\u010det voliteln\u00fdch vlastnost\u00ed a ponechat pouze nezbytn\u00e9 funkce pro spolehlivou interakci mezi za\u0159\u00edzen\u00edmi a zv\u00fd\u0161en\u00ed stability syst\u00e9mu.<\/p>\n<p>D\u00e1le byla ur\u010dena frekvence p\u0159enosu zpr\u00e1v:<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/117c81192ff2eb160652738bb9ecbb1d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nV podstat\u011b je pro v\u00fdb\u011br k dispozici pouze jeden parametr \u2013 typ hlavn\u00edch hodin (jednostup\u0148ov\u00e9 nebo dvoustup\u0148ov\u00e9).<\/p>\n<p>P\u0159esnost nesm\u00ed b\u00fdt v\u011bt\u0161\u00ed ne\u017e 1 \u03bcs. Jin\u00fdmi slovy, v jedn\u00e9 cest\u011b synchronizace m\u016f\u017ee b\u00fdt maxim\u00e1ln\u011b 15 transparentn\u00edch hodin nebo t\u0159i hrani\u010dn\u00ed hodiny.<\/p>\n<p><img decoding=\"async\" alt=\"Podrobnosti o implementaci protokolu synchronizace \u010dasu PTPv2\" src=\"\/wp-content\/uploads\/2020\/04\/d3f1cb822d01b8733eadb6cd75805b20.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/phoenix_contact\/blog\/495920\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u041a\u043e\u043d\u0446\u0435\u043f\u0446\u0438\u044f \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u044f \u00ab\u0426\u0438\u0444\u0440\u043e\u0432\u043e\u0439 \u043f\u043e\u0434\u0441\u0442\u0430\u043d\u0446\u0438\u0438\u00bb \u0432 \u044d\u043b\u0435\u043a\u0442\u0440\u043e\u044d\u043d\u0435\u0440\u0433\u0435\u0442\u0438\u043a\u0435 \u0442\u0440\u0435\u0431\u0443\u0435\u0442 \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0441 \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u044c\u044e 1 \u043c\u043a\u0441. \u0414\u043b\u044f \u043f\u0440\u043e\u0432\u0435\u0434\u0435\u043d\u0438\u044f \u0444\u0438\u043d\u0430\u043d\u0441\u043e\u0432\u044b\u0445 \u0442\u0440\u0430\u043d\u0437\u0430\u043a\u0446\u0438\u0439 \u0442\u0430\u043a\u0436\u0435 \u0442\u0440\u0435\u0431\u0443\u0435\u0442\u0441\u044f \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u044c \u0432 \u043c\u043a\u0441. \u0412 \u044d\u0442\u0438\u0445 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f\u0445 \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u0438 \u0432\u0440\u0435\u043c\u0435\u043d\u0438 NTP \u0443\u0436\u0435 \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e. \u041f\u0440\u043e\u0442\u043e\u043a\u043e\u043b \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 PTPv2, \u043e\u043f\u0438\u0441\u0430\u043d\u043d\u044b\u0439 \u0441\u0442\u0430\u043d\u0434\u0430\u0440\u0442\u043e\u043c IEEE 1588v2, \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0434\u043e\u0431\u0438\u0442\u044c\u0441\u044f \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u0438 \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0432 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u0434\u0435\u0441\u044f\u0442\u043a\u043e\u0432 \u043d\u0430\u043d\u043e\u0441\u0435\u043a\u0443\u043d\u0434. PTPv2 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u043e\u0442\u043f\u0440\u0430\u0432\u043b\u044f\u0442\u044c \u043f\u0430\u043a\u0435\u0442\u044b \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0447\u0435\u0440\u0435\u0437 L2 \u0438 L3-\u0441\u0435\u0442\u0438. \u041e\u0441\u043d\u043e\u0432\u043d\u044b\u043c\u0438 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":77042,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-77041","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=\"\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u041a\u043e\u043d\u0446\u0435\u043f\u0446\u0438\u044f \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u044f \u00ab\u0426\u0438\u0444\u0440\u043e\u0432\u043e\u0439 \u043f\u043e\u0434\u0441\u0442\u0430\u043d\u0446\u0438\u0438\u00bb \u0432 \u044d\u043b\u0435\u043a\u0442\u0440\u043e\u044d\u043d\u0435\u0440\u0433\u0435\u0442\u0438\u043a\u0435 \u0442\u0440\u0435\u0431\u0443\u0435\u0442 \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0441 \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u044c\u044e 1 \u043c\u043a\u0441. \u0414\u043b\u044f \u043f\u0440\u043e\u0432\u0435\u0434\u0435\u043d\u0438\u044f \u0444\u0438\u043d\u0430\u043d\u0441\u043e\u0432\u044b\u0445 \u0442\u0440\u0430\u043d\u0437\u0430\u043a\u0446\u0438\u0439 \u0442\u0430\u043a\u0436\u0435 \u0442\u0440\u0435\u0431\u0443\u0435\u0442\u0441\u044f \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u044c \u0432 \u043c\u043a\u0441.\" \/>\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\/podrobnosti-realizaczii-protokola-sinhronizaczii-vremeni-ptpv2\" \/>\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\u043e\u0434\u0440\u043e\u0431\u043d\u043e\u0441\u0442\u0438 \u0440\u0435\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0432\u0440\u0435\u043c\u0435\u043d\u0438 PTPv2 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u041a\u043e\u043d\u0446\u0435\u043f\u0446\u0438\u044f \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u044f \u00ab\u0426\u0438\u0444\u0440\u043e\u0432\u043e\u0439 \u043f\u043e\u0434\u0441\u0442\u0430\u043d\u0446\u0438\u0438\u00bb \u0432 \u044d\u043b\u0435\u043a\u0442\u0440\u043e\u044d\u043d\u0435\u0440\u0433\u0435\u0442\u0438\u043a\u0435 \u0442\u0440\u0435\u0431\u0443\u0435\u0442 \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0441 \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u044c\u044e 1 \u043c\u043a\u0441. \u0414\u043b\u044f \u043f\u0440\u043e\u0432\u0435\u0434\u0435\u043d\u0438\u044f \u0444\u0438\u043d\u0430\u043d\u0441\u043e\u0432\u044b\u0445 \u0442\u0440\u0430\u043d\u0437\u0430\u043a\u0446\u0438\u0439 \u0442\u0430\u043a\u0436\u0435 \u0442\u0440\u0435\u0431\u0443\u0435\u0442\u0441\u044f \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u044c \u0432 \u043c\u043a\u0441.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/podrobnosti-realizaczii-protokola-sinhronizaczii-vremeni-ptpv2\" \/>\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=\"2020-04-07T11:42:46+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-04-07T11:42:46+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\udd47Podrobnosti o implementaci protokolu pro synchronizaci \u010dasu PTPv2 | ProHoster","description":"\u00davod Koncept v\u00fdstavby \u201aDigit\u00e1ln\u00ed podz\u00e1kladny\u2018 v elektroenergetice vy\u017eaduje synchronizaci s p\u0159esnost\u00ed 1 \u03bcs. Pro prov\u00e1d\u011bn\u00ed finan\u010dn\u00edch transakc\u00ed je tak\u00e9 pot\u0159ebn\u00e1 p\u0159esnost v \u03bcs.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/podrobnosti-realizaczii-protokola-sinhronizaczii-vremeni-ptpv2","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\u043e\u0434\u0440\u043e\u0431\u043d\u043e\u0441\u0442\u0438 \u0440\u0435\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0432\u0440\u0435\u043c\u0435\u043d\u0438 PTPv2 | ProHoster","og:description":"\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u041a\u043e\u043d\u0446\u0435\u043f\u0446\u0438\u044f \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u0438\u044f \u00ab\u0426\u0438\u0444\u0440\u043e\u0432\u043e\u0439 \u043f\u043e\u0434\u0441\u0442\u0430\u043d\u0446\u0438\u0438\u00bb \u0432 \u044d\u043b\u0435\u043a\u0442\u0440\u043e\u044d\u043d\u0435\u0440\u0433\u0435\u0442\u0438\u043a\u0435 \u0442\u0440\u0435\u0431\u0443\u0435\u0442 \u0441\u0438\u043d\u0445\u0440\u043e\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0441 \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u044c\u044e 1 \u043c\u043a\u0441. \u0414\u043b\u044f \u043f\u0440\u043e\u0432\u0435\u0434\u0435\u043d\u0438\u044f \u0444\u0438\u043d\u0430\u043d\u0441\u043e\u0432\u044b\u0445 \u0442\u0440\u0430\u043d\u0437\u0430\u043a\u0446\u0438\u0439 \u0442\u0430\u043a\u0436\u0435 \u0442\u0440\u0435\u0431\u0443\u0435\u0442\u0441\u044f \u0442\u043e\u0447\u043d\u043e\u0441\u0442\u044c \u0432 \u043c\u043a\u0441.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/podrobnosti-realizaczii-protokola-sinhronizaczii-vremeni-ptpv2","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":"2020-04-07T11:42:46+00:00","article:modified_time":"2020-04-07T11:42:46+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"77041","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":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 17:25:29","updated":"2026-02-09 15:52:39","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\/77041","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=77041"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/77041\/revisions"}],"predecessor-version":[{"id":158469,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/77041\/revisions\/158469"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/77042"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=77041"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=77041"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=77041"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}