S5-AGENT-MIB :: s5AgSntpState

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › S5-AGENT-MIB › s5AgSntpState

s5AgSntpState

Module: S5-AGENT-MIB

OID (symbolic): S5-AGENT-MIB::s5AgSntpState

OID (numeric): 1.3.6.1.4.1.45.1.6.4.6.1

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This object is used to control whether the device uses the Simple Network Time Protocol (SNTP), to synchronize the device's clock to the Coordinated Universal Time (UTC).

If the value is disabled(1), the device will not synchronize it's clock using SNTP.

If the value is unicast(2), the device will first synchronize shortly after boot time when network access becomes available, and periodically thereafter, as specified by the value of s5AgSntpSyncInterval. If the value is not unicast(2) at boot, the device will synchronize when the value is first set to unicast(2), and periodically thereafter.

Synchronization process: This process applies to automatic (periodic) and manual synchronization attempts. The device will first attempt to synchronize with the primary NTP server as defined by s5AgSntpPrimaryServerAddress (if non-zero). If the primary server synchonization is attempted and fails, the s5AgSntpPrimaryServerSyncFailures counter is incremented. The device will then attempt to synchronize with the secondary NTP server as defined by s5AgSntpSecondaryServerAddress (if non-zero). If the secondary server synchronization is attempted and fails, the s5AgSntpSecondaryServerSyncFailures counter is incremented. If synchronization succeeds with either server, the s5AgSntpLastSyncTime and s5AgSntpLastSyncSource values are updated. The s5AgSntpNextSyncTime value is updated on success or failure. For the special case of first sync failures, the system will automatically retry every few minutes until synchronization is achieved without regard to s5AgSntpSyncInterval.

What is s5AgSntpState?

Enables or disables SNTP time synchronization: disabled(1) means the clock is never synchronized via SNTP, and unicast(2) synchronizes shortly after boot once network access is available and then periodically per s5AgSntpSyncInterval, also triggering an immediate sync the moment this object is first set to unicast(2).

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.45.1.6.4.6.1
snmpwalk -v2c -c public <target> S5-AGENT-MIB::s5AgSntpState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.45.1.6.4.6.1.1
snmpget -v2c -c public <target> S5-AGENT-MIB::s5AgSntpState.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.45.1.6.4.6.1.1 i <value>

Start monitoring Avaya/Nortel/Bay Networks S5000 series switch/hub (SNMP agent firmware/reboot control) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the S5-AGENT-MIB::s5AgSntpState OID value, configure state conditions and alerts, and monitor any Avaya/Nortel/Bay Networks S5000 series switch/hub (SNMP agent firmware/reboot control) from a single console.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.45synopticsCMU-MIB
1.3.6.1.4.1.45.1productsSYNOPTICS-ROOT-MIB
1.3.6.1.4.1.45.1.6series5000SYNOPTICS-ROOT-MIB
1.3.6.1.4.1.45.1.6.4s5AgentS5-ROOT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.45.1.6.4.6s5AgentSntpS5-AGENT-MIB
1.3.6.1.4.1.45.1.6.4.6.1s5AgSntpStateS5-AGENT-MIB