PTP
tmnxPtpCardNotSupported
Property name | Value |
---|---|
Application name |
PTP |
Event ID | 2001 |
Event name |
tmnxPtpCardNotSupported |
SNMP notification prefix and OID |
TIMETRA-PTP-MIB.tmnxPtp1588Notifications.1 |
Default severity |
minor |
Source stream | main |
Message format string |
CPM $tmnxCpmCardSlotNum$ does not support IEEE1588 (PTP) operation for the configured clock-type |
Cause | 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. |
tmnxPtpCardNotSupportedClear
Property name | Value |
---|---|
Application name |
PTP |
Event ID | 2002 |
Event name |
tmnxPtpCardNotSupportedClear |
SNMP notification prefix and OID |
TIMETRA-PTP-MIB.tmnxPtp1588Notifications.2 |
Default severity |
minor |
Source stream | main |
Message format string | CPM $tmnxCpmCardSlotNum$ supports IEEE1588 (PTP) operation for the configured clock-type |
Cause | The tmnxPtpCardNotSupportedClear notification is generated when the tmnxPtpCardNotSupported event is cleared for a particular CPM card. |
Effect | N/A |
Recovery | N/A |
tmnxPtpClockRecoveryStateChange
Property name | Value |
---|---|
Application name |
PTP |
Event ID | 2004 |
Event name |
tmnxPtpClockRecoveryStateChange |
SNMP notification prefix and OID |
TIMETRA-PTP-MIB.tmnxPtp1588Notifications.4 |
Default severity |
minor |
Source stream | main |
Message format string | IEEE1588 (PTP) Frequency Recovery state: $tmnxPtpClockRecoveryState$ |
Cause | The tmnxPtpClockRecoveryStateChange is generated when the Precision Timing Protocol (PTP) clock recovery state changes on the system. |
Effect | N/A |
Recovery | N/A |
tmnxPtpDynamicChange
Property name | Value |
---|---|
Application name |
PTP |
Event ID | 2007 |
Event name |
tmnxPtpDynamicChange |
SNMP notification prefix and OID |
TIMETRA-PTP-MIB.tmnxPtp1588Notifications.7 |
Default severity |
minor |
Source stream | main |
Message format string |
IEEE1588 (PTP) $tmnxPtpNotifyRowDescription$ |
Cause |
The tmnxPtpDynamicChange notification is generated when an object dynamically (i.e. not by configuration) changes state. This notification identifies the affected row. |
Effect | N/A |
Recovery | N/A |
tmnxPtpMasterClockChangedEvent
Property name | Value |
---|---|
Application name |
PTP |
Event ID | 2003 |
Event name |
tmnxPtpMasterClockChangedEvent |
SNMP notification prefix and OID |
TIMETRA-PTP-MIB.tmnxPtp1588Notifications.3 |
Default severity |
minor |
Source stream | main |
Message format string | PTP Parent Clock changed. New Parent $tmnxPtpMasterClockAddress$, Old Parent $tmnxPtpMasterClockLastIpAddress$. |
Cause | The tmnxPtpMasterClockChangedEvent is generated when the Master/Parent Clock for the Precision Timing Protocol (PTP) changes on the system. |
Effect | N/A |
Recovery | N/A |
tmnxPtpOutOfResources
Property name | Value |
---|---|
Application name |
PTP |
Event ID | 2005 |
Event name |
tmnxPtpOutOfResources |
SNMP notification prefix and OID |
TIMETRA-PTP-MIB.tmnxPtp1588Notifications.5 |
Default severity |
minor |
Source stream | main |
Message format string |
IEEE1588 (PTP) Card $tmnxChassisNotifyHwIndex$ out of resources |
Cause |
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. |
Effect | N/A |
Recovery | N/A |
tmnxPtpOutOfResourcesClear
Property name | Value |
---|---|
Application name |
PTP |
Event ID | 2006 |
Event name |
tmnxPtpOutOfResourcesClear |
SNMP notification prefix and OID |
TIMETRA-PTP-MIB.tmnxPtp1588Notifications.6 |
Default severity |
minor |
Source stream | main |
Message format string | IEEE1588 (PTP) Card $tmnxChassisNotifyHwIndex$ out of resources cleared |
Cause | 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. |
Effect | N/A |
Recovery | N/A |
tmnxPtpPeerNoRxTimestamping
Property name | Value |
---|---|
Application name |
PTP |
Event ID | 2015 |
Event name |
tmnxPtpPeerNoRxTimestamping |
SNMP notification prefix and OID |
TIMETRA-PTP-MIB.tmnxPtp1588Notifications.15 |
Default severity |
minor |
Source stream | main |
Message format string | Timestamping of receive communications with peer $tmnxPtpPeerIpAddress$ is performed at the CPM. Performance may be degraded. |
Cause | The tmnxPtpPeerNoRxTimestamping notification is generated on initial exchange of PTP event messages with a peer and whenever the location of the timestamping of the event messages received from the peer changes, and the location is 'cpm (2)'. |
Effect | When the timestamping location is 'cpm (2)', the accuracy of the PTP event messages is less then if the messages are timestamped at the port and performance will be negatively impacted. |
Recovery | It may be necessary to check the capabilities of the port being used for the messages and/or to modify routing to direct the messages to an alternate port. Some reasons for a port to not perform timestamping include: not configured, port not configured for ptp-hw-assist, port does not support ptp-hw-assist. |
tmnxPtpPeerNoRxTimestampingClear
Property name | Value |
---|---|
Application name |
PTP |
Event ID | 2016 |
Event name |
tmnxPtpPeerNoRxTimestampingClear |
SNMP notification prefix and OID |
TIMETRA-PTP-MIB.tmnxPtp1588Notifications.16 |
Default severity |
minor |
Source stream | main |
Message format string | Timestamping of receive communications with peer $tmnxPtpPeerIpAddress$ is now performed at the port. |
Cause | The tmnxPtpPeerNoRxTimestampingClear notification is generated when the conditions that caused the tmnxPtpPeerNoRxTimestamping event have been resolved and result in the location of the timestamping of the event messages received from the peer being changed from 'cpm (2)' to 'port (1)'. |
Effect | When the timestamping location is the 'port (2)', the accuracy of the PTP event messages is optimal. |
Recovery | No recovery is required for this notification. |
tmnxPtpPeerNoTxTimestamping
Property name | Value |
---|---|
Application name |
PTP |
Event ID | 2013 |
Event name |
tmnxPtpPeerNoTxTimestamping |
SNMP notification prefix and OID |
TIMETRA-PTP-MIB.tmnxPtp1588Notifications.13 |
Default severity |
minor |
Source stream | main |
Message format string | Timestamping of transmit communications with peer $tmnxPtpPeerIpAddress$ is performed at the CPM. Performance may be degraded. |
Cause | The tmnxPtpPeerNoTxTimestamping notification is generated on initial exchange of PTP event messages with a peer and whenever the location of the timestamping of the event messages transmitted to the peer changes, and the location is 'cpm (2)'. |
Effect | When the timestamping location is 'cpm (2)', the accuracy of the PTP event messages is less then if the messages are timestamped at the port and performance will be negatively impacted. |
Recovery | It may be necessary to check the capabilities of the port being used for the messages and/or to modify routing to direct the messages to an alternate port. Some reasons for a port to not perform timestamping include: not configured, port not configured for ptp-hw-assist, port does not support ptp-hw-assist. |
tmnxPtpPeerNoTxTimestampingClear
Property name | Value |
---|---|
Application name |
PTP |
Event ID | 2014 |
Event name |
tmnxPtpPeerNoTxTimestampingClear |
SNMP notification prefix and OID |
TIMETRA-PTP-MIB.tmnxPtp1588Notifications.14 |
Default severity |
minor |
Source stream | main |
Message format string | Timestamping of transmit communications with peer $tmnxPtpPeerIpAddress$ is now performed at the port. |
Cause | The tmnxPtpPeerNoTxTimestampingClear notification is generated when the conditions that caused the tmnxPtpPeerNoTxTimestamping event have been resolved and result in the location of the timestamping of the event messages transmitted to the peer being changed from 'cpm (2)' to 'port (1)'. |
Effect | When the timestamping location is the 'port (2)', the accuracy of the PTP event messages is optimal. |
Recovery | No recovery is required for this notification. |
tmnxPtpPortNoTimestamping
Property name | Value |
---|---|
Application name |
PTP |
Event ID | 2008 |
Event name |
tmnxPtpPortNoTimestamping |
SNMP notification prefix and OID |
TIMETRA-PTP-MIB.tmnxPtp1588Notifications.8 |
Default severity |
minor |
Source stream | main |
Message format string | Port $tmnxPtpNotifyPortId$ does not support PTP port-based timestamping. Performance may be degraded. |
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. |
tmnxPtpPortPtsfUnusable
Property name | Value |
---|---|
Application name |
PTP |
Event ID | 2009 |
Event name |
tmnxPtpPortPtsfUnusable |
SNMP notification prefix and OID |
TIMETRA-PTP-MIB.tmnxPtp1588Notifications.9 |
Default severity |
minor |
Source stream | main |
Message format string |
Packet timing signal from PTP port $tmnxPortPortID$ neighbor $tmnxPtpPortNeighborMacAddress$ is unusable. |
Cause | The PTP process detected excessive noise between the local port and the indicated external Master port. |
Effect | Any Announce messages received from the indicated neighbor shall be excluded from the BMCA algorithm until this condition is cleared. |
Recovery | The cause of the excessive noise should be identified and corrected. Once resolved, the clear command for this neighbor port must be executed to clear the condition and allow Announces from this neighbor to be considered in the BMCA. |
tmnxPtpRequiresSystemReboot
Property name | Value |
---|---|
Application name |
PTP |
Event ID | 2010 |
Event name |
tmnxPtpRequiresSystemReboot |
SNMP notification prefix and OID |
TIMETRA-PTP-MIB.tmnxPtp1588Notifications.10 |
Default severity |
major |
Source stream | main |
Message format string | The PTP configuration (clock-type $tmnxPtpClockClockType$, profile $tmnxPtpClockProfile$) is different than the initial configuration (clock-type $tmnxPtpNotifyInitialClockType$, profile $tmnxPtpNotifyInitialProfile$). A system reboot is required for the change to take effect. |
Cause | The PTP configuration has changed since system initialization. On some SROS series systems, changing the tmnxPtpClockClockType or tmnxPtpClockProfile requires a system reboot to take effect. |
Effect | PTP remains operationally out of service, even though it has been administratively enabled. |
Recovery | Reboot the system, or change the clock configuration to the original configuration. |
tmnxPtpRequiresSystemRebootClear
Property name | Value |
---|---|
Application name |
PTP |
Event ID | 2011 |
Event name |
tmnxPtpRequiresSystemRebootClear |
SNMP notification prefix and OID |
TIMETRA-PTP-MIB.tmnxPtp1588Notifications.11 |
Default severity |
cleared |
Source stream | main |
Message format string | The PTP configuration has changed to the initial configuration. A system reboot is no longer required. |
Cause | The system generates the tmnxPtpRequiresSystemRebootClear notification when the user changes the PTP configuration to match the initial configuration. |
Effect | PTP does not require a system reboot to become operationally in service. |
Recovery | There is no recovery required for this notification. |
tmnxPtpTimeRecoveryStateChange
Property name | Value |
---|---|
Application name |
PTP |
Event ID | 2012 |
Event name |
tmnxPtpTimeRecoveryStateChange |
SNMP notification prefix and OID |
TIMETRA-PTP-MIB.tmnxPtp1588Notifications.12 |
Default severity |
minor |
Source stream | main |
Message format string | IEEE1588 (PTP) Time Recovery state: $tmnxPtpTimeRecoveryState$ |
Cause | The tmnxPtpTimeRecoveryStateChange is generated when the Precision Timing Protocol (PTP) time recovery state changes on the system. |
Effect | N/A |
Recovery | N/A |