BGP4-OPT-PARAMETERS-MIB

File: BGP4-OPT-PARAMETERS-MIB.mib (10788 bytes)

Imported modules

SNMPv2-SMI BGP4-MIB SNMPv2-TC
SNMPv2-CONF

Imported symbols

MODULE-IDENTITY OBJECT-TYPE NOTIFICATION-TYPE
Integer32 Counter32 Gauge32
mib-2 bgp bgpPeerRemoteAddr
TruthValue AutonomousType MODULE-COMPLIANCE
OBJECT-GROUP NOTIFICATION-GROUP

Defined Types

BgpAuthenticationEntry  
SEQUENCE    
  bgpAuthenticationDirection Integer32
  bgpAuthenticationCode Integer32
  bgpAuthenticationDataLength Integer32
  bgpAuthenticationDataContents OCTET STRING

BgpPeerCapabilitiesEntry  
SEQUENCE    
  bgpPeerCapabilitiesAnnounced OCTET STRING
  bgpPeerCapabilitiesReceived OCTET STRING

Defined Values

bgp4OptParametersMIB 1.3.6.1.2.1.15.9
The extension of the MIB module for BGP-4 for optional parameters.
MODULE-IDENTITY    

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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    BgpAuthenticationPeerEntry

bgpAuthenticationPeerEntry 1.3.6.1.2.1.15.9.1.1
Information about Authentication on a per-peer basis.
Status: current Access: not-accessible
OBJECT-TYPE    
  BgpAuthenticationEntry  

bgpAuthenticationEntry 1.3.6.1.2.1.15.9.1.1.2
Information about BGP-4 Authentication.
Status: current Access: not-accessible
OBJECT-TYPE    
  BgpAuthenticationEntry  

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.
Status: current Access: not-accessible
OBJECT-TYPE    
  Integer32 sent(1), received(2)  

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.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32 -1 | 0..255  

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.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32 -1 | 0..252  

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.
Status: current Access: read-write
OBJECT-TYPE    
  OCTET STRING Size(1..252)  

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.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

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.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(0..32)  

bgpPeerCapabilitiesTable 1.3.6.1.2.1.15.9.4
This table contains contains the capabilities that are supported for a given peer.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    BgpPeerCapabilitiesEntry

bgpPeerCapabilitiesEntry 1.3.6.1.2.1.15.9.4.2
These entries are keyed by a BGP-4 peer's remote address and port combination over which the peering session has been established.
Status: current Access: not-accessible
OBJECT-TYPE    
  BgpPeerCapabilitiesEntry  

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.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(0..32)  

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.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(0..32)  

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.
Status: current Access: read-only
OBJECT-TYPE    
  AutonomousType