ZHONE-COM-IP-IP-MIB: View SNMP OID List / Download MIB

IP objects based on RFC 2011. The ipAddrTable has been removed as that information is now reflected in the ipInterfaceTable.

Zhone IP Table.

Zhone IP Entry. This table augments the Routing Domain Table defined in comIpRD.mib. A row will be added to this table whenever a domain is added to the Routing Domain Table.

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 source-routed via the host). Enumeration: 'forwarding': 1, 'notForwarding': 2.

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, etc.

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 addresses of unsupported Classes (e.g., Class E). For entities which are not IP routers and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address.

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 as IP routers, this counter will include only those packets which were Source-Routed via this entity, and the Source-Route option processing was successful.

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 datagrams discarded while awaiting re-assembly.

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 datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion.

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. Note that this includes any datagrams which a host cannot route because all of its default routers are down.

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 algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received.

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 Address Translation table used for mapping from IP addresses to physical addresses.

Each entry contains one IpAddress to `physical' address equivalence. An IpAddress is unique to the routing domain. An entry may be added to or removed from the table using the zhIpNetToMediaRowStatus object. The columnar objects required to create the row are zhIpNetToMediaIpIfIndex, zhIpNetToMediaNetAddress, zhIpNetToMediaPhysAddress, and zhIpNetToMediaType.

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) has the effect of invalidating the corresponding entry in the ipNetToMediaTable. That is, it effectively disassociates 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 ipNetToMediaType object. Enumeration: 'static': 4, 'other': 1, 'dynamic': 3, 'invalid': 2.

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

Zhone IP MIB Module. IP Software Minneapolis, MN