FORCE10-BGP4-V2-MIB: View SNMP OID List / Download MIB

This MIB module defines management objects for the Border Gateway Protocol, Version 4.

The BGP Established event is generated when the BGP FSM enters the ESTABLISHED state.

The BGPBackwardTransition Event is generated when the BGP FSM moves from a higher numbered state to a lower numbered state.

Table of supported BGP versions.

Entry containing data on a given supported version of the Border Gateway Protocol and the level of support provided. It is expected that any agent implementation supporting this MIB module will report support for Version 4 of the Border Gateway Protocol at the very minimum.

The version number of the BGP Protocol.

This value is TRUE if this version of the BGP protocol identified in 'f10BgpM2VersionIndex' is supported. The absence of a row for a particular f10BgpM2VersionIndex indicates that that f10BgpM2VersionIndex protocol version number is not supported.

This value is TRUE if capability support is available and is enabled.

Table of supported BGP-4 capabilities.

Information about supported capabilities indexed by capability number.

Index of supported capability. The index directly corresponds with the BGP-4 Capability Advertisement Capability Code.

This value is True if this capability is supported, False otherwise.

The size of the AS value in this implementation. The semantics of this are determined as per the as-4bytes draft. Enumeration: 'twoOctet': 1, 'fourOctet': 2.

The local autonomous system number. If the f10BgpM2AsSize is twoOctet, then the range is constrained to be 0-65535.

The BGP Identifier of local system. Current practice is trending away from this value being treated as an IP address and more as a generic identifier.

This value is TRUE if this implementation supports the BGP Route Reflection Extension and is enabled as a route reflector. If the BGP Route Reflection extension is not supported this value must be FALSE.

The configured Cluster-ID of the BGP Speaker. This will default to the BGP Speaker's F10BgpM2Identifier if this speaker is functioning as a route reflector and an explicit Cluster-ID has not been configured. A value of 0.0.0.0 will be present if Route Reflection is not enabled.

This value is TRUE if this implementation supports the BGP AS Confederations Extension and this router is configured to be in a confederation.

The local Confederation Identification Number. This value will be zero (0) if this BGP Speaker is not a confederation router.

This object specifies the intended storage type for all configurable base scalars.

The local autonomous system number. If the f10BgpM2AsSize is twoOctet, then the range is constrained to be 0-65535.

The BGP Identifier of local system. Current practice is trending away from this value being treated as an IP address and more as a generic identifier.

This value is set to true if this implementation will be supporting route reflection.

The configured Cluster-ID of the BGP Speaker. This will default to the BGP Speaker's F10BgpM2Identifier if this speaker is functioning as a route reflector and an explicit Cluster-ID has not been configured. A value of 0.0.0.0 will be present if Route Reflection is not enabled.

This value is set to true if this implementation will be supporting BGP AS Confederations.

The local Confederation Identification Number. This value will be zero (0) if this BGP Speaker is not a confederation router.

BGP peer table. This table contains, one entry per remote BGP peer, any information about the connections with the remote BGP peers.

Entry containing information about the connection with a remote BGP peer.

The routing instance index. Some BGP implementations permit the creation of multiple instances of a BGP routing process. An example includes RFC 2547 PE-CE routers. Implementations that do not support multiple routing instances should return 1 for this object. XXX TODO - We need to provide a way to configure these in the peer configuration table.

The BGP Identifier of this entry's remote BGP peer. This entry should be 0.0.0.0 unless the f10BgpM2PeerState is in the OpenConfirm or the Established state.

The remote BGP peer's FSM state. Enumeration: 'established': 6, 'openconfirm': 5, 'opensent': 4, 'idle': 1, 'connect': 2, 'active': 3.

Whether or not the BGP FSM for this remote peer is halted or running. The BGP FSM for a remote peer is halted after processing a Stop event. Likewise, it is in the running state after a Start event. The f10BgpM2PeerState will generally be in the idle state when the FSM is halted, although some extensions such as Graceful Restart will leave the peer in the Idle state but with the FSM running. Enumeration: 'halted': 1, 'running': 2.

The configured version to originally start with this remote peer. The BGP speaker may permit negotiation to a lower version number of the protocol.

The negotiated version of BGP running between the two peers.

The address family of the local end of the peering session.

The address of the local end of the peering session.

The local port for the TCP connection between the BGP peers.

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.

The address family of the remote end of the peering session.

The address of the remote end of the peering session.

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. Note that the objects f10BgpM2PeerLocalAddr, f10BgpM2PeerLocalPort, f10BgpM2PeerRemoteAddr and f10BgpM2PeerRemotePort provide the appropriate reference to the standard MIB TCP connection table. or even the ipv6 TCP MIB as in rfc2452.

The remote autonomous system number.

This value is a unique index for the remote peer entry in the f10BgpM2PeerTable. It is assigned by the agent at the point of creation of the f10BgpM2PeerTable 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 f10BgpM2PeerIndex row instance values across rows of the f10BgpM2PeerTable. It is used to provide an index structure for other tables whose data is logically per-peer. For explicitly configured peers, this value will remain consistent until this row is deleted by deleting the configured peers. Unconfigured peers will generate a monotonically increasing number when a BGP FSM is built to process the peering session. Values in the f10BgpM2PeerTable and other tables utilizing f10BgpM2PeerIndex are expected to remain in existence for an arbitrary time after the unconfigured peer has been deleted in order to allow management applications to extract useful management information for those peers. Thus, an unconfigured peer using the same indices as the f10BgpM2PeerTable that comes up while this row still exists will re-utilize the same row.

On a per peer basis, this table reflects the last protocol-defined error encountered and reported on the peer session. If no entry for a given peer, by its f10BgpM2PeerIndex, exists in this table, then no such errors have been observed, reported, and recorded on the session.

Each entry contains information about errors sent and received for a particular BGP peer.

The last error code and subcode received by this BGP Speaker via a NOTIFICATION message for this peer. If no error has occurred, this field is zero. Otherwise, the first byte of this two byte OCTET STRING contains the error code, and the second byte contains the subcode.

The last error code and subcode sent by this BGP Speaker via a NOTIFICATION message to this peer. If no error has occurred, this field is zero. Otherwise, the first byte of this two byte OCTET STRING contains the error code, and the second byte contains the subcode.

The timestamp that the last NOTIFICATION was received from this peer.

The timestamp that the last NOTIFICATION was sent to this peer.

This object contains an implementation specific explanation of the error that was reported.

This object contains an implementation specific explanation of the error that is being reported.

The last error code's data seen by this peer.

The last error code's data sent to this peer.

A table reporting the per-peering session amount of time elapsed and update events since the peering session advanced into the Established state.

Each row contains a set of statistics about time spent and events encountered in the peer session Established state.

This timer indicates how long (in seconds) this peer has been in the Established state or how long since this peer was last in the Established state. It is set to zero when a new peer is configured or the router is booted.

Elapsed time in seconds since the last BGP UPDATE message was received from the peer. Each time f10BgpM2PeerInUpdates is incremented, the value of this object is set to zero (0). This value shall also be zero (0) when the peer is not in the Established state

Per peer management data on BGP session timers.

Each entry corresponds to the current state of BGP timers on a given peering session.

Time interval in seconds for the ConnectRetry timer. The suggested value for this timer is 120 seconds.

Time interval in seconds for the Hold Time configured for this BGP speaker with this peer. This value is placed in an OPEN message sent to this peer by this BGP speaker, and is compared with the Hold Time field in an OPEN message received from the peer when determining the Hold Time (f10BgpM2PeerHoldTime) with the peer. This value must not be less than three seconds if it is not zero (0) in which case the Hold Time is NOT to be established with the peer. The suggested value for this timer is 90 seconds.

Time interval in seconds for the KeepAlive timer configured for this BGP speaker with this peer. The value of this object will only determine the KEEPALIVE messages frequency relative to the value specified in f10BgpM2PeerHoldTimeConfigured; the actual time interval for the KEEPALIVE messages is indicated by f10BgpM2PeerKeepAlive. A reasonable maximum value for this timer would be configured to be one third of that of f10BgpM2PeerHoldTimeConfigured. If the value of this object is zero (0), no periodical KEEPALIVE messages are sent to the peer after the BGP connection has been established. The suggested value for this timer is 30 seconds.

Time interval in seconds for the MinASOriginationInterval timer. The suggested value for this timer is 15 seconds.

Time interval in seconds for the MinRouteAdvertisementInterval timer. The suggested value for this timer is 30 seconds.

Current values of per-peer timers which can be dynamically set in the f10BgpM2PeerConfiguredTimersTable. Values reflected in this table are the current operational values, after negotiation from values derived from initial configuration or last set from f10BgpM2PeerConfiguredTimersTable row instances.

Each entry reflects a value of the currently operational, negotiated timers as reflected in the F10BgpM2PeerNegotiatedTimersEntry.

The value of this object is calculated by this BGP Speaker as being; zero (0) - if this was the value sent by the peer and this value is permitted by this BGP Speaker. In this case, no keepalive messages are sent and the Hold Timer is not set. At least three (3). This value is the smaller of the value sent by this peer in the OPEN message and f10BgpM2PeerHoldTimeConfigured for this peer. This value is only defined when the peering session is in the Established state.

Time interval in seconds for the KeepAlive timer established with the peer. The value of this object is calculated by this BGP speaker such that, when compared with f10BgpM2PeerHoldTime, it has the same proportion as what f10BgpM2PeerKeepAliveConfigured has when compared with f10BgpM2PeerHoldTimeConfigured. If the value of this object is zero (0), it indicates that the KeepAlive timer has not been established with the peer, or, the value of f10BgpM2PeerKeepAliveConfigured is zero (0). This value is only defined when the peering session is in the Established state.

This table contains the capabilities that are supported for a given peer.

These entries are keyed by a BGP-4 peer remote address and the BGP Capability Code

The BGP Capability Advertisement Capability Code.

Multiple instances of a given capability may be sent bgp a BGP speaker. This variable is used to index them.

The value of the announced capability.

This table contains the capabilities that are supported for a given peer.

These entries are keyed by a BGP-4 peer remote address and the BGP Capability Code

The BGP Capability Advertisement Capability Code.

Multiple instances of a given capability may be sent bgp a BGP speaker. This variable is used to index them.

The value of the announced capability.

The counters associated with a BGP Peer.

Each entry contains counters of message transmissions and FSM transitions for a given BGP Peering session.

The number of BGP UPDATE messages received on this connection. This object should be initialized to zero (0) when the connection is established.

The number of BGP UPDATE messages transmitted on this connection. This object should be initialized to zero (0) when the connection is established.

The total number of messages received from the remote peer on this connection. This object should be initialized to zero when the connection is established.

The total number of messages transmitted to the remote peer on this connection. This object should be initialized to zero when the connection is established.

The total number of times the BGP FSM transitioned into the established state for this peer.

The number of Keepalive messages received from a peer.Implemented by Dell.

The number of Keepalive messages sent to a peer. Implemented by Dell.

The number of Open messages received from a peer. Implemented by Dell.

The number of Open messages sent to a peer. Implemented by Dell.

The number of Route Refresh messages received from a peer. Implemented by Dell.

The number of Route Refresh messages sent to a peer. Implemented by Dell.

Additional per-peer, per AFI SAFI counters for prefixes

Entry containing information about a bgp-peers prefix counters.

The AFI index of the per-peer, per prefix counters

The SAFI index of the per-peer, per prefix counters

The number of prefixes received from a peer and are stored in the Adj-Ribs-In for that peer.

The number of prefixes for a peer that are installed in the Adj-Ribs-In and are eligible to become active in the Loc-Rib.

The number of prefixes for a peer that are installed in the Adj-Ribs-In and are NOT eligible to become active in the Loc-Rib.

The number of prefixes for a peer that are installed in that peers Adj-Ribs-Out.

The number of prefixes withdrawn by a peer. Implemened by Dell.

The number of prefixes withdrawn from a peer. Implemened by Dell.

Table of route reflection client settings on a per-peer basis.

Entry containing data on a per-peer basis on whether the peer is configured as a route reflector client.

This value indicates whether the given peer is a reflector client of this router, or not. A value of nonClient indicates that this peer is not a reflector client. A value of client indicates that this peer is a reflector client that is not fully meshed with other reflector clients. A value of meshedClient indicates that the peer is a reflector client and is fully meshed with all other reflector clients. This value must be nonClient (0) for BGP external peers. Enumeration: 'client': 1, 'nonClient': 0, 'meshedClient': 2.

Table of confederation member settings on a per-peer basis.

Entry containing data on a per-peer basis on whether the peer is configured as a BGP confederation member.

This value indicates whether the given peer is in our confederation or not.

Table containing rows for administratively starting and stopping peering sessions.

Entry containing row for administratively starting and stopping peers.

This object allows the Manual Stop and Manual Start events to be sent to an activated peering session. Enumeration: 'start': 2, 'stop': 1.

This object contains the next appropriate value to use as an index for creation of a row instance in in the f10BgpM2CfgPeerTable. If the number of available entries in the f10BgpM2CfgPeerTable is exhausted, a retrieval value of this object instance will return 0. A value of 0 may also be returned if the agent is otherwise incapable of f10BgpM2CfgPeerTable row creation at the time of f10BgpM2CfgPeerNextIndex retrieval.

BGP configuration peer table. This table allows the configuration of the parameters for a session with a BGP peer. +++wayne provide description of how config should be done for a peer per table.

Entry containing information set up by a management entity to configure a connection with a BGP peer.

The configured version to originally start with this peer. The BGP speaker may permit negotiation to a lower version number of the protocol depending on the set value of f10BgpM2CfgAllowVersionNegotiation.

If set to true, during session establishment with this peer, negotiation to a version lower than that specified in f10BgpM2CfgPeerConfiguredVersion will be allowed.

The address family of the speakers of this BGP session.

The address of the local end of the peering session.

Autonomous system represented to peer on peering session initialization. Some implementations of BGP can represent themselves as multiple ASes. These implementations can set this to an alternate autonomous system. If this object is set to zero (0) at the point this row instance is set to active, then the implementation will initialize this session representing itself as the value of f10BgpM2CfgLocalAs.

The address family of the speakers of the remote BGP session.

The address of the remote end (destination address of peer) for peering session.

Autonomous system number of the remote peer.

This object type specifies the intended storage type for the f10BgpM2CfgPeerEntry row instance.

This value indicates the current error status of the row denoting the configured error status. If this row is still under creation (has not been activated f10BgpM2CfgPeerRowEntryStatus), then this instance will be set to not-activated (1). At the point that the row is activated, f10BgpM2CfgPeerError will reflect the error status of the row data itself. If there is another session already activated with the same local and remote addresses as denoted by {f10BgpM2CfgPeerLocalAddrType, f10BgpM2CfgPeerLocalAddr, f10BgpM2CfgPeerRemoteAddr}, then the value of this will be set to err-duplicate-peering-session (2). If this row is associated with a peer session whose initialization has been attempted, the value will be set to activated (3) (and, f10BgpM2PeerCfgPeerEntry will be set to the row instance of the entry in the f10BgpM2PeerTable which reflects the state of the peering session). Note that this object only reflects the error as a function of the attempted activation of this row as containing data for a bgp peering session. The actual state of the session at the point of any protocol exchange or session state machine initiation is reflected in the f10BgpM2PeerTable row instance (as reflected through f10BgpM2CfgPeerPeerEntry) associated with this row instance. Enumeration: 'unknown': 0, 'errDuplicatePeeringSession': 2, 'notActivated': 1, 'activated': 3.

Upon activation of the session data contained in this row instance, this object points to an instance of a row within the f10BgpM2PeerTable reflecting the session in its initializing or operational state. Retrieval of this column instance will always yield a value of {0.0} unless the session has successfully been activated (via f10BgpM2CfgPeerRowEntryStatus). Such row instances will always have a value of f10BgpM2CfgPeerError which is activated (3).

This object type is used to control creation, activation, and deletion of this row instance.

Uniquely identifies an instance of a peer row, as an element of configuration.

This specifies the state of the peering session upon activation. If disabled, the FSM is in the halted state and no Automatic Start events are generated. If enabled, the FSM is in the running state and Automatic Start events may be generated. Enumeration: 'halted': 1, 'running': 2.

Table for configuration of per-peer timers.

Entry containing per-peer timer configuration.

Time interval in seconds for the ConnectRetry timer. The suggested value for this timer is 120 seconds.

Time interval in seconds for the Hold Time configured for this BGP speaker with this peer. This value is placed in an OPEN message sent to this peer by this BGP speaker, and is compared with the Hold Time field in an OPEN message received from the peer when determining the Hold Time (f10BgpM2PeerHoldTime) with the peer. This value must not be less than three seconds if it is not zero (0) in which case the Hold Time is NOT to be established with the peer. The suggested value for this timer is 90 seconds.

Time interval in seconds for the KeepAlive timer configured for this BGP speaker with this peer. The value of this object will only determine the KEEPALIVE messages frequency relative to the value specified in f10BgpM2PeerHoldTimeConfigured; the actual time interval for the KEEPALIVE messages is indicated by f10BgpM2PeerKeepAlive. A reasonable maximum value for this timer would be configured to be one third of that of f10BgpM2PeerHoldTimeConfigured. If the value of this object is zero (0), no periodical KEEPALIVE messages are sent to the peer after the BGP connection has been established. The suggested value for this timer is 30 seconds.

Time interval in seconds for the MinASOriginationInterval timer. The suggested value for this timer is 15 seconds.

Time interval in seconds for the MinRouteAdvertisementInterval timer. The suggested value for this timer is 30 seconds.

Table of route reflection client settings on a per-peer basis.

Entry containing data on a per-peer basis on whether the peer is configured as a route reflector client.

This value indicates whether the given peer is a reflector client of this router, or not. A value of nonClient indicates that this peer is not a reflector client. A value of client indicates that this peer is a reflector client that is not fully meshed with other reflector clients. A value of meshedClient indicates that the peer is a reflector client and is fully meshed with all other reflector clients. This value must be nonClient (0) for BGP external peers. Enumeration: 'client': 1, 'nonClient': 0, 'meshedClient': 2.

Table of confederation member settings on a per-peer basis.

Entry containing data on a per-peer basis on whether the peer is configured as a BGP confederation member.

This value indicates whether the given peer is in our confederation or not.

The BGP-4 Received Path Attribute Table contains information about paths to destination networks received from all BGP4 peers. Collectively, this represents the Adj-Ribs-In. The route where f10BgpM2NlriBest is TRUE represents, for this NLRI, the route that is installed in the LocRib from the Adj-Ribs-In.

Information about a path to a network.

This index allows for multiple instances of a base prefix for a certain AFI SAFI from a given peer. This is currently useful for two things: 1. Allowing for a peer in future implementations to send more than a single route instance. 2. Allow for extensions which extend the NLRI field to send the same prefix while utilizing other extension specific information. An example of this is RFC 3107 - Carrying MPLS labels in BGP.

The address family of the prefix for this NLRI.

The subsequent address family of the prefix for this NLRI

The type of the IP address prefix in the Network Layer Reachability Information field. The value of this object is derived from the appropriate value from the f10BgpM2NlriAfi field. Where an appropriate InetAddressType is not available, the value of the object must be unknown(0). XXX TODO - This seems like a hack.

An IP address prefix in the Network Layer Reachability Information field. This object is an IP address containing the prefix with length specified by f10BgpM2PathAttrAddrPrefixLen. Any bits beyond the length specified by f10BgpM2PathAttrAddrPrefixLen are zeroed.

Length in bits of the address prefix in the Network Layer Reachability Information field.

An indication of whether or not this route was chosen as the best BGP4 route.

The degree of preference calculated by the receiving BGP4 speaker for an advertised route.

This value is a unique index for the per-NLRI entry in the f10BgpM2PathAttrTable. It is assigned by the agent at the point of creation of the f10BgpM2PathAttrTable 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 f10BgpM2PathAttrIndex row instance values across rows of the f10BgpM2PeerAttrTable. It is used to provide an index structure for other tables whose data is logically per-peer, per-NLRI.

This object enumerates the type of the row that is pointed to in the table row f10BgpM2NlriOpaquePointer instance, if f10BgpM2NlriOpaquePointer is in fact not a zero length. f10BgpM2NlriOpaqueType is necessary since the data referenced by f10BgpM2NlriOpaquePointer is opaque to BGP. For example, in the case of RFC 3107, the label stack that is pointed to may occur in the mplsLabelStackTable from the MPLS-LSR-MIB, and the instance value of f10BgpM2NlriOpaqueType would be bgpMplsLabelStack(1). Enumeration: 'bgpMplsLabelStack': 1, 'none': 0.

Pointer to a row that decomposes the data that is opaque to the BGP MIB but is sent in the NLRI. This RowPointer has zero (0) length data instance if f10BgpM2NlriOpaqueType is none.

This table contains on a per-peer basis one or more routes from the f10BgpM2NlriTable that have been placed in this peer's Adj-Ribs-Out.

List of BGP routes that have been placed into a peer's Adj-Ribs-Out.

Certain extensions to BGP permit multiple instance of a per afi, per safi prefix to be advertised to a peer. This object allows the enumeration of them.

This object points to the route in the f10BgpM2NlriTable that corresponds to the entry in the peer's Adj-Rib-Out. Outgoing route maps are not reflected at this point as those are part of the Update-Send process.

The number of entries in the f10BgpM2PathAttrTable.

Provides per advertised network-prefix attribute data, as advertised over a peering session.

Each entry contains data about a given network prefix, per-prefix and per-advertising peer.

The ultimate origin of the path information. Enumeration: 'egp': 2, 'incomplete': 3, 'igp': 1.

The address family of the address for the border router that should be used to access the destination network.

The address of the border router that should be used to access the destination network. This address is the nexthop address received in the UPDATE packet. The address family of this object will be the same as that of the prefix in this row. Note that for RFC2545 style double nexthops, this object will always contain the global scope nexthop. f10BgpM2LinkLocalNextHopTable will contain the linklocal scope nexthop. In the case that the mechanism documented in draft-kato-bgp-ipv6-link-local-00.txt is used and only a link local nexthop has been sent, , f10BgpM2LinkLocalNextHopPresent will be false and f10BgpM2PathAttrNextHop will contain the link local nexthop.

Whether or not the MED value is present. If it is not present, the f10BgpM2PathAttrMed object has no useful value and should be set to 0.

This metric is used to discriminate between multiple exit points to an adjacent autonomous system.

Whether or not the LocalPref value is present. If it is not present, the f10BgpM2PathAttrLocalPref object has no useful value and should be set to 0.

The originating BGP4 speakers degree of preference for an advertised route.

When this object is set to atomicAggregatePresent, the ATOMIC_AGGREGATE Path Attribute is present and indicates that the NLRI MUST NOT be made more specific. Enumeration: 'atomicAggregateMissing': 2, 'atomicAggregatePresent': 1.

The AS number of the last BGP4 speaker that performed route aggregation. A value of zero (0) indicates the absence of this attribute. Note propagation of AS of zero is illegal in the Internet.

The IP address of the last BGP4 speaker that performed route aggregation. A value of 0.0.0.0 indicates the absence of this attribute.

This value represents the calculated length of the AS Path according to the rules of the BGP specification. This value is used in route selection.

This is a string depicting the autonomous system path to this network which was received from the peer which advertised it. The format of the string is implementation-dependent, and should be designed for operator readability.

This value is a unique index for the decomposed AS Path in the f10BgpM2AsPathTable. It is assigned by the agent at the point of creation of the f10BgpM2AsPathTable 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 f10BgpM2AsPathIndex row instance values across rows of the f10BgpM2AsPathTable.

This table is present for BGP speakers that support the AS 4byte specification and are functioning as a router between 2-byte and 4-byte AS space.

Each row contains the information for the AS 4-byte extension's NEW_AS_PATH and NEW_AGGREGATOR attributes.

This value may only be true if this BGP Speaker is functioning as a router between ASs that are in 2-byte and 4-byte AS space. If this value is true, then the NEW_AS_PATH attributes are present and the 4-byte versions of the appropriate path attributes are in this row. If this value is false, then the following values will be present in the row: f10BgpM2PathAttrAggregatorAS - zero (0). f10BgpM2AsPathCalcLength - zero (0). f10BgpM2AsPathString - zero (0) length string. f10BgpM2AsPathIndex - zero (0).

The NEW_AGGREGATOR AS number of the last BGP4 speaker that performed route aggregation. A value of zero (0) indicates the absence of this attribute. Note propagation of AS of zero is illegal in the Internet.

This value represents the calculated length of the NEW_AS_PATH according to the rules of the BGP specification. This value is used in route selection.

This is a string depicting the autonomous system path to this network which was received from the peer which advertised it. The format of the string is implementation-dependent, and should be designed for operator readability.

This value is a unique index for the decomposed AS Path in the f10BgpM2AsPathTable. It is assigned by the agent at the point of creation of the f10BgpM2AsPathTable 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 f10BgpM2AsPathIndex row instance values across rows of the f10BgpM2AsPathTable.

The BGP-4 Path Attribute AS Path Table contains the per network path (NLRI) AS PATH data received from the advertising BGP peer.

Information about an AS path provided with a path to a network.

A per-AS path segment index. This will index a set of autonomous systems in an AS path which are part of the same sequence or set (as determined by the row value of f10BgpM2AsPathType, which should be the same value for each f10BgpM2AsPathTable entry indexed by the same (f10BgpM2PathAttrIndex, f10BgpM2AsPathIndex) pair).

A per-AS element index. This will index a particular AS within a sequence or set of autonomous systems in an AS path.

The type of sequence in which this asPath was advertised as an attribute. Note that all asPath row instances for a given (f10BgpM2PathAttrIndex, f10BgpM2AsPathIndex) index pair will have their f10BgpM2AsPathType set to the same value. The values for f10BgpM2AsPathType are interpreted as defined in the base BGP document and the BGP AS Confederations document. Enumeration: 'confedSequence': 3, 'asSet': 1, 'confedSet': 4, 'asSequence': 2.

An AS value for an AS the related NLRI traversed in the propagation of its advertisement. This value is to be interpreted in the context of the sequence implied by f10BgpM2AsPathIndex and f10BgpM2AsPathType (and, in sequence of the other table rows with the same value of f10BgpM2PathAttrIndex and f10BgpM2AsPathIndex).

The BGP-4 Path Attribute Unknown Table contains the per network path (NLRI) data on the path attributes advertised with a route but not known to the local BGP implementation or not otherwise capable of being returned from this agent. The absence of row data for a given index value for f10BgpM2PathAttrIndex indicates a lack of such unknown attribute information for the indicated network path (as indexed by that f10BgpM2PathAttrIndex value in the f10BgpM2PathAttrTable).

Information about an unknown attribute provided with a path to a network.

An integer index for a row in this table.

The attribute type advertised with this unknown attribute by the peer.

Value of path attribute not understood by the base BGP-4 document. Octets beyond the maximum size, if any, are not recorded by this row object.

The BGP-4 Path Attribute Community Table contains the per network path (NLRI) data on the community membership advertised with a route. The absence of row data for a given index value for f10BgpM2PathAttrIndex indicates a lack of this attribute information for the indicated network path (as indexed by that f10BgpM2PathAttrIndex value in the f10BgpM2PathAttrTable).

Information about a community association provided with a path to a network.

An integer index for a row in this table.

A value representing a community. There are certain 4-octet long values which could be returned in this columnar row data that carry additional semantics.

Table of link local nexthops as sent by RFC 2545 for IPv6 BGP Speakers.

Entry containing the link-local nexthops as sent by a BGP speaker running RFC 2545 extensions for double-nexthops.

This value is TRUE if and only if the BGP speaker is receiving IPv6 NLRI using the RFC 2545 double nexthop convention and it has received a link local scope nexthop in addition to the global scope nexthop.

This value contains an IPv6 link local address of InetAddressType of type ipv6z. This value is only present if f10BgpM2LinkLocalNextHopPresent is true.

Per prefix data pertinent to advertisement of a network prefix through an originator.

Each entry contains data pertinent to a network prefix as received through its originating BGP route reflector.

The Originator-ID identifying the router that initially advertised this destination to a Route Reflector. A value of 0.0.0.0 indicates the absence of this attribute.

The BGP-4 Path Attribute Cluster Table contains the per network path (NLRI) data on the reflection path which a route has traversed. The absence of row data for a given index value for f10BgpM2PathAttrIndex indicates a lack of this attribute information for the indicated network path (as indexed by that f10BgpM2PathAttrIndex value in the f10BgpM2PathAttrTable).

Information about a cluster traversal provided with a path to a network.

An integral index for a row in this table.

A four octet long value representing a part of the reflection path that the route has passed. Each such four octet long value represents the ID of a cluster that the route has traversed. The sequence of this path as received in the route advertisement will be preserved in the sequence of f10BgpM2PathAttrClusterTable rows (and the f10BgpM2PathAttrClusterValues in each row) as returned for a given f10BgpM2PathAttrIndex value, and the monotonically increasing sequence of f10BgpM2PathAttrClusterIndex values for that f10BgpM2PathAttrIndex.

The BGP-4 Path Attribute Community Table contains the per network path (NLRI) data on the extended community membership advertised with a route. The absence of row data for a given index value for f10BgpM2PathAttrIndex indicates a lack of this attribute information for the indicated network path (as indexed by that f10BgpM2PathAttrIndex value in the f10BgpM2PathAttrTable). XXX JMH - can not assign the OID until an RFC is published.

Information about an extended community association provided with a path to a network.

An integral index for a row in this table.

A value representing an extended community which was received with the route implied by the f10BgpM2PathAttr Index value of this row data. There are certain 8-octet long values which could be returned in this columnar row data that carry additional semantics.

The compliance statement for entities which implement the BGP4 mib.

Objects associated with BGP communities.

Objects associated with BGP extended communities.

Objects associated with BGP route reflection.

Objects associated with BGP confederation membership.

Objects associated with BGP peering timers.

Objects to count discrete events and exchanges on BGP sessions.

Objects to report capabilities as received on BGP sessions.

Objects to report AS paths received on BGP NLRIs.

AS Size objects.

Basic objects in local BGP implementation.

Errors received on BGP peering sessions.

Core object types on BGP peering sessions.

Attributes received on BGP peering sessions.

Configuration objects for BGP peers.

Configuration objects for BGP peers that support route reflection.

Configuration objects for BGP peers that support BGP confederations.

This group contains objects for notifications supported by this mib module.

This group is required for peers that support exchanging of IPv6 NLRI per RFC 2545.