The tmnxPtpCardNotSupported notification is generated when the
Precision Timing Protocol (PTP) is enabled on a card that is not
capable of clock recovery using PTP.
          
This notification is triggered when the
TIMETRA-CHASSIS-MIB::tmnxCpmCardOscillatorType is not 'ocxo (3)', the
tmnxPtpClockClockType is set to 'ordinarySlave (1)' or 'boundary (3)',
and tmnxPtpClockAdminState is set to 'inService (2)'.
          
[EFFECT] While this event is active, tmnxPtpClockOperState will be
'outOfService (3)' on the card that this notification was generated.
          
[RECOVERY] This event is cleared when a replacement CPM card with an
Oscillator of type 'ocxo (3)' is inserted.
          
tmnxPtpCardNotSupportedClear is generated when this event is cleared.

The tmnxPtpCardNotSupportedClear notification is generated when the
tmnxPtpCardNotSupported event is cleared for a particular CPM card.

The tmnxPtpMasterClockChangedEvent is generated when the Master/Parent
Clock for the Precision Timing Protocol (PTP) changes on the system.

The tmnxPtpClockRecoveryStateChange is generated when the Precision
Timing Protocol (PTP) clock recovery state changes on the system.

The tmnxPtpOutOfResources notification is generated when the Precision
Timing Protocol (PTP) process on the card is out of resources.
          
This may occur in either two situations:
1.  The number of PTP peers exceeds the system limit.
2.  The total unicast packet rate negotiated with all PTP peers
    has reached the maximum packet rate supported by the system.
    Exceeding this rate would impact the ability of the master clock
    to provide an accurate stream of timing packets to each remote
    slave clock.
          
If either of the two situations above occur, the PTP process will
reject any new unicast packet requests from remote slave PTP peers.
          
tmnxPtpOutOfResourcesClear is generated when this event is cleared.

The tmnxPtpOutOfResourcesClear notification is generated when both the
total number of active PTP peers and the total negotiated unicast
packet rate goes below 90% of the system limit.

The tmnxPtpDynamicChange notification is generated when an object
dynamically (i.e. not by configuration) changes state. This
notification identifies the affected row.

[CAUSE] The tmnxPtpPortNoTimestamping notification is generated when a
PTP port is created and the associated Ethernet port does not support
IEEE 1588-2008 port-based timestamping.
          
[EFFECT] The PTP port is created but the performance may be degraded
due to timestamping at the CPM. For optimal performance, ensure PTP is
enabled on ports with IEEE 1588-2008 port-based timestamping
capability.
          
[RECOVERY] The Ethernet port used for the PTP port should be changed
to a port on an MDA that supports IEEE 1588-2008 port-based
timestamping.