HH3C-BGP-VPN-MIB :: hh3cBgpPeerRouteRcvCount

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › HH3C-BGP-VPN-MIB › hh3cBgpPeerRouteRcvCount

hh3cBgpPeerRouteRcvCount

Module: HH3C-BGP-VPN-MIB

OID (symbolic): HH3C-BGP-VPN-MIB::hh3cBgpPeerRouteRcvCount

OID (numeric): 1.3.6.1.4.1.25506.2.202.1.1.3.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Denotes the number of routes received from the BGP peer.

What is hh3cBgpPeerRouteRcvCount?

This counter object tracks the total number of routes received from a specific BGP peer over that session. An administrator monitors this to gauge how much routing information a peer is actually advertising, useful for spotting an unexpectedly large or small route count that might indicate a misconfiguration on the peer's side. Seeing this counter jump from 500 to 50,000 routes might indicate the peer began leaking a full routing table unexpectedly.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.25506.2.202.1.1.3.1.1
snmpwalk -v2c -c public <target> HH3C-BGP-VPN-MIB::hh3cBgpPeerRouteRcvCount

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.25506.2.202.1.1.3.1.1.1
snmpget -v2c -c public <target> HH3C-BGP-VPN-MIB::hh3cBgpPeerRouteRcvCount.1

Start monitoring H3C MPLS/VPN provider-edge router (BGP L3VPN peer/route tracking) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HH3C-BGP-VPN-MIB::hh3cBgpPeerRouteRcvCount OID value, configure state conditions and alerts, and monitor any H3C MPLS/VPN provider-edge router (BGP L3VPN peer/route tracking) from a single console.

How to Use in IPNetwork Monitor

Select an H3C MPLS/VPN provider-edge router (BGP L3VPN peer/route tracking) 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 hh3cBgpPeerRouteRcvCount 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. Denotes the number of routes received from the BGP peer. 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, 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.25506hh3cHH3C-OID-MIB
1.3.6.1.4.1.25506.2hh3cCommonHH3C-OID-MIB
Numeric OIDNameModule
1.3.6.1.4.1.25506.2.202hh3cBgpVpnHH3C-BGP-VPN-MIB
1.3.6.1.4.1.25506.2.202.1hh3cBgpVpnObjectsHH3C-BGP-VPN-MIB
1.3.6.1.4.1.25506.2.202.1.1hh3cBgpPeersHH3C-BGP-VPN-MIB
1.3.6.1.4.1.25506.2.202.1.1.3hh3cBgpPeerRouteTableHH3C-BGP-VPN-MIB
1.3.6.1.4.1.25506.2.202.1.1.3.1hh3cBgpPeerRouteEntryHH3C-BGP-VPN-MIB
1.3.6.1.4.1.25506.2.202.1.1.3.1.1hh3cBgpPeerRouteRcvCountHH3C-BGP-VPN-MIB