Have an account?

  •   Personalized content
  •   Your products and support

Need an account?

Create an account

Cisco cBR Converged Broadband Routers DOCSIS Software Configuration Guide for Cisco IOS XE Gibraltar 16.12.x

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco cBR Converged Broadband Routers DOCSIS Software Configuration Guide for Cisco IOS XE Gibraltar 16.12.x

Chapter Title

DOCSIS 3.1 Upstream Triggered Spectrum Capture – Proactive Network Management

Results

Updated:
November 8, 2019

Chapter: DOCSIS 3.1 Upstream Triggered Spectrum Capture – Proactive Network Management

DOCSIS 3.1 Upstream Triggered Spectrum Capture – Proactive Network Management

This document describes how to configure the DOCSIS 3.1 Upstream Triggered Spectrum Capture – Proactive Network Management on the Cisco cBR Series Converged Broadband Router.

Finding Feature Information

Your software release may not support all the features that are documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. The Feature Information Table at the end of this document provides information about the documented features and lists the releases in which each feature is supported.

Hardware Compatibility Matrix for the Cisco cBR Series Routers


Note
The hardware components that are introduced in a given Cisco IOS-XE release are supported in all subsequent releases unless otherwise specified.
Table 1. Hardware Compatibility Matrix for the Cisco cBR Series Routers

Cisco CMTS Platform

Processor Engine

Interface Cards

Cisco cBR-8 Converged Broadband Router

Cisco IOS-XE Release 3.15.0S and Later Releases

Cisco cBR-8 Supervisor:

  • PID—CBR-CCAP-SUP-160G

  • PID—CBR-CCAP-SUP-60G1

  • PID—CBR-SUP-8X10G-PIC

Cisco IOS-XE Release 3.15.0S and Later Releases

Cisco cBR-8 CCAP Line Cards:

  • PID—CBR-CCAP-LC-40G-R

  • PID—CBR-CCAP-LC-80G-R
1 Effective with Cisco IOS-XE Release 3.17.0S, CBR-CCAP-SUP-60G supports 8 cable line cards. The total traffic rate is limited to 60 Gbps. The total number of downstream service flows is limited to 72268, and downstream unicast low-latency flow does not count against the limits.

Information About Upstream Triggered Spectrum Capture – Proactive Network Management

Proactive Network Management (PNM) enables you to measure and report conditions in the network. The PNM detects, identifies, and quantifies undesired impacts to the network, such as cable faults and ingress noise. The DOCSIS 3.1 PHY specification defines the different types of tests and measurements that can be performed at CCAP and CM. You can leverage this information to make the necessary modifications that can improve conditions and monitor networking trends to detect when network improvements are needed.

Cisco cBR supports Upstream Triggered Spectrum Capture. The upstream triggered spectrum analysis measurement provides a wideband spectrum analyzer in the CCAP which can be triggered to examine desired upstream transmissions as well as underlying noise or interference during a quiet period.

The PNM tests and receives data output from the CMTS using the Simple Network Management Protocol (SNMP) objects. The PNM feature is supported on RPHY.

The following Upstream Triggered Spectrum Capture objects are supported:

  • UsTriggeredSpectrumCaptureFile

  • UsTriggeredSpectrumCaptureCfg

  • UsTriggeredSpectrumCaptureCtrl

  • UsTriggeredSpectrumCaptureStatus

  • UsTriggeredSpectrumCaptureCapabilities

  • CCAPBulkDataControl

The Cisco cBR router provides the ability to trigger spectrum sample capture and perform spectrum analysis using the FreeRun mode, which is a continuous mode with a maximum of 10 samples per second stacked on each capture file).

Proactive Network Management for Supervisor High Availability, Line Card High Availability and containers

PNM Supervisor High Availability support ensures that all captures are stopped and all the captures states in the Line Card and Supervisor client are cleaned up when Supervisor High Availability happens. You can create new capture configurations and initiate tests on the newly active supervisor through SNMP.

cBR supports Line Card High Availability and Line Card Process Restart for Proactive Network Management, and will support the restart of any test in progress.

Active syncing of capture data between active and standby SUP is not supported for Proactive Network Management. After switchover, all new captures must be configured by the user/client again.

Bulk Data Transfer MIBs enables configuration of the following paramters for PNM:

  • TFTP server bulk data transfer IP address

  • TFTP server bulk data transfer path

How to Configure Upstream Triggered Spectrum Capture – Proactive Network Management

The PNM IOX container is used for the TFTP transfer of capture files to user configured destination server. The guestshell IOX container for TFTP transfer of PNM files is supported. The PNM executable is built into the guestshell packaged as part of cbr8 image. This executable must be installed on both active and standby SUP manually.

Before you begin

The CCAP supports one client configuration per port on a line card. You must create a capture configuration entry before attempting to start or stop the capture tests. One capture configuration for the FreeRun trigger mode is defined by the interface index key for the UsTriggeredSpectrumCaptureCfg object.

Only one capture per end user client per port is supported at a time. Hence, the CCAP sets the Upstream Triggered Spectrum Capture configuration index to 1. A PNM MIB query for Upstream Triggered Spectrum Capture configuration index other than 1 is not supported. The Cisco cBR router supports a maximum of eight captures on upstream ports per line card and a maximum of 20 captures per Cisco cBR-8 router for RPHY.

The following scenarios are not supported:

  • UsTriggeredSpectrumCaptureResult MIB

  • Simultaneous captures on adjacent ports on CLC

  • RPD support captures only one us-port per RPD at a given time.

SUMMARY STEPS

  1. Ensure that the guestshell container is running before the captures are started to ensure successful TFTP operation. Use the show app-hosting list command to check if the guestshell container is running.
  2. The app-hosting CLI is used to install, deploy, start and stop the IOX container.
  3. Ensure that the python is running on the guestshell container.
  4. Ensure that the PNM tftp process is active and running on the guestshell container.

DETAILED STEPS

  Command or Action Purpose
Step 1

Ensure that the guestshell container is running before the captures are started to ensure successful TFTP operation. Use the show app-hosting list command to check if the guestshell container is running.

Example:


Router# show app-hosting list 
App id                           Stat
----------------------------------------------------- 
guestshell                        RUNNING
Step 2

The app-hosting CLI is used to install, deploy, start and stop the IOX container.

Example:


Router# show run | begin app-hosting
app-hosting appid guestshell
app-vnic gateway0 virtualportgroup 4 guest-interface 0  
guest-ipaddress 9.32.254.2 netmask 255.255.255.0 
app-default-gateway 9.32.254.1 guest-interface
Step 3

Ensure that the python is running on the guestshell container.

Example:


cBR8#guestshell run python -V
Python 2.7.5
Step 4

Ensure that the PNM tftp process is active and running on the guestshell container.

Example:


cBR8#guestshell run systemctl status pnm
 pnm.service - cbr pnm telemetry delivery system
    Loaded: loaded (/etc/systemd/system/pnm.service; disabled; vendor preset: disabled)
    Active: active (running) since Wed 2019-01-09 15:13:40 UTC; 9min ago

The PNM capture tests generate files to report measurements or test results. The results file includes header information that is common to all types of PNM tests and fields, and data that are specific to the type of PNM test. The abstract PnmCaptureFile object defines the attributes and format of the header information common to all PNM test files. File header fields are right-justified within the field and left-padded with zero values if necessary.

The following fields define the header for the PnmCaptureFile object for Upstream Spectrum Triggered Capture tests.

  • FileType - A four-byte hexadecimal identifier specific to the type of PNM test that generated the data file.

    For Upstream Triggered Spectrum Capture, the file type is 0x504e4e6a.

  • Major Version - This attribute represents the file header version. This value is incremented by one when the header format is modified by this specification.

    For Upstream Triggered Spectrum Capture, major version is 0x1.

  • Minor Version - This attribute is reserved for vendor-specific and vendor-defined version information.

    For Upstream Triggered Spectrum Capture, minor version is 0x0.

  • CaptureTime - This attribute represents the epoch time (also known as 'unix time') which is the number of seconds that have elapsed since midnight Coordinated Universal Time (UTC), Thursday, 1 January 1970.

  • IfIndex  - This attribute represents the ifIndex of the upstream RF port sampled.

  • UniqueCcapId - A 256-byte hexadecimal field representing a unique CCAP identifier (either a loopback address (IPv4 or IPv6) or FQDN). The value is a null-terminated string.

    For Upstream Triggered Spectrum Capture, this is the ‘hostname’ of the CMTS.

Proactive Network Management Interface Index

To determine which slot/subslot/port of an ifindex translateS to that of RPHY, see the mapping in the running configuration.

Before you begin

The Upstream Triggered Spectrum Capture – The Cisco cBR router supports multiple RPDs per line card with multiple US-ports. However, on RPD, you can configure only one US-port and initiate the captures anytime.

For RPHY, it is not mandatory that the US port is bound to a MAC domain. If it is configured under an RPD, it can be configured for PNM.
The SNMP ifindex for MIB objects can be obtained using the show CLI:

Router# show snmp mib ifmib ifindex | i  badb.ad13.2be0  
RPD(badb.ad13.2be0)-usport0: Ifindex = 435564
where badb.ad13.2be0 is the RPD identifier.

SUMMARY STEPS

  1. Run the following show command to identify the SNMP ifindex value:
  2. Run the following command to identify the slot/subslot/port an ifindex that would translate to RPHY:

DETAILED STEPS

  Command or Action Purpose
Step 1

Run the following show command to identify the SNMP ifindex value:

 

Router# show snmp mib ifmib ifindex | i 435564 
RPD(badb.ad13.2be0)-usport0: Ifindex = 435564
Step 2

Run the following command to identify the slot/subslot/port an ifindex that would translate to RPHY:

 

Router# show run | b badb.ad13.2be0
identifier badb.ad13.2be 
core-interface Te1/1/0
principal 
rpd-ds 0 downstream-cable 1/0/2 profile 2  
rpd-us 0 upstream-cable 1/0/2 profile 21     

The slot/subslot/port is upstream-cable 1/0/2 profile 21.


Note

Cisco cBR 16.10.1g introduces an RPHY ifIndex change. Ensure that you have gone through the following updates to enable the changes:

  • The RPHY ifIndex feature removes the Cisco private ifIndex for PRHY channels (ifIndex starting from 41,000). The ifIndex are not created manually. All the ifIndex are created automatically when configuring RPD. It is applicable fore ifIndex starting from 41w for US (if-type 205) and DS (if-type 128). The RPHY ifIndex feature does not work for ifIndex values that are greater than 41w.

    Before the ifIndex feature, in 16.10.1f and earlier releases:

    
Router# show snmp mib ifmib ifindex | i RPD
Upstream-Cable3/0/63:0-RPD(badb.ad13.420c)-usport0: Ifindex = 421224
……
RPD(badb.ad13.420c)-usport0: Ifindex = 435560
RPD(badb.ad13.420c)-dsport0: Ifindex = 436584
Downstream-Cable3/0/31:0-RPD(badb.ad13.420c)-dsport0: Ifindex = 437608
Downstream-Cable3/0/31:1-RPD(badb.ad13.420c)-dsport0: Ifindex = 437609

    With the ifIndex feature, in 16.10.1g:

    
Router# show snmp mib ifmib ifindex | s RPD
RPD(badb.ad13.420c)-usport0: Ifindex = 415080
RPD(badb.ad13.420c)-dsport0: Ifindex = 416104

  • The RPHY ifIndex reimplement CoreToRpdMap/RpdToCoreMap tables to keep them aligned with DOCS-RPHY-MIB-2018-07-26 definition.

You do not need to create any new ifIndex for US (if-type 205) and DS (if-type 128) channels when they are configured to RPD. For versions prior to 16.10.1g, it was required that a new ifIndex had to be created (>41k) for US (if-type 205) and DS (if-type 128) channels when they are configured to RPD: 


[CBR]#show snmp mib ifmib ifindex | s RPD
RPD(badb.ad13.420c)-usport0: Ifindex = 415080
RPD(badb.ad13.420c)-dsport0: Ifindex = 416104

With the cBR 16.10.1g RPHY ifIndex feature, you do not need to manually populate any extra item in legacy MIBs.

With the cBR 16.10.1g RPHY ifIndex feature, you need to re-implement docsRphyRpdIfCoreToRpdMapTable / docsRphyRpdIfRpdToCoreMapTable, not mapping to ifIndex (>41k) for US (if-type 205) and DS (if-type 128). See the following: 


Take docsRphyRpdIfCoreToRpdMapTable for example.
/* docsRphyRpdIfCoreToRpdMapRpdRfChanType OID :1.3.6.1.4.1.4491.2.1.30.1.2.6.1.5 
   Table Index: docsRphyRpdIfCoreToRpdMapRpdCoreIndex, docsRphyRpdIfCoreToRpdMapRpdUniqueId, docsRphyRpdIfCoreToRpdMapRpdRfPortDirection, docsRphyRpdIfCoreToRpdMapRpdRfPortIndex*/
SNMPv2-SMI::enterprises.4491.2.1.30.1.2.6.1.5.403561.0.4.159.51.0.145.2.0 = INTEGER: usAtdma(5)
SNMPv2-SMI::enterprises.4491.2.1.30.1.2.6.1.5.322358.0.4.159.51.0.145.1.0 = INTEGER: dsScQam(1)
IF-MIB::ifType.403561 = INTEGER: docsCableUpstream(129)
IF-MIB::ifType.322358 = INTEGER: other(1)

[CBR]#show snmp mib ifmib ifindex
Cable9/0/0-upstream1: Ifindex = 403561
Downstream-Cable9/0/4-downstream14: Ifindex = 322358
……

  • If RfChanType is usAtdma(5), ifType of docsRphyRpdIfCoreToRpdMapRpdCoreIndex is ifType docsCableUpstream(129)

  • If RfChanType is dsScQam(1), ifType of docsRphyRpdIfCoreToRpdMapRpdCoreIndex is other(1).

So does docsRphyRpdIfRpdToCoreMapTable.

Upstream Triggered Spectrum Capture Configuration Parameters – Proactive Network Management

The following configuration parameters for Upstream Triggered Spectrum Capture – Proactive Network Management are supported. Examples of using the MIBs are also included.


Note

PNM capture configuration on cBR8 is supported only through SNMP user interface. Configuration examples for MIB commands for PNM are provided in the following sections with examples using both snmpr (setany/getone commands) as well as net-snmp tools (snmpset/snmpget commands).

Upstream Triggered Spectrum Capture Configuration Objects

The following Upstream Triggered Spectrum Capture configuration objects are supported:

  • PNM UTSC OBJECTS OID: 1.3.6.1.4.1.4491.2.1.27.1.3.10

  • PNM UTSC CAPTURE CONFIGURATION OID: 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.X.Y.Z

    Where X is the capture config parameter, Y is Ifindex, and Z is the PNM UTSC Config Index – Which is always 1. Currently only one capture configuration per upstream port is supported.

  • The following capture configuration parameters are supported, and the corresponding MIB OID value is listed.

    Table 2. Supported capture configuration parameters and the corresponding MIB OID value

    Capture configuration parameters

    Corresponding MIB OID value

    I_docsPnmCmtsUtscCfgTriggerMode

    1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.3

    I_docsPnmCmtsUtscCfgCenterFreq

    1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.8

    I_docsPnmCmtsUtscCfgSpan

    1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.9

    I_docsPnmCmtsUtscCfgNumBins

    1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.10

    I_docsPnmCmtsUtscCfgAveraging

    1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.11

    I_docsPnmCmtsUtscCfgQualifyCenterFreq

    1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.13

    I_docsPnmCmtsUtscCfgQualifyBw

    1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.14

    I_docsPnmCmtsUtscCfgQualifyThrshld

    1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.15

    I_docsPnmCmtsUtscCfgWindow

    1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.16

    I_docsPnmCmtsUtscCfgOutputFormat

    1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.17

    I_docsPnmCmtsUtscCfgRepeatPeriod

    1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.18

    I_docsPnmCmtsUtscCfgFreeRunDuration

    1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.19

    I_docsPnmCmtsUtscCfgTriggerCount

    1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.20

    I_docsPnmCmtsUtscCfgStatus

    1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.21

Upstream Triggered Spectrum Capture Configuration MIB Objects

The following Upstream Triggered Spectrum Capture configuration MIB objects are supported for PNM:

  • CaptureCfg – Contains the test trigger mode and its required configuration.

  • CaptureCtrl – Controls when the test is started and stopped.

  • CaptureStatus – Contains the current status of the test.

  • CaptureCapability – Exposes CCAP Upstream Triggered Spectrum Capture capabilities.

The following Upstream Triggered Spectrum Capture configuration MIBs are supported. SNMP walk is supported for all the MIB objects.

  • docsPnmCmtsUtscCfgTriggerMode - This attribute indicates which of the upstream triggered spectrum capture function trigger modes is supported. Only FreeRun is supported. The following are the enumerated values for trigger mode for PNM.

    • D_docsPnmCmtsUsSpecAnTrigMode_other 1

    • D_docsPnmCmtsUsSpecAnTrigMode_freeRunning 2

    • D_docsPnmCmtsUsSpecAnTrigMode_miniSlotCount 3

    • D_docsPnmCmtsUsSpecAnTrigMode_sid 4

    • D_docsPnmCmtsUsSpecAnTrigMode_idleSid 5

    • D_docsPnmCmtsUsSpecAnTrigMode_minislotNumber 6

    • D_docsPnmCmtsUsSpecAnTrigMode_cmMac 7

    • D_docsPnmCmtsUsSpecAnTrigMode_quietProbeSymbol 8

  • For FreeRun mode, the CCAP initiates sampling and continues sampling until the time duration configured in the attribute FreeRunDuration has transpired. Sampling terminates when the time duration configured in FreeRunDuration has elapsed or when FFT is disabled. The interval between captures is RepeatPeriod, or the minimum period supported by the CCAP, whichever is greater.

  • Trigger mode set and get examples:

    • snmpr commands: 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.3.<ifIndex>.1 -i 2 
clabProjDocsis.27.1.3.10.2.1.3.<ifIndex>.1 = 2
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.3.<ifIndex>.1 
clabProjDocsis.<ifIndex> = 2

    • net-snmp commands: 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.3.<ifIndex>.1 i 2
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.3.<ifIndex>.1 = INTEGER: 2
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.3.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.3.<ifIndex>.1 = INTEGER: 2

  • docsPnmCmtsUtscCfgCenterFreq - This attribute specifies the center frequency of the upstream spectrum to be sampled for analysis.

    • snmpr commands: 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.8.<ifIndex>.1 –g 102400000 
clabProjDocsis.27.1.3.10.2.1.8.<ifIndex> = 102400000
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.8.<ifIndex>.1 
clabProjDocsis.27.1.3.10.2.1.8.<ifIndex>.1 = 102400000

    • net-snmp commands: 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.8.<ifIndex>.1 u 102400000
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.8.<ifIndex>.1 = Gauge32: 102400000
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.8.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.8.<ifIndex>.1 = Gauge32: 102400000

  • docsPnmCmtsUtscCfgSpan - This attribute determines the frequency span of the upstream spectrum sample capture. When this attribute is read, it provides the actual span, which may be different from the requested (configured) span due to implementation effects.

    • snmpr commands: 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.9.<ifIndex>.1 –g 204800000 
clabProjDocsis.27.1.3.10.2.1.9.<ifIndex>.1 = 204800000
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.9.<ifIndex>.1 
clabProjDocsis.27.1.3.10.2.1.9.<ifIndex>.1 = 204800000

    • net-snmp commands: 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.9.<ifIndex>.1 u 204800000
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.9.<ifIndex>.1 = Gauge32: 204800000
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.9.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.9.<ifIndex>.1 = Gauge32: 204800000

    Note

    The center frequency and span captures parameters are set to zero as per OSSI specification on capture configuration entry create. For freerun trigger mode, these values must be set in the valid range by the user in order to run capture tests on the port.

  • docsPnmCmtsUtscCfgNumBins - This attribute determines the number of frequency bins or samples per span when sampling the upstream spectrum. When this attribute is read, it provides the actual number of bins, which may be different from the requested (configured) number of bins due to implementation effects.

    • snmpr commands 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.10.<ifIndex>.1 –g 4096 
clabProjDocsis.27.1.3.10.2.1.10.<ifIndex>.1 = 4096
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.10.<ifIndex>.1 
clabProjDocsis.27.1.3.10.2.1.10.<ifIndex>.1 = 4096

    • net-snmp commands

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.10.<ifIndex>.1 u 4096
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.10.<ifIndex>.1 = Gauge32: 4096
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.10.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.10.<ifIndex>.1 = Gauge32: 4096

  • docsPnmCmtsUtscCfgAveraging - This attribute specifies whether the CCAP is to average spectral frequency domain sample power to remove spurious spectral peaks and troughs, and the number of samples to use to calculate the average power. The CCAP MUST NOT calculate the average of the upstream spectrum samples when the value of Averaging is zero. The CCAP MUST calculate the average power of upstream spectrum samples, over the number of samples specified, when the value of the Averaging attribute is non-zero.

    • snmpr commands 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.11.<ifIndex>.1 –g 245 
clabProjDocsis.27.1.3.10.2.1.11.<ifIndex>.1 = 245 
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.11.<ifIndex>.1 
clabProjDocsis.27.1.3.10.2.1.11.<ifIndex>.1 = 245

    • net-snmp commands

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.11.<ifIndex>.1 u 245
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.11.<ifIndex>.1 = Gauge32: 245
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.11.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.11.<ifIndex>.1 = Gauge32: 245

  • docsPnmCmtsUtscCfgQualifyCenterFreq - This attribute specifies the center frequency of a band that is used to qualify a spectrum for upload. The average of the FFT linear power values in this band is computed and compared to a threshold. If the average power in the band is below the threshold, the spectrum is discarded. If the power average is greater than or equal to the threshold, the spectrum is considered qualified.

    • snmpr commands 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.13.<ifIndex>.1 –g 102400000 
clabProjDocsis.27.1.3.10.2.1.13.<ifIndex>.1 = 102400000
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.13.<ifIndex>.1 
clabProjDocsis.27.1.3.10.2.1.13.<ifIndex>.1 = 102400000

    • net-snmp commands 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.13.<ifIndex>.1 u 102400000
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.13.<ifIndex>.1 = Gauge32: 102400000
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.13.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.13.<ifIndex>.1 = Gauge32: 102400000

  • docsPnmCmtsUtscCfgQualifyBw - This attribute specifies the bandwidth of a band that is used to qualify a spectrum for upload. The average of the FFT linear power values in this band is computed and compared to a threshold. If the average power in the band is below the threshold, the spectrum is discarded. If the power average is greater than or equal to the threshold, the spectrum is considered qualified.

    • snmpr commands: 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.14.<ifIndex>.1 –g 25600000 
clabProjDocsis.27.1.3.10.2.1.14.<ifIndex>.1 = 25600000
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.14.<ifIndex>.1 
clabProjDocsis.27.1.3.10.2.1.14.<ifIndex>.1 = 25600000

    • net-snmp commands: 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.14.<ifIndex>.1 u 25600000
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.14.<ifIndex>.1 = Gauge32: 25600000
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.14.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.14.<ifIndex>.1 = Gauge32: 25600000

  • docsPnmCmtsUtscCfgQualifyThrshld - This attribute specifies the threshold applied to qualify a spectrum for upload. The average of the FFT linear power values in the specified band is computed and compared to this threshold. If the average power in the band is below the threshold, the spectrum is discarded. If the power average is greater than or equal to the threshold, the spectrum is considered qualified.

    • snmpr commands 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.15.<ifIndex>.1 –i 200 
clabProjDocsis.27.1.3.10.2.1.15.<ifIndex> = -200
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.15.<ifIndex>.1 
clabProjDocsis.27.1.3.10.2.1.15.<ifIndex>.1 = -200

    • net-snmp commands 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.15.<ifIndex>.1 i -200
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.15.<ifIndex>.1 = INTEGER: -200
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.15.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.15.<ifIndex>.1 = INTEGER: -200

  • docsPnmCmtsUtscCfgWindow - This attribute indicates which of the upstream triggered spectrum capture function window formats are supported by the CCAP. Currently cBR supports rectangular (default), blackmann harris, hann and hamming. The following are the enumerated values for window mode for PNM.

    • D_docsPnmCmtsUtscCfgWindow_other 1

    • D_docsPnmCmtsUtscCfgWindow_rectangular 2

    • D_docsPnmCmtsUtscCfgWindow_hann 3

    • D_docsPnmCmtsUtscCfgWindow_blackmanHarris 4

    • D_docsPnmCmtsUtscCfgWindow_hamming 5

    • D_docsPnmCmtsUtscCfgWindow_flatTop 6

    • D_docsPnmCmtsUtscCfgWindow_gaussian 7

    • D_docsPnmCmtsUtscCfgWindow_chebyshev 8

  • Window mode set and get examples:

    • snmpr commands: 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.16.<ifIndex>.1 -i 3 
clabProjDocsis.27.1.3.10.2.1.16.<ifIndex>.1= 3
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.16.<ifIndex>.1 
clabProjDocsis.27.1.3.10.2.1.16.<ifIndex>.1 = 3
      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.16.<ifIndex>.1 -i 6 
Error code set in packet - COMMIT_FAILED_ERROR: 1.

    • net-snmp commands: 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.16.<ifIndex>.1 i 3
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.16.<ifIndex>.1 = INTEGER: 3
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.16.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.16.<ifIndex>.1 = INTEGER: 3
      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.16.<ifIndex>.1 i 6
Error in packet.
Reason: commitFailed
Failed object: SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.16.<ifIndex>.1

    Note

    • The flat-top, guassian, and chebyshev window modes are not supported.

  • docsPnmCmtsUtscCfgOutputFormat - This attribute indicates the upstream triggered spectrum capture function data output formats that are supported by the CCAP. The CCAP is capable of reporting upstream spectrum sample FFT output data in power format. The enumeration value for power format is fftPower. Currently CCAP supports only fftPower output format. The following are the enumerated values for output format mode for PNM.

    • D_docsPnmCmtsUtscCfgOutputFormat_timeIQ 1

    • D_docsPnmCmtsUtscCfgOutputFormat_fftPower 2

    • D_docsPnmCmtsUtscCfgOutputFormat_rawAdc 3

    • D_docsPnmCmtsUtscCfgOutputFormat_fftIQ 4

    • D_docsPnmCmtsUtscCfgOutputFormat_fftAmplitude 5

    • D_docsPnmCmtsUtscCfgOutputFormat_fftDb 6

  • Output format mode set and get examples:

    • snmpr commands: 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.17.<ifIndex>.1 -i 2 
clabProjDocsis.27.1.3.10.2.1.16.<ifIndex>.1 = 2
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.17.<ifIndex>.1 
clabProjDocsis.27.1.3.10.2.1.17.<ifIndex>.1 = 2
      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.17.<ifIndex>.1 -i 4 
Error code set in packet - COMMIT_FAILED_ERROR: 1.

    • net-snmp commands: 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.17.<ifIndex>.1 i 2
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.17.<ifIndex>.1 = INTEGER: 2

      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.17.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.17.<ifIndex>.1 = INTEGER: 2
      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.17.<ifIndex>.1 i 4
Error in packet.
Reason: commitFailed
Failed object: SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.17.<ifIndex>.1

    Note

    Only the fft-pwr output format is currently supported.

  • docsPnmCmtsUtscCfgRepeatPeriod - This attribute specifies the length of time in milliseconds for which the CCAP continues to capture and return FFT results when in free running mode. The CCAP is permitted to trigger at larger intervals if unable to support the requested interval. Configuring a zero value indicates that the test is to run once only.

  • The Repeat Period is configured in microseconds and default is 50000 usec. The CCAP MUST reject an attempt to set RepeatPeriod to a value greater than the current value of FreeRunDuration.

  • Repeat Period set and get examples:

    • snmpr commands: 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.18.<ifIndex>.1 -g 25000 
clabProjDocsis.27.1.3.10.2.1.18.<ifIndex>.1 = 25000 
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.18.<ifIndex>.1 
clabProjDocsis.27.1.3.10.2.1.18.<ifIndex>.1 = 25000

    • net-snmp commands: 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.18.<ifIndex>.1 u 25000
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.18.<ifIndex>.1 = Gauge32: 25000
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.18.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.18.<ifIndex>.1 = Gauge32: 25000

  • docsPnmCmtsUtscCfgFreeRunDuration - This attribute specifies the length of time in milliseconds for which the CCAP continues to capture and return FFT results when in free running mode. Sample captures are expected to take a few microseconds, so if FreeRunDuration is set for longer than a sample capture duration, the CCAP could potentially capture more sample data than it can store.

  • The CCAP MUST reject an attempt to set FreeRunDuration to a value less than the current value of RepeatPeriod. Freerun duration is configured in millisec and the default value is 1000ms (1 second).The CCAP CLC currently captures 10 samples per second stacked in a single file. With default freerun duration configuration, there will be 11 samples.

  • FreeRun Duration set and get examples:

    • snmpr commands 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.19.<ifIndex>.1 -g 5000 
clabProjDocsis.27.1.3.10.2.1.19.<ifIndex>.1 = 5000
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.19.<ifIndex>.1 
clabProjDocsis.27.1.3.10.2.1.19.<ifIndex>.1 = 5000

    • net-snmp commands 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.19.<ifIndex>.1 u 5000
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.19.<ifIndex>.1 = Gauge32: 5000
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.19.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.19.<ifIndex>.1 = Gauge32: 5000

  • docsPnmCmtsUtscCfgTriggerCount - This attribute determines the number of times to trigger upstream spectrum sample capture when Enable and InitiateTest are set to true and configured trigger conditions are met. The trigger count configuration does NOT apply and is ignored by CCAP for captures in FreeRun trigger mode.

  • Trigger count set and get examples:

    • snmpr commands 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.20.<ifIndex>.1 -g 200 
clabProjDocsis.27.1.3.10.2.1.20.<ifIndex>.1 = 200
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.20.<ifIndex>.1 
clabProjDocsis.27.1.3.10.2.1.20.<ifIndex>.1 = 200

    • net-snmp commands 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.20.<ifIndex>.1 u 200
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.20.<ifIndex>.1 = Gauge32: 200
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.20.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.20.<ifIndex>.1 = Gauge32: 200

  • docsPnmCmtsUtscCfgStatus - This attribute determines the creation or deletion and change of status of an actual capture configuration entry on any port on the CCAP CLC. All capture entries must first be created by a client on a port before attempting to initiate any tests on the port. Thereby the client ‘owns’ that port and its configuration after creation and no other client can run any tests on the port till the currently active ‘destroys’ the configuration entry and thereby releases ownership of that port.

  • Any tests on a given port owned by a client can be run only when the capture configuration status is ’Active’. When a configuration is created, it is created with certain default values and marked ‘Not Ready’. All capture parameters need to be configured in valid range for the capture entry status to become ‘Active’. If the configuration values for various capture parameters are modified by the user/client and not according to the OSSI specification, the configuration status of the entry will be marked ‘NotReady’.

  • A capture configuration entry cannot be modified to any state unless created first. An entry cannot be recreated without destroying the previous version first. An entry cannot be modified when capture tests are currently running on the port.

  • The following are the enumerated values for configuration entry status for PNM:

    • D_docsPnmCmtsUtscCfgStatus_active 1

    • D_docsPnmCmtsUtscCfgStatus_notInService 2

    • D_docsPnmCmtsUtscCfgStatus_notReady 3

    • D_docsPnmCmtsUtscCfgStatus_createAndGo 4

    • D_docsPnmCmtsUtscCfgStatus_createAndWait 5

    • D_docsPnmCmtsUtscCfgStatus_destroy 6

  • Utsc Configuration Entry set/get example:

    • snmpr commands 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.21.<ifIndex>.1 -i 4 
clabProjDocsis.27.1.3.10.2.1.21.<ifIndex>.1 = 4 
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.21.<ifIndex>.1 
clabProjDocsis.27.1.3.10.2.1.21.<ifIndex>.1 = 1

    • net-snmp commands 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.21.<ifIndex>.1 i 4
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.21.<ifIndex>.1 = INTEGER: 4
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.21.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.21.<ifIndex>.1 = INTEGER: 3

    Note

    A configuration can be created with certain default values and is marked 'Not Ready'. It is only changed to 'Active' when valid capture configuration parameters are configured by the user. Capture tests can only be run on configurations that are 'Active'.

  • Set multiple capture config parameters at the same time.

    • Server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.18.<ifIndex>.1 -g 45000
 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.20.<ifIndex>.1 -g 10
 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.8.<ifIndex>.1 -g 100000000
 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.10.<ifIndex>.1 -g 8092
 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.15.<ifIndex>.1 -i -100 
clabProjDocsis.27.1.3.10.2.1.18.<ifIndex>.1 = 45000 
clabProjDocsis.27.1.3.10.2.1.20.<ifIndex>.1 = 10 
clabProjDocsis.27.1.3.10.2.1.8.<ifIndex>.1 = 100000000 
clabProjDocsis.27.1.3.10.2.1.10.<ifIndex>.1 = 8092 
clabProjDocsis.27.1.3.10.2.1.15.<ifIndex>.1 = -100 10.3.1.1.<ifIndex>.1 = 0

SNMP walk is supported for all the above MIB objects.

An example of SNMP walk on upstream triggered spectrum capture configuration parameter repeat period is listed:
server > snmpwalk -v2c <cmts_ip> -c <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.18                       
   SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.18.<ifIndex>.1 = Gauge32: 45000  
   SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.18.<ifIndex>.1 = Gauge32: 45000 
   SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.18.<ifIndex>.1 = Gauge32: 45000 
   SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.18.<ifIndex>.1 = Gauge32: 45000 
   SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.18.<ifIndex>.1 = Gauge32: 45000 
   SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.18.<ifIndex>.1 = Gauge32: 45000 
   SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.18.<ifIndex>.1 = Gauge32: 50000 
    <<!snip>>

Upstream Triggered Spectrum Capture Control Objects and MIBs

The following Upstream Triggered Spectrum Capture control objects and MIBs are supported:

  • PNM UTSC OBJECTS OID: 1.3.6.1.4.1.4491.2.1.27.1.3.10

  • PNM UTSC CAPTURE CONTROL OID: 1.3.6.1.4.1.4491.2.1.27.1.3.10.3.1.1.Y.Z

    Where Y is Ifindex, and Z is the PNM Upstream Triggered Spectrum Capture Configuration Index – Which is always 1. Currently only one capture configuration per upstream port is supported.

  • The capture control entry can be used to start captures or stop any active captures. The docsPnmCmtsUtscCtrlInitiateTest is a boolean value which when set, initiates a capture.

  • Starting a capture (You can only start a capture only if you have configured and owned the port, and if the capture configuration entry is active).

    • snmpr commands: 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1 -i 1 
clabProjDocsis.27.1.3.10.3.1.1.<ifIndex>.1 = 1
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1 
clabProjDocsis.27.1.3.10.3.1.1.<ifIndex>.1 = 1

    • net-snmp commands: 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1 i 1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1 = INTEGER: 1
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1 = INTEGER: 1

  • Stop a capture (You can stop an active capture only if you own that port):

    • snmpr commands: 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1 -i 0 
clabProjDocsis.27.1.3.10.3.1.1.<ifIndex>.1 = 0
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1 
clabProjDocsis.27.1.3.10.3.1.1.<ifIndex>.1 = 0

    • net-snmp commands: 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1 i 0
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1 = INTEGER: 0
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1 = INTEGER: 0

Upstream Triggered Spectrum Capture Status Objects and MIBs

The following Upstream Triggered Spectrum Capture status objects and MIBs are supported:

  • PNM UTSC OBJECTS OID: 1.3.6.1.4.1.4491.2.1.27.1.3.10

  • PNM UTSC CAPTURE STATUS OID: 1.3.6.1.4.1.4491.2.1.27.1.3.10.4.1.1.Y.Z

    Where Y is Ifindex, and Z is the PNM Upstream Triggered Spectrum Capture Configuration Index – Which is always 1. Currently only one capture configuration per upstream port is supported.

  • The capture status MIB is a read-only MIB. It reports the status of the capture on a given port (if owned by that client).

  • When the value is sampleReady, the CCAP has completed capturing and recording samples. Following are the enumerated values for capture status entry for PNM.

    • D_docsPnmCmtsUtscStatusMeasStatus_other 1

    • D_docsPnmCmtsUtscStatusMeasStatus_inactive 2

    • D_docsPnmCmtsUtscStatusMeasStatus_busy 3

    • D_docsPnmCmtsUtscStatusMeasStatus_sampleReady 4

    • D_docsPnmCmtsUtscStatusMeasStatus_error 5

    • D_docsPnmCmtsUtscStatusMeasStatus_resourceUnavailable 6

    • D_docsPnmCmtsUtscStatusMeasStatus_sampleTruncated 7

  • The status is inactive when the capture configuration entry is created and is marked busy when the tests are actively running on the port. Any platform resource limitation to run a test to make the status ‘resource unavailable’ and the error encountered while running a test would mark the status as ‘error’.

  • Get capture status on a port (You can get the status of capture on the port only if you own that port.

    • snmpr commands: 

      server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.4.1.1.<ifIndex>.1 
clabProjDocsis.27.1.3.10.4.1.1.<ifIndex>.1 = 4

    • net-snmp commands: 

      server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.4.1.1.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.4.1.1.<ifIndex>.1 = INTEGER: 4

Upstream Triggered Spectrum Capture Capability Objects and MIBs

The following Upstream Triggered Spectrum Capture capability objects and MIBs are supported for PNM:

  • PNM UTSC OBJECTS OID: 1.3.6.1.4.1.4491.2.1.27.1.3.10

  • PNM UTSC CAPTURE CAPABILITY OID: 1.3.6.1.4.1.4491.2.1.27.1.3.10.1.1.X.Y

    Where X is the capability parameter and Y is the Ifindex.

  • The capture capability MIB is a read-only MIB. The Upstream Triggered Spectrum Capture Capabilities object exposes capabilities that are supported by the CCAP for Upstream Triggered Spectrum Capture trigger modes, data output formats, and windowing function used when performing the discrete Fourier transform.

  • The following are the enumerated values for capture capability entry for PNM for CCAP.

    • docsPnmCmtsUtscCapabTriggerMode 1

    • docsPnmCmtsUtscCapabOutputFormat 2

    • docsPnmCmtsUtscCapabWindow 3

    • docsPnmCmtsUtscCapabDescription 4

  • Get capture capability on a port:

    • snmpr commands: 

      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.1.1.1.<ifIndex> 
docsPnmCmtsObjects.10.1.1.1.<ifIndex> = 00 02 
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.1.1.2.<ifIndex> 
docsPnmCmtsObjects.10.1.1.2.<ifIndex> = 04 
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.1.1.3.<ifIndex> 
docsPnmCmtsObjects.10.1.1.3.<ifIndex> = 1e  
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.1.1.4.<ifIndex> 
docsPnmCmtsObjects.10.1.1.4.<ifIndex> = Center Frequency range and resolution

    • net-snmp commands: 

      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.1.1.1.<ifIndex>
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.1.1.1.<ifIndex> = Hex-STRING: 00 02
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.1.1.2.<ifIndex>
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.1.1.2.<ifIndex> = Hex-STRING: 04
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.1.1.3.<ifIndex>
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.1.1.3.<ifIndex> = Hex-STRING: 1
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.1.1.4.<ifIndex>
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.1.1.4.<ifIndex> = STRING: "Center Frequency range and resolution"

Upstream Triggered Spectrum Capture Bulk Data Control Objects and MIBs

The following Upstream Triggered Spectrum Capture bulk data control objects and MIBs are supported for PNM:

  • PNM Bulk Data Control Objects OID: 1.3.6.1.4.1.4491.2.1.27.1.1.1

  • PNM BULK DATA CONTROL OID: 1.3.6.1.4.1.4491.2.1.27.1.1.1.X

    Where X is the bulk data transfer control parameter.

  • The Bulk Data Transfer (BDT) control objects that are supported are the IPaddress type, BDT server IP and BDT destination path. This indicates to the CCAP the location where the capture results files should be sent through TFTP transfer. In CBR8, the TFTP transfer is done through IOX container and as such, other BDT objects are not relevant to this design model. IP address type can be automatically set by CCAP based on the server IP value specified.

  • The following are the enumerated values for BDT for PNM:

    • docsPnmBulkDestIpAddrType 1

    • docsPnmBulkDestIpAddr 2

    • docsPnmBulkDestPath 3

  • Set the BDT IPv4 IP address type and TFTP IP address

    • snmpr commands: 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 -o 20:01:0d:b8                                          
docsPnmBulkDestIpAddr.0 = 20 01  0d b8
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.1.0                         
docsPnmBulkDestIpAddrType.0 = ipv4(1)
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0                             
docsPnmBulkDestIpAddr.0 = 20 01  0d b8

    • net-snmp commands: 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 x 20010db8
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.2.0 = Hex-STRING: 20 01 0D B8
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.1.0 
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.1.0 = INTEGER: 1 
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.2.0 = Hex-STRING: 20 01 0D B8

  • Set the BDT IPv6 IP address type and TFTP IP address

    • snmpr commands: 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 -o 20:01:0d:b8:85:a3:00:00:00:00:8a:2e:03:70:73:11                                              
docsPnmBulkDestIpAddr.0 = 2001 0db8 85a3 0000 0000 8a2e 0370 7311 
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.1.0 
docsPnmBulkDestIpAddrType.0 = ipv6(2)
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0
docsPnmBulkDestIpAddr.0 = 2001 0db8 85a3 0000 0000 8a2e 0370 7311

    • net-snmp commands: 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 x 20010db885a3000000008a2e03707311
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.2.0 = Hex-STRING: 20 01 0D B8 85 A3 00 00 00 00 8A 2E 03 70 73 11
        server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.1.0 
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.1.0 = INTEGER: 2
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.2.0 = Hex-STRING: 20 01 0D B8 85 A3 00 00 00 00 8A 2E 03 70 73 11

  • Set the BDT destination TFTP path

    • snmpr commands: 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.3.0 -o pnm                   
docsPnmBulkDestPath.0 = pnm
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.3.0                      
docsPnmBulkDestPath.0 = pnm

    • net-snmp commands: 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.3.0 s ‘pnm/test’
SSNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.3.0 = STRING: "pnm/test"
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.3.0 
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.3.0 = STRING: "pnm/test"

Configuring the PNM MAX-HOLD trigger mode

When RPHY is configured for MAX-HOLD PNM mode, RPHY will send PNM data continuously, unless the user issues a stop command or when the duration is reached.

To configure for MAX-HOLD trigger mode on the Supervisor, complete the following steps:

SUMMARY STEPS

  1. Configure the PNM docsPnmCmtsUsSpecAnTrigMode to ‘other’ mode. Both the SNMP and CLI can set the trigger mode. See the following examples:
  2. Set the PNM bulk destination IP address.
  3. Start and stop the capture test.
  4. Enable GCP message support. Send the TFTP server IP address and Static L2tp session ID through TLV58 message, and the TrigMode ‘other’ is send to RPD through TLV41 message.

DETAILED STEPS

  Command or Action Purpose
Step 1

Configure the PNM docsPnmCmtsUsSpecAnTrigMode to ‘other’ mode. Both the SNMP and CLI can set the trigger mode. See the following examples:

  • For SNMP:
    snmpset -v2c -c private 80.4.2.11 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.3.435572.1 i 1
  • For CLI:
    test cable pnm uts configure trigger-mode other

Note that adding a new TrigMode to MIB might take long and cause many specification changes.
Step 2

Set the PNM bulk destination IP address.

  • For SNMP:

     snmpset -v2c -c private 80.4.2.11 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 x "20 01 0d b8"

  • For CLI:

    test cable pnm bdt config set-ip 32.1.13.184
Step 3

Start and stop the capture test.

  • Starting the SNMP:

    snmpset -v2c -c private 80.4.2.11 1.3.6.1.4.1.4491.2.1.27.1.3.10.3.1.1.435572.1 i 1

  • Starting the CLI:

    test cable pnm uts start client-id 1 test-id 1 0004.9f00.0591 0

  • Stopping the SNMP:

    snmpset -v2c -c private 80.4.2.11 1.3.6.1.4.1.4491.2.1.27.1.3.10.3.1.1.435572.1 i 0

  • Stopping the CLI:

    test cable pnm uts stop client-id 1 test-id 1 0004.9f00.0591 0
Step 4

Enable GCP message support. Send the TFTP server IP address and Static L2tp session ID through TLV58 message, and the TrigMode ‘other’ is send to RPD through TLV41 message.

Proactive Network Management MAX-HOLD trigger mode

The cBR enables MAX-HOLD trigger mode support in PNM. The non-CCAP defined MAX-HOLD mode offers significant advantages over the existing FREE-RUN mode that was used earlier. With the MAX-HOLD trigger mode, the RPD sends samples much faster - one sample every 2ms, compared to the earlier rate of one sample per 100ms. The RPD also sends the sample to the server, instead of the Line Card.

The MAX-HOLD trigger mode support functionality includes:

  • cBR support for the configuration of the MAX-HOLD trigger mode

  • cBR support for notify UBUNTU server IP and Static L2tp session IDs to RPD

  • RPD usage of the max hold mode to capture the upstream spectrum

  • RPD sending the captured BIN to UBUNTU server

Debugging the PNM feature on cBR8

cBR supports debugging on Upstream Triggered Spectrum Capture – Proactive Network Management by using the debug commands available for the UTSCOM client on supervisor.

Use the CLI to enable the debug commands:

  • debug cable pnm utscom-error

  • debug cable pnm utscom-debug

Use the following show command to check the state of capture on the Line Card. It lists the total number of samples per capture context in the CLC. When the capture tests are running, the packet counts on the corresponding Line Card would keep incrementing. 

Router# show cable card 6/0 us-triggered-spectrum its-commonLAST event
UTSCOM event    STATUS
client_id      1
test_id        1
port           0
dev            8
phy_chan       0
logi_chan      0
status         4
WBFFT    Dev    trig-mode,    data-ready,    packets on WBFFT dev,    countdown :
wbfft   dev 0:     0                0                     11            0
wbfft   dev 1:     0                0                     0             0
wbfft   dev 2:     0                0                     0             0
wbfft   dev 3:     0                0                     0             0
wbfft   dev 4:     0                0                     0             0
wbfft   dev 5:     0                0                     0             0
wbfft   dev 6:     0                0                     0             0
wbfft   dev 7:     0                0                     0             0
total packets:	11

The dtrack utility can also be used for debugging the packets punted through CPP from CLC to container. To use the dtrack utility, complete the following steps:

  1. On the supervisor, use the following CLI:
    
test platform hardware qfp active feature docsis dtrack mac 0001.aaaa.cccc
test platform hardware qfp active feature docsis dtrack packe
  2. Start the trigger and use the following CLI to dump the packets (this can be very verbose as there are 10 samples per file per second):
    
show platform hardware qfp active feature docsis dtrack statistics verbose

To obtain the dumping statistics on the IOX container, use the following CLI:

  • dir harddisk:/iox/repo-lxc/lxc-data/<CAF id>/logs/

  • more harddisk:/iox/repo-lxc/lxc-data/<CAF id>/logs/.stats

  • more harddisk:/iox/repo-lxc/lxc-data/<CAF id>/logs/pnm.log

To change configuration on the container console, complete the following steps:

  1. Log onto the CAF console as root.

  2. Run the echo "DEBUG" > /data/logs/.loglevel command. 

     debug level are: ERROR, WARNING, INFO, DEBUG, DEBUG1, DEBUG2, DEBUG3, DEBUG4
  3. Run the echo "0" > /data/logs/.resend command.
    
value "0" disable "tftp resend" due to tftp error.
value "12" enable clc log pnm file at local.
Ensure that the PNM TFTP process is active and running on the guestshell container as listed:

cbr8# guestshell run systemctl status pnm
â pnm.service - cbr pnm telemetry delivery system
   Loaded: loaded (/etc/systemd/system/pnm.service; disabled; vendor preset: disabled)
   Active: active (running) since Wed 2019-01-09 15:13:40 UTC; 1min 28s ago

  • If the PNM service is not active, attempt recovery by going through the following steps:

    1. Destroy the guestshell instance. Run the guestshell destroy command.

    2. Recreate the gusetshell by running the guestshell enable command.

    3. Check if the guestshell instance is running by using the show app-hosting list command. Verify that the PNM service is active.

  • Verify that the TFTP server IP is reachable from the guestshell container and ping is successful. 
    guestshell run ping -c5 <tftp_server_ip>

Quick Install Guide - Proactive Network Management

You can bring up the Proactive Network Management and get the captures running using a minimal configuration. Complete the following steps to enable PNM with a minimal configuration:

  1. Find the correct PNM Interface Index for the RPD. Run the show snmp mib ifmib ifindex | include <rpd_mac> command.
    Router# show snmp mib ifmib ifindex | i badb.ad13.2be0
RPD(badb.ad13.2be0)-usport0: Ifindex = 435564

    Where badb.ad13.2be0 is the RPD identifier.

  2. Ensure that the guestshell container is up and running on both active and standby SUP. Run the show app-hosting list command.
    
Router# show app-hosting list
App id                    State
-----------------------------------------------------
guestshell                RUNNING

  3. Ensure that the pnm process is running on the guestshell. Run the guestshell run systemctl status pnm command. For more information on the command usage, go through Step 4.

  4. Configure the Bulk Data Ttransfer parameters. Go through the following steps to set the TFTP IP address and TFTP path. Alternatively, also go through Upstream Triggered Spectrum Capture Bulk Data Control Objects and MIBs for detailed information.

    • Set the BDT IPv4 IP address type and TFTP IP address

      • snmpr commands: 

        • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 -o 20:01:0d:b8                                          
docsPnmBulkDestIpAddr.0 = 20 01  0d b8

      • net-snmp commands: 

        • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 x 20010db8
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.2.0 = Hex-STRING: 20 01 0D B8
        • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.1.0 
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.1.0 = INTEGER: 1 
        • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.2.0 = Hex-STRING: 20 01 0D B8

    • Set the BDT destination TFTP path

      • snmpr commands: 

        • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.1.1.3.0 -o pnm                   
docsPnmBulkDestPath.0 = pnm

      • net-snmp commands: 

        • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.3.0 s ‘pnm/test’
SSNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.3.0 = STRING: "pnm/test"
        • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.1.1.3.0 
SNMPv2-SMI::enterprises.4491.2.1.27.1.1.1.3.0 = STRING: "pnm/test"

  5. Create and configure a capture config entry. Go through the Upstream Triggered Spectrum Capture Control Objects and MIBs for information on creating and configuring a capture config entry.

  6. Set the minimum capture config paramters that are needed (center-frequency, span and duration).

    1. Set the D_docsPnmCmtsUtscCfgStatus_createAndGo 4.
      server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.21.<ifIndex>.1 -i 4 
clabProjDocsis.27.1.3.10.2.1.21.<ifIndex>.1 = 4
    2. Set the docsPnmCmtsUtscCfgCenterFreq.
      server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.8.<ifIndex>.1 –g 102400000 
clabProjDocsis.27.1.3.10.2.1.8.<ifIndex>.1 = 102400000
    3. Set the docsPnmCmtsUtscCfgSpan.
      server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.9.<ifIndex>.1 –g 204800000 
clabProjDocsis.27.1.3.10.2.1.9.<ifIndex>.1 = 204800000
    4. Set the docsPnmCmtsUtscCfgFreeRunDuration. Increase the duration to a large value to keep the freerun capture running.
      server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.19.<ifIndex>.1 -g 5000 
clabProjDocsis.27.1.3.10.2.1.19.<ifIndex>.1 = 5000

    5. Ensure that the config entry status is active.

      server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.21.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.2.1.21.<ifIndex>.1 = INTEGER: 1

    Note

    Ensure that the capture center frequency and span are in a valid range. IOS error messages are triggered if the user attempts to start capture tests with an invalid capture configuration. The recommended configuration values are provided in the messages.

  7. Start the PNM capture.

    • snmpr commands: 

      • server > setany -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1 -i 1 
clabProjDocsis.27.1.3.10.3.1.1.<ifIndex>.1 = 1
      • server > getone -v2c <cmts_ip> <community_name> 1.3.6.1.4.1.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1 
clabProjDocsis.27.1.3.10.3.1.1.<ifIndex>.1 = 1

    • net-snmp commands: 

      • server > snmpset -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1 i 1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1 = INTEGER: 1
      • server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1
SNMPv2-SMI::enterprises.4491.2.1.27.1.3.10.3.1.1.<ifIndex>.1 = INTEGER: 1

  8. The captures are running and files should appear on the TFTP server under the BDT TFTP path configured.

Troubleshooting Upstream Triggered Spectrum Capture – Proactive Network Management Issues

The Upstream Triggered Spectrum Capture – Proactive Network Management issues, their possible causes, and resolution are listed.

  • Capture configuration failure:

    • Ensure that the ifindex that is used is correct and the port is configured correctly under RPD for RPHY.

    • Ensure that the capture configuration entry was created properly and the client/snmp owns the capture port using MIB commands.

    • Ensure that the parameters being configured are supported and within the valid range.

    • Enable debug cable pnm utscom-error to check for any errors.

  • Capture control or initiate test failure:

    • Ensure that the capture configuration is created and configured correctly by the client using MIB commands.

    • Verify that the capture configuration entry status is active using MIB commands.

    • The total number of captures is below the enforced limit.

    • Ensure that no other tests are already running on the port using MIB commands.

    • Ensure that only one port per RPD is running the test.

  • TFTP file transfer failure:

    • Ensure that the BDT TFTP information is configured correctly on the CMTS.

    • Ensure that the TFTP server is reachable and the destination location is writable.

    • Ensure that the container is in running state using show commands.

    • Ensure that the PNM TFTP process is active and running on the guestshell container and the TFTP server IP is reachable from the guestshell container.

    • Ensure that the capture tests are running correctly and with the CLC show, CLI show, files are being generated.

    • Check dtrack to ensure that the punt path is working and packets are being sent to the container.

    • Use the PNM debug and the container statistics/log file to check for any errors.

Feature Information for Upstream Triggered Spectrum Capture – Proactive Network Management

Use Cisco Feature Navigator to find information about the platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to the www.cisco.com/go/cfn link. An account on the Cisco.com page is not required.


Note

The following table lists the software release in which a given feature is introduced. Unless noted otherwise, subsequent releases of that software release train also support that feature.

Table 3. Feature Information for Upstream Triggered Spectrum Capture - Proactive Network Management

Feature Name

Releases

Feature Information

DOCSIS 3.1 Upstream Triggered Spectrum Capture – Proactive Network Management

Cisco IOS XE Gibraltar 16.10.1

This feature was integrated into Cisco IOS XE Gibraltar 16.10.1 on the Cisco cBR Series Converged Broadband Routers.

Proactive Network Management MAX-HOLD trigger mode

Cisco IOS XE Gibraltar 16.10.1d

This feature was integrated into Cisco IOS XE Gibraltar 16.10.1d on the Cisco cBR Series Converged Broadband Routers.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

Related Cisco Community Discussions

About Us
Contact Us
Work with Us