MIBs Depot

SYMM-SMI

Registered at
1.3.6.1.4.1.9070
Last updated
2009-06-11 12:00
Organization
Symmetricom, Inc.
Revisions
2009-06-11 12:00
Namespace
microsemi
Source file
SYMM-SMI
Digest
sha256:801e43c5be2961c6abf4ff10e3dea71e50a9780633344c80666bbd55ff770380

Description

This is the MIB Module for Symmetricom's enterprise specific parameters.

Contact

Symmetricom, Inc. 2300 Orchard Parkway San Jose, CA 95131

Imports

FromSymbols
RFC-1212MODULE-IDENTITY, OBJECT-IDENTITY
RFC1155-SMIInteger32, Unsigned32
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP
SNMPv2-SMIMODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, TRAP-TYPE, enterprises, iso
SNMPv2-TCDisplayString, TEXTUAL-CONVENTION

Imported by

Nothing in this corpus imports this module.

Load order

Every file a consumer needs in order to load this module, dependencies first.

RFC-1212
RFC1155-SMI
SNMPv2-CONF
SNMPv2-SMI
SNMPv2-TC
SYMM-SMI

Objects

NameOIDSyntaxAccessStatus
symmNetworkManagement
OBJECT-IDENTITY
This is the root object identifier for all MIBS under the Symmetricom tree.
1.3.6.1.4.1.9070.1current
symmCmipManagement
OBJECT-IDENTITY
This is the root object identifier for CMIP based objects.
1.3.6.1.4.1.9070.1.1current
symmSnmpManagement
OBJECT-IDENTITY
This is the root object identifier for SNMP based objects.
1.3.6.1.4.1.9070.1.2current
symmTimePictra
OBJECT-IDENTITY
This is reserved for objects related to Symmetricom's TimePictra products.
1.3.6.1.4.1.9070.1.2.1current
symmBroadband
OBJECT-IDENTITY
The subtree that contains objects related to Symmetricom's GoWide products.
1.3.6.1.4.1.9070.1.2.2current
symmTTM
OBJECT-IDENTITY
The subtree that contains objects related to Symmetricom's Timing, Test and Measurement products.
1.3.6.1.4.1.9070.1.2.3current
products
OBJECT-IDENTITY
1.3.6.1.4.1.9070.1.2.3.1
ts2000
OBJECT-IDENTITY
1.3.6.1.4.1.9070.1.2.3.1.1
nts
OBJECT-IDENTITY
1.3.6.1.4.1.9070.1.2.3.1.2
ts2100
OBJECT-IDENTITY
1.3.6.1.4.1.9070.1.2.3.1.3
s100
OBJECT-IDENTITY
1.3.6.1.4.1.9070.1.2.3.1.4
syncserver
OBJECT-IDENTITY
1.3.6.1.4.1.9070.1.2.3.1.5
version
OBJECT-IDENTITY
1.3.6.1.4.1.9070.1.2.3.1.5.1
ntpSystem
OBJECT-IDENTITY
1.3.6.1.4.1.9070.1.2.3.1.5.1.1
ntpSysLeap
OBJECT-TYPE
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.
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.1INTEGER {noWarning(0), addSecond(1), subtractSecond(2), alarm(3)}read-onlycurrent
ntpSysStratum
OBJECT-TYPE
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) ================================================
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.2Integer32 (0..255)read-onlycurrent
ntpSysPrecision
OBJECT-TYPE
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).
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.3Integer32read-onlycurrent
ntpSysRootDelay
OBJECT-TYPE
Total roundtrip delay to the primary reference source at the root of the synchronization subnet, in seconds. Also known as root distance.
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.4OCTET STRINGread-onlycurrent
ntpSysRootDispersion
OBJECT-TYPE
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.
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.5OCTET STRINGread-onlycurrent
ntpSysRefID
OBJECT-TYPE
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 PPS Ext. 1 PPS input E10M Ext. 10 MHz input FREE Internal Clock FLY Internal Clock after the Hardware Clock reference is lost ==============================================
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.6DisplayString (SIZE(1..40))read-onlycurrent
ntpSysRefTime
OBJECT-TYPE
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.
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.7DisplayString (SIZE(1..40))read-onlycurrent
ntpSysPoll
OBJECT-TYPE
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.
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.8Integer32read-onlycurrent
ntpSysPeer
OBJECT-TYPE
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.
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.9Unsigned32read-onlycurrent
ntpSysPhase
OBJECT-TYPE
System clock offset from the selected source.
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.10DisplayString (SIZE(1..40))read-onlycurrent
ntpSysFreq
OBJECT-TYPE
System clock frequency correction from ntpd.
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.11DisplayString (SIZE(1..40))read-onlycurrent
ntpSysError
OBJECT-TYPE
Current system error from ntpd.
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.12DisplayString (SIZE(1..40))read-onlycurrent
ntpSysClock
OBJECT-TYPE
Current system time from ntpd. This is usually derived from the hardware clock but could be from any other ntp source.
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.13DisplayString (SIZE(1..40))read-onlycurrent
ntpSysSystem
OBJECT-TYPE
Description of the current system.
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.14DisplayString (SIZE(1..80))read-onlycurrent
ntpSysProcessor
OBJECT-TYPE
Type of local processor.
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.15DisplayString (SIZE(1..40))read-onlycurrent
ntpSysNotrust
OBJECT-TYPE
Force authentication.
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.16INTEGER (0..1)read-onlymandatory
ntpSysPktsReceived
OBJECT-TYPE
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.
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.17INTEGER (0..32768)read-onlymandatory
ntpSysMode
OBJECT-TYPE
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 ============================================
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.18INTEGER {unspecified(0), symactive(1), sympassive(2), client(3), server(4), broadcast(5), reservedctl(6), reservedpriv(7)}read-onlymandatory
ntpSysVersion
OBJECT-TYPE
The version of the NTP daemon on the system.
1.3.6.1.4.1.9070.1.2.3.1.5.1.1.19DisplayString (SIZE(1..80))read-onlycurrent
tyming
OBJECT-IDENTITY
1.3.6.1.4.1.9070.1.2.3.1.5.1.2
tymingStatus
OBJECT-TYPE
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. ============================================
1.3.6.1.4.1.9070.1.2.3.1.5.1.2.1DisplayString (SIZE(1..80))read-onlycurrent
tymingSource
OBJECT-TYPE
The time or frequency source currently in use by the Hardware Clock defined as follows: ============================================ 0 None 1 GPS 8 IRIG 16 External 1PPS 24 External 10 MHz 31 Freerun ============================================
1.3.6.1.4.1.9070.1.2.3.1.5.1.2.2DisplayString (SIZE(1..40))read-onlycurrent
tymingTime
OBJECT-TYPE
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 ============================================
1.3.6.1.4.1.9070.1.2.3.1.5.1.2.3DisplayString (SIZE(1..40))read-onlycurrent
tymingVersion
OBJECT-TYPE
The version of the software on the SyncServer's Hardware Clock.
1.3.6.1.4.1.9070.1.2.3.1.5.1.2.4DisplayString (SIZE(1..40))read-onlycurrent
tymingFlyPeriod
OBJECT-TYPE
This variable is not currently used and returns zero.
1.3.6.1.4.1.9070.1.2.3.1.5.1.2.5INTEGERread-onlycurrent
gps
OBJECT-IDENTITY
1.3.6.1.4.1.9070.1.2.3.1.5.1.3
gpsPosition
OBJECT-TYPE
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 ===============================================
1.3.6.1.4.1.9070.1.2.3.1.5.1.3.1DisplayString (SIZE(1..80))read-onlycurrent
gpsUTCOffset
OBJECT-TYPE
This variable is reserved for future use.
1.3.6.1.4.1.9070.1.2.3.1.5.1.3.2INTEGER (0..127)read-onlycurrent
gpsHealth
OBJECT-TYPE
This is the GPS’ receiver health status defined as follows: ====================================================== 0 = Receiver Down The Hardware Clock can't communicate with the receiver. 1 = Unknown Mode An undefined mode of the GPS receiver. 2 = Acquiring Signal The receiver is attempting to track a GPS signal. 3 = Bad Geometry The geometry of the tracked satellites is unsatisfactory for a position solution. 4 = Propagate Mode A position estimation mode used in highly dynamic environments. 5 = 2d Solution The receiver is able to perform position fixes for latitude and longitude but does not have enough satellites for altitude. 6 = 3d Solution The receiver is now able to perform position fixes for latitude, longitude and altitude. 7 = Position Hold Position fixes are no longer attempted, and the user entered or surveyed position is used. 8 = Time Valid The receiver has valid timing information from GPS satellites (including current leap second information). This is the final state for all configured GPS modes. ======================================================
1.3.6.1.4.1.9070.1.2.3.1.5.1.3.3DisplayString (SIZE(1..80))read-onlycurrent
gpsSatlist
OBJECT-TYPE
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 ======================================================
1.3.6.1.4.1.9070.1.2.3.1.5.1.3.4DisplayString (SIZE(1..128))read-onlycurrent
gpsMode
OBJECT-TYPE
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. ======================================================
1.3.6.1.4.1.9070.1.2.3.1.5.1.3.5DisplayString (SIZE(1..80))read-onlycurrent
dialup
OBJECT-IDENTITY
1.3.6.1.4.1.9070.1.2.3.1.5.1.4
net
OBJECT-IDENTITY
1.3.6.1.4.1.9070.1.2.3.1.5.1.5
etc
OBJECT-IDENTITY
1.3.6.1.4.1.9070.1.2.3.1.5.1.6
etcVersion
OBJECT-TYPE
Version info for SyncServer system.
1.3.6.1.4.1.9070.1.2.3.1.5.1.6.1DisplayString (SIZE(1..80))read-onlycurrent
etcSerialNbr
OBJECT-TYPE
Unique serial number factory programmed into each unit.
1.3.6.1.4.1.9070.1.2.3.1.5.1.6.2DisplayString (SIZE(1..40))read-onlycurrent
etcModel
OBJECT-TYPE
Model type factory programmed into each unit.
1.3.6.1.4.1.9070.1.2.3.1.5.1.6.3DisplayString (SIZE(1..40))read-onlycurrent
etcUpgrade
OBJECT-TYPE
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. ======================================================
1.3.6.1.4.1.9070.1.2.3.1.5.1.6.4DisplayString (SIZE(1..1024))read-onlycurrent
etcUpgradeServer
OBJECT-TYPE
Address of the server where new upgrades can be downloaded.
1.3.6.1.4.1.9070.1.2.3.1.5.1.6.5DisplayString (SIZE(1..1024))read-onlycurrent
etcAlarmString
OBJECT-TYPE
Defines the format for the system alarm traps. This is only valid embedded in a trap message.
1.3.6.1.4.1.9070.1.2.3.1.5.1.6.6DisplayString (SIZE(0..1024))read-onlycurrent
xli
OBJECT-IDENTITY
1.3.6.1.4.1.9070.1.2.3.1.6
experiment
OBJECT-IDENTITY
1.3.6.1.4.1.9070.1.2.3.99

Notifications

NameOIDStatus
etcAlarm
NOTIFICATION-TYPE
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.
1.3.6.1.4.1.9070.0.0