draft-ietf-idr-bgp-mibagent-survey-02.txt   rfc4275.txt 
Network Working Group
Internet Draft S. Hares
Document: draft-ietf-idr-bgp-mibagent-survey-02.txt NextHop
Expires: April 2005 D. Hares
October 2004
BGP-4 MIB Implementation Survey
Status of this Memo
By submitting this Internet-Draft, we certify that any applicable Network Working Group S. Hares
patent or other IPR claims of which we are aware have been Request for Comments: 4275 NextHop
disclosed, or will be disclosed, and any of which we become aware Category: Informational D. Hares
will be disclosed, in accordance with RFC 3668. Hickory Hill Consulting
January 2006
Internet-Drafts are working documents of the Internet Engineering BGP-4 MIB Implementation Survey
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 Status of This Memo
months 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 This memo provides information for the Internet community. It does
http://www.ietf.org/ietf/1id-abstracts.txt. not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
The list of Internet-Draft Shadow Directories can be accessed at Copyright Notice
http://www.ietf.org/shadow.html"
This document may not be modified, and derivative works of it may Copyright (C) The Internet Society (2006).
not be created, except to publish it as an RFC and to translate it
into languages other than English.
Abstract Abstract
This document provides of survey of BGP-4 [BGP4] protocol This document provides a survey of implementations of BGP-4 that
implementing RFC 1657 MIB agents according to the [BGP-v1-MIB] support RFC 1657 MIB agents according to the BGP-4 v1 MIB
specification. specification.
BGP-4 MIB Implementation Survey October 2004
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction ....................................................2
2. Survey Summary.................................................2 2. Survey Summary ..................................................2
2.1 MIB Agent Object Implementation Summary....................3 2.1. MIB Agent Object Implementation Summary ....................2
2.2 MIB Agent Read-Write Object Implementation Summary.........4 2.2. MIB Agent Read-Write Object Implementation Summary .........4
2.3 MIB Agent Trap Implementation Summary......................4 2.3. MIB Agent Trap Implementation Summary ......................4
2.4 MIB Agent BGP Peer Reset state.............................5 2.4. MIB Agent BGP Peer Reset state .............................4
2.5 MIB Manager interactions...................................5 2.5. MIB Manager Interactions ...................................5
3. Survey Forms...................................................6 3. Survey Forms ....................................................6
3.1 Cisco Systems..............................................6 3.1. Cisco Systems ..............................................6
3.2 NextHop Technologies.......................................8 3.2. NextHop Technologies .......................................8
3.3 Redback Networks..........................................11 3.3. Redback Networks ..........................................11
4. MIB Walks.....................................................14 4. MIB Walks ......................................................13
4.1 Cisco Systems.............................................14 4.1. Cisco Systems .............................................13
4.2 NextHop Technologies......................................23 4.2. NextHop Technologies ......................................23
4.3 Redback Networks..........................................31 4.3. Redback Networks ..........................................31
Security Considerations..........................................35 5. Security Considerations ........................................35
Normative References.............................................35 6. Acknowledgements ...............................................35
Acknowledgments..................................................35 7. Normative References ...........................................35
Authors' Addresses...............................................35
Copyright Statement..............................................36
1. 1. Introduction
Introduction
This document provides a survey of BGP-4 v1 MIB implementations. This document provides a survey of BGP-4 v1 MIB [RFC4274]
After a brief summary, each response is listed. The authors make no implementations. After a brief summary, each response is listed.
claim as to the accuracy of the information provided. The authors make no claim as to the accuracy of the information
provided.
The following organizations reported having BGP-4 MIB The following organizations reported having BGP-4 MIB
implementations: Cisco Systems, Redback Networks, and NextHop implementations: Cisco Systems, Redback Networks, and NextHop
Technologies. Technologies.
2. 2. Survey Summary
Survey Summary
This survey asked for information about the implementations of the This survey asked for information about the implementations of the
BGP-4 [BGP4] that support the BGP-4 v1 MIB [BGP4-V1-MIB]. BGP-4 [RFC4271] that support MIB agents [RFC1657] according to the
BGP-4 v1 MIB [RFC4274].
Two or more of the implementations of BGP-4 v1 MIB [BGP-V1-MIB] each
implement all the objects. None of the implementation that responded
to the survey implemented the read-write variables (section 2.2).
The two TRAPs as specified are not implemented by two implementations
(section 2.3). The counters initialized state is zeroed in all
implementation, but a reset peer is only reset by the Redback
implementation (section 2.4).
BGP-4 MIB Implementation Survey October 2004 Two or more of the implementations of BGP-4 v1 MIB [RFC4274] each
implement all the objects. None of the implementations that
responded to the survey implemented the read-write variables (Section
2.2). The two TRAPs as specified are not implemented by two
implementations (Section 2.3). The counters' initialized state is
zeroed in all implementations, but a reset peer is only reset by the
Redback implementation (Section 2.4).
There are 3 agent implementations for the 3 surveyed (section 2.5). There are 3 agent implementations for the 3 surveyed (Section 2.5).
The SNMP managers used to test the implementations are: netsnmp The Simple Network Management Protocol (SNMP) managers used to test
(www.netsnmp.org), mrtg (www.mrtg.org), and internal Cisco manager. the implementations are: Net-SNMP (www.net-snmp.org), Multi Router
Traffic Grapher (www.mrtg.org), and the internal Cisco manager.
No inter-operability issues related to the Manager specification were No interoperability issues related to the Manager specification were
found. found.
2.1 2.1. MIB Agent Object Implementation Summary
MIB Agent Object Implementation Summary
Cisco NextHop Redback Cisco NextHop Redback
Y Y Y bgpVersion Y Y Y bgpVersion
Y Y Y bgpLocalAs Y Y Y bgpLocalAs
Y Y Y bgpPeerIdentifier Y Y Y bgpPeerIdentifier
Y Y Y bgpPeerState Y Y Y bgpPeerState
Y Y Y bgpPeerAdminStatus Y Y Y bgpPeerAdminStatus
Y Y Y bgpPeerNegotiatedVersion Y Y Y bgpPeerNegotiatedVersion
Y Y Y bgpPeerLocalAddr Y Y Y bgpPeerLocalAddr
Y Y Y bgpPeerLocalPort Y Y Y bgpPeerLocalPort
skipping to change at page 4, line 4 skipping to change at page 3, line 29
N N N bgpPathAttrPeer N N N bgpPathAttrPeer
N N N bgpPathAttrDestNetwork N N N bgpPathAttrDestNetwork
N N N bgpPathAttrOrigin N N N bgpPathAttrOrigin
N N N bgpPathAttrASPath N N N bgpPathAttrASPath
N N N bgpPathAttrNextHop N N N bgpPathAttrNextHop
N N N bgpPathAttrInterASMetric N N N bgpPathAttrInterASMetric
Y Y Y bgp4PathAttrPeer Y Y Y bgp4PathAttrPeer
Y Y Y bgp4PathAttrIpAddrPrefixLen Y Y Y bgp4PathAttrIpAddrPrefixLen
BGP-4 MIB Implementation Survey October 2004
Y Y Y bgp4PathAttrIpAddrPrefix Y Y Y bgp4PathAttrIpAddrPrefix
Y Y Y bgp4PathAttrOrigin Y Y Y bgp4PathAttrOrigin
Y Y Y bgp4PathAttrASPathSegment Y Y Y bgp4PathAttrASPathSegment
Y Y Y bgp4PathAttrNextHop Y Y Y bgp4PathAttrNextHop
Y Y Y bgp4PathAttrMultiExitDisc Y Y Y bgp4PathAttrMultiExitDisc
Y Y Y bgp4PathAttrLocalPref Y Y Y bgp4PathAttrLocalPref
Y Y Y bgp4PathAttrAtomicAggregate Y Y Y bgp4PathAttrAtomicAggregate
Y Y Y bgp4PathAttrAggregatorAS Y Y Y bgp4PathAttrAggregatorAS
Y Y Y bgp4PathAttrAggregatorAddr Y Y Y bgp4PathAttrAggregatorAddr
Y Y Y bgp4PathAttrCalcLocalPref Y Y Y bgp4PathAttrCalcLocalPref
Y Y Y bgp4PathAttrBest Y Y Y bgp4PathAttrBest
Y Y Y bgp4PathAttrUnknown Y Y Y bgp4PathAttrUnknown
Please note that items bgpPathAttrPeer, bgpPathAttrDestNetwork, Please note that items bgpPathAttrPeer, bgpPathAttrDestNetwork,
bgpPathAttrOrigin, bgpPatthAttrASPath, bgpPathAttrNextHop, bgpPathAttrOrigin, bgpPatthAttrASPath, bgpPathAttrNextHop, and
bgpPathAttrInterASMetric are deprecated. An answer of Y/N is valid bgpPathAttrInterASMetric are deprecated. An answer of Y/N is valid
for this status. for this status.
2.2 2.2. MIB Agent Read-Write Object Implementation Summary
MIB Agent Read-Write Object Implementation Summary
Does your implementation allow managers to write to the following Does your implementation allow managers to write to the following
read-write objects? Indicate yes or no (Y or N) for each object: read-write objects? Indicate yes or no (Y or N) for each object:
Cisco NextHop Redback Cisco NextHop Redback
N N N bgpPeerAdminStatus N N N bgpPeerAdminStatus
N N N bgpPeerConnectRetryInterval N N N bgpPeerConnectRetryInterval
N N N bgpPeerHoldTimeConfigured N N N bgpPeerHoldTimeConfigured
N N N bgpPeerKeepAliveConfigured N N N bgpPeerKeepAliveConfigured
N N N bgpPeerMinASOriginationInterval N N N bgpPeerMinASOriginationInterval
N N N bgpPeerMinRouteAdvertisementInterval N N N bgpPeerMinRouteAdvertisementInterval
None of the implementations surveyed supported the read/write None of the implementations surveyed supported the read/write
variables. variables.
2.3 2.3. MIB Agent Trap Implementation Summary
MIB Agent Trap Implementation Summary
Does your implementation include each of the following Does your implementation include each of the following notifications?
notifications? Indicate yes or no (Y or N) for each Indicate yes or no (Y or N) for each notification:
notification:
Cisco NextHop Redback Cisco NextHop Redback
Y N N bgpEstablished Y N N bgpEstablished
Y N Y*1 bgpBackwardTransition Y N Y*1 bgpBackwardTransition
*1 - Redback only supports the transition from Established to *1 - Redback only supports the transition from Established to
Idle. Idle.
BGP-4 MIB Implementation Survey October 2004 2.4. MIB Agent BGP Peer Reset state
2.4
MIB Agent BGP Peer Reset state
Two questions were asked about the the bgpPeerInUpdates, Two questions were asked about the bgpPeerInUpdates,
bgpPeerOutUpdates, bgpPeerInTotalMessages and bgpPeerOutUpdates, bgpPeerInTotalMessages and
bgpPeerOutTotalMessages. bgpPeerOutTotalMessages.
The first was "do you initialize these counters zero", and the The first was "Do you initialize these counters to zero?", and the
second was "Do you reset these counters to zero when a configured second was "Do you reset these counters to zero when a configured
peer enters established state". peer enter the established state?"
Cisco NextHop Redback Cisco NextHop Redback
Y Y Y initialize to zero Y Y Y initialize to zero
N N Y reset to zero when configured peer N N Y reset to zero when configured peer
Enters established state Enters established state
2.5 2.5. MIB Manager Interactions
MIB Manager interactions
Managers: Managers:
BGP MIB agent: BGP MIB agent:
Cisco NextHop Redback Cisco NextHop Redback
Y Y N independent implementation Y Y N independent implementation
- - C (P or C)public or commercial - - C (P or C)public or commercial
Redback code based on SNMP Research EMANATE Redback code based on SNMP Research EMANATE
SNMP Manager Interaction SNMP Manager Interaction
Cisco NextHop Redback Cisco NextHop Redback
cisco NetSNMP MRTG SNMP Managers tested with cisco Net-SNMP MRTG SNMP Managers tested with
- Y Y Manager implemented independently - Y Y Manager implemented independently
from agent from agent
- Y Y Read access to BGP4 MIB - Y Y Read access to BGP-4 MIB
variables. variables.
N N N Write access to BGP4 MIB N N N Write access to BGP-4 MIB
variables. variables.
- N Y Sending and receiving BGP4 MIB - N Y Sending and receiving BGP-4 MIB
notifications. notifications.
Y Y Y Tested using SNMPv1/v2c. Y Y Y Tested using SNMPv1/v2c.
Y N Y Tested using SNMPv3. Y N Y Tested using SNMPv3.
"-" indicates cisco did not answer these questions. "-" indicates cisco did not answer these questions.
NextHop SNMP agent support is via SMUX interface. NextHop SNMP agent support is via SNMP Multiplex (SMUX)
interface.
MRTG SNMP is found at mrtg.org. NetSNMP (UC Davis tools) found
at www.netsnmp.org.
SNMP Manager-Agent Inter-operability issues MRTG SNMP is found at www.mrtg.org. Net-SNMP (UC Davis tools)
found at www.net-snmp.org.
BGP-4 MIB Implementation Survey October 2004 SNMP Manager-Agent Interoperability issues
Cisco NextHop Redback Cisco NextHop Redback
N N N Inter-operability issues N N N Interoperability issues
3. 3. Survey Forms
Survey Forms
3.1 3.1. Cisco Systems
Cisco Systems
Agent Implementation Checklist Agent Implementation Checklist
This section should be completed by individuals or companies who This section should be completed by individuals or companies who
have implemented RFC 1657 support in an SNMP agent. have implemented RFC 1657 [RFC1657] support in an SNMP agent.
Is your BGP4 MIB agent an independent implementation? Or is it Is your BGP-4 MIB agent an independent implementation? Or is it
based on public domain or commercial code? If it is not based on public domain or commercial code? If it is not
independent, what code base was used? independent, what code base was used?
- Cisco's BGP4 MIB agent is implemented on commercial Cisco IOS. - Cisco's BGP-4 MIB agent is implemented on commercial Cisco
Internetwork Operating System (IOS).
Have you done any interoperability testing with managers that Have you done any interoperability testing with managers that
implement the BGP4 MIB? If so, which manager implementations implement the BGP-4 MIB? If so, which manager implementations
have been used with your agent? have been used with your agent?
- (this portion was not returned by Cisco) - (this portion was not returned by Cisco)
For each manager with which you have interoperated, which of the For each manager with which you have interoperated, which of the
following features were tested? Duplicate this section for each following features were tested? Duplicate this section for each
manager, and indicate yes or no (Y/N) for each feature: manager, and indicate yes or no (Y/N) for each feature:
- (this portion was not returned by Cisco) - (this portion was not returned by Cisco)
Manager Implementation Used: <Name> Manager Implementation Used: <Name>
Original Manager Code Base (if known): <Name> Original Manager Code Base (if known): <Name>
(Y/N) Manager implemented independently from your agent? (Y/N) Manager implemented independently from your agent?
(Y/N) Read access to BGP4 MIB variables. (Y/N) Read access to BGP-4 MIB variables.
(Y/N) Write access to BGP4 MIB variables. (Y/N) Write access to BGP-4 MIB variables.
(Y/N) Sending and receiving BGP4 MIB notifications. (Y/N) Sending and receiving BGP-4 MIB notifications.
(Y/N) Tested using SNMPv1/v2c. (Y/N) Tested using SNMPv1/v2c.
(Y/N) Tested using SNMPv3. (Y/N) Tested using SNMPv3.
Are there any unresolved interoperability issues between your Are there any unresolved interoperability issues, between your
BGP4 MIB agent and any BGP4 MIB manager that may indicate BGP-4 MIB agent and any BGP-4 MIB manager, that may indicate
problems in the specification? If so, please provide technical problems in the specification? If so, please provide technical
details. details.
- (this portion was not returned by cisco) - (this portion was not returned by cisco)
BGP-4 MIB Implementation Survey October 2004
(Y) Does your agent support SNMPv3? (Y) Does your agent support SNMPv3?
Does your BGP4 MIB agent implement the following Does your BGP-4 MIB agent implement the following
objects? Indicate yes or no (Y or N) for each object: objects? Indicate yes or no (Y or N) for each object:
(Y) bgpVersion (Y) bgpVersion
(Y) bgpLocalAs (Y) bgpLocalAs
(Y) bgpPeerIdentifier (Y) bgpPeerIdentifier
(Y) bgpPeerState (Y) bgpPeerState
(Y) bgpPeerAdminStatus (Y) bgpPeerAdminStatus
(Y) bgpPeerNegotiatedVersion (Y) bgpPeerNegotiatedVersion
(Y) bgpPeerLocalAddr (Y) bgpPeerLocalAddr
(Y) bgpPeerLocalPort (Y) bgpPeerLocalPort
skipping to change at page 7, line 51 skipping to change at page 7, line 44
(N) bgpPathAttrOrigin (N) bgpPathAttrOrigin
(N) bgpPathAttrASPath (N) bgpPathAttrASPath
(N) bgpPathAttrNextHop (N) bgpPathAttrNextHop
(N) bgpPathAttrInterASMetric (N) bgpPathAttrInterASMetric
(Y) bgp4PathAttrPeer (Y) bgp4PathAttrPeer
(Y) bgp4PathAttrIpAddrPrefixLen (Y) bgp4PathAttrIpAddrPrefixLen
(Y) bgp4PathAttrIpAddrPrefix (Y) bgp4PathAttrIpAddrPrefix
(Y) bgp4PathAttrOrigin (Y) bgp4PathAttrOrigin
(Y) bgp4PathAttrASPathSegment (Y) bgp4PathAttrASPathSegment
(Y) bgp4PathAttrNextHop (Y) bgp4PathAttrNextHop
(Y) bgp4PathAt (Y) bgp4PathAttrMultiExitDisc
trMultiExitDisc
(Y) bgp4PathAttrLocalPref (Y) bgp4PathAttrLocalPref
(Y) bgp4PathAttrAtomicAggregate (Y) bgp4PathAttrAtomicAggregate
BGP-4 MIB Implementation Survey October 2004
(Y) bgp4PathAttrAggregatorAS (Y) bgp4PathAttrAggregatorAS
(Y) bgp4PathAttrAggregatorAddr (Y) bgp4PathAttrAggregatorAddr
(Y) bgp4PathAttrCalcLocalPref (Y) bgp4PathAttrCalcLocalPref
(Y) bgp4PathAttrBest (Y) bgp4PathAttrBest
(Y) bgp4PathAttrUnknown (Y) bgp4PathAttrUnknown
Does your implementation allow managers to write to the following Does your implementation allow managers to write to the following
read-write objects? Indicate yes or no (Y or N) for each object: read-write objects? Indicate yes or no (Y or N) for each object:
(N) bgpPeerAdminStatus (N) bgpPeerAdminStatus
skipping to change at page 8, line 31 skipping to change at page 8, line 25
(N) bgpPeerMinRouteAdvertisementInterval (N) bgpPeerMinRouteAdvertisementInterval
Does your implementation include each of the following Does your implementation include each of the following
notifications? Indicate yes or no (Y or N) for each notifications? Indicate yes or no (Y or N) for each
notification: notification:
(Y) bgpEstablished (Y) bgpEstablished
(Y) bgpBackwardTransition (Y) bgpBackwardTransition
Does your implementation initialize bgpPeerInUpdates, Does your implementation initialize bgpPeerInUpdates,
bgpPeerOutUpdates, bgpPeerInTotalMessages and bgpPeerOutUpdates, bgpPeerInTotalMessages, and
bgpPeerOutTotalMessages counters to zero? bgpPeerOutTotalMessages counters to zero?
Yes. Yes.
Does your implementation reset the bgpPeerInUpdates, Does your implementation reset the bgpPeerInUpdates,
bgpPeerOutUpdates, bgpPeerInTotalMessages and bgpPeerOutUpdates, bgpPeerInTotalMessages, and
bgpPeerOutTotalMessages counters to zero when a configured peer bgpPeerOutTotalMessages counters to zero when a configured peer
enters the established state? enters the established state?
No. No.
3.2 3.2. NextHop Technologies
NextHop Technologies
Agent Implementation Checklist Agent Implementation Checklist
This section should be completed by individuals or companies who This section should be completed by individuals or companies who
have implemented RFC 1657 support in an SNMP agent. have implemented RFC 1657 [RFC1657] support in an SNMP agent.
Is your BGP4 MIB agent an independent implementation? Or is it Is your BGP-4 MIB agent an independent implementation? Or is it
based on public domain or commercial code? If it is not based on public domain or commercial code? If it is not
independent, what code base was used? independent, what code base was used?
BGP-4 MIB Implementation Survey October 2004
- Independent implementation. - Independent implementation.
Have you done any interoperability testing with managers that Have you done any interoperability testing with managers that
implement the BGP4 MIB? If so, which manager implementations implement the BGP-4 MIB? If so, which manager implementations
have been used with your agent? have been used with your agent?
- Yes. - Yes.
For each manager with which you have interoperated, which of the For each manager with which you have interoperated, which of the
following features were tested? Duplicate this section for each following features were tested? Duplicate this section for each
manager, and indicate yes or no (Y/N) for each feature: manager, and indicate yes or no (Y/N) for each feature:
Manager Implementation Used: <Name> Manager Implementation Used: <Name>
- UCD SNMP Tools (NetSNMP) - UC Davis SNMP Tools (Net-SNMP)
Original Manager Code Base (if known): UC Davis SNMP Original Manager Code Base (if known): UC Davis SNMP
(Y) Manager implemented independently from your agent? (Y) Manager implemented independently from your agent?
(Y) Read access to BGP4 MIB variables. (Y) Read access to BGP-4 MIB variables.
(na) Write access to BGP4 MIB variables. (na) Write access to BGP-4 MIB variables.
(na) Sending and receiving BGP4 MIB notifications. (na) Sending and receiving BGP-4 MIB notifications.
(Y) Tested using SNMPv1/v2c. (Y) Tested using SNMPv1/v2c.
(N) Tested using SNMPv3. (N) Tested using SNMPv3.
Are there any unresolved interoperability issues between your Are there any unresolved interoperability issues, between your
BGP4 MIB agent and any BGP4 MIB manager that may indicate BGP-4 MIB agent and any BGP-4 MIB manager, that may indicate
problems in the specification? If so, please provide technical problems in the specification? If so, please provide technical
details. details.
(Y/N) Does your agent support SNMPv3? (Y/N) Does your agent support SNMPv3?
- N/A. Access to agent is provided via SMUX. - N/A. Access to agent is provided via SMUX.
Does your BGP4 MIB agent implement the following Does your BGP-4 MIB agent implement the following
objects? Indicate yes or no (Y or N) for each object: objects? Indicate yes or no (Y or N) for each object:
(Y) bgpVersion (Y) bgpVersion
(Y) bgpLocalAs (Y) bgpLocalAs
(Y) bgpPeerIdentifier (Y) bgpPeerIdentifier
(Y) bgpPeerState (Y) bgpPeerState
(Y) bgpPeerAdminStatus (Y) bgpPeerAdminStatus
(Y) bgpPeerNegotiatedVersion (Y) bgpPeerNegotiatedVersion
(Y) bgpPeerLocalAddr (Y) bgpPeerLocalAddr
(Y) bgpPeerLocalPort (Y) bgpPeerLocalPort
(Y) bgpPeerRemoteAddr (Y) bgpPeerRemoteAddr
(Y) bgpPeerRemotePort (Y) bgpPeerRemotePort
(Y) bgpPeerRemoteAs (Y) bgpPeerRemoteAs
BGP-4 MIB Implementation Survey October 2004
(Y) bgpPeerInUpdates (Y) bgpPeerInUpdates
(Y) bgpPeerOutUpdates (Y) bgpPeerOutUpdates
(Y) bgpPeerInTotalMessages (Y) bgpPeerInTotalMessages
(Y) bgpPeerOutTotalMessages (Y) bgpPeerOutTotalMessages
(Y) bgpPeerLastError (Y) bgpPeerLastError
(Y) bgpPeerFsmEstablishedTransitions (Y) bgpPeerFsmEstablishedTransitions
(Y) bgpPeerFsmEstablishedTime (Y) bgpPeerFsmEstablishedTime
(Y) bgpPeerConnectRetryInterval (Y) bgpPeerConnectRetryInterval
(Y) bgpPeerHoldTime (Y) bgpPeerHoldTime
(Y) bgpPeerKeepAlive (Y) bgpPeerKeepAlive
skipping to change at page 10, line 53 skipping to change at page 11, line 4
Does your implementation allow managers to write to the following Does your implementation allow managers to write to the following
read-write objects? Indicate yes or no (Y or N) for each object: read-write objects? Indicate yes or no (Y or N) for each object:
(N) bgpPeerAdminStatus (N) bgpPeerAdminStatus
(N) bgpPeerConnectRetryInterval (N) bgpPeerConnectRetryInterval
(N) bgpPeerHoldTimeConfigured (N) bgpPeerHoldTimeConfigured
(N) bgpPeerKeepAliveConfigured (N) bgpPeerKeepAliveConfigured
(N) bgpPeerMinASOriginationInterval (N) bgpPeerMinASOriginationInterval
(N) bgpPeerMinRouteAdvertisementInterval (N) bgpPeerMinRouteAdvertisementInterval
Does your implementation include each of the following Does your implementation include each of the following
BGP-4 MIB Implementation Survey October 2004
notifications? Indicate yes or no (Y or N) for each notifications? Indicate yes or no (Y or N) for each
notification: notification:
(N) bgpEstablished (N) bgpEstablished
(N) bgpBackwardTransition (N) bgpBackwardTransition
Does your implementation initialize bgpPeerInUpdates, Does your implementation initialize bgpPeerInUpdates,
bgpPeerOutUpdates, bgpPeerInTotalMessages and bgpPeerOutUpdates, bgpPeerInTotalMessages, and
bgpPeerOutTotalMessages counters to zero? bgpPeerOutTotalMessages counters to zero?
Yes. Yes.
Does your implementation reset the bgpPeerInUpdates, Does your implementation reset the bgpPeerInUpdates,
bgpPeerOutUpdates, bgpPeerInTotalMessages and bgpPeerOutUpdates, bgpPeerInTotalMessages, and
bgpPeerOutTotalMessages counters to zerowhen a configured peer bgpPeerOutTotalMessages counters to zerowhen a configured peer
enters the established state? enters the established state?
No. No.
3.3 3.3. Redback Networks
Redback Networks
Agent Implementation Checklist Agent Implementation Checklist
This section should be completed by individuals or companies who This section should be completed by individuals or companies who
have implemented RFC 1657 support in an SNMP agent. have implemented RFC 1657 [RFC1657] support in an SNMP agent.
Is your BGP4 MIB agent an independent implementation? Or is it Is your BGP-4 MIB agent an independent implementation? Or is it
based on public domain or commercial code? If it is not based on public domain or commercial code? If it is not
independent, what code base was used? independent, what code base was used?
- No, it is based on SNMP Research EMANATE - No, it is based on SNMP Research EMANATE
Have you done any interoperability testing with managers that Have you done any interoperability testing with managers that
implement the BGP4 MIB? If so, which manager implementations implement the BGP-4 MIB? If so, which manager implementations
have been used with your agent? have been used with your agent?
- We have done interoperability testing with SNMP managers from - We have done interoperability testing with SNMP managers from
MRTG. MRTG.
For each manager with which you have interoperated, which of the For each manager with which you have interoperated, which of the
following features were tested? Duplicate this section for each following features were tested? Duplicate this section for each
manager, and indicate yes or no (Y/N) for each feature: manager, and indicate yes or no (Y/N) for each feature:
Manager Implementation Used: MRTG (mrtg.org) Manager Implementation Used: MRTG (www.mrtg.org)
Original Manager Code Base (if known): Original Manager Code Base (if known):
(Y) Manager implemented independently from your agent? (Y) Manager implemented independently from your agent?
(Y) Read access to BGP-4 MIB variables.
Hares & Hares (N) Write access to BGP-4 MIB variables.
(Y) Sending and receiving BGP-4 MIB notifications.
BGP-4 MIB Implementation Survey October 2004
(Y) Read access to BGP4 MIB variables.
(N) Write access to BGP4 MIB variables.
(Y) Sending and receiving BGP4 MIB notifications.
(Y) Tested using SNMPv1/v2c. (Y) Tested using SNMPv1/v2c.
(Y) Tested using SNMPv3. (Y) Tested using SNMPv3.
Are there any unresolved interoperability issues between your Are there any unresolved interoperability issues between your
BGP4 MIB agent and any BGP4 MIB manager that may indicate BGP-4 MIB agent and any BGP-4 MIB manager that may indicate
problems in the specification? If so, please provide technical problems in the specification? If so, please provide technical
details. details.
No, there are not any unresolved interoperability issues. No, there are not any unresolved interoperability issues.
(Y) Does your agent support SNMPv3? (Y) Does your agent support SNMPv3?
Does your BGP4 MIB agent implement the following Does your BGP-4 MIB agent implement the following
objects? Indicate yes or no (Y or N) for each object: objects? Indicate yes or no (Y or N) for each object:
(Y) bgpVersion (Y) bgpVersion
(Y) bgpLocalAs (Y) bgpLocalAs
(Y) bgpPeerIdentifier (Y) bgpPeerIdentifier
(Y) bgpPeerState (Y) bgpPeerState
(Y) bgpPeerAdminStatus (Y) bgpPeerAdminStatus
(Y) bgpPeerNegotiatedVersion (Y) bgpPeerNegotiatedVersion
(Y) bgpPeerLocalAddr (Y) bgpPeerLocalAddr
(Y) bgpPeerLocalPort (Y) bgpPeerLocalPort
skipping to change at page 13, line 4 skipping to change at page 12, line 51
(Y) bgpPeerHoldTime (Y) bgpPeerHoldTime
(Y) bgpPeerKeepAlive (Y) bgpPeerKeepAlive
(Y) bgpPeerHoldTimeConfigured (Y) bgpPeerHoldTimeConfigured
(Y) bgpPeerKeepAliveConfigured (Y) bgpPeerKeepAliveConfigured
(Y) bgpPeerMinASOriginationInterval (Y) bgpPeerMinASOriginationInterval
(Y) bgpPeerMinRouteAdvertisementInterval (Y) bgpPeerMinRouteAdvertisementInterval
(Y) bgpPeerInUpdateElapsedTime (Y) bgpPeerInUpdateElapsedTime
(Y) bgpIdentifier (Y) bgpIdentifier
(N) bgpPathAttrPeer (N) bgpPathAttrPeer
BGP-4 MIB Implementation Survey October 2004
(N) bgpPathAttrDestNetwork (N) bgpPathAttrDestNetwork
(N) bgpPathAttrOrigin (N) bgpPathAttrOrigin
(N) bgpPathAttrASPath (N) bgpPathAttrASPath
(N) bgpPathAttrNextHop (N) bgpPathAttrNextHop
(N) bgpPathAttrInterASMetric (N) bgpPathAttrInterASMetric
(Y) bgp4PathAttrPeer (Y) bgp4PathAttrPeer
(Y) bgp4PathAttrIpAddrPrefixLen (Y) bgp4PathAttrIpAddrPrefixLen
(Y) bgp4PathAttrIpAddrPrefix (Y) bgp4PathAttrIpAddrPrefix
(Y) bgp4PathAttrOrigin (Y) bgp4PathAttrOrigin
skipping to change at page 13, line 47 skipping to change at page 13, line 42
Does your implementation include each of the following Does your implementation include each of the following
notifications? Indicate yes or no (Y or N) for each notifications? Indicate yes or no (Y or N) for each
notification: notification:
(Y) bgpEstablished (Y) bgpEstablished
(Y) bgpBackwardTransition (Y) bgpBackwardTransition
- transition from Established to Idle only. - transition from Established to Idle only.
Does your implementation initialize bgpPeerInUpdates, Does your implementation initialize bgpPeerInUpdates,
bgpPeerOutUpdates, bgpPeerInTotalMessages and bgpPeerOutUpdates, bgpPeerInTotalMessages, and
bgpPeerOutTotalMessages counters to zero? bgpPeerOutTotalMessages counters to zero?
Yes. Yes.
BGP-4 MIB Implementation Survey October 2004
Does your implementation reset the bgpPeerInUpdates, Does your implementation reset the bgpPeerInUpdates,
bgpPeerOutUpdates, bgpPeerInTotalMessages and bgpPeerOutUpdates, bgpPeerInTotalMessages, and
bgpPeerOutTotalMessages counters to zero bgpPeerOutTotalMessages counters to zero
when a configured peer enters the established state? when a configured peer enters the established state?
Yes. Yes.
4. 4. MIB Walks
MIB Walks
The following MIB walks were provided by the respondents, as The following MIB walks were provided by the respondents, as
identified. identified.
4.1 4.1. Cisco Systems
Cisco Systems
BGP4-MIB::bgpVersion.0 BGP4-MIB::bgpVersion.0
= Hex-STRING: 10 = Hex-STRING: 10
BGP4-MIB::bgpLocalAs.0 BGP4-MIB::bgpLocalAs.0
= INTEGER: 65000 = INTEGER: 65000
BGP4-MIB::bgpPeerIdentifier.10.10.1.29 BGP4-MIB::bgpPeerIdentifier.10.10.1.29
= IpAddress: 10.10.2.229 = IpAddress: 10.10.2.229
BGP4-MIB::bgpPeerIdentifier.11.10.128.3 BGP4-MIB::bgpPeerIdentifier.11.10.128.3
= IpAddress: 11.10.128.3 = IpAddress: 11.10.128.3
BGP4-MIB::bgpPeerState.10.10.1.29 BGP4-MIB::bgpPeerState.10.10.1.29
skipping to change at page 15, line 4 skipping to change at page 15, line 4
BGP4-MIB::bgpPeerLocalPort.10.10.1.29 BGP4-MIB::bgpPeerLocalPort.10.10.1.29
= INTEGER: 11014 = INTEGER: 11014
BGP4-MIB::bgpPeerLocalPort.11.10.128.3 BGP4-MIB::bgpPeerLocalPort.11.10.128.3
= INTEGER: 11013 = INTEGER: 11013
BGP4-MIB::bgpPeerRemoteAddr.10.10.1.29 BGP4-MIB::bgpPeerRemoteAddr.10.10.1.29
= IpAddress: 10.10.1.29 = IpAddress: 10.10.1.29
BGP4-MIB::bgpPeerRemoteAddr.11.10.128.3 BGP4-MIB::bgpPeerRemoteAddr.11.10.128.3
= IpAddress: 11.10.128.3 = IpAddress: 11.10.128.3
BGP4-MIB::bgpPeerRemotePort.10.10.1.29 BGP4-MIB::bgpPeerRemotePort.10.10.1.29
= INTEGER: 179 = INTEGER: 179
BGP-4 MIB Implementation Survey October 2004
BGP4-MIB::bgpPeerRemotePort.11.10.128.3 BGP4-MIB::bgpPeerRemotePort.11.10.128.3
= INTEGER: 179 = INTEGER: 179
BGP4-MIB::bgpPeerRemoteAs.10.10.1.29 BGP4-MIB::bgpPeerRemoteAs.10.10.1.29
= INTEGER: 2 = INTEGER: 2
BGP4-MIB::bgpPeerRemoteAs.11.10.128.3 BGP4-MIB::bgpPeerRemoteAs.11.10.128.3
= INTEGER: 65000 = INTEGER: 65000
BGP4-MIB::bgpPeerInUpdates.10.10.1.29 BGP4-MIB::bgpPeerInUpdates.10.10.1.29
= Counter32: 54 = Counter32: 54
BGP4-MIB::bgpPeerInUpdates.11.10.128.3 BGP4-MIB::bgpPeerInUpdates.11.10.128.3
= Counter32: 5 = Counter32: 5
skipping to change at page 16, line 4 skipping to change at page 16, line 5
= INTEGER: 180 = INTEGER: 180
BGP4-MIB::bgpPeerHoldTime.11.10.128.3 BGP4-MIB::bgpPeerHoldTime.11.10.128.3
= INTEGER: 180 = INTEGER: 180
BGP4-MIB::bgpPeerKeepAlive.10.10.1.29 BGP4-MIB::bgpPeerKeepAlive.10.10.1.29
= INTEGER: 60 = INTEGER: 60
BGP4-MIB::bgpPeerKeepAlive.11.10.128.3 BGP4-MIB::bgpPeerKeepAlive.11.10.128.3
= INTEGER: 60 = INTEGER: 60
BGP4-MIB::bgpPeerHoldTimeConfigured.10.10.1.29 BGP4-MIB::bgpPeerHoldTimeConfigured.10.10.1.29
= INTEGER: 180 = INTEGER: 180
BGP4-MIB::bgpPeerHoldTimeConfigured.11.10.128.3 BGP4-MIB::bgpPeerHoldTimeConfigured.11.10.128.3
BGP-4 MIB Implementation Survey October 2004
= INTEGER: 180 = INTEGER: 180
BGP4-MIB::bgpPeerKeepAliveConfigured.10.10.1.29 BGP4-MIB::bgpPeerKeepAliveConfigured.10.10.1.29
= INTEGER: 60 = INTEGER: 60
BGP4-MIB::bgpPeerKeepAliveConfigured.11.10.128.3 BGP4-MIB::bgpPeerKeepAliveConfigured.11.10.128.3
= INTEGER: 60 = INTEGER: 60
BGP4-MIB::bgpPeerMinASOriginationInterval.10.10.1.29 BGP4-MIB::bgpPeerMinASOriginationInterval.10.10.1.29
= INTEGER: 0 = INTEGER: 0
B BGP4-MIB::bgpPeerMinASOriginationInterval.11.10.128.3
GP4-MIB::bgpPeerMinASOriginationInterval.11.10.128.3
= INTEGER: 0 = INTEGER: 0
BGP4-MIB::bgpPeerMinRouteAdvertisementInterval.10.10.1.29 BGP4-MIB::bgpPeerMinRouteAdvertisementInterval.10.10.1.29
= INTEGER: 0 = INTEGER: 0
BGP4-MIB::bgpPeerMinRouteAdvertisementInterval.11.10.128.3 BGP4-MIB::bgpPeerMinRouteAdvertisementInterval.11.10.128.3
= INTEGER: 0 = INTEGER: 0
BGP4-MIB::bgpPeerInUpdateElapsedTime.10.10.1.29 BGP4-MIB::bgpPeerInUpdateElapsedTime.10.10.1.29
= Gauge32: 103451 = Gauge32: 103451
BGP4-MIB::bgpPeerInUpdateElapsedTime.11.10.128.3 BGP4-MIB::bgpPeerInUpdateElapsedTime.11.10.128.3
= Gauge32: 776416 = Gauge32: 776416
BGP4-MIB::bgpIdentifier.0 BGP4-MIB::bgpIdentifier.0
skipping to change at page 17, line 4 skipping to change at page 17, line 6
BGP4-MIB::bgp4PathAttrPeer.10.10.3.0.24.11.10.128.3 BGP4-MIB::bgp4PathAttrPeer.10.10.3.0.24.11.10.128.3
= IpAddress: 11.10.128.3 = IpAddress: 11.10.128.3
BGP4-MIB::bgp4PathAttrPeer.10.10.6.0.24.11.10.128.3 BGP4-MIB::bgp4PathAttrPeer.10.10.6.0.24.11.10.128.3
= IpAddress: 11.10.128.3 = IpAddress: 11.10.128.3
BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.10.10.1.21.32.10.10.1.29 BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.10.10.1.21.32.10.10.1.29
= INTEGER: 32 = INTEGER: 32
BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.10.10.1.22.32.10.10.1.29 BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.10.10.1.22.32.10.10.1.29
= INTEGER: 32 = INTEGER: 32
BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.10.10.1.23.32.10.10.1.29 BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.10.10.1.23.32.10.10.1.29
= INTEGER: 32 = INTEGER: 32
BGP-4 MIB Implementation Survey October 2004
BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.10.10.1.29.32.10.10.1.29 BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.10.10.1.29.32.10.10.1.29
= INTEGER: 32 = INTEGER: 32
BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.10.10.1.32.32.11.10.128.3 BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.10.10.1.32.32.11.10.128.3
= INTEGER: 32 = INTEGER: 32
BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.10.10.1.33.32.11.10.128.3 BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.10.10.1.33.32.11.10.128.3
= INTEGER: 32 = INTEGER: 32
BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.10.10.1.34.32.11.10.128.3 BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.10.10.1.34.32.11.10.128.3
= INTEGER: 32 = INTEGER: 32
BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.10.10.1.61.32.11.10.128.3 BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.10.10.1.61.32.11.10.128.3
= INTEGER: 32 = INTEGER: 32
skipping to change at page 18, line 4 skipping to change at page 18, line 7
= IpAddress: 10.10.3.0 = IpAddress: 10.10.3.0
BGP4-MIB::bgp4PathAttrIpAddrPrefix.10.10.6.0.24.11.10.128.3 BGP4-MIB::bgp4PathAttrIpAddrPrefix.10.10.6.0.24.11.10.128.3
= IpAddress: 10.10.6.0 = IpAddress: 10.10.6.0
BGP4-MIB::bgp4PathAttrOrigin.10.10.1.21.32.10.10.1.29 BGP4-MIB::bgp4PathAttrOrigin.10.10.1.21.32.10.10.1.29
= INTEGER: igp(1) = INTEGER: igp(1)
BGP4-MIB::bgp4PathAttrOrigin.10.10.1.22.32.10.10.1.29 BGP4-MIB::bgp4PathAttrOrigin.10.10.1.22.32.10.10.1.29
= INTEGER: igp(1) = INTEGER: igp(1)
BGP4-MIB::bgp4PathAttrOrigin.10.10.1.23.32.10.10.1.29 BGP4-MIB::bgp4PathAttrOrigin.10.10.1.23.32.10.10.1.29
= INTEGER: igp(1) = INTEGER: igp(1)
BGP4-MIB::bgp4PathAttrOrigin.10.10.1.29.32.10.10.1.29 BGP4-MIB::bgp4PathAttrOrigin.10.10.1.29.32.10.10.1.29
BGP-4 MIB Implementation Survey October 2004
= INTEGER: igp(1) = INTEGER: igp(1)
BGP4-MIB::bgp4PathAttrOrigin.10.10.1.32.32.11.10.128.3 BGP4-MIB::bgp4PathAttrOrigin.10.10.1.32.32.11.10.128.3
= INTEGER: igp(1) = INTEGER: igp(1)
BGP4-MIB::bgp4PathAttrOrigin.10.10.1.33.32.11.10.128.3 BGP4-MIB::bgp4PathAttrOrigin.10.10.1.33.32.11.10.128.3
= INTEGER: igp(1) = INTEGER: igp(1)
BGP4-MIB::bgp4PathAttrOrigin.10.10.1.34.32.11.10.128.3 BGP4-MIB::bgp4PathAttrOrigin.10.10.1.34.32.11.10.128.3
= INTEGER: igp(1) = INTEGER: igp(1)
BGP4-MIB::bgp4PathAttrOrigin.10.10.1.61.32.11.10.128.3 BGP4-MIB::bgp4PathAttrOrigin.10.10.1.61.32.11.10.128.3
= INTEGER: igp(1) = INTEGER: igp(1)
BGP4-MIB::bgp4PathAttrOrigin.10.10.1.62.32.11.10.128.3 BGP4-MIB::bgp4PathAttrOrigin.10.10.1.62.32.11.10.128.3
skipping to change at page 19, line 4 skipping to change at page 19, line 8
BGP4-MIB::bgp4PathAttrASPathSegment.10.10.6.0.24.11.10.128.3 BGP4-MIB::bgp4PathAttrASPathSegment.10.10.6.0.24.11.10.128.3
= Hex-STRING: 02 01 00 03 = Hex-STRING: 02 01 00 03
BGP4-MIB::bgp4PathAttrNextHop.10.10.1.21.32.10.10.1.29 BGP4-MIB::bgp4PathAttrNextHop.10.10.1.21.32.10.10.1.29
= IpAddress: 10.10.1.29 = IpAddress: 10.10.1.29
BGP4-MIB::bgp4PathAttrNextHop.10.10.1.22.32.10.10.1.29 BGP4-MIB::bgp4PathAttrNextHop.10.10.1.22.32.10.10.1.29
= IpAddress: 10.10.1.29 = IpAddress: 10.10.1.29
BGP4-MIB::bgp4PathAttrNextHop.10.10.1.23.32.10.10.1.29 BGP4-MIB::bgp4PathAttrNextHop.10.10.1.23.32.10.10.1.29
= IpAddress: 10.10.1.29 = IpAddress: 10.10.1.29
BGP4-MIB::bgp4PathAttrNextHop.10.10.1.29.32.10.10.1.29 BGP4-MIB::bgp4PathAttrNextHop.10.10.1.29.32.10.10.1.29
= IpAddress: 10.10.1.29 = IpAddress: 10.10.1.29
BGP-4 MIB Implementation Survey October 2004
BGP4-MIB::bgp4PathAttrNextHop.10.10.1.32.32.11.10.128.3 BGP4-MIB::bgp4PathAttrNextHop.10.10.1.32.32.11.10.128.3
= IpAddress: 11.10.128.3 = IpAddress: 11.10.128.3
BGP4-MIB::bgp4PathAttrNextHop.10.10.1.33.32.11.10.128.3 BGP4-MIB::bgp4PathAttrNextHop.10.10.1.33.32.11.10.128.3
= IpAddress: 11.10.128.3 = IpAddress: 11.10.128.3
BGP4-MIB::bgp4PathAttrNextHop.10.10.1.34.32.11.10.128.3 BGP4-MIB::bgp4PathAttrNextHop.10.10.1.34.32.11.10.128.3
= IpAddress: 11.10.128.3 = IpAddress: 11.10.128.3
BGP4-MIB::bgp4PathAttrNextHop.10.10.1.61.32.11.10.128.3 BGP4-MIB::bgp4PathAttrNextHop.10.10.1.61.32.11.10.128.3
= IpAddress: 11.10.128.3 = IpAddress: 11.10.128.3
BGP4-MIB::bgp4PathAttrNextHop.10.10.1.62.32.11.10.128.3 BGP4-MIB::bgp4PathAttrNextHop.10.10.1.62.32.11.10.128.3
= IpAddress: 11.10.128.3 = IpAddress: 11.10.128.3
skipping to change at page 19, line 32 skipping to change at page 19, line 33
= IpAddress: 11.10.128.3 = IpAddress: 11.10.128.3
BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.21.32.10.10.1.29 BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.21.32.10.10.1.29
= INTEGER: -1 = INTEGER: -1
BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.22.32.10.10.1.29 BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.22.32.10.10.1.29
= INTEGER: -1 = INTEGER: -1
BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.23.32.10.10.1.29 BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.23.32.10.10.1.29
= INTEGER: -1 = INTEGER: -1
BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.29.32.10.10.1.29 BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.29.32.10.10.1.29
= INTEGER: 0 = INTEGER: 0
BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.32.32.11.10.128.3 BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.32.32.11.10.128.3
= INTE = INTEGER: 0
GER: 0
BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.33.32.11.10.128.3 BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.33.32.11.10.128.3
= INTEGER: 0 = INTEGER: 0
BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.34.32.11.10.128.3 BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.34.32.11.10.128.3
= INTEGER: 0 = INTEGER: 0
BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.61.32.11.10.128.3 BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.61.32.11.10.128.3
= INTEGER: 0 = INTEGER: 0
BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.62.32.11.10.128.3 BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.1.62.32.11.10.128.3
= INTEGER: 0 = INTEGER: 0
BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.2.0.24.10.10.1.29 BGP4-MIB::bgp4PathAttrMultiExitDisc.10.10.2.0.24.10.10.1.29
= INTEGER: 0 = INTEGER: 0
skipping to change at page 20, line 4 skipping to change at page 20, line 9
= INTEGER: 0 = INTEGER: 0
BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.21.32.10.10.1.29 BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.21.32.10.10.1.29
= INTEGER: -1 = INTEGER: -1
BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.22.32.10.10.1.29 BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.22.32.10.10.1.29
= INTEGER: -1 = INTEGER: -1
BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.23.32.10.10.1.29 BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.23.32.10.10.1.29
= INTEGER: -1 = INTEGER: -1
BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.29.32.10.10.1.29 BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.29.32.10.10.1.29
= INTEGER: -1 = INTEGER: -1
BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.32.32.11.10.128.3 BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.32.32.11.10.128.3
BGP-4 MIB Implementation Survey October 2004
= INTEGER: -1 = INTEGER: -1
BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.33.32.11.10.128.3 BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.33.32.11.10.128.3
= INTEGER: -1 = INTEGER: -1
BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.34.32.11.10.128.3 BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.34.32.11.10.128.3
= INTEGER: -1 = INTEGER: -1
BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.61.32.11.10.128.3 BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.61.32.11.10.128.3
= INTEGER: -1 = INTEGER: -1
BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.62.32.11.10.128.3 BGP4-MIB::bgp4PathAttrLocalPref.10.10.1.62.32.11.10.128.3
= INTEGER: -1 = INTEGER: -1
BGP4-MIB::bgp4PathAttrLocalPref.10.10.2.0.24.10.10.1.29 BGP4-MIB::bgp4PathAttrLocalPref.10.10.2.0.24.10.10.1.29
skipping to change at page 21, line 4 skipping to change at page 21, line 10
BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.21.32.10.10.1.29 BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.21.32.10.10.1.29
= INTEGER: 0 = INTEGER: 0
BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.22.32.10.10.1.29 BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.22.32.10.10.1.29
= INTEGER: 0 = INTEGER: 0
BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.23.32.10.10.1.29 BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.23.32.10.10.1.29
= INTEGER: 0 = INTEGER: 0
BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.29.32.10.10.1.29 BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.29.32.10.10.1.29
= INTEGER: 0 = INTEGER: 0
BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.32.32.11.10.128.3 BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.32.32.11.10.128.3
= INTEGER: 0 = INTEGER: 0
BGP-4 MIB Implementation Survey October 2004
BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.33.32.11.10.128.3 BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.33.32.11.10.128.3
= INTEGER: 0 = INTEGER: 0
BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.34.32.11.10.128.3 BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.34.32.11.10.128.3
= INTEGER: 0 = INTEGER: 0
BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.61.32.11.10.128.3 BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.61.32.11.10.128.3
= INTEGER: 0 = INTEGER: 0
BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.62.32.11.10.128.3 BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.1.62.32.11.10.128.3
= INTEGER: 0 = INTEGER: 0
BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.2.0.24.10.10.1.29 BGP4-MIB::bgp4PathAttrAggregatorAS.10.10.2.0.24.10.10.1.29
= INTEGER: 0 = INTEGER: 0
skipping to change at page 22, line 4 skipping to change at page 22, line 11
= INTEGER: 100 = INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.1.22.32.10.10.1.29 BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.1.22.32.10.10.1.29
= INTEGER: 100 = INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.1.23.32.10.10.1.29 BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.1.23.32.10.10.1.29
= INTEGER: 100 = INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.1.29.32.10.10.1.29 BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.1.29.32.10.10.1.29
= INTEGER: 100 = INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.1.32.32.11.10.128.3 BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.1.32.32.11.10.128.3
= INTEGER: 100 = INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.1.33.32.11.10.128.3 BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.1.33.32.11.10.128.3
BGP-4 MIB Implementation Survey October 2004
= INTEGER: 100 = INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.1.34.32.11.10.128.3 BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.1.34.32.11.10.128.3
= INTEGER: 100 = INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.1.61.32.11.10.128.3 BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.1.61.32.11.10.128.3
= INTEGER: 100 = INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.1.62.32.11.10.128.3 BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.1.62.32.11.10.128.3
= INTEGER: 100 = INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.2.0.24.10.10.1.29 BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.2.0.24.10.10.1.29
= INTEGER: 100 = INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.3.0.24.11.10.128.3 BGP4-MIB::bgp4PathAttrCalcLocalPref.10.10.3.0.24.11.10.128.3
skipping to change at page 22, line 50 skipping to change at page 23, line 6
BGP4-MIB::bgp4PathAttrBest.10.10.3.0.24.11.10.128.3 BGP4-MIB::bgp4PathAttrBest.10.10.3.0.24.11.10.128.3
= INTEGER: true(2) = INTEGER: true(2)
BGP4-MIB::bgp4PathAttrBest.10.10.6.0.24.11.10.128.3 BGP4-MIB::bgp4PathAttrBest.10.10.6.0.24.11.10.128.3
= INTEGER: true(2) = INTEGER: true(2)
BGP4-MIB::bgp4PathAttrUnknown.10.10.1.21.32.10.10.1.29 BGP4-MIB::bgp4PathAttrUnknown.10.10.1.21.32.10.10.1.29
= "" = ""
BGP4-MIB::bgp4PathAttrUnknown.10.10.1.22.32.10.10.1.29 BGP4-MIB::bgp4PathAttrUnknown.10.10.1.22.32.10.10.1.29
= "" = ""
BGP4-MIB::bgp4PathAttrUnknown.10.10.1.23.32.10.10.1.29 BGP4-MIB::bgp4PathAttrUnknown.10.10.1.23.32.10.10.1.29
= "" = ""
BGP4-MIB::bgp4PathA BGP4-MIB::bgp4PathAttrUnknown.10.10.1.29.32.10.10.1.29
ttrUnknown.10.10.1.29.32.10.10.1.29
= "" = ""
BGP4-MIB::bgp4PathAttrUnknown.10.10.1.32.32.11.10.128.3 BGP4-MIB::bgp4PathAttrUnknown.10.10.1.32.32.11.10.128.3
= "" = ""
BGP4-MIB::bgp4PathAttrUnknown.10.10.1.33.32.11.10.128.3 BGP4-MIB::bgp4PathAttrUnknown.10.10.1.33.32.11.10.128.3
= "" = ""
BGP-4 MIB Implementation Survey October 2004
BGP4-MIB::bgp4PathAttrUnknown.10.10.1.34.32.11.10.128.3 BGP4-MIB::bgp4PathAttrUnknown.10.10.1.34.32.11.10.128.3
= "" = ""
BGP4-MIB::bgp4PathAttrUnknown.10.10.1.61.32.11.10.128.3 BGP4-MIB::bgp4PathAttrUnknown.10.10.1.61.32.11.10.128.3
= "" = ""
BGP4-MIB::bgp4PathAttrUnknown.10.10.1.62.32.11.10.128.3 BGP4-MIB::bgp4PathAttrUnknown.10.10.1.62.32.11.10.128.3
= "" = ""
BGP4-MIB::bgp4PathAttrUnknown.10.10.2.0.24.10.10.1.29 BGP4-MIB::bgp4PathAttrUnknown.10.10.2.0.24.10.10.1.29
= "" = ""
BGP4-MIB::bgp4PathAttrUnknown.10.10.3.0.24.11.10.128.3 BGP4-MIB::bgp4PathAttrUnknown.10.10.3.0.24.11.10.128.3
= "" = ""
BGP4-MIB::bgp4PathAttrUnknown.10.10.6.0.24.11.10.128.3 BGP4-MIB::bgp4PathAttrUnknown.10.10.6.0.24.11.10.128.3
= "" = ""
4.2 4.2. NextHop Technologies
NextHop Technologies
BGP4-MIB::bgpVersion.0 = Hex-STRING: 10 BGP4-MIB::bgpVersion.0 = Hex-STRING: 10
BGP4-MIB::bgpLocalAs.0 = INTEGER: 201 BGP4-MIB::bgpLocalAs.0 = INTEGER: 201
BGP4-MIB::bgpPeerIdentifier.10.132.10.14 = IpAddress: 10.132.10.14 BGP4-MIB::bgpPeerIdentifier.10.132.10.14 = IpAddress: 10.132.10.14
BGP4-MIB::bgpPeerState.10.132.10.14 = INTEGER: established(6) BGP4-MIB::bgpPeerState.10.132.10.14 = INTEGER: established(6)
BGP4-MIB::bgpPeerAdminStatus.10.132.10.14 = INTEGER: start(2) BGP4-MIB::bgpPeerAdminStatus.10.132.10.14 = INTEGER: start(2)
BGP4-MIB::bgpPeerNegotiatedVersion.10.132.10.14 = INTEGER: 4 BGP4-MIB::bgpPeerNegotiatedVersion.10.132.10.14 = INTEGER: 4
BGP4-MIB::bgpPeerLocalAddr.10.132.10.14 = IpAddress: 10.132.10.12 BGP4-MIB::bgpPeerLocalAddr.10.132.10.14 = IpAddress: 10.132.10.12
BGP4-MIB::bgpPeerLocalPort.10.132.10.14 = INTEGER: 1639 BGP4-MIB::bgpPeerLocalPort.10.132.10.14 = INTEGER: 1639
BGP4-MIB::bgpPeerRemoteAddr.10.132.10.14 = IpAddress: 10.132.10.14 BGP4-MIB::bgpPeerRemoteAddr.10.132.10.14 = IpAddress: 10.132.10.14
skipping to change at page 24, line 4 skipping to change at page 24, line 14
BGP4-MIB::bgpPeerMinRouteAdvertisementInterval.10.132.10.14 = BGP4-MIB::bgpPeerMinRouteAdvertisementInterval.10.132.10.14 =
INTEGER: 1 INTEGER: 1
BGP4-MIB::bgpPeerInUpdateElapsedTime.10.132.10.14 = Gauge32: 861 BGP4-MIB::bgpPeerInUpdateElapsedTime.10.132.10.14 = Gauge32: 861
BGP4-MIB::bgpIdentifier.0 = IpAddress: 10.132.10.12 BGP4-MIB::bgpIdentifier.0 = IpAddress: 10.132.10.12
BGP4-MIB::bgp4PathAttrPeer.223.1.0.0.24.10.132.10.14 = IpAddress: BGP4-MIB::bgp4PathAttrPeer.223.1.0.0.24.10.132.10.14 = IpAddress:
10.132.10.14 10.132.10.14
BGP4-MIB::bgp4PathAttrPeer.223.2.0.0.24.10.132.10.14 = IpAddress: BGP4-MIB::bgp4PathAttrPeer.223.2.0.0.24.10.132.10.14 = IpAddress:
10.132.10.14 10.132.10.14
BGP4-MIB::bgp4PathAttrPeer.223.3.0.0.24.10.132.10.14 = IpAddress: BGP4-MIB::bgp4PathAttrPeer.223.3.0.0.24.10.132.10.14 = IpAddress:
10.132.10.14 10.132.10.14
BGP-4 MIB Implementation Survey October 2004
BGP4-MIB::bgp4PathAttrPeer.223.137.137.0.24.10.132.10.14 = IpAddress: BGP4-MIB::bgp4PathAttrPeer.223.137.137.0.24.10.132.10.14 = IpAddress:
10.132.10.14 10.132.10.14
BGP4-MIB::bgp4PathAttrPeer.223.137.138.0.24.10.132.10.14 = IpAddress: BGP4-MIB::bgp4PathAttrPeer.223.137.138.0.24.10.132.10.14 = IpAddress:
10.132.10.14 10.132.10.14
BGP4-MIB::bgp4PathAttrPeer.223.137.139.0.24.10.132.10.14 = IpAddress: BGP4-MIB::bgp4PathAttrPeer.223.137.139.0.24.10.132.10.14 = IpAddress:
10.132.10.14 10.132.10.14
BGP4-MIB::bgp4PathAttrPeer.223.137.140.0.24.10.132.10.14 = IpAddress: BGP4-MIB::bgp4PathAttrPeer.223.137.140.0.24.10.132.10.14 = IpAddress:
10.132.10.14 10.132.10.14
BGP4-MIB::bgp4PathAttrPeer.223.137.141.0.24.10.132.10.14 = IpAddress: BGP4-MIB::bgp4PathAttrPeer.223.137.141.0.24.10.132.10.14 = IpAddress:
10.132.10.14 10.132.10.14
skipping to change at page 25, line 4 skipping to change at page 25, line 14
BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.223.137.143.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.223.137.143.0.24.10.132.10.14 =
INTEGER: 24 INTEGER: 24
BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.223.137.144.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.223.137.144.0.24.10.132.10.14 =
INTEGER: 24 INTEGER: 24
BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.223.137.145.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.223.137.145.0.24.10.132.10.14 =
INTEGER: 24 INTEGER: 24
BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.223.137.146.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrIpAddrPrefixLen.223.137.146.0.24.10.132.10.14 =
INTEGER: 24 INTEGER: 24
BGP4-MIB::bgp4PathAttrIpAddrPrefix.223.1.0.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrIpAddrPrefix.223.1.0.0.24.10.132.10.14 =
IpAddress: 223.1.0.0 IpAddress: 223.1.0.0
BGP-4 MIB Implementation Survey October 2004
BGP4-MIB::bgp4PathAttrIpAddrPrefix.223.2.0.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrIpAddrPrefix.223.2.0.0.24.10.132.10.14 =
IpAddress: 223.2.0.0 IpAddress: 223.2.0.0
BGP4-MIB::bgp4PathAttrIpAddrPrefix.223.3.0.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrIpAddrPrefix.223.3.0.0.24.10.132.10.14 =
IpAddress: 223.3.0.0 IpAddress: 223.3.0.0
BGP4-MIB::bgp4PathAttrIpAddrPrefix.223.137.137.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrIpAddrPrefix.223.137.137.0.24.10.132.10.14 =
IpAddress: 223.137.137.0 IpAddress: 223.137.137.0
BGP4-MIB::bgp4PathAttrIpAddrPrefix.223.137.138.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrIpAddrPrefix.223.137.138.0.24.10.132.10.14 =
IpAddress: 223.137.138.0 IpAddress: 223.137.138.0
BGP4-MIB::bgp4PathAttrIpAddrPrefix.223.137.139.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrIpAddrPrefix.223.137.139.0.24.10.132.10.14 =
IpAddress: 223.137.139.0 IpAddress: 223.137.139.0
skipping to change at page 26, line 4 skipping to change at page 26, line 14
BGP4-MIB::bgp4PathAttrOrigin.223.137.141.0.24.10.132.10.14 = INTEGER: BGP4-MIB::bgp4PathAttrOrigin.223.137.141.0.24.10.132.10.14 = INTEGER:
incomplete(3) incomplete(3)
BGP4-MIB::bgp4PathAttrOrigin.223.137.142.0.24.10.132.10.14 = INTEGER: BGP4-MIB::bgp4PathAttrOrigin.223.137.142.0.24.10.132.10.14 = INTEGER:
incomplete(3) incomplete(3)
BGP4-MIB::bgp4PathAttrOrigin.223.137.143.0.24.10.132.10.14 = INTEGER: BGP4-MIB::bgp4PathAttrOrigin.223.137.143.0.24.10.132.10.14 = INTEGER:
incomplete(3) incomplete(3)
BGP4-MIB::bgp4PathAttrOrigin.223.137.144.0.24.10.132.10.14 = INTEGER: BGP4-MIB::bgp4PathAttrOrigin.223.137.144.0.24.10.132.10.14 = INTEGER:
incomplete(3) incomplete(3)
BGP4-MIB::bgp4PathAttrOrigin.223.137.145.0.24.10.132.10.14 = INTEGER: BGP4-MIB::bgp4PathAttrOrigin.223.137.145.0.24.10.132.10.14 = INTEGER:
incomplete(3) incomplete(3)
BGP-4 MIB Implementation Survey October 2004
BGP4-MIB::bgp4PathAttrOrigin.223.137.146.0.24.10.132.10.14 = INTEGER: BGP4-MIB::bgp4PathAttrOrigin.223.137.146.0.24.10.132.10.14 = INTEGER:
incomplete(3) incomplete(3)
BGP4-MIB::bgp4PathAttrASPathSegment.223.1.0.0.24.10.132.10.14 = "" BGP4-MIB::bgp4PathAttrASPathSegment.223.1.0.0.24.10.132.10.14 = ""
BGP4-MIB::bgp4PathAttrASPathSegment.223.2.0.0.24.10.132.10.14 = "" BGP4-MIB::bgp4PathAttrASPathSegment.223.2.0.0.24.10.132.10.14 = ""
BGP4-MIB::bg BGP4-MIB::bgp4PathAttrASPathSegment.223.3.0.0.24.10.132.10.14 = ""
p4PathAttrASPathSegment.223.3.0.0.24.10.132.10.14 = ""
BGP4-MIB::bgp4PathAttrASPathSegment.223.137.137.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrASPathSegment.223.137.137.0.24.10.132.10.14 =
"" ""
BGP4-MIB::bgp4PathAttrASPathSegment.223.137.138.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrASPathSegment.223.137.138.0.24.10.132.10.14 =
"" ""
BGP4-MIB::bgp4PathAttrASPathSegment.223.137.139.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrASPathSegment.223.137.139.0.24.10.132.10.14 =
"" ""
BGP4-MIB::bgp4PathAttrASPathSegment.223.137.140.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrASPathSegment.223.137.140.0.24.10.132.10.14 =
"" ""
BGP4-MIB::bgp4PathAttrASPathSegment.223.137.141.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrASPathSegment.223.137.141.0.24.10.132.10.14 =
"" ""
skipping to change at page 27, line 4 skipping to change at page 27, line 16
BGP4-MIB::bgp4PathAttrNextHop.223.137.141.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrNextHop.223.137.141.0.24.10.132.10.14 =
IpAddress: 10.132.10.242 IpAddress: 10.132.10.242
BGP4-MIB::bgp4PathAttrNextHop.223.137.142.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrNextHop.223.137.142.0.24.10.132.10.14 =
IpAddress: 10.132.10.242 IpAddress: 10.132.10.242
BGP4-MIB::bgp4PathAttrNextHop.223.137.143.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrNextHop.223.137.143.0.24.10.132.10.14 =
IpAddress: 10.132.10.242 IpAddress: 10.132.10.242
BGP4-MIB::bgp4PathAttrNextHop.223.137.144.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrNextHop.223.137.144.0.24.10.132.10.14 =
IpAddress: 10.132.10.242 IpAddress: 10.132.10.242
BGP4-MIB::bgp4PathAttrNextHop.223.137.145.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrNextHop.223.137.145.0.24.10.132.10.14 =
IpAddress: 10.132.10.242 IpAddress: 10.132.10.242
BGP-4 MIB Implementation Survey October 2004
BGP4-MIB::bgp4PathAttrNextHop.223.137.146.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrNextHop.223.137.146.0.24.10.132.10.14 =
IpAddress: 10.132.10.242 IpAddress: 10.132.10.242
BGP4-MIB::bgp4PathAttrMultiExitDisc.223.1.0.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrMultiExitDisc.223.1.0.0.24.10.132.10.14 =
INTEGER: -1 INTEGER: -1
BGP4-MIB::bgp4PathAttrMultiExitDisc.223.2.0.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrMultiExitDisc.223.2.0.0.24.10.132.10.14 =
INTEGER: -1 INTEGER: -1
BGP4-MIB::bgp4PathAttrMultiExitDisc.223.3.0.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrMultiExitDisc.223.3.0.0.24.10.132.10.14 =
INTEGER: -1 INTEGER: -1
BGP4-MIB::bgp4PathAttrMultiExitDisc.223.137.137.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrMultiExitDisc.223.137.137.0.24.10.132.10.14 =
INTEGER: -1 INTEGER: -1
skipping to change at page 28, line 4 skipping to change at page 28, line 16
BGP4-MIB::bgp4PathAttrLocalPref.223.137.139.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrLocalPref.223.137.139.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
BGP4-MIB::bgp4PathAttrLocalPref.223.137.140.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrLocalPref.223.137.140.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
BGP4-MIB::bgp4PathAttrLocalPref.223.137.141.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrLocalPref.223.137.141.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
BGP4-MIB::bgp4PathAttrLocalPref.223.137.142.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrLocalPref.223.137.142.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
BGP4-MIB::bgp4PathAttrLocalPref.223.137.143.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrLocalPref.223.137.143.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
BGP-4 MIB Implementation Survey October 2004
BGP4-MIB::bgp4PathAttrLocalPref.223.137.144.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrLocalPref.223.137.144.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
BGP4-MIB::bgp4PathAttrLocalPref.223.137.145.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrLocalPref.223.137.145.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
BGP4-MIB::bgp4PathAttrLocalPref.223.137.146.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrLocalPref.223.137.146.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
BGP4-MIB::bgp4PathAttrAtomicAggregate.223.1.0.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAtomicAggregate.223.1.0.0.24.10.132.10.14 =
INTEGER: lessSpecificRouteNotSelected(1) INTEGER: lessSpecificRouteNotSelected(1)
BGP4-MIB::bgp4PathAttrAtomicAggregate.223.2.0.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAtomicAggregate.223.2.0.0.24.10.132.10.14 =
INTEGER: lessSpecificRouteNotSelected(1) INTEGER: lessSpecificRouteNotSelected(1)
skipping to change at page 29, line 4 skipping to change at page 29, line 16
BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.137.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.137.0.24.10.132.10.14 =
INTEGER: 0 INTEGER: 0
BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.138.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.138.0.24.10.132.10.14 =
INTEGER: 0 INTEGER: 0
BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.139.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.139.0.24.10.132.10.14 =
INTEGER: 0 INTEGER: 0
BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.140.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.140.0.24.10.132.10.14 =
INTEGER: 0 INTEGER: 0
BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.141.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.141.0.24.10.132.10.14 =
INTEGER: 0 INTEGER: 0
BGP-4 MIB Implementation Survey October 2004
BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.142.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.142.0.24.10.132.10.14 =
INTEGER: 0 INTEGER: 0
BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.143.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.143.0.24.10.132.10.14 =
INTEGER: 0 INTEGER: 0
BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.144.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.144.0.24.10.132.10.14 =
INTEGER: 0 INTEGER: 0
BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.145.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.145.0.24.10.132.10.14 =
INTEGER: 0 INTEGER: 0
BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.146.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAS.223.137.146.0.24.10.132.10.14 =
INTEGER: 0 INTEGER: 0
skipping to change at page 29, line 29 skipping to change at page 29, line 38
BGP4-MIB::bgp4PathAttrAggregatorAddr.223.2.0.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAddr.223.2.0.0.24.10.132.10.14 =
IpAddress: 0.0.0.0 IpAddress: 0.0.0.0
BGP4-MIB::bgp4PathAttrAggregatorAddr.223.3.0.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAddr.223.3.0.0.24.10.132.10.14 =
IpAddress: 0.0.0.0 IpAddress: 0.0.0.0
BGP4-MIB::bgp4PathAttrAggregatorAddr.223.137.137.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAddr.223.137.137.0.24.10.132.10.14 =
IpAddress: 0.0.0.0 IpAddress: 0.0.0.0
BGP4-MIB::bgp4PathAttrAggregatorAddr.223.137.138.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAddr.223.137.138.0.24.10.132.10.14 =
IpAddress: 0.0.0.0 IpAddress: 0.0.0.0
BGP4-MIB::bgp4PathAttrAggregatorAddr.223.137.139.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAddr.223.137.139.0.24.10.132.10.14 =
IpAddress: 0.0.0.0 IpAddress: 0.0.0.0
BGP4-MI BGP4-MIB::bgp4PathAttrAggregatorAddr.223.137.140.0.24.10.132.10.14 =
B::bgp4PathAttrAggregatorAddr.223.137.140.0.24.10.132.10.14 =
IpAddress: 0.0.0.0 IpAddress: 0.0.0.0
BGP4-MIB::bgp4PathAttrAggregatorAddr.223.137.141.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAddr.223.137.141.0.24.10.132.10.14 =
IpAddress: 0.0.0.0 IpAddress: 0.0.0.0
BGP4-MIB::bgp4PathAttrAggregatorAddr.223.137.142.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAddr.223.137.142.0.24.10.132.10.14 =
IpAddress: 0.0.0.0 IpAddress: 0.0.0.0
BGP4-MIB::bgp4PathAttrAggregatorAddr.223.137.143.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAddr.223.137.143.0.24.10.132.10.14 =
IpAddress: 0.0.0.0 IpAddress: 0.0.0.0
BGP4-MIB::bgp4PathAttrAggregatorAddr.223.137.144.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAddr.223.137.144.0.24.10.132.10.14 =
IpAddress: 0.0.0.0 IpAddress: 0.0.0.0
BGP4-MIB::bgp4PathAttrAggregatorAddr.223.137.145.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrAggregatorAddr.223.137.145.0.24.10.132.10.14 =
skipping to change at page 30, line 4 skipping to change at page 30, line 16
BGP4-MIB::bgp4PathAttrCalcLocalPref.223.2.0.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrCalcLocalPref.223.2.0.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.223.3.0.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrCalcLocalPref.223.3.0.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.223.137.137.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrCalcLocalPref.223.137.137.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.223.137.138.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrCalcLocalPref.223.137.138.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.223.137.139.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrCalcLocalPref.223.137.139.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
BGP-4 MIB Implementation Survey October 2004
BGP4-MIB::bgp4PathAttrCalcLocalPref.223.137.140.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrCalcLocalPref.223.137.140.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.223.137.141.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrCalcLocalPref.223.137.141.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.223.137.142.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrCalcLocalPref.223.137.142.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.223.137.143.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrCalcLocalPref.223.137.143.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
BGP4-MIB::bgp4PathAttrCalcLocalPref.223.137.144.0.24.10.132.10.14 = BGP4-MIB::bgp4PathAttrCalcLocalPref.223.137.144.0.24.10.132.10.14 =
INTEGER: 100 INTEGER: 100
skipping to change at page 31, line 4 skipping to change at page 31, line 17
true(2) true(2)
BGP4-MIB::bgp4PathAttrUnknown.223.1.0.0.24.10.132.10.14 = "" BGP4-MIB::bgp4PathAttrUnknown.223.1.0.0.24.10.132.10.14 = ""
BGP4-MIB::bgp4PathAttrUnknown.223.2.0.0.24.10.132.10.14 = "" BGP4-MIB::bgp4PathAttrUnknown.223.2.0.0.24.10.132.10.14 = ""
BGP4-MIB::bgp4PathAttrUnknown.223.3.0.0.24.10.132.10.14 = "" BGP4-MIB::bgp4PathAttrUnknown.223.3.0.0.24.10.132.10.14 = ""
BGP4-MIB::bgp4PathAttrUnknown.223.137.137.0.24.10.132.10.14 = "" BGP4-MIB::bgp4PathAttrUnknown.223.137.137.0.24.10.132.10.14 = ""
BGP4-MIB::bgp4PathAttrUnknown.223.137.138.0.24.10.132.10.14 = "" BGP4-MIB::bgp4PathAttrUnknown.223.137.138.0.24.10.132.10.14 = ""
BGP4-MIB::bgp4PathAttrUnknown.223.137.139.0.24.10.132.10.14 = "" BGP4-MIB::bgp4PathAttrUnknown.223.137.139.0.24.10.132.10.14 = ""
BGP4-MIB::bgp4PathAttrUnknown.223.137.140.0.24.10.132.10.14 = "" BGP4-MIB::bgp4PathAttrUnknown.223.137.140.0.24.10.132.10.14 = ""
BGP4-MIB::bgp4PathAttrUnknown.223.137.141.0.24.10.132.10.14 = "" BGP4-MIB::bgp4PathAttrUnknown.223.137.141.0.24.10.132.10.14 = ""
BGP4-MIB::bgp4PathAttrUnknown.223.137.142.0.24.10.132.10.14 = "" BGP4-MIB::bgp4PathAttrUnknown.223.137.142.0.24.10.132.10.14 = ""
BGP-4 MIB Implementation Survey October 2004
BGP4-MIB::bgp4PathAttrUnknown.223.137.143.0.24.10.132.10.14 = "" BGP4-MIB::bgp4PathAttrUnknown.223.137.143.0.24.10.132.10.14 = ""
BGP4-MIB::bgp4PathAttrUnknown.223.137.144.0.24.10.132.10.14 = "" BGP4-MIB::bgp4PathAttrUnknown.223.137.144.0.24.10.132.10.14 = ""
BGP4-MIB::bgp4PathAttrUnknown.223.137.145.0.24.10.132.10.14 = "" BGP4-MIB::bgp4PathAttrUnknown.223.137.145.0.24.10.132.10.14 = ""
BGP4-MIB::bgp4PathAttrUnknown.223.137.146.0.24.10.132.10.14 = "" BGP4-MIB::bgp4PathAttrUnknown.223.137.146.0.24.10.132.10.14 = ""
4.3 4.3. Redback Networks
Redback Networks
bgpPeerIdentifier.10.12.49.207 = 2.3.4.5 bgpPeerIdentifier.10.12.49.207 = 2.3.4.5
bgpPeerIdentifier.50.1.1.63 = 2.2.2.63 bgpPeerIdentifier.50.1.1.63 = 2.2.2.63
bgpPeerIdentifier.155.53.1.235 = 155.53.1.235 bgpPeerIdentifier.155.53.1.235 = 155.53.1.235
bgpPeerState.10.12.49.207 = established(6) bgpPeerState.10.12.49.207 = established(6)
bgpPeerState.50.1.1.63 = established(6) bgpPeerState.50.1.1.63 = established(6)
bgpPeerState.155.53.1.235 = established(6) bgpPeerState.155.53.1.235 = established(6)
bgpPeerAdminStatus.10.12.49.207 = start(2) bgpPeerAdminStatus.10.12.49.207 = start(2)
bgpPeerAdminStatus.50.1.1.63 = start(2) bgpPeerAdminStatus.50.1.1.63 = start(2)
bgpPeerAdminStatus.155.53.1.235 = start(2) bgpPeerAdminStatus.155.53.1.235 = start(2)
skipping to change at page 32, line 4 skipping to change at page 32, line 18
bgpPeerOutUpdates.155.53.1.235 = 2 bgpPeerOutUpdates.155.53.1.235 = 2
bgpPeerInTotalMessages.10.12.49.207 = 16 bgpPeerInTotalMessages.10.12.49.207 = 16
bgpPeerInTotalMessages.50.1.1.63 = 2 bgpPeerInTotalMessages.50.1.1.63 = 2
bgpPeerInTotalMessages.155.53.1.235 = 21189 bgpPeerInTotalMessages.155.53.1.235 = 21189
bgpPeerOutTotalMessages.10.12.49.207 = 18 bgpPeerOutTotalMessages.10.12.49.207 = 18
bgpPeerOutTotalMessages.50.1.1.63 = 5 bgpPeerOutTotalMessages.50.1.1.63 = 5
bgpPeerOutTotalMessages.155.53.1.235 = 18 bgpPeerOutTotalMessages.155.53.1.235 = 18
bgpPeerLastError.10.12.49.207 = 00 00 bgpPeerLastError.10.12.49.207 = 00 00
bgpPeerLastError.50.1.1.63 = 04 00 bgpPeerLastError.50.1.1.63 = 04 00
bgpPeerLastError.155.53.1.235 = 00 00 bgpPeerLastError.155.53.1.235 = 00 00
BGP-4 MIB Implementation Survey October 2004
bgpPeerFsmEstablishedTransitions.10.12.49.207 = 2 bgpPeerFsmEstablishedTransitions.10.12.49.207 = 2
bgpPeerFsmEstablishedTransitions.50.1.1.63 = 2 bgpPeerFsmEstablishedTransitions.50.1.1.63 = 2
bgpPeerFsmEstablishedTransitions.155.53.1.235 = 2 bgpPeerFsmEstablishedTransitions.155.53.1.235 = 2
bgpPeerFsmEstablishedTime.10.12.49.207 = 669 bgpPeerFsmEstablishedTime.10.12.49.207 = 669
bgpPeerFsmEstablishedTime.50.1.1.63 = 19 bgpPeerFsmEstablishedTime.50.1.1.63 = 19
bgpPeerFsmEstablishedTime.155.53.1.235 = 669 bgpPeerFsmEstablishedTime.155.53.1.235 = 669
bgpPeerConnectRetryInterval.10.12.49.207 = 120 bgpPeerConnectRetryInterval.10.12.49.207 = 120
bgpPeerConnectRetryInterval.50.1.1.63 = 120 bgpPeerConnectRetryInterval.50.1.1.63 = 120
bgpPeerConnectRetryInterval.155.53.1.235 = 120 bgpPeerConnectRetryInterval.155.53.1.235 = 120
bgpPeerHoldTime.10.12.49.207 = 180 bgpPeerHoldTime.10.12.49.207 = 180
skipping to change at page 32, line 48 skipping to change at page 33, line 11
============================================================ ============================================================
bgpVersion.0 = 08 bgpVersion.0 = 08
bgpLocalAs.0 = 300 bgpLocalAs.0 = 300
bgpPeerIdentifier.10.12.49.207 = 2.3.4.5 bgpPeerIdentifier.10.12.49.207 = 2.3.4.5
bgpPeerIdentifier.50.1.1.63 = 0.0.0.0 bgpPeerIdentifier.50.1.1.63 = 0.0.0.0
bgpPeerIdentifier.155.53.1.235 = 155.53.1.235 bgpPeerIdentifier.155.53.1.235 = 155.53.1.235
bgpPeerState.10.12.49.207 = established(6) bgpPeerState.10.12.49.207 = established(6)
bgpPeerState.50.1.1.63 = connect(2) bgpPeerState.50.1.1.63 = connect(2)
bgpPeerState.155.53.1.235 = established(6) bgpPeerState.155.53.1.235 = established(6)
bgpPeerAdminStatus.10.12.49.207 = start(2) bgpPeerAdminStatus.10.12.49.207 = start(2)
bg bgpPeerAdminStatus.50.1.1.63 = start(2)
pPeerAdminStatus.50.1.1.63 = start(2)
bgpPeerAdminStatus.155.53.1.235 = start(2) bgpPeerAdminStatus.155.53.1.235 = start(2)
bgpPeerNegotiatedVersion.10.12.49.207 = 4 bgpPeerNegotiatedVersion.10.12.49.207 = 4
bgpPeerNegotiatedVersion.50.1.1.63 = 0 bgpPeerNegotiatedVersion.50.1.1.63 = 0
bgpPeerNegotiatedVersion.155.53.1.235 = 4 bgpPeerNegotiatedVersion.155.53.1.235 = 4
bgpPeerLocalAddr.10.12.49.207 = 10.12.49.122 bgpPeerLocalAddr.10.12.49.207 = 10.12.49.122
bgpPeerLocalAddr.50.1.1.63 = 0.0.0.0 bgpPeerLocalAddr.50.1.1.63 = 0.0.0.0
bgpPeerLocalAddr.155.53.1.235 = 10.12.49.122 bgpPeerLocalAddr.155.53.1.235 = 10.12.49.122
BGP-4 MIB Implementation Survey October 2004
bgpPeerLocalPort.10.12.49.207 = 65455 bgpPeerLocalPort.10.12.49.207 = 65455
bgpPeerLocalPort.50.1.1.63 = 0 bgpPeerLocalPort.50.1.1.63 = 0
bgpPeerLocalPort.155.53.1.235 = 65456 bgpPeerLocalPort.155.53.1.235 = 65456
bgpPeerRemoteAddr.10.12.49.207 = 10.12.49.207 bgpPeerRemoteAddr.10.12.49.207 = 10.12.49.207
bgpPeerRemoteAddr.50.1.1.63 = 50.1.1.63 bgpPeerRemoteAddr.50.1.1.63 = 50.1.1.63
bgpPeerRemoteAddr.155.53.1.235 = 155.53.1.235 bgpPeerRemoteAddr.155.53.1.235 = 155.53.1.235
bgpPeerRemotePort.10.12.49.207 = 179 bgpPeerRemotePort.10.12.49.207 = 179
bgpPeerRemotePort.50.1.1.63 = 0 bgpPeerRemotePort.50.1.1.63 = 0
bgpPeerRemotePort.155.53.1.235 = 179 bgpPeerRemotePort.155.53.1.235 = 179
bgpPeerRemoteAs.10.12.49.207 = 200 bgpPeerRemoteAs.10.12.49.207 = 200
skipping to change at page 34, line 4 skipping to change at page 34, line 21
bgpPeerKeepAlive.10.12.49.207 = 60 bgpPeerKeepAlive.10.12.49.207 = 60
bgpPeerKeepAlive.50.1.1.63 = 0 bgpPeerKeepAlive.50.1.1.63 = 0
bgpPeerKeepAlive.155.53.1.235 = 60 bgpPeerKeepAlive.155.53.1.235 = 60
bgpPeerHoldTimeConfigured.10.12.49.207 = 180 bgpPeerHoldTimeConfigured.10.12.49.207 = 180
bgpPeerHoldTimeConfigured.50.1.1.63 = 180 bgpPeerHoldTimeConfigured.50.1.1.63 = 180
bgpPeerHoldTimeConfigured.155.53.1.235 = 180 bgpPeerHoldTimeConfigured.155.53.1.235 = 180
bgpPeerKeepAliveConfigured.10.12.49.207 = 60 bgpPeerKeepAliveConfigured.10.12.49.207 = 60
bgpPeerKeepAliveConfigured.50.1.1.63 = 60 bgpPeerKeepAliveConfigured.50.1.1.63 = 60
bgpPeerKeepAliveConfigured.155.53.1.235 = 60 bgpPeerKeepAliveConfigured.155.53.1.235 = 60
bgpPeerMinASOriginationInterval.10.12.49.207 = 15 bgpPeerMinASOriginationInterval.10.12.49.207 = 15
BGP-4 MIB Implementation Survey October 2004
bgpPeerMinASOriginationInterval.50.1.1.63 = 15 bgpPeerMinASOriginationInterval.50.1.1.63 = 15
bgpPeerMinASOriginationInterval.155.53.1.235 = 15 bgpPeerMinASOriginationInterval.155.53.1.235 = 15
bgpPeerMinRouteAdvertisementInterval.10.12.49.207 = 30 bgpPeerMinRouteAdvertisementInterval.10.12.49.207 = 30
bgpPeerMinRouteAdvertisementInterval.50.1.1.63 = 30 bgpPeerMinRouteAdvertisementInterval.50.1.1.63 = 30
bgpPeerMinRouteAdvertisementInterval.155.53.1.235 = 30 bgpPeerMinRouteAdvertisementInterval.155.53.1.235 = 30
bgpPeerInUpdateElapsedTime.10.12.49.207 = 43 bgpPeerInUpdateElapsedTime.10.12.49.207 = 43
bgpPeerInUpdateElapsedTime.50.1.1.63 = 5506 bgpPeerInUpdateElapsedTime.50.1.1.63 = 5506
bgpPeerInUpdateElapsedTime.155.53.1.235 = 0 bgpPeerInUpdateElapsedTime.155.53.1.235 = 0
bgpIdentifier.0 = 14.1.1.1 bgpIdentifier.0 = 14.1.1.1
bgp4PathAttrPeer.1.2.3.0.24.10.12.49.207 = 10.12.49.207 bgp4PathAttrPeer.1.2.3.0.24.10.12.49.207 = 10.12.49.207
skipping to change at page 35, line 4 skipping to change at page 35, line 22
bgp4PathAttrAtomicAggregate.6.8.0.0.20.155.53.1.235 = bgp4PathAttrAtomicAggregate.6.8.0.0.20.155.53.1.235 =
lessSpecificRouteSelected(2) lessSpecificRouteSelected(2)
bgp4PathAttrAggregatorAS.1.2.3.0.24.10.12.49.207 = 0 bgp4PathAttrAggregatorAS.1.2.3.0.24.10.12.49.207 = 0
bgp4PathAttrAggregatorAS.4.4.4.122.32.0.0.0.0 = 0 bgp4PathAttrAggregatorAS.4.4.4.122.32.0.0.0.0 = 0
bgp4PathAttrAggregatorAS.6.8.0.0.20.155.53.1.235 = 0 bgp4PathAttrAggregatorAS.6.8.0.0.20.155.53.1.235 = 0
bgp4PathAttrAggregatorAddr.1.2.3.0.24.10.12.49.207 = 0.0.0.0 bgp4PathAttrAggregatorAddr.1.2.3.0.24.10.12.49.207 = 0.0.0.0
bgp4PathAttrAggregatorAddr.4.4.4.122.32.0.0.0.0 = 0.0.0.0 bgp4PathAttrAggregatorAddr.4.4.4.122.32.0.0.0.0 = 0.0.0.0
bgp4PathAttrAggregatorAddr.6.8.0.0.20.155.53.1.235 = 0.0.0.0 bgp4PathAttrAggregatorAddr.6.8.0.0.20.155.53.1.235 = 0.0.0.0
bgp4PathAttrCalcLocalPref.1.2.3.0.24.10.12.49.207 = 100 bgp4PathAttrCalcLocalPref.1.2.3.0.24.10.12.49.207 = 100
bgp4PathAttrCalcLocalPref.4.4.4.122.32.0.0.0.0 = 100 bgp4PathAttrCalcLocalPref.4.4.4.122.32.0.0.0.0 = 100
BGP-4 MIB Implementation Survey October 2004
bgp4PathAttrCalcLocalPref.6.8.0.0.20.155.53.1.235 = 100 bgp4PathAttrCalcLocalPref.6.8.0.0.20.155.53.1.235 = 100
bgp4PathAttrBest.1.2.3.0.24.10.12.49.207 = true(2) bgp4PathAttrBest.1.2.3.0.24.10.12.49.207 = true(2)
bgp4PathAttrBest.4.4.4.122.32.0.0.0.0 = true(2) bgp4PathAttrBest.4.4.4.122.32.0.0.0.0 = true(2)
bgp4PathAttrBest.6.8.0.0.20.155.53.1.235 = true(2) bgp4PathAttrBest.6.8.0.0.20.155.53.1.235 = true(2)
bgp4PathAttrUnknown.1.2.3.0.24.10.12.49.207 = bgp4PathAttrUnknown.1.2.3.0.24.10.12.49.207 =
bgp4PathAttrUnknown.4.4.4.122.32.0.0.0.0 = bgp4PathAttrUnknown.4.4.4.122.32.0.0.0.0 =
bgp4PathAttrUnknown.6.8.0.0.20.155.53.1.235 = bgp4PathAttrUnknown.6.8.0.0.20.155.53.1.235 =
Security Considerations 5. Security Considerations
This document does not address any security issues. This document does not address any security issues.
Normative References 6. Acknowledgements
[BGP4] Rekhter, Y., Li, T., Hares, S., "A Border Gateway
Protocol 4 (BGP-4)", draft-ietf-idr-bgp4-24.txt,
June 2004
[BGP-V1-MIB]Haas, J., Hares, S., "Definitions of Managed Objects for
the Fourth Version of Border Gateway Protocol (BGP-4)",
draft-ietf-idr-bgp4-mib-14.txt, April 2004
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Our thanks to Russ White (Cisco), Sundar Ramachandran(Cisco), Enke
Requirement Levels", BCP 14, March 1997 Chen (Redback), Jenny (Redback), Sharon Chisolm (Nortel), Jeff Haas
(NextHop), Shane Wright (NextHop) for input to the survey and all the
questions they answered. Thanks to Jeff Haas for his digging out the
reset/initialization issues, and Bert Wijnen for his guidance.
[RFC3667] Bradner, S., "IETF Rights in Contributions", BCP 78, 7. Normative References
February 2004
[RFC3668] Bradner, S. "Intellectual Property Rights in IETF [RFC1657] Willis, S., Burruss, J., and J. Chu, "Definitions of
Technology", BCP 79, February 2004 Managed Objects for the Fourth Version of the Border
Gateway Protocol (BGP-4) using SMIv2", RFC 1657, July
1994.
Acknowledgments [RFC4271] Rekhter, Y., Li, T., and S. Hares, Eds., "A Border Gateway
Protocol 4 (BGP-4)", RFC 4271, January 2006.
Our thanks to Russ White(Cisco), Sundar Ramachandran(Cisco), Enke [RFC4274] Haas, J. and S. Hares, Eds., "Definitions of Managed
Chen(Redback), Jenny (Redback), Sharon Chisolm(Nortel), Jeff Objects for the Fourth Version of Border Gateway Protocol
Haas(NextHop), Shane Wright (NextHop) for input to the survey and all (BGP-4)", RFC 4274, January 2006.
the questions they answered. Thanks to Jeff Haas for his digging
out the reset/initialization issues, and Bert Wijnen for his
guidance.
Authors' Addresses Authors' Addresses
Susan Hares Susan Hares
NextHop Technologies NextHop Technologies
825 Victors Way, Suite 100 825 Victors Way, Suite 100
Ann Arbor, MI 48108 Ann Arbor, MI 48108
Phone: 734-222-1600
BGP v1 MIB Implementation Survey October 2004
Email: skh@nexthop.com Phone: 734-222-1600
EMail: skh@nexthop.com
David Hares David Hares
Hickory Hill Consulting Hickory Hill Consulting
7453 Hickory Hill 7453 Hickory Hill
Saline, MI Saline, MI 48176
Email: dhares@hickoryhill-consulting.com
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any EMail: dhares@hickoryhill-consulting.com
Intellectual Property Rights or other rights that might be claimed
to pe
rtain 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 Full Copyright Statement
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 Copyright (C) The Internet Society (2006).
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.
Disclaimer of Validity This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on This document and the information contained herein are provided on an
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Intellectual Property
BGP v1 MIB Implementation Survey October 2004 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.
Copyright (C) The Internet Society (2004). This document is subject Copies of IPR disclosures made to the IETF Secretariat and any
to the rights, licenses and restrictions contained in BCP 78, and assurances of licenses to be made available, or the result of an
except as set forth therein, the authors retain all their rights. 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. 126 change blocks. 
317 lines changed or deleted 165 lines changed or added

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