draft-ietf-idr-bgp4-mib-15.txt   rfc4273.txt 
INTERNET DRAFT BGP4-MIB August 2004 Network Working Group J. Haas, Ed.
Request for Comments: 4273 S. Hares, Ed.
Network Working Group Editors of this version: Obsoletes: 1269, 1657 NextHop Technologies
INTERNET DRAFT J. Haas Category: Standards Track January 2006
S. Hares
NextHop Technologies
August 2004
Definitions of Managed Objects
for the Fourth Version of Border Gateway Protocol (BGP-4)
<draft-ietf-idr-bgp4-mib-15.txt>
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Definitions of Managed Objects for BGP-4
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at Status of This Memo
http://www.ietf.org/ietf/1id-abstracts.
The list of Internet-Draft Shadow Directories can be accessed at This document specifies an Internet standards track protocol for the
http://www.ietf.org/shadow.html. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2006).
Abstract Abstract
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 or lower. Border Gateway Protocol Version 4 or lower.
The origin of this memo is from RFC 1269 "Definitions of Managed The origin of this memo is from RFC 1269 "Definitions of Managed
Objects for the Border Gateway Protocol (Version 3)", which was Objects for the Border Gateway Protocol (Version 3)", which was
updated to support BGP-4 in RFC 1657. This memo fixes errors updated to support BGP-4 in RFC 1657. This memo fixes errors
introduced when the MIB module was converted to use the SMIv2 introduced when the MIB module was converted to use the SMIv2
language. This memo also updates references to the current SNMP language. This memo also updates references to the current SNMP
framework documents. framework documents.
This memo is intended to document deployed implementations of this This memo is intended to document deployed implementations of this
MIB module in a historical context, provide clarifications of some MIB module in a historical context, to provide clarifications of some
items and also note errors where the MIB module fails to fully items, and to note errors where the MIB module fails to fully
represent the BGP protocol. Work is currently in progress to replace represent the BGP protocol. Work is currently in progress to replace
this MIB module with a new one representing the current state of the this MIB module with a new one representing the current state of the
BGP protocol and its extensions. BGP protocol and its extensions.
This document obsoletes RFC 1269 and RFC 1657. This document obsoletes RFC 1269 and RFC 1657.
Distribution of this memo is unlimited. Please forward comments to
idr@ietf.org.
Table of Contents Table of Contents
1. Introduction ................................................. 3 1. Introduction ....................................................2
2. The Internet-Standard Management Framework ................... 3 2. The Internet-Standard Management Framework ......................2
3. Overview ..................................................... 3 3. Overview ........................................................2
4. Definitions .................................................. 4 4. Definitions .....................................................3
5. Intellectual Property ....................................... 32 5. Security Considerations ........................................28
6. Security Considerations ..................................... 33 6. Acknowledgements ...............................................30
7. Acknowledgements ............................................ 35 7. Normative References ...........................................31
8. IANA Considerations ......................................... 36
9. Normative References ........................................ 36
10. Editors' Address ............................................ 36
11. Full Copyright Statement .................................... 37
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 or lower [BGP, BGP4APP]. Border Gateway Protocol Version 4 or lower [BGP4, BGP4APP].
This memo obsoletes RFC 1657 and RFC 1269. This memo obsoletes RFC 1657 and RFC 1269.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
skipping to change at page 3, line 35 skipping to change at page 2, line 45
module that is compliant to the SMIv2, which is described in STD 58, 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 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Overview 3. Overview
These objects are used to control and manage a BGP-4 implementation. These objects are used to control and manage a BGP-4 implementation.
Apart from a few system-wide scalar objects, this MIB is broken into Apart from a few system-wide scalar objects, this MIB is broken into
three tables: the BGP Peer Table, the BGP Received Path Attribute three tables: the BGP Peer Table, the BGP Received Path Attribute
Table, and the BGP-4 Received Path Attribute Table. The BGP Peer Table, and the BGP-4 Received Path Attribute Table. The BGP Peer
Table contains information about state and current activity of Table contains information about state and current activity of
connections with the BGP peers. The BGP Received Path Attribute connections with the BGP peers. The BGP Received Path Attribute
Table contains path attributes received from all peers running BGP Table contains path attributes received from all peers running BGP
version 3 or less. The BGP-4 Received Path Attribute Table contains version 3 or less. The BGP-4 Received Path Attribute Table contains
path attributes received from all BGP-4 peers. The actual attributes path attributes received from all BGP-4 peers. The actual attributes
used in determining a route are a subset of the received attribute used in determining a route are a subset of the received attribute
tables after local routing policy has been applied. tables after local routing policy has been applied.
4. Definitions 4. Definitions
BGP4-MIB DEFINITIONS ::= BEGIN BGP4-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
IpAddress, Integer32, Counter32, Gauge32, mib-2 IpAddress, Integer32, Counter32, Gauge32, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
bgp MODULE-IDENTITY bgp MODULE-IDENTITY
LAST-UPDATED "200408310000Z" LAST-UPDATED "200601110000Z"
ORGANIZATION "IETF IDR Working Group" ORGANIZATION "IETF IDR Working Group"
CONTACT-INFO "E-mail: idr@ietf.org CONTACT-INFO "E-mail: idr@ietf.org
Jeffrey Haas, Susan Hares (Editors) Jeffrey Haas, Susan Hares (Editors)
NextHop Technologies NextHop Technologies
825 Victors Way 825 Victors Way
Suite 100 Suite 100
Ann Arbor, MI 48108-2738 Ann Arbor, MI 48108-2738
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
skh@nexthop.com" skh@nexthop.com"
DESCRIPTION DESCRIPTION
"The MIB module for the BGP-4 protocol. "The MIB module for the BGP-4 protocol.
Copyright (C) The Internet Society (2004). This version Copyright (C) The Internet Society (2006). This
of this MIB module is part of RFC yyyy; see the RFC version of this MIB module is part of RFC 4273;
itself for full legal notices." see the RFC itself for full legal notices."
REVISION "200601110000Z"
DESCRIPTION
"Changes from RFC 1657:
REVISION "200408310000Z" 1) Fixed the definitions of the notifications
DESCRIPTION to make them equivalent to their initial
"Changes from RFC 1657: definition in RFC 1269.
2) Added compliance and conformance info.
3) Updated information for the values of
bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref,
bgp4PathAttrCalcLocalPref,
bgp4PathAttrMultiExitDisc,
bgp4PathAttrASPathSegement.
4) Added additional clarification comments where
needed.
1) Fixed the definitions of the notifications 5) Noted where objects do not fully reflect
to make them equivalent to their initial the protocol as Known Issues.
definition in RFC 1269. 6) Updated the DESCRIPTION for the
2) Added compliance and conformance info. bgp4PathAttrAtomicAggregate object.
3) Updated information for the values of 7) The following objects have had their DESCRIPTION
bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, clause modified to remove the text that suggested
bgp4PathAttrCalcLocalPref, bgp4PathAttrMultiExitDisc, (using 'should' verb) initializing the counter
bgp4PathAttrASPathSegement. to zero on a transition to the established state:
4) Added additional clarification comments where bgpPeerInUpdates, bgpPeerOutUpdates,
needed. bgpPeerInTotalMessages, bgpPeerOutTotalMessages
5) Noted where objects do not fully reflect Those implementations that still do this are
the protocol as Known Issues. still compliant with this new wording.
6) Updated the DESCRIPTION for the Applications should not assume counters have
bgp4PathAttrAtomicAggregate object. started at zero.
7) The following objects have had their DESCRIPTION
clause modified to remove the text that suggested
(using 'should' verb) to initialize the counter
to zero on a transition to the established state:
bgpPeerInUpdates, bgpPeerOutUpdates,
bgpPeerInTotalMessages, bgpPeerOutTotalMessages
Those implementations that still do this are
still compliant with this new wording.
Appliciations should not assume counters to have
started at zero.
Published as RFC yyyy." Published as RFC 4273."
REVISION "199405050000Z" REVISION "199405050000Z"
DESCRIPTION DESCRIPTION
"Translated to SMIv2 and published as RFC 1657." "Translated to SMIv2 and published as RFC 1657."
REVISION "199110261839Z" REVISION "199110261839Z"
DESCRIPTION DESCRIPTION
"Initial version, published as RFC 1269." "Initial version, published as RFC 1269."
::= { mib-2 15 }
::= { mib-2 15 } bgpVersion OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1..255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Vector of supported BGP protocol version
numbers. Each peer negotiates the version
from this vector. Versions are identified
via the string of bits contained within this
object. The first octet contains bits 0 to
7, the second octet contains bits 8 to 15,
and so on, with the most significant bit
referring to the lowest bit number in the
octet (e.g., the MSB of the first octet
refers to bit 0). If a bit, i, is present
and set, then the version (i+1) of the BGP
is supported."
REFERENCE
"RFC 4271, Section 4.2."
::= { bgp 1 }
bgpVersion OBJECT-TYPE bgpLocalAs OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1..255)) SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Vector of supported BGP protocol version "The local autonomous system number."
numbers. Each peer negotiates the version REFERENCE
from this vector. Versions are identified "RFC 4271, Section 4.2, 'My Autonomous System'."
via the string of bits contained within this ::= { bgp 2 }
object. The first octet contains bits 0 to
7, the second octet contains bits 8 to 15,
and so on, with the most significant bit
referring to the lowest bit number in the
octet (e.g., the MSB of the first octet
refers to bit 0). If a bit, i, is present
and set, then the version (i+1) of the BGP
is supported."
REFERENCE
"RFC yyyy, Section 4.2."
::= { bgp 1 }
-- BGP Peer table. This table contains, one entry per
-- BGP peer, information about the BGP peer.
bgpLocalAs OBJECT-TYPE bgpPeerTable OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX SEQUENCE OF BgpPeerEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The local autonomous system number." "BGP peer table. This table contains,
REFERENCE one entry per BGP peer, information about the
"RFC yyyy, Section 4.2, 'My Autonomous System'." connections with BGP peers."
::= { bgp 2 } ::= { bgp 3 }
-- BGP Peer table. This table contains, one entry per bgpPeerEntry OBJECT-TYPE
-- BGP peer, information about the BGP peer. SYNTAX BgpPeerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entry containing information about the
connection with a BGP peer."
INDEX { bgpPeerRemoteAddr }
::= { bgpPeerTable 1 }
bgpPeerTable OBJECT-TYPE BgpPeerEntry ::= SEQUENCE {
SYNTAX SEQUENCE OF BgpPeerEntry bgpPeerIdentifier
MAX-ACCESS not-accessible IpAddress,
STATUS current bgpPeerState
DESCRIPTION INTEGER,
"BGP peer table. This table contains, bgpPeerAdminStatus
one entry per BGP peer, information about the INTEGER,
connections with BGP peers." bgpPeerNegotiatedVersion
::= { bgp 3 } Integer32,
bgpPeerLocalAddr
IpAddress,
bgpPeerLocalPort
Integer32,
bgpPeerRemoteAddr
IpAddress,
bgpPeerRemotePort
Integer32,
bgpPeerRemoteAs
Integer32,
bgpPeerInUpdates
Counter32,
bgpPeerOutUpdates
Counter32,
bgpPeerInTotalMessages
Counter32,
bgpPeerOutTotalMessages
Counter32,
bgpPeerLastError
OCTET STRING,
bgpPeerFsmEstablishedTransitions
Counter32,
bgpPeerFsmEstablishedTime
Gauge32,
bgpPeerConnectRetryInterval
Integer32,
bgpPeerHoldTime
Integer32,
bgpPeerKeepAlive
Integer32,
bgpPeerHoldTimeConfigured
Integer32,
bgpPeerKeepAliveConfigured
Integer32,
bgpPeerMinASOriginationInterval
Integer32,
bgpPeerMinRouteAdvertisementInterval
Integer32,
bgpPeerInUpdateElapsedTime
Gauge32
}
bgpPeerEntry OBJECT-TYPE bgpPeerIdentifier OBJECT-TYPE
SYNTAX BgpPeerEntry SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Entry containing information about the "The BGP Identifier of this entry's BGP peer.
connection with a BGP peer." This entry MUST be 0.0.0.0 unless the
INDEX { bgpPeerRemoteAddr } bgpPeerState is in the openconfirm or the
::= { bgpPeerTable 1 } established state."
REFERENCE
"RFC 4271, Section 4.2, 'BGP Identifier'."
::= { bgpPeerEntry 1 }
BgpPeerEntry ::= SEQUENCE { bgpPeerState OBJECT-TYPE
bgpPeerIdentifier SYNTAX INTEGER {
IpAddress, idle(1),
bgpPeerState connect(2),
INTEGER, active(3),
bgpPeerAdminStatus opensent(4),
INTEGER, openconfirm(5),
bgpPeerNegotiatedVersion established(6)
Integer32, }
bgpPeerLocalAddr MAX-ACCESS read-only
IpAddress, STATUS current
bgpPeerLocalPort DESCRIPTION
Integer32, "The BGP peer connection state."
bgpPeerRemoteAddr REFERENCE
IpAddress, "RFC 4271, Section 8.2.2."
bgpPeerRemotePort ::= { bgpPeerEntry 2 }
Integer32,
bgpPeerRemoteAs
Integer32,
bgpPeerInUpdates
Counter32,
bgpPeerOutUpdates
Counter32,
bgpPeerInTotalMessages
Counter32,
bgpPeerOutTotalMessages
Counter32,
bgpPeerLastError
OCTET STRING,
bgpPeerFsmEstablishedTransitions
Counter32,
bgpPeerFsmEstablishedTime
Gauge32,
bgpPeerConnectRetryInterval
Integer32,
bgpPeerHoldTime
Integer32,
bgpPeerKeepAlive
Integer32,
bgpPeerHoldTimeConfigured
Integer32,
bgpPeerKeepAliveConfigured
Integer32,
bgpPeerMinASOriginationInterval
Integer32,
bgpPeerMinRouteAdvertisementInterval
Integer32,
bgpPeerInUpdateElapsedTime
Gauge32
}
bgpPeerIdentifier OBJECT-TYPE bgpPeerAdminStatus OBJECT-TYPE
SYNTAX IpAddress SYNTAX INTEGER {
MAX-ACCESS read-only stop(1),
STATUS current start(2)
DESCRIPTION }
"The BGP Identifier of this entry's BGP peer. MAX-ACCESS read-write
This entry MUST be 0.0.0.0 unless the STATUS current
bgpPeerState is in the openconfirm or the DESCRIPTION
established state." "The desired state of the BGP connection.
REFERENCE A transition from 'stop' to 'start' will cause
"RFC yyyy, Section 4.2, 'BGP Identifier'." the BGP Manual Start Event to be generated.
::= { bgpPeerEntry 1 } A transition from 'start' to 'stop' will cause
the BGP Manual Stop Event to be generated.
This parameter can be used to restart BGP peer
connections. Care should be used in providing
write access to this object without adequate
authentication."
REFERENCE
"RFC 4271, Section 8.1.2."
::= { bgpPeerEntry 3 }
bgpPeerState OBJECT-TYPE bgpPeerNegotiatedVersion OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Integer32
idle(1), MAX-ACCESS read-only
connect(2), STATUS current
active(3), DESCRIPTION
opensent(4), "The negotiated version of BGP running between
openconfirm(5), the two peers.
established(6)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The BGP peer connection state."
REFERENCE
"RFC yyyy, Section 8.2.2."
::= { bgpPeerEntry 2 }
This entry MUST be zero (0) unless the
bgpPeerState is in the openconfirm or the
established state.
bgpPeerAdminStatus OBJECT-TYPE Note that legal values for this object are
SYNTAX INTEGER { between 0 and 255."
stop(1), REFERENCE
start(2) "RFC 4271, Section 4.2.
} RFC 4271, Section 7."
MAX-ACCESS read-write ::= { bgpPeerEntry 4 }
STATUS current
DESCRIPTION
"The desired state of the BGP connection.
A transition from 'stop' to 'start' will cause
the BGP Manual Start Event to be generated.
A transition from 'start' to 'stop' will cause bgpPeerLocalAddr OBJECT-TYPE
the BGP Manual Stop Event to be generated. SYNTAX IpAddress
This parameter can be used to restart BGP peer MAX-ACCESS read-only
connections. Care should be used in providing STATUS current
write access to this object without adequate DESCRIPTION
authentication." "The local IP address of this entry's BGP
REFERENCE connection."
"RFC yyyy, Section 8.1.2." ::= { bgpPeerEntry 5 }
::= { bgpPeerEntry 3 }
bgpPeerNegotiatedVersion OBJECT-TYPE bgpPeerLocalPort OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The negotiated version of BGP running between "The local port for the TCP connection between
the two peers. the BGP peers."
::= { bgpPeerEntry 6 }
This entry MUST be zero (0) unless the bgpPeerRemoteAddr OBJECT-TYPE
bgpPeerState is in the openconfirm or the SYNTAX IpAddress
established state. MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The remote IP address of this entry's BGP
peer."
::= { bgpPeerEntry 7 }
Note that legal values for this object are bgpPeerRemotePort OBJECT-TYPE
between 0 and 255." SYNTAX Integer32 (0..65535)
REFERENCE MAX-ACCESS read-only
"RFC yyyy, Section 4.2. STATUS current
RFC yyyy, Section 7." DESCRIPTION
::= { bgpPeerEntry 4 } "The remote port for the TCP connection
between the BGP peers. Note that the
objects bgpPeerLocalAddr,
bgpPeerLocalPort, bgpPeerRemoteAddr, and
bgpPeerRemotePort provide the appropriate
reference to the standard MIB TCP
connection table."
::= { bgpPeerEntry 8 }
bgpPeerLocalAddr OBJECT-TYPE bgpPeerRemoteAs OBJECT-TYPE
SYNTAX IpAddress SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The local IP address of this entry's BGP "The remote autonomous system number received in
connection." the BGP OPEN message."
::= { bgpPeerEntry 5 } REFERENCE
"RFC 4271, Section 4.2."
::= { bgpPeerEntry 9 }
bgpPeerLocalPort OBJECT-TYPE bgpPeerInUpdates OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The local port for the TCP connection between "The number of BGP UPDATE messages
the BGP peers." received on this connection."
::= { bgpPeerEntry 6 } REFERENCE
"RFC 4271, Section 4.3."
::= { bgpPeerEntry 10 }
bgpPeerRemoteAddr OBJECT-TYPE bgpPeerOutUpdates OBJECT-TYPE
SYNTAX IpAddress SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote IP address of this entry's BGP "The number of BGP UPDATE messages
peer." transmitted on this connection."
::= { bgpPeerEntry 7 } REFERENCE
"RFC 4271, Section 4.3."
::= { bgpPeerEntry 11 }
bgpPeerRemotePort OBJECT-TYPE bgpPeerInTotalMessages OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote port for the TCP connection "The total number of messages received
between the BGP peers. Note that the from the remote peer on this connection."
objects bgpPeerLocalAddr, REFERENCE
bgpPeerLocalPort, bgpPeerRemoteAddr and "RFC 4271, Section 4."
bgpPeerRemotePort provide the appropriate ::= { bgpPeerEntry 12 }
reference to the standard MIB TCP
connection table."
::= { bgpPeerEntry 8 }
bgpPeerRemoteAs OBJECT-TYPE bgpPeerOutTotalMessages OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote autonomous system number." "The total number of messages transmitted to
REFERENCE the remote peer on this connection."
"RFC yyyy, Section 4.2." REFERENCE
::= { bgpPeerEntry 9 } "RFC 4271, Section 4."
::= { bgpPeerEntry 13 }
bgpPeerInUpdates OBJECT-TYPE bgpPeerLastError OBJECT-TYPE
SYNTAX Counter32 SYNTAX OCTET STRING (SIZE (2))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of BGP UPDATE messages "The last error code and subcode seen by this
received on this connection." peer on this connection. If no error has
REFERENCE occurred, this field is zero. Otherwise, the
"RFC yyyy, Section 4.3." first byte of this two byte OCTET STRING
::= { bgpPeerEntry 10 } contains the error code, and the second byte
contains the subcode."
REFERENCE
"RFC 4271, Section 4.5."
::= { bgpPeerEntry 14 }
bgpPeerOutUpdates OBJECT-TYPE bgpPeerFsmEstablishedTransitions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of BGP UPDATE messages "The total number of times the BGP FSM
transmitted on this connection." transitioned into the established state
REFERENCE for this peer."
"RFC yyyy, Section 4.3." REFERENCE
::= { bgpPeerEntry 11 } "RFC 4271, Section 8."
::= { bgpPeerEntry 15 }
bgpPeerInTotalMessages OBJECT-TYPE bgpPeerFsmEstablishedTime OBJECT-TYPE
SYNTAX Counter32 SYNTAX Gauge32
MAX-ACCESS read-only UNITS "seconds"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"The total number of messages received DESCRIPTION
from the remote peer on this connection." "This timer indicates how long (in
REFERENCE seconds) this peer has been in the
"RFC yyyy, Section 4." established state or how long
::= { bgpPeerEntry 12 } since this peer was last in the
established state. It is set to zero when
a new peer is configured or when the router is
booted."
REFERENCE
"RFC 4271, Section 8."
::= { bgpPeerEntry 16 }
bgpPeerOutTotalMessages OBJECT-TYPE bgpPeerConnectRetryInterval OBJECT-TYPE
SYNTAX Counter32 SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only UNITS "seconds"
STATUS current MAX-ACCESS read-write
DESCRIPTION STATUS current
"The total number of messages transmitted to DESCRIPTION
the remote peer on this connection." "Time interval (in seconds) for the
REFERENCE ConnectRetry timer. The suggested value
"RFC yyyy, Section 4." for this timer is 120 seconds."
::= { bgpPeerEntry 13 } REFERENCE
"RFC 4271, Section 8.2.2. This is the value used
to initialize the 'ConnectRetryTimer'."
::= { bgpPeerEntry 17 }
bgpPeerLastError OBJECT-TYPE bgpPeerHoldTime OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (2)) SYNTAX Integer32 ( 0 | 3..65535 )
MAX-ACCESS read-only UNITS "seconds"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"The last error code and subcode seen by this DESCRIPTION
peer on this connection. If no error has "Time interval (in seconds) for the Hold
occurred, this field is zero. Otherwise, the Timer established with the peer. The
first byte of this two byte OCTET STRING value of this object is calculated by this
contains the error code, and the second byte BGP speaker, using the smaller of the
contains the subcode." values in bgpPeerHoldTimeConfigured and the
REFERENCE Hold Time received in the OPEN message.
"RFC yyyy, Section 4.5."
::= { bgpPeerEntry 14 }
bgpPeerFsmEstablishedTransitions OBJECT-TYPE This value must be at least three seconds
SYNTAX Counter32 if it is not zero (0).
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of times the BGP FSM
transitioned into the established state
for this peer."
REFERENCE
"RFC yyyy, Section 8."
::= { bgpPeerEntry 15 }
bgpPeerFsmEstablishedTime OBJECT-TYPE If the Hold Timer has not been established
SYNTAX Gauge32 with the peer this object MUST have a value
UNITS "seconds" of zero (0).
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This timer indicates how long (in
seconds) this peer has been in the
established state or how long
since this peer was last in the
established state. It is set to zero when
a new peer is configured or the router is
booted."
REFERENCE
"RFC yyyy, Section 8."
::= { bgpPeerEntry 16 }
bgpPeerConnectRetryInterval OBJECT-TYPE
SYNTAX Integer32 (1..65535)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Time interval in seconds for the
ConnectRetry timer. The suggested value
for this timer is 120 seconds."
REFERENCE
"RFC yyyy, Section 8.2.2. This is the value used
to initialize the 'ConnectRetryTimer'."
::= { bgpPeerEntry 17 }
bgpPeerHoldTime OBJECT-TYPE If the bgpPeerHoldTimeConfigured object has
SYNTAX Integer32 ( 0 | 3..65535 ) a value of (0), then this object MUST have a
UNITS "seconds" value of (0)."
MAX-ACCESS read-only REFERENCE
STATUS current "RFC 4271, Section 4.2."
DESCRIPTION ::= { bgpPeerEntry 18 }
"Time interval in seconds for the Hold
Timer established with the peer. The
value of this object is calculated by this
BGP speaker by using the smaller of the
value in bgpPeerHoldTimeConfigured and the
Hold Time received in the OPEN message.
This value must be at least three seconds bgpPeerKeepAlive OBJECT-TYPE
if it is not zero (0). SYNTAX Integer32 ( 0 | 1..21845 )
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Time interval (in seconds) for the KeepAlive
timer established with the peer. The value
of this object is calculated by this BGP
speaker such that, when compared with
bgpPeerHoldTime, it has the same proportion
that bgpPeerKeepAliveConfigured has,
compared with bgpPeerHoldTimeConfigured.
If the Hold Timer has not been established If the KeepAlive timer has not been established
with the peer this object MUST have a value with the peer, this object MUST have a value
of zero (0). of zero (0).
If the bgpPeerHoldTimeConfigured object has If the of bgpPeerKeepAliveConfigured object
a value of (0), then this object MUST have a has a value of (0), then this object MUST have
value of (0)." a value of (0)."
REFERENCE REFERENCE
"RFC yyyy, Section 4.2." "RFC 4271, Section 4.4."
::= { bgpPeerEntry 18 } ::= { bgpPeerEntry 19 }
bgpPeerKeepAlive OBJECT-TYPE bgpPeerHoldTimeConfigured OBJECT-TYPE
SYNTAX Integer32 ( 0 | 1..21845 ) SYNTAX Integer32 ( 0 | 3..65535 )
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the KeepAlive "Time interval (in seconds) for the Hold Time
timer established with the peer. The value configured for this BGP speaker with this
of this object is calculated by this BGP peer. This value is placed in an OPEN
speaker such that, when compared with message sent to this peer by this BGP
bgpPeerHoldTime, it has the same proportion speaker, and is compared with the Hold
as what bgpPeerKeepAliveConfigured has when Time field in an OPEN message received
compared with bgpPeerHoldTimeConfigured. from the peer when determining the Hold
Time (bgpPeerHoldTime) with the peer.
This value must not be less than three
seconds if it is not zero (0). If it is
zero (0), the Hold Time is NOT to be
established with the peer. The suggested
value for this timer is 90 seconds."
REFERENCE
"RFC 4271, Section 4.2.
RFC 4271, Section 10."
::= { bgpPeerEntry 20 }
If the KeepAlive timer has not been established bgpPeerKeepAliveConfigured OBJECT-TYPE
with the peer this object MUST have a value SYNTAX Integer32 ( 0 | 1..21845 )
of zero (0). UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Time interval (in seconds) for the
KeepAlive timer configured for this BGP
speaker with this peer. The value of this
object will only determine the
KEEPALIVE messages' frequency relative to
the value specified in
bgpPeerHoldTimeConfigured; the actual
time interval for the KEEPALIVE messages is
indicated by bgpPeerKeepAlive. A
reasonable maximum value for this timer
would be one third of that of
bgpPeerHoldTimeConfigured.
If the value of this object is zero (0),
no periodical KEEPALIVE messages are sent
to the peer after the BGP connection has
been established. The suggested value for
this timer is 30 seconds."
REFERENCE
"RFC 4271, Section 4.4.
RFC 4271, Section 10."
::= { bgpPeerEntry 21 }
If the of bgpPeerKeepAliveConfigured object bgpPeerMinASOriginationInterval OBJECT-TYPE
has a value of (0), then this object MUST have SYNTAX Integer32 (1..65535)
a value of (0)." UNITS "seconds"
REFERENCE MAX-ACCESS read-write
"RFC yyyy, Section 4.4." STATUS current
::= { bgpPeerEntry 19 } DESCRIPTION
"Time interval (in seconds) for the
MinASOriginationInterval timer.
The suggested value for this timer is 15
seconds."
REFERENCE
"RFC 4271, Section 9.2.1.2.
RFC 4271, Section 10."
::= { bgpPeerEntry 22 }
bgpPeerHoldTimeConfigured OBJECT-TYPE bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE
SYNTAX Integer32 ( 0 | 3..65535 ) SYNTAX Integer32 (1..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the Hold Time "Time interval (in seconds) for the
configured for this BGP speaker with this MinRouteAdvertisementInterval timer.
peer. This value is placed in an OPEN The suggested value for this timer is 30
message sent to this peer by this BGP seconds for EBGP connections and 5
speaker, and is compared with the Hold seconds for IBGP connections."
Time field in an OPEN message received REFERENCE
from the peer when determining the Hold "RFC 4271, Section 9.2.1.1.
Time (bgpPeerHoldTime) with the peer. RFC 4271, Section 10."
This value must not be less than three ::= { bgpPeerEntry 23 }
seconds if it is not zero (0) in which
case the Hold Time is NOT to be
established with the peer. The suggested
value for this timer is 90 seconds."
REFERENCE
"RFC yyyy, Section 4.2."
::= { bgpPeerEntry 20 }
bgpPeerKeepAliveConfigured OBJECT-TYPE
SYNTAX Integer32 ( 0 | 1..21845 )
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Time interval in seconds for the
KeepAlive timer configured for this BGP
speaker with this peer. The value of this
object will only determine the
KEEPALIVE messages' frequency relative to
the value specified in
bgpPeerHoldTimeConfigured; the actual
time interval for the KEEPALIVE messages is
indicated by bgpPeerKeepAlive. A
reasonable maximum value for this timer
would be configured to be one
third of that of
bgpPeerHoldTimeConfigured.
If the value of this object is zero (0),
no periodical KEEPALIVE messages are sent
to the peer after the BGP connection has
been established. The suggested value for
this timer is 30 seconds."
REFERENCE
"RFC yyyy, Section 4.4."
::= { bgpPeerEntry 21 }
bgpPeerMinASOriginationInterval OBJECT-TYPE bgpPeerInUpdateElapsedTime OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Gauge32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the "Elapsed time (in seconds) since the last BGP
MinASOriginationInterval timer. UPDATE message was received from the peer.
The suggested value for this timer is 15 Each time bgpPeerInUpdates is incremented,
seconds." the value of this object is set to zero (0)."
REFERENCE REFERENCE
"RFC yyyy, Section 9.2.1.2." "RFC 4271, Section 4.3.
::= { bgpPeerEntry 22 } RFC 4271, Section 8.2.2, Established state."
::= { bgpPeerEntry 24 }
bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE bgpIdentifier OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX IpAddress
UNITS "seconds" MAX-ACCESS read-only
MAX-ACCESS read-write STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The BGP Identifier of the local system."
"Time interval in seconds for the REFERENCE
MinRouteAdvertisementInterval timer. "RFC 4271, Section 4.2."
The suggested value for this timer is 30 ::= { bgp 4 }
seconds."
REFERENCE
"RFC yyyy, Section 9.2.1.1."
::= { bgpPeerEntry 23 }
bgpPeerInUpdateElapsedTime OBJECT-TYPE -- BGP Received Path Attribute Table. This table contains
SYNTAX Gauge32 -- one entry per path to a network, and path attributes
UNITS "seconds" -- received from all peers running BGP version 3 or less.
MAX-ACCESS read-only -- This table is obsolete, having been replaced in
STATUS current -- functionality by the bgp4PathAttrTable.
DESCRIPTION
"Elapsed time in seconds since the last BGP
UPDATE message was received from the peer.
Each time bgpPeerInUpdates is incremented,
the value of this object is set to zero (0)."
REFERENCE
"RFC yyyy, Section 4.3.
RFC yyyy, Section 8.2.2, Established state."
::= { bgpPeerEntry 24 }
bgpIdentifier OBJECT-TYPE bgpRcvdPathAttrTable OBJECT-TYPE
SYNTAX IpAddress SYNTAX SEQUENCE OF BgpPathAttrEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS obsolete
DESCRIPTION DESCRIPTION
"The BGP Identifier of the local system." "The BGP Received Path Attribute Table
REFERENCE contains information about paths to
"RFC yyyy, Section 4.2." destination networks, received from all
::= { bgp 4 } peers running BGP version 3 or less."
::= { bgp 5 }
-- BGP Received Path Attribute Table. This table contains, bgpPathAttrEntry OBJECT-TYPE
-- one entry per path to a network, path attributes SYNTAX BgpPathAttrEntry
-- received from all peers running BGP version 3 or less. MAX-ACCESS not-accessible
-- This table is obsolete, having been replaced in STATUS obsolete
-- functionality with the bgp4PathAttrTable. DESCRIPTION
"Information about a path to a network."
INDEX { bgpPathAttrDestNetwork,
bgpPathAttrPeer }
::= { bgpRcvdPathAttrTable 1 }
bgpRcvdPathAttrTable OBJECT-TYPE BgpPathAttrEntry ::= SEQUENCE {
SYNTAX SEQUENCE OF BgpPathAttrEntry bgpPathAttrPeer
MAX-ACCESS not-accessible IpAddress,
STATUS obsolete bgpPathAttrDestNetwork
DESCRIPTION IpAddress,
"The BGP Received Path Attribute Table bgpPathAttrOrigin
contains information about paths to INTEGER,
destination networks received from all bgpPathAttrASPath
peers running BGP version 3 or less." OCTET STRING,
::= { bgp 5 } bgpPathAttrNextHop
IpAddress,
bgpPathAttrInterASMetric
Integer32
}
bgpPathAttrEntry OBJECT-TYPE bgpPathAttrPeer OBJECT-TYPE
SYNTAX BgpPathAttrEntry SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"Information about a path to a network." "The IP address of the peer where the path
INDEX { bgpPathAttrDestNetwork, information was learned."
bgpPathAttrPeer } ::= { bgpPathAttrEntry 1 }
::= { bgpRcvdPathAttrTable 1 }
BgpPathAttrEntry ::= SEQUENCE { bgpPathAttrDestNetwork OBJECT-TYPE
bgpPathAttrPeer SYNTAX IpAddress
IpAddress, MAX-ACCESS read-only
bgpPathAttrDestNetwork STATUS obsolete
IpAddress, DESCRIPTION
bgpPathAttrOrigin "The address of the destination network."
INTEGER, REFERENCE
bgpPathAttrASPath "RFC 1267, Section 4.3."
OCTET STRING, ::= { bgpPathAttrEntry 2 }
bgpPathAttrNextHop
IpAddress,
bgpPathAttrInterASMetric
Integer32
}
bgpPathAttrPeer OBJECT-TYPE bgpPathAttrOrigin OBJECT-TYPE
SYNTAX IpAddress SYNTAX INTEGER {
MAX-ACCESS read-only igp(1),-- networks are interior
STATUS obsolete egp(2),-- networks learned via the
DESCRIPTION -- EGP protocol
"The IP address of the peer where the path incomplete(3) -- networks that
information was learned." -- are learned by some other
::= { bgpPathAttrEntry 1 } -- means
bgpPathAttrDestNetwork OBJECT-TYPE }
SYNTAX IpAddress MAX-ACCESS read-only
MAX-ACCESS read-only STATUS obsolete
STATUS obsolete DESCRIPTION
DESCRIPTION "The ultimate origin of the path information."
"The address of the destination network." REFERENCE
REFERENCE "RFC 1267, Section 4.3.
"RFC 1267, Section 4.3." RFC 1267, Section 5."
::= { bgpPathAttrEntry 2 } ::= { bgpPathAttrEntry 3 }
bgpPathAttrOrigin OBJECT-TYPE bgpPathAttrASPath OBJECT-TYPE
SYNTAX INTEGER { SYNTAX OCTET STRING (SIZE (2..255))
igp(1),-- networks are interior MAX-ACCESS read-only
egp(2),-- networks learned via the STATUS obsolete
-- EGP protocol DESCRIPTION
incomplete(3) -- networks that "The set of ASes that must be traversed to reach
-- are learned by some other the network. This object is probably best
-- means represented as SEQUENCE OF INTEGER. For SMI
} compatibility, though, it is represented as
MAX-ACCESS read-only OCTET STRING. Each AS is represented as a pair
STATUS obsolete of octets according to the following algorithm:
DESCRIPTION
"The ultimate origin of the path information."
REFERENCE
"RFC 1267, Section 4.3.
RFC 1267, Section 5."
::= { bgpPathAttrEntry 3 }
bgpPathAttrASPath OBJECT-TYPE first-byte-of-pair = ASNumber / 256;
SYNTAX OCTET STRING (SIZE (2..255)) second-byte-of-pair = ASNumber & 255;"
MAX-ACCESS read-only REFERENCE
STATUS obsolete "RFC 1267, Section 4.3.
DESCRIPTION RFC 1267, Section 5."
"The set of ASs that must be traversed to reach ::= { bgpPathAttrEntry 4 }
the network. This object is probably best
represented as SEQUENCE OF INTEGER. For SMI
compatibility, though, it is represented as
OCTET STRING. Each AS is represented as a pair
of octets according to the following algorithm:
first-byte-of-pair = ASNumber / 256; bgpPathAttrNextHop OBJECT-TYPE
second-byte-of-pair = ASNumber & 255;" SYNTAX IpAddress
REFERENCE MAX-ACCESS read-only
"RFC 1267, Section 4.3. STATUS obsolete
RFC 1267, Section 5." DESCRIPTION
::= { bgpPathAttrEntry 4 } "The address of the border router that should
bgpPathAttrNextHop OBJECT-TYPE be used for the destination network."
SYNTAX IpAddress REFERENCE
MAX-ACCESS read-only "RFC 1267, Section 4.3.
STATUS obsolete RFC 1267, Section 5."
DESCRIPTION ::= { bgpPathAttrEntry 5 }
"The address of the border router that should
be used for the destination network."
REFERENCE
"RFC 1267, Section 4.3.
RFC 1267, Section 5."
::= { bgpPathAttrEntry 5 }
bgpPathAttrInterASMetric OBJECT-TYPE bgpPathAttrInterASMetric OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The optional inter-AS metric. If this "The optional inter-AS metric. If this
attribute has not been provided for this route, attribute has not been provided for this route,
the value for this object is 0." the value for this object is 0."
REFERENCE REFERENCE
"RFC 1267, Section 4.3. "RFC 1267, Section 4.3.
RFC 1267, Section 5." RFC 1267, Section 5."
::= { bgpPathAttrEntry 6 } ::= { bgpPathAttrEntry 6 }
-- BGP-4 Received Path Attribute Table. This table -- BGP-4 Received Path Attribute Table. This table
-- contains, one entry per path to a network, path -- contains one entry per path to a network, and path
-- attributes received from all peers running BGP-4. -- attributes received from all peers running BGP-4.
bgp4PathAttrTable OBJECT-TYPE bgp4PathAttrTable OBJECT-TYPE
SYNTAX SEQUENCE OF Bgp4PathAttrEntry SYNTAX SEQUENCE OF Bgp4PathAttrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BGP-4 Received Path Attribute Table "The BGP-4 Received Path Attribute Table
contains information about paths to contains information about paths to
destination networks received from all destination networks, received from all
BGP4 peers." BGP4 peers."
::= { bgp 6 } ::= { bgp 6 }
bgp4PathAttrEntry OBJECT-TYPE bgp4PathAttrEntry OBJECT-TYPE
SYNTAX Bgp4PathAttrEntry SYNTAX Bgp4PathAttrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a path to a network." "Information about a path to a network."
INDEX { bgp4PathAttrIpAddrPrefix, INDEX { bgp4PathAttrIpAddrPrefix,
bgp4PathAttrIpAddrPrefixLen, bgp4PathAttrIpAddrPrefixLen,
bgp4PathAttrPeer } bgp4PathAttrPeer }
::= { bgp4PathAttrTable 1 } ::= { bgp4PathAttrTable 1 }
Bgp4PathAttrEntry ::= SEQUENCE { Bgp4PathAttrEntry ::= SEQUENCE {
bgp4PathAttrPeer bgp4PathAttrPeer
IpAddress, IpAddress,
bgp4PathAttrIpAddrPrefixLen bgp4PathAttrIpAddrPrefixLen
Integer32, Integer32,
bgp4PathAttrIpAddrPrefix bgp4PathAttrIpAddrPrefix
IpAddress, IpAddress,
bgp4PathAttrOrigin bgp4PathAttrOrigin
INTEGER, INTEGER,
bgp4PathAttrASPathSegment
OCTET STRING,
bgp4PathAttrNextHop
IpAddress,
bgp4PathAttrMultiExitDisc
Integer32,
bgp4PathAttrLocalPref
Integer32,
bgp4PathAttrAtomicAggregate
INTEGER,
bgp4PathAttrAggregatorAS
Integer32,
bgp4PathAttrAggregatorAddr
IpAddress,
bgp4PathAttrCalcLocalPref
Integer32,
bgp4PathAttrBest
INTEGER,
bgp4PathAttrUnknown
OCTET STRING
}
bgp4PathAttrPeer OBJECT-TYPE bgp4PathAttrASPathSegment
SYNTAX IpAddress OCTET STRING,
MAX-ACCESS read-only bgp4PathAttrNextHop
STATUS current IpAddress,
DESCRIPTION bgp4PathAttrMultiExitDisc
"The IP address of the peer where the path Integer32,
information was learned." bgp4PathAttrLocalPref
::= { bgp4PathAttrEntry 1 } Integer32,
bgp4PathAttrAtomicAggregate
INTEGER,
bgp4PathAttrAggregatorAS
Integer32,
bgp4PathAttrAggregatorAddr
IpAddress,
bgp4PathAttrCalcLocalPref
Integer32,
bgp4PathAttrBest
INTEGER,
bgp4PathAttrUnknown
OCTET STRING
}
bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE bgp4PathAttrPeer OBJECT-TYPE
SYNTAX Integer32 (0..32) SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Length in bits of the IP address prefix in "The IP address of the peer where the path
the Network Layer Reachability information was learned."
Information field." ::= { bgp4PathAttrEntry 1 }
::= { bgp4PathAttrEntry 2 }
bgp4PathAttrIpAddrPrefix OBJECT-TYPE bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE
SYNTAX IpAddress SYNTAX Integer32 (0..32)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An IP address prefix in the Network Layer "Length in bits of the IP address prefix in
Reachability Information field. This object the Network Layer Reachability
is an IP address containing the prefix with Information field."
length specified by ::= { bgp4PathAttrEntry 2 }
bgp4PathAttrIpAddrPrefixLen.
Any bits beyond the length specified by
bgp4PathAttrIpAddrPrefixLen are zeroed."
REFERENCE
"RFC yyyy, Section 4.3."
::= { bgp4PathAttrEntry 3 }
bgp4PathAttrOrigin OBJECT-TYPE bgp4PathAttrIpAddrPrefix OBJECT-TYPE
SYNTAX INTEGER { SYNTAX IpAddress
igp(1),-- networks are interior MAX-ACCESS read-only
egp(2),-- networks learned via the STATUS current
-- EGP protocol DESCRIPTION
incomplete(3) -- networks that "An IP address prefix in the Network Layer
-- are learned by some other Reachability Information field. This object
-- means is an IP address containing the prefix with
} length specified by
MAX-ACCESS read-only bgp4PathAttrIpAddrPrefixLen.
STATUS current Any bits beyond the length specified by
DESCRIPTION bgp4PathAttrIpAddrPrefixLen are zeroed."
"The ultimate origin of the path REFERENCE
information." "RFC 4271, Section 4.3."
REFERENCE ::= { bgp4PathAttrEntry 3 }
"RFC yyyy, Section 4.3.
RFC yyyy, Section 5.1.1." bgp4PathAttrOrigin OBJECT-TYPE
::= { bgp4PathAttrEntry 4 } SYNTAX INTEGER {
igp(1),-- networks are interior
egp(2),-- networks learned via the
-- EGP protocol
incomplete(3) -- networks that
-- are learned by some other
-- means
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The ultimate origin of the path
information."
REFERENCE
"RFC 4271, Section 4.3.
RFC 4271, Section 5.1.1."
::= { bgp4PathAttrEntry 4 }
bgp4PathAttrASPathSegment OBJECT-TYPE bgp4PathAttrASPathSegment OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (2..255)) SYNTAX OCTET STRING (SIZE (2..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sequence of AS path segments. Each AS "The sequence of AS path segments. Each AS
path segment is represented by a triple path segment is represented by a triple
<type, length, value>. <type, length, value>.
The type is a 1-octet field which has two The type is a 1-octet field that has two
possible values: possible values:
1 AS_SET: unordered set of ASs a 1 AS_SET: unordered set of ASes that a
route in the UPDATE message route in the UPDATE message
has traversed has traversed
2 AS_SEQUENCE: ordered set of ASs 2 AS_SEQUENCE: ordered set of ASes that
a route in the UPDATE message a route in the UPDATE message
has traversed. has traversed.
The length is a 1-octet field containing the The length is a 1-octet field containing the
number of ASs in the value field. number of ASes in the value field.
The value field contains one or more AS The value field contains one or more AS
numbers, each AS is represented in the octet numbers. Each AS is represented in the octet
string as a pair of octets according to the string as a pair of octets according to the
following algorithm: following algorithm:
first-byte-of-pair = ASNumber / 256; first-byte-of-pair = ASNumber / 256;
second-byte-of-pair = ASNumber & 255; second-byte-of-pair = ASNumber & 255;
Known Issues: Known Issues:
o BGP Confederations will result in o BGP Confederations will result in
a value of either 3 or 4. a type of either 3 or 4.
o An AS Path may be longer than 255 octets. o An AS Path may be longer than 255 octets.
This may result in this object containing This may result in this object containing
a truncated AS Path." a truncated AS Path."
REFERENCE REFERENCE
"RFC yyyy, Section 4.3. "RFC 4271, Section 4.3.
RFC yyyy, Section 5.1.2." RFC 4271, Section 5.1.2."
::= { bgp4PathAttrEntry 5 } ::= { bgp4PathAttrEntry 5 }
bgp4PathAttrNextHop OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address of the border router that
should be used for the destination
network. This address is the nexthop
address received in the UPDATE packet."
REFERENCE
"RFC yyyy, Section 4.3.
RFC yyyy, Section 5.1.3."
::= { bgp4PathAttrEntry 6 }
bgp4PathAttrMultiExitDisc OBJECT-TYPE bgp4PathAttrNextHop OBJECT-TYPE
SYNTAX Integer32 (-1..2147483647) SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This metric is used to discriminate "The address of the border router that
between multiple exit points to an should be used for the destination
adjacent autonomous system. A value of -1 network. This address is the NEXT_HOP
indicates the absence of this attribute. address received in the UPDATE packet."
REFERENCE
"RFC 4271, Section 4.3.
RFC 4271, Section 5.1.3."
::= { bgp4PathAttrEntry 6 }
Known Issues: bgp4PathAttrMultiExitDisc OBJECT-TYPE
o The BGP-4 specification uses an SYNTAX Integer32 (-1..2147483647)
unsigned 32 bit number and thus this MAX-ACCESS read-only
object cannot represent the full STATUS current
range of the protocol." DESCRIPTION
REFERENCE "This metric is used to discriminate
"RFC yyyy, Section 4.3. between multiple exit points to an
RFC yyyy, Section 5.1.4." adjacent autonomous system. A value of -1
::= { bgp4PathAttrEntry 7 } indicates the absence of this attribute.
bgp4PathAttrLocalPref OBJECT-TYPE Known Issues:
SYNTAX Integer32 (-1..2147483647) o The BGP-4 specification uses an
MAX-ACCESS read-only unsigned 32 bit number. Thus, this
STATUS current object cannot represent the full
DESCRIPTION range of the protocol."
"The originating BGP4 speaker's degree of REFERENCE
preference for an advertised route. A "RFC 4271, Section 4.3.
value of -1 indicates the absence of this RFC 4271, Section 5.1.4."
attribute. ::= { bgp4PathAttrEntry 7 }
Known Issues: bgp4PathAttrLocalPref OBJECT-TYPE
o The BGP-4 specification uses an SYNTAX Integer32 (-1..2147483647)
unsigned 32 bit number and thus this MAX-ACCESS read-only
object cannot represent the full STATUS current
range of the protocol." DESCRIPTION
REFERENCE "The originating BGP4 speaker's degree of
"RFC yyyy, Section 4.3. preference for an advertised route. A
RFC yyyy, Section 5.1.5." value of -1 indicates the absence of this
::= { bgp4PathAttrEntry 8 } attribute.
bgp4PathAttrAtomicAggregate OBJECT-TYPE Known Issues:
SYNTAX INTEGER { o The BGP-4 specification uses an
lessSpecificRouteNotSelected(1), unsigned 32 bit number and thus this
-- Typo corrected from RFC 1657 object cannot represent the full
lessSpecificRouteSelected(2) range of the protocol."
} REFERENCE
MAX-ACCESS read-only "RFC 4271, Section 4.3.
STATUS current RFC 4271, Section 5.1.5."
DESCRIPTION ::= { bgp4PathAttrEntry 8 }
"If the ATOMIC_AGGREGATE attribute is present
in the Path Attributes then this object MUST
have a value of 'lessSpecificRouteNotSelected'.
If the ATOMIC_AGGREGATE attribute is missing bgp4PathAttrAtomicAggregate OBJECT-TYPE
in the Path Attributes then this object MUST SYNTAX INTEGER {
have a value of 'lessSpecificRouteSelected'. lessSpecificRouteNotSelected(1),
-- Typo corrected from RFC 1657
lessSpecificRouteSelected(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the ATOMIC_AGGREGATE attribute is present
in the Path Attributes then this object MUST
have a value of 'lessSpecificRouteNotSelected'.
Note that ATOMIC_AGGREGATE is now a primarily If the ATOMIC_AGGREGATE attribute is missing
informational attribute." in the Path Attributes then this object MUST
REFERENCE have a value of 'lessSpecificRouteSelected'.
"RFC yyyy, Sections 5.1.6 and 9.1.4."
::= { bgp4PathAttrEntry 9 }
bgp4PathAttrAggregatorAS OBJECT-TYPE Note that ATOMIC_AGGREGATE is now a primarily
SYNTAX Integer32 (0..65535) informational attribute."
MAX-ACCESS read-only REFERENCE
STATUS current "RFC 4271, Sections 5.1.6 and 9.1.4."
DESCRIPTION
"The AS number of the last BGP4 speaker that
performed route aggregation. A value of
zero (0) indicates the absence of this
attribute.
Note that propagation of AS of zero is illegal ::= { bgp4PathAttrEntry 9 }
in the Internet."
REFERENCE
"RFC yyyy, Section 5.1.7.
RFC yyyy, Section 9.2.2.2."
::= { bgp4PathAttrEntry 10 }
bgp4PathAttrAggregatorAddr OBJECT-TYPE bgp4PathAttrAggregatorAS OBJECT-TYPE
SYNTAX IpAddress SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the last BGP4 speaker "The AS number of the last BGP4 speaker that
that performed route aggregation. A performed route aggregation. A value of
value of 0.0.0.0 indicates the absence zero (0) indicates the absence of this
of this attribute." attribute.
REFERENCE
"RFC yyyy, Section 5.1.7.
RFC yyyy, Section 9.2.2.2."
::= { bgp4PathAttrEntry 11 }
bgp4PathAttrCalcLocalPref OBJECT-TYPE Note that propagation of AS of zero is illegal
SYNTAX Integer32 (-1..2147483647) in the Internet."
MAX-ACCESS read-only REFERENCE
STATUS current "RFC 4271, Section 5.1.7.
DESCRIPTION RFC 4271, Section 9.2.2.2."
"The degree of preference calculated by the ::= { bgp4PathAttrEntry 10 }
receiving BGP4 speaker for an advertised
route. A value of -1 indicates the
absence of this attribute.
Known Issues: bgp4PathAttrAggregatorAddr OBJECT-TYPE
o The BGP-4 specification uses an SYNTAX IpAddress
unsigned 32 bit number and thus this MAX-ACCESS read-only
object cannot represent the full STATUS current
range of the protocol." DESCRIPTION
REFERENCE "The IP address of the last BGP4 speaker
"RFC yyyy, Section 9.1.1." that performed route aggregation. A
::= { bgp4PathAttrEntry 12 } value of 0.0.0.0 indicates the absence
of this attribute."
REFERENCE
"RFC 4271, Section 5.1.7.
RFC 4271, Section 9.2.2.2."
::= { bgp4PathAttrEntry 11 }
bgp4PathAttrBest OBJECT-TYPE bgp4PathAttrCalcLocalPref OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Integer32 (-1..2147483647)
false(1),-- not chosen as best route MAX-ACCESS read-only
true(2) -- chosen as best route STATUS current
} DESCRIPTION
MAX-ACCESS read-only "The degree of preference calculated by the
STATUS current receiving BGP4 speaker for an advertised
DESCRIPTION route. A value of -1 indicates the
"An indication of whether or not this route absence of this attribute.
was chosen as the best BGP4 route for this
destination."
REFERENCE
"RFC yyyy, Section 9.1.2."
::= { bgp4PathAttrEntry 13 }
bgp4PathAttrUnknown OBJECT-TYPE Known Issues:
SYNTAX OCTET STRING (SIZE(0..255)) o The BGP-4 specification uses an
MAX-ACCESS read-only unsigned 32 bit number and thus this
STATUS current object cannot represent the full
DESCRIPTION range of the protocol."
"One or more path attributes not understood by
this BGP4 speaker.
Path attributes are recorded in the Update Path REFERENCE
attribute format of type, length, value. "RFC 4271, Section 9.1.1."
::= { bgp4PathAttrEntry 12 }
Size zero (0) indicates the absence of such bgp4PathAttrBest OBJECT-TYPE
attributes. SYNTAX INTEGER {
false(1),-- not chosen as best route
true(2) -- chosen as best route
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of whether this route
was chosen as the best BGP4 route for this
destination."
REFERENCE
"RFC 4271, Section 9.1.2."
::= { bgp4PathAttrEntry 13 }
Octets beyond the maximum size, if any, are not bgp4PathAttrUnknown OBJECT-TYPE
recorded by this object. SYNTAX OCTET STRING (SIZE(0..255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"One or more path attributes not understood by
this BGP4 speaker.
Known Issues: Path attributes are recorded in the Update Path
o Attributes understood by this speaker, but not attribute format of type, length, value.
represented in this MIB, are unavailable to
the agent."
::= { bgp4PathAttrEntry 14 }
-- Traps. Size zero (0) indicates the absence of such
attributes.
-- Note that in RFC 1657, bgpTraps was incorrectly Octets beyond the maximum size, if any, are not
-- assigned a value of { bgp 7 } and each of the recorded by this object.
-- traps had the bgpPeerRemoteAddr object inappropriately
-- removed from their OBJECTS clause. The following
-- definitions restore the semantics of the traps as
-- they were initially defined in RFC 1269.
bgpNotification OBJECT IDENTIFIER ::= { bgp 0 } Known Issues:
o Attributes understood by this speaker, but not
represented in this MIB, are unavailable to
the agent."
REFERENCE
"RFC 4271, Section 5."
::= { bgp4PathAttrEntry 14 }
bgpEstablishedNotification NOTIFICATION-TYPE -- Traps.
OBJECTS { bgpPeerRemoteAddr, -- Note that in RFC 1657, bgpTraps was incorrectly
bgpPeerLastError, -- assigned a value of { bgp 7 } and each of the
bgpPeerState } -- traps had the bgpPeerRemoteAddr object inappropriately
STATUS current -- removed from their OBJECTS clause. The following
DESCRIPTION -- definitions restore the semantics of the traps as
"The BGP Established event is generated when -- they were initially defined in RFC 1269.
the BGP FSM enters the ESTABLISHED state.
This Notification replaces the bgpEstablished bgpNotification OBJECT IDENTIFIER ::= { bgp 0 }
Notification."
::= { bgpNotification 1 }
bgpBackwardTransNotification NOTIFICATION-TYPE bgpEstablishedNotification NOTIFICATION-TYPE
OBJECTS { bgpPeerRemoteAddr, OBJECTS { bgpPeerRemoteAddr,
bgpPeerLastError, bgpPeerLastError,
bgpPeerState } bgpPeerState }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BGPBackwardTransNotification Event is "The bgpEstablishedNotification event is generated
generated when the BGP FSM moves from a higher when the BGP FSM enters the established state.
numbered state to a lower numbered state.
This Notification replaces the This Notification replaces the bgpEstablished
bgpBackwardsTransition Notification." Notification."
::= { bgpNotification 2 } ::= { bgpNotification 1 }
-- { bgp 7 } is deprecated. Do not allocate new objects or bgpBackwardTransNotification NOTIFICATION-TYPE
-- notifications underneath this branch. OBJECTS { bgpPeerRemoteAddr,
bgpPeerLastError,
bgpPeerState }
STATUS current
DESCRIPTION
"The bgpBackwardTransNotification event is
generated when the BGP FSM moves from a higher
numbered state to a lower numbered state.
bgpTraps OBJECT IDENTIFIER ::= { bgp 7 } -- deprecated This Notification replaces the
bgpBackwardsTransition Notification."
::= { bgpNotification 2 }
bgpEstablished NOTIFICATION-TYPE -- { bgp 7 } is deprecated. Do not allocate new objects or
OBJECTS { bgpPeerLastError, -- notifications underneath this branch.
bgpPeerState }
STATUS deprecated
DESCRIPTION
"The BGP Established event is generated when
the BGP FSM enters the ESTABLISHED state.
This Notification has been replaced by the bgpTraps OBJECT IDENTIFIER ::= { bgp 7 } -- deprecated
bgpEstablishedNotification Notification."
::= { bgpTraps 1 }
bgpBackwardTransition NOTIFICATION-TYPE bgpEstablished NOTIFICATION-TYPE
OBJECTS { bgpPeerLastError, OBJECTS { bgpPeerLastError,
bgpPeerState } bgpPeerState }
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The BGPBackwardTransition Event is generated "The bgpEstablished event is generated when
when the BGP FSM moves from a higher numbered the BGP FSM enters the established state.
state to a lower numbered state.
This Notification has been replaced by the This Notification has been replaced by the
bgpBackwardTransNotification Notification." bgpEstablishedNotification Notification."
::= { bgpTraps 2 }
-- Conformance information ::= { bgpTraps 1 }
bgp4MIBConformance OBJECT IDENTIFIER bgpBackwardTransition NOTIFICATION-TYPE
::= { bgp 8 } OBJECTS { bgpPeerLastError,
bgp4MIBCompliances OBJECT IDENTIFIER bgpPeerState }
::= { bgp4MIBConformance 1 } STATUS deprecated
bgp4MIBGroups OBJECT IDENTIFIER DESCRIPTION
::= { bgp4MIBConformance 2 } "The bgpBackwardTransition event is generated
when the BGP FSM moves from a higher numbered
state to a lower numbered state.
-- Compliance statements This Notification has been replaced by the
bgpBackwardTransNotification Notification."
::= { bgpTraps 2 }
bgp4MIBCompliance MODULE-COMPLIANCE -- Conformance information
STATUS current
DESCRIPTION
"The compliance statement for entities which
implement the BGP4 mib."
MODULE -- this module
MANDATORY-GROUPS { bgp4MIBGlobalsGroup,
bgp4MIBPeerGroup,
bgp4MIBPathAttrGroup }
GROUP bgp4MIBNotificationGroup
DESCRIPTION
"Implementation of BGP Notifications are
completely optional in this MIB."
::= { bgp4MIBCompliances 1 }
bgp4MIBDeprecatedCompliances MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement documenting deprecated
objects in the BGP4 mib."
MODULE -- this module
GROUP bgp4MIBTrapGroup
DESCRIPTION
"Group containing TRAP objects that were
improperly converted from SMIv1 in RFC 1657.
The proper semantics have been restored
with the objects in bgp4MIBNotificationGroup."
::= { bgp4MIBCompliances 2 }
bgp4MIBObsoleteCompliances MODULE-COMPLIANCE bgp4MIBConformance OBJECT IDENTIFIER
STATUS obsolete ::= { bgp 8 }
DESCRIPTION bgp4MIBCompliances OBJECT IDENTIFIER
"The compliance statement documenting obsolete ::= { bgp4MIBConformance 1 }
objects in the BGP4 mib." bgp4MIBGroups OBJECT IDENTIFIER
MODULE -- this module ::= { bgp4MIBConformance 2 }
GROUP bgpRcvdPathAttrGroup
DESCRIPTION
"Group containing objects relevant to BGP-3
and earlier objects."
::= { bgp4MIBCompliances 3 }
-- Units of conformance -- Compliance statements
bgp4MIBGlobalsGroup OBJECT-GROUP bgp4MIBCompliance MODULE-COMPLIANCE
OBJECTS { bgpVersion, STATUS current
bgpLocalAs, DESCRIPTION
bgpIdentifier } "The compliance statement for entities which
STATUS current implement the BGP4 mib."
DESCRIPTION MODULE -- this module
"A collection of objects providing MANDATORY-GROUPS { bgp4MIBGlobalsGroup,
information on global BGP state." bgp4MIBPeerGroup,
::= { bgp4MIBGroups 1 } bgp4MIBPathAttrGroup }
GROUP bgp4MIBNotificationGroup
DESCRIPTION
"Implementation of BGP Notifications are
completely optional in this MIB."
::= { bgp4MIBCompliances 1 }
bgp4MIBPeerGroup OBJECT-GROUP bgp4MIBDeprecatedCompliances MODULE-COMPLIANCE
OBJECTS { bgpPeerIdentifier, STATUS deprecated
bgpPeerState, DESCRIPTION
bgpPeerAdminStatus, "The compliance statement documenting deprecated
bgpPeerNegotiatedVersion, objects in the BGP4 mib."
bgpPeerLocalAddr, MODULE -- this module
bgpPeerLocalPort, GROUP bgp4MIBTrapGroup
bgpPeerRemoteAddr, DESCRIPTION
bgpPeerRemotePort, "Group containing TRAP objects that were
bgpPeerRemoteAs, improperly converted from SMIv1 in RFC 1657.
bgpPeerInUpdates, The proper semantics have been restored
bgpPeerOutUpdates, with the objects in bgp4MIBNotificationGroup."
bgpPeerInTotalMessages, ::= { bgp4MIBCompliances 2 }
bgpPeerOutTotalMessages,
bgpPeerLastError,
bgpPeerFsmEstablishedTransitions,
bgpPeerFsmEstablishedTime,
bgpPeerConnectRetryInterval,
bgpPeerHoldTime,
bgpPeerKeepAlive,
bgpPeerHoldTimeConfigured,
bgpPeerKeepAliveConfigured,
bgpPeerMinASOriginationInterval,
bgpPeerMinRouteAdvertisementInterval,
bgpPeerInUpdateElapsedTime }
STATUS current
DESCRIPTION
"A collection of objects for managing
BGP peers."
::= { bgp4MIBGroups 2 }
bgpRcvdPathAttrGroup OBJECT-GROUP bgp4MIBObsoleteCompliances MODULE-COMPLIANCE
OBJECTS { bgpPathAttrPeer, STATUS obsolete
bgpPathAttrDestNetwork, DESCRIPTION
bgpPathAttrOrigin, "The compliance statement documenting obsolete
bgpPathAttrASPath, objects in the BGP4 mib."
bgpPathAttrNextHop, MODULE -- this module
bgpPathAttrInterASMetric } GROUP bgpRcvdPathAttrGroup
STATUS obsolete DESCRIPTION
DESCRIPTION "Group containing objects relevant to BGP-3
"A collection of objects for managing BGP-3 and and earlier objects."
earlier path entries. ::= { bgp4MIBCompliances 3 }
This conformance group, like BGP-3, is obsolete." -- Units of conformance
::= { bgp4MIBGroups 3 }
bgp4MIBPathAttrGroup OBJECT-GROUP bgp4MIBGlobalsGroup OBJECT-GROUP
OBJECTS { bgp4PathAttrPeer, OBJECTS { bgpVersion,
bgp4PathAttrIpAddrPrefixLen, bgpLocalAs,
bgp4PathAttrIpAddrPrefix, bgpIdentifier }
bgp4PathAttrOrigin, STATUS current
bgp4PathAttrASPathSegment, DESCRIPTION
bgp4PathAttrNextHop, "A collection of objects providing
bgp4PathAttrMultiExitDisc, information on global BGP state."
bgp4PathAttrLocalPref, ::= { bgp4MIBGroups 1 }
bgp4PathAttrAtomicAggregate,
bgp4PathAttrAggregatorAS,
bgp4PathAttrAggregatorAddr,
bgp4PathAttrCalcLocalPref,
bgp4PathAttrBest,
bgp4PathAttrUnknown }
STATUS current
DESCRIPTION
"A collection of objects for managing
BGP path entries."
::= { bgp4MIBGroups 4 }
bgp4MIBTrapGroup NOTIFICATION-GROUP bgp4MIBPeerGroup OBJECT-GROUP
NOTIFICATIONS { bgpEstablished, OBJECTS { bgpPeerIdentifier,
bgpBackwardTransition } bgpPeerState,
STATUS deprecated bgpPeerAdminStatus,
DESCRIPTION bgpPeerNegotiatedVersion,
"A collection of notifications for signaling bgpPeerLocalAddr,
changes in BGP peer relationships. bgpPeerLocalPort,
bgpPeerRemoteAddr,
bgpPeerRemotePort,
bgpPeerRemoteAs,
bgpPeerInUpdates,
bgpPeerOutUpdates,
bgpPeerInTotalMessages,
bgpPeerOutTotalMessages,
bgpPeerLastError,
bgpPeerFsmEstablishedTransitions,
bgpPeerFsmEstablishedTime,
bgpPeerConnectRetryInterval,
bgpPeerHoldTime,
bgpPeerKeepAlive,
bgpPeerHoldTimeConfigured,
bgpPeerKeepAliveConfigured,
bgpPeerMinASOriginationInterval,
bgpPeerMinRouteAdvertisementInterval,
bgpPeerInUpdateElapsedTime }
STATUS current
DESCRIPTION
"A collection of objects for managing
BGP peers."
::= { bgp4MIBGroups 2 }
Obsoleted by bgp4MIBNotificationGroup" bgpRcvdPathAttrGroup OBJECT-GROUP
::= { bgp4MIBGroups 5 } OBJECTS { bgpPathAttrPeer,
bgpPathAttrDestNetwork,
bgpPathAttrOrigin,
bgpPathAttrASPath,
bgpPathAttrNextHop,
bgpPathAttrInterASMetric }
STATUS obsolete
DESCRIPTION
"A collection of objects for managing BGP-3 and
earlier path entries.
bgp4MIBNotificationGroup NOTIFICATION-GROUP This conformance group, like BGP-3, is obsolete."
NOTIFICATIONS { bgpEstablishedNotification, ::= { bgp4MIBGroups 3 }
bgpBackwardTransNotification }
STATUS current
DESCRIPTION
"A collection of notifications for signaling
changes in BGP peer relationships.
Obsoletes bgp4MIBTrapGroup." bgp4MIBPathAttrGroup OBJECT-GROUP
::= { bgp4MIBGroups 6 } OBJECTS { bgp4PathAttrPeer,
bgp4PathAttrIpAddrPrefixLen,
bgp4PathAttrIpAddrPrefix,
bgp4PathAttrOrigin,
bgp4PathAttrASPathSegment,
bgp4PathAttrNextHop,
bgp4PathAttrMultiExitDisc,
bgp4PathAttrLocalPref,
bgp4PathAttrAtomicAggregate,
bgp4PathAttrAggregatorAS,
bgp4PathAttrAggregatorAddr,
bgp4PathAttrCalcLocalPref,
bgp4PathAttrBest,
bgp4PathAttrUnknown }
STATUS current
DESCRIPTION
"A collection of objects for managing
BGP path entries."
END ::= { bgp4MIBGroups 4 }
5. Intellectual Property bgp4MIBTrapGroup NOTIFICATION-GROUP
NOTIFICATIONS { bgpEstablished,
bgpBackwardTransition }
STATUS deprecated
DESCRIPTION
"A collection of notifications for signaling
changes in BGP peer relationships.
The IETF takes no position regarding the validity or scope of any Obsoleted by bgp4MIBNotificationGroup"
intellectual property or other rights that might be claimed to ::= { bgp4MIBGroups 5 }
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-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.
The IETF invites any interested party to bring to its attention any bgp4MIBNotificationGroup NOTIFICATION-GROUP
copyrights, patents or patent applications, or other proprietary NOTIFICATIONS { bgpEstablishedNotification,
rights which may cover technology that may be required to practice bgpBackwardTransNotification }
this standard. Please address the information to the IETF Executive STATUS current
Director. DESCRIPTION
"A collection of notifications for signaling
changes in BGP peer relationships.
6. Security Considerations Obsoletes bgp4MIBTrapGroup."
::= { bgp4MIBGroups 6 }
This MIB relates to a system providing inter-domain routing. As END
5. Security Considerations
This MIB relates to a system providing inter-domain routing. As
such, improper manipulation of the objects represented by this MIB such, improper manipulation of the objects represented by this MIB
may result in denial of service to a large number of end-users. 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 There are several management objects defined in this MIB that have a
MAX-ACCESS clause of read-write and/or read-create. Such objects MAX-ACCESS clause of read-write and/or read-create. Such objects
should be considered sensitive or vulnerable in most network should be considered sensitive or vulnerable in most network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These objects include: network operations. These objects include:
o bgpPeerAdminStatus o bgpPeerAdminStatus
Improper change of bgpPeerAdminStatus from start to stop can Improper change of bgpPeerAdminStatus, from start to stop, can
cause significant disruption of the connectivity to those cause significant disruption of the connectivity to those
portions of the Internet reached via the applicable remote BGP portions of the Internet reached via the applicable remote BGP
peer. peer.
o bgpPeerConnectRetryInterval o bgpPeerConnectRetryInterval
Improper change of this object can cause connections to be Improper change of this object can cause connections to be
disrupted for extremely long time periods when otherwise they disrupted for extremely long time periods when otherwise they
would be restored in a relatively short period of time. would be restored in a relatively short period of time.
o bgpPeerHoldTimeConfigured, bgpPeerKeepAliveConfigured o bgpPeerHoldTimeConfigured, bgpPeerKeepAliveConfigured
Misconfiguration of these objects can make BGP sessions more Misconfiguration of these objects can make BGP sessions more
fragile and less resilient to denial of service attacks on the fragile and less resilient to denial of service attacks on the
inter-domain routing system. inter-domain routing system.
o bgpPeerMinASOriginationInterval, o bgpPeerMinASOriginationInterval,
bgpPeerMinRouteAdvertisementInterval bgpPeerMinRouteAdvertisementInterval
Misconfiguration of these objects may adversely affect global Misconfiguration of these objects may adversely affect global
Internet convergence of the routes advertised by this BGP Internet convergence of the routes advertised by this BGP
speaker. This may result in long-lived routing loops and speaker. This may result in long-lived routing loops and
blackholes for the portions of the Internet that utilize these blackholes for the portions of the Internet that utilize these
routes." routes.
There are a number of managed objects in this MIB that There are a number of managed objects in this MIB that contain
contain sensitive information regarding the operation of a network. sensitive information regarding the operation of a network. For
For example, a BGP peer's local and remote addresses might be example, a BGP peer's local and remote addresses might be sensitive
sensitive for ISPs who want to keep interface addresses on routers for ISPs who want to keep interface addresses on routers confidential
confidential to prevent router addresses used for a denial of service in order to prevent router addresses used for a denial of service
attack or spoofing. attack or spoofing.
Therefore, it is important in most environments to control read Therefore, it is important in most environments to control read
access to these objects and possibly to even encrypt the values of access to these objects and possibly to even encrypt the values of
these object when sending them over the network via SNMP. these object when sending them over the network via SNMP.
SNMPv1 by itself is not a secure environment. Even if the network SNMP versions prior to SNMPv3 did not include adequate security.
itself is secure (for example by using IPSec), there is still no Even if the network itself is secure (for example by using IPsec),
control as to who on the secure network is allowed to access and even then, there is no control as to who on the secure network is
GET/SET (read/change/create/delete) the objects in this MIB. allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is recommended that the implementers consider the security It is RECOMMENDED that implementers consider the security features as
features as provided by the SNMPv3 framework.[REF] Specifically, the provided by the SNMPv3 framework (see [RFC3410], section 8),
implementation and use of the User-based Security Model [REF] and the including full support for the SNMPv3 cryptographic mechanisms (for
View-based Access Control Model [REF] is recommended to provide authentication and privacy).
appropriate security controls.
It is then an operator/user responsibility to ensure that the SNMP Further, deployment of SNMP versions prior to SNMPv3 is NOT
entity giving access to an instance of this MIB, is properly RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
configured to give access to the objects only to those principals enable cryptographic security. It is then a customer/operator
(users) that have legitimate rights to indeed GET or SET responsibility to ensure that the SNMP entity giving access to an
(change/create/delete) them. instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
7. Acknowledgements 6. Acknowledgements
We would like to acknowledge the assistance of all the members of the We would like to acknowledge the assistance of all the members of the
Inter-Domain Routing Working Group, and particularly the following Inter-Domain Routing Working Group, and particularly the following
individuals: individuals:
Yakov Rekhter, Juniper Networks Yakov Rekhter, Juniper Networks
Rob Coltun, Redback Rob Coltun, Redback
Guy Almes, Internet2 Guy Almes, Internet2
Jeff Honig, BSDi Jeff Honig, BSDi
Marshall T. Rose, Dover Beach Consulting, Inc. Marshall T. Rose, Dover Beach Consulting, Inc.
skipping to change at page 35, line 36 skipping to change at page 30, line 38
Joel Halpern, CTO Longitude Systems, Inc. Joel Halpern, CTO Longitude Systems, Inc.
Nick Thille, RedBack Networks Nick Thille, RedBack Networks
Bert Wijnen, Lucent Bert Wijnen, Lucent
Shane Wright, NextHop Technologies Shane Wright, NextHop Technologies
Mike McFadden, Riverstone Networks, Inc. Mike McFadden, Riverstone Networks, Inc.
Jon Saperia, JDS Consulting, Inc. Jon Saperia, JDS Consulting, Inc.
Wayne Tackabury, Gold Wire Technology, Inc. Wayne Tackabury, Gold Wire Technology, Inc.
Bill Fenner, AT&T Research Bill Fenner, AT&T Research
RJ Atkinson, Extreme Networks RJ Atkinson, Extreme Networks
Dan Romascanu, Avaya Dan Romascanu, Avaya
Mathew Richardson, NextHop Technologies
The origin of this document is from RFC 1269 "Definitions of Managed The origin of this document is from RFC 1269 "Definitions of Managed
Objects for the Border Gateway Protocol (Version 3)" written by Steve Objects for the Border Gateway Protocol (Version 3)" written by Steve
Willis and John Burruss, which was updated by John Chu to support Willis and John Burruss, which was updated by John Chu to support
BGP-4 in RFC 1657. The editors wish to acknowledge the fine work of BGP-4 in RFC 1657. The editors wish to acknowledge the fine work of
these original authors. these original authors.
8. IANA Considerations 7. Normative References
This document presents no new IANA considerations. [BGP4] Rekhter, Y., Li, T., and S. Hares, Eds., "A Border
Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006.
9. Normative References [BGP4APP] Rekhter, Y. and P. Gross, "Application of the Border
Gateway Protocol in the Internet", RFC 1772, March 1995.
[BGP4] Rekhter, Y., Li, T., Hares, S., "A Border Gateway [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Protocol 4 (BGP-4)", RFC yyyy, zzzz 2004. "Structure of Management Information Version 2 (SMIv2)",
STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Textual Conventions for SMIv2", STD 58, RFC 2579, April
1999.
[BGP4APP] Rekhter, Y., Gross, P., "Application of the Border [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Gateway Protocol in the Internet", RFC 1772, March 1995. "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
Rose, M., and S. Waldbusser, "Structure of Management "Introduction and Applicability Statements for Internet-
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Standard Management Framework", RFC 3410, December 2002.
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Editors' Addresses
Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Jeffrey Haas
Rose, M., and S. Waldbusser, "Conformance Statements for NextHop Technologies
SMIv2", STD 58, RFC 2580, April 1999. 825 Victor's Way, Suite 100
Ann Arbor, MI 48103
10. Editors' Address Phone: +1 734 222-1600
Fax: +1 734 222-1602
EMail: jhaas@nexthop.com
Jeffrey Haas, Susan Hares Susan Hares
NextHop Technologies NextHop Technologies
825 Victor's Way, Suite 100 825 Victor's Way, Suite 100
Ann Arbor, MI 48103 Ann Arbor, MI 48103
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: skh@nexthop.com
skh@nexthop.com
11. Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved. Full Copyright Statement
This document and translations of it may be copied and furnished to Copyright (C) The Internet Society (2006).
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be This document is subject to the rights, licenses and restrictions
revoked by the Internet Society or its successors or assigns. contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein is provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 170 change blocks. 
1241 lines changed or deleted 1205 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/