IP-MIB
Functions Overview
The IP-MIB defined in RFC 4293, which is an extension to that defined in RFC 1213, contains the statistics about packets forwarded by a device by using an interface board and packets sent to the main control board.
This MIB provides the following information:
- IPv4 detail information and IPv6 detail information of the interface
- System-based IP packet statistics and interface-based IP packet statistics
- Addresses, address prefixes, and address translation information
- IPv6 scope zone indexes
- Router advertisement packets
- ICMP packet statistics
Root directory:
iso(1).org(3).dod(6).internet(1).mgmt(2).mib-2(1)
Description of MIB Tables
ipNetToPhysicalTable
The IP Address Translation table used for mapping from IP addresses to physical addresses.
The Address Translation tables contain the IP address to 'physical' address equivalences. Some interfaces do not use translation tables for determining address equivalences (for example, DDN-X.25 has an algorithmic method); if all interfaces are of this type, then the Address Translation table is empty, that is, has zero entries.
The ND protocol uses this type of address translation table.
The indexes of this table are ipNetToPhysicalIfIndex, ipNetToPhysicalNetAddressType, and ipNetToPhysicalNetAddress.
OID |
Object Name |
Syntax |
Max Access |
Description |
Implemented Specifications |
---|---|---|---|---|---|
1.3.6.1.2.1.4.35.1.1 |
ipNetToPhysicalIfIndex |
InterfaceIndex |
Not-accessible |
This object indicates the index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.4.35.1.2 |
ipNetToPhysicalNetAddressType |
InetAddressType |
Not-accessible |
This object indicates the type of ipNetToPhysicalNetAddress. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.4.35.1.3 |
ipNetToPhysicalNetAddress |
InetAddress |
Not-accessible |
This object indicates the IP address corresponding to the media-dependent 'physical' address. The address type of this object is specified in ipNetToPhysicalAddressType. Implementers need to be aware that if the size of ipNetToPhysicalNetAddress exceeds 115 octets, then OIDS of instances of columns in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.4.35.1.4 |
ipNetToPhysicalPhysAddress |
PhysAddress (SIZE(0..65535)) |
Read-create |
This object indicates the media-dependent 'physical' address. As the entries in this table are typically not persistent when this object is written the entity SHOULD NOT save the change to non-volatile storage. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.4.35.1.5 |
ipNetToPhysicalLastUpdated |
TimeStamp |
Read-only |
The value of sysUpTime at the time this entry was last updated. If this entry was updated prior to the last re-initialization of the local network management subsystem, then this object contains a zero value. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.4.35.1.6 |
ipNetToPhysicalType |
INTEGER { other(1), -- none of the following invalid(2), -- an invalidated mapping dynamic(3), static(4), local(5) -- local interface } |
Read-create |
The value of this object identifies the type of mapping. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the ipNetToPhysicalTable. That is, it effectively dis- associates the interface identified with said entry from the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ipNetToPhysicalType object. The 'dynamic(3)' type indicates that the IP address to physical addresses mapping has been dynamically resolved using for example, the IPv6 Neighbor Discovery protocol. The 'static(4)' type indicates that the mapping has been statically configured. Both of these refer to entries that provide mappings for other entities addresses. The 'local(5)' type indicates that the mapping is provided for an entity's own interface address. As the entries in this table are typically not persistent when this object is written the entity SHOULD NOT save the change to non-volatile storage. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.4.35.1.7 |
ipNetToPhysicalState |
INTEGER { reachable(1), -- confirmed reachability stale(2), -- unconfirmed reachability delay(3), -- waiting for reachability -- confirmation before entering -- the probe state probe(4), -- actively probing invalid(5), -- an invalidated mapping unknown(6), -- state cannot be determined -- for some reason. incomplete(7) -- address resolution is being -- performed } |
Read-only |
The value of this object identifies the Neighbor Unreachability Detection state for the interface when the address mapping in this entry is used. If Neighbor Unreachability Detection is not in use (for example for IPv4), this object is always unknown(6). |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.4.35.1.8 |
ipNetToPhysicalRowStatus |
RowStatus |
Read-create |
This object indicates the status of this conceptual row. The RowStatus TC requires that this DESCRIPTION clause states under which circumstances other objects in this row can be modified. The value of this object has no effect on whether other objects in this conceptual row can be modified. A conceptual row cannot be made active until the ipNetToPhysicalPhysAddress object has been set. The SET operation cannot be performed on logical interfaces. Note that if the ipNetToPhysicalType is set to 'invalid', the managed node may delete the entry independent of the state of this object. |
Currently, only CREATE_GO and DESTROY operations are supported. When the CREATE_GO operation is performed on an unspecified object, the default value is used. In the case of multi-value binding, the system supports the auto operation. |
Creation Restriction
None.
Modification Restriction
None.
Deletion Restriction
None.
Access Restriction
None.