Securestack SNTP Poll-Interval Command Syntax change for RFC1305 Compliance

  • 0
  • 1
  • Article
  • Updated 5 years ago
  • (Edited)
Article ID: 9843 

Products
SecureStack C3, C2, B3, B2 

Changes
Upgraded the SecureStack. 

Symptoms
The SNTP Poll Interval ('set sntp poll-interval...') command set has changed. 

Cause
This is due to a design change, for compliance with RFC1305.
Upgrading changes the configuration "on the fly", to conform with the new command format. 

With C3 firmware 1.00.92 and lower, C2 firmware 5.00.75 and lower, B3 firmware 1.00.86 and lower, B2 firmware 4.00.77 and lower, and all A2 firmware; the Poll Interval is specified in seconds, within the range of 16-16284. 

Here is the command format:

C3(su)->set sntp poll-interval

Command: set sntp Set SNTP client configuration

Object: poll-interval Set the interval between unicast SNTP request transmissions
Usage: set sntp poll-interval <interval>

interval Poll interval in seconds [16 to 16284]
C3(su)->

With C3 firmware 1.00.93 and higher, C2 firmware 5.00.76 and higher, B3 firmware 1.00.87 and higher, and B2 firmware 4.00.78 and higher; the Poll Interval is specified in intervals, within the range of 6-10. 

Here is the command format:

C3(su)->set sntp poll-interval

Command: set sntp Set SNTP client configuration

Object: poll-interval Set the interval between unicast SNTP request transmissions
Usage: set sntp poll-interval <interval>

interval Poll interval in 2^interval seconds [6 to 10]
C3(su)->

Solution/Workaround
Functions as Designed (FAD). 

Release notes state, in the "Firmware Changes and Enhancements" section: 
"Updated the SNTP poll interval value to be configured as a power of 2, with a valid range between six and ten as described in RFC-1305 (i.e. a poll interval set to "6" would be equal to 2^6 or 64 seconds). If upgrading from configuration which has an SNTP poll-interval set outside of the valid range of between 6 and 10, the default of 6 (2^6 = 64 seconds) will be set."

These are the mapping equivalents, between the two methods:

Seconds Interval
1024 10
512 9 [default]
256 8
128 7
64 6
other 6

If you choose to use a MIB browser to update etsysSntpClientUnicastPollInterval, remember to use the values expected by the firmware - either 16-16284 seconds with old firmware or 6-10 intervals with new firmware. 

NetSight Atlas Console does not regulate user input to be within the range of values defined in that OID (shown below), but some MIB browsers might. If so, then before being able to input data within the range of 6-10 it will be necessary to change the defined integer range (expanding it to "6..16284" would be most compatible with all devices), recompile the MIB, and re-import it into your MIB browser.

etsysSntpClientUnicastPollInterval=1.3.6.1.4.1.5624.1.2.38.1.2.1

iso.org.dod.internet.private.enterprises.enterasys.etsysMibs.etsysModules.etsysSntpClientMIB.
etsysSntpClientObjects.etsysSntpClientUnicast.etsysSntpClientUnicastPollInterval
1.3.6.1.4.1.5624.1.2.38.1.2.1

etsysSntpClientUnicastPollInterval OBJECT-TYPE
SYNTAX Unsigned Integer ( 16..16284 )
UNITS seconds
MAX-ACCESS Read/Write
STATUS Current
DESCRIPTION

The number of seconds between successive SNTP request
transmissions. This polling interval is used for directed
SNTP requests in unicast(1) operational mode. Maintaining the
value of this object across agent reboots is REQUIRED.

::= { etsysSntpClientUnicast 1 }

MODULE ENTERASYS-SNTP-CLIENT-MIB
FILE enterasys-sntp-client-mib.txt
PATH ftp://ftp.enterasys.com/pub/snmp/mibs/mibs.zip

See also: 14382.
Photo of FAQ User

FAQ User, Official Rep

  • 13,620 Points 10k badge 2x thumb

Posted 5 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.