ASCEND-CALL-LOGGING-MIB :: callLoggingResetTime

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › ASCEND-CALL-LOGGING-MIB › callLoggingResetTime

callLoggingResetTime

Module: ASCEND-CALL-LOGGING-MIB

OID (symbolic): ASCEND-CALL-LOGGING-MIB::callLoggingResetTime

OID (numeric): 1.3.6.1.4.1.529.25.8

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The time to reset to the primary server after it has failed.

What is callLoggingResetTime?

This integer specifies seconds before attempting to reconnect to a failed primary server. Typical values 60-3600. Higher values reduce failover traffic.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.529.25.8
snmpwalk -v2c -c public <target> ASCEND-CALL-LOGGING-MIB::callLoggingResetTime

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.529.25.8.1
snmpget -v2c -c public <target> ASCEND-CALL-LOGGING-MIB::callLoggingResetTime.1

Set instance 1 (SNMPv2c):

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

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> callLoggingResetTime.1

Start monitoring Ascend Communications (Lucent) MAX/Pipeline/TNT WAN access equipment (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ASCEND-CALL-LOGGING-MIB::callLoggingResetTime OID value, configure state conditions and alerts, and monitor any Ascend Communications (Lucent) MAX/Pipeline/TNT WAN access equipment (legacy) from a single console.

OID Breakdown

Upper-level ancestors (8 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.529ascendASCEND-MIB
1.3.6.1.4.1.529.25callLoggingGroupASCEND-MIB
Numeric OIDNameModule
1.3.6.1.4.1.529.25.8callLoggingResetTimeASCEND-CALL-LOGGING-MIB