draft-ietf-idr-bgp4-mib-14.txt   draft-ietf-idr-bgp4-mib-15.txt 
Network Working Group Editors of this version: Network Working Group Editors of this version:
INTERNET DRAFT J. Haas INTERNET DRAFT J. Haas
S. Hares S. Hares
NextHop Technologies NextHop Technologies
April 2004 August 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)
<draft-ietf-idr-bgp4-mib-14.txt> <draft-ietf-idr-bgp4-mib-15.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 RFC 2026. all provisions of Section 10 of RFC 2026.
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 1, line 40 skipping to change at page 1, line 40
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This memo is an extension to the SNMP MIB. It obsoletes RFC 1657 and This memo defines a portion of the Management Information Base (MIB)
RFC 1269. for use with network management protocols in the Internet community
In particular, it describes managed objects used for managing the
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 was converted to use the SNMPv2 SMI, as well introduced when the MIB module was converted to use the SMIv2
as updates references to the current SNMP framework documents. language. This memo also updates references to the current SNMP
framework documents.
This memo is intended to document deployed implementations of this This memo is intended to document deployed implementations of this
MIB in a historical context, provide clarifications of some items and MIB module in a historical context, provide clarifications of some
also note errors where the MIB fails to fully represent the BGP items and also note errors where the MIB module fails to fully
protocol. Work is currently in progress to replace this MIB with a represent the BGP protocol. Work is currently in progress to replace
new one representing the current state of the BGP protocol and its this MIB module with a new one representing the current state of the
extensions. BGP protocol and its extensions.
This document obsoletes RFC 1269 and RFC 1657.
Distribution of this memo is unlimited. Please forward comments to Distribution of this memo is unlimited. Please forward comments to
idr@ietf.org. idr@ietf.org.
Table of Contents Table of Contents
1. Introduction ................................................. 3 1. Introduction ................................................. 3
2. The Internet-Standard Management Framework ................... 3 2. The Internet-Standard Management Framework ................... 3
3. Overview ..................................................... 3 3. Overview ..................................................... 3
4. Definitions .................................................. 4 4. Definitions .................................................. 4
5. Intellectual Property ....................................... 30 5. Intellectual Property ....................................... 32
6. Security Considerations ..................................... 31 6. Security Considerations ..................................... 33
7. Acknowledgements ............................................ 33 7. Acknowledgements ............................................ 35
8. Normative References ........................................ 34 8. IANA Considerations ......................................... 36
9. Editors' Address ............................................ 35 9. Normative References ........................................ 36
10. Full Copyright Statement .................................... 35 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 [BGP, BGP4APP].
This memo obsoletes RFC 1657 and RFC 1269. This memo obsoletes RFC 1657 and RFC 1269.
skipping to change at page 4, line 17 skipping to change at page 4, line 17
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 "200404220000Z" LAST-UPDATED "200408310000Z"
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
skipping to change at page 4, line 40 skipping to change at page 4, line 40
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 (2004). This version
of this MIB module is part of RFC yyyy; see the RFC of this MIB module is part of RFC yyyy; see the RFC
itself for full legal notices." itself for full legal notices."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "200404220000Z" REVISION "200408310000Z"
DESCRIPTION DESCRIPTION
"Changes from RFC 1657: "Changes from RFC 1657:
1) Fixed the definitions of the traps to 1) Fixed the definitions of the notifications
make them equivalent to their initial to make them equivalent to their initial
definition in RFC 1269. definition in RFC 1269.
2) Added compliance and conformance info. 2) Added compliance and conformance info.
3) Updated information for the values of 3) Updated information for the values of
bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref,
bgp4PathAttrCalcLocalPref, bgp4PathAttrMultiExitDisc, bgp4PathAttrCalcLocalPref, bgp4PathAttrMultiExitDisc,
bgp4PathAttrASPathSegement. bgp4PathAttrASPathSegement.
4) Added additional clarification comments where 4) Added additional clarification comments where
needed. needed.
5) Noted where objects do not fully reflect 5) Noted where objects do not fully reflect
the protocol as Known Issues. the protocol as Known Issues.
6) Updated the DESCRIPTION for the 6) Updated the DESCRIPTION for the
bgp4PathAttrAtomicAggregate object. bgp4PathAttrAtomicAggregate object.
7) The following objects have had their DESCRIPTION 7) The following objects have had their DESCRIPTION
clause modified to remove the text that suggested clause modified to remove the text that suggested
(using "should" verb) to initialize the counter (using 'should' verb) to initialize the counter
to zero on a transition to the established state: to zero on a transition to the established state:
bgpPeerInUpdates, bgpPeerOutUpdates, bgpPeerInUpdates, bgpPeerOutUpdates,
bgpPeerInTotalMessages, bgpPeerOutTotalMessages bgpPeerInTotalMessages, bgpPeerOutTotalMessages
Those implementations that still do this are Those implementations that still do this are
still compliant with this new wording. still compliant with this new wording.
Appliciations should not assume counters to have Appliciations should not assume counters to have
started at zero. started at zero.
Published as RFC yyyy." Published as RFC yyyy."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
skipping to change at page 6, line 7 skipping to change at page 6, line 7
from this vector. Versions are identified from this vector. Versions are identified
via the string of bits contained within this via the string of bits contained within this
object. The first octet contains bits 0 to object. The first octet contains bits 0 to
7, the second octet contains bits 8 to 15, 7, the second octet contains bits 8 to 15,
and so on, with the most significant bit and so on, with the most significant bit
referring to the lowest bit number in the referring to the lowest bit number in the
octet (e.g., the MSB of the first octet octet (e.g., the MSB of the first octet
refers to bit 0). If a bit, i, is present refers to bit 0). If a bit, i, is present
and set, then the version (i+1) of the BGP and set, then the version (i+1) of the BGP
is supported." is supported."
REFERENCE
"RFC yyyy, Section 4.2."
::= { bgp 1 } ::= { bgp 1 }
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
bgpLocalAs OBJECT-TYPE bgpLocalAs OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The local autonomous system number." "The local autonomous system number."
REFERENCE
"RFC yyyy, Section 4.2, 'My Autonomous System'."
::= { bgp 2 } ::= { bgp 2 }
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
-- BGP Peer table. This table contains, one entry per -- BGP Peer table. This table contains, one entry per
-- BGP peer, information about the BGP peer. -- BGP peer, information about the BGP peer.
bgpPeerTable OBJECT-TYPE bgpPeerTable OBJECT-TYPE
SYNTAX SEQUENCE OF BgpPeerEntry SYNTAX SEQUENCE OF BgpPeerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"BGP peer table. This table contains, "BGP peer table. This table contains,
skipping to change at page 8, line 10 skipping to change at page 8, line 15
bgpPeerIdentifier OBJECT-TYPE bgpPeerIdentifier OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BGP Identifier of this entry's BGP peer. "The BGP Identifier of this entry's BGP peer.
This entry MUST be 0.0.0.0 unless the This entry MUST be 0.0.0.0 unless the
bgpPeerState is in the openconfirm or the bgpPeerState is in the openconfirm or the
established state." established state."
REFERENCE
"RFC yyyy, Section 4.2, 'BGP Identifier'."
::= { bgpPeerEntry 1 } ::= { bgpPeerEntry 1 }
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
bgpPeerState OBJECT-TYPE bgpPeerState 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 BGP peer connection state." "The BGP peer connection state."
REFERENCE
"RFC yyyy, Section 8.2.2."
::= { bgpPeerEntry 2 } ::= { bgpPeerEntry 2 }
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
bgpPeerAdminStatus OBJECT-TYPE bgpPeerAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
stop(1), stop(1),
start(2) start(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The desired state of the BGP connection. "The desired state of the BGP connection.
A transition from 'stop' to 'start' will cause A transition from 'stop' to 'start' will cause
skipping to change at page 8, line 38 skipping to change at page 9, line 4
SYNTAX INTEGER { SYNTAX INTEGER {
stop(1), stop(1),
start(2) start(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The desired state of the BGP connection. "The desired state of the BGP connection.
A transition from 'stop' to 'start' will cause A transition from 'stop' to 'start' will cause
the BGP Manual Start Event to be generated. the BGP Manual Start Event to be generated.
A transition from 'start' to 'stop' will cause A transition from 'start' to 'stop' will cause
the BGP Manual Stop Event to be generated. the BGP Manual Stop Event to be generated.
This parameter can be used to restart BGP peer This parameter can be used to restart BGP peer
connections. Care should be used in providing connections. Care should be used in providing
write access to this object without adequate write access to this object without adequate
authentication." authentication."
REFERENCE
"RFC yyyy, Section 8.1.2."
::= { bgpPeerEntry 3 } ::= { bgpPeerEntry 3 }
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
bgpPeerNegotiatedVersion OBJECT-TYPE bgpPeerNegotiatedVersion OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The negotiated version of BGP running between "The negotiated version of BGP running between
the two peers. the two peers.
This entry MUST be zero (0) unless the This entry MUST be zero (0) unless the
bgpPeerState is in the openconfirm or the bgpPeerState is in the openconfirm or the
established state. established state.
Note that legal values for this object are Note that legal values for this object are
between 0 and 255." between 0 and 255."
REFERENCE REFERENCE
"RFC yyyy, section 4.2." "RFC yyyy, Section 4.2.
RFC yyyy, Section 7."
::= { bgpPeerEntry 4 } ::= { bgpPeerEntry 4 }
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
bgpPeerLocalAddr OBJECT-TYPE bgpPeerLocalAddr OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The local IP address of this entry's BGP "The local IP address of this entry's BGP
skipping to change at page 10, line 23 skipping to change at page 10, line 37
reference to the standard MIB TCP reference to the standard MIB TCP
connection table." connection table."
::= { bgpPeerEntry 8 } ::= { bgpPeerEntry 8 }
bgpPeerRemoteAs OBJECT-TYPE bgpPeerRemoteAs OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote autonomous system number." "The remote autonomous system number."
REFERENCE
"RFC yyyy, Section 4.2."
::= { bgpPeerEntry 9 } ::= { bgpPeerEntry 9 }
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
bgpPeerInUpdates OBJECT-TYPE bgpPeerInUpdates 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 number of BGP UPDATE messages
received on this connection." received on this connection."
REFERENCE
"RFC yyyy, Section 4.3."
::= { bgpPeerEntry 10 } ::= { bgpPeerEntry 10 }
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
bgpPeerOutUpdates OBJECT-TYPE bgpPeerOutUpdates 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 number of BGP UPDATE messages
transmitted on this connection." transmitted on this connection."
REFERENCE
"RFC yyyy, Section 4.3."
::= { bgpPeerEntry 11 } ::= { bgpPeerEntry 11 }
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
bgpPeerInTotalMessages OBJECT-TYPE bgpPeerInTotalMessages OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of messages received "The total number of messages received
from the remote peer on this connection." from the remote peer on this connection."
REFERENCE
"RFC yyyy, Section 4."
::= { bgpPeerEntry 12 } ::= { bgpPeerEntry 12 }
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
bgpPeerOutTotalMessages OBJECT-TYPE bgpPeerOutTotalMessages OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of messages transmitted to "The total number of messages transmitted to
the remote peer on this connection." the remote peer on this connection."
REFERENCE
"RFC yyyy, Section 4."
::= { bgpPeerEntry 13 } ::= { bgpPeerEntry 13 }
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
bgpPeerLastError OBJECT-TYPE bgpPeerLastError OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (2)) SYNTAX OCTET STRING (SIZE (2))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The last error code and subcode seen by this "The last error code and subcode seen by this
peer on this connection. If no error has peer on this connection. If no error has
occurred, this field is zero. Otherwise, the occurred, this field is zero. Otherwise, the
first byte of this two byte OCTET STRING first byte of this two byte OCTET STRING
contains the error code, and the second byte contains the error code, and the second byte
contains the subcode." contains the subcode."
REFERENCE
"RFC yyyy, Section 4.5."
::= { bgpPeerEntry 14 } ::= { bgpPeerEntry 14 }
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
bgpPeerFsmEstablishedTransitions OBJECT-TYPE bgpPeerFsmEstablishedTransitions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of times the BGP FSM "The total number of times the BGP FSM
transitioned into the established state transitioned into the established state
for this peer." for this peer."
REFERENCE
"RFC yyyy, Section 8."
::= { bgpPeerEntry 15 } ::= { bgpPeerEntry 15 }
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
bgpPeerFsmEstablishedTime OBJECT-TYPE bgpPeerFsmEstablishedTime OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This timer indicates how long (in "This timer indicates how long (in
seconds) this peer has been in the seconds) this peer has been in the
established state or how long established state or how long
since this peer was last in the since this peer was last in the
established state. It is set to zero when established state. It is set to zero when
a new peer is configured or the router is a new peer is configured or the router is
booted." booted."
REFERENCE
"RFC yyyy, Section 8."
::= { bgpPeerEntry 16 } ::= { bgpPeerEntry 16 }
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
bgpPeerConnectRetryInterval OBJECT-TYPE bgpPeerConnectRetryInterval OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the "Time interval in seconds for the
ConnectRetry timer. The suggested value ConnectRetry timer. The suggested value
for this timer is 120 seconds." for this timer is 120 seconds."
REFERENCE
"RFC yyyy, Section 8.2.2. This is the value used
to initialize the 'ConnectRetryTimer'."
::= { bgpPeerEntry 17 } ::= { bgpPeerEntry 17 }
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
bgpPeerHoldTime OBJECT-TYPE bgpPeerHoldTime OBJECT-TYPE
SYNTAX Integer32 ( 0 | 3..65535 ) SYNTAX Integer32 ( 0 | 3..65535 )
UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the Hold "Time interval in seconds for the Hold
Timer established with the peer. The Timer established with the peer. The
value of this object is calculated by this value of this object is calculated by this
BGP speaker by using the smaller of the BGP speaker by using the smaller of the
value in bgpPeerHoldTimeConfigured and the value in bgpPeerHoldTimeConfigured and the
Hold Time received in the OPEN message. Hold Time received in the OPEN message.
skipping to change at page 12, line 43 skipping to change at page 13, line 43
if it is not zero (0). if it is not zero (0).
If the Hold Timer has not been established If the Hold 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 bgpPeerHoldTimeConfigured object has
a value of (0), then this object MUST have a a value of (0), then this object MUST have a
value of (0)." value of (0)."
REFERENCE REFERENCE
"RFC yyyy, Section 4.2" "RFC yyyy, Section 4.2."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgpPeerEntry 18 } ::= { bgpPeerEntry 18 }
bgpPeerKeepAlive OBJECT-TYPE bgpPeerKeepAlive OBJECT-TYPE
SYNTAX Integer32 ( 0 | 1..21845 ) SYNTAX Integer32 ( 0 | 1..21845 )
UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the KeepAlive "Time interval in seconds for the KeepAlive
timer established with the peer. The value timer established with the peer. The value
of this object is calculated by this BGP of this object is calculated by this BGP
speaker such that, when compared with speaker such that, when compared with
bgpPeerHoldTime, it has the same proportion bgpPeerHoldTime, it has the same proportion
as what bgpPeerKeepAliveConfigured has when as what bgpPeerKeepAliveConfigured has when
compared with bgpPeerHoldTimeConfigured. compared with bgpPeerHoldTimeConfigured.
If the KeepAlive 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 of bgpPeerKeepAliveConfigured object If the of bgpPeerKeepAliveConfigured object
has a value of (0), then this object MUST have has a value of (0), then this object MUST have
a value of (0)." a value of (0)."
REFERENCE REFERENCE
"RFC yyyy, Section 4.4" "RFC yyyy, Section 4.4."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgpPeerEntry 19 } ::= { bgpPeerEntry 19 }
bgpPeerHoldTimeConfigured OBJECT-TYPE bgpPeerHoldTimeConfigured OBJECT-TYPE
SYNTAX Integer32 ( 0 | 3..65535 ) SYNTAX Integer32 ( 0 | 3..65535 )
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 Hold Time
configured for this BGP speaker with this configured for this BGP speaker with this
peer. This value is placed in an OPEN peer. This value is placed in an OPEN
message sent to this peer by this BGP message sent to this peer by this BGP
speaker, and is compared with the Hold speaker, and is compared with the Hold
Time field in an OPEN message received Time field in an OPEN message received
from the peer when determining the Hold from the peer when determining the Hold
Time (bgpPeerHoldTime) with the peer. Time (bgpPeerHoldTime) with the peer.
This value must not be less than three This value must not be less than three
seconds if it is not zero (0) in which seconds if it is not zero (0) in which
case the Hold Time is NOT to be case the Hold Time is NOT to be
established with the peer. The suggested established with the peer. The suggested
value for this timer is 90 seconds." value for this timer is 90 seconds."
REFERENCE
"RFC yyyy, Section 4.2."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgpPeerEntry 20 } ::= { bgpPeerEntry 20 }
bgpPeerKeepAliveConfigured OBJECT-TYPE bgpPeerKeepAliveConfigured OBJECT-TYPE
SYNTAX Integer32 ( 0 | 1..21845 ) SYNTAX Integer32 ( 0 | 1..21845 )
UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the "Time interval in seconds for the
KeepAlive timer configured for this BGP KeepAlive timer configured for this BGP
speaker with this peer. The value of this speaker with this peer. The value of this
object will only determine the object will only determine the
KEEPALIVE messages' frequency relative to KEEPALIVE messages' frequency relative to
the value specified in the value specified in
bgpPeerHoldTimeConfigured; the actual bgpPeerHoldTimeConfigured; the actual
skipping to change at page 14, line 24 skipping to change at page 15, line 28
indicated by bgpPeerKeepAlive. A indicated by bgpPeerKeepAlive. A
reasonable maximum value for this timer reasonable maximum value for this timer
would be configured to be one would be configured to be one
third of that of third of that of
bgpPeerHoldTimeConfigured. bgpPeerHoldTimeConfigured.
If the value of this object is zero (0), If the value of this object is zero (0),
no periodical KEEPALIVE messages are sent no periodical KEEPALIVE messages are sent
to the peer after the BGP connection has to the peer after the BGP connection has
been established. The suggested value for been established. The suggested value for
this timer is 30 seconds." this timer is 30 seconds."
REFERENCE
"RFC yyyy, Section 4.4."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgpPeerEntry 21 } ::= { bgpPeerEntry 21 }
bgpPeerMinASOriginationInterval OBJECT-TYPE bgpPeerMinASOriginationInterval OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the "Time interval in seconds for the
MinASOriginationInterval timer. MinASOriginationInterval timer.
The suggested value for this timer is 15 The suggested value for this timer is 15
seconds." seconds."
REFERENCE
"RFC yyyy, Section 9.2.1.2."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgpPeerEntry 22 } ::= { bgpPeerEntry 22 }
bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the "Time interval in seconds for the
MinRouteAdvertisementInterval timer. MinRouteAdvertisementInterval timer.
The suggested value for this timer is 30 The suggested value for this timer is 30
seconds." seconds."
REFERENCE
"RFC yyyy, Section 9.2.1.1."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgpPeerEntry 23 } ::= { bgpPeerEntry 23 }
bgpPeerInUpdateElapsedTime OBJECT-TYPE bgpPeerInUpdateElapsedTime OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Elapsed time in seconds since the last BGP "Elapsed time in seconds since the last BGP
UPDATE message was received from the peer. UPDATE message was received from the peer.
Each time bgpPeerInUpdates is incremented, Each time bgpPeerInUpdates is incremented,
the value of this object is set to zero (0)." the value of this object is set to zero (0)."
REFERENCE
"RFC yyyy, Section 4.3.
RFC yyyy, Section 8.2.2, Established state."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgpPeerEntry 24 } ::= { bgpPeerEntry 24 }
bgpIdentifier OBJECT-TYPE bgpIdentifier OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BGP Identifier of local system." "The BGP Identifier of the local system."
REFERENCE
"RFC yyyy, Section 4.2."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgp 4 } ::= { bgp 4 }
-- BGP Received Path Attribute Table. This table contains, -- BGP Received Path Attribute Table. This table contains,
-- one entry per path to a network, path attributes -- one entry per path to a network, path attributes
-- received from all peers running BGP version 3 or less. -- received from all peers running BGP version 3 or less.
-- This table is obsolete, having been replaced in -- This table is obsolete, having been replaced in
-- functionality with the bgp4PathAttrTable. -- functionality with the bgp4PathAttrTable.
bgpRcvdPathAttrTable OBJECT-TYPE bgpRcvdPathAttrTable OBJECT-TYPE
SYNTAX SEQUENCE OF BgpPathAttrEntry SYNTAX SEQUENCE OF BgpPathAttrEntry
skipping to change at page 16, line 27 skipping to change at page 18, line 4
} }
bgpPathAttrPeer OBJECT-TYPE bgpPathAttrPeer OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The IP address of the peer where the path "The IP address of the peer where the path
information was learned." information was learned."
::= { bgpPathAttrEntry 1 } ::= { bgpPathAttrEntry 1 }
bgpPathAttrDestNetwork OBJECT-TYPE bgpPathAttrDestNetwork OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The address of the destination network." "The address of the destination network."
REFERENCE
"RFC 1267, Section 4.3."
::= { bgpPathAttrEntry 2 } ::= { bgpPathAttrEntry 2 }
bgpPathAttrOrigin OBJECT-TYPE bgpPathAttrOrigin OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
igp(1),-- networks are interior igp(1),-- networks are interior
egp(2),-- networks learned via the egp(2),-- networks learned via the
-- EGP protocol -- EGP protocol
incomplete(3) -- networks that incomplete(3) -- networks that
-- are learned by some other -- are learned by some other
-- means -- means
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The ultimate origin of the path information." "The ultimate origin of the path information."
REFERENCE
"RFC 1267, Section 4.3.
RFC 1267, Section 5."
::= { bgpPathAttrEntry 3 } ::= { bgpPathAttrEntry 3 }
bgpPathAttrASPath OBJECT-TYPE bgpPathAttrASPath OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (2..255)) SYNTAX OCTET STRING (SIZE (2..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The set of ASs that must be traversed to reach "The set of ASs that must be traversed to reach
the network. This object is probably best the network. This object is probably best
represented as SEQUENCE OF INTEGER. For SMI represented as SEQUENCE OF INTEGER. For SMI
compatibility, though, it is represented as compatibility, though, it is represented as
OCTET STRING. Each AS is represented as a pair OCTET STRING. Each AS is represented as a pair
of octets according to the following algorithm: of octets according to the 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;"
REFERENCE
"RFC 1267, Section 4.3.
RFC 1267, Section 5."
::= { bgpPathAttrEntry 4 } ::= { bgpPathAttrEntry 4 }
bgpPathAttrNextHop OBJECT-TYPE bgpPathAttrNextHop OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The address of the border router that should "The address of the border router that should
be used for the destination network." be used for the destination network."
REFERENCE
"RFC 1267, Section 4.3.
RFC 1267, Section 5."
::= { bgpPathAttrEntry 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
"RFC 1267, Section 4.3.
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, 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
skipping to change at page 19, line 41 skipping to change at page 21, line 28
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
bgp4PathAttrIpAddrPrefixLen. bgp4PathAttrIpAddrPrefixLen.
Any bits beyond the length specified by Any bits beyond the length specified by
bgp4PathAttrIpAddrPrefixLen are zeroed." bgp4PathAttrIpAddrPrefixLen are zeroed."
REFERENCE
"RFC yyyy, Section 4.3."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgp4PathAttrEntry 3 } ::= { bgp4PathAttrEntry 3 }
bgp4PathAttrOrigin OBJECT-TYPE bgp4PathAttrOrigin OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
igp(1),-- networks are interior igp(1),-- networks are interior
egp(2),-- networks learned via the egp(2),-- networks learned via the
-- EGP protocol -- EGP protocol
incomplete(3) -- networks that incomplete(3) -- networks that
-- are learned by some other -- are learned by some other
-- means -- means
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ultimate origin of the path "The ultimate origin of the path
information." information."
REFERENCE
"RFC yyyy, Section 4.3.
RFC yyyy, Section 5.1.1."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgp4PathAttrEntry 4 } ::= { 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>.
skipping to change at page 20, line 47 skipping to change at page 22, line 41
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 type of value of either 3 or 4. a value 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
"RFC yyyy, Section 4.3.
RFC yyyy, Section 5.1.2."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgp4PathAttrEntry 5 } ::= { bgp4PathAttrEntry 5 }
bgp4PathAttrNextHop OBJECT-TYPE bgp4PathAttrNextHop OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address of the border router that "The address of the border router that
should be used for the destination should be used for the destination
network. This address is the nexthop network. This address is the nexthop
address received in the UPDATE packet." address received in the UPDATE packet."
REFERENCE
"RFC yyyy, Section 4.3.
RFC yyyy, Section 5.1.3."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgp4PathAttrEntry 6 } ::= { bgp4PathAttrEntry 6 }
bgp4PathAttrMultiExitDisc OBJECT-TYPE bgp4PathAttrMultiExitDisc OBJECT-TYPE
SYNTAX Integer32 (-1..2147483647) SYNTAX Integer32 (-1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This metric is used to discriminate "This metric is used to discriminate
between multiple exit points to an between multiple exit points to an
adjacent autonomous system. A value of -1 adjacent autonomous system. A value of -1
indicates the absence of this attribute. indicates the absence of this attribute.
Known Issues: Known Issues:
o The BGP-4 specification uses an o The BGP-4 specification uses an
unsigned 32 bit number and thus this unsigned 32 bit number and thus this
object cannot represent the full object cannot represent the full
range of the protocol." range of the protocol."
REFERENCE
"RFC yyyy, Section 4.3.
RFC yyyy, Section 5.1.4."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgp4PathAttrEntry 7 } ::= { bgp4PathAttrEntry 7 }
bgp4PathAttrLocalPref OBJECT-TYPE bgp4PathAttrLocalPref OBJECT-TYPE
SYNTAX Integer32 (-1..2147483647) SYNTAX Integer32 (-1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The originating BGP4 speaker's degree of "The originating BGP4 speaker's degree of
preference for an advertised route. A preference for an advertised route. A
value of -1 indicates the absence of this value of -1 indicates the absence of this
attribute. attribute.
Known Issues: Known Issues:
o The BGP-4 specification uses an o The BGP-4 specification uses an
unsigned 32 bit number and thus this unsigned 32 bit number and thus this
object cannot represent the full object cannot represent the full
range of the protocol." range of the protocol."
REFERENCE
"RFC yyyy, Section 4.3.
RFC yyyy, Section 5.1.5."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgp4PathAttrEntry 8 } ::= { bgp4PathAttrEntry 8 }
bgp4PathAttrAtomicAggregate OBJECT-TYPE bgp4PathAttrAtomicAggregate OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
lessSpecificRouteNotSelected(1), lessSpecificRouteNotSelected(1),
-- Typo corrected from RFC 1657 -- Typo corrected from RFC 1657
lessSpecificRouteSelected(2) lessSpecificRouteSelected(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the ATOMIC_AGGREGATE attribute is present "If the ATOMIC_AGGREGATE attribute is present
in the Path Attributes then this object MUST in the Path Attributes then this object MUST
have a value of 'lessSpecificRouteNotSelected'. have a value of 'lessSpecificRouteNotSelected'.
If the ATOMIC_AGGREGATE attribute is missing If the ATOMIC_AGGREGATE attribute is missing
in the Path Attributes then this object MUST in the Path Attributes then this object MUST
have a value of 'lessSpecificRouteSelected'. have a value of 'lessSpecificRouteSelected'.
Note that ATOMIC_AGGREGATE has been deprecated Note that ATOMIC_AGGREGATE is now a primarily
in the BGP specification." informational attribute."
REFERENCE REFERENCE
"RFC yyyy, Sections 5.1.6 and 9.1.4." "RFC yyyy, Sections 5.1.6 and 9.1.4."
-- RFC Ed.: Replace yyyy with latest BGP RFC -- RFC Ed.: Replace yyyy with latest BGP RFC
::= { bgp4PathAttrEntry 9 } ::= { bgp4PathAttrEntry 9 }
bgp4PathAttrAggregatorAS OBJECT-TYPE bgp4PathAttrAggregatorAS OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The AS number of the last BGP4 speaker that "The AS number of the last BGP4 speaker that
performed route aggregation. A value of performed route aggregation. A value of
zero (0) indicates the absence of this zero (0) indicates the absence of this
attribute. attribute.
Note that propagation of AS of zero is illegal Note that propagation of AS of zero is illegal
in the Internet." in the Internet."
REFERENCE
"RFC yyyy, Section 5.1.7.
RFC yyyy, Section 9.2.2.2."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgp4PathAttrEntry 10 } ::= { bgp4PathAttrEntry 10 }
bgp4PathAttrAggregatorAddr OBJECT-TYPE bgp4PathAttrAggregatorAddr OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the last BGP4 speaker "The IP address of the last BGP4 speaker
that performed route aggregation. A that performed route aggregation. A
value of 0.0.0.0 indicates the absence value of 0.0.0.0 indicates the absence
of this attribute." of this attribute."
REFERENCE
"RFC yyyy, Section 5.1.7.
RFC yyyy, Section 9.2.2.2."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgp4PathAttrEntry 11 } ::= { bgp4PathAttrEntry 11 }
bgp4PathAttrCalcLocalPref OBJECT-TYPE bgp4PathAttrCalcLocalPref OBJECT-TYPE
SYNTAX Integer32 (-1..2147483647) SYNTAX Integer32 (-1..2147483647)
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. A value of -1 indicates the route. A value of -1 indicates the
absence of this attribute. absence of this attribute.
Known Issues: Known Issues:
o The BGP-4 specification uses an o The BGP-4 specification uses an
unsigned 32 bit number and thus this unsigned 32 bit number and thus this
object cannot represent the full object cannot represent the full
range of the protocol." range of the protocol."
REFERENCE
"RFC yyyy, Section 9.1.1."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgp4PathAttrEntry 12 } ::= { bgp4PathAttrEntry 12 }
bgp4PathAttrBest OBJECT-TYPE bgp4PathAttrBest OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
false(1),-- not chosen as best route false(1),-- not chosen as best route
true(2) -- chosen as best route true(2) -- chosen as best route
} }
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 for this was chosen as the best BGP4 route for this
destination." destination."
REFERENCE
"RFC yyyy, Section 9.1.2."
-- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification
::= { bgp4PathAttrEntry 13 } ::= { bgp4PathAttrEntry 13 }
bgp4PathAttrUnknown OBJECT-TYPE bgp4PathAttrUnknown OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..255)) SYNTAX OCTET STRING (SIZE(0..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"One or more path attributes not understood by "One or more path attributes not understood by
this BGP4 speaker. this BGP4 speaker.
skipping to change at page 25, line 14 skipping to change at page 27, line 34
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BGPBackwardTransNotification Event is "The BGPBackwardTransNotification Event is
generated when the BGP FSM moves from a higher generated when the BGP FSM moves from a higher
numbered state to a lower numbered state. numbered state to a lower numbered state.
This Notification replaces the This Notification replaces the
bgpBackwardsTransition Notification." bgpBackwardsTransition Notification."
::= { bgpNotification 2 } ::= { bgpNotification 2 }
-- { bgp 7 } is obsoleted -- { bgp 7 } is deprecated. Do not allocate new objects or
-- notifications underneath this branch.
bgpTraps OBJECT IDENTIFIER ::= { bgp 7 } bgpTraps OBJECT IDENTIFIER ::= { bgp 7 } -- deprecated
bgpEstablished NOTIFICATION-TYPE bgpEstablished NOTIFICATION-TYPE
OBJECTS { bgpPeerLastError, OBJECTS { bgpPeerLastError,
bgpPeerState } bgpPeerState }
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The BGP Established event is generated when "The BGP Established event is generated when
the BGP FSM enters the ESTABLISHED state. the BGP FSM enters the ESTABLISHED state.
This Notification has been replaced by the This Notification has been replaced by the
skipping to change at page 31, line 18 skipping to change at page 33, line 18
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 sensitive information regarding the operation of a network. contain sensitive information regarding the operation of a network.
skipping to change at page 33, line 35 skipping to change at page 35, line 35
Peder Chr Norgaard, Telebit Communications A/S Peder Chr Norgaard, Telebit Communications A/S
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
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. Normative References 8. IANA Considerations
This document presents no new IANA considerations.
9. Normative References
[BGP4] Rekhter, Y., Li, T., Hares, S., "A Border Gateway [BGP4] Rekhter, Y., Li, T., Hares, S., "A Border Gateway
Protocol 4 (BGP-4)", RFC yyyy, zzzz 2003. Protocol 4 (BGP-4)", RFC yyyy, zzzz 2004.
-- RFC Ed.: Replace yyyy with latest BGP RFC and zzzz with its -- RFC Ed.: Replace yyyy with latest BGP RFC and zzzz with its
-- month of publication -- month of publication
[BGP4APP] Rekhter, Y., Gross, P., "Application of the Border [BGP4APP] Rekhter, Y., Gross, P., "Application of the Border
Gateway Protocol in the Internet", RFC 1772, March 1995. Gateway Protocol in the Internet", RFC 1772, March 1995.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management Rose, M., and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for Rose, M., and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
9. Editors' Address 10. Editors' Address
Jeffrey Haas, Susan Hares Jeffrey Haas, 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: jhaas@nexthop.com
skh@nexthop.com skh@nexthop.com
10. Full Copyright Statement 11. Full Copyright Statement
Copyright (C) The Internet Society (2004). 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 included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
 End of changes. 

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