DC-BGP-MIB :: bgpPeerLocalAddr

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › DC-BGP-MIB › bgpPeerLocalAddr

bgpPeerLocalAddr

Module: DC-BGP-MIB

OID (symbolic): DC-BGP-MIB::bgpPeerLocalAddr

OID (numeric): 1.2.826.0.1.1578918.5.65.1.3.1.1.1.8

Node type: OBJECT-TYPE

Type: InetAddress

Access: read-only

Description: The address of the local end of the peering session. This is used as an index to the row. If a zero length address is used, DC-BGP will not bind a specific address but use whatever is available through the NM instance configured in the bgpPeerLocalNm field. In this case the bgpPeerSelectedLocalAddr field shows which local address is actually used. If a specific local address is configured, then outbound socket connections will be bound to this address. If a non-zero bgpPeerLocalPort is specified, then outbound socket connections will be bound to this port. Note that you can have 2 peer entries to the same remote if they come from a different local . To configure this each local must be specified explicitly and not be zero length. You will not be allowed to do this if you are listening on all addresses as it will be impossible to tell which peer an incoming connection is for. You must explicitly listen on each local address in this case. It is equivalent to the bgpM2PeerTable entry bgpM2PeerLocalAddr.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.2.826.0.1.1578918.5.65.1.3.1.1.1.8
snmpwalk -v2c -c public <target> DC-BGP-MIB::bgpPeerLocalAddr

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.2.826.0.1.1578918.5.65.1.3.1.1.1.8.1
snmpget -v2c -c public <target> DC-BGP-MIB::bgpPeerLocalAddr.1

Start monitoring Router/switch running Data Connection (DC) routing protocol software stack (BGP) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DC-BGP-MIB::bgpPeerLocalAddr OID value, configure state conditions and alerts, and monitor any Router/switch running Data Connection (DC) routing protocol software stack (BGP) from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.2member_bodyIEEE802dot11-MIB
1.2.826gbMETASWITCH-MIB
1.2.826.0gbNationalMETASWITCH-MIB
1.2.826.0.1gbNatCompanyMETASWITCH-MIB
1.2.826.0.1.1578918dataConnectionMETASWITCH-MIB
Numeric OIDNameModule
1.2.826.0.1.1578918.5.65.1bgpMibDC-BGP-MIB
1.2.826.0.1.1578918.5.65.1.3bgpPeerDC-BGP-MIB
1.2.826.0.1.1578918.5.65.1.3.1bgpPeerDataDC-BGP-MIB
1.2.826.0.1.1578918.5.65.1.3.1.1bgpPeerTableDC-BGP-MIB
1.2.826.0.1.1578918.5.65.1.3.1.1.1bgpPeerEntryDC-BGP-MIB
1.2.826.0.1.1578918.5.65.1.3.1.1.1.8bgpPeerLocalAddrDC-BGP-MIB