Kek Modem Key Assignment Is Rejected

Usage Guidelines

Use the cablepre-equalizationexclude command to disable pre-equalization for DOCSIS 1.1 CMs that claim pre-equalization support but do not properly implement pre-equalization functions.

To enable pre-equalization, use the cableupstreamequalization-coefficient interface configuration command. Pre-equalization starts when a cable modem that supports DOCSIS 1.1 or above sends the CMTS router a ranging request message indicating that pre-equalization is possible.

The following example of output from the showcablemodemverbose command shows which modems are indicating pre-equalizer support during the DOCSIS registration process. In this example, the first two modems are capable of pre-equalization support, and the last two modems support DOCSIS 1.0, which does not support pre-equalization. You do not need to use the cablepre-equalizationexclude command for DOCSIS 1.0 CMs.

Router# MAC Address : 0019.474a.c4b0 Transmit Equalizer Support : {Taps/Symbol= 1, Num of Taps= 24} MAC Address : 0019.474a.c498 Transmit Equalizer Support : {Taps/Symbol= 1, Num of Taps= 24} MAC Address : 0020.40dc.4ce4 Transmit Equalizer Support : {Taps/Symbol= 0, Num of Taps= 0} MAC Address : 0020.4077.21a0 Transmit Equalizer Support : {Taps/Symbol= 0, Num of Taps= 0}

Exclusion is supported for a specified DOCSIS 1.1 cable modem, or for a specified OUI value for the entire interface. Removing the cablepre-equalizationexcludeconfiguration returns the cable modem or interface to normal pre-equalization processes during cable modem registration.

Examples

The following example configures pre-equalization to be excluded for the specified cable modem. Pre-equalization data is not sent for the corresponding cable modem:

Router(config)#

The following example configures pre-equalization to be excluded for the specified OUI value of the entire interface. Pre-equalization data is not sent for the corresponding OUI value of the entire interface:

Router(config)#

The following series of commands configures pre-equalization on the Cisco uBR10012 router with MC5X20U BPEs. On the PRE Console, configure the following commands.

Router# Enter configuration commands, one per line. End with CNTL/Z. Router(config)# Router(config)# Router# Router# cable pre-equalization exclude oui 00.09.04 Router#

On the line card console for the same Cisco uBR10012 router, verify the configuration with the following command:

Linecard# cable pre-equalization exclude oui 00.09.04

The following series of commands configures pre-equalization on the Cisco uBR7246VXR router with MC28U cable interface line cards. On the Network Processing Engine (NPE) console, configure and verify with the following commands.

Router# Enter configuration commands, one per line. End with CNTL/Z. Router(config)# Router(config)# Router#show run 02:58:10: %SYS-5-CONFIG_I: Configured from console by consolen Router# cable pre-equalization exclude oui 00.09.24

On the line card console for the same Cisco uBR7246VXR router, verify the configuration with the following command:

Linecard# cable pre-equalization exclude oui 00.09.24

After either of these exclusion methods for pre-equalization are configured, you can verify that all ranging messages do not include pre-equalization data. Use the following debug commands in global configuration mode:

  • debugcablerange
  • debugcableinterfacecx/x/x mac-addr

Verify the ranging message for the non-excluded cable modems include pre-equalization data, and for the excluded cable modems, the ranging messages do not include such data.

The following example removes pre-equalization exclusion for the specified OUI and interface. This results in the cable modem or OUI to return to normal pre-equalization functions. Ranging messages resume sending pre-equalization data.

Router(config)# {mac-addr | id}

You can verify removal of this feature using the debugcableinterfacecommand.

MIBs list

With IPHost Network Monitor you can run simple snmp requests against a Cisco device in your network.

cdxCmtsCmStatusValue

Cisco DOCSIS Cmts Cable Modem Status Value

1.3.6.1.4.1.9.9.116.1.3.2.1.1

Current Cable Modem connectivity state. The object extends states in docsIfCmtsCmStatusValue in more details. The enumerations are: offline(1) : modem considered offline. others(2) : states is in docsIfCmtsCmStatusValue. initRangingRcvd(3) : modem sent initial ranging. initDhcpReqRcvd(4) : dhcp request received. onlineNetAccessDisabled(5): modem registered, but network access for the CM is disabled. onlineKekAssigned(6) : modem registered, BPI enabled and KEK assigned. onlineTekAssigned(7) : modem registered, BPI enabled and TEK assigned. rejectBadMic(8) : modem did attempt to register but registration was refused due to bad mic. rejectBadCos(9) : modem did attempt to register but registration was refused due to bad COS. kekRejected(10) : KEK modem key assignment rejected. tekRejected(11) : TEK modem key assignment rejected. online(12) : modem registered, enabled for data. initTftpPacketRcvd(13) : tftp packet received and option file transfer started. initTodRquestRcvd(14) : Time of the Day (TOD) request received. reset(15) : modem is resetting. rangingInProgress(16) : initial ranging is in progress. -- deprecated value -- rangingCompleted(17) : initial ranging is completed. dhcpGotIpAddr(18) : modem has got an IP address from the DHCP server. rejStaleConfig(19) : modem did attempt to register but registration was refused due to stale Config. rejIpSpoof(20) : modem did attempt to register but registration was refused due to IP Spoof. rejClassFail(21) : modem did attempt to register but registration was refused due to Class failure. rejRegNack(22) : modem did attempt to register but no acknowledgement was received. bpiKekExpired(23) : KEK modem key assignment expired. bpiTekExpired(24) : TEK modem key assignment expired. shutdown(25) : modem is in shutdown state. channelChgInitRangingRcvd(26) : modem sent initial ranging during channel change. channelChgRangingInProgress(27) : initial ranging is in progress during channel change. This cdxCmtsCmStatusValue could return initRangingRcvd(3) or rangingInProgress(16) when the docsIfCmtsCmStatusValue is ranging(2). This cdxCmtsCmStatusValue will return others(2) when the docsIfCmtsCmStatusValue states is either rangingAborted(3), rangingComplete(4), and ipComplete(5). This cdxCmtsCmStatusValue could return online(12), or onlineNetAccessDisabled(5) for CM with BPI disabled, or onlineNetAccessDisabled(5) or onlineTekAssigned(7) for CM with BPI enabled, when the docsIfCmtsCmStatusValue is registrationComplete(6). This cdxCmtsCmStatusValue could return either rejectBadMic(8), rejectBadCos(9) rejStaleConfig(19) or rejRegNack(22) when the docsIfCmtsCmStatusValue is accessDenied(7) for possible reasons of cable modem registration abort. This cdxCmtsCmStatusValue could return either onlineKekAssigned(6), kekRejected(10), tekRejected(11), or online(12) for the CM with BPI enabled when the docsIfCmtsCmStatusValue is registeredBPIInitializing(9). The state rejectBadCos(9) is not applicable for DOCSIS1.1 modems. The CMTS only reports states it is able to detect.

Back to CISCO-DOCS-EXT-MIB MIB page.

IPHost Network monitor allows you to monitor cdxCmtsCmStatusValue on Cisco device via the SNMP protocol. Download IPHost Network Monitor (500 monitors for 30 days, 50 monitors free forever) to start monitoring Cisco optical switches right now.

Easy monitoring of cdxCmtsCmStatusValue with IPHost tools

MIBs list

0 thoughts on “Kek Modem Key Assignment Is Rejected

Leave a Reply

Your email address will not be published. Required fields are marked *