DOCS-IETF-BPI2-MIB :: docsBpi2CmtsAuthBpkmCmCertValid

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › DOCS-IETF-BPI2-MIB › docsBpi2CmtsAuthBpkmCmCertValid

docsBpi2CmtsAuthBpkmCmCertValid

Module: DOCS-IETF-BPI2-MIB

OID (symbolic): DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthBpkmCmCertValid

OID (numeric): 1.3.6.1.2.1.126.1.2.2.1.19

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Contains the reason why a CM's certificate is deemed valid or invalid. Return unknown(0) if the CM is running BPI mode. ValidCmChained(1) means the certificate is valid because it chains to a valid certificate. ValidCmTrusted(2) means the certificate is valid because it has been provisioned (in the docsBpi2CmtsProvisionedCmCert table) to be trusted. InvalidCmUntrusted(3) means the certificate is invalid because it has been provisioned (in the docsBpi2CmtsProvisionedCmCert table) to be untrusted. InvalidCAUntrusted(4) means the certificate is invalid because it chains to an untrusted certificate. InvalidCmOther(5) and InvalidCAOther(6) refer to errors in parsing, validity periods, etc., which are attributable to the CM certificate or its chain, respectively; additional information may be found in docsBpi2AuthRejectErrorString for these types of errors.

What is docsBpi2CmtsAuthBpkmCmCertValid?

Records why the CMTS considers this CM's certificate valid or invalid: unknown (BPI mode), validCmChained/validCmTrusted for valid cases, or invalidCmUntrusted/invalidCAUntrusted/invalidCmOther/invalidCAOther for the various failure reasons. This is the key field to check when a modem is failing authorization due to a certificate problem, alongside docsBpi2CmtsAuthRejectErrorString for more detail on 'Other' cases.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.126.1.2.2.1.19
snmpwalk -v2c -c public <target> DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthBpkmCmCertValid

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.126.1.2.2.1.19.1
snmpget -v2c -c public <target> DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthBpkmCmCertValid.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> docsBpi2CmtsAuthBpkmCmCertValid.1

Start monitoring DOCSIS cable modem/CMTS (Baseline Privacy Plus, vendor-neutral IETF standard RFC 4131) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthBpkmCmCertValid OID value, configure state conditions and alerts, and monitor any DOCSIS cable modem/CMTS (Baseline Privacy Plus, vendor-neutral IETF standard RFC 4131) from a single console.

OID Breakdown

Upper-level ancestors (6 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.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.126docsBpi2MIBDOCS-IETF-BPI2-MIB
1.3.6.1.2.1.126.1docsBpi2MIBObjectsDOCS-IETF-BPI2-MIB
1.3.6.1.2.1.126.1.2docsBpi2CmtsObjectsDOCS-IETF-BPI2-MIB
1.3.6.1.2.1.126.1.2.2docsBpi2CmtsAuthTableDOCS-IETF-BPI2-MIB
1.3.6.1.2.1.126.1.2.2.1docsBpi2CmtsAuthEntryDOCS-IETF-BPI2-MIB
1.3.6.1.2.1.126.1.2.2.1.19docsBpi2CmtsAuthBpkmCmCertValidDOCS-IETF-BPI2-MIB