CASA-CABLE-CMCPE-MIB :: casaCmtsCpeIpNetToPhysicalType

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CASA-CABLE-CMCPE-MIB › casaCmtsCpeIpNetToPhysicalType

casaCmtsCpeIpNetToPhysicalType

Module: CASA-CABLE-CMCPE-MIB

OID (symbolic): CASA-CABLE-CMCPE-MIB::casaCmtsCpeIpNetToPhysicalType

OID (numeric): 1.3.6.1.4.1.20858.10.12.1.4.1.7

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: 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.

What is casaCmtsCpeIpNetToPhysicalType?

Indicates how this IP-to-physical-address mapping was established: dynamic(3) means it was learned via ARP or IPv6 Neighbor Discovery, static(4) means it was manually configured, and setting the value to invalid(2) effectively removes/disassociates the entry. Because these entries are typically not persistent, changes here normally shouldn't be saved to non-volatile storage.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.20858.10.12.1.4.1.7
snmpwalk -v2c -c public <target> CASA-CABLE-CMCPE-MIB::casaCmtsCpeIpNetToPhysicalType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.20858.10.12.1.4.1.7.1
snmpget -v2c -c public <target> CASA-CABLE-CMCPE-MIB::casaCmtsCpeIpNetToPhysicalType.1

Start monitoring Casa Systems CMTS platforms with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CASA-CABLE-CMCPE-MIB::casaCmtsCpeIpNetToPhysicalType OID value, configure state conditions and alerts, and monitor any Casa Systems CMTS platforms from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.20858casaCASA-MIB
1.3.6.1.4.1.20858.10casaMgmtCASA-802-TAP-MIB
Numeric OIDNameModule
1.3.6.1.4.1.20858.10.12casaCmtsCmCpeMibCASA-CABLE-CMCPE-MIB
1.3.6.1.4.1.20858.10.12.1casaCmtsCmCpeObjectsCASA-CABLE-CMCPE-MIB
1.3.6.1.4.1.20858.10.12.1.4casaCmtsCpeIpNetToPhysicalTableCASA-CABLE-CMCPE-MIB
1.3.6.1.4.1.20858.10.12.1.4.1casaCmtsCpeIpNetToPhysicalEntryCASA-CABLE-CMCPE-MIB
1.3.6.1.4.1.20858.10.12.1.4.1.7casaCmtsCpeIpNetToPhysicalTypeCASA-CABLE-CMCPE-MIB