STACK-TOP :: sysMasterVoteTimes

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › STACK-TOP › sysMasterVoteTimes

sysMasterVoteTimes

Module: STACK-TOP

OID (symbolic): STACK-TOP::sysMasterVoteTimes

OID (numeric): 1.3.6.1.4.1.3902.3.301.1

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: How many times stack system's master device be voted.

What is sysMasterVoteTimes?

Count of how many times the stack's master-device election (voting) process has run since the stack came up. A high or rapidly climbing count can indicate instability in the master-election process, worth investigating alongside sysTopChagTimes.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3902.3.301.1
snmpwalk -v2c -c public <target> STACK-TOP::sysMasterVoteTimes

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.3902.3.301.1.1
snmpget -v2c -c public <target> STACK-TOP::sysMasterVoteTimes.1

Start monitoring ZTE stackable switch (master-election/topology-change status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the STACK-TOP::sysMasterVoteTimes OID value, configure state conditions and alerts, and monitor any ZTE stackable switch (master-election/topology-change status) from a single console.

How to Use in IPNetwork Monitor

Select a ZTE stackable switch (master-election/topology-change status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type sysMasterVoteTimes into the Find box to locate it in the OID tree, then select it and click OK. It reports the how many times stack system's master device be voted. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an Integer32-type OID, Value bounds is the most useful condition here — trigger an alert if the value drifts significantly from its normal baseline, since an unexpected change often points to a real underlying issue. Click Finish to create the monitor; you can adjust any parameter later.

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.3902zteDPI-MIB
1.3.6.1.4.1.3902.3zxr10FANS-POWER-MIB
Numeric OIDNameModule
1.3.6.1.4.1.3902.3.301stacktopSTACK-TOP
1.3.6.1.4.1.3902.3.301.1sysMasterVoteTimesSTACK-TOP