All MIBs › VIPTELA-OPER-BGP › bgpBgpNeighborRec4byteAsCap
bgpBgpNeighborRec4byteAsCap
Module: VIPTELA-OPER-BGP
OID (symbolic): VIPTELA-OPER-BGP::bgpBgpNeighborRec4byteAsCap
OID (numeric): 1.3.6.1.4.1.41916.14.9.1.16
Node type: OBJECT-TYPE
Type: TruthValue
Access: read-only
Description: Received 4-byte AS capability
What is bgpBgpNeighborRec4byteAsCap?
A boolean indicating whether this neighbor advertised back that it supports the 4-byte AS number capability, confirming both sides can use AS numbers above 65535.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.41916.14.9.1.16 snmpwalk -v2c -c public <target> VIPTELA-OPER-BGP::bgpBgpNeighborRec4byteAsCap
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.41916.14.9.1.16.1 snmpget -v2c -c public <target> VIPTELA-OPER-BGP::bgpBgpNeighborRec4byteAsCap.1
Start monitoring Viptela/Cisco SD-WAN vEdge router (BGP peer-session/RIB-memory status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the VIPTELA-OPER-BGP::bgpBgpNeighborRec4byteAsCap OID value, configure state conditions and alerts, and monitor any Viptela/Cisco SD-WAN vEdge router (BGP peer-session/RIB-memory status) from a single console.
OID Breakdown
Upper-level ancestors (7 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.41916 | viptela | VIPTELA-GLOBAL |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.41916.14 | viptela_oper_bgp | VIPTELA-OPER-BGP |
| 1.3.6.1.4.1.41916.14.9 | bgpBgpNeighborTable | VIPTELA-OPER-BGP |
| 1.3.6.1.4.1.41916.14.9.1 | bgpBgpNeighborEntry | VIPTELA-OPER-BGP |
| 1.3.6.1.4.1.41916.14.9.1.16 | bgpBgpNeighborRec4byteAsCap | VIPTELA-OPER-BGP |