SYMM-SMI
AI MIB Summary
The SYMM-SMI module defines the structure for Symmetricom (now Microchip) enterprise-specific parameters, primarily enabling the monitoring of time synchronization hardware such as atomic clocks, GPS receivers, and NTP servers. It facilitates the retrieval of critical operational metrics including frequency accuracy, holdover status, GPS lock state, and internal temperature readings for network time protocol infrastructure.
This is the MIB Module for Symmetricom's enterprise specific parameters.
Main OID:
symmetricom.1.3.6.1.4.1.9070
59
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
59 total| Object Name |
|---|
symmetricomThis is the MIB Module for Symmetricom's enterprise specific
parameters. MODULE-IDENTITY .1.3.6.1.4.1.9070 |
IMPORTSThis is the MIB Module for Symmetricom's enterprise specific
parameters. Unknown .1.3.6.1.4.1.9070 |
etcAlarmThe trap provides notification of Hardware Clock, NTP,
system, and network alarms events. The user can configure
which alarms send traps on the ADMIN - Alarms page. TRAP-TYPE .1.3.6.1.4.1.9070.0.0 |
symmNetworkManagementThis is the root object identifier for all MIBS under the
Symmetricom tree. OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1 |
symmCmipManagementThis is the root object identifier for CMIP based objects. OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.1 |
symmSnmpManagementThis is the root object identifier for SNMP based objects. OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2 |
symmTimePictraThis is reserved for objects related to Symmetricom's TimePictra
products. OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.1 |
symmBroadbandThe subtree that contains objects related to Symmetricom's GoWide
products. OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.2 |
symmTTMThe subtree that contains objects related to Symmetricom's
Timing, Test and Measurement products. OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.3 |
products OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.3.1 |
ts2000 OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.3.1.1 |
nts OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.3.1.2 |
ts2100 OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.3.1.3 |
s100 OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.3.1.4 |
syncserver OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.3.1.5 |
version OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.3.1.5.1 |
ntpSystem OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.3.1.5.1.1 |
ntpSysLeapNTP Leap Indicator. This is a two-bit code
warning of an impending leap second to be inserted
into the NTP timescale. The bits are set before
23:59 on the day of insertion and reset after 00:00
on the following day. This causes the number of
seconds (rollover interval) in the day of insertion
to be increased or decreased by one. In the case
of primary servers the bits are set by operator
intervention, while in the case of secondary servers
the bits are set by the protocol. The two bits,
bit 0 and bit 1, respectively, are coded as follows:
===================================================
00 no warning
01 last minute has 61 seconds
10 last minute has 59 seconds
11 alarm condition(clock not synchronized)
===================================================
In all except the alarm condition(11), NTP itself
does nothing with these bits, except pass them on to
the time-conversion routines that are not part of
NTP. The alarm condition occurs when, for whatever
reason, the local clock is not synchronized, such
as when first coming up or after an extended period
when no primary reference source is available.ro Enumeration .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.1 |
ntpSysStratumCurrent NTP stratum level. This is an integer
indicating the stratum of the local clock with
values defined as follows:
================================================
0 unspecified
1 primary reference (e.g., calibrated atomic
clock, radio clock)
2-255 secondary reference (via NTP)
================================================ro Integer32 .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.2 |
ntpSysPrecisionCurrent NTP precision value. This is a signed
integer indicating the precision of the various
clocks, in seconds to the nearest power of two.
The value must be rounded to the next larger power
of two; for instance, a 50-Hz (20ms) or 60-Hz (16.17ms)
power-frequency clock would be assigned the value
-5 (31.25ms), while a 1000-Hz (1ms) crystal-controlled
clock would be assigned the value -9 (1.95ms).ro Integer32 .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.3 |
ntpSysRootDelayTotal roundtrip delay to the primary reference
source at the root of the synchronization
subnet, in secondsro OCTET STRING .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.4 |
ntpSysRootDispersionMaximum error relative to the primary reference
source at the root of the synchronization subnet,
in seconds. Only positive values greater than
zero are possiblero OCTET STRING .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.5 |
ntpSysRefIDNTP Reference Clock Identifier. This is a
32 bit code identifying the particular reference
clock. In the case of stratum 0 (unspecified) or
stratum 1 (primary reference), this is a four-
octet, left-justified, zero-padded ASCII string.
While not enumerated as part of the NTP spec, the
following are suggested ASCII identifiers:
==============================================
DCN DCN routing protocol
NIST NIST public modem
TSP TSP time protocol
DTS Digital Time Service
ATOM Atomic clock (calibrated)
VLF VLF radio (OMEGA,etc.)
callsign Generic radio
LORC LORAN-C radionavigation
GOES GOES UHF environment satellite
GPS GPS UHF satellite positioning
==============================================
The following ref ids are used by the SyncServer:
==============================================
GPS GPS satellite)
IRIG IRIG B timecode
1PPS Ext. 1 PPS input
E10M Ext. 10 MHz input
FREE Internal Clock
FLY Internal Clock after the Hardware
Clock reference is lost
==============================================ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.6 |
ntpSysRefTimeNTP Reference Timestamp. This is the time,
in timestamp format (converted to DisplayString),
when the local clock was last updated. If the
local clock has never been synchronized, the value
is zero.ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.7 |
ntpSysPollMinimum interval between transmitted messages, in
seconds as a power of two. For instance, a value
of six indicates a minimum interval of 64 seconds.ro Integer32 .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.8 |
ntpSysPeerCurrent synchronization source. In stratum > 1 this
variable returns the decimal representation of the
IPv4 address of its current peer. In stratum = 1 this
variable returns the decimal representation of the
hardware clock which is 2981759.ro Unsigned32 .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.9 |
ntpSysPhaseSystem clock offset from the selected source.ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.10 |
ntpSysFreqSystem clock frequency correction from ntpd.ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.11 |
ntpSysErrorCurrent system error from ntpd.ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.12 |
ntpSysClockCurrent system time from ntpd. This is usually
derived from the hardware clock but could be
from any other ntp source.ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.13 |
ntpSysSystemDescription of the current system.ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.14 |
ntpSysProcessorType of local processor.ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.15 |
ntpSysNotrustForce authentication.ro INTEGER .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.16 |
ntpSysPktsReceivedThis variable is a rollover counter which reflects
the number of ntp packets received by the SyncServer.
It is valid for all versions of the SyncServer.ro INTEGER .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.17 |
ntpSysModeAn integer indicating the NTP association mode
and are coded as follows:
============================================
0 unspecified
1 symmetric active
2 symmetric passive
3 client
4 server
5 broadcast
6 reserved for NTP control messages
7 reserved for private use
============================================ro Enumeration .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.18 |
ntpSysVersionThe version of the NTP daemon on the system.ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.1.19 |
tyming OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.3.1.5.1.2 |
tymingStatusIndicates what status the Hardware Clock considers
itself to be as a timing source defined as follows:
============================================
Good HW Clock has a valid time reference.
Bad HW Clock has no valid time reference.
============================================ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.2.1 |
tymingSourceThe time or frequency source currently in use
by the Hardware Clock defined as follows:
============================================
0 None
1 GPS
4 NTP
8 IRIG
16 External 1PPS
24 External 10 MHz
31 Freerun mode.
============================================ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.2.2 |
tymingTimeThe time according to the Hardware Clock in
the format of:
WWW MMM dd hh:mm:ss yyyy
defined as follows:
============================================
WWW weekday
MMM character month
dd day of month
hh:mm:ss time
yyyy year
Example Thu Sep 21 23:46:09 2006
============================================ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.2.3 |
tymingVersionThe version of the software on the SyncServer's
Hardware Clock.ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.2.4 |
tymingFlyPeriodThis variable is not currently used and returns zero.ro INTEGER .1.3.6.1.4.1.9070.1.2.3.1.5.1.2.5 |
gps OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.3.1.5.1.3 |
gpsPositionReturns the current position in the format of:
A BB CC DD EEE F GGG HH II JJJ KK
defined as follows:
===============================================
A sign of the latitude
(1 = North, -1 = South)
BB degrees of the latitude
CC minutes of the latitude
DD seconds of the latitude
EEE milliseconds of the latitude
F sign of the longitude
(1 = East, -1 = West)
GGG degrees of the longitude
HH minutes of the longitude
II seconds of the longitude
JJJ milliseconds of the longitude
KK altitude in meters
===============================================ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.3.1 |
gpsUTCOffsetThis variable returns the current offset between the
monotonic time maintained by the GPS satellite
constellation and UTC time. This value is commonly
referred to as the leap second count. It is only valid
on a Syncserver with GPS.ro INTEGER .1.3.6.1.4.1.9070.1.2.3.1.5.1.3.2 |
gpsHealthThis is the GPS receiver health status defined as
follows:
======================================================
0 = Receiver Down The Hardware Clock can't
communicate with the receiver.
1 = No Signal
2 = Acquiring Signal The receiver is tracking a GPS
signal.
3 = 2d Position mode The receiver is able to perform
position fixes for latitude and
longitude but does not have
enough satellites for altitude.
4 = 3d Position mode The receiver is now able to
perform position fixes for
latitude, longitude and altitude.
5 = Position Hold mode Position fixes are no longer
attempted, and the user entered
or surveyed position is used.
6 = Time Valid mode The receiver has valid timing
information from GPS satellites
(including current leap second
information). This is the final
state for all configured GPS modes.
======================================================ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.3.3 |
gpsSatlistDisplays the GPS satellite tracking information in the
format of:
N,X1,Y1,Z1,...,XN,YN,ZN
defined as follows:
======================================================
N Number of satellites. If one or more satellites
are available, Xi,Yi,Zi follows N.
Xi Satellite vehicle number.
Yi Satellite signal strength in dBW where less
than -200 dBW means no signal.
Zi Zi can be either T or C. T(racking) means the
SyncServer receives the information from the
satellite but the information is not used in its
timing solution. C(urrent) means the SyncServer
currently uses satellite information in its
timing solution.
Examples
For no satellites:
0
For one satellite with vehicle number 16:
1,16,C,-158
For six satellites:
6,12,C,-156,14,C,-155,8,T,-162,24,C,-158,18,C,161,6,C,-160
======================================================ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.3.4 |
gpsModeThe mode of the GPS receiver defined as follows:
======================================================
Receiver Mode: Survey.
The receiver is surveying and averaging its position.
When it has finished surveying, the receiver switches
to Position Hold mode. Survey mode and Position Hold
mode are appropriate for static applications, such as a
typical server room environment. This is the default mode
when the SyncServer starts.
Receiver Mode: Dynamic.
The GPS receiver surveys continuously to determine its
position and doesn't switch to another mode. This mode
must be initiated by a user, and is appropriate for mobile
applications such as ships, land vehicles, and aircraft.
The degree of accuracy this mode offers is fine for NTP
time over networks, but is less than optimal for the IRIG-B,
1 PPS, 10 MHz outputs available on some SyncServer models.
Receiver Mode: Hold.
The GPS receiver has completed Survey mode and switched to
this mode, or the user has manually entered a position and
forced it into this mode. The accuracy and stability of the
SyncServer's timing outputs are optimal when the receiver
has its exact position and is in this mode.
======================================================ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.3.5 |
dialup OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.3.1.5.1.4 |
net OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.3.1.5.1.5 |
etc OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.3.1.5.1.6 |
etcVersionVersion info for SyncServer system.ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.6.1 |
etcSerialNbrUnique serial number factory programmed into each unit.ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.6.2 |
etcModelModel type factory programmed into each unit.ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.6.3 |
etcUpgradeDescribes whether or not an upgrade is available from
the upgrade server described as follows:
======================================================
0 No upgrade is available.
1 An upgrade is available.
======================================================ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.6.4 |
etcUpgradeServerAddress of the server where new upgrades can be
downloaded.ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.6.5 |
etcAlarmStringDefines the format for the system alarm traps. This is
only valid embedded in a trap message.ro DisplayString .1.3.6.1.4.1.9070.1.2.3.1.5.1.6.6 |
xli OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.3.1.6 |
experiment OBJECT IDENTIFIER .1.3.6.1.4.1.9070.1.2.3.99 |