BGP4-OPT-PARAMETERS-MIB: View SNMP OID List / Download MIB

VENDOR: INTERNET-STANDARD


 Home MIB: BGP4-OPT-PARAMETERS-MIB
Download as:   
SNMPv2-SMI, SNMPv2-CONF, BGP4-MIB, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 bgp4OptParametersMIB 1.3.6.1.2.1.15.9
The extension of the MIB module for BGP-4 for optional parameters.
     bgpAuthenticationTable 1.3.6.1.2.1.15.9.1
The BGP-4 Authentication Table contains information about BGP Authentication Options on a per-peer basis.
         bgpAuthenticationPeerEntry 1.3.6.1.2.1.15.9.1.1
Information about Authentication on a per-peer basis.
             bgpAuthenticationEntry 1.3.6.1.2.1.15.9.1.1.2
Information about BGP-4 Authentication.
                 bgpAuthenticationDirection 1.3.6.1.2.1.15.9.1.1.2.1
This variable indicates whether authentication information is either being sent by the BGP speaker or has been been received by the BGP speaker. It also serves as the index into the table of authentication information for the direction of authentication.
                 bgpAuthenticationCode 1.3.6.1.2.1.15.9.1.1.2.2
This is the AuthenticationCode used. This value is set to -1 if Authentication is not present.
                 bgpAuthenticationDataLength 1.3.6.1.2.1.15.9.1.1.2.3
This value is derived from the optional parameter length minus one (the size of bgpAuthenticationCode). This value may be no larger than 252 due to overhead. This value is set to -1 if Authentication is not present.
                 bgpAuthenticationDataContents 1.3.6.1.2.1.15.9.1.1.2.4
This is the Authentication payload. The semantics of this variable are interpreted according to the authentication code.
     bgpCapabilitySupportAvailable 1.3.6.1.2.1.15.9.2
This variable determines whether BGP-4 capabilities are supported in this implementation. This variable may be set to false to disable capability support.
     bgpSupportedCapabilities 1.3.6.1.2.1.15.9.3
Vector of BGP-4 capabilities that are supported in this implementation. Capabilities are identified via the string of bits within this object. The first octet contains bits 0 to 7, the second octet contains bits 8 to 15 and so on. If a bit, i, is present and set, then the capability (i+1) is supported. When capabilities are not supported, all bits must be zero.
     bgpPeerCapabilitiesTable 1.3.6.1.2.1.15.9.4
This table contains contains the capabilities that are supported for a given peer.
         bgpPeerCapabilitiesEntry 1.3.6.1.2.1.15.9.4.2
These entries are keyed by a BGP-4 peers remote address and port combination over which the peering session has been established.
             bgpPeerCapabilitiesAnnounced 1.3.6.1.2.1.15.9.4.2.1
This bit vector identifies which capabilities have been announced to a BGP-4 speaker. Capabilities are identified via the string of bits within this object. The first octet contains bits 0 to 7, the second octet contains bits 8 to 15 and so on. If a bit, i, is present and set, then the capability (i+1) is supported. When capabilities are not supported, all bits must be zero.
             bgpPeerCapabilitiesReceived 1.3.6.1.2.1.15.9.4.2.2
This bit vector identifies which capabilities have been announced by the remote BGP-4 speaker. Capabilities are identified via the string of bits within this object. The first octet contains bits 0 to 7, the second octet contains bits 8 to 15 and so on. If a bit, i, is present and set, then the capability (i+1) is supported. When capabilities are not supported, all bits must be zero.
     bgpProtocolExtensions 1.3.6.1.2.1.15.9.5
Registration point for MIB Modules for BGP Protocol Extensions. The Capabilities Advertisement RFC delineates IANA registered capability code numbers, 0-127 and private use capability code numbers, 128-255. The first sub-identifier will be the enterprise number of the registering entity. This is used to remove the ambiguity of the private use portion of the capability code assignments. For IANA registered capability codes 0-127, the first sub-identifier will be 0. The second sub-identifier will be the capability code for the advertised capability. For example, the MPBGP-MIB would be assigned as { bgpProtocolStandardExtensions 0 1 } since it has been assigned capability code number 1 and is an IETF assigned (IANA registered) capability extension.