BGP4-V2-MIB-JUNIPER

Unsigned32 (0..255)

The version number of the BGP Protocol.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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

Unsigned32 (0..255)

The BGP authentication code.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This value is TRUE if a given authentication method is supported by the local implementation.

Unsigned32 (0..255)

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

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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

JnxBgpM2IdentifierThe representation of a BGP Identifier. The BGP Identifier should be represented in the OCTET STRING as with the first OCTET of the string containing the first OCTET of the BGP Identifier received or sent in the OPEN packet and so on. Even though the BGP Identifier is trending away from an IP address it is still displayed as if it was one, even when it would be an illegal IP address. SIZE (4) · OCTET STRING · hint 1d.

Reference: draft-ietf-idr-bgp4-17.txt, Sec. 4.2

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

INTEGER1 = idle2 = connect3 = active4 = opensent5 = openconfirm6 = established · Integer32

Reference: draft-ietf-idr-bgp4-17.txt, Sec. 8

The remote BGP peer's FSM state.

INTEGER1 = halted2 = running · Integer32

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 jnxBgpM2PeerState 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.

Unsigned32 (1..255)

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

Unsigned32 (1..255)

The negotiated version of BGP running between the two peers.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

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

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (4..20) · OCTET STRING

The address of the local end of the peering session.

InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (0..65535) · Unsigned32 · hint d

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

InetAutonomousSystemNumberRepresents an autonomous system number that identifies an Autonomous System (AS). An AS is a set of routers under a single technical administration, using an interior gateway protocol and common metrics to route packets within the AS, and using an exterior gateway protocol to route packets to other ASes'. IANA maintains the AS number space and has delegated large parts to the regional registries. Autonomous system numbers are currently limited to 16 bits (0..65535). There is, however, work in progress to enlarge the autonomous system number space to 32 bits. Therefore, this textual convention uses an Unsigned32 value without a range restriction in order to support a larger autonomous system number space.Reference: RFC 1771, RFC 1930 · Unsigned32 · hint d

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.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

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

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (4..20) · OCTET STRING

The address of the remote end of the peering session.

InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (0..65535) · Unsigned32 · hint d

Reference: RFC 2012 - SNMPv2 Management Information Base for the Transmission Control Protocol using SMIv2. RFC 2542 - IP Version 6 Management Information Base for the Transmission Control Protocol.

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 jnxBgpM2PeerLocalAddr, jnxBgpM2PeerLocalPort, jnxBgpM2PeerRemoteAddr and jnxBgpM2PeerRemotePort provide the appropriate reference to the standard MIB TCP connection table. or even the ipv6 TCP MIB as in rfc2452.

InetAutonomousSystemNumberRepresents an autonomous system number that identifies an Autonomous System (AS). An AS is a set of routers under a single technical administration, using an interior gateway protocol and common metrics to route packets within the AS, and using an exterior gateway protocol to route packets to other ASes'. IANA maintains the AS number space and has delegated large parts to the regional registries. Autonomous system numbers are currently limited to 16 bits (0..65535). There is, however, work in progress to enlarge the autonomous system number space to 32 bits. Therefore, this textual convention uses an Unsigned32 value without a range restriction in order to support a larger autonomous system number space.Reference: RFC 1771, RFC 1930 · Unsigned32 · hint d

The remote autonomous system number.

Unsigned32

This value is a unique index for the remote peer entry in the jnxBgpM2PeerTable. It is assigned by the agent at the point of creation of the jnxBgpM2PeerTable 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 jnxBgpM2PeerIndex row instance values across rows of the jnxBgpM2PeerTable. 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 jnxBgpM2PeerTable and other tables utilizing jnxBgpM2PeerIndex 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 jnxBgpM2PeerTable that comes up while this row still exists will re-utilize the same row.

Unsigned32

Routing instance index.

OCTET STRING SIZE (2)

Reference: draft-ietf-idr-bgp4-15.txt, Sec. 4.5

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.

OCTET STRING SIZE (2)

Reference: draft-ietf-idr-bgp4-15.txt, Sec. 4.5

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.

TimeTicks

Reference: draft-ietf-idr-bgp4-15.txt, Sec. 4.5

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

TimeTicks

Reference: draft-ietf-idr-bgp4-15.txt, Sec. 4.5

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

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

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

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

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

OCTET STRING SIZE (0..4075)

Reference: draft-ietf-idr-bgp4-15.txt, Sec. 4.5

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

OCTET STRING SIZE (0..4075)

Reference: draft-ietf-idr-bgp4-15.txt, Sec. 4.5

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

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

The local peer has sent authentication information to the remote peer in the BGP Authentication field.

Unsigned32 (0..255)

The code of the authentication information sent to the remote peer.

OCTET STRING SIZE (0..252)

The payload of the authentication information from the remote peer.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

The local peer has received authentication information from the remote peer in the BGP Authentication field.

Unsigned32 (0..255)

The code of the authentication information received from the remote peer.

OCTET STRING SIZE (0..252)

The payload of the authentication information from the remote peer.

Gauge32

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.

Gauge32

Elapsed time in seconds since the last BGP UPDATE message was received from the peer. Each time jnxBgpM2PeerInUpdates 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

Unsigned32 (1..65535)

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

Unsigned32 (0 | 3..65535)

Reference: draft-ietf-idr-bgp4-17.txt, Appendix 6.4

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 (jnxBgpM2PeerHoldTime) 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.

Unsigned32 (0 | 1..21845)

Reference: draft-ietf-idr-bgp4-17.txt, Appendix 6.4

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 jnxBgpM2PeerHoldTimeConfigured; the actual time interval for the KEEPALIVE messages is indicated by jnxBgpM2PeerKeepAlive. A reasonable maximum value for this timer would be configured to be one third of that of jnxBgpM2PeerHoldTimeConfigured. 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.

Unsigned32 (0..65535)

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

Unsigned32 (0..65535)

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

Unsigned32 (0 | 3..65535)

Reference: draft-ietf-idr-bgp4-17.txt, Sec. 4.2

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 jnxBgpM2PeerHoldTimeConfigured for this peer. This value is only defined when the peering session is in the Established state.

Unsigned32 (0 | 1..21845)

Reference: draft-ietf-idr-bgp4-17, Sec. 4.4

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 jnxBgpM2PeerHoldTime, it has the same proportion as what jnxBgpM2PeerKeepAliveConfigured has when compared with jnxBgpM2PeerHoldTimeConfigured. 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 jnxBgpM2PeerKeepAliveConfigured is zero (0). This value is only defined when the peering session is in the Established state.

Unsigned32 (0..255)

The BGP Capability Advertisement Capability Code.

Unsigned32 (1..128)

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

OCTET STRING SIZE (0..255)

The value of the announced capability.

Unsigned32 (0..255)

The BGP Capability Advertisement Capability Code.

Unsigned32 (1..128)

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

OCTET STRING SIZE (0..255)

The value of the announced capability.

Counter32

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

Counter32

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

Counter32

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.

Counter32

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.

Counter32

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

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

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

JnxBgpM2SafiThe representation of a BGP Safi (0..255) · Unsigned32 · hint d

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

Gauge32

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

Gauge32

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.

Gauge32

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.

Gauge32

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

Gauge32

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

INTEGER0 = nonClient1 = client2 = meshedClient · Integer32

Reference: RFC 2796 - BGP Route Reflection

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.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Reference: RFC 3065 - BGP Confederations

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

INTEGER1 = stop2 = start · Integer32

This object allows the Manual Stop and Manual Start events to be sent to an activated peering session.

Unsigned32 (1..255)

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 jnxBgpM2CfgAllowVersionNegotiation.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

The address family of the speakers of this BGP session.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (4..20) · OCTET STRING

The address of the local end of the peering session.

InetAutonomousSystemNumberRepresents an autonomous system number that identifies an Autonomous System (AS). An AS is a set of routers under a single technical administration, using an interior gateway protocol and common metrics to route packets within the AS, and using an exterior gateway protocol to route packets to other ASes'. IANA maintains the AS number space and has delegated large parts to the regional registries. Autonomous system numbers are currently limited to 16 bits (0..65535). There is, however, work in progress to enlarge the autonomous system number space to 32 bits. Therefore, this textual convention uses an Unsigned32 value without a range restriction in order to support a larger autonomous system number space.Reference: RFC 1771, RFC 1930 · Unsigned32 · hint d

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 jnxBgpM2CfgLocalAs.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

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

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (4..20) · OCTET STRING

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

Integer32 (-1 | 0..65535)

This is the remote port for the transport connection between the BGP peers. In the case of a transport for which the notion of port is irrelevant, the value of -1 can be defaulted or set.

InetAutonomousSystemNumberRepresents an autonomous system number that identifies an Autonomous System (AS). An AS is a set of routers under a single technical administration, using an interior gateway protocol and common metrics to route packets within the AS, and using an exterior gateway protocol to route packets to other ASes'. IANA maintains the AS number space and has delegated large parts to the regional registries. Autonomous system numbers are currently limited to 16 bits (0..65535). There is, however, work in progress to enlarge the autonomous system number space to 32 bits. Therefore, this textual convention uses an Unsigned32 value without a range restriction in order to support a larger autonomous system number space.Reference: RFC 1771, RFC 1930 · Unsigned32 · hint d

Autonomous system number of the remote peer.

StorageType1 = other2 = volatile3 = nonVolatile4 = permanent5 = readOnlyDescribes the memory realization of a conceptual row. A row which is volatile(2) is lost upon reboot. A row which is either nonVolatile(3), permanent(4) or readOnly(5), is backed up by stable storage. A row which is permanent(4) can be changed but not deleted. A row which is readOnly(5) cannot be changed nor deleted. If the value of an object with this syntax is either permanent(4) or readOnly(5), it cannot be written. Conversely, if the value is either other(1), volatile(2) or nonVolatile(3), it cannot be modified to be permanent(4) or readOnly(5). (All illegal modifications result in a 'wrongValue' error.) Every usage of this textual convention is required to specify the columnar objects which a permanent(4) row must at a minimum allow to be writable. · Integer32

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

INTEGER0 = unknown1 = notActivated2 = errDuplicatePeeringSession3 = activated · Integer32

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 jnxBgpM2CfgPeerRowEntryStatus), then this instance will be set to not-activated (1). At the point that the row is activated, jnxBgpM2CfgPeerError 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 {jnxBgpM2CfgPeerLocalAddrType, jnxBgpM2CfgPeerLocalAddr, jnxBgpM2CfgPeerRemoteAddr, jnxBgpM2CfgPeerRemotePort}, 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, jnxBgpM2PeerCfgPeerEntry will be set to the row instance of the entry in the jnxBgpM2PeerTable 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 jnxBgpM2PeerTable row instance (as reflected through jnxBgpM2CfgPeerPeerEntry) associated with this row instance.

RowPointerRepresents a pointer to a conceptual row. The value is the name of the instance of the first accessible columnar object in the conceptual row. For example, ifIndex.3 would point to the 3rd row in the ifTable (note that if ifIndex were not-accessible, then ifDescr.3 would be used instead). · OBJECT IDENTIFIER

Upon activation of the session data contained in this row instance, this object points to an instance of a row within the jnxBgpM2PeerTable 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 jnxBgpM2CfgPeerRowEntryStatus). Such row instances will always have a value of jnxBgpM2CfgPeerError which is activated (3).

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

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

Integer32 (1..65535)

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

INTEGER1 = halted2 = running · Integer32

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.

Unsigned32

Routing instance index.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This value is true if BGP Authentication is enabled for this peer. This is the authentication mechanism documented in the base BGP specification, not the MD5 session protection mechanism.

Unsigned32 (0..255)

Reference: draft-ietf-idr-bgp4-17.txt, Sec. 4.1.a

The authentication code for the BGP Authentication mechanism.

OCTET STRING SIZE (0..252)

Reference: draft-ietf-idr-bgp4-17.txt, Sec. 4.1.a

The authentication payload for the BGP authentication mechanism. This value has semantic meaning within the context of the authentication code.

Unsigned32 (1..65535)

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

Unsigned32 (0 | 3..65535)

Reference: draft-ietf-idr-bgp4-17.txt, Appendix 6.4

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 (jnxBgpM2PeerHoldTime) 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.

Unsigned32 (0 | 1..21845)

Reference: draft-ietf-idr-bgp4-17.txt, Appendix 6.4

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 jnxBgpM2PeerHoldTimeConfigured; the actual time interval for the KEEPALIVE messages is indicated by jnxBgpM2PeerKeepAlive. A reasonable maximum value for this timer would be configured to be one third of that of jnxBgpM2PeerHoldTimeConfigured. 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.

Unsigned32 (0..65535)

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

Unsigned32 (0..65535)

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

INTEGER0 = nonClient1 = client2 = meshedClient · Integer32

Reference: RFC 2796 - BGP Route Reflection

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.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Reference: RFC 3065 - BGP Confederations

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

Unsigned32

Reference: RFC 3107 - Carrying Label Information in BGP-4

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.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

The address family of the prefix for this NLRI.

JnxBgpM2SafiThe representation of a BGP Safi (0..255) · Unsigned32 · hint d

Reference: RFC 2858 - Multiprotocol Extensions for BGP-4

The subsequent address family of the prefix for this NLRI

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (4..20) · OCTET STRING

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

InetAddressPrefixLengthDenotes the length of a generic Internet network address prefix. A value of n corresponds to an IP address mask that has n contiguous 1-bits from the most significant bit (MSB), with all other bits set to 0. An InetAddressPrefixLength value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddressPrefixLength textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddressPrefixLength textual convention, if they appear in the same logical row. InetAddressPrefixLength values larger than the maximum length of an IP address for a specific InetAddressType are treated as the maximum significant value applicable for the InetAddressType. The maximum significant value is 32 for the InetAddressType 'ipv4(1)' and 'ipv4z(3)' and 128 for the InetAddressType 'ipv6(2)' and 'ipv6z(4)'. The maximum significant value for the InetAddressType 'dns(16)' is 0. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where the Internet network address prefix is unknown or does not apply. The upper bound of the prefix length has been chosen to be consistent with the maximum size of an InetAddress. (0..2040) · Unsigned32 · hint d

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

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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

Unsigned32

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

Unsigned32

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

INTEGER0 = none1 = bgpMplsLabelStack · Integer32

Reference: RFC 3107 - Carrying Label Information in BGP-4 draft-ietf-mpls-lsr-mib-08.txt

This object enumerates the type of the row that is pointed to in the table row jnxBgpM2NlriOpaquePointer instance, if jnxBgpM2NlriOpaquePointer is in fact not a zero length. jnxBgpM2NlriOpaqueType is necessary since the data referenced by jnxBgpM2NlriOpaquePointer 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 jnxBgpM2NlriOpaqueType would be bgpMplsLabelStack(1).

RowPointerRepresents a pointer to a conceptual row. The value is the name of the instance of the first accessible columnar object in the conceptual row. For example, ifIndex.3 would point to the 3rd row in the ifTable (note that if ifIndex were not-accessible, then ifDescr.3 would be used instead). · OBJECT IDENTIFIER

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 jnxBgpM2NlriOpaqueType is none.

Unsigned32

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.

RowPointerRepresents a pointer to a conceptual row. The value is the name of the instance of the first accessible columnar object in the conceptual row. For example, ifIndex.3 would point to the 3rd row in the ifTable (note that if ifIndex were not-accessible, then ifDescr.3 would be used instead). · OBJECT IDENTIFIER

Reference: draft-ietf-idr-bgp4-17.txt, Sec. 9.2

This object points to the route in the jnxBgpM2NlriTable 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.

INTEGER1 = igp2 = egp3 = incomplete · Integer32

The ultimate origin of the path information.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

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

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (4..20) · OCTET STRING

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. jnxBgpM2LinkLocalNextHopTable 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, , jnxBgpM2LinkLocalNextHopPresent will be false and jnxBgpM2PathAttrNextHop will contain the link local nexthop.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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

Unsigned32

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

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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

Unsigned32

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

INTEGER1 = atomicAggregatePresent2 = atomicAggregateMissing · Integer32

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.

InetAutonomousSystemNumberRepresents an autonomous system number that identifies an Autonomous System (AS). An AS is a set of routers under a single technical administration, using an interior gateway protocol and common metrics to route packets within the AS, and using an exterior gateway protocol to route packets to other ASes'. IANA maintains the AS number space and has delegated large parts to the regional registries. Autonomous system numbers are currently limited to 16 bits (0..65535). There is, however, work in progress to enlarge the autonomous system number space to 32 bits. Therefore, this textual convention uses an Unsigned32 value without a range restriction in order to support a larger autonomous system number space.Reference: RFC 1771, RFC 1930 · Unsigned32 · hint d

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.

JnxBgpM2IdentifierThe representation of a BGP Identifier. The BGP Identifier should be represented in the OCTET STRING as with the first OCTET of the string containing the first OCTET of the BGP Identifier received or sent in the OPEN packet and so on. Even though the BGP Identifier is trending away from an IP address it is still displayed as if it was one, even when it would be an illegal IP address. SIZE (4) · OCTET STRING · hint 1d.

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.

Unsigned32

Reference: draft-ietf-idr-bgp4-17.txt, Sec. 9.1.2.2.a

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.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

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.

Unsigned32

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

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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: jnxBgpM2PathAttrAggregatorAS - zero (0). jnxBgpM2AsPathCalcLength - zero (0). jnxBgpM2AsPathString - zero (0) length string. jnxBgpM2AsPathIndex - zero (0).

InetAutonomousSystemNumberRepresents an autonomous system number that identifies an Autonomous System (AS). An AS is a set of routers under a single technical administration, using an interior gateway protocol and common metrics to route packets within the AS, and using an exterior gateway protocol to route packets to other ASes'. IANA maintains the AS number space and has delegated large parts to the regional registries. Autonomous system numbers are currently limited to 16 bits (0..65535). There is, however, work in progress to enlarge the autonomous system number space to 32 bits. Therefore, this textual convention uses an Unsigned32 value without a range restriction in order to support a larger autonomous system number space.Reference: RFC 1771, RFC 1930 · Unsigned32 · hint d

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.

Unsigned32

Reference: draft-ietf-idr-bgp4-17.txt, Sec. 9.1.2.2.a

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.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

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.

Unsigned32

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

Unsigned32

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 jnxBgpM2AsPathType, which should be the same value for each jnxBgpM2AsPathTable entry indexed by the same (jnxBgpM2PathAttrIndex, jnxBgpM2AsPathIndex) pair).

Unsigned32

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

INTEGER1 = asSet2 = asSequence3 = confedSequence4 = confedSet · Integer32

Reference: draft-ietf-idr-bgp4-16 RFC 3065 - BGP AS Confederations

The type of sequence in which this asPath was advertised as an attribute. Note that all asPath row instances for a given (jnxBgpM2PathAttrIndex, jnxBgpM2AsPathIndex) index pair will have their jnxBgpM2AsPathType set to the same value. The values for jnxBgpM2AsPathType are interpreted as defined in the base BGP document and the BGP AS Confederations document.

InetAutonomousSystemNumberRepresents an autonomous system number that identifies an Autonomous System (AS). An AS is a set of routers under a single technical administration, using an interior gateway protocol and common metrics to route packets within the AS, and using an exterior gateway protocol to route packets to other ASes'. IANA maintains the AS number space and has delegated large parts to the regional registries. Autonomous system numbers are currently limited to 16 bits (0..65535). There is, however, work in progress to enlarge the autonomous system number space to 32 bits. Therefore, this textual convention uses an Unsigned32 value without a range restriction in order to support a larger autonomous system number space.Reference: RFC 1771, RFC 1930 · Unsigned32 · hint d

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 jnxBgpM2AsPathIndex and jnxBgpM2AsPathType (and, in sequence of the other table rows with the same value of jnxBgpM2PathAttrIndex and jnxBgpM2AsPathIndex).

Unsigned32

An integer index for a row in this table.

Unsigned32

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

OCTET STRING SIZE (0..4070)

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.

Unsigned32

An integer index for a row in this table.

JnxBgpM2CommunityThe representation of a BGP Community. SIZE (4) · OCTET STRING · hint 2d:

Reference: RFC 1997 - BGP Communities Attribute

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.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (20) · OCTET STRING

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

JnxBgpM2IdentifierThe representation of a BGP Identifier. The BGP Identifier should be represented in the OCTET STRING as with the first OCTET of the string containing the first OCTET of the BGP Identifier received or sent in the OPEN packet and so on. Even though the BGP Identifier is trending away from an IP address it is still displayed as if it was one, even when it would be an illegal IP address. SIZE (4) · OCTET STRING · hint 1d.

Reference: This attribute is defined in [RFC2796].

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.

Unsigned32

An integral index for a row in this table.

JnxBgpM2IdentifierThe representation of a BGP Identifier. The BGP Identifier should be represented in the OCTET STRING as with the first OCTET of the string containing the first OCTET of the BGP Identifier received or sent in the OPEN packet and so on. Even though the BGP Identifier is trending away from an IP address it is still displayed as if it was one, even when it would be an illegal IP address. SIZE (4) · OCTET STRING · hint 1d.

Reference: This attribute is defined in [RFC2796].

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 jnxBgpM2PathAttrClusterTable rows (and the jnxBgpM2PathAttrClusterValues in each row) as returned for a given jnxBgpM2PathAttrIndex value, and the monotonically increasing sequence of jnxBgpM2PathAttrClusterIndex values for that jnxBgpM2PathAttrIndex.

Unsigned32

An integral index for a row in this table.

JnxBgpM2ExtendedCommunityThe representation of a BGP Extended Community. SIZE (8) · OCTET STRING · hint 1x:

Reference: BGP-EXTCOMM - BGP Extended Communities Attribute

A value representing an extended community which was received with the route implied by the jnxBgpM2PathAttr 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.