RAPID-CITY :: rcIpBgpPeerRemoteAs

MIB Reference — IPNetwork Monitor

All MIBsRAPID-CITYrcIpBgpPeerRemoteAs

rcIpBgpPeerRemoteAs

Module: RAPID-CITY

OID (symbolic): RAPID-CITY::rcIpBgpPeerRemoteAs

OID (numeric): 1.3.6.1.4.1.2272.1.8.101.9.1.3

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description:

Remote Autonomous system number of this peer

What is rcIpBgpPeerRemoteAs?

This object stores the autonomous system (AS) number of a remote BGP peer, identifying which routing domain the neighboring router belongs to for proper routing policy application. The AS number is fundamental to BGP routing, as it determines how routes are propagated and which routing policies apply to traffic exchanged with this peer. Network operators configure and verify this value when establishing or modifying BGP peering relationships between routers in different autonomous systems.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2272.1.8.101.9.1.3
snmpwalk -v2c -c public <target> RAPID-CITY::rcIpBgpPeerRemoteAs

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2272.1.8.101.9.1.3.1
snmpget -v2c -c public <target> RAPID-CITY::rcIpBgpPeerRemoteAs.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.2272.1.8.101.9.1.3.1 i <value>

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> rcIpBgpPeerRemoteAs.1

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.2272rapidCityRAPID-CITY
1.3.6.1.4.1.2272.1rcMgmtRAPID-CITY
1.3.6.1.4.1.2272.1.8rcIpRAPID-CITY
1.3.6.1.4.1.2272.1.8.101rcIpBgpRAPID-CITY
1.3.6.1.4.1.2272.1.8.101.9rcIpBgpPeerTableRAPID-CITY
1.3.6.1.4.1.2272.1.8.101.9.1rcIpBgpPeerEntryRAPID-CITY
1.3.6.1.4.1.2272.1.8.101.9.1.3rcIpBgpPeerRemoteAsRAPID-CITY