[ntpwg] symmetricom s350 mib
Greg Dowd
gdowd at symmetricom.com
Tue Jan 3 17:21:04 UTC 2012
These enterprise MIBs predate the ntpwg work by well over a decade. Most of these devices were originally created as Stratum 1 devices so you will often find source specific error messages for analyzing connections. It looks like the peer reach register is not there as a generic. For dialup, maybe one of the error messages would tell you if a call failed? If you just want to verify current operations, maybe the reference time would show the last call. I would echo the suggestion to contact the tech support guys if you have more questions. Happy New Year.
Greg Dowd
gdowd at symmetricom dot com (antispam format)
Symmetricom, Inc.
www.symmetricom.com<http://www.symmetricom.com>
"A clever person solves a problem. A wise person avoids it." Albert Einstein
From: ntpwg-bounces+gdowd=symmetricom.com at lists.ntp.org [mailto:ntpwg-bounces+gdowd=symmetricom.com at lists.ntp.org] On Behalf Of Juliano Rodrigo De Oliveira Souza
Sent: Monday, January 02, 2012 9:22 AM
To: ntpwg at lists.ntp.org
Subject: [ntpwg] symmetricom s350 mib
Hy folks!
The SYMM-SMI mib for the s350 (Symmetricom) returns the valid codes(see below):
But where is the REACH inside that?
We calling via modem(Stratum 0) to have the timeclock.
Maybe the NTPv4-MIB can return that value?
Regards,
SYMM-SMI::ntpSysLeap.0 = INTEGER: noWarning(0)
SYMM-SMI::ntpSysStratum.0 = INTEGER: 2
SYMM-SMI::ntpSysPrecision.0 = INTEGER: -20
SYMM-SMI::ntpSysRootDelay.0 = STRING: "0.000432"
SYMM-SMI::ntpSysRootDispersion.0 = STRING: "0.751901"
SYMM-SMI::ntpSysRefID.0 = STRING: "12.13.14.33"
SYMM-SMI::ntpSysRefTime.0 = STRING: "3534513241.35040"
SYMM-SMI::ntpSysPoll.0 = INTEGER: 4
SYMM-SMI::ntpSysPeer.0 = Gauge32: 890507436
SYMM-SMI::ntpSysPhase.0 = STRING: "-0.000032"
SYMM-SMI::ntpSysFreq.0 = STRING: "-33.656860 PPM"
SYMM-SMI::ntpSysError.0 = STRING: "No error"
SYMM-SMI::ntpSysClock.0 = STRING: "Mon Jan 2 15:15:06 2012"
SYMM-SMI::ntpSysSystem.0 = STRING: "Symmetricom SyncServer"
SYMM-SMI::ntpSysProcessor.0 = STRING: "X86 Processor"
SYMM-SMI::ntpSysNotrust.0 = INTEGER: 1
SYMM-SMI::ntpSysPktsReceived.0 = INTEGER: 666993
SYMM-SMI::ntpSysMode.0 = INTEGER: client(3)
SYMM-SMI::ntpSysVersion.0 = STRING: "ntpd 4.2.4p8 at 1.1607-o Tue Dec 14 23:47:30 UTC 2010 (1)"
SYMM-SMI::tymingStatus.0 = STRING: "Good"
SYMM-SMI::tymingSource.0 = STRING: "4"
SYMM-SMI::tymingTime.0 = STRING: "Mon Jan 2 15:15:06 2012"
SYMM-SMI::tymingVersion.0 = STRING: "2.102"
SYMM-SMI::tymingFlyPeriod.0 = INTEGER: 0
SYMM-SMI::gpsPosition.0 = STRING: "1 0 0 0 0 1 0 0 0 0 0"
SYMM-SMI::gpsUTCOffset.0 = INTEGER: 0
SYMM-SMI::gpsHealth.0 = STRING: "Receiver Health: 2"
SYMM-SMI::gpsSatlist.0 = STRING: "0"
SYMM-SMI::gpsMode.0 = STRING: "Receiver Mode: Survey"
SYMM-SMI::etcVersion.0 = STRING: "2.62"
SYMM-SMI::etcSerialNbr.0 = STRING: "1114A33703"
SYMM-SMI::etcModel.0 = STRING: "S350"
SYMM-SMI::etcUpgrade.0 = STRING: "Update value: 0"
SYMM-SMI::etcUpgradeServer.0 = STRING: "www.symmetricom.com"
SYMM-SMI::etcAlarmString.0 = ""
___________
Juliano Souza
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ntp.org/pipermail/ntpwg/attachments/20120103/0144c509/attachment.html>
More information about the ntpwg
mailing list