SIAE-PTP-MIB

TEXTUAL-CONVENTION

The Domain is identified by an integer, the domainNumber, in the range of 0 to 255. An integer value that is used to assign each PTP device to a particular domain. The following values define the valid domains. [1] Section 7.1 Domains Table 2 Value definition. --------- ------------------- 0 Default domain 1 Alternate domain 1 2 Alternate domain 2 3 Alternate domain 3 4 - 23 User-defined domains 24 - 43 Telecom Profile domains 44 - 127 User-defined domains 128 - 255 Reserved

TEXTUAL-CONVENTION

The instance of the Clock of a given clock type in a given domain.

TEXTUAL-CONVENTION

The clock type based on whether End to End or peer to peer mechanisms are used. The mechanism used to calculate the Mean Path Delay as indicated in Table 9 of IEEE 1588-2008. Delay mechanism Value(hex) Specification E2E 01 The port is configured to use the delay request-response mechanism. P2P 02 The port is configured to use the peer delay mechanism. DISABLED FE The port does not implement the delay mechanism.

TEXTUAL-CONVENTION

The instance of the PPS (and ToD) socket.

TEXTUAL-CONVENTION

An index identifying a specific Precision Time Protocol (PTP) port on a PTP node.

TEXTUAL-CONVENTION

This is the value of the current state of the protocol engine associated with this port. Port state Value Description ----------------------------------------------------------- initializing 1 In this state a port initializes its data sets, hardware, and communication facilities. faulty 2 The fault state of the protocol. disabled 3 The port shall not place any messages on its communication path. listening 4 The port is waiting for the announceReceiptTimeout to expire or to receive an Announce message from a master. preMaster 5 The port shall behave in all respects as though it were in the MASTER state except that it shall not place any messages on its communication path except for Pdelay_Req, Pdelay_Resp, Pdelay_Resp_Follow_Up, signaling, or management messages. master 6 The port is behaving as a master port. passive 7 The port shall not place any messages on its communication path except for Pdelay_Req, Pdelay_Resp, Pdelay_Resp_Follow_Up, or signaling messages, or management messages that are a required response to another management message uncalibrated 8 The local port is preparing to synchronize to the master port. slave 9 The port is synchronizing to the selected master port.

TEXTUAL-CONVENTION

Clock Profile used. A profile is the set of allowed Precision Time Protocol (PTP) features applicable to a device.

TEXTUAL-CONVENTION

The ClockQuality as specified in section 5.3.7, 7.6.2.5 and Table 6 of [1]. The following values are not represented in the enumerated values. 0x01-0x1F Reserved 0x32-0x7F Reserved It is important to note that section 7.1.1 RFC2578 allows for gaps and enumerate values to start with zero when indicated by the protocol.

TEXTUAL-CONVENTION

The ClockQuality as specified in section 5.3.7, 7.6.2.4 and Table 5 of [1]. Value Description ------ ---------------------------------------------------------- 0 Reserved to enable compatibility with future versions. 1-5 Reserved 6 Shall designate a clock that is synchronized to a primary reference time source. The timescale distributed shall be PTP. A clockClass 6 clock shall not be a slave to another clock in the domain. 7 Shall designate a clock that has previously been designated as clockClass 6 but that has lost the ability to synchronize to a primary reference time source and is in holdover mode and within holdover specifications. The timescale distributed shall be PTP. A clockClass 7 clock shall not be a slave to another clock in the domain. 8 Reserved. 9-10 Reserved to enable compatibility with future versions. 11-12 Reserved. 13 Shall designate a clock that is synchronized to an application-specific source of time. The timescale distributed shall be ARB. A clockClass 13 clock shall not be a slave to another clock in the domain. 14 Shall designate a clock that has previously been designated as clockClass 13 but that has lost the ability to synchronize to an application-specific source of time and is in holdover mode and within holdover specifications. The timescale distributed shall be ARB. A clockClass 14 clock shall not be a slave to another clock in the domain. 15-51 Reserved. 52 Degradation alternative A for a clock of clockClass 7 that is not within holdover specification. A clock of clockClass 52 shall not be a slave to another clock in the domain. 53-57 Reserved. 58 Degradation alternative A for a clock of clockClass 14 that is not within holdover specification. A clock of clockClass 58 shall not be a slave to another clock in the domain. 59-67 Reserved. 68-122 For use by alternate PTP profiles. 123-127 Reserved. 128-132 Reserved. 133-170 For use by alternate PTP profiles. 171-186 Reserved. 187 Degradation alternative B for a clock of clockClass 7 that is not within holdover specification. A clock of clockClass 187 may be a slave to another clock in the domain. 188-192 Reserved. 193 Degradation alternative B for a clock of clockClass 14 that is not within holdover specification. A clock of clockClass 193 may be a slave to another clock in the domain. 194-215 Reserved. 216-232 For use by alternate PTP profiles. 233-247 Reserved. 248 Default. This clockClass shall be used if none of the other clockClass definitions apply. 249-250 Reserved. 251 Reserved for version 1 compatibility; see Clause 18. 252-254 Reserved. 255 Shall be the clockClass of a slave-only clock; see 9.2.2. The ClockQuality as specified in section 6.4 and Table 2 of [2]. Value Description ------ ---------------------------------------------------------- 6 T-GM connected to a PRTC in locked mode (e.g. PRTC traceable to GNSS) 140 T-GM in holdover, out of holdover specification, traceable to Category 1 frequency source 150 T-GM in holdover, out of holdover specification, traceable to Category 2 frequency source 160 T-GM in holdover, out of holdover specification, traceable to Category 3 frequency source 165 T-BC in holdover, out of holdover specification, using unspecified frequency source 255 Slave only OC (does not send Announce messages)

TEXTUAL-CONVENTION

The clock state returned by PTP engine. Clock State Value Description -------------------------------------------------------------- Freerun state 1 The PTP clock has never been synchronized to a time source and is not in the process of synchronizing to a time source. As it relates to the PTP port state defined in [IEEE 1588], a clock is in Free-Run state if there are no PTP ports in: MASTER, PRE-MASTER, PASSIVE, UNCALIBRATED, or SLAVE states. Acquiring state 2 The PTP clock is in process of synchronizing to a time source. The duration and functionality of this state is implementation specific. This state is not required in an implementation. As it relates to the PTP port state defined in [IEEE 1588], a clock is in Acquiring state if there is a PTP port in UNCALIBRATED state. Locked state 3 The PTP clock is synchronized to a time source and is within some internal acceptable accuracy. As it relates to the PTP port state defined in [IEEE 1588], a clock is in Locked state if there is a PTP port in SLAVE state. HoldoverInSpec state 4 The PTP clock is no longer synchronized to a time source and is using information obtained while it was previously synchronized or other information sources were still available, to maintain performance within desired specification. The node may be relying solely on its own facilities for holdover or may use something like a frequency input from the network to achieve a holdover of time and/or phase. As it relates to the PTP port state defined in [IEEE 1588], a clock is in HoldoverInSpec state if there are no PTP ports in: INITIALIZING, LISTENING, UNCALIBRATED or SLAVE states, and performance is within desired specification. HoldoverOutOfSpec state 5 The PTP clock is no longer synchronized to a time source and, while it may be using information obtained while it was previously synchronized or other information sources were still available, it is unable to maintain performance within desired specification. As it relates to the PTP port state defined in [IEEE 1588], a clock is in HoldoverOutOfSpec state if there are no PTP ports in: INITIALIZING, LISTENING, UNCALIBRATED or SLAVE states, and performance is not within desired specification.

TEXTUAL-CONVENTION

This textual convention corresponds to the TimeInterval structure indicated in section 5.3.2 of [1]. It will be presented in the form of a character array. The TimeInterval type represents time intervals. struct TimeInterval { Integer64 scaledNanoseconds; }; The scaledNanoseconds member is the time interval expressed in units of nanoseconds and multiplied by 2**16. Positive or negative time intervals outside the maximum range of this data type shall be encoded as the largest positive and negative values of the data type, respectively. For example, 2.5 ns is expressed as 0000 0000 0002 8000 in Base16.

TEXTUAL-CONVENTION

The ClockQuality as specified in section 5.3.7, 7.6.2.6 and Table 7 of [1]. The following values are not represented in the enumerated values. 0xF0-0xFE For use by alternate PTP profiles 0xFF Reserved It is important to note that section 7.1.1 RFC2578 allows for gaps and enumerate values to start with zero when indicated by the protocol.

TEXTUAL-CONVENTION

The clock types as defined in the MIB module description.

TEXTUAL-CONVENTION

This is the format used for ToD signal in input or in output direcdtion. ----------------------------------------------------------- Format Value Description ----------------------------------------------------------- telecomTimeEvent 1 telecomTimeAnnounce 2 telecomGNSSstatus 3 NMEAzda 4 ASCII format (eg: $GPZDA,003157.00,01,01,1970,00,00*69) ISO8601 5 ASCII format (eg: 1970-01-01T00:32:47Z) NTP 6 ASCII format (eg: 70 001 00:30:51.000 S) Ublox 7 Not ASCII ChinaMobile 8 Not ASCII ChinaTelecom 9 Not ASCII (standard ITU G.8271 is derived from this) BCM 10 Not ASCII BCMTS 11 Not ASCII -----------------------------------------------------------

OBJECT-TYPE

Numerical version of this module. The string version of this MIB have the following format: XX.YY.ZZ so, for example, the value 1 should be interpreted as 00.00.01 and the value 10001 should be interpreted as 01.00.01.

OBJECT-IDENTITY

OBJECT-TYPE

This object specifies the PTP Profile implemented on the system.

OBJECT-TYPE

This object describes the PTP Profile implemented on the system.

OBJECT-TYPE

The version of the profile consist of two fields: a primaryVersion and a revisionNumber. The profileVersion shall be printed as primaryVersion.revisionNumber

OBJECT-TYPE

The version of the profile consist of two fields: a primaryVersion and a revisionNumber. The profileVersion shall be printed as primaryVersion.revisionNumber

OBJECT-TYPE

This object show the PTP Profile version on the system.

OBJECT-IDENTITY

OBJECT-TYPE

Table of vendor specific information about the PTP clock for all domains.

OBJECT-TYPE

Contains vendor specific information for a particular PTP clock. Where not otherwise specified, every object of this entry can be modified with the conceptual row active.

OBJECT-TYPE

This object states if PTP is enabled or disabled for this PTP Clock in order to switch on/off the PTP protocol.

OBJECT-TYPE

This object states that in the PTP Clock the A-BMCA is disabled and it is working in Static PTP Port Role mode.

OBJECT-TYPE

This object shows the current state of the PTP Clock State Machine

OBJECT-TYPE

This object states if the clock is strictly profile compliant. The meaning of looseCompatibility is application dependent.

OBJECT-TYPE

Table of vendor specific information about the PTP clock for all domains.

OBJECT-TYPE

Contains vendor specific alarm information for a particular PTP clock.

OBJECT-TYPE

This alarm is raised when ptpClockState is set to freerun(1).

OBJECT-TYPE

This alarm is raised when ptpClockState is set to holdoverInSpec(4).

OBJECT-TYPE

This alarm is raised when ptpClockState is set to holdoverOutOfSpec(5).

OBJECT-TYPE

This object defines the severity associated to ptpFreeRunningAlarm and enables or disables the sending of the SNMP Trap on the alarm status transition.

OBJECT-TYPE

This object defines the severity associated to ptpHoldoverInSpecAlarm and enables or disables the sending of the SNMP Trap on the alarm status transition.

OBJECT-TYPE

This object defines the severity associated to ptpHoldoverOutOfSpecAlarm and enables or disables the sending of the SNMP Trap on the alarm status transition.

OBJECT-IDENTITY

OBJECT-TYPE

Table of information about the PTP clock Default Datasets for all domains.

OBJECT-TYPE

Contains the information of the clock on a particular doamin. This table will be initialised with default values if the clock is operating as a boundary or ordinary clock in the domain.

OBJECT-TYPE

This object specifies the domain number used to create logical group of PTP devices. The Clock Domain is a logical group of clocks and devices that synchronize with each other using the PTP protocol.

OBJECT-TYPE

This object specifies the clock type as defined in the Textual convention description.

OBJECT-TYPE

This object specifies the instance of the Clock for this clock type for the given domain.

OBJECT-TYPE

This is the unique identity of the local clock or management node. This should be the smptpDomainClockIdentity of the domain indicated by the ptpDomainNumber. Configuration of this value will take effect only when the PTP module is enabled.

OBJECT-TYPE

This value is TRUE if the clock is two step clock, otherwise it is FALSE. If this value is configured as TRUE, then PTP will transmit the originTimeStamp only through follow-up messages.

OBJECT-TYPE

This indicates the number of PTP ports on the device. For an ordinary clock this value should be 1.

OBJECT-TYPE

This object specifies the default dataset Quality Class.

OBJECT-TYPE

This object specifies the default dataset Quality Accurarcy.

OBJECT-TYPE

This value is an estimate of the variations of the local clock from a linear timescale when it is not synchronized to another clock using the protocol. The initialization value depends on the inherent characteristics of the clock during initialization. This value is used by the BMC algorithm to select the best master clock

OBJECT-TYPE

This value is used by BMC algorithm to select the best master clock. Lower values take precedence.

OBJECT-TYPE

This value is used by BMC algorithm to select the best master clock. This is used as a tiebreaker when the BMC failes to order the clock using ptpClockPriority1, ptpClockClass, ptpClockAccuracy and ptpClockOffsetScaledLogVariance. Lower values take precedence

OBJECT-TYPE

Configuring this value as true will make the clock to behave as slave clock. A boundary clock can not be a slave only clock.

OBJECT-TYPE

This attribute is used in the alternate BMCA as a tie-breaker in the dataset comparison algorithm, in the event that all other previous attributes of the datasets being compared are equal.

OBJECT-TYPE

RowStatus for creating the entries into this table. This object support only destroy and createAndGo values.

OBJECT-IDENTITY

OBJECT-TYPE

Table of information about the PTP clock Current Datasets for all domains.

OBJECT-TYPE

Contains synchronization information on a particular domain.

OBJECT-TYPE

This object specifies the distance measured by the number of Boundary clocks between the local clock and the Foreign master as indicated in the stepsRemoved field of Announce messages. Slave clock will update this field once port is selected as slave.

OBJECT-TYPE

This object specifies the current clock dataset ClockOffset value. The value of the computation of the offset in time between a slave and a master clock.

OBJECT-TYPE

This object specifies the current clock dataset MeanPathDelay value. The mean path delay between a pair of ports as measure by the delay request-response mechanism.

OBJECT-IDENTITY

OBJECT-TYPE

Table of information about the PTP clock Parent Datasets for all domains.

OBJECT-TYPE

Contains parent clock information on a particular domain.

OBJECT-TYPE

This is the clock identity of the port on the master that issues sync messages used in synchronizing this clock. The initial value of this field is the value of ptpClockIdentity

OBJECT-TYPE

This is the port number identity of the port on the master that issues sync message used in synchronizing this clock. Combination of ptpParentClockIdentity and ptpParentPortNumber gives the port identity of the parent clock.

OBJECT-TYPE

This is the clock identity attribute of the grand master clock. The initial value is ptpClockIdentity.

OBJECT-TYPE

This is the clock class of the grandmaster. The initialization value of this variable is ptpClockClass.

OBJECT-TYPE

This is the clock accuracy of the grandmaster. The initialization value of this variable is ptpClockAccuracy

OBJECT-TYPE

This is the offset scaled log variance of the grandmaster. The initialization value of this variable is ptpClockOffsetScaledLogVariance

OBJECT-TYPE

This is the priority1 of the grandmaster clock. The initialization value of this variable is ptpClockPriority1

OBJECT-TYPE

This is the priority2 of the grandmaster clock. The initialization value of this variable is ptpClockPriority2

OBJECT-IDENTITY

OBJECT-TYPE

Table of information about the PTP clock Timeproperties Datasets for all domains.

OBJECT-TYPE

Contains parent Time properties information of the clock on a particular domain.

OBJECT-TYPE

If systems epoch is the PTP epoch then this value indicates the offset in seconds between TAI and UTC.

OBJECT-TYPE

Value of this variable is TRUE if the ptpTimeCurrentUTCOffset is known to be correct.

OBJECT-TYPE

If the systems epoch is PTP epoch then TRUE value of this variable indicates that the last minute of the current UTC day contains 59 seconds.

OBJECT-TYPE

If the systems epoch is PTP epoch then TRUE value of this variable indicates that the last minute of the current UTC day contains 61 seconds.

OBJECT-TYPE

This variable is TRUE if the timescale and value of ptpTimeCurrentUTCOffset are traceable to a primary reference otherwise, the value shall be FALSE.

OBJECT-TYPE

This variable is TRUE if the frequecy determining the timescale is traceable to a primary reference otherwise, the value shall be FALSE.

OBJECT-TYPE

This variable is TRUE if the clock timescale of the grandmaster clock is PTP otherwise, the value shall be FALSE.

OBJECT-TYPE

This is the source of time used by the grandmaster clock. If the time source is known at the time of initialization then the value will be set to that otherwise the initial value is INTERNAL_OSCILLATOR(160).

OBJECT-IDENTITY

OBJECT-TYPE

Table Contains PTP configuration information for a particular port of boundary or an ordinary clock

OBJECT-TYPE

Contains PTP configuration information for a particular port. Valid ptpPortIfIndex need to be given to make this entry active. Where not otherwise specified, every object of this entry can be modified with the conceptual row active.

OBJECT-TYPE

The index value used to identify the port component on the device. The value of this object is used as a port index to the ptpPortConfigDataSetTable.

OBJECT-TYPE

This is the clock Identity of the port

OBJECT-TYPE

This is the index in ifTable of this port. This object can't be modified.

OBJECT-TYPE

Role of this port. This object forces the role of the port if ptpStaticPortRole is true.

OBJECT-TYPE

Administrive status of the port. The value down turns off the PTP protocol on the ethernet port.

OBJECT-TYPE

This denotes the PTP State of the PTP port as computed by the PTP State event machine. initializing: While a port is in the INITIALIZING state, the port initializes its data sets, hardware, and communication facilities. No port of the clock shall place any PTP messages on its communication path. If one port of a boundary clock is in the INITIALIZING state, then all ports shall be in the INITIALIZING state. faulty: The fault state of the protocol. A port in this state shall not place any PTP messages except for management messages that are a required response to another management message on its communication path. disabled: The port shall not place any messages on its communication path. In a boundary clock, no activity at the port shall be allowed to affect the activity at any other port of the boundary clock. A port in this state shall discard all PTP received messages except for management messages. listening: The port is waiting for the announceReceiptTimeout to expire or to receive an Announce message from a master. The purpose of this state is to allow orderly addition of clocks to a domain. A port in this state shall not place any PTP messages on its communication path except for Pdelay_Req, Pdelay_Resp, Pdelay_Resp_Follow_Up, or signaling messages, or management messages that are a required response to another management message. premaster: The port shall behave in all respects as though it were in the MASTER state except that it shall not place any messages on its communication path except for Pdelay_Req, Pdelay_Resp, Pdelay_Resp_Follow_Up, signaling or management messages. master: The port is behaving as a master port. It will periodically send announce and sync messages. passive: The port shall not place any messages on its communication path except for Pdelay_Req, Pdelay_Resp, Pdelay_Resp_Follow_Up, or signaling messages or management messages that are a required response to another management message. uncalibrated: This is a transient state to allow initialization of synchronization servos, updating of data sets when a new master port has been selected, and other implementation-specific activity. slave: The port is synchronizing to the selected master port.

OBJECT-TYPE

This is the log to the base 2 of the delay request interval in seconds. This speifies the time to the members devices to send delay request messages when the port is in the master. It specify the minimum permitted mean time interval between successive Delay_Req messages, min delay request interval value is a compromise between the fluctuation in link delay and startup time and the communication and computation load imposed by transmission of these messages.

OBJECT-TYPE

This is the log to the base 2 of the mean Announce message interval in seconds.

OBJECT-TYPE

This is the Announce receipt time out value. This should be an integral multiple of announce interval in seconds

OBJECT-TYPE

This is the logarithm to the base 2 of the sync message interval in seconds

OBJECT-TYPE

This indicates the propagation delay measuring option used by the port in computing meanpathDelay.

OBJECT-TYPE

This indicates the PTP version in use on the port.

OBJECT-TYPE

This attribute is used in the alternate BMCA to prevent that a port can be placed in the SLAVE state.

OBJECT-TYPE

This attribute is used in the alternate BMCA as a tie-breaker in the dataset comparison algorithm, in the event that all other previous attributes of the datasets being compared are equal.

OBJECT-TYPE

This attribute is used in to select the destination MAC address inserted in the outgoing packets: forwardable: 01-1B-19-00-00-00 nonForwardable: 01-80-C2-00-00-0E

OBJECT-TYPE

This attribute is used to compensate in nanoseconds the asymmetric delay. It works in TX direction.

OBJECT-TYPE

This attribute is used to compensate in nanoseconds the asymmetric delay. It works in RX direction.

OBJECT-TYPE

RowStatus for creating the entries into this table. This object can't be modified.

OBJECT-TYPE

Table Contains PTP alarm information for a particular port of boundary or an ordinary clock.

OBJECT-TYPE

Contains PTP alarm information for a particular port.

OBJECT-TYPE

This alarm is raised when ptpPortState is set to faulty(2).

OBJECT-TYPE

This alarm is raised when ptpPortState is set to initializing(1).

OBJECT-TYPE

This alarm is raised when ptpPortState is set to uncalibrated(8).

OBJECT-TYPE

This alarm is raised when ptpPortState is set to listening(4).

OBJECT-TYPE

This alarm is raised when ptpPortState is set to slave(9).

OBJECT-TYPE

Table Contains PTP alarm information for a radio port of boundary or an ordinary clock.

OBJECT-TYPE

Contains PTP alarm information for a radio port.

OBJECT-TYPE

This alarm is raised when the capacity of a radio link is not big enough to transport PTP packets.

OBJECT-TYPE

This object defines the severity associated to ptpPortFaultyAlarm and enables or disables the sending of the SNMP Trap on the alarm status transition.

OBJECT-TYPE

This object defines the severity associated to ptpPortInitializingAlarm and enables or disables the sending of the SNMP Trap on the alarm status transition.

OBJECT-TYPE

This object defines the severity associated to ptpPortUncalibratedAlarm and enables or disables the sending of the SNMP Trap on the alarm status transition.

OBJECT-TYPE

This object defines the severity associated to ptpPortListeningAlarm and enables or disables the sending of the SNMP Trap on the alarm status transition.

OBJECT-TYPE

This object enables or disables the sending of the SNMP Trap on ptpPortActiveStatus transition.

OBJECT-TYPE

This object enables or disables the sending of the SNMP Trap on ptpPortRadioCapacityAlarm transition.

OBJECT-IDENTITY

OBJECT-TYPE

Table of information about the PTP clock PPS and ToD properties.

OBJECT-TYPE

Contains PPS and ToD properties information of the specific domain and clock on a specific PPS socket.

OBJECT-TYPE

This object specifies the id of PPS interface socket. It represents the id of ToD interface socket too.

OBJECT-TYPE

This object is a bitmap and each bit represents a specific capability of the PPS or ToD interface. Bit 0 : 1 = the interface can be used either in input or in output and the user can select the direction using ptpClockPPSDirection object; 0 = the interface can have one direction specified by the system, in this case the ptpClockPPSDirection object is read only. Bit 1 : 1 = the ToD interface allows more baudrate; 0 = the ToD interface allows one only baudrate, fixed by system.

OBJECT-TYPE

This object specifies the direction (input or output) of PPS signal and ToD data

OBJECT-TYPE

This object specifies the label as appears near the PPS signal socket

OBJECT-TYPE

This object is the administrive status of PPS interface and specifies whether the node is enabled for PTP input/output clocking using the PPS interface.

OBJECT-TYPE

This object specifies whether an offset is configured in order to compensate for a known phase error such as network asymmetry.

OBJECT-TYPE

This object specifies the fixed offset signed value in nanoseconds configured to be added for the PPS output or input.

OBJECT-TYPE

This object specifies the label as appears near the ToD socket

OBJECT-TYPE

This object is the administrive status of PPS interface and specifies whether the ToD interface is enabled.

OBJECT-TYPE

This object specifies microseconds of delay between PPS edge and ToD data emitted, used only in output direction.

OBJECT-TYPE

This object specifies the Baudrate of ToD signal in input or output direction.

OBJECT-TYPE

This object specifies the format of ToD signal in input or output direction.

OBJECT-IDENTITY

OBJECT-TYPE

Table contains delay offset for asymmetries compensation for the Radio unit.

OBJECT-TYPE

Each ntry contains delay offset for asymmetries compensation for a specific Radio unit.

OBJECT-TYPE

This is the index in radioTable of this unit. This object can't be modified.

OBJECT-TYPE

This object is an offset in nanoseconds for asymmetry compensation and can have both positive and negative values.