Step 1 |
configure
|
|
Step 2 | interface
type
interface-path-id
Example:
RP/0/RSP0/CPU0:router(config)# interface gigabitethernet
0/1/0/1
|
Enters
interface configuration mode for the specified interface.
|
Step 3 | ptp
Example:
RP/0/RSP0/CPU0:router(config-if)# ptp
|
Enters PTP
interface configuration mode.
|
Step 4 | profile
name
Example:
RP/0/RSP0/CPU0:router(config-if-ptp)# profile tele64
|
Attaches a
previously-defined profile to this interface. Profiles are defined in global
PTP configuration mode.
Note
|
Any
configurations made in PTP interface configuration mode override the global
profile settings.
|
|
Step 5 |
sync
frequency
rate
Example:
RP/0/RSP0/CPU0:router(config-if-ptp)# sync frequency 128
|
Configures the
interval between sending Sync messages. Valid values are 2, 4, 8, 16, 32, 64 or
128.
|
Step 6 |
delay-request
frequency
rate
Example:
RP/0/RSP0/CPU0:router(config-if-ptp)# delay-request
frequency 128
|
Configures the
interval between sending Delay Request messages. Valid values are 2, 4, 8, 16,
32, 64 or 128.
|
Step 7 |
announce grant-duration
duration
Example:
RP/0/RSP0/CPU0:router(config-if-ptp)# announce
grant-duration 120
|
Specifies the
Announce message grant duration, in seconds. Values can range from 60 to 1000.
If the port is in slave state, this is the length of grant that is requested.
If the port is in master mode, this is the maximum grant allowed.
|
Step 8 | sync grant-duration
duration
Example:
RP/0/RSP0/CPU0:router(config-if-ptp)# sync grant-duration 120
|
Specifies the
Sync message grant duration, in seconds. Values can range from 60 to 1000. If
the port is in slave state, this is the length of grant requested. If the port
is in master mode, this is the maximum grant allowed.
|
Step 9 | delay-response grant-duration
duration
Example:
RP/0/RSP0/CPU0:router(config-if-ptp)# delay-response
grant-duration 120
|
Specifies the
Delay Response message grant duration in seconds. Values can range from 60 to
1000. If the port is in slave state, this is the length of the grant requested.
If the port is in master mode, this is the maximum grant allowed.
|
Step 10 | sync timeout
timeout
Example:
RP/0/RSP0/CPU0:router(config-if-ptp)# sync timeout 120
|
Specifies the
length of time in micro seconds that Sync messages are not received before a
PTSF-lossSync is raised. Values can range from 100 to 10000.
|
Step 11 | delay-response timeout
timeout
Example:
RP/0/RSP0/CPU0:router(config-if-ptp)# delay-response
timeout 120
|
Specifies the
length of time, in micro seconds, that Delay Response messages are not received
before a PTSF-lossSync is raised. Values can range from 100 to 10000.
|
Step 12 | unicast-grant
invalid-request {reduce |
deny}
Example:
RP/0/RSP0/CPU0:router(config-if-ptp)# unicast-grant
invalid-request reduce
|
Specifies
whether unicast grant requests with unacceptable parameters are denied or
granted with reduced parameters.
|
Step 13 | master{ipv4
ip-address|ipv6
ip-address}
Example:
RP/0/RSP0/CPU0:router(config-if-ptp)# master ipv4
192.168.2.1
RP/0/RSP0/CPU0:router(config-if-ptp)# master ipv6 2001:DB8::1
|
Specifies the
IPv4 address or the IPv6 address for the PTP master that the interface should
listen to. Multiple masters can be configured.
|
Step 14 | clock-class
class
Example:
RP/0/RSP0/CPU0:router(config-if-ptp-master)# clock-class 2
|
Overrides the
clock class received in announce messages from this master. Values can range
from 0 to 255.
|
Step 15 | Use one of these
commands:
Example:
RP/0/RSP0/CPU0:router(config-if-ptp-master)# end
or
RP/0/RSP0/CPU0:router(config-if-ptp-master)# commit
|
Saves
configuration changes.
-
When you
issue the
end command,
the system prompts you to commit changes:
Uncommitted changes found, commit them
before exiting(yes/no/cancel)? [cancel]:
-
Entering
yes saves configuration changes to the running
configuration file, exits the configuration session, and returns the router to
EXEC mode.
-
Entering
no exits the configuration session and returns the
router to EXEC mode without committing the configuration changes.
-
Entering
cancel leaves the router in the current
configuration session without exiting or committing the configuration changes.
-
Use the
commit
command to save the configuration changes to the
running configuration file, and remain within the configuration session.
|