TUNNEL-MIB: View SNMP OID List / Download MIB

VENDOR: INTERNET-STANDARD


 Home MIB: TUNNEL-MIB
Download as:   
SNMPv2-CONF, IF-MIB, IPV6-FLOW-LABEL-MIB, SNMPv2-SMI, IANAifType-MIB, INET-ADDRESS-MIB, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 tunnelMIB 1.3.6.1.2.1.10.131
The MIB module for management of IP Tunnels, independent of the specific encapsulation scheme in use. Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4087; see the RFC itself for full legal notices.
         tunnelMIBObjects 1.3.6.1.2.1.10.131.1
             tunnel 1.3.6.1.2.1.10.131.1.1
                 tunnelIfTable 1.3.6.1.2.1.10.131.1.1.1 no-access
The (conceptual) table containing information on configured tunnels.
                     tunnelIfEntry 1.3.6.1.2.1.10.131.1.1.1.1 no-access
An entry (conceptual row) containing the information on a particular configured tunnel.
                         tunnelIfLocalAddress 1.3.6.1.2.1.10.131.1.1.1.1.1 ipaddress read-only
The address of the local endpoint of the tunnel (i.e., the source address used in the outer IP header), or 0.0.0.0 if unknown or if the tunnel is over IPv6. Since this object does not support IPv6, it is deprecated in favor of tunnelIfLocalInetAddress.
                         tunnelIfRemoteAddress 1.3.6.1.2.1.10.131.1.1.1.1.2 ipaddress read-only
The address of the remote endpoint of the tunnel (i.e., the destination address used in the outer IP header), or 0.0.0.0 if unknown, or an IPv6 address, or the tunnel is not a point-to-point link (e.g., if it is a 6to4 tunnel). Since this object does not support IPv6, it is deprecated in favor of tunnelIfRemoteInetAddress.
                         tunnelIfEncapsMethod 1.3.6.1.2.1.10.131.1.1.1.1.3 ianatunneltype read-only
The encapsulation method used by the tunnel.
                         tunnelIfHopLimit 1.3.6.1.2.1.10.131.1.1.1.1.4 integer32 read-write
The IPv4 TTL or IPv6 Hop Limit to use in the outer IP header. A value of 0 indicates that the value is copied from the payload's header.
                         tunnelIfSecurity 1.3.6.1.2.1.10.131.1.1.1.1.5 integer read-only
The method used by the tunnel to secure the outer IP header. The value ipsec indicates that IPsec is used between the tunnel endpoints for authentication or encryption or both. More specific security-related information may be available in a MIB module for the security protocol in use. Enumeration: 'none': 1, 'other': 3, 'ipsec': 2.
                         tunnelIfTOS 1.3.6.1.2.1.10.131.1.1.1.1.6 integer32 read-write
The method used to set the high 6 bits (the differentiated services codepoint) of the IPv4 TOS or IPv6 Traffic Class in the outer IP header. A value of -1 indicates that the bits are copied from the payload's header. A value of -2 indicates that a traffic conditioner is invoked and more information may be available in a traffic conditioner MIB module. A value between 0 and 63 inclusive indicates that the bit field is set to the indicated value. Note: instead of the name tunnelIfTOS, a better name would have been tunnelIfDSCPMethod, but the existing name appeared in RFC 2667 and existing objects cannot be renamed.
                         tunnelIfFlowLabel 1.3.6.1.2.1.10.131.1.1.1.1.7 ipv6flowlabelorany read-write
The method used to set the IPv6 Flow Label value. This object need not be present in rows where tunnelIfAddressType indicates the tunnel is not over IPv6. A value of -1 indicates that a traffic conditioner is invoked and more information may be available in a traffic conditioner MIB. Any other value indicates that the Flow Label field is set to the indicated value.
                         tunnelIfAddressType 1.3.6.1.2.1.10.131.1.1.1.1.8 inetaddresstype read-write
The type of address in the corresponding tunnelIfLocalInetAddress and tunnelIfRemoteInetAddress objects.
                         tunnelIfLocalInetAddress 1.3.6.1.2.1.10.131.1.1.1.1.9 inetaddress read-write
The address of the local endpoint of the tunnel (i.e., the source address used in the outer IP header). If the address is unknown, the value is 0.0.0.0 for IPv4 or :: for IPv6. The type of this object is given by tunnelIfAddressType.
                         tunnelIfRemoteInetAddress 1.3.6.1.2.1.10.131.1.1.1.1.10 inetaddress read-write
The address of the remote endpoint of the tunnel (i.e., the destination address used in the outer IP header). If the address is unknown or the tunnel is not a point-to-point link (e.g., if it is a 6to4 tunnel), the value is 0.0.0.0 for tunnels over IPv4 or :: for tunnels over IPv6. The type of this object is given by tunnelIfAddressType.
                         tunnelIfEncapsLimit 1.3.6.1.2.1.10.131.1.1.1.1.11 integer32 read-write
The maximum number of additional encapsulations permitted for packets undergoing encapsulation at this node. A value of -1 indicates that no limit is present (except as a result of the packet size).
                 tunnelConfigTable 1.3.6.1.2.1.10.131.1.1.2 no-access
The (conceptual) table containing information on configured tunnels. This table can be used to map a set of tunnel endpoints to the associated ifIndex value. It can also be used for row creation. Note that every row in the tunnelIfTable with a fixed IPv4 destination address should have a corresponding row in the tunnelConfigTable, regardless of whether it was created via SNMP. Since this table does not support IPv6, it is deprecated in favor of tunnelInetConfigTable.
                     tunnelConfigEntry 1.3.6.1.2.1.10.131.1.1.2.1 no-access
An entry (conceptual row) containing the information on a particular configured tunnel. Since this entry does not support IPv6, it is deprecated in favor of tunnelInetConfigEntry.
                         tunnelConfigLocalAddress 1.3.6.1.2.1.10.131.1.1.2.1.1 ipaddress no-access
The address of the local endpoint of the tunnel, or 0.0.0.0 if the device is free to choose any of its addresses at tunnel establishment time. Since this object does not support IPv6, it is deprecated in favor of tunnelInetConfigLocalAddress.
                         tunnelConfigRemoteAddress 1.3.6.1.2.1.10.131.1.1.2.1.2 ipaddress no-access
The address of the remote endpoint of the tunnel. Since this object does not support IPv6, it is deprecated in favor of tunnelInetConfigRemoteAddress.
                         tunnelConfigEncapsMethod 1.3.6.1.2.1.10.131.1.1.2.1.3 ianatunneltype no-access
The encapsulation method used by the tunnel. Since this object does not support IPv6, it is deprecated in favor of tunnelInetConfigEncapsMethod.
                         tunnelConfigID 1.3.6.1.2.1.10.131.1.1.2.1.4 integer32 no-access
An identifier used to distinguish between multiple tunnels of the same encapsulation method, with the same endpoints. If the encapsulation protocol only allows one tunnel per set of endpoint addresses (such as for GRE or IP-in-IP), the value of this object is 1. For encapsulation methods (such as L2F) which allow multiple parallel tunnels, the manager is responsible for choosing any ID which does not conflict with an existing row, such as choosing a random number. Since this object does not support IPv6, it is deprecated in favor of tunnelInetConfigID.
                         tunnelConfigIfIndex 1.3.6.1.2.1.10.131.1.1.2.1.5 interfaceindexorzero read-only
If the value of tunnelConfigStatus for this row is active, then this object contains the value of ifIndex corresponding to the tunnel interface. A value of 0 is not legal in the active state, and means that the interface index has not yet been assigned. Since this object does not support IPv6, it is deprecated in favor of tunnelInetConfigIfIndex.
                         tunnelConfigStatus 1.3.6.1.2.1.10.131.1.1.2.1.6 rowstatus read-only
The status of this row, by which new entries may be created, or old entries deleted from this table. The agent need not support setting this object to createAndWait or notInService since there are no other writable objects in this table, and writable objects in rows of corresponding tables such as the tunnelIfTable may be modified while this row is active. To create a row in this table for an encapsulation method which does not support multiple parallel tunnels with the same endpoints, the management station should simply use a tunnelConfigID of 1, and set tunnelConfigStatus to createAndGo. For encapsulation methods such as L2F which allow multiple parallel tunnels, the management station may select a pseudo-random number to use as the tunnelConfigID and set tunnelConfigStatus to createAndGo. In the event that this ID is already in use and an inconsistentValue is returned in response to the set operation, the management station should simply select a new pseudo-random number and retry the operation. Creating a row in this table will cause an interface index to be assigned by the agent in an implementation-dependent manner, and corresponding rows will be instantiated in the ifTable and the tunnelIfTable. The status of this row will become active as soon as the agent assigns the interface index, regardless of whether the interface is operationally up. Deleting a row in this table will likewise delete the corresponding row in the ifTable and in the tunnelIfTable. Since this object does not support IPv6, it is deprecated in favor of tunnelInetConfigStatus.
                 tunnelInetConfigTable 1.3.6.1.2.1.10.131.1.1.3 no-access
The (conceptual) table containing information on configured tunnels. This table can be used to map a set of tunnel endpoints to the associated ifIndex value. It can also be used for row creation. Note that every row in the tunnelIfTable with a fixed destination address should have a corresponding row in the tunnelInetConfigTable, regardless of whether it was created via SNMP.
                     tunnelInetConfigEntry 1.3.6.1.2.1.10.131.1.1.3.1 no-access
An entry (conceptual row) containing the information on a particular configured tunnel. Note that there is a 128 subid maximum for object OIDs. Implementers need to be aware that if the total number of octets in tunnelInetConfigLocalAddress and tunnelInetConfigRemoteAddress exceeds 110 then OIDs of column instances in this table will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. In practice this is not expected to be a problem since IPv4 and IPv6 addresses will not cause the limit to be reached, but if other types are supported by an agent, care must be taken to ensure that the sum of the lengths do not cause the limit to be exceeded.
                         tunnelInetConfigAddressType 1.3.6.1.2.1.10.131.1.1.3.1.1 inetaddresstype no-access
The address type over which the tunnel encapsulates packets.
                         tunnelInetConfigLocalAddress 1.3.6.1.2.1.10.131.1.1.3.1.2 inetaddress no-access
The address of the local endpoint of the tunnel, or 0.0.0.0 (for IPv4) or :: (for IPv6) if the device is free to choose any of its addresses at tunnel establishment time.
                         tunnelInetConfigRemoteAddress 1.3.6.1.2.1.10.131.1.1.3.1.3 inetaddress no-access
The address of the remote endpoint of the tunnel.
                         tunnelInetConfigEncapsMethod 1.3.6.1.2.1.10.131.1.1.3.1.4 ianatunneltype no-access
The encapsulation method used by the tunnel.
                         tunnelInetConfigID 1.3.6.1.2.1.10.131.1.1.3.1.5 integer32 no-access
An identifier used to distinguish between multiple tunnels of the same encapsulation method, with the same endpoints. If the encapsulation protocol only allows one tunnel per set of endpoint addresses (such as for GRE or IP-in-IP), the value of this object is 1. For encapsulation methods (such as L2F) which allow multiple parallel tunnels, the manager is responsible for choosing any ID which does not conflict with an existing row, such as choosing a random number.
                         tunnelInetConfigIfIndex 1.3.6.1.2.1.10.131.1.1.3.1.6 interfaceindexorzero read-only
If the value of tunnelInetConfigStatus for this row is active, then this object contains the value of ifIndex corresponding to the tunnel interface. A value of 0 is not legal in the active state, and means that the interface index has not yet been assigned.
                         tunnelInetConfigStatus 1.3.6.1.2.1.10.131.1.1.3.1.7 rowstatus read-only
The status of this row, by which new entries may be created, or old entries deleted from this table. The agent need not support setting this object to createAndWait or notInService since there are no other writable objects in this table, and writable objects in rows of corresponding tables such as the tunnelIfTable may be modified while this row is active. To create a row in this table for an encapsulation method which does not support multiple parallel tunnels with the same endpoints, the management station should simply use a tunnelInetConfigID of 1, and set tunnelInetConfigStatus to createAndGo. For encapsulation methods such as L2F which allow multiple parallel tunnels, the management station may select a pseudo-random number to use as the tunnelInetConfigID and set tunnelInetConfigStatus to createAndGo. In the event that this ID is already in use and an inconsistentValue is returned in response to the set operation, the management station should simply select a new pseudo-random number and retry the operation. Creating a row in this table will cause an interface index to be assigned by the agent in an implementation-dependent manner, and corresponding rows will be instantiated in the ifTable and the tunnelIfTable. The status of this row will become active as soon as the agent assigns the interface index, regardless of whether the interface is operationally up. Deleting a row in this table will likewise delete the corresponding row in the ifTable and in the tunnelIfTable.
                         tunnelInetConfigStorageType 1.3.6.1.2.1.10.131.1.1.3.1.8 storagetype read-only
The storage type of this row. If the row is permanent(4), no objects in the row need be writable.
         tunnelMIBConformance 1.3.6.1.2.1.10.131.2
             tunnelMIBCompliances 1.3.6.1.2.1.10.131.2.1
                 tunnelMIBCompliance 1.3.6.1.2.1.10.131.2.1.1
The (deprecated) IPv4-only compliance statement for the IP Tunnel MIB. This is deprecated in favor of tunnelMIBInetFullCompliance and tunnelMIBInetReadOnlyCompliance.
                 tunnelMIBInetFullCompliance 1.3.6.1.2.1.10.131.2.1.2
The full compliance statement for the IP Tunnel MIB.
                 tunnelMIBInetReadOnlyCompliance 1.3.6.1.2.1.10.131.2.1.3
The read-only compliance statement for the IP Tunnel MIB.
             tunnelMIBGroups 1.3.6.1.2.1.10.131.2.2
                 tunnelMIBBasicGroup 1.3.6.1.2.1.10.131.2.2.1
A collection of objects to support basic management of IPv4 Tunnels. Since this group cannot support IPv6, it is deprecated in favor of tunnelMIBInetGroup.
                 tunnelMIBInetGroup 1.3.6.1.2.1.10.131.2.2.2
A collection of objects to support basic management of IPv4 and IPv6 Tunnels.