INFORMANT-MSCS :: mscsResourceRestartPeriod

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › INFORMANT-MSCS › mscsResourceRestartPeriod

mscsResourceRestartPeriod

Module: INFORMANT-MSCS

OID (symbolic): INFORMANT-MSCS::mscsResourceRestartPeriod

OID (numeric): 1.3.6.1.4.1.9600.1.31.11.1.17

Node type: OBJECT-TYPE

Type: Gauge32

Access: read-only

Description: The RestartPeriod property defines an interval of time, in milliseconds, during which a specified number of restart attempts can be made on a nonresponsive resource. The RestartThreshold property specifies the allowable number of restart attempts that can occur within the interval defined by RestartPeriod.

When a resource fails, the Cluster service attempts to restart the resource (unless the RestartAction property is set to ClusterResourceDontRestart).

The RestartPeriod and RestartThreshold properties work together to limit restart attempts. For example, if the RestartPeriod property is set to 200 milliseconds, and the RestartThreshold property is set to two retry attempts, the Cluster service tolerates two restart failures within any 200 millisecond interval. More than two failures can occur, as long as they occur over an interval that is greater than 200 milliseconds. On the third restart failure within the 200 millisecond interval, the Cluster service considers the resource to have failed and may, depending on the RestartAction property, attempt to fail over the resource's group to another node.

After the interval defined by the RestartPeriod property is exceeded, the Cluster service resets the property to zero.

If not specified, the default value for the RestartPeriod property is 90000 milliseconds.

What is mscsResourceRestartPeriod?

This read-only value, in milliseconds (default 90000), defines the sliding window within which a set number of restart attempts (per mscsResourceRestartThreshold) are counted before the Cluster service considers the resource truly failed and may fail its group over to another node. An admin uses this together with the restart threshold to gauge how many quick restart cycles a flapping resource is allowed before triggering a group failover.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9600.1.31.11.1.17
snmpwalk -v2c -c public <target> INFORMANT-MSCS::mscsResourceRestartPeriod

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9600.1.31.11.1.17.1
snmpget -v2c -c public <target> INFORMANT-MSCS::mscsResourceRestartPeriod.1

Start monitoring Windows Server failover cluster node (Microsoft Cluster Server, SNMP Informant) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the INFORMANT-MSCS::mscsResourceRestartPeriod OID value, configure state conditions and alerts, and monitor any Windows Server failover cluster node (Microsoft Cluster Server, SNMP Informant) 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.9600wtcsWTCS
1.3.6.1.4.1.9600.1informantWTCS
Numeric OIDNameModule
1.3.6.1.4.1.9600.1.31mscsINFORMANT-MSCS
1.3.6.1.4.1.9600.1.31.11mscsResourceTableINFORMANT-MSCS
1.3.6.1.4.1.9600.1.31.11.1mscsResourceEntryINFORMANT-MSCS
1.3.6.1.4.1.9600.1.31.11.1.17mscsResourceRestartPeriodINFORMANT-MSCS