The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
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.
Fast Fourier Transform
Table 2. Feature History
Feature Name
Release Information
Feature Description
Fast Fourier Transform (FFT) Enhancements
Cisco IOS XE Dublin 17.12.1x
In this release, we have optimized legacy periodical FFT for both cBR-8 and RPD which helps in reducing system memory and
CPU resources. Use the cable rpd period-fft [ start | stop ] command to start or stop RPD periodical FFT polling.
In releases before Cisco IOS XE Dublin 17.12.1x, IOSd CLC sends periodical FFT polling requests to CDMAN every 300 milliseconds
for an upstream channel. CDMAN then sends this poll request to RPHYMAN and RPHYMAN sends this poll request to RPD. Huge IPC
messages between CDMAN and RPHYMAN, and GCP messages transactions between cBR-8 and RPD consume most of RPHYMAN memory and
CPU resources. In a large-scale environment, RPDs drop offline during LCHA and SUPHA.
To solve the FFT consuming resource issue, we have optimized legacy periodical FFT for both cBR8 and RPD.
cBR-8 send whole FFT configuration for all upstream channel to RPD side at the beginning bulk config and period FFT polling
on IOSd CLC side is removed.
CDMAN inserts the sm-rng interval in each map message for all upstream channels on CLC. After every 1-second interval, RPD reports FFT sample data
to cBR-8, every 1 second for one upstream channel.
When upstream channel state changes, from up to down, or down to up, or when upstream channel mac domain binding state changes,
from bind to unbind, or unbind to bind, RPD is notified about the changes with different TLV operation: WRITE or DELETE.
You can run multiple FFTs by configuring one port on the RPD to run CM MAC FFT while the other port on this RPD and other
RPDs on this line card continue periodical FFT and other types FFT.
Fast Fourier Transform Enhancements
The following changes are implemented in FFT to reduce memory and CPU resource consumption.
The period FFT polling on the IOSd CLC side is removed. cBR-8 send whole FFT configuration for all upstream channels to the
RPD side at the beginning bulk config.
CDMAN inserts the sm-rng interval in each map message for all upstream channels on CLC. After every 1-second interval, RPD reports FFT sample data
to cBR-8, every 1 second for one upstream channel.
When upstream channel state changes, from up to down, or down to up, or when upstream channel mac domain binding state changes,
from bind to unbind, or unbind to bind, RPD is notified about the changes with different TLV operation: WRITE or DELETE.
In previous releases, if any RPD on the line card is running CM MAC FFT, then all other types of FFT are stopped for all RPDs
on this line card. Starting with Cisco IOS XE Dublin 17.12.1x, you can configuring one port on RPD to run CM MAC FFT while
the other port on this RPD and other RPDs on this line card continue periodical FFT and other types FFT.
Priority of Different FFT Types
There are several types of FFT, and they are prioritized in the following order:
CM MAC
One Time FFT Request (CLI and SNMP)
Periodical FFT polling
When CM MAC is running on one upstream controller, one time FFT request and periodical FFT polling on the upstream channel
of this controller is disabled.
When a one-time FFT request is issued, periodical FFT polling on the same upstream channel is disabled. When a one-time FFT
response is received, periodical FFT polling on this upstream channel is enabled again.
CM MAC Affection
As CM MAC has the highest priority, in previous releases, if any RPD on the line card is running CM MAC FFT, then all other
types of FFT are stopped for all RPDs on this line card.
Starting with Cisco IOS XE Dublin 17.12.1x, we can make one port on RPD run CM MAC FFT while the other port on this RPD and
other RPDs on this line card continue periodical FFT and other types FFT.
If multiple RPDs share the same upstream controller, and one RPD is running CM MAC on this controller, then all other RPDs
sharing the same upstream controller must stop periodical FFT and one time FFT on the corresponding port using the same upstream
controller.
router#show cable spectrum-analysis cable 2/0/28 upstream 0 sid 14 devID 0
Spectrum Analysis Measurements for Cable2/0/28: Upstream 0 Sid 14
Device ID: 0
Channel Center Frequency: 11400 kHz
Frequency Span: 6400 kHz
Number of Bins: 257
Bin Spacing: 25.0 kHz
Resolution Bandwidth: 42.750 kHz
Amplitude Data:
Bin 1: -35.00 dBmV
Bin 2: -40.00 dBmV
Bin 3: -32.00 dBmV
Bin 4: -37.00 dBmV
Bin 5: -30.00 dBmV
Bin 6: -38.00 dBmV
Bin 7: -28.00 dBmV
Bin 8: -34.00 dBmV
Bin 9: -27.00 dBmV
Bin 10: -33.00 dBmV
Bin 11: -30.00 dBmV
Bin 12: -26.00 dBmV
Bin 13: -25.00 dBmV
Bin 14: -24.00 dBmV
Bin 15: -22.00 dBmV
Bin 16: -24.00 dBmV
Bin 17: -26.00 dBmV
...........
Bin 249: -33.00 dBmV
Bin 250: -34.00 dBmV
Bin 251: -38.00 dBmV
Bin 252: -43.00 dBmV
Bin 253: -60.00 dBmV
Bin 254: -60.00 dBmV
Bin 255: -60.00 dBmV
Bin 256: -60.00 dBmV
Bin 257: -60.00 dBmV
One Time FFT Command – CM CNR
router#scm c0c6.87ff.cdd0 cnr
Load for five secs: 47%/4%; one minute: 57%; five minutes: 59%
Time source is NTP, 17:33:07.936 CST Fri Nov 17 2023
MAC Address IP Address I/F MAC Prim ExPwr RxPwr cnr
State Sid (dBmV) (dBmV) (dB)
c0c6.87ff.cdd0 116.1.26.204 C1/0/0/U8 w-online(pt) 22 0.0 0.00 > 40
c0c6.87ff.cdd0 116.1.26.204 C1/0/0/U9 w-online(pt) 22 0.0 0.00 > 40
c0c6.87ff.cdd0 116.1.26.204 C1/0/0/U10 w-online(pt) 22 0.0 0.00 > 40
c0c6.87ff.cdd0 116.1.26.204 C1/0/0/U11 w-online(pt) 22 0.0 0.00 > 40
c0c6.87ff.cdd0 116.1.26.204 C1/0/0/U12 w-online(pt) 22 0.0 0.00 > 40
c0c6.87ff.cdd0 116.1.26.204 C1/0/0/U13 w-online(pt) 22 0.0 0.00 3
c0c6.87ff.cdd0 116.1.26.204 C1/0/0/U14 w-online(pt) 22 0.0 0.00 12
c0c6.87ff.cdd0 116.1.26.204 C1/0/0/U15 w-online(pt) 22 0.0 0.00 > 40
Note
In new design, after one time CLI issued, we must wait 1s before sending the FFT request to RPD for each Upstream channel
to make sure what we got is not periodical FFT packet.
So for the following command, for example, this modem has 8 upstream channels, the CLI response waiting time is at least 8s
router#scm c0c6.87ff.cdd0 cnr
Load for five secs: 47%/4%; one minute: 57%; five minutes: 59%
Time source is NTP, 17:33:07.936 CST Fri Nov 17 2023
MAC Address IP Address I/F MAC Prim ExPwr RxPwr cnr
State Sid (dBmV) (dBmV) (dB)
c0c6.87ff.cdd0 116.1.26.204 C1/0/0/U8 w-online(pt) 22 0.0 0.00 > 40
c0c6.87ff.cdd0 116.1.26.204 C1/0/0/U9 w-online(pt) 22 0.0 0.00 > 40
c0c6.87ff.cdd0 116.1.26.204 C1/0/0/U10 w-online(pt) 22 0.0 0.00 > 40
c0c6.87ff.cdd0 116.1.26.204 C1/0/0/U11 w-online(pt) 22 0.0 0.00 > 40
c0c6.87ff.cdd0 116.1.26.204 C1/0/0/U12 w-online(pt) 22 0.0 0.00 > 40
c0c6.87ff.cdd0 116.1.26.204 C1/0/0/U13 w-online(pt) 22 0.0 0.00 3
c0c6.87ff.cdd0 116.1.26.204 C1/0/0/U14 w-online(pt) 22 0.0 0.00 12
c0c6.87ff.cdd0 116.1.26.204 C1/0/0/U15 w-online(pt) 22 0.0 0.00 > 40
In the output line, In Control [02060001] : 0246 ,
02 indicates channel Number, and 46 indicates legacy FFT if 32 means CM MAC.
In the output line, FFT Packet Count [05180004] : 00014A9C
this value indicates the capture count. If it has increased, it indicates it is fine.
Use the following command to check whether CM MAC is running and whether periodical FFT is disabled or not.
RPD#show bcm-register fft configuration 0
* NOTE: CM MAC configuration *
Enable CMMAC : True
SAC Index : 1
Channel Index : 0
Sid : 2
Trigger Cound : 30000
RPD#show bcm-register fft configuration 1
* NOTE: legacy fft db configuration *
Port ID Chan ID Sid Frequency IUC Disable
1 0 8191 11400000 4 N
1 1 8191 17800000 4 N
1 2 8191 24200000 4 N
1 3 8191 30600000 4 N
Information about 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.
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.
Table 3. Feature History
Feature Name
Release Information
Feature Description
KMAN Updates
Cisco IOS XE Dublin 17.12.1y
In this release, the KMAN process is disabled by default for SNMP PNM TFTP. The cable snmp pnm enable command must be configured on cBR-8 for PNM TFTP to work on cBR-8 and enable captures to be sent via TFTP to an external
server.
Kafka support for PNM SNMP/TFTP
Cisco IOS XE Dublin 17.12.1x
In this release, the SNMP PNM TFTP is supported with a new KMAN process on CBR8 and the guestshell configuration is no longer
necessary. Please note that there is no additional configuration needed for kman to work with PNM TFTP in the 17.12.1x release.
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
IPv6 Support for KMAN
Table 4. Feature History
Feature Name
Release Information
Feature Description
IPv6 Support for KMAN
Cisco IOS XE Dublin 17.15.1y
IPv6 Support for KMAN is a feature that enhances the existing KMAN infrastructure to enable:
IPv6 support for KMAN in addition to existing IPv4 support. Configuration of either IPv6 or IPv4 for the cBR-8 Kafka bus is
available.
The operator to use KMAN to override the source address that is used for both IPv4 and/or IPv6.
Information About IPv6 Support for KMAN
KMAN IPv6 Support extends the capabilities of the KMAN process by enabling IPv6 connectivity, crucial for modern networking
environments where IPv6 adoption is increasing. This feature is essential for improved routing, security, and future-proofing
network infrastructures. The enablement of IPv6 support allows Cable Telemetry Kafka messages and PNM TFTP files to be sent
to servers supporting IPv6 network interfaces. It also allows for the configuration of the source address for packets, enhancing
security through ACL configurations and providing flexibility in network management.
Benefits of IPv6 Support for KMAN
Enables IPv6 protocol support for KMAN, which is essential for modern and future-proof networking.
Provides greater flexibility and control over network packet routing and source address configuration.
Enhances security by allowing ACL configurations based on specific source addresses.
Supports both IPv4 and IPv6, ensuring compatibility with existing network setups.
Cable Telemetry Configuration Overview
To enable IPv6 support for Kafka broker:
Use the command: cable telemetry broker <broker-name> bootstrap-servers <bootstrap-string>
Ensure that the bootstrap string includes valid IPv6 addresses.
Sub-mode command to define the Kafka broker "bootstrap.servers" conf option. This string must consist of valid IP addresses,
or IP addresses with port numbers, which are separated by commas. The list is checked and passed to the Kafka Producer during
startup. This string now supports IPv6 addresses in addition to IPv4 addresses. The default value is an empty string.
To set the IPv6 L3 source address:
Use the command: [no] cable kman source ipv6 <ipv6-addr>
Default is disabled, meaning outbound IPv6 packets use the WAN interface IPv6 address unless configured.
The KMAN process on the SUP sources packets for both PNM TFTP and for Kafka event publishing. By default, outbound IPv4 and
IPv6 packets acquire the external WAN interface address as their source address. It may be desirable for operators to control
the L3 source address of packets that are sent from KMAN in order to improve system security via ACLs. KMAN configuration
allows for the configuration of source IPv4 and IPv6 addresses. When optionally configured, KMAN sends outbound packets using
the configured source address.
Configure KMAN IPv6 Source Address
Enable cable telemetry:
Use the command: cable telemetry enable
Set the message publish rate:
Use the command: cable telemetry message us-rxmer publish-rate 1
Use the command: show platform software kman R0 kafka broker ver
Sample Output:
Router#show platform software kman R0 kafka broker ver
Broker: kafka-broker
Bootstrap.Servers : FD26:BA99:AAE:102::2:251
Broker State: UP
Node Name State
----------------------------------------------
1.2.2.251:9092 INIT
FD26:BA99:AAE:102::2:251:9092 UP
Message Status
---------------------------
us-rxmer enabled
Check if the Broker State is UP and the IPv6 address is correctly configured.
Proactive Network Maintenance (PNM) TFTP Support for IPv6 is a feature that enhances the existing PNM infrastructure to enable
IPv6 support for transferring RxMER, AQProbe, and UTSC data files to TFTP servers. This feature allows network administrators
to access upstream information using IPv6, facilitating better management and troubleshooting of network performance issues.
PMA polls the cBR-8 router via SNMP to schedule the PNM data collection via TFTP. The IP address for PNM TFTP can be configured
as an IPv6 address.
PNM TFTP Support for IPv6 utilizes SNMP and TFTP protocols to gather and transfer network data to designated servers, enabling
the collection of proactive maintenance information for network optimization. This feature supports IPv6 addresses, ensuring
compatibility with modern network environments.
Restrictions for PNM TFTP Support for IPv6
Ensure that all network devices support IPv6 addressing.
Configuration of the TFTP server must be accurate to avoid data transfer failures.
Benefits of PNM TFTP Support for IPv6
Enables comprehensive network monitoring by supporting IPv6 address formats.
Facilitates proactive network maintenance with enhanced data collection capabilities.
Supports high availability, ensuring network resilience and uptime.
Provides scalability by allowing multiple TFTP destinations for data storage.
Prerequisites for PNM TFTP Support for IPv6
Ensure the TFTP server is configured and accessible using IPv6.
SNMP must be operational on the network devices involved.
Proper configuration of network devices for dual-stack operation if both IPv4 and IPv6 are used.
Supported Scenarios
PNM TFTP Support for IPv6 can be used in scenarios where network devices need to report maintenance data to a centralized
server using IPv6. This is useful in network environments where IPv6 is the primary protocol and ensure compatibility with
modern network standards.
Configure PNM TFTP Support for IPv6
To enable PNM TFTP Support for IPv6, use the following command:
router(config)#cable snmp pnm enable
To configure the KMAN source IPv6 address, use the following command:
router(config#cable kman source ipv6 IPv6 Address
PNM BDT MIB Overview
Proactive Network Management
Provides measurement and reporting of network conditions.
Detection of plant impairments and interface.
PNM BDT MIB
Supports three different TFTP destination servers IPv4/IPv6.
Each TFTP server details is stored into a BDT table using unique index values (i.e., 1, 2 and 3).
BDT Commands
Create and Go:
snmpset -v2c -c private <IP> 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9.1 i 4
IPv6:
snmpset -v2c -c private <IP> 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.3.1 i 2
TFTP IP:
snmpset -v2c -c private <IP> 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.4.1 x "TFTP IP Address(Ipv6)"
TFTP Path:
snmpset -v2c -c private <IP> 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.6.1 s "tftp://[TFTP IP Address(IPv6]/path"
Proactive Network Management Using Upstream Triggered Spectrum Capture
Cisco cBR-8 supports Upstream Triggered Spectrum Capture (UTSC). The upstream triggered spectrum analysis measurement provides a wideband spectrum analyzer in the CCAP which can be triggered to examine upstream transmissions and underlying noise or interference during a quiet
period.
The Cisco cBR-8 supports the following Upstream Triggered Spectrum Capture objects:
UsTriggeredSpectrumCaptureFile
UsTriggeredSpectrumCaptureCfg
UsTriggeredSpectrumCaptureCtrl
UsTriggeredSpectrumCaptureStatus
UsTriggeredSpectrumCaptureCapabilities
CCAPBulkDataControl
The Cisco cBR-8 router enables you to trigger a spectrum sample capture and perform spectrum-analysis using the FreeRun mode. FreeRun mode
is a continuous-mode with a maximum of 10 samples per second stacked on each capture file).
The CCAP supports one client configuration per port on a line card. Create a capture configuration entry before attempting
to start or stop the capture tests. The interface index key for the UsTriggeredSpectrumCaptureCfg object defines the one capture configuration for the FreeRun trigger mode.
The Cisco cBR-8 supports only one capture per end-user client per port simultaneously. Hence, the CCAP sets the Upstream Triggered Spectrum
Capture configuration index to 1. The Cisco cBR-8 does not support a PNM MIB query for an Upstream Triggered Spectrum Capture configuration index other than 1. The Cisco cBR-8
supports a maximum of eight captures on upstream ports per line card and supports a maximum of 20 captures per cBR-8 router
for both I-CMTS and RPHY.
Table 7. UTSC Support
WBFFT
NBFFT
UTSC Trigger Mode
MAX_HOLD
FREE Run
CM MAC
RPHY
CISCO RPD
Y
Y
Y
VECIMA RPD
Y
Y
I-CTMS
Y
The Cisco cBR-8 does not support the following scenarios:
UsTriggeredSpectrumCaptureResult MIB
Simultaneous captures on adjacent ports on CLC
RPD support captures only one us-port per RPD at a given time.
docsPnmCmtsUtscCfgFilename OID
Note
The UsTriggeredSpectrumCaptureConfiguration MIB is supported. The docsPnmCmtsUtscCfgFilename OID under this MIB is not supported only for UTSC capture mode for PNM.
The PNM IOX container is used for the TFTP transfer of capture files to a user configured destination server.
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. The file also includes data that is 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). This value is a null-terminated string.
For Upstream Triggered Spectrum Capture, this value is the ‘hostname’ of the CMTS.
Proactive Network Management Interface Index
Before you begin
For Upstream Triggered Spectrum Capture(USTC), the Cisco cBR-8 router supports multiple RPDs per line card with multiple US-ports.
However, on RPDs, 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 to be used in MIB objects can be obtained from the show snmp mib ifmib ifindex command on the CMTS. It is slightly different for I-CMTS as compared to RPHY.
Procedure
Step 1
Run this show command to identify the SNMP ifindex value for MIB object.
Router# show snmp mib ifmib ifindex | i Cable6/0/0-upstream0Cable6/0/0-upstream0
Ifindex = 396648
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.
where badb.ad13.2be0 is the RPD identifier.
Step 2
To determine which slot/subslot/port of an ifindex translates to that of RPHY, see the mapping in the running configuration by running this command.
Router# show snmp mib ifmib ifindex | i 435564
RPD(badb.ad13.2be0)-usport0: Ifindex = 435564
Router# show run | b 0053.0013.2be0
identifier 0053.0013.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
where rpd-us 0 upstream-cable 1/0/2 profile 21 is the slot/subslot/port.
Step 3
For I-CMTS, the upstream port that is to be configured for capture run must be configured and bound to a MAC domain. For RPHY,
there is no requirement that the USport be bound to a MD. If it is configured under an RPD as above, it can be configured
for PNM.
On I-CMTS, in order to run tests on an upstream port, for example, upstream-Cable 6/0/0 us-channel 0, it must be bound to some cable mac domain and the ifindex must be determined as shown above using show snmp CLI.
The slot/subslot/port is upstream-cable 1/0/2 profile 21.
Note
Cisco IOS XE Gibraltar 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 for 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 | s RPD
RPD(0053.0013.420c)-usport0: Ifindex = 415080
RPD(0053.0013.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 a new ifIndex for US (if-type 205) and DS (if-type 128) channels when they are configured to RPD. For versions before Cisco IOS XE Gibraltar 16.10.1g, it was required to create a new ifIndex (>41k) for US (if-type 205) and DS (if-type 128) channels when they are configured to RPD:
With the Cisco cBR-8 16.10.1g RPHY ifIndex feature, you do not need to manually populate any extra item in legacy MIBs.
With the Cisco cBR-8 16.10.1g RPHY ifIndex feature, you must reimplement docsRphyRpdIfCoreToRpdMapTable / docsRphyRpdIfRpdToCoreMapTable, not mapping to ifIndex (>41k) for US (if-type 205) and DS (if-type 128). See the following:
The following configuration parameters for Upstream Triggered Spectrum Capture 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).
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 8. 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_docsPnmCmtsUtscCfgCmMacAddr
1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.6
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
Starting from Cisco IOS XE Gibraltar 16.12.1x release, PNM output format ‘timeIQ’ and UTSC trigger mode ‘cmMac’ are supported
in upstream triggered spectrum capture configuration objects.
Below is an example of the SNMP command configuration with PNM output format ‘timeIQ’ and UTSC trigger mode ‘cmMac’.
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.1.1.2.0 x "0B 01 01 0C"
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.1.1.3.0 s "path"
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.21.415084.1 i 6
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.21.415084.1 i 4
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.2.415084.1 i ifindex
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.3.415084.1 i 6
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.6.415084.1 x "CM MAC"
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.8.415084.1 u 16400000
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.9.415084.1 u 6400000
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.10.415084.1 u 1024
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.11.415084.1 u 245
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.13.415084.1 u 10240000
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.14.415084.1 u 25600000
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.15.415084.1 i -200
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.16.415084.1 i 3
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.17.415084.1 i 1
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.18.415084.1 u 25000
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.19.415084.1 u 5000
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.20.415084.1 u 500
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.21.415084.1 i 1
snmpset -v2c -c private 10.74.54.13 1.3.6.1.4.1.4491.2.1.27.1.3.10.3.1.1.415084.1 i 1
The following Upstream Triggered Spectrum Capture configuration MIBs are supported. SNMP walk is supported for all the MIB
objects.
docsPnmCmtsUtscCfgTriggerMode - This attribute indicates which upstream triggered spectrum capture function trigger modes are supported. Only FreeRun is supported.
Starting with Cisco IOS XE Dublin 17.12.1, UTSC supports three trigger modes: FreeRun, Other, and CM-MAC.
The following are the enumerated values for trigger mode for PNM.
D_docsPnmCmtsUsSpecAnTrigMode_other 1
D_docsPnmCmtsUsSpecAnTrigMode_freeRunning 2
D_docsPnmCmtsUsSpecAnTrigMode_sid 4
D_docsPnmCmtsUsSpecAnTrigMode_idleSid 5
D_docsPnmCmtsUsSpecAnTrigMode_minislotNumber 6
D_docsPnmCmtsUsSpecAnTrigMode_cmMac 6
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 the greater of RepeatPeriod and the minimum period that is supported by the CCAP.
From Cisco IOS XE Gibraltar 16.12.1x release, PNM output format ‘timeIQ’ and UTSC trigger mode ‘cmMac’ are supported in upstream triggered spectrum capture configuration objects.
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.
The center frequency and span capture parameters are set to zero as per OSSI specifications on capture configuration entry creation. For freerun trigger mode, you must set these values in the valid range 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. This attribute
provides the actual number of bins, which may be different from the configured number due to implementation effects.
docsPnmCmtsUtscCfgAveraging - This attribute specifies whether the CCAP should 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 that are specified, when the value of the Averaging attribute is nonzero.
docsPnmCmtsUtscCfgCmMacAddr - This attribute specifies the cable modem from which the CCAP captures upstream transmissions. This attribute is used only
when the TriggerMode is CmMac and is ignored otherwise.
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.6.<ifIndex>.1
x “CM-MAC”
server > snmpget -v2c -c <community_name> <cmts_ip> 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.6.<ifIndex>.1
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.
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.
docsPnmCmtsUtscCfgQualifyThrshld - This attribute specifies the threshold that is 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.
docsPnmCmtsUtscCfgWindow - This attribute indicates which of the upstream triggered spectrum capture function window formats are supported by the CCAP. Currently Cisco cBR-8 supports rectangular (default), Blackmann-Harris, and Hann and Hamming formats. The following are the enumerated values for window mode for PNM.
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
Flat-top, Gaussian, 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. CCAP supports time-IQ and fftPower output format. The time-IQ is supported from Cisco IOS XE Gibraltar
16.12.1x. The following are the enumerated values for output format mode for PNM.
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
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 1
Note
Only the fft-pwr and time-IQ output formats are 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.
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. 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.
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.
docsPnmCmtsUtscCfgStatus - This attribute determines the creation, deletion, and change of status of an actual capture configuration entry on any port of 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. No other client can run any tests on the port till the currently
active client ‘destroys’ the configuration entry and thereby releases ownership of that port.
Any tests on a given port that is 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 must
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:
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.
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).
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.
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
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.
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
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
Table 9. Feature History
Feature Name
Release Information
Feature Description
Multiple Bulk Data Transfer support
Cisco IOS XE Dublin 17.12.1
You can now configure multiple BDTs for the following:
For TFTP in CM-MAC and Other trigger modes. PNM BDT (DocsPnmBulkDataTransferCfgTable) MIB extends support from one TFTP server
address to three.
PNM BDT MIB Updates
Cisco IOS XE Dublin 17.12.1
In this release, PNM BDT MIB (docsPnmBulkDataTransferCfg) can support both OFDMA RxMER and UTSC. (UTSC has three trigger modes:
Freerun, other, and CM-MAC.) The docPnmBulkDestIpaddr object (UTSC CM-MAC) is also supported.
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 are sent through TFTP transfer. In CBR8, the
TFTP transfer is done through IOX container and as such, other BDT objects aren’t 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.
Multiple TFTP Servers Support for PNM BDT SNMP Infra
In releases before Cisco IOS XE Cupertino 17.9.1y, only one BDT TFTP destination server per CCAP is supported to store the
captured UTSC or RxMER data, and maximum eight captures on upstream ports per line card and a maximum of 20 captures per CBR8
is supported for both I-CMTS and RPHY. All captured files are stored into the same TFTP server.
Starting with Cisco IOS XE Cupertino 17.9.1y, the new PNM BDT MIB (docsPnmBulkDataTransferCfgTable) support has been added.
It introduces support for multiple TFTP destination servers, and simultaneous capture of both UTSC freerun and RxMER data
and store into different TFTP server locations. PNM captured files can be stored in three different TFTP servers simultaneously.
Each TFTP server detail is stored into BDT table using unique index values (that is, 1, 2 and 3).
Starting with Cisco IOS XE Dublin 17.12.1, PNM Bulk Data Transfer configuration (docsPnmBulkDataTransferCfgTable) MIB extends
support from one TFTP server address to three.
The existing PNM Bulk Data Control Table MIB remains supported with the following changes.
Capture doesn’t start if the destination TFTP IP address and PATH aren’t configured.
For UTSC other mode, the path isn’t required and only IP is required.
Starting with Cisco IOS XE Cupertino 17.9.1y, PNM BulkData Transfer Cfg MIB and the legacy PNM Bulk Data Control MIB, can
be configured and used at the same time.
Starting with Cisco IOS XE Cupertino 17.9.1y, we support legacy BDT table for UTSC other and CM MAC trigger modes. PNM BDT
MIB (docsPnmBulkDataTransferCfgTable) can support OFDMA RxMER and UTSC.
Starting with Cisco IOS XE Dublin 17.12.1, PNM BDT MIB (docsPnmBulkDataTransferCfg) can support both OFDMA RxMER and UTSC.
UTSC has three trigger modes: Freerun, other, and CM-MAC). The docPnmBulkDestIpaddr object (UTSC CM-MAC) is also supported.
The captured UTSC or RxMER data are stored into the same TFTP server or different TFTP servers. This is done based on the
destination index mappings between BDT table and RxMER or UTSC configuration settings. The destination index is configured
as part of the docsPnmCmtsUtscCfgTable for UTSC and docsPnmCmtsUsOfdmaRxMerTable for Rxmer captures and should map to one
of the indices created in the BDT table - docsPnmBulkDataTransferCfgTable. So based on this destination index mapping, captured
data is stored into respective TFTP server locations.
LCs can run captures as long the max limit per LC and per cBR-8 aren’t exceeded but only using one of the three allowed TFTP
servers. That is, there’s no restriction that a server can be mapped to only one utsc capture config at a time, the same server
can be mapped to different type of captures
A BDT table entry may be modified at any given time. However, if there’s a capture running using the BDT entry, the capture
continues to run with the prior TFTP information with which it was started. The updated BDT details take effect only for new
captures which started after that update.
Proactive Network Management
Provides measurement and reporting of network conditions.
Detection of plant impairments and interference.
docPnmBulkDestIpaddr
Note
The docPnmBulkDestIpaddr object (UTSC CM-MAC) is also supported on legacy BDT table.
The docPnmBulkDestIpaddr object exports spectrum capture data by TFTP. The set of docPnmBulkDestIpaddr isn’t a required configuration for initialing capture, but needed for the TFTP. In the R-PHY system, the upstream spectrum
is captured by the RPD. The captured spectrum data is delivered from the RPD to the CCAP Core via SpecMan or PNM pseudowires,
described in [R-UEPI]. Configure L2TPv3 pseudo wire destining to Viavi server, RPD sends the data to RCI server directly.
The existing docPnmBulkDestIpaddr is used configure the L2TP pseudo wire destination.In a case where upstream spectrum data must be captured continuously and
delivered timely to a PNM server, it’s possible for the controlling CCAP Core to create a static pseudowire between the RPD
and the PNM server, thus bypassing the CCAP itself in the data plane. In this case, the PNM server is considered a Traffic
Engine that supports L2TPv3 data plane only but doesn’t support the GCP or the L2TPv3 control plane protocols. There could
be a separate communication path between the PNM server and the CCAP Core to exchange UTSC configuration, control, and status
information.
Basic Infrastructure to Support Multiple TFTP Servers
PNM CCAP Bulk File Transfer Objects
The following are the DataTransferCfg MIB objects that are specified in DOCS-PNM-MIB in CM-SP-CCAP-OSSIv3.1-I23-220216 spec
and these MIB objects is used to support multiple TFTP destination servers to upload the captured UTSC and RxMER data from
cBR-8.
Starting with Cisco IOS XE 17.12.1, docsPnmBulkDataTransferCfgEntry MIB supports PNM CM-MAC, Other, and FreeRun trigger-modes
for multiple destination indices.
Table 10. PNM CCAP Bulk File Transfer Objects
CCAP bulk data control Objects
OID
Supported
docsPnmBulkFileTransfer
1.3.6.1.4.1.4491.2.1.27.1.1.3
Yes
docsPnmBulkDataTransferCfgTable
1.3.6.1.4.1.4491.2.1.27.1.1.3.1
Yes
docsPnmBulkDataTransferCfgEntry
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1
Yes
docsPnmBulkDataTransferCfgDestIndex
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.1
Yes
docsPnmBulkDataTransferCfgDestHostname
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.2
No
docsPnmBulkDataTransferCfgDestHostIpAddrType
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.3
Yes
docsPnmBulkDataTransferCfgDestHostIpAddress
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.4
Yes
docsPnmBulkDataTransferCfgDestPort
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.5
No
docsPnmBulkDataTransferCfgDestBaseUri
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.6
Yes
docsPnmBulkDataTransferCfgProtocol
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.7
No
docsPnmBulkDataTransferCfgLocalStore
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.8
No
docsPnmBulkDataTransferCfgRowStatus
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9
Yes
The destination port and protocol are set to default values which are shown below, it only has read access.
docsPnmBulkDataTransferCfgDestPort = 69 (UDP)
docsPnmBulkDataTransferCfgProtocol = 1 (tftp)
UTSC Config Table Object
The new objects below are added to the existing UTSC Capture config table as mentioned in the spec but the object which is
relevant to DataTransferCfg is supported as shown in the following table.
Table 11. UTSC Config Table Object
UTSC docsPnmCmtsUtscCfgTable Objects
OID
Supported
docsPnmCmtsUtscCfg
1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.22
No
docsPnmCmtsUtscCfgMaxResultsPerFile
1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.23
No
docsPnmCmtsUtscCfgDestinationIndex
1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.24
Yes
Upstream OFDMA RxMER table object
The following new object is added to the existing Upstream OFDMA RxMER table:
Table 12. Upstream OFDMA RxMER table object
docsPnmCmtsUsOfdmaRxMerTable object
OID
Supported
docsPnmCmtsUsOfdmaRxMerDestinationIndex
1.3.6.1.4.1.4491.2.1.27.1.3.7.1.7
Yes
docsPnmBulkDataTransferCfgEntry
1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1
Yes
Starting with Cisco IOS XE Dublin 17.12.1, docsPnmBulkDataTransferCfgEntry MIB supports multiple destination indexes for OFDMA
RxMER.
Legacy PNM Bulk Data Control Objects
The legacy docsPnmBulkCtl objects continue to be supported for all capture types with a Guest shell design.
Table 13. Legacy PNM Bulk Data Control Objects
docsPnmCmtsUsOfdmaRxMerTable object
OID
docsPnmBulkDestIpAddrType
1.3.6.1.4.1.4491.2.1.27.1.1.1.1
docsPnmBulkDestIpAddr
1.3.6.1.4.1.4491.2.1.27.1.1.1.2
docsPnmBulkDestPath
1.3.6.1.4.1.4491.2.1.27.1.1.1.3
docsPnmBulkUploadControl
1.3.6.1.4.1.4491.2.1.27.1.1.1.4
The IP type and upload control are set to default values as shown below, it only has read access.
docsPnmBulkDestIpAddrType is automatically set as the IPV4 (1)/IPV6(2), will be set automatically while configuring ipv4 or ipv6 address.
docsPnmBulkUploadControl is set to default as autoupload (3).
Note
This object only has read-access. You cannot modify the value via the snmpset command.
UTSC/RxMER capture is blocked to start capture if Destination IP address and PATH aren’t configured.
Note
The CM-MAC or OTHER mode capture types aren’t supported with docsPnmBulkDataTransferCfg MIB.
PNM UTSC/RxMER Config Destination Index
The BDT and UTSC/RxMER configs are linked using below destination the docsPnmCmtsUtscCfgDestinationIndex and docsPnmCmtsUsOfdmaRxMerDestinationIndex indices with the default index values as 0xFFFFFFFF.
You must configure this index to one of the valid BDT config indexes. If capture is started with default index value, then
it uses TFTP server details configured using Legacy MIBs. If valid BDT index is mapped, then it uses the TFTP server details
that are configured in that BDT index. Capture can’t be started if the row status of the mapped BDT index isn’t in ACTIVE
state.
BDT MIB table rows are created with unique dest index value to store three different TFTP server details. A maximum of 3
DestIndex are supported and the DestIndex values for can be 1,2, or 3. In cBR-8, the following BDT objects are supported.
BDT table active status is not required for OTHER mode, only a valid IP configuration is necessary.
If the same BDT entry is to be used for both OTHER and freerun/rxmer mode, then the TFTP path must be specified in the correct
format, in the BDT table and BDT entry must be active for freerrun/rxmer, to use this BDT entry.
docsPnmBulkDataTransferCfgDestHostIpAddrType: To set IP types either IPV4 (1) and IPV6 (2)
docsPnmBulkDataTransferCfgDestHostIpAddress: To set IPV4/IPV6 address in hex value. Configure BDT URI in this format - tftp://{tftp_ip}/{tftp_path}.
docsPnmBulkDataTransferCfgDestBaseUri: To set IPV4/IPV6 address and PATH details in TFTP URL format.
docsPnmBulkDataTransferCfgRowStatus: To create or update or delete a row in BDT table.
docsPnmBulkDataTransferCfgProtocol: This object is hardcoded, same for port and supported for read.
Rows can be created with createandgo and createandwait.
If created with “createandgo then one time mandatory configs (ip address and Uri) are configured, and then row is moved to ACTIVE state automatically, else it remains in NOT READY state.
If created with createandwait then one time mandatory configs (ip address and Uri) are configured, and then row is moved to NotInUse state and user must configure the row to ACTIVE state manually.
SUPHA, LCHA, and LCPR
SUPHA - All BDT MIB configs get erased on SUPSO, you must reconfigure the BDT rows with all required details.
LCHA/LCPR - BDT MIB runs in SUP IOSd process so BDT configs remain intact after LCHA/LCPR.
The following is an example of the steps that are required for PNM BDT configuration.
Row: Create a BDT entry.
snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9.1 i 4
IP Type: Set an IP type.
snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.3.1 i 1
IP/IPV6 address: Set IPV4/IPV6 address.
snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.4.1 x C0A8648C
Uri: Set TFTP URL format.
snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.6.1 s tftp://192.168.100.140/pnm1
Note
You must configure both TFTP IP and BDT URI to initiate the UTSC capture.
RPHY#test cable pnm bdt config get-ip
BDT TABLE ip addresses:
The destination index : 1
The assigned IP is type : 1
IPv4: 192.168.100.140
IPv6: ---
BDT V0 TFTP details:
The assigned IP is type: 0
IPv4: ---
IPv6: ---
CHN3-RACK3-RPHY#test cable pnm bdt config get-path
BDT TABLE TFTP path:
Destination Index = 1 : TFTP path is = tftp://192.168.100.140/pnm1
BDT V0 TFTP Path:
oob-auto@oob-auto:/tftpboot/pnm1$ snmpwalk -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.2.1 = ""
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.3.1 = INTEGER: 1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.4.1 = Hex-STRING: C0 A8 64 8C
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.5.1 = Gauge32: 69
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.6.1 = STRING: "tftp://192.168.100.140/pnm1"
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.7.1 = INTEGER: 1
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.8.1 = INTEGER: 0
iso.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9.1 = INTEGER: 1
oob-auto@oob-auto:/tftpboot/pnm1$
To Delete a row:
snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9.1 i 6
PHY#test cable pnm bdt config get-ip
BDT TABLE ip addresses:
BDT V0 TFTP details:
The assigned IP is type: 0
IPv4: ---
IPv6: ---
RPHY#test cable pnm bdt config get-path
BDT TABLE TFTP path:
BDT V0 TFTP Path:
RPHY#
The following example shows PNM BDT dest index mapping to UTSC configs.
UTSC destination index should be set to BDT index before starting the capture. If destination index is not set in UTSC (DocsPnmCmtsUtscCfgEntry),
it uses the legacy PNM Bulk Data objects for getting the TFTP details.
RxMER destination index should be set to BDT index before starting the capture. If not set it uses the legacy TFTP infra.
If destination index is not set in RxMER table (DocsPnmCmtsUsOfdmaRxMerEntry) , it uses the legacy PNM Bulk Data objects for
TFTP purpose.
Before setting BDT index:
RPHY#test cable pnm uts configure show 0 client-id 1 2/0/0
Acquire capcfg for capture entry success, ret: No error
Capture Config params for client 1 on clc 2/0/0
utsc config index 1
BDT TFTP dest index FFFFFFFF
physical channel 0
logical channel 0
snmp ifIndex 490350
trigger-mode freerun
frequency 70000000
span 30000000
bins 4096
window mode blackman-harris
output format fft-pwr
repeat-period 50000
duration 500000
trigger-count 0
capcfg entry status active
minislot count 0
sid 0
timestamp 0
cm-mac 0000.0000.0000
averaging 0
qualify frequency 0
qualify bandwidth 5120000
qualify threshold -100
RPHY#
snmpset -v2c -c pnm 113.113.113.113 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.24.490446.1 u 1
RPHY#test cable pnm uts configure show 0 client-id 1 2/0/0
Acquire capcfg for capture entry success, ret: No error
Capture Config params for client 1 on clc 2/0/0
utsc config index 1
BDT TFTP dest index 1
physical channel 0
logical channel 0
snmp ifIndex 490350
trigger-mode freerun
frequency 70000000
span 30000000
bins 4096
window mode blackman-harris
output format fft-pwr
repeat-period 50000
duration 500000
trigger-count 0
capcfg entry status active
minislot count 0
sid 0
timestamp 0
cm-mac 0000.0000.0000
averaging 0
qualify frequency 0
qualify bandwidth 5120000
qualify threshold -100
RPHY#
Router#scm rpd name shelf-node5
D
MAC Address IP Address I/F MAC Prim RxPwr Timing Num I Dev
State Sid (dBmV) Offset CPE P Class
4800.33ee.dc6e 12.0.1.34 C7/0/9/UB w-online(pt) 1 -0.50 1176 0 N CM
5039.5577.0bbc 12.0.1.42 C7/0/10/U0 online(pt) 1 0.00 866 0 N CM
5039.5577.06e2 12.0.1.43 C7/0/10/U0 online(pt) 2 0.00 867 0 N CM
To verify an upstream ranging class ID of a cable modem, use the show cable modem command with the verbose keyword.
Following is a sample output of the show cable modem verbose command:
Router#show cable modem 4458.2945.2da6 verbose
MAC Address : 4458.2945.2da6
IP Address : 91.7.0.6
IPv6 Address : ---
Dual IP : N
Prim Sid : 1
Host Interface : C9/0/11/UB
RPD ID : 1004.9fb1.0500
MD-DS-SG / MD-US-SG : 1 / 1
MD-CM-SG : 0x15B0101
Primary Wideband Channel ID : 58625 (Wi9/0/5:0)
Primary Downstream : Do9/0/5:3 (RfId : 58627, SC-QAM)
Wideband Capable : Y
DS Tuner Capability : 8
RCP Index : 3
RCP ID : 00 10 00 00 08
Downstream Channel DCID RF Channel : 4 9/0/5:3 (SC-QAM)
Downstream Channel DCID RF Channel : 1 9/0/5:0 (SC-QAM)
Downstream Channel DCID RF Channel : 2 9/0/5:1 (SC-QAM)
Downstream Channel DCID RF Channel : 3 9/0/5:2 (SC-QAM)
Downstream Channel DCID RF Channel : 5 9/0/5:4 (SC-QAM)
Downstream Channel DCID RF Channel : 6 9/0/5:5 (SC-QAM)
Downstream Channel DCID RF Channel : 7 9/0/5:6 (SC-QAM)
Downstream Channel DCID RF Channel : 8 9/0/5:7 (SC-QAM)
UDC Enabled : N
US Frequency Range Capability : Standard (5-42 MHz)
Extended Upstream Transmit Power : 0dB
Multi-Transmit Channel Mode : Y
Max US SC-QAMs Supported : 4
Number of US in UBG : 1
Minimum power load in DRW (dB) : 16.50
Upstream Channel : US0
Device ID : 0
Ranging Status : sta
Upstream SNR (dB) : 38.16
Upstream Data SNR (dB) : 41.55
Received Power (dBmV) : 0.00
Router#show cable modem 4458.2945.2da6
D
MAC Address IP Address I/F MAC Prim RxPwr Timing Num I
State Sid (dBmV) Offset CPE P
4458.2945.2da6 91.7.0.6 C9/0/11/UB w-online(pt) 1 0.00 868 0 N
Configure the upstream channel ifIndex.
To identify the SNMP ifIndex value, execute the following show command:
Router#test cable pnm bdt config get-ip
BDT TABLE ip addresses:
The destination index : 1
The assigned IP is type : 1
IPv4: 20.1.0.33
IPv6: ---
The destination index : 2
The assigned IP is type : 1
IPv4: 10.79.196.143
IPv6: ---
The destination index : 3
The assigned IP is type : 1
IPv4: 20.1.0.33
IPv6: ---
BDT V0 TFTP details:
The assigned IP is type: 1
IPv4: 20.1.0.33
IPv6: ---
Router#test cable pnm uts configure show 0 client-id 1 1004.9fb1.0500 0
Acquire capcfg for capture entry success, ret: No error
Capture Config params for client 1 on clc 9/0/8
utsc config index 1
BDT TFTP dest index 1
physical channel 0
logical channel 502392
snmp ifIndex 513396
trigger-mode cm-mac-add
frequency 16800000
span 6400000
bins 1100
window mode hann
output format fft-pwr
repeat-period 100000
duration 300000
trigger-count 3000
capcfg entry status active
minislot count 0
sid 1
timestamp 0
cm-mac 4458.2945.2da6
averaging 8
qualify frequency 10240000
qualify bandwidth 25600000
qualify threshold -200
Router#test cable pnm uts show
--- PNM UTSC Activity ---
CLC 9/0/8 dev 0 client 1 test 1 in progress
RphyNode-L09#
Verify the spectrum capabilities using the following show command:
Router#show cable card 9/0 us-triggered-spectrum uts-common
Last event
UTSCOM event STATUS
client_id 1
test_id 1
port 8
dev 0
phys_chan 22740992
logi_chan 1
status 3
Port 8 Dev 0 configuration
UTSCOM event START
client_id 1
test_id 1
port 8
dev 0
phys_chan 22740992
logi_chan 1
sac index 1
trigger-mode 6
frequency 16800000
span 6400000
bins 1100
window 3
output 2
repeat-period 100000
duration 300000
trigger-count 3000
qual-center-freq 10240000
qual-bw 25600000
qual-threshld -200
WBFFT Dev port, devId, trig-mode,data-ready, packets on WBFFT dev, countdown:
wbfft dev 0: 8 0 6 1 156 2938
wbfft dev 1: 64 8 0 0 0 0
wbfft dev 2: 64 8 0 0 0 0
wbfft dev 3: 64 8 0 0 0 0
wbfft dev 4: 64 8 0 0 0 0
wbfft dev 5: 64 8 0 0 0 0
wbfft dev 6: 64 8 0 0 0 0
wbfft dev 7: 64 8 0 0 0 0
total packets: 156
Verify the frequency from the running configuration:
Bulk Data Transfer can support three multiple bulkDataTransferCfg MIB, and the index value starts from 1 to 3.
The following is an example of the steps that are required for PNM BDT bulkDataTransferCfg MIB configuration with multiple
destination indexes for the Other trigger mode:
Row: Create a BDT entry.
snmpset -v2c -c private x.x.x.x 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.9.1 i 4
IP Type: Set a Destination IP type.
snmpset -v2c -c private x.x.x.x 1.3.6.1.4.1.4491.2.1.27.1.1.3.1.1.3.1 i 1
Destination IP address: Set the destination IP address.
You must configure both TFTP IP and BDT URI to initiate the UTSC capture.
RPHY#test cable pnm bdt config get-ip
BDT TABLE ip addresses:
The destination index : 1
The assigned IP is type : 1
IPv4: 20.1.0.33
IPv6: ---
The destination index : 2
The assigned IP is type : 1
IPv4: 10.79.196.143
IPv6: ---
The destination index : 3
The assigned IP is type : 1
IPv4: 20.1.0.33
IPv6: ---
BDT V0 TFTP details:
The assigned IP is type: 0
IPv4: ---
IPv6: ---
CHN3-RACK3-RPHY#test cable pnm bdt config get-path
BDT TABLE TFTP path:
Destination Index = 1 : TFTP path is = tftp://20.1.0.33/jiexiao/PNM
Destination Index = 2 : TFTP path is = tftp://10.79.196.143/PNM
Destination Index = 3 : TFTP path is = tftp://20.1.0.33/jiexiao/WBFFT
RPHY#test cable pnm bdt config row-status
BDT TABLE Row status:
Destination Index = 1 : Row status is = 1
Destination Index = 2 : Row status is = 1
Destination Index = 3 : Row status is = 1
High-Split Upstream Spectrum Capture Support
This feature allows 409.6M span to be configured with Upstream Triggered Spectrum Capture “other” mode for cBR-8 routers.
This allows the full spectrum capture range of 0 MHz to 204.8MHz to be supported. Pass through occurs on cBR-8. L2TP packets
go directly to a Viavi RCI Agent.
BCM Chip Limitation:
When sample rate is set as 204.8 MHz, useful span = 204.8 MHz * 80% = 163.84 MHz
When sample rate is set as 409.6 MHz, useful span = 409.6 MHz * 80% = 327.68 MHz
Limitations
Only accepts span greater than 204.8MHz when trigger mode is other.
Any span greater than 204.8MHz is converted to 409.6MHz on the RPD side.
Resolution is 100KHz for span greater than 204.8MHz and bin size is equal to 4096.
Example
Center Frequency = 153.6MHz
Span = 307.2MHZ (adopt to 409.6MHz on RPD)
Reported frequency range [-51.2 MHz to 358.4MHz]
Expected frequency range [0 MHz to 204.8MHz] need to extract from bin data [512, 2560]
Multiple Spectrum Acquisition Circuits on a Single Port
Table 15. Feature History
Feature Name
Release Information
Feature Description
Multiple Spectrum Acquisition Circuits on a single port
Cisco IOS XE Dublin 17.12.1
You can now configure two Spectrum Acquisition Circuits on a single port.
Starting with Cisco IOS XE Dublin 17.12.1, you can configure two spectrum acquisition circuits (MIG-I-4365) on a single port
at the same time and two UTSC configuration entries are supported. Prior to Cisco IOS XE Dublin 17.12.1, only one UTSC configuration
entry was supported. The receiver (Cox) collects TimeIQ and spectrum FFT data for a single port.
cBR-8 reads the spectrum acquisition circuits supported trigger mode from the RPD reported capabilities.
The following are the supported trigger modes that have to be mapped to the spectrum acquisition circuits type:
Other or FreeRun trigger mode for wide band.
CM-MAC trigger mode for narrow band.
Note
When the required spectrum acquisition circuits are in the operation mode, the capture start operation fails.
You cannot configure two FreeRun or other trigger mode on the same RPD.
You cannot configure two CM-MAC trigger mode on the same port.
The receiver (BCM3161) supports multiple spectrum acquisition circuits and has:
Two Narrow band spectrum acquisition circuits—Captures on one delegated upstream port.
One Wide band spectrum acquisition circuits—Captures on one of the two upstream ports.
Configuring Multiple Spectrum Acquisition Circuits on a Single Port
The following example shows how to create two rows for the UTSC configuration:
snmpset -v2c -c private 10.74.59.202 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.21.513439.1 i 4
snmpset -v2c -c private 10.74.59.202 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.21.513439.2 i 4
The SNMP walk is supported for the upstream triggered spectrum capture.
The following is an example of the SNMP walk on the upstream triggered spectrum capture configuration parameter:
For BCM3161, the configuration 1 is for the OTHER trigger mode and configuration 2 is for the CM-MAC trigger mode running
on the same port.
Verifying the Spectrum Acquisition Circuits Configuration
To verify the spectrum acquisition circuits capabilities sent from cBR-8, execute the following show command:
Router#show cable rpd
Load for five secs: 6%/1%; one minute: 7%; five minutes: 8%
Time source is NTP, 18:04:00.099 CST Mon Jul 10 2023
MAC Address IP Address I/F State Role HA Auth Name
0018.48fe.e643 30.85.65.150 Te6/1/5 online Pri Act N/A vecima-rpd
1004.9fb1.1300 30.85.65.152 Te6/1/5 online Pri Act N/A ng13-shelf-node2
! = PTP clock out of phaselock occurred, ^ = Default password in use
Router#show cable rpd 0018.48fe.e643 spectrum-capture-capabilities
Load for five secs: 18%/1%; one minute: 8%; five minutes: 8%
Time source is NTP, 18:04:08.239 CST Mon Jul 10 2023
RPD ID : 0018.48fe.e643
NumSacs : 4
SacIndex : 4
SacDescription : Narrowband spectrum analysis circuit, upstream RF port 1
MaxCaptureSpan : 204800000 Hz
MinimumCaptureFrequency : 0 HzMaximumCaptureFrequency : 85120000 HzSupportedTriggerModes : |freeRunning|miniSlotCount|sid|burstIuc|
SupportedOutputFormats : |timeIQ|fftPower|fftIQ|fftAmplitude|
SupportedWindowFormats : |rectangular|hann|blackmanHarris|hamming|flatTop|gaussian|chebyshev|
SupportsAveraging : Support
SupportedAggregationMethods : None
SupportsSpectrumQualification : Not Support
MaxNumBins : 4096
MinNumBins : 256
MinRepeatPeriod : 100000 us
SupportedTrigChanTypes : |SC-QAM|
PwType : |SpecMan PW|
LowestCapturePort : 1HighestCapturePort : 1
SupportsScanningCapture : Not Support
MinScanningRepeatPeriod : 0 ms
UTSC CM-MAC for Third-Party RPD
Table 16. Feature History
Feature Name
Release Information
Feature Description
UTSC CM-MAC for third-party RPD
Cisco IOS XE Dublin 17.12.1
cBR-8 now supports the suitable spectrum acquisition circuit and sends the related spectrum acquisition circuit index for
the CM-MAC trigger mode. The UTSC CM-MAC works with the Cisco RPD and third-party RPD.
cBR-8 uses a spectrum acquisition circuit for a third-party capture in the CM-MAC mode. The CM-MAC is for NBFFT, and only
uses the SPECMAN session. The capture supports narrow band spectrum for a modem on a used upstream channel.
cBR-8 supports the IQ-FFT data based on the CM-MAC trigger mode on the PNM upstream capture for NBFFT. This process initiates
sampling data on a grant for any SID assigned to CM-MAC. Then the CCAP receives the burst corresponding to the grant to perform
the spectrum analysis capture.
The spectrum acquisition circuit index is selected from the reported capture capabilities list. The capture is triggered between
PNM and UTSC. The high and low bin sessions are removed from the port and the correct PNM or SPECMAN sessions are retained
for each spectrum acquisition circuit entity.
In the CM-MAC trigger mode, a SPECMAN dynamic session per channel per port is established. This session helps to communicate
between the Cisco RPD and the third-party RPD. A specified MAC address defining a SID is triggered. Each available upstream
channel establishes a SPECMAN session by default. For the CM-MAC trigger mode to work, ensure that you add the dynamic PNM
standby sessions setup when the RPD is online.
Note
The CM-MAC trigger mode supports LCHA and SUPHA.
When there are configuration updates to the RPD, the RPD reconnects, and the CM-MAC trigger mode works under the following
conditions:
cBR-8 first checks if it is a CM-MAC trigger mode.
cBR-8 sets up the dynamic PNM session, only after the RPD is online.
Example: Sample Configuration for UTSC CM-MAC for Third-Party RPD
Configure upstream channel ifIndex
snmpset -v2c -c private 20.5.1.49 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.2.415082.1 i 404045
Configure trigger mode CM-MAC
snmpset -v2c -c private 20.5.1.49 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.3.415082.1 i 6
Configure CM-MAC
snmpset -v2c -c private 20.5.1.49 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.6.415082.1 x "48 00 33 ee dd 9e"
Configure center frequency
snmpset -v2c -c private 20.5.1.49 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.8.415082.1 u 16400000
snmpset -v2c -c private 20.5.1.49 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.9.415082.1 u 6400000
Configure bins
snmpset -v2c -c private 20.5.1.49 1.3.6.1.4.1.4491.2.1.27.1.3.10.2.1.10.415082.1 u 4096
Configuring the PNM MAX-HOLD UTSC Other Trigger Mode
When RPHY configuration is for PNM MAX-HOLD UTSC Other trigger mode, RPHY sends PNM data continuously, until the user issues
stop command or the duration is complete.
To configure for MAX-HOLD trigger mode on the Supervisor, complete the following steps:
Procedure
Step 1
Configure the PNM docsPnmCmtsUtseCfgTriggerMode 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
Adding a new TrigMode to MIB might take long and cause many specification changes.
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.
The maximum number of L2TP sessions is increased from 131072 to 262144. The benefit of having more L2TP sessions is that it
enables better support for large-scale RPD deployments.
Note:
System logs are created when the number of sessions get close 262144. Configure the memory chunk siblings threshold 20000 command, to eliminate system logs.
The rate-limit warning is logged when L2TP session number is greater than 262144.
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 uts-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:
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
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:
Log onto the CAF console as root.
Run the echo "DEBUG" > /data/logs/.loglevel command.
value "0" disable "tftp resend" due to tftp error.
value "12" enable clc log pnm file at local.
Quick Install Guide
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:
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
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.
The captures are running and files should appear on the TFTP server under the BDT TFTP path configured.
Proactive Network Management using OFDMA RxMER Probes
Starting with Cisco IOS XE Gibraltar 16.12.1y, cBR-8 routers support Proactive Network Management using OFDMA RxMER Probes.
This feature enables collection and reporting of the OFDMA channel Receive Modulation Error Ratio (RxMER) for every subcarrier.
The DOCSIS 3.1 CMTS and CM support OFDMA RxMER probes. The CM transmits signals over the OFDMA upstream channel to the CMTS.
The signals are received at the upstream PHY, and each subcarrier in the OFDMA channel is evaluated. RxMER is defined as the
ratio of the average power of the ideal QAM constellation to the average error-vector power. The error vector is the difference
between the equalized received probe value and the known correct probe value. If some subcarriers (such as exclusion bands)
cannot be measured by the CMTS, a value of 0xFF will be returned for that subcarrier.
PNM RxMER probes are initiated and controlled through SNMP MIB commands. The DOCS-PNM-MIB specification details the applicable
commands under the docsPnmCmtsUsOfdmaRxMerTable. A single RxMER probe can be started for each OFDMA channel in the system by specifying the target cable modem mac-address.
The following command options are supported for DocsPnmCmtsUsOfdmaRxMerTable:
docsPnmCmtsUsOfdmaRxMerEntry.[ifIndex]
Each row of the DocsPnmCmtsUsOfdmaRxMerTable is uniquely identified by the OFDMA channel ifIndex. You can identify the ifIndex of a particular OFDMA channel by running
the following command:
Router# show snmp mib ifmib ifindex | i Cable1/0/2-upstream7 Cable1/0/2-upstream7: Ifindex = 389839
docsPnmCmtsUsOfdmaRxMerEnable
Set to TRUE to initiate collection of the RxMER data and send to TFTP server. Setting it to FALSE restores the MIB values
to defaults.
docsPnmCmtsUsOfdmaRxMerCmMac
Specifies the mac-address of the CM that performs the RxMER probe.
docsPnmCmtsUsOfdmaRxMerPreEq
You can either set the value to TRUE to perform RxMER probe with Pre-Equalization, or choose to set the value to FALSE to
perform RxMER probe without Pre-Equalization.
Note
We recommend that probing is done with Pre-Equalization, as this will have the CM transmit on each sub-carrier using a gain
that will normalize the signal arriving at the CMTS.
docsPnmCmtsUsOfdmaRxMerNumAvgs
This is in the range of 1-255. Any integer greater than one will generate multiple probes and average the result before sending
it to the TFTP server.
docsPnmCmtsUsOfdmaRxMerMeasStatus
Indicates the status of the probe request [Inactive, Busy, SampleReady, Error]. See the MIB definition for complete details.
Ensure that no modifications are made to other MIB fields for the table entry while the probe is in Busy state.
docsPnmCmtsUsOfdmaRxMerFileName
Displays the name of the file written to the TFTP server. You can choose to leave it blank, and an autogenerated filename
will be used. The filename is read back after the probe is complete and the status is read as SampleReady.
Note
Do note that new file names are not autogenerated for subsequent probes. Hence, ensure that your filename value is cleared
or set to a new value before initiating a subsequent probe. This will avoid the problem of new probe data overwriting information
on the previous probe with the same filename.
docsPnmCmtsUsOfdmaRxMerDestinationIndex
Specifies the multiple destination index added to the existing Upstream OFDMA RxMER.
Use the following command to configure the number of RxMER samples taken and averaged at the end oF an RxMER-poll interval:
You can also configure the same using the ping docsis pnm mac-address num-avgs num-avgs . Here is a sample configuration:
Router#ping docsis pnm 4800.33ef.0cca num-avgs 5
PNM RxMER Probe High Availability
docsPnmCmtsUsOfdmaRxMerTable
SUPHA: In progress operation will need to be restarted by the operator after the switchover. Currently the IOX PNM service
is not available after a SUP-HA event.
LCHA: In progress operation will need to be restarted by the operator after switchover
Note
When restarting the RxMER probe on the Standby Line Card, care should be taken to identify the new ifIndex of the OFMDA channel.
This will be different from the Primary Line Card.
LCPR: Operations that are in progress will be restarted by SUP after the LCPR completion. An internal operation timeout will
restart the RxMER probe after one minute, for a maximum of three attempts. During this time, the RxMER status will remain
as “Busy”.
RxMer Probe Debugging
You can use the following command options to display the status and count of the PNM RxMER jobs.
To display the status of PNM RxMER jobs by ifIndex, use the test cable pnm rxmer show command. See the following usage example:
Router# test cable pnm rxmer show
Job Client ifIndex CM-Mac Status Enable Pre-Eq Num-Avgs Retry
-------------------------------------------------------------------------------------
0 SNMP 389838 0000.0000.0000 INACTIVE N N 1 0
0 SNMP 389839 0000.0000.0000 INACTIVE N N 1 0
0 SNMP 389933 0000.0000.0000 INACTIVE N N 1 0
0 SNMP 389981 0000.0000.0000 INACTIVE N N 1 0
.
.
.
0 SNMP 404239 0000.0000.0000 INACTIVE N N 1 0
0 SNMP 404246 0000.0000.0000 INACTIVE N N 1 0
0 SNMP 404247 0000.0000.0000 INACTIVE N N 1 0
PNM RxMER job count 33
To display the count of all the PNM RxMER jobs by ifIndex, use the test cable pnm rxmer <ifIndex> get all command. See the following example:
Router# test cable pnm rxmer 389838 get all PNM RxMER MIB for ifIndex 389838
Status: INACTIVE
CM-mac: 0000.0000.0000
Enable: False
Pre-Eq: OFF
Num-Avgs: 1
TFTP filename: <default>
When upstream profile management is enabled, the show cable modem <mac> prof-mgmt upstream verbose command can also be used to view the OFDMA RxMER probe data. The values shown should be similar to, but not exactly the same
as the values reported in the TFTP upload file. This is because data was collected using probes at different times.
The RxMER probe data can also be collected and displayed directly on the CBR8 console using the ping docsis pnm <ip-address> upstream <us-chan> ignored command. This command will initiate a RxMER probe to the targeted cable modem upstream OFDMA channel. The ignore option on the command will prevent the RxMER probe results from impacting OFDMA profile management. The RxMER probe data
can then be viewed on the console using the show cable modem <ip-address> prof-mgmt upstream ignored command. For example:
Set to TRUE to initiate measurement of the received power.
Set to FALSE to restore MIB values to defaults.
Example:
./setany -v2c 8.23.1.1 private docsPnmCmtsUsOfdmaRxPwrEnable.389838.000000000001 -i 1
docsPnmCmtsUsOfdmaRxPwrEnable.389838.000000000001 = true(1)
router#show cable modem 0000.0000.0001 pnm us-rxpwr
MAC Address IP Address I/F MAC Num Pre RxPwr TimeStamp
State Avgs Eq (dBmv)
0000.0000.001 9.23.0.14 Ca1/0/0:u6 w-online(pt) 1 Y -0.2 2023-03-02 14:55:52
router#test cable pnm us-rxpwr 488046 cm-mac 0000.0000.0001 get all
PNM US-RxPwr Get Entry for ifIndex 488046, CM 0000.0000.0001
ifIndex: 488046
chid: 6
CM-Mac: 0000.0000.0001
Status: SAMPLE READY (4)
Enable: Disable (2)
Pre-Eq: On (1)
Num-Avgs: 1
Rx Power: -2 (-0.2 dBmv)
Probe Retry Cnt: 0
Probe Configured: Y
Partial-Mode: 0x00 (None)
TimeStamp: 2023-03-02 14:55:52
docsPnmCmtsUsOfdmaRxPwrCmMac: The mac-address of the modem that performs the RxPwr probe.
docsPnmCmtsUsOfdmaRxPwrPreEq
Set TRUE to request modem enable equalizer during probe burst.
The Upstream Controller OFDMA Channel's "equalization-coefficient" must also be enabled (default).
Set FALSE to request modem disable equalizer during probe burst.
Probing with equalizer enabled is preferred as the CM transmits on each sub-carrier using a gain that normalizes the signal
arriving at the CMTS.
Example:
./setany -v2c 8.23.1.1 private docsPnmCmtsUsOfdmaRxPwrPreEq.488046.000000000001 -i 1
docsPnmCmtsUsOfdmaRxPwrPreEq.3488046.000000000001 = true(1)
router#show cable modem 0000.0000.0001 pnm us-rxpwr
MAC Address IP Address I/F MAC Num Pre RxPwr TimeStamp
State Avgs Eq (dBmv)
0000.0000.001 9.23.0.14 Ca1/0/0:u6 w-online(pt) 1 Y --- 0
router#test cable pnm us-rxpwr 488046 cm-mac 0000.0000.0001 get all
PNM US-RxPwr Get Entry for ifIndex 488046, CM 0000.0000.0001
ifIndex: 488046
chid: 6
CM-Mac: 0000.0000.0001
Status: INACTIVE (2)
Enable: Disable (2)
Pre-Eq: On (1)
Num-Avgs: 1
Rx Power: -255 (-25.5 dBmv)
Probe Retry Cnt: 0
Probe Configured: Y
Partial-Mode: 0x00 (None)
TimeStamp: 0
docsPnmCmtsUsOfdmaRxPwrNumAvgs
Range is 1-32. cBR-8 doesn’t support values above 32.
>1 generates multiple probes and average the result reported by docsPnmCmtsUsOfdmaRxPwrOnePtSixPsd
Example:
./setany -v2c 8.23.1.1 private docsPnmCmtsUsOfdmaRxPwrNumAvgs.488046.000000000001 –I 1
docsPnmCmtsUsOfdmaRxPwrNumAvgs.488046.000000000001 = 1
router# show cable modem 0000.0000.0001 pnm us-rxpwr
MAC Address IP Address I/F MAC Num Pre RxPwr TimeStamp
State Avgs Eq (dBmv)
0000.0000.001 9.23.0.14 Ca1/0/0:u6 w-online(pt) 1 N --- 0
router #test cable pnm us-rxpwr 488046 cm-mac 0000.0000.0001 get all
PNM US-RxPwr Get Entry for ifIndex 488046, CM 0000.0000.0001
ifIndex: 488046
chid: 6
CM-Mac: 0000.0000.0001
Status: INACTIVE (2)
Enable: Disable (2)
Pre-Eq: Off (2)
Num-Avgs: 1
Rx Power: -255 (-25.5 dBmv)
Probe Retry Cnt: 0
Probe Configured: Y
Partial-Mode: 0x00 (None)
TimeStamp: 0
docsPnmCmtsUsOfdmaRxPwrOnePtSixPsd: After triggering the measurement via Enable, wait for MeasStatus to return SampleReady and then read this MIB variable to
retrieve the resulting power measurement.
docsPnmCmtsUsOfdmaRxMerMeasStatus: Indicates the status of the requested measurements and result [Inactive, Busy, SampleReady, Error]
PNM RxMER Probe High Availability
SUPHA
MIBs may be temporarily unavailable while newly active SUP completes initialization of non-dataplane subsystems after becoming
active.
SNMP architecture of cBR-8 changes the ifIndex of channels to match the currently active slot.
In Progress operation will need to be restarted by operator after switchover for entry with ifIndex of newly active slot.
Before Switchover:
docsPnmCmtsUsOfdmaRxPwrOnePtSixPsd[488046][STRING: 4800.33ef.3b0a] = INTEGER: -6.0 dB
After Switchover to Secondary:
docsPnmCmtsUsOfdmaRxPwrOnePtSixPsd[485742][STRING: 4800.33ef.3b0a] = INTEGER: -6.0 dB
LCPR
IOSd-CLC and CDMAN LCPR: If measurement is in progress when LCPR is triggered, some measurement samples may be lost and MeasStatus may report “Error”
instead of “SampleReady”. If this occurs, set Enable to TRUE to restart the measurement.
The following is a sample output for the show cable modem pnm us-rxpwr command:
router#show cable modem pnm us-rxpwr
MAC Address IP Address I/F MAC Num Pre RxPwr TimeStamp
State Avgs Eq (dBmv)
4800.33ef.053e 9.38.8.21 Ca1/0/0:u6 w-online(pt) 10 N -5.7 2023-03-02 09:23:55
4800.33ef.053e 9.38.8.21 Ca1/0/0:u7 w-online(pt) 3 N -6.0 2023-03-02 09:24:46
4800.33ef.093a 9.38.8.5 Ca1/0/0:u6 w-online(pt) 32 N -6.0 2023-03-02 09:28:57
4800.33ef.093a 9.38.8.5 Ca1/0/0:u7 w-online(pt) 5 N -6.0 2023-03-02 09:29:48
206a.9454.30ac 9.38.8.34 Ca1/0/2:u6 w-online(pt) 1 N -6.2 2023-03-02 09:32:17
4800.33ef.0d1a 9.38.8.11 Ca9/0/0:u6 w-online(pt) 32 N -6.0 2023-03-02 09:46:33
4800.33ef.0d1a 9.38.8.11 Ca9/0/0:u6 w-online(pt) 32 N -6.0 2023-03-02 09:46:33
4800.33ef.3f12 9.38.8.27 Ca9/0/0:u6/p w-online(pt) 1 N --- 2023-03-02 09:41:30
4800.33ef.3f12 9.38.8.27 Ca9/0/0:u7/p w-online(pt) 7 N -6.0 2023-03-02 09:42:21
4800.33ef.3e86 9.38.8.20 Ca9/0/1:u6 w-online(pt) 2 N -6.0 2023-03-02 09:48:11
4800.33ef.3e86 9.38.8.20 Ca9/0/1:u7 w-online(pt) 1 N -6.0 2023-03-02 09:49:02
4800.33ef.0666 9.38.8.2 Ca9/0/8:u6 w-online(pt) 1 N -6.0 2023-03-02 09:49:53
4800.33ef.0666 9.38.8.2 Ca9/0/8:u7 w-online(pt) 3 N -5.7 2023-03-02 09:50:44
4800.33ef.3f3e 9.38.8.16 Ca9/0/9:u6 w-online(pt) 2 N -6.0 2023-03-02 09:51:3
4800.33ef.3f3e 9.38.8.16 Ca9/0/9:u7 w-online(pt) 32 N -3.0 2023-03-02 09:52:22
The following is a sample output for the test cable pnm us-rxpwr snmp-walk all command:
router#test cable pnm us-rxpwr snmp-walk all
Chan Num Retry Probe Partial
ifIndex ID CM-Mac Status Enable Pre-Eq Avgs RxPwr Cnt Config Timestamp Mode
-----------------------------------------------------------------------------------------------------------------------------------
488046 6 4800.33ef.053e SAMPLE READY N N 10 -57 0 Y 2023-03-02 09:23:55 0x00 (None)
488046 6 4800.33ef.093a SAMPLE READY N N 32 -60 0 Y 2023-03-02 09:28:57 0x00 (None)
488047 7 4800.33ef.053e SAMPLE READY N N 3 -60 0 Y 2023-03-02 09:24:46 0x00 (None)
488047 7 4800.33ef.093a SAMPLE READY N N 5 -60 0 Y 2023-03-02 09:29:48 0x00 (None)
488142 6 206a.9454.30ac SAMPLE READY N N 1 -62 0 Y 2023-03-02 09:32:17 0x00 (None)
501870 6 4800.33ef.0d1a SAMPLE READY N N 32 -60 0 Y 2023-03-02 09:46:33 0x00 (None)
501870 6 4800.33ef.3f12 SAMPLE READY N N 7 -255 0 Y 2023-03-02 09:42:21 0x01 (RNG)
501871 7 4800.33ef.0d1a SAMPLE READY N N 1 -57 0 Y 2023-03-02 09:47:20 0x00 (None)
501871 7 4800.33ef.3f12 SAMPLE READY N N 7 -60 0 Y 2023-03-02 09:42:21 0x01 (RNG)
501918 6 4800.33ef.3e86 SAMPLE READY N N 2 -255 0 Y 2023-03-02 09:48:11 0x00 (None)
501919 7 4800.33ef.3e86 SAMPLE READY N N 1 -60 0 Y 2023-03-02 09:49:02 0x00 (None)
502254 6 4800.33ef.0666 SAMPLE READY N N 1 -60 0 Y 2023-03-02 09:49:53 0x00 (None)
502255 7 4800.33ef.0666 SAMPLE READY N N 3 -57 0 Y 2023-03-02 09:50:44 0x00 (None)
502302 6 4800.33ef.3f3e SAMPLE READY N N 2 -60 0 Y 2023-03-02 09:51:32 0x00 (None)
502303 7 4800.33ef.3f3e SAMPLE READY N N 32 -30 0 Y 2023-03-02 09:52:22 0x00 (None)
The following scenarios indicate the Proactive Network Management upstream channel RxPwr clear and show commands:
Clearing Modem on PNM Upstream Channel RxPwr
To clear all the PNM upstream channel RxPwr information for cable modems, use the following clear cable modem pnm us-rxpwr command in the privileged EXEC mode.
router#clear cable modem pnm us-rxpwr
The following is a sample output for the show cable modem pnm us-rxpwr command:
router#show cable modem pnm ?
us-rxpwr PNM US RxPwr (1.6 MHz normalized) from docsPnmCmtsUsOfdmaRxPwrTable
router#show cable modem pnm us-rxpwr
MAC Address IP Address I/F MAC Num Pre RxPwr TimeStamp
State Avgs Eq (dBmv)
4800.33ef.3c52 9.14.0.11 Ca1/0/0:u6 w-online(pt) 1 Y 0.0 2023-09-02 10:38:14
4800.33ef.3c52 9.14.0.11 Ca1/0/0:u7 w-online(pt) 2 Y 0.7 2023-09-02 10:38:14
4800.33ef.3a72 9.14.0.45 Ca1/0/0:u6 w-online(pt) 1 Y 0.0 2023-09-02 10:40:26
4800.33ef.3a72 9.14.0.45 Ca1/0/0:u7 w-online(pt) 2 Y 0.0 2023-09-02 10:40:26
4800.33ef.3a12 9.14.0.56 Ca1/0/0:u6 w-online(pt) 1 Y 0.0 2023-09-02 10:39:31
4800.33ef.3a12 9.14.0.56 Ca1/0/0:u7 w-online(pt) 2 Y 0.0 2023-09-02 10:39:31
4800.33ef.39ce 9.14.0.51 Ca1/0/0:u6 w-online(pt) 1 Y 0.2 2023-09-02 10:40:27
4800.33ef.39ce 9.14.0.51 Ca1/0/0:u7 w-online(pt) 2 Y 0.2 2023-09-02 10:40:27
4800.33ef.3a92 9.14.0.60 Ca1/0/0:u6 w-online(pt) 1 Y 0.2 2023-09-02 10:40:28
4800.33ef.3a92 9.14.0.60 Ca1/0/0:u7 w-online(pt) 2 Y 0.2 2023-09-02 10:40:28
4800.33ef.0baa 9.14.0.72 Ca1/0/0:u6 w-online(pt) 1 Y 0.5 2023-09-02 10:38:14
4800.33ef.0baa 9.14.0.72 Ca1/0/0:u7 w-online(pt) 2 Y -0.2 2023-09-02 10:38:14
4800.33ef.3aa2 9.14.0.55 Ca1/0/0:u6 w-online(pt) 1 Y 0.2 2023-09-02 10:38:20
4800.33ef.3aa2 9.14.0.55 Ca1/0/0:u7 w-online(pt) 2 Y 0.2 2023-09-02 10:38:20
4800.33ee.f732 9.14.0.73 Ca1/0/0:u6 w-online(pt) 1 Y 0.0 2023-09-02 10:38:13
4800.33ee.f732 9.14.0.73 Ca1/0/0:u7 w-online(pt) 2 Y 0.0 2023-09-02 10:38:13
4800.33ef.060a 9.14.0.70 Ca1/0/0:u6 w-online(pt) 1 Y 1.0 2023-09-03 08:57:41
4800.33ef.060a 9.14.0.70 Ca1/0/0:u7 w-online(pt) 8 Y 0.2 2023-09-02 10:38:13
0cb9.37d8.00c4 9.14.0.36 Ca1/0/0:u6 w-online(pt) 1 Y -t- 2023-09-02 10:40:29
0cb9.37d8.00c4 9.14.0.36 Ca1/0/0:u7 w-online(pt) 3 Y -t- 2023-09-02 10:40:29
4800.33ef.38ae 9.14.0.66 Ca1/0/0:u6 w-online(pt) 1 Y 0.2 2023-09-02 10:39:30
4800.33ef.38ae 9.14.0.66 Ca1/0/0:u7 w-online(pt) 2 Y 0.2 2023-09-02 10:39:30
4800.33ef.394e 9.14.0.44 Ca1/0/0:u6 w-online(pt) 1 Y 0.0 2023-09-02 10:40:25
4800.33ef.394e 9.14.0.44 Ca1/0/0:u7 w-online(pt) 2 Y 0.0 2023-09-02 10:40:25
4800.33ef.3a9a 9.14.0.35 Ca1/0/0:u6 w-online(pt) 1 Y 0.0 2023-09-02 10:39:37
4800.33ef.3a9a 9.14.0.35 Ca1/0/0:u7 w-online(pt) 2 Y 0.0 2023-09-02 10:39:37
4800.33ef.38c2 9.14.0.38 Ca1/0/0:u6 w-online(pt) 1 Y 0.2 2023-09-02 10:39:41
4800.33ef.38c2 9.14.0.38 Ca1/0/0:u7 w-online(pt) 2 Y 0.2 2023-09-02 10:39:41
4800.33ef.3a82 9.14.0.54 Ca1/0/0:u6 w-online(pt) 1 Y 0.2 2023-09-02 10:39:41
4800.33ef.3a82 9.14.0.54 Ca1/0/0:u7 w-online(pt) 2 Y 0.0 2023-09-02 10:39:41
4800.33ef.3972 9.14.0.53 Ca1/0/0:u6 w-online(pt) 1 Y 0.2 2023-09-02 10:38:24
4800.33ef.3972 9.14.0.53 Ca1/0/0:u7 w-online(pt) 2 Y 0.0 2023-09-02 10:38:24
d4b9.2f6e.f4b8 9.14.0.75 Ca1/0/1:u6 w-online(pt) 2 Y 0.2 2023-09-02 10:40:30
d4b9.2f6e.f4b8 9.14.0.75 Ca1/0/1:u7 w-online(pt) 3 Y 0.2 2023-09-02 10:40:30
4800.33ef.06ca 9.14.0.71 Ca1/0/1:u6 w-online(pt) 2 Y 0.0 2023-09-02 10:40:31
4800.33ef.06ca 9.14.0.71 Ca1/0/1:u7 w-online(pt) 3 Y 0.2 2023-09-02 10:40:31
4800.33ea.716a 9.14.0.74 Ca1/0/1:u6 w-online(pt) 2 Y 0.0 2023-09-02 10:40:30
4800.33ea.716a 9.14.0.74 Ca1/0/1:u7 w-online(pt) 3 Y 0.0 2023-09-02 10:40:30
4800.33ef.0ac2 9.14.0.34 Ca1/0/1:u6 w-online(pt) 2 Y -0.2 2023-09-02 10:40:31
4800.33ef.0ac2 9.14.0.34 Ca1/0/1:u7 w-online(pt) 3 Y 0.0 2023-09-02 10:40:31
i = probe inactive
n = very low power or no energy
q = equalization coefficent config mismatch with probe pre-equalization setting
t = probe response timeout condition, no probe response received
x = probe not sent
Clearing Modem on PNM Upstream Channel RxPwr on a Specific OFDMA channel
To clear all the PNM upstream channel RxPwr information for cable modems on a specific OFDMA channel, use the following clear cable modem pnm us-rxpwr command in the privileged EXEC mode.
Clearing Modem on PNM Upstream Channel RxPwr on a Specific Cable Interface
To clear all the PNM upstream channel RxPwr information for cable modems on a specific cable interface on a specific OFDMA
channel, use the following clear cable modem pnm us-rxpwr Cable command in the privileged EXEC mode.
router#show cable modem C1/0/0 pnm us-rxpwr
MAC Address IP Address I/F MAC Num Pre RxPwr TimeStamp
State Avgs Eq (dBmv)
4800.33ef.3c52 9.14.0.11 Ca1/0/0:u6 w-online(pt) 1 Y 0.0 2023-09-02 10:38:14
4800.33ef.3c52 9.14.0.11 Ca1/0/0:u7 w-online(pt) 2 Y 0.7 2023-09-02 10:38:14
4800.33ef.3a72 9.14.0.45 Ca1/0/0:u6 w-online(pt) 1 Y 0.0 2023-09-02 10:40:26
4800.33ef.3a72 9.14.0.45 Ca1/0/0:u7 w-online(pt) 2 Y 0.0 2023-09-02 10:40:26
4800.33ef.3a12 9.14.0.56 Ca1/0/0:u6 w-online(pt) 1 Y 0.0 2023-09-02 10:39:31
4800.33ef.3a12 9.14.0.56 Ca1/0/0:u7 w-online(pt) 2 Y 0.0 2023-09-02 10:39:31
4800.33ef.39ce 9.14.0.51 Ca1/0/0:u6 w-online(pt) 1 Y 0.2 2023-09-02 10:40:27
4800.33ef.39ce 9.14.0.51 Ca1/0/0:u7 w-online(pt) 2 Y 0.2 2023-09-02 10:40:27
4800.33ef.3a92 9.14.0.60 Ca1/0/0:u6 w-online(pt) 1 Y 0.2 2023-09-02 10:40:28
4800.33ef.3a92 9.14.0.60 Ca1/0/0:u7 w-online(pt) 2 Y 0.2 2023-09-02 10:40:28
4800.33ef.0baa 9.14.0.72 Ca1/0/0:u6 w-online(pt) 1 Y 0.5 2023-09-02 10:38:14
4800.33ef.0baa 9.14.0.72 Ca1/0/0:u7 w-online(pt) 2 Y -0.2 2023-09-02 10:38:14
4800.33ef.3aa2 9.14.0.55 Ca1/0/0:u6 w-online(pt) 1 Y 0.2 2023-09-02 10:38:20
4800.33ef.3aa2 9.14.0.55 Ca1/0/0:u7 w-online(pt) 2 Y 0.2 2023-09-02 10:38:20
4800.33ee.f732 9.14.0.73 Ca1/0/0:u6 w-online(pt) 1 Y 0.0 2023-09-02 10:38:13
4800.33ee.f732 9.14.0.73 Ca1/0/0:u7 w-online(pt) 2 Y 0.0 2023-09-02 10:38:13
4800.33ef.060a 9.14.0.70 Ca1/0/0:u6 w-online(pt) 1 Y 1.0 2023-09-03 08:57:41
4800.33ef.060a 9.14.0.70 Ca1/0/0:u7 w-online(pt) 8 Y 0.2 2023-09-02 10:38:13
0cb9.37d8.00c4 9.14.0.36 Ca1/0/0:u6 w-online(pt) 1 Y -t- 2023-09-02 10:40:29
0cb9.37d8.00c4 9.14.0.36 Ca1/0/0:u7 w-online(pt) 3 Y -t- 2023-09-02 10:40:29
4800.33ef.38ae 9.14.0.66 Ca1/0/0:u6 w-online(pt) 1 Y 0.2 2023-09-02 10:39:30
4800.33ef.38ae 9.14.0.66 Ca1/0/0:u7 w-online(pt) 2 Y 0.2 2023-09-02 10:39:30
4800.33ef.394e 9.14.0.44 Ca1/0/0:u6 w-online(pt) 1 Y 0.0 2023-09-02 10:40:25
4800.33ef.394e 9.14.0.44 Ca1/0/0:u7 w-online(pt) 2 Y 0.0 2023-09-02 10:40:25
4800.33ef.3a9a 9.14.0.35 Ca1/0/0:u6 w-online(pt) 1 Y 0.0 2023-09-02 10:39:37
4800.33ef.3a9a 9.14.0.35 Ca1/0/0:u7 w-online(pt) 2 Y 0.0 2023-09-02 10:39:37
4800.33ef.38c2 9.14.0.38 Ca1/0/0:u6 w-online(pt) 1 Y 0.2 2023-09-02 10:39:41
4800.33ef.38c2 9.14.0.38 Ca1/0/0:u7 w-online(pt) 2 Y 0.2 2023-09-02 10:39:41
4800.33ef.3a82 9.14.0.54 Ca1/0/0:u6 w-online(pt) 1 Y 0.2 2023-09-02 10:39:41
4800.33ef.3a82 9.14.0.54 Ca1/0/0:u7 w-online(pt) 2 Y 0.0 2023-09-02 10:39:41
4800.33ef.3972 9.14.0.53 Ca1/0/0:u6 w-online(pt) 1 Y 0.2 2023-09-02 10:38:24
4800.33ef.3972 9.14.0.53 Ca1/0/0:u7 w-online(pt) 2 Y 0.0 2023-09-02 10:38:24
i = probe inactive
n = very low power or no energy
q = equalization coefficent config mismatch with probe pre-equalization setting
t = probe response timeout condition, no probe response received
x = probe not sent
State Avgs Eq (dBmv)
Clearing Modem on PNM Upstream Channel RxPwr on a Specific Cable Modem
To clear the PNM upstream channel RxPwr information for a specific cable modem, use the following clear cable modem pnm us-rxpwr [H.H.H or A.B.C.D] upstream command in the privileged EXEC mode.
Where [H.H.H] is a specific modem's unique MAC address and [A.B.C.D] is a specific modem's assigned IP address.
router#show cable modem 4800.33ef.060a pnm us-rxpwr
MAC Address IP Address I/F MAC Num Pre RxPwr TimeStamp
State Avgs Eq (dBmv)
4800.33ef.060a 9.14.0.70 Ca1/0/0:u6 w-online(pt) 1 Y 1.0 2023-09-03 08:57:41
4800.33ef.060a 9.14.0.70 Ca1/0/0:u7 w-online(pt) 8 Y 0.2 2023-09-02 10:38:13
i = probe inactive
n = very low power or no energy
q = equalization coefficent config mismatch with probe pre-equalization setting
t = probe response timeout condition, no probe response received
x = probe not sent
Clearing Modem on PNM Upstream Channel RxPwr on a Specific Cable Modem on a Specific Upstream Channel OFDMA Channel
To clear the PNM upstream channel RxPwr information for a specific cable modem on a specific upstream channel OFDMA channel,
use the following clear cable modem pnm us-rxpwr [H.H.H or A.B.C.D] command in privileged EXEC mode.
Where [H.H.H] is a specific modem's unique MAC address and [A.B.C.D] is a specific modem's assigned IP address.
Verifying the Proactive Network Management Using OFDMA RxPwr Probes
You can verify the Proactive Network Management using OFDMA RxPwr Probes under the following scenarios:
Verifying the PNM using Specific Status Reason Codes
The following example shows the PNM RxPwr Probe to the modem 0cb9.37d8.00c4 failure due to a -t- timeout because the modem did not respond to the PNM RxPwr Probe.
router#scm 0cb9.37d8.00c4 pnm us
router#show cable modem 0cb9.37d8.00c4 pnm us-rxpwr
MAC Address IP Address I/F MAC Num Pre RxPwr TimeStamp
State Avgs Eq (dBmv)
0cb9.37d8.00c4 9.14.0.36 Ca1/0/0:u6 w-online(pt) 1 Y -t- 2023-09-02 10:40:29
0cb9.37d8.00c4 9.14.0.36 Ca1/0/0:u7 w-online(pt) 3 Y -t- 2023-09-02 10:40:29
where,
i—indicates that the probe is inactive
n—very low power or no energy
q—equalization coefficient configuration mismatch with probe pre-equalization setting
t—probe response timeout condition, no probe response received
x—probe not sent
Verifying the PNM using Upstream Channel Partial-Service Mode (RNG)
If the OFDMA upstream channel of a modem is in a partial-service condition due to RNG mode, then the PNM RxPwr Probes are
not sent to the modem and will be dropped on the iCMTS.
The I/F column indicates the upstream channel partial-service condition with a /p following the interface name string. And, the RxPwr column has the specific status reason code -x- indicating the PNM RxPwr probe request was dropped. There is a possibility that the OFDMA upstream channel entered the partial-service
condition after the PNM RxPwr Probe was received from the modem. In this case, the I/F column indicates the upstream channel partial-service condition with a /p following the interface name string. And, the RxPwr column has the specific status reason code -i- to indicate the PNM RxPwr Probe is in the inactive state.
The following example shows the PNM RxPwr Probe to the OFDMA upstream channel in a partial-service condition state due to
RNG mode and denotes -t- indicating the PNM RxPwr Probe in inactive state and /p the interface name string and -x indicating the probe request dropped.
router#show cable modem 4800.33ef.060a pnm us-rxpwr
MAC Address IP Address I/F MAC Num Pre RxPwr TimeStamp
State Avgs Eq (dBmv)
4800.33ef.060a 9.14.0.70 Ca1/0/0:u6 /p w-online(pt) 1 Y -x- 2023-09-02 10:41:12
4800.33ef.060a 9.14.0.70 Ca1/0/0:u7 w-online(pt) 8 Y 0.2 2023-09-02 10:38:13
router#show cable modem 4800.33ef.060a pnm us-rxpwr
MAC Address IP Address I/F MAC Num Pre RxPwr TimeStamp
State Avgs Eq (dBmv)
4800.33ef.060a 9.14.0.70 Ca1/0/0:u6 /p w-online(pt) 1 Y -i- 2023-09-02 10:44:02
4800.33ef.060a 9.14.0.70 Ca1/0/0:u7 w-online(pt) 8 Y 0.2 2023-09-02 10:38:13
Verifying the PNM using Equalization Coefficient Configuration Mismatch
If there is a mismatch between the PNM RxPwr Probe DocsPnmCmtsOfdmaRxPwrEntry's docsPnmCmtsOfdmaRxPwrPreEq (Pre-Equalization) setting and the iCMTS's Upstream Controller configuration or the RPHY's Upstream Controller Profile configuration
of the OFDMA channel's equalization-coefficient, then the RxPwr column has the specific status reason code -q- to indicate the PNM RxPwr Probe equalization coefficient configuration mismatch case.
The following example shows the OFDMA channel's equalization-coefficient denoting -q- indicating the PNM RxPwr Probe equalization coefficient configuration mismatch case.
router#show cable modem 4800.33ef.060a pnm us-rxpwr
MAC Address IP Address I/F MAC Num Pre RxPwr TimeStamp
State Avgs Eq (dBmv)
4800.33ef.060a 9.14.0.70 Ca1/0/0:u6 w-online(pt) 1 Y -q- 2023-09-03 08:46:20
4800.33ef.060a 9.14.0.70 Ca1/0/0:u7 w-online(pt) 8 Y 0.2 2023-09-02 10:38:13
Verifying the Probe Timeout
If a PNM RxPwr Probe request to a specific modem on a specific OFDMA upstream channel is not answered by the modem within
60 seconds, then the RxPwr column has the specific status reason code -t- to indicate that the PNM RxPwr Probe response timeout condition, no probe response received case. During the time period
that the iCMTS waits for the modem's PNM RxPwr response, the RxPwr column has the specific status reason code --- to indicate that the PNM RxPwr Probe is in a Busy condition case.
The following example shows the OFDMA channel's equalization-coefficient denoting the PNM RxPwr Probe Busy condition case:
router#show cable modem 4800.33ef.060a pnm us-rxpwr
MAC Address IP Address I/F MAC Num Pre RxPwr TimeStamp
State Avgs Eq (dBmv)
4800.33ef.060a 9.14.0.70 Ca1/0/0:u6 w-online(pt) 1 Y --- 2023-09-02 21:56:05
4800.33ef.060a 9.14.0.70 Ca1/0/0:u7 w-online(pt) 8 Y 0.2 2023-09-02 10:38:13
Eventually, the sample output displays the timeout condition:
router#show cable modem 4800.33ef.060a pnm us-rxpwr
MAC Address IP Address I/F MAC Num Pre RxPwr TimeStamp
State Avgs Eq (dBmv)
4800.33ef.060a 9.14.0.70 Ca1/0/0:u6 w-online(pt) 1 Y -t- 2023-09-02 21:56:05
4800.33ef.060a 9.14.0.70 Ca1/0/0:u7 w-online(pt) 8 Y 0.2 2023-09-02 10:38:13
The Upstream Triggered Spectrum Capture 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 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 Proactive Network Management
The following table provides release information about the feature or features described in this module. This table lists
only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise,
subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco
Feature Navigator, go to https://cfnng.cisco.com/. An account on Cisco.com is not required.
Table 19. Feature Information for Upstream Triggered Spectrum Capture - Proactive Network Management
Feature Name
Releases
Feature Information
DOCSIS 3.1 Upstream Triggered Spectrum Capture
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.
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.
Support PNM output format ‘timeIQ’ and UTSC trigger mode ‘cmMac’
Cisco IOS XE Gibraltar 16.12.1x
This feature was integrated into Cisco IOS XE Gibraltar 16.12.1x on the Cisco cBR Series Converged Broadband Routers.
Proactive Network Management using OFDMA RxMER Probes
Cisco IOS XE Gibraltar 16.12.1y
This feature was integrated into Cisco IOS XE Gibraltar 16.12.1y on the Cisco cBR Series Converged Broadband Routers.
Feedback