draft-ietf-idr-bgp4-mib-08.txt

xorp源码hg

INTERNET DRAFT                  BGP4-MIB                   November 2001



Network Working Group                           Editors of this version:
INTERNET DRAFT                                                   J. Haas
                                                                 NextHop
                                                                S. Hares
                                                                 NextHop
                                            Authors of previous version:
                                                               S. Willis
                                                          Argon Networks
                                                              J. Burruss
                                                                 WinData
                                             Editor of previous version:
                                                                  J. Chu
                                                                  Cosine
                                                           November 2001



                     Definitions of Managed Objects
       for the Fourth Version of Border Gateway Protocol (BGP-4)
                    <draft-ietf-idr-bgp4-mib-08.txt>




1.  Status of this Memo

   This  document  is  an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC 2026.

   Internet-Drafts are working documents  of  the  Internet  Engineering
   Task  Force  (IETF),  its  areas,  and its working groups.  Note that
   other groups may  also  distribute  working  documents  as  Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   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
   http://www.ietf.org/ietf/1id-abstracts.

   The  list  of  Internet-Draft  Shadow  Directories can be accessed at
   http://www.ietf.org/shadow.html.






Expires May 2002                                                [Page 1]

INTERNET DRAFT                  BGP4-MIB                   November 2001



2.  Copyright Notice

   Copyright (C) The Internet Society (1999). All Rights Reserved.


3.  Abstract

   This memo is an extension to the SNMP MIB.  The origin of  this  memo
   is  from  RFC  1269  "Definitions  of  Managed Objects for the Border
   Gateway Protocol (Version 3)", which was 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 as updates references to the
   current SNMP framework documents.

   This  memo  is  intended to document deployed implementations of this
   MIB in a historical context, provide clarifications of some items and
   also  note  errors  where  the  MIB  fails to fully represent the BGP
   protocol.  Work is currently in progress to replace this MIB  with  a
   new  one  representing  the current state of the BGP protocol and its
   extensions.

   Distribution of this memo is unlimited.  Please forward  comments  to
   [e-mail].



4.  Introduction

   This  memo defines a portion of the Management Information Base (MIB)
   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 [BGP, BGPAPPL].


5.  The SNMP Management Framework

   The SNMP  Management  Framework  presently  consists  of  five  major
   components:

     -- An overall architecture, described in RFC 2571 [RFC2571].

     -- Mechanisms  for describing and naming objects and events for the
        purpose of management.  The first version of this  Structure  of
        Management  Information  (SMI)  is called SMIv1 and described in
        STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212]  and  RFC
        1215  [RFC1215].  The second version, called SMIv2, is described
        in STD 58, RFC 2578 [RFC2578], STD 58, RFC  2579  [RFC2579]  and
        STD 58, RFC 2580 [RFC2580].


Expires May 2002                                                [Page 2]

INTERNET DRAFT                  BGP4-MIB                   November 2001



     -- Message  protocols for transferring management information.  The
        first version of the SNMP message protocol is called SNMPv1  and
        described  in  STD  15, RFC 1157 [RFC1157].  A second version of
        the SNMP message protocol, which is not  an  Internet  standards
        track  protocol,  is  called  SNMPv2c  and described in RFC 1901
        [RFC1901] and RFC 1906 [RFC1906].   The  third  version  of  the
        message  protocol  is  called  SNMPv3  and described in RFC 1906
        [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].

     -- Protocol operations for accessing management  information.   The
        first  set  of protocol operations and associated PDU formats is
        described in STD 15,  RFC  1157  [RFC1157].   A  second  set  of
        protocol  operations  and associated PDU formats is described in
        RFC 1905 [RFC1905].

     -- A  set  of  fundamental  applications  described  in  RFC   2573
        [RFC2573]  and the view-based access control mechanism described
        in RFC 2575 [RFC2575].

   A more detailed introduction to the current SNMP Management Framework
   can be found in RFC 2570 [RFC2570].

   Managed  objects are accessed via a virtual information store, termed
   the Management Information Base or  MIB.   Objects  in  the  MIB  are
   defined using the mechanisms defined in the SMI.

   This  memo  specifies a MIB module that is compliant to the SMIv2.  A
   MIB conforming to the SMIv1 can be produced through  the  appropriate
   translations.   The  resulting  translated  MIB  must be semantically
   equivalent, except where objects or events  are  omitted  because  no
   translation  is  possible  (use of Counter64).  Some machine readable
   information in SMIv2 will be converted into textual  descriptions  in
   SMIv1  during the translation process.  However, this loss of machine
   readable information is not considered to change the semantics of the
   MIB.


6.  Overview

   These  objects are used to control and manage a BGP-4 implementation.

   Apart from a few system-wide scalar objects, this MIB is broken  into
   three  tables:  the  BGP  Peer Table, the BGP Received Path Attribute
   Table, and the BGP-4 Received Path Attribute  Table.   The  BGP  Peer
   Table  contains  information  about  state  and  current  activity of
   connections with the BGP peers.  The Received  Path  Attribute  Table
   contains  path attributes received from all peers running BGP version
   3 or less.  The BGP-4 Received Path  Attribute  Table  contains  path


Expires May 2002                                                [Page 3]

INTERNET DRAFT                  BGP4-MIB                   November 2001



   attributes received from all BGP-4 peers.  The actual attributes used
   in determining a route are a subset of the received attribute  tables
   after local routing policy has been applied.















































Expires May 2002                                                [Page 4]

INTERNET DRAFT                  BGP4-MIB                   November 2001



7.  Definitions



    BGP4-MIB DEFINITIONS ::= BEGIN


        IMPORTS
            MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
            IpAddress, Integer32, Counter32, Gauge32, mib-2
                FROM SNMPv2-SMI
            MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
                FROM SNMPv2-CONF;


        bgp MODULE-IDENTITY
            LAST-UPDATED "200111030000Z"
            ORGANIZATION "IETF IDR Working Group"
            CONTACT-INFO "E-mail:  [e-mail]

                          Jeff Haas, Sue Hares  (Editor)
                          517 W. William Street
                          Ann Arbor, MI 48103-4943
                          Tel: [phone]
                          Fax: [phone]
                          E-mail: [e-mail]
                      [e-mail]"

            DESCRIPTION
                    "The MIB module for the BGP-4 protocol.

                     Changes since RFC 1657:

                     1) Fixed the definitions of the traps to
                        make them equivalent to their initial
                        definition in RFC 1269.
                     2) Added compliance and conformance info.
                     3) Updated for latest BGP information
                        draft-ietf-idr-bgp4-15.txt for value of
                        bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref,
                        bgp4PathAttrCalcLocalPref,bgp4PathAttrMultiExitDisc,
                        bgp4PathAttrASPathSegement.
                     4) Added additional clarification commments where
                        needed.
                     5) Noted where objects do not fully reflect
                        the protocol as Known Issues."
            ::= { mib-2 15 }



Expires May 2002                                                [Page 5]

INTERNET DRAFT                  BGP4-MIB                   November 2001



        bgpVersion OBJECT-TYPE
            SYNTAX     OCTET STRING (SIZE (1..255))
            MAX-ACCESS read-only
            STATUS     current
            DESCRIPTION
                    "Vector of supported BGP protocol version
                    numbers.  Each peer negotiates the version
                    from this vector.  Versions are identified
                    via the string of bits contained within this
                    object.  The first octet contains bits 0 to
                    7, the second octet contains bits 8 to 15,
                    and so on, with the most significant bit
                    referring to the lowest bit number in the
                    octet (e.g., the MSB of the first octet
                    refers to bit 0).  If a bit, i, is present
                    and set, then the version (i+1) of the BGP
                    is supported."
            ::= { bgp 1 }


        bgpLocalAs OBJECT-TYPE
            SYNTAX     Integer32 (0..65535)
            MAX-ACCESS read-only
            STATUS     current
            DESCRIPTION
                    "The local autonomous system number."
            ::= { bgp 2 }




        -- BGP Peer table.  This table contains, one entry per
        -- BGP peer, information about the BGP peer.


        bgpPeerTable OBJECT-TYPE
            SYNTAX     SEQUENCE OF BgpPeerEntry
            MAX-ACCESS not-accessible
            STATUS     current
            DESCRIPTION
                    "BGP peer table.  This table contains,
                     one entry per BGP peer, information about the
                     connections with BGP peers."
            ::= { bgp 3 }


        bgpPeerEntry OBJECT-TYPE
            SYNTAX     BgpPeerEntry


Expires May 2002                                                [Page 6]

INTERNET DRAFT                  BGP4-MIB                   November 2001



            MAX-ACCESS not-accessible
            STATUS     current
            DESCRIPTION
                    "Entry containing information about the
                     connection with a BGP peer."
            INDEX { bgpPeerRemoteAddr }
            ::= { bgpPeerTable 1 }


        BgpPeerEntry ::= SEQUENCE {
                bgpPeerIdentifier
                    IpAddress,
                bgpPeerState
                    INTEGER,
                bgpPeerAdminStatus
                    INTEGER,
                bgpPeerNegotiatedVersion
                    Integer32,
                bgpPeerLocalAddr
                    IpAddress,
                bgpPeerLocalPort
                    Integer32,
                bgpPeerRemoteAddr
                    IpAddress,
                bgpPeerRemotePort
                    Integer32,
                bgpPeerRemoteAs
                    Integer32,
                bgpPeerInUpdates
                    Counter32,
                bgpPeerOutUpdates
                    Counter32,
                bgpPeerInTotalMessages
                    Counter32,
                bgpPeerOutTotalMessages
                    Counter32,
                bgpPeerLastError
                    OCTET STRING,
                bgpPeerFsmEstablishedTransitions
                    Counter32,