IP objects

Integer

read-write

The indication of whether this entry is acting as an IP gateway in respect to the forwarding of datagrams received by, but not address to, this entity. IP gateways forward datagrams. IP hosts do not (except those source-routed via the host).

Note that for some managed nodes, this object may take on only a subset of the value possible. Accordingly, it is appropriate for an agent to return a 'badValue' respond if a management station attempts to change this object to an inappropriate value.

Integer

read-write

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.

Counter

read-only

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

Counter

read-only

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.

Counter

read-only

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 that are not IP Gateways and there do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address.

Counter

read-only

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

Counter

read-only

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

Counter

read-only

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.

Counter

read-only

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

Counter

read-only

The total number of IP datagrams that 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.

Counter

read-only

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.

Counter

read-only

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

Integer

read-only

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

Counter

read-only

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

Counter

read-only

The number of IP datagrams successfully reassembled.

Counter

read-only

The number of failures detected by the IP reassembly 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.

Counter

read-only

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

Counter

read-only

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.

Counter

read-only

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

N/A

not-accessible

The table of addressing information relevant to this entity's IP addresses.

N/A

not-accessible

The addressing information for one of this entity's IP addresses.

Each entry contains data for the following objects:

ipAdEntAddr

ipAdEntIfIndex

ipAdEntNetMask

ipAdEntBcastAddr

ipAdEntReasmMaxSize

IpAddress

read-only

The IP address to which this entry's addressing information pertains.

Integer

read-only

The index value which 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 ifIndex.

IpAddress

read-only

The subnet mask associated with the IP address of this entry. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.

Integer

read-only

The value of the leas-significant bit in the IP broadcast address used for sending datagrams on the (logical) interface associated with the IP address of this entry. For example, when the Internet standard all-ones broadcast address is used, the value will be 1. This value applies to both the subnet and network broadcasts addresses used by the entity on this (logical) interface.

Integer

read-only

The size of the largest IP datagram which this entity can reassemble from incoming IP fragmented datagrams received on this interface.

N/A

not-accessible

This entity's IP Routing table.

N/A

not-accessible

A route to a particular destination.

Each entry contains data for the following objects:

ipRouteDest

ipRouteIfIndex

ipRouteMetric1

ipRouteMetric2

ipRouteMetric3

ipRouteMetric4

ipRouteNextHop

ipRouteType

ipRouteProto

ipRouteAge

ipRouteMask

ipRouteMetric5

ipRouteInfo

IpAddress

read-write

The destination IP address of this route. An entry with a value of 0.0.0.0 is considered a default route. Multiple routes to a single destination can appear in the table, but access to such multiple entries is dependent on the table-access mechanisms defined by the network management protocol in use.

Integer

read-write

The index value that uniquely identifies the local interface through which the next hop of this route should be reached. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.

Integer

read-write

The primary routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.

Integer

read-write

An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.

Integer

read-write

An alternate routing metric for this route. The semantics of this metric aredetermined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.

Integer

read-write

An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.

IpAddress

read-write

The IP address of the next hop of this route. In the case of a route bound to an interface which is realized via a broadcast media, the value of this field is the agent's IP address on that interface.

Integer

read-write

The type of route. Note that the values 'direct' and 'indirect' refer to the notion of direct and indirect routing in the IP architecture.

Setting this object to the value 'invalid' (2) has the effect of invalidating the corresponding entry in the ipRouteTable object. That is, it effectively disassociates the destination identified with said entry from the route 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 ipRouteType object.

This object supports the following values:

1 = other

2 = invalid

3 = direct

4 = indirect

Integer

read-only

The routing mechanism via which this route was learned. Inclusion of value for gateway routing protocols is not intended to imply that hosts should support those protocols.

This object supports the following values:

1 = other

2 = local

3 = netmgmt

4 = icmp

5 = egp

6 = ggp

7 = hello

8 = rip

9 = is-is

10 = es-is

11 = ciscoIgrp

12 = bbnSpfIgp

13 = ospf

14 = bgp

Integer

read-write

The number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of 'too old' can be implied except through knowledge of the routing protocol by which the route was learned.

IpAddress

read-write

Indicate the mask to be local-ANDed with the destination address before being compared to the value in the ipRouteDest field. For those systems that do not support arbitrary subnet masks, an agent constructs the value fo the ipRouteMask by determining whether the value of the correspondent ipRouteDest field belong to a class-A, B, or C network, and then using one of:

If the value of the ipRouteDest is 0.0.0.0 (a default route), then the mask value is also 0.0.0.0. It should be noted that all IP routing subsystems implicitly use this mechanism.

Integer

read-write

An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.

Object Identifier

read-only

A reference to MIB definitions specific to the particular routing protocol which is responsible for this route, as determined by the value specified in the route's ipRouteProto value. If this information is not present, its value should be set to the OBJECT IDENTIFIER {0 0}, which is a syntactically valid object identifier, and any conformant implementation of ASN.1 and BER must be able to generate and recognize this value.

N/A

not-accessible

The IP Address Translation table used for mapping from IP addresses to physical addresses.

N/A

not-accessible

Each entry contains one IpAddress to 'physical' address equivalence.

Each entry contains data for the following objects:

ipNetToMediaIfIndex

ipNetToMediaPhysAddress

ipNetToMediaNetAddress

ipNetToMediaType

Integer

read-write

The 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.

PhysAddress

read-write

The media-dependent 'physical' address.

IpAddress

read-write

The IpAddress corresponding to the media-ddependent 'physical' address.

Integer

read-write

The type of mapping.

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.

This object supports the following values:

1 = other

2 = invalid

3 = dynamic

4 = static

Counter

read-only

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.