CISCO-GDOI-MIB :: cgmGdoiKeyServerRekeysPushed

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-GDOI-MIBcgmGdoiKeyServerRekeysPushed

cgmGdoiKeyServerRekeysPushed

Module: CISCO-GDOI-MIB

OID (symbolic): CISCO-GDOI-MIB::cgmGdoiKeyServerRekeysPushed

OID (numeric): 1.3.6.1.4.1.9.9.759.1.2.1.1.5

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The sequence number of the last rekey sent from the Key Server to its registered Group Members for this GDOI group.

What is cgmGdoiKeyServerRekeysPushed?

Reports the sequence number of the most recent rekey message the Key Server has sent to its registered Group Members for a given GDOI group, letting you track rekey progress.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.759.1.2.1.1.5
snmpwalk -v2c -c public <target> CISCO-GDOI-MIB::cgmGdoiKeyServerRekeysPushed

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.759.1.2.1.1.5.1
snmpget -v2c -c public <target> CISCO-GDOI-MIB::cgmGdoiKeyServerRekeysPushed.1

Start monitoring Cisco routers (GET VPN / GDOI) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-GDOI-MIB::cgmGdoiKeyServerRekeysPushed OID value, configure state conditions and alerts, and monitor any Cisco routers (GET VPN / GDOI) from a single console.

How to Use in IPNetwork Monitor

Select a Cisco router (GET VPN / GDOI) 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 cgmGdoiKeyServerRekeysPushed into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The sequence number of the last rekey sent from the Key Server to its registered Group Members for this GDOI group. 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 a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline (in GROUPKEY-PUSH Messages), since an unexpected spike often reflects a real change in traffic or activity. 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.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.759ciscoGdoiMIBCISCO-GDOI-MIB
1.3.6.1.4.1.9.9.759.1cgmGdoiMIBObjectsCISCO-GDOI-MIB
1.3.6.1.4.1.9.9.759.1.2cgmGdoiPeersCISCO-GDOI-MIB
1.3.6.1.4.1.9.9.759.1.2.1cgmGdoiKeyServerTableCISCO-GDOI-MIB
1.3.6.1.4.1.9.9.759.1.2.1.1cgmGdoiKeyServerEntryCISCO-GDOI-MIB
1.3.6.1.4.1.9.9.759.1.2.1.1.5cgmGdoiKeyServerRekeysPushedCISCO-GDOI-MIB