CISCO-WAN-SRCP-MIB :: srcpPeerGrpTimeSinceHeartbeat

MIB Reference — IPNetwork Monitor

All MIBsCISCO-WAN-SRCP-MIBsrcpPeerGrpTimeSinceHeartbeat

srcpPeerGrpTimeSinceHeartbeat

Module: CISCO-WAN-SRCP-MIB

OID (symbolic): CISCO-WAN-SRCP-MIB::srcpPeerGrpTimeSinceHeartbeat

OID (numeric): 1.3.6.1.4.1.351.150.11.1.1.4.1.2

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description:

The time since the last heartbeat was received, in milliseconds. This represents the difference between the current time and the last time an SRCP command was received.

A value of 0 shall be returned if the heartbeat is not monitored. Even if the heartbeat is monitored, a value of 0 shall be returned if any of the following is true:

i) The system is locked or disabled (as indicated by mgAdministrativeState). ii) The stateChangeNtfy flag is disabled for the srcpPeer Group (as indicated by mgcRedundancyGrpStateChangeNtfy of CISCO-WAN-MGC-REDUN-MIB).

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.150.11.1.1.4.1.2
snmpwalk -v2c -c public <target> CISCO-WAN-SRCP-MIB::srcpPeerGrpTimeSinceHeartbeat

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.351.150.11.1.1.4.1.2.1
snmpget -v2c -c public <target> CISCO-WAN-SRCP-MIB::srcpPeerGrpTimeSinceHeartbeat.1

How to Use in IPNetwork Monitor

Select a Cisco WAN media gateway or media gateway controller (MGX-based) 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 locate srcpPeerGrpTimeSinceHeartbeat under the srcpPeerGrpParamEntry branch of CISCO-WAN-SRCP-MIB, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports, in milliseconds, how long it has been since the last SRCP heartbeat was received from the peer media gateway controller. 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 this value exceeds 30,000 (30 seconds), which would indicate the peer has stopped sending heartbeats and may have failed. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Numeric OIDNameModule
1isoLANART-AGENT
1.3orgBIANCA-BRICK-PPP-MIB
1.3.6dodBIANCA-BRICK-PPP-MIB
1.3.6.1internetBIANCA-BRICK-PPP-MIB
1.3.6.1.4privateBIANCA-BRICK-PPP-MIB
1.3.6.1.4.1enterprisesANIROOT-MIB
1.3.6.1.4.1.351stratacomCISCOWAN-SMI
1.3.6.1.4.1.351.150ciscoWanCISCOWAN-SMI
1.3.6.1.4.1.351.150.11ciscoWanSrcpMIBCISCO-WAN-SRCP-MIB
1.3.6.1.4.1.351.150.11.1srcpObjectsCISCO-WAN-SRCP-MIB
1.3.6.1.4.1.351.150.11.1.1srcpAdminObjectsCISCO-WAN-SRCP-MIB
1.3.6.1.4.1.351.150.11.1.1.4srcpPeerGrpParamTableCISCO-WAN-SRCP-MIB
1.3.6.1.4.1.351.150.11.1.1.4.1srcpPeerGrpParamEntryCISCO-WAN-SRCP-MIB
1.3.6.1.4.1.351.150.11.1.1.4.1.2srcpPeerGrpTimeSinceHeartbeatCISCO-WAN-SRCP-MIB