draft-ietf-idr-bgp4-mibv2-03.txt   draft-ietf-idr-bgp4-mibv2-04.txt 
Inter-Domain Routing Working Group J. Haas Inter-Domain Routing Working Group J. Haas
Internet Draft NextHop Internet Draft NextHop
S. Hares S. Hares
NextHop NextHop
W. Tackabury W. Tackabury
Gold Wire Technology Gold Wire Technology
November 4, 2002 January 12, 2004
Definitions of Managed Objects Definitions of Managed Objects
for the Fourth Version of Border Gateway Protocol (BGP-4), for the Fourth Version of Border Gateway Protocol (BGP-4),
Second Version Second Version
<draft-ietf-idr-bgp4-mibv2-03.txt> <draft-ietf-idr-bgp4-mibv2-04.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 2, line 15 skipping to change at page 2, line 15
Distribution of this memo is unlimited. Distribution of this memo is unlimited.
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects used for managing the In particular, it describes managed objects used for managing the
Border Gateway Protocol Version 4. Border Gateway Protocol Version 4.
The SNMP Management Framework presently consists of five major compo- The Internet-Standard Management Framework
nents:
o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for
the purpose of management. The first version of this Structure
of Management Information (SMI) is called SMIv1 and described
in STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215
[4]. The second version, called SMIv2, is described in STD 58,
RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1
and described in STD 15, RFC 1157 [8]. A second version of the
SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in RFC 1901
[9] and RFC 1906 [10]. The third version of the message proto-
col is called SNMPv3 and described in RFC 1906 [10], RFC 2572
[11] and RFC 2574 [12].
o Protocol operations for accessing management information. The For a detailed overview of the documents that describe the current
first set of protocol operations and associated PDU formats is Internet-Standard Management Framework, please refer to section 7 of
described in STD 15, RFC 1157 [8]. A second set of protocol RFC 3410 [RFC3410].
operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2573 [14]
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. MIB objects are generally
defined using the mechanisms defined in the SMI. accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
2. Objectives 2. Objectives
This MIB Module is meant to broadly update and replace a prior MIB This MIB Module is meant to broadly update and replace a prior MIB
Module defined in RFC 1657 [12]. Additionally, there is another Module defined in RFC 1657 [RFC1657]. Additionally, there is another
effort underway to address very specific limited objectives in updat- effort underway to address very specific limited objectives in updat-
ing points in the RFC 1657 object definition and managed object ing points in the RFC 1657 object definition and managed object
attributes [13]. The MIB Module described herein is intended to attributes [MIB-DRAFT]. The MIB Module described herein is intended
fully serve the functions and scope of RFC 1657 and these RFC 1657 to fully serve the functions and scope of RFC 1657 and these RFC 1657
updates. updates.
2.1. Protocol Extensions 2.1. Protocol Extensions
Additionally, however, there are a number of ways in which the BGP Additionally, however, there are a number of ways in which the BGP
Protocol has been enhanced through its ability for added capabili- Protocol has been enhanced through its ability for added capabili-
ties. Implementations of those capabilities have not been able to ties. Implementations of those capabilities have not been able to
have any management capabilities present in RFC 1657-compliant MIB have any management capabilities present in RFC 1657-compliant MIB
module agents, since the capabilities themselves postdated the adop- module agents, since the capabilities themselves postdated the adop-
tion of RFC 1657. For several significant capabilities, in the form tion of RFC 1657. For several significant capabilities, in the form
of BGP Communities [17], Autonomous System Confederation [16] , BGP of BGP Communities [RFC1997], Autonomous System Confederation
Multiprotocol Extensions [18], and Route Reflection [19], the MIB [RFC3065] , BGP Multiprotocol Extensions [RFC2858], and Route Reflec-
Module defined in this document exposes object types to manage those tion [RFC2796], the MIB Module defined in this document exposes
extended capabilities and their operation. object types to manage those extended capabilities and their opera-
tion.
One of these extensions in particular (the multiprotocol extensions) One of these extensions in particular (the multiprotocol extensions)
requires a thorough redefinition of MIB table row indices from the requires a thorough redefinition of MIB table row indices from the
RFC 1657 state. This allows transport-independent address indices RFC 1657 state. This allows transport-independent address indices
consistent with the Address Family Identifier (AFI) and Subsequent consistent with the Address Family Identifier (AFI) and Subsequent
Address Family Identifier (SAFI) mechanisms of that extension. Address Family Identifier (SAFI) mechanisms of that extension.
2.2. Mechanisms for MIB Extensibility 2.2. Mechanisms for MIB Extensibility
Moreover, the requirement for the incremental update of support for Moreover, the requirement for the incremental update of support for
skipping to change at page 5, line 14 skipping to change at page 4, line 35
3.1. bgpM2BaseScalars 3.1. bgpM2BaseScalars
The bgpM2BaseScalars section (and corresponding OBJECT IDENTIFIER) is The bgpM2BaseScalars section (and corresponding OBJECT IDENTIFIER) is
used to delineate object types used for basic management and monitor- used to delineate object types used for basic management and monitor-
ing of the protocol implementation. These are core parameters for ing of the protocol implementation. These are core parameters for
the local configuration. While notifications are designed to be the local configuration. While notifications are designed to be
extensible into any other section in the MIB module, the currently extensible into any other section in the MIB module, the currently
defined traps are located here, in a subsection 'bgpM2BaseNotifica- defined traps are located here, in a subsection 'bgpM2BaseNotifica-
tions'. This is rooted at index level zero (0) here, owing to con- tions'. This is rooted at index level zero (0) here, owing to con-
ventions established in [4]. ventions established in [RFC2576].
Support for multiple concurrently supported versions of BGP is Support for multiple concurrently supported versions of BGP is
exposed through the entries of the bgpM2VersionTable. Similarly, exposed through the entries of the bgpM2VersionTable. Similarly,
support for multiple capabilities and authentication mechanisms, as support for multiple capabilities and authentication mechanisms, as
identified by their assigned numbers, are reported in the bgpM2Sup- identified by their assigned numbers, are reported in the bgpM2Sup-
portedCapabilitiesTable and bgpM2SupportedAuthTable respectively. portedCapabilitiesTable and bgpM2SupportedAuthTable respectively.
In the MIB document, there are currently scalar extension mechanisms In the MIB document, there are currently scalar extension mechanisms
to allow the agent to report membership of a local BGP Confederation to allow the agent to report membership of a local BGP Confederation
[21] or Route Reflection Cluster ID [24], as well as whether these [RFC3065] or Route Reflection Cluster ID [RFC2796], as well as
capabilities are in fact supported by the implementation. These are whether these capabilities are in fact supported by the implementa-
consistent with the non-capability based extension section indexing tion. These are consistent with the non-capability based extension
guidelines as presented above. section indexing guidelines as presented above.
bgpM2BaseScalars also is the root for a subsection, bgpM2BaseScalar- bgpM2BaseScalars also is the root for a subsection, bgpM2BaseScalar-
Configuration, which contains the companion configuration objects for Configuration, which contains the companion configuration objects for
the base scalar objects delineated in the preceding paragraphs. the base scalar objects delineated in the preceding paragraphs.
These are presented as a series of scalar read-write objects, with a These are presented as a series of scalar read-write objects, with a
single OBJECT-TYPE of syntax StorageType to designate the persistence single OBJECT-TYPE of syntax StorageType to designate the persistence
of the instance value data for these configuration scalars. of the instance value data for these configuration scalars.
3.2. bgpM2PeerData 3.2. bgpM2PeerData
skipping to change at page 6, line 8 skipping to change at page 5, line 28
last error encountered on a given peering session. last error encountered on a given peering session.
Further subsections report authentication state with the peer, peer- Further subsections report authentication state with the peer, peer-
ing session detected errors, and elapsed time it has taken to ing session detected errors, and elapsed time it has taken to
advance the peering session into various states defined in the proto- advance the peering session into various states defined in the proto-
col FSM. col FSM.
The bgpM2PeerConfiguredTimersTable reports and allows dynamic reset The bgpM2PeerConfiguredTimersTable reports and allows dynamic reset
of key timers on the peer session. These currently allow reset of of key timers on the peer session. These currently allow reset of
hold time and keepalive timer, for compatibility with the same capa- hold time and keepalive timer, for compatibility with the same capa-
bilities in RFC 1657 [17]. For these resettable timers, their end-to- bilities in RFC 1657 [RFC1657]. For these resettable timers, their
end negotiated current values are reflected in the bgpM2PeerNegotiat- end-to-end negotiated current values are reflected in the
edTimersTable. bgpM2PeerNegotiatedTimersTable.
As currently defined, these tables describing authentication, error As currently defined, these tables describing authentication, error
state, and timer values (in addition to the configuration tables for state, and timer values (in addition to the configuration tables for
session timers) are tightly coupled enough to the logical per-row session timers) are tightly coupled enough to the logical per-row
view exposed in the bgpM2PeerTable row entries on a session that view exposed in the bgpM2PeerTable row entries on a session that
these subordinate "tables" are defined as AUGMENTing the these subordinate "tables" are defined as AUGMENTing the
bgpM2PeerTable itself. The other primary design criterion behind bgpM2PeerTable itself. The other primary design criterion behind
this decision is that using this AUGMENTation does not increase the this decision is that using this AUGMENTation does not increase the
per-row-data requirements of bgpM2PeerTable instance retrieval so as per-row-data requirements of bgpM2PeerTable instance retrieval so as
to make such per-row retrieval unwieldy for the management applica- to make such per-row retrieval unwieldy for the management applica-
tion. tion.
3.2.1. bgpM2PeerCapabilities 3.2.1. bgpM2PeerCapabilities
bgpM2PeerCapabilitiesData has objects and tables to describe BGP bgpM2PeerCapabilitiesData has objects and tables to describe BGP
capabilities locally supported, and those reported and negotiated capabilities locally supported, and those reported and negotiated
over each peer session. For tables supporting each of these capa- over each peer session. For tables supporting each of these capa-
bility sets, capability code and data value are provided. Attention bility sets, capability code and data value are provided. Attention
must be given to the fact that multiple instances of a given capabil- must be given to the fact that multiple instances of a given
ity can be transmitted between BGP speakers. capability can be transmitted between BGP speakers.
3.2.2. bgpM2PeerCounters 3.2.2. bgpM2PeerCounters
The bgpM2CountersTable and bgpM2PrefixCountersTable report protocol The bgpM2CountersTable and bgpM2PrefixCountersTable report protocol
exchanges/FSM transitions, and discrete number of NLRIs exchanged per exchanges/FSM transitions, and discrete number of NLRIs exchanged per
peering session, respectively. This is independent of actual peering session, respectively. This is independent of actual
exchanged path attributes, which are tabularized later in the MIB exchanged path attributes, which are tabularized later in the MIB
module. Note that session transitions as reflected in changes of module. Note that session transitions as reflected in changes of
instances within this table may also be reflected in issuance of instances within this table may also be reflected in issuance of
bgpM2Established and bgpM2BackwardTransition NOTIFICATION-TYPE PDUs. bgpM2Established and bgpM2BackwardTransition NOTIFICATION-TYPE PDUs.
skipping to change at page 7, line 31 skipping to change at page 6, line 49
its related AUGMENTed tables bgpM2CfgPeerTimersTable and bgpM2Cfg- its related AUGMENTed tables bgpM2CfgPeerTimersTable and bgpM2Cfg-
PeerAuthTable. These are used to facilitate direct creation of peer- PeerAuthTable. These are used to facilitate direct creation of peer-
ing sessions by the management application. The function of columnar ing sessions by the management application. The function of columnar
OBJECT-TYPEs within the bgpM2CfgPeerTable for local and remote OBJECT-TYPEs within the bgpM2CfgPeerTable for local and remote
address, version negotiation, and various row-administrative address, version negotiation, and various row-administrative
attributes (RowStatus and StorageType SYNTAXes) are straightforward attributes (RowStatus and StorageType SYNTAXes) are straightforward
enough. The only subtlety with respect to how peering sessions are enough. The only subtlety with respect to how peering sessions are
activated from usage of this table, and how the activated sessions activated from usage of this table, and how the activated sessions
are reflected through their bgpM2PeerTable and bgpM2CfgPeerAdminSta- are reflected through their bgpM2PeerTable and bgpM2CfgPeerAdminSta-
tusTable entries, is in the usage of the bgpM2CfgPeerTable columnar tusTable entries, is in the usage of the bgpM2CfgPeerTable columnar
object bgpM2CfgPeerStatus. bgpM2CfgPeerStatus can take on two val- object bgpM2CfgPeerStatus. bgpM2CfgPeerStatus can take on two
ues. When a peering session, as reflected through its row instance values. When a peering session, as reflected through its row
in the bgpM2CfgPeerTable, has the bgpM2CfgPeerStatus instance value instance in the bgpM2CfgPeerTable, has the bgpM2CfgPeerStatus
in that row set to running(2) at the time of the SYNTAX RowStatus instance value in that row set to running(2) at the time of the SYN-
object instance of bgpM2CfgPeerRowEntryStatus set to active(1), the TAX RowStatus object instance of bgpM2CfgPeerRowEntryStatus set to
peering session will in fact be activated in the BGP routing process active(1), the peering session will in fact be activated in the BGP
(in addition to having its row instance created in the bgpM2Cfg- routing process (in addition to having its row instance created in
PeerTable and bgpM2CfgPeerAdminStatusTable). In this case, the asso- the bgpM2CfgPeerTable and bgpM2CfgPeerAdminStatusTable). In this
ciated row of the bgpM2CfgPeerAdminStatusTable row bgpM2CfgPeerAdmin- case, the associated row of the bgpM2CfgPeerAdminStatusTable row
Status instance would have the value of start(2). If, in the prior bgpM2CfgPeerAdminStatus instance would have the value of start(2).
example, the bgpM2CfgPeerStatus is halted(1) at the time of the If, in the prior example, the bgpM2CfgPeerStatus is halted(1) at the
bgpM2CfgPeerRowEntryStatus instance set to active(1), only the peer- time of the bgpM2CfgPeerRowEntryStatus instance set to active(1),
ing table entries would be created at this time of activation, with- only the peering table entries would be created at this time of acti-
out the peering session being automatically started. The bgpM2Cfg- vation, without the peering session being automatically started. The
PeerAdminStatusTable row bgpM2CfgPeerAdminStatus instance associated bgpM2CfgPeerAdminStatusTable row bgpM2CfgPeerAdminStatus instance
with the session would in this case reflect a value of stop(1). associated with the session would in this case reflect a value of
stop(1).
Since the row entries of the per-peer configuration tables which AUG- Since the row entries of the per-peer configuration tables which AUG-
MENT the bgpM2CfgPeerTable logically fate-share the row instances in MENT the bgpM2CfgPeerTable logically fate-share the row instances in
the bgpM2CfgPeerTable which they are AUGMENTing, they also share the the bgpM2CfgPeerTable which they are AUGMENTing, they also share the
same StorageType and RowStatus SYNTAX object sense of the same StorageType and RowStatus SYNTAX object sense of the bgpM2Cfg-
bgpM2CfgPeerTable rows which they augment. PeerTable rows which they augment.
3.3. BGP Routing Information Base Data 3.3. BGP Routing Information Base Data
An important table for providing index information for other tables An important table for providing index information for other tables
in the MIB module is the bgpM2NlriTable. This discriminates on a in the MIB module is the bgpM2NlriTable. This discriminates on a
given network prefix (by AFI/SAFI), and the peer which advertised the given network prefix (by AFI/SAFI), and the peer which advertised the
prefix (since it can be heard of from multiple speakers). The prefix (since it can be heard of from multiple speakers). The
bgpM2PathAttrIndex column which identifies each row in this table is bgpM2PathAttrIndex column which identifies each row in this table is
used as an index for other per-attribute tables through the remainder used as an index for other per-attribute tables through the remainder
of the MIB module. of the MIB module.
RFC 3107 [26] specifies a capability for exchanged routes between BGP RFC 3107 [RFC3107] specifies a capability for exchanged routes
peers to attach attribute information to a route indicating, specifi- between BGP peers to attach attribute information to a route indicat-
cally, related MPLS label path information. The MIB supports the ing, specifically, related MPLS label path information. The MIB sup-
presentation of this attribute information by generalizing how these ports the presentation of this attribute information by generalizing
attributes are presented to accommodate further extensions of this how these attributes are presented to accommodate further extensions
particular type. Within a given bgpM2NlriTable entry, we speak of of this particular type. Within a given bgpM2NlriTable entry, we
attribute data of this type as being 'opaque' to BGP, and use the speak of attribute data of this type as being 'opaque' to BGP, and
columnar OBJECT-TYPEs bgpM2NlriOpaqueType and bgpM2NlriOpaquePointer use the columnar OBJECT-TYPEs bgpM2NlriOpaqueType and bgpM2Nlri-
to refer to it. In the case of the RFC 3107 MPLS label encoding OpaquePointer to refer to it. In the case of the RFC 3107 MPLS label
(which is the only usage of these columnar fields in the bgpM2NlriTa- encoding (which is the only usage of these columnar fields in the
ble right now), a MPLS label stack would be referenced by bgpM2Nlri- bgpM2NlriTable right now), a MPLS label stack would be referenced by
OpaquePointer by its per-NLRI instance pointing to a row instance in bgpM2NlriOpaquePointer by its per-NLRI instance pointing to a row
the MPLS LSR MIB mplsLabelStackTable, and the bgpM2NlriOpaqueType instance in the MPLS LSR MIB mplsLabelStackTable, and the bgpM2Nlri-
instance having a value of bgpMplsLabelStack(1). OpaqueType instance having a value of bgpMplsLabelStack(1).
The bgpM2AdjRibsOutTable row entries reflect data on routes which The bgpM2AdjRibsOutTable row entries reflect data on routes which
have been placed, per peering session, in the Adj-Rib-Out for adver- have been placed, per peering session, in the Adj-Rib-Out for adver-
tisement to the associated peer. tisement to the associated peer.
The bgpM2PathAttrTable provides discrete BGP NLRI attributes which The bgpM2PathAttrTable provides discrete BGP NLRI attributes which
were received with the advertisement of the prefix by its advertising were received with the advertisement of the prefix by its advertising
peer. Specific information about the autonomous system path (AS peer. Specific information about the autonomous system path (AS
Path) advertised with the NLRI, on a per AS value, is to be found in Path) advertised with the NLRI, on a per AS value, is to be found in
the bgpM2AsPathTable. the bgpM2AsPathTable.
skipping to change at page 10, line 19 skipping to change at page 9, line 38
gle row retrieval exceed PDU size, for example), and those of general gle row retrieval exceed PDU size, for example), and those of general
logical data organization permit, certain tables logically at the logical data organization permit, certain tables logically at the
sub-peering-session level have been specified as AUGMENTing the pri- sub-peering-session level have been specified as AUGMENTing the pri-
mary tables (bgpM2PeerTable and bgpM2CfgPeerTable) to which those mary tables (bgpM2PeerTable and bgpM2CfgPeerTable) to which those
sub-peering-session row entries relate. This is to facilitate ease sub-peering-session row entries relate. This is to facilitate ease
on the part of a management application of assembling (for example, on the part of a management application of assembling (for example,
via GET-BULK operations across a lexicographically contiguous row via GET-BULK operations across a lexicographically contiguous row
scope) a management image of control information on a given peering scope) a management image of control information on a given peering
session. session.
1. 4. Definitions
BGP4-V2-MIB DEFINITIONS ::= BEGIN BGP4-V2-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Counter32, Gauge32, mib-2, Unsigned32, Integer32 Counter32, Gauge32, mib-2, Unsigned32, Integer32,
TimeTicks
FROM SNMPv2-SMI FROM SNMPv2-SMI
-- Note that the following reference to INET-ADDRESS-MIB
-- refers to the version as published in the RFC 2851
-- update internet draft.
InetAddressType, InetAddress, InetPortNumber, InetAddressType, InetAddress, InetPortNumber,
InetAutonomousSystemNumber, InetAddressPrefixLength InetAutonomousSystemNumber, InetAddressPrefixLength
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
TEXTUAL-CONVENTION, TruthValue, RowPointer, StorageType, TEXTUAL-CONVENTION, TruthValue, RowPointer, StorageType,
RowStatus RowStatus
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB; FROM SNMP-FRAMEWORK-MIB;
bgpM2 MODULE-IDENTITY bgpM2 MODULE-IDENTITY
LAST-UPDATED "200211040000Z" LAST-UPDATED "200401120000Z"
ORGANIZATION "IETF IDR Working Group" ORGANIZATION "IETF IDR Working Group"
CONTACT-INFO "E-mail: idr@merit.net CONTACT-INFO "E-mail: idr@merit.net
Jeffrey Haas (Editor) Jeffrey Haas (Editor)
825 Victors Way, Suite 100 825 Victors Way, Suite 100
Ann Arbor, MI 48108 Ann Arbor, MI 48108
Tel: +1 734 222-1600 Tel: +1 734 222-1600
Fax: +1 734 222-1602 Fax: +1 734 222-1602
E-mail: jhaas@nexthop.com" E-mail: jhaas@nexthop.com"
DESCRIPTION DESCRIPTION
"This MIB module defines management objects for "This MIB module defines management objects for
the Border Gateway Protocol, Version 4." the Border Gateway Protocol, Version 4."
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Ed.: replace XXX with IANA-assigned number & remove this note
BgpM2Identifier ::= TEXTUAL-CONVENTION BgpM2Identifier ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d." DISPLAY-HINT "1d."
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The representation of a BGP Identifier. The BGP "The representation of a BGP Identifier. The BGP
Identifier should be represented in the OCTET STRING Identifier should be represented in the OCTET STRING
as with the first OCTET of the string containing as with the first OCTET of the string containing
the first OCTET of the BGP Identifier received or sent the first OCTET of the BGP Identifier received or sent
in the OPEN packet and so on. in the OPEN packet and so on.
Even though the BGP Identifier is trending away from Even though the BGP Identifier is trending away from
an IP address it is still displayed as if it was one, an IP address it is still displayed as if it was one,
even when it would be an illegal IP address." even when it would be an illegal IP address."
SYNTAX OCTET STRING(SIZE (4)) SYNTAX OCTET STRING(SIZE (4))
BgpM2Afi ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The representation of a BGP AFI"
SYNTAX Unsigned32(0..65535)
BgpM2Safi ::= TEXTUAL-CONVENTION BgpM2Safi ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The representation of a BGP Safi" "The representation of a BGP SAFI"
SYNTAX Unsigned32(0..255) SYNTAX Unsigned32(0..255)
BgpM2Community ::= TEXTUAL-CONVENTION BgpM2Community ::= TEXTUAL-CONVENTION
DISPLAY-HINT "2d:" DISPLAY-HINT "2d:"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The representation of a BGP Community." "The representation of a BGP Community."
SYNTAX OCTET STRING(SIZE(4)) SYNTAX OCTET STRING(SIZE(4))
BgpM2ExtendedCommunity ::= TEXTUAL-CONVENTION BgpM2ExtendedCommunity ::= TEXTUAL-CONVENTION
skipping to change at page 14, line 16 skipping to change at page 13, line 39
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value is TRUE if this version of the BGP protocol "This value is TRUE if this version of the BGP protocol
identified in 'bgpM2VersionIndex' is supported. The absence identified in 'bgpM2VersionIndex' is supported. The absence
of a row for a particular bgpM2VersionIndex indicates that of a row for a particular bgpM2VersionIndex indicates that
that bgpM2VersionIndex protocol version number is not that bgpM2VersionIndex protocol version number is not
supported." supported."
::= { bgpM2VersionEntry 2 } ::= { bgpM2VersionEntry 2 }
-- --
-- Supported authentication mechanisms
--
bgpM2SupportedAuthentication
OBJECT IDENTIFIER ::= { bgpM2BaseScalars 2 }
bgpM2SupportedAuthTable OBJECT-TYPE
SYNTAX SEQUENCE OF BgpM2SupportedAuthEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The supported BGP authentication mechanisms."
::= { bgpM2SupportedAuthentication 1 }
bgpM2SupportedAuthEntry OBJECT-TYPE
SYNTAX BgpM2SupportedAuthEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entry containing information whether a given BGP
authentication mechanism is supported by this
implementation."
INDEX {
bgpM2SupportedAuthCode
}
::= { bgpM2SupportedAuthTable 1 }
BgpM2SupportedAuthEntry ::= SEQUENCE {
bgpM2SupportedAuthCode
Unsigned32,
bgpM2SupportedAuthValue
TruthValue
}
bgpM2SupportedAuthCode OBJECT-TYPE
SYNTAX Unsigned32(0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The BGP authentication code."
::= { bgpM2SupportedAuthEntry 1 }
bgpM2SupportedAuthValue OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This value is TRUE if a given authentication method
is supported by the local implementation."
::= { bgpM2SupportedAuthEntry 2 }
--
-- Supported BGP Capabilities -- Supported BGP Capabilities
-- --
bgpM2SupportedCapabilities bgpM2SupportedCapabilities
OBJECT IDENTIFIER ::= { bgpM2BaseScalars 3 } OBJECT IDENTIFIER ::= { bgpM2BaseScalars 2 }
bgpM2CapabilitySupportAvailable OBJECT-TYPE bgpM2CapabilitySupportAvailable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value is TRUE if capability support is "This value is TRUE if capability support is
available and is enabled." available and is enabled."
::= { bgpM2SupportedCapabilities 1 } ::= { bgpM2SupportedCapabilities 1 }
skipping to change at page 23, line 8 skipping to change at page 21, line 24
::= { bgpM2PeerData 1 } ::= { bgpM2PeerData 1 }
bgpM2PeerEntry OBJECT-TYPE bgpM2PeerEntry OBJECT-TYPE
SYNTAX BgpM2PeerEntry SYNTAX BgpM2PeerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Entry containing information about the connection with "Entry containing information about the connection with
a remote BGP peer." a remote BGP peer."
INDEX { INDEX {
bgpM2PeerInstance,
bgpM2PeerLocalAddrType, bgpM2PeerLocalAddrType,
bgpM2PeerLocalAddr, bgpM2PeerLocalAddr,
bgpM2PeerRemoteAddrType, bgpM2PeerRemoteAddrType,
bgpM2PeerRemoteAddr bgpM2PeerRemoteAddr
} }
::= { bgpM2PeerTable 1 } ::= { bgpM2PeerTable 1 }
BgpM2PeerEntry ::= SEQUENCE { BgpM2PeerEntry ::= SEQUENCE {
bgpM2PeerInstance
Unsigned32,
bgpM2PeerIdentifier bgpM2PeerIdentifier
BgpM2Identifier, BgpM2Identifier,
bgpM2PeerState bgpM2PeerState
INTEGER, INTEGER,
bgpM2PeerStatus bgpM2PeerStatus
INTEGER, INTEGER,
bgpM2PeerConfiguredVersion bgpM2PeerConfiguredVersion
Unsigned32, Unsigned32,
bgpM2PeerNegotiatedVersion bgpM2PeerNegotiatedVersion
Unsigned32, Unsigned32,
skipping to change at page 23, line 46 skipping to change at page 22, line 19
bgpM2PeerRemoteAddr bgpM2PeerRemoteAddr
InetAddress, InetAddress,
bgpM2PeerRemotePort bgpM2PeerRemotePort
InetPortNumber, InetPortNumber,
bgpM2PeerRemoteAs bgpM2PeerRemoteAs
InetAutonomousSystemNumber, InetAutonomousSystemNumber,
bgpM2PeerIndex bgpM2PeerIndex
Unsigned32 Unsigned32
} }
bgpM2PeerInstance OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The routing instance index.
Some BGP implementations permit the creation of
multiple instances of a BGP routing process. An
example includes RFC 2547 PE-CE routers.
Implementations that do not support multiple
routing instances should return 1 for this object.
XXX TODO - We need to provide a way to configure these
in the peer configuration table."
::= { bgpM2PeerEntry 1 }
bgpM2PeerIdentifier OBJECT-TYPE bgpM2PeerIdentifier OBJECT-TYPE
SYNTAX BgpM2Identifier SYNTAX BgpM2Identifier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BGP Identifier of this entry's remote BGP peer. "The BGP Identifier of this entry's remote BGP peer.
This entry should be 0.0.0.0 unless the bgpM2PeerState is This entry should be 0.0.0.0 unless the bgpM2PeerState is
in the OpenConfirm or the Established state." in the OpenConfirm or the Established state."
REFERENCE REFERENCE
"draft-ietf-idr-bgp4-17.txt, Sec. 4.2" "draft-ietf-idr-bgp4-17.txt, Sec. 4.2"
::= { bgpM2PeerEntry 1 } ::= { bgpM2PeerEntry 2 }
bgpM2PeerState OBJECT-TYPE bgpM2PeerState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
idle(1), idle(1),
connect(2), connect(2),
active(3), active(3),
opensent(4), opensent(4),
openconfirm(5), openconfirm(5),
established(6) established(6)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote BGP peer's FSM state." "The remote BGP peer's FSM state."
REFERENCE REFERENCE
"draft-ietf-idr-bgp4-17.txt, Sec. 8" "draft-ietf-idr-bgp4-17.txt, Sec. 8"
::= { bgpM2PeerEntry 2 } ::= { bgpM2PeerEntry 3 }
bgpM2PeerStatus OBJECT-TYPE bgpM2PeerStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
halted(1), halted(1),
running(2) running(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Whether or not the BGP FSM for this remote peer is halted "Whether or not the BGP FSM for this remote peer is halted
or running. The BGP FSM for a remote peer is halted after or running. The BGP FSM for a remote peer is halted after
processing a Stop event. Likewise, it is in the running processing a Stop event. Likewise, it is in the running
state after a Start event. state after a Start event.
The bgpM2PeerState will generally be in the idle state when The bgpM2PeerState will generally be in the idle state when
the FSM is halted, although some extensions such as the FSM is halted, although some extensions such as
Graceful Restart will leave the peer in the Idle state Graceful Restart will leave the peer in the Idle state
but with the FSM running." but with the FSM running."
::= { bgpM2PeerEntry 3 } ::= { bgpM2PeerEntry 4 }
bgpM2PeerConfiguredVersion OBJECT-TYPE bgpM2PeerConfiguredVersion OBJECT-TYPE
SYNTAX Unsigned32 (1..255) SYNTAX Unsigned32 (1..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The configured version to originally start with this "The configured version to originally start with this
remote peer. The BGP speaker may permit negotiation to a remote peer. The BGP speaker may permit negotiation to a
lower version number of the protocol." lower version number of the protocol."
::= { bgpM2PeerEntry 4 } ::= { bgpM2PeerEntry 5 }
bgpM2PeerNegotiatedVersion OBJECT-TYPE bgpM2PeerNegotiatedVersion OBJECT-TYPE
SYNTAX Unsigned32 (1..255) SYNTAX Unsigned32 (1..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The negotiated version of BGP running between the two "The negotiated version of BGP running between the two
peers." peers."
::= { bgpM2PeerEntry 5 } ::= { bgpM2PeerEntry 6 }
bgpM2PeerLocalAddrType OBJECT-TYPE bgpM2PeerLocalAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address family of the local end of the peering "The address family of the local end of the peering
session." session."
::= { bgpM2PeerEntry 6 } ::= { bgpM2PeerEntry 7 }
bgpM2PeerLocalAddr OBJECT-TYPE bgpM2PeerLocalAddr OBJECT-TYPE
SYNTAX InetAddress (SIZE(4..20)) SYNTAX InetAddress (SIZE(4..20))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address of the local end of the peering session." "The address of the local end of the peering session."
::= { bgpM2PeerEntry 7 } ::= { bgpM2PeerEntry 8 }
bgpM2PeerLocalPort OBJECT-TYPE bgpM2PeerLocalPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The local port for the TCP connection between the BGP "The local port for the TCP connection between the BGP
peers." peers."
::= { bgpM2PeerEntry 8 } ::= { bgpM2PeerEntry 9 }
bgpM2PeerLocalAs OBJECT-TYPE bgpM2PeerLocalAs OBJECT-TYPE
SYNTAX InetAutonomousSystemNumber SYNTAX InetAutonomousSystemNumber
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Some implementations of BGP can represent themselves "Some implementations of BGP can represent themselves
as multiple ASs. This is the AS that this peering as multiple ASs. This is the AS that this peering
session is representing itself as to the remote peer." session is representing itself as to the remote peer."
::= { bgpM2PeerEntry 9 } ::= { bgpM2PeerEntry 10 }
bgpM2PeerRemoteAddrType OBJECT-TYPE bgpM2PeerRemoteAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address family of the remote end of the peering "The address family of the remote end of the peering
session." session."
::= { bgpM2PeerEntry 10 } ::= { bgpM2PeerEntry 11 }
bgpM2PeerRemoteAddr OBJECT-TYPE bgpM2PeerRemoteAddr OBJECT-TYPE
SYNTAX InetAddress (SIZE(4..20)) SYNTAX InetAddress (SIZE(4..20))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address of the remote end of the peering session." "The address of the remote end of the peering session."
::= { bgpM2PeerEntry 11 } ::= { bgpM2PeerEntry 12 }
bgpM2PeerRemotePort OBJECT-TYPE bgpM2PeerRemotePort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote port for the TCP connection between the BGP "The remote port for the TCP connection between the BGP
peers. In the case of a transport for which the notion peers. In the case of a transport for which the notion
of 'port' is irrelevant, an instance value of -1 of 'port' is irrelevant, an instance value of -1
should be returned by the agent for this object. should be returned by the agent for this object.
skipping to change at page 27, line 4 skipping to change at page 25, line 39
should be returned by the agent for this object. should be returned by the agent for this object.
Note that the objects bgpM2PeerLocalAddr, Note that the objects bgpM2PeerLocalAddr,
bgpM2PeerLocalPort, bgpM2PeerRemoteAddr and bgpM2PeerLocalPort, bgpM2PeerRemoteAddr and
bgpM2PeerRemotePort provide the appropriate reference to bgpM2PeerRemotePort provide the appropriate reference to
the standard MIB TCP connection table. or even the ipv6 the standard MIB TCP connection table. or even the ipv6
TCP MIB as in rfc2452." TCP MIB as in rfc2452."
REFERENCE REFERENCE
"RFC 2012 - SNMPv2 Management Information Base for the "RFC 2012 - SNMPv2 Management Information Base for the
Transmission Control Protocol using SMIv2. Transmission Control Protocol using SMIv2.
RFC 2542 - IP Version 6 Management Information Base RFC 2542 - IP Version 6 Management Information Base
for the Transmission Control Protocol." for the Transmission Control Protocol."
::= { bgpM2PeerEntry 12 } ::= { bgpM2PeerEntry 13 }
bgpM2PeerRemoteAs OBJECT-TYPE bgpM2PeerRemoteAs OBJECT-TYPE
SYNTAX InetAutonomousSystemNumber SYNTAX InetAutonomousSystemNumber
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote autonomous system number." "The remote autonomous system number."
::= { bgpM2PeerEntry 13 } ::= { bgpM2PeerEntry 14 }
bgpM2PeerIndex OBJECT-TYPE bgpM2PeerIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value is a unique index for the remote peer entry "This value is a unique index for the remote peer entry
in the bgpM2PeerTable. It is assigned by the agent in the bgpM2PeerTable. It is assigned by the agent
at the point of creation of the bgpM2PeerTable row at the point of creation of the bgpM2PeerTable row
entry. While its value is guaranteed to be unique at entry. While its value is guaranteed to be unique at
skipping to change at page 27, line 46 skipping to change at page 26, line 35
a monotonically increasing number when a BGP FSM is a monotonically increasing number when a BGP FSM is
built to process the peering session. Values in the built to process the peering session. Values in the
bgpM2PeerTable and other tables utilizing bgpM2PeerIndex bgpM2PeerTable and other tables utilizing bgpM2PeerIndex
are expected to remain in existence for an arbitrary are expected to remain in existence for an arbitrary
time after the unconfigured peer has been deleted time after the unconfigured peer has been deleted
in order to allow management applications to extract in order to allow management applications to extract
useful management information for those peers. Thus, useful management information for those peers. Thus,
an unconfigured peer using the same indices as the an unconfigured peer using the same indices as the
bgpM2PeerTable that comes up while this row still bgpM2PeerTable that comes up while this row still
exists will re-utilize the same row." exists will re-utilize the same row."
::= { bgpM2PeerEntry 14 } ::= { bgpM2PeerEntry 15 }
-- --
-- Errors -- Errors
-- --
bgpM2PeerErrors bgpM2PeerErrors
OBJECT IDENTIFIER ::= { bgpM2Peer 2 } OBJECT IDENTIFIER ::= { bgpM2Peer 2 }
bgpM2PeerErrorsTable OBJECT-TYPE bgpM2PeerErrorsTable OBJECT-TYPE
SYNTAX SEQUENCE OF BgpM2PeerErrorsEntry SYNTAX SEQUENCE OF BgpM2PeerErrorsEntry
skipping to change at page 31, line 10 skipping to change at page 29, line 43
SYNTAX OCTET STRING (SIZE(0..4075)) SYNTAX OCTET STRING (SIZE(0..4075))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The last error code's data sent to this peer." "The last error code's data sent to this peer."
REFERENCE REFERENCE
"draft-ietf-idr-bgp4-15.txt, Sec. 4.5" "draft-ietf-idr-bgp4-15.txt, Sec. 4.5"
::= { bgpM2PeerErrorsEntry 8 } ::= { bgpM2PeerErrorsEntry 8 }
-- --
-- Peer Authentication
--
bgpM2PeerAuthentication
OBJECT IDENTIFIER ::= { bgpM2Peer 3 }
bgpM2PeerAuthTable OBJECT-TYPE
SYNTAX SEQUENCE OF BgpM2PeerAuthEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"BGP peer authentication table.
This table contains, one entry per BGP peer,
information about the authentication with BGP peers."
::= { bgpM2PeerAuthentication 1 }
bgpM2PeerAuthEntry OBJECT-TYPE
SYNTAX BgpM2PeerAuthEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entry containing information about the authentication
with a BGP peer."
AUGMENTS {
bgpM2PeerEntry
}
::= { bgpM2PeerAuthTable 1 }
BgpM2PeerAuthEntry ::= SEQUENCE {
bgpM2PeerAuthSent
TruthValue,
bgpM2PeerAuthSentCode
Unsigned32,
bgpM2PeerAuthSentValue
OCTET STRING,
bgpM2PeerAuthRcvd
TruthValue,
bgpM2PeerAuthRcvdCode
Unsigned32,
bgpM2PeerAuthRcvdValue
OCTET STRING
}
bgpM2PeerAuthSent OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The local peer has sent authentication information
to the remote peer in the BGP Authentication field."
::= { bgpM2PeerAuthEntry 1 }
bgpM2PeerAuthSentCode OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The code of the authentication information sent to
the remote peer."
::= { bgpM2PeerAuthEntry 2 }
bgpM2PeerAuthSentValue OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..252))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The payload of the authentication information
from the remote peer."
::= { bgpM2PeerAuthEntry 3 }
bgpM2PeerAuthRcvd OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The local peer has received authentication information
from the remote peer in the BGP Authentication field."
::= { bgpM2PeerAuthEntry 4 }
bgpM2PeerAuthRcvdCode OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The code of the authentication information received from
the remote peer."
::= { bgpM2PeerAuthEntry 5 }
bgpM2PeerAuthRcvdValue OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..252))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The payload of the authentication information from
the remote peer."
::= { bgpM2PeerAuthEntry 6 }
--
-- Peer Event Times -- Peer Event Times
-- --
bgpM2PeerTimers bgpM2PeerTimers
OBJECT IDENTIFIER ::= { bgpM2Peer 4 } OBJECT IDENTIFIER ::= { bgpM2Peer 3 }
bgpM2PeerEventTimesTable OBJECT-TYPE bgpM2PeerEventTimesTable OBJECT-TYPE
SYNTAX SEQUENCE OF BgpM2PeerEventTimesEntry SYNTAX SEQUENCE OF BgpM2PeerEventTimesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table reporting the per-peering session amount "A table reporting the per-peering session amount
of time elapsed and update events since the peering of time elapsed and update events since the peering
session advanced into the Established state." session advanced into the Established state."
::= { bgpM2PeerTimers 1 } ::= { bgpM2PeerTimers 1 }
skipping to change at page 39, line 4 skipping to change at page 35, line 23
the value of this object is zero (0), it indicates the value of this object is zero (0), it indicates
that the KeepAlive timer has not been established that the KeepAlive timer has not been established
with the peer, or, the value of with the peer, or, the value of
bgpM2PeerKeepAliveConfigured is zero (0). bgpM2PeerKeepAliveConfigured is zero (0).
This value is only defined when the peering session is This value is only defined when the peering session is
in the Established state." in the Established state."
REFERENCE REFERENCE
"draft-ietf-idr-bgp4-17, Sec. 4.4" "draft-ietf-idr-bgp4-17, Sec. 4.4"
::= { bgpM2PeerNegotiatedTimersEntry 2 } ::= { bgpM2PeerNegotiatedTimersEntry 2 }
-- --
-- Peer Capabilities -- Peer Capabilities
-- --
bgpM2PeerCapabilities bgpM2PeerCapabilities
OBJECT IDENTIFIER ::= { bgpM2Peer 5 } OBJECT IDENTIFIER ::= { bgpM2Peer 4 }
-- --
-- Announced Capabilities -- Announced Capabilities
-- --
bgpM2PeerCapsAnnouncedTable OBJECT-TYPE bgpM2PeerCapsAnnouncedTable OBJECT-TYPE
SYNTAX SEQUENCE OF BgpM2PeerCapsAnnouncedEntry SYNTAX SEQUENCE OF BgpM2PeerCapsAnnouncedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 44, line 31 skipping to change at page 41, line 4
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Entry containing information about a bgp-peers prefix "Entry containing information about a bgp-peers prefix
counters." counters."
INDEX { INDEX {
bgpM2PeerIndex, bgpM2PeerIndex,
bgpM2PrefixCountersAfi, bgpM2PrefixCountersAfi,
bgpM2PrefixCountersSafi bgpM2PrefixCountersSafi
} }
::= { bgpM2PrefixCountersTable 1 } ::= { bgpM2PrefixCountersTable 1 }
BgpM2PrefixCountersEntry ::= SEQUENCE { BgpM2PrefixCountersEntry ::= SEQUENCE {
bgpM2PrefixCountersAfi bgpM2PrefixCountersAfi
InetAddressType, BgpM2Afi,
bgpM2PrefixCountersSafi bgpM2PrefixCountersSafi
BgpM2Safi, BgpM2Safi,
bgpM2PrefixInPrefixes bgpM2PrefixInPrefixes
Gauge32, Gauge32,
bgpM2PrefixInPrefixesAccepted bgpM2PrefixInPrefixesAccepted
Gauge32, Gauge32,
bgpM2PrefixInPrefixesRejected bgpM2PrefixInPrefixesRejected
Gauge32, Gauge32,
bgpM2PrefixOutPrefixes bgpM2PrefixOutPrefixes
Gauge32 Gauge32
} }
bgpM2PrefixCountersAfi OBJECT-TYPE bgpM2PrefixCountersAfi OBJECT-TYPE
SYNTAX InetAddressType SYNTAX BgpM2Afi
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The AFI index of the per-peer, per prefix counters" "The AFI index of the per-peer, per prefix counters"
::= { bgpM2PrefixCountersEntry 1 } ::= { bgpM2PrefixCountersEntry 1 }
bgpM2PrefixCountersSafi OBJECT-TYPE bgpM2PrefixCountersSafi OBJECT-TYPE
SYNTAX BgpM2Safi SYNTAX BgpM2Safi
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 51, line 17 skipping to change at page 47, line 34
bgpM2CfgPeerLocalAddrType bgpM2CfgPeerLocalAddrType
InetAddressType, InetAddressType,
bgpM2CfgPeerLocalAddr bgpM2CfgPeerLocalAddr
InetAddress, InetAddress,
bgpM2CfgPeerLocalAs bgpM2CfgPeerLocalAs
InetAutonomousSystemNumber, InetAutonomousSystemNumber,
bgpM2CfgPeerRemoteAddrType bgpM2CfgPeerRemoteAddrType
InetAddressType, InetAddressType,
bgpM2CfgPeerRemoteAddr bgpM2CfgPeerRemoteAddr
InetAddress, InetAddress,
bgpM2CfgPeerRemotePort
Integer32,
bgpM2CfgPeerRemoteAs bgpM2CfgPeerRemoteAs
InetAutonomousSystemNumber, InetAutonomousSystemNumber,
bgpM2CfgPeerEntryStorageType bgpM2CfgPeerEntryStorageType
StorageType, StorageType,
bgpM2CfgPeerError bgpM2CfgPeerError
INTEGER, INTEGER,
bgpM2CfgPeerBgpPeerEntry bgpM2CfgPeerBgpPeerEntry
RowPointer, RowPointer,
bgpM2CfgPeerRowEntryStatus bgpM2CfgPeerRowEntryStatus
RowStatus, RowStatus,
skipping to change at page 53, line 19 skipping to change at page 49, line 34
bgpM2CfgPeerRemoteAddr OBJECT-TYPE bgpM2CfgPeerRemoteAddr OBJECT-TYPE
SYNTAX InetAddress (SIZE(4..20)) SYNTAX InetAddress (SIZE(4..20))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address of the remote end (destination address "The address of the remote end (destination address
of peer) for peering session." of peer) for peering session."
::= { bgpM2CfgPeerEntry 7 } ::= { bgpM2CfgPeerEntry 7 }
bgpM2CfgPeerRemotePort OBJECT-TYPE
SYNTAX Integer32 (-1 | 0..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This is the remote port for the transport connection
between the BGP peers. In the case of a transport for
which the notion of port is irrelevant, the value of
-1 can be defaulted or set."
DEFVAL { -1 }
::= { bgpM2CfgPeerEntry 8 }
bgpM2CfgPeerRemoteAs OBJECT-TYPE bgpM2CfgPeerRemoteAs OBJECT-TYPE
SYNTAX InetAutonomousSystemNumber SYNTAX InetAutonomousSystemNumber
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Autonomous system number of the remote peer." "Autonomous system number of the remote peer."
::= { bgpM2CfgPeerEntry 9 } ::= { bgpM2CfgPeerEntry 8 }
bgpM2CfgPeerEntryStorageType OBJECT-TYPE bgpM2CfgPeerEntryStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object type specifies the intended storage "This object type specifies the intended storage
type for the bgpM2CfgPeerEntry row instance." type for the bgpM2CfgPeerEntry row instance."
::= { bgpM2CfgPeerEntry 10 } ::= { bgpM2CfgPeerEntry 9 }
bgpM2CfgPeerError OBJECT-TYPE bgpM2CfgPeerError OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(0), unknown(0),
notActivated (1), notActivated (1),
errDuplicatePeeringSession (2), errDuplicatePeeringSession (2),
activated (3) activated (3)
-- +++wayne more to follow -- +++wayne more to follow
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 54, line 27 skipping to change at page 50, line 30
If this row is still under creation (has not been activated If this row is still under creation (has not been activated
bgpM2CfgPeerRowEntryStatus), then this instance will be set to bgpM2CfgPeerRowEntryStatus), then this instance will be set to
not-activated (1). not-activated (1).
At the point that the row is activated, bgpM2CfgPeerError At the point that the row is activated, bgpM2CfgPeerError
will reflect the error status of the row data itself. If will reflect the error status of the row data itself. If
there is another session already activated with the same there is another session already activated with the same
local and remote addresses as denoted by local and remote addresses as denoted by
{bgpM2CfgPeerLocalAddrType, bgpM2CfgPeerLocalAddr, {bgpM2CfgPeerLocalAddrType, bgpM2CfgPeerLocalAddr,
bgpM2CfgPeerRemoteAddr, bgpM2CfgPeerRemotePort}, then bgpM2CfgPeerRemoteAddr}, then
the value of this will be set to the value of this will be set to
err-duplicate-peering-session (2). err-duplicate-peering-session (2).
If this row is associated with a peer session whose If this row is associated with a peer session whose
initialization has been attempted, the value will be initialization has been attempted, the value will be
set to activated (3) (and, bgpM2PeerCfgPeerEntry will set to activated (3) (and, bgpM2PeerCfgPeerEntry will
be set to the row instance of the entry in the be set to the row instance of the entry in the
bgpM2PeerTable which reflects the state of the peering bgpM2PeerTable which reflects the state of the peering
session). session).
Note that this object only reflects the error as a Note that this object only reflects the error as a
function of the attempted activation of this row as function of the attempted activation of this row as
containing data for a bgp peering session. The actual containing data for a bgp peering session. The actual
state of the session at the point of any protocol exchange state of the session at the point of any protocol exchange
or session state machine initiation is reflected in the or session state machine initiation is reflected in the
bgpM2PeerTable row instance (as reflected through bgpM2PeerTable row instance (as reflected through
bgpM2CfgPeerPeerEntry) associated with this row instance." bgpM2CfgPeerPeerEntry) associated with this row instance."
::= { bgpM2CfgPeerEntry 11 } ::= { bgpM2CfgPeerEntry 10 }
bgpM2CfgPeerBgpPeerEntry OBJECT-TYPE bgpM2CfgPeerBgpPeerEntry OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Upon activation of the session data contained in this "Upon activation of the session data contained in this
row instance, this object points to an instance of a row row instance, this object points to an instance of a row
within the bgpM2PeerTable reflecting the session in its within the bgpM2PeerTable reflecting the session in its
initializing or operational state. Retrieval of this initializing or operational state. Retrieval of this
column instance will always yield a value of {0.0} unless column instance will always yield a value of {0.0} unless
the session has successfully been activated (via the session has successfully been activated (via
bgpM2CfgPeerRowEntryStatus). Such row instances will always bgpM2CfgPeerRowEntryStatus). Such row instances will always
have a value of bgpM2CfgPeerError which is activated (3)." have a value of bgpM2CfgPeerError which is activated (3)."
::= { bgpM2CfgPeerEntry 12 } ::= { bgpM2CfgPeerEntry 11 }
bgpM2CfgPeerRowEntryStatus OBJECT-TYPE bgpM2CfgPeerRowEntryStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object type is used to control creation, "This object type is used to control creation,
activation, and deletion of this row instance." activation, and deletion of this row instance."
-- +++wayne need better directions for agent auto-removal -- +++wayne need better directions for agent auto-removal
-- of row instances which have moved to active or error -- of row instances which have moved to active or error
-- state -- state
::= { bgpM2CfgPeerEntry 13 } ::= { bgpM2CfgPeerEntry 12 }
bgpM2CfgPeerIndex OBJECT-TYPE bgpM2CfgPeerIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Uniquely identifies an instance of a peer row, as "Uniquely identifies an instance of a peer row, as
an element of configuration." an element of configuration."
::= { bgpM2CfgPeerEntry 14 } ::= { bgpM2CfgPeerEntry 13 }
bgpM2CfgPeerStatus OBJECT-TYPE bgpM2CfgPeerStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
halted(1), halted(1),
running(2) running(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This specifies the state of the peering session upon "This specifies the state of the peering session upon
activation. If disabled, the FSM is in the halted activation. If disabled, the FSM is in the halted
state and no Automatic Start events are generated. state and no Automatic Start events are generated.
If enabled, the FSM is in the running state and If enabled, the FSM is in the running state and
Automatic Start events may be generated." Automatic Start events may be generated."
::= { bgpM2CfgPeerEntry 15 } ::= { bgpM2CfgPeerEntry 14 }
--
-- Per-peer authentication table.
--
bgpM2CfgPeerAuthTable OBJECT-TYPE
SYNTAX SEQUENCE OF BgpM2CfgPeerAuthEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table contain per peer configuration for BGP Authentication."
::= { bgpM2PeerConfiguration 4 }
bgpM2CfgPeerAuthEntry OBJECT-TYPE
SYNTAX BgpM2CfgPeerAuthEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entry containing information about a peer's BGP Authentication
configuration."
AUGMENTS {
bgpM2CfgPeerEntry
}
::= { bgpM2CfgPeerAuthTable 1 }
BgpM2CfgPeerAuthEntry ::= SEQUENCE {
bgpM2CfgPeerAuthEnabled
TruthValue,
bgpM2CfgPeerAuthCode
Unsigned32,
bgpM2CfgPeerAuthValue
OCTET STRING
}
bgpM2CfgPeerAuthEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This value is true if BGP Authentication is enabled for
this peer. This is the authentication mechanism
documented in the base BGP specification, not the MD5
session protection mechanism."
DEFVAL {
false
}
::= { bgpM2CfgPeerAuthEntry 1 }
bgpM2CfgPeerAuthCode OBJECT-TYPE
SYNTAX Unsigned32(0..255)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The authentication code for the BGP Authentication
mechanism."
REFERENCE
"draft-ietf-idr-bgp4-17.txt, Sec. 4.1.a"
::= { bgpM2CfgPeerAuthEntry 2 }
bgpM2CfgPeerAuthValue OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..252))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The authentication payload for the BGP authentication
mechanism. This value has semantic meaning within
the context of the authentication code."
REFERENCE
"draft-ietf-idr-bgp4-17.txt, Sec. 4.1.a"
::= { bgpM2CfgPeerAuthEntry 3 }
-- --
-- Per-peer timers table -- Per-peer timers table
-- --
bgpM2CfgPeerTimersTable OBJECT-TYPE bgpM2CfgPeerTimersTable OBJECT-TYPE
SYNTAX SEQUENCE OF BgpM2CfgPeerTimersEntry SYNTAX SEQUENCE OF BgpM2CfgPeerTimersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table for configuration of per-peer timers." "Table for configuration of per-peer timers."
::= { bgpM2PeerConfiguration 5 } ::= { bgpM2PeerConfiguration 4 }
bgpM2CfgPeerTimersEntry OBJECT-TYPE bgpM2CfgPeerTimersEntry OBJECT-TYPE
SYNTAX BgpM2CfgPeerTimersEntry SYNTAX BgpM2CfgPeerTimersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Entry containing per-peer timer configuration." "Entry containing per-peer timer configuration."
AUGMENTS { AUGMENTS {
bgpM2CfgPeerEntry bgpM2CfgPeerEntry
} }
skipping to change at page 60, line 26 skipping to change at page 55, line 4
DEFVAL { DEFVAL {
30 30
} }
::= { bgpM2CfgPeerTimersEntry 5 } ::= { bgpM2CfgPeerTimersEntry 5 }
-- --
-- Per-peer configuration extensions -- Per-peer configuration extensions
-- --
bgpM2CfgPeerExtensions bgpM2CfgPeerExtensions
OBJECT IDENTIFIER ::= { bgpM2PeerConfiguration 6 } OBJECT IDENTIFIER ::= { bgpM2PeerConfiguration 5 }
bgpM2CfgPeerNonCapExts bgpM2CfgPeerNonCapExts
OBJECT IDENTIFIER ::= { bgpM2CfgPeerExtensions 1 } OBJECT IDENTIFIER ::= { bgpM2CfgPeerExtensions 1 }
bgpM2CfgPeerCapExts bgpM2CfgPeerCapExts
OBJECT IDENTIFIER ::= { bgpM2CfgPeerExtensions 2 } OBJECT IDENTIFIER ::= { bgpM2CfgPeerExtensions 2 }
-- --
-- Peer route reflection configuration -- Peer route reflection configuration
-- --
skipping to change at page 64, line 11 skipping to change at page 58, line 34
bgpM2NlriPrefix, bgpM2NlriPrefix,
bgpM2NlriPrefixLen, bgpM2NlriPrefixLen,
bgpM2NlriIndex bgpM2NlriIndex
} }
::= { bgpM2NlriTable 1 } ::= { bgpM2NlriTable 1 }
BgpM2NlriEntry ::= SEQUENCE { BgpM2NlriEntry ::= SEQUENCE {
bgpM2NlriIndex bgpM2NlriIndex
Unsigned32, Unsigned32,
bgpM2NlriAfi bgpM2NlriAfi
InetAddressType, BgpM2Afi,
bgpM2NlriSafi bgpM2NlriSafi
BgpM2Safi, BgpM2Safi,
bgpM2NlriPrefixType
InetAddressType,
bgpM2NlriPrefix bgpM2NlriPrefix
InetAddress, InetAddress,
bgpM2NlriPrefixLen bgpM2NlriPrefixLen
InetAddressPrefixLength, InetAddressPrefixLength,
bgpM2NlriBest bgpM2NlriBest
TruthValue, TruthValue,
bgpM2NlriCalcLocalPref bgpM2NlriCalcLocalPref
Unsigned32, Unsigned32,
bgpM2PathAttrIndex bgpM2PathAttrIndex
Unsigned32, Unsigned32,
skipping to change at page 65, line 4 skipping to change at page 59, line 28
send more than a single route instance. send more than a single route instance.
2. Allow for extensions which extend the NLRI field 2. Allow for extensions which extend the NLRI field
to send the same prefix while utilizing other to send the same prefix while utilizing other
extension specific information. An example of extension specific information. An example of
this is RFC 3107 - Carrying MPLS labels in BGP." this is RFC 3107 - Carrying MPLS labels in BGP."
REFERENCE REFERENCE
"RFC 3107 - Carrying Label Information in BGP-4" "RFC 3107 - Carrying Label Information in BGP-4"
::= { bgpM2NlriEntry 1 } ::= { bgpM2NlriEntry 1 }
bgpM2NlriAfi OBJECT-TYPE bgpM2NlriAfi OBJECT-TYPE
SYNTAX InetAddressType SYNTAX BgpM2Afi
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address family of the prefix for this NLRI." "The address family of the prefix for this NLRI."
::= { bgpM2NlriEntry 2 } ::= { bgpM2NlriEntry 2 }
bgpM2NlriSafi OBJECT-TYPE bgpM2NlriSafi OBJECT-TYPE
SYNTAX BgpM2Safi SYNTAX BgpM2Safi
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subsequent address family of the prefix for "The subsequent address family of the prefix for
this NLRI" this NLRI"
REFERENCE REFERENCE
"RFC 2858 - Multiprotocol Extensions for BGP-4" "RFC 2858 - Multiprotocol Extensions for BGP-4"
::= { bgpM2NlriEntry 3 } ::= { bgpM2NlriEntry 3 }
bgpM2NlriPrefixType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of the IP address prefix in the
Network Layer Reachability Information field.
The value of this object is derived from the
appropriate value from the bgpM2NlriAfi field.
Where an appropriate InetAddressType is not
available, the value of the object must be
unknown(0).
XXX TODO - This seems like a hack."
::= { bgpM2NlriEntry 4 }
bgpM2NlriPrefix OBJECT-TYPE bgpM2NlriPrefix OBJECT-TYPE
SYNTAX InetAddress (SIZE (4..20)) SYNTAX InetAddress (SIZE (4..20))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An IP address prefix in the Network Layer "An IP address prefix in the Network Layer
Reachability Information field. This object Reachability Information field. This object
is an IP address containing the prefix with is an IP address containing the prefix with
length specified by length specified by
bgpM2PathAttrAddrPrefixLen. bgpM2PathAttrAddrPrefixLen.
Any bits beyond the length specified by Any bits beyond the length specified by
bgpM2PathAttrAddrPrefixLen are zeroed." bgpM2PathAttrAddrPrefixLen are zeroed."
::= { bgpM2NlriEntry 4 } ::= { bgpM2NlriEntry 5 }
bgpM2NlriPrefixLen OBJECT-TYPE bgpM2NlriPrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Length in bits of the address prefix in "Length in bits of the address prefix in
the Network Layer Reachability Information field." the Network Layer Reachability Information field."
::= { bgpM2NlriEntry 5 } ::= { bgpM2NlriEntry 6 }
bgpM2NlriBest OBJECT-TYPE bgpM2NlriBest OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of whether or not this route "An indication of whether or not this route
was chosen as the best BGP4 route." was chosen as the best BGP4 route."
::= { bgpM2NlriEntry 6 } ::= { bgpM2NlriEntry 7 }
bgpM2NlriCalcLocalPref OBJECT-TYPE bgpM2NlriCalcLocalPref OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The degree of preference calculated by the "The degree of preference calculated by the
receiving BGP4 speaker for an advertised receiving BGP4 speaker for an advertised
route." route."
::= { bgpM2NlriEntry 7 } ::= { bgpM2NlriEntry 8 }
bgpM2PathAttrIndex OBJECT-TYPE bgpM2PathAttrIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value is a unique index for the per-NLRI entry "This value is a unique index for the per-NLRI entry
in the bgpM2PeerAttrTable. It is assigned by the in the bgpM2PathAttrTable. It is assigned by the
agent at the point of creation of the bgpM2PeerAttrTable agent at the point of creation of the bgpM2PathAttrTable
row entry. While its value is guaranteed to be unique row entry. While its value is guaranteed to be unique
at any time, it is otherwise opaque to the management at any time, it is otherwise opaque to the management
application with respect to its value or the contiguity application with respect to its value or the contiguity
of bgpM2PeerAttrIndex row instance values across rows of bgpM2PathAttrIndex row instance values across rows
of the bgpM2PeerAttrTable. It is used to provide an of the bgpM2PeerAttrTable. It is used to provide an
index structure for other tables whose data is logically index structure for other tables whose data is logically
per-peer, per-NLRI." per-peer, per-NLRI."
::= { bgpM2NlriEntry 8 } ::= { bgpM2NlriEntry 9 }
bgpM2NlriOpaqueType OBJECT-TYPE bgpM2NlriOpaqueType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
none(0), none(0),
bgpMplsLabelStack(1) bgpMplsLabelStack(1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object enumerates the type of the row that is "This object enumerates the type of the row that is
skipping to change at page 67, line 13 skipping to change at page 62, line 6
a zero length. bgpM2NlriOpaqueType is necessary since a zero length. bgpM2NlriOpaqueType is necessary since
the data referenced by bgpM2NlriOpaquePointer is the data referenced by bgpM2NlriOpaquePointer is
opaque to BGP. For example, in the case of RFC 3107, opaque to BGP. For example, in the case of RFC 3107,
the label stack that is pointed to may occur in the the label stack that is pointed to may occur in the
mplsLabelStackTable from the MPLS-LSR-MIB, and the mplsLabelStackTable from the MPLS-LSR-MIB, and the
instance value of bgpM2NlriOpaqueType would be instance value of bgpM2NlriOpaqueType would be
bgpMplsLabelStack(1)." bgpMplsLabelStack(1)."
REFERENCE REFERENCE
"RFC 3107 - Carrying Label Information in BGP-4 "RFC 3107 - Carrying Label Information in BGP-4
draft-ietf-mpls-lsr-mib-08.txt" draft-ietf-mpls-lsr-mib-08.txt"
::= { bgpM2NlriEntry 9 } ::= { bgpM2NlriEntry 10 }
bgpM2NlriOpaquePointer OBJECT-TYPE bgpM2NlriOpaquePointer OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Pointer to a row that decomposes the data that is "Pointer to a row that decomposes the data that is
opaque to the BGP MIB but is sent in the NLRI. opaque to the BGP MIB but is sent in the NLRI.
This RowPointer has zero (0) length data instance This RowPointer has zero (0) length data instance
if bgpM2NlriOpaqueType is none." if bgpM2NlriOpaqueType is none."
::= { bgpM2NlriEntry 10 } ::= { bgpM2NlriEntry 11 }
-- --
-- Adj-Ribs-Out Table -- Adj-Ribs-Out Table
-- --
bgpM2AdjRibsOutTable OBJECT-TYPE bgpM2AdjRibsOutTable OBJECT-TYPE
SYNTAX SEQUENCE OF BgpM2AdjRibsOutEntry SYNTAX SEQUENCE OF BgpM2AdjRibsOutEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 77, line 18 skipping to change at page 72, line 13
bgpM2AsPathTableEntry OBJECT-TYPE bgpM2AsPathTableEntry OBJECT-TYPE
SYNTAX BgpM2AsPathEntry SYNTAX BgpM2AsPathEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about an AS path provided with a path to "Information about an AS path provided with a path to
a network." a network."
INDEX { INDEX {
bgpM2PathAttrIndex, bgpM2PathAttrIndex,
bgpM2AsPathSegmentIndex, bgpM2AsPathSegmentIndex,
bgpM2AsPathElementIndex, bgpM2AsPathElementIndex
bgpM2AsPathElementValue
} }
::= { bgpM2AsPathTable 1 } ::= { bgpM2AsPathTable 1 }
BgpM2AsPathEntry ::= SEQUENCE { BgpM2AsPathEntry ::= SEQUENCE {
bgpM2AsPathSegmentIndex bgpM2AsPathSegmentIndex
Unsigned32, Unsigned32,
bgpM2AsPathElementIndex bgpM2AsPathElementIndex
Unsigned32, Unsigned32,
bgpM2AsPathType bgpM2AsPathType
INTEGER, INTEGER,
skipping to change at page 88, line 41 skipping to change at page 83, line 35
bgpM2As4byteGroup, bgpM2As4byteGroup,
bgpM2BaseGroup, bgpM2BaseGroup,
bgpM2ErrorsGroup, bgpM2ErrorsGroup,
bgpM2PeerGroup, bgpM2PeerGroup,
bgpM2PathAttributesGroup bgpM2PathAttributesGroup
} }
GROUP bgpM2MIBNotificationsGroup GROUP bgpM2MIBNotificationsGroup
DESCRIPTION DESCRIPTION
"The notifications group is completely optional, "The notifications group is completely optional,
but highly recommended." but highly recommended."
GROUP bgpM2AuthenticationGroup
DESCRIPTION
"The authentication group is
mandatory only for those implementations which
support sending and receiving authentication
information with peers in the BGP Authentication
Field."
GROUP bgpM2CommunitiesGroup GROUP bgpM2CommunitiesGroup
DESCRIPTION DESCRIPTION
"The communities group is mandatory only for those "The communities group is mandatory only for those
which support the BGP community attribute." which support the BGP community attribute."
GROUP bgpM2ExtCommunitiesGroup GROUP bgpM2ExtCommunitiesGroup
DESCRIPTION DESCRIPTION
"The communities group is mandatory only for those "The communities group is mandatory only for those
which support the BGP extended community attribute." which support the BGP extended community attribute."
GROUP bgpM2RouteReflectionGroup GROUP bgpM2RouteReflectionGroup
DESCRIPTION DESCRIPTION
skipping to change at page 89, line 51 skipping to change at page 84, line 37
GROUP bgpM2PeerGroup GROUP bgpM2PeerGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for all agent implementations." "This group is mandatory for all agent implementations."
GROUP bgpM2PathAttributesGroup GROUP bgpM2PathAttributesGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for all agent implementations." "This group is mandatory for all agent implementations."
GROUP bgpM2PeerConfigurationGroup GROUP bgpM2PeerConfigurationGroup
DESCRIPTION DESCRIPTION
"This group is optional for implementations that wish to "This group is optional for implementations that wish to
support configuration via SNMP." support configuration via SNMP."
GROUP bgpM2PeerAuthConfigurationGroup
DESCRIPTION
"This group is optional for implementations that wish to
support configuration of BGP authentication via SNMP.
Implementation of this feature requires support of the
bgpM2PeerConfigurationGroup."
GROUP bgpM2PeerRouteReflectorCfgGroup GROUP bgpM2PeerRouteReflectorCfgGroup
DESCRIPTION DESCRIPTION
"This group is optional for implementations that wish to "This group is optional for implementations that wish to
support configuration of route reflection via SNMP. support configuration of route reflection via SNMP.
Implementation of this feature requires support of the Implementation of this feature requires support of the
bgpM2PeerConfigurationGroup." bgpM2PeerConfigurationGroup."
GROUP bgpM2PeerAsConfederationCfgGroup GROUP bgpM2PeerAsConfederationCfgGroup
DESCRIPTION DESCRIPTION
"This group is optional for implementations that wish to "This group is optional for implementations that wish to
support configuration of BGP AS Confederations via SNMP. support configuration of BGP AS Confederations via SNMP.
Implementation of this feature requires support of the Implementation of this feature requires support of the
bgpM2PeerConfigurationGroup." bgpM2PeerConfigurationGroup."
GROUP bgpM2Rfc2545Group GROUP bgpM2Rfc2545Group
DESCRIPTION DESCRIPTION
"This group is required for peers that support exchanging "This group is required for peers that support exchanging
of IPv6 NLRI per RFC 2545." of IPv6 NLRI per RFC 2545."
::= { bgpM2MIBCompliances 1 } ::= { bgpM2MIBCompliances 1 }
bgpM2AuthenticationGroup OBJECT-GROUP
OBJECTS {
bgpM2SupportedAuthCode,
bgpM2SupportedAuthValue,
bgpM2PeerAuthSent,
bgpM2PeerAuthSentCode,
bgpM2PeerAuthSentValue,
bgpM2PeerAuthRcvd,
bgpM2PeerAuthRcvdCode,
bgpM2PeerAuthRcvdValue
}
STATUS current
DESCRIPTION
"Objects associated with BGP authentication."
::= { bgpM2MIBGroups 1 }
bgpM2CommunitiesGroup OBJECT-GROUP bgpM2CommunitiesGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bgpM2PathAttrCommIndex, bgpM2PathAttrCommIndex,
bgpM2PathAttrCommValue bgpM2PathAttrCommValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects associated with BGP communities." "Objects associated with BGP communities."
::= { bgpM2MIBGroups 2 } ::= { bgpM2MIBGroups 1 }
bgpM2ExtCommunitiesGroup OBJECT-GROUP bgpM2ExtCommunitiesGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bgpM2PathAttrExtCommIndex, bgpM2PathAttrExtCommIndex,
bgpM2PathAttrExtCommValue bgpM2PathAttrExtCommValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects associated with BGP extended communities." "Objects associated with BGP extended communities."
::= { bgpM2MIBGroups 3 } ::= { bgpM2MIBGroups 2 }
bgpM2RouteReflectionGroup OBJECT-GROUP bgpM2RouteReflectionGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bgpM2RouteReflector, bgpM2RouteReflector,
bgpM2ClusterId, bgpM2ClusterId,
bgpM2PeerReflectorClient, bgpM2PeerReflectorClient,
bgpM2PathAttrOriginatorId, bgpM2PathAttrOriginatorId,
bgpM2PathAttrClusterIndex, bgpM2PathAttrClusterIndex,
bgpM2PathAttrClusterValue bgpM2PathAttrClusterValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects associated with BGP route reflection." "Objects associated with BGP route reflection."
::= { bgpM2MIBGroups 4 } ::= { bgpM2MIBGroups 3 }
bgpM2AsConfederationGroup OBJECT-GROUP bgpM2AsConfederationGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bgpM2ConfederationRouter, bgpM2ConfederationRouter,
bgpM2ConfederationId, bgpM2ConfederationId,
bgpM2PeerConfedMember bgpM2PeerConfedMember
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects associated with BGP confederation membership." "Objects associated with BGP confederation membership."
::= { bgpM2MIBGroups 5 } ::= { bgpM2MIBGroups 4 }
bgpM2TimersGroup OBJECT-GROUP bgpM2TimersGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bgpM2PeerFsmEstablishedTime, bgpM2PeerFsmEstablishedTime,
bgpM2PeerInUpdatesElapsedTime, bgpM2PeerInUpdatesElapsedTime,
bgpM2PeerConnectRetryInterval, bgpM2PeerConnectRetryInterval,
bgpM2PeerHoldTimeConfigured, bgpM2PeerHoldTimeConfigured,
bgpM2PeerKeepAliveConfigured, bgpM2PeerKeepAliveConfigured,
bgpM2PeerMinASOrigInterval, bgpM2PeerMinASOrigInterval,
bgpM2PeerMinRouteAdverInterval, bgpM2PeerMinRouteAdverInterval,
bgpM2PeerHoldTime, bgpM2PeerHoldTime,
bgpM2PeerKeepAlive bgpM2PeerKeepAlive
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects associated with BGP peering timers." "Objects associated with BGP peering timers."
::= { bgpM2MIBGroups 6 } ::= { bgpM2MIBGroups 5 }
bgpM2CountersGroup OBJECT-GROUP bgpM2CountersGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bgpM2PeerInUpdates, bgpM2PeerInUpdates,
bgpM2PeerOutUpdates, bgpM2PeerOutUpdates,
bgpM2PeerInTotalMessages, bgpM2PeerInTotalMessages,
bgpM2PeerOutTotalMessages, bgpM2PeerOutTotalMessages,
bgpM2PeerFsmEstablishedTrans, bgpM2PeerFsmEstablishedTrans,
bgpM2PrefixCountersAfi, bgpM2PrefixCountersAfi,
bgpM2PrefixCountersSafi, bgpM2PrefixCountersSafi,
bgpM2PrefixInPrefixes, bgpM2PrefixInPrefixes,
bgpM2PrefixInPrefixesAccepted, bgpM2PrefixInPrefixesAccepted,
bgpM2PrefixInPrefixesRejected, bgpM2PrefixInPrefixesRejected,
bgpM2PrefixOutPrefixes bgpM2PrefixOutPrefixes
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects to count discrete events and exchanges on BGP "Objects to count discrete events and exchanges on BGP
sessions." sessions."
::= { bgpM2MIBGroups 7 } ::= { bgpM2MIBGroups 6 }
bgpM2CapabilitiesGroup OBJECT-GROUP bgpM2CapabilitiesGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bgpM2CapabilitySupportAvailable, bgpM2CapabilitySupportAvailable,
bgpM2SupportedCapabilityCode, bgpM2SupportedCapabilityCode,
bgpM2SupportedCapability, bgpM2SupportedCapability,
bgpM2PeerCapAnnouncedCode, bgpM2PeerCapAnnouncedCode,
bgpM2PeerCapAnnouncedIndex, bgpM2PeerCapAnnouncedIndex,
bgpM2PeerCapAnnouncedValue, bgpM2PeerCapAnnouncedValue,
bgpM2PeerCapReceivedCode, bgpM2PeerCapReceivedCode,
bgpM2PeerCapReceivedIndex, bgpM2PeerCapReceivedIndex,
bgpM2PeerCapReceivedValue bgpM2PeerCapReceivedValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects to report capabilities as received on BGP "Objects to report capabilities as received on BGP
sessions." sessions."
::= { bgpM2MIBGroups 8 } ::= { bgpM2MIBGroups 7 }
bgpM2AsPathGroup OBJECT-GROUP bgpM2AsPathGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bgpM2AsPathSegmentIndex, bgpM2AsPathSegmentIndex,
bgpM2AsPathElementIndex, bgpM2AsPathElementIndex,
bgpM2AsPathType, bgpM2AsPathType,
bgpM2AsPathElementValue bgpM2AsPathElementValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects to report AS paths received on BGP NLRIs." "Objects to report AS paths received on BGP NLRIs."
::= { bgpM2MIBGroups 9 } ::= { bgpM2MIBGroups 8 }
bgpM2As4byteGroup OBJECT-GROUP bgpM2As4byteGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bgpM2AsSize, bgpM2AsSize,
bgpM2AsPath4bytePathPresent, bgpM2AsPath4bytePathPresent,
bgpM2AsPath4byteAggregatorAS, bgpM2AsPath4byteAggregatorAS,
bgpM2AsPath4byteCalcLength, bgpM2AsPath4byteCalcLength,
bgpM2AsPath4byteString, bgpM2AsPath4byteString,
bgpM2AsPath4byteIndex bgpM2AsPath4byteIndex
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"AS Size objects." "AS Size objects."
::= { bgpM2MIBGroups 10 } ::= { bgpM2MIBGroups 9 }
bgpM2BaseGroup OBJECT-GROUP bgpM2BaseGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bgpM2LocalAs, bgpM2LocalAs,
bgpM2LocalIdentifier, bgpM2LocalIdentifier,
bgpM2VersionIndex, bgpM2VersionIndex,
bgpM2VersionSupported bgpM2VersionSupported
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Basic objects in local BGP implementation." "Basic objects in local BGP implementation."
::= { bgpM2MIBGroups 11 } ::= { bgpM2MIBGroups 10 }
bgpM2ErrorsGroup OBJECT-GROUP bgpM2ErrorsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bgpM2PeerLastErrorReceived, bgpM2PeerLastErrorReceived,
bgpM2PeerLastErrorReceivedData, bgpM2PeerLastErrorReceivedData,
bgpM2PeerLastErrorReceivedTime, bgpM2PeerLastErrorReceivedTime,
bgpM2PeerLastErrorReceivedText, bgpM2PeerLastErrorReceivedText,
bgpM2PeerLastErrorSent, bgpM2PeerLastErrorSent,
bgpM2PeerLastErrorSentData, bgpM2PeerLastErrorSentData,
bgpM2PeerLastErrorSentTime, bgpM2PeerLastErrorSentTime,
bgpM2PeerLastErrorSentText bgpM2PeerLastErrorSentText
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Errors received on BGP peering sessions." "Errors received on BGP peering sessions."
::= { bgpM2MIBGroups 12 } ::= { bgpM2MIBGroups 11 }
bgpM2PeerGroup OBJECT-GROUP bgpM2PeerGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bgpM2PeerInstance,
bgpM2PeerIdentifier, bgpM2PeerIdentifier,
bgpM2PeerState, bgpM2PeerState,
bgpM2PeerStatus, bgpM2PeerStatus,
bgpM2PeerConfiguredVersion, bgpM2PeerConfiguredVersion,
bgpM2PeerNegotiatedVersion, bgpM2PeerNegotiatedVersion,
bgpM2PeerLocalAddrType, bgpM2PeerLocalAddrType,
bgpM2PeerLocalAddr, bgpM2PeerLocalAddr,
bgpM2PeerLocalPort, bgpM2PeerLocalPort,
bgpM2PeerLocalAs, bgpM2PeerLocalAs,
bgpM2PeerRemoteAddrType, bgpM2PeerRemoteAddrType,
bgpM2PeerRemoteAddr, bgpM2PeerRemoteAddr,
bgpM2PeerRemotePort, bgpM2PeerRemotePort,
bgpM2PeerRemoteAs, bgpM2PeerRemoteAs,
bgpM2PeerIndex bgpM2PeerIndex
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Core object types on BGP peering sessions." "Core object types on BGP peering sessions."
::= { bgpM2MIBGroups 13 } ::= { bgpM2MIBGroups 12 }
bgpM2PathAttributesGroup OBJECT-GROUP bgpM2PathAttributesGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bgpM2PathAttrCount, bgpM2PathAttrCount,
bgpM2AsPathCalcLength, bgpM2AsPathCalcLength,
bgpM2AsPathElementValue, bgpM2AsPathElementValue,
bgpM2AsPathIndex, bgpM2AsPathIndex,
bgpM2AsPathString, bgpM2AsPathString,
bgpM2AsPathType, bgpM2AsPathType,
bgpM2NlriAfi, bgpM2NlriAfi,
bgpM2NlriBest, bgpM2NlriBest,
bgpM2NlriPrefixType,
bgpM2NlriPrefix, bgpM2NlriPrefix,
bgpM2NlriPrefixLen, bgpM2NlriPrefixLen,
bgpM2NlriSafi, bgpM2NlriSafi,
bgpM2NlriOpaqueType, bgpM2NlriOpaqueType,
bgpM2NlriOpaquePointer, bgpM2NlriOpaquePointer,
bgpM2NlriIndex, bgpM2NlriIndex,
bgpM2NlriCalcLocalPref, bgpM2NlriCalcLocalPref,
bgpM2AdjRibsOutIndex, bgpM2AdjRibsOutIndex,
bgpM2AdjRibsOutRoute, bgpM2AdjRibsOutRoute,
bgpM2PathAttrAggregatorAS, bgpM2PathAttrAggregatorAS,
skipping to change at page 95, line 30 skipping to change at page 89, line 42
bgpM2PathAttrNextHop, bgpM2PathAttrNextHop,
bgpM2PathAttrNextHopAddrType, bgpM2PathAttrNextHopAddrType,
bgpM2PathAttrOrigin, bgpM2PathAttrOrigin,
bgpM2PathAttrUnknownIndex, bgpM2PathAttrUnknownIndex,
bgpM2PathAttrUnknownType, bgpM2PathAttrUnknownType,
bgpM2PathAttrUnknownValue bgpM2PathAttrUnknownValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Attributes received on BGP peering sessions." "Attributes received on BGP peering sessions."
::= { bgpM2MIBGroups 14 } ::= { bgpM2MIBGroups 13 }
bgpM2PeerConfigurationGroup OBJECT-GROUP bgpM2PeerConfigurationGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bgpM2CfgBaseScalarStorageType, bgpM2CfgBaseScalarStorageType,
bgpM2CfgLocalAs, bgpM2CfgLocalAs,
bgpM2CfgLocalIdentifier, bgpM2CfgLocalIdentifier,
bgpM2CfgPeerAdminStatus, bgpM2CfgPeerAdminStatus,
bgpM2CfgPeerNextIndex, bgpM2CfgPeerNextIndex,
bgpM2CfgPeerConfiguredVersion, bgpM2CfgPeerConfiguredVersion,
bgpM2CfgAllowVersionNegotiation, bgpM2CfgAllowVersionNegotiation,
bgpM2CfgPeerLocalAddrType, bgpM2CfgPeerLocalAddrType,
bgpM2CfgPeerLocalAddr, bgpM2CfgPeerLocalAddr,
bgpM2CfgPeerLocalAs, bgpM2CfgPeerLocalAs,
bgpM2CfgPeerRemoteAddrType, bgpM2CfgPeerRemoteAddrType,
bgpM2CfgPeerRemoteAddr, bgpM2CfgPeerRemoteAddr,
bgpM2CfgPeerRemotePort,
bgpM2CfgPeerRemoteAs, bgpM2CfgPeerRemoteAs,
bgpM2CfgPeerEntryStorageType, bgpM2CfgPeerEntryStorageType,
bgpM2CfgPeerError, bgpM2CfgPeerError,
bgpM2CfgPeerBgpPeerEntry, bgpM2CfgPeerBgpPeerEntry,
bgpM2CfgPeerRowEntryStatus, bgpM2CfgPeerRowEntryStatus,
bgpM2CfgPeerIndex, bgpM2CfgPeerIndex,
bgpM2CfgPeerStatus, bgpM2CfgPeerStatus,
bgpM2CfgPeerConnectRetryInterval, bgpM2CfgPeerConnectRetryInterval,
bgpM2CfgPeerHoldTimeConfigured, bgpM2CfgPeerHoldTimeConfigured,
bgpM2CfgPeerKeepAliveConfigured, bgpM2CfgPeerKeepAliveConfigured,
bgpM2CfgPeerMinASOrigInterval, bgpM2CfgPeerMinASOrigInterval,
bgpM2CfgPeerMinRouteAdverInter bgpM2CfgPeerMinRouteAdverInter
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Configuration objects for BGP peers." "Configuration objects for BGP peers."
::= { bgpM2MIBGroups 15 } ::= { bgpM2MIBGroups 14 }
bgpM2PeerAuthConfigurationGroup OBJECT-GROUP
OBJECTS {
bgpM2CfgPeerAuthEnabled,
bgpM2CfgPeerAuthCode,
bgpM2CfgPeerAuthValue
}
STATUS current
DESCRIPTION
"Configuration objects for BGP peers that support
authentication."
::= { bgpM2MIBGroups 16 }
bgpM2PeerRouteReflectorCfgGroup OBJECT-GROUP bgpM2PeerRouteReflectorCfgGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bgpM2CfgRouteReflector, bgpM2CfgRouteReflector,
bgpM2CfgClusterId, bgpM2CfgClusterId,
bgpM2CfgPeerReflectorClient bgpM2CfgPeerReflectorClient
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Configuration objects for BGP peers that support route "Configuration objects for BGP peers that support route
reflection." reflection."
::= { bgpM2MIBGroups 17 } ::= { bgpM2MIBGroups 15 }
bgpM2PeerAsConfederationCfgGroup OBJECT-GROUP bgpM2PeerAsConfederationCfgGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bgpM2CfgConfederationRouter, bgpM2CfgConfederationRouter,
bgpM2CfgConfederationId, bgpM2CfgConfederationId,
bgpM2CfgPeerConfedMember bgpM2CfgPeerConfedMember
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Configuration objects for BGP peers that support BGP "Configuration objects for BGP peers that support BGP
confederations." confederations."
::= { bgpM2MIBGroups 18 } ::= { bgpM2MIBGroups 16 }
bgpM2MIBNotificationsGroup NOTIFICATION-GROUP bgpM2MIBNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
bgpM2Established, bgpM2Established,
bgpM2BackwardTransition bgpM2BackwardTransition
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group contains objects for notifications "This group contains objects for notifications
supported by this mib module." supported by this mib module."
::= { bgpM2MIBGroups 19 } ::= { bgpM2MIBGroups 17 }
bgpM2Rfc2545Group OBJECT-GROUP bgpM2Rfc2545Group OBJECT-GROUP
OBJECTS { OBJECTS {
bgpM2LinkLocalNextHopPresent, bgpM2LinkLocalNextHopPresent,
bgpM2LinkLocalNextHop bgpM2LinkLocalNextHop
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group is required for peers that support exchanging "This group is required for peers that support exchanging
of IPv6 NLRI per RFC 2545." of IPv6 NLRI per RFC 2545."
::= { bgpM2MIBGroups 20 } ::= { bgpM2MIBGroups 18 }
END END
2. Security Considerations 5. Intellectual Property Rights
This MIB module contains controls which relate to core services for The IETF takes no position regarding the validity or scope of any
interdomain routing using the Border Gateway Protocol. In particu- intellectual property or other rights that might be claimed to per-
lar, this MIB allows configuration of operational elements for those tain to the implementation or use of the technology described in this
services. If such configuration is done without consideration for document or the extent to which any license under such rights might
the effects of such configuration activity, or malicious configura- or might not be available; neither does it represent that it has made
tion activity is allowed on the managed elements, the effect could be any effort to identify any such rights. Information on the IETF's
denial of service to the processes and end users in the affected procedures with respect to rights in standards-track and standards-
domain(s). related documentation can be found in BCP-11. Copies of claims of
rights made available for publication and any assurances of licenses
to be made available, or the result of an attempt made to obtain a
general license or permission for the use of such proprietary rights
by implementors or users of this specification can be obtained from
the IETF Secretariat.
SNMPv1 is not considered a sufficiently secure environment for the The IETF invites any interested party to bring to its attention any
deployment of such configuration ability. Even if the management copyrights, patents or patent applications, or other proprietary
data path is secure at the network protocol layer (by the deployment rights which may cover technology that may be required to practice
of secure IP, for example), there are still points of exposure around this standard. Please address the information to the IETF Executive
such issues as to what operators and applications are allowed to Director.
access and modify the configuration as exposed through this MIB mod-
ule.
It is strongly recommended that the agent implementor considers the 6. Security Considerations
security features afforded by the SNMP Version 3 framework in expos-
ing the configuration features of this MIB module. In particular,
the availability and usage of the User-based Security Model [12]
5. Changes From Last Version This MIB relates to a system providing inter-domain routing. As
such, improper manipulation of the objects represented by this MIB
may result in denial of service to a large number of end-users.
There are several management objects defined in this MIB that have a
MAX-ACCESS clause of read-write and/or read-create. Such objects
should be considered sensitive or vulnerable in most network environ-
ments. The support for SET operations in a non-secure environment
without proper protection can have a negative effect on network oper-
ations. These objects include:
XXX TODO
There are a number of managed objects in this MIB that con-
tain sensitive information regarding the operation of a network. For
example, a BGP peer's local and remote addresses might be sensitive
for ISPs who want to keep interface addresses on routers confiden-
tial to prevent router addresses used for a denial of service attack
or spoofing.
Therefore, it is important in most environments to control read
access to these objects and possibly to even encrypt the values of
these object when sending them over the network via SNMP.
SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), there is still no con-
trol as to who on the secure network is allowed to access and GET/SET
(read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security fea-
tures as provided by the SNMPv3 framework.[REF] Specifically, the
implementation and use of the User-based Security Model [REF] and the
View-based Access Control Model [REF] is recommended to provide
appropriate security controls.
It is then an operator/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly config-
ured to give access to the objects only to those principals (users)
that have legitimate rights to indeed GET or SET (change/cre-
ate/delete) them.
7. Acknowledgements
Tom Nadeau, Cisco Systems, Inc.
Jon Saperia, JDS Consulting, Inc.
Bill Fenner, AT&T Research
Mike McFaden, Riverstone Networks, Inc.
Joel Krauska, Exodus Communications, Inc.
Carl W. Kalbfleisch, Verio Networks, Inc.
Joe Dupre, Gold Wire Technology
others TBD...
8. Changes From Last Version
This section is used to track changes from version to version of this This section is used to track changes from version to version of this
document. This section will be removed from the document prior to document. This section will be removed from the document prior to
being issued to IDR working group last call. being issued to IDR working group last call.
* Changes from draft-ietf-idr-bgp4-mibv2-03.txt to draft-ietf-
idr-bgp4-mibv2-04.txt (12 January 2004)
Remove all objects related to BGP authentication as BGP
authentication has been officially removed.
Removed bgpM2AsPathElementValue from bgpM2AsPathTable
Add current OPS group MIB boilerplate and security boiler-
plate. Work still needs to be done in the security section.
Split references into Normative References and Informational
References. Add IETF Intellectual Property Rights statement.
Update copyright dates.
Add new TEXTUAL-CONVENTION, BgpM2Afi to more properly reflect
BGP Multi-Protocol Extensions.
Add bgpM2NlriPrefixType to bgpM2NlriTable as an interim mecha-
nism to support "proper" translation of an AFI to an InetAd-
dressType. Further thought must be put into this.
Delete bgpM2CfgPeerRemotePort object. Deployed implementa-
tions do not seem to allow this to be configured.
Add bgpM2PeerInstance to permit multiple BGP routing instances
to be supported.
Renumber numerous OIDs to account for re-organizing objects.
Update conformance statements to match.
* Changes from draft-ietf-idr-bgp4-mibv2-02.txt to draft-ietf- * Changes from draft-ietf-idr-bgp4-mibv2-02.txt to draft-ietf-
idr-bgp4-mibv2-03.txt (4 November 2002): idr-bgp4-mibv2-03.txt (4 November 2002):
Changed the order of the bgpM2NlriPrefixLen and Changed the order of the bgpM2NlriPrefixLen and
bgpM2NlriPrefix objects and renumbered them. This was to make bgpM2NlriPrefix objects and renumbered them. This was to make
it consistant with user expectations. it consistant with user expectations.
Clarify the peer table description text to specify the remote Clarify the peer table description text to specify the remote
peer. peer.
skipping to change at page 100, line 5 skipping to change at page 94, line 48
bgpM2CalcLength and PathString columns added to bgpM2PathAttr bgpM2CalcLength and PathString columns added to bgpM2PathAttr
table. table.
Creation of separate bgpM2AdjRibsOutTable. Creation of separate bgpM2AdjRibsOutTable.
Appearance of NLRI table notions such as 'opaque type'. Appearance of NLRI table notions such as 'opaque type'.
Overhaul of specification of AS Path types to accommodate eas- Overhaul of specification of AS Path types to accommodate eas-
ier management at time of route aggregation. ier management at time of route aggregation.
6. References 9. Normative References
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2571, April 1999.
[2] Rose, M., and K. McCloghrie, "Structure and Identification of Man-
agement Information for TCP/IP-based Internets", STD 16, RFC 1155,
May 1990.
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model
1212, March 1991. (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC 2574, April 1999.
[4] Rose, M., "A Convention for Defining Traps for use with the SNMP", [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
RFC 1215, March 1991. Rose, M., and S. Waldbusser, "Structure of Management Infor-
mation Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
and S. Waldbusser, "Structure of Management Information Version 2 Rose, M., and S. Waldbusser, "Textual Conventions for
(SMIv2)", STD 58, RFC 2578, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC Rose, M., and S. Waldbusser, "Conformance Statements for
2579, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., [RFC3411] D. Harrington, R. Presuhn, B. Wijnen, "An Architecture for
and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC Describing Simple Network Management Protocol (SNMP) Manage-
2580, April 1999. ment Frameworks", RFC 3411, December 2002.
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network [RFC3413] D. Levi, P. Meyer, B. Stewart, "Simple Network Management
Management Protocol", STD 15, RFC 1157, May 1990. Protocol (SNMP) Applications", RFC 3413, December 2002.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduc- [RFC3415] B. Wijnen, R. Presuhn, K. McCloghrie, "View-based Access
tion to Community-based SNMPv2", RFC 1901, January 1996. Control Model (VACM) for the Simple Network Management Pro-
tocol (SNMP)", RFC 3415, December 2002.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport [RFC3416] Presuhn, R., Editor, "Version 2 of the Protool Operations
Mappings for Version 2 of the Simple Network Management Protocol for the Simple Network Management Protocol (SNMP)", RFC
(SNMPv2)", RFC 1906, January 1996. 3416, December 2002.
[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Pro- [RFC3417] Presuhn, R., Editor, "Transport Mappings for the Simple Net-
cessing and Dispatching for the Simple Network Management Protocol work Management Protocol (SNMP)", RFC 3417, December 2002.
(SNMP)", RFC 2572, April 1999.
[12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for [RFC1213] McCloghrie, K. and M. Rose, Editors, "Management Information
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC Base for Network Management of TCP/IP-based Internets: MIB-
2574, April 1999. II", STD 17, RFC 1213, Hughes LAN Systems, Performance Sys-
tems International, March 1991.
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol [RFC1657] Willis, S., Burruss, J., and Chu, J., "Definitions of Man-
Operations for Version 2 of the Simple Network Management Protocol aged Objects for the Fourth Version of the Border Gateway
(SNMPv2)", RFC 1905, January 1996. Protocol (BGP-4) using SMIv2", RFC 1657, July 1994.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC [MIB-DRAFT] Hares, S., Haas, J., Willis, S., Burruss, J., and Chu, J.,
2573, April 1999. "Definitions of Managed Objects for the Fourth Version of
Border Gateway Protocol (BGP-4)", draft-ietf-idr-
bgp4-mib-06.txt, Work-in-progress.
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Con- [RFC1771] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)",
trol Model (VACM) for the Simple Network Management Protocol RFC 1771, March 1995.
(SNMP)", RFC 2575, April 1999.
[16] McCloghrie, K. and M. Rose, Editors, "Management Information Base [RFC1772] Rekhter, Y., Gross, P., "Application of the Border Gateway
for Network Management of TCP/IP-based Internets: MIB-II", STD 17, Protocol in the Internet", RFC 1772, March 1995.
RFC 1213, Hughes LAN Systems, Performance Systems International,
March 1991.
[17] Willis, S., Burruss, J., and Chu, J., "Definitions of Managed [RFC3065] Traina, P., McPherson, D., and Scudder, J., "Autonomous Sys-
Objects for the Fourth Version of the Border Gateway Protocol tem Confederations for BGP", RFC 3065, February, 2001.
(BGP-4) using SMIv2", RFC 1657, July 1994.
[18] Hares, S., Haas, J., Willis, S., Burruss, J., and Chu, J., "Defini- [RFC1997] Chandra, R., Traina, P., and Li, T., "BGP Communities
tions of Managed Objects for the Fourth Version of Border Gateway Attribute", RFC 1997, August, 1996.
Protocol (BGP-4)", draft-ietf-idr-bgp4-mib-06.txt, Work-in-
progress.
[19] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", RFC [RFC2858] Bates, T., Rekhter, Y., Chandra, R., and Katz, D., "Multi-
1771, March 1995. protocol Extensions for BGP-4", RFC 2858, June, 2000.
[20] Rekhter, Y., Gross, P., "Application of the Border Gateway Proto- [RFC2796] Bates, T., Chandra, R., and Chen, E., "BGP Route Reflection
col in the Internet", RFC 1772, March 1995. - An Alternative to Full Mesh IBGP", RFC 2796, April 2000.
[21] Traina, P., McPherson, D., and Scudder, J., "Autonomous System [BGP-EXTCOMM] Sangli, S., Tappan, D., and Rekhter, Y., "BGP Extended
Confederations for BGP", RFC 3065, February, 2001. Communities Attribute", Work-in-progress.
[22] Chandra, R., Traina, P., and Li, T., "BGP Communities Attribute", [RFC3107] Rehkter, Y., and Rosen, E., "Carrying Label Information in
RFC 1997, August, 1996. BGP-4", RFC 3107, May 2001.
[23] Bates, T., Rekhter, Y., Chandra, R., and Katz, D., "Multiprotocol 10. Informative References
Extensions for BGP-4", June, 2000.
[24] Bates, T., Chandra, R., and Chen, E., "BGP Route Reflection - An [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
Alternative to Full Mesh IBGP", RFC 2796, April 2000. "Introduction to Community-based SNMPv2", RFC 1901, January
1996.
[25] Sangli, S., Tappan, D., and Rekhter, Y., "BGP Extended Communities [RFC2576] Frye, R., Levi, D., Routhier, S. and B. Wijnen, "Coexistence
Attribute", Work-in-progress. between Version 1, Version 2, and Version 3 of the Internet-
Standard Network Management Framework", RFC 2576, March
2000.
[26] Rehkter, Y., and Rosen, E., "Carrying Label Information in BGP-4", [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduc-
RFC 3107, May 2001. tion and Applicability Statements for Internet- Standard
Management Framework", RFC 3410, December 2002.
7. Authors' Addresses 11. Authors' Addresses
Jeff Haas Jeff Haas
NextHop Technologies NextHop Technologies
825 Victors Way, Suite 100 825 Victors Way, Suite 100
Ann Arbor, MI 48108 Ann Arbor, MI 48108
Phone: +1 734 222-1600 Phone: +1 734 222-1600
Fax: +1 734 222-1602 Fax: +1 734 222-1602
Email: jhaas@nexthop.com Email: jhaas@nexthop.com
Susan Hares Susan Hares
NextHop Technologies NextHop Technologies
825 Victors Way, Suite 100 825 Victors Way, Suite 100
Ann Arbor, MI 48108 Ann Arbor, MI 48108
Phone: +1 734 222-1600 Phone: +1 734 222-1600
Fax: +1 734 222-1602 Fax: +1 734 222-1602
Email: skh@nexthop.com Email: skh@nexthop.com
Wayne Tackabury Wayne Tackabury
Gold Wire Technology Gold Wire Technology
skipping to change at page 102, line 31 skipping to change at page 97, line 20
Email: skh@nexthop.com Email: skh@nexthop.com
Wayne Tackabury Wayne Tackabury
Gold Wire Technology Gold Wire Technology
411 Waverley Oaks Rd. 411 Waverley Oaks Rd.
Waltham, MA 02452-8401 Waltham, MA 02452-8401
Phone: +1 781 398-8819 Phone: +1 781 398-8819
Fax: +1 781 398-8811 Fax: +1 781 398-8811
Email: wayne@goldwiretech.com Email: wayne@goldwiretech.com
8. Full Copyright Statement 12. Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this doc- included on all such copies and derivative works. However, this doc-
ument itself may not be modified in any way, such as by removing the ument itself may not be modified in any way, such as by removing the
copyright notice or references to the Internet Society or other copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of develop- Internet organizations, except as needed for the purpose of develop-
skipping to change at page 103, line 12 skipping to change at page 98, line 8
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MER- HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MER-
CHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. CHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . . 2
2.2. Mechanisms for MIB Extensibility . . . . . . . . . . . . . . . 3 2.2. Mechanisms for MIB Extensibility . . . . . . . . . . . . . . . 3
2.3. BGP Configuration . . . . . . . . . . . . . . . . . . . . . . . 4 2.3. BGP Configuration . . . . . . . . . . . . . . . . . . . . . . . 3
3. MIB Organization . . . . . . . . . . . . . . . . . . . . . . . . 4 3. MIB Organization . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. bgpM2BaseScalars . . . . . . . . . . . . . . . . . . . . . . . 5 3.1. bgpM2BaseScalars . . . . . . . . . . . . . . . . . . . . . . . 4
3.2. bgpM2PeerData . . . . . . . . . . . . . . . . . . . . . . . . . 5 3.2. bgpM2PeerData . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2.1. bgpM2PeerCapabilities . . . . . . . . . . . . . . . . . . . . 6 3.2.1. bgpM2PeerCapabilities . . . . . . . . . . . . . . . . . . . . 5
3.2.2. bgpM2PeerCounters . . . . . . . . . . . . . . . . . . . . . . 6 3.2.2. bgpM2PeerCounters . . . . . . . . . . . . . . . . . . . . . . 6
3.2.3. Peering Data Extensions . . . . . . . . . . . . . . . . . . . 6 3.2.3. Peering Data Extensions . . . . . . . . . . . . . . . . . . . 6
3.2.4. Configuring Peering Sessions . . . . . . . . . . . . . . . . 7 3.2.4. Configuring Peering Sessions . . . . . . . . . . . . . . . . 6
3.3. BGP Routing Information Base Data . . . . . . . . . . . . . . . 8 3.3. BGP Routing Information Base Data . . . . . . . . . . . . . . . 7
3.3.1. Routing Information Base Extensions . . . . . . . . . . . . . 9 3.3.1. Routing Information Base Extensions . . . . . . . . . . . . . 8
3.4. Considerations on Table Indexing . . . . . . . . . . . . . . . 9 3.4. Considerations on Table Indexing . . . . . . . . . . . . . . . 8
1. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2. Security Considerations . . . . . . . . . . . . . . . . . . . . . 97 5. Intellectual Property Rights . . . . . . . . . . . . . . . . . . 91
3. Intellectual Property . . . . . . . . . . . . . . . . . . . . . . 98 6. Security Considerations . . . . . . . . . . . . . . . . . . . . . 92
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 98 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 93
5. Changes From Last Version . . . . . . . . . . . . . . . . . . . . 99 8. Changes From Last Version . . . . . . . . . . . . . . . . . . . . 93
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 9. Normative References . . . . . . . . . . . . . . . . . . . . . . 94
7. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 102 10. Informative References . . . . . . . . . . . . . . . . . . . . . 96
8. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 102 11. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 96
12. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 97
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/