| OID symbolic | OID numeric | Type | Access | Description |
|---|
| 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 | | | |
| INT 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. |
| tnIp2DnsConfig | 1.3.6.1.4.1.868.2.5.10.8.2 | | | |
| INT 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. |
| tnIp2DnsServerConfTable | 1.3.6.1.4.1.868.2.5.10.8.2.2 | | not-accessible | Table to manage IP configuration. |
| tnIp2DnsServerConfEntry | 1.3.6.1.4.1.868.2.5.10.8.2.2.1 | | not-accessible | An entry containing IP status for each device. |
| INT tnIp2DnsServerIndex | 1.3.6.1.4.1.868.2.5.10.8.2.2.1.1 | INTEGER | not-accessible | DNS Server Instance. |
| INT 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. |
| IP 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. |
| NUM 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 | | not-accessible | Table to manage IP Interfaces. |
| tnIp2InterfaceEntry | 1.3.6.1.4.1.868.2.5.10.8.3.1 | | not-accessible | An entry containing IP status for each device. |
| INT tnIp2IntVlan | 1.3.6.1.4.1.868.2.5.10.8.3.1.1 | INTEGER | not-accessible | 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. |
| INT tnIp2IntDHCPEnable | 1.3.6.1.4.1.868.2.5.10.8.3.1.2 | INTEGER | read-create | 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. |
| INT tnIp2IntFallback | 1.3.6.1.4.1.868.2.5.10.8.3.1.3 | INTEGER | read-create | 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. |
| IPt 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. |
| IP tnIp2IntCurrentLease | 1.3.6.1.4.1.868.2.5.10.8.3.1.5 | InetAddress | read-create | For DHCP interfaces with an active lease, this column show
the current interface address, as provided by the DHCP server. |
| IP tnIp2Addr | 1.3.6.1.4.1.868.2.5.10.8.3.1.6 | InetAddress | read-create | 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. |
| INT tnIp2MaskLen | 1.3.6.1.4.1.868.2.5.10.8.3.1.7 | INTEGER | read-create | 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. |
| ROW tnIp2Status | 1.3.6.1.4.1.868.2.5.10.8.3.1.8 | RowStatus | read-create | 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 | | not-accessible | Table to manage IP Routes. |
| tnIp2RoutesEntry | 1.3.6.1.4.1.868.2.5.10.8.4.1 | | not-accessible | An entry containing IP Routes. |
| IP tnIp2RoutesNetwork | 1.3.6.1.4.1.868.2.5.10.8.4.1.1 | InetAddress | not-accessible | 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. |
| INT tnIp2RoutesMaskLen | 1.3.6.1.4.1.868.2.5.10.8.4.1.2 | INTEGER | not-accessible | 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). |
| IP tnIp2RoutesGateway | 1.3.6.1.4.1.868.2.5.10.8.4.1.3 | InetAddress | not-accessible | 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. |
| INT tnIp2RoutesNextHop | 1.3.6.1.4.1.868.2.5.10.8.4.1.4 | INTEGER | read-create | 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. |
| IPt tnIp2RoutesType | 1.3.6.1.4.1.868.2.5.10.8.4.1.5 | InetAddressType | read-create | The IP address type of the routes.
For a detailed description of this type, please refer to INET-ADDRESS-MIB. |
| ROW tnIp2RoutesStatus | 1.3.6.1.4.1.868.2.5.10.8.4.1.6 | RowStatus | read-create | 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. |
