ipNetToPhysicalTable

1.3.6.1.2.1.4.35.1.1

ipNetToPhysicalIfIndex

INTEGER

not-accessible

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

INTEGER{unknown(0),ipv4(1),ipv6(2),ipv4z(3),ipv6z(4),dns(16)}

not-accessible

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

OCTET STRING{(0,255)}

not-accessible

The IP Address corresponding to the media-dependent

`physical' address. The address type of this object is

specified in ipNetToPhysicalAddressType.

Implementors 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

OCTET STRING{(0,65535)}

read-create

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.

The actually supported access is read-only.

1.3.6.1.2.1.4.35.1.5

ipNetToPhysicalLastUpdated

TimeTicks

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),invalid(2),dynamic(3),static(4),local(5)}

read-create

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 e.g., IPv4 ARP or 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.

The actually supported access is read-only.

1.3.6.1.2.1.4.35.1.7

ipNetToPhysicalState

INTEGER{reachable(1),stale(2),delay(3),probe(4),invalid(5),unknown(6),incomplete(7)}

read-only

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 (e.g. 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

INTEGER{active(1),notInService(2),notReady(3),createAndGo(4),createAndWait(5),destroy(6)}

read-create

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 can not be made active until the

ipNetToPhysicalPhysAddress object has been set.

Note that if the ipNetToPhysicalType is set to 'invalid',

the managed node may delete the entry independent of the

state of this object.

The actually supported access is read-only.