FOUNDRY-BGP4V2-MIB :: bgp4V2PeerInUpdates

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › FOUNDRY-BGP4V2-MIB › bgp4V2PeerInUpdates

bgp4V2PeerInUpdates

Module: FOUNDRY-BGP4V2-MIB

OID (symbolic): FOUNDRY-BGP4V2-MIB::bgp4V2PeerInUpdates

OID (numeric): 1.3.6.1.4.1.1991.3.5.1.1.7.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of BGP UPDATE messages received on this connection.

What is bgp4V2PeerInUpdates?

This counter tracks the number of BGP UPDATE messages received on a specific peering connection. Admins monitor this to confirm a peer is actively sending route information, since a stalled count can indicate a routing or session problem even if the TCP connection stays up. For example, this counter staying flat for an extended period on an otherwise established session would prompt the admin to check for a stuck or misbehaving peer.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1991.3.5.1.1.7.1.1
snmpwalk -v2c -c public <target> FOUNDRY-BGP4V2-MIB::bgp4V2PeerInUpdates

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1991.3.5.1.1.7.1.1.1
snmpget -v2c -c public <target> FOUNDRY-BGP4V2-MIB::bgp4V2PeerInUpdates.1

Start monitoring Brocade/Foundry FastIron router/Layer 3 switch (BGP4 v2) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the FOUNDRY-BGP4V2-MIB::bgp4V2PeerInUpdates OID value, configure state conditions and alerts, and monitor any Brocade/Foundry FastIron router/Layer 3 switch (BGP4 v2) from a single console.

How to Use in IPNetwork Monitor

Select a Brocade/Foundry FastIron router/Layer 3 switch (BGP4 v2) 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 bgp4V2PeerInUpdates 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 number of BGP UPDATE messages received on this connection. 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 (11 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.1991foundryFOUNDRY-SN-ROOT-MIB
1.3.6.1.4.1.1991.3experimentalFOUNDRY-SN-ROOT-MIB
1.3.6.1.4.1.1991.3.5bgp4V2RootFOUNDRY-SN-ROOT-MIB
1.3.6.1.4.1.1991.3.5.1bgp4V2BGP4V2-MIB
1.3.6.1.4.1.1991.3.5.1.1bgp4V2ObjectsBGP4V2-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1991.3.5.1.1.7bgp4V2PeerCountersTableFOUNDRY-BGP4V2-MIB
1.3.6.1.4.1.1991.3.5.1.1.7.1bgp4V2PeerCountersEntryFOUNDRY-BGP4V2-MIB
1.3.6.1.4.1.1991.3.5.1.1.7.1.1bgp4V2PeerInUpdatesFOUNDRY-BGP4V2-MIB