📄 draft-ietf-idr-bgp4-mibv2-01.txt
字号:
treated as an IP address and more as a generic identifier." ::= { bgpBaseScalars 6 } -- -- Base Scalar Extensions -- bgpBaseScalarExtensions OBJECT IDENTIFIER ::= { bgpBaseScalars 7 } bgpBaseScalarNonCapExts OBJECT IDENTIFIER ::= { bgpBaseScalarExtensions 1 } bgpBaseScalarCapExts OBJECT IDENTIFIER ::= { bgpBaseScalarExtensions 2 } -- -- Base Scalar AS Confederation Extensions -- bgpBaseScalarASConfederationExts OBJECT IDENTIFIER ::= { bgpBaseScalarNonCapExts 1965 } bgpConfederationId OBJECT-TYPE SYNTAX BgpAutonomousSystemNumber MAX-ACCESS read-writeVarious Authors Expires May 21, 2002 [Page 14]Internet Draft BGP-MIB v2 November 21, 2001 STATUS current DESCRIPTION "The local Confederation Identification Number. A value of zero (0) indicates the absence of this value." REFERENCE "RFC 3065 - Autonomous System Confederations for BGP" ::= { bgpBaseScalarASConfederationExts 1 } -- -- Base Scalar Route Reflection Extensions -- bgpBaseScalarRouteReflectionExts OBJECT IDENTIFIER ::= { bgpBaseScalarNonCapExts 1966 } bgpClusterId OBJECT-TYPE SYNTAX BgpIdentifier MAX-ACCESS read-write STATUS current DESCRIPTION "The configured Cluster-ID of the local router. A value of 0.0.0.0 indicates the absence of this value." REFERENCE "RFC 2796 - BGP Route Reflection" ::= { bgpBaseScalarRouteReflectionExts 1 } bgpPeer OBJECT IDENTIFIER ::= { bgp 2 } bgpPeerData OBJECT IDENTIFIER ::= { bgpPeer 1 } -- -- BGP Peer Data -- bgpPeerTable OBJECT-TYPE SYNTAX SEQUENCE OF BgpPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTIONVarious Authors Expires May 21, 2002 [Page 15]Internet Draft BGP-MIB v2 November 21, 2001 "BGP peer table. This table contains, one entry per BGP peer, and information about the connections with BGP peers." ::= { bgpPeerData 1 } bgpPeerEntry OBJECT-TYPE SYNTAX BgpPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entry containing information about the connection with a BGP peer." INDEX { -- JMH We should only need one AddrType? bgpPeerLocalAddrType, bgpPeerLocalAddr, bgpPeerRemoteAddrType, bgpPeerRemoteAddr } ::= { bgpPeerTable 1 } BgpPeerEntry ::= SEQUENCE { bgpPeerIdentifier BgpIdentifier, bgpPeerState INTEGER, bgpPeerAdminStatus INTEGER, bgpPeerConfiguredVersion Unsigned32, bgpPeerNegotiatedVersion Unsigned32, bgpPeerLocalAddrType InetAddressType, bgpPeerLocalAddr InetAddress, bgpPeerLocalPort Integer32, bgpPeerLocalAs BgpAutonomousSystemNumber, bgpPeerRemoteAddrType InetAddressType, bgpPeerRemoteAddr InetAddress, bgpPeerRemotePortVarious Authors Expires May 21, 2002 [Page 16]Internet Draft BGP-MIB v2 November 21, 2001 Integer32, bgpPeerRemoteAs BgpAutonomousSystemNumber, bgpPeerIndex Unsigned32, bgpPeerRowEntryStatus RowStatus } bgpPeerIdentifier OBJECT-TYPE SYNTAX BgpIdentifier MAX-ACCESS read-only STATUS current DESCRIPTION "The BGP Identifier of this entry's BGP peer. This entry should be 0.0.0.0 unless the bgpPeerState is in the openconfirm or the established state." ::= { bgpPeerEntry 1 } bgpPeerState OBJECT-TYPE SYNTAX INTEGER { idle(1), connect(2), active(3), opensent(4), openconfirm(5), established(6) } MAX-ACCESS read-only STATUS current DESCRIPTION "The BGP peer's FSM state." ::= { bgpPeerEntry 2 } -- JMH -- The work here is done by a transition. -- This implies that we stay in a state even though -- automatic start/stop events imply strobing something -- even when the state machine is running. bgpPeerAdminStatus OBJECT-TYPE SYNTAX INTEGER { stop(1), start(2) }Various Authors Expires May 21, 2002 [Page 17]Internet Draft BGP-MIB v2 November 21, 2001 MAX-ACCESS read-write STATUS current DESCRIPTION "The desired state of the BGP connection. A transition from 'stop' to 'start' will cause the BGP Start Event to be generated. A transition from 'start' to 'stop' will cause the BGP Stop Event to be generated. This parameter can be used to restart BGP peer connections. Care should be used in providing write access to this object without adequate authentication." ::= { bgpPeerEntry 3 } -- JMH -- Added this bgpPeerConfiguredVersion OBJECT-TYPE SYNTAX Unsigned32 (1..255) MAX-ACCESS read-write STATUS current DESCRIPTION "The configured version to originally start with this peer. The BGP speaker may permit negotiation to a lower version number of the protocol." ::= { bgpPeerEntry 4 } bgpPeerNegotiatedVersion OBJECT-TYPE SYNTAX Unsigned32 (1..255) MAX-ACCESS read-only STATUS current DESCRIPTION "The negotiated version of BGP running between the two peers." ::= { bgpPeerEntry 5 } bgpPeerLocalAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-write STATUS current DESCRIPTION "The address family of the local end of the peering session." ::= { bgpPeerEntry 6 }Various Authors Expires May 21, 2002 [Page 18]Internet Draft BGP-MIB v2 November 21, 2001 bgpPeerLocalAddr OBJECT-TYPE SYNTAX InetAddress (SIZE (20)) MAX-ACCESS read-write STATUS current DESCRIPTION "The address of the local end of the peering session." ::= { bgpPeerEntry 7 } bgpPeerLocalPort OBJECT-TYPE SYNTAX Integer32 (-1 | 0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The local port for the transport connection between the BGP peers. In the case of a transport for which the notion of 'port' is irrelevant, an instance value of -1 should be returned by the agent for this object." ::= { bgpPeerEntry 8 } bgpPeerLocalAs OBJECT-TYPE SYNTAX BgpAutonomousSystemNumber MAX-ACCESS read-write STATUS current DESCRIPTION "Some implementations of BGP can represent themselves as multiple ASs. This is the AS that this peering session is representing itself as to the remote peer." ::= { bgpPeerEntry 9 } bgpPeerRemoteAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-write STATUS current DESCRIPTION "The address family of the remote end of the peering session." ::= { bgpPeerEntry 10 } bgpPeerRemoteAddr OBJECT-TYPE SYNTAX InetAddress (SIZE (20)) MAX-ACCESS read-write STATUS current DESCRIPTION "The address of the remote end of the peering session."Various Authors Expires May 21, 2002 [Page 19]Internet Draft BGP-MIB v2 November 21, 2001 ::= { bgpPeerEntry 11 } bgpPeerRemotePort OBJECT-TYPE SYNTAX Integer32 (-1 | 0..65535) MAX-ACCESS read-write STATUS current DESCRIPTION "The remote port for the TCP connection between the BGP peers. In the case of a transport for which the notion of 'port' is irrelevant, an instance value of -1 should be returned by the agent for this object. -- JMH - this text needs updating Note that the objects bgpPeerLocalAddr, bgpPeerLocalPort, bgpPeerRemoteAddr and bgpPeerRemotePort provide the appropriate reference to the standard MIB TCP connection table. or even the ipv6 tcp MIB as in rfc2452." ::= { bgpPeerEntry 12 } bgpPeerRemoteAs OBJECT-TYPE SYNTAX BgpAutonomousSystemNumber MAX-ACCESS read-write STATUS current DESCRIPTION "The remote autonomous system number." ::= { bgpPeerEntry 13 } bgpPeerIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "This value is a unique index for the peer entry in the bgpPeerTable. It is assigned by the agent at the point of creation of the bgpPeerTable row entry. While its value is guaranteed to be unique at any time, it is otherwise opaque to the management application with respect to its value or the contiguity of bgpPeerIndex row instance values across rows of the bgpPeerTable. It is used to provide an index structure for other tables whose data is logically per-peer."-- +++wayne (from Tom Nadeau): need text describing fate sharing of index, if-- peering session comes up, peer disconnects, and then this or other peerVarious Authors Expires May 21, 2002 [Page 20]Internet Draft BGP-MIB v2 November 21, 2001-- connects again. Will this grow monotonically? (I think that's the question) ::= { bgpPeerEntry 14 } bgpPeerRowEntryStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-only
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -