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.
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 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.2 | mgmt | AXON-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.126 | docsBpi2MIB | DOCS-IETF-BPI2-MIB |
| 1.3.6.1.2.1.126.1 | docsBpi2MIBObjects | DOCS-IETF-BPI2-MIB |
| 1.3.6.1.2.1.126.1.2 | docsBpi2CmtsObjects | DOCS-IETF-BPI2-MIB |
| 1.3.6.1.2.1.126.1.2.2 | docsBpi2CmtsAuthTable | DOCS-IETF-BPI2-MIB |
| 1.3.6.1.2.1.126.1.2.2.1 | docsBpi2CmtsAuthEntry | DOCS-IETF-BPI2-MIB |
| 1.3.6.1.2.1.126.1.2.2.1.19 | docsBpi2CmtsAuthBpkmCmCertValid | DOCS-IETF-BPI2-MIB |