CMTS RF Config GD CMD Reference R7.2.4!03!15 2017

RF Cable Configuration Guide
and Command Reference
For Casa Software Releases to 7.2.4
DOC-3022-01
Document Revision 07.02.04a
March 2017
© 2017 Casa Systems, Inc.
All rights reserved. Licensed software products are owned by Casa Systems or its suppliers and are protected
by United States copyright laws and international treaty provisions.
The information regarding the product in this manual is subject to change without notice. All statements,
information, and recommendations in this manual are believed to be accurate but are presented without
warranty of any kind, express of implied. Users must take full responsibility for their application of the product.
In no event shall Casa or its suppliers be liable for any indirect, special, consequential, or incidental damages,
including, without limitation, lost profits or loss or damage to data arising out of the use or inability to use this
manual, even if Casa or its suppliers have been advised of the possibility of such damages.
iii
Contents
Preface
Chapter 1. RF cable operations overview

About this chapter ............................................................................................. 1-1 .
CMTS installation in the network topology ........................................................ 1-2 .
Cable modem initialization and learning ........................................................... 1-5 .
Cable modem initial ranging and registration .................................................... 1-6 .
Cable modem provisioning and configuration ................................................... 1-7 .
Cable modem power considerations ................................................................. 1-7 .
Upstream channel descriptors and MAPs ......................................................... 1-9 .
UCD and MAP operations ................................................................................. 1-9 .
Channel bonding and service group operations ............................................. 1-12 .
Physical fiber node vs. DOCSIS terminology .................................................. 1-13 .
Load balancing CMTS traffic ........................................................................... 1-13 .
Terminology covered in this chapter ............................................................... 1-17 .
Configuration examples .................................................................................. 1-22 .
Chapter 2. Application classes and policies

Application class and policy commands description ......................................... 2-1 .
application ................................................................................................... 2-2.
class ...................................................................................................... 2-3

.
policy ................................................................................................... 2-12.
Casa Systems
iv RF Cable Configuration Guide and Command Reference
Contents
Chapter 3. Baseline Privacy Interface

BPI commands description ............................................................................... 3-1 .
cable privacy ............................................................................................... 3-3.
cable sa-des-tlvlen-2 ................................................................................. 3-10 .
privacy hotlist ............................................................................................ 3-11.
shared-secondary-secret .......................................................................... 3-12 .
shared-secret ............................................................................................ 3-13 .
Chapter 4. Cable commands

Cable commands description ............................................................................ 4-1 .
cable admission-control .............................................................................. 4-5 .
cable arp fast-timeout ................................................................................. 4-8 .
cable arp filter ............................................................................................. 4-9

.
cable call-signal-classifier ......................................................................... 4-10 .
cable dhcp filter ......................................................................................... 4-12 .
cable dhcp-leasequery filter ...................................................................... 4-13 .
cable dhcpv6-leasequery filter .................................................................. 4-14 .
cable diaglog ............................................................................................. 4-15 .
cable docsis version 31 ............................................................................. 4-17 .
cable dsx authorization ............................................................................. 4-18 .
cable dynamic-service-flow ....................................................................... 4-19 .
cable ecn 770 ............................................................................................ 4-21 .
cable event ................................................................................................ 4-22.
cable flap-list ............................................................................................. 4-29

.
cable host authorization ............................................................................ 4-33 .
cable icmp filter ......................................................................................... 4-34 .
cable igmp filter ......................................................................................... 4-35 .
cable igmp permit src-ip ............................................................................ 4-36 .
cable igmp static-group ............................................................................. 4-37 .
cable igmp vrf static-group ........................................................................ 4-40 .
cable map-advance-adjust ........................................................................ 4-42 .
cable mdd ................................................................................................. 4-43 .
Casa Systems
RF Cable Configuration Guide and Command Reference v
Contents
cable mirror ................................................................................................4-46.
cable modem .............................................................................................4-47 .
cable monitor-period ..................................................................................4-48 .
cable partial-service ...................................................................................4-49 .
cable privacy ..............................................................................................4-53 .
cable proxy-arp unknown ..........................................................................4-54 .
cable qos ...................................................................................................4-55.
cable rcp-select priority ..............................................................................4-61 .
cable sa-des-tlvlen-2 .................................................................................4-62 .
cable sec ...................................................................................................4-63.
cable service attribute withhold-TLVs peak-rate ........................................4-70 .
cable service-class ....................................................................................4-71 .
cable service-flow active-timeout ...............................................................4-83 .
cable service-type-id ds-frequency ............................................................4-84 .
cable spectrum ..........................................................................................4-85 .
cable subscriber over-consume trap .........................................................4-88 .
cable tag ....................................................................................................4-89

.
cable tcc us-bonding-disable .....................................................................4-92 .
cable traffic-policy ......................................................................................4-93 .
cable upstream ..........................................................................................4-99 .
reg-rsp-original-upstream-action .............................................................4-102 .
Chapter 5. Cable modem commands

Cable modem commands description ...............................................................5-1 .
cable modem ...............................................................................................5-3 .
cable modem <mac_addr> dbc ...................................................................5-4 .
cable modem <mac_addr> dcc ...................................................................5-8 .
cable modem <mac_addr> l2vpn-map ......................................................5-10 .
cable modem <mac_addr> mpls ...............................................................5-11 .
cable modem <mac_addr> qos-override ...................................................5-13 .
cable modem <mac_addr> ucc upstream .................................................5-15 .
cable modem authorization .......................................................................5-16 .
Casa Systems
vi RF Cable Configuration Guide and Command Reference
Contents
cable modem deny .................................................................................... 5-17 .
cable modem excessive-request detection ............................................... 5-18 .
cable modem offline aging ........................................................................ 5-19 .
cable modem remote-query ...................................................................... 5-20 .
cable modem rip authentication-bypass ................................................... 5-21 .
cable modem vendor ................................................................................ 5-22 .
cm-ctrl ....................................................................................................... 5-26

.
default cable modem vendor ..................................................................... 5-28 .
Chapter 6. Channel bonding

Channel bonding commands description .......................................................... 6-1 .
bonding-group ............................................................................................. 6-5 .
dbg_id_set qam ........................................................................................ 6-11 .
rcc ............................................................................................................. 6-12

.
rcp ............................................................................................................. 6-15

.
service group ............................................................................................ 6-18 .
Chapter 7. Channel blocks

Channel block commands description .............................................................. 7-1 .
channel-block downstream group 4 ............................................................ 7-2 .
channel-block downstream mac-domain block-id ....................................... 7-3 .
channel-utilization-interval .......................................................................... 7-5 .
Chapter 8. DOCSIS MAC interface

DOCSIS MAC interface commands description ............................................... 8-1 .
interface docsis-mac ................................................................................... 8-2 .
Chapter 9. DOCSIS Set-Top Gateway

DSG commands description ............................................................................. 9-1 .
Configuration summary ..................................................................................... 9-4 .
dsg channel-list ........................................................................................... 9-5 .
dsg client-list ............................................................................................... 9-8 .
dsg dcd-global-enable ............................................................................... 9-10 .
Casa Systems
RF Cable Configuration Guide and Command Reference vii
Contents
dsg timer-id ................................................................................................9-11

.
dsg tunnel ..................................................................................................9-12

.
dsg tunnel-group ........................................................................................9-17 .
dsg unicast-port .........................................................................................9-19 .
dsg vendor-param-id .................................................................................9-20 .
Chapter 10. Load balancing

Load balancing commands description ...........................................................10-1 .
load-balance ..............................................................................................10-6 .
load-balance annexb-upper-frequency ......................................................10-8 .
load-balance basic-rule .............................................................................10-9 .
load-balance dcc-retry .............................................................................10-11 .
load-balance enable ................................................................................10-12 .
load-balance exclusion list .......................................................................10-14 .
load-balance execution-rule ....................................................................10-16 .
load-balance general-group .....................................................................10-22 .
load-balance permit dbc-chg-prim-ds ......................................................10-28 .
load-balance policy ..................................................................................10-29 .
load-balance restricted-cm ......................................................................10-32 .
load-balance restricted-group ..................................................................10-35 .
Chapter 11. Modulation profiles

Modulation profile commands description ....................................................... 11-1 .
modulation-profile ......................................................................................11-2 .
a-long ...................................................................................................11-7 .
a-short .................................................................................................11-9 .
initial ..................................................................................................11-10.
long ....................................................................................................11-11 .
request ...............................................................................................11-12 .
short ...................................................................................................11-13 .
station ................................................................................................11-14 .
ugs .....................................................................................................11-15 .
Casa Systems
viii RF Cable Configuration Guide and Command Reference
Contents
Chapter 12. Multicast cable operations

Multicast cable operation commands description ........................................... 12-1 .
mcast-classifier ds_chan ........................................................................... 12-4 .
mcast-service-flow ds_chan ...................................................................... 12-6 .
multicast authorization .............................................................................. 12-9 .
multicast default grp-service-class-name ................................................ 12-14 .
multicast group ........................................................................................ 12-15 .
multicast load-balance initial-tech ........................................................... 12-21 .
multicast max channel-util ....................................................................... 12-23 .
multicast single_said ............................................................................... 12-24 .
multicast switch over time ....................................................................... 12-26 .
Chapter 13. NetFlow Monitoring

NetFlow monitoring commands description .................................................... 13-1 .
flow exporter-map ..................................................................................... 13-3 .
flow monitor-map ...................................................................................... 13-6 .
flow sampler-map ...................................................................................... 13-8 .
Chapter 14. Orthogonal Frequency Division Multiplexing

OFDM description ........................................................................................... 14-1 .
ofdm .......................................................................................................... 14-7

.
interface qam .......................................................................................... 14-14 .
interface docsis-mac ............................................................................... 14-23 .
module <slot> ofdm-channels ................................................................. 14-25 .
service group .......................................................................................... 14-27 .
OFDM configuration examples ..................................................................... 14-28 .
Chapter 15. Orthogonal Frequency Division Multiple Access

OFDMA description ......................................................................................... 15-1 .
ofdma ...................................................................................................... 15-10 .
interface docsis-mac ............................................................................... 15-19 .
interface ofdma ....................................................................................... 15-21 .
service group .......................................................................................... 15-35 .
Casa Systems
RF Cable Configuration Guide and Command Reference ix
Contents
OFDMA configuration example .....................................................................15-37 .
Chapter 16. PacketCable

PacketCable commands description ...............................................................16-1 .
packetcable ...............................................................................................16-2 .
Chapter 17. QAM interface

QAM channel configuration .............................................................................17-1 .
interface qam ...........................................................................................17-14 .
module .....................................................................................................17-33.
Chapter 18. Quality of service

QoS commands description ............................................................................18-1 .
cops pdp-ip ................................................................................................18-5 .
qos-profile ..................................................................................................18-7
.
Chapter 19. Spectrum management

Spectrum management commands description ..............................................19-1 .
channel-utilization-interval .........................................................................19-6 .
hop period ..................................................................................................19-7

.
spectrum ....................................................................................................19-9
.
spectrum analysis ....................................................................................19-10 .
spectrum monitor-interface ......................................................................19-13 .
spectrum rule ...........................................................................................19-14 .
spectrum scheduler .................................................................................19-24 .
test cable hop upstream ..........................................................................19-26 .
test cable hop-cm-mode upstream ..........................................................19-27 .
Chapter 20. Subscriber management

Subscriber management commands description ............................................20-1 .
docsis submgt default ................................................................................20-2 .
docsis submgt filters clear-all ....................................................................20-8 .
docsis submgt ip-filter ................................................................................20-9 .
Casa Systems
x RF Cable Configuration Guide and Command Reference
Contents
Chapter 21. Upstream interface

Upstream interface commands description ..................................................... 21-1 .
interface upstream .................................................................................... 21-2 .
upstream igmp filter ................................................................................ 21-19 .
upstream map size .................................................................................. 21-20 .
Chapter 22. Video

Video commands description .......................................................................... 22-1 .
adduser ..................................................................................................... 22-4.
interface video ........................................................................................... 22-6 .
video ....................................................................................................... 22-12

.
video cat-interval ..................................................................................... 22-13 .
video channel-id-offset ............................................................................ 22-14 .
video clk-drift-correction .......................................................................... 22-16 .
video dejitter-interval ............................................................................... 22-17 .
video drop ghost-pid ............................................................................... 22-18 .
video drop reserved-pids ........................................................................ 22-19 .
video edis ................................................................................................ 22-20 .
video erm ................................................................................................ 22-25 .
video error-threshold ............................................................................... 22-28 .
video error-window .................................................................................. 22-30 .
video logging ........................................................................................... 22-31 .
video min-stream-switch-time ................................................................. 22-33 .
video module ........................................................................................... 22-34 .
video multicast-session-loss-timeout ...................................................... 22-39 .
video ngod .............................................................................................. 22-40 .
video pat-interval ..................................................................................... 22-43 .
video pid-remapping-mode ..................................................................... 22-44 .
video pktloss-window .............................................................................. 22-46 .
video pme ............................................................................................... 22-47 .
video pme install-certificate ..................................................................... 22-52 .
video pmt-interval .................................................................................... 22-53 .
Casa Systems
RF Cable Configuration Guide and Command Reference xi
Contents
video power-key on .................................................................................22-54 .
video qam-domain ...................................................................................22-56 .
video qam export configuration slot .........................................................22-61 .
video reserved-pid upper-limit .................................................................22-63 .
video session ...........................................................................................22-64 .
video signaling-mode ...............................................................................22-78 .
video simulcrypt .......................................................................................22-79 .
video stream-proc reset ...........................................................................22-87 .
video stream-switch .................................................................................22-88 .
video table ...............................................................................................22-89

.
video unicast-session-loss-timeout ..........................................................22-92 .
no video sessions ....................................................................................22-94 .
Casa Systems
xi
Preface
About this guide

The Casa Systems – RF Cable Configuration Guide and Command Reference guide is
intended for system administrators, support engineers, and operators who are
responsible for configuring and managing Casa CMTS products. Specifically, this
manual covers the commands that operate on the DOCSIS RF cable side of the
CMTS, such as configuring upstream and downstream channels, spectrum
management, modulation profiles, PacketCable, quality of service policies, subscriber
management, and video.
Cable network administrators and operators who are integrating and configuring the
CMTS RF cable interfaces in the cable headend with their existing network
infrastructure should have experience with the following:
• Internet Layer 2 and Layer 3 networking technologies and transports
• Frequency management on upstream and downstream interfaces.
Note: The additional NSI Configuration Guide and Command Reference

covers the IETF routing protocols that are supported on CMTS network side
interfaces.
The following topics are covered in this guide:
For information about See
Overview of RF cable operations Chapter 1.

Application classes and policies Chapter 2.
Baseline Privacy Interface Chapter 3.
Cable commands Chapter 4.
Casa Systems CMTS

xii RF Cable Configuration Guide and Command Reference
Preface
For information about See
Cable modem commands Chapter 5.

Channel bonding commands Chapter 6.
Channel blocks and channel utilization commands Chapter 7.
DOCIS MAC interface commands Chapter 8.
DOCSIS Set-Top Gateway commands Chapter 9.
Load balancing commands Chapter 10.
Modulation profile commands Chapter 11.
Multicast cable operations commands Chapter 12.
NetFlow monitoring commands Chapter 13.
Orthogonal frequency division multiplexing (OFDM) commands Chapter 14.
Orthogonal frequency division multiple access (OFDMA) commands Chapter 15.
PacketCable commands Chapter 16.
QAM interface commands Chapter 17.
Quality of service commands Chapter 18.
Spectrum management commands Chapter 19.
Subscriber management commands Chapter 20.
Upstream interface commands Chapter 21.
Video commands Chapter 22.
Revision history
This guide supports Casa CMTS software releases up through Release 7.2. See the
Casa Systems – CMTS Release Notes for information on new or late features not yet
covered in this guide.
• 1.00.00 — August 2014; initial review draft.
• 1.00.01 — September 2014; added QAM 8x96 interface chapter.
• 1.00.02 — September 2014; initial release.
• 1.00.03 — October 2014; updated released version with latest functionality.
• 1.00.04 — January 2015; updated 6.4.3 released version with latest functionality.
• 1.00.05 — August 2015; updated to Release 6.4.3.4.
Casa Systems CMTS

RF Cable Configuration Guide and Command Reference xiii
Preface
• 1.01.00 — April 2015; updated to Release 6.5.2.

• 1.02.00 — August 2015; Release 7.0.1 initial review draft.
• 1.02.01 — January 2016; updated to Release 7.1.2.
• 1.02.02 — February 2016; updated to Release 7.1.3.
• 1.03.00 — August 2016; updated to Release 7.2.3 build 4882.
• 1.03.01 — October 2016; updated to Release 7.2.3 build 49e9.
• 1.03.02 — December 2016; updated to Release 7.2.3 build 4b91
• 1.03.03 through 7.02.03 not used — Revision level restructured; January 2017.
• 07.02.04 — January 2017; updated to Release 7.2.4.
• 07.02.04a — March 2017; updated to Release 7.2.4 build 5356.
Supported software releases

The following software releases are supported in this latest revision:
• CMTS Releases 5.4.21, 6.1.2, 6.1.3, 6.4.1, 6.4.2, 6.4.3, 6.5, 7.0, 7.1, and 7.2. Note
that Release 7.0 and later software is not supported on Casa C10200, C3200, and
C2200 systems.
• 1G.1 (for Casa C1G systems with customized functionality; see the Casa Systems
– C1G CMTS Release Notes for information).
Contacting Casa
Corporate facility
Casa Systems, Inc.
100 Old River Road
Andover, MA 01810
Tel.: 978-688-6706
World Wide Web: www.casa-systems.com
Casa Systems CMTS

xiv RF Cable Configuration Guide and Command Reference
Preface
Technical Support
In the United States: Tel: 978-699-3045
E-mail: support@casa-systems.com
Technical documentation
Casa Systems provides the following documentation set in PDF format, viewable
using Adobe Reader 5.0 or later. These PDF files are available from the Casa FTP site
at ftp://support.casa-systems.com.
• Casa Systems – C1G CMTS Quick Installation
• Casa Systems – C1G CMTS Hardware Installation Guide
• Casa Systems – CMTS Operations and Administration Guide
• Casa Systems – SNMP MIBs and Traps Reference
• Casa Systems – CCAP Video Edge User Guide
• Casa Systems – CMTS Network Solutions Guide
• Casa Systems – NSI Configuration Guide and Command Reference
• Casa Systems – RF Cable Configuration Guide and Command Reference (this
manual)
• Casa Systems – CMTS Troubleshooting and Diagnostics Guide
• Casa Systems – CMTS Release 7.2 Features Guide
• Casa Systems – C1G CMTS Release Notes
• Casa Systems – CMTS Release Notes
Casa Systems CMTS

RF Cable Configuration Guide and Command Reference xv
Preface
Note: Casa Systems provides updates to the manuals on a regular basis. Log
on to the Casa Systems Web site at www.casa-systems.com for the latest files
in PDF format. Select customer login and enter your username and
password. If you do not have a Casa-assigned username and password, send
e-mail to support@casa-systems.com.
Effective September 1, 2013, technical documentation CD-ROMs are no

longer shipped with Casa CMTS hardware.
Conventions used in Casa documentation

Key Convention Function Example
boldface font Commands and keywords are in Enter abc

boldface.
Italic font Emphasized terminology is in italics. burst profile
brackets [ ] Elements in square brackets are [<ip_addr>]
optional.
braces {x | y | z} Indicates a required argument with a {enabled | disabled}
choice of values; choose one.
brackets [x | y | z] Indicates an optional argument with a [abc | 123]
choice of values; choose one.
vertical bar | Separates parameter values. Same as {TCP | TLS}
“or.”
string A non-quoted set of characters. Do not abc
use quotation marks (“”) around the
string as the string will include the
quotation marks.
screen font CLI sessions and information the CASA(config)#
system displays are in screen font.
boldface screen font Information you must enter is in
boldface screen font.
<variable> Arguments for which you supply values <as_number>
are enclosed in angle brackets.
Multi-word arguments are indicated
with underscore-separated words.
<value:value> Arguments may include a range of <0:65535>
values, with the minimum and
maximum values separated by a colon.
Casa Systems CMTS

xvi RF Cable Configuration Guide and Command Reference
Preface
Acronyms
Casa Systems manuals contain the following industry-standard and product-specific
acronyms:
3DES Triple Data Encryption Standard (IPsec)
ABR Area Border Router (OSPF)
ARP Address Resolution Protocol
AS Autonomous System
ASN Autonomous System Number
ATDMA Asynchronous Time Division Multiple Access
BDR Backup Designated Router (OSPF)
BFD Bidirectional Forwarding Detection (RFC 5880)
BFS Broadcast File System
BGP Border Gateway Protocol
BKPM Baseline Privacy Key Management
BNG Broadband Network Gateway
BPI[+] Baseline Privacy Interface [Plus]
BPSK Binary Phase Shift Keying
BSoD Business Services over DOCSIS
BSR Bootstrap Router (PIM)
FIB Forwarding Information Base
CAS Conditional Access System (SimulCrypt)
CCAP Converged Cable Access Platform
CE Customer Edge
CIDR Classless Inter-Domain Routing
CIR Committed Information Rate
CM Cable Modem
CMTS Cable Modem Termination System
CNR Carrier-to-noise ratio
COPS Common Open Policy Service
CPD Control Point Discovery (PacketCable)
CPE Customer Premises Equipment
CRC Cyclic Redundancy Check
Casa Systems CMTS

RF Cable Configuration Guide and Command Reference xvii
Preface
CSM Casa Spectrum Management

CSMA Carrier Sense Multiple Access
DAD Duplicate Address Detection (interfaces)
DBC Dynamic Bonding Change
DBG Downstream Bonding Group
DCC Dynamic Channel Change
DCD Downstream Channel Descriptor (QAM)
DCTS Digital Cable Termination System
DCU DOCSIS Control and Upstream module
DDM DOCSIS Device Manager
DES Data Encryption Standard
DNCS Digital Network Control System
DNS Domain Name System/Server
DHCP Dynamic Host Configuration Protocol
DLF Destination lookup failure (packets)
DPD Downstream Profile Descriptor (OFDM)
DQM DOCSIS QAM Module
DSA Digital Signature Algorithm (SSH)
DSCP Differentiated Services Code Point
DSG DOCSIS Set-Top Gateway specification (QAM)
DSID Downstream Service Identifier (DOCSIS MAC)
DSX Dynamic Service Change (DSA, DSC, and DSD)
DVB Digital Video Broadcasting
EAE Early Authentication Encryption (DOCSIS MAC)
EAM Emergency Alert Message
eBGP External Border Gateway Protocol
ECM Entitlement Control Message (SimulCrypt)
ECMG Entitlement Control Message Generator (SimulCrypt)
EDIS Edge Device Interface Specification
EDRCA EuroDOCSIS Root Certificate Authority
EIS Event Information Scheduler (SimulCrypt)
EQAM Edge QAM Module
Casa Systems CMTS

xviii RF Cable Configuration Guide and Command Reference
Preface
ERM Edge Resource Manager (NGOD)

ERS Encryption Renewal System (PME)
FEC Forward Error Correction
FFT Fast Fourier Transform
FPGA Field Programmable Gate Array
FSM Finite State Machine
GigE Gigabit Ethernet
GRE Generic Routing Encapsulation (upstream interface)
HCS Header Check Sequence
HMAC Keyed-Hash Authentication Code
IA_PD Identity Association for Prefix Delegation (IPv6)
IGMP Internet Group Management Protocol (interfaces)
IGP Interior Gateway Protocol
IKE Internet Key Exchange (IPsec)
IP Internet Protocol
IPC Inter-process communication (error)
IPDR IP Detail Record
IPsec Internet Protocol Security
IPTV Internet Protocol Television (policies)
IS-IS Intermediate System-to-Intermediate System routing protocol
IUC Interval Usage Code (OFDMA)
KEK Key Encryption Key (BPI)
L2VPN Layer 2 Virtual Private Network
LACP Link Aggregation Control Protocol
LDP Label Distribution Protocol
LDPC Low Density Parity Check (OFDMA)
LSA Link State Advertisement
LSP Link-State Packet (IS-IS)
LSR Label-Switched Router (LDP)
MAC Media Access Code
MD5 Message Digest 5 algorithm
MDD MAC Domain Descriptor (DOCSIS MAC)
Casa Systems CMTS

RF Cable Configuration Guide and Command Reference xix
Preface
MED Multi-Exit Discriminator (BGP)

MGMD Multicast Group Membership Discovery (DOCSIS MAC)
MGPI Multiple Grants Per Interval (PacketCable)
MIB Management Information Base
MIC Message Integrity Check (DOCSIS MAC)
MLD Multicast Listener Discovery (interfaces)
MMS Maximum message size (SNMP)
MPD Mark Probability Denominator (QoS)
MPLS Multi-Protocol Label Switching
MPTS Multiple Program Transport Stream
MTA Multimedia Terminal Adapter (interfaces)
MTDMA Modified Time Division Multiple Access
MTU Maximum Transmission Unit
NCP Next Codeword Pointer (OFDM)
NET Network Entity Title (IS-IS)
NGOD Next Generation on Demand (video)
NLS Network Layer Signaling (PacketCable)
NSAP Network Service Access Point (IS-IS)
NSEL NSAP Selector (IS-IS)
NSF Non-Stop Forwarding (OSPF)
NSI Network System Interface
NSM Network Services Manager
NTP Network Time Protocol
OCD OFDM Channel Descriptor
OCSP Online Certification Status Protocol
OFDM Orthogonal Frequency Division Multiplexing
OFDMA Orthogonal Frequency Division Multiplexing Multiple Access
OSPF Open Shortest Path First routing protocol
OUI Organizational Unique Identifier
PAP Password Authentication Protocol (AAA)
PAT Program Association Table (video)
PCMM PacketCable Multimedia (policies)
Casa Systems CMTS

xx RF Cable Configuration Guide and Command Reference
Preface
PDP Policy Decision Point (COPS)

PDU Protocol data unit (interfaces)
PE Provider Edge
PEP Policy Enforcement Point (COPS)
PHS Payload Header Suppression
PID Packet ID (interfaces)
PIM-SM Protocol Independent Multicast in Sparse Mode
PLC PHY Link Channel (OFDM)
PME Privacy Mode Encryption (video)
PMT Program Mapping Table
PPS Packets per second
PS Portal Server
PSK Pre-Shared Key (IPsec)
QAM Quadrature Amplitude Modulation
QinQ IEEE 802.1ad VLAN double tagging protocol based on 802.1q
QoS Quality of Service
QPSK Quadrature Phase Shift Keying
RADIUS Remote Authentication Dial In User Service
RCP Receive Channel Profile
RD Route Distinguisher (VRF)
RFoG Radio Frequency over Glass
RIP Routing Information Protocol
RKS Record Keeping Server
RLB Restricted Load Balancing
RLBCM Restricted Load Balancing Cable Modem
RLBG Restricted Load Balancing Group
RP Rendezvous Point (PIM-SM), or Rolloff Postfix (OFDM)
RPC Remote Procedure Call (SNMP)
RSA Rivest, Shamir and Adleman cryptographic algorithm (SSH)
RT Route target (BGP)
SA Security Association (BPI)
SAID Security Association Identifier
Casa Systems CMTS

RF Cable Configuration Guide and Command Reference xxi
Preface
SAV Source Address Verification

SC Subchannel
SC-QAM Single-carrier QAM
SCG Scrambling Control Group (SimulCrypt)
SCS SimulCrypt Synthesizer
SDV Switched Digital Video
SFP Small Form-Factor Pluggable
SHA Secure Hash Algorithm
SI Service Information (QAM)
SID Service identifier (DOCSIS MAC)
SMM Switch and Management Module
SNP Sequence Number PDU
SNR Signal-to-noise ratio
SOO Site-of-origin (BGP)
SPD Security Policy Database (IPsec)
SPF Shortest Path First algorithm
SPI Security Policy Index (IPsec)
SPT Shortest Path Tree (PIM-SM)
SPTS Single-Program Transport Stream
SRM Session Resource Manager
SSH Secure Shell
SSM Source-Specific Multicast (PIM-SM)
STM Subscriber Traffic Management
TACACS Terminal Access Controller Access Control System
TCC Transmit Channel Configuration
TCP Transmission Control Protocol
TDMA Time Division Multiple Access
TEK Traffic Encryption Key (BPI)
TLV Type-length-value encoding scheme
TOS Type of service
TPID Tag Protocol Identifier (VLAN)
UCC Upstream Channel Change
Casa Systems CMTS

xxii RF Cable Configuration Guide and Command Reference
Preface
UCD Upstream Channel Descriptor (DOCSIS MAC)

UDC Upstream Drop Classifier (DOCSIS MAC)
UGS Unsolicited Grant Service
UGS-AD Unsolicited Grant Service with Activity Detection
URL Uniform Resource Locator
USM User-based Security Model (SNMP)
VLAN Virtual Local Area Network
VLSM Variable Length Subnet Mask
VOD Video On Demand
VPLS Virtual Private LAN Service
VPWS Virtual Private Wire Service
VRF Virtual Routing and Forwarding
VSRM Video on Demand System Resource Manager
WFQ Weighted Fair Queuing QoS algorithm
WRED Weighted Random Early Detection
XGigE XGigabit Ethernet
Casa Systems CMTS

1-1
Chapter 1. RF cable operations

overview
About this chapter

This chapter provides information on how the CMTS operates in the cable headend
network. It covers the following topics:
Topic Page
CMTS installation in the network topology 1-2

About the Casa CMTS as a headend device 1-2
Understanding the CMTS as a DOCSIS MAC domain 1-4
Cable modem initialization and learning 1-5
Cable modem initial ranging and registration 1-6
Cable modem provisioning and configuration 1-7
Cable modem power considerations 1-7
Upstream channel descriptors and MAPs 1-9
UCD and MAP operations 1-9
Channel bonding and service group operations 1-12
Physical fiber node vs. DOCSIS terminology 1-13
Load balancing CMTS traffic 1-13
Dynamic channel and bonding changes 1-15
Load balancing policies 1-15
Static vs. dynamic load balancing 1-16
Applying exclusion lists 1-17
Casa Systems
1-2 RF Cable Configuration Guide and Command Reference
CMTS installation in the network topology
Topic Page
Terminology covered in this chapter 1-17

Configuration examples 1-22
Basic configuration 1-23
General configuration 1-24
CMTS installation in the network topology

Figure 1-1 illustrates a sample cable headend network and a typical cable topology.
This example shows a CMTS DOCSIS MAC domain with one downstream interface
and multiple upstream interfaces to a fiber network, network accessible servers,
routing to the Internet, content networks providing modulated signals downstream,
and a distribution area topology with a single CM customer with attached customer
premises equipment (CPEs).
About the Casa CMTS as a headend device
The Casa CMTS provides both a network side interface (NSI) and a radio frequency
interface (RFI). On the NSI, the CMTS provides Ethernet 10/100 Mbps (for system
management), GigE, and 10GigE (C10G) interfaces to routing gateways and servers.
On the RFI, the CMTS provides both upstream and downstream interfaces for
transmission and receipt of digitized content and data services over fiber network
trunks and coaxial cable to and from the subscriber distribution areas.
Residing between the NSI and the RFI is the CMTS forwarding engine that resides in
the CMTS Switch and Management Module. As data, voice, and video traffic is
processed over both the NSI and the RFI, the forwarding engine selectively directs the
traffic over the correct interface for transmission and delivery to a destination.
Upstream HTTP requests to the Internet from a customer PC, for example, is
transmitted by the cable modem (CM) over the fiber network to the upstream CMTS
channels before being forwarded to the NSI and routing gateway to the Internet. The
HTTP response (and Web page) from the Internet destination is then returned to the
CMTS and forwarded over a downstream channel to that customer’s CM for
transmission and presentation at the PC.
Casa Systems
RF cable operations overview 1-3
About the Casa CMTS as a headend device
Figure 1-1. Example D1.0 cable network topology with Casa CMTS
Cable headend network Servers

TFTP DHCP ToD Content networks
Internet - Streaming video/
video-on demand
servers
- News and sports feeds
- Network and satelite TV
Network edge router/ - Local TV
gateway to Internet
Hub
Modulated digital signals
Casa CMTS
CASA SYSTEMS SYS 3 4 5
Single
Multiple C3000 CCASA
ASA
ALM 0 1 2
downstream
upstream channel Forward channel lineup
channels
DOCSIS MAC domain (1 x N)

Television and
Diplexer/filter Forward combiner channel lineup
LOW | HIGH
5 to 42 MHz 50 MHz to 1 GHz
MPEG-2 Set-top box
Fiber network and transport stream
amplifier CH 851
Coaxial cable Cable modem

DS
US
D3.0, 2.0, PC
1.1, 1.0
Phone
Distribution over cable access
network to home subscribers
Note: The topology illustrated in Figure 1-1 uses the Casa C3200 CMTS as
an example. Other CMTS platforms, such as the Casa C10G and future Casa
platforms, also fit into this topology.
Casa Systems
Understanding the CMTS as a DOCSIS MAC domain
Understanding the CMTS as a DOCSIS MAC domain
The Casa CMTS comprises up to 64 DOCSIS MAC domains depending on the

particular model of CMTS you are integrating. The RFI, which consists of at least one
downstream channel and multiple upstream channels, is the DOCSIS Media Access
Control (MAC) domain. Today’s cable networks and CMs support the various
implementations of DOCSIS since its acceptance by cable providers in the late 1990s,
including:
• DOCSIS 1.0 — One downstream, multiple upstream channels in 1xN

configuration. Baseline privacy interface (BPI); CM identification by service ID
(SID).
configuration. Baseline privacy interface plus (BPI+); CM identification by
service flow. QoS provisioning services for reliable voice and video streaming.
Quadrature Phase Shift Keying (QPSK) modulation only.
configuration. QAM64 modulation with downstream channel width at 6.4 MHz.
Improved performance and speed at 30 Mbps on the upstream channels.
• DOCSIS 3.0 — Multiple downstream channels, multiple upstream channels in
MxN configuration. Channel bonding of up to 24 channels for increased
downstream bandwidth; logical bonding of channels from the MAC domain to
compatible DOCSIS 3.0 CMs supporting multiple transmitters and receivers. See
Figure 1-2.
• DOCSIS 3.1 — Follows the same Evolved Telecommunication System (ETS)
development in parallel with wireless evolution. DOCSIS 3.1 supports
Orthogonal Frequency Division Multiplexing (OFDM) and Orthogonal
Frequency Division Multiple Access (OFDMA).
Note: DOCSIS versions are backward compatible, such that a D3.0 CM is

fully compatible with prior versions D2.0, D1.1, and D1.0. However, a D1.0 CM
cannot take advantage of D3.0 channel bonding capabilities if the CMTS is
configured with multiple downstream channels.
Casa Systems
Cable modem initialization and learning
Figure 1-2. DOCSIS 3.0 topology with multiple downstream channels
DOCSIS 3.0 Multiple Modulated digital signals

MAC domain (M x N) downstream from content providers
channels
CASA SYSTEMS SYS 3 4 5
C3000 CCASA
ASA
ALM 0 1 2
Multiple
Forward channel lineup
upstream
channels
Television and
Diplexer/filter Forward combiner channel lineup
LOW | HIGH
MPEG-2 Set-top box
Fiber network and transport stream
amplifier CH 851
DS
US PC
Coaxial cable D3.0 cable modem
- Multiple tranmitters
and receivers
- Channel bonding
Phone
Cable modem initialization and learning

In order for CMs in the subscriber distribution areas to establish two-way
communication with the CMTS, CMs must first initialize by listening and learning
how to receive transmissions from the CMTS downstream channels, and then by
learning how to transmit to the CMTS over the upstream channels.
Modem initialization begins when the modem is connected to the cable provider’s
network and powered on. The modem listens for MAC management message (MMM)
broadcasts from the CMTS. Using QAM modulated signals, the MMM carries the
188-byte MPEG-2 transport stream for modem synchronization with the MAC
domain, as well as the upstream channel descriptors (UCDs) and their associated
MAP packets for establishing upstream transmissions, and a MAC domain descriptor
(MDD) for D3.0 modems capable of channel bonding.
Casa Systems
Cable modem initial ranging and registration
Once the CM is able to listen for and receive the MPEG-2 transport streams that are
modulated on the downstream carrier signals, the modem begins the initial ranging
process over the upstream channels.
Cable modem initial ranging and registration

Initial ranging is a scheduled event that allows a CM to request an upstream
transmission grant from the CMTS. Initial ranging requests are carried in the UCD
burst profile with an associated MAP containing the CMTS-assigned interval usage
code (IUC). The IUC schedules the initial ranging interval in the upstream time line to
the CMTS. Once a transmission interval is set, the MAC domain then adjusts CM
frequency, power, and delay for two-way communication.
In large networks with many CMs attempting to register with the CMTS at the same
time, initial ranging requests are subject to collisions with requests from other
modems. Each initial ranging request is considered an initial ranging opportunity.
Because of the high probability of collisions, the MAC domain uses a ranging backoff
algorithm to tell the modem how long to wait before retransmitting another initial
ranging request.
The ranging backoff algorithm reschedules and increases initial ranging transmissions
at random intervals to provide a better opportunity for CMs to avoid collisions.
Ranging backoff values are expressed as an exponential value to set the number of
ranging opportunities per retry, such 23, 24, 25, and 26. For example, configuring a
value of 3 specifies 23, or 8 ranging opportunities on the first attempt. Configuring a
value of 4 specifies 24, or 16 ranging opportunities on the second attempt and so on.
The Casa CMTS allows up to sixteen initial ranging retry attempts. When the CM
receives an upstream transmission grant from the CMTS, the MAC domain adjusts the
CM for frequency, power, and delay. Two-way modem communication with the
CMTS is then established.
After the initial ranging request has completed, the CM is then provisioned using
DHCP and TFTP to complete the initialization process, as described in the next
section. When the initialization process has completed, the CM requests registration
with the CMTS. The CM can then receive transmissions on the downstream channels
and transmit to the CMTS over the upstream channels.
Casa Systems
Cable modem provisioning and configuration
Cable modem provisioning and configuration

Provisioning servers at the headend are necessary for the CM to properly complete the
initialization process, as follows:
1. The CM initiates a request to a dynamic host configuration protocol (DHCP)

server for an IPv4 or IPv6 address assignment. DHCP DISCOVER, OFFER,
REQUEST, and ACKNOWLEDGMENT packets are exchanged between the
modem and the DHCP server. The DHCP acknowledgment message returns the
offered IP configuration to the requesting CM.
2. Once the CM is assigned an IP address, the modem submits a request to a target
TFTP server for the DOCSIS modem configuration file. The configuration file
provides operational information to the modem using parameters that are set by
the cable service provider, including program identification to the CMTS MAC
domain. The TFTP server responds to the request by forwarding and loading the
configuration file to the modem at the DHCP-assigned address.
3. Optionally, the CM may request time information from a time-of-day (ToD)
server. In most cases, time information is returned to the CM using DOCSIS time
synchronization packets from the MAC domain that are carried in the MAC
management messages.
Figure 1-3 shows the the cable modem initialization and configuration process.
Cable modem power considerations

In the downstream, if you have eight channels turned on instead of four, the
per-channel power should be 3 dBmV less than if you had four channels on. The
power setting is total output power from the port (the sum of all channels’ power). If
you double the number of channels, their per-channel power must drop by 3 dBmV.
Note also that the DOCSIS specification lowers the maximum required per-channel
output power by 3 dBmV for every doubling of channels above 4.
In the upstream, you should not see any power difference, regardless of the number of
channels enabled.
Casa Systems
Cable modem power considerations
Figure 1-3. Cable modem initialization and configuration process

TFTP DHCP
Modem IP config MAC management message

config file to cable modem
188-byte
MPEG-2 transport
stream (42 Mbps)
Multiple Hub PID 1FFE MAC domain

upstream source
Casa CMTS Single
channels SYNC
CASA SYSTEMS
C3000 CCASA
ASA
SYS 3 4 5
ALM 0 1 2 downstream
channel UCD1
Modem initial UCD2
ranging
UCD3
and registration
Forward UCD4
combiner SYNC
Diplexer/filter
LOW | HIGH MAP1
MAP2
QAM64 or QAM256 MAP3
Fiber network and modulation
amplifier MAP4
Coaxial cable
DS
US
Cable modem frequency,
power, and delay adjustments.
Modem self-configuration using

file from TFTP server
1. Modem performs an initial ranging request with the CMTS. Transmission interval is
determined and modem is adjusted for frequency, power and delay. Modem sends
a registration request to the CMTS for two-way communication with the MAC domain.
2. Modem DCHP DISCOVER, OFFER, REQ, ACK packets exchanged with DHCP server.
3. IP configuration downloaded to cable modem.
4. Modem receives modem config file from TFTP server and configures itself. Optional
time-of-day packet exchange.
Casa Systems
Upstream channel descriptors and MAPs
Upstream channel descriptors and MAPs

As CMs continually listen for downstream MAC management messages from the
CMTS, the MPEG-2 transport stream carries the information that instructs the modem
on how to transmit over the upstream channels. A CM uses upstream channel
descriptors (UCDs) and associated MAPs carried in the MPEG-2 transport stream to
tell the modem “how and when” to transmit to the CMTS.
UCD and MAP operations

The CMTS MAC domain sends one upstream channel descriptor (UCD) for every
upstream channel. If there are four upstream channels configured at the CMTS MAC
domain, the MPEG-2 transport stream will contain four UCDs, as illustrated in
Figure 1-3. The CM will select one UCD at random to instruct the modem on “how”
to transmit.
Each UCD describes an upstream channel with the following information:
• Frequency
• Width
• Burst profile
The burst profile is a set of burst descriptors, where:
1. Each burst profile can be one of five burst types: initial ranging, periodic ranging,
long data, short data, and request. (See Chapter 11, “Modulation profiles.”)
2. Each burst type can have one or more burst descriptors with up to twelve burst
description parameters, such as modulation type, forward error correction (FEC),
scrambler, preamble, long/short data, and others.
Each UCD has one associated MAP that instructs the modem on “when” to transmit
over an upstream timeline.
Figure 1-4 illustrates the association between the UCD and the MAP, where:
• UCD1 specifies the CMTS upstream channel, frequency, width and burst profile.
Casa Systems
• MAP1 specifies when time-zero (t0) begins on the upstream timeline, as well as
the 32-byte field that carries the service identifier (SID) that describes “who” is
transmitting.
• The interval usage code (IUC) that indicates “what” type of transmission, and the
t0 timing offset to indicate “when” to begin the upstream transmission interval
from t0 on the timeline.
Figure 1-4. UCD and MAP components

188-byte
MPEG-2 transport stream
1FFE
SYNC
“How to transmit” UCD1 Upstream channel selection, frequency, width, burst profile
UCD2
UCD3
Field of data
UCD4
SYNC
MAP
“When to transmit” MAP1 Elements 32 14 4 14 14 4 14
header
MAP2
MAP3
MAP4 “Who” “When”
Service ID (SID) t0 offset
“What”
Interval Usage Code (IUC)
The upstream timeline is comprised of intervals and minislots, where a single group of
minislots makes up one interval. These intervals vary in size starting at time-zero (t0)
until the end of the interval where t0 begins again. Time-division multiplexing (TDM)
scheduling is used to set both long and short intervals in the timeline where the
interval size is based on traffic conditions. Each minislot within each interval is 6.25
microseconds. Figure 1-5 illustrates the upstream channel timeline, intervals, and
minislots in the network context. (See Chapter 21, “Upstream interface.”)
Casa Systems
Figure 1-5. MAP upstream channel timeline, intervals and minislots

188-byte
MPEG-2
transport stream
Multiple 1FFE
upstream Casa CMTS Single
channels SYNC
CASA SYSTEMS
C3000 CCASA
ASA
SYS 3 4 5
ALM 0 1 2 downstream
channel UCD1
One upstream
channel selected UCD2
from UCD
UCD3
Forward UCD4
UCD1
combiner SYNC
Diplexer/filter
LOW | HIGH MAP1
MAP2
QAM64 or QAM256 MAP3
modulation
MAP4
Coaxial cable Cable modem

DS
US
Upstream timeline
Intervals Large and small intervals in timeline
IUC interval
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Minislots
(6.2 ms per minislot) 0
t0 0
MAP1
MAP
Elements 32 14 4 14 14 4 14
header
“Who” “When”
Service ID (SID) t0 offset
“What”
Interval Usage Code (IUC)
Casa Systems
Channel bonding and service group operations
Channel bonding and service group operations

Channel bonding, a DOCSIS 3.x capability, is the CMTS process that logically
combines multiple downstream or upstream channels for extended bandwidth for
modems having multiple transmitters and receivers. For downstream channels, the
MAC domain descriptor in the MPEG-2 transport stream informs the modem about
the receive channel configuration and the receive channel set (RCS) to be used by a
registered modem. (See Chapter 6, “Channel bonding.”)
Figure 1-6 illustrates a sample network with eight downstream channels. Even though
the modem only supports 4 downstream and 4 upstream channels, the modem learns
how to receive traffic across all eight CMTS downstream channels. The CMTS
dynamically creates a channel bonding group using four of the channels (based on
current traffic load) and creates a downstream service group, or DS-SG associated
with the assigned modem channel set. A service group is simply a group of channels.
Figure 1-6. DOCSIS 3.0 channel bonding to cable modems

Eight
Four upstream Modulated digital signals
DOCSIS 3.0 downstream
channels in two from content providers
MAC domain (M x N) channels
service groups CASA SYSTEMS SYS 3 4 5
C3000 CCASA
ASA
ALM 0 1 2
A
B Forward channel lineup
C
D
Forward combiner
Multicast bus
LOW | HIGH LOW | HIGH LOW | HIGH LOW | HIGH

A B C D Diplexers/filters in
each distribution area
Fiber network 4US x 4DS
and amplifier DS-SG = CM-SG
US-SG
DS
US
D3.0 cable modem

Cable distribution areas - Channel bonding of
four DS channels based
the modem’s capability.
- Two-channel US service group.
Casa Systems
Physical fiber node vs. DOCSIS terminology
Similarly, the set of upstream channels is called the upstream service group, or
US-SG. Collectively, the upstream and downstream service groups make up the cable
modem service group, or CM-SG. All upstream and downstream channels originating
from the same MAC domain are known as a MAC domain cable modem service
group, or MD-CM-SG.
Note that the CM in Figure 1-6 at the “D” distribution area endpoint uses a
two-channel upstream service group. This means that upstream traffic from the CM
will be assigned to one of two channels from the MAC domain-assigned US-SG for
this modem.
Physical fiber node vs. DOCSIS terminology

Cable service providers deliver voice, data, and video traffic over fiber optic trunks to
subscriber distribution areas. These physical distribution areas are known as physical
fiber nodes, as illustrated in Figure 1-6.
A DOCSIS fiber node refers to a CM service group (CM-SG), which is made up of the
upstream and downstream service groups described in the previous section.
While cable providers around the world today use the term fiber node to describe the
physical cable infrastructure to the distribution areas, it is important to understand that
the term DOCSIS fiber node is associated with a CM service group and not the
physical network.
Load balancing CMTS traffic

Load balancing is the process that enables the CMTS to move a CM from one channel
to another so that traffic load is redistributed for improved bandwidth utilization and
reduced consumption of CMTS resources. When the CMTS determines that a channel
is reaching a traffic overload condition, the CMTS then moves the CM to a channel to
which that modem has access. This means that load balancing can only take place only
if the affected modem has multiple and “available” downstream and upstream
channels, restricted only by the MAC domain CM service group (MD-CM-SG)
configuration. (See Chapter 10, “Load balancing.”)
Casa Systems
Load balancing CMTS traffic
The Casa CMTS supports two types of load balancing: general load balancing and
restricted load balancing.
The general load balancing group (GLBG) uses the complete set of upstream and
downstream channels in that modem’s CM service group (CM-SG).
A restricted load balancing group (RLBG) uses a configured subset of channels in a

modem’s CM service group. This means that the channels available for load balancing
are interactively selected and saved in the CMTS running configuration file.
Note: A single CM cannot belong to more than one load balancing group at
any given time.
Both general and restricted load balancing groups have the following characteristics:
• Downstream and upstream channels belong to the same MD-CM-SG.

• A CMTS policy configuration controls whether a CM or service flow can be
moved.
• A CMTS priority configuration selects which CMs to move.
At CM registration time, the CMTS attempts to assign the modem either to a restricted
load balancing group (if it exists), or to a general load balancing group. If a restricted
load balancing group does not exist in the CMTS configuration file, the CM is then
assigned by default to the general load balancing group using the channels in the
MD-CM-SG for that modem.
The following load balancing restrictions apply:
• A single CM can belong to only one load balancing group using only the upstream
and downstream channels within that group.
• Load balancing does not take place if the CMTS cannot determine the load
balancing group to which a registered CM belongs.
Casa Systems
Dynamic channel and bonding changes
Dynamic channel and bonding changes
Dynamic channel change (DCC) and dynamic bonding change (DBC) messages from
the MAC domain instruct CMs on when to change channels, or when to change an
upstream or downstream bonding group. Both DCC and DBC can occur during traffic
load balancing at the CMTS when the CM has access to multiple upstream or
downstream channels.
DCC moves legacy and current DOCSIS 3.x modems (not operating with a multiple
receive channel set) from one downstream channel to another using the MD-CM-SG
for that modem. On the upstream side, DCC also instructs CMs to move from one
transmit channel to another from the MD-CM-SG.
DBC moves DOCSIS 3.x modems downstream service flows to different channels in
the modem’s receive channel set. DBC also moves D3.0 upstream service flows to
different channels in the current transmit channel set. In the Casa implementation, the
number of upstream channels is reduced whenever an attenuation change causes a
modem to maximize its transmit power where the modem cannot reach the expected
input power level at the CMTS.
Load balancing policies
A load balancing policy is a set of rules that govern load balancing operations. There
are two types of rules that the CMTS uses when load balancing takes place: basic
rules and execution rules. The CMTS uniquely identifies each load balancing policy
using a policy ID.
A basic rule sets the time of day when the CMTS is to perform load balancing. The
configured time will be during predictable traffic periods when congestion over the
downstream and upstream channels is most likely to occur. Multiple basic rules are
supported in a load balancing policy. A basic rule is a DOCSIS specification
requirement.
An execution rule defines the specific traffic conditions or parameters that enable the
load balancing algorithms of the CMTS regardless of the time of day (as set in a basic
rule). The execution rule can specify when load balancing is to occur and to which
modems, the time interval, or how often certain modems participate in DCC or DBC
load balancing operations, as well as other parameter settings such as static and
Casa Systems
Static vs. dynamic load balancing
dynamic load balancing. Unlike basic load balancing rules, execution rules are
vendor-specific and are not mandated by the DOCSIS specification.
At CM registration time, the CMTS assigns a load balancing policy ID to the CM

based on the default policy of the general load balancing group or the restricted load
balancing group for this CM.
Static vs. dynamic load balancing
The CMTS performs load balancing in one of two ways, or a combination of the two:
Static load balancing takes place when a CM sends its initial ranging request message
to the CMTS. For DOCSIS 1.0, 1.1 and 2.0 modems, the CMTS responds with a
ranging response (RNG-RSP) message that includes either a Downstream Frequency
Override or an Upstream Channel ID Override field that instructs the CM which
channels it should use. For DOCSIS 3.x modems, when a CM sends its registration
request (REG-REQ) messages, the CMTS responds with a registration response
(REG-RSP) message to instruct the CM to select the channels.
Dynamic load balancing moves CMs among upstream and downstream channels
within the same service group when the difference between two channels exceeds a
defined percentage. The CMTS will use dynamic channel change messages (DCC) to
move CMs with single upstream/downstream channels, and dynamic bonding change
(DBC) messages to move CMs with bonded upstream/downstream channels to
different bonding groups.
Note: For DOCSIS and EuroDOCSIS 3.x modems, the dynamic load
balancing software generates a downstream channel set with a minimum load
to fit the modem‘s receive channel profile (RCP). This prevents rejection of the
new channel set so that load balancing is not canceled when the assigned
modem is under load.
The CMTS does not move modems to disconnected (idle) downstream channels
where there are no registered online CMs.
Casa Systems
Applying exclusion lists
Applying exclusion lists
An exclusion list disables one or more modems from load balancing across CMTS
downstream and upstream channels in situations where it is not feasible to load
balance particular modems. For example, there may be cases where an older DOCSIS
1.0 or 2.0 modem from a specific vendor may not be a good candidate for load
balancing, as well as modems that process particular types of traffic where moving
those modems to other channels introduces risks. CMs in the exclusion list are
specified by MAC address.
Terminology covered in this chapter

burst descriptor — The single description of a burst type having up to twelve burst
description parameters, such as modulation type, forward error correction, scrambler,
preamble, long/short data, and others.
burst profile — The set of burst descriptors carried by UCD packets in the MPEG-2
transport stream as sent by the CMTS to a target CM. A burst profile supports up to
five upstream burst types to describe an upstream channel.
burst type — One of five possible upstream burst types that describe an upstream
channel as carried in the burst profile portion of a UCD packet. Possible upstream
burst types include initial-ranging, periodic-ranging, request, long data, and short data.
Each burst type is one burst descriptor with up to twelve parameters.
cable modem service group (CM-SG) — The combination of upstream (US-SG) and
downstream channels (DS-SG) at the CMTS to which a CM has access.
channel bonding — The DOCSIS 3.x CM feature that allows the CMTS to link a
group of channels based on the number of channels supported by the target CM. When
the CMTS creates a bonding group for a CM that has four physical downstream
receivers, the modem can receive over the four channels simultaneously over a
downstream channel set.
DOCSIS fiber node — A CM service group (CM-SG) made up of the upstream

service group (US-SG) and the downstream service group (DS-SG).
Casa Systems
downstream channel — The CMTS 50-MHz through 1-GHz channel over which the
CMTS sends MPEG-2 transport streams over the cable infrastructure to the one more
distribution areas. The downstream channel operates with the forward combiner to
deliver modulated content on carrier signals to target cable subscribers.
downstream service group (DS-SG) — The group of CMTS downstream channels

over which MPEG-2 transport streams are modulated on carrier signals to a target
CM; the group of downstream channels to which a CM has access.
dynamic channel change (DCC) — The MAC management message from the CMTS
that instructs a CM to move from one channel to another within the CM service group
(CM-SG).
dynamic bonding change (DBC) — The MAC management that moves DOCSIS 3.x
modem downstream service flows to different channels in the modem’s receive
channel set (RCS). DBC also moves D3.0 upstream service flows to different
channels in the current transmit channel set (TCS).
dynamic host control protocol (DHCP) — The IETF protocol for dynamically
assigning an IPv4 or IPv6 address to a requesting device, such as a CM. The CMTS
forwards a DHCP request from a CM to a dedicated DHCP server. The CMTS then
forwards the DHCP response message containing the IP address to the requesting CM.
dynamic load balancing — The CMTS traffic balancing method that moves CMs
among upstream and downstream channels within the same service group after their
initial difference between two channels exceeds a defined percentage.
exclusion list — A list of one or more modems that the CMTS purposely excludes
from load balancing across CMTS downstream and upstream channels.
execution rule — A load balancing metric the defines the specific traffic conditions or
parameters that trigger load balancing operations at the CMTS.
fiber node — The physical cable infrastructure that links the cable headend to one or
more geographical distribution areas.
forward combiner — The cable headend device that places modulated digital content,
such as the downstream channel lineup, onto CMTS downstream carrier signals to
cable distribution areas.
Casa Systems
forward channel lineup — Modulated digital content, such as local and satellite
television, news and sports feeds, and streaming video, that is carried on CMTS
downstream MPEG-2 transport streams to cable distribution areas.
forwarding engine — The set of CMTS processes that reside between the CMTS
network side interface (NSI) and radio frequency interface (RFI) for controlling how
CMTS traffic is forwarded “through” one or more MAC domains or routed “to”
network destinations.
general load balancing group (GLBG) — The complete set of upstream and
downstream channels in a CM service group (CM-SG) that are available for load
balancing operations.
initial ranging — The upstream burst type that is carried by the upstream channel
descriptor in the MPEG-2 transport stream that enables a CM to request an upstream
transmission grant from the CMTS so that the modem can register with the CMTS.
interval usage code (IUC) — The CMTS-assigned code that schedules the initial
ranging interval in the upstream time line to the CMTS. Once a transmission interval
is set, the MAC domain then adjusts CM frequency, power, and delay for two-way
communication. IUCs are carried by MAP packets in the MPEG-2 transport stream.
load balancing — The CMTS process that enables modems to move from one channel
to another so that traffic load is redistributed for improved bandwidth utilization and
reduced consumption of CMTS resources. See dynamic channel change and dynamic
bonding change.
MAC domain — The Open Systems Interconnect (OSI) Layer 2 device through which
radio frequency traffic is forwarded to CMs over downstream channels, and received
over CMTS upstream channels. The minimum MAC domain contains one upstream
and one downstream channel. The Casa CMTS is an integrated Layer 2 MAC domain
and a Layer 3 physical routing device supported by an internal forwarding engine.
Casa CMTS systems can support up to 64 MAC domains. (See Chapter 8, “DOCSIS
MAC interface.”)
MAC domain cable modem service group (MD-CM-SG) — All CM upstream and
downstream channels originating from a single MAC domain.
Casa Systems
MAC domain descriptor (MDD) — The DOCSIS 3.x packet carried by the MPEG-2
transport stream that defines the receive channel set for CMs that support multiple
receivers and transmitters, such as a D3.0 CM with four downstream and four
upstream channels.
MAC management message (MMM) — The CMTS message that carries the MPEG-2
transport stream that includes MAC time synchronization packets, UCD and MAP
packets, and the MDD.
MAP — The packet carried by the MPEG-2 transports stream that instructs the
modem when to transmit over an upstream timeline by specifying when time-zero (t0)
begins. The MAP carries a 32-byte field to indicate the service identifier (SID) to
declare “who” is transmitting, the interval usage code (IUC) that indicates “what”
type of transmission, and the t0 timing offset to indicate “when” to begin the upstream
transmission interval from t0 on the timeline.
minislot — A series or group of time components that make up one upstream time
interval. These intervals vary in size starting at time-zero (t0) until the end of the
interval where t0 begins again. Time-division multiplexing (TDM) scheduling sets
both long and short intervals in the timeline where the interval size is based on traffic
conditions. Each minislot within each interval is 6.25 microseconds.
MPEG-2 transport stream — The 188-byte packet carried in the MAC management
message that includes MAC time synchronization packets, UCD and MAP packets,
and the MDD. An MPEG-2 transport stream with a program identifier (PID) of 1FEE
indicates that the stream originates from a MAC domain. The MPEG-2 transport
stream carries modulated digital content signals to cable distribution areas.
network side interface (NSI) — The OSI Layer 3 routing side of the CMTS. The NSI
supports the IP routing protocols such as OSPF, RIP, BGP, and IS-IS to support
routing between neighbor routers. The CMTS uses 10/100 Fast Ethernet for
out-of-band remote management, as well as GigE and 10GigE interfaces for voice,
data, and video traffic routing. The NSI uses the CMTS forwarding engine to route
network protocol traffic to network destinations.
QAM64 — A 64-state modulation method that combines phase angle and amplitude
signals over downstream channels. QAM64 modulation over 6 MHz channels
operates at 30 Mbps.
Casa Systems
QAM256 — A 256-state modulation method that combines phase angle and amplitude
signals over downstream channels. QAM256 modulation over 6 MHz channels
operates at 42 Mbps.
radio frequency interface (RFI) — The combination of at least one upstream and one
downstream channel to form the DOCSIS MAC domain. The CMTS provides both
upstream and downstream interfaces for transmission and receipt of digitized content
and data services over fiber network trunks and coaxial cable to and from the
subscriber distribution areas.
ranging backoff algorithm — The CMTS process that tells a CM how long to wait
before retransmitting another initial ranging request. The ranging backoff algorithm
reschedules and increases initial ranging transmissions at random intervals to provide
a better opportunity for CMs to avoid collisions with other modems. Ranging backoff
values are expressed as an exponential value to set the number of ranging
opportunities per retry, such 23, 24, 25, and 26.
receive channel set (RCS) — The downstream channels over which a CM receives
traffic from the MAC domain. The MAC domain descriptor (MDD) in the MPEG-2
transport stream informs the modem about the receive-channel configuration and the
receive channel set to be used by that modem.
restricted load balancing group (RLBG) — A subset of channels in a modem’s CM

service group; the channels available for load balancing are interactively selected and
saved in the CMTS running configuration file. A QAM channel can be included in up
to 12 RLBGs per QAM and DOCSIS MAC domain configuration.
service flow — A MAC layer transport service that provides unidirectional transport
of packets from the upper layer to the RF layer along with shaping, policing, and
prioritizing of traffic according to QoS traffic.
service group (SG) — The group of downstream channels (DS-SG) over which a CM
receives traffic from the MAC domain, or the group of upstream channels (US-SG)
over which the CM transmits to the CMTS. The combination of both upstream and
downstream service groups is known as the CM service group (CM-SG) or DOCSIS
fiber node.
service identifier (SID) — The 14-byte portion of the 32-byte packet carried in the
MAP that identifies a particular CM attempting to transmit upstream to the CMTS.
Casa Systems
Configuration examples
static load balancing — The CMTS traffic balancing method that instructs the CM
which channels it should use after initial ranging. For DOCSIS 3.x modems, when a
CM sends its registration request (REG-REQ) messages, the CMTS responds with a
registration response (REG-RSP) message to instruct the CM to select the channels.
transmit channel set (TCS)— The CMTS 5–42 MHz upstream channels over which a
CM transmits traffic to the CMTS MAC domain. Upstream channel information is
determined by the UCD and MAP packets carried in the MPEG-2 transport stream
from the CMTS.
trivial file transfer protocol (TFTP) — The IETF protocol used by the CMTS for
transferring a CM configuration file from a dedicated TFTP server to a target CM,
allowing the modem to properly configure itself for two-way communication with the
CMTS.
upstream channel — The CMTS 5–42 MHz channel over which a CM transmits
traffic to the CMTS over a transmit channel set (TCS). Upstream channel information
is determined by the UCD and MAP packets carried in the MPEG-2 transport stream
from the CMTS. (See Chapter 21, “Upstream interface.”)
upstream channel descriptor (UCD) — The packet carried in the MPEG-2 transport
stream that describes the upstream channels over the which a CM transmits to the
CMTS. Each UCD describes an upstream channel with frequency, width, and burst
profile (set of burst descriptors). Each UCD has one associated MAP that instructs the
modem on “when” to transmit over an upstream timeline.
upstream service group — The group of CMTS upstream channels over which a CM
transmits traffic to the CMTS over a transmit channel set (TCS); the group of
upstream channels to which a CM has access.
Configuration examples
This section contains two sample configuration files: basic and general. The basic
configuration allows the CMs to register. The general configuration demonstrates how
to configure advanced features, such as Spectrum Management, Channel Bonding,
and Load Balancing.
Casa Systems
Basic configuration
Basic configuration
The following sample configuration provides basic settings for registering CMs.
hostname CASA-CMTS
interface eth 0
ip address 192.168.2.215 255.255.255.0
interface qam 0/0

no shutdown
no channel 0 shutdown
power 580
interface qam 0/1

no shutdown
power 580
interface qam 0/2

no shutdown
power 580
interface qam 0/3

no shutdown
power 580
interface gige 0
ip address 192.168.3.106 255.255.255.0
ip igmp
no shutdown
route net 0.0.0.0 0 gw 192.168.3.7
igmp client version 2

interface upstream 1/0
no shutdown
Casa Systems
General configuration
no logical-channel 0 shutdown
no shutdown
no shutdown
no shutdown
no shutdown
no shutdown
no shutdown
no shutdown
channel-utilization-interval 10
interface ip-bundle 1
ip address 192.168.7.1 255.255.255.0
cable helper-address 192.168.3.7
interface docsis-mac 1
no shutdown
ip bundle 1
downstream 1 interface qam 0/0/0
upstream 1 interface upstream 1/0/0
The following sample configuration includes spectrum management, channel

bonding, and load-balancing configuration.
hostname CASA-CMTS
interface eth 0
ip address 192.168.2.215 255.255.255.0
spectrum rule 35
action modulation frequency channel-width
channel-width 3200000 1600000
snmp traphost 192.168.0.196 community public version 2
Casa Systems
interface qam 0/0

no shutdown
power 580
interface qam 0/1

no shutdown
power 580
interface qam 0/2

no shutdown
power 580
interface qam 0/3

no shutdown
power 580
interface gige 0
ip address 192.168.3.106 255.255.255.0
ip igmp
no shutdown
route net 0.0.0.0 0 gw 192.168.3.7
interface ip-bundle 1
ip address 192.168.6.1 255.255.255.0
ip address 122.8.74.1 255.255.254.0 secondary
cable helper-address 192.168.3.7
service group 1
qam 0/0/0
qam 0/0/1
qam 0/0/2
qam 0/0/3
qam 0/1/0
Casa Systems
qam 0/1/1
qam 0/1/2
qam 0/1/3
upstream 1/0.0
upstream 1/1.0
upstream 1/2.0
upstream 1/3.0
upstream 1/4.0
upstream 1/5.0
upstream 1/6.0
upstream 1/7.0
no shutdown
ip bundle 1
upstream 1 interface upstream 1/0.0

spectrum-rule 35
no shutdown

no shutdown

no shutdown

no shutdown
Casa Systems

no shutdown

no shutdown

no shutdown

no shutdown
Casa Systems
2-1
Chapter 2. Application classes and

policies
Application class and policy commands

description
Application classes are used in association with cable admission-control for
upstream or downstream traffic. Application policies are used in defining include
factors for application classes and in association with multicast group admission
control.
Configuration summary
Table 2-1 lists and briefly describes the objects related to application classes and
policies.
Table 2-1. Policy objects
Object name Description
application Configures application classes and policies.

class Configures application classes.
policy Configures application policies.
Casa Systems
application
application
Purpose
The application command configures application classes and policies. The two
application objects are described in the following sections.
Modes
(config)#
(conf-app-class <index>)#
(conf-app-policy <id>)#
Syntax
[no] application class <1:16>
[no] application policy <1:32>
Properties
Property name Description
class <1:16> Sets an application class.
Example:
CASA(config)# application class 1

CASA(conf-app-class 1)# exit
CASA(config)# no application class 1
policy <1:32> Sets an application policy.
Example:
CASA(config)# application policy 12

CASA(conf-app-policy 12)# exit
CASA(config)# no application policy 12
Casa Systems
Application classes and policies 2-3
class
class
Purpose
The application class command defines application class properties. Each application
class is a service that defines the rules for matching service flows to that application
class for bandwidth calculation prior to cable admission-control. An application
class can be assigned in only one direction, downstream or upstream. This includes
schedule types for the following:
• Upstream — Best Effort, (Non)-Real-Time Polling Service, Unsolicited Grant

Service (UGS), UGS with Activity Detection (UGS-AD)
• PCMM with application identifier or gate-priority
• PacketCable with emergency call or normal call
• Cable service class name
Up to 16 unique application classes are supported in the CMTS configuration for

classifying different flows. Each application class can be assigned a unique bandwidth
percentage on upstream or downstream channels (with upstream being the default).
This bandwidth percentage can be exclusive or non-exclusive. With the exclusive
bandwidth percentage, one application class uses all the allocated percentage. The
non-exclusive bandwidth percentage provides additional resources whenever the
exclusive bandwidth is insufficient to handle the service flows belonging to the
application class. If both are used, they cannot add up to more than 100%.
An application class needs to have a defined name and can have up to eight child
classes that can be configured for availability when the parent application class
reaches its maximum bandwidth. A parent include rule statement must precede
adding a child class. A child class preempts another one from the same parent using
the exclusive and non-exclusive bandwidth percentage settings, although the sum of
all child class exclusive settings cannot exceed that of the parent. For emergency and
normal calls, one child class can be set for normal calls with exclusive set to zero and
non-exclusive set to the maximum normal calls allowed, while another child class can
be set for emergency calls with exclusive set to the maximum voice calls allowed and
non-exclusive set to zero.
Casa Systems
class
Mode
(conf-app-class <1:16>)#
Syntax
name <name>
[no] child-class <1:8> {name <name> | downstream-bandwidth exclusive
<0:100> [non-exclusive <0:100>] | include <val> |
upstream-bandwidth exclusive <0:100> [non-exclusive <0:100>]}
downstream-bandwidth exclusive <1:100> [non-exclusive <0:100>]
[no] include {BE | multicast application-id <1:65535>... | packetcable
[emergency | normal] | pcmm {app-id <0:65535>... | gate-priority
<0:7>...} | sched-type [be] [nrtps] [rtps] [ugs] [ugs-ad] |
service-class <name>...}
upstream-bandwidth exclusive <0:100> [non-exclusive <0:100>]
Properties
name <name> Required application class (or child application class)

name, up to 15 characters.
Example:
CASA(conf)# application class 1

CASA(conf-app-class 1)# name APPCLASS1
Casa Systems
class
Properties (continued)
child-class <1:8> {name Child class ID, which requires a name and an
<name> | include rule set for the parent class (see the include
downstream-bandwidth property). There can be up to eight child classes per
exclusive <0:100> application class.The child should have a related
[non-exclusive <0:100>] | include rule and its own bandwidth values, with the
include <val> | limitation that the sum of exclusive bandwidth
upstream-bandwidth percentages of all the children cannot exceed that of
exclusive <0:100> the parent.
[non-exclusive <0:100>]}
Example:
CASA(conf-app-class 1)# include BE

CASA(conf-app-class 1)# child-class 1
name APPCLASS1.1
include pcmm app-id 1
upstream-bandwidth exclusive 10
CASA(conf-app-class 1)#
no child-class 1
Casa Systems
class
downstream-bandwidth Downstream bandwidth exclusive range that is the

exclusive <1:100> critical threshold for the downstream throughput
[non-exclusive <0:100>] resource, or the percentage of throughput reserved
exclusively for this class or child class. The optional
non-exclusive range is the percentage of bandwidth
over and above the exclusive share that can be used
by this class or child class. The non-exclusive range
can be used by other classes as specified. The
exclusive and non-exclusive ranges cannot add up to
more than 100%. If non-exclusive is omitted for the
parent class, it assumes the remaining percentage
from the exclusive range. If non-exclusive is omitted
for the child class, it assumes the exclusive value
from the parent.
The child class bandwidth definition must have a

matching direction (upstream or downstream)
defined for the parent. If a direction for the parent is
omitted, upstream is the default.
Example:
downstream-bandwidth exclusive 16
non-exclusive 20
Casa Systems
class
include {BE | multicast Binds a rule to the application class or child class.
application-id <1:65535>... Required for a parent class when defining child
| packetcable [emergency | classes. The rules, which are evaluated in the order
normal] | they are defined, are the following:
pcmm {app-id <0:65535>... |
gate-priority <0:7>...} | • BE — Best effort (BE) service flow with a
sched-type [be] [nrtps] non-zero committed information rate (CIR).
[rtps] [ugs] [ugs-ad] | • multicast application-id <0:65535> — Applica-
service-class <name>...} tion policy ID or space-separated IDs of the mul-
ticast service flow, up to eight IDs.
• packetcable [emergency | normal] — Packet-
Cable call class, with the optional emergency or
normal service type. The emergency service pre-
empts the normal service once the parent class
reaches its maximum bandwidth. For emergency
calls, the exclusive threshold should be set to the
maximum voice calls allowed and the non-exclu-
sive threshold set to zero.
• pcmm {app-id <0:65535> | gate-priority <0:7>}
— PacketCable Multimedia (PCMM), with the
application ID or gate priority. The parent class
can list the child application policy IDs separated
by spaces, up to eight. Gate priority can also take
up to eight values. Set a low gate priority value for
priority services such as multicast streaming.
• sched-type {be | nrtps | rtps | ugs | ugs-ad} —
Quality of service (QoS) class schedule type, as
best-effort (be), non-real-time polling (nrtps),
real-time polling (rtps), Unsolicited Grant Service
(ugs), or Unsolicited Grant Service with Activity
Detection (ugs-ad), which can be combined.
• service-class <name> — Cable service class
name or names, space-separated up to 10.
Example:
CASA(conf-app-class 1)# include pcmm

app-id 0 1 2 3 4 5 6 7
no include pcmm app-id 0
Casa Systems
class
upstream-bandwidth Upstream bandwidth exclusive range that is the

exclusive <0:100> critical threshold for the upstream throughput
[non-exclusive <0:100>] resource, or the percentage of throughput reserved
exclusively for this class or child class. The optional
non-exclusive range is the percentage of bandwidth
over and above the exclusive share that can be used
by this class or child class. The non-exclusive range
can be used by other classes as specified. The
exclusive and non-exclusive ranges cannot add up to
more than 100%. If non-exclusive is omitted for the
parent class, it assumes the remaining percentage
from the exclusive range. If non-exclusive is omitted
for the child class, it assumes the exclusive value
from the parent.
The child class bandwidth definition must have a

matching direction (upstream or downstream)
defined for the parent. If a direction for the parent is
omitted, upstream is the default.
Example:
upstream-bandwidth exclusive 16
non-exclusive 20
Examples
The following example shows an application class with exclusive and non-exclusive
downstream bandwidth thresholds adding up to 30%. The subsequently defined child
class combined bandwidths exceeded this amount, resulting in an error.
CASA(conf-app-class 10)# show application class 10

application class 10
name class1
downstream-bandwidth exclusive 10 non-exclusive 20
child-class 1 name 10.1
child 1 : accept 0, deny 0, dcc 0, force free 0
total : accept 0, deny 0, dcc 0, force free 0
Casa Systems
class
CASA(conf-app-class 10)# child-class 1 downstream-bandwidth

exclusive 2 non-exclusive 30
error, child-class total threshold 32 exceeded the limitation of
parent-class's total 30
In the following example, the parent class thresholds add up to 30%, the individual
child class thresholds add up to no more then 30%, and the totaled child exclusive
thresholds add up to no more than the 10% defined for the parent. This is acceptable.
The non-exclusive thresholds do not have this limitation and can be higher. The count
values show that no modem has yet come online.
CASA# show application class 10

application class 10
name class1
child-class 1 downstream-bandwidth exclusive 2 non-exclusive 28
In the following example, two identical application classes are defined. The CMTS
evaluates the include rules in order and picks the service-class definitions from the
first class. In so doing, it pegs the accept count to 14 (the two downstream flows times
the seven modems coming online) for the first application class only, and not for the
second. The additional show cable modem qos output shows the upstream and
downstream service-classes for one of the modems that were used in the evaluation.
Casa Systems
class
CASA# show application class

application class 1
name wave1
include service-class STMrule_DWN.2 STMrule_DWN.1
include BE
child-class 1 name Wave3_CC_1
child-class 1 include pcmm app-id 1 5
child-class 2 downstream-bandwidth exclusive 20
child-class 3 include pcmm app-id 3
application class 2
name Wave3
include service-class STMrule_DWN.2 STMrule_DWN.1
include BE
child-class 3 include pcmm app-id 3
CASA# show cable modem qos

Sfid Dir Curr Sid Sched Prio ... Throughput ServiceClassName
State Type
Mac Addr : 0014.04dd.6586
49165 US act 15 BE 0 ... ... STMrule_UP.2
49168 US act 16 BE 0 ... ... STMrule_UP.1
57358 DS act N/A UNDEF 0 ... ... STMrule_DWN.2
57359 DS act N/A UNDEF 0 ... ... STMrule_DWN.1
Casa Systems
class
Other related commands
cable traffic-policy
Implements Subscriber Traffic Management (STM) to allow CMTS users to monitor

and enforce upstream and downstream transmission rates for subscribers. (See the
cable traffic-policy command in Chapter 4, “Cable commands.”)
Related show commands
show application class
Shows the configured application classes. See the “Examples” above. The child and
total accept and deny counts at the bottom of the output are for currently active calls
(that can be synced with admission-control).
show pcmm {gateid <0:0xffffffff> {clsfy spec | spec | traffic spec} |

multicast | ps server}
Shows the PacketCable Multimedia (PCMM) configuration, if any. The gateid value
to obtain the classifier, gate specification and traffic profile output can be derived
from the multicast output. The ps server identifies the Common Open Policy Service
(COPS) server address, port, and version, as set by the cops pdp-ip command.
CASA# show pcmm multicast

GateID SubscriberID Multicast-Session SharedResourceID
CASA# show pcmm ps server

IP Address Port PSID Version
24.114.21.102 56275 null 5.0
Casa Systems
policy
policy
Purpose
The application policy command defines application policy properties. An

application policy is an object that stores application attributes, such as limiting
replication for multicast group sessions. Up to 32 application policies are supported.
There are three ways to trigger multi-link trunking (MLT) for dynamic channel
changes (DCCs) using an application policy:
• Enable limit replication, create a session on channel A, let a D2.0/3.0 CM get

online on channel B (if a D3.0 CM, the channel set should not include channel A),
and dynamically join the same session.
• Enable limit replication, set the multicast max channel-util threshold, let the
channel’s utilization exceed the threshold, and dynamically join the session on
these channel(s).
• Enable limit replication, set the multicast switch over time in seconds, leave a
session for a D2.0 CM, and switch to an idle channel.
Mode
(conf-app-policy <1:32>)#
Syntax
[no] limit replication [override]
max iptv channel <0:2>
[no] monitor threshold min-rate-ratio <1:100>
Casa Systems
policy
Properties
limit replication Limits replication, with the optional override modifier

[override] to limit replication overriding.
Example:
CASA(conf)# application policy 1

CASA(conf-app-policy 1)#
limit replication override
CASA(conf-app-policy 1)#
no limit replication override
max iptv channel <0:2> Sets the optional maximum Internet Protocol
Television (IPTV) channels the CM is allowed to join,
with 0 disabling the feature.
Example:
CASA(conf-app-class 1)# max iptv

channel 0
monitor threshold Sets the optional monitor threshold to the minimum

min-rate-ratio <1:100> rate ratio, as a percentage of the guaranteed rate
defined in the QoS.
Example:
CASA(conf-app-policy 12)# monitor

threshold min-rate-ratio 100
CASA(conf-app-policy 12)# no monitor
threshold min-rate-ratio
Example
The following commands configure identifying multicast sessions that match group
address 230.0.1.0/24 as limited multicast sessions. (See also Chapter 12, “Multicast
cable operations.”)
CASA(config) application policy 1234

CASA(conf-app-policy 1234) limit replication
CASA(conf-app-policy 1234) max iptv channel 2
Casa Systems
policy
CASA(conf-app-policy 1234) exit

CASA(config)# multicast group config 1
CASA(conf-grp-config 1) source-address 0.0.0.0/0
CASA(conf-grp-config 1) group-address 230.0.1.0/24
CASA(conf-grp-config 1) qos-id 1
CASA(conf-grp-config 1) exit
CASA(config) multicast group qos 1 IPTV aggregate max-sess 10 app-id 1
show application policy
Shows the application policies configured in the running configuration.
CASA(config)# show application policy
application policy 1
show multicast replication
Shows multicast replication, including for type DSG, DEF, and IPTV.
CASA(config)# show multicast replication

Multicast Session
Module ReplID DSID(hex) SFID Type Chan(s)
<224.0.100.33::0.0.0.0>
qam 13 2 80002* 2 DSG 13/1/0
qam 13 1 80001 1 DSG 13/0/35
<224.0.100.34::192.30.3.30>
qam 13 4 80004* 4 DSG 13/1/0
qam 13 3 80003 3 DSG 13/0/35
<224.0.100.35::0.0.0.0>
qam 13 8 80008* 8 DEF 13/1/1
qam 13 6 80006* 6 DEF 13/1/0
qam 13 7 80007* 7 IPTV 13/1/1
qam 13 5 80005* 5 IPTV 13/1/0
…
Casa Systems
3-1
Chapter 3. Baseline Privacy Interface
BPI commands description

The CMTS provides commands that enforce the Baseline Privacy Interface (BPI) and
Baseline Privacy Interface Plus (BPI+) security protocols running between the CMTS
and the cable modems (CMs). BPI is defined as a set of extended services within the
DOCSIS MAC sub-layer that gives subscribers data privacy across the RF network,
encrypting traffic flows between the CMTS and CM.
BPI authentication protocols protect CM data traffic by preventing upstream and

downstream eavesdropping by other users who are connected over the same cable.
Traffic between the CMTS and the CMs is encrypted using an encapsulation protocol,
as well as a key management protocol called Baseline Privacy Key Management
(BKPM) for processing authentication and authorization key exchanges between the
CM and CMTS.
BPI+ is required on all DOCSIS 1.1 (and later) compliant CMs. Earlier CMs use BPI.
Note: Enabling BPI reduces performance and can cause fluctuations in the
upstream throughput rates.
Casa Systems
BPI commands description
Table 3-1 lists and briefly describes the objects related to BPI and BPI+.
Table 3-1. BPI and BPI+ objects
cable privacy Sets the privacy mode for, and enforces, BPI.
cable sa-des-tlvlen-2 Sets the security association TLV length as required by
some BPI-authenticated CMs.
privacy hotlist Adds entries to the privacy hotlist to mark a CM’s or
manufacturer’s certificate as distrusted.
shared-secondary-secret Configures an authentication shared secondary encryption
key.
shared-secret Configures an authentication shared primary encryption
key.
Casa Systems
Baseline Privacy Interface 3-3
cable privacy
cable privacy
Purpose
The cable privacy command sets the privacy mode for, and enforces, BPI or BPI+.
The bpi-enforce and the bpi-plus-enforce parameters can be set concurrently in the
CMTS configuration, because each setting operates on different modem types.
Note: When the bpi-plus-enforce property is enabled, BPI CMs running

DOCSIS 1.1 or higher that are not running BPI+ cannot register with the
CMTS. However, non-BPI CMs are allowed to register.
Mode
(config)#
Syntax
[no] cable privacy 40-bit-des
[no] cable privacy add-certificate {manufacturer | root} <string>
[no] cable privacy bpi-enforce [mandatory]
[no] cable privacy bpi-plus-enforce [mandatory]
[no] cable privacy test-edrca-certificate
Properties
40-bit-des Sets the privacy mode to 40-bit Data Encryption

Standard (DES) encryption. CMs that do not support
40-bit DES encryption cannot complete BPI. (See
also the cable sec encryp_alg_priority command.)
Example:
CASA(config)# cable privacy 40-bit-des

CASA(config)# no cable privacy
40-bit-des
Casa Systems
cable privacy
add-certificate Adds a manufacturer or root CA certificate to the list

{manufacturer | root} of trusted certificates, defined by the string, enclosed
<string> in quotes if space-separated. The maximum number
of CA certificates is 200.
Example:
CASA(config)# cable privacy

add-certificate manufacturer
35c146353431a541463b4133734393833337314
FEF03A8BC7A441313134749A0A592C9C6683141
add-certificate manufacturer
35c146353431a541463b4133734393833337314
FEF03A8BC7A441313134749A0A592C9C6683141
bpi-enforce [mandatory] Enforces BPI-authenticated CMs and prohibits traffic

for non-BPI authenticated CMs. Data is not
forwarded before a BPI-enabled CM completes BPI
initialization. The mandatory option prevents all
non-BPI CMs from registering with the CMTS. If
omitted, non-BPI CMs will register and come online
with the CMTS.
Example:
CASA(config)# cable privacy bpi-enforce

CASA(config)#
no cable privacy bpi-enforce
bpi-plus-enforce Enforces BPI-plus for DOCSIS 1.1 or later CMs.

[mandatory] When enabled, CMs running DOCSIS 1.1 or higher
that are not running BPI-plus are rejected. Omitting
the mandatory option prevents BPI CMs from
registering; only BPI+ CMs will register.
Example:

bpi-plus-enforce mandatory
bpi-plus-enforce mandatory
Casa Systems
cable privacy
test-edrca-certificate Uses a EuroDOCSIS Root Certificate Authority

(EDRCA) for test purposes.
Example:

test-edrca-certificate
CASA(config)#
no cable privacy test-edrca-certificate
interface docsis-mac
privacy
Configures Key Encryption Key (KEK) or Traffic Encryption Key (TEK) lifetime on
a MAC domain interface for BPI. Each lifetime is from 1–604800 seconds. (See the
DOCSIS MAC interface privacy property.)
CASA(config)# interface docsis-mac 1

CASA(conf-if-mac 1)# privacy tek life-time 300
qos-profile
The qos-profile command includes a property for specifying whether BPI is used in a
quality of service (QoS) profile, either true or false.
CASA(config)# qos-profile 1 7 1000000 1000000 1000000 true 65535
show cable modem
Shows the possible BPI MAC state status values on CMs:
• init(r1) — An initial ranging request was sent by the CM to the CMTS.
Casa Systems
cable privacy
• init(r2) — The CMTS received an initial ranging request from the CM. The
CMTS responded and returned RF power information, timing offset, and
frequency adjustments to the CM. The CM and CMTS link is still in the ranging
state, and ranging is not complete. Check the RF attenuations if initial ranging
remains stuck. Use the debug cable ranging command for information.
• init(ov) — CMTS is static load balancing and is using the upstream channel ID
override and/or downstream frequency override to move the modem to new
channel. Check the modem power if stuck in this state.
• init(rc) — CM ranging to the CMTS completed. Check the cable helper address
configuration and IP connectivity to the DHCP server. Use the debug cable dhcp
command for information. Note: It is also possible that the upstream is at capacity
and has no additional bandwidth for the CM to finish registration and come
online. If this is the case, make sure load balancing is enabled.
• init(ua) — Upstream channel adjustment (for DOCSIS 3.0 modems).
• init(d) — The CMTS received the DHCP discover message; the first IP broadcast
packet was received from the CM.
• init(i) — The CM received the DHCPOFFER reply from the DHCP server, but
the CM has not yet replied with a DHCPREQUEST message, nor has it sent an IP
packet with its assigned IP address. It is possible that the CM received the
DHCPOFFER reply from the DHCP server, but the reply might have invalid
options for that particular CM.
• init(e) — Early authentication and encryption started (D3.0 modems). Check the
modem certificate if stuck in this state.
• init(t) — Time-of-day (TOD) exchange on the configuration file download has
started.
• init(o) — The CM began downloading the DOCSIS configuration file from the
provisioning server. If the CM remains in this state, the download failed, possibly
due to incorrect or corrupt data, inability to reach the TFTP server (such as wrong
file permissions), or invalid or missing configuration parameters.
• init(r) — The CMTS received a register-request from the CM, but has not yet
received a reg-ack. If stuck, check the modem config file. Use the debug cable
registration command to debug the registration request received.
• init(bpi) — Starts baseline privacy. If stuck in this state, check the modem
certificate and ensure that the CM is synchronized with the BPI server.
Casa Systems
cable privacy
• resetting — The CM is being reset; the registration process is restarting.
The following are non-error status conditions:
• cc(r1) — The CM previously registered and was online, but the CMTS sent a
Dynamic Channel Change (DCC) or Upstream Channel Change (UCC) request
message to the CM. The CM started moving to the new channel, sending an initial
ranging request on the new downstream or upstream channel to the CMTS. At the
MAC layer, the CM is not yet passing traffic to the new channel and is considered
in the off-line state. This state does not trigger the flap-list counters.
• cc(r2) — This state normally follows cc(r1) and indicates that the CM finished its
initial ranging on the new channel, and is currently performing continuous
ranging on the new channel. At the MAC layer, the CM is not yet passing traffic to
the new channel and is considered in the off-line state. This state does not trigger
the flap-list counters.
• offline — The CM is detected as off-line, disconnected, or powered off.
• online — The CM has registered; the CM is ready to pass data on the network.
• online(d) — The CM is registered. However, network access for CPE devices
using this CM was disabled by the DOCSIS configuration file. The CMTS
continues to communicate with the CM using DOCSIS messages and IP traffic
(such as SNMP) but the CM does not forward traffic to or from the CPE devices.
Note: If BPI was enabled in the DOCSIS configuration file sent to the CM, the
CM is using BPI encryption unless other messages indicate that the BPI
negotiation and key assignments failed.
• online(pk) — BPI is enabled and the key-encrypting key (KEK) is assigned.
• online(pkd) — BPI is enabled and the KEK is assigned, but network access for
CPE devices using this CM was disabled.
• online(pt) — BPI is enabled and the traffic-encrypting key (TEK) is assigned.
• online(ptd) — BPI is enabled and the TEK is assigned, but network access for
CPE devices using this CM was disabled.
• expire(pk) — BPI is enabled and the KEK was assigned, but the current KEK
expired before the CM could successfully renew a new KEK value.
• expire(pke) — Equivalent to the online(d) and expire(pk) states except that
network access for CPE devices using this CM was disabled.
Casa Systems
cable privacy
• expire(pt) — BPI is enabled and the TEK was assigned, but the current TEK
expired before the CM could successfully renew a new TEK value.
• expire(ptd) — Equivalent to the online(d) and expire(pt) states except that
network access for CPE devices using this CM was disabled.
The following are error status conditions:
• bpi(wait) — BPI wait state in which the affected modem is flapping and cannot
fully come back up, thus not forwarding data. If stuck in this state, reboot the
modem.
• reject(pk) — The KEK assignment is rejected and BPI encryption was not
established.
• reject(pkd) — The KEK assignment is rejected and BPI encryption was not
established, but network access for CPE devices using this CM was disabled.
• reject(pt) — TEK assignment is rejected with BPI encryption not established.
• reject(ptd) — The TEK assignment is rejected and BPI encryption was not
established, but network access for CPE devices using this CM was disabled.
# show cable modem
MAC Address IP Address US DS MAC Prim RxPwr
Intf Intf Status Sid (dBmV)
7cb2.1b42.x 10.200.0.154 2/0.0/0 0/0/3* online(pt) 1 -0.5
e448.c7ba.x 10.200.0.155 2/2.3/0* 0/1/6* online(pt) 1 -0.2
Timing Num BPI
Offset CPEs Enb
2429 0 yes
2382 0 yes
online cm 2 ; offline cm 0 ; ranging cm 0
show cable modem verbose
Shows the capabilities, whether BPI is enabled, and the BPI encryption algorithm for
each MAC address.
# show cable modem verbose
MAC Address :7cb2.1b42.b1be

…
Capabilities :{Frag=Y, Concat=Y, PHS=Y, Priv=BPI+}
Optional Filtering Support :{802.1P=N, 802.1Q=N}
BPI Enbld
…
Casa Systems
cable privacy
show cable modem [<mac_addr>] privacy verbose
Shows BPI state information for online and offline modems, if BPI is enabled.
# show cable modem 2476.7d98.b7d1 privacy verbose
MAC Address : 2476.7d98.b7d1

Primary SID : 1
BPI Mode : BPI+
BPI State : assign(tek)
Security Capabilities :
BPI Version : BPI+
Encryption : AES-128 DES-56
EAE : Disable
…
show interface docsis-mac | beg privacy
Shows one of the lifetime settings on a DOCSIS MAC interface for the Key
Encryption Key (KEK) and Traffic Encryption Key (TEK) required for BPI. The
value belongs to the previous interface, DOCSIS MAC 1 in this example.
# show interface docsis-mac | beg privacy

privacy kek life-time 604800
privacy tek life-time 43200
no cable cm-status report event-list 1,2,3,4,5,6,7,8,9,10
no cm trap
cm trap interval 600
…
Casa Systems
cable sa-des-tlvlen-2
Purpose
The cable sa-des-tlvlen-2 command sets the security association (SA) type-length
value (TLV) length to two bytes as required by some BPI-authenticated CMs. These
modems may not register with the CMTS using a one-byte descriptor. The
sa-des-tlvlen-2 value is the default.
Mode
(config)#
Syntax
[no] cable sa-des-tlvlen-2
Casa Systems
privacy hotlist
privacy hotlist
Purpose
The privacy hotlist command adds entries to the privacy hotlist to mark a CM’s or
manufacturer’s certificate as distrusted and prevent those CMs from registering.
Mode
(config)#
Syntax
[no] privacy hotlist cm <mac_addr>
[no] privacy hotlist manufacturer <serial_num>
Properties
cm <mac_addr> MAC address for the CM certificate to be added to

the hotlist, specified as a hexadecimal string, without
periods or other separators.
Example:
CASA(config)# privacy hotlist cm

0026.24a8.db36
CASA(config)#
no privacy hotlist cm 0026.24a8.db36
manufacturer <serial_num> Serial number for the particular manufacturer CA

certificate, specified as a hexadecimal string up to 32
bytes. Enter multiple lines as needed, and use a
blank line to terminate the string.
Example:
CASA(config)# privacy hotlist

manufacturer 12345678
CASA(config)# no privacy hotlist
manufacturer 12345678
Casa Systems
shared-secondary-secret
Purpose
The shared-secondary-secret command provides a second password should a CM

fail to authenticate with the primary shared-secret. With the secondary secret
configured, the CM must authenticate using either the primary or secondary password
so that the modem can register and come online. Using a secondary secret allows
CMTS operators to frequently revise the primary password without interrupting a
currently active and online CM with a primary password update.
Mode
(config)#
Syntax
shared-secondary-secret <1|2> <0|7> <key> [extend]
no shared-secondary-secret <1|2> [extend]
Properties
<1|2> Secondary shared secret index, 1 or 2. If two

secondary secrets, the index determines which
secondary secret password is checked first.
<0|7> Encryption type, either 0 (clear text follows) or 7
(encrypted text follows).
<key> MIC string used to encrypt and decrypt the
configuration file, up to 32 characters.
extend Optional modifier to set the shared-secret MIC for the
extend TLVs received from Reg-Req messages.
Example:
CASA(config)# shared-secondary-secret 1
0 DOCSIS extend
Casa Systems
shared-secret
shared-secret
Purpose
The shared-secret command configures an authentication shared encryption key to

protect modem configuration files from possible tampering. Because DOCSIS
configuration files from an authorized TFTP server provide critical quality of service
(QoS) definitions and other data for CMs, security measures must be applied to
protect the configuration file from unauthorized intercept, theft, substitution, and
potential modification. The DOCSIS specification supports the shared-secret and
shared-secondary-secret passwords to protect modem configuration files from
possible tampering. Once configured, these passwords calculate the CMTS Message
Integrity Check (MIC) field that is attached to all DOCSIS configuration files.
The CMTS supports up to 198 shared secrets (primary, secondary, and extended),
including those defined under the interface docsis-mac configuration.
Mode
(config)#
Syntax
shared-secret <0|7> <key> [extend]
no shared-secret <0|7> [extend]
Properties
<0|7> Encryption type, either 0 (clear text follows) or 7

(encrypted text follows). If omitted, sets the shared
secret MIC globally.
<key> MIC string used to encrypt and decrypt the
Casa Systems
shared-secret
extend Optional modifier to set the shared-secret MIC for the

extend TLVs received from the Reg-Req message.
Example:
CASA(config)# shared-secret 7 DOCSIS

extend
Casa Systems
4-1
Chapter 4. Cable commands
Cable commands description

Cable modem (CM) initialization begins when the CM is connected to the cable
provider’s network and powered on. The CM listens for MAC management message
(MMM) broadcasts from the CMTS. Using QAM modulated signals, the MMM
carries the 188-byte MPEG-2 transport stream for modem synchronization with the
MAC domain, as well as the upstream channel descriptors (UCDs) and their
associated MAP packets for establishing upstream transmissions, and a MAC Domain
Descriptor (MDD) for D3.0 modems capable of channel bonding.

code (IUC). The IUC schedules the initial ranging interval in the upstream timeline to
the CMTS. Once a transmission interval is set, the MAC domain adjusts CM
frequency, power, and delay for two-way communication.
Provisioning servers at the headend are necessary for the CM to properly complete the
initialization process. The CM initiates a request to a DHCP server for an IPv4 or IPv6
address assignment. Once the CM is assigned an IP address, it submits a request to a
target TFTP server for the DOCSIS modem configuration file. The configuration file
provides operational information to the modem using parameters that are set by the
cable service provider, including program identification to the CMTS MAC domain.
The TFTP server responds to the request by forwarding and loading the configuration
file to the modem at the DHCP-assigned address. Optionally, the CM may request
time information from a time-of-day (ToD) server.
This chapter describes the cable commands necessary for CM configuration.
Casa Systems
Table 4-1 lists and briefly describes the objects related to cable commands.
Table 4-1. Cable objects
cable admission-control Enables admission control and sets global

parameters.
cable arp fast-timeout Prevents ARP entry from timing out and being
removed from the ARP table.
cable arp filter Sets the number of ARP response packets to
accept from the CM and CPE in a configured
time window.
cable call-signal-classifier Creates separate service flow classifiers for
load balancing call signal traffic.
cable dhcp filter Sets the number of DHCP response packets
to accept from the CM and CPE in a
configured time window.
cable dhcp-leasequery filter Sets the number of DHCPv4 leasequery
packets to send to the CM and CPE.
cable dhcpv6-leasequery filter Sets the number of DHCPv6 leasequery
packets to send to the CM and CPE.
cable diaglog Configures DOCSIS diagnostic logging.
cable docsis version 31 Enables DOCSIS 3.1.
cable dsx authorization Checks all DSX messages (DSA, DSC and
DSD) for a valid gate ID authorization value.
cable dynamic-service-flow Assigns dynamic service flows to
cable ecn 770 Enables CableLabs Engineering Change
Notice (ECN) 770
cable event Enables generating and dispatching DOCSIS
cable event message notifications.
cable flap-list Detects abnormal CMs in the network.
cable host authorization Enables CM host authorization.
cable icmp filter Sets the number of ICMP response packets
Casa Systems
Cable commands 4-3
Table 4-1. Cable objects (continued)
cable igmp filter Sets the number of IGMP response packets

cable igmp permit src-ip Sets the prefix filter for the IGMP packet
source address.
cable igmp static-group Creates a static multicast session for
any-source-multicast.
cable igmp vrf static-group Creates a Virtual Routing and Forwarding
instance for the IGMP static group.
cable map-advance-adjust Adjusts the MAP lead time globally for all
upstream cards.
cable mdd Informs registered CMs through the MAC
Domain Descriptor (MDD) that it supports
extended transmission power over upstream
channels, or fragmented RCC/RCP TLV
packet transmissions if the RCP length
exceeds 255.
cable mirror Mirrors traffic from one device to another.
cable modem See Chapter 5, “Cable modem commands.”
cable monitor-period Sets the cable monitoring period.
cable partial-service Sets properties for CM partial-service
channels.
cable privacy Enables privacy settings for the CM.
cable proxy-arp unknown Fixes IP remote host deployments in which
the CMTS does not have an ARP binding.
cable qos Sets quality of service (QoS) options for the
CM.
cable rcp-select priority Sets the Receive Channel Profile (RCP)
selection for the CM.
cable sa-des-tlvlen-2 Sets the security association TLV length.
cable sec Sets CM security properties.
cable service attribute Restricts the CMTS from sending peak traffic
withhold-TLVs peak-rate rate information to non-DOCSIS 3.x CMs.
cable service-class Sets parameters for DOCSIS 1.1 cable
service classes.
Casa Systems
Table 4-1. Cable objects (continued)
cable service-flow Manages and removes idle upstream service

active-timeout flows.
cable service-type-id Moves D2.0 CMs between two CMTS
ds-frequency platforms.
cable spectrum Sets cable spectrum management properties.
cable subscriber over-consume Sets a trap for subscribers who exceeded the
trap maximum allowable bandwidth.
cable tag Defines a cable tag and sets its properties.
cable tcc us-bonding-disable Disables transmit channel configuration
(TCC) bonding to the upstream channel.
cable traffic-policy Configures Subscriber Traffic Management
(STM).
cable upstream Sets upstream traffic parameters.
reg-rsp-original-upstream-action Enables the CMTS to use the ADD action for
the original upstream channel in the
REG-RSP-MP message.
Casa Systems
Cable commands 4-5
cable admission-control
Purpose
The cable admission-control command enables (and sets global parameters for)
admission control, a mechanism that manages the service flow admission requests
when resources are not available to support the incoming service flow. It allows
mapping different service flow types into different application classes with defined
attribute rules. If the bandwidth resource for the application class is not available for
the upstream or downstream channel, the new service flow request is rejected.
Bandwidth allocation is configured with the exclusive and non-exclusive thresholds of

an application class. The exclusive bandwidth cannot be shared with other application
classes. The sum of exclusive and non-exclusive thresholds indicates the maximum
bandwidth the application class can have.
Perform the following steps to enable and configure admission control:
1. Use the cable admission-control command by itself to enable admission control,

then add any further properties.
2. Use the application class command to create one or more service-flow
application classes to define rules and the bandwidth to be calculated for matching
upstream or downstream traffic.
3. Use the include property of the application class command to add rules and
schedule types.
Mode
(config)#
Syntax
[no] cable admission-control
[no] cable admission-control cm-registration
[no] cable admission-control dynamic-service [exceed {dcc | reject}]
[no] cable admission-control multicast
[no] cable admission-control preempt priority-voice
Casa Systems
Properties
cm-registration If admission-control is enabled, applies admission

control to CM registration upstream service flows to
the CMTS.
Example:
CASA(config)# cable admission-control

cm-registration
CASA(config)#
no cable admission-control
CASA(config)# no cable
admission-control cm-registration
dynamic-service [exceed If admission-control is enabled, applies admission

{dcc | reject}] control to Dynamic Channel Change (DCC) service
flows. Use the optional exceed modifier with dcc to
force DCC service flow admission if the calculated
bandwidth is insufficient, or with reject to disallow the
service-flow.
Example:

dynamic-service exceed dcc
admission-control dynamic-service
multicast If admission-control is enabled, rejects multicast

replication of the channel set if adequate bandwidth
is unavailable.
Example:

multicast
admission-control multicast
Casa Systems
Cable commands 4-7
preempt priority-voice If admission-control is enabled, gives bandwidth

priority to certain voice flows over all other traffic,
known as high-priority call preemption.
Example:

preempt priority-voice
CASA(config)#
no cable admission-control preempt
priority-voice
Example
CASA(config)# cable admission-control cm-registration
CASA(config)# cable admission-control dynamic-service exceed dcc
CASA(config)# application class 4
CASA(conf-app-class 4)# downstream-bandwidth exclusive 100
CASA(conf-app-class 4)# upstream-bandwidth exclusive 100
CASA(conf-app-class 4)# include BE
CASA(conf-app-class 4)# include packetcable emergency
show cable admission-control
Shows admission control settings.
CASA(config)# show cable admission-control

cable admission-control dynamic-service exceed dcc
cable admission-control cm-registration
show cable admission-control interface {downstream | ofdm | ofdma |

upstream}
Shows admission control results for the particular downstream or upstream interface.
CASA(config)# show cable admission-control interface upstream 13/0.0

App-Class Exclusive Non-Exclusive Curr-Resv Curr-Ovrsb
Casa Systems
cable arp fast-timeout
cable arp fast-timeout

Purpose
The cable arp fast-timeout command prevents ARP entry from timing out and being
removed from the ARP table if no responses are received after six consecutive
attempts. If this feature is enabled, the SMM ARP still does round robin polling, but if
an ARP reply is not received in eight seconds, SMM ARP polls it again up to two
more times, each eight seconds after the previous request. If no ARP reply is received
at the end of the eight-second interval of the last request, the ARP entry of the CPE is
removed. The default is fast-timeout not enabled.
Mode
(config)#
Syntax
[no] cable arp fast-timeout
show cable arp fast-timeout
Shows whether fast timeout is enabled.
CASA# show cable arp fast-timeout

cable arp fast-timeout enabled
Casa Systems
Cable commands 4-9
cable arp filter
cable arp filter

Purpose
The cable arp filter command sets the number of ARP response packets to accept
from the CM and CPE in a configured time window.
Mode
(config)#
Syntax
cable arp filter <0:20> <1:60>
no cable arp filter
Properties
<0:20> <1:60> Number of ARP packets to accept in a window

(default 8) followed by the number of seconds in a
window (default 2).
Example:
CASA(config)# cable arp filter 8 2

CASA(config)# no cable arp filter
show cable filter running-config
Shows the cable filter settings in the running configuration.
CASA(config)# show cable filter running-config

cable arp filter 8 2
cable dhcp filter 100 2
Casa Systems
cable call-signal-classifier
Purpose
The cable call-signal-classifier command uses a service flow classifier to separate

and keep voice call load balancing from performing Dynamic Bonding Change (DBC)
or Dynamic Channel Change (DCC) operations. This change allows PacketCable
voice signaling to use a dedicated service flow. Optional source and destination
starting and ending port numbers for the dedicated service flow can be specified.
Mode
(config)#
Syntax
cable call-signal-classifier [source-port-range <0:65535> <0:65535>]
[dest-port-range <0:65535> <0:65535>]
Properties
dest-port-range <0:65535> Destination port range indicating the starting and

<0:65535> ending port numbers. A zero value for the starting
range indicates no starting value, and a zero value
for the ending range indicates no ending value. The
starting values must be lower than the ending values.
The source-port-range and dest-port-range can be
specified on the same command line.
Example:
CASA(config)# cable
call-signal-classifier
CASA(config)# cable
call-signal-classifier dest-port-range
30 50
Casa Systems
Cable commands 4-11
source-port-range <0:65535> Source port range indicating the starting and ending
<0:65535> port numbers. A zero value for the starting range
indicates no starting value, and a zero value for the
ending range indicates no ending value. The starting
values must be lower than the ending values. The
source-port-range and dest-port-range can be
specified on the same command line.
Example:
CASA(config)# cable
call-signal-classifier
source-port-range 30 60 dest-port-range
70 90
show cable call-signal-classifier
Shows the cable call signal classifier configuration.
CASA(config)# show cable call-signal-classifier

cable call-signal-classifier source-port 30 60 dest-port-range 70 90
Casa Systems
cable dhcp filter
cable dhcp filter

Purpose
The cable dhcp filter command sets the number of DHCP response packets to accept
from the CM and CPE in a configured time window.
Mode
(config)#
Syntax
cable dhcp filter <0:255> <1:60>
no cable dhcp filter
Properties
<0:255> <1:60> Number of DHCP packets to accept in a window

(default 20) followed by the number of seconds in a
window (default 2).
Example:
CASA(config)# cable dhcp filter 20 2

CASA(config)# no cable dhcp filter

Casa Systems
Cable commands 4-13
cable dhcp-leasequery filter
cable dhcp-leasequery filter

Purpose
The cable dhcp-leasequery filter command sets the number of DHCP leasequery
packets to send to the CM and CPE in a configured time window.
Mode
(config)#
Syntax
cable dhcp-leasequery filter <0:20> <1:4>
no cable dhcp-leasequery filter
Properties
<0:20> <1:4> Number of DHCP leasequery packets to send in a

window (default 8) followed by the number of
seconds in a window (default 2).
Example:
CASA(config)# cable dhcp-leasequery

filter 8 2
CASA(config)#
no cable dhcp-leasequery filter

cable icmp filter 0 2
cable dhcp-leasequery filter 8 2
Casa Systems
cable dhcpv6-leasequery filter
cable dhcpv6-leasequery filter

Purpose
The cable dhcpv6-leasequery filter command sets the number of DHCPv6

leasequery packets to send to the CM and CPE in a configured time window.
Mode
(config)#
Syntax
cable dhcpv6-leasequery filter <0:20> <1:4>
no cable dhcpv6-leasequery filter
Properties
<0:20> <1:4> Number of DHCPv6 leasequery packets to send in a

window (default 8) followed by the number of
seconds in a window (default 2).
Example:
CASA(config)# cable dhcpv6-leasequery

filter 8 2
CASA(config)#
no cable dhcpv6-leasequery filter

cable dhcpv6-leasequery filter 8 2
Casa Systems
Cable commands 4-15
cable diaglog
cable diaglog
Purpose
The cable diaglog command configures DOCSIS diagnostic logging.
Mode
(config)#
Syntax
[no] cable diaglog
[no] cable diaglog ranging
cable diaglog reg-detail-mask <0x0:0xffff>
cable diaglog reg-time-interval <60:86400>
[no] cable diaglog registration
Properties
ranging Enables the ranging missed flap-list log.
Example:
CASA(config)# cable diaglog ranging

CASA(config)# no cable diaglog ranging
CASA(config)# no cable diaglog
reg-detail-mask Sets the registration detail mask, a user-defined

<0x0:0xffff> value, default 0x0.
Example:
CASA(config)# cable diaglog

reg-detail-mask 0x0
Casa Systems
cable diaglog
reg-time-interval Sets the registration timeout value, default 90

<60:86400> seconds.
Example:

reg-time-interval 90
registration Enables the registration timeout log.
Example:

registration
CASA(config)#
no cable diaglog registration
Casa Systems
Cable commands 4-17
cable docsis version 31
cable docsis version 31

Purpose
The cable docsis version 31 command enables DOCSIS 3.1 for CMs. The setting
shows up when you run a show running-config verbose | include “cable docsis”
command.
Mode
(config)#
Syntax
[no] cable docsis version 31
Casa Systems
cable dsx authorization
cable dsx authorization

Purpose
The cable dsx authorization command checks all Dynamic Service Change (DSX)
messages (DSA, DSC and DSD) for a valid gate ID authorization value. If the DSX
message is invalid, the CMTS rejects the message.
Mode
(config)#
Syntax
[no] cable dsx authorization
Casa Systems
Cable commands 4-19
cable dynamic-service-flow
Purpose
The cable dynamic-service-flow command assigns dynamic service flows to bonded

downsteam channels (the default), to any one of the downstream channels
(non-bonding), or to the modem’s primary downstream channel. For example, to
assign Voice over IP (VoIP) traffic to the modem’s primary downstream channel, use
the cable dynamic-service-flow primary command.
Mode
(config)#
Syntax
cable dynamic-service-flow bonding
cable dynamic-service-flow non-bonding
cable dynamic-service-flow primary
Properties
bonding Assigns dynamic service flows to bonded

downstream channels. This is the default setting.
Example:
CASA(config)# cable
dynamic-service-flow bonding
non-bonding Assigns dynamic service flows to any one of the

Example:
CASA(config)# cable
dynamic-service-flow non-bonding
Casa Systems
primary Assigns dynamic service flows to the modem’s

primary downstream channel.
Example:
CASA(config)# cable
dynamic-service-flow primary
Casa Systems
Cable commands 4-21
cable ecn 770
cable ecn 770

Purpose
The cable ecn 770 command enables CableLabs Engineering Change Notice (ECN)
770 to help keep modems from getting into the upstream partial service state when
there are a large number of modems attempting to register with the CMTS while the
CMTS is assigning and bonding channels to D3.0 modems. This feature is enabled by
default.
Some CMs end up in upstream partial service mode if there are collisions followed by
no additional attempts to range on the assigned upstream channels. Configuring
unicast ranging as the initial technique instead of the default broadcast ranging in
interface docsis-mac configuration, by using the initial-tech unicast-ranging
command, avoids any collisions and helps prevent modems from getting into
upstream partial service mode.
By enabling ECN 770, UCD encodings are included in the transmit channel
configuration (TCC) in the CMTS registration response to the prevent the partial
service problem. However, modems that are already in partial service mode must be
reset.
Mode
(config)#
Syntax
[no] cable ecn 770
Casa Systems
cable event
cable event
Purpose
The cable event command enables generating and dispatching DOCSIS cable event
message notifications. This function is enabled by default. The cable event <id>
command controls the dispatching of DOCIS cable event messages by event ID. By
default, all cable event messages except 82010100 and 82010400 are enabled. Use the
show cable event running-config [brief] command to display the list of cable event
IDs.
Mode
(config)#
Syntax
[no] cable event
[no] cable event <0:4294967295>
[no] cable event <0:4294967295> delivery
[no] cable event priority {alert | critical | debug | emergency | error
| informational | notice | warning} <nonvol_flag> [<vol_flag>]
[no] cable event syslog-server <ip_addr> [port <1:65535>]
[no] cable event throttle-adminStatus {inhibited |
maintainBelowThreshold | stopAtThreshold | unconstrained}
[no] cable event throttle-interval <1:2147483647>
[no] cable event throttle-threshold <num>
Properties
<0:4294967295> Valid cable event ID, as determined by the

show cable event running-config [brief]
command.
Example:
CASA(config)# cable event

CASA(config)# cable event 1
CASA(config)# no cable event 1
CASA(config)# no cable event
Casa Systems
Cable commands 4-23
cable event
delivery With the event ID indicated, enables forwarding

major cable event messages to the syslog server.
Use the no form of the command to disable any
previously specified cable events from being
forwarded to the syslog server.
Example:
CASA(config)# cable event 1 delivery

CASA(config)# no cable event 1 delivery
CASA(config)# no cable event delivery
Casa Systems
cable event
priority {alert | critical Configures the event reporting flags for DOCSIS
| debug | emergency | error event messages, which determines how the CMTS
| informational | notice | reports these events. The reporting flags can be
warning} <nonvol_flag> alert, critical, debug, emergency, error,
[<vol_flag>] informational, notice, or warning. The flag values
(in hex) designate how messages are handled. The
first value is the non-volatile (flash) flag and the
second optional value can be 0x00 or 0x80 for the
local volatile (memory) log flag:
• 0x00 — Not reported.

• 0x80 — Reported to local log.
• 0xA0 — Reported to local non-volatile log and
SYSLOG.
• 0xC0 — Reported to local non-volatile log and
trap receivers.
• 0xE0 — Reported to local non-volatile log, SYS-
LOG, and trap receivers.
• 0x20 — Reported to SYSLOG.
• 0x40 — Reported to trap receivers.
• 0x60 — Reported to SYSLOG and trap receivers.
Example:
CASA(config)# cable event priority

alert 0x20
CASA(config)#
no cable event priority alert
Casa Systems
Cable commands 4-25
cable event
syslog-server <ip_addr> Enables logging of DOCSIS event messages to a

[port <1:65535>] SYSLOG server, identified by IP address (and
optional port).
Example:
CASA(config)# cable event syslog-server

192.168.8.8
CASA(config)#
no cable event syslog-server
throttle-adminStatus Configures how the CMTS throttles the SNMP traps

{inhibited | and SYSLOG messages it generates for DOCSIS
maintainBelowThreshold | event messages, as follows:
stopAtThreshold |
unconstrained} • inhibited — Causes all trap transmission and
SYSLOG messages to be suppressed.
• maintainBelowThreshold — Causes trap trans-
mission and SYSLOG messages to be sup-
pressed if the number of traps would otherwise
exceed the threshold.
• stopAtThreshold — Causes trap transmission to
cease at the threshold, and not resume until
directed to do so.
• unconstrained — Causes traps and SYSLOG
messages to be transmitted without regard to the
threshold settings.
Example:

throttle-adminStatus inhibited
CASA(config)#
no cable event throttle-adminStatus
Casa Systems
cable event
throttle-interval Specifies the throttle interval that controls how often

<1:2147483647> the CMTS generates SNMP traps, in seconds.
Example:

throttle-interval 1200
CASA(config)#
no cable event throttle-interval
throttle-threshold <num> Sets the maximum number of SNMP traps and

SYSLOG messages that the CMTS can generate for
DOCSIS event messages during the throttle interval.
Example:

throttle-threshold 1200
CASA(config)#
no cable event throttle-threshold
clear cable events
Clears all cable events.
CASA(config)# clear cable events
show cable events
Shows all the cable events in reverse chronological order. Because of the shear
volume of output, use this command sparingly.
Casa Systems
Cable commands 4-27
cable event
show cable event running-config [brief]
Shows the list of cable events in the running configuration, with the added brief
option.
CASA(config)# show cable event running-config

cable event
cable event 66010100
no cable event 83020203
…
show cable event delivery
Shows the event IDs currently forwarded to the syslog server.
CASA(config)# show cable event delivery

cable event 66010100 delivery
show cable event notification-policy
Shows the event reporting flags for cable event messages.
CASA(config)# show cable event notification-policy
priority flash-log mem-log traps syslog

-------------------------------------------------
emergency yes no no no
alert yes no no no
critical yes no yes yes
error yes no yes yes
warning no yes yes yes
notice no yes yes yes
informational no no no no
debug no no no no
show cable event syslog-server
Shows the syslog host IP address for DOCSIS events.
CASA(config)# show cable event syslog-server

DOCSIS syslog server: 0.0.0.0
Casa Systems
cable event
show cable event throttle-config
Shows the cable event throttling configuration.
CASA(config)# show cable event throttle-config

Throttle Admin Status: unconstrained
Throttle Inhibited: false
Throttle Threshold: 0
Throttle Interval: 1
Casa Systems
Cable commands 4-29
cable flap-list
cable flap-list
Purpose
The cable flap-list command enables detecting abnormal CMs in the network and
providing a list of malfunctioning ones to help identify the problem.
Mode
(config)#
Syntax
cable flap-list add {<mac_addr> | all | downstream <slot>/<port>/
<chan> | ofdm <slot>/<port>/<chan> | ofdma <slot>/<port>.<pchan>
| upstream <slot>/<port>.<pchan>/<lchan>}
cable flap-list aging {<15:86400> | default}
cable flap-list check-interval {<1:1200> | default}
[no] cable flap-list insertion-time {<1:120> | default}
[no] cable flap-list miss threshold {<3:12> [<60:65535>] | default}
[no] cable flap-list power-adjust threshold {<1:20> | default}
[no] cable flap-list trap
Properties
add {<mac_addr> | all | Adds a flap list to a specific MAC address, all
downstream <slot>/<port>/ modems, or a specific downstream, OFDM, OFDMA,
<chan> | ofdm <slot>/ or upstream interface.
<port>/<chan> | ofdma
<slot>/<port>.<pchan> | Example:
upstream <slot>/
<port>.<pchan>/<lchan>} CASA(config)# cable flap-list add
downstream 4/0/2
Casa Systems
cable flap-list
aging {<15:86400> | Period in which the CM is maintained in the flap list

default} table, maximum 60 days, default 10080 minutes (one
week). If the time limit is reached, the CM is removed
from the flap-list table. After the CM is removed, the
user cannot get flap list information about this CM.
Example:
CASA(config)# cable flap-list aging

10080
check-interval {<1:1200> | Interval for the CMTS to scan the flap list table,
default} default 120 minutes (2 hours). If the CMTS finds any
CM that reached the aging limit, the CMTS removes
it from the flap list table. When the CM is removed,
the user cannot check the CM’s flap-list information.
Example:
CASA(config)# cable flap-list

check-interval 120
insertion-time {<1:120> | Insertion time, if in which period the CM constantly

default} sends out initial ranging requests, it is put in the flap
list table for observation. The default is 60 seconds.
Example:

insertion-time 60
CASA(config)#
no cable flap-list insertion-time
Casa Systems
Cable commands 4-31
cable flap-list
miss threshold {<3:12> When the CMs do not reply to the maintenance
[<60:65535>] | default} message sent from the CMTS after the specified
number of times, they are put in the flap list table for
observation. The default is 6 times. The optional
second parameter is the maximum number of
maintenance messages, default 90.
Example:
CASA(config)# cable flap-list miss

threshold 6
CASA(config)#
no cable flap-list miss threshold
power-adjust threshold After the CMs come online and the status is stable, if
{<1:20> | default} the power adjustment from the CMTS to the CMs is
greater than the specified unit of dB, the CMs are
moved to the flap list table for observation. The
default is 2 dB.
Example:

power-adjust threshold 2
CASA(config)# no cable flap-list
power-adjust threshold
trap Enables the CM flap list trap.
Example:
CASA(config)# cable flap-list trap

CASA(config)# no cable flap-list trap
Casa Systems
cable flap-list
clear flap-list {delete | reset}
Clears all cable flap lists. The optional delete modifier deletes all flap list CM records,
and the reset modifier resets all flap list counters.
CASA(config)# clear cable flap-list
show cable flap-list [<mac_addr> | downstream <slot>/<port>/<chan> |

sort-flap | sort-int | sort-mac | sort-time | upstream <slot>/<port>/
<pchan>/<lchan>]
Shows the cable flap list. A number of sort options are available.
CASA(config)# show cable flap-list

MAC Address Us-Int Ins Hit Miss(%) CRC P-Adj ARP-TO Flap Time
0005.caa3.x 10/0.1/0 210 99 10(9.2 %) 0 18 0 228 2014-07-10,14:30:54
0013.f735.x 10/0.0/0 25 207 70(25.3%) 0 61 0 86 2014-07-10,14:06:49
show cable flap-list config
Shows the cable flap list property settings.
CASA(config)# show cable flap-list config

cable flap-list power-adjust threshold 2
cable flap-list miss threshold 6 90
cable flap-list insertion-time 60
cable flap-list aging 10080
cable flap-list check-interval 120
cable diaglog reg-time-interval 90

cable diaglog reg-detail-mask 0x0000
Casa Systems
Cable commands 4-33
cable host authorization
cable host authorization

Purpose
The cable host authorization command enables a CM host authorization address

without changing the CM config file, up to 2048 for each of IPv4 and IPv6.
Mode
(config)#
Syntax
[no] cable host authorization <mac_addr> {<ip_addr> | <ip6_addr>} [vrf
<name>]
Properties
<mac_addr> {<ip_addr> | MAC address and the IPv4 or IPv6 address of the
<ip6_addr>} [vrf <name>] CM, with the optional VRF name.
Example:
CASA(config)# cable host authorization

0015.f2fe.c904 67.1.8.23
CASA(config)# no cable host
authorization 0015.f2fe.c904 67.1.8.23
show cable host authorization
Shows the cable host authorization settings.
CASA(config)# show cable host authorization

cable host authorization 0015.f2fe.c904 67.1.8.23
Casa Systems
cable icmp filter
cable icmp filter

Purpose
The cable icmp filter command sets the number of Internet Control Message Protocol
(ICMP) response packets to accept from the CM and CPE in a time window.
Mode
(config)#
Syntax
[no] cable icmp filter <0:255> <1:60>
Properties
<0:255> Maximum number of ICMP response packets to

accept from the CM or CPE within the specified time
window, default 0 (no filter).
<1:60> Seconds to specify the time window for accepting
ICMP packets from the CM or CP, default 2 seconds.
Example:
CASA(config)# cable icmp filter 100 2

CASA(config)# no cable icmp filter
CASA(config)# show cable filter running-config | inc icmp

Casa Systems
Cable commands 4-35
cable igmp filter
cable igmp filter

Purpose
The cable igmp filter command sets the number of Internet Group Management
Protocol (IGMP) response packets to accept in a configured time window.
Mode
(config)#
Syntax
[no] cable igmp filter <1:5000> <1:60>
Properties
<1:5000> Maximum number of IGMP response packets to

accept from the CM or CPE within the specified time
window, default 100.
<1:60> Seconds to specify the time window for accepting
IGMP packets from the CM or CP, default 2 seconds.
Example:
CASA(config)# cable igmp filter 100 2

CASA(config)# no cable igmp filter
CASA(config)# show cable filter running-config | incl igmp

cable igmp filter 100 2
Casa Systems
cable igmp permit src-ip
cable igmp permit src-ip

Purpose
The cable igmp permit src-ip command sets the permit filter for the Internet Group
Management Protocol (IGMP) packet source address. Situations may occur where
certain D2.0 STBs send IGMP join packets using a private NAT source IP address
instead of the external CPE IP address obtained via DHCP. The command bypasses
the source address verification (SAV) check for the given prefix in order to accept the
private NAT source IP address.
Mode
(config)#
Syntax
[no] cable igmp permit src-ip <ip_addr> <ip_mask>
Properties
<ip_addr> Packet source IP address, in octet format. The value

cannot be 0.0.0.0.
<ip_mask> Address mask, in octet format.
Example:
CASA(config)# cable igmp permit src-ip

192.168.8.8 255.255.255.0
CASA(config)# no cable igmp permit
src-ip 192.168.8.8 255.255.255.0
Casa Systems
Cable commands 4-37
cable igmp static-group

Purpose
The cable igmp static-group command creates a static multicast session for IGMP
any-source-multicast.
Modes
(config)#
(conf-igmp-static-group <addr>)#
Syntax
(config)#
[no] cable igmp static-group {<ip_addr> | ipv6 <v6_addr>}
[source <ip_addr>] [dsid <85689:86688>]
(conf-igmp-static-group x)#
[no] description “<text>”
[no] qam <slot>/<port>/<chan>
Properties
{<ip_addr> | ipv6 Valid multicast group IP address for the static group.
<v6_addr>}
Example:
CASA(config)# cable igmp static-group

224.0.0.0
CASA(conf-igmp-static-group 224.0.0.0)#
CASA(config)#
no cable igmp static-group
CASA(config)#
no cable igmp static-group ipv6 ::1
Casa Systems
dsid <85689:86688> Optional Downstream Service Identifier (DSID).
Example:

224.0.0.0 dsid 85689
source <ip_addr> Optional alternative source IP address for the

multicast session.
Example:

224.0.0.0 source 192.168.0.1
description “<text>” Descriptive text for the static group, up to 64

characters.
Example:
description “First static group”
no description
qam <slot>/<port>/<chan> Downsteam channel using the system slot, port

number, and physical downstream channel number.
Use the interface qam command to create the
interface.
Example:
qam 2/0/0
no qam 2/0/0
Casa Systems
Cable commands 4-39
show cable igmp static-group
Shows the configured IGMP static group.
CASA(config)# show cable igmp static-group
cable igmp static-group 224.0.0.0
cable igmp static-group 224.0.100.100 source 192.168.8.8
Casa Systems
cable igmp vrf static-group

Purpose
The cable igmp vrf static-group command creates a Virtual Routing and Forwarding
(VRF) static group instance for IGMP.
Modes
(config)#
Syntax
(config)#
[no] cable igmp vrf <vpn_id> static-group <ip_addr> [source <ip_addr>]
[dsid <85689:86688>]
Properties
<vpn_id> VPN ID of the VRF. Requires the static-group

property.
static-group <ip_addr> Static group multicast IP address.
[source <ip_addr>] [dsid
<85689:86688>] Example:
CASA(config)# cable igmp vrf VPN94

static-group 224.0.0.0
exit
CASA(config)# no cable igmp vrf VPN94
static-group 224.0.0.0
Casa Systems
Cable commands 4-41
description “<text>” Descriptive text for the static group, up to 64

characters.
Example:
description “First static group”
no description
qam <slot>/<port>/<chan> Downsteam channel using the system slot, port

number, and physical downstream channel number.
Use the interface qam command to create the
interface.
Example:
qam 2/0/0
no qam 2/0/0
show cable igmp vrf <id> static-group
Shows the configured IGMP static group for the VRF.
CASA(config)# show cable igmp vrf VPN94 static-group
Casa Systems
cable map-advance-adjust
cable map-advance-adjust
Purpose
The cable map-advance-adjust command adjusts the MAP lead time globally for all
upstream cards, which addresses some DOCSIS 3.x CMs that require longer MAP
lead times. MAP advance for the upstream interface defines the amount of look-ahead
time for MAPs based on the plant characteristics. The system already has a built-in
look-ahead time to account for internal operations like generating the MAP. The
adjustment can range -1000 through 5000 microseconds, the default 0. (See also the
interface upstream map-advance property.) The show run verbose command
shows the current setting (see Example).
Mode
(config)#
Syntax
[no] cable map-advance-adjust <-1000:5000>
Example
CASA(config)# cable map-advance-adjust 500
CASA(config)# show run verbose | include “cable map-advance”
cable map-advance-adjust 500
Casa Systems
Cable commands 4-43
cable mdd
cable mdd
Purpose
The cable mdd command enables the CMTS to inform registered CMs through the
MAC Domain Descriptor (MDD) that it supports extended transmission power over
upstream channels, or fragmented RCC/RCP TLV packet transmissions if the RCP
length exceeds 255.
Mode
(config)#
Syntax
[no] cable mdd cm-status-ack support
[no] cable mdd extended tx-power support <0|1>
[no] cable mdd rcp {fragment | verbose} support
Properties
cm-status-ack support Enables CM-STATUS-ACK reports per event.
Example:
CASA(config)# cable mdd cm-status-ack

support
CASA(config)#
no cable mdd cm-status-ack support
extended tx-power support Enables supporting extended transmission power

<0|1> over upstream channels. Specify 1 to support
extended power levels; 0 (the default) disables the
extended transmission power support feature.
Example:
CASA(config)# cable mdd extended

tx-power support 0
CASA(config)#
no cable mdd extended tx-power support
Casa Systems
cable mdd
rcp {fragment | verbose} When fragment support is enabled, the CMTS

support informs registered CMs that it supports fragmented
RCC/RCP TLV packet transmissions if the Receive
Channel Profile (RCP) length exceeds 255. The
default is disabled (no RCP fragment support).
Example:
CASA(config)# cable mdd rcp fragment

support
CASA(config)# no cable mdd rcp verbose
support
show cable mdd extended tx-power support
Shows the extended transmission power support. With extended transmission power
support enabled, debug output shows “Extended Upstream Transmit Power
Capability(40):f4.”
CASA(config)# show cable mdd extended tx-power support
cable mdd extended tx-power support 0
show cable mdd msg downstream [<slot>/<port>/<chan>]
Shows the MDD messages for a downstream channel, including the decoding and
initialization parameters.
CASA(config)# show cable mdd msg downstream 2/0/3

Dump primary MDD message,MAC-DOMAIN 1:
01 e0 2f 00 00 01 00 17 10 82 cb c2 01 b6 00 00
03 04 21 00 0d 01 01 04 01 13 01 01 01 02 04 17
d7 84 00 03 01 01 04 01 01 05 02 00 36 01 13 01
…
Decode MDD message
Dest. Address : 01e0.2f00.0001
Casa Systems
Cable commands 4-45
cable mdd
Source Address: 0017.1082.cbc2

Message Length: 438 (decimal) DSAP: 00 SSAP: 00
Control: 03 Version: 04
Type: mdd(33) RSVD: 00
Configuration Change Count: 40 Num of Fragments: 01

Fragment Seq Num: 01 Current Channel DCID: 01
Downstream Active Channel List(1): ---------- 19 bytes

|Channel ID(1): 01
|Frequency(2): 1c 40 aa 80
|Modulation Order/Annex(3): 01
|Primary Capable(4): 01
|CM-Status Event Enable Bitmask(5): 00 00
…
IP Initialization Parameters(5): ---------- 8 bytes
|IP Provisioning Mode(1): 03
|Pre-Registration DSID(2): 0b 00 87
Casa Systems
cable mirror
cable mirror
Purpose
The cable mirror command mirrors traffic from specified devices by setting the CM
or CPE MAC address being mirrored and the destination IPv4 address and UDP port
to which the mirrored traffic is sent. The command takes effect immediately.
Mode
(config)#
Syntax
[no] cable mirror <mac_addr> <dest_ip_addr> <1:65535>
Properties
<mac_addr> MAC address of the CPE or CM, with all data packets
captured and encapsulated to one or the other.
<dest_ip_addr> Destination IP address of the mirror stream.
<1:65535> UDP port to assign the stream.
Example:
CASA(config)# cable mirror

2476.7d98.bd08 10.200.0.150 144
CASA(config)# no cable mirror
2476.7d98.bd08 10.200.0.150 144
show cable mirror
Shows the mirrored CMs or CPEs.
Casa Systems
Cable commands 4-47
cable modem
cable modem
Purpose
The cable modem command sets various CM properties.
These commands are described in Chapter 5, “Cable modem commands.”
Modes
#
(config)#
Casa Systems
cable monitor-period
cable monitor-period
Purpose
The cable monitor-period command sets the cable monitoring period. Casa Spectrum
Management (CSM) monitors the quality of all upstream channels by periodically
polling measured parameters of signal-to-noise ratio (SNR), correctable Forward
Error Corrections (FECs), and uncorrectable FECs.
Mode
(config)#
Syntax
cable monitor-period <5:3600>
Properties
<5:3600> Monitor polling interval, starting at 5 seconds and

defaulting to 30 seconds.
Example:
CASA# cable monitor-period 30
show cable modem fec
Shows forward error correction (FEC) statistics for each upstream port.
CASA(config)# show cable modem fec

MAC Address US IF USSNR Unerrored Corrected Uncorrectable
0018.4de7.3d60 9/0.3/0 40.4 2269 0 0
…
Casa Systems
Cable commands 4-49
cable partial-service
Purpose
The cable partial-service command sets the following properties for CM

partial-service channels:
• continue-ranging — Assigns unicast ranging opportunity to a partial-service

channel.
• dbc-recovery — Recovers upstream partial service channels using DBC rather
than doing a modem reset, using a time interval between recovery attempts.
• reset-legacy-cm — Resets the legacy CM if in partial-service mode.
• tx-power-deficit — Reduces the channel set on a transmit power deficit, enabled
by default.
• upstream-impairment — Handles conditions where a channel impairment
causes modem throughput issues. The optional margin to restore service is in dB,
default 3.
Mode
(config)#
Syntax
[no] cable partial-service continue-ranging
[no] cable partial-service dbc-recovery <60:3600>
[no] cable partial-service reset-legacy-cm
[no] cable partial-service tx-power-deficit
[no] cable partial-service upstream-impairment [margin <1:10>]
Casa Systems
Properties
continue-ranging Enables assigning a unicast ranging opportunity to a

partial-service channel, enabled by default.
Example:
CASA# cable partial-service

continue-ranging
CASA# no cable partial-service
continue-ranging
dbc-recovery <60:3600> Recovers upstream partial service channels using

Dynamic Bonding Change (DBC) rather than doing a
modem reset, using the specified time interval, in
seconds, between recovery attempts. Disabled by
default.
Note: Recovery is possible only for upstream

channels that enter partial service due to
ranging timeout. This means that the
channel was ranging successfully before
going into partial service.
Example:

dbc-recovery 60
CASA#
no cable partial-service dbc-recovery
reset-legacy-cm Enables resetting the legacy CM if in partial-service

mode.
Example:

reset-legacy-cm
reset-legacy-cm
Casa Systems
Cable commands 4-51
tx-power-deficit Reduces the channel set on a transmit power deficit,

enabled by default.
Example:

tx-power-deficit
tx-power-deficit
upstream-impairment [margin Handles conditions where a channel impairment

<1:10>] causes modem throughput issues. The command
monitors SNR and FEC during normal
communications and triggers partial service when low
SNR or high FEC error count occurs. The threshold
to trigger partial service is an uncorrectable FEC
error rate of 1%, or low SNR. The SNR threshold
depends on the modulation profile used; 20 dB for
64QAM, and 14 dB for 16QAM. To exit partial
service, the trigger is a resulting good SNR, which is
3 dB over the SNR threshold by default, which can be
modified using the margin value. With its no form
specified, the CMTS does not use partial-service
channels for data traffic. Ranging continues once the
SNR for ranging bursts is sufficient to restore service;
the channel is then re-enabled for data traffic.
Example:

upstream-impairment margin 1
upstream-impairment
Casa Systems
show cable modem partial-service [downstream | mac <id> | upstream]
Shows CMs in partial-service mode. Note the reason codes appended to the US/DS
CHAN EXCLUDED column. Output can also be filtered by MAC address,
downstream or upstream, or service-group.
CASA(config)# show cable modem partial-service

Reason code: x/y/z(reason_code)
1 MDD timeout 2 FEC lock failure
3 Bad tcc 4 Bad rcc
5 Reg ack 6 DBC rsp
7 TR power bad 8 NCP profile failure
9 Impaired channel 10 Channel unreachable
11 Range timeout 12 Ranging failure
0 Unknown
MAC Address MAC US DS US DS US/DS CHAN EXCLUDED

id Intf Intf SET SET
e448.c7b4.ab62 1 13/0.2/0 2/0/3 256 256(4*4) 2/0/4,2/0/5
e448.c7c0.ebca 3 13/4.0/0 2/2/3 257 256(3*4) 2/2/4,2/2/5
e448.c7c0.f0dc 2 13/2.0/0 2/1/0 256 256(4*4) 2/1/4,2/1/5
Casa Systems
Cable commands 4-53
cable privacy
cable privacy
Purpose
The cable privacy command enables privacy settings for CMs.
See the cable privacy command in Chapter 3, “Baseline Privacy Interface.”
Casa Systems
cable proxy-arp unknown
cable proxy-arp unknown

Purpose
The cable proxy-arp unknown command is implemented for fixed IP remote host
deployments in which the CMTS does not have an ARP binding to an IP address in
the ARP table. When configured, the CMTS responds to an ARP request for an
unknown IP address in the IP bundle with the proxy ARP gateway MAC address.
The additional subnet option stipulates that the ARP request is for an IP address in an
unknown subnet to allow the CMTS to respond to ARP requests from CPE devices
which are outside the IP bundle address scope. The enhancement addresses situations
where CPE devices cannot register due to the CMTS not responding to ARP requests
from unknown IP address subnets. The default setting is disabled. Note that the IP
bundle ip address <addr> proxy-arp unknown subnet setting, if used, takes
precedence over this global setting.
Mode
(config)#
Syntax
[no] cable proxy-arp unknown [subnet]
show cable proxy-arp config
Shows whether proxy ARP unknown is enabled.
CASA(config)# show cable proxy-arp config

proxy-arp unknown enabled
CASA(config)# show cable proxy-arp config

proxy-arp unknown not enabled
Casa Systems
Cable commands 4-55
cable qos
cable qos
Purpose
The cable qos command sets quality of service (QoS) options for the CM. The class
property defines the service classes based on bandwidth priority for downstream and
upstream traffic. Normally, bandwidth is assigned in strict priority based on one of 10
priority levels assigned in the configuration file for the CM. Weighted fair queuing
(WFQ) takes one or more of the lower eight priority service classes and assigns a
weight to each one, such that the block of available bandwidth for those classes is
“fairly” and proportionally assigned among them. The method is described in more
detail in the “Weighted fair queuing” section.
Mode
(config)#
Syntax
[no] cable qos class {ds | us} <0:7> {flow-wfq {enable | max-rate
<1000:2147483647>} | weight <1:100>}
cable qos ds scheduler mode {guaranteed-plus | normal}
[no] cable qos temp-us-sf <svclass_name>
cable qos us scheduler mode {guaranteed-plus | normal}
Casa Systems
cable qos
Properties
class {ds | us} <0:7> Sets the QoS class for the downstream or upstream
{flow-wfq {enable | service. The DOCSIS priority is from 0–7, with 7 the
max-rate <1000:2147483647>} default highest priority. The Weighted Fair Queuing
| weight <1:100>} (WFQ) scheduling algorithm prioritizes weighted
multiple traffic queues that share the same link
capacity (Release 6.4) and the US and DS service
flows within a single queue (Release 6.5.). The
weight is the bandwidth allocation, in ticks. (See
“Weighted fair queuing” for details.) The flow-wfq is
service flow WFQ, which can be enabled and its
maximum traffic rate set, in bits per second. For
details on service flow WFQ, see “Service flow
weighted fair queuing.”
Example:
CASA(config)# cable qos class ds 7

weight 100
CASA(config)# no cable qos class ds 7
ds scheduler mode Sets the QoS downstream scheduler mode to

{guaranteed-plus | normal} guaranteed-plus or normal (the default). See
“Scheduler modes” for details.
Example:
CASA(config)# cable qos ds scheduler

mode normal
temp-us-sf <svclass_name> Matches a temporary upstream service flow using a

pre-defined cable service-class name <name> with
QoS-defined settings before a CM registers with the
CMTS. Using the defined service class, this
command enables certain CMs to come online with
highest priority during high upstream traffic periods.
Example:
CASA(config)# cable qos

temp-us-sf SVCL1
CASA(config)# no cable qos temp-us-sf
Casa Systems
Cable commands 4-57
cable qos
us scheduler mode Sets the QoS upstream scheduler mode to

{guaranteed-plus | normal} guaranteed-plus or normal (the default). See
“Scheduler modes” for details.
Example:
CASA(config)# cable qos us scheduler

mode guaranteed-plus
Weighted fair queuing
Normally, bandwidth is assigned downstream and upstream in a strict priority fashion

based on the service priority class defined in the CM’s configuration file. The service
flows in each service class are scheduled round-robin unless there are traffic shaping
constraints on a particular service flow. Strict priority queuing consists of always
giving higher classes traffic priority. That is, it services a particular class until it is
empty from the highest priority to lowest. Each service class can have one of eight
DOCSIS priority levels (labeled 7–0) for downstream and upstream traffic, with
additional two system-level priorities (9 and 8) being reserved for MAC control or
real-time and guaranteed bandwidth traffic, where bandwidth should always be
available. The lower eight priority levels determine a priority hierarchy addressing the
remaining available bandwidth in a best-effort (BE) manner. These priority classes
can operate in one of two modes, strict priority (the default) and weight fair queuing
(WFQ).
In best-effort (BE) weighted fair queuing (using the weight property), the WFQ
scheduler allows contention bandwidth to be allocated across different queues at their
levels based on assigned weights. The CMTS essentially treats all the classes with
WFQ weights assigned with the same block of available remaining bandwidth and
proportions them “fairly” among the classes. All the service flows in each class
assume the aggregated weight from the service class and are treated equally.
For example, if QOS classes 2,3,4,5 have a weight configured, the scheduler services
the DOCSIS MAC (9) and guaranteed bandwidth (8) classes, then classes 7, 6, 1, and
0 in a strict priority fashion. It then services WFQ classes 5, 4, 3, and 2 round-robin
until they either exhaust their quota or it finds the queue empty. Each of the WFQ
Casa Systems
cable qos
classes is assigned a weight from 0 – 100, which determines the bandwidth proportion
for each class. The effective bandwidth assigned to each service class then becomes a
percentage in terms of the ratio of its weight to the total of all the weights assigned
with the WFQ policy.
Priority Policy Weight Bandwidth in WFQ classes

7 Strict Priority -
6 Strict Priority -
5 Weighted Fair Queue 80 80/200 = 40%
1 Strict Priority -
0 Strict Priority -
Service flow weighted fair queuing
Service flow level WFQ (using the flow-wfq property) supports finer grained
bandwidth allocation control than BE WFQ in that it can address individual service
flows in a single queue. If enabled for a particular queue level and when there is
bandwidth contention, bandwidth will be allocated to different service flows within
the queue based on the service flow’s assigned maximum sustained rate.
The service flow WFQ mechanism must be explicitly enabled using cable qos class
{ds | us} <priority> flow-wfq enable. If the maximum sustained rate is not set for the
service flow in the CM’s configuration file, a default maximum traffic rate for each
flow can be set with the max-rate property (in bits per second). If neither rates are set,
the flow assumes the default maximum traffic rate defined for the class.
CASA(config)# cable qos class ds 4 flow-wfq enable

CASA(config)# cable qos class ds 4 flow-wfq max-rate 10000
Priority: 4 Max-rate: 10000
The maximum sustained rate can be determined with the show cable modem qos
command.
CASA# show cable modem qos

Sfid Dir Curr Sid Sched Prio MaxSusRate MaxBrst …
State Type (kbps) (kbps)…
Mac Addr : c446.199d.fe6d
196613 US act 20 BE 0 25000 64000 …
204806 DS act N/A UNDEF 0 25000 64000 …
Casa Systems
Cable commands 4-59
cable qos
If guaranteed-plus scheduler mode (see below) is also turned on downstream or

upstream, only the traffic that exceeds the minimum reserved rate goes into the BE
queue and is subject to the service flow WFQ algorithm.
Scheduler modes
The default normal scheduling mode satisfies the minimum and maximum
guaranteed rate service flows, and does best-effort round-robin scheduling once the
minimum rate is fulfilled. For example, if there are two service flows (SFs) on a
channel (at maximum 38 Mbps), when 50 Mbps is sent on both streams, they each get
38/2 = 19 Mbps:
SF a — 10 Mbps Min-rate, 40 Mbps Max-rate

SF b — 0 Min-rate, 40 Mbps Max-rate
With guaranteed-plus mode, the 10 Mbps minimum rate is accounted separately

(38 - 10 Mbps = 28 Mbps). 28 Mbps then becomes available for best-effort
round-robin scheduling, so that each SF can get 28/2 = 14 Mbps. SF a thus gets a
throughput of ~(10 + 14) = 24 Mbps, while SF b gets a throughput of 14 Mbps.
Guaranteed-plus mode must be explicitly enabled.
CASA(config)# cable qos ds scheduler mode guaranteed-plus
show cable qos class {ds | us} weight
Shows the cable QoS downstream or upstream weight (bandwidth allocation) using
the Weighted Fair Queuing (WFQ) scheduling algorithm. In the example, the CMTS
uses the strict priority until it reaches priorities 4, 3, and 2, when it uses the WFQ
algorithm based on the weights set, with priority 4 having the largest weight.
CASA(config)# show cable qos class ds weight

Downstream QOS Weighted Fair Queue Allocations
----------------------------------------------
Priority: Policy: Weight:
7 Strict Priority -
6 Strict Priority -
5 Strict Priority -
4 Weighted Fair Queue 80
Casa Systems
cable qos

1 Strict Priority -
0 Strict Priority -
show cable qos class {ds | us} flow-wfq
Shows the cable QoS downstream or upstream weight (bandwidth allocation) using
the service flow WFQ scheduling algorithm. In this example, only priority 7 is
enabled to use the algorithm. If a maximum sustained traffic rate is not set for a
service flow in that class, it uses the defined default maximum rate.
CASA(config)# show cable qos class ds flow-wfq

Downstream QOS Service Flow Weighted Fair Queue Configuration
-----------------------------------------------------------
Priority: Enable: Default Maximum Rate:
7 Enabled 20000000
6 Disabled Not Set
5 Disabled Not Set
4 Disabled Not Set
3 Disabled Not Set
2 Disabled Not Set
1 Disabled Not Set
0 Disabled Not Set
show cable qos scheduler mode
Shows the cable QoS downstream and upstream scheduler mode.
CASA(config)# show cable qos scheduler mode

cable qos ds scheduler mode: normal
cable qos us scheduler mode: normal
Casa Systems
Cable commands 4-61
cable rcp-select priority
cable rcp-select priority

Purpose
The cable rcp-select priority command sets the priority for the Receive Channel
Profile (RCP) selection for the CM. (See also the rcp command in Chapter 6,
“Channel bonding.”)
Mode
(config)#
Syntax
[no] cable rcp-select <string> priority <1:100>
Properties
<string> RCP hex string (xx:xx:xx:xx:xx).

priority <1:100> RCP ID priority, the higher the number the higher the
priority. If the command is omitted, the priority is 0 (no
priority).
Example:
CASA(config)# cable rcp-select

00:10:00:00:02 priority 1
CASA(config)# no cable rcp-select
00:10:00:00:02
show cable rcp-select
Shows the RCP-selected cable modems and their priority values.
CASA(config)# show cable rcp-select

cable rcp-select 00:10:00:00:02 priority 1
cable rcp-select 00:10:00:10:02 priority 0
Casa Systems
Purpose
The cable sa-des-tlvlen-2 command sets the security association TLV length to two
bytes as required by some BPI-authenticated CMs. These modems may not be able to
register with the CMTS using a one-byte descriptor. The sa-des-tlvlen-2 value is the
default.
See the cable sa-des-tlvlen-2 command in Chapter 3, “Baseline Privacy Interface.”
Casa Systems
Cable commands 4-63
cable sec
cable sec
Purpose
The cable sec command sets the following modem security properties:
• Certification revocation lists and methods

• Configuration learning enabling
• Early Authentication Encryption (EAE) exclusion
• Encryption algorithm priority
• CM certification
• Online Certification Status Protocol (OCSP)
• Source Address Verification (SAV) authorization and configuration
• TFTP proxy option
Mode
(config)#
Syntax
[no] cable sec cert-revocation-list {refresh-interval <1:524160> | url
<url_addr>}
[no] cable sec cert-revocation-method {crl | crlAndOcsp | none | ocsp}
[no] cable sec config-file-learning
[no] cable sec eae-exclusion <1:4294967295> <mac_addr> [<mask>]
cable sec encrypt_alg_priority [aes128CbcMode] [des40CbcMode]
[des56CbcMode]
[no] cable sec modem-cert check
[no] cable sec ocsp {protocol-url <url> | signature-bypass}
[no] cable sec sav-auth-enable
[no] cable sec sav-cfg-list <name> <1:4294967295> {<ip4_addr>/<mask> |
ipv6 <ip6_addr>/<prefix>} [vrf <name>]
cable sec tftp-options {both | hw-addr | net-addr | none}
Casa Systems
cable sec
Properties
cert-revocation-list Applies a certificate revocation list, with a refresh

{refresh-interval interval, set in minutes, or a source URL for the list.
<1:524160> | url
<url_addr>} Example:
CASA(config)# cable sec

cert-revocation-list refresh-interval
600
cert-revocation-list url revlist.org
CASA(config)# no cable sec
cert-revocation-list refresh-interval
CASA(config)#
no cable sec cert-revocation-list url
cert-revocation-method {crl Applies a certificate revocation method, which can be

| crlAndOcsp | none | ocsp} using a certificate revocation list (CRL), using both a
CRL and the Online Certification Status Protocol
(OCSP), no method, or OCSP only.
Example:

cert-revocation-method crl
CASA(config)#
no cable sec cert-revocation-method
config-file-learning Enables configuration file learning, the default

behavior where the CMTS responds with
Authentication Failure in the REG-RSP message
when there is a mismatch between learned config file
parameters and REG-REQ parameters. Default
enabled. If disabled, the CMTS does not execute
config file learning and a mismatch check.
Example:

config-file-learning
CASA(config)#
no cable sec config-file-learning
Casa Systems
Cable commands 4-65
cable sec
eae-exclusion Configures Early Authentication Encryption (EAE)

<1:4294967295> <mac_addr> exclusion, which includes an ID and the CM MAC
[<mask>] address with an optional mask. There can be up to
500 EAE exclusion lists.
Example:
CASA(config)# cable sec eae-exclusion 1

0026.24a8.db36
CASA(config)# no cable sec
eae-exclusion 1 0026.24a8.db36
encrypt_alg_priority Sets the encryption algorithm priority to one or more

[aes128CbcMode] of the following, listed in their default order of
[des40CbcMode] preference:
[des56CbcMode]
• aes128CbcMode — 128-bit Advanced Encryp-
tion Standard (AES).
• des56CbcMode — 56-bit DES.
• des40CbcMode — 40-bit Data Encryption Stan-
dard (DES).
Example:

encrypt-alg-priority aes128CbcMode
des56CbcMode des40CbcMode
modem-cert check Enables a CM certificate check.
Example:
CASA(config)# cable sec modem-cert

check
CASA(config)#
no cable sec modem-cert check
Casa Systems
cable sec
ocsp {protocol-url <url> | Enables Online Certification Status Protocol (OCSP),

signature-bypass} with the URL to retrieve the OCSP information, or
signature checking on the OCSP response
messages.
Example:
CASA(config)# cable sec ocsp

protocol-url url.org
CASA(config)# cable sec ocsp
signature-bypass
CASA(config)#
no cable sec ocsp protocol-url
CASA(config)#
no cable sec ocsp signature-bypass
sav-auth-enable Enables Source Address Verification (SAV)

authorization for the CM (the default). When
dhcp-authorization is disabled on a DOCSIS MAC
domain, anyone can assign their own IP address.
This may cause conflicts and may not be desirable by
the service provider. One secure way to allow
customers authorized by their ISPs to use static IP
addresses is to enable DHCP authorization and the
sav-auth-enable feature, and set a sav-cfg-list.
Example:
CASA(config)# cable sec sav-auth-enable

CASA(config)#
no cable sec sav-auth-enable
Casa Systems
Cable commands 4-67
cable sec
sav-cfg-list <name> Sets the Source Address Verification (SAV)

<1:4294967295> {<ip4_addr>/ configuration rule, defined by a list name (maximum
<mask> | ipv6 <ip6_addr>/ 16 characters), rule ID, IPv4 or IPv6 address and
<prefix>} [vrf <name>] mask (for a contiguous range of addresses), and an
optional VRF name. The sav-cfg-list supports up to
2048 entries, 128 for static IPs. This list is then
associated with a specific modem using the
cable modem authorization command’s
<sav_cfg_list_name> property.
Example:
CASA(config)# cable sec sav-cfg-list

list1 1 6.7.8.9/24 vrf localnet
CASA(config)#
no cable sec sav-cfg-list list1 1
tftp-options {both | Configures TFTP proxy. Once an option for TFTP

hw-addr | net-addr | none} proxies is configured, the CMTS adds the
corresponding address in the TFTP message. The
options are as follows:
• both — Both the hardware and net address are

added.
• hw-addr — Only the hardware address is added.
• net-addr — Only the net address is added.
• none — Neither the hardware address nor net
address is added.
Example:
CASA(config)# cable sec tftp-options

both
Casa Systems
cable sec
show cable sec cert-revocation-list [url | refresh-interval]
Shows the CM’s certification revocation list properties.
CASA(config)# show cable sec cert-revocation-list

cable sec cert-revocation-list refresh-interval 10080
cable sec cert-revocation-list url
show cable sec cert-revocation-method
Shows the CM’s certification revocation method properties.
CASA(config)# show cable sec cert-revocation-method

cable sec cert-revocation-method none
show cable sec config-file-learning
Shows whether the CM’s configuration file learning is enabled.
CASA(config)# show cable sec config-file-learning

cable sec config-file-learning
show cable sec eae-exclusion
Shows the CM’s EAE exclusion properties.
show cable sec encrypt-alg-priority
Shows the CM’s encryption algorithm priority.
CASA(config)# show cable sec encrypt-alg-priority

cable sec encrypt-alg-priority des56CbcMode des40CbcMode aes128CbcMode
Casa Systems
Cable commands 4-69
cable sec
show cable sec ocsp [protocol-url | signature-bypass]
Shows the CM’s OCSP properties. Output can also be filtered by protocol-url or
signature-bypass.
CASA(config)# show cable sec ocsp

cable sec ocsp protocol-url
show cable sec sav-auth-enable
Shows the CM’s SAV properties.
CASA(config)# show cable sec sav-auth-enable

cable sec sav-auth-enable
show cable sec sav-cfg-list [<name>] [<rule_id>]
Shows the CM’s Source Address Verification (SAV) configuration rules. Output can
also be filtered by name and rule ID.
CASA(config)# show cable sec sav-cfg-list

cable sec sav-cfg-list merlin 1 97.64.138.169/29
show cable sec tftp-options
Shows the CM’s TFTP proxy configuration. Note that during a CMTS reset, the TFTP
option should be set to none when downloading the config file.
CASA(config)# show cable sec tftp-options

cable sec tftp-options net-addr
Casa Systems
cable service attribute withhold-TLVs peak-rate
cable service attribute withhold-TLVs

peak-rate
Purpose
The cable service attribute withhold-TLVs peak-rate command allows capping of

the burst rate by restricting the CMTS from sending the TLVs 24.27 and 25.27 for
DOCSIS 3.x peak traffic rate information to non-DOCSIS 3.x CMs.
Mode
(config)#
Syntax
[no] cable service attribute withhold-TLVs peak-rate
show cable service-class [brief | verbose]
Shows any peak traffic rate settings. Output can also be brief or verbose.
CASA(config)# show cable service-class verbose

cable service-class 1
peak-traffic-rate 0
show cable modem qos
Shows the maximum burst and peak traffic rate settings.
CASA(config)# show cable modem qos

Sfid Dir Curr Sid Sched Prio MaxSusRate MaxBrst MinRsvRate
State Type (kbps) (kbps)
PeakTrafRate Throughput ServiceClassName
(kbps) (kbps)
Mac Addr : 7cb2.1b42.b1be
16388 US act 3 BE 0 16 3044 12
0 0
Casa Systems
Cable commands 4-71
cable service-class
cable service-class
Purpose
The cable service-class command sets parameters for DOCSIS cable service classes.
Service classes support the QoS profile number, traffic priority, maximum upstream
bandwidth, guaranteed upstream bandwidth, maximum downstream bandwidth,
maximum transmit burst length, baseline privacy enable/disable, and type of service
(ToS) overwrite byte. The service class requires an ID and a name.
Modes
(config)#
(conf-service-class <id>)# | (conf-default-ugs)#
Syntax
(config)# [no] cable service-class {<1:1024> | default_ugs}
(conf-service-class x)#
[(conf-default-ugs)#]
name <name>
activity-timeout <0:65535>
admission-timeout <0:65535>
app-id <0:4294967295>
attr-aggr-rule-mask <0x0:0xffffffff>
downstream
ds-resequencing {noResequencingDsid | resequencingDsid}
dscp-overwrite <-1:63>
forbidden-attr-mask <0x0:0xffffffff>
grant-interval <0:4294967295>
grant-jitter <0:4294967295>
grant-size <0:65535>
grants-per-interval <0:127>
max-buff-size <0:4294967295>
max-concat-burst <0:65535>
max-latency <0:4294967295>
max-outstanding-bytes-per-sid-cluster <0:4294967295>
max-req-per-sid-cluster <0:255>
max-time-in-sid-cluster <0:65535>
max-tot-bytes-req-per-sid-cluster <0:4294967295>
max-traffic-burst <1522:4294967295>
max-traffic-rate <0:4294967295>
min-buff-size <0:4294967295>
min-packet-size <0:65535>
min-reserved-rate <0:4294967295>
Casa Systems
cable service-class
multiplier-bytes-req <bytes>
multiplier-contention-req-window <4:12>
peak-traffic-rate <0:4294967295>
poll-interval <0:4294967295>
poll-jitter <0:4294967295>
priority <0:7>
req-trans-policy <0x0:0xffffffff>
required-attr-mask <0x0:0xffffffff>
sched-type {bestEffort | nonRealTimePollingService |
realTimePollingService | undefined | unsolicitedGrantService
| unsolicitedGrantServiceWithAD}
storage-type {nonVolatile | other | permanent | readOnly |
volatile}
tar-buff-size <0:4294967295>
tos-overwrite <0x0:0xff> <0x0:0xff>
upstream
Properties
{<1:1024> | default_ugs} Service class ID, or the default QoS for the
Unsolicited Grant Service (UGS).
Example:
CASA(config)# cable
service-class 1
CASA(conf-service-class 1)#
CASA(config)#
no cable service-class 1
name <name> Required service class name associated with

the service class instance, 1–15 characters.
(Does not apply to default_ugs.)
Example:
CASA(conf-service-class 1)# name

SRVCL1
Casa Systems
Cable commands 4-73
cable service-class
activity-timeout <0:65535> Service class activity timeout, in seconds.

Example:
activity-timeout 600
admission-timeout <0:65535> Service class admission timeout, in seconds.

Applies also to default_ugs.
Example:
admission-timeout 600
app-id <0:4294967295> Service class application ID. Applies also to

default_ugs.
Example:
app-id 21345
attr-aggr-rule-mask Service class attribute aggregation rule bit

<0x0:0xffffffff> mask, default 0x0. Applies also to
default_ugs.
Example:
attr-aggr-rule-mask 0x0
downstream Enables the downstream service class. (Does

not apply to default_ugs.)
Example:
downstream
Casa Systems
cable service-class
ds-resequencing Sets downstream resequencing, as no

{noResequencingDsid | resequencing or resequencing (the default).
resequencingDsid} (Does not apply to default_ugs.)
Example:
ds-resequencing
noResequencingDsid
dscp-overwrite <-1:63> Enables Differentiated Services Code Point

(DSCP) overwrite, default -1 (no overwrite).
Example:
dscp-overwrite -1
forbidden-attr-mask Mask for forbidden attributes, default 0x0.

<0x0:0xffffffff> Applies also to default_ugs.
Example:
forbidden-attr-mask 0x0
grant-interval <0:4294967295> Grant interval, in microseconds, default 0.
Example:
grant-interval 0
grant-jitter <0:4294967295> Grant jitter interval, default 0. Applies also to

default_ugs.
Example:
grant-jitter 0
Casa Systems
Cable commands 4-75
cable service-class
grant-size <0:65535> Unsolicited grant size, in bytes, default 0,

applies to unsolicitedGrantService and
unsolicitedGrantServiceWithAD only. (Does
Example:
grant-size 0
grants-per-interval <0:127> Grants per interval, default 0. (Does not apply

to default_ugs.)
Example:
grants-per-interval 0
max-buff-size <0:4294967295> Maximum buffer size in bytes, default 0.

Example:
max-buff-size 0
max-concat-burst <0:65535> Maximum concatenated bursts, default

40000 bytes. (Does not apply to
default_ugs.)
Example:
max-concat-burst 40000
Casa Systems
cable service-class
max-latency <0:4294967295> Maximum latency, in microseconds, default 0.

Example:
max-latency 0
max-outstanding-bytes-per-sid- Maximum outstanding bytes per SID cluster,

cluster <0:4294967295> default 0. (Does not apply to default_ugs.)
Example:
max-outstanding-bytes-per-sid-
cluster 0
max-req-per-sid-cluster Maximum requests per SID cluster, default 0.

<0:255> (Does not apply to default_ugs.)
Example:
max-req-per-sid-cluster 0
max-time-in-sid-cluster Maximum time in the SID cluster, default 0.

Example:
max-time-in-sid-cluster 0
max-tot-bytes-req-per-sid-clus Maximum total bytes requested per SID,

ter <0:4294967295> default 0. (Does not apply to default_ugs.)
Example:
max-tot-bytes-req-per-sid-cluster
0
Casa Systems
Cable commands 4-77
cable service-class
max-traffic-burst Maximum traffic bursts, default 40000 bytes.

Example:
max-traffic-burst 40000
max-traffic-rate Maximum traffic rate, default 0 (no traffic rate

<0:4294967295> enforced). (Does not apply to default_ugs.)
Example:
max-traffic-rate 0
min-buff-size <0:4294967295> Minimum buffer size in bytes, default 0. (Does

Example:
min-buff-size 0
min-packet-size <0:65535> Minimum packet size in bytes, default 0.

Example:
min-packet-size 0
min-reserved-rate Minimum reserved rate in bps, default 0 (no

<0:4294967295> bandwidth reserved). (Does not apply to
default_ugs.)
Example:
min-reserved-rate 0
Casa Systems
cable service-class
multiplier-bytes-req <bytes> Multiplier bytes requested, as 1, 2, 4, 8, or 16

bytes; default 4. (Does not apply to
default_ugs.)
Example:
multiplier-bytes-req 4
multiplier-contention-req-wind Multiplier contention request window, default

ow <4:12> 8. (Does not apply to default_ugs.)
Example:
multiplier-contention-req-window
8
peak-traffic-rate Allows capping of the burst rate, in kilobits

<0:4294967295> per second, default 0. (Does not apply to
default_ugs.)
Example:
peak-traffic-rate 0
poll-interval <0:4294967295> Polling interval, in microseconds, default 0.

Example:
poll-interval 0
Casa Systems
Cable commands 4-79
cable service-class
poll-jitter <0:4294967295> Polling jitter, in microseconds, default 0,

applies to realtimePolllingService and
unsolicitedGrantServiceWithAD only. Applies
also to default_ugs.
Example:
poll-jitter 0
priority <0:7> Priority level. (Does not apply to

default_ugs.)
Example:
priority 0
req-trans-policy Requested transmit policy bit mask,

<0x0:0xffffffff> default 0x0. (Does not apply to default_ugs.)
Example:
req-trans-policy 0x0
required-attr-mask Required attribute bit mask, default 0x0.

<0x0:0xffffffff> Applies also to default_ugs.
Example:
required-attr-mask 0x0
Casa Systems
cable service-class
sched-type {bestEffort | Scheduler type, default bestEffort, undefined

nonRealTimePollingService | if downstream. (Does not apply to
realTimePollingService | default_ugs.)
undefined |
unsolicitedGrantService | Example:
unsolicitedGrantServiceWithAD}
sched-type bestEffort
storage-type {nonVolatile | Storage type. (Does not apply to

other | permanent | readOnly | default_ugs.)
volatile}
Example:
storage-type nonVolatile
tar-buff-size <0:4294967295> Target or desired buffer size for the service

flow queue in bytes, default 0. (Does not
apply to default_ugs.)
Example:
tar-buff-size 0
tos-overwrite <0x0:0xff> QoS service class TOS and mask, default

<0x0:0xff> 0xFF 0x0. Applies also to default_ugs.
Example:
tos-overwrite 0xff 0x0
upstream Enables the upstream service class. (Does

Example:
upstream
Casa Systems
Cable commands 4-81
cable service-class
Applying service classes to modem configuration files
To apply the service class parameters, specify the service class name in TLV 24/25.4.
For example:
Main
{
NetworkAccess 1;
UsServiceFlow
{
UsServiceFlowRef 1;
QosParamSetType 7;
ServiceClassName "test"; >specify name here
SchedulingType 2;
}
DsServiceFlow
{
DsServiceFlowRef 3;
ServiceClassName "test-ds"; >specify name here; suppose you defined a
service class name "test-ds "on cmts
QosParamSetType 7;
}
MaxCPE 8;
GlobalPrivacyEnable 0;
/* CmMic 1be76c7df4777d078f76a3eb45d650d5; */
/* CmtsMic 6cf3523752bbd5bd627bb05460f1ff27; */
/* EndOfDataMkr*/
/* Pad */
}
show cable service-class [<index> | default-ugs]
Shows the cable service class activity. Output can also be filtered by service-class ID
or default Unsolicited Grant Service (UGS) data grant.
CASA# show cable service-class 1

Index Name Dir Sched Prio MaxSusRat MaxBurst MinRsvRate
1 SRVCL1 US BE 0 0 3044 0
Casa Systems
cable service-class
show cable service-class brief
Shows a subset of the configured cable service class settings.
CASA# show cable service-class brief

name SRVCL1
min-packet-size 0
activity-timeout 500
admission-timeout 500
tos-overwrite 0xFF 0x0
app-id 500
…
show cable service-class verbose
Shows the full configured cable service class settings.
CASA# show cable service-class verbose

name SRVCL1
priority 0
max-traffic-rate 0
max-traffic-burst 3044
min-reserved-rate 0
min-packet-size 0
max-concat-burst 1522
…
Casa Systems
Cable commands 4-83
cable service-flow active-timeout
cable service-flow active-timeout

Purpose
The cable service-flow active-timeout command manages and removes idle

upstream service flows for PacketCable implementations where a policy server is not
used.
Mode
(config)#
Syntax
cable service-flow active-timeout <0:600> [force-delete]
no cable service-flow active-timeout
Properties
<0:600> Active timeout period, default 60 seconds.

force-delete Optionally overrides the service flow timeout and
deletes the service completely.
Example:
CASA(config)# cable service-flow

active-timeout 60 force-delete
CASA(config)# no cable service-flow
active-timeout
Casa Systems
cable service-type-id ds-frequency
cable service-type-id ds-frequency

Purpose
The cable service-type-id ds-frequency command moves D2.0 CMs between two
CMTS platforms. The command configures up to 128 frequency entries. Traffic on
these downstream frequencies that are not matched to a service-group on the local
CMTS are moved to the other CMTS. There can be up to 524,288 service flows, with
up to 120,000 for DCU, 65525 per 8x8 card, and 174,080 per 8x96 card. Use the show
cable service-type-id command to display the ID settings.
Mode
(config)#
Syntax
[no] cable service-type-id <id> ds-frequency <47000000:999000000>
Properties
<id> Service type ID, maximum 16 characters.

ds-frequency Required downstream frequency, in Hz.
<47000000:999000000>
Example:
CASA(config)# cable service-type-id VOD

ds-frequency 591000000
CASA(config)# cable service-type-id
DATA ds-frequency 639000000
CASA(config)# show cable
service-type-id
cable service-type-id VOD ds-frequency
591000000
cable service-type-id DATA ds-frequency
639000000
CASA(config)#
no cable service-type-id vod
Casa Systems
Cable commands 4-85
cable spectrum
cable spectrum
Purpose
The cable spectrum command sets spectrum management properties for the CM.
Forward-hopping from QPSK to 32QAM, 64QAM or 16QAM takes place depending
on the calculated SNR and thresholds, unless back-hopping is applied.
Mode
(config)#
Syntax
cable spectrum back-hop-step
cable spectrum cm-mode-monitor-period <5:3600>
cable spectrum hop-period <5:3600>
cable spectrum monitor-period <5:3600>
cable spectrum syslog
[no] cable spectrum trap
Properties
back-hop-step Enables spectrum modulation or channel-width

back-hopping one step at a time, depending on the
spectrum rule action, and as determined by the
SNR. For example, a modulation back-hop from
QPSK to 64QAM will be in steps QPSK, 16QAM,
32QAM, and 64QAM. A channel-width back-hop from
800 KHz to 6.4 MHz will be in steps 0.8 MHz,
1.6 MHz, 3.2 MHz, and 6.4 MHz The default is no
back-hopping.
Example:
CASA(config)# cable spectrum

back-hop-step
CASA(config)#
no cable spectrum back-hop-step
Casa Systems
cable spectrum
cm-mode-monitor-period Sets the CM mode spectrum monitoring polling

<5:3600> interval, default 45 seconds. (See the spectrum rule
command.)
Example:

cm-mode-monitor-period 60
hop-period <5:3600> Sets the hop period, in seconds, default 30 seconds.
Example:
CASA(config)# cable spectrum hop-period

60
monitor-period <5:3600> Sets the spectrum monitoring period, in seconds.
Example:

monitor-period 60
syslog Enables system logging on spectrum hops. Be sure

to configure syslog hosts to receive the log
messages.
Example:
CASA(config)# cable spectrum syslog

CASA(config)# no cable spectrum syslog
trap Enables three traps for spectrum management:

casaCsmModulationChangeNotification,
casaCsmChannelWidthChangeNotification, and
casaCsmFreqHoppingNotification.
Example:
CASA(config)# cable spectrum trap

CASA(config)# no cable spectrum trap
Casa Systems
Cable commands 4-87
cable spectrum
show spectrum rule
Shows the cable spectrum settings at the beginning of the output.
CASA(config)# show spectrum rule

cable spectrum hop period 30
cable spectrum monitor-period 10
cable spectrum cm-mode-monitor-period 60
cable spectrum trap
…
Casa Systems
cable subscriber over-consume trap
cable subscriber over-consume trap

Purpose
The cable subscriber over-consume trap command sets a trap for subscribers who
exceeded the maximum allowed bandwidth.
Mode
(config)#
Syntax
[no] cable subscriber over-consume trap
Casa Systems
Cable commands 4-89
cable tag
cable tag
Purpose
The cable tag command defines a cable tag and sets its properties. Cable tagging
allows restricted load balancing (RLB) of policy-based traffic based on how modems
are classified. The command sets the attributes that classifies a matching modem type
to a unique Load balancing policy at the CMTS. Each cable tag is identified by a
unique name and can include up to eight attributes for DOCSIS version and device
class, organizationally unique identifier (OUI), priority, service type identifier, and
type length value (TLV).
Modes
(config)#
(conf-cable-tag <name>)#
Syntax
(config)# [no] cable tag <name>
(conf-cable-tag x)#
[no] docsis device class {eMTA | eSTB}
[no] docsis version {docsis10 | docsis11 | docsis20 | docsis30 |
docsis31}
[no] oui <xx:xx:xx>
priority <1:2560>
[no] service-type-id <name>
tlv ext-upstream-freq-range {0 | 1}
no tlv ext-upstream-freq-range
Properties
<name> Cable tag name, maximum 16 characters.
Example:
CASA(config)# cable tag TAG1

CASA(conf-cable-tag TAG1)# exit
CASA(config)#
no cable tag TAG1
Casa Systems
cable tag
docsis device class Sets the DOCSIS device class for the cable tag,
{eMTA | eSTB} either eMTA for embedded Multimedia Terminal
Adapter (MTA), or eSTB for embedded Set-Top Box
(STB).
Example:
CASA(conf-cable-tag TAG1)# docsis

device class eMTA
CASA(conf-cable-tag TAG1)# no docsis
device class eMTA
docsis version {docsis10 Sets the DOCSIS version to DOCSIS 1.0, 1.1, 2.0,
| docsis11 | docsis20 | 3.0, or 3.1.
docsis30 | docsis31}
Example:
CASA(conf-cable-tag TAG1)# docsis

version docsis10
CASA(conf-cable-tag TAG1)#
no docsis version docsis10
oui <xx:xx:xx> Sets the Organizationally Unique Identifier (OUI) for

the cable tag in a three-byte format.
Example:
CASA(conf-cable-tag TAG1)# oui 12:34:56

no oui 12:34:56
priority <1:2560> Sets the tag priority, unique across the system,
default 1. When more than one cable tag is present in
the configuration, the tag with the highest priority is
selected first.
Example:
CASA(conf-cable-tag TAG1)# priority 1
Casa Systems
Cable commands 4-91
cable tag
service-type-id <name> Adds a cable service-type-id ds-frequency name

for the tag, maximum 16 characters, embedded in
quotes if blank spaces.
Example:
service-type-id plant1
no service-type-id plant1
tlv Determines type-length-value (TLV) extended

ext-upstream-freq-range upstream frequency range support, 0 for no or 1 for
{0 | 1} yes.
Example:
CASA(conf-cable-tag TAG1)# tlv

ext-upstream-freq-range 1
no ext-upstream-freq-range
show cable tag [<name>]
Shows the cable tag settings, optionally for a specific tag name.
CASA(config)# show cable tag
cable tag TAG1

priority 1
docsis device class eMTA
docsis version docsis30
oui 12:12:12
tlv ext-upstream-freq-range 1
service-type-id SType xxx
Casa Systems
cable tcc us-bonding-disable
cable tcc us-bonding-disable

Purpose
The cable tcc us-bonding-disable command disables transmit channel configuration

(TCC) bonding to the upstream channel.
Mode
(config)#
Syntax
[no] cable tcc us-bonding-disable
Casa Systems
Cable commands 4-93
Purpose
The cable traffic-policy command configures Subscriber Traffic Management

(STM). STM allows CMTS users to monitor and enforce upstream or downstream
transmission rates for subscribers. Subscribers who exceed the enforced maximum
bandwidth and channel utilization are switched automatically to a lower rate quality of
service (QoS) during the peak traffic penalty period (in minutes).
Modes
(config)#
(traffic-policy <name>)#
Syntax
(config)# [no] cable traffic-policy <name>
(traffic-policy x)#
channel-utilization-threshold <0:100>
downstream
duration <10:1440> [sample-interval <5:60>] [avg-rate
<1:4294967295>]
[no] enable
enforce {max-traffic-rate <1:4294967295> [no-persistence] |
percentage <1:100>} [no-persistence] | priority <0:7>}
max-traffic-rate <0:4294967295>
[no] peak-time1 {daily | weekday | weekend} <0:23> duration
<60:1440>
<60:1440>
<60:1440>
<60:1440>
penalty-enforce {all-day | peak-only}
penalty-period <5:10080>
upstream
Casa Systems
Properties
<name> Cable traffic policy name, maximum 15 characters.
Example:
CASA(config)# cable traffic-policy

TRPOL1
CASA(traffic-policy TRPOL1)#
CASA(config)#
no cable traffic-policy TRPOL1
channel-utilization-thre Percentage threshold of the channel utilization. STM

shold <0:100> applies penalty-enforce to the service flow if the
traffic rate and channel utilization are above the
threshold during the duration period. The default is
0, no limitation.
Example:
channel-utilization-threshold 70
downstream Binds the traffic policy to the downstream channel,

and replaces the upstream setting.
Example:
CASA(traffic-policy TRPOL1)# downstream
duration <10:1440> Duration of the traffic policy, default 300 (5 hours).

[sample-interval <5:60>] The optional sample interval defaults to 15 minutes,
[avg-rate and can be followed by the average rate setting
<1:4294967295>] (default 10000000 b/s).
Example:
CASA(traffic-policy TRPOL1)# duration

300 sample-interval 15 avg-rate 300
Casa Systems
Cable commands 4-95
enable Enables (or disables) the cable traffic policy.

Enabling first requires setting the max-traffic-rate.
Example:
CASA(traffic-policy TRPOL1)# enable

CASA(traffic-policy TRPOL1)# no enable
enforce Enforces changing the max-traffic-rate to a new

{max-traffic-rate fixed value, changing it to a percentage of
<1:4294967295> provisioned value, or setting a priority value. The
[no-persistence] | percentage property defaults to 50%, with 100% as
percentage <1:100>} monitor mode. The optional no-persistence modifier
[no-persistence] | for the percentage indicates that the enforced rule
priority <0:7>} should not remain enforced when a CM reboots (the
default is persistence). The priority property
accommodates networks where changing the
max-traffic-rate is not feasible, and is disabled by
default. CMs that match the max-traffic-rate and
exceed the average rate for the configured duration
use the enforce priority setting under penalty, with 0
being the lowest priority. If the priority value is higher
than the original QoS priority, no penalty is enforced
on the affected service flow. Only the priority
property can take the no form.
Example:
CASA(traffic-policy TRPOL1)# enforce

priority 7
no enforce priority
max-traffic-rate Maximum traffic rate in bits/second. This rate must

<0:4294967295> first be set before enabling the traffic policy.
Example:
max-traffic-rate 600
Casa Systems
peak-time1 {daily | Sets the first peak time in a day, and can be set daily,
weekday | weekend} weekdays, or weekends, followed by the hour start
<0:23> duration time and duration in minutes, with the duration not
<60:1440> crossing midnight.
Example:
CASA(traffic-policy TRPOL1)# peak-time1

daily 12 duration 120
no peak-time1 daily
peak-time2 {daily | Sets the second peak time in a day, and can be set
weekday | weekend} daily, weekdays, or weekends, followed by the hour
<0:23> duration start time and duration in minutes, with the duration
<60:1440> not crossing midnight.
Example:

no peak-time2 weekend
peak-time3 {daily | Sets the third peak time in a day, and can be set
Example:

no peak-time3 weekday
Casa Systems
Cable commands 4-97
peak-time4 {daily | Sets the fourth peak time in a day, and can be set
Example:

no peak-time4 daily
penalty-enforce {all-day Time to enforce the penalty, either all-day (the

| peak-only} default) or peak-only.
Example:
penalty-enforce all-day
penalty-period <5:10080> Penalty period, default 1440 minutes (one day).
Example:
penalty-period 1440
upstream Binds the traffic policy to the physical upstream port

(the default), and replaces the downstream setting.
Example:
CASA(traffic-policy TRPOL1)# upstream
Casa Systems
clear cable subscriber-usage
Clears all cable subscriber usage data.
CASA(config)# clear cable subscriber-usage
show cable traffic-policy
Shows the cable traffic policy.
CASA(config)# show cable traffic-policy

cable traffic-policy TRPOL1
upstream
enforce percentage 50
penalty-period 1440
penalty-enforce all-day
duration 300 sample-interval 15 avg-rate 10000000
show cable subscriber-usage [over-consume]
Shows the cable subscriber usage, which depends on a traffic policy being defined.
The optional over-consume modifier shows only those subscribers who exceeded
their maximum allowed bandwidth. Output can also be filtered by MAC address and
DOCSIS MAC domain (with an added service-group filter).
CASA(config)# show cable subscriber-usage

MAC Address Sfid
Dir Enforce-rule Max-Rate Last-detect Last-penalty Pen Util
Name kbps time time Flag
show cable modem [<mac_addr>] qos
This command shows an asterisk (*) in the Prio (priority) or MaxSusRate (maximum
sustain rate) columns for those CMs under traffic priority enforcement penalty based
on the subscriber traffic management (STM) rule. A penalized modem exceeds the
average rate for the configured duration period and where the enforce priority setting
is applied when setting the cable traffic-policy.
Casa Systems
Cable commands 4-99
cable upstream
cable upstream
Purpose
The cable upstream command sets certain upstream properties.
Mode
(config)#
Syntax
cable upstream hi-power <0:6>
cable upstream snr-interval <0:600>
Properties
hi-power <0:6> Sets the CM output level to a higher upstream power

level, in decibels per millivolt (dBmV), default 0
(disabled).
Example:
CASA(config)# cable upstream hi-power 0
snr-interval <0:600> Sets the time interval for the re-averaging of

signal-to-noise ratio (SNR) graphing statistics when
there are excessive upstream SNR fluctuations over
certain time periods. The CMTS performs the SNR
averaging at the specified time interval in seconds,
default 0 (disabled).
Example:
CASA(config)# cable upstream

snr-interval 0
Casa Systems
cable upstream
show upstream [<slot>/<port>.<pchan>[/<lchan>]] burst-noise
Shows the upstream burst noise, if enabled. The logical channel output also shows the
burst noise event details, including the percentage and absolute values of the
correctable and uncorrectable burst events.
CASA(config)# show upstream burst-noise

upstream channel burst noise rate (events/sec)
12/0.0/0 0.0
12/0.0/1 0.0
12/0.1/0 0.0
…
CASA# show upstream 11/0.0/1 burst-noise

Burst Noise Stats for Channel 11/0.0/1:
Burst noise event rate: 5.8 events/second.

Percentage of Correctable Burst Events: 39 %
Percentage of Uncorrectable Burst Events: 60 %
Burst Duration (microseconds) % of Events Max Power (in dB)

----------------------------- ----------- -----------------
0 to 1 0 0
1 to 3 0 0
3 to 10 0 0
10 to 50 0 0
50 to 500 0 0
500 to 2000 0 0
2000 to 10000 0 0
10000 to 50000 0 0
> 50000 0 0
show cable channel utilization
Shows the cable upstream and downstream channel utilization.
CASA# show cable channel utilization

Downstream Total-BW Utilization Online Secondary
Slot/Port/Channel (Mb/Sec) Percentage Modems Modems Channel
Description
----------------------------------------------------------------------
2/0/0 (549000000 Hz) 42.9 3 0 0 3
2/0/1 (555000000 Hz) 42.9 0 0 0 3
2/0/2 (561000000 Hz) 42.9 0 0 0 3
2/0/3 (567000000 Hz) 42.9 0 0 0 3
Casa Systems
Cable commands 4-101
cable upstream
2/0/4 (573000000 Hz) 42.9 0 0 0 2

2/0/5 (579000000 Hz) 42.9 0 0 0 2
2/0/6 (585000000 Hz) 42.9 0 0 0 2
2/0/7 (591000000 Hz) 42.9 0 0 0 2
2/0/8 (597000000 Hz) 42.9 0 0 0 2
2/0/9 (603000000 Hz) 42.9 0 0 0 2
2/0/10 (609000000 Hz) 42.9 0 0 0 2
2/0/11 (615000000 Hz) 42.9 0 0 0 2
…
show cable modem phy
Shows the power setting and SNR for upstream traffic, if enabled. Channels in partial
state are appended with a hash mask (#). The output also shows any Orthogonal
Frequency Division Multiplexing (OFDM) channel information.
CASA(config)# show cable modem phy

MAC Address USIF DSIF Sid USPwr USSNR Timing MReflec DSPwr DSSNR Mode
TX RX (dBmV) Offset (dBc) (dB) (dB)
00d0.59e1.x 2/11/25 18 0.0 -0.5 42.1 - 36 -2.6 42.9 ofdma
0018.4de7.x 11/0.0/0 1/0/0 1 - -0.5 30.8 - - - - tdma
c446.199d.x 11/0.0/0 1/0/0 5 - 0.7 27.4 - - - - tdma
Casa Systems
reg-rsp-original-upstream-action
Purpose
The reg-rsp-original-upstream-action command enables the CMTS to use the ADD

action for the original upstream channel in the REG-RSP-MP message. By default, or
if disabled with the no form of the command, the CMTS uses the NO ACTION action
for the original upstream channel in the REG-RSP-MP message.
Mode
(config)#
Syntax
[no] reg-rsp-original-upstream-action
show run | incl reg-rsp
Shows whether the upstream action is enabled.
CASA# show run | incl reg-rsp

Casa Systems
5-1
Chapter 5. Cable modem commands
Cable modem commands description

In order for cable modems in the subscriber distribution areas to establish two-way
communication with the CMTS, CMs must first initialize by listening and learning
how to receive transmissions from the CMTS downstream channels, and then by
learning how to transmit to the CMTS over the upstream channels. Modem
initialization begins when the modem is connected to the cable provider's network and
powered on. The modem listens for MAC management message (MMM) broadcasts
from the CMTS. Using QAM modulated signals, the MMM carries the 188-byte
MPEG-2 transport stream for modem synchronization with the MAC domain, as well
as the upstream channel descriptors (UCDs) and their associated MAP packets for
establishing upstream transmissions, and a MAC domain description (MDD) for D3.0
modems capable of channel bonding. Once the CM is able to listen for and receive the
MPEG-2 transport streams that are modulated on the downstream carrier signals, the
modem begins the initial ranging process over the upstream channels.

code (IUC). The IUC schedules the initial ranging interval in the upstream time line to
the CMTS. Once a transmission interval is set, the MAC domain then adjusts CM
frequency, power, and delay for two-way communication. In large networks with
many CMs attempting to register with the CMTS at the same time, initial ranging
requests are subject to collisions with requests from other modems. Each initial
ranging request is considered an initial ranging opportunity. Because of the high
probability of collisions, the MAC domain uses a ranging backoff algorithm to tell the
modem how long to wait before retransmitting another initial ranging request.
Casa Systems
Cable modem commands description
Table 5-1 lists and briefly describes the objects related to cable modem commands.
Table 5-1. Cable modem command objects
cable modem General cable modem command.

cable modem <mac_addr> Changes a CM’s upstream and downstream channels using
dbc the Dynamic Bonding Change (DBC) method.
cable modem <mac_addr> Changes a CM’s upstream and downstream channels using
dcc the Dynamic Channel Change (DCC) method.
cable modem <mac_addr> Maps a MAC address to a VLAN for Layer 2 VPN (L2VPN).
l2vpn-map
cable modem <mac_addr> Maps a MAC address to a Multi-Protocol Label Switching
mpls (MPLS) VPN.
cable modem <mac_addr> Changes the quality of service (QoS) parameters for
qos-override upstream and downstream primary service flows.
cable modem <mac_addr> Changes an upstream channel using the Upstream
ucc upstream Channel Change (UCC) method.
cable modem Sets authorization for a specific CM.
authorization
cable modem deny Denies service to a specific modem.
cable modem Detects interface utilization and prevents granting more
excessive-request requested bandwidth than necessary to an upstream
detection service flow.
cable modem offline Clears modems previously registered with the CMTS but off
aging line for a specified number of hours.
cable modem remote-query Sets the remote query polling interval.
cable modem rip Allows bypass of Router Information Protocol (RIP)
authentication-bypass authentication for specified modems.
cable modem vendor Adds a user-defined CM vendor or modifies the system
default CM vendor.
cm-ctrl Triggers a CM control request message (cm_ctrl_req_msg).
default cable modem Sets a system default CM vendor.
vendor
Casa Systems
Cable modem commands 5-3
cable modem
cable modem
Purpose
The cable modem commands set various CM properties. Some require specifying the
MAC address of the CM, others do not. The maximum number of CMs is 65536, with
a maximum UPS of 3000 and downstream 16384 per card.
The Dynamic Bonding Change (DBC) and Dynamic Channel Change (DCC) methods
include a choice of the initial technique for moving a CM to a new channel. The
initial-tech options are as follows:
• broadcast-ranging — The CM broadcasts the full initial ranging request without

going off-line and performing re-registration with the CMTS.
• direct — The initial technique default setting. The CM moves directly to another
channel without performing any type of ranging.
• period-ranging — The CM moves to a new channel, but performs periodic
ranging requests for an improved channel opportunity.
• reinitialize-mac — The CM MAC address is reset, forcing the CM off-line and
re-registering with the CMTS on the new channel.
• unicast-ranging — The CM performs an initial ranging request for a dedicated
channel from the CMTS where there is no other transmission activity.
See the “Other related commands” for the clear cable modem commands.
Modes
#
(config)#
Casa Systems
cable modem <mac_addr> dbc

Purpose
The cable modem <mac_addr> dbc command changes a CM’s upstream and
downstream channels using the Dynamic Bonding Change (DBC) method. DBC
moves a DOCSIS 3.x modem’s downstream service flows to different channels in the
modem’s receive channel set. DBC also moves D3.0 upstream service flows to
different channels in the current transmit channel set. The DBC configuration is for
the downstream or upstream list, or sets Receive Channel Profile (RCP) properties.
Up to 64 downstream service flows are supported per CM.
Modes
#
(config)#
Syntax
cable modem <mac_addr> dbc downstream-list <list> initial-tech
{broadcast-ranging | direct | period-ranging | reinitialize-mac
| unicast-ranging}
cable modem <mac_addr> dbc downstream-list <list> upstream-list <list>
initial-tech {broadcast-ranging | direct | period-ranging |
reinitialize-mac | unicast-ranging}
cable modem <mac_addr> dbc rcp-id <id> rcc-id <1:255> [upstream-list
<list>] initial-tech {broadcast-ranging | direct |
period-ranging | reinitialize-mac | unicast-ranging}
cable modem <mac_addr> dbc upstream-list <list> initial-tech
| unicast-ranging} [ofdma-initial-tech {broadcast-ranging |
probing | station-ranging | unicast-ranging}]
Properties
<mac_addr> MAC address of the CM, in xxxx.xxxx.xxxx format,

which is required and followed by other properties.
Casa Systems
dbc downstream-list <list> Sets the Dynamic Bonding Change (DBC)

initial-tech downstream list for the CM followed by the initial
{broadcast-ranging | direct technique (as described for the cable modem
| period-ranging | command). The downstream list defines the
reinitialize-mac | downstream channels as a comma-separated list,
unicast-ranging} such as 1,2,3. The first entry is the primary channel.
The channel must be included in the service group
for the requested channel change.
Example:
CASA# cable modem 0005.caa3.cf6c dbc

downstream-list 1,2,3 initial-tech
broadcast-ranging
dbc downstream-list <list> Sets the DBC downstream list for the CM followed by
upstream-list <list> the upstream list and initial technique (as described
initial-tech for the cable modem command). The downstream
{broadcast-ranging | direct list defines the downstream channels as a
| period-ranging | comma-separated list, such as 1,2,3. The upstream
reinitialize-mac | list defines the upstream channels in the same way.
unicast-ranging} The channel must be included in the service group
for the requested channel change.
Example:

downstream-list 1,2,3 upstream-list
1,2,3 initial-tech direct
Casa Systems
dbc rcp-id <id> rcc-id Sets Dynamic Bonding Change (DBC) Receive
<1:255> [upstream-list Channel Profile (RCP) properties for channel
<list>] initial-tech bonding. The properties are as follows:
{broadcast-ranging | direct
| period-ranging | • rcp-id <id> — Defines the RCP ID, in the format
reinitialize-mac | xx:xx:xx:xx:xx. (See the channel bonding rcp
unicast-ranging} command.)
• rcc-id <1:255> — Defines the Receive Channel
Configuration (RCC) based on the MAC domain
ID. (See the channel bonding rcc command.)
• upstream-list <list> — Optionally defines the
upstream channels as a comma-separated list,
such as 1,2,3. The channel must be included in
the service group for the requested channel
change.
• initial-tech — Sets the initial technique to use for
moving CMs, as described for the cable modem
command.
Example:

rcp-id 00:10:00:10:02 1 upstream-list
1,2,3 initial-tech unicast-ranging
dbc upstream-list <list> Sets the DBC upstream list for the CM followed by
initial-tech the initial technique (as described for the cable
{broadcast-ranging | direct modem command). The upstream list defines the
| period-ranging | upstream channels as a comma-separated list, such
reinitialize-mac | as 1,2,3. The channel must be included in the service
unicast-ranging} group for the requested channel change. OFDMA
[ofdma-initial-tech initial-tech load-balancing parameters can also be
{broadcast-ranging | added. The default OFDMA initial-tech is
probing | station-ranging | broadcast-ranging.
unicast-ranging}]
Example:

upstream-list 1,2,3 initial-tech direct
Casa Systems
show cable modem dbc-failure
Shows CMs that have a non-zero DBC failure count and are failing DBC with the
CMTS. The command displays the total number of DBC failures and timeouts per
DSID, and the last DBC error code.
CASA# show cable modem dbc-failure

MAC Address Total TimeOut DSID LastCode
e448.c7ba.5260 10 10 8 537(RETRY_EXHAUST)
Casa Systems
cable modem <mac_addr> dcc

Purpose
The cable modem <mac_addr> dcc command changes a CM’s upstream and
downstream channels using the Dynamic Channel Change (DCC) dynamic service
flow method. The DCC configuration sets the change frequency or initial technique
for the upstream channel.
Modes
#
(config)#
Syntax
cable modem <mac_addr> dcc change-frequency <50000000:999000000>
[upstream <chan_id>] initial-tech {broadcast-ranging | direct |
cable modem <mac_addr> dcc upstream <1:255>} initial-tech
| unicast-ranging}
Properties

Casa Systems
dcc change-frequency Sets the new Dynamic Channel Change (DCC)

<50000000:999000000> downstream frequency value. The
[upstream <chan_id>] change-frequency is followed by the optional
initial-tech upstream channel ID (see the interface upstream
{broadcast-ranging | direct command) and the required initial-tech setting, as
| period-ranging | described for the cable modem command. The
reinitialize-mac | channel must be included in the service group for the
unicast-ranging} requested channel change.
Note: The reinitialize-mac function is currently only

for CMs without channel bonding. Do not specify the
upstream channel ID here.
Example:
CASA# cable modem 0005.caa3.cf6c dcc

change-frequency 500000000 upstream 1
initial-tech unicast-ranging
dcc upstream <1:255>} Sets the Dynamic Channel Change (DCC) upstream
initial-tech channel ID (see the interface upstream command),
{broadcast-ranging | direct along with the required initial-tech setting, as
| period-ranging | described for the cable modem command.
reinitialize-mac |
unicast-ranging} Example:
CASA# cable modem 0005.caa3.cf6c dcc

upstream 1 initial-tech period-ranging
Casa Systems
cable modem <mac_addr> l2vpn-map
cable modem <mac_addr> l2vpn-map

Purpose
The cable modem <mac_addr> l2vpn-map command maps a modem MAC address
to a VLAN for Layer 2 VPN (L2VPN).
Mode
(config)#
Syntax
cable modem <mac_addr> 12vpn-map <1:4094> [vpnid <id>]
no cable modem <mac_addr> l2vpn-map
Properties

12vpn-map <1:4094> [vpnid VLAN ID and the optional VPN ID (maximum 32 hex
<id>] characters).
Example:
CASA(config)# cable modem

0111.affd.addf l2vpn-map 4034
CASA(config)#
no cable modem 0111.affd.addf l2vpn-map
Casa Systems
cable modem <mac_addr> mpls

Purpose
The cable modem <mac_addr> mpls vpnid command maps a MAC address to a
Multi-Protocol Label Switching (MPLS) Virtual Private LAN Service (VPLS) or
Virtual Private Wire Service (VPWS).
Mode
(config)#
Syntax
cable modem <mac_addr> mpls vpls <id>
cable modem <mac_addr> mpls vpws <id> <1:2147483647>
no cable modem <mac_addr> mpls
Properties

mpls vpls <id> Maps a CM to a Virtual Private LAN Service (VPLS),
maximum 32 hex characters.
Example:

0111.affd.addf mpls vpls 40FF
CASA(config)#
no cable modem 0111.affd.addf mpls
Casa Systems
mpls vpws <id> Maps a CM to a Virtual Private Wire Service (VPWS),

<1:2147483647> maximum 32 hex characters, along with the Virtual
Circuit (VC) ID.
Example:
CASA(config)# mpls vpws VPLS-net1

CASA(config-vpws)# peer 192.168.8.8 10
CASA(config-vpws-peer)# backup-peer
192.168.8.9 11
CASA(config-vpws-peer)# exit
0111.affd.addf mpls vpws VPLS-net1 10
CASA(config)#
no cable modem 0111.affd.addf mpls vpws
Casa Systems
cable modem <mac_addr> qos-override

Purpose
The cable modem <mac_addr> qos-override command allows changing the quality
of service (QoS) parameters for upstream and downstream primary service flows by
overriding them with the parameters of the specified cable service class without
having to unregister the specified CM. The QoS override settings normally persist
across CMTS reboots or CM resets and are maintained in the startup configuration
unless the non-persistent option is used. Up to 64,000 override entries are supported.
Mode
(config)#
Syntax
[no] cable modem <mac_addr> qos-override {ds-service-class |
us-service-class} <name> [non-persistent]
Properties

which is required. Note that specifying an
FFFF.FFFF.FFFF MAC address overrides the QoS
parameters for all modems in the applied service
class. The override does not take effect until modems
have re-registered with the CMTS.
Casa Systems
qos-override The downstream or upstream

{ds-service-class | cable service-class name <name> is maximum 15
us-service-class} <name> characters. Downstream and upstream can be
[non-persistent] specified on the same command line, along with
non-persistent for not allowing QoS override rules to
be persisted across CMTS reboots or CM resets
(persistent rules are the default).
Example:

0015.f2fe.ba13 qos-override
us-service-class ups1M non-persistent
CASA(config)# no cable modem
0015.f2fe.ba13 qos-override
us-service-class
show cable modem qos-override [all | online | non-persistent]
Shows CMs with QoS override in effect, also filtered by online CMs or those for
which QoS override is not persisted across CMTS reboots or CM resets.
CASA# show cable modem qos-override non-persistent

cable modem 0001.0002.0003 qos-override ds-service-class ds1
Casa Systems
cable modem <mac_addr> ucc upstream
cable modem <mac_addr> ucc upstream

Purpose
The cable modem <mac_addr> ucc upstream command changes an upstream

channel using the Upstream Channel Change (UCC) method.
Modes
#
(config)#
Syntax
cable modem <mac_addr> ucc upstream <1:255>
Properties

ucc upstream <1:255> Sets the new Upstream Channel Change (UCC)
upstream channel ID (see the interface upstream
command).
Example:
CASA# cable modem 0015.f2fe.ba13 ucc

upstream 1
Casa Systems
cable modem authorization
cable modem authorization

Purpose
The cable modem authorization command sets CM authorization for a specific

modem based on a Source Address Verification (SAV) configuration rule. Note that
the command can override DOCSIS MAC dhcp-authorization [ipv4-only |
ipv6-only] and allow CPEs behind specific CMs to be configured with specific IP
addresses to access the network. There can be up to 2048 authorizations.
Mode
(config)#
Syntax
cable modem authorization <mac_addr> <sav_cfg_list_name>
no cable modem authorization <mac_addr>
Properties
<mac_addr> MAC address of the CM, in xxxx.xxxx.xxxx format.

<sav_cfg_list_name> Source Address Verification (SAV) configuration list
name to apply, up to 16 characters, as defined by the
cable sec command’s sav-cfg-list property, to set
the configuration rule for the modem.
Example:
CASA(config)# cable modem authorization

0015.f2fe.ba13 SAVCONF
authorization 0015.f2fe.ba13
CASA(config)#
show cable modem authorization
Casa Systems
cable modem deny
cable modem deny

Purpose
The cable modem deny command specifies the MAC address of a cable modem that
is prohibited from registering with the CMTS. The deny list can contain up to 2048
modems.
Mode
(config)#
Syntax
[no] cable modem deny <mac_addr>
Properties
<mac_addr> MAC address of the CM to deny service, in

xxxx.xxxx.xxxx format.
Example:
CASA(config)# cable modem deny

0015.f2fe.ba13
CASA(config)#
no cable modem deny 0015.f2fe.ba13
show cable modem deny
Shows CMs added to the deny list.
CASA# show cable modem deny

cable modem deny 0015.f2fe.cee6
Casa Systems
cable modem excessive-request detection
cable modem excessive-request detection

Purpose
The cable modem excessive-request detection command detects interface utilization

and prevents granting more requested bandwidth than necessary to an upstream
service flow. The command sets the transmission grant size and packet-receive
thresholds to prevent a service flow from consuming excessive bandwidth. The
detection interval is 10 seconds and the CMTS resets the modem after 60 continuous
transmission grant requests for bandwidth that exceeds the configured threshold
settings. The packet-recv setting should be less than half the grant-assigned setting.
Mode
(config)#
Syntax
cable modem excessive-request detection grant-assigned <100:65535>
packet-recv <1:32767>
no cable modem excessive-request detection
Properties
grant-assigned <100:65535> Number of grants assigned to the service flow in the

10-second detection interval, default 0.
packet-recv <1:32767> Number of packets in 10 seconds from the service
flow, but should be less than half the grant-assigned
value.
Example:

excessive-request detection
grant-assigned 100 packet-recv 45
excessive-request detection
Casa Systems
cable modem offline aging
cable modem offline aging

Purpose
The cable modem offline aging command clears modems that have previously
registered with the CMTS but have been off line for a specified number of hours. If set
to 0 (the default), the modem maintains an off-line state indefinitely and is not cleared.
If set to a value in the range 1 to 8760 hours (1 year), the CMTS clears all modems
that have been offline for the specified number of hours.
Mode
(config)#
Syntax
cable modem offline aging <0:8760>
Properties
<0:8760> Aging period, maximum 1 year, default 0 hours.
Example:
CASA(config)# cable modem offline

aging 0
Casa Systems
cable modem remote-query
cable modem remote-query

Purpose
The cable modem remote-query command sets the remote query polling interval.
Mode
(config)#
Syntax
[no] cable modem remote-query {<0 | 30:1800> [<snmp_comm>] | loopback
[0:255]}
Properties
{<0 | 30:1800> The polling interval can be 0 (off) or in seconds,

[<snmp_comm>] | loopback followed by the optional default SNMP community
[0:255]} string to poll the CMs, or the loopback interface.
Example:
CASA(config)# cable modem remote-query

1000 loopback 15
CASA(config)#
no cable modem remote-query
show cable modem [<mac_addr>] remote-query [downstream | immediate

| ofdm | ofdma | upstream]
Shows the cable remote-query information, including for VRF CMs.
CASA(config)# show cable modem remote-query

MAC Address IP Address S/N US DS TX Time Micro(dB) Modem
Ratio Power Power Offset Reflection State
Casa Systems
cable modem rip authentication-bypass
cable modem rip authentication-bypass

Purpose
The cable modem rip authentication-bypass command allows bypass of Router

Information Protocol (RIP) authentication for a specified range of modems.
Mode
(config)#
Syntax
[no] cable modem rip authentication-bypass <mac_addr> <mask>
Properties
<mac_addr> <mask> MAC address and mask of a range of CMs to set up

for RIP authentication bypassing.
Example:
CASA(config)# cable modem rip

authentication-bypass 0005.caa3.cf6c
0000.0000.ffff
CASA(config)# no cable modem rip
authentication-bypass 0005.caa3.cf6c
0000.0000.ffff
Casa Systems
cable modem vendor
cable modem vendor

Purpose
The cable modem vendor command adds user-defined CM vendor information or

modifies the system default CM vendor. There can be up to 512 user-defined
Organizational Unique Identifier (OUI)-associated vendors. (See also the default
cable modem vendor command.)
Mode
(config)#
Syntax
cable modem vendor <oui> <name>
no cable modem vendor <oui>
Properties
<oui> <name> Vendor Organizational Unique Identifier (OUI), in the

form xx:xx:xx hex, followed by the vendor name,
embedded in quotes if spaces included.
Example:
CASA(config)# cable modem vendor

00:05:ca CMVENDOR
CASA(config)#
no cable modem vendor 00:05:ca
Casa Systems
show cable modem verbose immediate [community-string <name>]
Polls on the fly to show details on all CMs. (See also the “Related show commands” in
Chapter 3, “Baseline Privacy Interface.”)
CASA(config)# show cable modem verbose immediate

MAC Address :0005.caa3.cf6c
IP Address :20.160.2.134
CM-ID :67
Prim Sid :2503
MAC Domain :2
Service-Group :2
Upstream :10/0.1/0
Downstream :0/3/6
Unusable channel list :
Timing Offset :2403
…
show cable modem qos verbose
Shows CM statistics, including pending upstream byte statistics (best-effort,

guarantee, total). Use this option when there is high upstream utilization, but with low
throughput. This may indicate a modem that is receiving upstream transmission
grants, but is not sending upstream data.
CASA(config)# show cable modem qos verbose

Pending bytes(Best-Effort/Guarantee/Total): 0/0/0
Pending bytes(Best-Effort/Guarantee/Total):
1040/0/1040
show cable modem docsis-mac <id>
Shows CMs belonging to the specified DOCSIS MAC interface. An additional display
is the show cable modem docsis-mac <id> service-group <id> {downstream |
upstream} throughput command.
CASA(config)# show cable modem docsis-mac 1

MAC Address IP Address US DS MAC Prim RxPwr Timing Num BPI
Intf Intf Status Sid (dBmV) Offset CPEs Enb
7cb2.1b42.b1be 10.20.0.15 2/0.1/0* 0/0/2* online(pt) 1 2.0 2391 0 yes
Casa Systems
show cable modem mac downstream summary
Shows CM MAC layer downstream summary information.
CASA(config)# show cable modem mac downstream summary

Mac Version QoS Provision Mode
Interface Total DOC3.0 DOC2.0 DOC1.1 DOC1.0 Register DOC2.0 DOC1.1
DOC1.0
0/0/0 0 0 0 0 0 0 0 0 0
0/0/1 0 0 0 0 0 0 0 0 0
0/0/2 1 1 0 0 0 1 0 1 0
0/0/3 0 0 0 0 0 0 0 0 0
0/0/4 0 0 0 0 0 0 0 0 0
0/0/5 0 0 0 0 0 0 0 0 0
…
show cable modem maintenance
Shows CM maintenance ranging information. Ensure that there are no differences in

internal clock times.
CASA(config)# show cable modem maintenance

MAC Address US Intf Ds Intf Prim SM Fail Active-Time
Sid Count Count
7cb2.1b42.b1be 2/0.1/0 0/0/2 1 38354 0 2014-08-05,14:19:17
e448.c7ba.4576 2/2.2/0 0/1/2 1 38366 0 2014-08-05,14:18:50
show cable modem rogue
Shows CM spoof information during ranging.
CASA(config)# show cable modem rogue

MAC Address Vendor US Intf Ds Intf Spoof Count Dynamic Secret
0022.3a7e.ed71 00:22:3a 1/4.0/0 0/0/0 60 a46838ad13cc4cf1
show cable modem errors
Shows CM error information, including cyclic redundancy check (CRC) and header
check sequence (HCS) errors.
CASA(config)# show cable modem errors

MAC Address US Intf DS Intf CRC HCS
0008.0d55.da42 1/3/0 0/0/1 0 0
0015.f2fe.bea2 1/3/0 0/0/3 0 0
0050.f112.b764 1/3/0 0/0/1 0 0
Casa Systems
show cable downstream channel counter
Shows downstream cable total and used bytes per downstream channel.
CASA(config)# show cable downstream channel counter

Downstream Slot/Port/Channel TotalBytes UsedBytes ExtTotalBytes
ExtUsedBytes
show cable downstream channel utilization
Shows downstream cable utilization statistics.
CASA(config)# show cable downstream channel utilization

Slot/Port/Channel (Mb/Sec) Percentage Modems Modems
Channel Description
----------------------------------------------------------------------
2/0/0 (400000000 Hz) 55.6 1 0 0
2/0/1 (408000000 Hz) 55.6 1 0 0
2/0/2 (416000000 Hz) 55.6 1 0 0
2/0/3 (424000000 Hz) 55.6 1 0 0
2/0/4 (578000000 Hz) 55.6 1 0 0
2/0/5 (586000000 Hz) 55.6 1 0 0
2/0/6 (594000000 Hz) 55.6 1 0 0
2/0/7 (602000000 Hz) 55.6 1 0 0
…
Casa Systems
cm-ctrl
cm-ctrl
Purpose
The cm-ctrl command triggers a CM control request message (cm_ctrl_req_msg).
Modes
#
(config)#
Syntax
cm-ctrl <mac_addr> {cm-reinit | disable-forwarding {0|1} |
event_ds_mask <1:255> <0:ffff> | event_mask <0:ffff> |
event_us_mask <1:255> <0:ffff> | mute <0:255> <1:65535>}
Properties
<mac_addr> Identifies the required CM to which to send the

message by 48-bit MAC address.
Casa Systems
cm-ctrl
{cm-reinit | Sends the type of control message request. At least

disable-forwarding {0|1} | one of the following request types are required:
event_ds_mask <1:255>
<0:ffff> | event_mask • cm-reinit — Sends a CM reinitialization request.
<0:ffff> | event_us_mask • disable-forwarding {0 | 1} — Sends a disable
<1:255> <0:ffff> | mute forwarding request. 0 indicates false; 1 indicates
<0:255> <1:65535>} true.
• event_ds_mask <1:255> <0:FFFF> — Sends a
mask for a status event request for the down-
stream channel number and bitmask value.
• event_mask <0:FFFF> — Sends a status event
mask request for the bitmask value.
• event_us_mask <1:255> <0:FFFF> — Sends a
mask for a status event request for the upstream
channel number and bitmask value.
• mute <0:255> <1:65535> — Sends a mute
request for the channel number, followed by the
length in milliseconds the mute operation is in
effect.
Example:
CASA(config)# cm-ctrl 0026.24a8.db36

mute 1 300
Casa Systems
default cable modem vendor
default cable modem vendor

Purpose
The default cable modem vendor command sets a system default vendor.
Mode
(config)#
Syntax
default cable modem vendor <oui>
Properties
<oui> Organizational Unique Identifier (OUI) for the default

vendor, in the form hex xx:xx:xx.
Example:
CASA(config)# default cable modem

vendor 00:05:ca
show cable modem vendor default
Shows the default cable vendor database entries.
CASA# show cable modem vendor default

cable modem vendor 00:0f:9f Motorola
cable modem vendor 00:11:1a Motorola
…
Casa Systems
clear cable modem {<ip_addr> | <ipv6_addr>}
Clears the CM by its IP or IPv6 address.
CASA(config)# clear cable modem 192.168.8.8
clear cable modem <mac_addr>
Clears the CM by its MAC address.
CASA(config)# clear cable modem e448.c7b4.ab62
clear cable modem offline
Clears all off-line CMs.
CASA(config)# clear cable modem offline
clear cable modem counters
Clears all CM counters.
CASA(config)# clear cable modem counters
clear cable modem [bonding | non-bonding | partial-service] reset
Resets the CMs, including specific types.
CASA(config)# clear cable modem bonding reset
Casa Systems
6-1
Chapter 6. Channel bonding
Channel bonding commands description

Channel bonding, a DOCSIS 3.x capability, is the CMTS process that logically
combines multiple downstream or upstream channels for extended bandwidth for
modems having multiple transmitters and receivers. For downstream channels, the
MAC domain descriptor in the MPEG-2 transport stream informs the modem about
the receive channel configuration and the receive channel set (RCS) to be used by a
registered modem.
In the example of a network with eight downstream channels, even though the modem
supports only four downstream and four upstream channels, the modem learns how to
receive traffic across all eight CMTS downstream channels. The CMTS dynamically
creates a channel bonding group using four of the channels (based on current traffic
load) and creates a downstream service group (DS-SG) associated with the assigned
modem channel set. A service group is simply a group of channels.
Similarly, the set of upstream channels is called the upstream service group (US-SG).
Collectively, the upstream and downstream service groups make up the CM service
group (CM-SG). All upstream and downstream channels originating from the same
MAC domain are known as a MAC domain CM service group (MD-CM-SG).
Configuring channel bonding operations
In order for the Casa CMTS to operate in channel bonding mode, the DOCSIS MAC
interface must be configured, as well as a service group with at least one downstream
channel and one upstream channel. For CMs that support channel bonding operation,
the Casa CMTS automatically creates channel bonding groups with channels that
belong to the same service group, and the same DOCSIS MAC interface. The Casa
Casa Systems
Configuration example
CMTS supports channel bonding in the same line card module. The maximum number
of downstream channels per QAM module is 32, and the maximum number of
upstream channels per DOCSIS Control and Upstream (DCU) module is 32.
In the following example, one service group is formed with 16 downstream and 8
upstream channels from the same downstream/upstream modules, with two MAC
domain interfaces created within the service group. Each domain contains 8
downstream and 4 upstream channels. The channel bonding then occurs inside each of
the domains, or 8 downstream and 4 upstream channels.
CASA(config)# service group 1

CASA(config-svc-grp 1)# qam 0/0/0
CASA(config-svc-grp 1)# upstream 1/0
CASA(config-svc-grp 1)# end

CASA(config-if-mac 1)# no shutdown
CASA(config-if-mac 1)# no dhcp-authorization
CASA(config-if-mac 1)# no early-authentication-encryption
CASA(config-if-mac 1)# no tftp-proxy
CASA(config-if-mac 1)# ip bundle 1
CASA(config-if-mac 1)# downstream 1 interface qam 0/0/0
Casa Systems
Channel bonding 6-3

CASA(config-if-mac 1)# upstream 1 interface upstream 1/0/0
CASA(config-if-mac 1)# end

CASA(config-if-mac 2)# no shutdown
CASA(config-if-mac 2)# no dhcp-authorization
CASA(config-if-mac 2)# no early-authentication-encryption
CASA(config-if-mac 2)# no tftp-proxy
CASA(config-if-mac 2)# ip bundle 1
CASA(config-if-mac 2)# end
CASA(config)#
Table 6-1 lists and briefly describes the objects related to channel bonding.
Table 6-1. Channel bonding objects
bonding-group Directs traffic streams to specific channels configured at the

CMTS.
dbg_id_set qam Configures a downstream bonding group (DBG) for a CM.
rcc Sets up the Receive Channel Configuration (RCC) for
downstream channel bonding to the CM.
Casa Systems
Table 6-1. Channel bonding objects
rcp Sets up the Receive Channel Profile (RCP) for downstream

channel bonding to the CM.
service group Configures a service group for channel bonding.
Casa Systems
Channel bonding 6-5
bonding-group
bonding-group
Purpose
In networks where traffic from a particular modem or service area must use a specific
downstream or upstream channel, upstream and downstream bonding groups can be
configured using the bonding-group object to direct traffic streams to specific
channels configured at the CMTS. This means that the CMTS uses the configured
bonding group and only the specific channels defined in the group. The CMTS does
not make the channel selection dynamically from a group of available channels at the
MAC domain. Up to 480 upstream bonding groups can be configured.
Casa highly recommends the dynamic service group configuration over the static
bonding group configuration, which should only be used in very specific cases where
dynamic channel selection is not feasible.
Note: Service groups are required for cable traffic load balancing and for channel
bonding over D3.0 modems. Service groups are not required for CMs to
register and come up only as long as upstream and downstream channels are
configured in the DOCSIS MAC domain.
Modes
(config)#
(bond-ds-mac-x-group-x)#
(bond-us-mac-x-group-x)#
Syntax
(config)#
[no] bonding-group downstream mac-domain <1:96> group-id <1:65535>
[no] bonding-group upstream mac-domain <1:96> group-id <1:65535>
(bond-ds-mac-x-group-x)#
prov-attr-mask <0x0:0xFFFFFFFF>
reseq wait-time <255 | 0:180>
reseq warn-thrshld <255 | 0:179>
(bond-us-mac-x-group-x)#
prov-attr-mask <0x0:0xFFFFFFFF>
[no] upstream <slot>/<port>.<chan>/<log_chan>
Casa Systems
bonding-group
Properties
downstream mac-domain Adds a static downstream CM bonding group, with

<1:96> group-id <1:65535> the MAC domain and group IDs.
Example:
CASA(config)# bonding-group downstream

mac-domain 30 group-id 100
CASA(bond-ds-mac-30-group-100)# exit
CASA(config)# no bonding-group
downstream mac-domain 30 group-id 100
upstream mac-domain <1:96> Adds a static upstream CM bonding group, with the
group-id <1:65535> MAC domain and group IDs, with a maximum 480
upstream groups.
Example:
CASA(config)# bonding-group upstream

CASA(bond-us-mac-30-group-100)# exit
CASA(config)# no bonding-group upstream
prov-attr-mask Sets the provisioned attribute mask in an upstream or

<0x0:0xFFFFFFFF> downstream bonding group. When the CMTS
receives a service flow request from a CM, the CMTS
compares a TLV integer received in the service flow
request with the attribute masks of all of the available
channels it manages. The CMTS assigns a
requesting CM to the channel specified by the
attribute mask that represents the attributes
presented in the TLV included in the service flow
request. The mask can be user-defined in hex, or can
be set for bonding, high-availability, or the low latency
provisioning attribute masks, or all of the above. To
disable the mask, specify the default setting of 0x0.
Example:
CASA(bond-ds-mac-30-group-100)#
prov-attr-mask 0x0
Casa Systems
Channel bonding 6-7
bonding-group
qam <slot>/<port>/<chan> Binds a downstream QAM interface to a bonding

group, with the interface qam slot/port/channel
specified.
Example:
qam 0/2/1
no qam 0/2/1
reseq wait-time <255 | Sets the Downstream Service Identifier (DSID)

0:180> resequencing wait time in a downstream bonding
group, in hundred microseconds, or the specific value
255 (the wait time is determined by the CMTS).
Example:
reseq wait-time 255
reseq warn-thrshld <255 Sets the DSID re-sequencing warning threshold in a

| 0:179> downstream bonding group, in hundred
microseconds, or the specific value 255 (the
threshold is determined by the CMTS). A value of 0
disables threshold warnings.
Example:
reseq warn-thrshld 255
Casa Systems
bonding-group
upstream <slot>/ Binds an upstream interface to a bonding group, with

<port>.<chan>/<log_chan> the upstream slot/port.channel/logical channel
specified. (See the interface upstream command.)
Example:
CASA(bond-us-mac-30-group-100)#
upstream 13/0.0/0
CASA(bond-us-mac-30-group-100)#
no upstream 13/0.0/0
upstream channel bonding
downstream channel bonding
initial-tech
max sid-cluster per-service-flow
sid-cluster
These commands configure a DOCSIS MAC interface required for upstream or

downstream channel bonding. (See Chapter 8, “DOCSIS MAC interface.”) The
upstream channel bonding and downstream channel bonding settings are enabled
by default. The initial-tech property modifies the initial technique for bonding D3.0
modems registering on upstream channels assigned by the CMTS. The default
initial-tech setting is broadcast-ranging followed by unicast-ranging,
period-ranging, and direct ranging. The max sid-cluster per-service-flow property
assigns a type of service flow to each channel in a bonding group. The sid-cluster
property sets parameters for the SID cluster. These settings are reflected in a
show interface docsis-mac command.
Casa Systems
Channel bonding 6-9
bonding-group
interface qam
interleave 8
modulation 256qam
The CMTS should have the interface qam configurations to get maximum
throughput on channel bonding and non-bonding CMs. The downstream QAM
interface channel interleave should be 8 and the channel modulation type should be set
to 256qam.
CASA(config)# interface qam 0/0

CASA(config-if-qam 0/0)# interleave 8
CASA(config-if-qam 0/0)# modulation 256qam
clear cable modem {bonding | non-bonding | partial-service} reset
This command resets specific groups of modems, including bonding, non-bonding,

and partial-service modems.
CASA(config)# clear cable modem bonding
show bonding-group [downstream | mac-domain | upstream | utilization

[downstream | upstream] [mac-domain <id>] [group-id <id>]
[app-class <id>]]
Shows the configured bonding groups or their utilization. Output can also be for
downstream or upstream (and optionally filtered by group-id or app-class) or for a
particular MAC domain. For the utilization output, "M" refers to the MAC domain
and "G" refers to the group ID.
CASA# show bonding-group

bonding-group downstream mac-domain 1 group-id 1
qam 0/1/0
qam 0/1/1
qam 0/1/2
qam 0/1/3
bonding-group upstream mac-domain 1 group-id 1

upstream 3/0/0
upstream 3/1/0
Casa Systems
bonding-group
CASA# show bonding-group utilization

Mac GroupID App-Class-Id Total BW(kbps) Used
BW(kbps) Util(%) Grants Rejects DIR
1 - - 8192 0
0 0 0 US
11 - - 32768 0
0 0 0 US
…
show cable modem [<mac_addr>] bonding
Shows the channel bonding for all CMs or a particular CM.
CASA# show cable modem bonding

Reason code: x/y/z(reason_code)
1 MDD timeout 2 FEC lock failure
3 Bad tcc 4 Bad rcc
5 Reg ack 6 DBC rsp
7 TR power bad 8 NCP profile failure
9 Impaired channel 10 Channel unreachable
11 Range timeout 12 Ranging failure
0 Unknown
MAC Address MAC US DS US DS US/DS CHAN EXCLUDED

id Intf Intf SET SET
e448.c7b4.ab62 1 13/0.2/0 2/0/3 256 256(4*4) 2/0/4,2/0/5
e448.c7c0.ebca 3 13/4.0/0 2/2/3 257 256(3*4) 2/2/4,2/2/5
e448.c7c0.f0dc 13/2.0/0 2/1/0 256 256(4*4) 2/1/4,2/1/5
show cable modem [<mac_addr>] non-bonding
Shows all non-bonding CMs or for a particular MAC address.
CASA# show cable modem non-bonding

Casa Systems
Channel bonding 6-11
dbg_id_set qam
dbg_id_set qam
Purpose
The dbg_id_set qam command configures a downstream bonding group (DBG) for a
CM. The properties require entering, in succession, a QAM slot number, CM number,
and DBG ID.
Mode
(config)#
Syntax
dbg_id_set qam <slot> cm <0:16384> dbg <17:48>
no dbg_id_set qam <slot> cm <0:16384>
Properties
<slot> QAM slot number. (See the interface qam

command.)
cm <0:16384> CM number.
dbg <17:48> DBG ID, starting at 17 through 48.
Example:
CASA(config)# dbg_id_set
qam 0 cm 1 dbg 17
CASA(config)# no dbg_id_set qam 0 cm 1
Casa Systems
rcc
rcc
Purpose
The rcc command sets up the Receive Channel Configuration (RCC) for downstream
channel bonding to the CM (up to 512). RCC is used for downstream channel bonding
of 16 channels in earlier Casa releases that do not support channel bonding. Determine
the following before configuring the RCC group:
1. The RCP ID to use.

2. How many receive modules (RMs) the RCP ID supports (up to 512).
3. How many receive channels (RCs) the RCP ID supports (up to 2048).
Modes
(config)#
(conf-mac <id> rcc <id>)#
Syntax
(config)#
[no] rcc mac <1:96> rcp-id <string> <1:4294967295>
(conf-mac x rcc y)#

rc <1:255> downstream <0:255> {primary | secondary} connect <0:255>
no rc <1:255>
rcc-desc “<text>”
no rcc-desc
rm <1:255> frequency <0:999000000> connect <0:255>
no rm <1:255>
vendor-specific {spacing6 | spacing8}
Properties
mac <1:96> DOCSIS MAC <1:96>. Requires the following

additional rcp-id <string> and <1:4294967295>
properties.
rcp-id <string> Receive Channel Profile (rcp) ID, in the form
xx:xx:xx:xx:xx, which requires the additional RCC
configuration ID property.
Casa Systems
rcc
<1:4294967295> RCC configuration ID.
Example:
CASA(config)# rcc mac 1 rcp-id

00:11:11:11:11 2
CASA(conf-mac 1 rcc 2)# exit
CASA(config)#
no rcc mac 1 rcp-id 00:11:11:11:11 2
rc <1:255> downstream Receive channel (RC) ID, with the downstream

<0:255> {primary | interface number and the primary or secondary
secondary} connect connectivity ID.
<0:255>
Example:
CASA(conf-mac 1 rcc 2)# rc 1 downstream

0 primary connect 0
CASA(conf-mac 1 rcc 2)# no rc 1
rcc-desc “<text>” Adds an RCC description, enclosed in quotes if a

space-separated string.
Example:
CASA(conf-mac 1 rcc 2)# rcc-desc

“spacing 6”
CASA(conf-mac 1 rcc 2)# no rcc-desc
rm <1:255> frequency Assigns a receive module (RM) to the receive

<0:999000000> connect channel (RC) configuration, per ID. The frequency
<0:255> range is in Hz. An RM connect value of 0 means that
there is no other receive module connected to this
receive module.
Example:
CASA(conf-mac 1 rcc 2)# rm 1 frequency

549000000 connect 0
CASA(conf-mac 1 rcc 2)# no rm 1
Casa Systems
rcc
vendor-specific Assigns vendor-specific spacing, either spacing6 or

{spacing6 | spacing8} spacing8.
Example:
CASA(conf-mac 1 rcc 2)# vendor-specific

spacing6
show rcc [mac <id>] [rcp-id <id>]
Shows the RCC configuration.
CASA(config)# show rcc

rcc mac 1 rcp-id 10:00:00:00:01 1
vendor-specific spacing6
rcc-desc spacing=6;
rc 1 downstream 1 primary connect 1
rm 1 frequency 549000000 connect 0
Casa Systems
rcp
rcp
Purpose
The rcp command sets up the Receive Channel Profile (RCP) for downstream channel
bonding to the CM, up to 200.
Modes
(config)#
(rcp xx:xx:xx:xx:xx)#
Syntax
[no] rcp <string>
(rcp xx:xx:xx:xx:xx)#
rc <1:32> {primary | secondary} connect <1:16>
no rc <1:32>
[no] rcp <string>
[no] rcp-description [“<text>”]
rm <1:16> channels <0:64> [min-freq <111000000:999000000> max-freq
<111000000:999000000>]
no rm <1:16>
vendor-specific {spacing6 | spacing8}
Properties
<string> Receive Channel Profile (RCP) ID, in the form

xx:xx:xx:xx:xx.
Example:
CASA(config)# rcp 00:10:00:10:02

CASA(rcp 00:10:00:10:02)#
CASA(config)# no rcp 00:10:00:10:02
Casa Systems
rcp
rc <1:32> {primary | Receive channel (RC) ID, with the primary or

secondary} connect secondary connectivity ID, up to 32.
<1:16>
Example:
CASA(rcp 00:10:00:10:02)# rc 1 primary

connect 1
CASA(rcp 00:10:00:10:02)# no rc 1
rcp <string> Defines another RCP ID.
Example:
CASA(rcp 00:10:00:10:02)# rcp

00:10:00:10:03
CASA(rcp 00:10:00:10:02)#
no rcp 00:10:00:10:03
rcp-description Adds an RCP description, enclosed in quotes if a

[“<text>”] space-separated string.
Example:
CASA(rcp 00:10:00:10:02)#
rcp-description “spacing 6”
CASA(rcp 00:10:00:10:02)#
no rcp-description
rm <1:16> channels Assigns a receive module (RM) to the receive

<0:64> [min-freq channel (RC) configuration, per ID. The frequency
<111000000:999000000> range is in Hz. An RM connect value of 0 means that
max-freq there is no other receive module connected to this
<111000000:999000000>] receive module.
Example:
CASA(rcp 00:10:00:10:02)# rm 1 channels

32 min-freq 549000000 max-freq
649000000
CASA(rcp 00:10:00:10:02)# no rm 1
Casa Systems
rcp
vendor-specific Assigns vendor-specific spacing, either spacing6 or

{spacing6 | spacing8} spacing8.
Example:
CASA(rcp 00:10:00:10:02)#
show rcp running-config
Shows the RCP configurations.
CASA(config)# show rcp running-config
show rcp-list
Shows the list of RCP configurations.
CASA(config)# show rcp-list

rcp 00:10:00:00:02
rcp-description CLAB-6M-002
rm 1 channels 10
rc 1 primary connect 1
rc 2 secondary connect 1
rcp 00:10:00:10:02
rcp-description CLAB-8M-002
rm 1 channels 8
rc 1 primary connect 1
rc 2 secondary connect 1
…
Casa Systems
service group
service group
Purpose
The service group command configures a service group for channel bonding. A
service group is a collection of upstream and downstream channels that is allocated to
a single fiber node that supports a given service area. A service group can be bound to
an upstream or downstream interface. There can be up to 48 downstream and 16
upstream channels per node in Release 7.
Radio Frequency over Glass (RFoG) is a CMTS operating mode defined in SCTE 174
2010 and supported in DOCSIS 3.1. In this mode, the CMTS limits the number of
simultaneous upstream transmitters that are coupled to the same optical fiber splitter
to a single transmitter. Because CMs on the same splitter would not be allowed to
transmit data concurrently to the CMTS, an enhancement to the upstream scheduler
allocates the upstream spectrum for modem upstream transmissions to ensure that
time slots do not overlap if these modems are on the same optical fiber. RFoG mode is
enabled or disabled on a per service group basis, allowing cable operators to configure
the CMTS based on each deployment topology. Note that the same contention period
is shared by all subscriber modems.
A limitation of RFoG mode is that it does not permit simultaneous transmissions from
multiple modems that are sharing the same optical fiber, regardless of their baseband
channel frequencies. Therefore, it is undesirable to enable RFoG mode in the
conventional coaxial cables network, because the channel spectrum cannot be fully
utilized for concurrent transmissions.
Creating a service group puts you in the Casa service-group configuration mode.
Note: Service groups are required for cable traffic load balancing and for channel
bonding over D3.0 modems. Service groups are NOT required for CMs to
register and come up only as long as upstream and downstream channels are
configured in the DOCSIS MAC domain.
Modes
(config)#
(conf-svc-grp <name>)#
Casa Systems
service group
Syntax
(config)# [no] service group <name>
(conf-svc-grp x)#
[no] downstream channel bonding
[no] ofdm <slot>/<port>/<chan>
[no] ofdma <slot>/<port>.<chan>
[no] qam <slot>/<port>/<chan> [<1:48>]
[no] upstream <slot>/<port>.<pchan> [<1:8>]
[no] upstream channel bonding
[no] upstream rfog-scheduler
Properties
<name> Service group name, up to 16 characters. Up to 255

service groups are supported in Release 7.
Example:
CASA(config)# service group SVGP

CASA(conf-svc-grp SVGP)#
CASA(config)# no service group SVGP
description “<text>” Optional description for the service group, up to 64

characters, with text including space characters
embedded in quotes.
Example:
CASA(conf-svc-grp SVGP)# description

“Primary service group”
CASA(conf-svc-grp SVGP)# no description
Casa Systems
service group
downstream channel Enables downstream channel bonding from the

bonding service group configuration. Channel bonding must
be enabled from both the interface docsis-mac and
service group configurations.
Example:
CASA(conf-svc-grp SVGP)# downstream

channel bonding
no downstream channel bonding
ofdm <slot>/<port>/ Downstream binding of the service group to a

<chan> specified Orthogonal Frequency Division Multiplexing
(OFDM) interface. Only channel 0 can currently be
specified. (See Chapter 14, “Orthogonal Frequency
Division Multiplexing.”)
Example:
CASA(conf-svc-grp OFDM)# ofdm 2/0/0

CASA(conf-svc-grp OFDM)# no ofdm 2/0/0
ofdma <slot>/ Upstream binding of the service group to a specified

<port>.<chan> OFDMA interface. Currently the channel must be set
to 0. Overlapping OFDMA and TDMA can exist.
Example:
CASA(conf-svc-grp OFDMA)# ofdma 11/1.0

CASA(conf-svc-grp OFDMA)#
no ofdma 11/1.0
qam <slot>/<port>/<chan> Downstream binding of the service group to a

[<1:48>] specified QAM interface or range of ports (the
number value). (See the interface qam command.)
Example:
CASA(conf-svc-grp SVGP)# qam 0/2/1

CASA(conf-svc-grp SVGP)# no qam 0/2/1
Casa Systems
service group
upstream <slot>/ Physical upstream port binding of the service group,

<port>.<pchan> [<1:8>] with optional port range value. (See the interface
upstream command.)
Example:
CASA(conf-svc-grp SVGP)# upstream

13/0.0
no upstream 13/0.0
upstream channel bonding Enables upstream channel bonding from the service
group configuration. Channel bonding must be
enabled from both the interface docsis-mac and
service group configurations.
Example:

channel bonding
no upstream channel bonding
upstream rfog-scheduler Enables Radio Frequency over Glass (RFoG) mode,

defined in DOCSIS3.1.The RFoG scheduler allocates
the upstream spectrum for modem upstream
transmissions to ensure that time slots do not overlap
if these modems are on the same optical fiber. The
RFoG scheduler is supported for OFDMA channels.
Example:

rfog-scheduler
no upstream rfog-scheduler
Note: If service groups are configured or changed while the modems are online, the
CMTS can lose track of them and it will be necessary to reset them (or reboot
Casa Systems
service group
the CMTS). When the CMTS does not know which service group a modem
belongs to, it writes a message such as the following to the ddm_log:
[Fri May 4 22:44:43 2016]-lbm_chgoverstatus_update can not find

mdcmsg by mac 7,mdcmsg 0
show service group
Shows the configured service groups. OFDM and OFDMA channels in service groups
are also indicated.
CASA# show service group

service group 1
qam 2/0/0
qam 2/0/1
qam 2/0/2
qam 2/0/3
qam 2/0/4
qam 2/0/5
qam 2/0/6
qam 2/0/7
upstream 13/0.0
upstream 13/0.1
upstream 13/0.2
upstream 13/0.3
service group 5
ofdm 1/0/0
ofdma 10/1.0
…
show service group verbose
Shows the configured service groups in more detail.
CASA# show service group verbose

service group 1
qam 2/0/0 400000000 annex A 256qam dmac 1 UP
upstream 12/0.0 48000000 6400000 prof 3 dmac 63 UP
Casa Systems
service group

ofdm 2/0/0 437000000 - - dmac 63 UP
OFDM channel on 2/0
ofdm 2/2/0 832000000 - - dmac 63 DOWN
ofdma 12/0.0 5000000 37000000 - dmac 63 UP
…
show service group <id> upstream signal-quality
Shows the upstream signal quality for the specified service group.
CASA# show service group 1 upstream signal-quality

upstream channel frequency channel-width signal noise
12/0.1/0 20000000 3200000 0.0
12/0.1/1 20000000 3200000 0.0
show md-ds-sg [mac <1:96>] [service-group <name>]
Shows the MAC domain downstream service groups, which can also be filtered by
MAC domain and service group name.
CASA# show md-ds-sg

docsis-mac 1 service-group 1
qam 0/1/0
qam 0/1/1
qam 0/1/2
qam 0/1/3
qam 0/2/0
qam 0/2/1
qam 0/2/2
qam 0/2/3
…
show md-us-sg [mac <1:96>] [service-group <name>]
Shows the MAC domain upstream service groups, which can also be filtered by MAC
domain and service group name.
CASA# show md-us-sg service-group 1

upstream 1/4/0
…
Casa Systems
7-1
Chapter 7. Channel blocks
Channel block commands description

DOCSIS channels are configured with the interface qam command. Each port on the
QAM 8x96 supports up to 32 narrowcast channels and the QAM 8x192 supports up to
48 narrowcast channels. With Annex B, each port is comprised of four 192 MHz
blocks totaling 768 MHz. The offset value indicates the frequency width from the
starting (default) frequency for a given block. A typical channel frequency distribution
could be as follows:
CASA(config-if-qam 0/7)# channel 16 frequency 609000000 8

CASA(config-if-qam 0/7)# channel 24 frequency 801000000 8
Creating channel blocks better facilitates channel assignment to CMs by grouping

channels into blocks.
Table 7-1 lists and briefly describes the objects related to channel blocks.
Table 7-1. Channel block objects
channel-block downstream Creates four-channel downstream blocks automatically for

group 4 each DOCSIS MAC domain.
channel-block downstream Creates blocks of channels to better facilitate channel
mac-domain block-id assignment to CMs.
channel-utilization-inte Sets the interval over which the channel utilization
rval information is collected and averaged.
Casa Systems
channel-block downstream group 4

Purpose
The channel-block downstream group 4 command automatically creates groups of

four (or fewer) channels from the downstream channels defined for a DOCSIS MAC
domain, each with a separate block ID. A group can have fewer than four channels if
the defined QAM channels for a MAC domain are not in multiples of four. The block
ID numbering begins with 256 for each MAC domain.
Mode
(config)#
Syntax
show channel-block downstream [block-id <id>]
Shows the automatically created downstream channel blocks defined for DOCSIS
MAC domains, in groups of up to four. In the example, with six QAM channels
defined, the remaining two channels are given a separate block ID.
CASA(config)# show channel-block downstream
channel-block downstream mac-domain 11 block-id 256

qam 4/0/2
qam 4/0/3
qam 4/0/4
qam 4/0/5
prov-attr-mask 0x80000000

qam 4/0/6
qam 4/0/7
Casa Systems
Channel blocks 7-3
channel-block downstream mac-domain block-id
channel-block downstream mac-domain

block-id
Purpose
The channel-block downstream mac-domain block-id command creates blocks of

channels to better facilitate channel assignment to CMs. There can be up to 1024
downstream channel blocks.
Modes
(config)#
(chan-block-mac-x-block-y)#
Syntax
(config)#
[no] channel-block downstream mac-domain <1:96> block-id <1:255>
(chan-block-mac-x-block-y)#
prov-attr-mask <0x0:0xffffffff>
Properties
<1:96> block-id <1:255> Creates the channel block with a MAC domain ID and
block ID.
Example:
CASA(config)# channel-block downstream

mac-domain 1 block-id 1
CASA(chan-block-mac-1-block-1)#
CASA(config)# no channel-block
downstream mac-domain 1 block-id 1
Casa Systems
channel-block downstream mac-domain block-id
prov-attr-mask Sets the provisioned attribute mask for a channel

<0x0:0xffffffff> block. See the prov-attr-mask property of the
bonding-group command for details.
Example:
prov-attr-mask 0x0
qam <slot>/<port>/<chan> Binds a QAM interface to a channel block, with the

QAM slot/port/channel specified. (See the interface
qam command.)
Example:
qam 1/7/4
no qam 1/7/4
show channel-block [downstream | mac-domain <id>] [block-id <id>]
Shows the channel block configuration. The output can be filtered by downstream,
MAC domain ID, or block ID.
CASA(config)# show channel-block

qam 0/0/0
qam 0/0/1

qam 0/0/2
qam 0/0/3
…
Casa Systems
Channel blocks 7-5
channel-utilization-interval
Purpose
The channel-utilization-interval command sets the interval over which the channel
utilization information is collected and averaged.
Mode
(config)#
Syntax
channel-utilization-interval <0:86400>
Properties
<0:86400> Channel utilization interval, default 30 seconds.

Setting this value to 0 turns off utilization collection. It
is not advisable to use a value lower than 10 in an
operational system.
Example:
CASA(config)#
show channel-utilization-interval
Shows the channel utilization interval.
CASA(config)# show channel-utilization-interval

channel utilization interval = 30 s
Casa Systems
8-1
Chapter 8. DOCSIS MAC interface
DOCSIS MAC interface commands description

For normal DOCSIS operation, a DOCSIS MAC interface must be configured. Setting
properties with the interface docsis-mac command creates an association between
downstream and upstream channels. A downstream or upstream logic channel can be
associated with only one DOCSIS MAC interface, whose channel ID must be unique.
The most important part of configuring the DOCSIS MAC interface is correctly
defining the ip bundle and participating downstream and upstream channels, and
starting up the interface. Many other parameters can be set, such as for channel
bonding, multicasting, service flows, privacy, and traps.
Table 8-1 lists and briefly describes the objects related to DOCSIS MAC interface.
Table 8-1. DOCSIS MAC interface objects
interface docsis-mac Configures the DOCSIS MAC interface.
Casa Systems
Purpose
The interface docsis-mac command configures a DOCSIS MAC interface. After

creating one or more IP bundles, you need to apply the configured IP bundles to the
DOCSIS MAC interfaces. This ensures that all primary and secondary IP interfaces,
access groups (using configured ACLs), and helper addresses are associated with a
specific MAC domain. Up to 96 MAC domains are supported, with maximum 255
each of downstream and upstream channels, and maximum 8191 CMs.
Note: The maximum number of available DOCSIS MAC interfaces depends on the
Casa CMTS system, but the absolute maximum number across all systems is 96.
Modes
(config)#
(conf-if-mac <num>)#
Syntax
(config)# [no] interface docsis-mac <1:96>
(conf-if-mac x)#
[no] battery backup
[no] cable cm-status {event <1:27> {max-timer <1:1310> max-number
<0:255>} | report event-list <list>}
[no] cm trap [interval [<0:86400>] | l2vpn-cm-offline-only |
l2vpn-cm-online-only | online-offline-only]
[no] cm-status event report
[no] dhcp-authorization [ipv4-only | ipv6-only]
[no] dhcp-giaddr-primary
[no] dhcp-insert {circuit-id upstream-description |
downstream-description | hostname | MSO-text | service-class
| upstream-description | upstream-description-mac}
[no] dhcpv6-link-address-primary
[no] downstream <1:255> interface ofdm <slot>/<port>/<chan>
[no] downstream <1:255> interface qam <slot>/<port>/<chan>
[secondary] [<1:80>]
[no] downstream channel bonding
[no] early-authentication-encryption {capability | ranging | total}
[no] energy management
Casa Systems
DOCSIS MAC interface 8-3
initial-tech {broadcast-ranging [ranging-parameters] | direct |

ofdma {broadcast-ranging | probing | station-ranging |
unicast-ranging} | period-ranging | unicast-ranging}
[no] insertion-interval <10:200>
[no] invited-ranging-attempts <0:1024>
[no] ip bundle <1:16>
ip-provisioning-mode {alternate | dual-stack | ipv4-only |
ipv6-only}
max sid-cluster per-service-flow <1:4>
[no] mdd interval <0:2000>
[no] mgmd {ipv4 | ipv6} [last-member-query-interval <0:31744> |
max-query-response-time <0:31744> | proxy-interface <if> |
query-interval <0:31744> | robustness <1:255> | shutdown |
version <1:3 | 1:2>]
[no] multicast-dsid-forward [wb-cm-only]
[no] privacy {kek | tek} life-time <1:604800>
[no] router-advertisement <modifier>
[no] shared-secondary-secret <1|2> <0|7> <mic_string> [extend]
[no] shared-secret <0|7> <mic_string> [extend]
[no] shutdown
sid-cluster {max-outstanding-bytes <0:4294967295> | max-requests
<0:255> | max-time <0:65535> | max-total-bytes
<0:4294967295>>}
[no] sync-interval <1:200>
[no] tftp-enforce [src-interface {ip-bundle | loopback <0:255>}]
[no] tftp-proxy
[no] ucd-interval <100:2000>
[no] upstream <1:255> interface {ofdma <slot>/<port>.<pchan> |
upstream <slot>/<port>.<pchan>/<lchan> [ambiguity-exclude]
[no] upstream channel bonding
[no] upstream drop classifier
[no] upstream extended-frequency-range
Properties
<1:96> Required identity of the MAC domain.
Example:

CASA(conf-if-mac 1)# exit
CASA(config)# no interface docsis-mac 1
Casa Systems
battery backup Enables DBC to make the modem enter 1x1 mode
when operating on battery backup.
Example:
CASA(conf-if-mac 1)# battery backup

CASA(conf-if-mac 1)# no battery backup
Casa Systems
cable cm-status {event Sets parameters for showing cable events, and sets
<1:27> {max-timer the codes for the event types to report in a
<1:1310> max-number comma-separated list.The event codes and
<0:255>} | report parameters are as follows:
event-list <list>}
• 1 — Secondary channel MDD timeout.
• 2 — FEC lock failure.
• 3 — Sequence out-of-range.
• 4 — Secondary channel MDD recovery.
• 5 — FEC lock recovery.
• 6 — T4 timeout.
• 7 — T3 retries exceeded.
• 8 — Successful ranging after T3 retries
exceeded.
• 9 — CM operating on battery backup.
• 10 — CM returned to AC power.
• 11 — MAC address removed.
• 16 — DS OFDM profile failure.
• 17 — Primary downstream change.
• 18 — DPD mismatch.
• 20 — NCP profile failure.
• 21 — Loss of FEC lock on PLC.
• 22 — NCP profile recovery.
• 23 — FEC recovery on PLC channel.
• 24 — FEC recovery on OFDM profile.
• 25 — OFDMA profile failure.
• 26 — MAP storage overflow indicator.
• 27 — MAP storage almost full indicator.
(continued next page)
Casa Systems
cable cm-status • max-timer <1:1310> — Maximum event timer, in

(continued) seconds, for the report.
• max-number <0:255> — Maximum number of
events in the report; 0 means no limit.
Use the cm-status event report property to enable
showing the event report using the
show cable modem cm-status log command.
Example:
CASA(conf-if-mac 1)# cable cm-status

event 1 max-timer 60 max-number 0
CASA(conf-if-mac 1)# cable cm-status
report event-list 1,2,3,4,5,6,7,8,9,10
CASA(conf-if-mac 1)#
no cable cm-status report event-list
cm trap [interval Enables CMTS trap generation any time there are
[<0:86400>] | changes to the cable modem (CM) status over a
l2vpn-cm-offline-only | DOCSIS-MAC interface. An optional time interval
l2vpn-cm-online-only | controls the minimum time to elapse between CMTS
online-offline-only] trap notifications, default 600 seconds (10 minutes).
You can set options for trap notifications whenever
Business Service over DOCSIS/L2VPN modems
deregister and go offline, or when the CM goes online
or offline.
Example:
CASA(conf-if-mac 1)# cm trap interval

600 online-offline-only
CASA(conf-if-mac 1)# no cm trap
no cm trap interval
no cm trap interval 600
Casa Systems
cm-status event report Enables showing CM status events using the

show cable modem cm-status log command, as
determined by settings for the cable cm-status
property.
Example:
CASA(conf-if-mac 1)# cm-status event

report
no cm-status event report
description “<text>” Description for the DOCSIS-MAC domain, up to 64

characters, embedded in quotes if space characters
are included.
Example:
CASA(conf-if-mac 1)# description

“DOCSIS MAC domain 1”
CASA(conf-if-mac 1)# no description
dhcp-authorization Enables Dynamic Host Configuration (DHCP)

[ipv4-only | ipv6-only] authorization on MAC domain to prevent IP address
and mac-address spoofing. This property is enabled
by default. The ipv4-only and ipv6-only modifiers
set authorization for one or the other only; if omitted,
authorization for both occurs.
Example:
CASA(conf-if-mac 1)# dhcp-authorization

no dhcp-authorization
Casa Systems
dhcp-giaddr-primary Enables DHCP discovery messages (CM, MTA and

CPE) to be relayed to the DHCP server with the
source IP address of the dhcp-giaddr. The default
setting is disabled.
Example:
dhcp-giaddr-primary
no dhcp-giaddr-primary
Casa Systems
dhcp-insert {circuit-id A dhcp-insert allows users to insert type values in

upstream-description | DHCP packets using Option 82 (DHCP Relay Agent)
downstream-description | to include information about a CM. The DHCP server
hostname | MSO-text | attempts to match the received information to
service-class | determine if the device is a CM or CPE device. One
upstream-description | of the following modifiers is required:
upstream-description-mac
} • circuit-id upstream-description
• downstream-description
• hostname
• MSO-text — Inserts Option 82.125 Multi-Service
Operator (MSO) text in OFFER packets, as set in
the MSO-text <string> property of the IP bundle.
• service-class — Inserts DHCP option 82 with the
service-class name to instruct DHCP to treat
CPEs differently than other public IP devices. The
primary service-class name appears in the DHCP
relay message where the provisioned service
class as defined on the CMTS is relayed to the
DHCP server.
• upstream-description
• upstream-description-mac — Combines the
Remote ID (DHCPv4 option 82 suboption 2 or
DHCPv6 option 37) with the Circuit ID field
(DHCPv4 option 82 suboption 1 or DHCPv6
option 18) so that the Circuit ID carries both the
upstream description and the CM MAC address
(see the following Example).
Example:
CASA(conf)# interface upstream 12/0.1

CASA(config-if-ups 12/0.1)# description
"UP 12/0.1"
CASA(config-if-ups 12/0.1)# end
CASA(conf)# interface docsis-mac 1
CASA(conf-if-mac 1)# dhcp-insert
downstream-description-mac
CASA(conf-if-mac 1)# no dhcp-insert
Casa Systems
dhcpv6-link-address-prim Forces the CMTS to use the primary IPv6 address

ary from the ip-bundle interface for all DHCPv6 packets.
This enhancement addresses conditions where the
CMTS picks up the secondary IPv6 address from the
CPE DHCPv6 SOLICIT message.
Example:
dhcpv6-link-address-primary
no dhcpv6-link-address-primary
downstream <1:255> Binds a downstream OFDM interface to a MAC

interface ofdm <slot>/ domain. Currently only channel 0 can be set. See the
<port>/<chan> full description in Chapter 14, “Orthogonal Frequency
Division Multiplexing.”
Example:
CASA(conf-if-mac 1)# downstream 1

interface ofdm 4/0/0
CASA(conf-if-mac 1)# no downstream 1
Casa Systems
downstream <1:255> Binds a downstream interface to a MAC domain, up

interface qam <slot>/ to 255. The values are as follows:
<port>/<chan>
[secondary] [<1:80>] • <1:255> — Required user-defined channel
identifier unique within a MAC domain.
• interface qam — Required modifier.
• <slot>/<port>/<chan> — Required module slot,
port, and channel.
• secondary — Binds a secondary downstream
interface. Because the MAC domain supports a
maximum of 8191 service IDs, it is sometimes
desirable to bind secondary downstream
interfaces to multiple MAC domains. This allows
3.0 modems to load-balance across several MAC
domains without requiring all downstream
interfaces to be in the same MAC domain. The
secondary interfaces can be in up to four MAC
domains. Secondary channels cannot transmit
MAP files, so that the MAC domain must also
include at least one primary channel.
• <1:80> — Optional number of downstream
channels in a range, primary or secondary.
Example:

interface qam 0/2/1
downstream channel Enables downstream channel bonding for the

bonding DOCSIS MAC interface.
Example:
CASA(conf-if-mac 1)# downstream channel

bonding
no downstream channel bonding
Casa Systems
early-authentication-enc Early authentication encryption (EAE) allows the

ryption {capability | CMTS to authenticate CMs immediately after ranging
ranging | total} instead of performing the authentication after
modems have registered. When EAE is enabled, the
CMTS does not rely on the REG-REQ message from
the modem to determine whether a CM must perform
authentication. EAE helps prevent unauthorized CMs
from accessing IP provisioning servers and provides
security for IP provisioning messages between the
CM and the CMTS. The CMTS sends early
authentication encryption to the CM in the MAC
Domain Descriptor (MDD) message. When the CM
receives the MDD message with EAE enabled, the
modem initiates EAE during the registration process
just after ranging and just prior to DHCP. Only
authenticated CMs are allowed to continue their
initialization process with the CMTS and may be
subsequently admitted to the network. One of the
following modifiers is required:
• capability — Specifies EAE for modems with the

EAE flag set in the modem configuration file.
• ranging — Specifies EAE for modems with the
B_INT_RNG_REQ message set.
• total — Enforces EAE always for all CMs
registering with the CMTS.
Example:
early-authentication-encryption
capability
no early-authentication-encryption
Casa Systems
energy management Enables energy management for the interface.
Example:
CASA(conf-if-mac 1)# energy management

no energy management
initial-tech Ranging technique to be used by D3.0 or D3.1

{broadcast-ranging modems when moving to new upstream channels
[ranging-parameters] | associated with the MAC domain interface. One of
direct | ofdma the following modifiers is required:
{broadcast-ranging |
probing | • broadcast-ranging [ranging-parameters] —
station-ranging | Move to new channels during broadcast ranging
unicast-ranging} | (the default).
period-ranging | • direct — Move to new channels directly.
unicast-ranging}
• ofdma — Move to an OFDMA channel for
DOCSIS 3.1 modems. The default method is
broadcast-ranging, but ranging can also be by
probing (TLV 46.7 value 5: probing on a new
channel before normal operation),
station-ranging (TLV 46.7 value 7: station
ranging on a new channel before normal
operation), or unicast-ranging (TLV 46.7 value
6: unicast ranging on a new channel before
normal operation).
• period-ranging — Move to new channels during
period ranging.
• unicast-ranging — Move to new channels during
unicast ranging.
Example:
CASA(conf-if-mac 1)# initial-tech

broadcast-ranging ranging-parameters
Casa Systems
insertion-interval Time interval between consecutive initial ranging

<10:200> slots on an upstream, a MAC domain characteristic.
When set, it applies to all upstream channels bound
to the MAC domain. The interval is between initial
ranging slots in 1/100ths of a second.
Example:
CASA(conf-if-mac 1)# insertion-interval

10
no insertion-interval
invited-ranging-attempts Maximum number of attempts to make on invitations
<0:1024> for ranging requests. A value of zero means the
system tries to range forever.
Example:
invited-ranging-attempts 100
no invited-ranging-attempts
ip bundle <1:16> Applies a configured IP bundle interface to the

DOCSIS MAC interface, which ensures that all
primary and secondary IP interfaces, access groups
(using configured ACLs) and helper addresses are
associated with specific MAC domain.
Example:
CASA(conf-if-mac 1)# ip-bundle 1

CASA(conf-if-mac 1)# no ip-bundle 1
Casa Systems
ip-provisioning-mode IP provisioning mode to select the IP addressing

{alternate | dual-stack scheme for a MAC domain interface. One of the
| ipv4-only | ipv6-only} following modifiers is required:
• alternate — Attempts IPv6 provisioning; if it fails,

revert to IPv4 provisioning.
• dual-stack — Attempts IPv4 and IPv6
provisioning concurrently with dual IP addressing;
if one or the other fails, the successful
provisioning remains in effect.
• ipv4-only — IPv4 provisioning only, the default.
• ipv6-only — IPv6 provisioning only.
Example:
ip-provisioning-mode ipv4-only
max sid-cluster A SID cluster assigns a type of service flow to each

per-service-flow <1:4> channel in a bonding group. The maximum number of
clusters per service flow defaults to two.
Example:
CASA(conf-if-mac 1)# max sid-cluster

per-service-flow 2
mdd interval <0:2000> Interval for the MAC Domain Descriptor (MDD) that
includes the downstream service groups in the MAC
domain and the upstream ambiguity resolution
channel, in milliseconds, with 0 disabling the MDD.
Example:
CASA(conf-if-mac 1)# mdd interval 10

CASA(conf-if-mac 1)# no mdd interval
Casa Systems
mgmd {ipv4 | ipv6} Enables the Multicast Group Membership Discovery

[last-member-query-inter (MGMD) protocol on a docsis-mac domain interface,
val <0:31744> | required for IPv4 or IPv6. The optional qualifiers are
max-query-response-time as follows:
<0:31744> |
proxy-interface <if> | • last-member-query-interval <time> — Last
query-interval <0:31744> member query interval, in tenths of seconds.
| robustness <1:255> | • max-query-response-time <time> — Maximum
shutdown | version <1:3 | query response time, in tenths of seconds.
1:2>]
• proxy-interface {gige | xgige} <num> — Proxy
interface and number, either gige (0–7) or xgige
(0 or 1).
• query-interval <seconds>— Query interval, in
seconds.
• robustness <factor> — Robustness to packet
losses.
• shutdown — Shuts down MGMD.
• version <num> — Sets the Internet Group
Management Protocol (IGMP) version for IPv4 to
1, 2, or 3, or the Multicast Listener Discovery
(MLD) version for IPv6 to 1 or 2. The MLD
process running over a CMTS interface discovers
listeners (or receivers) for distributing multicast
traffic.
Example:
CASA(conf-if-mac 1)# mgmd ipv4

version 1
no mgmd ipv4 last-member-query-interval
Casa Systems
multicast-dsid-forward Enables multicast Downstream Service Identifier

[wb-cm-only] (DSID) forwarding that allows CMs to filter multicast
traffic before forwarding the traffic to CPE devices.
DSIDs uniquely identify multicast streams over a
MAC domain bonding group. The optional
wb-cm-only modifier sets DSID for wide-band CMs
only. The default is no multicast DSID forwarding. Set
this property especially if running DOCSIS 3.x and
pre-3.x along with IPv6. The no form of the command
also takes the dsg modifier.
Example:
multicast-dsid-forward wb-cm-only
no multicast-dsid-forward
no multicast-dsid-forward dsg
privacy {kek | tek} Key Encryption Key (KEK) or Traffic Encryption Key
life-time <1:604800> (TEK) lifetime on MAC domain interfaces for the
Baseline Privacy Interface (BPI). The lifetime is in
seconds.
Example:
CASA(conf-if-mac 1)# privacy tek

life-time 300
no privacy tek life-time
Casa Systems
router-advertisement Route advertisements must be enabled when a MAC

<modifier> domain has a CM or CPE in IPv6 mode. One of the
following modifiers must be used:
• cur-hop-limit <0:255> — Maximum hops.

• [no] enable — Enables router advertisement.
• life-time <0:9000> — Router lifetime, in seconds,
default 3*max-advert-interval.
• link-mtu <512:1500> — MTU default 1500 bytes.
• managed-flag {true | false}> — Managed
address configuration flag, either true or false.
• max-advert-interval <4:1800> — Maximum
advertised interval, default 600.
• min-advert-interval <3:1350> — Minimum
advertised interval, default 200 seconds.
• [no] multicast-only — Only a multicast response
to router solicitation.
• other-config-flag {true | false}> — Other stateful
configuration flag, either true or false.
• [no] prefix suppression — Suppresses the
prefix option (the default).
• reachable-time <0:3600000> — Router
reachable time, in milliseconds, default 0
(unspecified).
• retransmit-time <0:65535> — Advertisement
retransmit time, in seconds, default 0
(unspecified).
• row-state {0 | 1} — Row status, 0 down or 1 up,
default up.
Example:
router-advertisement enable
no router-advertisement enable
Casa Systems
shared-secondary-secret The shared-secondary-secret provides a second

<1|2> <0|7> <mic_string> password should a CM fail to authenticate with the
[extend] primary shared-secret. With the secondary secret
configured, the CM must authenticate using either
the primary or secondary password for the modem to
register and come online. Using a secondary secret
allows CMTS operators to frequently revise the
primary password without interrupting a currently
active and online CM with a primary password
update. The CMTS supports a maximum of 198
shared secrets (primary, secondary, and primary/
secondary extended). The required parameters are
as follows:
• <1 | 2> — Index number of the secondary secret,

1 or 2. If two secondary secrets are configured,
the index determines which one it checks first.
• <0 | 7> — Either an unencrypted (0) or encrypted
(7) message will follow.
• <mic_string> — Message Integrity Check (MIC)
string used to encrypt and decrypt the
The optional extend modifier sets the shared-secret
MIC for the extended type-length value encoding
schemes (TLVs) received from the Reg-Req
message.
Example:
shared-secondary-secret 1 7 3155ff
no shared-secondary-secret 1
Casa Systems
shared-secret <0|7> With the shared secret configured, the CM must

<mic_string> [extend] authenticate using either the primary or secondary
password for the modem to register and come online.
The CMTS supports a maximum of 198 shared
secrets (primary, secondary, and primary/secondary
extended). The required parameters are as follows:
• <0 | 7> — Either an unencrypted (0) or encrypted

(7) message will follow.
• <mic_string> — Message Integrity Check (MIC)
string used to encrypt and decrypt the
The optional extend modifier sets the shared-secret
MIC for the extended type-length value encoding
schemes (TLVs) received from the Reg-Req
message.
Example:
CASA(conf-if-mac 1)# shared-secret 7

3155ff extend
CASA(conf-if-mac 1)# no shared-secret
shutdown Shuts down the DOCSIS-MAC interface. The no

form of the command restarts the interface.
Example:
CASA(conf-if-mac 1)# shutdown

CASA(conf-if-mac 1)# no shutdown
Casa Systems
sid-cluster A SID cluster assigns a type of service flow to each

{max-outstanding-bytes channel in a bonding group. The following
<0:4294967295> | parameters set the SID cluster properties:
max-requests <0:255> |
max-time <0:65535> | • max-outstanding-bytes <0:4294967295> —
max-total-bytes Maximum outstanding bytes, default 0.
<0:4294967295>>} • max-requests <0:255> — Maximum number of
requests, default 0.
• max-time <0:65535> — Maximum time, in
milliseconds, default 0.
• max-total-bytes <0:4294967295> — Maximum
total bytes, default 0.
Example:
CASA(conf-if-mac 1)# sid-cluster

max-time 6000
sync-interval <1:200> Interval between successive sync message

transmissions from the CMTS, default 10
milliseconds.
Example:
CASA(conf-if-mac 1)# sync-interval 100

CASA(conf-if-mac 1)# no sync-interval
Casa Systems
tftp-enforce Enables the CMTS to reject registration requests

[src-interface from CMs on the specific MAC domain. If set, CMs
{ip-bundle | loopback must first download their DOCSIS configuration files
<0:255>}] from a TFTP server before the modems are allowed
to register with the CMTS. If disabled (by default),
CMs are allowed to register with the CMTS and come
online without first downloading their DOCSIS
configuration file from a TFTP server. The optional
source interface can be added, with either the IP
bundle or loopback interface specified. The default
setting is disabled.
Example:
CASA(conf-if-mac 1)# tftp-enforce

src-interface ip-bundle
CASA(conf-if-mac 1)# no tftp-enforce
CASA(conf-if-mac 1)# no tftp-enforce
source-interface loopback
tftp-proxy Enables the TFTP proxy on a domain interface so

that the CM can get the DOCSIS configuration file
(see also the tftp-enforce property).
Example:
CASA(conf-if-mac 1)# tftp-proxy

CASA(conf-if-mac 1)# no tftp-proxy
ucd-interval <100:2000> Interval between transmitting upstream channel

descriptor (UCD) messages scheduled by the CMTS
for all CMs on a cable interface, in milliseconds.
Example:
CASA(conf-if-mac 1)# ucd-interval 100

CASA(conf-if-mac 1)# no ucd-interval
Casa Systems
upstream <1:255> Binds an interface upstream to a MAC domain, up

interface {ofdma <slot>/ to 255. The values and modifiers are as follows:
<port>.<pchan> |
upstream <slot>/ • <chan_id> — User-defined channel identifier
<port>.<pchan>/<lchan> unique within a MAC domain.
[ambiguity-exclude] • <slot> — Module or slot number.
• <port> — Port number.
• <pchan> — Physical channel (0–3).
• <lchan> — Logical channel (0–1).
• ambiguity-exclude — Optionally excludes the
channel from the upstream-ambiguity-resolution
list in the MAC Domain Descriptor (MDD).
Example:
CASA(conf-if-mac 1)# upstream 5

interface upstream 13/1.1/0
CASA(conf-if-mac 1)# no upstream 5
upstream channel bonding Enables the DOCSIS3.0 CM to bond to more than

one upstream or downstream channel of the MAC
domain. The maximum number of upstream bonded
service flows per MAC domain is 8192.
Example:
CASA(conf-if-mac 1)# upstream channel

bonding
no upstream channel bonding
Casa Systems
upstream drop classifier Enables the Upstream Drop Classifier (UDC), which
has a set of matching criteria applied by the CMs to
packets to determine if a packet should be dropped
on upstream traffic.
Example:
CASA(conf-if-mac 1)# upstream drop

classifier
no upstream drop classifier
upstream Enables extending the upstream frequency range

extended-frequency-range beyond the standard North American range to
support other cable systems, such as the European
65 MHz and the Japanese
55 MHz top of ranges.
Example:
CASA(conf-if-mac 1)# upstream

extended-frequency-range
no upstream extended-frequency-range
Creates a shared secondary secret. The command syntax is identical to the interface
docsis-mac shared-secondary-secretcommand.
shared-secret
Creates a shared secret. The command syntax is identical to the interface docsis-mac
shared-secondary-secret command.
Casa Systems
show interface docsis-mac [<id>] [brief | stat | topology]
Shows the DOCSIS MAC interface configuration. Other options include specifying a
particular DOCSIS MAC ID, brief, stat, and topology.
CASA(config)# show interface docsis-mac

no shutdown
sync-interval 10
insertion-interval 20
ucd-interval 1000
no dhcp-authorization
invited-ranging-attempts 16
ip-provisioning-mode ipv4-only
no extended-upstream-frequency-range
cm-status event report
multicast-dsid-forward
…
Casa Systems
CASA(config)# show interface docsis-mac topology

interface docsis-mac 1,AdminStatus: UP
=======================================
DS Cable Chan Oper Mod Power Service
Int Mac ID State Annex Freq(Hz) Type (.1dBmV) Group(s)
…
US Cable Chan Oper Chan Channel Mini Mod Power Service

Int Mac ID State Type Freq(Hz) Width Slot Prof (.1dBmV) Group(
s)
…
show docsis downstream channel counter
Shows the bytes used for each downstream channel.
CASA(config)# show docsis downstream channel counter

Downstream Slot/Port/Channel TotalBytes UsedBytes ExtTotalBytes
ExtUsedBytes
2/0/0 3089777725 3762326357 2515645645885 55301933909
2/0/1 2643899594 3668488914 2515199767754 390215545554
2/0/2 2643927555 166260656 2515199795715 391008284592
…
show docsis downstream channel utilization
Shows the utilization rates of all the downstream channels in the system. Note that the
column headings change when shared channels or admission control is enabled.
CASA(config)# show docsis downstream channel utilization

Downstream Total-BW Utilization Reserved-BW Online Secondary Channel
Slot/Port/Channel (Mb/
Sec) Percentage Utilization Modems Modems Description
----------------------------------------------------------------------
1/0/0 (483000000 Hz) 42.9 1 0 0 1
1/0/1 (489000000 Hz) 42.9 1 0 0 1
1/0/2 (495000000 Hz) 42.9 1 0 0 1
1/0/3 (501000000 Hz) 42.9 1 0 0 1
…
Downstream Total-BW Utilization Online Secondary Channel
Slot/Shared Channel (Mb/Sec) Percentage Modems Modems Description
---------------------------------------------------------------------
1/0 (453000000 Hz) 42.9 0 0 0 (shared)
1/1 (459000000 Hz) 42.9 0 0 0 (shared)
1/2 (465000000 Hz) 42.9 0 0 0 (shared)
1/3 (471000000 Hz) 42.9 0 0 0 (shared)
1/4 (477000000 Hz) 42.9 0 0 0 (shared)
…
Casa Systems
show downstream channel set [id] [mac-domain <id>]
Shows all downstream channel sets. You can also filter by id and mac-domain.
CASA(config)# show downstream channel set

MAC Chan Channel
ID Set List
1 1 0/0/0
1 2 0/0/1
1 3 0/0/2
1 4 0/0/3
1 5 0/0/4
1 6 0/0/5
1 7 0/0/6
1 8 0/0/7
1 256 0/0/0, 0/0/1, 0/0/2, 0/0/3, 0/0/4
2 1 0/1/8
2 2 0/1/9
2 3 0/1/10
2 4 0/1/11
…
show controller docsis-mac [<1:96>]
Shows DOCSIS MAC interface status and statistics. Other options include specifying
a particular domain ID.
CASA(config)# show controller docsis-mac 1

Interface docsis-mac 1 statistics
Ifindex: 2000001
Administrated status: UP
Operation status: UP
Mac address: 0017.1082.c502
DSA Request : 0/ups; 0/ds
DSA Response : 0/ups; 0/ds
DSA Acknowledgements : 0/ups; 0/ds
DSA Success : 0/ups; 0/ds
DSA Fail : 0/ups; 0/ds
…
show channelset <1:downstream | 2:upstream> <mac_domain> <id>
Shows channel sets, downstream or upstream, by MAC domain and ID.
CASA(config)# show channelset 1 1 1

channel id list:1
Casa Systems
show cable modem {<ip_addr> | <ip6_addr> | <mac_addr>} classifiers
Shows classifiers in the configuration file that the CM is using.
CASA(config)# show cable modem 0050.f112.b764 classifiers

CM Mac Address: 0050.f112.b764
Classifier ID: 3
ServiceFlow ID: 514
Direction: Upstream
Rule Priority: 20
Activation State: Active
IP classifiers:
LLC classifiers:
IEEE 802 classifiers:
L2VPN classifiers:
Vlan ID: 0x12c0190
l2vpn CMIM: 0x47.ff.00.00
CM Interface Mask: 0x00.00.00.00
show cable modem cm-status log
Shows the CM status log of the CM, based on the event parameters set.
CASA(config)# show cable modem cm-status log

CMAC Address Status_Event Msg Content Time
e448.c7b4.ab62 SEQ_OUT_OF_RNG Dsid: 56 2015-02-05 17:47:43
…
show cable modem summary mac-domain
Shows the MAC domain interface to which a particular upstream channel is linked.
CASA(config)# show cable modem summary mac-domain

Upstream Mac Total Active Registered Secondary Offline Bonding
Interface Int Modems Modems Modems Modems Modems Modems
Non_Bonding Channel
Modems Description
1:0/0.0/0 1 11 11 11 0 0 2
9
…
Casa Systems
show cable modem tftp-bypass
Shows CMs that bypassed TFTP download of the DOCSIS configuration file and
have registered with the CMTS.
CASA(config)# show cable modem tftp-bypass

total cm 0
show router-advertisement
Shows CMs that bypassed TFTP download of the DOCSIS configuration file and
have registered with the CMTS.
CASA(config)# show router-advertisement

router advert table, domain=22
SendAdverts=1
MaxInterval=600
MinInterval=200
ManagedFlag=1
Casa Systems
9-1
Chapter 9. DOCSIS Set-Top Gateway
DSG commands description

The CASA CMTS supports the latest DOCSIS Set-Top Gateway (DSG) specification
from CableLabs. As a specification for transporting set-top box (STB) command and
control information over DOCSIS, DSG offers substantial support for enhanced
DOCSIS implementation in the Broadband Cable environment. It provides transparent
unidirectional and bidirectional transport of out-of-band (OOB) service messaging
over IP between the CMTS and STBs over hybrid fiber coaxial (HFC) networks.
Types of OOB messages include conditional access (CA), system information (SI),
electronic program guide (EPG), emergency alert system (EAS), and other generic
messages.
Definitions
The terms in use for DSG include the following:
• DSG channel — DOCSIS downstream QAM channel that contains one or more
DSG tunnels.
• DSG classifier — Description of Layer 3 and 4 filtering that applies to DSG
tunnel traffic. Classifiers can be specified in the DSG agent contained in the
CMTS and sent as a component of the DSG address table in the Downstream
Channel Descriptor (DCD) message.
• DSG client — Terminates the DSG tunnel at the STB across the cable network
and receives content from the DSG server.
• DSG server — Part of the Set-Top Controller attached from the CMTS via the
regional or WAN IP backbone.
Casa Systems
Configuration steps
• Downstream channel descriptor (DCD) — DOCSIS MAC management message

for the DSG tunnel that includes a keep-alive mechanism, allows address
substitution and classification, allows multicast addresses, sets timers to allow
operator-driven changes, and contains the list of tunnel downstream frequencies.
Configuration steps
Configure DSG using the following steps:
1. Define the DSG tunnel group and the mapping between a tunnel to downstream
QAM channels and DSG rule-related data. See the dsg tunnel-group command
for details. For example:
CASA(config)# dsg tunnel-group 1
CASA(conf-dsg-tunnel-grp-1)# channel 1 qam 0/0/0 rule-priority 20
CASA(conf-dsg-tunnel-grp-1)# end
2. Define the client list, which includes the participating clients that terminate the
DSG tunnel and receive content from the DSG server. Each client has a client type
defined as an application ID, well-known STB MAC address, broadcast ID, or
conditional access (CA) ID, along with any vendor parameters. See the dsg
client-list command for details. For example:
CASA(config)# dsg client-list 1 client 1
id-type macAddr id-value 0001.a6ff.0015 vendor-param-id 0
CASA(config)# dsg client-list 1 client 2
id-type broadcast id-value 0 vendor-param-id 0
3. Set up the tunnel with its tunnel group, destination MAC address, service class,
client list, and service class for tunnel QoS parameters, along with any DSG
classifier ID with the source and destination multicast address. See the dsg tunnel
command for details. For example:
CASA(config)# dsg tunnel 1
CASA(conf-dsg-tunnel 1)# group 1
CASA(conf-dsg-tunnel 1)# dst-address 0013.f735.d38a
CASA(conf-dsg-tunnel 1)# client-list 1
CASA(conf-dsg-tunnel 1)# service-class SRVLCL1
CASA(conf-dsg-tunnel 1)# classifier 1 10 192.168.3.6/32 239.1.1.8
Casa Systems
DOCSIS Set-Top Gateway 9-3
Configuration steps
4. Set the DSG timer ID, the global timer entry to be associated with the DSG client
state machine. There are four distinct times to set, an initial timeout (t1),
operational timeout (t2), two-way retry timer (t3), and a one-way retry timer (t4),
set in seconds. See the dsg timer-id command for details. For example:
CASA(config)# dsg timer-id 1 t1 2 t2 30 t3 1 t4 35
5. Optionally define the DSG channel list with the center frequency for DSG
channels as a way to expedite bringing up DSG STBs. You can assign this channel
list to any QAM channel, but the center frequency must be in the range set for the
DSG channels. See the dsg channel-list command for details. For example:
CASA(config)# dsg channel-list 1 channel 1 frequency 526000000
6. For each downstream QAM channel to support DSG, enable DCD messages and
set the DSG properties. For details, see the interface qam command in Chapter
17, “QAM interface.” For example, for one of the QAM channels:
CASA(conf-if-qam 0/0)# channel 0 frequency 279000000
CASA(conf-if-qam 0/0)# channel 0 dsg dcd-enable
CASA(conf-if-qam 0/0)# channel 0 dsg timer-id 1
CASA(conf-if-qam 0/0)# channel 0 dsg vendor-param-id 1
CASA(conf-if-qam 0/0)# channel 0 dsg interval 5
CASA(conf-if-qam 0/0)# end
7. Enable the Protocol Independent Multicast (PIM) (the preferred method) or

Internet Group Management Protocol (IGMP) on the GigE, XGigeE, VLAN, or
trunk interface (the two protocols cannot be used concurrently). For the interface
details, see the Casa Systems – NSI Configuration Guide and Command
Reference. For example, the following set of commands configures PIM with a
bootstrap router (BSR) candidate interface, a rendezvous point (RP) multicast
address, an RP candidate interface, the default highest next-hop IP address for the
reverse path forwarding (RPF) profile for multicast packets, the shortest path tree
(SPT) threshold value of 1500 Kbps to control the multicast traffic rate, and by
enabling the default source-specific multicast (SSM) group IP address of
232.255.0.0/8. It then enables the GigE 6/0 interface for PIM Sparse Mode:
CASA(config)# ip pim bsr-candidate gige 6/0
CASA(config)# ip pim rp-address 143.1.1.1
CASA(config)# ip pim rp-candidate gige 6/0
CASA(config)# ip pim rpf-profile default
CASA(config)# ip pim spt-threshold 1500
CASA(config)# ip pim ssm default
CASA(config)# interface gige 6/0
CASA(config-if-gige 6/0)# ip pim sparse-mode
Casa Systems
DSG maximum capacities
DSG maximum capacities
Table 9-1 lists the maximum capacities for the DSG elements.
Table 9-1. DSG maximum capacities
DSG element Maximum capacity
DSG tunnels per chassis 64

Separate multicast groups 2048
Channels across all tunnel groups 5120
Channels per tunnel group 2560
Multicast replications per QAM 12K
Multicast service flows per QAM 12K
Replications per multicast stream (max. replications per QAM) x (max. QAM cards)
(tunnel)
Total multicast replications per CMTS (channels per QAM) x (QAM cards) x (DSG tunnels)
Table 9-2 lists and briefly describes the objects related to DOCSIS Set-Top Gateway.
Table 9-2. DSG objects
dsg channel-list Creates a DOCSIS Set-Top Gateway (DSG) channel list.

dsg client-list Creates a DSG client list.
dsg dcd-global-enable Globally enables the downstream channel descriptor (DCD)
for DSG
dsg timer-id Sets the DSG timer.
dsg tunnel Creates a DSG tunnel.
dsg tunnel-group Creates a DSG tunnel group.
dsg unicast-port Defines the DSG unicast port.
dsg vendor-param-id Configures DSG vendor parameters.
Casa Systems
dsg channel-list
dsg channel-list
Purpose
The dsg channel-list command creates a DSG channel-list used in the DCD message
to advertise which QAMs contain DSG tunnels and which channel frequencies carries
them, in order to reduce the STB initial scan time and expedite the DSG client
bring-up. The channel-list can then be applied on any QAM channel (regardless of
whether there are DSG tunnels on it). It is not intended to indicate which STB devices
go on which channel. However, the center frequency indicated by the channel-list
definition must be within the frequency range defined for the QAM channels enabled
for DSG. The center frequency must be defined as a multiple of 62500 Hz.
Mode
(config)#
Syntax
dsg channel-list <1:4294967295> channel <1:4294967295> frequency
<0:1000000000>
no dsg channel-list <1:4294967295> channel <1:4294967295>
Properties
<1:4294967295> Channel list ID.

channel <1:4294967295> Downstream channel index.
frequency <0:1000000000> Center frequency of the DSG channels. The actual
number must be a multiple of 62500 Hz.
Example:
CASA(config)# dsg channel-list 1

channel 1 frequency 526000000
CASA(config)# no dsg channel-list 1
channel 1
Casa Systems
dsg channel-list
interface qam
channel <id> dsg channel-list <id>
Sends a DSG channel list as a DCD message over a QAM channel. (See the
interface qam command.)

CASA(conf-qam 0/1)# channel 0 dsg channel-list 1
show dsg channel-list [<id>]
Shows the DSG channel list configuration.
CASA(config)# show dsg channel-list

dsg channel-list 1 channel 0 frequency 62500
show dsg downstream [<slot>/<port>/<chan>] {dcd | decoded-dcd | tg

[<1:4294967295> channel <1:4294967295>] | tunnel [<1:4294967295>]}
Shows a downstream DSG configuration.
CASA(config)# show dsg downstream dcd

ds dcd dcd num of dcd num of dcd num of
i/f state Tx sent change cnt fragment
0/1/0 dis off 0 0 0
0/1/1 dis off 0 0 0
0/1/2 dis off 0 0 0
0/1/3 dis off 0 0 0
show dsg statistics [dcd | traffic]
Shows the DSG statistics.
CASA(config)# show dsg statistics

DS Channel DCD
2/0/0 0
2/0/1 0
Casa Systems
dsg channel-list
show dsg qam [<slot>/<port>]
Shows the DSG QAM configuration.
CASA(config)# show dsg qam

interface qam 0/0
interface qam 0/1
interface qam 0/2
interface qam 0/3
interface qam 0/4
interface qam 0/5
interface qam 0/6
interface qam 0/7
interface qam 4/0

interface qam 4/1
interface qam 4/2
interface qam 4/3
interface qam 4/4
interface qam 4/5
interface qam 4/6
interface qam 4/7
Casa Systems
dsg client-list
dsg client-list
Purpose
The dsg client-list command creates a DSG client list. This client list can then be
assigned to a dsg tunnel.
Mode
(config)#
Syntax
dsg client-list <1:4294967295> client <1:4294967295> id-type {appId
id-value <0:65535> | broadcast id-value <1:65535> | caSysId
id-value <0:65535> | macAddr id-value <mac_addr}
[vendor-param-id <1:4294967295>]
no dsg client-list <1:4294967295> client <1:4294967295>
Properties
<1:4294967295> Client list ID.

client <1:4294967295> Client number.
id-type {appId id-value Client list ID type with its value, one of the following:
<0:65535> | broadcast
id-value <1:65535> | • appID — Application ID.
caSysId id-value <0:65535> • broadcast — Broadcast ID.
| macAddr id-value
<mac_addr} • caSysId — Conditional Access (CA) system ID.
• macAddr — Well-known STB MAC address.
Example:
CASA(config)# dsg client-list 1

client 1 id-type appID id-value 0
CASA(config)#
no dsg client-list 1 client 1
Casa Systems
dsg client-list
Properties
vendor-param-id Optional dsg vendor-param-id for the

<1:4294967295> vendor-specific parameters, and applied to the
specified vendor group, default 0.
Example:
CASA(config)# dsg client-list 1 client

1 id-type appID id-val 0
vendor-param-id 12222
show dsg client-list
Shows the DSG client list configuration.
CASA(config)# show dsg client-list

dsg client-list 1 client 1 id-type broadcast id-value 2048
vendor-param-id 2
Casa Systems
dsg dcd-global-enable
dsg dcd-global-enable
Purpose
The dsg dcd-global-enable command globally enables the downstream channel

descriptor (DCD) for DSG. This property is enabled by default and must remain
enabled for DCD to work on any the modules.
Mode
(config)#
Syntax
[no] dsg dcd-global-enable
Casa Systems
dsg timer-id
dsg timer-id
Purpose
The dsg timer-id command sets the DSG client state machine timer. The DSG timer
entry is then applied to a downstream channel and encoded in the DCD message.
Mode
(config)#
Syntax
dsg timer-id <1:4294967295> t1 <1:65535> t2 <1:65535> t3 <1:65535>
t4 <1:65535>
no dsg timer-id <1:4294967295>
Properties
<1:4294967295> Timer ID.

t1 <1:65535> DSG initialization timeout (t1) in seconds.
t2 <1:65535> DSG operational timeout (t2) in seconds.
t3 <1:65535> DSG two-way retry timeout (t3) in seconds.
t4 <1:65535> DSG one-way retry timeout (t4) in seconds.
Example:
CASA(config)# dsg timer-id 1 t1 20 t2

30 t3 40 t4 50
CASA(config)# no dsg timer-id 1
show dsg timer
Shows the DSG timer configuration.
CASA(config)# show dsg timer
Casa Systems
dsg tunnel
dsg tunnel
Purpose
The dsg command creates a DOCSIS Set-top Gateway (DSG) tunnel. The number of
supported DSG replications per chassis is 8192. Each QAM line card can have up to
1638 DSG replications.
Modes
(config)#
(conf-dsg-tunnel <id>)#
Syntax
(config)# [no] dsg tunnel <1:4294967295>
(conf-dsg-tunnel x)#
classifier <1:65535> <0:255> {<src_ip4/mask> | ipv6 <src_ip6/mask>}
<dst_ip> [<0:65535> <0:65535>] [indcd [<0:65535> <0:65535>]]
no classifier <1:65535>
[no] client-list <1:4294967295>
dst-address <mac_addr>
no dst-address
group <1:4294967295>
no group
service-class <name>
no service-class
Properties
<1:4294967295> DSG tunnel ID.
Example:
CASA(config)# dsg tunnel 2

CASA(config)# no dsg tunnel 2
Casa Systems
dsg tunnel
Properties
classifier <1:65535> Classifier ID, where a classifier can have multiple

<0:255> {<src_ip4/mask> sources to a single multicast destination address.
| ipv6 <src_ip6/mask>} The parameters are as follows:
<dst_ip> [<0:65535>
<0:65535>] [indcd • <1:65535> — ID. The maximum number of DSG
[<0:65535> <0:65535>]] tunnel classifiers is 64.
• <0:255> — Priority.
• <src_ip4/mask> — Source IPv4 address and
mask. Multiple sources can be applied to a single
destination.
• ipv6 <src_ip6/mask> — Alternative source IPv6
address and mask.
• <dst_ip> — Destination multicast IP address,
such as 224.0.0.1. Multiple sources can be
applied to a single destination.
• <start_dst_pt> <end_dst_pt> — Optional destina-
tion starting and ending port numbers.
• indcd [<start_dst_pt> <end_dst_pt>] — Optional
to include the classifier in the downstream chan-
nel descriptor (DCD) message, with the optional
destination start and end port numbers.
Example:
CASA(conf-dsg-tunnel 2)# classifier 1

20 192.168.0.1/24 224.0.0.100 indcd
6666 6667
CASA(conf-dsg-tunnel 2)#
no classifier 1
client-list Assigns a dsg client-list to the DSG tunnel.

<1:4294967295>
Example:
CASA(conf-dsg-tunnel 2)# client-list

123
CASA(conf-dsg-tunnel 2)# no client-list
Casa Systems
dsg tunnel
Properties
dst-address <mac_addr> Destination MAC address for the DSG tunnel, in the
form xxxx.xxxx.xxxx.
Example:
CASA(conf-dsg-tunnel 2)# dst-address

1234.2345.3456
CASA(conf-dsg-tunnel 2)# no dst-address
group <1:4294967295> Associates a dsg tunnel-group with the DSG tunnel.
Example:
CASA(conf-dsg-tunnel 2)# group 3

CASA(conf-dsg-tunnel 2)# no group
service-class <name> Assigns a cable service-class name <name> to the

DSG tunnel, up to 16 characters.
Example:
CASA(conf-dsg-tunnel 2)# service-class

private-class
CASA(conf-dsg-tunnel 2)#
no service-class
show dsg tunnel [<id>]
Shows the DSG tunnel configuration, optionally for a specific tunnel ID.
CASA(config)# show dsg tunnel 1
group 1
dst-address 0100.5e40.100b
client-list 1
classifier 1 1 0.0.0.0/0 239.192.16.11 indcd
Casa Systems
dsg tunnel
show cable dsg tunnel [<id> [cfrs | clients | interface | verbose]]
Shows the cable DSG tunnel configuration. Output can also be filtered by ID, and then
by DSG classifier (CFRS), clients, interface, or verbose.
CASA(config)# show cable dsg tunnel 1

tunnel TG cfr tunnel rule rule client service
id state mac-addr id id state IF id state listId class
1 en 0100.5e40.100b 1 1 en 11/0/0 1 en 1
CASA(config)# show cable dsg tunnel 1 cfrs

cfr cfr cfr destination ip source ip srcPre d_port d_port
id state pri address address length start end
1 en 1 192.168.0.1 000.000.000.000 0 0 65535
CASA(config)# show cable dsg tunnel 1 clients

tunnel client client client client
id listId id id type address
1 1 1 Application ID 0x1
CASA(config)# show cable dsg tunnel 1 interface

tunnel downstream rule
id interface id
1 11/0/0 1
CASA(config)# show cable dsg tunnel 1 verbose

Tunnel ID : 1
State : en
MAC Addr : 0100.5e40.100b
TG Id : 1
Cfr Id : 1
State : en
Priority : 1
Dest IP : 239.192.016.011
Src IP : 000.000.000.000
Src Prefix Length : 0
Dest Port Start : 0
Dest Port End : 65535
Client List Id : 1
Client Id : 1
Client Id Type : Application ID 0x1
Interface : 11/0/0
Rule ID : 1
Casa Systems
dsg tunnel
show multicast replication
Shows the multicast replication that includes DSG.
multicast group config 1

Multicast Session
Casa Systems
dsg tunnel-group
dsg tunnel-group
Purpose
The dsg tunnel-group command creates a DSG tunnel group. A DSG tunnel can then
be added to the tunnel group and you can associate a downstream channel with a DSG
tunnel group. The maximum number of DSG channels in a tunnel group is 2560 and
across all tunnel groups is 5120.
Modes
(config)#
(conf-dsg-tunnel-grp <id>)#
Syntax
(config)# [no] dsg tunnel-group <1:4294967295>
(conf-dsg-tunnel-grp x)#
channel <1:4294967295> qam <slot>/<port>/<chan> [rule-priority
<0:255>] [vendor-param-id <1:4294967295>]
no channel <1:4294967295>
Properties
<1:4294967295> DSG tunnel group ID, although the maximum number

of tunnel groups is 32.
Example:
CASA(config)# dsg tunnel-group 2

CASA(conf-dsg-tunnel-grp 2)# exit
CASA(config)# no dsg tunnel-group 2
channel <1:4294967295> Channel ID.

qam <slot>/<port>/<chan> QAM interface ID, as <slot>/<port>/<channel>. (See
the interface qam command.) The maximum
number of QAM channels per tunnel group is 2560.
rule-priority <0:255> Optional rule priority number.
Casa Systems
dsg tunnel-group
Properties
vendor-param-id Optional dsg vendor-param-id.

<1:4294967295>
Example:
CASA(conf-dsg-tunnel-grp 2)# channel 1

qam x/y/z rule-priority 20
vendor-param-id 1 ucid-list 1
CASA(conf-dsg-tunnel-grp 2)#
no channel 1
show dsg tunnel-group
Shows the DSG tunnel group configuration.
CASA(config)# show dsg tunnel-group

channel 1 qam x/y/z rule-priority 20 vendor-param-id 1 ucid-list 1
channel 2 qam x/y/z rule-priority 30 vendor-param-id 500 ucid-list 2
show dsg tunnel
Shows the tunnel groups for each DSG tunnel.
CASA(config)# show dsg tunnel
dsg tunnel 1
group 1
dst-address 0100.5e01.6401
service-class "video-DS"
classifier 1 2 0.0.0.0/0 224.11.11.1 indcd 3001 30011
dsg tunnel 2
group 2
service-class "video-DS"
…
Casa Systems
dsg unicast-port
dsg unicast-port
Purpose
The dsg unicast-port command configures the DSG unicast port, 8888 by default.
Mode
(config)#
Syntax
dsg unicast-port <1:65535>
Properties
<1:65535> Unicast port ID. The default is 8888
Example:
CASA(config)# dsg unicast-port 8888
show dsg running-config
Shows the DSG running configuration that includes the unicast port value.
CASA(config)# show dsg running-config

dsg tunnel-group 1
dsg tunnel-group 2
dsg tunnel 1
dsg unicast-port 8888
Casa Systems
dsg vendor-param-id
dsg vendor-param-id
Purpose
The dsg vendor-param-id command configures DSG vendor parameters. The vendor
parameter ID can then be assigned to a dsg client-list.
Mode
(config)#
Syntax
dsg vendor-param-id <1:4294967295> vendor <1:4294967295> oui <oui>
value <val>
no dsg vendor-param-id <1:4294967295> vendor <1:4294967295>
Properties
<1:4294967295> Vendor parameter index for the vendor-specific

parameters, and applied to the specified vendor
group.
vendor <1:4294967295> Vendor ID.
oui <oui> Vendor Organizational Unique Identifier (OUI), in the
form xx:xx:xx.
value <val> DSG vendor parameters vendor value.
Example:
CASA(config)# dsg vendor-param-id 1

vendor 1 oui 01:02:03 value VENDOR
CASA(config)# no dsg vendor-param-id 1
vendor 1
Casa Systems
dsg vendor-param-id
show dsg vendor-param
Shows the default CM vendor configuration.
CASA(config)# show dsg vendor-param

dsg vendor-param-id 1 vendor 1 oui 01:02:03 value abc
Casa Systems
10-1
Chapter 10. Load balancing
Load balancing commands description

The load balancing feature of the Casa CMTS allows system operators to distribute
cable modems across radio frequency downstream and upstream channels on the same
cable interface line card, or across multiple cable interface line cards in some
circumstances. Load balancing maximizes bandwidth and usage of the cable plant.
Load balancing supports multiple methods to achieve greater bandwidth availability.
These include static and dynamic load balancing schemes, inter-line card and
intra-line card support, and in some circumstances, configuration of load balancing
groups that entail multiple interfaces, multiple load balancing policies, and the option
to configure multiple additional load balancing parameters.
A CMTS channel can be load-balanced using one of two methods:
• Number of CMs — Load balancing according to the number of CMs on the

interface, or based on how modems are classified by cable tag.
• Utilization — Load balancing according to the current percentage of channel
utilization.
Each of the methods can further be operated in two types: static or dynamic.
• Static — Load balancing is done at ranging request time. When a CM sends its
initial ranging request message, the CMTS responds with a ranging response
message that includes either a Downstream Frequency Override or an Upstream
Channel ID Override field that instructs the CM which channels it should use.
Casa Systems
Load balancing commands description
• Dynamic — A form of load balancing in which CMs are moved among upstream
and downstream channels within the same service group after their initial
difference between two interfaces exceeds a user-defined percentage. The CMTS
will use DCC/UCC messages to move CMs with single upstream/downstream
channels, and Dynamic Bonding Change (DBC) messages to move CMs with
bonding upstream/downstream channels, to different bonding groups.
For DOCSIS and EuroDOCSIS 3.x modems, the dynamic load-balancing software
generates a downstream channel set with a minimum load to fit the modem’s RCP.
This prevents rejection of the new channel set so that load balancing is not canceled
when the assigned modem is under load. The Casa CMTS supports both methods and
types to load balance upstream and downstream channels. You can configure a Casa
CMTS using static load balancing only, or using static load balancing and dynamic
load balancing together.
Because load balancing can only be done to upstream and downstream interfaces
sharing the same physical connectivity, the upstream and downstream interfaces have
to belong to the same service group. Both channel bonding and non-channel bonding
modems can participate in load balancing. Channel bonding modems will count as one
CM for each of its channels.
To configure load balancing:
1. Define the MAC domains and the service groups.

2. Define the basic rules and/or the execution rules.
3. Define the load balancing policy and assign the rules to the policy.
4. Apply the policy to a load balancing group, either the default group or a restricted
load balance group.
To apply a load balancing policy globally, apply it to the default group. To apply
different load balancing policies to different MAC Domain/Service Groups, first
define the rules and the policies. Then create a restricted load balance group, and
assign it to the MAC Domain/Service group.
Casa Systems
Load balancing 10-3
Sample load balancing configuration
The following series of commands shows a sample load balancing configuration.
CASA(config)# load-balance enable
CASA(config)# load-balance basic-rule 1

CASA(load-bal-basic-rule 1)# enable
CASA(load-bal-basic-rule 1)# suspend-load-balance from 13:00:00 to
20:00:00

23:00:00

01:00:00
CASA(config)# load-balance execution-rule 1

CASA(load-bal-exe-rule 1)# enable
CASA(load-bal-exe-rule 1)# method modem
CASA(load-bal-exe-rule 1)# method util dynamic
CASA(load-bal-exe-rule 1)# threshold load 10 enforce 30 minimum 35
CASA(config)# load-balance policy 1

CASA(load-bal-policy 1)# rule basic 1
CASA(load-bal-policy 1)# rule execution 1
CASA(config)# load-balance general-group default-settings

(load-bal-general-default)# initial-tech unicast-ranging
CASA(config)# load-balance general-group mac-domain 1 service-group

FN_A
CASA(load-bal-general-mac-1-sg-FN_A)# enable
CASA(load-bal-general-mac-1-sg-FN_A)# initial-tech direct
CASA(load-bal-general-mac-1-sg-FN_A)# policy-id 1
CASA(config)# load-balance general-group mac-domain 1 service-group

FN_B
CASA(load-bal-general-mac-1-sg-FN_B)# no enable
CASA(load-bal-general-mac-1-sg-FN_B)# initial-tech direct
CASA(load-bal-general-mac-1-sg-FN_B)# policy-id 1
CASA(config)# load-balance restricted-group group-id 10

CASA(load-bal-restrict 10)# enable
CASA(load-bal-restrict 10)# docsis-mac 1
Casa Systems
CASA(load-bal-restrict 10)# initial-tech broadcast-ranging

CASA(load-bal-restrict 10)# policy-id 1
CASA(load-bal-restrict 10)# service-type-id restrict1
CASA(load-bal-restrict 10)# qam 0/1/0
CASA(load-bal-restrict 10)# upstream 1/2
CASA(load-bal-restrict 10)# upstream 1/3
CASA(config)# load-balance restricted-cm 1

CASA(load-bal-restrict-cm 1)# mac addr 0018.0123.5678
CASA(load-bal-restrict-cm 1)# service-type-id restrict1
CASA(load-bal-restrict-cm 1)# restricted-load-balance-group 10
CASA(config)# load-balance restricted-cm 2

CASA(load-bal-restrict-cm 2)# mac addr 0019.0000.0000 mask
ffff.0000.0000
CASA(load-bal-restrict-cm 2)# service-type-id restrict1
CASA(load-bal-restrict-cm 2)# restricted-load-balance-group 10
Table 10-1 lists and briefly describes the objects related to load balancing.
Table 10-1. Load balancing objects
load-balance Initiates load balancing.

load-balance Sets the Annex B upstream upper frequency limit.
annexb-upper-frequency
load-balance basic-rule Set load balancing basic rules.
load-balance dcc-retry Enables load balancing channel move retries.
load-balance enable Enables load balancing globally.
load-balance exclusion Defines a load balancing exclusion list.
list
load-balance Defines load balancing execution rules.
execution-rule
load-balance Defines load balancing general group policies.
general-group
load-balance permit Permits dynamic bonding change (DBC) messages for
dbc-chg-prim-ds downstream load balancing.
Casa Systems
Load balancing 10-5
Table 10-1. Load balancing objects
load-balance policy Defines a load balancing policy.

load-balance Creates a restricted configuration for CMs.
restricted-cm
load-balance Creates a restricted group configuration.
restricted-group
Casa Systems
load-balance
load-balance
Purpose
The load-balance command configures load balancing for the CMTS. Configuring
load balancing requires the following steps:

2. Define the basic rules and/or the execution rules.
3. Define the load balancing policy and assign the rules to the policy.
4. Apply the policy to a load balancing group, either the
load-balance general-group or a load-balance restricted-group. To apply a
load balancing policy globally, apply it to the default group.
To apply different load balancing policies to different MAC domain/service groups,

first define the rules and the policies. Then create a restricted load balance group, and
assign it to the MAC domain/service group.
Modes
(config)#
(load-bal-basic-rule x)#
(load-bal-exclusion-list)#
(load-bal-exe-rule x)#
(load-bal-general-mac-x-sg-x)#
(load-bal-policy x)#
(load-bal-restrict-cm x)#
(load-bal-restrict x)#
clear load-balance log
Clears all load balancing logs.
CASA(config)# clear load-balance log
Casa Systems
Load balancing 10-7
load-balance
show load-balance dynamic [{begin | end} <date> <time>]
Shows the load balancing dynamic configuration.
CASA(config)# show load-balance dynamic

Mac address Mac_id upstream-channel downstream-channel initial_tech
-------------------------------------------------------------------
cmd status type time
-----------------------------------
e448.c7b8.f306 1->1 1->2 11,2,3,4,9,10,1,12->- direct
dbc Success BAL 2015-12-15 14:11:06
---------------------------------------------------------------------
total: 1; success:1; other:0
The possible type values are as follows:
BAL — Balancing done by the system.

CLI — Load balancing done manually from the CLI.
CSM — Dynamic Channel Change (DCC) done by CSM per CM.
DSA — DCC done by voice (Dynamic Service Addition).
EM — Energy management.
MIB — Load balancing done manually from SNMP.
MLT — DCC by limit replication multicast.
RGLB — General load balancing done until registration.
RSLB — DCC moved a CM into a restricted load-balance group.
SG — Channel is not in the channel set of the configured service group.
show load-balance static [{begin | end} <date> <time>]
Shows the load balancing static configuration, the equivalent of the show static
load-balance command.
CASA(config)# show load-balance static

Mac address date time upstream downstream new us new ds
---------------------------------------------------------------------
total: 0;
Casa Systems
load-balance annexb-upper-frequency
load-balance annexb-upper-frequency
Purpose
The load-balance annexb-upper-frequency command sets the Annex B upstream

upper frequency limit. This allows CMs supporting extended upstream frequencies to
register with the CMTS (or move per dynamic bonding change, DBC) on Annex B
upstream channels up to the specified frequency. The configurable upper frequency
range is 0–99 MHz, specified in Hz, with the default 0 value setting no frequency
limit.
Modes
(config)#
Syntax
(config)# load-balance annexb-upper-frequency <0:99000000>
Casa Systems
Load balancing 10-9
load-balance basic-rule
Purpose
The load-balance basic-rule command sets the basic rules for load balancing. The
DOCS-LOADBAL3-MIB defines the load balance basic rules in SNMP. To configure
the basic rules, do the following:

2. Enter a basic rule.
3. Enable or disable this rule.
4. Specify a time period during which to suspend load balancing.
Modes
(config)#
(load-bal-basic-rule <id>)#
Syntax
(config)# [no] load-balance basic rule <1:4294967295>
(load-bal-basic-rule x)#
[no] enable
suspend-load-balance from <start_time> to <end_time>
Properties
<1:4294967295> Load balancing basic rule ID.
Example:

CASA(config)#
no load-balance basic-rule 1
Casa Systems
enable Enables the basic rule. The default for the

load-balance basic-rule is no enable.
Example:

CASA(load-bal-basic-rule 1)# no enable
suspend-load-balance Sets a basic rule for a time period (from and to) to
from <start_time> to suspend load balancing, in H:MM:SS or HH:MM:SS
<end_time> format.
Example:
CASA(load-bal-basic-rule 1)#
suspend-load-balance from 12:30:00 to
15:00:00
show load-balance basic-rule
Shows the load balancing basic rule configuration.
CASA(config)# show load-balance basic-rule
load-balance basic-rule 1
suspend-load-balance from 12:30:00 to 15:00:00
Casa Systems
Load balancing 10-11
load-balance dcc-retry
load-balance dcc-retry
Purpose
The load-balance dcc-retry command sets the number of Dynamic Channel Change
(DCC) retries to perform during load balancing. These retries address situations when
a single DCC attempt fails to move a modem away from a forbidden port (using the
prov-attr-mask attribute mask in the modem configuration file) and additional retry
attempts at moving the modem are necessary. The configurable range is 0–10 retries.
The default is zero retries, meaning to try the DCC only once.
Mode
(config)#
Syntax
[no] load-balance dcc-retry <0:10>
Casa Systems
load-balance enable
load-balance enable
Purpose
The load-balance enable command enables the load balancing function globally.
By default, the upstream channel has precedence in load balancing across MAC
domains, where the lowest loaded (least busy) upstream channel is selected within the
service group. Then, the lowest loaded downstream channel is selected within the
MAC domain of the selected upstream channel. If the downstream precedence is
configured, then the downstream channel is selected first.
The CMTS uses downstream frequency override and the upstream channel ID
override in the ranging response message to move modems to a different MAC
domain if needed. This applies to all DOCSIS 1.0, 1.1, 2.0 and 3.0 modems. The SID
in the ranging response message is 0x3fff.
Mode
(config)#
Syntax
[no] load-balance enable
[no] load-balance enable across-mac [downstream]
Properties
enable Enables load balancing globally.
Example:

CASA(config)# no load-balance enable
Casa Systems
load-balance enable
enable across-mac Optionally enables static load balancing across MAC

[downstream] domains, with the optional downstream modifier.
Example:

across-mac downstream
CASA(config)#
no load-balance enable across-mac
show load-balance running-config
Shows if load balancing is enabled in the running configuration.
CASA(config)# show load-balance running-config

!
!
! load balance commands
!
load-balance enable
load-balance basic-rule 1
suspend-load-balance from 12:30:00 to 13:00:00
Casa Systems
load-balance exclusion list

Purpose
The load-balance exclusion list command sets exclusions for load balancing (up to
200).
Modes
(config)#
Syntax
(config)# [no] load balance exclusion list
[no] mac addr <mac_addr> mask <mask> [both | dynamic | static]
Properties
mac addr <mac_addr> mask MAC address and mask for the exclusion list, in
<mask> [both | dynamic | xxxx.xxxx.xxxx hex format, to apply the exclusion list
static] to modems from a particular modem vendor. One of
the optional modifiers excludes the CM from both
dynamic and static load balancing, from just dynamic
load balancing, or from just static load balancing.
Example:
CASA(config)# load-balance exclusion

list
CASA(load-bal-exclusion-list)# mac addr
0014.0000.0000 mask ffff.0000.0000
static
CASA(load-bal-exclusion-list)# no mac
addr 0014.0000.0000 mask ffff.0000.0000
Casa Systems
show load-balance exclusion list
Shows the exclusion list configuration.
CASA(config)# show load-balance exclusion list

!
mac addr 0022.2d77.fc56 mask ffff.0000.0000 static
Casa Systems
load-balance execution-rule
Purpose
The load-balance execution-rule command sets execution rules for load balancing,
with up to 16 execution rules allowed. Note that an execution rule is always enabled;
there is no command to disable it. Define execution rules as follows:
1. Enter a load balance execution rule.

2. Specify a minimum time interval between each load balance.
3. Specify a minimum time interval between each upstream load balance.
4. Specify a minimum time interval to move the same modem.
5. Specify a method for load balancing calculation.
6. Specify a method of upstream load balancing for load balancing calculation.
Modes
(config)#
(load-bal-exe-rule <id>)#
Syntax
(config)# [no] load-balance execution-rule <1:16>
(load-bal-exe-rule x)#
cable modem rebalance-interval <60:3600>
no cable modem rebalance-interval
cable modem retry-interval first <0:4294967295> second
<0:4294967295>
no cable modem retry-interval
[no] enable
interval <10:3600>
method {modem | utilization} [dynamic]
no method [dynamic]
[no] permit multicast-session modem move
suspicious-channel retry interval <0:86400>
threshold load <0:100> [enforce <0:100>] [dynamic minimum <2:500> |
minimum <2:500>]
no threshold
upstream-interval <10:3600>
no upstream-interval
upstream-method {modem | utilization} [dynamic]
Casa Systems
no upstream-method [dynamic]
upstream-threshold load <0:100> [enforce <0:100>] [dynamic minimum
<2:500> | minimum <2:500>]
no upstream-threshold
Properties
<1:16> Execution rule ID.
Example:
CASA(config)# load-balance
execution-rule 5
CASA(config)#
no load-balance execution-rule 5
cable modem Minimum time between when CM does load

rebalance-interval balancing successfully and then it can be
<60:3600> load-balanced again, the default 3600 seconds.
Example:
CASA(load-bal-exe-rule 5)# cable modem

rebalance-interval 200
CASA(load-bal-exe-rule 5)#
no cable modem rebalance-interval
cable modem Minimum time interval to move the same modem if

retry-interval first previous load-balancing failed. There are two retry
<0:4294967295> second values. The first retry defaults to 86400 seconds (24
<0:4294967295> hours). The second retry defaults to 432000 seconds
(5 days).
Example:
CASA(load-bal-exe-rule 5)# cable modem

retry-interval first 35000 second 87000
no cable modem retry-interval
Casa Systems
enable Enables the execution rule.
Example:
CASA(load-bal-exe-rule 5)# enable

CASA(load-bal-exe-rule 5)# no enable
interval <10:3600> Minimum time interval between each load balance

calculation, default 10 seconds.
Example:
CASA(load-bal-exe-rule 5)# interval 30
method {modem | Method to determine when to load balance, either

utilization} [dynamic] modem (number of CMs on the interface) or
utilization (current percentage of channel utilization).
A method can apply to dynamic, static or both types
of load balancing. If dynamic is not configured, the
method will apply to both static and dynamic load
balancing. If dynamic is configured, the method
applies only to dynamic load balancing. To disable
static load balancing, set the threshold load to 0.
The default load-balance execution-rule method is
modem.
Example:
CASA(load-bal-exe-rule 5)# method modem

dynamic
no method dynamic
CASA(load-bal-exe-rule 5)# no method
Casa Systems
permit multicast-session Permits (or denies) moving a CM in a multicast

modem move session to the most idle channel in the service group,
unless a restricted load balancing group applies. The
default is permit.
Example:
CASA(load-bal-exe-rule 5)# permit

multicast-session modem move
no permit multicast-session modem move
suspicious-channel retry Retry interval for suspicious channels from

interval <0:86400> unregistered modems, default 3600 seconds; a 0
value indicates disabling moving the modem to a
suspicious channel.
Example:
suspicious-channel retry interval 3600
Casa Systems
threshold load <0:100> Load difference between interfaces to start static load
[enforce <0:100>] balancing, the number of modems on the modem
[dynamic minimum <2:500> method or the percentage on the utilization method,
| minimum <2:500>] default 10. The optional additional modifiers are as
follows:
• enforce <num> — Enforces the load difference

for dynamic load balancing, the number of
modems on the modem method or the percent-
age on the utilization method, default 0 (not
enforced).
• dynamic minimum <num> — Minimum number
of modems for dynamic load balancing, default 0.
• minimum <num> — For static load balancing,
the minimum number of modems on the modem
method or the minimum percentage on the utiliza-
tion method, default 10.
Example:
CASA(load-bal-exe-rule 5)# threshold

load 100 dynamic minimum 2
CASA(load-bal-exe-rule 5)# no threshold
upstream-interval Minimum interval between upstream load balancing

<10:3600> calculations, in seconds.
Note: If the upstream-interval is not configured, the

interval value applies to both upstream and
downstream load balancing. If the upstream-interval
is configured, the upstream-interval value applies to
upstream load balancing; the interval value applies
to downstream load balancing.
Example:
upstream-interval 60
no upstream-interval 60
Casa Systems
upstream-method {modem | Method to determine when to load balance for

utilization} [dynamic] upstream traffic. See the method property for details.
Example:
upstream-method modem dynamic
no upstream-method dynamic
no upstream-method
upstream-threshold load Utilization method for upstream load balancing

<0:100> [enforce calculations. See the threshold load property for
<0:100>] [dynamic details on the options.
minimum <2:500> |
minimum <2:500>] Example:
upstream-threshold load 100
no upstream-threshold
show load-balance execution-rule [<num>]
Shows the load balancing execution rule configuration.
CASA(config)# show load-balance execution rule
load-balance execution-rule 1
method modem
threshold load 100 dynamic minimum 2
Casa Systems
load-balance general-group
Purpose
The load-balance general-group command configures general groups for load

balancing. To apply a load balancing policy globally, apply it to the default group. To
apply different load balancing policies to different MAC domain/service groups, first
define the rules and the policies. Then create a restricted load balance group and
assign it to the MAC domain/service group. Configure general groups as follows:
1. Enter the general load balance group default.

2. Enable or disable load balancing on the MAC service-group general group.
3. Specify a technique to move CMs.
4. Specify the policy to use for load balancing execution.
Modes
(config)#
(load-bal-general-default)#
(load-bal-general-mac-<id>-sg-<name>)#
Syntax
(config)#
load-balance general-group default-settings
(load-bal-general-default)#
[no] enable
initial-tech {broadcast-ranging | direct [frequency-limit <0:60>] |
policy-id <0:4294967295>
(config)#
[no] load-balance general-group mac-domain <1:96> service-group <name>
(load-bal-general-mac-x-sg-y)#
[no] enable
policy-id <0:4294967295>
Casa Systems
Properties
default-settings Enters load balancing group default settings mode.
Example:
general-group default-settings
CASA(load-bal-general-default)#
enable Enables the load balancing function for the default

group (the default).
Example:
CASA(load-bal-general-default)# enable
no enable
Casa Systems
initial-tech Specifies the initial technique to use for moving CMs,

{broadcast-ranging | one of the following:
direct [frequency-limit
<0:60>] | period-ranging • broadcast-ranging — The CM broadcasts the
| reinitialize-mac | full initial ranging request without going off-line
unicast-ranging} and performing re-registration with the CMTS.
• direct — This is the initial technique default set-
ting. The CM moves directly to another channel
without performing any type of ranging. The fre-
quency-limit value is optional, with 0 no limit.
When this limit is set, if the CMTS needs to move
a modem to a new upstream channel with a fre-
quency difference greater than the set limit during
dynamic load balancing, it uses broadcast-rang-
ing instead of direct.
• period-ranging — The CM move to a new chan-
nel, but performs periodic ranging requests for an
improved channel opportunity.
• reinitialize-mac — The CM MAC address is
reset, forcing the cable model off-line and re-reg-
istering with the CMTS on the new channel.
• unicast-ranging — The CM performs an initial
ranging request for a dedicated channel from the
CMTS where there is no other transmission activ-
ity.
The default for the load-balance general-group is no
initial-tech.
Example:
initial-tech broadcast-ranging
Casa Systems
policy-id <0:4294967295> Sets the load-balance policy for the load balancing
general group. The default for the load-balance
general-group is no policy-id.
Example:
policy-id 2
mac-domain <1:96> Enters load balancing group MAC domain

service-group <name> service-group mode, specified with a MAC domain ID
(see the <1:96> property of the
interface docsis-mac command) and an existing
service group name.
Example:
general-group mac-domain 1
service-group FN_A
CASA(config)# no load-balance
general-group mac-domain 1
service-group FN_A
CASA(load-bal-general-mac-1-sg-FN_A)#
enable Enables the load balancing function for the group.
Example:
enable
no enable
Casa Systems

| reinitialize-mac | full initial ranging request without going off-line
unicast-ranging} and performing re-registration with the CMTS.
quency-limit value is optional, with 0 as no limit.
reset, forcing the cable model off-line and re-reg-
istering with the CMTS on the new channel.
ity.
Example:
policy-id <0:4294967295> Creates the load-balance policy for load balancing

execution.
Example:
policy-id 2
Casa Systems
show load-balance general-group
Shows the load balancing general group configuration.
CASA(config)# show load-balance general-group

cfg-id mac sg-name ds-chan-list us-chan-list enable init-tech policy
success fail
- 1 plant1 1,2,3,4,5,6,7 1,2,3,4 true unknown 0
0 0
0 0
0 0
0 0
show load-balance general-group default-settings
Shows the load balancing general group default settings configuration.
CASA(config)# show load-balance general-group default-settings
load-balance general-group default-settings

policy-id 2
enable
show load-balance general-group mac-domain <id> service-group

<name>
Shows the load balancing MAC domain/service group configuration.
CASA(config)# show load-balance general-group mac-domain 1

service-group plant1
load-balance general-group mac-domain 1 service-group plant1

enable
Casa Systems
load-balance permit dbc-chg-prim-ds
load-balance permit dbc-chg-prim-ds

Purpose
The load-balance permit dbc-chg-prim-ds command permits Dynamic Bonding

Change (DBC) messages for load balancing on the downstream. The optional
dcc-retry setting can also be applied, and can also be set independently of DBC with
the load-balance dcc-retry command.
Mode
(config)#
Syntax
[no] load-balance permit dbc-chg-prim-ds [dcc-retry <0:10>]
Properties
dcc-retry <0:10> Optional number of Dynamic Channel Change (DCC)

retries during load balancing due to a forbidden
attribute mask rule (as set by the prov-attr-mask for
the QAM channel). The default is 0 retries, meaning
try only once. Note that the load-balance dcc-retry
setting supersedes the setting made at this level.
Example:
CASA(config)# load-balance permit

dbc-chg-prim-ds dcc-retry 0
CASA(load-bal-policy 1)# exit
CASA(config)# no load-balance permit
dbc-chg-prim-ds dcc-retry
Casa Systems
load-balance policy
load-balance policy
Purpose
The load-balance policy command sets policies for load balancing (up to 20). To set a
policy:
1. Enter a load balance policy.

2. Add basic rules to a policy. A policy can have multiple basic rules.
3. Add an execution rule to a policy. A policy can have just one execution rule.
Modes
(config)#
(load-bal-policy <id>)#
Syntax
(config)# [no] load-balance policy <1:4294967295>
(load-bal-policy x)#
[no] cable tag <name> {both | dynamic | static}
[no] rule basic <1:4294967295>
rule execution <1:16>
no rule execution
Properties
<1:4294967295> Load balancing policy ID.
Example:
CASA(config)# load-balance policy 1

CASA(load-bal-policy 1)# exit
CASA(config)# no load-balance policy 1
Casa Systems
load-balance policy
cable tag <name> {both | Cable tag for the load balancing policy, as defined by
dynamic | static} the cable tag command. One of the following options
is required:
• disable — Disable dynamic and static load

balancing.
• dynamic — Permit dynamic load balancing only.
• static — Permit static load balancing only.
Example:
CASA(load-bal-policy 1)# cable tag TAG1

dynamic
CASA(load-bal-policy 1)#
no cable tag TAG1 dynamic
rule basic The load-balance basic-rule ID. A policy can have

<1:4294967295> multiple basic rules (up to 64).
Example:

no rule basic 2
rule execution <1:16> The load-balance execution-rule ID, up to 16. A

policy can have only one execution rule.
Example:
rule execution 1
no rule execution
Casa Systems
load-balance policy
show load-balance policy [<num>]
Shows the load balancing policy configuration.
CASA(config)# show load-balance policy
load-balance policy 1
rule execution 1
rule basic 1
rule basic 2
Casa Systems
load-balance restricted-cm
Purpose
The load-balance restricted-cm command creates a restricted configuration for CMs

(RLBCM). To set a restricted CM policy (up to 64):
1. Enter the restricted CM configuration.

2. Enter CM MAC address information.
3. Add a service type ID.
4. Add reference to a restricted load balancing group.
Modes
(config)#
(load-bal-restrict-cm <id>)#
Syntax
(config)# [no] load-balance restricted-cm <1:4294967295>
(load-bal-restrict-cm x)#
cable tag <name>
mac addr <addr> [mask <mask>]
restricted-load-balance-group <1:4294967295>
no restricted-load-balance-group
service-type-id <name>
no service-type-id
Properties
<1:4294967295> Restricted modem ID.
Example:
restricted-cm 1
CASA(load-bal-restrict-cm 1)# exit
CASA(config)#
no load-balance restricted-cm 1
Casa Systems
cable tag <name> Cable tag for the restricted load balancing policy, as
defined by the cable tag command.
Example:
CASA(load-bal-restrict-cm 1)# cable tag

TAG1
no cable tag TAG1
mac addr <addr> [mask MAC address of the modem, in 48-bit xxxx.xxxx.xxxx
<mask>] format, and optional mask (if omitted, defaults to
FFFF.FFFF.FFFF).
Example:
CASA(load-bal-restrict-cm 1)# mac addr

0022.2d77.fc56
restricted-load-balance- References a load-balance restricted-group.

group <1:4294967295>
Example:
CASA(load-bal-restrict-cm 1)#
restricted-load-balance-group 1
no restricted-load-balance-group
service-type-id <name> Adds a cable service-type-id ds-frequency name,

maximum 16 characters, embedded in quotes if
blank spaces.
Example:
no service-type-id
Casa Systems
show load-balance restricted-cm [<num>]
Shows the load balancing restricted-CM configuration.
CASA(config)# show load-balance restricted-cm
load-balance restricted-cm 1
mac addr 0022.2d77.fc56
show cable modem load-balance statistics

CASA# show cable modem load-balance statistics
MACAddress IP Address US DS Mac Sg-name RLBG Policy Cable DS Us Success
Intf Id Id Tag Fail
e448.c7b4.ab62 12.105.1.253 13/3.3/0* 2/1/7# 2 8 0 1 -- 0 0 0 20:1:1::9
show cable modem load-balance downstream restricted-group counters

CASA# show cable modem load-balance downstream restricted-group
counters
Cfg Downstream Registered
Id Interface Modems
----------------------------------------------------------------------
1 1/0/3 1
2 1/0/1 0
3 1/0/2 0
show cable modem load-balance upstream restricted-group counters

CASA# show cable modem load-balance upstream restricted-group counters
Cfg Upstream Registered
Id Interface Modems
----------------------------------------------------------------------
1 4/1.3/0 1
2 4/1.1/0 0
3 4/1.2/0 0
Casa Systems
load-balance restricted-group
Purpose
The load-balance restricted-group command creates a restricted group

configuration. A restricted load balancing group is similar to a general load balancing
group except that an upstream and downstream channel set must be specified. A
restricted load balancing group (RLBG) must be a subset of a CM service group, or
CMs cannot reliably register with the CMTS. The maximum number of RLBGs per
MAC domain and QAM channel is 12.
To set a restricted group policy (up to 600):
1. Enter load balance restricted group mode.

2. Specify the MAC domain on a restricted group.
3. Enable load balancing for this restricted group.
4. Specify a technique to move CMs.
Modes
(config)#
(load-bal-restrict <id>)#
Syntax
(config)# [no] load-balance restricted-group <1:4294967295>
(load-bal-restrict x)#
docsis-mac <1:96>
[no] enable
[no] ofdma <slot>/<port>.<phy_chan>
policy-id <0:4294967295>
[no] qam <slot>/<port>/<chan> [<1:60>]
[no] service-type-id <name>
[no] upstream <slot>/<port>.<chan>/<log_chan> [<1:8>]
Casa Systems
Properties
<1:4294967295> Restricted group ID.
Example:
restricted-group 1
CASA(load-bal-restrict 1)# exit
CASA(config)#
no load-balance restricted-group 1
docsis-mac <1:96> DOCSIS MAC domain on a restricted group. (See the

interface docsis-mac command.)
Example:
CASA(load-bal-restrict 1)# docsis-mac 1
enable Enables load balancing on a restricted group.
Example:
CASA(load-bal-restrict 1)# enable

CASA(load-bal-restrict 1)# no enable
Casa Systems

| reinitialize-mac | full initial ranging request without going offline and
unicast-ranging} performing re-registration with the CMTS.
quency-limit value is optional, with 0 no limit.
reset, forcing the cable model offline and re-regis-
tering with the CMTS on the new channel.
ity.
Example:
CASA(load-bal-restrict 1)# initial-tech

broadcast-ranging
ofdm <slot>/<port>/ Sets a restricted group for the Orthogonal Frequency

<chan> Division Multiplexing (OFDM) channel.
Example:
CASA(load-bal-restrict 1)# ofdm 2/0/0
ofdma <slot>/ Sets a restricted group for the Orthogonal Frequency

<port>.<phy_chan> Division Multiple Access (OFDMA) channel.
Example:
CASA(load-bal-restrict 1)# ofdma 10/0.0
Casa Systems
policy-id <0:4294967295> Sets the load-balance policy for the load balancing
restricted group.
Example:
CASA(load-bal-restrict 1)# policy-id 2
qam <slot>/<port>/<chan> Adds one or more downstream channels on a

[<1:60>] restricted group, specified by slot, port, and
downstream channel. The additional value is the
number of channels in the range. A QAM channel
can be included in up to 12 restricted groups.
Example:
CASA(load-bal-restrict 1)# qam 0/0/0 2

CASA(load-bal-restrict 1)# show this
load-balance restricted-group 1
docsis-mac 1
enable
qam 0/0/0
qam 0/0/1
CASA(load-bal-restrict 1)# end
restricted-group 13
qam 0/0/0 has bond to 12
restricted-groups, please remove one
first!
CASA(load-bal-restrict 13)# no qam 0/0/
0
service-type-id <name> Adds a service type name, up to 16 characters,

embedded in quotes if space characters.
Example:
CASA(load-bal-restrict 1)#
no service-type-id plant1
Casa Systems
upstream <slot>/ Adds an upstream channel to the restricted group, in

<port>.<chan>/<log_chan> the format slot/port.channel/logical channel, with the
[<1:8>] optional number of channels. (See the
interface upstream command.)
Example:
CASA(load-bal-restrict 1)# upstream

5/0.0/1
no upstream 5/0.0/1
show load-balance restricted-group [<num>]
Shows the load balancing restricted group configuration.
CASA(config)# show load-balance restricted-group

cfg-id mac sg-name ds-chan-list us-chan-list enable init-tech policy
success fail
Casa Systems
show cable modem service-type-id
Shows the CMs using the service-type ID.
CASA(config)# show cable modem service-type-id

MAC Address IP Address US DS MAC Prim
Service-Type_ID(C/P)
Intf Intf Status Sid
e448.c7b4.ab62 0.0.0.0 13/0.3/0 2/0/0 init(rc) 285 -/-
e448.c7c0.ebca 0.0.0.0 13/4.2/0 2/2/4 init(rc) 297 -/-
e448.c7c0.f0dc 0.0.0.0 13/2.1/0 2/1/0 init(rc) 288 -/-
Casa Systems
11-1
Chapter 11. Modulation profiles
Modulation profile commands description

A modulation profile is a collection of burst profiles sent to cable modems in upstream
channel descriptor (UCD) messages to configure modem transmit parameters.
Primary and secondary modulation profiles are supported in an upstream logical
channel configuration. Secondary profiles are not supported on logical channel 1.
Making the number of forward error correction (FEC) bytes smaller in the modulation
profile to reduce overhead helps increase throughput.
Table 11-1 lists and briefly describes the objects related to modulation profiles.
Table 11-1. Modulation profile objects
modulation-profile Initiates modulation profiles.

a-long Creates an a-long modulation profile.
a-short Creates an a-short modulation profile.
initial Creates an initial modulation profile.
long Creates a long modulation profile.
request Creates a request modulation profile.
short Creates a short modulation profile.
station Creates a station modulation profile.
ugs Creates an Unsolicited Grant Service (UGS) modulation
profile.
Casa Systems
modulation-profile
modulation-profile
Purpose
The modulation-profile command configures a modulation profile, a collection of

burst profiles sent to CMs in upstream channel descriptor (UCD) messages to
configure modem transmit parameters. Primary and secondary modulation profiles are
supported in an upstream logical channel configuration. Secondary profiles are not
supported on logical channel 1. Making the number of FEC error correction bytes
smaller in the modulation profile to reduce overhead helps increase throughput. There
can be up to 64 modulation profiles.
There are five “Predefined modulation profiles.” This means that any new ones added
have an ID of 6 or higher. The predefined profiles are recommended. However, you
can use the predefined profiles to create profiles in auto mode, which is by simply
specifying the operation mode and modulation type when creating the profile. For
example, specifying qpsk creates a profile the same as predefined modulation profile
1; specifying 16qam creates a profile the same as predefined modulation profile 2.
Recommendations for which operation mode to use are as follows:
• If all modems are running DOCSIS 2.0 or 3.0, use Asynchronous Time Division
Multiple Access (ATDMA) mode.
• If the upstream interface has 1.1 or 1.0 modems and 2.0 or 3.0 modems, use
Modified Time Division Multiple Access (MTDMA) mode.
• If all modems are 1.0 or 1.1, use Time Division Multiple Access (TDM) mode.
Mode
(config)#
Syntax
(config)#
[no] modulation-profile <6:1024> [<operation_mode>]
[<modulation_type>]
(config-mod-profile-<id>)#
a-long
a-short
initial
Casa Systems
Modulation profiles 11-3
modulation-profile
long
request
short
station
ugs
Properties
<6:1024> Modulation profile ID. (The numbering begins with 6

because there are five “Predefined modulation
profiles.”) This ID can be used for primary and
secondary modulation profiles assigned to upstream
logical channels.
Example:
CASA(config)# modulation-profile 10
CASA(config-mod-prof-10)# exit
CASA(config)# no modulation-profile 10
Casa Systems
modulation-profile
<operation_mode> Optional mode of operation or channel type when

creating the profile in auto mode, one of the following:
• atdma — Asynchronous Time Division Multiple

Access (ATDMA), a direct evolution of DOCSIS
1.x physical layer (PHY), which uses TDMA multi-
plexing.
• mtdma — Modified Time Division Multiple Access
(MTDMA), or mixed mode operation for ATDMA
and TDMA. MTDMA would let the modem go to
ATDMA if it supports DOCSIS 2.0 and let the
DOCSIS 1.0 modems work on the 16qam or qpsk
modulation type. MTDMA does not support the
6.4-MHz US channel width.
• tdma — Time Division Multiple Access (TDMA),
allowing multiple CMs to share the same individ-
ual RF channel in that it allocates each CM its
own transmit time slot. TDMA supports DOCSIS
1.0/1.1 with a channel width limit of 3.2 MHz.
Example:
CASA(config)#
modulation-profile 10 tdma
CASA(config-mod-prof-10)#
Casa Systems
modulation-profile
<modulation_type> Optional modulation type when creating the profile in

auto mode, one of the following:
• qpsk— Quadrature Phase Key Shifting (QPSK),

available in all modes
• 8qam — 8 QAM, available in all modes
• 16qam — 16 QAM, available in all modes
• 32qam— 32 QAM, not available in TDMA mode
• 64qam— 64 QAM, not available in TDMA mode
Example:
CASA(config)#
modulation-profile 10 tdma qpsk
CASA(config-mod-prof-10)#
This example creates a profile identical to

modulation-profile 1.
Predefined modulation profiles

modulation-profile 1
-->> Uses QPSK for all burst types for TDMA upstream channels.
request tdma qpsk off 64 0 16 338 0 16 fixed on
initial tdma qpsk off 640 5 34 338 0 48 fixed on
station tdma qpsk off 384 5 34 338 0 48 fixed on
short tdma qpsk off 84 6 75 338 13 16 shortened on
long tdma qpsk off 96 8 220 338 0 16 shortened on
-->> Similar to profile 1 except uses 16qam for short and long data
burst types for TDMA upstream channels.
short tdma 16qam off 168 6 75 338 7 16 shortened on
long tdma 16qam off 192 8 220 338 0 16 shortened on
-->> ATDMA type profile; uses QPSK for management bursts, 64qam for
data traffic.
request atdma qpsk off 64 0 16 338 0 16 fixed on 1 1536 qpsk0
initial atdma qpsk off 640 5 34 338 0 48 fixed on 1 1536 qpsk0
Casa Systems
modulation-profile
station atdma qpsk off 384 5 34 338 0 48 fixed on 1 1536 qpsk0

a-short atdma 64qam off 104 12 75 338 6 16 shortened on 1 1536 qpsk1
a-long atdma 64qam off 104 16 220 338 0 16 shortened on 1 1536 qpsk1
-->> MTDMA type profile; uses QPSK for management bursts, 16qam for
TDMA data traffic, 64qam for ATDMA data traffic.
request mtdma qpsk off 64 0 16 338 0 16 fixed on 1 1536 qpsk0
initial mtdma qpsk off 640 5 34 338 0 48 fixed on 1 1536 qpsk0
station mtdma qpsk off 384 5 34 338 0 48 fixed on 1 1536 qpsk0
short mtdma 16qam off 168 6 75 338 7 16 shortened on 1 1536 qpsk1
long mtdma 16qam off 192 8 220 338 0 16 shortened on 1 1536 qpsk1
a-short mtdma 64qam off 104 12 75 338 6 16 shortened on 1 1536 qpsk1
a-long mtdma 64qam off 104 16 220 338 0 16 shortened on 1 1536 qpsk1
Casa Systems
a-long
a-long
Purpose
The a-long command configures a modulation profile for an a-long data grant used
for transmitting large upstream data in DOCSIS 2.0, 3.0, and 3.1.
Mode
Syntax
a-long <operation_mode> <modulation_type> {on | off} <1:1024> <0:16>
<16:255> <0:32767> <0:255> <4:255> {fixed | shortened} {on |
off} <0:2048> <0:2048> {qpsk0 | qpsk1}
Properties
<operation_mode> The a-long modulation profile has the following

operation modes or channel types:
• atdma
• mtdma
<modulation_type> One of the modulation types described in the
<modulation_type> property.
{on | off} Diff encoding, either on or off.
<1:1024> Preamble length. CM burst preambles are a known
data pattern sent to all CMs by the CMTS through the
Upstream Channel Descriptor (UCD).
<0:16> FEC-T bytes.
<16:255> FEC-K bytes, where FEC-T and FEC-K cannot add
up to more than 255 bytes.
<0:32767> Scrambler 15-bit seed. In most cases, this value is
338. See also the {on | off} property for scrambler
mode.
<0:255> Maximum burst size (mini-slots).
Casa Systems
a-long
<4:255> Guard time, the number of symbols to follow the end

of a burst, in modulation intervals.
{fixed | shortened} Code word length, fixed or shortened. Code word
shortening is used for two purposes: when there is
insufficient data to fill complete codewords, and to
achieve strong burst noise protection. Shortened
code words are usually recommended in that they
save bandwidth.
{on | off} Scrambler mode, on or off.
<0:2048> Interleave depth. This value applies only in certain
cases. In most cases, it is set to 1.
<0:2048> Interleave block. This value applies only in certain
cases. In most cases, it is set to 1536.
{qpsk0 | qpsk1} Preamble type, qpsk0 (low power) or qpsk1 (high
power).
Example
CASA(config-mod-prof-6)# a-long atdma 64qam off 104 4 220 338 0 8 fixed
on 1 1536 qpsk1
Casa Systems
a-short
a-short
Purpose
The a-short command configures an a-short data grant used for transmitting smaller
upstream data in DOCSIS 2.0 and 3.0.
See the a-long command for a description of the properties. The a-short modulation
profile has the following operation modes, as recommended:
• atdma
• mtdma
Mode
Syntax
a-short <operation_mode> <modulation_type> {on | off} <1:1024> <0:16>
off} <0:2048> <0:2048> {qpsk0 | qpsk1}
Example
CASA(config-mod-prof-7)# a-short atdma 64qam off 104 4 75 338 6 8 fixed
on 1 1536 qpsk1
Casa Systems
initial
initial
Purpose
The initial command defines an initial data grant used for transmitting upstream data
when, an interval in which new CMs can join the network.
See the a-long command for a description of the properties. The initial modulation
• atdma
• mtdma
• tdma
Mode
Syntax
initial <operation_mode> <modulation_type> {on | off} <1:1024> <0:16>
off} <0:2048> <0:2048> {qpsk0 | qpsk1}
Example
CASA(config-mod-prof-8)# initial atdma qpsk off 640 5 34 338 0 48 fixed
on 1 1536 qpsk0
Casa Systems
long
long
Purpose
The long command defines a long data grant used for transmitting large upstream data
in DOCSIS 1.0 and 1.1. The number of minislots in the interval is larger than the
maximum for short interval transmissions.
See the a-long command for a description of the properties. The long modulation
• mtdma
• tdma
Mode
Syntax
long <operation_mode> <modulation_type> {on | off} <1:1024> <0:16>
off} <0:2048> <0:2048> {qpsk0 | qpsk1}
Example
CASA(config-mod-prof-9)# long tdma qpsk off 640 5 34 338 0 48 fixed on
Casa Systems
request
request
Purpose
The request command defines a request data grant used for transmitting upstream
data, an interval in which requests can be made for bandwidth for upstream data
transmission.
See the a-long command for a description of the properties. The request modulation
• atdma
• mtdma
• tdma
Mode
Syntax
request <operation_mode> <modulation_type> {on | off} <1:1024> <0:16>
off} <0:2048> <0:2048> {qpsk0 | qpsk1}
Example
CASA(config-mod-prof-10)# request atdma qpsk off 64 0 16 338 0 16 fixed
on 1 1536 qpsk0
Casa Systems
short
short
Purpose
The command defines a short data grant used for transmitting shorter upstream data in
DOCSIS 1.0 and 1.1. The interval for a short interval is less than or equal to
maximum-burst-size defined in the short profile.
See the a-long command for a description of the properties. The short modulation
• mtdma
• tdma
Mode
Syntax
short <operation_mode> <modulation_type> {on | off} <1:1024> <0:16>
off} <0:2048> <0:2048> {qpsk0 | qpsk1}
Example
CASA(config-mod-prof-11)# short mtdma qpsk off 64 0 16 338 0 16 fixed
on 1 1536 qpsk0
Casa Systems
station
station
Purpose
The station command defines a station data grant used for transmitting upstream data,
an interval in which CMs are expected to perform some aspect of routine network
maintenance, such as ranging or power adjustment.
See the a-long command for a description of the properties. The station modulation
• atdma
• mtdma
• tdma
Mode
Syntax
station <operation_mode> <modulation_type> {on | off} <1:1024> <0:16>
off} <0:2048> <0:2048> {qpsk0 | qpsk1}
Example
CASA(config-mod-prof-12)# station atdma qpsk off 384 5 34 338 0 48
fixed on 1 1536 qpsk0
Casa Systems
ugs
ugs
Purpose
The ugs command defines an Unsolicited Grant Service (UGS) data grant used for
transmitting upstream data. The UGS algorithm is designed to support real-time
service flows, such as Voice over IP (VoIP), that generate fixed size data packets
periodically. The grant period is negotiated during the initialization process of the
connection. Unsolicited Grant Service with Activity Detection (UGS-AD) also
incorporates activity detection to address UL resource wastage in the UGS algorithm,
which makes it suitable for use with on/off voice codecs.
See the a-long command for a description of the properties. The UGS modulation
• atdma
• mtdma
Mode
Syntax
ugs <operation_mode> <modulation_type> {on | off} <1:1024> <0:16>
off} <0:2048> <0:2048> {qpsk0 | qpsk1}
Example
CASA(config-mod-prof-13)# ugs atdma qpsk off 384 5 34 338 0 48 fixed on
1 1536 qpsk0
Casa Systems
show modulation-profile [<id>] [table]
Shows the modulation profile configuration, including the default first five profiles.
The additional table modifier renders the output in table form. Note that the show run
output omits the default first five profiles and shows no profiles if no additional ones
are defined.
CASA(config)# show modulation-profile

short tdma qpsk off 84 6 75 338 13 16 shortened on
long tdma qpsk off 96 8 220 338 0 16 shortened on
…
CASA(config)# show run | beg modulation-profile
CASA(config)# show modulation-profile 10 table

iuc-type request initial station short long a-short a-long ugs
channel-type atdma atdma atdma - - atdma atdma -
modulation-type qpsk qpsk qpsk - - qpsk qpsk -
diff-encoding off off off - - off off -
preamble-len 64 640 384 - - 104 104 -
FEC-T 0 5 5 - - 12 16 -
FEC-K 16 34 34 - - 75 220 -
scrambler-seed 338 338 338 - - 338 338 -
max-burst-size 0 0 0 - - 6 0 -
guard-time 16 48 48 - - 16 16 -
last-codeword-len fixed fixed fixed - - shortened shortened -
scramble-mode on on on - - on on -
interleaver-depth 1 1 1 - - 1 1 -
interleaver-block 1536 1536 1536 - - 1536 1536 -
preamble-type qpsk0 qpsk0 qpsk0 - - qpsk1 qpsk1 -
interleaver-step - - - - - - - -
spreader - - - - - - - -
subframe-code - - - - - - - -
TCM-encode - - - - - - - -
Casa Systems
show upstream burst-noise
Shows brief burst noise statistics for all logical channels.
CASA(config)# show upstream burst-noise

upstream channel burst noise rate (events/sec)
10/0.0/0 143.0
10/0.0/1 119.7
10/0.1/0 95.2
10/0.1/1 131.1
10/1.0/0 0.0
10/1.0/1 0.0
10/1.1/0 0.0
10/1.1/1 0.0
…
show upstream <x/y.c/z> burst-noise
Shows brief burst noise statistics for a specified logical channel.
CASA(config)# show upstream 10/0.0/0 burst-noise

Burst Noise Stats for Channel 10/0.0/0:
Burst noise event rate: 143.5 events/second.

Percentage of Correctable Burst Events: 98%
Percentage of Uncorrectable Burst Events: 2%
Burst Duration (microseconds) % of Events Max Power (in dB)

----------------------------- ----------- -----------------
0 to 1 0 0
1 to 3 65 0
3 to 10 35 0
10 to 50 0 0
50 to 500 0 0
500 to 2000 0 0
2000 to 10000 0 0
10000 to 50000 0 0
> 50000 0 0
Casa Systems
12-1
Chapter 12. Multicast cable

operations
Multicast cable operation commands description

CASA CMTS software supports DOCSIS 3.x enhanced IP multicast features such as
Source Specific Multicast (SSM), Quality of Service (QoS) support for multicast
traffic, IPv6 multicast, and bonded multicast. These enhanced IP multicast features
enable cable operators to offer various IP multicast-based multimedia services, such
as Internet Protocol Television (IPTV), over the DOCSIS network.
This chapter describes the multicast operations on the cable side. The “Multicast
network operations” chapter in the Casa Systems – NSI Configuration Guide and
Command Reference describes the multicast network operations.
Limited multicast sessions
To conserve bandwidth, it is desirable to minimize multicast replication for IPTV

programs. A modem joining a multicast session that is replicated on a different
channel should be moved to that channel, if that channel is reachable by the modem.
Multicast sessions that desire minimum replication are termed limited multicast
sessions. There are multicast sessions that many clients join. For example, multicast
sessions used to distribute electronic program guide (EPG) information are referred to
as general multicast sessions. General multicast sessions should be replicated to
current channels, and must not trigger downstream channel change (DCC) or
downstream bonding change (DBC) transactions.
You can identify limited multicast sessions by using the application ID, an attribute
that can be configured into a group QoS configuration. It currently has no significance
Casa Systems
to the CMTS. An application policy is a new object that is used to store application
attributes, such as limiting replication for multicast sessions. The procedure for
identifying a limited multicast session is:
1. Configure a multicast group table with matching group-address and QoS ID.
2. Configure the multicast group QoS with a specified application ID.
3. Configure the application policy to limit replication and with the maximum
number of IPTV channels.
For example, to identify multicast session matching group address 230.0.1.0/24 as

limited multicast sessions, define the following configuration:

CASA(conf-grp-config 1) source-address 0.0.0.0/0
CASA(conf-grp-config 1) group-address 230.0.1.0/24
CASA(conf-grp-config 1) end
CASA(config) application policy 1234
CASA(conf-app-policy 1234) limit replication
CASA(conf-app-policy 1234) max iptv channel 2
Table 12-1 lists and briefly describes the objects related to multicast cable operations.
Table 12-1. Multicast cable operation objects
mcast-classifier ds_chan Classifies packets according to both source and destination

(group) addresses.
mcast-service-flow Creates a multicast service flow.
ds_chan
multicast authorization Configures multicast authorization
multicast default Configures a default service class.
grp-service-class-name
multicast group Configures a multicast group and its properties
multicast load-balance Sets the ranging technique for multicast load balancing.
initial-tech
Casa Systems
Multicast cable operations 12-3
Table 12-1. Multicast cable operation objects (continued)
multicast max Sets the maximum percentage threshold for multicast

channel-util streams per channel.
multicast single_said Enables a single security association (SA) identifier (SAID)
to be used for multicast session encryption.
multicast switch over Sets the time to switch over from multicast to unicast.
time
Casa Systems
mcast-classifier ds_chan
Purpose
The mcast-classifier ds_chan command classifies packets according to source and

destination (group) addresses. Multicast group classifiers must be configured to
enable forwarding of both clear and encrypted multicast IPTV streams.
Mode
(config)#
Syntax
mcast-classifier ds_chan <slot>/<port>/<chan> cl_id <1:4092> sf_id
<1:4092> [dst-ip <ip_addr> <mask> | pri <0:24> | protocol
<0:257> | src-ip <ip_addr> <mask> | tos <0:255> <0:255> <0:255>
no mcast-classifier ds_chan <slot>/<port>/<chan> cl_id <1:4092>
Properties
<slot>/<port>/<chan> Downstream channel ID, in the form slot/port/

channel.
cl_id <1:4092> Classification ID.
sf_id <1:4092> Service flow ID.
dst-ip <ip_addr> <mask> Optional destination IP address and mask, which can
be followed by the protocol or tos value.
Example:
CASA(config)# mcast-classifier ds_chan

2/0/0 cl_id 1 sf_id 1 dst-ip
192.168.8.8 255.255.255.0
Casa Systems
pri <0:24> Optional priority of the classifier, which can be

followed by the src-ip, dst-ip, protocol, or tos value.
Example:

2/0/0 cl_id 1 sf_id 1 priority 24
protocol <0:257> Optional IP protocol number, 256 for all protocols and
257 for TCP/UDP, which can be followed by the tos
value.
Example:

2/0/0 cl_id 1 sf_id 1 protocol 256
src-ip <ip_addr> <mask> Optional source IP address and mask values, which
can be followed by the dst-ip, protocol, or tos value.
Example:

2/0/0 cl_id 1 sf_id 1 src-ip
192.168.7.7 255.255.255.0
tos <0:255> <0:255> <0:255> Optional type of service (ToS), with the low, high, and
mask values, indicated at the end of the command.
Multicast group classifiers must be configured to
enable forwarding of both clear and encrypted
multicast IPTV streams.
Example:

2/0/0 cl_id 1 sf_id 1 tos 2 4 255
Casa Systems
mcast-service-flow ds_chan
Purpose
A multicast service flow is a specific type of flow where the packets comprising the
flow require particular treatment by the network forwarding devices along the path to
the packet’s destination.
Mode
(config)#
Syntax
mcast-service-flow ds_chan <slot>/<port>/<chan> sf_id <1:4092> dsid
<1:4092> pri <0:7> gu_rate <Bps> gu_buf_sz <bytes> mx_rate <Bps>
mx_buf_sz <bytes> [default]
no mcast-service-flow ds_chan <slot>/<port>/<chan> sf_id <1:4092>
Properties
<slot>/<port>/<chan> Downstream channel ID, in the form slot/port/

channel.
sf_id <1:4092> Service flow ID.
Example:
CASA(config)# mcast-service-flow
ds_chan 2/0/0 sf_id 1
CASA(config)# no mcast-service-flow
ds_chan 2/0/0 sf_id 1
dsid <1:4092> ID for multicast packets of the downstream service

flow.
Example:
ds_chan 2/0/0 sf_id 1 dsid 1
Casa Systems
pri <0:7> Priority of the packets of the service flow.
Example:
ds_chan 2/0/0 sf_id 1 dsid 1 pri 7
gu_rate <Bps> Guaranteed rate of the service flow, in bytes per

second.
Example:
gu_rate 24
gu_buf_sz <bytes> Guaranteed buffer size, in bytes.
Example:
gu_rate 24 gu_buf_sz 8
mx_rate <Bps> Maximum rate of the service flow, in bytes per

second.
Example:
gu_rate 24 gu_buf_sz 8 mx_rate 32
mx_buf_sz <bytes> Maximum buffer size, in bytes.
Example:
mx_buf_sz 64
Casa Systems
default Optional default service flow.
Example:
mx_buf_sz 64 default
show multicast service-flow [module <id>]
Shows the multicast service flow configuration.
CASA(config)# show multicast service-flow

Module SFID Chan(s) KBitrate Stats (PktSent, ByteSent, PktDrop
ByteDrop)
qam 0 1 0/0/0 0 0, 0, 0, 0
2 0/0/0 0 0, 0, 0, 0
3 0/0/1 0 0, 0, 0, 0
4 0/0/1 0 0, 0, 0, 0
5 0/0/1 0 0, 0, 0, 0
6 0/0/2 136 154050, 10475400, 0, 0
7 0/0/2 0 0, 0, 0, 0
8 0/0/2 136 154046, 10475128, 0, 0
9 0/0/0 0 0, 0, 0, 0
10 0/0/1 0 0, 0, 0, 0
Casa Systems
multicast authorization
Purpose
The multicast authorization command configures authorization for multicast

operations. It tells the CCAP which CMs are authorized to join multicasts and how
many groups a given CM can join by way of matching profiles.
Modes
(config)#
(conf-auth-file <name>)#
Syntax
(config)#
multicast authorization default-action {deny | permit}
[no] multicast authorization enable
[no] multicast authorization match-profile <name>
multicast authorization max-session-num <0:65535>
[no] multicast authorization profile <name>

(conf-auth-file x)#
[no] desc “<text>”
session-rule <1:4294967295> {accept | deny} {<src_v4_addr>/<mask>
<grp_v4_addr>/<mask> | ipv6 <src_v6_addr>/<prefix>
<grp_v6_addr>/<prefix>} priority <0:255> [vrf <id>]
no session-rule <1:4294967295>
Properties
default-action {deny | Changes the default behavior of a multicast join

permit} request to deny or permit.
Example:
CASA(config)# multicast authorization

default-action permit
Casa Systems
enable Enables multicast authorization globally.
Example:

enable
CASA(config)#
no multicast authorization enable
match-profile <name> Assigns a profile <name> to multicast authorization,

up to eight. When IP multicast authorization is
enforced, provides the default set of multicast
authorization profiles the CMTS enforces for a CM if
it did not signal a set of profiles during the registration
process. Use the command again for each profile.
Example:

match-profile MYPROF
CASA(config)# no multicast
authorization match-profile MYPROF
max-session-num <0:65535> Restricts the number of join requests accepted from

each CM. If set to 0, the maximum number of
sessions is not limited by the CMTS.
Example:

max-session-num MYPROF
profile <name> Configures a multicast authorization profile, with a

name up to 15 characters.
Example:

profile MYPROF
CASA(conf-auth-file MYPROF)# exit
CASA(config)# no multicast
authorization profile MYPROF
Casa Systems
desc “<text>” Description of the authorization profile, a quoted

string up to 32 characters.
Example:
CASA(conf-auth-file MYPROF)# desc “My

Multicast Profile”
CASA(conf-auth-file MYPROF)# no desc
Casa Systems
session-rule Sets an authorization profile session rule (up to 512

<1:4294967295> {accept | per profile) with a rule ID and one of the following
deny} {<src_v4_addr>/ properties:
<mask> <grp_v4_addr>/
<mask> | ipv6 • accept or deny — Indicates whether the rule per-
<src_v6_addr>/<prefix> mits a matching multicast join request to be
<grp_v6_addr>/<prefix>} accepted or denied. If no rules match the multi-
priority <0:255> [vrf cast join request, the request will take the
<id>] default-action {deny | permit}.
• <src_v4_addr>/<mask> — Source IPv4 address
and mask to indicate a range of source
addresses, in the form A.B.C.D/M. If a mask
length of zero is set for the source address,
requests with any source address match this rule.
• <grp_v4_addr>/<mask> — Multicast group IPv4
address and mask to indicate a range of multicast
group addresses, in the form A.B.C.D/M.
• ipv6 <src_v6_addr>/<mask> <grp_v6_addr>/
<mask> — Alternative IPv6 source and group
address ranges. If a mask length of zero is set for
the source address, requests with any source
address match this rule.
• priority <0:255> — Priority number. If more than
one session rule matches a joined session, the
session rule with the highest rule priority (the low-
est number) determines the authorization action.
• vrf <id> — Optional Virtual Routing and Forward-
ing (VRF) identifier.
Example:
CASA(conf-auth-file MYPROF)#
session-rule 1234 accept 192.168.6.6/24
224.168.5.5/24 priority 1
max number of rules has been
configured: 512
CASA(conf-auth-file MYPROF)#
no session-rule 1234
Casa Systems
show multicast authorization profile
Shows the multicast authorization profile configuration with the session rule.
CASA(config)# show multicast authorization profile

multicast authorization profile MYPROF
desc MYPROF
session-rule 1234 accept ipv6 111:111::111/32 111:111::112/32
priority 255
show multicast client [group-address <addr>]
Shows the multicast client sessions, with the optional group address filter.
CASA(config)# show multicast client

Multicast Session
CM Mac Chan(s) MD DCS MDF Proto UpTime /Expiry Client MAC / IP
show multicast client [vrf <name>] summary [docsis-mac <id>]
Shows summary statistics for multicast clients.
CASA(config)# show multicast client summary

MD Static/Dynamic Last Reporter Multicast Session
1 0 /2 10.94.0.180 <226.94.2.0, 0.0.0.0>
1 0 /2 10.94.0.180 <226.94.2.1, 0.0.0.0>
…
MD New Joins Active Groups Total Reports Rate/Min

5 4/4 0/3 31/11 0/4
8 3/0 0/0 26/0 0/0
show igmp client-db [<v4_addr>]
Shows the multicast IGMP client database entries, optionally for a specific IPv4
address. There can be up to 192K multicast IGMP clients.
CASA(config)# show igmp client-db 229.0.99.1

VRF Group/Source Vif Module Pri State
0 229.0.99.1/0.0.0.0 0 qam 11 0 n/a
Total entries : 1
Casa Systems
multicast default grp-service-class-name
multicast default grp-service-class-name

Purpose
The multicast default grp-service-class-name command configures a default service

class, which is used if a join request does not match any of the multicast group
configuration table entries. If a default service class is not configured, the request will
be denied.
Mode
(config)#
Syntax
multicast default grp-service-class-name <name>
no multicast default grp-service-class-name
Properties
<name> Identifies the cable service-class name <name>, up

to 15 characters.
Example:
CASA(conf)# multicast default

grp-service-class-name DGSC1
CASA(conf)# no multicast default
grp-service-class-name
Casa Systems
multicast group
multicast group
Purpose
The multicast group command configures a multicast group and its properties.
Dynamic IPTV sessions are allowed only if there is a matching classifier defined for
the group. In the multicast group configuration, specify the group-address prefix to
match the supported multicast session. This is required to enable forwarding of both
clear and encrypted multicast IPTV streams. If not matched, IGMP join/leave packets
are dropped. The additional encryption-id parameter is necessary for encryption to be
applied to a matching multicast session. If not specified, traffic is forwarded clear.
Modes
(config)#
(conf-grp-config <id>)#
Syntax
(config)#
[no] multicast group config <1:4294967295>
(conf-grp-config x)#
encryption-id <0:65535>
group-address {<ip_addr>/<mask> | ipv6 <v6_addr>/<prefix>}
phs-id <0:65535>
priority <0:255>
qos-id <0:65535>
source-address {<ip_addr>/<mask> | ipv6 <v6_addr>/<prefix>}
tos-high <0:255>
tos-low <0:255>
tos-mask <0:255>
vrf <id>
(config)#
multicast group encryption <1:65535> algorithm {aes128 | cmts | des40 |
des56}
no multicast group encryption <1:65535>
multicast group qos <1:65535> <class_name> {aggregate max-sess
<1:65535> | single} [app-id <1:32>}
no multicast group qos <1:65535>
Casa Systems
multicast group
Properties
config <1:4294967295> Configures a multicast group configuration table, with

an ID. The minimum configuration is to set the
source-address and group-address parameters.
Example:

CASA(conf-grp-config 1)# exit
CASA(config)#
no multicast group config 1
encryption-id <0:65535> Multicast encryption ID, if encryption is required. To

enable forwarding of both clear and encrypted
multicast IPTV streams, a multicast group classifier
must be set to match the supported multicast session
in the group-address property.
Example:
CASA(conf-grp-config 1)# encryption-id

1
group-address Range of multicast group IP addresses. The mask/

{<ip_addr>/<mask> | ipv6 prefix value is 0–32 for IPv4, and 1–128 for IPv6.
<v6_addr>/<prefix>}
Example:
CASA(conf-grp-config 1)# group-address

192.168.8.8/24
phs-id <0:65535> Payload header suppression (PHS) identifier. PHS

reduces redundant packet header information during
the multicast session. Any suppression information is
re-inserted at the destination.
Example:
CASA(conf-grp-config 1)# phs-id 1
Casa Systems
multicast group
priority <0:255> Priority of the entry when a newly replicated multicast

session matches multiple entries. Higher values
indicate a higher priority.
Example:
CASA(conf-grp-config 1)# priority 1
qos-id <0:65535> Identifies the qos instance for configuring the QoS for
the replications of the sessions matching this GC, if
QoS treatment is required. The value 0 indicates that
QoS is allocated based on the default SCN for all
replications derived from this group configuration.
Example:
CASA(conf-grp-config 1)# qos-id 1
source-address Range of source IP addresses. The mask/prefix

{<ip_addr>/<mask> | ipv6 value is 0 for ASM-based sessions, 0–32 for IPv4,
<v6_addr>/<prefix>} and 1–128 for IPv6.
Example:
CASA(conf-grp-config 1)# source-address

192.168.8.8/24
tos-high <0:255> High value of a range of the type of service (ToS)

byte value to be defined in a packet classifier.
Multicast group classifiers must be configured in the
group-address prefix to enable forwarding of both
clear and encrypted multicast IPTV streams.
Example:
CASA(conf-grp-config 1)# tos-high 100
Casa Systems
multicast group
tos-low <0:255> Low value of a range of the type of service (ToS) byte
value to be defined in a packet classifier.
Example:
CASA(conf-grp-config 1)# tos-low 1
tos-mask <0:255> Mask value bitwise and with a type of service (ToS)
byte value to be defined in a packet classifier.
Example:
CASA(conf-grp-config 1)# tos-mask 255
vrf <id> Virtual Routing and Forwarding (VRF) identifier, with

global the default.
Example:
CASA(conf-grp-config 1)# vrf VPN1
encryption <1:65535> Configures multicast group encryption, with an

algorithm {aes128 | cmts | instance ID and an algorithm setting to identify which
des40 | des56} encryption algorithm should be used for a security
association (SA) referenced by this object (AES-128,
CMTS, DES-40, or DES-56; cmts indicates that the
CMTS should select the algorithm, which is DES-56
by default). Encryption is not required, but multicast
group classifiers must be configured to enable
forwarding of both clear and encrypted multicast
IPTV streams.
Example:
CASA(conf)# multicast group encryption

1 algorithm cmts
CASA(conf)#
no multicast group encryption 1
Casa Systems
multicast group
qos <1:65535> <class_name> Configures the multicast group quality of service

{aggregate max-sess (QoS), with the following properties:
<1:65535> | single} [app-id
<1:32>} • <id> — Service ID.
• <class_name> — The
cable service-class name <name> reference for
the set of QoS parameters for this GQC object,
up to 15 characters.
• aggregate — Combines all sessions with match-
ing criteria into the same GCR, and only one ser-
vice flow is used for all sessions and the
max-sess number will determine the maximum
number of sessions that will be allowed to use the
service flow.
• single — Creates a unique GCR and GSF for the
session. If the multicast group QoS is configured
to be single, a new downstream service flow is
used for each session.
• max-sess <num> — Maximum number of ses-
sions that can be aggregated in an aggregated
service flow. This value is ignored in case of a
CGR with QosCtrl set to single.
• app-id <id> — Optional application ID to enable
special features for QoS admission control or
other policies. The behavior and usage of the
application identifier is vendor-specific.
Example:
CASA(conf)# multicast group qos 13

SRVCL1 single app-id 1
CASA(conf)# no multicast group qos 13
Casa Systems
show multicast group config [<id>]
Shows the multicast group configuration.
CASA(config)# show multicast group config

source-address 192.168.8.8/24
group-address 192.168.7.7/24
tos-low 255
tos-high 255
tos-mask 255
qos-id 124
encryption-id 1
phs-id 1
priority 255
show multicast group encryption
show multicast group qos
show multicast group-address <ip_addr> client
show multicast replication [module <0:13>]
Shows the multicast replication for each session, with the optional QAM module
specified.

Multicast Session
<226.94.0.0::0.0.0.0>
qam 0 2 n/a 2 DEF 0/0/0
qam 0 1 n/a 1 IPTV 0/0/0
show multicast vrf <name> client [group-address <ip_addr>]
show cable modem <mac_addr> multicast-session

CASA(config)# show cable modem e448.c7b4.aad2 multicast-session
VRF Ver UpTime /Expiry CPE MAC /IP Multicast Session
Casa Systems
multicast load-balance initial-tech

Purpose
The multicast load-balance initial-tech command sets the initial ranging technique
for load balancing. For details on load balancing, see Chapter 10, “Load balancing.”
Mode
(config)#
Syntax
multicast load-balance initial-tech broadcast-ranging
multicast load-balance initial-tech direct
multicast load-balance initial-tech period-ranging
multicast load-balance initial-tech reinitialize-mac
multicast load-balance initial-tech unicast-ranging
Properties
broadcast-ranging Enables the CM to broadcast the full initial ranging

request without going off line and performing
re-registration with the CMTS.
Example:
CASA(config)# multicast load-balance

direct Initial technique default setting. The CM moves

directly to another channel without performing any
type of ranging.
Example:

initial-tech direct frequency-limit 60
Casa Systems
period-ranging Enables the CM to move to a new channel, but

performs periodic ranging requests for an improved
channel opportunity.
Example:

initial-tech period-ranging
reinitialize-mac Enables resetting the CM MAC address, forcing the

cable model off line and re-registering with the CMTS
on the new channel.
Example:

initial-tech reinitialize-mac
unicast-ranging Enables the CM to perform an initial ranging request

for a dedicated channel from the CMTS where there
is no other transmission activity.
Example:

initial-tech unicast-ranging
Casa Systems
multicast max channel-util
multicast max channel-util

Purpose
The multicast max channel-util command sets the maximum percentage threshold
for multicast streams per channel. Once the channel reaches the configured threshold,
no further multicast sessions are allowed on that channel. If the threshold percentage
is too low, bandwidth may be wasted (unusable for multicast), or the channel will be
used entirely for unicast traffic. If the threshold percentage is too high, the channel
may become congested with multicast traffic. Casa recommends that you monitor the
default configuration setting of 60 and then tune the value for best performance.
Mode
(config)#
Syntax
multicast max channel-util <1:100>
Properties
<1:100> Maximum percentage threshold for multicast streams

per channel, default 60.
Example:
CASA(config)# multicast max

channel-util 60
Casa Systems
multicast single_said
multicast single_said
Purpose
The multicast single_said command enables a single security association (SA)

identifier (SAID) to be used for multicast session encryption during multicast traffic
forwarding on bonded CMs. The default setting is disabled, where each multicast
replication is assigned a different SAID to help prevent CMs from receiving duplicate
traffic. When enabled, a single SAID is assigned to all multicast replications.
Mode
(config)#
Syntax
[no] multicast single_said
multicast-dsid-forward
Enables multicast Downstream Service Identifier (DSID) forwarding that allows CMs
to filter multicast traffic before forwarding the traffic to CPE devices. (See the
DOCSIS MAC multicast-dsd-forward property for details.)

CASA(conf-if-mac 1)# multicast-dsid-forward wb-cm-only
no mgmd ipv4 shutdown
Enables the Multicast Group Membership Discovery (MGMD) protocol on a DOCSIS

MAC domain interface. (See the DOCSIS MAC mgmd property for details.)

CASA(conf-if-mac 1)# no mgmd ipv4 shutdown
Casa Systems
interface vlan
rate-limit multicast
Performs a rate limit on the multicast upstream for the VLAN, in maximum number of
packets permitted per second (default no limit).
CASA(config)# interface vlan 244

CASA(conf-if-vlan 244)# rate-limit multicast 256
show multicast running-config
Shows the multicast running configuration.
CASA(config)# show multicast running-config

!
!multicast
!
multicast authorization profile MYPROF
desc THIS IS IT...
session-rule 1234 accept ipv6 111:111::111/32 111:111::112/32
priority 255

source-address 192.168.8.8/24
group-address 192.168.7.7/24
tos-low 255
tos-high 255
tos-mask 255
qos-id 124
encryption-id 1
phs-id 1
priority 255
multicast load-balance initial-tech direct

!
Casa Systems
multicast switch over time
multicast switch over time

Purpose
The multicast switch over time command sets the time to switch over from multicast
to unicast and determines how long the CCAP forwards multicast streams to CMs
before changing them to multiple unicast streams. See also the
load-balance execution-rule permit multicast-session modem move property.
Mode
(config)#
Syntax
[no] multicast switch over time <100:10000>
Properties
<100:10000> Switchover time from multicast to unicast, in tenths of

a second, with no switchover by default.
Example:
CASA(config)# multicast switch over

time 100
CASA(config)#
no multicast switch over time
Casa Systems
13-1
Chapter 13. NetFlow Monitoring
NetFlow monitoring commands description

NetFlow provides the ability to collect IP network traffic as it enters or exits an
interface. By analyzing the data provided by NetFlow, a network administrator can
determine such things as the source and destination of traffic, class of service, and the
causes of congestion. A network flow is a unidirectional stream of packets identified
as the combination of factors. Any one of the following factors being different defines
the flow as unique:
• Source IP address
• Destination IP address
• IP protocol
• Source port number
• Destination port number
• Type of service (ToS)
• Ingress interface (SNMP IfIndex).
The Casa NetFlow implementation is based on NetFlow version 9, described in RFCs

7011 and 7012. Version 9 is template-based and complies with IPv6 as well as IPv4
addressing. NetFlow information collection is turned on and off on individual IP
bundle interfaces only. One sampler MAP and one exporter map are supported per
CMTS, with one data template each for IPv4 and IPv6. Each line card is both an
observation domain and an export device. Only UDP transport is supported.
NetFlow depends on a sampling rate. The Casa minimum sampling rate is defined as
one packet out of one thousand packets.
Casa Systems
NetFlow monitoring commands description
Table 13-1 lists and briefly describes the objects related to NetFlow monitoring.
Table 13-1. NetFlow monitoring objects
flow exporter-map Configures the exporter map.

flow monitor-map Configures the monitor map.
flow sampler-map Configures the sampler map.
Casa Systems
NetFlow Monitoring 13-3
flow exporter-map
flow exporter-map
Purpose
The flow exporter-map command configures an exporter map and its parameters.
Only one exporter map by name is supported initially.
Mode
(config)#
(config-ipfix exporter <n>)#
Syntax
(config)# [no] flow exporter-map <name>
(config-ipfix exporter <n>)#
destination <ip>
options {interface-table | sampler-table} timeout <120:3600>
source loopback <0:255>
template {data | options} timeout <120:3600>
transport udp {dst-port | src-port} <1024:65535>
Properties
<name> Exporter name to associate with the exporter map.
Example:
CASA(config)# flow exporter-map EXMAP1

CASA(config-ipfix exporter EXMAP1)# end
CASA(config)#
no flow exporter-map EXMAP1
destination <ip> Destination IP address of the export packets, as IPv4

or IPv6.
Example:

CASA(config-ipfix exporter EXMAP1)#
destination 192.168.8.8
Casa Systems
flow exporter-map
options {interface-table Timeout interval for interface table data or sampler

| sampler-table} timeout table data, in seconds, default 300.
<120:3600>
Example:

options interface-table timeout 300
source loopback <0:255> Loopback interface ID for the source address.
Example:

source loopback 0
template {data | Template data or options timeout, in seconds, default

options} timeout 300. There can be one data template for each of IPv4
<120:3600> and IPv6.
Example:

template data timeout 300
transport udp {dst-port Transport UDP port for destination or source.
| src-port} <1024:65535>
Example:

transport dst-port 2025
transport src-port 1025
Casa Systems
flow exporter-map
show flow exporter-map [<name>]
Shows the flow exporter map configuration.
CASA(config)# show flow exporter-map

flow exporter-map EXMAP1
options interface-table timeout 300
options sampler-table timeout 300
template data timeout 300
template options timeout 300
transport udp dst-port 2025
transport udp src-port 1025
destination 192.168.8.8
source loopback 0
index id 0
…
show flow exporter stat
Shows the flow exporter counts per module.
UPS 9/ 9: nobuf 0
UPS 12/12: nobuf 0
QAM 1/ 5: nobuf 0
QAM 5/ 5: nobuf 0
QAM 10/10: nobuf 0
TTL 0/ 0: nobuf 0
Casa Systems
flow monitor-map
flow monitor-map
Purpose
The flow monitor-map command configures a flow monitor map and its parameters.
Each monitor has a data cache. An export packet is generated when the cache is full or
the cache timeout is reached.
Mode
(config)#
(config-ipfix monitor <n>)#
Syntax
(config)# flow monitor-map <name>
(config-ipfix monitor <n>)#
cache timeout update <120:3600>
exporter <name>
record {dual | ipv4 | ipv6}
Properties
<name> Monitor name to associate with the monitor map.
Example:
CASA(config)# flow monitor-map MONMAP1

CASA(config-ipfix monitor MONMAP1)# end
CASA(config)#
no flow monitor-map MONMAP1
cache timeout update Cached record timeout update interval, in seconds.

<120:3600>
Example:

CASA(config-ipfix monitor MONMAP1)#
cached timeout update 300
Casa Systems
flow monitor-map
exporter <name> Exporter name of the monitor.
Example:

exporter EXNAME1
record {dual | ipv4 | IP protocol of the traffic for monitoring: dual stack,
ipv6} IPv4, or IPv6.
Example:

record ipv4
Related commands
interface ip-bundle <id>

flow egress monitor <name> sampler <name>
flow ingress monitor <name> sampler <name>
Instantiates NetFlow egress and ingress monitors for the IP bundle interface.
CASA(config)# interface ip-bundle 16

CASA(ip-bundle 16)# flow egress monitor MONMAP1 sampler SAMP1
CASA(ip-bundle 16)# flow ingress monitor MONMAP1 sampler SAMP1
show flow monitor-map [<name>]

CASA(config)# show flow exporter-map
flow monitor-map MONMAP1
record ipv4
exporter EXNAME1
cache timeout update 300
Casa Systems
flow sampler-map
flow sampler-map
Purpose
The flow sampler-map command configures a flow sampler map and its parameters.
Only one sampler map by name is supported initially. The minimum sampler rate is
one out of a thousand packets.
Mode
(config)#
(config-ipfix sampler <n>)#
Syntax
(config)# flow sampler-map <name>
(config-ipfix sampler <n>)#
random 1-out-of <1000:10000>
Properties
<name> Sampler name to associate with the sampler map.
Example:
CASA(config)# flow sampler SAMP1

CASA(config-ipfix sampler SAMP1)# end
CASA(config)#
no flow sampler-map SAMP1
random 1-out-of Random sampler rate, default one out of 1024

<1000:10000> packets.
Example:
CASA(config)# flow sampler SAMP1

CASA(config-ipfix sampler SAMP1)#
random 1-out-of 1024
Casa Systems
flow sampler-map
show flow sampler-map [<name>]
Shows the flow exporter map configuration. A source loopback ID of -1 indicates that
it is not defined.
CASA(config)# show flow sampler-map

flow sampler-map SAMP1
random 1-out-of 1024
Casa Systems
14-1
Chapter 14. Orthogonal Frequency

Division Multiplexing
OFDM description
Orthogonal Frequency Division Multiplexing (OFDM) is a data transmission method
where a large number of closely spaced or overlapping very-narrow-bandwidth
orthogonal (mutually exclusive) QAM signals are transmitted in a given channel.
OFDM provides the downstream function, while Orthogonal Frequency Division
Multiplexing Multiple Access (OFDMA) provides the upstream function. The feature
is available for the QAM 8x192 module and UPS 16x8 line card on the C100G and
C40G platforms and is based on the following DOCSIS 3.1 standards:
• http://www.cablelabs.com/wp-content/uploads/specdocs/
CM-SP-CCAP-OSSIv3.1-I01-140808.pdf
• http://www.cablelabs.com/wp-content/uploads/specdocs/
CM-SP-PHYv3.1-I01-131029.pdf
Each of the QAM signals, called a subcarrier, carries a small percentage of the total
payload at a very low data rate. In OFDM, the subcarrier frequencies are chosen so
that the subcarriers are orthogonal to each other, meaning that crosstalk between the
subchannels is eliminated and intercarrier guard bands are not required. This greatly
simplifies the design of both the transmitter and the receiver. In conventional FDM, a
separate filter for each subchannel is required.
OFDMA handles the upstream function for DOCSIS 3.1. For details on OFDMA, see
Chapter 15, “Orthogonal Frequency Division Multiple Access.”
Casa Systems
Definitions
Table 14-1 lists and briefly describes the objects related to OFDM.
Table 14-1. OFDM objects
ofdm Sets the OFDM downstream frequency exclusion band or

profile.
interface qam Sets the OFDM parameters for a QAM slot, port, and
channel, and for any port exclusion band.
interface docsis-mac Sets the OFDM downstream binding for the DOCSIS MAC
interface.
module <slot> Sets the number of OFDM channels per slot, 1 or 2.
ofdm-channels
service group Sets the service group for the OFDM downstream binding.
Definitions
channel configuration — Defines the downstream OFDM channel table. OFDM

channels carry only DOCSIS traffic and cannot be used to carry EQAM video traffic.
Two modes of operation are defined for the downstream: 4K Fast-Fourier Transform
(FFT) and 8K FFT modes for a sampling rate of 204.8 MHz. The downstream OFDM
channel bandwidth can be any value in the range 24–192 MHz. However, an OFDM
channel must have a contiguous region that is at least 22 MHz wide and cannot have
the width of total active subcarriers exceed 190 MHz. Smaller bandwidths than
192 MHz are achieved by nulling subcarriers prior to the Inverse Discrete Fourier
Transform (IDFT), part of the family of mathematical methods known as Fourier
analysis, which defines the “decomposition” of signals into sinusoids. IDFT defines
the transformation from the frequency to the time domain, that is, by adjusting the
equivalent number of active subcarriers while maintaining the same subcarrier
spacing of 25 or 50 KHz. The CCAP can optionally be configured for up to 16 distinct
data profiles and one Next Codeword Pointer (NCP) profile. If automatic profile
configuration is supported by the vendor and enabled, then automatic configuration of
the profiles occurs. If automatic profile configuration is not supported or disabled, the
CCAP must reject the configuration if the NCP modulation is not set, or if profile 0
(a.k.a. profile A) is not configured.
Casa Systems
Orthogonal Frequency Division Multiplexing 14-3
Definitions
cyclic prefix — Enables the receiver to overcome the effects of inter-symbol and
intercarrier interference caused by micro-reflections in the channel. There are five
possible values and the choice depends on the delay spread of the channel. A longer
delay spread requires a longer cyclic prefix.
interleave — Number of samples for the OFDM downstream channel, with a

maximum of 32 samples for 4K FFT and 16 samples for 8K FFT. The default is one
sample. An interleaver rearranges or mixes data to be transmitted such that the
original bits, bytes, or symbols are no longer adjacent, providing improved resistance
to various forms of interference, especially burst or impulse noise.
lower-freq — Defines the lowest active subcarrier frequency, range 108–1196 MHz.
upper-freq — Defines the highest active subcarrier frequency, range 130–1218 MHz.
modulation type — Defines the modulation type supported by the CM demodulator, in

the range 16QAM–4096QAM for OFDM, and includes Quadrature Phase Shift
Keying (QPSK) or zero.
next codeword pointer (NCP) —A codeword is a forward error correction (FEC) data
block, comprising a combination of information bytes and parity bytes. The NCP
identifies the physical (PHY) parameters communicated from the CMTS to CMs.
NCP points to the beginning of codewords in a symbol, counting only data
subcarriers. Each FEC-encoded NCP is 48 bits wide. NCPs may be modulated using
QPSK, 16-QAM or 64-QAM, and this modulation is signaled by the physical link
channel (PLC). In addition to the NCPs carrying next codeword pointers, there is also
an NCP carrying the cyclic redundancy check (CRC) for all the NCPs of the symbol.
For 8K FFT mode, there will be NCPs in each symbol. For 4K FFT mode, there will
be one set of NCPs per pair of symbols.
NCP modulation — Defines the modulation of all subcarriers in the NCP channel. If
omitted, the modulation is automatically configured by the CCAP. The NCP profile is
assigned profile ID 255. NCPs may be modulated using QPSK, 16-QAM or 64-QAM
and this modulation is signaled by the physical link channel (PLC).
pilot — A dedicated OFDM subcarrier that can be used for channel estimation
(measurement of channel condition), synchronization, and other purposes. Pilot
subcarriers do not carry data. There are three types of pilots: continuous, scattered,
and complementary. Continuous pilots occur at the same frequency location in every
Casa Systems
Definitions
OFDM symbol and are used for frequency and phase synchronization. Scattered pilots
occur at different frequency locations in different symbols and are used for channel
estimation. Complementary pilots are at a lower modulation order, allow phase
tracking along the time axis for frequency offset and phase noise correction, and are
used by the CMTS upstream receiver to enhance signal processing. A set of pilot
patterns is defined from which the CMTS or operator can select to match the
frequency response of the network. The pilot-scale-factor indicates the scale factor for
calculating the number of continuous pilots for a downstream channel.
plc-freq — The PHY link channel (PLC) frequency, the center frequency of the lowest
subcarrier of the 6 MHz encompassed spectrum containing the PLC at its center. The
frequency of this subcarrier is required to be located on a 1-MHz grid and outside any
defined exclusion zone. The aim of the PLC is to convey to the CM the physical
properties of the OFDM channel.
rolloff — The rolloff period or windowing maximizes channel capacity by sharpening

the edges of the frequency spectrum of the OFDM signal. For windowing purposes,
another segment at the start of the Inverse Discrete Fourier Transform (IDFT) output
is appended to the end of the IDFT output, the rolloff postfix (RP). There are five
possible values for the RP, and the choice depends on the bandwidth of the channel
and the number of exclusion bands within the channel. A larger RP provides sharper
edges in OFDM signal spectrum; however, there is a time vs. frequency trade-off.
Larger RP values reduce the efficiency of transmission in the time domain, but
because the spectral edges are sharper, more useful subcarriers appear in the
frequency domain. There is an optimum value for the RP that maximizes capacity for
a given bandwidth and/or exclusion band scenario.
subcarrier — The OFDM downstream multicarrier systems are composed of a large

number of subcarriers that have either 25 or 50 KHz spacing. These subcarriers are
grouped into independently configurable OFDM channels, each occupying a spectrum
of up to 192 MHz in the downstream, totaling 7680 25-KHz subcarriers or
3840 50-KHz subcarriers, of which up to 7601 (25-KHz) or 3801 (50-KHz) active
subcarriers span 190 MHz. Many parameters of these channels can be independently
configured, thereby optimizing configuration based on channel conditions. A
subcarrier group is a collection of consecutive subcarriers.
subcarrier exclusion — Excludes all subcarriers that can be referenced by any

downstream RF port. Muted subcarriers have a value of zero in the bit-loading pattern
of a profile. An exclusion subcarrier group is a collection of exclusion subcarriers.
Casa Systems
OFDM configuration steps
subcarrier spacing — Defines the KHz spacing associated with a particular FFT
mode configured on the OFDM downstream channel. If it is 4K mode, the subcarrier
spacing is 50 KHz (the default). If it is 8K mode, the subcarrier spacing is 25 KHz.
up-down-trap-enable — Indicates if a trap should be sent when the channel transitions

from up to down and from down to up.
OFDM configuration steps
The steps to configuring downstream OFDM are the following (see also the “OFDM
configuration examples” section):
1. Enable DOCSIS 3.1 by using the cable docsis version 31 command in

configuration mode.
2. Configure the number of channels per port using the
module <slot> ofdm-channels <0:1> command. (Note that the command is not
required by default for one OFDM channel or 64 single-carrier channels.)
3. Configure a modulation profile <1:64>, with frequency modulation defined.
4. Add subcarrier groups to the profiles, with contiguous and discreet stop and start
frequency ranges and defined frequency modulations.
5. Define skip modulations for subcarriers that need to be skipped.
6. Define exclusion zones for one or more subcarriers using a profile
exclusion-band <1:16> configuration.
7. Configure the interface qam channels for at least a lower frequency, as follows
(be sure the channel is shut down first):
• lower-freq — The lowest active frequency in the spectrum. The range is
108000000–1196000000 Hz.
• upper-freq — The uppermost frequency in the spectrum. The range is
130000000–1218000000 Hz.
• plc-freq — The center PHY Link Channel (PLC) frequency of the lowest
subcarrier in the range. The range is 108000000–1212000000 Hz and the
frequency must be on a 1-MHz grid and outside any defined exclusion zone,
otherwise the configuration is rejected with an error message. If the PLC
frequency is omitted, an algorithm automatically calculates it in an
appropriate place outside any exclusion zone.
Casa Systems
QAM 8x192 support of shared channels
8. Configure any exclusion zones on the QAM port level using a QAM interface
ofdm port-exclusion-band <1:16> configuration.
9. Configure the interface docsis-mac for the OFDM downstream binding.
10. Configure the service group for the OFDM downstream binding.
11. Save the configuration by using the copy run start command.
12. Perform a system reboot to load the configuration to the active and standby SMM
modules.
QAM 8x192 support of shared channels
The QAM 8x192 line card can support 192 shared (broadcast) channels if two OFDM
channels are used per port. With one OFDM channel per port, 128 broadcast channels
are supported. The following is a review:
• QAM 8x192 supports eight ports per slot, 32 channels per port, and up to 192
shared channels. Hence:
• One OFDM channel per port provides up to 64 single-carrier channels and 128
shared channels. The maximum number of narrowcast channels per port is 80
(64 + 128/8).
• Two OFDM channels per port provides up to 32 single-carrier channels and 192
shared channels. The maximum number of narrowcast channels per port is 56
(32 + 192/8).
Note: A module changeover from one OFDM channel to two channels, and vice
versa, requires a module reboot. For example:
CASA(config)# module
CASA(config)# module 1 ofdm-channels 2
Need to reboot module 1 to apply the change.
CASA(config)# end
CASA# reboot module 1
Casa Systems
ofdm
ofdm
Purpose
The ofdm command sets two Orthogonal Frequency Division Multiplexing (OFDM)
downstream parameters: a frequency exclusion band and a profile.
Modes
(config)#
(conf-ofdm-exclusion-band <1:16>)
(conf-ofdm-profile <1:64>)
Syntax
(config)# [no] ofdm exclusion-band <1:16>
(conf-ofdm-exclusion-band x)
[no] exclusion-subcarrier-group <1:128> <108000000:1218000000>
<108000000:1218000000>
[no] ofdm exclusion-band <1:16>...
(config)# [no] ofdm profile <1:64>

(conf-ofdm-profile x)
[no] ofdm profile <1:64>...
profile-modulation <type> rxmer threshold <0:254> [percentage
<0:100>]
[no] subcarrier-group <1:128> [<108000000:1218000000>
<108000000:1218000000> modulation <type> | [skip-modulation
<type>]]
(config)# ofdm profile-modulation <type> rxmer threshold <0:254>
[percentage <0:100>]
Properties
exclusion-band <1:16> Determines the excluded subcarriers that can be

referenced by any downstream RF port.
Example:
CASA(config)# ofdm exclusion-band 1

CASA(conf-ofdm-exclusion-band 1)# exit
CASA(config)# no ofdm exclusion-band 1
Casa Systems
ofdm
exclusion-subcarrier-gro Configures the excluded subcarriers in the OFDM

up <1:128> spectrum. The ID can be provided by itself or along
<108000000:1218000000> with the stop and start frequencies.
<108000000:1218000000>
Example:
CASA(conf-ofdm-exclusion-band 1)#
exclusion-subcarrier-group 1 108000000
109000000
no exclusion-subcarrier-group 1
108000000 109000000
ofdm exclusion-band Configures another OFDM exclusion band without

<1:16> having to exit the exclusion-band context.
Example:
CASA(conf-ofdm-exclusion-band 1)# ofdm

exclusion-band 2
no exclusion-band 2
Casa Systems
ofdm
profile <1:64> Creates distinct data profiles for OFDM.
Dynamic profile changes are supported with DOCSIS

modems remaining online when profiles are updated.
During modem registration, the CMTS selects the
appropriate OFDM channels and the highest-rate
profile according to the modem’s capability. Once the
CM returns a registration acknowledgment, the
CMTS then requests the return modulation error ratio
(RxMER) from the CM to determine if the error rate
(lower RxMER values) is too high to support the
current modulation profile. The software maintains
the highest-rate profile and only moves to a
lower-rate modulation profile if necessary. Once the
CM comes online with the CMTS, the software
switches between modulation profiles (if requested
by the CM) to ensure that the highest-rate profile is
applied to CMs on the OFDM channel.
Example:
CASA(config)# ofdm profile 1

CASA(config)# show cable modem verbose
…
Downstream Channel Set
:11/1/1, 11/1/0, 11/1/2, 11/1/3,
11/1/0w(1,0,2,3)
…
CASA(conf-ofdm-profile 1)# exit
CASA(config)# no ofdm profile 1
ofdm profile <1:64> Configures another OFDM profile without having to

exit the profile context.
Example:
CASA(conf-ofdm-profile 1)# ofdm profile

2
CASA(conf-ofdm-profile 2)#
no ofdm profile 2
Casa Systems
ofdm
profile-modulation Profile modulation type. The types are as follows:

<type>
• 16qam
• 64qam
• 128qam
• 256qam
• 512qam
• 1024qam
• 2048qam
• 4096qam
• zero
Example:
profile-modulation 256qam
subcarrier-group <1:128> Profile subcarrier group ID, which can be combined

[<108000000:1218000000> with their start and stop frequencies, modulation type,
<108000000:1218000000> and skip-modulation type (see the
modulation <type> | profile-modulation property for the type values).
[skip-modulation Multiple subcarrier groups can be configured per
<type>]] profile.
Example:
subcarrier-group 1 108000000 109000000
modulation 256qam
no subcarrier-group 1 108000000
109000000 modulation 256qam
Casa Systems
ofdm
profile-modulation <type> Return modulation error ratio (RxMER) threshold per

rxmer threshold <0:254> subcarrier for the specified modulation type, which
[percentage <0:100>] can be:
• 16qam
• 64qam
• 128qam
• 256qam
• 512qam
• 1024qam
• 2048qam
• 4096qam
The threshold is an integer in 0.25 dB increments,

with an effective range 0–63.5 dB, so a value of 190
would result in a threshold of 190 x 0.25 = 47.5 dB;
the default threshold is 0. A percentage of the
subcarriers with the highest RxMER to check can
also be specified, default 90%. The RxMER results
(as hex 0x00–0xFE values in 0.25 dB increments)
can be viewed with the
show cable ods-report ofdm <slot>/<port>/
<chan> command.
Example:
CASA(config)# ofdm profile-modulation

256qam rxmer threshold 190 percentage
90
show ofdm exclusion-band <1:16> [detail]
Shows the OFDM exclusion band settings.
Casa Systems
ofdm
CASA(config)# show ofdm exclusion-band 1 detail

ofdm exclusion-band 1
exclusion-subcarrier-group 1 108000000 109000000
show all ports that are binding to this ofdm exclusion band 1:
port 4/0 is using exclusion band 1
show ofdm profile [<1:64>] [detail]
Shows the OFDM profile settings.
CASA# show ofdm profile
ofdm profile 1
subcarrier-group 1 110000000 120000000 modulation 256qam
skip-modulation 16qam
CASA(config-if-qam 4/0)# show ofdm profile 2 detail
ofdm profile 2
profile-modulation zero
subcarrier-group 1 108000000 109000000 modulation zero
skip-modulation zero
show all ofdm channel bindings to this ofdm profile 2:

ofdm channel 4/0/0 with admin status 0 have local profile 2 bind to
ofdm profile 2
show cable dpd msg ofdm <slot>/<port>/<chan> profile <id> [plc]
Shows the cable Downstream Profile Descriptor (DPD) message for the OFDM
channel. The optional plc modifier shows the PHY Link Channel (PLC) output only.
Only channel 0 can currently be specified.
CASA# show cable dpd msg ofdm 2/0/0 profile 0

Dump OFDM 2/0/0 profile 0 DPD message(cnt=934032):
0x01 0xe0 0x2f 0x00 0x00 0x01 0x00 0x17 0x10 0x82 0xc7 0x33
0x00 0x10 0x00 0x00
0x03 0x05 0x32 0x00 0x32 0x00 0x01 0x05 0x05 0x2c 0x00 0x00
0x0f 0xff
Decode DPD message
Dest. Address : 01e0.2f00.0001

Source Address: 0017.1082.c733
Message Length: 16 (decimal) DSAP: 00 SSAP: 00
Casa Systems
ofdm
Control: 03 Version: 05
Type: dpd(50) RSVD: 00
Downstream Channel ID: 32

Profile Identifier: 00
Configuration Change Count: 01
Subcarrier Assignment Range/List(5): 2c 00 00 0f ff
show cable ods-report ofdm <slot>/<port>/<chan>
Reports the return modulation error rate (RxMER) values for subcarriers of an OFDM
channel to help determine how to transmit data to the CM as efficiently as possible by
properly configuring the profile settings for all subcarriers. RxMER is defined as the
ratio of the average power of the ideal QAM constellation to the average error-vector
power. The OFDM Downstream Spectrum (ODS) report is initiated as an ODS
request (ODS-REQ) by way of the cable ods-req [<n>:]<slot>/<port>/<chan>
command in diagostic mode (executed under Casa technical support supervision
only). Thresholds are set by the ofdm profile-modulation rxmer threshold
command. The report is cleared through the clear cable ods-report ofdm
[<n>:]<slot>/<port>/<chan> command in diagnostic mode. Up to a thousand ODS
reports are supported. The RxMER values are reported from lowest to highest active
subcarrier, in hex as 4 x dB (in the range 0x00–0xFE), such as in the example the first
value, 84, translates to decimal 132, which yields 132 x .25 = 33 dB.
CASA(diag)# cable ods-req ofdm 2/0/0

CASA# show cable ods-report ofdm 2/0/0
fc52.8d5e.858c on ofdm 11/1/0 ods_report total_len=2551
First Subcarrier-ID: 148
RxMER per Subcarrier:
84 8b 86 89 8b 89 88 89 8c 8d 89 8c 8a 8d 8e 8e
8f 8c 8e 8f 90 8f 8d 8d 8a 8b 8f 8f 8c 91 8b 8f
8b 8e 8d 8c 8c 8e 8e 8d 8b 93 8f 93 8e 90 8f 8f
8d 8f 8f 8e 8c 8f 8e 8c 8f 8f 8f 8e 92 93 8f 91
95 93 8f 93 90 95 93 94 94 92 90 93 90 96 8f 8e
95 91 93 93 91 91 96 95 92 94 91 93 91 90 93 94
…
CASA(diag)# clear cable ods-report ofdm 2/0/0
show module config | include QAM8x192
Shows how many OFDM channels are configured with each QAM 8x192 module.
CASA(config)# show module config | include QAM8x192

module 8: QAM8x192 1 ofdm channel(s)
module 12: QAM8x192 1 ofdm channel(s)
Casa Systems
interface qam
interface qam
Purpose
The interface qam command sets the OFDM parameters for a QAM slot, port, and
channel, and for any port exclusion band. The full QAM interface configuration
options are described in Chapter 17, “QAM interface.”
Modes
(config)#
(config-if-qam <slot>/<port>)#
Syntax
(config)# [no] interface qam <slot>/<port>
(config-if-qam X/Y)#
[no] ofdm port-exclusion-band <1:16>
[no] ofdm-channel <0:1>
[no] ofdm-channel <0:1> cyclic-prefix <192 | 256 | 512 | 768 |
1024>
[no] ofdm-channel <0:1> description <string>
[no] ofdm-channel <0:1> interleave <1:32>
[no] ofdm-channel <0:1> lower-freq <108000000:1196000000>
[upper-freq <130000000:1218000000>] [plc-freq
<108000000:1212000000>]
[no] ofdm-channel <0:1> ncp-modulation <type>
[no] ofdm-channel <0:1> pilot-scale-factor <48:120>
[no] ofdm-channel <0:1> plc-freq <108000000:1212000000>
[no] ofdm-channel <0:1> profile <1:4> <1:64>
[no] ofdm-channel <0:1> rolloff-period <0 | 64 | 128 | 192 | 256>
[no] ofdm-channel <0:1> sc-spacing <25 | 50>
[no] ofdm-channel <0:1> shutdown
[no] ofdm-channel <0:1> up-down-trap-enable
[no] ofdm-channel <0:1> upper-freq <130000000:1218000000>
[lower-freq <108000000:1196000000>] [plc-freq
<108000000:1212000000>]
Casa Systems
interface qam
Properties
ofdm port-exclusion-band Sets the ID of the subcarrier exclusion-band <1:16>

<1:16> on the port level.
Example:

CASA(config-if-qam 4/0)# ofdm
port-exclusion-band 1
CASA(config-if-qam 4/0)#
no ofdm port-exclusion-band 1
ofdm-channel <0:1> On channel 1 or 2, sets the OFDM parameters that

follow on the command line.
Example:
CASA(config)# ofdm-channel 0
CASA(config-if-qam 4/0)# ofdm-channel 0
no ofdm-channel 0
cyclic-prefix <192 | 256 A cyclic prefix (CP) enables the receiver to overcome
| 512 | 768 | 1024> the effects of inter-symbol and intercarrier
interference caused by micro-reflections in the
channel. There are five possible values for the CP
and the choice depends on the delay spread of the
channel: a longer delay spread requires a longer
cyclic prefix. The default is 192. The CP is converted
into samples using the sample rate of
204.8 Msamples/sec and is an integer multiple of
1/64 * 20 microseconds.
Example:

cyclic-prefix 256
no ofdm-channel 0 cyclic-prefix 256
Casa Systems
interface qam
description <string> Adds a description of the OFDM channel, up to 64

are included.
Example:

description “OFDMA for channel 0”
no ofdm-channel 0 description
interleave <1:32> Number of samples for the OFDM downstream

channel, limited to 32 samples for 4K FFT and
16 samples for 8K FFT, respectively. The default is 1.
Example:

interleave 32
no ofdm-channel 0 interleave 32
lower-freq Lower edge frequency of the OFDM downstream

<108000000:1196000000> channel. The upper- freq and/or plc -freq can also
[upper-freq be added, but can be omitted in that these
<130000000:1218000000>] frequencies adjust according to the lower edge
[plc-freq frequency setting. The PLC frequency must be set on
<108000000:1212000000>] a 1-MHz boundary and outside any exclusion zones.
Be sure that the interface is shut down before making

or changing any frequency settings.
Example:

lower-freq 133375000
lower-freq 133375000
upper-freq 323375000
plc-freq 225000000
no ofdm-channel 0 lower-freq 133375000
Casa Systems
interface qam
ncp-modulation <type> Modulation type of all subcarriers in the Next

Codeword Pointer (NCP) channel. If omitted, the
modulation is automatically configured by the CCAP.
The NCP profile is assigned profile ID 255. A
codeword is the forward error correction (FEC) data
block comprising a combination of information bytes
and parity bytes. NCP points to the beginning of
codewords in a symbol, counting only data
subcarriers. It also identifies the physical parameters
communicated from the CMTS to CMs in the NCP.
The modulation type must be consistent across the
interface. NCP modulation changes do not require a
channel shutdown. The modulation types are as
follows (the default is Quadrature Phase Shift
Keying):
• 16qam
• 64qam
• qpsk (default)
• zero
Example:

ncp-modulation 256qam
no ofdm-channel 0 ncp-modulation 256qam
Casa Systems
interface qam
pilot-scale-factor Determines the scale factor for calculating the

<48:120> number of continuous pilots for the OFDM
downstream channel. Continuous pilots, which do not
carry data, occur at the same frequency location in
every OFDM symbol and are used for frequency and
phase synchronization. The default value is 48.
Example:

pilot-scale-factor 48
no ofdm-channel 0 pilot-scale-factor 48
plc-freq The PHY Link Channel (PLC) frequency, the center

<108000000:1212000000> frequency of the lowest subcarrier of the 6 MHz
encompassed spectrum containing the PLC at its
center. The frequency of this subcarrier is required to
be located on a 1-MHz grid. The aim of the PLC is for
the CMTS to convey to the CM the physical
properties of the OFDM channel. If omitted, the PLC
frequency is calculated from the lower or upper
frequency setting, using an algorithm that avoids
setting it inside an exclusion zone. An error message
is returned if the PLC frequency is explicitly set inside
an exclusion zone.

Example:

plc-freq 225000000
no ofdm-channel 0 plc-freq 225000000
Casa Systems
interface qam
profile <1:4> <1:64> OFDM local profile <1:64> ID defined for the
channel (up to four profiles per channel), followed by
the global profile ID (up to 64 profiles). The global
setting may be different from the local one if the
global profile ID is higher than 4, as might be defined
for a composite profile (with multiple subcarrier
groups). The no form of the command uses the local
profile value only.
Example:

profile 1 5
no profile 1
rolloff-period <0 | 64 | The roll-off period or windowing maximizes channel

128 | 192 | 256> capacity by sharpening the edges of the spectrum of
the OFDM signal. There are five available values.
The default is 64.
Example:

rolloff-period 64
no ofdm-channel 0 rolloff-period 64
sc-spacing <25 | 50> Subcarrier spacing associated with a particular FFT

mode configured on the OFDM downstream channel.
If it is 4K mode, the subcarrier spacing is 50 KHz. If it
is 8K mode, the subcarrier spacing is 25 KHz. The
default is 50.
Example:

sc-spacing 25
no ofdm-channel 0 sc-spacing 25
Casa Systems
interface qam
shutdown Shuts down or (with the no form of the command)

restarts the OFDM channel. Any changes that cause
one or more OFDM channel configurations to change
can only be done when those to be impacted
channels are in shutdown mode, except OFDM
profile and channel NCP modulation changes. The
default is shutdown.
Example:

shutdown
no ofdm-channel 0 shutdown
up-down-trap-enable Enables a trap to be sent when the channel

transitions from up to down and from down to up. The
default is not enabled.
Example:

up-down-trap-enable
no ofdm-channel 0 up-down-trap-enable
Casa Systems
interface qam
upper-freq Upper edge frequency of the OFDM downstream

<130000000:1218000000> channel. The lower- freq and/or plc -freq can also
[lower-freq be added, but can be omitted in that these
<108000000:1196000000>] frequencies adjust according to the upper edge
[plc-freq frequency setting. The PLC frequency must be set on
<108000000:1212000000>] a 1-MHz boundary and outside any exclusion zones.

Example:

upper-freq 323375000
upper-freq 323375000 plc-freq 225000000
no ofdm-channel 0 upper-freq 323375000
show ofdm channel [<slot>/<port>/<chan>] [detail]
Shows the OFDM channel settings.
CASA(config)# show ofdm channel 4/0/0
interface qam 4/0/0

ofdm-channel 0 lower-freq 133375000 upper-freq 323375000 plc-freq
148000000
ofdm-channel 0 cyclic-prefix 192
ofdm-channel 0 rolloff-period 64
ofdm-channel 0 interleave 1
ofdm-channel 0 sc-spacing 50
ofdm-channel 0 pilot-scale-factor 48
ofdm-channel 0 ncp-modulation qpsk
ofdm port-exclusion-band 1
ofdm-channel 0 profile 1 1
Casa Systems
interface qam
show ofdm port-exclusion-band <slot>/<port>
Shows the OFDM port exclusion band ID for the QAM channel.
CASA(config)# show ofdm port-exclusion-band 4/0
interface qam 4/0

ofdm port-exclusion-band 1
show cable modem ofdm <slot>/<port>/<chan>
Shows the CMs with OFDM transactions, based on various other options. See the
Casa Systems – CMTS Troubleshooting and Diagnostics Guide, Chapter 2, for details.
Only channel 0 can currently be specified.
CASA# show cable modem ofdm 0/7/0

Intf Intf Status Sid (dBmV)Offset CPEs Enb
fc52.8d5e.9cb7 10.15.1.1 10/0.0w 0/7/0w online 120 0.7 227 0 no
show cable admission-control interface ofdm [<n>:]<slot>/<port>/<chan>
Shows admission control results for the OFDM interface.
CASA# show cable admission-control interface ofdma 11/0/0

2 10 0 0 0
Casa Systems
Purpose
The interface docsis-mac command sets the OFDM downstream binding for the
DOCSIS MAC interface. The full DOCSIS MAC interface configuration options are
described in Chapter 8, “DOCSIS MAC interface.”
Modes
(config)#
(config-if-mac <1:96>)#
Syntax
(config-if-mac x)#
downstream <1:255> interface ofdm <slot>/<port>/<chan>
no downstream <1:255>
Properties
<1:96> ID of the DOCSIS MAC interface.
Example:

CASA(config-if-mac 1)# exit
CASA(config)#
no interface docsis-mac 1
Casa Systems
downstream <1:255> Binds a downstream OFDM interface to a DOCSIS

interface ofdm <slot>/ MAC domain. The values are as follows:
<port>/<chan>
• <1:255> — Required user-defined channel identi-
fier unique within a MAC domain.
• interface ofdm — Required modifier for OFDM
binding, followed by the channel configuration.
Example:

interface ofdm 4/0/0
show interface docsis-mac [<1:96>] brief
Shows the OFDM channel setting on the DOCSIS MAC interface.
CASA(config)# show interface docsis-mac 1 brief
no shutdown
tftp-proxy
downstream 1 interface ofdm 4/0/0
Casa Systems
module <slot> ofdm-channels

Purpose
The module <slot> ofdm-channels command configures the number of OFDM

channels per port, either one or two (the command is not required for one channel by
default unless reverting to one channel from two channels). The FPGA that supports
one OFDM channel on the QAM 8x192 allows for maximum 64 single-carrier QAM
(SC-QAM) channels. The FPGA that supports two OFDM channels allows for
maximum 32 SC-QAM channels and 192 broadcast/shared channels, with maximum
56 narrowcast channels (192 DIV 8 + 32). Any change to the number requires
rebooting the module because of the separate FPGAs used, unless the revision does
not allow you to make the change. Redundant modules must have the same FPGA
image for one or two OFDM channels. Two OFDM channels are currently not
supported with DVB SimulCrypt.
Mode
(config)#
Syntax
module <slot> <1:2>
Properties
<slot> Sets the module slot number.

<1:2> Sets the number of OFDMA channels per port, 1 or 2
channels. Any change to this value requires a module
reboot, if prompted.
Example:

Need to reboot module 1 to apply the
change.
CASA(config)# reboot module 1
Casa Systems
show ofdm-channels [<id>]
Shows the number of OFDM channels per module.
CASA(config)# show ofdm-channels

module 0 ofdm-channels 1
Casa Systems
service group
service group
Purpose
The service group command sets the service group for the OFDM downstream
binding. Once OFDM is enabled for the DOCSIS MAC interface and service group,
the channel information is included in the MAC Domain Descriptor (MDD) message
to broadcast to the modem. The full service group configuration options are described
in Chapter 6, “Channel bonding.”
Modes
(config)#
Syntax
(config-svc-grp x)#
Properties
<name> Service group name for OFDM, up to 16 characters.

Up to 160 service groups are supported.
Example:
CASA(config)# service group OFDM

CASA(conf-svc-grp OFDM)#
CASA(config)# no service group OFDM
ofdm <slot>/<port>/ Downstream binding of the service group to a

<chan> specified OFDM interface. Currently the channel
must be set to 0. (See the interface qam command.)
Example:
CASA(conf-svc-grp OFDM)# ofdm 2/0/0

CASA(conf-svc-grp OFDM)# no ofdm 2/0/0
Casa Systems
OFDM configuration examples

1. OFDM channel, simple profile, no exclusion zone
A simple profile has a default modulation only. A composite profile has both a default
modulation and some additional modulation definitions for some frequency regions.
The following configuration sets the lower frequency to 133.375 MHz, PLC center
frequency to 225 MHz, and upper frequency to 323.375 MHz for one QAM channel
(1/0/0). A single profile has a defined modulation of 16qam. No exclusion zone is
defined.

CASA(conf-ofdm-profile)# profile-modulation 16qam
CASA(conf-ofdm-profile)# exit

CASA(config-if-qam 1/0)# ofdm-channel 0 lower-freq 133375000
CASA(config-if-qam 1/0)# ofdm-channel 0 profile 1 1
CASA(config-if-qam 1/0)# no ofdm-channel 0 shutdown
CASA(config-if-qam 1/0)# show ofdm channel

interface qam 1/0
225000000
ofdm-channel 0 profile 1 1 <----
2. OFDM channel, multiple simple profiles, no exclusion zone
The following configuration sets the lower frequency to 433.375 MHz, PLC
frequency to 525 MHz, and upper frequency to 623.375 MHz. Four defined profiles
are specified at different modulations, and no exclusion zone.

Casa Systems


CASA(config-if-qam 1/0)# show ofdm channel 1/0/0

interface qam 1/0
525000000
ofdm-channel 0 profile 1 1 <---
3. OFDM channel, simple profile, exclusion zone
The following configuration sets the frequency ranges as in configuration #1, with a
simple profile on QAM channel 1/1/0. The difference here is that an exclusion zone is
defined based on a defined port exclusion band for a subcarrier group. Because of the
exclusion frequencies, the PLC frequency needs to be adjusted outside this range.

CASA(conf-ofdm-exclusion-band 1)# exclusion-subcarrier-group 1
200000000 250000000 <----
Casa Systems

CASA(config-if-qam 1/1)# ofdm port-exclusion-band 1

interface qam 1/1
283000000
4. OFDM channel, multiple simple profiles, exclusion zone
The following configuration sets the same frequency ranges as configuration #2 on

QAM channel 1/2/0, but involves multiple simple profiles and a separate
single-subcarrier-group exclusion zone. Global profiles 6 and 8 are added.



CASA(conf-ofdm-exclusion-band 2)# exclusion-subcarrier-group 1
480000000 560000000

CASA(config-if-qam 1/2)# ofdm-channel 0 profile 3 6 <---
CASA(config-if-qam 1/2)# ofdm port-exclusion-band 2 <---
Casa Systems

interface qam 1/2
588000000
5. OFDM channel, composite profile, no exclusion zone
The following configuration involves a single composite profile (having multiple

subcarrier groups) and no exclusion zone, as set on QAM channel 1/3/0.

CASA(conf-ofdm-profile)# subcarrier-group 1 110000000 120000000

modulation 256qam
modulation 64qam skip-modulation 16qam
modulation 512qam
modulation 1024qam
modulation 2048qam
modulation 512qam

Casa Systems

interface qam 1/3
209000000
6. OFDM channel, multiple composite profiles, no exclusion zone
The following configuration involves multiple composite global profiles (9, 10, 11,
and 12) and no exclusion zone, as set on QAM channel 1/3/0.
CASA(config)# show ofdm profile

ofdm profile 9
ofdm profile 10
ofdm profile 11
Casa Systems

ofdm profile 12

CASA(config-if-qam 1/3)# lower-freq 407375000 upper-freq 597375000
plc-freq 499000000

interface qam 1/3
499000000
Casa Systems
7. OFDM channel, composite profile, exclusion zone
The following configuration involves a single composite global profile (9) and the
exclusion zone on the QAM port from Example 3, as set on channel 1/4/0.

plc-freq 283000000
interface qam 1/4
283000000
8. OFDM channel, multiple composite profiles, exclusion zone
The following configuration involves multiple composite global profiles and an

exclusion zone on the QAM port involving two frequency-separated exclusion
subcarrier groups, as set on QAM channel 1/4/0. Setting just the lower and upper
frequencies sets the PLC frequency automatically outside the exclusion zone.
CASA(config)# show ofdm exclusion-band 5

ofdm exclusion-band 5
exclusion-subcarrier-group 1 480000000 500000000 <---
exclusion-subcarrier-group 2 560000000 580000000 <---
Casa Systems

interface qam 1/4
ofdm-channel 0 lower-freq 407375000 upper-freq 597375000
Casa Systems
15-1
Chapter 15. Orthogonal Frequency

Division Multiple Access
OFDMA description
Orthogonal Frequency Division Multiple Access (OFDMA) is a multi-user version of
Orthogonal Frequency Division Multiplexing (OFDM) where many users can
transmit and receive over a single channel simultaneously. OFDMA uses distributed
subcarriers among users to enable multiple user transmissions over one channel.
DOCSIS Version 3.1-specific modems are necessary to support OFDMA in the cable
network. DOCSIS 3.0 and earlier modems are not supported.
The OFDMA upstream channel capability is available for the UPS 16x8 line card on
the C100G and C40G platforms and is based on the DOCSIS 3.1 specifications from
CableLabs. One OFDMA upstream channel is supported per port.
Backward compatibility and interoperability with legacy QAM and UPS channels
coexist with both OFDM (downstream) and OFDMA (upstream) implementations.
Table 15-1 lists and briefly describes the objects related to OFDMA.
Table 15-1. OFDMA objects
ofdma Sets the OFDMA upstream exclusion bands, Interval Usage

Code (IUC) profile, and minislot configuration.
Casa Systems
Definitions
Table 15-1. OFDMA objects
interface docsis-mac Sets the OFDMA upstream binding for the DOCSIS MAC
interface.
interface ofdma Sets the OFDMA upstream interface binding.
service group Sets the service group for the OFDMA binding.
Definitions
channel configuration — Defines the upstream OFDMA channel table. The minimum
occupied bandwidth is 6.4 MHz for 25-KHz and 10 MHz for 50-KHz subcarrier
spacing, and cannot exceed 96 MHz.
cyclic prefix — Enables the receiver to overcome the effects of inter-symbol and
intercarrier interference caused by micro-reflections in the channel. There are five
possible values and the choice depends on the delay spread of the channel. A longer
delay spread requires a longer cyclic prefix.
fine ranging — Ranging used after initial ranging is completed, to fine-tune timing
and power.
initial ranging — Ranging used by the CMTS to identify a new admitting CM and for
coarse power and timing ranging.
interval usage code (IUC) — Burst profile descriptor for OFDMA upstream channels,
a 4-bit code in the Upstream Channel Descriptor (UCD) message. IUC profiles are
defined for data, initial ranging, and fine ranging.
low-density parity-checking — The low-density parity-check (LDPC) error-correcting

code is supported with OFDMA transmissions. The LDCP implementation is
compliant with the DOCSIS 3.1 specification. There is no configuration requirement
with this functionality.
lower-freq — Defines the lowest active subcarrier frequency, range 5–94.6 MHz.
upper-freq — Defines the highest active subcarrier frequency, range 11.4–101 MHz.
Casa Systems
Orthogonal Frequency Division Multiple Access 15-3
Definitions
minislot — A group of dedicated subcarriers with the same modulation order, for
upstream transmission by a given cable modem.
modulation type — Defines the modulation type supported by the CM demodulator, in

the range 8QAM–1024QAM, and includes Quadrature Phase Shift Keying (QPSK) or
zero.
pilot — A dedicated OFDMA subcarrier that can be used for channel estimation
(measurement of channel condition), synchronization, and other purposes. Pilot
subcarriers do not carry data. A set of pilot patterns is defined from which the CMTS
or operator can select to match the frequency response of the network. The
pilot-scale-factor indicates the scale factor for calculating the number of continuous
pilots for a downstream channel.
pre-equalization — Compensates for the difference in delays between the signal on

the lower part of the 6-MHz channel spectrum and the higher part, or microreflections,
caused by imperfections in the cable plant for OFDMA upstream traffic. The CMTS
uses the CM’s probe signal for pre-equalizer coefficient updates. A probe is a
wideband physical layer signal that the CM sends in response to a special probe
bandwidth allocation.
ranging backoff —The random back-off window to use when retrying ranging
requests, expressed as start and end values in powers of two. A CM transmitting a
RNG-REQ performs truncated binary exponential backoff using the two values to
control the backoff window.
redundancy — UPS 16x8 line cards operating in mixed-mode TDMA/OFDMA are

not redundancy protected if the UPS 16x8 standby is configured as a TDMA
single-mode version. This also applies in the opposite scenario. For mixed-mode
redundancy protection, the standby UPS 16x8 module in redundant system slot 5 or 8
must be configured as a matching mixed-mode UPS 16x8. To redundancy-protect the
active UPS card with a non-matching standby UPS card, interactively configure the
standby UPS card to match the active UPS so that both modules are a matching
single-mode or mixed-mode pair before performing a switchover.
rolloff — The rolloff period (RP) or windowing maximizes channel capacity by

sharpening the edges of the frequency spectrum of the OFDMA signal. There are five
possible values for the RP, and the choice depends on the bandwidth of the channel
and the number of exclusion bands within the channel. There is an optimum value for
Casa Systems
Definitions
the RP that maximizes capacity for a given bandwidth and/or exclusion band scenario.
OFDMA has eight windowing types for upstream traffic.
SNMP MIBS and traps — OFDMA is supported in the DOCS-IF31-MIB.
subcarrier — The OFDMA upstream multicarrier systems are composed of a large

number of subcarriers that have either 25 or 50 KHz spacing. These subcarriers are
grouped into independently configurable OFDMA channels, each occupying a
spectrum of up to 192 MHz in the downstream, totaling 7680 25-KHz subcarriers or
3840 50-KHz subcarriers, of which up to 7601 (25-KHz) or 3801 (50-KHz) active
subcarriers span 190 MHz. Many parameters of these channels can be independently
configured, thereby optimizing configuration based on channel conditions. A
subcarrier group is a collection of consecutive subcarriers.
subcarrier exclusion — Excludes all subcarriers that can be referenced by any

downstream RF port. Muted subcarriers have a value of zero in the bit-loading pattern
of a profile. An exclusion subcarrier group is a collection of exclusion subcarriers.
subcarrier spacing — Defines the KHz spacing associated with a particular FFT
mode configured on the OFDMA upstream channel. If it is 4K mode, the subcarrier
spacing is 50 KHz (the default). If it is 8K mode, the subcarrier spacing is 25 KHz.
subcarrier zero (SC0)— A subcarrier without power or data and below the defined
channel frequency range. The SC0 center frequency is based on the defined 25-KHz
or 50-KHz spacing. For example, a frequency range of 5–35 MHz for 50-KHz spacing
would have a center frequency of 1.35 MHz; a range of 10–35 MHz would have a
center frequency of 6.35 MHz.
time and frequency division multiplexing (TaFDM) — Allows the upstream frequency
spectrum to be shared between the two types of channels, where a TDMA and
OFDMA channel overlap each other. This feature allows users to transition from the
traditional TDMA scheme to the OFDMA scheme. With multi-access to shared
spectrum resources using the TaFDM scheme, spectrum resources are divided into
time and frequency dimensions which are then allocated to one channel or another.
The upstream scheduler determines which area is used for TDMA or OFDMA
transmissions, with guard bands inserted on the boundary between TDMA and
OFDMA channels both in frequency and time dimensions. The overlapping channels
must be configured into the same OFDMA subcarrier service group. An OFDMA
Casa Systems
OFDMA configuration steps
channel can (a) cover the entirety of all TDMA channels, (b) cover a portion of the
TDMA channels on one side, or (c) reside inside the TDMA spectrum area.
up-down-trap-enable — Indicates if a trap should be sent when the channel transitions

from up to down and from down to up.
OFDMA configuration steps
The steps to configuring upstream OFDMA are the following (see also the “OFDMA
configuration example” section):
1. Enable OFDMA for UPS 16x8 by using the module <num> ofdma enable
command. (See “Related commands.”)
2. Define the modulation and pilot pattern for one or more consecutively numbered
OFDMA minislots (minislot-cfg <1:64>).
3. Configure the Interval Usage Code profile (iuc-profile <1:64>) to set the data
grant and ranging parameters.
4. Define any frequency exclusion bands (exclusion-band <1:16>), to be set in the
next step at the port level for the upstream OFDMA interface.
5. Configure the upstream interface ofdma channel parameters for OFDMA
bindings (be sure the channel is shut down first).
6. Configure the service group for the OFDMA upstream binding.
TaFDM between OFDMA and TDMA channels
Time and Frequency Division Multiplexing (TaFDM) allows the upstream frequency
spectrum to be shared between the two types of channels, where one OFDMA channel
overlaps one or more TDMA channels. This feature allows users to transition from the
traditional TDMA scheme to the OFDMA scheme.
With multi-access to shared spectrum resources using the TaFDM scheme, spectrum
resources are divided up into time and frequency dimensions which are then allocated
to one channel or another. The upstream scheduler determines which area will be used
for TDMA or OFDMA transmissions. A guardband will be inserted on the boundary
between TDMA and OFDMA channels both in frequency and time dimensions. The
overlapping channels must be in the same OFDMA subcarrier service group.
Casa Systems
TaFDM between OFDMA and TDMA channels
TaFDM restrictions
There are no restrictions on how the frequency overlap can occur. For example, an
OFDMA channel can:
• Cover the entirety of all TDMA channels,

• Cover a portion of the TDMA channels on one side, and
• Reside inside the TDMA spectrum area.
Example
CASA(config)# interface upstream 11/1.0
CASA(config-if-ups 11/1.0)# frequency 22000000 CASA(config-if-ups 11/
1.0
CASA(config-if-ups 11/1.1)# frequency 28400000 CASA(config-if-ups 11/
1.1)# channel-width 6400000
CASA(config-if-ups 11/1.2)# frequency 38000000
CASA(config-if-ups 11/1.2)# channel-width 6400000
CASA(config-if-ups 11/1.2)# interface upstream 11/1.3
CASA(config-if-ups 11/1.3)# channel-width 3200000
CASA(config-if-ups 11/1.3)# end
CASA(config)# ofdma exclusion-band 1
CASA(conf-ofdma-exclusion-band 1)# exclusion-sc-group 1 5000000
7000000
CASA(conf-ofdma-exclusion-band 1)# end
CASA(config)# interface ofdma 11/1.0
CASA(conf-ofdma-channel 11/1.0)# lower-freq 5000000 upper-freq
85000000
CASA(conf-ofdma-channel 11/1.0)# prov-attrib-mask 0x0
CASA(conf-ofdma-channel 11/1.0)# sc-spacing 50
CASA(conf-ofdma-channel 11/1.0)# symbols-per-frame 16
CASA(conf-ofdma-channel 11/1.0)# data-backoff automatic
CASA(conf-ofdma-channel 11/1.0)# ranging-backoff 0 4
CASA(conf-ofdma-channel 11/1.0)# voice-bw-reserve 75 emergency 0
CASA(conf-ofdma-channel 11/1.0)# power-level 0
CASA(conf-ofdma-channel 11/1.0)# power-adjust continue 4
CASA(conf-ofdma-channel 11/1.0)# power-adjust threshold 1
CASA# show docsis upstream channel utilization

Upstream Total-BW Utilization Online Secondary Channel
Slot/Port.Channel (Mb/Sec) Percentage Modems Modems Description
11/1.0 (22000000 Hz) 30.7 80 1 2
11/1.1 (28400000 Hz) 30.7 79 0 3
11/1.2 (34800000 Hz) 30.7 80 0 3
Casa Systems
TDMA/OFDMA guardband implementation
11/1.3 (39600000 Hz) 15.4 65 1 2

11/1.0w ( 5M- 85M Hz) 580.6 55 1 1 ofdma

With Time Division Multiple Access (TDMA) and Orthogonal Frequency Division
Multiple Access (OFDMA) channels both enabled on upstream ports, RF interference
may occur between the TDMA and OFDMA channels that can degrade the overall
throughput of all the channels. To address this situation, a guardband (a region not
used for transmission) has been implemented between the channels to safeguard
against RF interference (Figure 15-1).
Figure 15-1. OFDMA/TDMA guardband implementation
With OFDMA mode enabled on a UPS 16x8 line card, each port supports up to one
OFDMA channel and four TDMA single-carrier channels. The OFDMA channels are
between 5 and 101 MHz, while the ATDMA channels can have a center frequency
between 5 and 100 MHz. If the non-overlapping area between the OFDMA and
TDMA edge frequencies is less than 2 MHz, the chances of RF interference can
increase.
An algorithm has been applied to insert a guardband of a specific size automatically

between the OFDMA and single-carrier frequencies based on the signal-to-noise ratio
(SNR) to guarantee error-free transmission. The guardband can be placed at either the
Casa Systems
low or high end of the OFDMA spectrum based on where the TDMA spectrum is
located.
The SNR value determines the size of the guardband. The guardband range is in
increments of 0.25 MHz from 0.25 MHz through 2.0 MHz. For example, with an SNR
measured at 4 dB, a guardband of 0.25 MHz is imposed, whereas an SNR of 20 dB
imposes a larger guardband of 2.0 MHz. The system does this automatically and
requires no user input. The frequency modulation rate also has an effect on the
guardband size. Lower modulation rates (at a smaller bitrate) are less sensitive to
SNR, in which case a smaller guardband can be applied. A high modulation rate at
QAM1024, for example, requires a higher SNR (35.5 dB, translated to 9.5 dB by the
guardband algorithm), requiring a higher guardband size.
The system imposes certain fixed filter sizes for the OFDMA band with the guardband
in effect, in 5-MHz intervals starting at 10 MHz and extending to 95 MHz. The
95 MHz filter is used if no combined OFDMA and TDMA traffic is enabled. The
other 10 filters are used when overlapping occurs inside the OFDMA band. With
combined traffic, the narrowest filter that completely covers the overlapping area is
selected. For example, with a 20–40 MHz OFDMA band and a 6.4 MHz TDMA band
at 22 MHz, with both sets of channels operating, a 15 MHz filter is selected for the
OFDMA band.
With the guardband in effect, the OFDMA band typically has a 70–80% utilization
rate with OFMA and TDMA transmitting simultaneously.
Note: To disable the system from adding a guardband automatically, an

exclusion zone between the OFDMA and TDMA channels can be configured.
However, the size of the exclusion zone must be calculated to be sufficiently
large to safeguard against overlaps.
Example
The following shows a guardband assignment based on changing a TDMA upstream
interface frequency.
CASA(config-if-ups 12/0.0)# show this
interface upstream 12/0.0

frequency 20000000
channel-width 6400000
power-adjustment continue 4
Casa Systems
logical-channel 0 profile 7
logical-channel 0 minislot 2
logical-channel 1 shutdown
no shutdown
CASA(config-if-ups 12/0.0)# show interface ofdma 12/0.0
interface ofdma 12/0.0

lower-freq 20000000 upper-freq 55000000
no voice-bw-reserve
power-adjust continue 4
rolloff-period 64
iuc-profile 1
no shutdown
CASA(config-if-ups 12/0.0)# show cable modem fec

MAC Address US IF USSNR Unerrored Corrected Uncorrectable
6814.01f0.3e67 12/0.0/0 42.1 75 0 0
6814.01f0.3e67 12/0.0w 42.1 11483944 12745 8
e448.c7c0.dc1a 12/0.0/0 42.1 7834606 0 0
After the frequency adjustment from 20 to 21 MHz, the OFDMA wide filter selected
is 40 MHz (centered at 37.55 MHz) while the narrow filter selected is 35 MHz
(centered at 41.95 MHz). The guardband is set at 0.25 MHz. The ensuing signal
quality during mixed mode transmission then has a 0.1% correctable forward error
correction (FEC) rate.
Casa Systems
ofdma
ofdma
Purpose
The ofdma command sets three OFDM Multiple Access (OFDMA) upstream
parameters: exclusion bands, an Interval Usage Code (IUC) profile, and a minislot
configuration. With OFDMA enabled, the maximum number of single-carrier
channels per port is four (channels 0–3).
If multiple data IUCs are specified, the system performs the following steps:
1. It selects up to two IUCs (which must include IUC 13 as the baseline profile) for
an OFDMA channel as the initial ranging channel of modems. (It assigns IUC 13
to the OFDMA channel only if the CM registers with a non-OFDMA channel.)
2. It dynamically switches between the two IUCs based on signal-to-noise ratio
(SNR) and the data error rate.
3. It does not send dynamic bonding change (DBC) to a dynamically changed IUC
set after the modem registers in step 1.
Modes
(config)#
(conf-ofdma-exclusion-band <1:16>)#
(conf-IUC-profile <1:64>)#
(conf-minislot-cfg <1:64>)#
Syntax
(config)# [no] ofdma exclusion-band <1:16>
(conf-ofdma-exclusion-band x)#
exclusion-sc-group <1:32> <5000000:101000000> <5000000:101000000>
no exclusion-sc-group <1:32>
(config)# [no] ofdma iuc-profile <1:64>

(conf-IUC-profile x)#
data-iuc <5|6|9|10|11|12|13> modulation <type> pilot-pattern <1:8>
[minislot-cfg <1:64>]
no data-iuc <5|6|9|10|11|12|13>
fine-ranging-iuc <32:512> <1:10000000>
initial-ranging-iuc <32:128> <1:10000000>
(config)# [no] ofdma minislot-cfg <1:64>
Casa Systems
ofdma
(conf-minislot-cfg x)#
subcarrier-group-minislot <1:32> <5000000:100600000>
<5400000:101000000> modulation <type> pilot-pattern <1:8>
no subcarrier-group-minislot <1:32>
(config)# ofdma probe interval <10:10080>

no ofdma probe interval
Properties
exclusion-band <1:16> Determines the excluded subcarriers that can be

referenced by any upstream RF port.
Example:

CASA(conf-ofdma-exclusion-band 1)# exit
CASA(config)# no ofdma exclusion-band 1
exclusion-sc-group Group ID of the subcarrier group as assigned on the

<1:32> port level for the QAM interface along with the start
<5000000:101000000> and stop frequencies for the exclusion band.
<5000000:101000000>
Example:

CASA(conf-ofdma-exclusion-band 1)#
exclusion-sc-group 1 50000 550000
CASA(conf-ofdma-exclusion-band 1)#
no exclusion-sc-group 1
Casa Systems
ofdma
iuc-profile <1:64> Interval Usage Code (IUC) profile for OFDMA

upstream. The CMTS selects up to two data profiles
for the OFDMA channel that ranged prior to
registration, one is always IUC 13 (the default and
usually the lowest modulation), and the other being
the one with the highest modulation. TLV 46.11 is
included in the REG-RSP-MP message based on the
IUC selected.
Example:
CASA(config)# ofdma iuc-profile 1

CASA(conf-IUC-profile 1)# exit
CASA(config)# no ofdma iuc-profile 1
Casa Systems
ofdma
data-iuc Data grant ID for the IUC profile. Up to five data IUCs
<5|6|9|10|11|12|13> can be defined for an OFDMA channel. The 5, 6, 9,
modulation <type> 10, 11, and 12 IDs are optional data IUCs. The 13 ID
pilot-pattern <1:8> is the required unpredefined type 5 upstream channel
[minislot-cfg <1:64>] data if the other IDs are not specified (see the top of
the command description for details).
The modulation types are as follows:
• 8qam
• 16qam
• 32qam
• 64qam
• 128qam
• 256qam
• 512qam
• 1024qam
• qpsk (Quadrature Phase Shift Keying)
The current IUCs are listed in show cable modem

<mac_addr> verbose command output at the end of
the Upstream Channel Set list as w<uic,...>, with
the selected UIC (or UICs, up to two), with the
currently active one listed first.
Example:

CASA(conf-IUC-profile 1)# data-iuc 13
modulation qpsk pilot-pattern 1
CASA(conf-IUC-profile 1)#
no data-iuc 13
Casa Systems
ofdma
fine-ranging-iuc Fine ranging is used for station maintenance and

<32:512> <1:10000000> provides an interval in which new stations are
expected to perform some aspect of routine network
maintenance after initial ranging is completed, such
as fine-tuning timing and power. The parameter sets
the maximum number of subcarriers for fine ranging,
along with the sum of the upper and lower guard
bands for fine ranging in Hz.
Example:

fine-ranging-iuc 32 1000000
initial-ranging-iuc Initial ranging is used by the CMTS to identify a new

<32:128> <1:10000000> admitting CM and for coarse power and timing
ranging. It provides an interval in which new stations
can join the network. The parameter sets the
maximum number of subcarriers for initial ranging,
along with the sum of the upper and lower guard
bands for initial ranging in Hz.
Example:

initial-ranging-iuc 32 1000000
Casa Systems
ofdma
minislot-cfg <1:64> Defines the modulation and pilot pattern for one or
more consecutively numbered minislots, where one
or both of these parameters differ from the default for
the OFDMA profile for this channel. For OFDMA, a
minislot is a group of dedicated subcarriers all with
the same modulation order. The minislots affected
are defined by a frequency range.
Example:
CASA(config)# ofdma minislot-cfg 1

CASA(conf-minislot-cfg 1)#
subcarrier-group-minislot 1 5000000
pilot-pattern 2
CASA(conf-minislot-cfg 1)# end
CASA(config)# no ofdma minislot-cfg 1
Casa Systems
ofdma
subcarrier-group-minislo Subcarrier group minislot ID along with its start and

t <1:32> end frequencies, modulation type, and pilot pattern:
<5000000:100600000>
<5400000:101000000> • The start frequency defines where the minislot
modulation <type> uses the pilot pattern and modulation as specified
pilot-pattern <1:8> by this object instead of the defaults for the
channel, and must be within the frequencies
allotted to the channel.
• The end frequency defines where the minislot
uses the pilot pattern and modulation as specified
by this object instead of the defaults for the
channel, and must be greater than or equal to the
start frequency. An error message appears if
there are frequency overlaps among multiple
subcarrier groups.
The modulation types are as follows:
• 8qam
• 16qam
• 32qam
• 64qam
• 128qam
• 256qam
• 512qam
• 1024qam
• zero
Example:

subcarrier-group-minislot 1 5000000
pilot-pattern 2
no subcarrier-group-minislot 1
Casa Systems
ofdma
probe interval <10:10080> Sets the OFDMA probe interval, in minutes. The
default at bootup is disabling the probe so that no
CMs probe, at initial ranging or periodically.
Example:
CASA(config)# ofdma probe interval 60

CASA(config)#
no ofdma probe
Related commands
show ofdma exclusion-band [<1:16>]
Shows the OFDMA exclusion band settings.
CASA(config)# show ofdma exclusion-band
ofdma exclusion-band 1
show ofdma iuc-profile [<1:64>]
Shows the OFDMA IUC profile settings.
CASA(config)# show ofdma iuc-profile
ofdma iuc-profile 1
fine-ranging-iuc 32 800000
initial-ranging-iuc 32 800000
data-iuc 13 modulation 1024qam pilot-pattern 2
Casa Systems
ofdma
show ofdma minislot-cfg [<1:64>]
Shows the OFDMA minislot configuration settings.
CASA(config)# show ofdma minislot-cfg
ofdma minislot-cfg 1
subcarrier-group-minislot 1 5000000 9600000 modulation zero
pilot-pattern 1
show ofdma probe interval
Shows the OFDMA probe interval, if set by the ofdma probe interval command.
Probing is disabled by default.
CASA(config)# show ofdma probe interval
OFDMA probe interval is set to 60 minutes.
show cable modem ofdma <slot>/<port>.<chan>
Shows the CMs with OFDMA transactions, based on various other options. See the
Casa Systems – CMTS Troubleshooting and Diagnostics Guide, Chapter 2, for details.
CASA# show cable modem ofdma 11/0.0

0895.2a9b.2aa 10.84.1.144 10/1.0w 3/0/0w online 1 0.7 174 0 no
online cm 1 ; offline cm 0 ; ranging cm 0
clear cable modem ofdma <slot>/<port>.<chan> [offline | reset]
Clears a CM of OFDMA, with the offline and reset options.
CASA# clear cable modem ofdma 10/1.0 offline
show cable admission-control interface ofdma [<n>:]<slot>/<port>.<chan>
Shows admission control results for the OFDMA interface.
CASA# show cable admission-control interface ofdma 0/0.0

1 10 0 0 0
Casa Systems
Purpose
The interface docsis-mac command sets the OFDMA upstream binding for the
DOCSIS MAC interface. The full DOCSIS MAC interface configuration options are
described in Chapter 8, “DOCSIS MAC interface.”
Modes
(config)#
(config-if-mac <1:96>)#
Syntax
(config-if-mac x)#
upstream <1:255> interface ofdma <slot>/<port>.<chan>
no upstream <1:255>
Properties
<1:96> ID of the DOCSIS MAC interface.
Example:

CASA(config-if-mac 1)# exit
CASA(config)#
no interface docsis-mac 1
Casa Systems
upstream <1:255> Binds an upstream OFDMA interface to a DOCSIS

interface ofdma <slot>/ MAC domain. The values are as follows:
<port>.<chan>
• <1:255> — Required user-defined channel identi-
fier unique within a MAC domain.
• interface ofdma — Required modifier for
OFDMA binding, followed by the channel configu-
ration (currently the OFDMA channel must be set
to 0).
Example:
CASA(conf-if-mac 1)# upstream 1

CASA(conf-if-mac 1)# no upstream 1
show interface docsis-mac [<1:96>] brief
Shows the OFDMA channel setting on the DOCSIS MAC interface.
CASA(config)# show interface docsis-mac 1 brief
no shutdown
tftp-proxy
upstream 1 interface ofdma 11/1.0
Casa Systems
interface ofdma
interface ofdma
Purpose
The interface ofdma command sets the OFDMA upstream channel binding. OFDMA
can be configured on upstream interface ports 0–15. With OFDMA, the maximum
number of single-carrier (TDMA or ATDMA) channels per port are reduced to four.
Note: For redundancy, the standby UPS_16x8 module installed (in slot 5 or 8) must
also be a multi-mode FPGA that includes OFDMA. Use the show system or show
module config command to confirm.
Modes
(config)#
(conf-ofdma-channel <slot>/<port>.<chan>)#
Syntax
(config)# [no] interface ofdma <slot>/<port>.<chan>
(conf-ofdma-channel x/y.z)#
cyclic-prefix <96 | 128 | 160 | 192 | 224 | 256 | 288 | 320 | 384 |
512 | 640>
data-backoff <0:15> {<0:15> | automatic}
no data-backoff
description <string>
no description
exclusion-band <1:16>
interface ofdma <slot>/<port>.<chan>
iuc-profile <1:64>
lower-freq <5000000:94600000> upper-freq <11400000:101000000>
map-advance {dynamic <200:2000> | static <200:4000>}
no map-advance
[no] multiple-iuc [err-threshold <1:999> | interval <1:200> |
max-retry {<2:200> | unlimited}]
power-adjustment {continue <2:15> | threshold <0:2>}
power-level <-12:12>
[no] pre-equalization
prov-attr-mask {<0x0:0xffffffff> | {[bonding] [highavailability]
[lowlatency]}
ranging-backoff <0:15> <0:15>
no ranging-backoff
rolloff-period <0 | 32 | 64 | 96 | 128 | 160 | 192 | 256>
sc-spacing <25 | 50>
Casa Systems
interface ofdma
[no] shutdown
symbols-per-frame <6:36>
[no] up-down-trap-enabled
voice-bw-reserve {<0:100> [emergency <0:100>] | max-calls <0:255>}
[emergency <0:255>]
no voice-bw-reserve
Properties
<slot>/<port>.<chan> Slot, port, and channel of the OFDMA interface.

Currently only channel 0 can be specified (otherwise
an error is returned).
Example:

Error: supported port:
1,3,5,7,9,11,13,15
Invalid ofdma channel; only channel 0
is supported
CASA(conf-ofdma-channel 11/1.0)# exit
CASA(config)# no interface ofdma 11/1.0
cyclic-prefix <96 | 128 | A cyclic prefix (CP) enables the receiver to overcome
160 | 192 | 224 | 256 | the effects of inter-symbol and intercarrier
288 | 320 | 384 | 512 | interference caused by micro-reflections in the
640> channel. There are 11 possible values for the CP and
the choice depends on the delay spread of the
channel: a longer delay spread requires a longer
cyclic prefix. The CP is converted into samples using
the sample rate of 204.8 Msamples/sec and is an
integer multiple of 1/64 * 20 microseconds. The cyclic
prefix must be greater than the rolloff-period. There
is no no form of the command.
Example:

CASA(conf-ofdma-channel 11/1.0)#
cyclic-prefix 128
Casa Systems
interface ofdma
data-backoff <0:15> The DOCSIS-specified method of contention

{<0:15> | automatic} resolution for CMs wanting to transmit on the
upstream channel is a truncated binary exponential
backoff value, with the initial backoff window and the
maximum backoff window controlled by the CMTS.
The CMTS specifies backoff window values for both
data transmission and initial ranging. It sends these
values downstream as part of the MAP message.
The power-of-two values are configurable. For
example, 4 indicates a window between 0 and 15; 10
indicates a window between 0 and 1023. You can set
fixed start and end values for data backoff on the
upstream ports or have them done automatically. The
default start value is 0; the default end value is 4.
Example:

data-backoff 0 automatic
no data-backoff
description <string> Adds a description of the OFDMA channel, up to 64

are included.
Example:

description “OFDMA channel 11/1.0”
no description
Casa Systems
interface ofdma
exclusion-band <1:16> Determines the excluded subcarriers for the OFDMA

channel, based on the exclusion-band
configuration.
Example:

exclusion-band 1
no exclusion-band 1
interface ofdma <slot>/ Configures another OFDMA interface.

<port>.<chan>
Example:

iuc-profile <1:64> Interval Usage Code (IUC) profile for the OFDMA
upstream channel. An error is returned if an
iuc-profile is not preconfigured with a data-uic
defined.
Example:

iuc-profile 2
data-iuc profile 2 has not been
configured
iuc-profile 1
Casa Systems
interface ofdma
lower-freq Lower and upper edge frequencies of the OFDMA

<5000000:94600000> upstream channel. For 25-KHz (4K FFT) subcarrier
upper-freq spacing, the bandwidth must be multiples of 6.4 MHz,
<11400000:101000000> which makes the lower frequency maximum value
94.6 MHz. For 50-KHz (2K FFT) subcarrier spacing,
the bandwidth must be multiples of 10 MHz, which
makes the lower frequency maximum value 90 MHz.
This makes the upper frequency minimum value
11.4 MHz for 25-KHz spacing and 15 MHz for
50-KHz spacing. Differences in lower and upper
frequency values greater than the specified
bandwidth (maximum 96 MHz) are not allowed and
an error is returned.
Example:

Error: invalid frequency range for
50khz spacing (BW = 10 ~ 96Mhz) from
5000000 to 11400000
Casa Systems
interface ofdma
map-advance {dynamic MAP advance for the OFDMA interface is the amount
<200:2000> | static of look-ahead time for MAPs based on the plant
<200:4000>} characteristics. The system already has a built-in
look-ahead time to account for internal operations
such as generating the MAP. One of two options are
available, as follows:
• dynamic <max_delay> — Dynamic MAP

advance automatically tunes the look-ahead time
by calculating the offset to the farthest modem on
that upstream port. The delay value defines an
additional look-ahead time for MAPs to allow for
internal latencies and inaccuracies in the mea-
surement system.
• static <max_delay> — Static MAP advance uses
a specified fixed look-ahead time. (For reference,
a mile of coax cable has a delay of about 7 ms
and a mile of fiber has a delay of about 8 ms.)
The default delay is equivalent to map-advance
static 3000, a conservative value. Using large delay
values increases the runtime look-ahead in MAPs,
but also reduces the upstream performance. A delay
value of 200 ms is usually adequate. For optimal
performance, measure the throughput relative to the
percent utilization and adjust the delay value to
achieve maximum throughput.
Example:

map-advance dynamic 200
no map-advance
Casa Systems
interface ofdma
multiple-iuc Enables sending multiple Internal Usage Code (IUC)

[err-threshold <1:999> | TLV 46.11 messages to CMs supporting multiple
interval <1:200> | IUCs over OFDMA channels. With this feature in
max-retry {<2:200> | effect (it is disabled by default), after the modem
unlimited}] registers with the TLV, the CMTS selects the best
IUC on the channel based on the error rate and SNR,
thereby switching the channel from the lower
data-iuc (IUC 13 by default) to the one with the
higher rate. If the SNR and FEC values are both high,
a 15-minute switching delay period allows the SNR to
resolve itself before deciding on a switching change.
The optional parameters set the following values:
• err-threshold <1:999> — Uncorrectable packet

rate threshold to switch the IUC to a lower
modulation rate, specified in 0.1 percent units (to
provide granularity at lower percentages), default
20 (2%).
• interval <1:200> — Number of ranging intervals
to wait (default 6) before considering another IUC
change, to avoid excessive changes. Each rang-
ing interval is normally 10 seconds (thus the
default waiting period is 60 seconds). The usual
range interval checking resumes after this waiting
period until the next IUC change when the waiting
period again takes effect.
• max-retry {<2:200> | unlimited>} — Maximum
IUC switching retry attempts before making a
dynamic bonding change (DBC) to substitute
another data-iuc contained in the iuc-profile
defined for the OFDMA interface. The unlimited
keyword (the default setting) prevents this from
occurring.
Example:

multiple-iuc err-threshold 10
no multiple-iuc
Casa Systems
interface ofdma
power-adjustment Configures the power adjustment. With a power

{continue <2:15> | adjustment larger than the continue value, the
threshold <0:2>} ranging status becomes CONTINUE. With a power
adjustment smaller than the threshold value, a zero
power adjustment is sent instead of the actual value
in the RNG-RSP message.
Example:

power-adjustment continue
power-level <-12:12> Adjusts the output power level (attenuation) of the

interface. The Casa CMTS controls the output power
levels of CMs to meet the desired upstream input
power level. The nominal input power level for the
upstream RF carrier is in 10thdecibels per millivolt
(.1dBmV). The optimal setting is 0.
Example:

power-level -3
pre-equalization Enables OFDMA channel pre-equalization, which

compensates for the difference in delays between the
signal on the lower part of the 6-MHz channel
spectrum and the higher part, or microreflections,
caused by imperfections in the cable plant. The
default state is disabled, but Casa recommends that
it be enabled.
Example:

pre-equalization
no pre-equalization
Casa Systems
interface ofdma
prov-attr-mask Logical channel’s provisioned attribute mask.

{<0x0:0xffffffff> | DOCSIS 3.1 provisioned attribute masks allow
{[bonding] assigning of service flows to channels or channel
[highavailability] bonding groups. These attributes are either
[lowlatency]} user-defined or specification-defined. At least one of
the following values is required:
• <0x0:0xffffffff> — User-defined value, default 0x0.

• bonding — Upstream channel bonding attribute
mask, bit 0 for channel interfaces and bit 1 for
channel bonding groups.
• highavailability — High-availability provisioned
attribute mask, the bit set to 0 for all channels and
user-defined.
• lowlatency — Low-latency provisioned attribute
mask, the bit set to 0 for all channels and
user-defined.
Example:

prov-attrib-mask bonding bonding
ranging-backoff <0:15> Allowed start and end values for applying windowing
<0:15> to maximize the capacity of the upstream channel,
expressed as powers of two.
Example:

ranging-backoff 2 8
no ranging-backoff
Casa Systems
interface ofdma
rolloff-period <0 | 32 | The roll-off period or windowing maximizes channel

64 | 96 | 128 | 160 | 192 capacity by sharpening the edges of the spectrum of
| 256> the OFDM signal. There are eight available values,
which must be less than the cyclic-prefix. There is
no no form of the command.
Example:

rolloff-period 32
sc-spacing <25 | 50> Subcarrier spacing associated with a particular FFT

mode configured on the OFDMA upstream channel.
If it is 4K mode, the subcarrier spacing is 25 KHz. If it
is 2K mode, the subcarrier spacing is 50 KHz. An
error is returned if the spacing does not match the
configured bandwidth.
Example:

sc-spacing 25
shutdown Shuts down or (with the no form of the command)

restarts the OFDMA channel. A no shutdown
requires that at least one iuc-profile be configured
for the channel that has a data-iuc defined. The
default is shutdown.
Example:

shutdown
iuc-profile 1
no shutdown
Casa Systems
interface ofdma
symbols-per-frame <6:36> Number of symbol periods per frame. For 25-KHz or

50-KHz subcarrier spacing, the CCAP rejects
configurations where this value exceeds a certain
threshold based on the encompassed spectrum of
the OFDMA channel. An error is returned if the value
exceeds what is allowed for the current bandwidth.
Example:

symbols-per-frame 18
up-down-trap-enabled Enables a trap to be sent when the channel

transitions from up to down and from down to up. The
default is not enabled.
Example:

up-down-trap-enable
no up-down-trap-enable
voice-bw-reserve Voice bandwidth reserve percentage for the OFDMA

{<0:100> [emergency interface. When the configured percentage threshold
<0:100>] | max-calls is reached, no new voice calls are accepted on that
<0:255>} [emergency channel and any unused portion of the configured
<0:255>] percentage is available for data sessions. However,
new voice calls will assume priority and preempt any
data sessions. Additionally, you can also reserve a
portion of the configured voice bandwidth percentage
for emergency calls. The default is 75%.
Example:

voice-bw-reserve max-calls 100
CASA(config-if-ups 13/1.0)#
no voice-bw-reserve
Casa Systems
interface ofdma
Related commands
module <num> ofdma enable
Enables OFDMA on a UPS 16x8 module, which requires rebooting the module (or
enabling OFDMA on the redundancy card, which triggers rebooting). Use the no form
of the command to disable the OFDMA module. Trying to enable on a UPS_16x4
module returns an error message.
CASA(config)# module 11 ofdma enable

CASA(config)# end
CASA# reboot module 11
CASA# conf
CASA(config)# no module 11 ofdma enable
debug cable pre-equalization
Enables dumping of pre-equalization data for all non-OFDMA channels.
CASA# debug cable mac-address 0895.2a9b.2a99

CASA# debug cable pre-equalization
CASA# show debugging
Cable:
…
pre-equalization
show module [<num>] config
Shows the upstream module or modules configured with OFDMA. In this example,
there is no redundant standby (such as module 8) enabled for OFDMA redundancy.
CASA(config)# show module config

module 0: QAM256
module 1: empty
module 2: QAM8x192
module 3: empty
module 4: QAM
module 5: empty
module 8: empty
module 9: UPS
module 10: empty
module 11: UPS16x8 DOCSIS 3.1 ofdma enabled
Casa Systems
interface ofdma
show interface ofdma [<slot>/<port>.<chan> | stat | ugs statistics]

[verbose]
Shows the OFDMA upstream interface channel settings or statistics.
CASA(config)# show interface ofdma 12/1.0

exclusion-band 1
iuc-profile 1
no shutdown
CASA(config)# show interface ofdma stat

Interface ofdma 12/1.0 statistics
Admin status: UP
Channel utilization interval: 3
Avg OFDMA channel utilization: 0
Avg percent contention slots: 0
Avg percent initial ranging slots: 0
Avg percent minislots lost on late MAPs: 0
Received 222 broadcasts, 0 multicasts, 3607 unicasts
0 discards, 0 errors, 0 unknown protocol
12515 Unerroreds, 7670 Correcteds, 0 Uncorrectables
Total Modems On This Upstream Channel: 2 ,2 active cm,0 secondary cm
…
CASA(config)# show interface ofdma ugs statistics
Interface ofdma 12/0.0

Active ugs flow on the OFDMA: 0
UGS Allocation Statistics
max min avg
Last 0.3 Hour 0 0 0.00
Last 1.5 Min 0 0 0.00
Interface ofdma 12/1.0

Active ugs flow on the OFDMA: 0
max min avg
Last 0.3 Hour 0 0 0.00
Last 1.5 Min 0 0 0.00
…
show iftable ofdma
Shows OFDMA upstream interface details and current status, with up to one OFDMA
upstream channel per port.
Casa Systems
interface ofdma
CASA> show iftable ofdma

------------------------------------------------
ifIndex: 16000160
ifDescr: OFDMA Upstream 1/0.0
ifType: ifType_ofdma
ifPhysAddress: 00:00:00:00:00:00
ifAdminStatus: Up (2) ifOperStatus: Up(1)
------------------------------------------------
ifIndex: 16000161
ifDescr: OFDMA Upstream 1/1.0
…
Casa Systems
service group
service group
Purpose
The service group command sets the service group for the OFDMA upstream
binding. Once OFDMA is enabled for the DOCSIS MAC interface and service group,
the channel information is included in the MAC Domain Descriptor (MDD) message
to broadcast to the modem. The full service group configuration options are described
in Chapter 6, “Channel bonding.”
Modes
(config)#
Syntax
(config-svc-grp x)#
[no] ofdma <slot>/<port>.<chan>
Properties
<name> Service group name for OFDMA, up to 16 characters.

Up to 160 service groups are supported.
Example:
CASA(config)# service group OFDMA

CASA(conf-svc-grp OFDMA)# end
CASA(config)# no service group OFDMA
Casa Systems
service group
ofdma <slot>/ Upstream binding of the service group to a specified

<port>.<chan> OFDMA interface. Currently the channel must be set
to 0. (See the interface ofdma command.)
Example:

CASA(conf-svc-grp OFDMA)#
no ofdma 11/1.0
show service group [<name>] [verbose]
Shows the QAM channels associated with a service group, including OFDMA.
CASA(config)# show service group
service group OFDM

qam 1/1/0
qam 1/1/1
qam 1/1/2
qam 1/1/3
qam 1/1/4
qam 1/1/5
upstream 11/1.0
ofdma 11/1.0
…
Casa Systems
OFDMA configuration example

The following is a sample basic OFDMA upstream configuration, with some returned
alerts and possible error conditions indicated.
1. Enable OFDMA on the module.

CASA(config)# module 10 ofdma enable
Please reboot module 10 for the change to take effect!
2. Configure the OFDMA minislots for subcarrier groups.

CASA(conf-minislot-cfg 1)# subcarrier-group-minislot 1
5000000 11400000 modulation ?
1024qam 1024qam
128qam 128qam
16qam 16qam
256qam 256qam
32qam 32qam
512qam 512qam
64qam 64qam
8qam 8qam
qpsk qpsk
zero zero

5000000 7000000 modulation qpsk pilot-pattern ?
<1-8> pattern number
5000000 7000000 modulation qpsk pilot-pattern 1

20000000 25000000 modulation 64qam pilot-pattern 8

5000000 7000000 modulation qpsk pilot-pattern 3
Error: subcarrier group overlaps with 1
CASA(conf-minislot-cfg 1)# end
3. Configure the OFDMA Interval Usage Code (IUC) profile.

CASA(conf-IUC-profile 1)# data-iuc ?
<5,6,9,10,11,12,13> data-iuc num
Casa Systems
CASA(conf-IUC-profile 1)# data-iuc 5 modulation 8qam

pilot-pattern 2
CASA(conf-IUC-profile 1)# data-iuc 6 modulation 64qam
pilot-pattern 3
CASA(conf-IUC-profile 1)# data-iuc 9 modulation qpsk
pilot-pattern 1 minislot-cfg 4
Error: minislot cfg 4 has not been defined
CASA(conf-IUC-profile 1)# initial-ranging-iuc 128 ?

<1-100000> sum of guardband in hz
CASA(conf-IUC-profile 1)# initial-ranging-iuc 128 10000
CASA(conf-IUC-profile 1)# fine-ranging-iuc 32 10000
CASA(conf-IUC-profile 1)# end
4. Configure any OFDMA exclusion zones.

CASA(conf-ofdma-exclusion-band 1)# exclusion-sc-group 1
8000000 10000000
25000000 30000000
85000000 90000000
CASA(conf-ofdma-exclusion-band 1)# show this

ofdma exclusion-band 1
CASA(conf-ofdma-exclusion-band 1)# end
5. Configure the OFDMA interface and channel properties.

Invalid ofdma channel; only channel 0 is supported
CASA(conf-ofdma-channel 10/1.0)# show this
interface ofdma channel 10/1.0

sc-spacing 50
no preEqualizationEnable
no up-down-trap-enabled
shutdown
Casa Systems
CASA(conf-ofdma-channel 10/1.0)# no shutdown

Error: at least one data-iuc profile should be configured
CASA(conf-ofdma-channel 10/1.0)# iuc-profile 2

data-iuc profile 2 has not been configured
CASA(conf-ofdma-channel 10/1.0)# iuc-profile 1
CASA(conf-ofdma-channel 10/1.0)# lower-freq 5000000

upper-freq 99950000
Error: invalid frequency range for 50khz spacing (BW = 10 ~ 96Mhz)
from 5000000 to 99950000
CASA(conf-ofdma-channel 10/1.0)# lower-freq 5000000
upper-freq 94600000

Error: the maximum allowed value is 18 for current bandwidth 94950
Khz
CASA(conf-ofdma-channel 10/1.0)# exclusion-band 1
CASA(conf-ofdma-channel 10/1.0)# show this

sc-spacing 50
exclusion-band 1
iuc-profile 1
shutdown
CASA(conf-ofdma-channel 10/1.0)# rolloff-period ?

0 valid number
128 valid number
160 valid number
192 valid number
224 valid number
32 valid number
64 valid number
96 valid number
CASA(conf-ofdma-channel 10/1.0)# power-level ?

<0-2048> in TenthdBmV
Casa Systems
CASA(conf-ofdma-channel 10/1.0)# data-backoff ?

<0-15> backoff start
CASA(conf-ofdma-channel 10/1.0)# data-backoff 0 ?
<0-15> backoff end
automatic automatically set up
CASA(conf-ofdma-channel 10/1.0)# data-backoff 0 automatic
CASA(conf-ofdma-channel 10/1.0)# ranging-backoff 5 7
CASA(conf-ofdma-channel 10/1.0)# no shutdown
6. Configure the service group to create the upstream binding to the OFDMA
interface.
Once OFDMA is enabled for the DOCSIS MAC interface and service group, the
channel information is included in the MAC Domain Descriptor (MDD) message
to broadcast to the modem. The channel number is currently always 0.
CASA(config)# service group OFDMA
7. Show the OFDMA configuration.

CASA(conf-ofdma-channel 10/1.0)# show run | beg minislot
ofdma minislot-cfg 1
subcarrier-group-minislot 1 5000000 7000000 modulation qpsk
pilot-pattern 1
subcarrier-group-minislot 2 20000000 25000000 modulation 64qam
pilot-pattern 8
ofdma iuc-profile 1

sc-spacing 50
data-backoff 0 automatic
ranging-backoff 5 7
exclusion-band 1
iuc-profile 1
no shutdown
Casa Systems
16-1
Chapter 16. PacketCable
PacketCable commands description

The Casa CMTS supports the latest PacketCable specification from CableLabs™.
Those PacketCable features offer an end-to-end solution for traffic that originates or
terminates on a cable network, simplifying the task of providing multimedia services
over an infrastructure composed of disparate networks and media types. It also
provides an integrated approach to end-to-end call signaling, provisioning, quality of
service (QoS), security, billing, and network management.
Table 16-1 lists and briefly describes the objects related to PacketCable.
Table 16-1. PacketCable objects
packetcable Enables and configures PacketCable.
Casa Systems
packetcable
packetcable
Purpose
The packetcable command enables PacketCable and configures its properties.
Mode
(config)#
Syntax
[no] packetcable <cr>
packetcable cops ip dscp <0:63>
[no] packetcable dscp check
packetcable elemid <0:99999>
[no] packetcable ftp {newuser <name> | user password <pwd>}
[no] packetcable gate maxcount <1:196607>
packetcable inactive call aging <0:24> [minimum traffic <0:1000>]
[no] packetcable max {emerg | normal} call <0:8000>
[no] packetcable media alive time <hh:mm>
[no] packetcable mgpi
[no] packetcable multimedia [T1 <1:1000>]
[no] packetcable myaddress <ip_addr>
[no] packetcable nls {agid <0:4294967295> key <key> | cpd |
source-interface loopback <0:255>}
packetcable pepid <text>
[no] packetcable rks batchfile {max {msg <1:1000> | size <1024:65535>}
| sendmode {ftp | udp} | time <1:200>}
[no] packetcable rks retry <1:10>
[no] packetcable rks timeout <1:30>
[no] packetcable t0 <1:65535>
[no] packetcable t1 <1:65535>
[no] packetcable vrf <name>
Properties
<cr> The packetcable keyword with a carriage return

enables PacketCable operations.
Example:
CASA(config)# packetcable
CASA(config)# no packetcable
Casa Systems
PacketCable 16-3
packetcable
cops ip dscp <0:63> Sets the Differentiated Services Code Point (DSCP)
priority for the Common Open Policy Service
(COPS), up to 64.
Example:
CASA(config)# packetcable cops ip dscp

62
dscp check Enables checking of Differentiated Services Code

Point (DSCP) level of service settings in IP headers.
Example:
CASA(config)# packetcable dscp check

CASA(config)# no packetcable dscp check
elemid <0:99999> Configures an event message, with the event

message ID defaulting to 99999.
Example:
CASA(config)# packetcable elemid 99996

CASA(config)# no packetcable elemid
ftp {newuser <name> | user Configures an FTP user for PacketCable, with a
password <pwd>} username and password, default casa.
Example:
CASA(config)# packetcable ftp newuser

FTPUSER
CASA(config)# packetcable ftp user
password casa
CASA(config)# no packetcable ftp user
Casa Systems
packetcable
gate maxcount <1:196607> Maximum gate count that controls the gate scale,
default value max_cm * 3/100. If the count is larger
than 32767 (0x7fff), the system ID occupies only 15
bits instead of 17, in which case the current gates are
freed forcibly (requiring confirmation; see Example).
Example:
CASA(config)# packetcable gate maxcount

96000
This command will free all current
gates, Please type YES to confirm:
CASA(config)# no packetcable gate
maxcount
inactive call aging <0:24> Inactive call aging controls freeing of PacketCable
[minimum traffic <0:1000>] gates when service flows become inactive.
Previously, PacketCable gates remained active and
calls were not being torn down after a call ended,
consuming system resources and bandwidth. This
command sets the number of hours to pass before
tearing down a call, as well as setting an optional
minimum voice downstream throughput threshold (in
kilobits) to determine if the call session should be torn
down.
Example:
CASA(config)# packetcable inactive call

aging 4 minimum traffic 50
max {emerg | normal} call Configures maximum emergency or normal calls for
<0:8000> the CMTS, default 0 (disabled).
Example:
CASA(config)# packetcable max emergency

call 100
CASA(config)# packetcable max normal
call 0
CASA(config)#
no packetcable max normal call
Casa Systems
PacketCable 16-5
packetcable
media alive time <hh:mm> Media Alive Time is an EM message. To set the
media alive time, set the hours and minutes in the
form hh:mm.
Example:
CASA(config)# packetcable media alive

time 10:30
CASA(config)#
no packetcable media alive
mgpi Enables multiple grants per interval (MGPI) that

allows mapping of multiple PacketCable Multimedia
(PCMM) voice flows into a single DOCSIS service
flow.
Example:
CASA(config)# packetcable mgpi

CASA(config)# no packetcable mgpi
multimedia [T1 <1:1000>] Enables PacketCable Multimedia (PCMM) so that the

CMTS generates and responds to PCMM Common
Open Policy Service (COPS) commands. Once
enabled, the CMTS attempts a COPS connection
over a TCP connection to a PCMM policy server. The
optional T1 property sets a T1 timer, in seconds, that
configures the amount of time that PCMM will remain
in an authorized state.
Example:
CASA(config)# packetcable multimedia T1

100
CASA(config)# no packetcable multimedia
Casa Systems
packetcable
myaddress <ip_addr> Configures an IP address for PacketCable, in octet

format, default 0.0.0.0.
Example:
CASA(config)# packetcable myaddress

1.1.1.1
CASA(config)# no packetcable myaddress
nls {agid <0:4294967295> Configures Network Layer Signaling (NLS) for

key <key> | cpd | transporting Control Point Discovery (CPD)
source-interface loopback messages, setting the Authentication Group Identifier
<0:255>} (AGID), and the CMTS loopback interface for NLS
traffic. The options are agid, cpd, and the loopback
source-interface, as follows:
• agid <id> key <key> — Authentication Group

Identifier and key TLV to be carried over NLS
authentication message exchanges. The AGID
and variable key string must be matched for a
successful request and reply exchange.
• cpd — Specifies using Control Point Discovery
(CPD) messaging. CPD messages are carried by
the NLS protocol to media endpoints (MTAs) to
gather the IP addresses of end devices.
• source-interface loopback <0:255> — CMTS
logical interface for NLS traffic.
Example:
CASA(config)# packetcable nls cpd

CASA(config)# packetcable nls
source-interface loopback 10
CASA(config)# packetcable nls agid 124
key alpha
CASA(config)# no packetcable nls cpd
Casa Systems
PacketCable 16-7
packetcable
pepid <text> Policy Enforcement Point (PEP) ID, up to 63 bytes.

PEP is the client entity in COPS that consults with the
Policy Decision Point (PDP) to make policy decisions
or obtain policy information that it may use to make
admission control decisions. The PEP may receive
requests for service and initiate a query to the PDP
that results in a go/no-go response, or the PEP may
inform the PDP that it wants to receive decisions and
policy related information on an unsolicited basis.
Example:
CASA(config)# packetcable pepid

casa@packet.cable
rks batchfile {max {msg A batch file can be sent to the Record Keeping
<1:1000> | size Server (RKS) by UDP or FTP. The batchfile property
<1024:65535>} | sendmode sets the following parameters:
{ftp | udp} | time <1:200>}
• max msg <1:1000> — Maximum number of mes-
sages in a batch file, default 20 messages.
• max size <1024:65535> — Maximum size, in
bytes, of the event message batch file, default
65535.
• sendmode {ftp | udp} — Specified FTP or UDP
as the send mode.
• time <1:200> — Time intervals to send the batch
file to the RKS server, default 200 seconds.
Example:
CASA(config)# packetcable rks batchfile

max msg 10
max size 4096
sendmode udp
time 120
CASA(config)#
no packetcable rks batchfile time
Casa Systems
packetcable
rks retry <1:10> Set the RKS retry count, the number of times that a
RADIUS request is resent to a RKS server, default 3
retries.
Example:
CASA(config)# packetcable rks retry 6

CASA(config)# no packetcable rks retry
rks timeout <1:30> Sets the RKS timeout, the time interval that the router
waits for the RKS server to reply before
retransmitting, default 5 seconds.
Example:
CASA(config)# packetcable rks timeout 9

CASA(config)#
no packetcable rks timeout
t0 <1:65535> Configures the T0 timer, default 30 seconds.
Example:
CASA(config)# packetcable t0 30
CASA(config)# no packetcable t0
t1 <1:65535> Configures the T1 timer, default 200 seconds.
Example:
CASA(config)# packetcable t1 200

CASA(config)# no packetcable t1
vrf <name> Configures the virtual routing forwarding (VRF)

instance for PacketCable.
Example:
CASA(config)# packetcable vrf VFR1

CASA(config)# no packetcable vrf VRF1
Casa Systems
PacketCable 16-9
packetcable
show packetcable global
Shows the packet cable global parameters. Note that in Release 6.5 the PacketCable
Multimedia (PCMM) version is set to 5.0 by default.
CASA(config)# show packetcable global

**********PacketCable Global***********
PacketCable: enable
Element ID: 9999
PEP ID: casa@packet.cable
MyIPaddr: 0.0.0.0
Gate ID Used: 0
Max Gate: 19660
COPS Server Listen Port: 2126
RKS_Receive_Port: 1813
PCMM Listen Port: 3918
PCMM version: 5.0
…
show packetcable log
Shows the PacketCable event messages.
CASA(config)# show packetcable log

697
show packetcable rks server
Shows the Record Keeping Server (RKS) information.
CASA(config)# show packetcable rks server

IP Address Port Timeout Retry Batch_file File_mode File_size
File_max_msg
Casa Systems
packetcable
show packetcable gate
Shows a summary of live gates. A gate defines a resource authorization envelope

consisting of IP level QoS parameters as well as classifiers that define the scope of
service flows to be established. There can be up to 20,000 gates.
CASA(config)# show packetcable gate

GateID SubID Type State Dir PDPIP RKSIP
0xf 10.162.1.199 PCMM COMMIT down 192.168.57.145 192.168.55.49
show packetcable gateid <0:0xffffffff> {dspec | uspec}
Shows the gate specifications for a particular gate ID, downstream or upstream.
CASA(config)# show packetcable gateid 0 dspec

Packetcable gateid 0x0 downstream failed.
show packetcable commit gate
Shows the number of committed gates.
CASA(config)# show packetcable commit gate

Packetcable committed gates count is 0
show packetcable cms server
Shows the Common Open Policy Service (COPS) server IP address and listen port.
CASA(config)# show packetcable cms server

IP Address Port
show packetcable mgpi [cm <mac_addr>]
Shows the multiple grants per interval (MGPI), if enabled by the packetcable mgpi
command, with the option of specifying a particular cable modem.
CASA(config)# show packetcable mgpi
Casa Systems
17-1
Chapter 17. QAM interface
QAM channel configuration

The interface qam command configures a Quadrature Amplitude Modulation (QAM)
interface. QAM is the modulation scheme for digital cable and CMs for downstream
traffic and interfaces need to be configured for that traffic. The Casa QAM interface is
available in the following three versions:
• QAM 8x8—Eight QAM modules with each eight channels. QAM 8x8 modules
have two modes of operation: normal and high frequency. Normal mode requires
all channels on a given QAM module to be contained in the range 47–860 MHz.
High frequency mode requires all channels on a module in the range 295–
999 MHz. Each QAM module is completely independent of other modules in the
same chassis; some modules can be in high-frequency mode, while others are in
normal mode. The center frequencies for channels on the same port are correlated.
When any one is set, the others change accordingly. The center frequency of each
channel is separated by 6–8 MHz, depending on whether the QAM port is
configured as Annex type B, C, or A.
• QAM 8x96—Eight QAM modules with each 96 channels. The QAM 8x96
module supports both narrowcast and shared channels, where each of the eight
ports consists of 36 unicast channels and 12 shared channels. Shared channels are
RF channels that operate over any or all eight physical ports with up to 96 shared
channels across all ports. The QAM 8x96 module supports 352 QAM channels in
Annex B and Annex A modes — 256 channels are capable of both DOCSIS and
video traffic, plus 96 video channels capable of broadcasting over any of the RF
ports.
• QAM 8x192—Eight QAM modules with each 192 channels, with up to
64 multi-port shared (broadcast) and 64 narrowcast channels per port. The module
introduced for DOCSIS 3.1 supports up to 400 DOCSIS channels per module,
Casa Systems
QAM shared channel modes
128 multi-port shared channels per module and broadcast channels per port,
80 single-carrier channels (DOCSIS, SDV, and VOD) across eight channel
blocks, 24 Annex A/B/C channels per port operating in DVB SimulCrypt
encryption mode configured in the upper channel range, and up to two channels
per port for Orthogonal Frequency Division Multiplexing (OFDM) (SimulCrypt
allows only one OFDM channel) and one channel per port for Orthogonal
Frequency Division Multiple Access (OFDMA) over 10-Gbps downstream and
1-Gbps upstream service flows.
Note: Before hot-swapping a QAM module, use the command ha replace

linecard <module> with QAM8x192, for example. Currently the QAM 8x192
module requires the SMM 8x10G in the system chassis, and excludes the
SMM 2x10G. QAM 8x192 is not supported on the C10G platform.
Table 17-1 lists and briefly describes the objects related to the QAM interface.
Table 17-1. QAM interface objects
interface qam Configures the QAM interface.

module Introduced for QAM 8x96, defines a module and configures
narrowcast and shared channels.
QAM shared channel modes
As introduced for QAM 8x96, shared channels are in one of the two following modes,
with the system allowing a combination of the modes across an RF port:
• Extra narrowcast shared channel mode

• Multi-port shared channel mode
Extra narrowcast channel mode
In extra (sometimes called extended) narrowcast channel mode, a shared channel

emulates one of the narrowcast channels on a port. The content of this channel does
Casa Systems
QAM interface 17-3
Configuring narrowcast channels
not replicate to any other port. This mode is useful in cable environments that do not
require replication, where the shared channels are used to increase the channel density
of a port. With 96 shared channels (QAM 8x96), each of the eight RF ports can get up
to 12 extra narrowcast channels; with 128 shared channels (QAM 8x192), each of the
eight RF ports can get up to 16 extra narrowcast channels.
The number of narrowcast channels per port can range 36–48. The following
conditions apply:
• When module <id> narrowcast-channels is set to 48, all 96 channels are equally
allocated to the eight RF ports, and there are no shared channels available.
• When module <id> narrowcast-channels is set to 36, all 96 shared channels are
theoretically available for multi-port shared channels. However, because the
number of QAM channels on each RF port cannot exceed 128, there are
effectively only 128–36=92 shared channels available.
• When the system is configured for Digital Video Broadcasting (DVB)
SimulCrypt, the maximum number of possible shared channels is reduced from
96 to 64, with a resulting maximum module <id> narrowcast-channels value of
40 to indicate no available shared channels. On the QAM 8x192 module, when
enabling SimulCrypt on any QAM channel in an eight-channel block, all
remaining channels in that block are unavailable as DOCSIS channels. All
channels within the block must be SimulCrypt video channels. Up to 24 Annex A,
B, or C channels per port can operate in DVB SimulCrypt encryption mode and
must be configured at the upper numbered channel range, such as 40–63.
Multi-port shared channel mode
In this mode, the content of the channel can be replicated to all eight RF ports, for
video only. The set of downstream ports on each shared channel can be selected to
allow a subset of RF ports for shared channel replication. The RF frequency of the
shared channel must be the same on all the outgoing RF ports.
Configuring narrowcast channels
As introduced for QAM 8x96, to configure shared channels in “Extra narrowcast

channel mode” mode, use the module command in the following format:
CASA(config)# [no] module <id> narrowcast-channels <num>
Casa Systems
Configuring the shared channels for QAM 8x96 ports
The syntax, number values, and an example are described in the module command
description. The command sets the total number of narrowcast channels on the module
RF downstream port. With the number of narrowcast-channels set to more than 36, the
system places a set of shared channels into extra narrowcast mode to meet the
assigned number. The maximum value for narrowcast channels is 48, the default,
where no extra narrowcast shared channels are available.
Example
CASA(config)# module 0 narrowcast-channels 44
This command creates 44 narrowcast channels, eight channels per port in excess of the
default 36, which creates 96–[8(excess)x8]=32 shared channels across all ports. Use
the no form of the command to remove the current narrowcast-channels configuration
setting and revert to the default setting of 48 narrowcast channels. Use the show
narrowcast-channels command to display the current narrowcast channels.
CASA(config)# no module narrowcast-channels
Example
CASA(config)# show narrowcast-channels
module 4 narrowcast-channels 44
Configuring the shared channels for QAM 8x96 ports
As introduced for QAM 8x96, the shared-channel command places a shared channel
into multi-port shared channel mode (video only). Shared channels in the range 0–91
are enabled using an assigned frequency. Each shared channel frequency must be
assigned first using the following command format:
shared-channel <id> frequency <Hz> [1-32]
See the shared-channel property of the interface qam command for details. The
optional range of 1–32 is the number of channels to which the frequency applies using
a single command. Use the clear interface qam shared-channel <slot> stat
command to remove shared channel statistics.
Example
CASA(config-if-qam 0/0)# shared-channel 0 frequency 555000000
Casa Systems
QAM interface 17-5
Sharing channels over other QAM 8x96 ports
CASA(config-if-qam 0/0)# shared-channel 0 transport stream id 125
Note: If some of the shared channels are assigned to the narrowcast channel
mode, there will be less shared channels available for multi-port shared
channel mode.
Once a shared channel is created on one of the QAM 8x96 ports, it can then be shared
across up to seven additional ports on the same module.
Figure 17-1 shows a sample mapping of the eight QAM 8x96 ports where port 0
shares 12 SDV0 channels with port 1, port 2 shares SDV1 channels with port 3, port 4
shares SDV2 channels with port 5, and port 6 shares SDV3 channels with port 7.
The following CLI session configures the shared channels on port 0 and shares them
with port 1 using the following steps:
1. Configure the number of narrowcast channels on module 0 and module 1.

2. Configure the shared channel identifier on the first module and number of
channels to be shared, then configure the second and any subsequent ports using
the same shared channel identifier.
3. Execute the show module <slot> shared-channel mapping command to verify
the configuration.
4. Add multi-port shared channels to the video QAM domain and QAM group. The
qam-group command in the video qam-domain configuration supports the range
of narrowcast and multi-port shared channels.
qam-group <group-id> shared-channel
<first_shchan> <last_shchan>
where group-id is the qam group ID in the range 1–8, and first_shchan and
last_shchan specify the block of multi-port shared QAM channels.
5. Run the show docsis channel utilization command to display multi-port shared
channel statistics.
Casa Systems
Figure 17-1. Sample QAM 8x96 shared channel mappings

Narrowcast channels
Multiport shared channels
Channel number
0 15 16 31 43
Port 0 DOCSIS VOD SDV0
Shared channel IDs
0 to 11; channels 32 to 43
1 DOCSIS VOD SDV0
2 DOCSIS VOD SDV1

Shared channel IDs
3 DOCSIS VOD SDV1
4 DOCSIS VOD SDV2 Shared channel IDs

5 DOCSIS VOD SDV2
6 DOCSIS VOD SDV3 Shared channel IDs

7 DOCSIS VOD SDV3
Example


CASA(config-if-qam 0/0)# shared-channel 0 frequency 72300000 12
CASA(config-if-qam 0/0)# no shared-channel 0 shutdown 12

CASA(config)# show module 0 shared-channel mapping

PORT CHAN SH_CH FREQ(MHz) BINDP BINDC REPL-P P_MASK BLK_OFF STATUS
*****12 multiport shared-channels on QAM 0/0*****

*****12 multiport shared-channels on QAM 0/1*****
CASA(config)# video qam domain 1

CASA(conf-qam-domain 1)# qam-group 2 shared-channel 0/0 0/11
Casa Systems
QAM interface 17-7
QAM 8x96 and QAM 8x192 channel frequency range
CASA(conf-qam-domain 2)# show video qam-domain

video qam-domain 1
edis 1
video service group 1
interface video 6
qam-group 1 0/0/16 0/0/31
qam-group 2 shared-channel 0/0 0/11 <<<<==== 12 multi-port
shared-channels added to
video qam-domain.
CASA(config-if-qam 0/1)# show docsis channel utilization

Slot/Port/Channel (Mb/Sec) Percentage Modems Modems
Channel
Description
----------------------------------------------------------------------
<<<<==== Utilization on 12 multi-port shared-channels
0/0 (723000000 Hz) 42.9 49 0 0 (shared)

0/1 (729000000 Hz) 42.9 49 0 0 (shared)
0/2 (735000000 Hz) 42.9 49 0 0 (shared)
0/3 (741000000 Hz) 42.9 49 0 0 (shared)
0/4 (747000000 Hz) 42.9 49 0 0 (shared)
0/5 (753000000 Hz) 42.9 49 0 0 (shared)
0/6 (759000000 Hz) 42.9 49 0 0 (shared)
0/7 (765000000 Hz) 42.9 49 0 0 (shared)
0/8 (771000000 Hz) 42.9 49 0 0 (shared)
0/9 (777000000 Hz) 42.9 49 0 0 (shared)
0/10 (783000000 Hz) 42.9 49 0 0 (shared)
0/11 (789000000 Hz) 42.9 49 0 0 (shared)

As in earlier Release 6.4 implementations, the configuration maintains four RF
blocks. Each block covers 192 MHz width, with the four blocks covering the
768 MHz frequency range. The frequency range may not be continuous, and
frequency gaps may exist between blocks.
• In Annex B or C mode at the 6 MHz channel width, the maximum number of

channels on a single block is 32. The maximum number of Annex B or C channels
on each physical port is 128 RF channels (4 blocks x 32 channels). See
Figure 17-2.
• In Annex A mode, at the 8 MHz channel width, the maximum number of channels
on a single block is 24. The maximum number of Annex A channels on each
physical port is 96 RF channels (4 blocks x 24 channels). See Figure 17-3.
Casa Systems
Figure 17-2. QAM 8x96 channel time line frequency blocks (Annex B, C; 128 ch.)
Dynamic system-assigned default frequencies
99000000 291000000 483000000 675000000
192 MHz 192 MHz 192 MHz 192 MHz
block 0 block 1 block 2 block3
32 channels 32 channels 32 channels 32 channels
47 MHz 768 MHz 1 GHz

QAM 8x96 (Annex B/Annex C, 128 channels)
Figure 17-3. QAM 8x96 channel time line frequency blocks (Annex A; 96 ch.)
Dynamic system-assigned default frequencies
99000000 291000000 483000000 675000000
192 MHz 192 MHz 192 MHz 192 MHz
block 0 block 1 block 2 block3
24 channels 24 channels 24 channels 24 channels
47 MHz 768 MHz 1 GHz

QAM 8x96 (Annex A, 96 channels)
Example
CASA# show interface qam 0/1 block
Notes:
annex: 0-A, 1-B, 2-C; mod: 0-64qam, 1-128qam, 3-256qam;
mid: 0-not in any mode, 1-in mode 1, 2-in mode 2;
QCC_MODULE_INFO:
mode 1: annex 1 mod 3 symb 0 intlv 12801 dvb 0 ref_cnt 16 bchan_cnt 0
mode 2: annex 0 mod 0 symb 0 intlv 0 dvb 0 ref_cnt 0 bchan_cnt 0
total active bchan count: 0
interface qam 0/1:
PORT 1: power (510,420) annex 1 mod 3 sym 0 intlv (12801,12801) nd 36

nu 36 ns 92 status 1 bch_act 0
Casa Systems
QAM interface 17-9
FPGA_A: annex 1 mod 3 sym 0 intlv (12801,12801) nd 36 nu 36 ns 92

status 0 pmap 0xff
FPGA_B: annex 1 mod 3 sym 0 intlv (12801,12801) nd 36 nu 36 ns 92
status 0 pmap 0xff
block 0 freq 483000000 mask 000000ff mode_id 1 in_used 1

channel 0 freq 483000000 blk 0 off 0 mid 1 annex 1 mod 3 sym 0
intlv 12801 dvb 3 status 1
block 1 freq 0 mask 00000000 mode_id 0 in_used 0
schan_id:
4 5 6 7 8 9 10 11 12 13 14 15
16 17 18 19 20 21 22 23 24 25 26 27
28 29 30 31 32 33 34 35 36 37 38 39
40 41 42 43 44 45 46 47 48 49 50 51
52 53 54 55 56 57 58 59 60 61 62 63
64 65 66 67 68 69 70 71 72 73 74 75
76 77 78 79 80 81 82 83 84 85 86 87
88 89 90 91 0 1 2 3 255 255 255 255
shutdown channels:
…
Casa Systems
QAM 8x192 multi-port shared channels
Once a shared channel on one of the QAM 8x192 ports is created, this channel can
then be shared across one or more ports (up to seven additional) on the same module.
The following CLI session configures the video-only multi-port shared channels on
port 0 and shares them with port 1:
1. Configure the number of narrowcast channels on the QAM 8x192 in system

slot 4.
channels to be shared.
3. Configure no shared-channel shutdown for each port interface.
the configuration.
Example
CASA(config)# interface video 10

CASA(conf-if-video 10)# ip address 88.88.88.88 255.255.255.0

CASA(config-if-qam 4/0)# shared-channel 0frequency 47000000 16
CASA(config-if-qam 4/0)# show interface qam 4/0

…
shared-channel 0 frequency 47000000
no shared-channel 0 shutdown
Casa Systems
QAM interface 17-11







PORT CHAN SH_CH FREQ(MHz) BINDP BINDC BINDM ANNEX MOD SYMB REPL-P P_MASK BLK_OFF
STATUS
0 0 0 47000000 0 64 ff A 256qam 6952 255 00 0 0 up
0 1 1 55000000 0 65 ff A 256qam 6952 255 00 0 1 up
0 2 2 63000000 0 66 ff A 256qam 6952 255 00 0 2 up
0 3 3 71000000 0 67 ff A 256qam 6952 255 00 0 3 up
0 4 4 79000000 0 68 ff A 256qam 6952 255 00 0 4 up
0 5 5 87000000 0 69 ff A 256qam 6952 255 00 0 5 up
0 6 6 95000000 0 70 ff A 256qam 6952 255 00 0 6 up
0 7 7 103000000 0 71 ff A 256qam 6952 255 00 0 7 up
0 8 8 111000000 0 72 ff A 256qam 6952 255 00 0 8 up
0 9 9 119000000 0 73 ff A 256qam 6952 255 00 0 9 up
0 10 10 127000000 0 74 ff A 256qam 6952 255 00 0 10 up
0 11 11 135000000 0 75 ff A 256qam 6952 255 00 0 11 up
0 12 12 143000000 0 76 ff A 256qam 6952 255 00 0 12 up
0 13 13 151000000 0 77 ff A 256qam 6952 255 00 0 13 up
Casa Systems
0 14 14 159000000 0 78 ff A 256qam 6952 255 00 0 14 up

0 15 15 167000000 0 79 ff A 256qam 6952 255 00 0 15 up
2 0 0 47000000 0 64 ff A 256qam 6952 255 00 0 0 up

2 1 1 55000000 0 65 ff A 256qam 6952 255 00 0 1 up
2 2 2 63000000 0 66 ff A 256qam 6952 255 00 0 2 up
2 3 3 71000000 0 67 ff A 256qam 6952 255 00 0 3 up
2 4 4 79000000 0 68 ff A 256qam 6952 255 00 0 4 up
2 5 5 87000000 0 69 ff A 256qam 6952 255 00 0 5 up
2 6 6 95000000 0 70 ff A 256qam 6952 255 00 0 6 up
2 7 7 103000000 0 71 ff A 256qam 6952 255 00 0 7 up
2 8 8 111000000 0 72 ff A 256qam 6952 255 00 0 8 up
2 9 9 119000000 0 73 ff A 256qam 6952 255 00 0 9 up
2 10 10 127000000 0 74 ff A 256qam 6952 255 00 0 10 up
2 11 11 135000000 0 75 ff A 256qam 6952 255 00 0 11 up
2 12 12 143000000 0 76 ff A 256qam 6952 255 00 0 12 up
2 13 13 151000000 0 77 ff A 256qam 6952 255 00 0 13 up
2 14 14 159000000 0 78 ff A 256qam 6952 255 00 0 14 up
7 0 0 47000000 0 64 ff A 256qam 6952 255 00 255 255 up

7 1 1 55000000 0 65 ff A 256qam 6952 255 00 255 255 up
7 2 2 63000000 0 66 ff A 256qam 6952 255 00 255 255 up
7 3 3 71000000 0 67 ff A 256qam 6952 255 00 255 255 up
7 4 4 79000000 0 68 ff A 256qam 6952 255 00 255 255 up
7 5 5 87000000 0 69 ff A 256qam 6952 255 00 255 255 up
7 6 6 95000000 0 70 ff A 256qam 6952 255 00 255 255 up
7 7 7 103000000 0 71 ff A 256qam 6952 255 00 255 255 up
7 8 8 111000000 0 72 ff A 256qam 6952 255 00 255 255 up
7 9 9 119000000 0 73 ff A 256qam 6952 255 00 255 255 up
7 10 10 127000000 0 74 ff A 256qam 6952 255 00 255 255 up
7 11 11 135000000 0 75 ff A 256qam 6952 255 00 255 255 up
7 12 12 143000000 0 76 ff A 256qam 6952 255 00 255 255 up
7 13 13 151000000 0 77 ff A 256qam 6952 255 00 255 255 up
7 14 14 159000000 0 78 ff A 256qam 6952 255 00 255 255 up
7 15 15 167000000 0 79 ff A 256qam 6952 255 00 255 255 up
Example
CASA(config)# video qam-domain 1
CASA(conf-qam-domain 1)# qam-group <id> shared-channel
<first> <last>
where id is the QAM group ID in the range 1–8, and first and last are the first and
last QAM channels in the block of multi-port shared channels.

video qam-domain 1
edis 1
interface video 6
qam-group 1 0/0/16 0/0/31
shared channels added to video qam-domain
Casa Systems
QAM interface 17-13
QAM 8x192 MPTS pass-through broadcast video
QAM 8x192 MPTS pass-through broadcast video
Release 7.2 supports Multiple Program Transport Stream (MPTS) processing over
QAM 8x192 ports 0–7 where one input MPTS can be output to one QAM multi-port
shared channel. Note that PID replacement (drop and add) is supported with broadcast
video. Perform the follow steps to configure the QAM for video broadcast:
1. Configure the multi-port shared channels, including the interface video,

interface qam, and video qam domain configurations.
2. Configure the broadcast video session shared channel using the video session
<id> pass-through command with the MPTS destination and source addresses.
Create a video pass-through session on one QAM 8x192 module, then repeat the
command for additional QAM 8x192 modules. In the following example, the MPTS
broadcast video stream is configured on shared channel 4/0. The MPTS is destined for
the multicast group address at IP 227.0.0.0 and the video source IP address for the
MPTS is 17.56.102.2.
Example
CASA(config)# video session 1 pass-through ip-address 227.0.0.0
qam-channels shared-channel 4/0 src-ip 17.56.102.2
Casa Systems
interface qam
interface qam
Purpose
The interface qam command configures a Quadrature Amplitude Modulation (QAM)

interface. QAM is the modulation scheme for digital cable and CMs for downstream
traffic and interfaces need to be configured for that traffic. Warnings or informative
messages appear if changes are made to configured channels.
Modes
(config)#
(config-if-qam <slot>/<port>)#
Syntax
(config)# interface qam <slot>/<port>
(config-if-qam X/Y)#
QAM8x8: annex {A [spectral-inversion] | B | C [spectral-inversion]}
QAM8x96/192: annex {A [spectral-inversion] | B | C
[spectral-inversion]}
QAM8x96/192: channel <num> annex {A [spectral-inversion] [symbol
rate <5000:6999>] | B | C [spectral-inversion] [symbol rate
<5000:6999>]}
[no] channel <num> description “<text>”
[no] channel <num> dsg {channel-list <1:4294967295> | dcd-enable |
interval <2:10> | timer-id <1:4294967295> | vendor-param-id
<1:4294967295>}
channel <num> frequency <0 | 47000000:999000000> [<1:80>]
channel <num> interleave <level>
QAM8x96/192: channel <num> modulation {128qam | 256qam | 64qam |
off}
QAM8x96/192: channel <num> power-attenuation <0:100> [<1:80>]
channel <num> prov-attr-mask {<0x0:0xFFFFFFFF> | {[bonding]
[highavailability] [lowlatency]}}
QAM8x96/192: [no] channel <num> replicate-port <ports_list>
[<1:80>]
[no] channel <num> shutdown [<1:80>]
[no] channel <num> transport stream id <0:65535> <1:80> [inc
<1:100>]
interface qam <slot>/<port>
interleave <level>
modulation {128qam | 256qam | 64qam | off}
QAM8x192: ofdm port-exclusion-band <1:16>
QAM8x192: ofdm profile-modulation <type>
Casa Systems
QAM interface 17-15
interface qam
QAM8x192: ofdm-channel 0
power <250:620> [per-channel]
[no] shared-channel <id> {annex {A [symbol rate <5000:6999>]
[spectral-inversion] | B | C [spectral-inversion]} |
description “<text>” | frequency <0 | 47000000:999000000>
[<1:48>]| interleave <level> | modulation {128qam | 256qam |
64qam | off} | power-attenuation <0:100> [<1:96>] | shutdown
[<1:48>] | transport stream id <0:65535> [inc <1:96>]}
[no] shutdown
[no] spectral inversion on
spectrum-tilt <0:50>
[no] video 64qam-6db-backoff
Properties
<slot>/<port> Required slot and port number of the QAM interface.

The <slot> is the slot or module number and the
<port> is the port number, from 0–7.
Example:

Casa Systems
interface qam
annex {A [symbol rate QAM 8x8: Sets the QAM channel annex. There are
<5000:6999>] [channel three MPEG framing formats for a QAM channel,
spacing Annex A (Europe), Annex B (North America), and
<6000000:8000000>] | B | Annex C (Japan), described as follows:
C}
• A — Annex A describes an earlier European CM
system, for which a symbol rate and channel
spacing can be specified. The default symbol
rate is 6952 kilo-symbols per second. For the
DOCSIS channel, 6952 is the only setting. The
channel spacing default is 8000000 Hz (8 MHz).
• B — Annex B corresponds to
DOCSIS/EuroDOCSIS 1.1 and has a channel
spacing of 6 MHz. The symbol rate and channel
spacing are not options for this annex type.
• C— Annex C describes a variant of DOCSIS 1.1
that is designed to operate in Japanese cable
systems and has a channel spacing of 6 MHz.
The symbol rate and channel spacing are not
options for this annex type.
Example:
CASA(config-if-qam 0/0)# annex A symbol

rate 6952 channel spacing 8000000
Casa Systems
QAM interface 17-17
interface qam
annex {A QAM 8x96/192: Annex for all channels on the port.

[spectral-inversion] | B There are three MPEG framing formats for a QAM
| C channel, Annex A (Europe), Annex B (North
[spectral-inversion]} America), and Annex C (Japan), described as
follows:
• A — Annex A describes an earlier European CM

system. Spectral inversion can be applied.
• B — Annex B corresponds to DOCSIS/EuroDOC-
SIS 1.1 and has a channel spacing of 6 MHz. No
symbol rate or channel spacing needs to be spec-
ified.
• C— Annex C describes a variant of DOCSIS 1.1
that is designed to operate in Japanese cable
systems and has a channel spacing of 6 MHz. No
symbol rate or channel spacing needs to be spec-
ified. Spectral inversion can be applied.
With spectral inversion, the frequency, modulation,
and symbol rate are persisted.
Example:
CASA(config-if-qam 0/0)# annex A

spectral-inversion
Casa Systems
interface qam
channel <num> annex {A Annex for the particular channel, in addition to the
[spectral-inversion] annex set at the port level. The QAM 8x96/192 port
[symbol rate can have up to two different sets of symbol rates
<5000:6999>] | B | C assigned to different channels because of the
[spectral-inversion] different RF requirements of CMs and STBs.
[symbol rate
<5000:6999>]} Spectral inversion and the symbol rate can be
applied to Annex A and Annex C. The default Annex
A symbol rate is 6952 and the default Annex C
symbol rate is 5274. With spectral inversion, the
frequency, modulation, and symbol rate are
persisted.
The upper symbol rate can be increased to 6999,

which issues a warning message in the CLI output
(see the Example).
Example:
CASA(config-if-qam 0/0)# channel 0

annex A symbol rate 6999
spectral-inversion
Warning: Symbol Rate will be changed

to: 6999 Ksymbols/sec for 36 unicast
channels on port: 0/0
channel <num> Adds a channel description, maximum 64 characters

description “<text>” and embedded in quotes if spaces are included.
Example:

description “QAM 0/0 channel 1”
no channel 1 description
Casa Systems
QAM interface 17-19
interface qam
channel <num> dsg DOCSIS Set-Top Gateway (DSG) properties for the
{channel-list QAM channel. One of the following modifiers is
<1:4294967295> | required:
dcd-enable | interval
<2:10> | timer-id • channel-list <1:4294967295> — Enables send-
<1:4294967295> | ing a DSG channel-list with the frequency defined
vendor-param-id by the dsg channel-list command to the DSG
<1:4294967295>} agent in the Downstream Channel Descriptor
(DCD) message to advertise which QAMs contain
DSG tunnels and what their frequencies are, in
order to expedite bringing up the DSG client STB.
The channel-list can be applied on any QAM
channel and is not intended to indicate which STB
devices go on which channel. However, the cen-
ter frequency defined by the dsg channel-list
must be within the frequency range set for the
QAM channels enabled for DSG.
• dcd-enable — Enables the channel for DCD
messaging, required for DSG.
• interval <2:10> — Sets a downstream time inter-
val in ticks (100 milliseconds per tick), default 5.
• timer-id <1:4294967295> — Assigns a DSG
timer ID to the channel, configured using the dsg
timer-id command in configuration mode.
• vendor-param-id <1:4294967295> — Assigns a
DSG vendor parameter ID to the downstream
channel. A vendor-param-id is configured using
the dsg vendor-param-id command in configura-
tion mode.
Example:
CASA(config-if-qam 0/0)# channel 1 dsg

dcd-enable
no channel 1 dsg dcd-enable
Casa Systems
interface qam
channel <num> frequency QAM channel frequency. The default for channel 1 is
<0 | 47000000:999000000> 549000000 Hz (549 MHz). The center frequencies for
[<1:80>] the four channels on the same port are correlated.
When any one is set, the others change accordingly.
The center frequency of each channel is separated
by 6–8 MHz, depending on the annex type specified.
Changing the frequency requires shutting down the
channel first. Narrowcast and shared channels can
be configured with a frequency of 0 for unused or
disabled channels (shutdown) to avoid possible
unexpected frequencies.
Example:

frequency 549000000
channel <num> interleave QAM channel interleave level, with the possible
<level> values 8, 16, 32, 64, 128x1 (default), 128x2, 128x3,
128x4, 128x5, 128x6, 128x7, or 128x8. (See also the
interleave <level> command.)
Example:

interleave 128x8
channel <num> modulation QAM 8x96/192: Modulation rate for the specific QAM
{128qam | 256qam | 64qam output channel on the selected QAM port. The
| off} possible modulation rates are 64qam, 128qam,
256qam (default), and off. A modulation type is
required.
Example:

modulation 256qam
Casa Systems
QAM interface 17-21
interface qam
channel <num> QAM 8x96/192: Sets the power attenuation value in

power-attenuation tenths of a dBmV (.1dBmV), default 0, for a particular
<0:100> [<1:80>] channel. The second optional value determines the
range (number of successive channels starting with
the channel number) to apply the attenuation value.
The no form of the command removes any
attenuation for the channel (or the number
representing the given range of successive channels
starting with that channel number).
Example:

power-attenuation 20 8
CASA(config-if-qam 0/0)# no channel 1
power-attenuation 8
channel <num> Provisioned attribute mask for the channel. DOCSIS

prov-attr-mask 3.x provisioned attribute masks allow assigning of
{<0x0:0xFFFFFFFF> | service flows to channels or channel bonding groups
{[bonding] using binary attributes. These attributes are either
[highavailability] user-defined or specification-defined. At least one of
[lowlatency]}} the following values is required:
• <val> — User-defined value, default 0x0.

user-defined.
user-defined.
Example:

prov-attr-mask 0x0
Casa Systems
interface qam
channel <num> Replicates the channel configuration to other

replicate-port specified ports on the current QAM slot. The ports in
<ports_list> [<1:80>] the list are separated by commas and include
hyphens to indicate ranges, such as 1,5-7 to indicate
ports 1, 5, 6, and 7. The optional number of channels
value applies to QAM 8x96/192 boards only. Note
that the number of channels plus half the number of
channels to replicate times the number of ports for
replication must be less than or equal to 48.
Example:

replicate-port 1,5-7
no channel 1 replicate-port 1,5-7
channel <num> shutdown Shuts down the channel. The optional number of
[<1:80>] channels designation applies to QAM 8x96/192
boards only.
Example:

shutdown 36
Casa Systems
QAM interface 17-23
interface qam
channel <num> transport The channel transport stream ID is needed in Service

stream id <0:65535> Information (SI) table generation. The SI table
<1:80> [inc <1:100>] contains four sub-tables: EIT (Event Information
Table), NIT (Network Information Table), SDT
(Service Description Table), and TDT (Time of Day
Table), each of which can be turned on or off
individually. The inc property sets the increment of
the IDs, such as 2 to skip every second number (such
as 1, 3, 5, etc).
Example:

transport stream id 500
no channel 1 transport stream id
interface qam <slot>/ Opens another QAM interface.

<port>
Example:
CASA(config-if-qam 0/0)# interface qam

2/1
interleave <level> QAM port interleave level to minimize the effect of

burst noise by spreading data over time, with the
possible values 8, 16, 32, 64, 128x1, 128x2, 128x3,
128x4, 128x5, 128x6, 128x7, or 128x8. 128x1 is the
default and highest amount of interleaving, and 8 is
the lowest. All channels on the port are automatically
set to the same interleave level. The interleave level
can also be set for a specific channel (see the
channel <num> interleave <level> property). For
Annex A, the interleave is fixed at 12 and cannot be
changed.
Example:
CASA(config-if-qam 0/0)# interleave

128x1
Casa Systems
interface qam
modulation {128qam | Modulation rate for all QAM output channels on the
256qam | 64qam | off} selected QAM port. The possible modulation rates
are 64qam, 128qam, 256qam, and off, the default
256qam.
Example:
CASA(config-if-qam 0/0)# modulation

256qam
ofdm port-exclusion-band QAM 8x192: Sets the ID of the subcarrier exclusion

<1:16> band on the port level for Orthogonal Frequency
Division Multiplexing (OFDM). See the full description
in Chapter 14, “Orthogonal Frequency Division
Multiplexing.”
Example:

CASA(config-if-qam 4/0)# ofdm
port-exclusion-band 1
no ofdm port-exclusion-band 1
Casa Systems
QAM interface 17-25
interface qam
ofdm profile-modulation OFDM profile’s modulation type. The types are as

<type> follows:
• 16qam
• 64qam
• 128qam
• 256qam
• 512qam
• 1024qam
• 2048qam
• 4096qam
• zero
Example:
ofdm-channel 0 QAM 8x192: Sets OFDM parameters on channel 0.

See the full description of all available command
parameters in Chapter 14, “Orthogonal Frequency
Division Multiplexing.”
Example:

no ofdm-channel 0
Casa Systems
interface qam
power <250:620> Output power level for all QAM channels per QAM
[per-channel] port, in .1dBmV, default 510. The actual channel
output level depends on how many channels are
enabled on the port. The power setting is the sum of
all enabled QAM channels on the same port, except if
the per-channel modifier is used to set the power
value at the channel level.
The per-port max output power levels (.1dBmV):
• 620: <= 1 channel

• 610: = 2 channels
• 600: => 3 and <= 8 channels
• 590: => 9 and <= 32 channels
• 580: => 33 and <= 64 channels
• 570: => 65 and <= 128 channels
• 560: => 129 channels
The measureable per-channel max output power

levels (in dBmV), which can be hardware-adjusted:
• 60: 1 channel/port
• 56: 2 channels/port
Setting the port power level more than 580 is not
recommended unless the actual CMTS output shows
as slightly lower than what is requested in the CLI, or
when the cable plant is highly attenuated and the
only solution is to force the CMTS to overdrive its
output level (instead of removing attenuation).
Example:
CASA(config-if-qam 0/0)# power 510
Casa Systems
QAM interface 17-27
interface qam
shared-channel <id> Shared channel ID for the QAM interface, with the
{annex {A [symbol rate following properties:
<5000:6999>]
[spectral-inversion] | B • annex {A [spectral-inversion] | B | C [spec-
| C tral-inversion]}, along with the optional symbol
[spectral-inversion]} | rate for Annex A.
description “<text>” | • description “<text>” — Description for the
frequency <0 | shared channel, up to 64 characters.
47000000:999000000>
[<1:48>]| interleave • frequency <47000000:999000000> — Narrow-
<level> | modulation cast and shared channels can also be configured
with a frequency of 0 for unused or disabled
{128qam | 256qam | 64qam
(shutdown) channels to avoid possible unex-
| off} |
pected frequencies.The optional 1–48 value indi-
power-attenuation
cates the number of channels to apply the
<0:100> [<1:96>] | incrementing frequencies to, default 48.
shutdown [<1:48>] |
transport stream id • interleave <level>
<0:65535> [inc <1:96>]} • modulation {128qam | 256qam | 64qam | off}
• [no] power-attenuation <0:100> [<1:96>] — See
the channel version of this property for a full
description.
• [no] shutdown [<1:48>] — This operation must
be specified. The optional 1–48 value indicates
the number of channels to start up or shut down.
• transport stream id <0:65535> — An ID of 0
removes the transport stream. The inc property
sets the increment of the IDs, such as 2 to skip
every second number (such as 1, 3, 5, etc).
With spectral inversion,only one channel is changed
if the port or configured channel is down, otherwise
all active broadcast channels are changed.
Example:
CASA(config-if-qam 0/0)# shared-channel

1 frequency 549000000
no shared-channel 1
Casa Systems
interface qam
shutdown Shuts down the QAM port. This command can also
be performed for a specific channel (see the channel
<num> shutdown [<1:80>]) command. The default
state for all QAM ports and channels is shutdown.
This prevents interference with existing
cable-channel configurations. If the QAM port is
disabled, enabling the individual channel will have no
effect until the QAM port is enabled. The no form of
the command restarts the interface.
Example:
CASA(config-if-qam 0/0)# shutdown

CASA(config-if-qam 0/0)# no shutdown
spectral inversion on Turns on spectral inversion for the QAM interface. All
parts of the command are required. Spectral
inversion inverts the orientation of the signal
bandwidth with respect to the carrier frequency, a
feature that is turned off by default. Turning spectral
inversion off requires the no form of the command.
Example:
CASA(config-if-qam 0/0)# spectral

inversion on
no spectral inversion on
Casa Systems
QAM interface 17-29
interface qam
spectrum-tilt <0:50> Adjusts each channel’s power as an integer value

based on the channel’s position in the frequency
spectrum. A channel’s power normally decreases at
higher frequencies. Spectrum tilt compensates by
gradually increasing power at the higher end. At the
default tilt value of 0, all channels have the same
power level. The power level difference between
active channels cannot exceed 10 dB over the full
spectrum (the 50–1000 MHz span). If not the full
spectrum, use the following formula to calculate the
spectrum-tilt setting to be entered:
N * 1000
<channel_span>
N is the decibel tilt to be achieved over the spectrum.

For example, for a desired 10-dB tilt over a channel
frequency span of 402 MHz (460–862 MHz), the
setting would be calculated as follows:
10/402 * 1000 = 24.8 = 25 dB integer value
Thus the smaller the spectrum span, the smaller the

desired tilt must be to stay within the value range.
Example:
CASA(config-if-qam 0/0)# spectrum-tilt

25
video 64qam-6db-backoff Triggers power attenuation by 6 dB when changing

channel modulation from 256QAM to 64QAM. The
no form of the command removes the attenuation
(the default).
Example:
CASA(config-if-qam 0/0)# video

64qam-6db-backoff
no video 64qam-6db-backoff
Casa Systems
si generator tot
Generates a Service Information (SI) table for the Time Offset Table (TOT). The
Time Offset Table (TOT) carries the UTC time and date information as well as the
local time offset. It is transmitted in TS packets with a PID value of 0x0014 and a
table ID of 0x73. The command can take the following additional parameters:
• country-code <3_char_code> region-id <0:60>

• dst begin month <1:12> week <|1:5> time <0:3>
• dst end month <1:12> week <|1:5> time <0:3>
• offset-hours <–12:+13> offset-minutes <0 | 30 | 45>
CASA(config)# si generator tot country-code cet region-id 0

CASA(config)# si generator tot dst begin month 4 week 1 time 2
CASA(config)# si generator tot dst end month 10 week 5 time 2
CASA(config)# si generator tot offset-hours 5 offset-minutes 30
CASA(config)# no si generator tot
CASA(config)# no si generator tot dst
show interface qam [brief]
Shows the QAM interfaces channel frequencies and shutdown status. The basic
version of the command also shows the associated properties and any shared channels,
which the brief version of the command does not.
CASA# show interface qam
interface qam 0/0

no spectral inversion on
annex B
modulation 256qam
interleave 128x1
power 510
channel 0 shutdown
channel 1 shutdown
…
Casa Systems
QAM interface 17-31
show interface qam [<slot>/<port>[/<chan>]] stat
Shows the QAM channel statistics. If the channel is specified, it must currently be set
to 0.
CASA# show interface qam stat

Interface qam 0/0 statistics
Admin Status: DOWN
Channel 0
TotalBytes:0
UsedBytes :0
Admin Status: DOWN
Last clearing of interface stat: never
Channel 1
TotalBytes:0
UsedBytes :0
Admin Status: DOWN
…
show interface qam <slot>/<port> power
Shows the QAM channel power settings for a specified port, including any spectrum
tilt effects. B_POWER is the calculated power before the tilt factor (which gradually
decreases towards the higher end of the frequencies) is subtracted; T_POWER
(B_POWER minus TILT) and CH_POWER show the true channel power.
CASA# show interface qam 0/0 power
Configured Total Power: 510

Calculated Per-Channel Power: 359
Send to FPGA Power: 510
Spectrum-tilt: 37
Power adjusted: 471
CHAN_ID FREQUENCY ATTNU B_POWER TILT T_POWER CH_POWER

0 474000000 0 359 96 263 263
1 482000000 0 359 93 266 266
2 490000000 0 359 90 269 269
3 498000000 0 359 87 272 272
4 506000000 0 359 84 275 275
5 514000000 0 359 81 278 278
6 522000000 0 359 77 282 282
7 530000000 0 359 74 285 285
8 538000000 0 359 71 288 288
…
Casa Systems
show interface qam <slot>/<port> fpga
Shows the QAM field-programmable gate array (FPGA) parameters. For output of the
show interface qam <x/y> block command, see the “Example” on page 8.
CASA# show interface qam 0/0 fpga

Mode 1 ref cnt 64 (used by bchan 0): Annex 0 Mod 3 Sym R 6952 Intlv 12
Mode 2 ref cnt 0 (used by bchan 0): Annex 0 Mod 0 Sym R 0 Intlv 0
Thread: Timer: 50 Tick: 50
Port admin : Up
Port power : 510
Port power tilt : 0
Port power adjusted: 510
total chan up: 8
…
show dsg channel-list
Shows any configured DSG channel lists.
CASA# show dsg channel-list

show dsg qam
Shows the QAM interfaces configured with DSG.
CASA# show dsg qam

interface qam 0/0
interface qam 0/1
…
show dsg running-config
Shows the DSG lines in the running-configuration.
CASA# show dsg running-config

dsg tunnel-group 1
channel 2 qam 0/1/0 rule-priority 1
dsg tunnel 1
group 1
…
Casa Systems
QAM interface 17-33
module
module
Purpose
The module command sets a number of module properties. The channel-id-offset,

narrowcast-channels, and ofdm-channels settings require the module ID, while the
ofdma enable setting does not.
Mode
(config)#
Syntax
[no] module <id> channel-id-offset <1:63>
[no] module <id> narrowcast-channels {<32:96> | <32 | 40 | 48 | 56 |
64>}
[no] module <id> ofdm-channels <1:2>
[no] module <id> ofdma enable
Properties
<id> Module ID, which must be a QAM module.

channel-id-offset <1:63> A module-specific override of the more general
video channel-id-offset command. The valid range
is 1, or N – 64 if N is greater that 64, through N – 1,
where N is the number of narrowcast channels.
Example:
CASA(config)# module 0
channel-id-offset 48
CASA(config)#
no module 0 channel-id-offset
Casa Systems
narrowcast-channels Number of narrowcast channels in the given range,

{<32:96> | <32 | 40 | 48 default 48. In two-OFDM channel mode, the values
| 56 | 64>} are at the given distinct intervals.
Example:
CASA(config)# module 0
narrowcast-channels 48
CASA(config)#
no module 0 narrowcast-channels
ofdm-channels <1:2> OFDM channels per port, either 1 (the default) or 2.

See Chapter 14, Orthogonal Frequency Division
Multiplexing, for details.
Example:
ofdma enable Enables OFDMA on a UPS 16x8 module. See

Chapter 15, Orthogonal Frequency Division Multiple
Access, for details.
show narrowcast-channels
For QAM 8x96/192, shows the narrowcast channel configuration.
CASA# show narrowcast-channels

show controller qam [<slot>]
Shows QAM interface status and statistics. Other options include specifying a
particular slot.
Casa Systems
QAM interface 17-35
CASA# show controller qam 9

Interface QAM 9/0
Admin Status: UP
Power level: 490
Channel 0:
IfIndex : 3002592
Admin Status : UP
Operating Status : UP
Frequency : 705000000
Channel Width : 6000000
Modulation : 256QAM
Annex: : B
Statistics:
Broadcast packets : 248929
Multicast packets : 0
Unicast packets : 18000
UCD counts : 191624
MAP counts : 5092868
…
show module <num> qam-mode [summary]
Shows the QAM modes for the module and its ports. There can be up to three QAM
modes for a QAM 8x192 module, two for unicast and one for broadcast (the one with
the positive ref_cnt). The second broadcast mode (bc_mode 2) is used only in per
channel interleave mode where all the module channels have the same annex,
modulation, and symbol rates, and vary only between two interleave values. The
summary option shows the same output in table format.
CASA# show module 1 qam-mode
Module 1:
uc_mode 1: annex A modulation 256qam interleave 12 symbol_rate 6952
ref_cnt 24
ref_cnt 24
bc_mode 1: annex A modulation 256qam interleave 12 symbol_rate 6900

ref_cnt 8
bc_mode 2: annex B modulation 256qam interleave 128x1 symbol_rate 0
ref_cnt 0
Port 0:
admin status: UP
total channel up: 28
number uchan up: 24
number bchan up: 4
uchan in mode 1: 12
Casa Systems
uchan in mode 2: 12
bchan in mode 1: 4
bchan in mode 2: 0
default mode: annex A modulation 256qam interleave 12
symbol_rate 6952
other mode: annex B modulation 256qam interleave 128x1
symbol rate 0
…
CASA# show module 1 qam-mode summary
Module 1:
ref_cnt 24
ref_cnt 24
bc_mode 1: annex A modulation 256qam interleave 12 symbol_rate 6900

ref_cnt 8
bc_mode 2: annex B modulation 256qam interleave 128x1 symbol_rate 0
ref_cnt 0
PORT ADMIN T_UP UC_UP BC_UP UC_M1 UC_M2 BC_M1 BC_M2 DEF_ANN DEF_MOD
DEF_ITL DEF_SYM OTH_ANN OTH_MOD OTH_ITL OTH_SYM
0 UP 28 24 4 12 12 4 0 Annex_A 64qam
12 6952 Annex_B 256qam 128x1 0
1 DOWN 0 0 0 0 0 0 0 Annex_B 256qam
128x1 0 Annex_B 256qam 128x1 0
2 DOWN 0 0 0 0 0 0 0 Annex_B 256qam
128x1 0 Annex_B 256qam 128x1 0
3 DOWN 0 0 0 0 0 0 0 Annex_B 256qam
128x1 0 Annex_B 256qam 128x1 0
4 DOWN 0 0 0 0 0 0 0 Annex_B 256qam
128x1 0 Annex_B 256qam 128x1 0
5 UP 28 24 4 12 12 4 0 Annex_A 256qam
12 6952 Annex_B 256qam 128x1 0
6 DOWN 0 0 0 0 0 0 0 Annex_B 256qam
128x1 0 Annex_B 256qam 128x1 0
7 DOWN 0 0 0 0 0 0 0 Annex_B 256qam
128x1 0 Annex_B 256qam 128x1 0
Casa Systems
18-1
Chapter 18. Quality of service
QoS commands description

The Casa CMTS supports quality of services (QoS) as defined by the DOCSIS 1.0, 1.1
specifications. Service classes can be configured to support the QoS profile number,
traffic priority, maximum upstream bandwidth, guaranteed upstream bandwidth,
maximum downstream bandwidth, maximum transmit burst length, baseline privacy
enable/disable, and type of service (ToS) overwrite byte. (See the cable service-class
command for service class definitions and also Chapter 2, “Application classes and
policies.”)
QoS support in DQM modules
The DOCSIS QAM Module (DQM) provides QoS support through a two-level
hierarchical scheduler. The top level is priority based, and the second level is a fair
scheduler based on round robin. Each packet destined for a downstream interface is
assigned a service flow through classification by the DOCSIS forwarding engine. The
scheduler in the DQM module supports a minimum guaranteed rate and a maximum
transmitted rate. Packets are serviced in the order of priority specified by the service
flow. A service flow that is within minimum guaranteed rate is served first. Within the
same priority, round robin is used to schedule between different service flows, unless
service flow weighted fair queuing (WFQ) is enabled.
If the service flow has a minimum guaranteed rate and the current rate is within the
one specified, the packet is queued in the guaranteed class that has the highest priority.
The packet is subsequently rate limited through a token bucket to conform to the
maximum transmitted rate specified for the service flow. Packets that exceed the
maximum transmitted rate are rate-shaped by deferring their transmission. Packets are
Casa Systems
QoS support in DCU modules
dropped only if the buffer utilization is high and the buffer usage by the service flow is
above the drop threshold.
The packet scheduler is driven by availability of transmission opportunities on the

downstream channel. The scheduler can provide millisecond level latency guarantees
for high priority traffic through the use of shallow transmit queues. Every time a
channel transmit queue becomes available, the scheduler services the service flows in
the order of priority until the transmit queue is full or all eligible packets are serviced.
For downstream channel bonding operation, the service flow is serviced by each of the
channels in the bonding channel set in parallel.
QoS support in DCU modules
In the DOCSIS Control and Upstream (DCU) module, the upstream scheduler handles
modem transmission opportunities. In addition to providing minimum guaranteed rate
and rate limiting support, it also provides jitter guarantees for jitter-sensitive services,
such as unsolicited grant service (UGS). The hierarchical upstream scheduler serves
upstream service flows based on priority. Jitter-sensitive service flows are serviced
first, followed by service flows that are within its guaranteed rate. Best effort service
flows are then serviced in the order of priority. Within each priority, the service flows
are serviced by a round robin scheduler.
For best effort services, the minimum guaranteed rate is checked first. If the
transmission rate of the service flow is within its specified guaranteed rate, the request
is placed in the guaranteed queue, which is serviced before other best effort queues. A
token bucket is used to rate-limit the service flow within its configured maximum
transmission rate and maximum burst size. Requests that exceed the maximum
transmission rate are deferred. Requests that conform to the maximum transmission
rate are placed into the queue determined by the priority of the service flow.
Jitter-sensitive service flows are scheduled by the real-time scheduler. To provide

jitter guarantees, the transmission opportunities are pre-allocated when the service
flow is admitted to prevent overlap. At MAP generation time, the real time scheduler
aggregates jitter-sensitive grants into clusters. The best effort grants are then placed
into the gaps between the real time grant clusters. If the gap is not big enough, the
cluster is allowed to move to increase the gap, as long as jitter guarantees can be met
for the real time grants in the cluster. If the gap is still not enough to place the best
effort grant, the best effort grant is then fragmented. The scheduler keeps track of the
Casa Systems
Quality of service 18-3
QoS support in switch fabric and Gigabit Ethernet interfaces
remainder of the fragments and continues to serve the fragments until the request is
fulfilled.
For service flows that are serviced by upstream channel bonding, the service flow is
inserted into multiple queues, one for each of the upstream channels in the bonding
channel set. The service flow is serviced by each of the upstream channels until all the
outstanding bytes requested are served.
The switch fabric connects to the RF modules and Gigabit Ethernet interfaces. Each of
the fabric ports supports eight classed-based queues. The scheduler in the switch
fabric is straight priority. For packets entering the switch fabric from the DCU
module, the priority is determined by the priority value in the upstream service flow.
For packets entering the switch fabric from Gigabit Ethernet interfaces, the priority is
from the 802.1p field if the packet is VLAN-tagged. For untagged packets, the DSCP
value in the IP header is used to determine the priority. The filtering engine can be
used to overwrite the DSCP value using access list. The priority value can also be
modified based on access lists.
To prevent head-of-line blocking, the switch fabric keeps track of the outstanding
buffer count and packet count for each of the ingress ports and each of the classes.
When an egress port on the switch fabric becomes congested, a packet is discarded at
ingress if the outstanding buffer count or packet count from the ingress port exceeds
the discard threshold for the class it belongs to.
Table 18-1 lists and briefly describes the objects related to QoS.
Table 18-1. QoS objects
cable qos Configures the cable QoS. (See Chapter 4, “Cable

commands.”)
cable service-class Configures the cable service class. (See Chapter 4, “Cable
commands.”)
Casa Systems
Table 18-1. QoS objects (continued)
cops pdp-ip Sets the address of the Policy Decision Point (PDP) for the
Common Open Policy Service (COPS).
qos-profile Configures a QoS profile.
Casa Systems
cops pdp-ip
cops pdp-ip
Purpose
The cops pdp-ip command sets the address of the Policy Decision Point (PDP) for the
Common Open Policy Service (COPS). The COPS protocol is part of the internet
protocol suite as defined by RFC 2748. COPS specifies a simple client/server model
for supporting policy control over Quality of Service (QoS) signaling protocols (such
as the Resource Reservation Protocol). Policies are stored on servers, and acted upon
by PDPs and are enforced on clients, known as Policy Enforcement Points (PEPs).
There are two models of COPS: the Outsourcing Model and the Provisioning Model,
considered from the view of the client or PEP. The COPS IP address must be in the list
of trusted addresses, or the incoming connection is denied.
The show packetcable cms server command shows the COPS server IP address and
listen port.
Mode
(config)#
Syntax
[no] cops pdp-ip <ip_addr>
Properties
<ip_addr> IP address of the Policy Decision Point (PDP), in

A.B.C.D format.
Example:
CASA(config)# cops pdp-ip 192.168.8.8

CASA(config)# no cops pdp-ip
CASA(config)#
no cops pdp-ip 192.168.8.8
Casa Systems
cops pdp-ip
show pcmm ps server
Shows the PacketCable Multimedia (PCMM) configuration with the COPS server
address, port, and version, if a trusted server.
CASA# show pcmm ps server

IP Address Port PSID Version
24.114.21.102 56275 null 5.0
show packetcable gate
Shows a summary of PacketCable live gates, including the PDP IP.
CASA(config)# show packetcable gate

GateID SubID Type State Dir PDPIP RKSIP
0xf 10.162.1.199 PCMM COMMIT down 192.168.57.145 192.168.55.49
Casa Systems
qos-profile
qos-profile
Purpose
The qos-profile command creates a QoS profile with upstream and downstream
bandwidth settings.
Mode
(config)#
Syntax
[no] qos-profile <1:10000> <0:7> <0:100000000> <0:100000000>
<0:100000000> {true|false} <0:65535>
Properties
<1:10000> Profile index.

<0:7> Priority setting.
<0:100000000> Maximum upstream bandwidth.
<0:100000000> Guaranteed upstream bandwidth.
<0:100000000> Maximum downstream bandwidth.
{true|false} Determines if the Baseline Privacy Interface (BPI) is
used, true or false.
<0:65535> Maximum transmit burst, in bytes.
Example:
CASA(config)# qos-profile 1 7 10000000

100000000 100000000 true 65535
CASA(config)# no qos-profile 1
Casa Systems
qos-profile
cable qos
The cable qos command sets QoS options for the CM.
CASA(config)# cable qos class ds 7 weight 100
multicast group config

qos-id
The qos-id property of the multicast group config command configures the QoS for
the replication of the sessions matching the group configuration.

multicast group qos
The multicast group qos command configures the QoS for a multicast group.
show qos-profile
Shows the QOS profile configuration.
CASA(config)# show qos-profile

index = 10
Casa Systems
qos-profile
show cable modem qos
Shows the CM QoS configuration.
CASA(config)# show cable modem qos

Sfid Dir Curr Sid Sched Prio MaxSusRate MaxBrst MinRsvRate
State Type (kbps) (kbps)
PeakTrafRate Throughput ServiceClassName
(kbps)) (kbps)
Mac Addr : 0026.24a8.db36
16385 US act 1 BE 0 0 24480 0
0 0
245 DS act N/A UNDEF 0 0 24480 0
0 0
Casa Systems
19-1
Chapter 19. Spectrum management
Spectrum management commands description

Casa Spectrum Management (CSM) allows the Casa CMTS to monitor the quality of
upstream paths and automatically perform correcting actions when upstream plant
impairments are detected. The monitored upstream plant impairments include Signal
to Noise Ratio (SNR), correctable Forward Error Corrections (FECs), and
uncorrectable FECs. The automatic corrections include frequency hopping, upstream
channel-width adjustment, and dynamic upstream modulation profile changes. CSM
also provides a means to report the configurations, actions, and some test facilities.
Some considerations when using CSM include the following:
1. A spectrum map is a collection of frequency ranges where a target frequency can

be selected when performing frequency hopping for an upstream channel. It is
dynamic (calculated when it is used) and upstream-interface-specific. It is
calculated based on two factors. First, by frequency ranges specified in a given
spectrum rule. Second, by current frequencies used by other upstream channels in
the same service group. You can give a large frequency range and let CSM take
care of it without concerns about frequency overlapping.
2. A discrete frequency in a spectrum rule can be viewed as a frequency band with a
given center frequency and current channel width.
3. There is no frequency back-hopping when a channel's impairments disappear;
only modulation and channel width roll-backs.
4. A meaningful order of modulation profiles specified for dynamic modulation
profile change is the order of bandwidth efficiency (or reliability), most efficient
first and most reliable last.
Casa Systems
Spectrum management commands description
5. If the configured channel width differs from the starting high channel width in a
spectrum rule, the high channel width governs in the rule. For example, if the
configured channel width is 3.2MHz and chan-width 6400000 800000 is in the
rule, when a channel width adjustment occurs, it changes to 1.6 MHz (anything
less is unsupported for upstream 16x8 modules). When it recovers, it tries from
6.4 MHz (the high end) first, then the lower width.
6. The show interface upstream x/y and show running-config commands show
configurations, but not necessarily the current configuration of an upstream
interface. If CSM is in use, use show interface upstream x/y current and show
spectrum hop-history upstream x/y[.lchan-1].
7. CSM has a built-in default SNR threshold for each modulation type. To view
them, use the show spectrum snr-threshold-default command. CSM can work
without an SNR threshold for a modulation profile specified in a spectrum rule;
that is, using the default SNR threshold. However, a corrective action will not take
place due to low polled SNR.
8. There can be up to three action command items in the spectrum rule, unless CM
mode is in effect, where only one of two (channel-width or modulation) can be
specified. There is no default action. CSM will attempt a corrective (or
improvement) action in the order specified in the command. However, this does
not guarantee the action takes place. It is important to know how the action helps
before performing it. If an action does not help, it attempts the next one. The most
common reason for an action not helping is that the calculated SNR for that action
does not satisfy the SNR threshold for a modulation profile.
9. A spectrum rule can be Fast Fourier Transform (FFT) or CM mode. An FFT mode
rule can be applied on an upstream physical channel, which means that it
functions on logical channel 0. An FFT rule cannot be applied specifically on
logical channel 0; it can be applied specifically on logical channel 1, but it does
not allow for frequency hops, because the frequency is shared between the logical
channels. A CM mode spectrum rule can be applied (and takes effect) on a logical
channel only. If both physical and logical channels of an interface have spectrum
rules applied, the logical channel rule takes priority.
10. If you want to change configuration based on modulation profile or channel width
(whatever you want CSM to manage), remove the spectrum rule from the channel
first, and put the spectrum rule back in the channel list after the configuration
change. This avoids a conflict between the manual change and CSM control.
Casa Systems
Spectrum management 19-3
Frequency hop case study
Frequency hop case study
If CSM cannot find a frequency to hop to, it will not hop, even if the current frequency
is too noisy to support modems. For example, if there is noise at 31 MHz on interface
5/1/0, then it should perform a frequency hop. There can be multiple steps in the
hopping. However, if the spectrum map is as follows:
CASA(config)# show spectrum-map upstream 8/1

interface upstream 8/1/0
band 0: [28000000, 32800000]
band 1: [36000000, 38400000]
band 2: [41600000, 42000000]
…
There is nowhere to hop to avoid the noise. The three bands (0-2) are too narrow to
escape the noise. When CSM tries a hop (frequency, modulation, or channel width), it
checks if the calculated SNR at the destination (new freq, etc.) is good enough to
accommodate the SNR threshold (280, in this case). If so, hopping is performed.
Otherwise, it tries the next action. In this example, there is no other action.
However, if the 8/4 frequency is moved to 45MHz (away from 25+1.6=26.6 MHz) to
give channel 8/1 more room, as in the following:
spectrum rule 2
frequency band 26000000 42000000
action frequency
Then move channel 8/1 back to 30 MHz (resetting the CSM state machine at
channel 8/1), and apply the rule 2 to upstream 8/1, to acquire:
CASA(config-if-ups 8/1)# show spectrum-map upstream 8/1

interface upstream 8/1/0
band 0: [26000000, 32800000]
band 1: [36000000, 38400000]
band 2: [41600000, 42000000]
…
When the CSM poll reaches a threshold, the channel hops to freq 27.6 MHz, as
indicated by the following debug message:
[Wed Dec 2 21:26:18 2009]-DE-CSM-FSM-1: H -> R on 8/1/0.. freq hop

30000000 to 27600000
Casa Systems
CSM configuration examples
Example 1: Modulation and channel width

spectrum rule 1
action modulation channel-width
correctable-fec threshold 3
uncorrectable-fec threshold 1
profile 3 snr-threshold 280

spectrum-rule 1
…
logical-channel 0 profile 3 secondary-profile 12,22,30,33
Example 2: Frequency, channel width, and modulation

spectrum rule 20
frequency 60000000
action frequency channel-width modulation

spectrum-rule 20
…
logical-channel 0 profile 10 secondary-profile 20
Example 3: CM mode spectrum rule applied on a logical channel

spectrum rule 2
cm-mode
cm-mode tolerance-count 15
cm-mode backhop-count 5
action channel-width

logical-channel 0 spectrum-rule 2
logical-channel 0 channel-width 3200000
Casa Systems
Table 19-1 lists and briefly describes the objects related to spectrum management.
Table 19-1. Spectrum management objects
channel-utilization-interval Sets the interval over which the channel utilization

information is collected and averaged.
hop period Sets the time period between two consecutive
frequency hops.
spectrum Configures spectrum management
spectrum analysis Configures spectrum analysis.
spectrum monitor-interface Sets the spectrum upstream interface to monitor.
spectrum rule Configures spectrum rules.
spectrum scheduler Configures the spectrum scheduler.
test cable hop upstream Tests cable upstream hops.
test cable hop-cm-mode Tests cable upstream hops for a CM mode
upstream spectrum rule.
Casa Systems
Purpose
The channel-utilization-interval command sets the interval over which the channel
utilization information is collected and averaged.
Mode
(config)#
Syntax
channel-utilization-interval <0:86400>
Properties
<0:86400> Channel utilization interval, default 30 seconds.

Setting this value to 0 turns off utilization collection. It
is not advisable to use a value lower than 10 in an
operational system.
Example:
CASA(config)#
show channel-utilization-interval
Shows the channel utilization interval.
CASA(config)# show channel-utilization-interval

channel utilization interval = 5 s
Casa Systems
hop period
hop period
Purpose
The hop period command sets a time period between two consecutive frequency
hops. This period allows new channels to stabilize before making a frequency hopping
decision to assign the traffic to cleaner upstream channels. The default hop period is
every 30 seconds. (This command may be replaced by the cable spectrum
hop-period command.)
Mode
(config)#
Syntax
hop period <5:3600>
Properties
<5:3600> Hop period, default 30 seconds.
Example:
CASA(config)# hop-period 30
show cm-hop log
Shows the CM frequency hop history for the CM addresses.
CASA(config)# show cm-hop log

Mac address Time Upstream CFEC UFEC SNR
-----------------------------------------------------------------
total: 0;
Casa Systems
hop period
show spectrum hop-history [upstream <slot>/<port>.<chan>[/<lchan>]]
Shows the spectrum hop history. The Code column shows the abbreviations M
(modulation), C (channel-width), or F (frequency). Filtering can also be by upstream
interface. The last column in the example shows that CM mode is in effect. CM 16
(15) means that 16 modems suffered a hop-down, based on a tolerance-count
threshold (15). CM 7 (15-3) shows a subsequent back-hop of seven modems, which is
less than 12, the tolerance-count (15) minus the backhop-count (3). Use the clear
spectrum hop-stats upstream command to reset the statistics counter.
CASA(config)# show spectrum hop-history upstream 10/0.3/1

Port Action Time Code From To Reason
10/0.3/1 Tue Mar 25 19:54:16 2014 C 800000 1600000 CM 7 (15-3)
10/0.3/1 Tue Mar 25 19:47:31 2014 C 1600000 800000 CM 16 (15)
show spectrum hop-stats service-group <name> [channel-width |

modulation] [time-info]
Shows the spectrum hop statistics for a service group. Additional qualifiers can be
channel-width, modulation, and time-info. Channels without spectrum management
rules or where monitoring is not active appear simply as the channel and logical
channel (such as 10/8.1/1: in the example). The associated MIB is the
clabTopoFiberNodeCfgNodeName object type in the DOCSIS CLAB-TOPO-MIB.
CASA(config)# show spectrum hop-stats service-group 1
current time: Fri Oct 30 07:54:08 2015
10/8.1/0: hop counts: M 2 C 0 F 0, monitored: 0d 0h 11m

MODULATION(%): PREVIOUS CURRENT
qpsk 16qam 8qam 32qam 64qam 128qam 64qam
0 6 0 0 31 0 62
CHAN-WIDTH(%): PREVIOUS CURRENT
200k 400k 800k 1.6m 3.2m 6.4m 3200000
0 0 0 0 0 0 100
10/8.1/1:
10/8.2/0: hop counts: M 12 C 0 F 0, monitored: 0d 0h 11m
MODULATION(%): PREVIOUS CURRENT
qpsk 16qam 8qam 32qam 64qam 128qam 16qam
25 31 37 0 0 0 5
CHAN-WIDTH(%): PREVIOUS CURRENT
200k 400k 800k 1.6m 3.2m 6.4m 3200000
0 0 0 0 0 0 100
Casa Systems
spectrum
spectrum
Purpose
Casa Spectrum Management (CSM) allows the Casa CMTS to monitor the quality of
upstream paths and automatically perform corrective actions when upstream plant
impairments are detected. The monitored upstream plant impairments include Signal
to Noise Ratio (SNR), correctable Forward Error Corrections (FECs), and
uncorrectable FECs. The automatic corrections include frequency hopping, upstream
channel-width adjustment, and dynamic upstream modulation profile changes. CSM
also provides a means to report the configurations, actions, and some test facilities.
Modes
(config)#
(conf-rule x)#
(conf-sched x)#
Casa Systems
spectrum analysis
spectrum analysis
Purpose
The spectrum analysis command is Spectrum Measurement DOCSIS 3.x compliant.

A CLI command is used to show the measured results. Note that the measurement
must be triggered through a MIB setting by creating a table entry for the
docsIf3CmtsSpectrumAnalysisMeasTable for an upstream channel.
Mode
(config)#
Syntax
[no] spectrum analysis full-spectrum
spectrum analysis measurement-interval <5:30>
Properties
full-spectrum With the analysis property, the Casa CMTS displays

full-spectrum data in the same MIB entry and same
format, which, in turn, can be used for the same
purpose. Note that this property alway displays
40960000, which is the center frequency of the full
spectrum.
Example:
CASA(config)# spectrum analysis

full-spectrum
CASA(config)#
no spectrum analysis full-spectrum
measurement-interval <5:30> Seconds to allow for spectrum analysis, default

15 seconds.
Example:
CASA(config)# spectrum analysis

measurement-interval 10
Casa Systems
show spectrum impair-flag
Shows the currently impaired upstream spectrum.
CASA(config)# show spectrum impair-flag

Port channels
2/ 0: 0 0 0 0 0 0 0 0
2/ 1: 0 0 0 0 0 0 0 0
2/ 2: 0 0 0 0 0 0 0 0
2/ 3: 0 0 0 0 0 0 0 0
2/ 4: 0 0 0 0 0 0 0 0
…
show spectrum snr-threshold-default
Shows the spectrum signal-to-noise ratio (SNR) threshold defaults.
CASA(config)# show spectrum snr-threshold-default

Default SNR threshold per modulation type (tenth dB):
QPSK: 130
8QAM: 190
16QAM: 220
32QAM: 250
64QAM: 280
128QAM: 310
show spectrum upstream <slot>/<port>[.<chan>] [chan-width <freq>] [raw]
Shows an upstream interface’s spectrum noise level results in dBmV at a channel

width of 3200000. The chan-width option allows you to evaluate the channel width
frequency at 400000, 800000, 1600000, 3200000, or 6400000 Hz, with the raw
modifier showing the results in dB instead of dBmV.
CASA(config)# show spectrum upstream 13/0

FREQUENCY NOISE-LEVEL at channel-width 3200000

(dBmV)
5000000: -42.1 8200000: -42.1
11400000: -42.1 14600000: -42.1
17800000: -42.1 21000000: -42.1
24200000: -42.1 27400000: -42.1
30600000: -42.1 33800000: -42.1
Casa Systems
37000000: -42.1 40200000: -42.1

43400000: -42.1 46600000: -42.1
49800000: -42.1 53000000: -42.1
56200000: -42.1 59400000: -42.1
62600000: -42.1
…
show spectrum-map upstream <slot>/<port>[.<chan>]
Shows an upstream interface’s spectrum map. The spectrum map is a collection of

possible frequency slots for the frequency hopping operation to target. The map is
dynamic for each upstream channel, and depends on the frequency ranges defined in
the rule and the current frequency used by other channels in the same service group.
CASA(config)# show spectrum-map upstream 13/2.0

Spectrum Map for interface 13/2.0
band 0: [5000000, 18400000]
band 1: [21600000, 40000000]
show spectrum-meas upstream <slot>/<port>[.<chan>]
Shows spectrum measurement results for a specified upstream channel. The

measurement must be triggered through a DOCSIS-IF3-MIB
docsIf3CmtsSpectrumAnalysisMeasAmplitudeData setting for an upstream
channel. The output shows the data in the same MIB entry and format, which, in turn,
can be used for the same purpose. The spectral amplitudes are shown as a sequence of
two-byte hexadecimal elements in relation to the expected received signal power, in
units of 0.01 dB (EF 8E representing -42.1 dB, F1 E8 representing -36.8 dB).
CASA(config)# show spectrum-meas upstream 11/3.0

11/3.0 (0) Spectrum MEAS data (in Hz):
chan cnter freq: 40960000
frequency span: 81920000
number of bins: 1024
resolution bw: 80000
bin spacing: 80000
EF 8E EF 8E EF 8E EF 8E EF 8E EF 8E EF 8E EF 8E EF 8E EF 8E EF 8E
EF 8E EF 8E EF 8E EF 8E EF 8E EF 8E EF 8E EF 8E EF 8E EF 8E EF 8E
EF 8E EF 8E EF 8E F1 E8 F1 E8 F1 E8 F1 E8 F1 E8 F1 E8 F1 E8 F1 E8
…
Casa Systems
spectrum monitor-interface
spectrum monitor-interface
Purpose
The spectrum monitor-interface command sets the upstream interface to monitor to

display with the show spectrum monitor-interface command.
Mode
(config)#
Syntax
[no] spectrum monitor-interface <slot>/<port>.<phy_chan>
Properties
<slot>/<port>.<phy_chan> Upstream interface to monitor.
Example:
CASA(config)# spectrum
monitor-interface 11/0.1
CASA(config)#
no spectrum monitor-interface 11/0.1
show spectrum monitor-interface [<slot>/<port>.<chan>]
Shows status and other statistics for the configured monitor interfaces.
CASA(config)# show spectrum monitor-interface

ENTRY MONITOR-INTERFACE INTERVAL STATUS
----- ----------------- -------- ------
1 3/0.0/0 30 Secs ACTIVE
Casa Systems
spectrum rule
spectrum rule
Purpose
Casa Spectrum Manager (CSM) uses the Fast Fourier Transform (FFT) technique to
monitor signal quality on the return path. The FFT screening results, signal-to-noise
ratio (SNR) and Forward Error Correction (FEC) errors in particular, are the main
error events monitored to determine whether plant noise exists and corrective actions
are necessary. Corrective actions can be one, two or all three of frequency hopping,
channel width adjustment, and dynamic modulation profile change.
CSM also provides cable modem (CM) mode management in place of FFT mode
management, if specified via the cm-mode property. CM mode uses the upstream
SNR of a group of CMs to determine the overall quality of the upstream channel. The
CSM approach is tolerance control, that is, how many CMs to tolerate on a particular
channel that suffer low signal quality. CSM polls the CMs, counts how many on a
logical channel have a lower-than-threshold SNR, and may perform a channel hop
when this count is exceeded. In CM mode, roll-back provisions are also included
based on the tolerance. FFT mode and CM mode spectrum rules can be applied to
upstream interfaces in any valid combination, except that CM mode rules must be
applied on logical channels. The roll-back SNR conditions (whether using modulation
profile defaults or explicitly defined) are the same for CM mode and FFT mode.
The following rules apply to using FFT and CM mode spectrum rules on physical and
logical upstream interface channels:
• An FFT mode rule applied on a physical channel functions on logical channel 0.

• An FFT mode rule cannot be applied specifically on logical channel 0.
• An FFT mode rule applied specifically on logical channel 1 functions on that
logical channel, but does not allow for frequency hops, because the frequency is
shared between the two logical channels.
• A CM mode rule must be applied on a logical channel only.
• If both a physical and logical channel of an interface have a rule applied, the
logical channel rule takes effect.
Casa Systems
spectrum rule
The following conditions apply only to CM mode spectrum rules:
• A CM mode rule must be applied on a logical channel only.

• A CM mode rule can use only one of two actions, modulation or channel-width.
CSM maintains a list of discrete channel frequencies and/or one or more frequency
bands for each upstream interface as frequency hopping targets. This is called a
spectrum map. CSM scans through the spectrum map to select the cleanest channel.
The spectrum map is updated when a hop is performed. CSM uses spectrum rules to
manage the corrective actions. A spectrum rule consists of a set of thresholds and a
sequential list of actions. An action can be frequency hopping, channel width
adjustment, or modulation profile. An FFT or CM mode procedure is triggered when a
monitored indicator to an upstream interface hits a defined or default threshold.
The actions take place in an order defined by the operator in the action commands. If
plant signal quality is maintained within the thresholds due to one or more actions, the
subsequent actions in a rule are not performed, because they are not necessary. If the
upstream channel signal with corrected modulation and/or adjusted channel width
returns to 3 dB above normal, the spectrum manager may roll back the settings to their
original channel width or modulation profile setting. The back-hop threshold can also
be specified in the CLI. To activate CSM on specified upstream interfaces, spectrum
rules need to be defined and assigned on the interfaces.
Modes
(config)#
(conf-rule x)#
Syntax
(config)# [no] spectrum rule <1:64>
(conf-rule x)#
action {channel-width | frequency | modulation | scheduler <1:16>}
back-hop-limit <1:16> <1:144> [channel-width | modulation]
no back-hop-limit
channel-width <high> <low>
no channel-width
[no] cm-hop
cm-mode [backhop-count <3:10> | backhop-delay <1:100> |
modulation-immediate | tolerance-count <4:100>
no cm-mode
correctable-fec threshold <0:100> [1000]
Casa Systems
spectrum rule
[no] frequency <5000000:100000000>

[no] frequency band <5000000:99800000> <5200000:100000000>
profile <1:1024> snr-threshold <.1dB> [<.1dB>]
no profile <1:1024>
uncorrectable-fec threshold <0:30> [1000]
Properties
<1:64> Configures a spectrum rule to apply to a service flow

over an upstream channel. There can be up to 64
rules.
Note: Frequency hopping occurs only if a

frequency band is specified in a spectrum
rule. A modulation profile change occurs
only if a secondary profile is defined in the
upstream channel. A channel-width
adjustment occurs only if a channel width
range is specified.
Example:
CASA(config)# spectrum rule 1

CASA(conf-rule 1)# exit
CASA(config)# no spectrum rule 1
Casa Systems
spectrum rule
action {channel-width | Specifies the order of effort of trying corrective

frequency | modulation | actions for FFT mode, or only one action for CM
scheduler <1:16>} mode. There is no default action or default order of
actions. For FFT mode, the following frequency
hopping priorities are set by the order they appear on
the command line:
• channel-width
• frequency (FFT mode only)
• modulation
A modulation action requires a secondary profile for
the logical channel in the interface upstream
definition. The spectrum scheduler ID can also be
specified separately for rule scheduling.
Example:
CASA(conf-rule 1)# action frequency

modulation channel-width
back-hop-limit <1:16> Sets the maximum number of previous spectrum

<1:144> [channel-width | hops (<1:16>) to occur over given 10-minute periods
modulation] (<1:144>) to prevent spectrum flip-flopping, based on
channel-width and modulation, or each individually.
In the example, a maximum of three spectrum
back-hops can occur over a 20-minute (2x10) period,
based on channel width only. If the current condition
does not represent an improved spectrum hop, no
action is taken over that time period.
Example:
CASA(conf-rule 1)# back-hop-limit 3 2

channel-width
CASA(conf-rule 1)# no back-hop-limit
Casa Systems
spectrum rule
channel-width <high> Sets the required channel width adjustment range,

<low> with a high width followed by a low width. The high
width is in the Hertz interval 400000, 800000,
1600000, 3200000, or 6400000. The low width is in
the Hertz interval 400000, 800000, 1600000, or
3200000, and should be less than or equal to the
high width. If the specified high width is larger than
the current effective width, the channel-width change
starts from the high width. Otherwise, the change
starts from the current effective width.
Example:
CASA(conf-rule 1)# channel-width

3200000 1600000
CASA(conf-rule 1)# no channel-width
cm-hop Enables CM hopping. When multiple logical channels

are configured with different modulation profiles in an
upstream physical channel and a cm-hop command
is issued, a CM can be moved among the channels
based on specified thresholds. If the thresholds
specified are exceeded for the CM, it will move to the
next (more reliable) logical channel.
Example:
CASA(conf-rule 1)# cm-hop

CASA(conf-rule 1)# no cm-hop
Casa Systems
spectrum rule
cm-mode [backhop-count Enables CM mode instead of Fast Fourier Transform

<3:10> | backhop-delay (FFT) mode and sets the CM parameters:
<1:100> |
modulation-immediate | • <cr> — Enables CM mode, required for setting
tolerance-count <4:100> the following parameters.
• backhop-count <3:10> — Causes a backhop
(roll-back of a spectrum rule action) to occur
when conditions improve if the polled number of
CMs with a lower-than-threshold SNR is less than
the tolerance-count minus this value, default 3.
• backhop-delay <1:100> — Minimum waiting
time in polling cycles to delay a backhop
(roll-back of a spectrum rule action), default 1
polling cycle. Adjust the polling cycle using the
cable spectrum cm-mode-monitor-period
command (default 45 seconds).
• modulation-immediate — Immediately hops to
the proper modulation profile based on the SNR.
Without this modifier, CM mode cascades through
all available modulation profiles.
• tolerance-count <4:100> — Maximum number
of tolerated CMs on the upstream channel that
are detected with lower-than-threshold SNR
during a polling, default 15 CMs. A higher number
can trigger the specified spectrum rule action.
Example:
CASA(conf-rule 1)# cm-mode

CASA(conf-rule 1)# cm-mode
backhop-count 3
CASA(conf-rule 1)# no cm-mode
Casa Systems
spectrum rule
correctable-fec Only correctable or uncorrectable FEC are possible

threshold <0:100> [1000] triggers to start a corrective action. The correctable
FEC threshold is set as a percentage, default 3%.
Specify smaller thresholds in 0.1% units by adding
the 1000 option.
Example:
CASA(conf-rule 1)# correctable-fec

threshold 5
description “<text>” Adds a description for the spectrum rule, maximum

64 characters in a quoted string.
frequency Sets a discrete frequency for the rule, in Hz. After the
<5000000:100000000> spectrum rule is assigned to an upstream interface,
the discrete frequency becomes a frequency band
with the same width as that of the upstream interface.
Example:
CASA(conf-rule 1)# frequency 34000000

CASA(conf-rule 1)#
no frequency 34000000
frequency band Sets a frequency band for the rule, in Hz, with a value
<5000000:99800000> for the left edge and a value for the right edge of the
<5200000:100000000> spectrum.
Example:
CASA(conf-rule 1)# frequency band

14000000 20000000
CASA(conf-rule 1)# no frequency band
14000000 20000000
Casa Systems
profile <1:1024> Applies a modulation-profile signal-to-noise ratio

snr-threshold <.1dB> (SNR) threshold, in tenths of a dB. To prevent SNR
[<.1dB>] from triggering a possible corrective action for a
particular modulation profile, do not specify the SNR
threshold for the modulation profile or set it to 0. The
optional additional number is the roll-back SNR
threshold.
CSM has a built-in default SNR threshold for each

modulation type and for each modulation profile. See
the show spectrum snr-threshold-default
command in the “Related show commands.”
Example:
CASA(conf-rule 1)# profile 3

snr-threshold 0
CASA(conf-rule 1)# no profile 3
uncorrectable-fec The uncorrectable FEC threshold is set as a

threshold <0:30> [1000] percentage, default 1%. Specify smaller thresholds in
0.1% units by adding the 1000 option.
Example:
CASA(conf-rule 1)# uncorrectable-fec

threshold 0
interface upstream
spectrum-rule
The spectrum-rule property of the interface upstream command applies a spectrum

rule to the upstream interface.

CASA(conf-service-class 1)# spectrum-rule 1
Casa Systems
interface qam
spectral inversion on
The spectral inversion on property of the interface qam command turns on spectral
inversion for the QAM interface

CASA(config-if-qam 0/0)# spectral inversion on
show spectrum rule [<id> | brief]
Shows the cable spectrum settings and spectrum rules, including any CM mode
settings. Filtering can be by rule ID or more brief output.
CASA(config)# show spectrum rule

cable spectrum hop period 30
cable spectrum monitor-period 10
cable spectrum cm-mode-monitor-period 10
spectrum analysis full-spectrum
spectrum rule 1
cm-hop
spectrum rule 35
cm-mode
cm-mode modulation-immediate
action modulation
profile 8 snr-threshold 190 220
show spectrum snr-threshold-default
Shows the spectrum SNR threshold defaults. CSM has a built-in default SNR
threshold for each modulation type and for each modulation profile. The default SNR
threshold takes effect for a spectrum rule if there is no threshold specified in a
spectrum rule for a particular modulation profile.
Casa Systems
CASA# show spectrum snr-threshold-default

Default SNR threshold per modulation type (tenth dB):
QPSK: 130
8QAM: 190
16QAM: 220
32QAM: 250
64QAM: 280
128QAM: 310
Casa Systems
spectrum scheduler
spectrum scheduler
Purpose
The spectrum scheduler command applies a start and end time to spectrum rules.
When enabled, the spectrum rule is in effect to applied channels over the scheduled
time period. When disabled, the rule is not in effect over the specified time periods,
but the rule is enabled during the other configured times. By default, and without any
start and end time, the spectrum rule is scheduled at all times for the applicable
channels. There can be up to 16 scheduler IDs.
Modes
(config)#
(conf-sched x)#
Syntax
[no] spectrum scheduler <1:16>
(conf-sched x)#
time-action <1:8> {always | {{mon | tue | wed | thu | fri | sat |
sun} <hh:mm>} {mon | tue | wed | thu | fri | sat | sun}
<hh:mm>}} {channel width | frequency | modulation}
no time-action <1:8>
Properties
<1:16> Scheduler ID.
Example:
CASA(conf)# spectrum scheduler 1

CASA(conf-sched 1)# exit
CASA(conf)# no spectrum scheduler 1
description “<text>” Adds a description for the spectrum scheduler,

maximum 64 characters in a quoted string.
Casa Systems
spectrum scheduler
time-action <1:8> Determines the time-action for the scheduler, which

{always | {{mon | tue | takes a priority value, meaning that multiple
wed | thu | fri | sat | time-action statements can be made, up to eight.
sun} <hh:mm>} {mon | tue When enabled, the spectrum rule is in effect to the
| wed | thu | fri | sat | applied channels over the scheduled time period.
sun} <hh:mm>}} {channel When disabled, the rule is not in effect over the
width | frequency | specified time periods, but is enabled during the other
modulation} configured times. By default, and without any start
and end time, the spectrum rule is scheduled at all
times for the applicable channels. The action is
always, or a start and end day-of-week (in a
3-character code plus hour and minutes, for each).
The final modifiers indicate if the action should be
based on channel width, frequency, or modulation, or
they can be combined.
Example:
CASA(conf-sched 1)# time-action 1 mon

08:00 fri 20:00 frequency
CASA(conf-sched 1)# time-action 2
always frequency modulation chan-width
CASA(conf-rule 1)# action scheduler 1
CASA(conf)# spectrum scheduler 1
CASA(conf-sched 1)# no time-action 1
show spectrum scheduler
Shows the spectrum scheduler setup.
CASA(config)# show spectrum scheduler

spectrum scheduler 1
time-action 1 mon 08:00 fri 20:00 frequency
Casa Systems
test cable hop upstream
test cable hop upstream

Purpose
The test cable hop upstream command tests the upstream cable hop for a particular
interface.
Mode
(diag)#
Syntax
test cable hop upstream <slot>/<port>.<chan>/<lchan>
Properties
<slot>/<port>.<chan>/ Upstream interface identifier (see the

<lchan> interface upstream command). The logical channel
is required. Logical channel 1 can be specified for an
FFT mode spectrum rule.
Example:
CASA# diag
Password:
CASA(diag)# test cable hop upstream
13/0.0/0
no spectrum rule on the channel or less
than hop period since last hop on
13/0.0/0
Casa Systems
test cable hop-cm-mode upstream
test cable hop-cm-mode upstream

Purpose
The test cable hop-cm-mode upstream command tests the upstream cable hop for a
CM mode spectrum rule for a particular interface by simulating an upstream poll
based on the polled number of low SNR modems and the corresponding spectrum rule
at the channel.
Mode
(diag)#
Syntax
test cable hop-cm-mode upstream <slot>/<port>.<chan>/<lchan> <1:100>
<1:64>
Properties
<slot>/<port>.<chan>/ Upstream interface identifier (see the

<lchan> <1:100> <1:64> interface upstream command). The logical channel
is required. The values that follow are the number of
simulated modems with low SNRs suffering from
hops, followed by the spectrum rule ID.
Example:
CASA# diag
Password:
CASA(diag)# test cable hop-cm-mode
upstream 13/0.0/0 10 3
a simulated threshold hit in cm-mode is
sent to 13/0.0/0
Casa Systems
20-1
Chapter 20. Subscriber management
Subscriber management commands description

Casa CMTS supports Subscriber Management features defined in DOCSIS 3.x.
Subscriber management allows a CMTS operator to control the IP addresses and
protocols associated with subscribers’ cable modems.
Table 20-1 lists and briefly describes the objects related to subscriber management.
Table 20-1. Subscriber management objects
docsis submgt default Configures the subscriber management default settings

docsis submgt filters Removes all subscriber management IP and TCP/UDP
clear-all filters
docsis submgt ip-filter Sets filter rules for DOCSIS subscriber management.
Casa Systems
docsis submgt default

Purpose
The docsis submgt default command sets the subscriber management default settings
from the CMTS if the modem configuration file does not specify otherwise. The
packet filter group ID in each case refers to the docsis submgt ip-filter value.
Mode
(config)#
Syntax
docsis submgt default active {off | on}
docsis submgt default cm-filter-downstream <0:1024>
docsis submgt default cm-filter-upstream <0:1024>
docsis submgt default cpe-filter-downstream <0:1024>
docsis submgt default cpe-filter-upstream <0:1024>
docsis submgt default learnable {off | on}
docsis submgt default max-ip <0:1023>
docsis submgt default max-ipv6-iapd <0:1023>
docsis submgt default max-ipv6-prefix <0:1023>
docsis submgt default mta-filter-downstream <0:1024>
docsis submgt default mta-filter-upstream <0:1024>
docsis submgt default ps-filter-downstream <0:1024>
docsis submgt default ps-filter-upstream <0:1024>
docsis submgt default stb-filter-downstream <0:1024>
docsis submgt default stb-filter-upstream <0:1024>
Properties
active {off | on} Turns DOCSIS subscriber management on or off.

The default is off.
Example:
CASA(config)# docsis submgt default

active off
Casa Systems
Subscriber management 20-3
cm-filter-downstream Packet filter group ID to be applied to CM

<0:1024> downstream traffic, default 0 (no associated filter).
Example:

cm-filter-downstream 0
cm-filter-upstream <0:1024> Packet filter group ID to be applied to CM upstream

traffic, default 0 (no associated filter).
Example:

cm-filter-upstream 0
cpe-filter-downstream Packet filter group ID to be applied to downstream

<0:1024> traffic to CPE devices, default 0 (no associated filter).
Example:

cpe-filter-downstream 0
cpe-filter-upstream Packet filter group ID to be applied to upstream traffic

<0:1024> from CPE devices, default 0 (no associated filter).
Example:

cpe-filter-upstream 0
learnable {off | on} Allows the CM to learn its IP address. The default is
on.
Example:

learnable on
Casa Systems
max-ip <0:1023> Maximum number of CPE IP addresses that can be

allowed for each CM connected to the CMTS, default
maximum 16.
Example:

max-ip 16
max-ipv6-iapd <0:1023> Maximum number of IPv6 IA_PDs (Identity

Associations for Prefix Delegation) allowed for the
CM's CPEs if not signaled during the registration
process. Because this attribute only counts IA_PDs
against the default, IA_NA addresses and link-local
addresses are not counted against this default limit.
The default is 3 IA_PDs.
Example:

max-ipv6-prefix 16
max-ipv6-prefix <0:1023> Maximum number of IPv6 prefixes that can be

allowed for each CM connected to the CMTS, default
16 prefixes.
Example:

max-ipv6-prefix 16
mta-filter-downstream Packet filter group ID to be applied to downstream

<0:1024> traffic to Multimedia Terminal Adapter (MTA) devices,
default 0 (no associated filter).
Example:

mta-filter-downstream 0
Casa Systems
mta-filter-upstream Packet filter group ID to be applied to upstream traffic

<0:1024> from MTA devices, default 0 (no associated filter).
Example:

mta-filter-upstream 0
ps-filter-downstream Packet filter group ID to be applied to downstream

<0:1024> traffic to Portal Server (PS) devices, default 0 (no
associated filter).
Example:

ps-filter-downstream 0
ps-filter-upstream <0:1024> Packet filter group ID to be applied to upstream traffic

from PS devices, default 0 (no associated filter).
Example:

ps-filter-upstream 0
stb-filter-downstream Packet filter group ID to be applied to downstream

<0:1024> traffic to Set-Top Box (STB) devices, default 0 (no
associated filter).
Example:

stb-filter-downstream 0
stb-filter-upstream Packet filter group ID to be applied to upstream traffic

<0:1024> from STB devices, default 0 (no associated filter).
Example:

stb-filter-upstream 0
Casa Systems
clear cable subscriber-usage [<mac_addr> | docsis-mac <id>]
Clears cable subscriber usage data.
CASA# clear cable subscriber-usage 2476.7d98.bd08 docsis-mac 1
Casa Systems
show docsis submgt default
Shows the default DOCSIS subscriber management settings.
CASA(config)# show docsis submgt default

docsis submgt default active off
docsis submgt default max-ip 16
docsis submgt default max-ipv6-prefix 16
docsis submgt default learnable on
docsis submgt default cm-filter-downstream 0
docsis submgt default cm-filter-upstream 0
docsis submgt default cpe-filter-downstream 0
docsis submgt default cpe-filter-upstream 0
docsis submgt default ps-filter-downstream 0
docsis submgt default ps-filter-upstream 0
docsis submgt default mta-filter-downstream 0
docsis submgt default mta-filter-upstream 0
docsis submgt default stb-filter-downstream 0
docsis submgt default stb-filter-upstream 0
show cable subscriber-usage
Shows the cable subscriber usage. This command depends on a cable traffic-policy
being defined. (See Chapter 4, “Cable commands.”)
Casa Systems
docsis submgt filters clear-all

Purpose
The docsis submgt filters clear-all command removes all subscriber management IP
and TCP/UDP filters in the system. The command requires a confirmation response.
Mode
(config)#
Syntax
Are you sure? (yes/no)
Clearing all submgt filters...
Casa Systems
docsis submgt ip-filter

Purpose
The docsis submgt ip-filter command sets a filter rule for DOCSIS subscriber
management to control IP packet forwarding to and from each CM, at the CMTS.
Each modem can be afforded a different subscriber management treatment. Filtering
criteria are maintained through SNMP at the CMTS. There can be up to 1500
subscriber management filters.
In addition to classifying traffic based on L2/L3/L4 fields in the packet headers,

upstream traffic can be classified based on which CM interface received the packet.
The CM interface mask (CMIM) encoding provides a bit mask representing the
inbound interfaces of the CM for which this classifier applies. Each bit of the CM
interface mask corresponds to an interface, logical or physical. By convention, bit
position 0 corresponds to the CM’s IP stack, even though it is not an actual interface.
This is configured with the cm-intf-mask property.
Mode
(config)#
Syntax
docsis submgt ip-filter <1:1024> <1:65535> {accept | deny}
docsis submgt ip-filter <1:1024> <1:65535> {accept | deny}
[cm-intf-mask <0:ffffff>] [dst-ip <ip_addr> <mask> | dst-ipv6
<ipv6_addr>] [dst-port <0:65535> <0:65535>] [protocol <0:257>]
[src-ip <ip_addr> <mask>] [src-ipv6 <ipv6_addr>] [src-port
<0:65535> <0:65535>] [tos <0:255> <0:255> <0:255> [cm-intf-mask
<0:ffffff> | dst-port <0:65535> <0:65535> | protocol <0:257> |
src-port <0:65535> <0:65535>]]
no docsis submgt ip-filter <1:1024> <1:65535>
Properties
<1:1024> IP filter group ID.

<1:65535> IP filter index, which allows multiple filter settings for
a group, with the CMTS considering the first matched
instance.
Casa Systems
{accept | deny} Allows the packet to pass (accept), or drops the

packet (deny). All further filter settings are optional.
Example:
CASA(config)# docsis submgt ip-filter

10 330 accept
CASA(config)#
no docsis submgt ip-filter 10 330
cm-intf-mask <0:ffffff> CM interface mask (CMIM), a bitmask. For example,

a CMIM classifier intended to match all the CPE ports
(external interfaces) of a CM has a CMIM setting of
bit 1 (400000) plus bits 5–15 (07FF00), an encoding
of 47FF00 when combined. The encodings are as
follows:
• Bit 0 (800000) — CM’s IP stack.

• Bit 1 (400000) — Primary CPE Interface (also
ePS or eRouter).
• Bit 2 (200000) — RF interface.
• Bits 3 and 4 — Reserved.
• Bits 5–15 (07FF00) — Other CPE Ports.
• Bit 16 (000080) — PacketCable-eMTA.
• Bit 17 (000040) — eSTB-IP.
• Bit 18 (000020) — Reserved.
• Bits 19–31 (001FFF) — Other eSAFE interfaces.
dst-ip <ip_addr> <mask> Destination IP address and mask, in the form
A.B.C.D. Other filter settings can follow.
dst-ipv6 <ipv6_addr> Destination IPv6 address and prefix, in the form
xxxx:xxxx::xxxx/yy. Other filter settings can follow.
dst-port <0:65535> Destination TCP/UDP low and high port numbers.
<0:65535> Only the cm-intf-mask setting can follow.
protocol <0:257> Protocol number. Other filter settings can follow.
src-ip <ip_addr> <mask> Source IP address and mask, in the form A.B.C.D.
Other filter settings can follow.
Casa Systems
src-ipv6 <ipv6_addr> Source IPv6 address and prefix, in the form

xxxx:xxxx::xxxx/yy. Other filter settings can follow.
src-port <0:65535> Source TCP/UDP low and high port numbers. Other
<0:65535> filter settings can follow.
tos <0:255> <0:255> <0:255> Type of service (ToS), low, high, and mask. Other
[cm-intf-mask <0:ffffff> | filter settings can follow.
dst-port <0:65535>
<0:65535> | protocol
<0:257> | src-port
<0:65535> <0:65535>]
show docsis submgt ip-filter
Shows the IP filters for DOCSIS subscriber management. An accept appears as the
number 1 in the output.
CASA(config)# show docsis submgt ip-filter

Group Index Accept UIP TOSlo TOShi TOSMask Src Port Dst Port Hit Cnt
1 1 1 256 0 100 255 0 65535 0 65535 0
1 2 1 256 0 255 0 255 256 335 336 0
Casa Systems
21-1
Chapter 21. Upstream interface
Upstream interface commands description

The interface upstream command configures an upstream interface. Upstream ports
are physical interfaces the cable modem return paths connect to. The Casa CMTS
allows up to two logical channels in each upstream port in two different A-TDMA
modes). Each upstream port and logical channel can be enabled or disabled
independently. The default state for all upstream ports and channels is shutdown. If an
upstream port is disabled, individual logical channels cannot be enabled.
Upstream modules are available as 16x4, 16x8, or 32x4 line cards. The UPS 16x8
module does not support channel widths less than 1.6 MHz. The UPS 32x4 module is
a revised version of the UPS 16x8 line card, operates with the Casa C100G, C40G,
and C10G CMTS platforms, and is not supported for use with the UPS 16x4 line card.
Table 21-1 lists and briefly describes the objects related to the upstream interface.
Table 21-1. Upstream interface objects
interface upstream Configures the upstream interface.

upstream igmp filter Sets the number of Internet Group Management Protocol
(IGMP) packets to accept in a window.
upstream map size Configures the minimum upstream MAP size.
Casa Systems
interface upstream
interface upstream
Purpose
The interface upstream command configures an upstream interface. Upstream ports

are physical interfaces the CM return paths connect to. The Casa CMTS allows up to
two logical channels in each upstream port in two different A-TDMA modes). Each
upstream port and logical channel can be enabled or disabled independently. The
default state for all upstream ports and channels is shutdown. If an upstream port is
disabled, individual logical channels cannot be enabled.
With Orthogonal Frequency Division Multiple Access (OFDMA) supported on the

upstream port, only channels 0–3 are available for single-carrier traffic.
Modes
(config)#
(config-if-ups X/Y.C)#
Syntax
(config)# interface upstream <slot>/<port>.<pchan>
(config-if-ups X/Y.C)#
channel-width <Hz>
description “<text>”
no description
frequency <5000000:100000000>
ingress-cancellation [<10:1000>]
no ingress-cancellation
interface upstream <slot>/<port>.<pchan>
logical-channel {0|1} [description “<text>”]
no logical-channel {0|1} description
logical-channel {0|1} channel-width <Hz>
logical-channel {0|1} class-id <0x0:0xffffffff>
logical-channel {0|1} data-backoff {<0:15> <0:15> | automatic}
no logical-channel {0|1} data-backoff
logical-channel {0|1} minislot <size>
logical-channel {0|1} power-offset <-10:10>
[no] logical-channel {0|1} pre-equalization [auto-reset] [0:65535]
logical-channel {0|1} profile <1:1024> [secondary-profile
<id_list>]
logical-channel {0|1} prov-attr-mask {<0x0:0xffffffff> | {[bonding]
[highavailability] [lowlatency]}
[no] logical-channel {0|1} ranging-backoff <0:15> <0:15>
Casa Systems
Upstream interface 21-3
interface upstream
logical-channel {0|1} ranging-priority <0x0:0xffffffff>

[no] logical-channel {0|1} shutdown
[no] logical-channel {0|1} spectrum-rule <1:64>
map-advance {dynamic <200:2000> | static <200:4000>}
no map-advance
partial-service {fec-threshold <1:100> | snr-threshold <-10:10>}
power-adjustment {continue <2:15> | threshold <0:2>}
no power-adjustment {continue | threshold}
power-level <-16:34>
[no] pre-equalization extended-taps
[no] rate-limit
[no] shutdown
[no] small-signal- compensation
spectrum-rule <1:64>
no spectrum-rule
voice-bw-reserve {<0:100> | max-calls <0:255>} [emergency <0:255>]
no voice-bw-reserve
Properties
<slot>/<port>.<pchan> Required upstream interface ID, in the form slot/

port.physical_channel.
Note: After an upgrade to the UPS 32x4 I/O, the

per-port configuration associated with the
first four upstream channels (0–3)
previously configured on the UPS 16x8
must be re-configured, because the
supported frequency per channel was
revised to the range 18–52 MHz. After a
successful upgrade, channels 4–7 from the
original configuration are dropped and are
reconfigured over the new 16 ports (16–31)
as ports 0–3.
Example:

Casa Systems
interface upstream
channel-width <Hz> Upstream channel width, in Hertz. The only valid

values are 400000, 800000, 1600000, 3200000, and
6400000 (6.4 MHz).
Example:
description “<text>” Optional upstream interface description, up to 64

characters, enclosed in quotes if embedded spaces.
Example:
CASA(config-if-ups 13/1.0)# description

“Upstream 13”
no description
frequency Upstream channel frequency in the range 5–100

<5000000:100000000> MHz, expressed in Hertz. The range for the UPS
16x8 with the I/O 32x4 module is 15–55 MHz.
Example:
CASA(config-if-ups 13/1.0)# frequency

65000000
ingress-cancellation Enables ingress noise cancellation, which is disabled

[<10:1000>] by default. The optional sampling interval default is
200 milliseconds.
Example:
ingress-cancellation 500
no ingress-cancellation
Casa Systems
interface upstream
interface upstream Configures another upstream interface, in the form

<slot>/<port>.<pchan> slot/port.physical_channel.
Example:
CASA(config-if-ups 13/1.0)# interface

upstream 13/1.1
logical-channel {0|1} Enables an upstream logical channel for the

[description “<text>”] interface, 0 or 1. An optional descriptive text
(enclosed in quotes) can be added. A logical channel
must be specified if applying a CM mode
spectrum rule.
Example:
logical-channel 1
no logical-channel 1
no logical-channel 1 description
logical-channel {0|1} Logical channel’s channel width, as in the

channel-width <Hz> channel-width <Hz> property for the interface.
Multiple logical channels on an interface can have
different channel widths, allowing for dynamic
channel width switching based on the same center
frequency.
Example:
logical-channel 1 channel-width 6400000
Casa Systems
interface upstream
logical-channel {0|1} Logical channel’s class ID bit value. The class-id

class-id parameter enables the ranging hold-off upstream
<0x0:0xffffffff> channel descriptor (UCD) Type-19 type-length values
(TLVs). The value sets the ranging hold-off bit field
identifier, with 0x0 disabling the identifier.
Example:
logical-channel 1 class-id 0xFFFFFFFF
logical-channel {0|1} Logical channel’s data backoff value. The

data-backoff {<0:15> DOCSIS-specified method of contention resolution
<0:15> | automatic} for CMs wanting to transmit on the upstream channel
is a truncated binary exponential backoff value, with
the initial backoff window and the maximum backoff
window controlled by the CMTS. The CMTS specifies
backoff window values for both data transmission
and initial ranging. It sends these values downstream
as part of the Bandwidth Allocation Map MAC
message. The values are configurable and are
power-of-two values. For example, a value of 4
indicates a window between 0 and 15; a value of 10
indicates a window between 0 and 1023. You can set
fixed start and end values for data backoff on the
upstream ports, or set the upstream ports for
automatic data backoff (recommended for data
transmission). The default start value is 0; the default
end value is 4.
Example:
logical-channel 0 data-backoff 2 8
no logical-channel 0 data-backoff
Casa Systems
interface upstream
logical-channel {0|1} Logical channel’s minislot size, in ticks. The value

minislot <size> can be 1, 2, 4, 8, 16, 32, 64, or 128. Increase the
minislot size to avoid switchover due to buffer
corruption.
Example:
logical-channel {0|1} Logical channel’s power offset (relative to the

power-offset <-10:10> physical channel power), in decibels (dB).
Example:
logical-channel 0 power-offset 0
logical-channel {0|1} Enables logical channel pre-equalization, which

pre-equalization compensates for the difference in delays between the
[auto-reset] [0:65535] signal on the lower part of the 6Mhz channel
spectrum and the higher part, or microreflections,
caused by imperfections in the cable plant. The
default state is disabled, but Casa recommends that
it be enabled. The auto-reset modifier is optional,
along with the auto-reset period interval, in minutes,
default 1440 (24 hours), with 0 disabling the
auto-reset period.
Example:
logical-channel 0 pre-equalization
auto-reset 1440
no logical-channel 0 pre-equalization
Casa Systems
interface upstream
logical-channel {0|1} Modulation profile for the logical channel. A

profile <1:1024> modulation profile can cause changes to the physical
[secondary-profile layer and can be created automatically
<id_list>] (recommended) or manually using the
modulation-profile command. The logical channel
can have a primary profile and an optional secondary
profile, although the two profiles must have the same
channel type and the secondary profile is not
supported on logical channel 1 and has to be less
bandwidth-efficient. The following values apply:
• profile <id> — Predefined primary profile ID.

• secondary-profile <id_list> — Optional second-
ary profile ID list, specifying the order of priority in
which Casa Spectrum Management (CSM) tries
to use the predefined profiles, up to 5 values sep-
arated by commas. The secondary profile is
required for the spectrum rule modulation action.
Example:
secondary-profile 12,20,33
Casa Systems
interface upstream
logical-channel {0|1} Logical channel’s provisioned attribute mask.

prov-attr-mask DOCSIS 3.x provisioned attribute masks allow
{<0x0:0xffffffff> | assigning of service flows to channels or channel
{[bonding] bonding groups using binary attributes. These
[highavailability] attributes are either user-defined or
[lowlatency]} specification-defined. At least one of the following
values is required:
• <0x0:0xffffffff> — User-defined value, default 0x0.

user-defined.
user-defined.
Example:
logical-channel 0 prov-attr-mask 0x0
logical-channel {0|1} Logical channel’s ranging backoff start and end

ranging-backoff <0:15> values. The start value is the initial back-off window
<0:15> and the end value is the final back-off window for
initial ranging contention. Both are expressed as a
power of two.
Example:
logical-channel 0 ranging-backoff 2 8
no logical-channel 0 ranging-backoff
Casa Systems
interface upstream
logical-channel {0|1} Logical channel’s ranging hold-off priority value, with

ranging-priority 0x0 disabling the ranging hold-off TLV.
<0x0:0xffffffff>
Example:
logical-channel 0 ranging-priority 0x0
logical-channel {0|1} Shuts down the logical channel.

shutdown
Example:
logical-channel {0|1} Logical channel’s spectrum rule.

spectrum-rule <1:64>
Example:
logical-channel spectrum-rule 1
no logical-channel spectrum-rule
Casa Systems
interface upstream
map-advance {dynamic MAP advance for the upstream interface, which

<200:2000> | static defines the amount of look-ahead time for MAPs
<200:4000>} based on the plant characteristics. The system
already has a built-in look-ahead time to account for
internal operations like generating the MAP. One of
two options are available, as follows:
• dynamic <max_delay> — Dynamic MAP

advance automatically tunes the look-ahead time
by calculating the offset to the farthest modem on
that upstream port. The delay value defines an
additional look-ahead time for MAPs to allow for
internal latencies and inaccuracies in the mea-
surement system.
• static <max_delay> — Static MAP advance uses
a fixed look-ahead time specified by the user. (For
reference, a mile of coax cable has a delay of
about 7 microseconds; a mile of fiber has a delay
of about 8 microseconds.)
The default delay is equivalent to map-advance
static 3000, a conservative value. Using large delay
values increases the run-time look-ahead in MAPs,
but also reduces the upstream performance. A delay
value of 200 ms is usually adequate. For optimal
performance, measure the throughput relative to the
percent utilization and adjust the delay value to
achieve maximum throughput.
Example:
CASA(config-if-ups 13/1.0)# map-advance

dynamic 200
no map-advance
Casa Systems
interface upstream
partial-service Partial service forward error correction (FEC) or

{fec-threshold <1:100> | signal-to-noise ratio (SNR) threshold percentage.
snr-threshold <-10:10>} The partial-service SNR threshold is the offset dB
from the SNR threshold.
Example:
partial-service fec-threshold 3
partial-service snr-threshold -1
power-adjustment Adjusts the upstream input power for the interface, in

{continue <2:15> | the following ways:
threshold <0:2>}
• continue <2:15> — The CMTS can be set to
continue to adjust the modem power output
during ranging response. If the power offset is
within the power level set by the power-adjust
continue command, the CM is properly ranged in
transmit power. The adjustment level is in dBmV,
default 2. If it is beyond this level, the CMTS con-
tinues to send power adjust messages.
• threshold <0:2> — The upstream input power
threshold determines whether or not the CMTS
will send power adjustments. If the modem trans-
mits power is within the threshold, the CMTS
sends no adjustments. The adjustment level is in
dBmV. If it is beyond the threshold, then it sends
a power adjustment. After 16 failed attempts, the
CMTS stops sending ranging and the modem
remains offline.
Example:
power-adjustment threshold 1
no power-adjustment continue
Casa Systems
interface upstream
power-level <-16:34> Output power level of the interface. The Casa CMTS
controls the output power levels of CMs to meet the
desired upstream input power level. The nominal
input power level for the upstream RF carrier is in
decibels per millivolt (dBmV). The optimal setting is
0 dBmV.
Example:
power-level 0
pre-equalization Enables all 24 taps of the pre-equalizer, which could

extended-taps provide additional immunity to large echo and/or
group delay impairments. If not enabled, the default
number of taps remains at 16 (the only option for
UPS 16x4 cards).
Example:
pre-equalization extended-taps
no pre-equalization extended-taps
rate-limit Upstream rate limiting, which is the default setting.
Example:
CASA(config-if-ups 13/1.0)# rate-limit

no rate-limit
shutdown Shuts down the upstream interface. The no form of

the command restarts the interface.
Example:
CASA(config-if-ups 13/1.0)# shutdown

CASA(config-if-ups 13/1.0)# no shutdown
Casa Systems
interface upstream
small-signal- Handles sudden power swings (up to 12 dB) over

compensation upstream channels that could result in modem
deregistration. The default setting is disabled; once
enabled, use the no form of the command to disable
this feature. Note that enabling this feature results in
a slight decrease in SNR, so it is recommended to
enable this feature only in conditions where known
power swings occur that are most commonly caused
by loose connections.
Example:
small-signal-compensation
no small-signal-compensation
Casa Systems
interface upstream
spectrum-rule <1:64> Predefined spectrum rule for the upstream interface,

identified by the spectrum rule ID. The spectrum rule
is created by the spectrum rule command. With a
spectrum rule assigned to an upstream interface, the
actions defined in the rule will take place in the
specified (or default) order of priority if:
• Plant noise level exceeds signal-to-noise ratio

(SNR) threshold defined explicitly in the com-
mands or by default.
• Percentage of correctable FEC errors of total
packets received on the upstream (during polling
period) exceeds the defined or default threshold.
• Percentage of uncorrectable FEC errors of total
packets received on the upstream (during polling
period) exceeds the defined or default threshold.
A rule can be assigned to any number of upstream
interfaces. However, only one rule assignment per
upstream interface is allowed.
Example:

CASA(conf-rule 1)# channel-width
3200000 1600000
CASA(conf-rule 1)# exit
spectrum-rule 1
no spectrum-rule
Casa Systems
interface upstream
voice-bw-reserve Voice bandwidth reserve percentage for the

{<0:100> | max-calls upstream interface. When the configured percentage
<0:255>} [emergency threshold is reached, no new voice calls are accepted
<0:255>] on that channel and any unused portion of the
configured percentage is available for data sessions.
However, new voice calls will assume priority and
preempt any data sessions. Additionally, you can
also reserve a portion of the configured voice
bandwidth percentage for emergency calls. The
default is 75%.
Example:
voice-bw-reserve max-calls 100
no voice-bw-reserve
modulation-profile <id>
This command creates a modulation profile with the necessary Forward Error
Correction (FEC) bytes to help increase throughput when applied to a downstream
logical channel.
show interface upstream [<slot>/<port>/<chan> | port <slot>/<port>] {brief |

current}
Shows the upstream interface configuration in a brief form, or the current

configuration. The specification can also be by port only.
CASA(config)# show interface upstream brief

spectrum-rule 37
Casa Systems
interface upstream
frequency 20000000
ingress-cancellation
no shutdown
show interface upstream stat
Shows the statistics for the upstream interfaces.
CASA(config)# show interface upstream stat

Interface upstream 2/0.0 statistics
Admin status: DOWN
Channel utilization interval: 30
Avg upstream channel utilization: 0
Avg percent contention slots: 0
Avg percent initial ranging slots: 0
Avg percent minislots lost on late MAPs: 0
Total BW : 0.0 Mbps
Voice BW Reservation setting 75% for Normal calls
Voice BW Reservation setting 0% for emergency calls
Number of normal voice calls 0(0.00%)
Number of emergency voice calls 0(0.00%)
show interface upstream <slot>/<port>/<chan> logical-channel <id> stat
Shows the statistics for the upstream logical channel.
CASA(config)# show interface upstream 13/0.0 logical-channel 0 stat

…
Logical-channel 0
Total Modems On This Upstream Channel: 1 ,1 active cm,0 secondary
cm
Req Mslots 1024814224, Used Req Mslots 12684
Init Mtn Mslots 541327773, Used Init Mtn Mslots 0
Total Mslots 1566609521, Ucast Granted Mslots 467460
Admin status: UP
Casa Systems
interface upstream
show interface upstream [<slot>/<port>/<chan>] ugs statistics
Shows the Unsolicited Grant Service (UGS) statistics for the upstream interfaces.
CASA(config)# show interface 13/0.0 upstream ugs statistics

Interface upstream 13/0.0
Active ugs flow on the Upstream: 0
max min avg
Last 3 Hour 0 0 0.00
Last 15 Min 0 0 0.00
…
show controller upstream
Shows the upstream interface status for the controller, including the modulation
profile and SNR.
CASA(config)# show controller upstream
Interface upstream 13/0.0/0 information:

IfIndex : 5003328
Admin status: UP
Operating status: UP
Frequency: 20000000 Hz
Channel Width: 3200000 Hz
Power Level: 0
Modulation profile 2
SNR: 0.0
Statistics:
…
show upstream [x/y.z[/c]] [burst-noise | cnr]
Shows the upstream interface burst noise rate or carrier-to-noise ratio (CNR).
CASA(config)# show upstream cnr
upstream channel cnr

11/0.0/0 39.1
…
Casa Systems
upstream igmp filter
upstream igmp filter

Purpose
The upstream igmp filter command sets the number of Internet Group Management
Protocol (IGMP) packets to accept and the number of seconds in a window.
Mode
(config)#
Syntax
upstream igmp filter <0:5000> <1:5>
no upstream igmp filter
Properties
<0:5000> <1:5> Number of IGMP packets to accept followed by the

number of seconds in a window.
Example:
CASA(config)# upstream igmp filter 2500

5
CASA(config)# no upstream igmp filter
Casa Systems
upstream map size
upstream map size

Purpose
The upstream map size command sets the minimum upstream MAP size.
Mode
(config)#
Syntax
[no] upstream map size <2:10>
Properties
<2:10> Minimum upstream MAP size, default 5 milliseconds

(recommended). A smaller MAP size reduces
upstream latency at the expense of more frequent
MAP messages that consume more downstream
bandwidth.
Example:
CASA(config)# upstream map size 2

CASA(config)# no upstream map size 2
Casa Systems
show interface upstream brief
Shows the upstream interface configuration in a brief form. You can also use the
current modifier to get the current configuration.
CASA(config)# show interface upstream brief

spectrum-rule 37
frequency 20000000
ingress-cancellation
no shutdown
…
show controller upstream
Shows the upstream interface status for the controller, including the modulation
profile and SNR.
CASA(config)# show controller upstream

Interface upstream 13/0.0/0 information:
IfIndex : 5003328
Admin status: UP
Operating status: UP
Frequency: 20000000 Hz
Channel Width: 3200000 Hz
Power Level: 0
Modulation profile 2
SNR: 0.0
Statistics:
Casa Systems
show docsis upstream channel utilization
Shows the upstream channel utilization.
CASA(config)# show docsis upstream channel utilization

Upstream Total-BW Utilization Online Secondary Channel
Slot/Port.Channel (Mb/Sec) Percentage Modems Modems Description
----------------------------------------------------------------------
13/0.0 (24000000 Hz) 10.2 80 0 1
13/0.1 (27200000 Hz) 10.2 81 1 0
…
show upstream channel set [id] [mac-domain <id>]
Shows the upstream channel sets. The added | count-only / output modifier returns the
number of count lines only (the slash is a regular expression) to determine the number
of channel sets in use.
CASA(config)# show upstream channel set

MAC Chan Channel
ID Set List
1 1 10/0.0/0
2 1 10/0.1/0
3 1 10/0.2/0
4 1 10/0.3/0
5 1 13/15.0/0
6 1 13/15.1/0
7 1 13/15.2/0
8 1 13/15.3/0
show upstream cnr
Shows the upstream interface carrier-to-noise ratio (CNR).
CASA(config)# show upstream cnr

upstream channel cnr
11/0.0/0 39.1
Casa Systems
show upstream fec [<x/y.c> | docsis-mac <id> | ofdma <x/y.c |

service-group <id>]
Shows the upstream Forward Error Correction (FEC) values.
CASA(config)# show upstream fec docsis-mac 11

US chan frequency status cFEC uFEC
10/0.0/0 20000000 UP 0 0
10/0.1/0 24000000 UP 0 0
10/0.2/0 28000000 UP 0 0
10/0.3/0 32000000 UP 16 78
show upstream [<x/y.c>] signal-quality
Shows the average signal-to-noise ratio (SNR) of the upstream channels in dB units.
CASA(config)# show upstream signal-quality

upstream channel signal noise
11/0.0/1 42.0
11/0.0/1 42.0
modulation-profile
This command creates a modulation-profile with the necessary Forward Error

Correction (FEC) bytes to help increase throughput when applied to a downstream
logical channel.
Casa Systems
22-1
Chapter 22. Video
Video commands description

A video configuration consists of a unique QAM domain along with the following:
• At least one preconfigured video interface.

• One preconfigured Edge Device Interface Specification (EDIS) Session Resource
Manager (SRM) or Edge Resource Manager (ERM).
• At least one QAM group.
1. Add users — See the adduser command.
2. Configure QAM ports — See the interface qam command.
3. Configure the QAM 8x96 downstream channels — See Chapter 17, “QAM
interface.”
4. Configure the general video parameters — See the video command.
5. Create the video interfaces — See the interface video command.
6. Create the EDIS/SRM or ERM— See the video edis or video erm command
(along with the video signaling-mode and video module commands for ERM).
7. Create the QAM domain to include the video interfaces — See the video
qam-domain command.
8. Create one or more QAM groups — See the qam-group property of the video
qam-domain command.
9. Copy the configuration to startup-config.
10. Export the configuration for EDIS/SRM — See the video qam export
configuration slot command.
Casa Systems
Table 22-1 lists and briefly describes the objects related to video.
Table 22-1. Video objects
adduser Adds a video user.

interface video Configures a video interface.
video Upper level video command.
video cat-interval Sets the millisecond interval between adjacent CAT tables.
video channel-id-offset Sets the channel numbering offset for video channels.
video Enables clock drift correction to reduce video clock jitter.
clk-drift-correction
video dejitter-interval Sets the dejitter buffer size.
video drop ghost-pid Enables dropping ghost Packet Identifiers (PIDs).
video drop Enables dropping packets containing packet IDs (PIDs) in
reserved-pids the range of reserved PIDs.
video edis Configures the Edge Device Interface Specification (EDIS).
video erm Configures Edge Resource Manager (ERM) properties.
video error-threshold Sets the number of errors to occur before detecting video
degradation.
video error-window Sets the time period when sampling for degraded video.
video logging Selects one or more logging levels.
video Sets the minimum time gap between two QAM-issued
min-stream-switch-time stream switches.
video module Defines a video module.
video Defines the elapsed time before detecting multicast/
multicast-session-loss Switched Digital Video (SDV) session loss.
-timeout
video ngod Enables Next Generation On Demand (NGOD) control
source binding.
video pat-interval Defines the maximum time between adjacent program
association tables (PATs).
Casa Systems
Video 22-3
Table 22-1. Video objects (continued)
video Sets the packet identifier (PID) remapping mode.

pid-remapping-mode
video pktloss-window Sets the number of seconds to allow when checking for loss
of video packets.
video pme Sets the Privacy Mode Encryption (PME) properties.
video pme Installs an existing ERS certificate.
install-certificate
video pmt-interval Sets the maximum time between adjacent program
mapping tables (PMTs).
video power-key on Enables PowerKey encryption for video.
video qam-domain Edits the QAM parameters for the Converged Cable Access
Platform (CCAP) device.
video qam export Sets the video QAM export configuration slot.
configuration slot
video reserved-pid Sets the upper limit of the range of reserved packet IDs
upper-limit (PIDs) contained in video packets.
video session Creates a video session.
no video sessions Removes video sessions.
video signaling-mode Sets the signaling mode to either EDIS or NGOD.
video simulcrypt Sets the video DVB SimulCrypt algorithm.
video stream-proc reset Resets the QAM video stream program clock reference
(PCR) processing and program mapping table (PMT)
rebuild.
video stream-switch Sets the transport rate or video bit rate thresholds to signal
stream-switching.
video table Sets the system-wide Video On Demand (VOD) table
mode.
video Sets the time to elapse before detecting unicast VOD
unicast-session-loss-t session loss.
imeout
Casa Systems
adduser
adduser
Purpose
The adduser command adds a user to the CMTS configuration. The user’s password
is encrypted by default. The default username is root and the default password is casa.
Modes
#
(config)#
Syntax
adduser <login_id> [privilege <0:15>]
New password: <pwd>
Reenter password: <pwd>
adduser <login_id> [privilege <0:15>] encrypted-password <pwd>
Properties
<login_id> Required user’s login ID.

privilege <0:15> Command privilege level for the user. The privileges
range from 0 (lowest operation: show and clear
commands only) through 15 (superuser). If omitted,
the privilege level defaults to 1 (operator).
encrypted-password <pwd> Encrypts the password, which is the default. The
<pwd> is a text string, which will be encrypted.
Casa Systems
Video 22-5
adduser
<pwd> Required password. You are prompted for the

password if not adding the encrypted-password
modifier; if using the encrypted-password modifier,
specify the password as part of the
encrypted-password <pwd>. The password must
be a minimum 5 and maximum 8 characters in
length, with a combination of uppercase and
lowercase characters and integers.
Example:
CASA# adduser robert privilege 15

Changing password for robert
Enter the new password (minimum of 5,
maximum of 8 characters)
Please use a combination of upper and
lower case letters and numbers.
New password: *****
Re-enter new password: *****
Password changed.
show user [current | privilege]
Shows the user configuration. The same result can be achieved with the show run |
include user command. The current or privilege modifier can also be added.
CASA(config)# show user

user root privilege 15 encrypted-password vQ5PNUDraqcgc
user homeslice privilege 15 encrypted-password 0ORTMKdIqeBhg
user USER1 privilege 13 encrypted-password c1qfliaev4U
…
Casa Systems
interface video
interface video
Purpose
The interface video command configures a video interface, up to 16.
Modes
(config)#
(conf-if-video <id>)#
Syntax
(config)# [no] interface video <1:16>
(conf-if-video x)#
bandwidth <0:80000000>
no description
edis control-source loopback <0:255>
no edis control-source
[no] gige <slot>/<port>
input-group-name <name>
no input-group-name
input-port-id <1:8 | 1:65535>
no input-port-id
ip {address <ip_addr> <mask> | igmp [version <1:3>]}
no ip {address | igmp}
[no] trunk <1:65535>
vlan <1:4094>
no vlan
vrf forwarding <name>
no vrf forwarding
[no] xgige <slot>/<port>
Casa Systems
Video 22-7
interface video
Properties
<1:16> Required video interface ID.
Example:

CASA(conf-if-video 1)# exit
CASA(config)# no interface video 1
bandwidth <0:80000000> Required bandwidth setting for the video interface,

default 10000000 kbps.
Example:
CASA(conf-if-video 1)# bandwidth

10000000
description “<text>” Optional video interface description, up to 64

characters, enclosed in quotes if embedded spaces.
Example:
CASA(conf-if-video 1)# description

“Video 1 interface”
CASA(conf-if-video 1)# no description
edis control-source Edge Device Interface Specification (EDIS) cable

loopback <0:255> control source on the loopback interface, default 0.
Example:
CASA(conf-if-video 1)# edis

control-source loopback 1
CASA(conf-if-video 1)#
no edis control-source
Casa Systems
interface video
gige <slot>/<port> GigE interface slot and port for the voice interface.
There can be up to 16 video interfaces per GigE port.
Example:
CASA(conf-if-video 1)# gige 6/1

CASA(conf-if-video 1)# no gige 6/1
input-group-name <name> Input group name for the voice interface, up to 50

characters.
Example:
CASA(conf-if-video 1)# input-group-name

IGRP1
no input-group-name
input-port-id <1:8 | Input port ID, to provide the flexibility of modifying the
1:65535> input port used in signaling. For EDIS the maximum
value is 8, for Next Generation on Demand (NGOD)
the maximum value is 65535. If omitted, takes the
value of the video interface ID.
Example:
CASA(conf-if-video 1)# input-port-id 8

CASA(conf-if-video 1)# no input-port-id
ip {address <ip_addr> IP address and mask of the voice interface, in

<mask> | igmp [version A.B.C.D form, or the igmp keyword to enable the
<1:3>]} Internet Group Management Protocol, with its
optional version (default 3). Video traffic always has a
higher routing priority than DOCSIS traffic for IGMP.
Example:
CASA(conf-if-video 1)# ip address

192.168.8.8 255.255.255.255
CASA(conf-if-video 1)# no ip address
CASA(conf-if-video 1)# no ip igmp
Casa Systems
Video 22-9
interface video
trunk <1:65535> Trunk interface for the voice traffic.
Example:
CASA(conf-if-video 1)# trunk 1

CASA(conf-if-video 1)# no trunk 1
vlan <1:4094> VLAN ID for the voice traffic.
Example:
CASA(conf-if-video 1)# vlan 1

CASA(conf-if-video 1)# no vlan
vrf forwarding <name> Enables video Virtual Routing and Forwarding (VRF)
based on a predefined VRF on the VLAN. See the
“Video in a virtual routing and forwarding instance”
section for further details.
Example:
CASA(conf-if-video 1)# vrf forwarding

VRF1
no vrf forwarding
xgige <slot>/<port> XGigE interface slot and port for the voice interface.
There can be up to 16 video interfaces per XGigE
port.
Example:
CASA(conf-if-video 1)# xgige 7/0

CASA(conf-if-video 1)# no xgige 7/0
Casa Systems
interface video
Example
The following set of commands creates a video interface that operates in routing mode
and configures the GigE and XGigE interfaces. Note the absence of GigE or XGigE
ports configured for the video interface and the presence of IP addresses on the GigE
and XGigE interfaces.

CASA(conf-if-video 6)# edis control-source loopback 0
CASA(conf-if-video 6)# exit
CASA(config) interface gige 6/6

CASA(conf-if-gige 6)# mac address 00:17:10:03:c8:87
CASA(conf-if-gige 6)# ip address 199.6.6.1 255.255.255.255
CASA(conf-if-gige 6)# no ip igmp
CASA(conf-if-gige 6)# no ipv6 mld
CASA(conf-if-gige 6)# auto negotiate
CASA(conf-if-gige 6)# no shutdown
CASA(conf-if-gige 6)# exit
CASA(config)# interface xgige 7/6

CASA(conf-if-xgige 7/6)# mac address 00:17:10:03:f4:07
CASA(conf-if-xgige 7/6)# ip address 199.7.6.1 255.255.255.255
CASA(conf-if-xgige 7/6)# no ip igmp
CASA(conf-if-xgige 7/6)# no ipv6 mld
CASA(conf-if-xgige 7/6)# auto negotiate
CASA(conf-if-xgige 7/6)# no shutdown
CASA(conf-if-xgige 7/6)# exit
show interface video
Shows the video interface configuration.
CASA(config)# show interface video

interface video 1
ip address 169.254.1.1 255.255.255.0
ip igmp
edis control-source loopback 1
input-port-id 1
bandwidth 10000000
Casa Systems
Video 22-11
interface video
show interface video stat
Shows the video interface status.
CASA(config)# show interface video stat

interface video 1 status: Up
L3 Mode UP
qam module 0
video unicast count 0
interface video 2 status: Up

L3 Mode UP
qam module 4
video unicast count 13733
show cable voice summary
Shows the video voice statistics. OFDMA upstream channels are indicated with a “w”
(for wideband).
CASA(config)# show cable voice summary

Upstream Normal Emergency Total Last 15 Minutes Last 3 Hour
Channel Allow-Alloc(%)/Curr-Alloc (%)… Max Min Avg Max Min Avg
-------- ---------------------------- --------------- -----------
2/0.0 75/0.00/0 0/0.00/0 75/0.00/0 0 0 0.00 0 0 0.00
11/0.0 75/0.00/0 0/0.00/0 75/0.00/0 0 0 0.00 0 0 0.00
11/0.1 75/0.00/0 0/0.00/0 75/0.00/0 0 0 0.00 0 0 0.00
11/0.2 75/0.00/0 0/0.00/0 75/0.00/0 0 0 0.00 0 0 0.00
11/0.3 75/0.00/0 0/0.00/0 75/0.00/0 0 0 0.00 0 0 0.00
11/1.0 75/0.00/0 0/0.00/0 75/0.00/0 0 0 0.00 0 0 0.00
11/1.1 75/0.00/0 0/0.00/0 75/0.00/0 0 0 0.00 0 0 0.00
11/1.2 75/0.00/0 0/0.00/0 75/0.00/0 0 0 0.00 0 0 0.00
11/1.3 75/0.00/0 0/0.00/0 75/0.00/0 0 0 0.00 0 0 0.00
…
Casa Systems
video
video
Purpose
The video command sets video properties. Some commands spawn other
configuration modes.
Modes
#
(config)#
(conf-video-edis x)#
(conf-video-erm x)#
(conf-qam-domain x)#
(conf-video-session x)#
Casa Systems
Video 22-13
video cat-interval
video cat-interval
Purpose
The video cat-interval command sets the maximum time in milliseconds between
adjacent conditional access tables (CATs). A CAT manages cypher keys for
decrypting restricted video streams used for maintaining regular key updates.
Mode
(config)#
Syntax
video cat-interval {<50:1000> | default}
Properties
{<50:1000> | default} CAT interval, in milliseconds. The alternative default

setting accepts the default value of 250 ms.
Example:
CASA(config)# video cat-interval 200
Casa Systems
video channel-id-offset
Purpose
The video channel-id-offset command excludes DOCSIS channels from the video
channel numbering space. The specified offset indicates the number of reserved
DOCSIS channels. Video channel numbering begins following the offset, where the
first video channel begins at 0. To use the maximum number of narrowcast channels
per port (64) for QAM 8x96 or QAM 8x192, use this command so that the number of
narrowcast video channels per port is less than or equal to 64.
The channel ID offset value can be configured based on the following formula of valid
module narrowcast-channels ranges:
From 1 (or Nmax–64 if Nmax is greater than 64) through Nmax–1, where Nmax is
the largest module narrowcast-channels <num> setting among the modules.
This means that for QAM 8x96 at Nmax 48, the offset value range is 1–47; for
QAM 8x192 at Nmax 80, the offset value range is 16–79. For Nmax 70, the valid
offset value range would be 6–69 (70 minus 64 through 70 minus 1).
The module <id> channel-id-offset command is a module-specific implementation

and overrides the more general video setting (see “Related command”).
Example: QAM 8x96 (Nmax=48) and QAM 8x192 (Nmax=80)

CASA(config)# video channel-id-offset 32
The channel-id-offset is set to 32, where channels 0–31 are reserved for DOCSIS and
the remaining 16 channels (32–47) are video channels for QAM 8x96, or 48 channels
(32–79) for QAM 8x192. The remaining video channels are then numbered 0–15 for
QAM 8x96, or 0–47 for QAM 8x192.
Example: QAM 8x192 (Nmax=80 narrowcast channels)

The channel-id-offset is set to 64, where channels 0–63 are reserved for DOCSIS and
the remaining 16 channels (64–79) are video channels for the QAM 8x192. The
remaining video channels are then numbered 0–15.
Casa Systems
Video 22-15
Mode
(config)#
Syntax
video channel-id-offset <1:79>
Properties
<1:79> Offset value. The value depends on the largest of the

module <id> narrowcast-channels <num> settings.
For a system having, for example, the largest
narrowcast channel value of 70 (module 12 in the
Example), the offset must be in the range 6–69.
Without an offset value, you cannot configure 64
video channels. Remove the offset value using the
no form of the command (although this can render a
QAM group invalid; see the Example).
Example:

Error: video addressing space must be
equal to or less than 64
CASA(conf-qam-domain 1)# qam-group 1
12/0/6 12/0/69
CASA(config)#
no video channel-id-offset
qam-domain 1 qam-group 1 is invalid
without channel id offset configured
Related command
[no] module <id> channel-id-offset [<1:63>]
A module-specific override of the more general video channel-id-offset setting. The

show versions are show module <id> channel-id-offset and show channel-id-offset.
Casa Systems
video clk-drift-correction
video clk-drift-correction
Purpose
The video clk-drift-correction command enables clock drift correction to reduce

video clock jitter.
Mode
(config)#
Syntax
[no] video clk-drift-correction
Casa Systems
Video 22-17
video dejitter-interval
video dejitter-interval
Purpose
The video dejitter-interval command sets the dejitter buffer size. Jitter is the
deviation from true periodicity of a presumed periodic signal, often in relation to a
reference clock source.
Mode
(config)#
Syntax
video dejitter-interval {<10:500> | default}
Properties
{<10:500> | default} Dejitter buffer size, in milliseconds. The alternative

default setting accepts the default value of 200 ms.
Example:
CASA(config)# video dejitter-interval

200
Casa Systems
video drop ghost-pid
video drop ghost-pid

Purpose
The video drop ghost-pid command enables dropping ghost Packet Identifiers
(PIDs). A ghost PID is not identified as a well-known PID and is not included in PMT
tables. By default, ghost PIDs are dropped (enabled).
Mode
(config)#
Syntax
(config)# [no] video drop ghost-pid
Casa Systems
Video 22-19
video drop reserved-pids
video drop reserved-pids

Purpose
The video drop reserved-pids command enables dropping packets containing packet
IDs (PIDs) in the range of reserved PIDs, default enabled. Packets with reserved PIDs
should not appear in a Program Mapping Table (PMT) or video Program Association
Table (PAT), or they might be forwarded unconditionally without being processed,
causing the session to be stuck in the Initial state. PIDs 1–15 are the well-known
reserved PIDs, but other markets have other reserved PID ranges, such as Digital
Video Broadcasting (DVB) with PID ranges 16–31 reserved for DVB metadata.
According to these requirements, the desired reserved range is set by the
video reserved-pid upper-limit command.
Packets marked with these reserved PIDs are either dropped with video drop
reserved-pids as they should, or passed through with no video drop reserved-pids.
Mode
(config)#
Syntax
[no] video drop reserved-pids
Casa Systems
video edis
video edis
Purpose
The video edis command configures the Edge Device Interface Specification (EDIS)
index in the QAM domain that defines the session resource manager (SRM). Using
the EDIS protocol, the SRM controls video interfaces and QAM channels in the QAM
domain. One SRM could be from a source such as the Cisco Universal Session and
Resource Manager (USRM), or from another vendor. The EDIS index becomes part
of the video qam-domain definition. Using EDIS, the video runs in SRM mode.
Modes
(config)#
(conf-video-edis <index>)#
Syntax
(config)# [no] video edis <1:8>
(conf-video-edis x)#
[no] announce
[no] ip-address <ip_addr>
[no] output-port-base <0 | 1>
[no] reset-indication [on-failure]
reset-interval <1:60>
[no] srm-type {bbnd-cvex | casa | cisco-usrm}
(config)# [no] video edis bandwidth-control
Properties
<1:8> EDIS index.
Example:
CASA(config)# video edis 5

CASA(conf-video-edis 5)# exit
CASA(config)# no video edis 5
Casa Systems
Video 22-21
video edis
announce Enables EDIS announce messages, the default. The

EDIS announce message codes are as follows:
• 2104 — Stream successfully established, PAT

and PMT updated.
• 5200 — Stream lost or degraded and is no longer
flowing properly.
• 5406 — Stream failed to acquire a multicast
stream for a source specific address (source IP
address included).
Example:
CASA(conf-video-edis 5)# announce

CASA(conf-video-edis 5)# no announce
description “<text>” SRM name, up to 31 alphanumeric characters,

embedded in quotes if spaces included.
Example:
CASA(conf-video-edis 5)# description

“EDIS 5”
CASA(conf-video-edis 5)# no description
ip-address <ip_addr> IP address of the EDIS server, in standard 32-bit

dotted notation.
Example:
CASA(conf-video-edis 5)# ip-address

192.168.8.8
CASA(conf-video-edis 5)# no ip-address
Casa Systems
video edis
output-port-base <0 | 1> Sets the output port base, 0 by default, and
overwrites the video qam export configuration slot
base setting. With an output base value of:
• 0 – Output port 0 maps to interface qam 0/0/0

with a video channel ID offset of 0 and maps to
interface qam 0/0/32 with a video channel ID
offset of 32. The default and used for Casa or
Cisco SRM.
• 1 – Output port 1 maps to interface qam 0/0/0
with a video channel ID offset of 0 and maps to
qam 0/0/32 with a video channel ID offset of 32.
Used for BigBand SRM.
Example:
CASA(conf-video-edis 5)#
output-port-base 0
reset-indication Enables EDIS reset indication messages, the default.

[on-failure] The optional on-failure modifier resends a reset
indication message upon SMM failover or edge
manager restart.
Example:
reset-indication
no reset-indication
reset-interval <1:60> Reset interval for the EDIS protocol, default 5

seconds.
Example:
CASA(conf-video-edis 5)# reset-interval

30
Casa Systems
Video 22-23
video edis
srm-type {bbnd-cvex | Identifies the third-party SRM, which can be casa,

casa | cisco-usrm} bbnd-cvex (BigBand Networks Converged Video
Exchange) or cisco-usrm (Cisco Universal Session
and Resource Manager).
Example:
CASA(conf-video-edis 5)# srm-type casa

CASA(conf-video-edis 5)# no srm-type
bandwidth-control Enables or (using the no form of the command)

disables video bandwidth control for EDIS-based
session setup, default disabled.
Example:
CASA(config)# video edis

bandwidth-control
CASA(config)#
no video edis bandwidth-control
Casa Systems
video edis
Related command
edis access-group <access_list_name> [in | out]
Configures an access control for EDIS traffic, inbound (the default) or outbound.
CASA(config)# edis access-group EDISIN in
show video edis [<1:8>]
Shows the video EDIS configuration.
CASA(config)# show video edis 1

video edis 1
ip-address 169.254.1.2
srm-type bbnd-cvex
reset-interval 5
announce
no reset-indication
video edis 2
srm-type casa
reset-interval 5
announce
no reset-indication
Casa Systems
Video 22-25
video erm
video erm
Purpose
The video erm command configures Edge Resource Manager (ERM) properties.
ERM is part of the Next Generation On Demand (NGOD) specification and provides
reliable and optimized access to Edge QAM (EQAM) device resources. The ERM
interface is designed to manage the resource allocation of various EQAM resources
for DOCSIS and VoD activities. In addition, the EQAM device supports a
Registration Interface to ERM with the purpose of maintaining an accurate inventory
of resources availability in the EQAM devices. (See the Casa Systems – CCAP Video
Edge User Guide for details.)
Modes
(config)#
(conf-video-erm <id>)#
Syntax
(config)#
[no] video erm <1:8>
(conf-video-erm x)#
connect-retry-time <1.0:60.0>
hold-timeout <30:300>
[no] host-address <addr> [port <1:65535>]
keepalive-timeout <1:120>
Properties
<1:8> Edge Resource Manager (ERM) ID.
Example:
CASA(config)# video erm 1

CASA(conf-video-erm 1)# exit
CASA(config)# no video erm 1
Casa Systems
video erm
connect-retry-time Connect retry interval to the ERM server, in decimal

<1.0:60.0> seconds, default 7.5 seconds.
Example:
CASA(conf-video-erm 1)#
connect-retry-time 7.5
hold-timeout <30:300> Hold timeout interval, which indicates the duration

between responses to successive keepalive or
UPDATE messages received by the CCAP. If the
duration time elapses and a response is not received,
the CCAP attempts to re-establish the connection
with the ERM. The parameter should not be edited
once a session with the ERM is established.
• The hold-timeout is negotiated between the

Edge and the ERM in the D6 OPEN message.
Each peer sends their configured hold time and
they agree on the lower of the two.
• If set to zero, KEEPALIVE messages are not
sent.
• If set to a non-zero value, each peer must send a
KEEPALIVE within that period to reset this timer.
• Only the EDGE sends UPDATE messages; an
UPDATE message also resets this timer.
• If the timer expires and no KEEPALIVE message
is received, the D6 connection terminates and
restarts after the connect-retry-time.
• If modified at the Edge, the D6 connection is
restarted for re-negotiation with the ERM.
Example:
CASA(conf-video-erm 1)# hold-timeout 60
Casa Systems
Video 22-27
video erm
host-address <addr> ERM host address, as IP address or domain name,

[port <1:65535>] optionally followed by the port number, default 6069.
Example:
CASA(conf-video-erm 1)# host-address

192.168.8.8 port 6069
CASA(conf-video-erm 1)# no host-address
keepalive-timeout Keepalive timeout interval, default 10 seconds, which

<1:120> indicates the interval in which a D6 KEEPALIVE
message is transmitted to the ERM. The timeout
must be less than the hold-timeout; if it is greater
than or equal to the negotiated hold-timeout, the
keepalive-timeout is set to one-third the negotiated
hold-timeout for the duration of the D6 session.
Example:
CASA(conf-video-erm 1)#
keepalive-timeout 20
show video erm [<1:8>]
Shows the video ERM configuration.
CASA(config)# show video erm

host-address 192.168.8.8 port 6069
hold-timeout 60
connect-retry-time 7.5
keepalive-timeout 20
Casa Systems
video error-threshold
Purpose
The video error-threshold command sets the number of errors to occur before
detecting video degradation.
Mode
(config)#
Syntax
video error-threshold {<1:65535> | default}
Properties
{<1:65535> | default} Number of errors to occur before detecting video

degradation. The alternative default setting accepts
the default value of 100 errors.
Example:
CASA(config)# video error-threshold 10
show video error-stats {all | port <slot>/<port> | slot <slot>}
Shows the video error statistics.
CASA(config)# show video error-stats all
Casa Systems
Video 22-29
show video error-sessions {all | multicast | unicast} {brief | verbose}
Shows any video error sessions, filtered by all, multicast, or unicast.
CASA(config)# show video error-sessions all brief

SRM Video Dest UDP QAM QAM PID In Out
Session ID ID Intf IpAddress Port Chan Domain Remap ProgNo ProgNo
---------- --------- --------- ---- ---- ------ ----- ------ ------
Detected Input Output PSI Uptime
Bitrate State State Detected (s)
------- ----- ----- -------- ------
Casa Systems
video error-window
video error-window
Purpose
The video error-window command sets the time period when sampling for degraded
video.
Mode
(config)#
Syntax
[no] video error-window {<1:30> | default}
Properties
{<1:30> | default} Time period in seconds when sampling for degraded

video. The alternative default setting accepts the
default value of 10 seconds.
Example:
CASA(config)# video error-window 10

CASA(config)# no video error-window 10
show video error-stats {all | port <slot>/<port> | slot <slot>}
Shows the video error statistics.
CASA(config)# show video error-stats all
Casa Systems
Video 22-31
video logging
video logging
Purpose
The video logging command selects one or more logging levels for capturing video
event messages to the system log file. By default, the system logs messages are
classified at the Warning, Informational, and Errors event levels. All other levels must
be interactively enabled with the command.
Before starting a video configuration, ensure that NTP, logging (IPv4 or IPv6), and
SNMP trap server IP addresses have been configured on the system. These services
are important for capturing and monitoring video session activity and for keeping
synchronized with NTP and other servers operating in the video network.
Note: It is recommended that you keep the debugging level disabled unless you are
actively troubleshooting a video problem. Keeping it enabled may impact
system performance when debugging processes are running.
Mode
(config)#
Syntax
[no] video logging {announce | d6-keep-alive | debugging | edis-ping |
edis-raw | edis-text | errors | host | informational | ngod-raw
| ngod-text | trace | source-interface | trace | warning}
Casa Systems
video logging
Properties
{announce | d6-keep-alive | Logging level. By default, system log messages are

debugging | edis-ping | classified at the Warning, Informational, and Errors
edis-raw | edis-text | event levels. All other levels must be set explicitly.
errors | host | Clear the logging level with the clear video log
informational | ngod-raw | command.
ngod-text | trace |
source-interface | trace | Example:
warning}
CASA(config)# video logging announce
CASA(config)# no video logging
CASA(config)# no video logging announce
CASA(config)# clear video log announce
Please type YES to confirm deleting
video announce logfile(s): yes
Cleared announce video log files
[Thu Dec 17 16:11:05 2015]-AL-CLI-1:
smm6: User root cleared announce
logfile at Thu Dec 17 16:11:05 2015
show video log {announce | non-volatile | volatile}
Shows video session log messages of a specific type.
CASA(config)# show video log non-volatile

[2016-05-31,17:16:23.7717]-WA-_edg_upd_svc():965: thread for
127.1.0.6:46150 exit
[2016-05-31,14:28:38.1697]-WA-_edg_upd_svc(): start edg_upd_svc for
slot 2
…
show video mirror
Shows a video diagnostic session, if present.
CASA(config)# show video mirror
Casa Systems
Video 22-33
video min-stream-switch-time
video min-stream-switch-time
Purpose
The video min-stream-switch-time command sets the minimum time gap between
two QAM-issued stream switches, or sets the default to 3 seconds. A QAM-issued
stream switch is controlled by QAM, but two successive stream switches cannot take
place within the given time interval. The latter stream switch will be pushed to a queue
and scheduled in a dedicated thread, and in the meantime, a flag indicating the stream
error is saved for the session. After the time interval, the latter stream switch is
processed. If the stream error is recovered during the time, no stream switch is
performed, otherwise, it switches to the next source. When the flag exists, all
subsequent stream errors reported by QAM are discarded.
Use the show video global config command to see the configuration setting.
Mode
(config)#
Syntax
[no] video min-stream-switch-time {<1:60> | default}
Properties
<1:60> | default Sets the minimum time gap between two

QAM-issued stream switches, or the default, which
is 3 seconds.
Example:
CASA(config)# video
min-stream-switch-time 30
Casa Systems
video module
video module
Purpose
The video module command edits the QAM_8x96 video module per the specified
chassis slot. Only QAM_8x96 (NGOD) modules are supported for this command.
Modes
(config)#
(conf-video-module <id>)#
Syntax
[no] video module <0:13>
(conf-video-module x)#
bandwidth-update-threshold <0:2147483647>
cost <0:255>
[no] d6-enable
[no] edge-name <name>
[no] erm <1:8>
[no] location “<state>.<city>.<loc_id>.<hub_name>”
[no] ngod control-source loopback <0:255> [port <1:65535>]
[no] shutdown
[no] streaming-zone <name>
Properties
<0:13> Defines a video module. Only QAM 8x96 modules

are supported.
Example:
CASA(config)# video module 10

CASA(conf-video-module 10)# exit
CASA(config)# no video module 10
Casa Systems
Video 22-35
video module
bandwidth-update-thresho Available bandwidth threshold, in kilobits-per-second,

ld <0:2147483647> default 0.
Example:
CASA(conf-video-module 10)#
bandwidth-update-threshold 0x70000000
cost <0:255> Cost value, default 1.
Example:
CASA(conf-video-module 10)# cost 255
d6-enable Enables the D6 cable interface for the module.
Example:
CASA(conf-video-module 10)# d6-enable

no d6-enable
description “<text>” Optional description for the module, up to 64

characters, embedded in quotes if spaces.
Example:
CASA(conf-video-module 10)# description

“This video module is in Andover”
no description
Casa Systems
video module
edge-name <name> Edge name (instance ID) for the module, three digits
identifying the edge devices in a location, maximum
50 characters.
Example:
CASA(conf-video-module 10)# edge-name

001
no edge-name
erm <1:8> Edge Resource Manager (ERM) properties for the

module based on the ERM ID, as defined by the
video erm command. The video signaling-mode
must be set to ngod.
Example:
CASA(conf-video-module 10)# erm 1

Error: Video signaling mode is not ngod
CASA(conf-video-module 10)# no erm 1
location Module location, in the form

“<state>.<city>.<loc_id> “<State>.<City>.<Locality ID>.<Hub name>”,
.<hub_name>” maximum 36 characters.
Example:
CASA(conf-video-module 10)# location

"MA.Andover.01810.HUB1"
CASA(conf-video-module 10)# no location
Casa Systems
Video 22-37
video module
ngod control-source Next Generation On Demand (NGOD) control source

loopback <0:255> [port address-defined loopback interface, with the optional
<1:65535>] R6 port number, default 554. The
video signaling-mode must be set to ngod.
Example:
CASA(conf-video-module 10)# ngod

control-source loopback 0 port 554
Error: Video signaling mode is not ngod
no ngod control-source
shutdown Shuts down the video module interface. Use the no

form of the command to restart the interface.
Example:
CASA(conf-video-module 10)# shutdown

CASA(conf-video-module 10)# no shutdown
streaming-zone <name> Streaming zone name for initiating a connection with

the ERM.
Example:
streaming-zone SZNAME
no streaming-zone
Casa Systems
video module
show video module
Shows configured video modules.
CASA(config)# show video module

video module 4
d6-enable
no shutdown
no erm
no streaming-zone
no location
no edge-name
no description
cost 1
bandwidth-update-threshold 0
video module 10
d6-enable
no shutdown
no erm
no streaming-zone
location MA.Andover.01810.HUB1
edge-name 001
description "This video module is in Andover"
cost 1
bandwidth-update-threshold 0
Casa Systems
Video 22-39
video multicast-session-loss-timeout
video multicast-session-loss-timeout
Purpose
The video multicast-session-loss-timeout command defines the elapsed time before

detecting multicast/Switched Digital Video (SDV) session loss. SDV provides video
services in a more efficient manner than broadcast video. It does this by not sending
unwatched programs to the video service group(s), which frees up bandwidth on the
QAM channels for other applications. (See the Casa Systems – CCAP Video Edge
User Guide for more details.)
Mode
(config)#
Syntax
video multicast-session-loss-timeout {<1:172800> | default}
Properties
{<1:172800> | default} Elapsed time before detecting multicast/SDV session

loss. The alternative default setting accepts the
default value of 60 seconds.
Example:
CASA(config)# video
multicast-session-loss-timeout 30
Casa Systems
video ngod
video ngod
Purpose
The video ngod command sets various Next Generation On Demand (NGOD)
properties involving control sources, R6 resource management attributes, and vendor
string parameters.
Mode
(config)#
Syntax
video ngod control-source bind
no video ngod control-source bind
video ngod r6-connection-timeout {<30:600> | default]
video ngod r6-control-source loopback <0:255>
no video ngod r6-control-source loopback
video ngod r6-listening-port {<1:65535> | default]
video ngod vendor-string <name>
no video ngod vendor-string
Properties
control-source bind Enables NGOD control source binding, default

enabled.
Example:
CASA(config)# video ngod control-source

bind
CASA(config)#
no video ngod control-source bind
r6-connection-timeout Sets the NGOD R6 connection timeout period, in

{<30:600> | default] seconds. The default keyword sets the value to 180.
Example:
CASA(config)# video ngod

r6-connection-timeout default
Casa Systems
Video 22-41
video ngod
r6-control-source loopback Sets the NGOD R6 control source to the loopback

<0:255> interface ID.
Example:

r6-control-source loopback 0
CASA(config)# no video ngod
r6-control-source loopback
r6-listening-port Sets the NGOD R6 listening port. The default

{<1:65535> | default] keyword sets the value to 554.
Example:

r6-listening-port default
Casa Systems
video ngod
vendor-string <name> Populates the vendor string parameter in the VREP

message forwarded to the Edge Resource Manager
(ERM). The vendor string used to be defined by the
description property of the video module command,
but is now a separate NGOD property that applies to
all video modules. The string is maximum 50
characters, no blank spaces.
NGOD communicates with the ERM using the D6

(Discovery) protocol. When the TCP protocol is first
established, it exchanges a D6-OPEN message with
the ERM and this vendor string is included in the
message. If both sides agree on the other’s OPEN
message, they send a KEEPALIVE as a positive
acknowledgment. This sends D6-UPDATE
messages to the ERM indicating the status of the
input (GigE or XGigE) video interface and video QAM
channels.
Example:
CASA(config)# video ngod vendor-string

casa-c100g
CASA(config)#
no video ngod vendor-string
Related command
ngod access-group <acl> [in | out]
Sets the access group for NGOD.
CASA(config)# ngod access-group NGOD1 in
Casa Systems
Video 22-43
video pat-interval
video pat-interval
Purpose
The video pat-interval command defines the maximum time between adjacent
program association tables (PATs).
Mode
(config)#
Syntax
video pat-interval {<50:1000> | default}
Properties
{<50:1000> | default} Maximum time between adjacent program

association tables (PAT), in milliseconds. The
alternative default setting accepts the default value
of 250 ms.
Example:
CASA(config)# video pat-interval 250
Casa Systems
video pid-remapping-mode
Purpose
The video pid-remapping-mode command sets the packet identifier (PID)

remapping mode to reserve a range of PIDs that do not conflict with the transparent
passing of a video stream through a QAM channel. Auto-mapped video sessions use
256 PIDs beginning with the start PID.
Mode
(config)#
Syntax
video pid-remapping-mode {auto [start-pid <16:7900>] | pg-num-based}
Casa Systems
Video 22-45
Properties
{auto [start-pid <16:7900>] Sets the PID remapping mode to either automatic or
| pg-num-based} program-number-based, default auto. All elementary
PIDs from all input programs are multiplexed into the
same MPTS for a given QAM channel. The PIDs
must be unique for proper demultiplexing when the
MPTS reaches a QAM set-top box. For multiplexed
video QAM, there are two modes of operation:
• auto — The system assigns a PID from the range

256–511 (0x21–0x1FF0) and guarantees that all
remapped PIDs are unique in a QAM channel.
The start-pid option reserves a range of PIDs
that will not conflict with the transparent passing
of a video stream through a QAM channel.
Auto-mapped video sessions use 256 PIDs
beginning with the start PID.
• pg-num-based — Program-number-based
mode. The following fixed mapping is used for a
given output program number N:
PMT PID = N * 0x10

PCR PID = Video PID = (PMT PID) + 1
Audio 1 PID = (PMT PID) + 4; for the 1st audio
Audio 2 PID = (PMT PID) + 5; for the 2nd audio if
it exists
ECM PID = (PMT PID) + 9
Example:
CASA(config)# video pid-remapping-mode

auto
Casa Systems
video pktloss-window
video pktloss-window
Purpose
The video pktloss-window command sets the number of seconds to allow when
checking for loss of video packets.
Mode
(config)#
Syntax
video pktloss-window {<1:60> | default}
no video pktloss-window
Properties
{<1:60> | default} Number of seconds to allow when checking for loss

of video packets. The alternative default setting
accepts the default value of 1 second.
Example:
CASA(config)# video pktloss-window 10

CASA(config)# no video pktloss-window
Casa Systems
Video 22-47
video pme
video pme
Purpose
The video pme command sets the Privacy Mode Encryption (PME) properties. PME
is a proprietary protocol for video on demand (VOD) services that are widely
supported and implemented in North America. PME includes a conditional access
systems (CAS), edge QAMs, or Converged Cable Access Platform (CCAP)
equipment to provide program encryption to authorized subscribers. The C100G
CCAP provides full support for PME services, including software support for data
path, signaling and management. The encryption of the video stream is completed by
the C100G CCAP hardware.
Note that the separately described video pme install-certificate command is available
only in enable mode.
Mode
(config)#
Syntax
video pme contact <name>
no video pme contact
video pme device-id [2] <id> password [2] <pwd>
no video pme device-id
[no] video pme on
video pme proxy server <addr> [port <0:65535>]
no video pme proxy server
video pme proxy server keepalive <10:3600>
no video pme proxy server keepalive
video pme proxy server master [port <0:65535>]
no video pme proxy server master
video pme retry-time <1:1440>
no video pme retry-time
video pme source-interface loopback <0:255>
no video pme source-interface
video pme url <url>
no video pme url
Casa Systems
video pme
Properties
contact <name> Contact email address for the PME device, as a text
string up to 64 characters. The configuration is
mapped to HTTP headers.
Example:
CASA(config)# video pme contact

support@casa-systems.com
CASA(config)# no video pme contact
device-id [2] <id> password Device ID and password, as text strings up to 32

[2] <pwd> characters. If the optional number 2 is omitted, the
device ID and password are presented in clear text. If
inserted, the second 2 in front of the password must
also be inserted and is intended for system
startup-configuration processing. Clear text should
be used for configuration.
Example:
CASA(config)# video pme device-id

XXXX-XXX password YYYYYYY
CASA(config)# no video pme device-id
on Turns PME encryption on. By default, encryption is

turned off. When turned on, the encryption engine
starts encrypting the incoming stream immediately.
Use the no form of the command to turn encryption
off. The command is also available in diagnostic
mode where it uses the off qualifier instead of the no
form.
Example:
CASA(config)# video pme on

CASA(config)# no video pme on
CASA(diag)# video pme on
CASA(diag)# video pme off
Casa Systems
Video 22-49
video pme
proxy server <addr> [port PME server IP address on the client side of the
<0:65535>] network. The specified IP address must be the
loopback IP. The default port is 50010. Ensure that
the port is unique to this application.
Example:
CASA(config)# video pme proxy server

192.168.8.9 port 50010
CASA(config)# no video pme proxy server
proxy server keepalive PME server keepalive, maximum 3600 seconds

<10:3600> (1 hour), default 30 seconds.
Example:

keepalive 60
CASA(config)#
no video pme proxy server keepalive
proxy server master [port PME proxy server to be the master server in the
<0:65535>] cluster. The default port is 50010; ensure that the
port is unique to this application.
Example:

master
CASA(config)#
no video pme proxy server master
retry-time <1:1440> PME retry time interval, default 5 minutes.
Example:
CASA(config)# video pme retry-time 10

CASA(config)# no video pme retry-time
Casa Systems
video pme
source-interface loopback Internal Converged Cable Access Platform (CCAP)

<0:255> loopback interface for Encryption Renewal System
(ERS) communication, no default. The ERS manages
encryption data for the PME Conditional Access
System (CAS) and provides the interface to the
CCAP Edge QAM Manager.
Example:
CASA(config)# video pme

CASA(config)#
no video pme source-interface
url <url> URL of the ERS. Specify the URL as a text string of
up to 128 characters. The default URL is the
licensing ERS. Use the no form of the command to
revert to the current URL setting.
Example:
CASA(config)# video pme url

casa-systems.com
CASA(config)# no video pme url
show video pme
Shows the current PME video configuration.
CASA(config)# show video pme

PME status : Off
Loopback : N/A
Retry timer : 5 minutes
Test-mode : Off
Contact info : N/A
Certificate installed : Yes
URL: N/A
Sync Number: 0
Casa Systems
Video 22-51
video pme
show video pme proxy stats
Shows the current PME video proxy server statistics.
CASA(config)# show video pme proxy stats

Client or Server is not configured
show video homeless-streams {all | slot <id>}
Shows reported unknown video sessions to the SMM.
CASA(config)# show video homeless-streams all

QAM Src Dest Dest Total
Module IpAddress IpAddress Port Pkts
------ --------------- --------------- ----- -----
show video input-streams [multicast | unicast] [rows [<start> [<end>] |

count]
Shows filtered packet statistics (unicast, multicast, or both) from the active video
sessions. The rows argument sets the number of rows to show, with the starting and
ending row numbers, or shows the numerical count of the output rows.
CASA(config)# show video input-streams rows 1 1

Destination Source Input Stream Bitrate
Type IP Addr:Port IP Addr Port Slot ID (mbps)
---- ---------------- ------------- ----- ------- ------- -------
SPTS 199.175.1.1:1017 201.175.1.254 xgige 6/6 1 10 9.0720
Prog PMT PCR Total Contin PcrInter Jitt
Nmbr PID PID ES PIDs Error Exceeds (ms) Rep
---- ---- ---- ------- ------- --------- ----- ---
1 500 484 3 29 389 2 1
show smm sync-status
Shows the file synchronization between the active and standby SMM.
CASA(config)# show smm sync-status

Data base sync status: synchronized
Boot image sync status: synchronized
Casa Systems
video pme install-certificate
video pme install-certificate

Purpose
The video pme install-certificate command installs an existing ERS certificate. Use
the copy command to install the certificate file to NVRAM before issuing the video
pme install-certificate command to install the certificate in the system.
Modes
#
(diag)#
Syntax
# [no] video pme install-certificate
(diag)# no video pme install-certificate
show video pme
Shows the current PME video configuration with the certificate uninstalled.
CASA# show video pme

PME status : Off
Loopback : N/A
Retry timer : 5 minutes
Test-mode : Off
Contact info : N/A
Certificate installed : No
URL : N/A
Sync Number : 0
Proxy : Off
Casa Systems
Video 22-53
video pmt-interval
video pmt-interval
Purpose
The video pmt-interval command sets the maximum time between adjacent program
mapping tables (PMTs).
Mode
(config)#
Syntax
video pmt-interval {<50:10000> | default}
Properties
{<50:10000> | default} Maximum time between adjacent program mapping

tables (PMTs), in milliseconds. The alternative
default setting accepts the default value of 250 ms.
Example:
CASA(config)# video pmt-interval 500
Casa Systems
video power-key on
video power-key on
Purpose
The video power-key on command turns on video PowerKey encryption.
CCAP PowerKey is a protocol for video encryption services that is widely supported
and implemented in North America. PowerKey systems include a video server (called
a “video pump”), Digital Network Control System/VOD System Resource Manager
(DNCS/VSRM), CCAP/QAMs, and management equipment to provide program
encryption to authorized subscribers.
In the PowerKey encryption environment, the DNCS/VSRM interfaces with CCAP

for encryption scheduling, key, and video management. The CCAP Edge QAM
component communicates with the control module and performs the encryption at the
hardware level. PowerKey uses a PKI-like system of secret, public, and private keys.
Mode
(config)#
Syntax
video power-key on
no video power-key
show video power-key [encrypt-data] [session <id>]
Shows the video PowerKey settings, optionally for a specific session.The update and
setup periods are reported in milliseconds. The encrypt-data qualifier is available in
diagnostic mode only.
CASA# show video power-key

video power-key: on
Private data installed: No
CASA# show video power-key session 001710035f5500000001

Encryption:
Configured :Yes
Actual :Yes
Casa Systems
Video 22-55
video power-key on
Override :No
Start Time :03/09/2016,14:32:36 UTC
ECM Update Period :100
CW Update Period :4000
CW Setup Period :450
CW update Counter :243
C10G-181#show video power-key session 1
Error: Length of session ID should be 20
CASA(diag)# show video power-key encrypt-data session 88

Power-Key encryptor data for session 001710035f40 00000088:
streamId(local session id): 4474306
Power-Key session id (to lib): 1
is_encrypted: 1
start_immediate: 1
start_time: 0
ecm_update_period: 100
cw_update_period: 4000
cw_setup_peroid: 450
caDATA[0] typeOfData: 0
caDATA[0] deliveryId: 0
caDATA[0] serialNumber: 0
caDATA[0] caDataLen: 80
caDATA[0] caData:
…
Casa Systems
video qam-domain
video qam-domain
Purpose
The video qam-domain command edits the QAM parameters for the Converged
Cable Access Platform (CCAP) device. A video QAM domain equates to a video
service group in deployment and the latter can be identified in the configuration.
Modes
(config)#
(conf-qam-domain <index>)#
Syntax
([no] video qam-domain <1:128>
(conf-qam-domain x)#
no description
[no] edis <1:8>
[no] interface video <1:16>
qam-group <1:8> {<start_qam> <end_qam> | shared-channel <start_qam>
<end_qam>}
no qam-group <1:32>
video service group <0:4294967295>
no video service group
Properties
<1:128> QAM domain index.
Example:

CASA(conf-qam-domain 56)# exit
CASA(config)# no video qam-domain 56
Casa Systems
Video 22-57
video qam-domain
description “<text>” Adds a description for the QAM domain, up to 64

characters, embedded in quotes if space characters.
Example:
CASA(conf-qam-domain 56)# description

“#56 QAM domain”
CASA(conf-qam-domain 56)#
no description
edis <1:8> Identifies the Edge Device Interface Specification

(EDIS) instance by index number, as set by the
video edis command.
Example:
CASA(conf-qam-domain 56)# edis 1

CASA(conf-qam-domain 56)# no edis 1
interface video <1:16> Sets one or more previously-configured video

interfaces to include in the QAM domain. A QAM
domain can associate with more than one video
interface, but each interface cannot associate with
QAM domains on different QAM cards. (See the
interface video command.)
Example:
CASA(conf-qam-domain 56)# interface

video 1
no interface video 1
Casa Systems
video qam-domain
qam-group <1:8> Configures up to 32 QAM groups on a downstream

{<start_qam> <end_qam> | line card, with a maximum eight QAM groups per
shared-channel QAM domain. A QAM channel cannot be present in
<start_qam> <end_qam>} more than one QAM group. Specify start and end
QAM channels, in the form <slot>/<port>/<chan>, or
a start and shared channel in the form <slot>/<chan>.
Example:
CASA(conf-qam-domain 56)# qam-group 7

4/7/10 4/7/31
no qam-group 7
video service group A way of associating the QAM domain with a defined
<0:4294967295> video service group, default 0. Use the show video
session service-group <id> command to list the
video session IDs and QAM channels in the QAM
domain associated with the video service group.
Example:
CASA(conf-qam-domain 56)# video service

group 1
no video service group
show video qam channel [<slot>/<port>/<chan>] stat
Shows the current video QAM channel statistics.
CASA(config)# show video qam channel stat

Session Out QAM Detected Max Sess Sess Input Output
ID ProgrNo Chan Bitrate Bitrate Mode State Packet Packet
(kbps) (kbps)
--------- ------- ---- -------- ------- ---- ----- ------ ------
Casa Systems
Video 22-59
video qam-domain
show video [qam] port [<slot>/<port>] [stat]
Shows the current video port statistics.
CASA(config)# show video qam port stat

QAM Detected Available Max Util Total Total Packet
Chan Bitrate Bitrate Bitrate (%) Bandwidth Programs Trans
(kbps) (kbps) (kbps)
---- -------- --------- ------- ------------- -------- ----
0/0/0 0 38814 0 0 38814 0 0
0/0/1 0 38814 0 0 38814 0 0
…
show video qam shared-channel [<slot>/<port>] stat
Shows the current video QAM shared channel statistics.
CASA(config)# show video qam shared-channel stat

Session Out QAM Detected Max Sess Sess Input Output
ID ProgNo Chan Bitrate Bitrate Mode State Packet Packet
(kbps) (kbps)
--------- ------ ---- ------- ------- ---- ----- ----- ------
show video qam [<mod_id>] stat
Shows the current video QAM statistics.
CASA(config)# show video qam stat

Port Bitrate Bitrate Bitrate (%) Bandwidth Programs Trans
(kbps) (kbps) (kbps)
------- ---------- ---------- ---------- ---- ---------- -------------
10/0 0 1242048 0 0 1242048 0 0
10/1 0 1242048 0 0 1242048 0 0
show video qam-domain [<1:128>]
Shows the current video QAM domain configuration.
CASA(config)# show video qam-domain

video qam-domain 1
edis 1
interface video 1
qam-group 1 4/7/0 4/7/2
Casa Systems
video qam-domain
show qam-group [<1:8>]
Shows the current QAM groups in a particular QAM domain. The command is
available in the QAM domain context only.
CASA(conf-qam-domain 1)# show qam-group

qam-group 1 4/7/0 4/7/2
show video channel <qam_if> {psi | stat}
Shows the current video QAM channel configuration.
CASA(config)# show video channel 1/0/0 psi

Qam channel 1/0/0
Total-bandwidth : 29.162000 Mbps
Annex : ITU-T/J.83/C-INV
Frequency : 731000000 Hz
Modulation : 64 QAM
Utilization : 8%
Bitrate : 6.94 Mbps
Packet-rate : 4615 pps
Packet Transmitted : 141696
TSID : 1
Active programs : 1
PAT interval : 98 ms
PAT version : 27
PMT interval : 12 ms
Prog PMT PMT PCR ECM ES ES

Nmbr PID Ver PID PID PID Type
---------- ------- ---------- ------- ------- ---------- -------
1 289 1 288 0 288 Video
287 Audio
show video session service-group <id>
Shows the related sessions and QAM channels in a particular video service group.
CASA(config)# show video session service-group 100001

SRM Video Dest UDP QAM QAM PID
Session ID ID Intf IpAddress Port Chan Domain Remap
-------------------- --------- ------------- ----- ------ ------ -----
199bcb76153100009eba 1 4 227.175.146.1 9999 3/6/16 62 Yes
In Out Detected Input Output PSI Uptime
ProgNo ProgNo Bitrate State State Detected (s)
------------- -------- ----- ------ -------- ------
0 20 8595281 On On Yes 48
Casa Systems
Video 22-61
video qam export configuration slot

Purpose
The video qam export configuration slot command sets the video QAM export
configuration slot to allow exporting the video topology into a vendor-specific format.
A file is generated for each EDIS assigned to a QAM domain on the selected modules
to the active SMM’s /tftpboot/ directory in the format edisip.slot.srmtype. Then copy
the file using TFTP to NVRAM, usually from the loopback interface.
The optional base value is the output port base in the config file, which should be
default base 0 for a Casa or Cisco System Resource Manager (SRM) QAM 8x96 or
QAM 8x192, or default base 1 for a BigBand QAM 8x96 or QAM 8x192.
Mode
#
Syntax
video qam export configuration slot <list> [base {0 | 1}] [filename
<file>} [in-service-state] [srm-num <1:8>]
Casa Systems
Properties
<list> [base {0 | 1}] List of QAM slots, separated by commas (see the
[filename <file>} interface qam command). The base option indicates
[in-service-state] [srm-num the output port base type, either 0 for a Casa or Cisco
<1:8>] SRM, or 1 for a BigBand SRM. (Note that the base
setting is overwritten by the more general
video edis output-port-base <0 | 1> setting if not
base 0.)
The in-service-state option includes video channels

in shutdown state that can be enabled with no
shutdown later without having to re-export the
configuration.
The filename supports a configurable name for the

exported file, up to 50 characters. Use the Session
Resource Manager (SRM) number if there are
multiple SRMs controlling the QAM 8x96 or
QAM 8x192module. Use the copy command to copy
the file using TFTP to NVRAM.
Example:
CASA# video qam export configuration

slot 2,0 in-service-state filename
willow
Export video QAM configurations of
module 2 to file /tftpboot/
willow_2_1.xml successfully
Export video QAM configurations of
module 0 to file /tftpboot/
willow_0_1.xml successfully
CASA# copy tftp 224.0.0.1 EXPORT nvram
Casa Systems
Video 22-63
video reserved-pid upper-limit
video reserved-pid upper-limit

Purpose
The video reserved-pid upper-limit command sets the upper limit of the range of
reserved packet IDs (PIDs) contained in video packets. Packets with reserved PIDs
should not appear in a Program Mapping Table (PMT) or video Program Association
Table (PAT), or they might be forwarded unconditionally without being processed,
causing the session to be stuck in the Initial state. PIDs 1–15 are the well-known
reserved PIDs (and the default upper limit), but other markets have other reserved PID
ranges, such as Digital Video Broadcasting (DVB) with PID ranges 16–31 reserved
for DVB metadata. Packets with reserved PIDs set in these ranges are either dropped
(with the video drop reserved-pids command) as they should, or passed through
(with the no video drop reserved-pids command).
Mode
(config)#
Syntax
video reserved-pid upper-limit <1:65535>
Properties
<1:65535> Upper limit number of the reserved PID range,

default 15.
Example:
CASA(config)# video reserved-pid

upper-limit 31
Casa Systems
video session
video session
Purpose
The video session command adds a video session on a given QAM channel without
the presence of a Session Resource Manager (SRM) external signaling (EDIS) server.
The video session can be a data, multicast, or pass-through session, with only one
video session bound to a unicast stream. A pass-through session is a Multiple Program
Transport Stream (MPTS) broadcast video session over QAM 8x96 ports 0–7, where
one input MPTS can be output to one QAM multi-port shared channel. Configuring
QAM 8x96 for video broadcast requires configuring the multi-port shared channels on
the video, QAM, and QAM domain interfaces (see the “Broadcast video
configuration” section for details). There can be up to 96,000 Edge QAM sessions.
Support for two-stage video session creation is implemented when performing

encryption with the Cisco SRM Explorer Controller. With it, the behavior changes
how an encrypted session creation response occurs when no CA data is present with
the Encrypted Flag set to 1. The second stage handles the video session creation
request.
The video session initial-timeout command detects packet loss before a unicast or
multicast session timeout occurs. See also the no video sessions command.
Mode
(config)#
Syntax
video session <1:4294967295> data ip-address <dst_addr> qam-channels
<slot>/<port>/<chan> input-port <1:8> [bitrate <bps>]
[in-program-number <0:65535>] [pid-drop <pid_list>]
[pid-remapping] [src-ip <ip_addr> [<ip_addr>] [<ip_addr>]]
[udp-port <1:65535>]
video session <1:4294967295> data ip-address <dst_addr> qam-channels
shared-channel <slot>/<s_chan> input-port <1:8> [bitrate <bps>]
[in-program-number <0:65535>] [pid-drop <pid_list>]
[pid-remapping] [src-ip <ip_addr> [<ip_addr>] [<ip_addr>]]
[udp-port <1:65535>]
Casa Systems
Video 22-65
Broadcast video configuration
video session <1:4294967295> mux ip-address <dst_addr> qam-channels

<slot>/<port>/<chan> import-port <1:8> out-program-number
<1:65535> in-program-number <0:65535> [bitrate <bps>] [pid-drop
<pid_list>] [pid-remapping] [src-ip <ip_addr> [<ip_addr>]
[<ip_addr>]] [udp-port <1:65535>]
all import-port <1:8> out-program-number <1:65535>
in-program-number <0:65535> [bitrate <bps>] [pid-drop
[<ip_addr>]] [udp-port <1:65535>]
channel-list <qam_chans_list> import-port <1:8>
out-program-number <1:65535> in-program-number <0:65535>
[bitrate <bps>] [pid-drop <pid_list>] [pid-remapping] [src-ip
<ip_addr> [<ip_addr>] [<ip_addr>]] [udp-port <1:65535>]
module <id> import-port <1:8> out-program-number <1:65535>
in-program-number <0:65535> [bitrate <bps>] [pid-drop
[<ip_addr>]] [udp-port <1:65535>]
port <slot>/<port> import-port <1:8> out-program-number
<1:65535> in-program-number <0:65535> [bitrate <bps>] [pid-drop
[<ip_addr>]] [udp-port <1:65535>]
shared-channel <slot>/<s_chan> input-port <1:8>
out-program-number <1:65535> in-program-number <0:65535>
[bitrate <bps>] [pid-drop <pid_list>] [pid-remapping] [src-ip
video session <1:4294967295> pass-through ip-address <dst_addr>
qam-channels {<slot>/<port>/<chan> | shared-channel <slot>/
<s_chan>} input-port <1:8> [bitrate <bps>] [in-program-number
<0:65535>] [pid-drop <pid_list>] [pid-remapping] [src-ip
no video session <1:4294967295>
video session initial-timeout {<300:1000> | default}

Perform the follow steps to configure the QAM 8x96 for video broadcast.
1. Configure the multi-port shared channels, including the interface video,

interface qam, and video qam domain configurations.
2. Configure the broadcast video configuration using the video session <identifier>
pass-through command.
Casa Systems
Properties
<1:4294967295> Video session ID (20-byte hex) or index (1–

4294967295), and requires one of the properties that
follow. The no form of the command with the ID or
index removes the video session.
Example:
CASA(config)# no video session 1
data ip-address <dst_addr> Creates a video data session based on a destination

qam-channels <slot>/<port>/ IP address, specified QAM channels, and an import
<chan> input-port <1:8> port representing the interface video index. The
[bitrate <bps>] other properties that can be combined on the
[in-program-number command line are listed separately.
<0:65535>] [pid-drop
<pid_list>] [pid-remapping] Example:
[src-ip <ip_addr>
[<ip_addr>] [<ip_addr>]] CASA(config)# video session 1 data
ip-address 192.168.8.8 qam-channels
[udp-port <1:65535>] 2/0/0 input-port 1
data ip-address <dst_addr> Creates a video data session based on a destination

qam-channels shared-channel IP address, shared QAM channel, and an import port
<slot>/<s_chan> input-port representing the interface video index. The other
<1:8> [bitrate <bps>] properties that can be combined on the command
[in-program-number line are listed separately.
<0:65535>] [pid-drop
<pid_list>] [pid-remapping] Example:
[src-ip <ip_addr>
[<ip_addr>] [<ip_addr>]] CASA(config)# video session 1 data
[udp-port <1:65535>] shared-channel 2/0 input-port 1
Casa Systems
Video 22-67
mux ip-address <dst_addr> Creates a video multicast session based on a

qam-channels <slot>/<port>/ multicast IP address, given QAM channels, import
<chan> import-port <1:8> port representing the interface video index,
out-program-number out-program number, and in-program number. The
<1:65535> in-program-number other properties that can be combined on the
<0:65535> [bitrate <bps>] command line are listed separately.
[pid-drop <pid_list>]
[pid-remapping] [src-ip Example:
<ip_addr> [<ip_addr>]
CASA(config)# video session 1 mux
[<ip_addr>]] [udp-port
<1:65535>] 2/0/0 input-port 1 out-program-number 1
in-program-number 0

qam-channels all multicast IP address, all video channels on the
import-port <1:8> chassis, import port representing the interface video
out-program-number index, out-program number, and in-program number.
<1:65535> in-program-number The other properties that can be combined on the
<0:65535> [bitrate <bps>] command line are listed separately.
ip-address 192.168.8.8 qam-channels all
<1:65535>] input-port 1 out-program-number 1
in-program-number 0
Casa Systems

qam-channels channel-list multicast IP address, a video channel list, import port
<qam_chans_list> representing the interface video index, out-program
import-port <1:8> number, and in-program number. The list of channels
out-program-number is separated by commas and can include hyphens for
<1:65535> in-program-number ranges, as in 0/0/1,0/0/3,0/1/2-0/1/19,0/4/3. The
<0:65535> [bitrate <bps>] other properties that can be combined on the
[pid-drop <pid_list>] command line are listed separately.
[pid-remapping] [src-ip
Example:
<1:65535>] ip-address 192.168.8.8 qam-channels
channel-list 2/0/0-2/0/4 input-port 1
out-program-number 1
in-program-number 0

qam-channels module <id> multicast IP address, a module ID, import port
import-port <1:8> representing the interface video index, out-program
out-program-number number, and in-program number. The other
<1:65535> in-program-number properties that can be combined on the command
<0:65535> [bitrate <bps>] line are listed separately.
<1:65535>] module 1 input-port 1
in-program-number 0
Casa Systems
Video 22-69

qam-channels port <slot>/ multicast IP address, a QAM port, import port
<port> import-port <1:8> representing the interface video index, out-program
out-program-number number, and in-program number. The other
<1:65535> in-program-number properties that can be combined on the command
<0:65535> [bitrate <bps>] line are listed separately.
<1:65535>] port 2/0 input-port 1
in-program-number 0

qam-channels shared-channel multicast IP address, a shared channel, out-program
<slot>/<s_chan> input-port number, and in-program number. The other
<1:8> out-program-number properties that can be combined on the command
<1:65535> in-program-number line are listed separately.
<0:65535> [bitrate <bps>]
[pid-drop <pid_list>] Example:
[pid-remapping] [src-ip
<ip_addr> [<ip_addr>] CASA(config)# video session 1 mux
[<ip_addr>]] [udp-port shared-channel 2/0 input-port 1
<1:65535>] out-program-number 1
in-program-number 0
pass-through ip-address Creates a pass-through multicast session based on

<dst_addr> qam-channels specific QAM channel or shared channel, and an
{<slot>/<port>/<chan> | import port representing the interface video index.
shared-channel <slot>/ The other properties that can be combined on the
<s_chan>} input-port <1:8> command line are listed separately.
[bitrate <bps>]
[in-program-number Example:
<0:65535>] [pid-drop
<pid_list>] [pid-remapping] CASA(config)# video session 1
pass-through ip-address 192.168.8.8
[src-ip <ip_addr> qam-channels 2/0/0 input-port 1
[<ip_addr>] [<ip_addr>]]
[udp-port <1:65535>]
Casa Systems
bitrate <bps> Optional bitrate for the session to be created, in bits

per second, default 0.
Example:
CASA(config)# video session 1

qam-channels 2/0/0 input-port 1
bitrate 600
in-program-number Input program ID to be included in the session.

<0:65535> Specify 0 to indicate the first program stream.
Example:

in-program-number 0
pid-drop <pid_list> List of PIDs to drop, up to 32 separated by commas,

with PIDs ranging from 1–8190.
Example:

pid-drop 1,4,6,8
pid-remapping Specifies if PIDs are subject to remapping, the

default.
Example:

pid-remapping
Casa Systems
Video 22-71
src-ip <ip_addr> Source-specific multicast IP address, or optional

[<ip_addr>] [<ip_addr>] multiple addresses, up to three. This property must
be set as the last one.
Example:

src-ip 10.0.0.1
udp-port <1:65535> Destination UDP port for a unicast session.
Example:

udp-port 1565
initial-timeout {<300:1000> Sets the time (in milliseconds) to elapse before

| default} reporting that a video transport stream was not
received at the CCAP. The setting should be less
than the configured
video unicast-session-loss-timeout or
video multicast-session-loss-timeout value (which
is in seconds). The default value is 1000 ms.
Example:
CASA(config)# video session

initial-timeout 500
Configuring multi-port shared channels
Once a shared channel on one of the QAM 8x96 ports is created, this channel can then
be shared across one or more ports (up to seven additional) on the same module.
Casa Systems
The following CLI session configures the shared channels on port 0 and shares them
with port 1 using the following steps.
1. Configure the number of narrowcast channels on module 0 and module 1.
channels to be shared, then configure the second and any subsequent ports using
the same shared channel identifier. Execute a no shared-channel shutdown
command for each interface.
the configuration.
Example

CASA(config)# ip address 88.88.88.88 255.255.255.0

…

PORT CHAN SH_CH FREQ(MHz) BINDP BINDC REPL-P P_MASK BLK_OFF STATUS
*****12 multi-port shared channels on QAM 0/0*****

0 32 0 723000000 0 32 255 ff 3 8 up
0 33 1 729000000 0 33 255 ff 3 9 up
0 34 2 735000000 0 34 255 ff 3 10 up
0 35 3 741000000 0 35 255 ff 3 11 up
0 36 4 747000000 0 36 255 ff 3 12 up
0 37 5 753000000 0 37 255 ff 3 13 up
0 38 6 759000000 0 38 255 ff 3 14 up
0 39 7 765000000 0 39 255 ff 3 15 up
0 40 8 771000000 0 40 255 ff 3 16 up
0 41 9 777000000 0 41 255 ff 3 17 up
0 42 10 783000000 0 42 255 ff 3 18 up
0 43 11 789000000 0 43 255 ff 3 19 up
*****12 multi-port shared channels on QAM 0/7*****

7 32 0 723000000 0 32 255 ff 3 8 up
7 33 7 729000000 0 33 255 ff 3 9 up
7 34 2 735000000 0 34 255 ff 3 10 up
Casa Systems
Video 22-73
7 35 3 741000000 0 35 255 ff 3 11 up
7 36 4 747000000 0 36 255 ff 3 12 up
7 37 5 753000000 0 37 255 ff 3 13 up
7 38 6 759000000 0 38 255 ff 3 14 up
7 39 7 765000000 0 39 255 ff 3 15 up
7 40 8 771000000 0 40 255 ff 3 16 up
7 41 9 777000000 0 41 255 ff 3 17 up
7 42 10 783000000 0 42 255 ff 3 18 up
7 43 11 789000000 0 43 255 ff 3 19 up
CASA(conf-qam-domain 1)# qam-group <id> shared-channel <first>
<last>
where id is the QAM group ID in the range 1–8, and first and last are the first and
last QAM channels in the block of multi-port shared channels.

video qam-domain 1
edis 1
interface video 6
qam-group 1 0/0/16 0/0/31
shared channels added to
video qam-domain
Configure broadcast video pass-through
Create a video pass-through session on one QAM 8x96 module, then repeat the
command for additional QAM 8x96 modules. In the following example, the MPTS
broadcast video stream is being configured on slot/channel 0/0 and 1/0 (system slots 0
and 1, channel 0). In the example, the MPTS is destined for the multicast group
address at IP 227.0.0.0 on the system QAM modules in slots 0 and 1, where 0/0 is the
slot/channel in module slot 0, and 1/0 is the slot/channel in module slot 1. The video
source IP address for the MPTS is 17.56.102.2.
Casa Systems
Example

Video in a virtual routing and forwarding instance

Video can be in a preconfigured Virtual Routing and Forwarding (VRF) instance in
networks where the video service must run independently from the Internet backbone.
VRF allows participation of provider edge (PE) or customer edge (CE) devices in
virtual private networks (VPNs) using routing protocols. The following rules apply:
• Only one VRF instance is allowed per video interface; however, this same VRF
instance can be applied to multiple unique video interfaces (see the Example).
• All video interfaces used in the video qam-domain must have the same VRF (see
the Example), or else none of the video interfaces in the video qam-domain can
have a VRF configured.
Example
CASA(config)# vrf definition VRF1
CASA(config-vrf)# end

CASA(conf-if-video 3)# vrf forwarding VRF1
CASA(conf-if-video 3)# edis control-source loopback 1
CASA(conf-if-video 3)# input-port-id 1
CASA(conf-if-video 3)# bandwidth 10000000
CASA(conf-if-video 3)# end

CASA(conf-if-video 4)# vrf forwarding VRF1
…
CASA(conf-if-video 4)# end

CASA(conf-qam-domain 5)# interface video 3
CASA(conf-qam-domain 5)# interface video 4
CASA(conf-qam-domain 5)# show this

video qam-domain 5
edis 5
interface video 3
interface video 4
Casa Systems
Video 22-75
show video session <id>
Shows summary information for a particular video session. The ID must be the full
20-character hex value. Use the clear video session-parameters command to clear
the session statistics.
CASA(config)# show video session 0000000000010014091f

Created On : 02/24/2015,17:05:54 UTC
StreamId : 3576
Session ID : 0000000000010014091f
Pid-remapping : Yes
Session Mode : Multiplex
Provision Mode : TableMode
Session State : Active
Input Stream:
Uptime : 0 days 01:56:27
Data State : On
Packets Detected : Yes
PSI Detected : Yes
Bitrate Requested : 9081000 bps
Bitrate Detected Avg: 9080000 bps
Bitrate Detected Max: 9108000 bps
Jitter Detected Avg : 2 ms
Jitter Detected Max : 25 ms
Stream Type : SPTS
SSM Address : 192.168.3.131(*)
Destination IP Addr : 199.175.2.1
Destination UDP Port: 1025
PIDs to be dropped :
Input Port : xgige 6/5
PAT ver 0, TSID 1

Program 1, PMT pid 500
PMT ver 0, PCR pid 484
ES-pid ES-type
484 Video
481 Audio
IP Packets in : 6415723
TP Packets in : 42087081
TS Packets in : 41982972
PcrPackets : 972505 NonPcrPackets : 41114576
UnexpectedPackets : 559
ContinuityErrors : 0 SyncLossPackets : 0
PcrIntervalExceeds : 19
Output Qam Channel:
Casa Systems
Data State : On
QAM-Channel : 2/0/16
QAM-Domain : 17
PAT ver 4, TSID 20016

Program 1, PMT pid 259
PMT ver 0, PCR pid 258
ES-pid ES-type
258 Video
257 Audio
TP Packets out : 41980566 Under-flow : 0 Over-flow :
0
show video session all summary
Shows summary information for all current video sessions.
CASA(config)# show video session all summary

Video Session Summary for all:
Active : 0 Init : 0 Idle : 0
Off : 0 Blocked : 0 PSI-Ready: 0
UDP : 0 ASM : 0 SSM : 0
Remap : 0 Data : 0 Passthru : 0
Total Sessions : 0
Total Measured Bitrate : 0 bps
show video session all brief [rows <start> [<end>]]
Shows brief information for all current video sessions, including session creation
parameters and uptime. The rows argument sets the number of rows to show, with the
starting and (optional) ending row numbers. With the <end> number omitted, the
output shows the starting row through the remaining rows. Bit rate statistics are also
shown.
CASA(config)# show video session all brief

SRM Video Dest UDP QAM QAM PID In
Session ID ID Intf IpAddress Port Chan Domain Remap ProgNo
----------------- --- ----- --------- ---- ---- ------ ----- ------
001b8febe01901 1 1 226.94.0.0 1234 2/0/16 1 No 0
Detected Input Output PSI Uptime
Bitrate State State Detected (s) Encryption
-------- ----- ------ -------- ------- ----------
1 Off Off No 17
…
Casa Systems
Video 22-77
show video session service-group <id>
Shows the video service group information for the current video session.
CASA(config)# show video session service-group 10031

SRM Video Dest UDP QAM QAM PID
Session ID ID Intf IpAddress Port Chan Domain Remap
-------------------- --------- ------------- ----- ------ ------ -----
199bcb76153100009eba 1 4 227.175.146.1 9999 3/6/16 62 Yes
199bcb76153100009ebb 1 4 227.175.146.2 9999 3/6/16 62 Yes
In Out Detected Input Output PSI Uptime
ProgNo ProgNo Bitrate State State Detected (s)
------------- -------- ----- ------ -------- ------
0 20 8595281 On On Yes 48
0 21 8329327 On On Yes 48
…
show video input-streams [multicast | unicast] [rows {<start> [<end>] |

count}]
Shows filtered packet statistics (unicast, multicast, or both) from the active video
sessions. The rows argument sets the number of rows to show, with the starting and
(optional) ending row numbers, or shows just the numerical count of the rows. With
the <end> number omitted, the output shows the starting row through the remaining
rows.
CASA(config)# show video input-streams multicast

Destination Source Input Bitrate Program PMT PCR Total
IP Addr:Port IP Addr Port (mbps) Number PID PID ES PIDs
------------ ------------- --------- ------- ------- -------- --------
230.55.0.2 198.24.25.55 xgige 7/0 3.7480 2 480 481 3
230.55.0.2 198.24.25.55 xgige 7/0 3.7470 2 480 481 3
Contin Sync PcrInter Jitter Replicated
Error Loss Exceeds (ms)
------ ------- ---------- ----------- ----------
0 0 0 0 0
2 0 0 0 0
Casa Systems
video signaling-mode
video signaling-mode
Purpose
The video signaling-mode command has been obsoleted in favor of setting Edge
Device Interface Specification (EDIS) or Next Generation on Demand (NGOD)
signaling, or both, using the video edis command for EDIS or the video module
command for NGOD. The video signaling-mode command returns a message to that
effect.
Mode
(config)#
Syntax
video signaling-mode {edis | ngod}
Properties
{edis | ngod} Issuing either of these commands returns an

obsoleted command message.
Example:
CASA(config)# video signaling-mode edis

This command is obsoleted, the
signaling of edis will be enabled as
long as "video edis <x>" is configured
CASA(config)# video signaling-mode ngod

This command is obsoleted, the
signaling of ngod will be enabled as
long as "video module <x>" is
configured
Casa Systems
Video 22-79
video simulcrypt
video simulcrypt
Purpose
The video simulcrypt command sets SimulCrypt properties. Digital Video

Broadcasting (DVB) SimulCrypt is a standard protocol for video encryption services.
It includes conditional access systems (CAS), CCAP QAMs, and management
equipment to provide program encryption to authorized subscribers. The C100G
CCAP provides full support for SimulCrypt services, including software support for
data path, signaling and management. Encrypting the video stream is completed by
the C100G CCAP hardware. Encryption can be tier-mode (the default) or
session-mode. In session-mode, each session communicates with an Event
Information Scheduler (EIS) and each session requires separate encryption.
The CCAP SimulCrypt system includes the following components:

• Conditional Access System (CAS) — In the DVB SimulCrypt environment, the
CAS interfaces with CCAP to perform scheduling and key management.
• SimulCrypt Synchronizer (SCS) — Provides the interface to the CAS and
manages the encryption on the CCAP.
• CCAP Edge QAM Module (EQAM) — The component communicates with the
control module and performs the encryption through hardware.
QAM 8x96 with the DVB FPGA allows for 16 SimulCrypt channels numbered 16–31
of the possible 32 narrowcast channels, with an additional 64 shared channels that can
be up to eight narrowcast per port or 64 multiport shared. QAM 8x192 allows for 24
SimulCrypt channels numbered 40–63 of the possible 64 narrowcast channels, with an
additional 128 shared channels that can be up to 16 narrowcast per port or 64
multiport shared. (The numbers are slightly different if Orthogonal Frequency
Division Multiplexing channels are in effect.)
When enabling SimulCrypt on any QAM channel in an eight-channel block, all

remaining channels in that block are unavailable as DOCSIS channels. All channels
within the block must be SimulCrypt video channels.
Modes
(config)#
(config-ecmg <name>)#
Casa Systems
video simulcrypt
Syntax
(config)#
video simulcrypt cp <10:6000>
video simulcrypt ecm-channel-id start <1:65535> end <1:65535>
no video simulcrypt cp
[no] video simulcrypt ecmg {<name> | load-balancing | vrf <id>}
(config-ecmg x)#
access-criteria <hex_string>
domain-name <ip_addr>
ip-address <ip_addr>
priority <1:8>
protocol-version <2:3>
subsystem-id <0:65535>
system-id <1:65535>
tcp-port <1:65535>
(config)#
video simulcrypt ecmg-retries <1:5>
no video simulcrypt ecmg-retries
video simulcrypt ecmg-timeout <1:60>
no video simulcrypt ecmg-timeout
video simulcrypt eis {tcp-port <1024:65535> | vrf <id>}
no video simulcrypt eis tcp-port
video simulcrypt session-mode
[no] video simulcrypt source-interface loopback <0:255>
video simulcrypt tier-mode
video simulcrypt version {1 | 2}
no video simulcrypt version
Properties
cp <10:6000> Sets the crypto period, default 30 seconds. For

session-mode encryption, the value is used as a
rule-over.
Example:
CASA(config)# video simulcrypt cp 60

CASA(config)# no video simulcrypt cp
CASA(config)# no video simulcrypt
Casa Systems
Video 22-81
video simulcrypt
ecm-channel-id start Sets the Entitlement Control Message (ECM) start

<1:65535> end <1:65535> and end IDs to set the ID range to address situations
where there are two CCAP nodes interfering with
each other when communicating with the same
Conditional Access (CA) system. Setting the range
requires restarting the SimulCrypt daemon using the
video simulcrypt restart command. Use the show
video simulcrypt ecmg command to show the
configured ECM channel ID range and the ECM
channel ID for each Entitlement Control Message
Generator (ECMG). ECMG redundancy is supported.
Example:
CASA(config)# video simulcrypt

ecm-channel-id start 1 end 88
ECM channel ID range configuration was
saved to database. Please use diag
command to restart Simulcrypt daemon to
use the new configuration.
CASA(config)# diag
Password:
CASA(diag)# video simulcrypt restart
CASA(diag)# end
CASA(config)#
no video simulcrypt ecm-channel-id
ecmg {<name> | Sets a name (maximum 16 characters) for each

load-balancing | vrf <id>} Entitlement Control Message Generator (ECMG),
maximum 16 characters. The maximum number of
supported ECMGs is eight.The load-balancing
option selects an ECMG for connection based on the
load balance rule and does not enter ECMG
configuration mode. The vrf ID can also be specified.
(Both keywords must be entered in full.)
Example:
CASA(config)# video simulcrypt ecmg E1

CASA(config-ecmg E1)# exit
CASA(config)#
no video simulcrypt ecmg E1
Casa Systems
video simulcrypt
access-criteria Sets the access criteria for the ECMG, which applies
<hex_string> only to SimulCrypt tier-mode encryption and has no
effect in session-mode encryption. The hex string
should omit the 0x prefix, such as 0123, which
requires the leading 0 and is maximum length 1024.
Example:
CASA(config-ecmg E1)#
access-criteria 0123
domain-name <ip_addr> Domain name of the ECMG, maximum 254

characters. If the domain name is used, the IP
address cannot be used.
Example:
domain-name casa.test.com
ip-address <ip_addr> IPv4 address of the ECMG. If the IP address is used,

the domain name cannot be used.
Example:
priority <1:8> Priority level of the ECMG instance defined by the

system-id and subsystem-id.
Example:
CASA(config-ecmg E1)# priority 7
protocol-version <2:3> ECMG protocol version, either 2 or 3 (the default).
Example:
protocol-version 2
Casa Systems
Video 22-83
video simulcrypt
subsystem-id <0:65535> Subsystem ID for the ECMG under the unique

system-id.
Example:
CASA(config-ecmg E1)# subsystem-id 18
system-id <1:65535> Unique system ID for the ECMG.
Example:
CASA(config-ecmg E1)# system-id 1898
tcp-port <1:65535> TCP port for ECMG, which cannot be one of the
well-known ports.
Example:
CASA(config-ecmg E1)# tcp-port 33333
ecmg-retries <1:5> Sets the retry time for ECMG communication. Use
the no form of the command to revert to the default
3 retries.
Example:

ecmg-retries 5
CASA(config)#
no video simulcrypt ecmg-retries
ecmg-timeout <1:60> Sets the timeout value for ECMG communication.

Use the no form of the command to revert the
timeout to the default 3 seconds.
Example:

ecmg-timeout 5
CASA(config)#
no video simulcrypt ecmg-timeout
Casa Systems
video simulcrypt
eis {tcp-port <1024:65535> Sets the TCP port or VRF ID for communication
| vrf <id>} between the SimulCrypt Synchronizer (SCS) and the
Event Information Scheduler (EIS). The configuration
applies only to session-mode encryption. The
configuration cannot use the well-known ports in the
range used by other applications. For example,
PCMM port 3918 and IPDR port 4737 cannot be
used.
Example:
CASA(config)# video simulcrypt eis

tcp-port 22222
CASA(config)#
no video simulcrypt eis tcp-port
session-mode Enables session-based encryption in SimulCrypt,

which involves communication with an Event
Information Scheduler (EIS). (See also the
eis tcp-port property.) Session-mode and
tier-mode encryption are mutually exclusive, with
tier-mode the default. Four Conditional Access (CA)
systems and four redundant CAs are supported with
session-based SimulCrypt.
Example:

session-mode
source-interface loopback Sets the SimulCrypt interface to CAS to use the

<0:255> specific loopback interface. By default, this is not
configured.
Example:

CASA(config)# no video simulcrypt
Casa Systems
Video 22-85
video simulcrypt
tier-mode Enables tier-based encryption in SimulCrypt, where

all incoming video streams are encrypted using the
same set of key material. Adding a QAM channel to
the QAM group sets the DVB mode; channels 0–7 of
the QAM port are reserved for DOCSIS only and are
not allowed in the QAM group. Session-mode and
tier-mode encryption are mutually exclusive, with
tier-mode the default.
Example:

tier-mode
version {1 | 2} Sets version 1 or 2 encryption, intended for systems

using alternative decryption when only a partial
encryption key is used. Version 1 is the default.
Example:

version 1
CASA(config)#
no video simulcrypt version
show video simulcrypt ecmg [<id>] [stats]
Shows the Entitlement Control Message Generator (ECMG) configuration. Note that
the CP remaining time shows as N/A for session-mode SimulCrypt.
CASA(config)# show video simulcrypt ecmg EEEE

Encryption Period : 30 s
ECMG Timeout : 3 s
ECMG Retries : 3
ECMG Load-balancing : Disabled
CP remaining time : 0 s
ECM channel ID range : N/A
ECMG VRF : N/A
Casa Systems
video simulcrypt
EIS VRF : vrf1
ECMG EEEE:
System Id : 18981
Subsystem Id : 0
IP Address : 172.16.8.199
TCP Port : 22288
Priority : 1
Protocol Version : 3
Access-criteria : N/A
ECMG Uptime : 0 d : 0 h : 11 m : 37 s
Connection Status : Connected
Channel Status : Open
ECM channel ID : 254
Stream Information:
Stream ID Stream ECM ID CP number Status
--------- ------------- --------- ------------
1 1 12 Open
show video simulcrypt scg [<id>]
Shows the Scrambling Control Group (SCG) configuration (unless not found) along
with the Entitlement Control Message (ECM) information, optionally filtered by the
SCG ID to reduce the amount of output. An SCG gathers together in one logical set
the list of streams scrambled at the same time with the same control word and the list
of ECMs that are going to be generated with the identifier of their Conditional Access
(CA) system and with their respective access criteria. Up to 1000 SCGs are supported.
CASA(config)# show video simulcrypt scg 10

SCG 10:
Transport Stream ID : 1016
Network ID : 0
SCG Reference ID : 0
Activation Time : 2016-08-30 15:40:32
Recommended CP duration : 60 s
Module : 4
Port : 0
Channel : 16
Nominal CP duration : 60 s
CP Number : 8
CP remaining time : 35 s
Program IDs : 1
ECM 0:
ECM ID : 10
Super CAS ID : 1243938816
Access-criteria : 22446688aa0000000000
Casa Systems
Video 22-87
video stream-proc reset
video stream-proc reset

Purpose
The video stream-proc reset command resets the QAM video stream program clock
reference (PCR) processing or program mapping table (PMT) rebuild. With multiple
sets of PCRs in an input stream, one optimal PCR (PID) set is chosen as the reference.
NULL packets are forwarded to egress to maintain the scheduling parameters to
prevent triggering of drift correction. For SimulCrypt tier-mode encryption, the QAM
daemon rebuilds the PMT using global data, whereas in session-mode encryption the
PMT is built per stream.
Mode
(diag)#
Syntax
video stream-proc reset {pcr | pmt} ip-address <ip_addr> udp-port
<1:65535> [src-ip <ip_addr>]
Properties
{pcr | pmt} ip-address Program clock reference (PCR) or program mapping

<ip_addr> udp-port table (PMT) IP address and UDP port, with the
<1:65535> [src-ip optional source IP address.
<ip_addr>]
Example:
CASA(diag)# video stream-proc reset pcr

ip-address 192.168.8.8 udp-port 655
Casa Systems
video stream-switch
video stream-switch
Purpose
The video stream-switch command sets the transport rate or video bit rate thresholds
to signal stream-switching. The video switches streams at the transport-rate or
video-bitrate threshold. Use the show video global config command to see the
configuration settings.
Mode
(config)#
Syntax
video stream-switch <1:60> | default
Properties
transport-rate <1:5000> Sets the transport rate threshold, in kb/s, at which the
video switches streams.
Example:
CASA(config)# video stream-switch

transport-rate 60
CASA(config)#
no video stream-switch transport-rate
video-bitrate <1:5000> Sets the video bitrate threshold, in kb/s, at which the
video switches streams.
Example:
CASA(config)# video stream-switch

video-bitrate 60
CASA(config)#
no video stream-switch video-bitrate
Casa Systems
Video 22-89
video table
video table
Purpose
The video table command sets the system-wide Video On Demand (VOD) table
mode. Unlike external mode, table mode VOD does not require any EDIS signaling.
The eQAM simply parses the destination UDP port of the incoming unicast
single-program transport stream (SPTS) to decide what QAM channel and program
number to use. Table mode cannot be used over multi-port shared channels. The
eQAM can be configured to operate in one of seven table modes, plus a custom mode:
• mode0 — The two-byte UDP port is masked as 0qqqqqqq qqqppppp, where the
seven least significant bits (LSBs) of the upper byte and the three most significant
bits (MSBs) of the lower byte are combined to form the zero-based QAM channel
number on a given line card slot, and where ppppp is the 1-based program number
in the QAM channel. In this mode, an IP address can cover 1024 QAM channels,
and each QAM channel can have 63 programs.
• mode1 — The two-byte UDP port is preceded by the number 1 to protect the
known UDP port space, as 1qqqqqqq qqqppppp. In this mode, an IP address can
cover 1024 QAM channels, and each QAM channel can have 31 programs. This
leaves the lower 32K ports unused for video, as many of the UDP ports are
reserved for well-known UDP ports.
• mode2 — Only the mask is different: 1qqqqqqq qqqpppp0. In this mode, an IP
address can cover 1024 QAM channels, and each QAM channel can have 15
programs.
• mode3 — The applied mask is qqqqqqqq pppppppp. In this mode, an IP address
can cover 256 QAM channels, and each QAM channel can have 255 programs.
• mode4 — Identical to mode3 except that it uses 1-based instead of 0-based QAM
channel numbers.
• mode5 — In this mode, at most 16 channels per port are exported by the D6
interface. The UDP port mapping is 100qqqqq qqpppppp. If
video channel-id-offset is not configured, the channel used for mode5 ranges
from x/y/0 through x/y/7. If the offset is configured, the channel ranges from
x/y/offset through x/y/offset+7.
• mode6 — Similar to mode3 except the UDP port mapping is 00qqqqqq
pppppppp, with maximum eight channels.
Casa Systems
video table
• custom — Sets special mapping properties for a custom video table mode.
Mode
(config)#
Syntax
video table {mode0 | mode1 | mode2 | mode3 | mode4 | mode5 | mode6}
video table custom prog-per-chan <32|64|256> chan-per-port <1:32>
[skip-chan <0:12>] [start-udp-offset <1:65535>]
no video table
Properties
{mode0 | mode1 | mode2 | Sets the system-wide VOD table mode to mode0
mode3 | mode4 | mode5 | (qqqqqqqq qqqppppp), mode1 (1qqqqqqq
mode6} qqqppppp), mode2 (1qqqqqqq qqqpppp0), mode3
(qqqqqqqq pppppppp), mode4 (identical to mode3,
except that it uses 1-based QAM channel numbers),
mode5 (1000qqqq qqpppppp), or mode6 (00qqqqqq
pppppppp). If omitted, sessions are exclusively
managed by the SRM. Both table mode and SRM
mode can coexist.
Example:
CASA(config)# video table mode1

CASA(config)# no video table
Casa Systems
Video 22-91
video table
custom prog-per-chan Sets custom video table mode properties to

<32|64|256> chan-per-port determine the mapping, as follows:
<1:32> [skip-chan <0:12>]
[start-udp-offset • prog-per-chan <32 | 64 | 256> — Number of pro-
<1:65535>] grams per QAM channel for the mapping, valid
values 32, 64, or 256, default 64.
• chan-per-port <1:32> — Number of QAM chan-
nels for RF port mapping, default 32.
• skip-chan <0:12> — Optional number of QAM
channels to skip in addressing between RF ports,
default 0.
• start-udp-offset <1:65535> — Optional offset of
the first valid UDP port for the mapping.
Example:
CASA(config)# video table custom

prog-per-chan 64 chan-per-port 24
start-udp-offset 65 skip-chan 12
CASA(config)# no video table
Casa Systems
video unicast-session-loss-timeout
video unicast-session-loss-timeout
Purpose
The video unicast-session-loss-timeout command sets the time to elapse before

detecting unicast VOD session loss.
Mode
(config)#
Syntax
video unicast-session-loss-timeout {<1:172800> | default}
Properties
{<1:172800> | default} Time to elapse before detecting unicast VOD session

loss, in seconds. The alternative default setting
accepts the default value of 60 seconds.
Example:
CASA(config)# video
unicast-session-loss-timeout 60
show run | inc video
Shows all lines in the running configuration with “video” in them.
CASA(config)# show run | inc video

video table mode1
video clk-drift-corr
!video edis configurations begin
video edis 1
!end of video edis configurations
!video ngod configurations begin
!end of video ngod configurations
Casa Systems
Video 22-93
!video module configurations begin

video module 4
video module 10
!end of video module configurations
interface video 1
video qam-domain 1
interface video 1
video qam-domain 56
show video {all | slot <id>} stat
Shows all video channel statistics or for a particular slot.
CASA(config)# show video all stat

ChannelID Total Packets Data Rate Over Flow Under Flow Dropped Packets
--------- ------------- --------- --------- ---------- --------------
show video global config
Shows the video global configuration.
CASA(config)# show video global config

no video edis virtual-qam-mode
video signaling-mode edis
video dejitter-interval 200
video pat-interval 250
video pmt-interval 250
video unicast-session-loss-timeout 60
video multicast-session-loss-timeout 60
video ngod control-source bind
video pid-remapping-mode auto
video table mode1
video error-window 10
video error-threshold 5
video pktloss-window 1
video clk-drift-correction enabled
no video logging edis-raw
no video logging edis-text
no video logging edis-ping
video logging ngod-raw
no video logging ngod-text
video logging errors
video logging srm-errors
Casa Systems
no video sessions
no video sessions
Purpose
The no video sessions command removes video sessions based on a session index,
channel, port, or shared channel.
Mode
#
Syntax
no video sessions <1:9999>
no video sessions channel <slot>/<port>/<chan>
no video sessions port <slot>/<port>
no video sessions shared-channel <slot>/<s_chan>
Properties
<1:9999> Removes the video session with the given index.
Example:
CASA# no video sessions 1
channel <slot>/<port>/ Removes the video sessions from a channel.

<chan>
Example:
CASA# no video sessions channel 2/0/0
port <slot>/<port> Removes the video sessions from a port.
Example:
CASA# no video sessions port 2/0
Casa Systems
Video 22-95
no video sessions
shared-channel <slot>/ Removes the video sessions from a shared channel.

<s_chan>
Example:
CASA# no video sessions shared-channel

2/1
Casa Systems
100 Old River Road
Suite 100
Andover, MA 01810
USA
978-688-6706
RF Cable Configuration Guide and

Command Reference
© 2017 Casa Systems, Inc.
All rights reserved.
DOC-3022-01
Document Revision 07.02.04a

March 2017
Printed in United States of America

CMTS RF Config GD CMD Reference R7.2.4!03!15 2017

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

CMTS RF Config GD CMD Reference R7.2.4!03!15 2017

Hochgeladen von

Copyright:

Verfügbare Formate

RF Cable Configuration Guide

and Command Reference

For Casa Software Releases to 7.2.4

Chapter 1. RF cable operations overview

CMTS installation in the network topology ........................................................ 1-2 .

Cable modem initialization and learning ........................................................... 1-5 .

Cable modem initial ranging and registration .................................................... 1-6 .

Cable modem provisioning and configuration ................................................... 1-7 .

Cable modem power considerations ................................................................. 1-7 .

Upstream channel descriptors and MAPs ......................................................... 1-9 .

UCD and MAP operations ................................................................................. 1-9 .

Channel bonding and service group operations ............................................. 1-12 .

Physical fiber node vs. DOCSIS terminology .................................................. 1-13 .

Load balancing CMTS traffic ........................................................................... 1-13 .

Terminology covered in this chapter ............................................................... 1-17 .

Configuration examples .................................................................................. 1-22 .

Chapter 2. Application classes and policies

application ................................................................................................... 2-2.

class ...................................................................................................... 2-3

policy ................................................................................................... 2-12.

Chapter 3. Baseline Privacy Interface

cable privacy ............................................................................................... 3-3.

cable sa-des-tlvlen-2 ................................................................................. 3-10 .

privacy hotlist ............................................................................................ 3-11.

shared-secondary-secret .......................................................................... 3-12 .

shared-secret ............................................................................................ 3-13 .

Chapter 4. Cable commands

cable admission-control .............................................................................. 4-5 .

cable arp fast-timeout ................................................................................. 4-8 .

cable arp filter ............................................................................................. 4-9

cable call-signal-classifier ......................................................................... 4-10 .

cable dhcp filter ......................................................................................... 4-12 .

cable dhcp-leasequery filter ...................................................................... 4-13 .

cable dhcpv6-leasequery filter .................................................................. 4-14 .

cable diaglog ............................................................................................. 4-15 .

cable docsis version 31 ............................................................................. 4-17 .

cable dsx authorization ............................................................................. 4-18 .

cable dynamic-service-flow ....................................................................... 4-19 .

cable ecn 770 ............................................................................................ 4-21 .

cable event ................................................................................................ 4-22.

cable flap-list ............................................................................................. 4-29

cable host authorization ............................................................................ 4-33 .

cable icmp filter ......................................................................................... 4-34 .

cable igmp filter ......................................................................................... 4-35 .

cable igmp permit src-ip ............................................................................ 4-36 .

cable igmp static-group ............................................................................. 4-37 .

cable igmp vrf static-group ........................................................................ 4-40 .

cable map-advance-adjust ........................................................................ 4-42 .

cable mdd ................................................................................................. 4-43 .

cable mirror ................................................................................................4-46.

cable modem .............................................................................................4-47 .

cable monitor-period ..................................................................................4-48 .

cable partial-service ...................................................................................4-49 .

cable privacy ..............................................................................................4-53 .

cable proxy-arp unknown ..........................................................................4-54 .

cable qos ...................................................................................................4-55.

cable rcp-select priority ..............................................................................4-61 .

cable sa-des-tlvlen-2 .................................................................................4-62 .

cable sec ...................................................................................................4-63.

cable service attribute withhold-TLVs peak-rate ........................................4-70 .

cable service-class ....................................................................................4-71 .

cable service-flow active-timeout ...............................................................4-83 .

cable service-type-id ds-frequency ............................................................4-84 .