Chapter 18: Baseline Privacy Interface (BPI)
STANDARD Revision 1.0
C4® CMTS Release 8.3 User Guide
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
604
If all fields in the privacy line have been filled in with valid values, the modem should be BPI-enabled and capable of
passing data. If the modem is unauthorized, or the Primary SAId has an invalid value (Primary SAId: XXXX Seq: XX), then
proceed to the BPI MIB debugging section.
Baseline Privacy MIB Debugging
At this point the modem should be registered and have completed some portion of Baseline Privacy initialization. Steady
state CM information may be collected using a MIB browser or respective BPI CLI commands to check the appropriate MIB
entries for any failures that may have occurred. For issues related to denied authorization, check the
docsBpi2CmtsAuthEntry and look at the reject error string for the respective modem. For issues related to traffic keys
(TEKs), check the docsBpi2CmtsTekEntry and look at the reject error string for the respective modem’s SAId (Key Id).
(UCAM) Use the following command to display privacy authorization for a given cable-mac group registered on a UCAM:
show interface cable-mac <mac> cable privacy authorization <mac>
(UCAM) Use the following command to display privacy traffic key (TEK) for a given cable-mac group registered on a UCAM:
show interface cable-mac <mac> cable privacy tek <SAId>
Baseline Privacy Trap Codes
The table below lists the Baseline Privacy traps furnished by the C4/c CMTS and the recommended user action for each
one. See
Baseline Privacy Interface (BPI)
(page 585) for more information. For information on enabling or disabling traps,
see
Simple Network Management Protocol Management Station
Table 79.
Baseline Privacy Trap Codes
Trap Code
Name
Process
ANM_DOCSIS_B101_0
Missing Baseline Privacy Configuration Setting TLV
CM Registration
Problem: May occur only when registering modems in BPI mode, not BPI+ mode.