EZ5 MIB Catalog

ARISTA-FIB-STATS-MIB

2017-05-19

Arista devices that function as a router support various dynamic routing protocols like BGP, OSPF. Customers can configure local or static routes as well. The routing subsystem is responsible for creating the forwarding information base (FIB) from routing information received by customer configuration or dynamic routing protocols. The FIB has the complete details about all the routes that are active in the system and will be used for data forwarding. In the context of this MIB, we specifically refer to the unicast FIB. This MIB provides useful statistics about the FIB. Arista devices support routing function for IPv4 and IPv6 address families. Arista devices also support the concept of virtual routing and forwarding (VRF), with a single device providing multiple routing instances. This allows customers to isolate network traffic and use overlapping addresses. A VRF instance is identified by a customer configured string. Arista devices maintain independent FIB for each address family and VRF instance. This MIB provides access to FIB summary of all address families within a specific VRF instance. Network Management Stations can obtain FIB summary for every VRF instance by specifying the VRF instance as a context, when using SNMPv3; or by including the VRF instance in the community string (format is <community>@<vrf instance>) when using SNMPv2.

Download ARISTA-FIB-STATS-MIB.txt Open ARISTA-FIB-STATS-MIB.txt in a new tab

TABLES (3)

Tables (3)

NameOID
aristaFIBStatsSummaryTable1.3.6.1.4.1.30065.3.23.1.1
aristaFIBStatsByRouteTypeTable1.3.6.1.4.1.30065.3.23.1.2
aristaFIBStatsByPrefixLenTable1.3.6.1.4.1.30065.3.23.1.3

END OF TOC

Table details

aristaFIBStatsSummaryTable

1.3.6.1.4.1.30065.3.23.1.1

Index: aristaFIBStatsAF

This table contains overall FIB statistics for each address family.

aristaFIBStatsAF

1.3.6.1.4.1.30065.3.23.1.1.1.1

InetVersion0 = unknown1 = ipv42 = ipv6A value representing a version of the IP protocol. unknown(0) An unknown or unspecified version of the IP protocol. ipv4(1) The IPv4 protocol as defined in RFC 791 (STD 5). ipv6(2) The IPv6 protocol as defined in RFC 2460. Note that this textual convention SHOULD NOT be used to distinguish different address types associated with IP protocols. The InetAddressType has been designed for this purpose.Reference: RFC 791, RFC 2460 · Integer32

Indicates the IP version of this row.

aristaFIBStatsTotalRoutes

1.3.6.1.4.1.30065.3.23.1.1.1.2

Gauge32

Indicates the total number of routes active in the FIB for the specified address family.

aristaFIBStatsByRouteTypeTable

1.3.6.1.4.1.30065.3.23.1.2

Index: aristaFIBStatsAF · aristaFIBStatsRouteType

This table contains FIB statistics for each address family and route type. Every entry in the FIB may have been contributed by a specific route type. This table provides statistics for various route types that contribute to the FIB.

aristaFIBStatsRouteType

1.3.6.1.4.1.30065.3.23.1.2.1.1

RouteType1 = other2 = connected3 = static8 = rip9 = isIs13 = ospf14 = bgp200 = ospfv3201 = staticNonPersistent202 = staticNexthopGroup203 = attached204 = vcs205 = internalThe type of the route present in the FIB. Not all values of the route type may be supported on all Arista devices. A short description of some of the route types is provided below. OSPF[v3], BGP, RIP, IS-IS are dynamic routing protocols as specified by the standards bodies. On Arista devices, customers can run their own application and program routes from the applications using EOS SDK. These routes are not saved - when the device reboots, the routes are not longer present in the system, and have to be reprogrammed. These routes are static but not persistent. On Arista devices, customers can also create a 'nexthop list' and use the list to create routes manually. Packets that match specific routes will be forwarded to one of the nexthops in the list. This route type is referred as a nexthop-group route. All subnets which an Arista device is (configured to be) part of, are referred to as connected routes. Hosts attached to the subnets of which an Arista device is part of, are referred to as attached hosts or routes. On Arista devices, there may be system-configured non-routeable prefixes which are referred to as internal routes. Route types that correspond to 'standard routing protocols' and are defined in IANA-RTPROTO-MIB, take on the same value as IANAipRouteProtocol. · Integer32

The route type that corresponds to this conceptual row.

aristaFIBStatsTotalRoutesForRouteType

1.3.6.1.4.1.30065.3.23.1.2.1.2

Gauge32

Indicates the total number of routes active in the FIB for the specified address family and route type.

aristaFIBStatsByPrefixLenTable

1.3.6.1.4.1.30065.3.23.1.3

Index: aristaFIBStatsAF · aristaFIBStatsPrefixLen

Each route entry present in the FIB has an associated prefix length. This table contains FIB statistics for each address family and prefix length.

aristaFIBStatsPrefixLen

1.3.6.1.4.1.30065.3.23.1.3.1.1

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

The prefix length that corresponds to this conceptual row.

aristaFIBStatsTotalRoutesForPrefixLen

1.3.6.1.4.1.30065.3.23.1.3.1.2

Gauge32

Indicates the total number of routes active in the FIB for the specified address family and specific prefix length.

↑ To TOC