SYMM-SMI

All MIBs › SYMM-SMI

Organization: Symmetricom, Inc.

Last Updated: 2010-02-06

Category: Enterprise SMI and OID Registration, Timing and Synchronization

Description: Defines Symmetricom enterprise SMI OID registration tree for all Symmetricom products.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is SYMM-SMI?

SYMM-SMI is Symmetricom's enterprise Structure of Management Information module, which simply registers the private enterprise OID tree under which all of Symmetricom's product-specific MIBs (timing and synchronization equipment such as GPS-disciplined clocks and NTP appliances) are rooted. It defines no runtime data objects of its own; it exists purely to establish the OID namespace that other Symmetricom MIBs build upon. As a pure SMI/registration module it carries no hardware or software status data itself, so it plays no direct role in monitoring uptime, temperature, CPU, or any other operational parameter — that responsibility falls to the product-specific MIBs registered beneath it. Every other Symmetricom MIB depends on this module for its OID root, making it a foundational but data-free dependency. It is present on any network where Symmetricom timing/synchronization products are managed via SNMP, loaded as a prerequisite for the vendor's functional MIBs. Network engineers evaluating or troubleshooting this functionality can download the SYMM-SMI file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in SYMM-SMI. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Symmetricom timing/synchronization products (namespace-only module, applies broadly across the vendor's line)

Monitoring Examples

This module defines only the enterprise OID arc for Symmetricom products and contains no monitorable tables or scalars, so no realistic polling scenario can be honestly described here; it should be understood strictly as a namespace-registration MIB that other Symmetricom MIBs import from.

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From RFC1155-SMI

enterprises

From RFC1213-MIB

DisplayString

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
OBJECT-IDENTITY
Unsigned32

OIDs

OID symbolic	OID numeric	Type	Access	Description
dialup	1.3.6.1.4.1.9070.1.2.3.1.5.1.4
etc	1.3.6.1.4.1.9070.1.2.3.1.5.1.6
NTF etcAlarm	1.3.6.1.4.1.9070.0.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.
STR etcAlarmString	1.3.6.1.4.1.9070.1.2.3.1.5.1.6.6	DisplayString	read-only	Defines the format for the system alarm traps. This is only valid embedded in a trap message.
STR etcModel	1.3.6.1.4.1.9070.1.2.3.1.5.1.6.3	DisplayString	read-only	Model type factory programmed into each unit.
STR etcSerialNbr	1.3.6.1.4.1.9070.1.2.3.1.5.1.6.2	DisplayString	read-only	Unique serial number factory programmed into each unit.
STR etcUpgrade	1.3.6.1.4.1.9070.1.2.3.1.5.1.6.4	DisplayString	read-only	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. ======================================================
STR etcUpgradeServer	1.3.6.1.4.1.9070.1.2.3.1.5.1.6.5	DisplayString	read-only	Address of the server where new upgrades can be downloaded.
STR etcVersion	1.3.6.1.4.1.9070.1.2.3.1.5.1.6.1	DisplayString	read-only	Version info for SyncServer system.
experiment	1.3.6.1.4.1.9070.1.2.3.99
gps	1.3.6.1.4.1.9070.1.2.3.1.5.1.3
STR gpsHealth	1.3.6.1.4.1.9070.1.2.3.1.5.1.3.3	DisplayString	read-only	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. ======================================================
STR gpsMode	1.3.6.1.4.1.9070.1.2.3.1.5.1.3.5	DisplayString	read-only	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. ======================================================
STR gpsPosition	1.3.6.1.4.1.9070.1.2.3.1.5.1.3.1	DisplayString	read-only	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 ===============================================
STR gpsSatlist	1.3.6.1.4.1.9070.1.2.3.1.5.1.3.4	DisplayString	read-only	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 ======================================================
INT gpsUTCOffset	1.3.6.1.4.1.9070.1.2.3.1.5.1.3.2	INTEGER	read-only	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.
net	1.3.6.1.4.1.9070.1.2.3.1.5.1.5
STR ntpSysClock	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.13	DisplayString	read-only	Current system time from ntpd. This is usually derived from the hardware clock but could be from any other ntp source.
STR ntpSysError	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.12	DisplayString	read-only	Current system error from ntpd.
STR ntpSysFreq	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.11	DisplayString	read-only	System clock frequency correction from ntpd.
INT ntpSysLeap	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.1	INTEGER	read-only	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.
INT ntpSysMode	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.18	INTEGER	read-only	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 ============================================
INT ntpSysNotrust	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.16	INTEGER	read-only	Force authentication.
U32 ntpSysPeer	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.9	Unsigned32	read-only	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.
STR ntpSysPhase	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.10	DisplayString	read-only	System clock offset from the selected source.
INT ntpSysPktsReceived	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.17	INTEGER	read-only	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.
I32 ntpSysPoll	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.8	Integer32	read-only	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.
I32 ntpSysPrecision	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.3	Integer32	read-only	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).
STR ntpSysProcessor	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.15	DisplayString	read-only	Type of local processor.
STR ntpSysRefID	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.6	DisplayString	read-only	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 ==============================================
STR ntpSysRefTime	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.7	DisplayString	read-only	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.
OCT ntpSysRootDelay	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.4	OCTET STRING	read-only	Total roundtrip delay to the primary reference source at the root of the synchronization subnet, in seconds
OCT ntpSysRootDispersion	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.5	OCTET STRING	read-only	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
I32 ntpSysStratum	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.2	Integer32	read-only	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) ================================================
STR ntpSysSystem	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.14	DisplayString	read-only	Description of the current system.
ntpSystem	1.3.6.1.4.1.9070.1.2.3.1.5.1.1
STR ntpSysVersion	1.3.6.1.4.1.9070.1.2.3.1.5.1.1.19	DisplayString	read-only	The version of the NTP daemon on the system.
nts	1.3.6.1.4.1.9070.1.2.3.1.2
products	1.3.6.1.4.1.9070.1.2.3.1
s100	1.3.6.1.4.1.9070.1.2.3.1.4
symmBroadband	1.3.6.1.4.1.9070.1.2.2			The subtree that contains objects related to Symmetricom's GoWide products.
symmCmipManagement	1.3.6.1.4.1.9070.1.1			This is the root object identifier for CMIP based objects.
symmetricom	1.3.6.1.4.1.9070			This is the MIB Module for Symmetricom's enterprise specific parameters.
symmNetworkManagement	1.3.6.1.4.1.9070.1			This is the root object identifier for all MIBS under the Symmetricom tree.
symmSnmpManagement	1.3.6.1.4.1.9070.1.2			This is the root object identifier for SNMP based objects.
symmTimePictra	1.3.6.1.4.1.9070.1.2.1			This is reserved for objects related to Symmetricom's TimePictra products.
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.
syncserver	1.3.6.1.4.1.9070.1.2.3.1.5
ts2000	1.3.6.1.4.1.9070.1.2.3.1.1
ts2100	1.3.6.1.4.1.9070.1.2.3.1.3
tyming	1.3.6.1.4.1.9070.1.2.3.1.5.1.2
INT tymingFlyPeriod	1.3.6.1.4.1.9070.1.2.3.1.5.1.2.5	INTEGER	read-only	This variable is not currently used and returns zero.
STR tymingSource	1.3.6.1.4.1.9070.1.2.3.1.5.1.2.2	DisplayString	read-only	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. ============================================
STR tymingStatus	1.3.6.1.4.1.9070.1.2.3.1.5.1.2.1	DisplayString	read-only	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. ============================================
STR tymingTime	1.3.6.1.4.1.9070.1.2.3.1.5.1.2.3	DisplayString	read-only	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 ============================================
STR tymingVersion	1.3.6.1.4.1.9070.1.2.3.1.5.1.2.4	DisplayString	read-only	The version of the software on the SyncServer's Hardware Clock.
version	1.3.6.1.4.1.9070.1.2.3.1.5.1
xli	1.3.6.1.4.1.9070.1.2.3.1.6

RFC description

Symmetricom NTP, timing, and measurement product enterprise MIB structure.

Start monitoring Symmetricom timing/synchronization products (namespace-only module, applies broadly across the vendor's line) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download SYMM-SMI

What Is SYMM-SMI?

Supported Devices

Monitoring Examples

This MIB depends on

Related MIBs

RFC description