TN-DEV-SYS-IP2-MIB: View SNMP OID List / Download MIB

VENDOR: TRANSITION ENGINEERING INC.


 Home MIB: TN-DEV-SYS-IP2-MIB
Download as:   
SNMPv2-CONF, IF-MIB, SNMPv2-SMI, TN-TC, IP-MIB, INET-ADDRESS-MIB, TRANSITION-SMI, ENTITY-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
 tnDevSysIpMgmtMIB 1.3.6.1.4.1.868.2.5.10
The mib provides functionalities for managing the IP DHCP, IPv6 and DNS.
       tnDevSysIp2mgmt 1.3.6.1.4.1.868.2.5.10.8
           tnIp2Mode 1.3.6.1.4.1.868.2.5.10.8.1 integer read-write
Configure whether the IP stack should act as a Host or a Router. In Host mode, IP traffic between interfaces will not be routed. In Router mode traffic is routed between all interfaces. Enumeration: 'notApplicable': 0, 'host': 1, 'router': 2.
           tnIp2DnsConfig 1.3.6.1.4.1.868.2.5.10.8.2
               tnIp2DnsProxy 1.3.6.1.4.1.868.2.5.10.8.2.1 integer read-write
When DNS proxy is enabled, system will relay DNS requests to the currently configured DNS server, and reply as a DNS resolver to the client devices on the network. Enumeration: 'true': 1, 'false': 2.
               tnIp2DnsServerConfTable 1.3.6.1.4.1.868.2.5.10.8.2.2 no-access
Table to manage IP configuration.
                   tnIp2DnsServerConfEntry 1.3.6.1.4.1.868.2.5.10.8.2.2.1 no-access
An entry containing IP status for each device.
                       tnIp2DnsServerIndex 1.3.6.1.4.1.868.2.5.10.8.2.2.1.1 integer no-access
DNS Server Instance.
                       tnIp2DnsServerMode 1.3.6.1.4.1.868.2.5.10.8.2.2.1.2 integer read-write
This setting controls the DNS name resolution done by the switch. The following modes are supported: No DNS server: No DNS server will be used. staticIPv4 : Explicitly provide the IPv4 address of the DNS Server in dotted decimal notation. staticIPv6 : Explicitly provide the IPv6 address of the DNS Server in dotted decimal notation. anyDHCPv4 : From any IPv4 DHCP interfaces: The first DNS server offered from a DHCP lease to a DHCP-enabled interface will be used. thisDHCPv4 : From the specified IPv4 DHCP interface. Specify from which DHCP-enabled interface a provided DNS server should be preferred. anyDHCPv6 : From any IPv6 DHCP interfaces: The first DNS server offered from a DHCP lease to a DHCP-enabled interface will be used. thisDHCPv6 : From the specified IPv6 DHCP interface. Specify from which DHCP-enabled interface a provided DNS server should be preferred. Enumeration: 'thisDHCPv4': 5, 'thisDHCPv6': 7, 'anyDHCPv4': 4, 'staticIPv4': 2, 'anyDHCPv6': 6, 'staticIPv6': 3, 'noDNS': 1.
                       tnIp2DnsServerAddr 1.3.6.1.4.1.868.2.5.10.8.2.2.1.3 inetaddress read-write
The DNS IP address of the device. For a detailed description of this type, please refer to INET-ADDRESS-MIB.
                       tnIp2DnsVlan 1.3.6.1.4.1.868.2.5.10.8.2.2.1.4 tninterfaceindex read-write
Specify from which DHCP-enabled interface a provided DNS server should be preferred.
           tnIp2InterfaceTable 1.3.6.1.4.1.868.2.5.10.8.3 no-access
Table to manage IP Interfaces.
               tnIp2InterfaceEntry 1.3.6.1.4.1.868.2.5.10.8.3.1 no-access
An entry containing IP status for each device.
                   tnIp2IntVlan 1.3.6.1.4.1.868.2.5.10.8.3.1.1 integer no-access
The VLAN associated with the IP interface. Only ports in this VLAN will be able to access the IP interface. This field is only available for input when creating an new interface.
                   tnIp2IntDHCPEnable 1.3.6.1.4.1.868.2.5.10.8.3.1.2 integer read-only
Enable the DHCP client. If this option is enabled, the system will configure the IPv4 address and mask of the interface using the DHCP protocol. The DHCP client will announce the configured System Name as hostname to provide DNS lookup. Enumeration: 'true': 1, 'false': 2.
                   tnIp2IntFallback 1.3.6.1.4.1.868.2.5.10.8.3.1.3 integer read-only
The number of seconds for trying to obtain a DHCP lease. After this period expires, a configured IPv4 address will be used as IPv4 interface address. A value of zero disables the fallback mechanism, such that DHCP will keep retrying until a valid lease is obtained.
                   tnIp2AddrType 1.3.6.1.4.1.868.2.5.10.8.3.1.4 inetaddresstype read-write
The IP address type of the device. For a detailed description of this type, please refer to INET-ADDRESS-MIB.
                   tnIp2IntCurrentLease 1.3.6.1.4.1.868.2.5.10.8.3.1.5 inetaddress read-only
For DHCP interfaces with an active lease, this column show the current interface address, as provided by the DHCP server.
                   tnIp2Addr 1.3.6.1.4.1.868.2.5.10.8.3.1.6 inetaddress read-only
The IPv4 address of the interface in dotted decimal notation. If DHCP is enabled, this field is not used. The field may also be left blank if IPv4 operation on the interface is not desired.
                   tnIp2MaskLen 1.3.6.1.4.1.868.2.5.10.8.3.1.7 integer read-only
The IPv4 network mask, in number of bits (prefix length). Valid values are between 0 and 30 bits for a IPv4 address. If DHCP is enabled, this field is not used. The field may also be left blank if IPv4 operation on the interface is not desired.
                   tnIp2Status 1.3.6.1.4.1.868.2.5.10.8.3.1.8 rowstatus read-only
The status of this conceptual row entry of IP Interface table. This object is used to manage the creation and deletion of conceptual rows. 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); - '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; - '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.
           tnIp2RoutesTable 1.3.6.1.4.1.868.2.5.10.8.4 no-access
Table to manage IP Routes.
               tnIp2RoutesEntry 1.3.6.1.4.1.868.2.5.10.8.4.1 no-access
An entry containing IP Routes.
                   tnIp2RoutesNetwork 1.3.6.1.4.1.868.2.5.10.8.4.1.1 inetaddress no-access
The destination IP network or host address of this route. Valid format is dotted decimal notationor a valid IPv6 notation. A default route can use the value 0.0.0.0or IPv6 :: notation.
                   tnIp2RoutesMaskLen 1.3.6.1.4.1.868.2.5.10.8.4.1.2 integer no-access
The destination IP network or host mask, in number of bits (prefix length). It defines how much of a network address that must match, in order to qualify for this route. Valid values are between 0 and 32 bits respectively 128 for IPv6 routes. Only a default route will have a mask length of 0 (as it will match anything).
                   tnIp2RoutesGateway 1.3.6.1.4.1.868.2.5.10.8.4.1.3 inetaddress no-access
The IP address of the IP gateway. Valid format is dotted decimal notation or a valid IPv6 notation. Gateway and Network must be of the same type.
                   tnIp2RoutesNextHop 1.3.6.1.4.1.868.2.5.10.8.4.1.4 integer read-only
The VLAN ID (VID) of the specific IPv6 interface associated with the gateway. The given VID ranges from 1 to 4094 and will be effective only when the corresponding IPv6 interface is valid. If the IPv6 gateway address is link-local, it must specify the next hop VLAN for the gateway. If the IPv6 gateway address is not link-local, system ignores the next hop VLAN for the gateway.
                   tnIp2RoutesType 1.3.6.1.4.1.868.2.5.10.8.4.1.5 inetaddresstype read-only
The IP address type of the routes. For a detailed description of this type, please refer to INET-ADDRESS-MIB.
                   tnIp2RoutesStatus 1.3.6.1.4.1.868.2.5.10.8.4.1.6 rowstatus read-only
The status of this conceptual row entry of IP Interface table. This object is used to manage the creation and deletion of conceptual rows. 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); - '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; - '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.