ZHONE-COM-IP-IP-MIB Table View

The indication of whether this entity is acting as an IP
router in respect to the forwarding of datagrams received
by, but not addressed to, this entity. IP routers forward
datagrams. IP hosts do not (except those sou…

The default value inserted into the Time-To-Live field of
the IP header of datagrams originated at this entity,
whenever a TTL value is not supplied by the transport layer
protocol.

The total number of input datagrams received from
interfaces, including those received in error.

The number of input datagrams discarded due to errors in
their IP headers, including bad checksums, version number
mismatch, other format errors, time-to-live exceeded, errors
discovered in processing their IP options, …

The number of input datagrams discarded because the IP
address in their IP header's destination field was not a
valid address to be received at this entity. This count
includes invalid addresses (e.g., 0.0.0.0) and add…

The number of input datagrams for which this entity was not
their final IP destination, as a result of which an attempt
was made to find a route to forward them to that final
destination. In entities which do not act a…

The number of locally-addressed datagrams received
successfully but discarded because of an unknown or
unsupported protocol.

The number of input IP datagrams for which no problems were
encountered to prevent their continued processing, but which
were discarded (e.g., for lack of buffer space). Note that
this counter does not include any data…

The total number of input datagrams successfully delivered
to IP user-protocols (including ICMP).

The total number of IP datagrams which local IP user-
protocols (including ICMP) supplied to IP in requests for
transmission. Note that this counter does not include any
datagrams counted in ipForwDatagrams.

The number of output IP datagrams for which no problem was
encountered to prevent their transmission to their
destination, but which were discarded (e.g., for lack of
buffer space). Note that this counter would include…

The number of IP datagrams discarded because no route could
be found to transmit them to their destination. Note that
this counter includes any packets counted in ipForwDatagrams
which meet this `no-route' criterion. …

The maximum number of seconds which received fragments are
held while they are awaiting reassembly at this entity.

The number of IP fragments received which needed to be
reassembled at this entity.

The number of IP datagrams successfully re-assembled.

The number of failures detected by the IP re-assembly
algorithm (for whatever reason: timed out, errors, etc).
Note that this is not necessarily a count of discarded IP
fragments since some algorithms (notably the algor…

The number of IP datagrams that have been successfully
fragmented at this entity.

The number of IP datagrams that have been discarded because
they needed to be fragmented at this entity but could not
be, e.g., because their Don't Fragment flag was set.

The number of IP datagram fragments that have been
generated as a result of fragmentation at this entity.

The number of routing entries which were chosen to be
discarded even though they are valid. One possible reason
for discarding such an entry could be to free-up buffer
space for other routing entries.

The IP interface on which this entry's equivalence is
effective. The interface identified by a particular value
of this index is the same interface as identified by the
same value of ifIndex in MIB-II (rfc2233).

The IpAddress corresponding to the media-dependent
`physical' address.

The media-dependent `physical' address.

The type of mapping.
other(1) -- cannot be determined
dynamic(3) -- mapping is supplied by the ARP server.
static(4) -- mapping is configured by the user.

Setting this object to the value invalid(2) ha…

This is required to be able to add/remove entries to/from
the table.