IP-MIB Table View

The table containing per-interface IPv4-specific
information.

The table containing per-interface IPv6-specific
information.

The table containing system wide, IP version specific
traffic statistics.  This table and the ipIfStatsTable
contain similar objects whose difference is in their
granularity.  Where this table contains system wide traffic
statistics, the ipIfStatsTable contains the same statistics
but counted on a per-interface basis.

The table containing per-interface traffic statistics.  This
table and the ipSystemStatsTable contain similar objects
whose difference is in their granularity.  Where this table
contains per-interface statistics, the ipSystemStatsTable
contains the same statistics, but counted on a system wide
basis.

This table allows the user to determine the source of an IP
address or set of IP addresses, and allows other tables to
share the information via pointer rather than by copying.
          
For example, when the node configures both a unicast and
anycast address for a prefix, the ipAddressPrefix objects
for those addresses will point to a single row in this
table.
          
This table primarily provides support for IPv6 prefixes, and
several of the objects are less meaningful for IPv4.  The
table continues to allow IPv4 addresses to allow future
flexibility.  In order to promote a common configuration,
this document includes suggestions for default values for
IPv4 prefixes.  Each of these values may be overridden if an
object is meaningful to the node.
          
All prefixes used by this entity should be included in this
table independent of how the entity learned the prefix.
(This table isn't limited to prefixes learned from router
          
advertisements.)

This table contains addressing information relevant to the
entity's interfaces.
          
This table does not contain multicast address information.
Tables for such information should be contained in multicast
specific MIBs, such as RFC 3019.
          
While this table is writable, the user will note that
several objects, such as ipAddressOrigin, are not.  The
intention in allowing a user to write to this table is to
allow them to add or remove any entry that isn't
          
permanent.  The user should be allowed to modify objects
and entries when that would not cause inconsistencies
within the table.  Allowing write access to objects, such
as ipAddressOrigin, could allow a user to insert an entry
and then label it incorrectly.
          
Note well: When including IPv6 link-local addresses in this
table, the entry must use an InetAddressType of 'ipv6z' in
order to differentiate between the possible interfaces.

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
(e.g., DDN-X.25 has an algorithmic method); if all
interfaces are of this type, then the Address Translation
table is empty, i.e., has zero entries.
          
While many protocols may be used to populate this table, ARP
and Neighbor Discovery are the most likely
options.

The table used to describe IPv6 unicast and multicast scope
zones.
          
For those objects that have names rather than numbers, the
names were chosen to coincide with the names used in the
IPv6 address architecture document.

The table used to describe the default routers known to this
          
entity.

The table containing information used to construct router
advertisements.

The table of generic system-wide ICMP counters.

The table of system-wide per-version, per-message type ICMP
counters.