ARISTA-CONMON-MIB

ProbeIndexIdentifier with bounded length, derived from the aggregation of client, host, IP address (ICMP and TCP probe specific), port number (only TCP probe specific) and source interface names of the connectivity monitor probes. If the index string is longer than 90 characters, then the remaining characters are hashed and added as a suffix to the first 90 characters. ICMP probe: - index string: '<client>+<host>+<ip address>+<source interface>' HTTP probe: - index string: '<client>+<host>+<url>+<source interface>' TCP probe: - index string: '<client>+<host>+<ip address>+<port number> +<source interface>' For example: - index string: 'client1-host1-10.1.1.2-Et1/1' identifier: 'client1-host1-10.1.1.2-Et1/1' - index string: 'client1-...<very long host name>...-10.1.1.2-Et1/1' identifier: 'client1-host...0123456789'. SIZE (0..100) · OCTET STRING · hint 100t

Connectivity monitor ICMP probe index.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

Connectivity monitor client name.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

Optional connectivity monitor host name. If there is no host name, the value will be an empty string.

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

Optional IP address type of configured host. If there is no IP address type, the value will be unknown(0), and the value of aristaIcmpProbeIpAddr will be a zero-length string.

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 (0..255) · OCTET STRING

Optional IP address of configured host. If there is no IP address, the value will be a zero-length string, and the value of aristaIcmpProbeIpAddrType will be unknown(0).

InterfaceIndexOrZeroThis textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced. (0..2147483647) · Integer32 · hint d

The value of the ifIndex object, defined in IF-MIB for the source interface from which the probe was sent. Zero means the interface used for probing was unknown and was selected by kernel.

NetworkStatisticsPrecisionThe number of decimal places of precision in fixed-point network statistics. An object of type NetworkStatisticsPrecision is used to identify the semantics of an object of type NetworkStatisticsValue. Connectivity monitor statistics are rounded up to 3 decimal places, so the number of decimal places must be between 0 and 3. (0..3) · Integer32 · hint d

The number of decimal places of precision in fixed-point latency values returned by the associated aristaIcmpProbeLatencyValue object.

NetworkStatisticsValueAn oject of this data type represents connectivity monitor statistics. The semantics of an object using this data type are determined by the value of the associated NetworkStatisticsPrecision object. For example, the network latency of 123.45 ms for a probe, would have a NetworkStatisticsPrecision value of '2', and a NetworkStatisticsValue value of '12345'. (0..2147483647) · Integer32 · hint d

Latency in milliseconds. If the probe failed, this will be set to its maximum value (2,147,483,647). To correctly interpret the value of this object, the associated aristaIcmpProbeLatencyPrecision object must be examined.

NetworkStatisticsPrecisionThe number of decimal places of precision in fixed-point network statistics. An object of type NetworkStatisticsPrecision is used to identify the semantics of an object of type NetworkStatisticsValue. Connectivity monitor statistics are rounded up to 3 decimal places, so the number of decimal places must be between 0 and 3. (0..3) · Integer32 · hint d

The number of decimal places of precision in fixed-point jitter values returned by the associated aristaIcmpProbeJitterValue object.

NetworkStatisticsValueAn oject of this data type represents connectivity monitor statistics. The semantics of an object using this data type are determined by the value of the associated NetworkStatisticsPrecision object. For example, the network latency of 123.45 ms for a probe, would have a NetworkStatisticsPrecision value of '2', and a NetworkStatisticsValue value of '12345'. (0..2147483647) · Integer32 · hint d

Jitter in milliseconds. If the probe failed, this will be set to its maximum value (2,147,483,647). To correctly interpret the value of this object, the associated aristaIcmpProbeJitterPrecision object must be examined.

Integer32 (0..100)

Percentage of packet loss.

ProbeIndexIdentifier with bounded length, derived from the aggregation of client, host, IP address (ICMP and TCP probe specific), port number (only TCP probe specific) and source interface names of the connectivity monitor probes. If the index string is longer than 90 characters, then the remaining characters are hashed and added as a suffix to the first 90 characters. ICMP probe: - index string: '<client>+<host>+<ip address>+<source interface>' HTTP probe: - index string: '<client>+<host>+<url>+<source interface>' TCP probe: - index string: '<client>+<host>+<ip address>+<port number> +<source interface>' For example: - index string: 'client1-host1-10.1.1.2-Et1/1' identifier: 'client1-host1-10.1.1.2-Et1/1' - index string: 'client1-...<very long host name>...-10.1.1.2-Et1/1' identifier: 'client1-host...0123456789'. SIZE (0..100) · OCTET STRING · hint 100t

Connectivity monitor HTTP probe index.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

Connectivity monitor client name.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

Connectivity monitor host name.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

Connectivity monitor url.

InterfaceIndexOrZeroThis textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced. (0..2147483647) · Integer32 · hint d

The value of the ifIndex object, defined in IF-MIB for the source interface from which the probe was sent. Zero means the interface used for probing was unknown and was selected by kernel.

NetworkStatisticsPrecisionThe number of decimal places of precision in fixed-point network statistics. An object of type NetworkStatisticsPrecision is used to identify the semantics of an object of type NetworkStatisticsValue. Connectivity monitor statistics are rounded up to 3 decimal places, so the number of decimal places must be between 0 and 3. (0..3) · Integer32 · hint d

The number of decimal places of precision in fixed-point response time values returned by the associated aristaHttpProbeResponseTimeValue object.

NetworkStatisticsValueAn oject of this data type represents connectivity monitor statistics. The semantics of an object using this data type are determined by the value of the associated NetworkStatisticsPrecision object. For example, the network latency of 123.45 ms for a probe, would have a NetworkStatisticsPrecision value of '2', and a NetworkStatisticsValue value of '12345'. (0..2147483647) · Integer32 · hint d

Response time in milliseconds. If the probe failed, this will be set to its maximum value (2,147,483,647). To correctly interpret the value of this object, the associated aristaHttpProbeResponseTimePrec object must be examined.

ProbeIndexIdentifier with bounded length, derived from the aggregation of client, host, IP address (ICMP and TCP probe specific), port number (only TCP probe specific) and source interface names of the connectivity monitor probes. If the index string is longer than 90 characters, then the remaining characters are hashed and added as a suffix to the first 90 characters. ICMP probe: - index string: '<client>+<host>+<ip address>+<source interface>' HTTP probe: - index string: '<client>+<host>+<url>+<source interface>' TCP probe: - index string: '<client>+<host>+<ip address>+<port number> +<source interface>' For example: - index string: 'client1-host1-10.1.1.2-Et1/1' identifier: 'client1-host1-10.1.1.2-Et1/1' - index string: 'client1-...<very long host name>...-10.1.1.2-Et1/1' identifier: 'client1-host...0123456789'. SIZE (0..100) · OCTET STRING · hint 100t

Connectivity monitor TCP probe index.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

Connectivity monitor client name.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

Optional connectivity monitor host name. If there is no host name, the value will be an empty string.

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

Optional IP address type of configured host. If there is no IP address type, the value will be unknown(0), and the value of aristaTcpProbeIpAddr will be a zero-length string.

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 (0..255) · OCTET STRING

Optional IP address of configured host. If there is no IP address, the value will be a zero-length string, and the value of aristaTcpProbeIpAddrType will be unknown(0).

Integer32

Configured TCP server port.

InterfaceIndexOrZeroThis textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced. (0..2147483647) · Integer32 · hint d

The value of the ifIndex object, defined in IF-MIB for the source interface from which the probe was sent. Zero means the interface used for probing was unknown and was selected by kernel.

NetworkStatisticsPrecisionThe number of decimal places of precision in fixed-point network statistics. An object of type NetworkStatisticsPrecision is used to identify the semantics of an object of type NetworkStatisticsValue. Connectivity monitor statistics are rounded up to 3 decimal places, so the number of decimal places must be between 0 and 3. (0..3) · Integer32 · hint d

The number of decimal places of precision in fixed-point latency values returned by the associated aristaTcpProbeLatencyValue object.

NetworkStatisticsValueAn oject of this data type represents connectivity monitor statistics. The semantics of an object using this data type are determined by the value of the associated NetworkStatisticsPrecision object. For example, the network latency of 123.45 ms for a probe, would have a NetworkStatisticsPrecision value of '2', and a NetworkStatisticsValue value of '12345'. (0..2147483647) · Integer32 · hint d

Latency in milliseconds. If the probe failed, this will be set to its maximum value (2,147,483,647). To correctly interpret the value of this object, the associated aristaTcpProbeLatencyPrecision object must be examined.