Brkiot 2517

BRKIOT-2517
Precision Time Protocol -

deep dive and use cases
Subtitle goes here
Albert Mitchell
January 2019
Agenda
Basics of PTP
• PTP Messaging
• Grandmaster clock
• PTP Profiles
• Boundary and Transparent Clocks
Configuring PTP on Cisco IE Switches
• Profile, modes and changing the defaults
Troubleshooting: How to know its working?
• Show commands
• Debug commands
• Vlan impacts
• Spanning tree issues
Close
BRKIOT-2517 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
Perspective for PTP Breakout session
• This Training oriented towards Network Administrator needing to configure
PTP in the network.
• Not a PTP expert, yet responsible to implement
• The session covers
• What is PTP
• How to configure on the Cisco Industrial Ethernet Bridges
• How to Troubleshoot problems
PTP Timing Distribution Architecture
• PTP uses a hierarchical master-slave architecture for clock distribution. GPS
• Grandmaster clock (GMC) is the root timing reference. It transmits Antenna
synchronization information to the clocks residing on its network segment.
• Ordinary clock (OC) is a device with a single network (PTP) connection and
is either the source of (master) or destination for (slave) a synchronization Grandmaster
reference.
• Boundary clock (BC) has multiple network (PTP) connections and can M
White VLAN
accurately bridge synchronization from one network segment to another.
• ‘M’ – interface in Master sate Boundary
• ‘S’ – interface in Slave State Clock S S
• Clocks in cascaded topologies: Transparent Ordinary

• End-to-end transparent clock (E2E) Clock Clock
• Peer-to-peer transparent clock (P2P)
M M
Red VLAN Green VLAN

• PTP epoch is the same as Unix time (Midnight, 1 January 1970).
• Using UTC with PTP is subject to leap seconds. S S S S S
• PTP uses TAI (Temps Atomique International) time scale and moves forward
monotonically.
• TAI is currently ahead of UTC by 35 seconds.
• TAI is always ahead of GPS by 19 seconds.
• The PTP grandmaster communicates the current offset between UTC and Ordinary Clocks
TAI so that UTC can be computed from the received PTP time.
PTP messages
Have you seen this diagram?
Master Slave
t1
Sy
Fo nc
llow Delay
-Up 1
(t1
)
t2
• What does this mean?
t3
R eq • How can I use this?
Delay D el _
2
t4
De
l_ R
e sp
(t4
)
But first, Well used Terms in PTP
• Common terms used throughout the session.
• Good for a reference
PTP Terms
• PTP –precision time protocol
• GMC – Grand Master Clock (Master)
• BC – boundary clock
• TC – Transparent clock
• OC – Ordinary clock (eg: slave)
• E2E TC – End to End Transparent clock
• P2P TC – Peer to Peer transparent clock
• PDV – packet Delay Variation
• M – designates an interface is in Master mode
• S – designates an interface is in Slave Mode
Event Messaging in PTP master and slave
Event msgs are timed.
• Sync – master to all slaves, contains time
• Announce – used by BMCA to build clock hierarchy select GMC
• Follow_Up – master to all slaves, contains time t1; only in two-step
• Delay_Request (E2E only)– Slave to master, requests delay time
• Pdelay_Req (P2P only) slave Peer asking for per hop delay from Master
PTP Protocol General messages
General messages are untimed
• Follow_Up master to all slaves, contains time t1; only in two-step

• Delay_Resp, (E2E only) Master to Slave, responds with time t4
• Pdelay_Resp_Follow_Up (P2P only)
• Management
• Signaling
• Pdelay_Req, Pdelay_Resp and Pdelay_Resp_Follow_Up are used by Peer-to-
Peer Transparent Clocks to measure delays across the network so that they
can be compensated for by the system.
PTP Synchronization Message Exchange
1. It starts when Master clock sends ‘Sync’ message. Master Slave
1. ‘t1’ is timestamp when it leaves master
2. In one-step ‘t1’ in Sync message t1
3. In two-step, ‘t1’ in Follow-up message Sy
Fo nc
llow Delay
2. Slave receives ‘Sync’ at ‘t2’. -Up 1
3. Slave sends ‘Delay_Req’ message (t1
)
1. ‘t3’ is timestamp when it leaves slave t2
4. Master receives ‘Delay_Req’ at ‘t4’
5. Master responds with ‘Delay_Resp’ e q
t3
1. contains ‘t4’ l _R
Delay De
2
Slave needs t3 and t4 timestamps for delay
t4
MeanPathDelay = ((t2 - t1) + (t4 - t3))/2 De
l_ R
e sp
(t4
)
Offset = t2 – t1 – MeanPathDelay
Offset = difference between the master and slave clock
Calculating Delay
Mean path Delay = ((t2 – t1)+(t4 – t3))/2 Master Slave
t1
Sy
Mean path Delay is really an Average Fo nc
llow Delay
-Up 1
(t1
)
An assumption is made: t2
Delay 1 = Delay 2 t1, t2

t3
e q
l _R
Delay De
Assumption is usually wrong 2
(to some degree) t4
De
l_ R
Protocol Mechanisms can correct e sp
(t4
)
for known Asymmetry
t1, t2, t3, t4
Asymmetry cannot be detected
Calculating Time Offset
Delay = ((t2 – t1)+(t4 – t3))/2 Master Slave
t1
Sy
Fo nc
Delay
Offset = ((t2 – t1)-(t4 – t3))/2 llow
-Up 1
(t1
Offset = (Delay1–Delay2)/2 )
t2
or t1, t2
t3
Offset = Master Time – Slave Time – Delay l _R
e q
Delay De
2
In other words: t4
De
l_ R
e sp
When Ordinary clock is Frequency Locked (t4
)
and you assume Delay1 = Delay2, then any t1, t2, t3, t4
difference is due to error in Time (Offset).
Packet Delay Variation (PDV)
PDV is primarily due to Varying Queue Delays at each hop…
Packet Network
Master Hop 1 Hop 2 Hop 3 Hop 4 Hop n Slave
PTP Session
Even High Priority packets get behind a 1518 from time to time.
The variance comes from the fact that sometimes you do and sometimes you don’t.
It’s all statistics…
PTP Message rates
Message Power profile Default profile
Announce 1 Second 2 second intervals
Sync 1 Second 1
Follow-up ( two step only) Triggered by Sync Triggered by Sync
Delay Request NA 32 seconds to slaves from

BC/GMC*
Delay Response NA Triggered by Delay request
Peer Delay Request 1 second; NA

802.1AS = 8 / second
Peer Delay Response Triggered by Peer Delay request NA
‘*’ burst at beginning then fall back,path delay should not change
PTP messaging
End to End
Time Synchronization across the network
How PTP works to distribute time using messages GPS
Antenna
A ‘typical’ Ethernet network topology

Grandmaster
A single PTP Domain M
S
Transparent
Transparent Clock
Clock M M
Boundary
Clock
Transparent
Clocks
S S S S S
Ordinary Clocks
Synchronization across the network - Sync
‘Sync’ from GMC to all Ordinary Clocks (slaves)
GPS
Antenna
throughout the PTP Domain

Grandmaster
Starts from GMC

Clock
1. M
sync
2. Passed to from Master Ports to Slave ports by S
network devices Transparent
sync sync
Transparent
Clock
Clock M M
Arrives at Ordinary Clocks
BC
3. sync
Boundary
Clock sync
sync
Transparent
Clocks
sync sync sync

S S S S S
Ordinary Clocks
Synchronization across the network – Delay Req
Delay Request from all Ordinary Clocks toward GMC
GPS
Antenna
throughout the PTP Domain

Grandmaster
Starts at ordinary clocks

Clock
1. M
Delay_Req
2. Passed to from Slave Ports to Master ports by
network devices
S
Delay_Req
Delay_Req Transparent
Transparent Clock
Clock M M
Delay_Req stop at the Boundary Clock
BC
3. Boundary
Delay_Req Clock Delay_Req
Delay_Req
1. BC initiates its own Delay_Req
Transparent
Clocks
Delay_Req Delay_Req
S S S S S
Ordinary Clocks
End to End Sync Msg – 2 Step
E2E TC Ordinary Clock
GMC E2E TC link
link link
or
BC
SYNC
t1
path delay (pd)
SYNC
Residence
Follow up
Time (rt)
(contains t1)
T1 not
modified by Residence
SYNC
E2E TCs Time (rt) Follow up
(contains t1 , rt , pd)
t2
Follow up
Follow up
Contains t1, and All Delay
(contains t1,
- except path delay of last hop
sum of all rt,
OC must compute its own
sum of all pd)
path delay on last hop
‘rt’ of SYNC carried in correction field of Follow_Up
End to End Delay_Req and Delay_Resp – 2 Step
E2E TC Ordinary Clock
GMC E2E TC link
link link
or
BC
Residence Delay_Req
Time (rt)
t3
T3 not
Residence Delay_Req
modified by Time (rt)
E2E TCs
Delay_Req
t4
Master responds
with T4
Delay_Resp
(contains T4)
Delay_Resp
(contains T4, rt for T3)
Delay_Resp
(contains T4, sum of rt for T3)
‘rt’ of Delay_Req carried in correction field of Delay_Resp
Peer to Peer Transparent Clock – Sync and Delay
P2P
MASTER Transparent SLAVE
Master time = T M Clock Slave time = TS
t1 = TM + offset
SYNC
Offset = ((t2 – t1)–(t4 – t3))/2
Residency Time (rt)
pt1
SYNC Offset = (t2 – t1)
pDelay_Request
– PD2
t2
– correctionField
pt2 pt1
pDelay_Request
pt3
pDelay_Response
pt2 correctionField = PD1 + rt
pt4 pt3
pDelay_Response
PD : meanPathDelay
PD1= ((pt2 – pt1)+(pt4 – pt3))/2 pt4
PD2= ((pt2 – pt1)+(pt4 – pt3))/2
Delay and pdelay Mechanisms
Side by side Types of TCs: End-to-End and Peer-to-Peer
Non-PTP
BC BC E2E TC
SYNC
GM S M S M S M Delay_Resp
M P
Delay_Req
Delay
E2E TC not
initiating
E2E TC
Delay_Req Brownfield
BC BC P2P TC BC SYNC
S M S M S pdelay_Resp
GM S M M
M P pdelay_Req
P2P TC is
initiating
pDelay_Req P2P TC
Difference between PTP
Profiles and Power
profile
PTP Profile definitions
• Profiles - a set of rules defining PTP behavior, intended to meet the needs of a
specific application.
• Supported by Cisco IE switches:
• Default Profile - IEEE 1588-2008 standard – used by Industrial Automation
• Also called PTPv2. second version of IEEE 1588
• Power Profile – IEEE C37.238 (Power Profile) – used by Power Utilities and substations;
• < 1us over 16 P2P hops
• 802.1AS – IEEE 802.1AS – used by Audio Video Bridging (AVB) and Time Sensitive Networks
(TSN)
• Also called gPTP
• Other popular profiles

• ITU-T G.82751 – Telecom and Mobile Backhaul
PTP Industrial Profile differences - summary
Profile Default Power 802.1AS
IEEE Standard IEEE 1588 v2 (J.3) IEEE C37.238 IEEE 802.1AS
Supported modes Boundary & Boundary & Not configurable.

End-to-End transparent Peer-to-Peer Transparent
Path Delay Delay Request/Respond Peer delay Peer delay
Request/respond Request/respond
Non-PTP device allowed Yes No no
Transport UDP over IP (multicast & L2 Multicast L2 Multicast

Unicast); cross L2
boundary
Deployment cases Industrial Automation Power Utilities substations Enterprise networks
Bridges and Wifi APs do not All Bridges support PTP deploying AVB
support PTP adding PDV Industrial Automation - TSN
Profile differences
Power Profile and Default Profile, 802.1AS
PTP property Default Profile Power Profile 802.1AS
Transparent End to End Peer to Peer Peer to Peer

Clock type
Transport L2 and L3 L2 L2 only
L2 MAC Mgs 01-80-C2-00-00-0E Mgs 01-80-C2-00-00-0E

Pdelay – 01-1B-19-00-00-00-
Address 00
IPv4 Addresses 224.0.1.129 Peer Delay 224.0.0.107
Sync msg rate 32 second intervals* 1 / second 8 / second
Vlan Tagging Untagged on Native Mandatory or vlan 0 Prohibited
‘*’ – burst at beginning to get mean delay
IEEE1588-2008 Profiles
• Primary Profiles 4G Mobile RAN
IEEE1588 ITU G.8265.1 IEEE C37.238

Default Profiles Telecom Profile Frequency Power Profile
Industrial Solutions 2G Mobile RAN
Segment Smart Grid
High Speed Trading 3G Mobile RAN
Profile ID / 00-19-A7-00-01-00 / v1.0
00-19-A7-00-01-00 / v1.0 1C-12-9D-00-00-00 / v1.0
Version 00-19-A7-00-02-00 / v2.0
One-way & two-way One-way & two-way Two-way
PTP Modes
One-step & two-step One-step & two-step One-step & two-step
PTP Transport IPv4 & Layer 2 Multicast IPv4 Unicast Negotiation Layer 2 Multicast
Alternate BMCA
Master • QL (Clock Class)
BMCA BMCA
Selection • PTSF
• Local Priority
Path Delay Delay request/response
Delay request/response Peer-to-Peer
Mechanism Peer-to-Peer
Management
Mgmt Message per Clause 15 not specified IEEE C37.238 MIB
Option
Ordinary Master/Slave, Ordinary Master/Slave, Boundary
Node Types Ordinary Master and Slave
Boundary and Transparent and Transparent
PTP domains
PTP domains and purpose
• A domain[note 9] is an interacting set of clocks that synchronize to one
another using PTP. Clocks are assigned to a domain by virtue of the
contents of the Subdomain name (IEEE 1588-2002) or the domainNumber
(IEEE 1588-2008) fields in PTP messages they receive or generate.
Domains allow multiple clock distribution systems to share the same
communications medium.
• Default Domain – 0
• Cisco IE switches work with a single Domain.
• Power profile standard requires domain be configurable.
• BC drops packets with wrong domain
GrandMaster Clock
Basics
GMC and BMCA
Grandmaster clock
Announce messages are used for BMCA

IE switches operate are Hybrid GMC+BC because they have multiple ports.
PTP Best Master Clock (BMC) Algorithm
• The BMC is used to determine which device should be
used as the master clock device.
Priority1: A user-configurable variable from 0 to
255; lower values takes precedence
• This algorithm uses the clocks characteristics multicast
on the network through “Announce” messages to
determine which clock is the most accurate.
Class: Defines the traceability of the time or
frequency from the grandmaster clock • Once the BMC algorithm has completed, the master
clock starts sending synchronization messages at
Accuracy: Defines the accuracy of a clock; regular intervals.
lower values take precedence
• If the best grandmaster clock is removed from the
Variance: Defines the stability of a clock network or is determined by the BMC algorithm to no
longer be the highest quality clock, the algorithm then
redefines what the new BMC is and adjusts all other
Priority2: A user configurable variable from 0
to 255; lower value take precedence
clocks accordingly.
• No administrator input is needed for this readjustment
Identity: An 8-byte number is typically because the algorithm provides a fault tolerant.
constructed based on a device's MAC address.
BMCA– clock Class
IE5000-2004# show ptp clock
PTP CLOCK INFO
Class value Definition PTP Device Type: Boundary clock
PTP Device Profile: Default Profile
0 Reserved to enable compability with future versions
Clock Identity: 0x18:8B:9D:FF:FE:75:EC:0
6 Clock synchronized to a primary reference (eg: GPS). Clock Domain: 0
Timescale distribution is PTP Number of PTP ports: 28
Time Transfer: Linear Filter
7 Clock previously designated as Class 6, but lost the sync to
Priority1: 120
primary reference. ). Timescale distribution is PTP
Priority2: 128
13 Clock synchronized to a primary reference (eg: GPS). Clock Quality:
Timescale distribution is ARB Class: 248
14 Clock previously designated as Class 13, but lost the sync to Accuracy: Unknown
primary reference. ). Timescale distribution is ARB Offset (log variance): N/A
Offset From Master(ns): 0
… Mean Path Delay(ns): 0
248 Default Steps Removed: 0
Local clock time: 17:05:15 UTC Dec 31 2018
• Class is 248 when free running on internal Oscillator
BMCA Clock Class with GPS input
v23-ie5000-12S12P-10G-2# show ptp clock
• Grand Master with GPS PTP CLOCK INFO
PTP Device Type: Grand Master clock - Boundary clock
• Class = 6 PTP Device Profile: Power Profile
Clock Identity: 0x8:96:AD:FF:FE:A8:1:0
• There’s still a potential race Clock Domain: 0
Number of PTP ports: 28
condition even with one BC PTP Packet priority: 7
having class 6 Time Transfer: Feedforward
Priority1: 128
• ‘flapping’ GMC’s Priority2: 128
• Configure priority1 to mitigate Clock Quality:
Class: 6
Accuracy: Within 250ns
Offset (log variance): N/A
Mean Path Delay(ns): 0
Steps Removed: 0
Local clock time: 19:23:16 UTC Dec 21 2018
IE switching Oscillator
• The Oscillator matters when picking a GM with Class 248
• when you do not have GPS or IRIG-B
• Temperature will impact Oscillator
• IE-5000 has Stratum 3e OCXO (oven Controlled Crystal Oscillators)
• IE-4010 has TCXO ( Temperature compensated crystal oscillator)
Configure the GrandMaster
• When no External sources (eg: GPS, IRIG-B, …) available.
• Configure priority1 or priority2 to sway the BMCA to a specific BC
• The lower the priority the better the clock is represented in BMCA
IE5000-2004#conf t
PTP CLOCK INFO
PTP Device Type: Boundary clock
IE5000-2004(config)#ptp priority? PTP Device Profile: Default Profile
priority1 priority2 Clock Identity: 0x18:8B:9D:FF:FE:75:EC:0
Clock Domain: 0
IE5000-2004(config)#ptp priority1 ? Number of PTP ports: 28
<0-255> clock priority1 number Time Transfer: Linear Filter
Priority1: 120
IE5000-2004(config)#ptp priority1 120 Priority2: 128
IE5000-2004(config)#exit Clock Quality:
Class: 248
Accuracy: Unknown
Steps Removed: 0
© 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 38
Grandmaster – configure a backup
• Backup GMC considerations
• Freerun oscillator or external application (eg: GPS, IRIG-B)
• Oscillator matters if freerun
• Hops from Primary GMC
• Limit PDV change to ordinary clocks in the network
Grandmaster – Primary and Backup
• How to connect and configure the two clocks. From the FS
Convert from jpg
• If GMC is IE, the two can be directly connected
• Use priority to impact BMCA election
• Priority1 used to pick primary and backup
• Priority2 is used to break ties
Cisco IE 5000
Timing Interfaces
GPS
NMEA 0183
IRIG-B In & Out Analog

IRIG-B122 and IRIG-B123
IRIG-B In & Out TTL

IRIG-B002 and IRIG-B003
ToD
IRIG Analog Time of Day
IRIG TTL “Cisco ToD” format
GPS
RS-422 and RS-232
IRIG-B TTL format (B002 and B003) Future
Boundary clocks and
Transparent Clocks
Boundary Clock v. Transparent Clock – Error Sources
Boundary Clock End-to-End Transparent Clock
TimeStamp Switch TimeStamp Switch

Reference Reference
PHY PHY
Time & Message
Transfer Time & Message
Transfer
Slave
Servo
Oscillator
Monitor
Time Servo
Freq
Master Only
Oscillator
TimeStamp TimeStamp
Reference Reference
PHY PHY
4
Transparent Clock Operation vs. Boundary Clock
Operation
S = Slave Mode
M = Master Mode
Transparent Clock Operation Boundary Clock Operation

PTP msgs from GM PTP
are terminated by GM
PTP Clock
GM
the BC. M
Clock
No PTP msgs
PTP msgs pass VLAN S
boundary Internal Clock
TTL=1
adjusted by the
M

Time Servo Time Servo
PTP msgs M M M M Switch Port

generated at running in BC
S each BC port mode
S
S
S
S
S
Boundary clock is master to Ordinary Clocks
• Boundary clock (BC) is not GMC.
• BC looks like master to slave clocks.
• Source of Sync, and responds to delay_requests
• Slave clocks can be Ordinary clocks (end devices) or other Boundary
Clocks ( Switches)
• BCs transfer time by recovering time from a master then regenerating time
to its slaves. Generally, BCs also terminate the messages from the master
and generate messages to their slaves.
Pros and Cons of Boundary Clocks
Pros:
• Breaks up the PTP message domain Message Transfer
• Breaks up the PTP timing domain
• Spans across VLANs
• Shields Slaves from Transients due to hierarchy changes (BMCA)
• Filters PDV
Time Transfer
Cons:
• Adds low frequency (wander) time error (hard to filter)
• Cumulative error: Limit to number of BCs in a row from GMC
Transparent Clocks (end to end, peer to peer)
• TC update the Correction Field with the Residence Time.
• End to End TC does not send Delay Requests
• TC cannot know what true time is. that is OK
• TC needs to get close to GM frequency to minimize the Residence Time Error.
• End to End – available in Default Profile
• Peer to Peer – available Power Profile and 802.1AS
Pros and Cons of Transparent Clocks
Pros:
• Maintains tight timing throughout a domain
• Enables faster convergence in the network – less impact from GMC Time Transfer
change
• Nothing to configure
• Peer-to-Peer TCs can converge faster after network topology

changes
Cons:
• End-to-End TCs can have scalability issues with number of OCs Message Transfer
• PTP Limited to single vlan
TC Scalability with End to End
GPS
GMC
TC TC
TC TC TC TC
1000
TC TC TC TC
Ordinary
Clocks
OC OC OC OC
1 2 999 1000
Imagine a large hierarchy of TCs. If this were all E2E TCs, the GMC would be receiving Delay Request
messages from all 1000 OCs (slaves).
With P2P TCs, however, each TC receives Pdel_Reqs from all of its subs, but only sends one to the device
above it.
BC Cascading
GPS
GMC
BC1
BC2 BC3 BCX

BC4 1000
Ordinary
Clocks
OC1 OC10 OC11 OC20 OC21

OC980 OC30
OC1000
Why not just make all the TCs into BCs?
• Precision error compounded at each BC (due to MTIE + MTIE )

• Cascading BCs is like cascading PLLs – instabilities can occur.
Guidance to choose BC or TC IE Bridge
Choose BC for IE Switch Choose TC for IE Switch
• Change Vlans • Power utilities – mandate P2P

• Need clock to be primary or backup Transparent Clock
GMC • All devices support PTP and network is
• Device at head of ring (REP or STP) stable
• Use TC for devices on a ring
How to Configure IE
Switches for PTP
IE3x00 platforms at a glance
IE3200 IE3300 IE3400
fixed basic modular basic modular advanced
IE 3000 transition
Low port count, low power, High port count, Cisco DNA Advanced features, high port count
Positioning
Network Essentials features Essentials, or Cisco DNA High port count
Advantage features
• Layer 2 • Layer 2 • Layer 2

FCS • Fixed: 10 x 1GE ports • Modular – 26 x1GE ports • Modular –26 x 1GE ports
features • PTP, REP • PTP, NetFlow, REP • PTP, NetFlow, REP
• PoE/PoE+ • PoE/PoE+ • PoE/PoE+
• Layer 3
• Layer 3
• Profinet, MRP, HSR, PRP, L2NAT
• Profinet, MRP
• Macsec, SGT, SGACL
Post-FCS • Profinet, MRP • Macsec
• Cisco DNA Essentials, Cisco DNA Advantage
features • Cisco DNA Essentials • Cisco DNA Essentials,
• SDA Extended Node, SDA Fabric Edge
Cisco DNA Advantage
• TSN
• SDA Extended Node
• Cisco® IOx
Cisco IoT Industrial Ethernet SwitchingAggregation
portfolio
Access
Best in class IE 5000

IE3400 IE 4000 IE 4010 • Designed for all
industries
• Layer 2 or 3
IE3300 (IP service)
IE3200 • 4 10 GE* uplinks
IE 3000 IE 3010 • For all industries • 24 GE downlinks
• Layer 2 or 3 • For all industries • IEEE1588 PTP
IE 2000 IE2000U CGS • Layer 2 • Layer 2 or 3 (default and power
Feature
(IP service)
• 2 GE uplinks
2520 • Up to 24 GE
• 4 GE uplinks (IP service)
• 4 GE uplinks
profiles)
• Layer 2 NAT
• Up to 20 GE
• Layer 2 ports ports • 28 total GE • Up to 12
• Layer 2 • 2 GE uplinks • Up to 24 • IEEE1588 PTP ports PoE/PoE+
IE 1000 • 2 GE uplinks • Up to 24 GE PoE/PoE+
• FNF, REP
(default and • IEEE1588 PTP • Dying gasp
• 8 GE downlinks ports power profiles) (default and • Cisco TrustSec
• Up to 8 • Up to 24 • IEEE1588 PTP • Layer 2 NAT power profiles) SGT/SGACL
• L2 or L3 (IP lite) • L2 or L3 (IP • L2 or L3 (IP • L2 or L3 (IP PoE/PoE+ ports Roadmap • Up to 8 • Layer 2 NAT • MACSec
PoE/PoE+
• Small form factor services) services) services) • REP • Layer 3 • Up to 12 or 24 • FNF
• 1 RU ports PoE/PoE+
• IP30, IP67 • Small form factor • Modular • IEEE1588 PTP • Profinet PoE/PoE+ • TSN-ready
• 2 GE uplink • FNF, REP • Dying gasp
• Lightly-managed • MRP, REP • PRP, REP • Up to 26 ports Roadmap • TrustSec® • Dying gasp • Stacking*
• Layer 2 NAT • IEEE 1588 PTP • REP ports • IEEE1588 PTP • Cisco TrustSec®
• Layer 2 only • Profinet Roadmap SGT/SGACL SGT/SGACL • Cisco® TrustSec • Conformal
• IEEE1588 PTP (default and • IEEE1588 PTP • 24 FE downlink
• 30 sec bootup ports • Cisco DNA • Layer 3 • Layer 2 NAT, • MACSec, FNF SGT/SGACL coating*
time • Up to 8 power profiles) v2
• REP Essentials • MACSec • MACSec • Time-Sensitive • MACSec • Iox-ready
• Web config tool PoE/PoE+ ports • Up to 4 • Up to 8
• Conformal PoE/PoE+ ports PoE/PoE+ • 8 PoE/PoE+ • Profinet • MRP, PRP, HSR Network (TSN) • TSN-ready • MRP, REP, PRP
• Up to 8 ports, 16 SFP, • IOX • Iox-ready
coating * • Conformal ports • MRP • IOx • HSR
PoE/PoE+ ports or 24 copper • TSN • MRP, REP, PRP
• Cisco DNA coating * • Cisco DNA • Cisco DNA • MRP, REP, PRP • Timing interfaces
Essentials Essentials • IEEE 1588 PTP • SDA FE • HSR (IRIG-B, GPS)
(default and Essentials • HSR
• Cisco DNA • Cisco DNA • Cisco DNA • Cisco DNA • Cisco DNA
power profiles) Essentials Essentials/
* Advantage Essentials/ Essentials/
• Cisco DNA Advantage Advantage Advantage
Advantage
10/100M 1G 10G
No PTP on IE1000 ‘*’ –Selected Models
PTP support in Cisco IE Switches
PTP IE-2000 / IE-2000U / IE-4000 IE-4010 IE-5000 IE-3x00

Feature IE-3000 CGS-2520
Profiles • Default • Power • Default, • Default • Default • Default
• Power • Power • Power • Power • Power
• 802.1AS
Clock • GMC • GMC • GMC • GMC • GMC • GMC
modes • BC • BC • BC • BC • BC • BC
• E2E-TC • P2P-TC • E2E-TC • E2E-TC • E2E-TC • E2E-TC
• P2P-TC • P2P-TC • P2P-TC • P2P-TC • P2P-TC
• PTP 2-Step only
• Multicast PTP messages only
IE Switch default PTP configuration
• Profile: Default profile (for IE Switches that support default profiles)
• Mode: end to end transparent – is always the default. Least impacting.
• Clock Domain - 0
IE4K-8# show ptp clock
PTP CLOCK INFO
PTP Device Type: End to End transparent clock
PTP Device Profile: Default Profile
Clock Identity: 0xF4:4E:5:FF:FE:E5:85:80
Clock Domain: 0
Delay Mechanism: End to End
Local clock time: 16:25:06 PDT Dec 31 2018
PTP – Configure Profile on IE switch
Desired Profile CLI to configure
Default Profile - default*; nothing to configure * - unless Power Profile only

- Negate current profile
Switch(config)# no ptp profile power

Power Profile Switch(config)# ptp profile power
802.1AS Switch(config)# ptp profile 802.1as
PTP Modes per profile Default Profile Power Profile 802.1AS
Modes • Boundary Clock • Boundary Clock • GMC-BC

• E2E transparent, • E2E transparent, • P2PTransparent
• Forward, • Forward,
• GMC-BC • GMC-BC
IE Switching – Mode details
Mode name details
Boundary Clock Only peer delay mode is supported
GMC-BC Automatically selects NTP as time source (‘flywheel’)
E2E transparent Selects bridge to operate in transparent mode for

Default Profile
P2p transparent Selects bridge to operate in transparent mode for
power profile
Forward Forwards PTP without processing. – disables PTP
No changes for resident time
Treats PTP as normal Mcast traffic
IE Switching configuration table
• Possible configuration for different Modes/Profiles
Feature Default Profile Power Profile 802.1AS
Modes Boundary Clock Boundary, GMC-BC or

E2E transparent, P2P Transparent, P2PTransparent
Forward, Forward,
GMC-BC GMC-BC
Transparent clock End to End Peer to Peer Peer to Peer
Allow Announce without TLV No yes no
Tune PTP Adaptive filters No Yes no
Neighbor propagation delay No No yes

threshold
Persistence with previous GM’s Yes Yes no
time property
Domain Yes Yes yes
IE switch PTP configuration: all Profiles
Global Configuration parameters
Feature CLI string What it does
common to all Profiles
When to use
domain Identifies the PTP domain IE support single domain
Priority1, priority2 Influences BMCA to choose GMC, Identify on BC to be the GMC.

and also redundant GMC in case of Default and 802.1as profiles only. Not
primary failure in power profile
Mode Configure BC or TC Default and Power profile only
Not in 802.1as profile
Time-property persist <value> Preserve time on the OC during a In Default and 802.1as. Only as BC.
change in GMC Prevent time jumps during BMCA on
primary failover.
Interface level configuration common to all Profiles
Feature CLI string What it does When to use

Enable Enable disable PTP at interface Stop PTP processing on an interface.
Possible to force PTP to use another
IE switch PTP configuration: Default Profile
• Unique Global PTP config for Default Profile in Boundary clock mode

Transfer feedforward BC sync algorithm that does The BC internal clock will behave like a TC. If your organization
not filter PDV believes this is better than ‘linear filtering’. Best for networks
where all Bridges support PTP, and PDV is minimal.
Still terminates Delay_req. Minimizes cascading error effect of too
many BC in a row.
OCs will sync faster
Transfer filter adaptive BC Sync algorithm that filters For BCs in networks with lots of PDV. Bridges that do not support
as much PDV as possible PTP or with wireless bridges.
Transfer filter linear BC Sync algorithm provides This is the default setting. Use when you don’t know the PDV in the
a simple linear filter network
IE switch PTP configuration Default Profile
• Interface level PTP config for Default Profile
Announce interval Interval time between announce msgs When working with equipment that requires a different
behavior other than default time intervals
Announce timeout Time Interval to declare announce msg When working with equipment working correctly but could
timeout potentially miss announce msgs for more than 8 seconds
(the default timeout)
delay-req interval Interval to send delay-Req when ports Default is 1 second. Change when devices that need
is in Master state (device is slave) slower or faster delay-req msg intervals
Sync interval Changes frequency of ‘Sync’ msgs The BC or GMC sends Sync msgs 1 per second. Faster
transmits Sync’s converge faster cause more CPU cycles on OCs
and BCs. Slower syncs converge slower, less CPU
intense.
Sync limit Max offset until attempt to resync Only in BC mode. if there’s significant drift being
experienced, then shorten the sync limit to lessen the
drift. The default is the max of 0.5 seconds.
vlan PTP Vlan on Trunk port For BC’s, change the 802.1Q tagged Vlan for PTP
messages. Needs to be same Vlan tag on both ends of
Ethernet link.
IE switch PTP configuration Power Profile
• Unique Global PTP config for Power Profile

Transfer filter adaptive BC Sync algorithm that filters as much PDV as For BCs in networks with lots of PDV. Bridges
possible that do not support PTP or with wireless bridges.
Transfer filter linear BC Sync algorithm provides a simple linear This is the default setting. Use when you don’t
filter know the PDV in the network
Allow-without-TLV Does not drop Announce msgs from non GMC not compliant, sends Announce msgs
compliant GMC. Uses PTP from non without specific TLVs
compliant GMC
IE switch PTP configuration Power Profile
• Interface level PTP config for power Profile
Announce interval Interval time between announce msgs Change default Faster or slower BMCA convergence.
Default is 2 seconds
Announce timeout Interval time to announce timeout msgs Change default for Faster or slower BMCA
convergence. Too Fast and wrong GMC wins BMCA,
too slow and Servo drifts longer. Default is 8 seconds
Pdelay-req interval Interval to send Pdelay-Req when ports is in Default is 1 second. Networks with lots of PDV, more
Master state (device is slave) msgs/sec better sync
Sync interval Changes frequency of ‘Sync’ msgs transmits
Sync limit Max offset until attempt to resync Only in BC mode if there’s significant drift being
experienced, then shorten the sync limit to lessen the
drift. The default is the max of 0.5 seconds.
vlan PTP Vlan on Trunk port change the 802.1Q tagged Vlan for PTP
messages. Needs to be same Vlan tag on both ends
of Ethernet link.
IE switch PTP configuration 802.1AS Profile
• Unique Global PTP config for 802.1AS profile
neighbor-propagation-delay-threshold Limits the amount of time a neighbor can some end devices are not fully compliant
report as its delay. to 802.1AS and they do not calibrate their
PTP timestamps correctly. Without
calibration, IE switch mark good enough
end devices as bad. This CLI adjusts the
good/bad threshold.
adaptive-filter-params cost-function Adjusts the internal working of the Servo Only modify when you know what you’re
adaptive-filter-params group doing. Consult with Cisco AM/SE
adaptive-filter-params merge
adaptive-filter-params ptpdev
adaptive-filter-params rate
adaptive-filter-params training
Troubleshooting on the
Cisco Switch
How to read ‘show ptp clock’ output on GM
Role GMC, BC, or TC

PTP CLOCK INFO
PTP Device Type: Grand Master clock - Boundary clock Active PTP Profile
PTP Device Profile: Power Profile
Clock Identity: 0x18:8B:9D:FF:FE:75:EC:0
Clock Domain: 0 MAC Address of Bridge
Number of PTP ports: 28 Domain ID
PTP Packet priority: 4
Priority1: 128 BC clock transfers algorithm
Priority2: 128
Clock Quality:
Class: 13 Path delay from GMC
Accuracy: Within 1s
Offset From Master(ns): 0 Steps removed from GMC
Mean Path Delay(ns): 0 0 = GMC
Steps Removed: 0
Local clock time: 02:57:48 UTC Nov 15 2018
How to read ‘show ptp clock’ output on slave BC
Role GMC, BC, or TC
IIE4010-16S12P# show ptp clock

PTP CLOCK INFO
Active PTP Profile
Clock Identity: 0x50:1C:B0:FF:FE:23:14:80
Clock Domain: 0 MAC Address of Bridge
PTP Packet priority: 4
Priority1: 128 BC clock transfers algorithm
Priority2: 128
Clock Quality:
Class: 248
Accuracy: Unknown Path delay from GMC
Mean Path Delay(ns): 14 Steps removed from GMC
Steps Removed: 1 1 = GMC is neighbor
How to read ‘show ptp parent’ output on GMC
When IE Bridge is GMC
IE5000-2004# show ptp parent

PTP PARENT PROPERTIES
Parent Clock: MAC of this Bridge
Parent Clock Identity: 0x18:8B:9D:FF:FE:75:EC:0
Parent Port Number: 0
Observed Parent Offset (log variance): N/A
Observed Parent Clock Phase Change Rate: N/A
Grandmaster Clock: MAC of GMC

Grandmaster Clock Identity: 0x18:8B:9D:FF:FE:75:EC:0
Grandmaster Clock Quality:
Class: 13
Accuracy: Within 1s
Priority1: 128
Priority2: 128
How to read ‘show ptp parent’ output on BC
Slave
When IE Bridge is not GMC
IE4010-16S12P# show ptp parent

Parent Clock: MAC of Parent
Parent Clock Identity: 0x18:8B:9D:FF:FE:75:EC:0 Same as GMC because GMC
Parent Port Number: 2 is the next hop
Grandmaster Clock: MAC of GMC

Grandmaster Clock Identity: 0x18:8B:9D:FF:FE:75:EC:0
Class: 13
Accuracy: Within 1s
Priority1: 128
Priority2: 128
Layout with 3 Boundary clocks
• Clocks downstream from BC see upstream BC as GM (steps removed)
GMC-BC Upstream BC Downsteam BC
IE5000-2004# show ptp clock IE4010-16S12P# show ptp clock

PTP CLOCK INFO IE4010-24P# show ptp clock
PTP CLOCK INFO
PTP Device Type: Grand Master clock – PTP CLOCK INFO
PTP Device Profile: Power Profile PTP Device Type: Boundary clock
Clock Identity: 0x18:8B:9D:FF:FE:75:EC:0 PTP Device Profile: Power Profile
Clock Identity: 0x50:1C:B0:FF:FE:23:14:80
Clock Domain: 0 Clock Identity: 0x0:6B:F1:FF:FE:68:D2:0
Clock Domain: 0
Number of PTP ports: 28 Clock Domain: 0
Time Transfer: Linear Filter Number of PTP ports: 28
Priority1: 128 PTP Packet priority: 4
Priority1: 128
Priority2: 128 Time Transfer: Linear Filter
Priority2: 128
Clock Quality: Priority1: 128
Clock Quality:
Class: 248 Priority2: 128
Class: 248
Accuracy: unknown Clock Quality:
Accuracy: Unknown
Offset (log variance): N/A Class: 248
Offset From Master(ns): 0 Accuracy: Unknown
Mean Path Delay(ns): 0 Offset (log variance): N/A
Steps Removed: 0 Offset From Master(ns): -4
Steps Removed: 1
Local clock time: 02:57:48 UTC Nov 15 2018 Mean Path Delay(ns): 10
Steps Removed: 2
Local clock time: 14:37:34 UTC Apr 1 2000
PTP Parent output debugging
• Third downstream BC output from PTP Parent
GMC-BC Upstream BC Downsteam BC
0x50:1C:B0:FF:FE:23:14:80
0x18:8B:9D:FF:FE:75:EC:0
IE4010-24P# show ptp parent
Parent Clock:
Parent is upstream BC Parent Clock Identity: 0x50:1C:B0:FF:FE:23:14:80
Parent Port Number: 1
Grandmaster Clock:
GMC is not same as parent Grandmaster Clock Identity: 0x18:8B:9D:FF:FE:75:EC:0
Class: 248
Accuracy: Unknown
Priority1: 120
Priority2: 128
Syslog for PTP master change
• IF PTP Master Frequent changes – issues with BMCA algorithms
• Example PTP master change syslog
• Easy fix – change priority1 or priority 2 value on desired GMC
• Harder fix – change the announce msg times
Switch# show logging

Jan 21 20:10:59.969: %PTP-6-GRANDMASTER_CLOCK_CHANGE_TO_LOCAL:
Old grandmaster clock identity: 0x18:8B:9D:FF:FE:75:EC:0,
New grandmaster clock identity: 0x50:1C:B0:FF:FE:23:14:80 (local system)
Debug commands overview
IE4010-16S12P# debug ptp ? Really Chatty with lots of
bmc PTP Best Master Clock Algorithm details. useful to SW Engr only
clock-correction PTP Clock correction
collision PTP source collision
error PTP errors State machine of port (M,S), announce msgs,
event PTP state event errors in Sync time stamps
messages PTP messages No output – no errors perceived by IE switch
platform PTP platform
transparent-clock PTP transparent clock No significant benefit to end user
IE4010-16S12P# undebug all Sync msg tracking
Debug PTP BMC
IE4010-16S12P#
IE4010-16S12P#
Jan 21 20:29:37.915: Compare: clock-A: GM Id: 0x50:1C:B0:FF:FE:23:14:80, FM port num: 0, Rx port num: 0
Jan 21 20:29:37.915: with clock-B: GM Id: 0x18:8B:9D:FF:FE:75:EC:0, FM port num: 2, Rx port num: 2
Jan 21 20:29:37.915: B is better for lower Priority1 value (128:120)
Jan 21 20:29:37.915: Ebest = 0x21A0DA68, Er_best = 0x21A0C4CC
Jan 21 20:29:37.915: Ebest->received_port = 2 , Er_best->received_port = 2
Announce msgs every 2

seconds by default © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 75
Debug PTP Messages – Ports and messages
IE4010-16S12P#debug ptp messages
PTP Messages debugging is on
IE4010-16S12P#
Jan 21 20:37:33.358: PTP message sent: intf: GigabitEthernet1/1, type: SYNC
Jan 21 20:37:33.781: PTP message received, intf: GigabitEthernet1/2, vlan_id: 1, type: SYNC, seq_id: 18109
Jan 21 20:37:33.781: PTP message received, intf: GigabitEthernet1/2, vlan_id: 1, type: FOLLOWUP, seq_id: 18109
Jan 21 20:37:33.872: PTP message received, intf: GigabitEthernet1/2, vlan_id: 1, type: ANNOUNCE, seq_id: 11037
Jan 21 20:37:34.295: PTP message sent: intf: GigabitEthernet1/1, type: ANNOUNCE
Jan 21 20:37:35.871: PTP message received, intf: GigabitEthernet1/2, vlan_id: 1, type: ANNOUNCE, seq_id: 11038
Issues with Vlan tagging
Power Profile & 802.1AS mode

• interface is configured as an access port, PTP messages are sent as untagged, Layer 2 packets
• interface is configured as a trunk port, PTP packets are sent as 802.1q tagged Layer 2 packets over the port native VLAN
Default Profile mode

• interface is configured as an trunk port, PTP messages are sent as untagged, Layer 2 packets on native
- use ‘vlan dot1q tag native’ to tag PTP on Native vlan.
End Device requires Vlan Tagged PTP – power
profile (1)
• On Cisco IE - Announce and Sync msgs
• Received accepted on any Vlan.
• FWD on same Vlan
• On Cisco IE Switches as P2P TC P2P-Prior to 15.2(6)x and earlier
• Peer delay msgs sent tagged on native vlan on Trunk interfaces
• Interface toward GMC
• Configure Native Vlan to match expected Vlan from GMC
• Configure as Trunk “switchport mode trunk”
• “Vlan tag dot1q native” just in case.
• This will ensure that Sync, Announce, Peer Delay, Peer Delay Request on same vlan
End Device requires Vlan Tagged PTP – power
profile (2)
• When GMC configures VLAN for PTP Announce and Sync
• On Cisco IE Switches as P2P TC - 15.2(7)E (Feb/Mar 2019) and later
• Configure ‘PTP vlan x’ to match Vlan used by GMC
• PTP Vlan configured per interface for Delay msgs
• PTP Vlan different than Native vlan
• All announce, sync, Pdelay_req, Pdelay-resp on same Vlan
• Default : PTP uses native vlan – when PTP Vlan not configured.
• “Vlan tag dot1q native” as work around
PTP in ring topologies
• Main Consideration is for Topo
change
• BC configured on Gateway Bridges Grandmaster
Clock
• TC’s on Bridges inside Ring Grandmaster

BC Clock
• STP issue not blocking PTP mcast
on STP Blk Link BC BC
BC
REP Edge REP Edge

• Fixed in latest IOS SW
Transparent Transparent
Transparent
Not an issue with REP
Clock Clock
• Clock Transparent
STP
Clock
REP
Transparent
Clock Transparent
Transparent Transparent Clock
Clock Clock
PTP not working - Spanning tree PortFast
• Issue: STP Topology change in Network causing PTP sync loss
downstream
• Tough to debug because Topo change not near the impacted OC
• STP topo change causes links from Bridges to BLK pending reconvergence
• 1 second with RSTP/MSTP, 30 seconds STP
Grandmaster
• Configure STP Portfast on links to non-Bridges Clock
• Does not stop FWD on STP topo change BC
• Link A to an Ordinary Clock Transparent Transparent

Clock
With Portfast – not impacted by Topo change
Clock
•
• Without Portfast – loses PTP sync Link A STP
Ordinary Transparent Transparent

Clock Clock Clock
Mismatch profiles
• IE4K running power profile – OC running default profile
• Client not syncing
IE4010-24P#show ptp port gi1/22

PTP PORT DATASET: GigabitEthernet1/22
Port identity: clock identity: 0x0:6B:F1:FF:FE:68:D2:0
Port identity: port number: 22
PTP version: 2
Port state: MASTER
Delay request interval(log mean): 5
Announce receipt time out: 3 Note: Field not present in Default End to End TC
Peer mean path delay(ns): 0
Announce interval(log mean): 0
Sync interval(log mean): 0
Delay Mechanism: Peer to Peer
Peer delay request interval(log mean): 0
Sync fault limit: 500000
Same Profiles – Default profile
• Both switch and OC in default profile
• Client syncing
IE4010-24P#show ptp port gi1/22

PTP PORT DATASET: GigabitEthernet1/22
Port identity: clock identity: 0x0:6B:F1:FF:FE:68:D2:0
Port identity: port number: 22
PTP version: 2
Port state: MASTER
Delay request interval(log mean): 5
Announce receipt time out: 3
Announce interval(log mean): 1
Sync interval(log mean): 0
Delay Mechanism: End to End
Peer delay request interval(log mean): 5
Sync fault limit: 500000
Closing Notes
PTP in Industrial / Utility deployments
• Transparent (end to end , and peer to peer ) is easiest, and least impactful
• Announce messages – more frequent is better in ‘well behaved’ networks
• Faster convergence during Primary GMC failure
• Sync messages – more frequent is better in ‘well behaved’ networks
• Faster convergence during Topo change
• GMC overloaded with Delay_Requests from OCs
• Convert a Transparent Clock to Boundary Clock
• Use Default Profile in Networks with non PTP aware bridges.
Cisco Webex Teams
Questions?
Use Cisco Webex Teams (formerly Cisco Spark)
to chat with the speaker after the session
How
1 Find this session in the Cisco Events Mobile App
2 Click “Join the Discussion”
3 Install Webex Teams or go directly to the team space
4 Enter messages/questions in the team space
cs.co/ciscolivebot#BRKIOT-2517
Complete your online
session survey
• Please complete your Online Session
Survey after each session
• Complete 4 Session Surveys & the Overall
Conference Survey (available from
Thursday) to receive your Cisco Live T-
shirt
• All surveys can be completed via the Cisco
Events Mobile App or the Communication
Stations
Don’t forget: Cisco Live sessions will be available for viewing

on demand after the event at ciscolive.cisco.com
Continue Your Education
Demos in Meet the Related

Walk-in
the Cisco engineer sessions
self-paced
Showcase labs 1:1
meetings
Thank you
Backup
Ubuntu PTP notes
• Install ptpd
• upgrade to 16.4 LTS
sudo apt-get install ptpd
• Generate a default config file

Sudo ptpd –O > ./ptpd_config.txt

Brkiot 2517

Uploaded by

Copyright:

Available Formats

Brkiot 2517

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Brkiot 2517

Uploaded by

Copyright:

Available Formats

BRKIOT-2517

Precision Time Protocol -

Configuring PTP on Cisco IE Switches

• Profile, modes and changing the defaults

Troubleshooting: How to know its working?

• Clocks in cascaded topologies: Transparent Ordinary

Red VLAN Green VLAN

• GMC – Grand Master Clock (Master)

• OC – Ordinary clock (eg: slave)

• E2E TC – End to End Transparent clock

• P2P TC – Peer to Peer transparent clock

• PDV – packet Delay Variation

• M – designates an interface is in Master mode

• S – designates an interface is in Slave Mode

• Follow_Up master to all slaves, contains time t1; only in two-step

Offset = difference between the master and slave clock

Delay 1 = Delay 2 t1, t2

It’s all statistics…

Announce 1 Second 2 second intervals

Follow-up ( two step only) Triggered by Sync Triggered by Sync

Delay Request NA 32 seconds to slaves from

Peer Delay Request 1 second; NA

A ‘typical’ Ethernet network topology

A single PTP Domain M

throughout the PTP Domain

Starts from GMC

sync sync sync

throughout the PTP Domain

Starts at ordinary clocks

• Other popular profiles

IEEE Standard IEEE 1588 v2 (J.3) IEEE C37.238 IEEE 802.1AS

Supported modes Boundary & Boundary & Not configurable.

Transport UDP over IP (multicast & L2 Multicast L2 Multicast

Transparent End to End Peer to Peer Peer to Peer

L2 MAC Mgs 01-80-C2-00-00-0E Mgs 01-80-C2-00-00-0E

IPv4 Addresses 224.0.1.129 Peer Delay 224.0.0.107

Sync msg rate 32 second intervals* 1 / second 8 / second

Vlan Tagging Untagged on Native Mandatory or vlan 0 Prohibited

‘*’ – burst at beginning to get mean delay

IEEE1588 ITU G.8265.1 IEEE C37.238

Announce messages are used for BMCA

• Class is 248 when free running on internal Oscillator

IRIG-B In & Out Analog

IRIG-B In & Out TTL

TimeStamp Switch TimeStamp Switch

Transparent Clock Operation Boundary Clock Operation

PTP msgs M M M M Switch Port

• Spans across VLANs

• Shields Slaves from Transients due to hierarchy changes (BMCA)

• Cumulative error: Limit to number of BCs in a row from GMC

• Peer-to-Peer TCs can converge faster after network topology

BC2 BC3 BCX

OC1 OC10 OC11 OC20 OC21

Why not just make all the TCs into BCs?

• Precision error compounded at each BC (due to MTIE + MTIE )

Choose BC for IE Switch Choose TC for IE Switch

• Change Vlans • Power utilities – mandate P2P

• Layer 2 • Layer 2 • Layer 2

Best in class IE 5000

Default Profile - default; nothing to configure - unless Power Profile only