All MIBs › RC-IPV6-MIB › rcIpv6NetToPhysicalType
rcIpv6NetToPhysicalType
Module: RC-IPV6-MIB
OID (symbolic): RC-IPV6-MIB::rcIpv6NetToPhysicalType
OID (numeric): 1.3.6.1.4.1.2272.1.62.1.1.7.1.6
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-create
Description: The type of mapping.
The 'dynamic(2)' 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(3)' type indicates that the mapping has been statically configured. Both of these refer to entries that provide mappings for other entities addresses.
The 'local(4)' 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.
What is rcIpv6NetToPhysicalType?
Reports how this IPv6-to-physical-address mapping was learned: dynamically via neighbor discovery, statically configured, or as the local interface's own address. An admin uses this to tell a manually pinned neighbor entry apart from one learned automatically.
OID Breakdown
Upper-level ancestors (13 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.2272 | rapidCity | RAPID-CITY |
| 1.3.6.1.4.1.2272.1 | rcMgmt | RAPID-CITY |
| 1.3.6.1.4.1.2272.1.62 | rcIpv6 | RAPID-CITY |
| 1.3.6.1.4.1.2272.1.62.1 | rcIpv6Mib | RAPID-CITY |
| 1.3.6.1.4.1.2272.1.62.1.1 | rcIpv6Objects | RAPID-CITY |
| 1.3.6.1.4.1.2272.1.62.1.1.7 | rcIpv6NetToPhysicalTable | RAPID-CITY |
| 1.3.6.1.4.1.2272.1.62.1.1.7.1 | rcIpv6NetToPhysicalEntry | RAPID-CITY |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2272.1.62.1.1.7.1.6 | rcIpv6NetToPhysicalType | RC-IPV6-MIB |