SYMM-SMI

File: SYMM-SMI.mib (20046 bytes)

Imported modules

RFC-1212	RFC1213-MIB	RFC-1215
RFC1155-SMI	SNMPv2-SMI

Imported symbols

OBJECT-TYPE	DisplayString	TRAP-TYPE
enterprises	Integer32	Unsigned32
MODULE-IDENTITY	OBJECT-IDENTITY

Defined Values

symmetricom		1.3.6.1.4.1.9070
This is the MIB Module for Symmetricom's enterprise specific parameters.
MODULE-IDENTITY

symmNetworkManagement		1.3.6.1.4.1.9070.1
This is the root object identifier for all MIBS under the Symmetricom tree.
Status: current	Access: read-write
OBJECT-IDENTITY

symmCmipManagement		1.3.6.1.4.1.9070.1.1
This is the root object identifier for CMIP based objects.
Status: current	Access: read-write
OBJECT-IDENTITY

symmSnmpManagement		1.3.6.1.4.1.9070.1.2
This is the root object identifier for SNMP based objects.
Status: current	Access: read-write
OBJECT-IDENTITY

symmTimePictra		1.3.6.1.4.1.9070.1.2.1
This is reserved for objects related to Symmetricom's TimePictra products.
Status: current	Access: read-write
OBJECT-IDENTITY

symmBroadband		1.3.6.1.4.1.9070.1.2.2
The subtree that contains objects related to Symmetricom's GoWide products.
Status: current	Access: read-write
OBJECT-IDENTITY

symmTTM		1.3.6.1.4.1.9070.1.2.3
The subtree that contains objects related to Symmetricom's Timing, Test and Measurement products.
Status: current	Access: read-write
OBJECT-IDENTITY

products		1.3.6.1.4.1.9070.1.2.3.1
OBJECT IDENTIFIER

experiment		1.3.6.1.4.1.9070.1.2.3.99
OBJECT IDENTIFIER

ts2000		1.3.6.1.4.1.9070.1.2.3.1.1
OBJECT IDENTIFIER

nts		1.3.6.1.4.1.9070.1.2.3.1.2
OBJECT IDENTIFIER

ts2100		1.3.6.1.4.1.9070.1.2.3.1.3
OBJECT IDENTIFIER

s100		1.3.6.1.4.1.9070.1.2.3.1.4
OBJECT IDENTIFIER

syncserver		1.3.6.1.4.1.9070.1.2.3.1.5
OBJECT IDENTIFIER

xli		1.3.6.1.4.1.9070.1.2.3.1.6
OBJECT IDENTIFIER

version		1.3.6.1.4.1.9070.1.2.3.1.5.1
OBJECT IDENTIFIER

ntpSystem		1.3.6.1.4.1.9070.1.2.3.1.5.1.1
OBJECT IDENTIFIER

tyming		1.3.6.1.4.1.9070.1.2.3.1.5.1.2
OBJECT IDENTIFIER

gps		1.3.6.1.4.1.9070.1.2.3.1.5.1.3
OBJECT IDENTIFIER

dialup		1.3.6.1.4.1.9070.1.2.3.1.5.1.4
OBJECT IDENTIFIER

net		1.3.6.1.4.1.9070.1.2.3.1.5.1.5
OBJECT IDENTIFIER

etc		1.3.6.1.4.1.9070.1.2.3.1.5.1.6
OBJECT IDENTIFIER

ntpSysLeap		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.1
NTP 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.
Status: current	Access: read-only
OBJECT-TYPE
	INTEGER	noWarning(0), addSecond(1), subtractSecond(2), alarm(3)

ntpSysStratum		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.2
Current 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) ================================================
Status: current	Access: read-only
OBJECT-TYPE
	Integer32	0..255

ntpSysPrecision		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.3
Current 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).
Status: current	Access: read-only
OBJECT-TYPE
	Integer32

ntpSysRootDelay		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.4
Total roundtrip delay to the primary reference source at the root of the synchronization subnet, in seconds
Status: current	Access: read-only
OBJECT-TYPE
	OCTET STRING

ntpSysRootDispersion		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.5
Maximum error relative to the primary reference source at the root of the synchronization subnet, in seconds. Only positive values greater than zero are possible
Status: current	Access: read-only
OBJECT-TYPE
	OCTET STRING

ntpSysRefID		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.6
NTP 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 ==============================================
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..40)

ntpSysRefTime		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.7
NTP 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.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..40)

ntpSysPoll		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.8
Minimum interval between transmitted messages, in seconds as a power of two. For instance, a value of six indicates a minimum interval of 64 seconds.
Status: current	Access: read-only
OBJECT-TYPE
	Integer32

ntpSysPeer		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.9
Current 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.
Status: current	Access: read-only
OBJECT-TYPE
	Unsigned32

ntpSysPhase		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.10
System clock offset from the selected source.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..40)

ntpSysFreq		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.11
System clock frequency correction from ntpd.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..40)

ntpSysError		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.12
Current system error from ntpd.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..40)

ntpSysClock		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.13
Current system time from ntpd. This is usually derived from the hardware clock but could be from any other ntp source.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..40)

ntpSysSystem		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.14
Description of the current system.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..80)

ntpSysProcessor		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.15
Type of local processor.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..40)

ntpSysNotrust		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.16
Force authentication.
Status: mandatory	Access: read-only
OBJECT-TYPE
	INTEGER	0..1

ntpSysPktsReceived		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.17
This 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.
Status: mandatory	Access: read-only
OBJECT-TYPE
	INTEGER	0..32768

ntpSysMode		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.18
An 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 ============================================
Status: mandatory	Access: read-only
OBJECT-TYPE
	INTEGER	unspecified(0), symactive(1), sympassive(2), client(3), server(4), broadcast(5), reservedctl(6), reservedpriv(7)

ntpSysVersion		1.3.6.1.4.1.9070.1.2.3.1.5.1.1.19
The version of the NTP daemon on the system.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..80)

tymingStatus		1.3.6.1.4.1.9070.1.2.3.1.5.1.2.1
Indicates 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. ============================================
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..80)

tymingSource		1.3.6.1.4.1.9070.1.2.3.1.5.1.2.2
The 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. ============================================
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..40)

tymingTime		1.3.6.1.4.1.9070.1.2.3.1.5.1.2.3
The 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 ============================================
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..40)

tymingVersion		1.3.6.1.4.1.9070.1.2.3.1.5.1.2.4
The version of the software on the SyncServer's Hardware Clock.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..40)

tymingFlyPeriod		1.3.6.1.4.1.9070.1.2.3.1.5.1.2.5
This variable is not currently used and returns zero.
Status: current	Access: read-only
OBJECT-TYPE
	INTEGER

gpsPosition		1.3.6.1.4.1.9070.1.2.3.1.5.1.3.1
Returns 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 ===============================================
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..80)

gpsUTCOffset		1.3.6.1.4.1.9070.1.2.3.1.5.1.3.2
This 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.
Status: current	Access: read-only
OBJECT-TYPE
	INTEGER	0..127

gpsHealth		1.3.6.1.4.1.9070.1.2.3.1.5.1.3.3
This 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. ======================================================
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..80)

gpsSatlist		1.3.6.1.4.1.9070.1.2.3.1.5.1.3.4
Displays 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 ======================================================
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..128)

gpsMode		1.3.6.1.4.1.9070.1.2.3.1.5.1.3.5
The 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. ======================================================
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..80)

etcVersion		1.3.6.1.4.1.9070.1.2.3.1.5.1.6.1
Version info for SyncServer system.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..80)

etcSerialNbr		1.3.6.1.4.1.9070.1.2.3.1.5.1.6.2
Unique serial number factory programmed into each unit.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..40)

etcModel		1.3.6.1.4.1.9070.1.2.3.1.5.1.6.3
Model type factory programmed into each unit.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..40)

etcUpgrade		1.3.6.1.4.1.9070.1.2.3.1.5.1.6.4
Describes whether or not an upgrade is available from the upgrade server described as follows: ====================================================== 0 No upgrade is available. 1 An upgrade is available. ======================================================
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..1024)

etcUpgradeServer		1.3.6.1.4.1.9070.1.2.3.1.5.1.6.5
Address of the server where new upgrades can be downloaded.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(1..1024)

etcAlarmString		1.3.6.1.4.1.9070.1.2.3.1.5.1.6.6
Defines the format for the system alarm traps. This is only valid embedded in a trap message.
Status: current	Access: read-only
OBJECT-TYPE
	DisplayString	Size(0..1024)

etcAlarm		0
The 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

Generation date: July 28, 2023, 16:18:13, Copyright © 2007 - 2022 - Circitor