In this section
This section describes how to set the PTP profile.
The PTP profile is specified by the PtpProfile parameter. The purpose of a PTP profile is to allow organizations to specify a specific selection of PTP parameter values and optional features that work together, when using the same transport protocol. In this way a performance that meets the requirements of a particular application can be achieved.
A PTP profile can define:
- Best master clock algorithm options
- Configuration management options
- Path delay mechanisms (peer delay or delay request response)
- Range and default values of all PTP configurable parameters and data set members
- Required, permitted, or prohibited transport mechanisms
- Required, permitted, or prohibited node types
- Required, permitted, or prohibited options
Available PTP profiles
The SmartNICs support these profiles:
- Default profile (profile ID: 00-1B-19-00-01-00)
- Telecom profile (profile ID: 00-19-A7-00-01-00)
- Power profile (profile ID: 1C-12-9D-00-00-00)
- Enterprise profile (profile ID: 00-00-5E-00-01-00)
- G.8275.1 profile (profile ID: 00:19:A7:01:02:00 )
The Default profile represents the PTP Default delay request profile and uses the same default parameter settings. However the ranges are wider and only limited by the capability of the NT SmartNICs.
The Telecom profile uses an alternate BMCA (Best Master Clock algorithm), unicast mode on IPv4/UDP and E2E delay mechanism.
The Power profile uses extended TLV information on announce messages to identify a Power profile compliant master. When this profile is used, no other announce messages are considered; thus only Power profile compliant masters are used. Information from these TLVs is to be retrieved through the information stream. The Power profile uses the PTP default BMCA, multicast mode, P2P delay mechanism and IEEE 803.2 communication technology.
The Enterprise profile uses the PTP default BMCA, E2E delay mechanism and IPv4/UDP transport mechanism. The profile allows delay requests to be sent either as multicast messages or as unicast messages. When the Enterprise profile is used, the Napatech slave SmartNIC will send delay requests as unicast messages.
The G.8275.1 profile uses the PTP default BMCA, E2E delay mechanism and IEEE802.3 transport mechanism. When the G.8275.1 profile is used, the Napatech slave SmartNIC will send delay requests as multicast messages.
ntservice.ini code line
The syntax for the ntservice.ini code line setting the PTP profile is:
'PtpProfile' '=' ( 'Default' | 'Telecom' | 'Power' | 'Enterprise' | 'G.8275.1' )
This table shows the default value.