As per Relevance of the word mandatory, we have this rfc below:
Network Working Group S.
Request for Comments: 1269 J.
Wellfleet Communications Inc
October 1991
Definitions of Managed
for the Border Gateway Protocol (Version 3)
Status of this
This memo is an extension to the SNMP MIB. This RFC specifies an
standards track protocol for the Internet community, and
discussion and suggestions for improvements. Please refer to
current edition of the "IAB Official Protocol Standards" for
standardization state and status of this protocol. Distribution
this memo is unlimited
1.
This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in TCP/IP-based internets
In particular, it defines objects for managing the Border
Protocol [11,12].
2. The Network Management
The Internet-standard Network Management Framework consists of
components. They are
RFC 1155 which defines the SMI, the mechanisms used for
and naming objects for the purpose of management. RFC 1212
defines a more concise description mechanism, which is
consistent with the SMI
RFC 1156 which defines MIB-I, the core set of managed objects
the Internet suite of protocols. RFC 1213, defines MIB-II,
evolution of MIB-I based on implementation experience and
operational requirements
RFC 1157 which defines the SNMP, the protocol used for
access to managed objects
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
Willis & Burruss [Page 1]
RFC 1269 BGP-3 MIB October 1991
3.
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the subset of Abstract Syntax Notation One (ASN.1) [7]
defined in the SMI. In particular, each object has a name, a syntax
and an encoding. The name is an object identifier,
administratively assigned name, which specifies an object type.
object type together with an object instance serves to
identify a specific instantiation of the object. For
convenience, we often use a textual string, termed the
DESCRIPTOR, to also refer to the object type
The syntax of an object type defines the abstract data
corresponding to that object type. The ASN.1 language is used
this purpose. However, the SMI [3] purposely restricts the ASN.1
constructs which may be used. These restrictions are explicitly
for simplicity
The encoding of an object type is simply how that object type
represented using the object type's syntax. Implicitly tied to
notion of an object type's syntax and encoding is how the object
is represented when being transmitted on the network
The SMI specifies the use of the basic encoding rules of ASN.1 [8],
subject to the additional requirements imposed by the SNMP
3.1. Format of
Section 5 contains contains the specification of all object
contained in this MIB module. The object types are defined using
conventions defined in the SMI, as amended by the
specified in [9,10].
4.
These objects are used to control and manage a BGP [11,12]
implementation
The Border Gateway Protocol (BGP) is an inter-Autonomous
routing protocol. The primary function of a BGP speaking system
to exchange network reachability information with other BGP systems
This network reachability information includes information on
full path of Autonomous Systems that traffic must transit to
these networks
BGP runs over a reliable transport protocol. This eliminates
need to implement explicit update fragmentation, retransmission
Willis & Burruss [Page 2]
RFC 1269 BGP-3 MIB October 1991
acknowledgement, and sequencing. Any authentication scheme used
the transport protocol may be used in addition to BGP's
authentication mechanisms
The planned use of BGP in the Internet environment, including
issues as topology, the interaction between BGP and IGPs, and
enforcement of routing policy rules is presented in a
document [12].
Apart from a few system variables, this MIB is broken into
tables: the BGP Peer Table and the BGP Received Path Attribute Table
The Peer Table reflects information about BGP peer connections,
as their state and current activity. The Received Path
Table contains all attributes received from all peers before
routing policy has been applied. The actual attributes used
determining a route are a subset of the received attribute table
5.
RFC1269-MIB DEFINITIONS ::=
NetworkAddress, IpAddress,
FROM RFC1155-
mib-2
FROM RFC1213-
OBJECT-
FROM RFC-1212
TRAP-
FROM RFC-1215;
-- This MIB module uses the extended OBJECT-TYPE macro
-- defined in [9], and the TRAP-TYPE macro as
-- in [10].
bgp OBJECT IDENTIFIER ::= { mib-2 15 }
bgpVersion OBJECT-
SYNTAX OCTET
ACCESS read-
STATUS
"Vector of supported BGP protocol
numbers. Each peer negotiates the version
this vector. Versions are identified via
string of bits contained within this object
The first octet contains bits 0 to 7,
second octet contains bits 8 to 15, and so on
Willis & Burruss [Page 3]
RFC 1269 BGP-3 MIB October 1991
with the most significant bit referring to
lowest bit number in the octet (e.g., the
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-
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS
"The local autonomous system number."
::= { bgp 2 }
bgpPeerTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS
"The bgp peer table."
::= { bgp 3 }
bgpIdentifier OBJECT-
SYNTAX
ACCESS read-
STATUS
"The BGP Identifier of local system."
::= { bgp 4 }
bgpPeerEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"Information about a BGP peer connection."
{ bgpPeerRemoteAddr }
::= { bgpPeerTable 1 }
BgpPeerEntry ::= SEQUENCE {
IpAddress
INTEGER
INTEGER
Willis & Burruss [Page 4]
RFC 1269 BGP-3 MIB October 1991
INTEGER
IpAddress
INTEGER
IpAddress
INTEGER
INTEGER
Counter
Counter
Counter
Counter
OCTET
}
bgpPeerIdentifier OBJECT-
SYNTAX
ACCESS read-
STATUS
"The BGP Identifier of this entry's BGP peer."
::= { bgpPeerEntry 1 }
bgpPeerState OBJECT-
SYNTAX INTEGER {
idle(1),
connect(2),
active(3),
opensent(4),
openconfirm(5),
established(6)
}
ACCESS read-
STATUS
"The bgp peer connection state. "
::= { bgpPeerEntry 2 }
Willis & Burruss [Page 5]
RFC 1269 BGP-3 MIB October 1991
bgpPeerAdminStatus OBJECT-
SYNTAX
ACCESS read-
STATUS
"The desired state of the BGP connection.
transition from 'stop' to 'start' will
the BGP Start Event to be generated.
transition from 'start' to 'stop' will
the BGP Stop Event to be generated.
parameter can be used to restart BGP
connections. Care should be used in
write access to this object without
authentication."
::= { bgpPeerEntry 3 }
bgpPeerNegotiatedVersion OBJECT-
SYNTAX
ACCESS read-
STATUS
"The negotiated version of BGP running
the two peers. "
::= { bgpPeerEntry 4 }
bgpPeerLocalAddr OBJECT-
SYNTAX
ACCESS read-
STATUS
"The local IP address of this entry's
connection."
::= { bgpPeerEntry 5 }
bgpPeerLocalPort OBJECT-
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS
"The local port for the TCP connection
the BGP peers."
::= { bgpPeerEntry 6 }
bgpPeerRemoteAddr OBJECT-
SYNTAX
ACCESS read-
STATUS
Willis & Burruss [Page 6]
RFC 1269 BGP-3 MIB October 1991
"The remote IP address of this entry's
peer."
::= { bgpPeerEntry 7 }
bgpPeerRemotePort OBJECT-
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS
"The remote port for the TCP connection
the BGP peers. Note that the
bgpLocalAddr, bgpLocalPort, bgpRemoteAddr
bgpRemotePort provide the appropriate
to the standard MIB TCP connection table."
::= { bgpPeerEntry 8 }
bgpPeerRemoteAs OBJECT-
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS
"The remote autonomous system number."
::= { bgpPeerEntry 9 }
bgpPeerInUpdates OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of BGP UPDATE messages received
this connection. This object should
initialized to zero when the connection
established."
::= { bgpPeerEntry 10 }
bgpPeerOutUpdates OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of BGP UPDATE messages received
this connection. This object should
initialized to zero when the connection
established."
::= { bgpPeerEntry 11}
bgpPeerInTotalMessages OBJECT-
SYNTAX
Willis & Burruss [Page 7]
RFC 1269 BGP-3 MIB October 1991
ACCESS read-
STATUS
"The total number of messages received from
remote peer on this connection. This
should be initialized to zero when
connection is established."
::= { bgpPeerEntry 12 }
bgpPeerOutTotalMessages OBJECT-
SYNTAX
ACCESS read-
STATUS
"The total number of messages transmitted
the remote peer on this connection. This
should be initialized to zero when
connection is established."
::= { bgpPeerEntry 13 }
bgpPeerLastError OBJECT-
SYNTAX OCTET STRING (SIZE (2))
ACCESS read-
STATUS
"The last error code and subcode seen by
peer on this connection. If no error
occurred, this field is zero. Otherwise,
first byte of this two byte OCTET
contains the error code; the second
the subcode."
::= { bgpPeerEntry 14 }
bgpRcvdPathAttrTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS
"The BGP Received Path Attribute Table
information about paths to destination
received by all peers."
::= { bgp 5 }
bgpPathAttrEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
Willis & Burruss [Page 8]
RFC 1269 BGP-3 MIB October 1991
"Information about a path to a network."
{ bgpPathAttrDestNetwork
bgpPathAttrPeer }
::= { bgpRcvdPathAttrTable 1 }
BgpPathAttrEntry ::= SEQUENCE {
IpAddress
IpAddress
INTEGER
OCTET STRING
IpAddress
}
bgpPathAttrPeer OBJECT-
SYNTAX
ACCESS read-
STATUS
"The IP address of the peer where the
was learned."
::= { bgpPathAttrEntry 1 }
bgpPathAttrDestNetwork OBJECT-
SYNTAX
ACCESS read-
STATUS
"The address of the destination network."
::= { bgpPathAttrEntry 2 }
bgpPathAttrOrigin OBJECT-
SYNTAX INTEGER {
igp(1),-- networks are
egp(2),-- networks learned via
incomplete(3) --
}
ACCESS read-
STATUS
Willis & Burruss [Page 9]
RFC 1269 BGP-3 MIB October 1991
"The ultimate origin of the path information."
::= { bgpPathAttrEntry 3 }
bgpPathAttrASPath OBJECT-
SYNTAX OCTET
ACCESS read-
STATUS
"The set of ASs that must be traversed to
the network. ( This object is probably
represented as SEQUENCE OF INTEGER. For
compatibility, though, it is represented
OCTET STRING. Each AS is represented as a
of octets according to the following algorithm
first-byte-of-pair = ASNumber / 256;
second-byte-of-pair = ASNumber & 255;"
::= { bgpPathAttrEntry 4 }
bgpPathAttrNextHop OBJECT-
SYNTAX
ACCESS read-
STATUS
"The address of the border router that
be used for the destination network."
::= { bgpPathAttrEntry 5 }
bgpPathAttrInterASMetric OBJECT-
SYNTAX
ACCESS read-
STATUS
"The optional inter-AS metric. If
attribute has not been provided for this route
the value for this object is 0."
::= { bgpPathAttrEntry 6 }
bgpEstablished TRAP-
ENTERPRISE { bgp }
VARIABLES { bgpPeerRemoteAddr
bgpPeerLastError
bgpPeerState }
"The BGP Established event is generated
the BGP FSM enters the ESTABLISHED state. "
::= 1
Willis & Burruss [Page 10]
RFC 1269 BGP-3 MIB October 1991
bgpBackwardTransition TRAP-
ENTERPRISE { bgp }
VARIABLES { bgpPeerRemoteAddr
bgpPeerLastError
bgpPeerState }
"The BGPBackwardTransition Event is
when the BGP FSM moves from a higher
state to a lower numbered state."
::= 2
6.
We would like to acknowledge the assistance of all the members of
Interconnectivity Working Group, and particularly the
individuals
Yakov Rekhter,
Rob Coltun, University of
Guy Almes, Rice
Jeff Honig, Cornell Theory
Marshall T. Rose, PSI, Inc
Dennis Ferguson, University of
Mike Mathis,
7.
[1] Cerf, V., "IAB Recommendations for the Development of
Network Management Standards", RFC 1052, NRI, April 1988.
[2] Cerf, V., "Report of the Second Ad Hoc Network Management
Group", RFC 1109, NRI, August 1989.
[3] Rose M., and K. McCloghrie, "Structure and Identification
Management Information for TCP/IP-based internets", RFC 1155,
Performance Systems International, Hughes LAN Systems, May 1990.
[4] McCloghrie K., and M. Rose, "Management Information Base
Network Management of TCP/IP-based internets", RFC 1156,
LAN Systems, Performance Systems International, May 1990.
[5] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "
Network Management Protocol", RFC 1157, SNMP Research
Performance Systems International, Performance
International, MIT Laboratory for Computer Science, May 1990.
[6] McCloghrie K., and M. Rose, Editors, "Management Information
Willis & Burruss [Page 11]
RFC 1269 BGP-3 MIB October 1991
for Network Management of TCP/IP-based internets", RFC 1213,
Performance Systems International, March 1991.
[7] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization,
Standard 8824, December 1987.
[8] Information processing systems - Open Systems Interconnection -
Specification of Basic Encoding Rules for Abstract Notation
(ASN.1), International Organization for Standardization
International Standard 8825, December 1987.
[9] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
RFC 1212, Performance Systems International, Hughes LAN Systems
March 1991.
[10] Rose, M., Editor, "A Convention for Defining Traps for use
the SNMP", RFC 1215, Performance Systems International,
1991.
[11] Lougheed, K., and Y. Rekhter, "A Border Gateway Protocol 3 (BGP
3)", RFC 1267, cisco Systems, T.J. Watson Research Center,
Corp., October 1991.
[12] Rekhter, Y., and P. Gross, Editors, "Application of the
Gateway Protocol in the Internet", RFC 1268, T.J. Watson
Center, IBM Corp., ANS, October 1991.
8. Security
Security issues are not discussed in this memo
Willis & Burruss [Page 12]
RFC 1269 BGP-3 MIB October 1991
Authors'
Steven
Wellfleet Communications Inc
15 Crosby
Bedford, MA 01730
Phone: (617) 275-2400
Email: swillis@wellfleet.
John
Wellfleet Communications Inc
15 Crosby
Bedford, MA 01730
Phone: (617) 275-2400
Email: jburruss@wellfleet.
Willis & Burruss [Page 13]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
