CMTS Debug - DiagRef - 7 - 27 - 11 - Release - 6.0.3

Casa Systems
CMTS
Debugging and Diagnostics

Reference
For Releases 5.2 to 6.0.3
DOC-3006-01
Document Version 6.0.3
July 2011
2011 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
About this guide ................................................................................................... vii
Revision history..............................................................................................viii
Contacting Casa ..................................................................................................viii
Corporate facility ............................................................................................viii
Technical Support ..........................................................................................viii
Technical documentation ...............................................................................viii
Conventions used in Casa documentation ........................................................... ix
Typographical conventions ............................................................................. ix
Acronyms ......................................................................................................... x
Chapter 1. Casa CMTS debugging commands

Activating logging .............................................................................................. 1-2
Additional logging ........................................................................................ 1-3
Displaying debug log settings ..................................................................... 1-3
Debug AAA ....................................................................................................... 1-4
Debug ARP ....................................................................................................... 1-4
Debug cable plant ............................................................................................. 1-5
Signal quality ............................................................................................... 1-5
Table 1-1.
Signal quality modulation ..................................................... 1-5
Displaying the noise level .......................................................................1-6
Debug cable modem ......................................................................................... 1-7
Cable modem flapping ...................................................................................... 1-9
Cable modem configuration information ......................................................... 1-10
Cable modem status ....................................................................................... 1-12
Cable modem remote query ........................................................................... 1-13
.
Casa Systems CMTS Release 6.0.3
iv
Debugging and Diagnostics Reference

Contents
Debug PacketCable ........................................................................................ 1-14

Debug IP ......................................................................................................... 1-14
Debug BGP ..................................................................................................... 1-15
Debug IS-IS .................................................................................................... 1-16
Debug OSPF ................................................................................................... 1-17
OSPF packet information .......................................................................... 1-20
Debug RIP ...................................................................................................... 1-21
Debug LACP ................................................................................................... 1-21
Connection testing .......................................................................................... 1-22
Chapter 2. Casa CMTS diagnostics commands

SMM diagnostics ............................................................................................... 2-2
QAM diagnostics ............................................................................................... 2-4
Downstream and upstream interface statistics ................................................. 2-5
Checking for downstream errors ....................................................................... 2-8
Upstream diagnostics (Release 5.4 only) ......................................................... 2-9
Past DHCP transactions ................................................................................... 2-9
System kernel messages ................................................................................ 2-10
Capturing packets on the GigE interfaces .......................................................2-11
Tracing the IP path .......................................................................................... 2-13
Capturing cable modem traffic on the SMM .................................................... 2-16
Displaying cable modems by modem ID ......................................................... 2-18
Core dumps .................................................................................................... 2-19
Removing old core dump files ................................................................... 2-19
Testing connectivity (extended Ping) .............................................................. 2-20
Other diagnostic commands ........................................................................... 2-20
ARP table entry ......................................................................................... 2-21
Auto-reboot ............................................................................................... 2-21
Set the CPU receive rate .......................................................................... 2-22
Turning power on and off to individual CMTS module .............................. 2-22
Shutdown or restart SNMP ....................................................................... 2-23
Show ACL applications ............................................................................. 2-23
Contents
Reboot a module unconditionally ..............................................................2-24

Show kernel interface information .............................................................2-25
Display modem information by QAM .........................................................2-26
Display VLAN information ..........................................................................2-28
Display information about modems on a VLAN .........................................2-29
vii
Preface
About this guide

The Casa Systems CMTS Debugging and Diagnostics Reference describes the
debugging and diagnostic commands that are available for diagnosing possible
problems with the CMTS or equipment that is connected to the CMTS. The debugging
and diagnostic commands are supported in the Casa command line interface (CLI) and
are included to help diagnose system problems.
This guide is intended for system administrators, support engineers, and operators
who are responsible for configuring and managing Casa CMTS products. Users who
perform these tasks should be familiar with the Casa CMTS hardware and cabling, as
well as have experience with the following:
IP routing protocols
MPEG-2 protocol
DOCSIS protocol
RF cable plants
The following topics are covered in this guide:

For information about
See
Debugging commands
Chapter 1.
Diagnostic commands
Chapter 2.
viii

Contacting Casa
Revision history
This guide supports Casa CMTS software releases up to version 5.4.21. See the Casa
Systems CMTS Release Notes for additional 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
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 C2200 CMTS Quick Installation
Casa Systems C2200 CMTS Hardware Installaton Guide
Casa Systems C3200 CMTS Quick Installation
Casa Systems C3200 CMTS Hardware Installation Guide
Casa Systems C10200 CMTS Hardware Installation Guide
Casa Systems C10G CMTS Hardware Installation Guide
Casa Systems C10G/C10200 CMTS Quick Installation
Casa Systems CMTS Software Configuration Guide
Casa Systems CMTS Debugging and Diagnostics Reference
Preface
ix
Conventions used in Casa documentation
Casa Systems CMTS Release Notes
Note: Casa Systems provides updates to the manuals on a regular basis. Log
on to Casa FTP site for the latest files in PDF format.

Typographical conventions
Key Convention
Function
Example
Boldface font
Commands and keywords in text are in

boldface.
The show running-config

command...
Bold italic font
Arguments mentioned in are in bold

italic font.
Where:
<id>: the area identifier.
brackets [ ]
Elements in square brackets are

optional.
CASA-CMTS# show rstp port

[<port-id>]
braces {x | y | z}
Indicates a required argument with a

choice of values; choose one.
CASA-CMTS(config-router-o
spf)# area <id> shortcut
{enable | disable |
default}
brackets [x | y | z]
Indicates an optional argument with a

choice of values; choose one.
CASA-CMTS(config-router-o
spf)# area <id> nssa
[translate-always |
translatecandidate |
translate-never]
vertical bar |
Separates parameter values. Same as CASA-CMTS(config-router-o

or.
spf)# ospf abr-type
[cisco | ibm | shortcut |
standard]
string
A non-quoted set of characters. Do not CASA-CMTS# hostname

use quotation marks ()around the
<string>
string as the string will include the
quotation marks.

Key Convention
Function
Example
Screen font
Terminal sessions and information the

system displays are in screen font.
[Wed Sep 1 20:58:07

2010]-AL-SYS-1: Module 8
(QAM), is up.
Bold screen font
Information you must enter is in

boldface screen font.
CMTS# show docsis channel

utilization
Bold italic screen

font
Arguments for which you supply values CASA-CMTS(config-router-o

are in bold italic screen font. spf)# timers spf
<delay-time> <hold-time>
<>
Non-printing characters such as

CASA-CMTS(config)# system
passwords are in angle brackets in
monitor memory <num>
contexts where italics are not available. threshold <amt>
Angle brackets are also used for
variables.
!,#
An exclamation point (!) or a pound

sign (#) at the beginning of a line of
code indicates a comment line.
# This is a comment.
Acronyms
Casa Systems manuals contain the following industry-standard and product-specific
acronyms:
AAA
Authentication, Authorization, Accounting
ACL
Access Control List
ARP
Address Resolution Protocol
ATDMA
Asynchronous Time Division Multiple Access
BGP
Border Gateway Protocol
BPI
Baseline Privacy Interface
CM
Cable Modem
CMTS
Cable Modem Termination System
DBC
Dynamic Bonding Change
DCC
Dynamic Channel Change
DDM
DOCSIS Data Manager
DOCSIS
Data Over Cable Service Interface Specification
DHCP
Dynamic Host Configuration Protocol
Preface
xi
DSG
DOCSIS Set-top Gateway
GigE
Gigabit Ethernet
HFC
Hybrid fiber coaxial
ICMP
Internet Control Message Protocol
IP
Internet Protocol
IS-IS
Intermediate System-to-Intermediate System
LACP
Link Aggregration Control Protocol
MIB
Management Information Base
NTP
Network Time Protocol
OSPF
Open Shortest Path First Protocol
PCMM
Packet Cable Multimedia
PIM
Protocol Independant Multicast
QAM
Quadrature Amplitude Modulation
RIP
Routing Information Protocol
SCDMA
Synchronous Code Division Multiple Access
SMM
Switch and Management Module (Casa Systems)
SNR
Signal to Noise Ratio
STB
Set-top Box
TACACS
Terminal Access Controller Access Control System
TCP
Transmission Control Protocol
TDMA
Time Division Multiple Access
TOS
Type of Service
UCC
Upstream Channel Change
VoIP
Voice over IP
VLAN
Virtual Local Area Network
1-1
Chapter 1. Casa CMTS debugging

commands
This chapter describes the Casa CMTS debugging commands available from the CLI
for debugging purposes. The CMTS supports commands for debugging the following
categories:
AAA Accounting, Authorization, and Authentication
ARP Address Resolution Protocol
Cable cable plant
IP Internet Protocol
LACP Link Aggregation Control Protocol
You can also debug connectivity issues with the extended ping command.
This chapter covers the following topics:
Topic
Page
Activating logging
1-2
Additional logging
1-3
Displaying debug log settings
1-3
Debug AAA
1-4
Debug ARP
1-4
Debug cable plant
1-5
Debug cable modem
1-7
Cable modem flapping
1-9
Cable modem configuration information
1-10
1-2

Activating logging
Topic
Page
1-10
Cable modem status
1-12
Cable modem remote query
1-13
Debug PacketCable
1-14
Debug IP
1-14
Debug BGP
1-15
Debug IS-IS
1-16
Debug OSPF
1-17
Debug RIP
1-21
Debug LACP
1-21
Connection testing
1-22
Activating logging
Debug output is captured in the CMTS log. It is necessary to first enable logging
functionality before enabling the debug options.
To enable or disable debugging output:
Step
Command
Purpose
1.
[no] logging debugging
Enables or disables
debug logging.
Example:
Enable logging of debugging messages.
CASA-CMTS(config)# logging debugging
Disable logging of debugging messages.
CASA-CMTS(config)# no logging debugging
For additional information on logging commands, refer to the Casa Systems CMTS
Software Configuration Guide.
Casa CMTS debugging commands
1-3
Activating logging
Additional logging
Additional logging information can be collected for analysis by Casa Technical
Support using the following commands:
Step
Command
Purpose
1.
show tech
Get module-specific
information for use
by Casa Technical
Support.
or
show tech module <module_id>
Where:
<module_id> is the number of the unique module identifier,
usually the slot number of the module location in the chassis.
Example:
CASA-CMTS# show tech
Displaying debug log settings

To display debug logging settings before or during the log printing process, enter the
show debugging command.
Step
Command
Purpose
1.
show debugging [bgp | isis | ospf | rip | ripng]
Displays the current

debug log settings.
Example:
CASA-C10000#logging debugging
CASA-C10000#debug cable mac-address
0050.f112.b764
CASA-C10000#debug cable cfg
CASA-C10000#debug cable verbose
CASA-C10000#show debugging
Cable:
mac-address: 0050.f112.b764
mask
: ffff.ffff.ffff
config
verbose
1-4

Debug AAA
Debug AAA
To debug problems with AAA:
Step
Command
Purpose
1.
[no] debug aaa [(accounting) | (authentication) |

(authorization)]
Enable or disable
AAA debugging.
Example:
CASA-CMTS# debug aaa
CASA-CMTS# debug aaa authentication
Use the no form of the command to disable AAA or a AAA
option.
When enabled, the logging session will show the AAA-related transaction.
Debug ARP
To debug problems with the Address Resolution Protocol (ARP):
Step
Command
Purpose
1.
[no] debug arp
Enable or disable
ARP debugging, or
debug ARP on a
specific cable
modem.
Example:
CASA-CMTS# debug arp
To debug ARP problems with specific cable modems, specify
the MAC address:
[no] debug arp mac-address <cm-mac-addr>
CASA-CMTS# debug arp mac-address
0050.f112.b765
1-5
Debug cable plant
Debug cable plant

To obtain information on the cable plant, use one of the following debugging
commands:
signal quality
debug cable
show cable flap list
show cable modem information
show cable modem remote query
Signal quality
To check the signal quality on the plant as detected by the CMTS, use the commands
that display the signal quality and spectrum characteristics.
For signal noise:
Step
Command
Purpose
1.
show upstream [<x/y.c>] signal-quality
Displays signal
quality. To display all
the upstream
channels at once,
leave out the
upstream port
number.
Example:
CASA-CMTS# show upstream 1/4.1 signal-quality
Where:
X/Y.C is the slot/port.channel specification.
Check the following values in Table 1-1against the modulation profile to be sure the
noise level can support the modulation that is running. Use the show spectrum
snr-threshold-default command to display these values.
Table 1-1.
Signal quality modulation
Module
Conservative
Addressive
QPSK
130
100
8QAM
190
160
1-6

Debug cable plant
Table 1-1.
Signal quality modulation (continued)
Module
Conservative
Addressive
16QAM
220
190
32QAM
250
220
64QAM
280
250
128QAM
310
290
If the signal is too low, find the source of the noise or adjust attenuation first, then
adjust power levels.
Displaying the noise level
To display the noise level in tenths of a dB at each frequency on an upstream channel:
Step
Command
Purpose
1.
show spectrum upstream <x/y.c> [chan-wd>] raw
Displays signal noise

levels.
Where:
X/Y.C is the slot/port.channel specification.
<chan-wd> is the channel width; default is 6400000
Example:
CASA-CMTS# show spectrum upstream 1/4.1 raw
FREQUENCY NOISE-LEVEL at channel-width
6400000
(dB)
5000000: 13.0
11400000: 19.7
17800000: 13.4
24200000: 14.5
30600000: 07.8
37000000: 00.0
43400000: 00.0
49800000: 10.8
56200000: 09.0
62600000: 09.0
1-7
Debug cable modem
To determine the signal-to-noise ratio, subtract the dB from 42. In the above example,
the SNR at 49.8 MHz is 31.2. This will support 16 QAM, but not QAM per the table.
To debug the upstream ports, disconnect the port and run the show spectrum
upstream command. The result should be 0. If the result is not 0, then there is a
problem with the port.
Debug cable modem

To view the messages between a cable modem and the CMTS, perform the following
steps:
Step
Command
Purpose
1.
debug cable mac-address <mac-address>
Specify the MAC

address of the
modem.
Where:
<mac_address> is the media access control address of the
modem in hexadecimal format.
Example:
CASA-CMTS# debug cable mac-address
0015.f2fe.c904
Specify the asterisk (*) wildcard to filter portions of the MAC
address.
CASA-CMTS# debug cable mac-address 0015.*.*
continued
1-8

Debug cable modem
Step
Command
Purpose
2.
[no] debug cable [cfg | cm-ctrl | cm-status | dcc | dhcp |

dynsrv | load-balance | mac-address | packetcable |
privacy | ranging | registration | service-group |
specmgmt | tlv | verbose]
Specify the
information to
display.
Where:
cfg Debug cm downloading configuration file.
cm-ctrl Debug cable cm-ctrl msg.
cm-status Debug cable cm-status msg.
dcc Debug dynamic channel change.
dhcp Debug dhcp process <verbose>.
dynsvr Debug dynamic service transactions.
To view all the

ranging messages at
one time, do not
select an optional
argument
load-balance Debug cable load-balance [static |
dynamic].
mac-address Select cable modem to debug.
packetcable Debug packet cable.
privacy Debug baseline privacy process.
ranging Debug ranging process.
registration Debug registration process.
service-group Debug the service group.
specmgmt Spectrum management process.
tlv Debug TLV information on all MAC packets.
verbose Detailed information.
Example:
CASA-CMTS# debug cable tlv
Feb 26 14:26:08.483 CET: TLV-Block Bytes:
Feb 26 14:26:08.483 CET: 0x0000: 12 01 04 03
01 01 1D 01 01 19 1C 01 02 00 01 06
Feb 26 14:26:08.483 CET: 0x0010: 01 07 07 01
03 08 04 00 00 00 00 09 04 00 00 1F
Feb 26 14:26:08.483 CET: 0x0020: 40 0A 04 00
00 00 00 18 29 01 02 00 02 06 01 07
3.
logging debugging
Turn on debug
logging.
1-9
Example output:
Ranging information
[Fri Apr 3 13:34:34 2009]-DE-RNG-1: Sending RNG-RSP message to
0018.c0bf.1058 o n qam 0/0/3, power adjustment 0, frequency
adjustment 0, timing adjustment 0, status SUCCESS
[Fri Apr 3 13:34:44 2009]-DE-RNG-1: Grant 0018.c0bf.1058 ranging
opportunity on
upstream 1/5/0,iuc 4
[Fri Apr 3 13:34:44 2009]-DE-RNG-1: RNG_REQ message received from
0018.c0bf.105 8 on upstream 1/5/0, power offset 0, frequency
offset 234, timing offset 0, sid
220
[Fri Apr 3 13:34:44 2009]-DE-RNG-1: Sending RNG-RSP message to
0018.c0bf.1058 o n qam 0/0/3, power adjustment 0, frequency
adjustment 0, timing adjustment 0, status SUCCESS
For spectrum management debugging, specify more options as follows:

CASA-CMTS# [no]debug cable specmgmt [trace | poll | event | fft |fsm
|hop]

To display the cable modems that continually re-register:
CASA-CMTS# show cable flap-list
1-10


To display the cable modem configuration information:
Step
Command
Purpose
1.
show cable modem [<macaddr> | <ip-addr>] <info>

[ verbose ]
Display the cable

modem information.
Where:
<info> is one of the following:
classifiers Classifiers information.
counters Counter information.
cpe CPE information.
dropped-packets Dropped packets counters.
errors Error counters.
mac MAC layer information.
maintenance Maintenance information.
multicast-session Multicast session exists.
online Display online cable modems
phy PHY information
qos Quality of Service (QOS) information
remote-query show cable modem remote

information
vendor Vendor information
Example output:
MAC Address
IP Address
Prim Sid
MAC Domain
Upstream
Downstream
Timing Offset
Initial Timing Offset
Received Power
MAC Version
:0018.6892.89b8
:10.12.170.214
:870
:2
:4/13/0
:0/1/0
:2613
:2612
:0 dBmV
:DOC2.0
1-11
Qos Provisioned Mode

Enable DOCSIS2.0 Mode
Initial Ranging Message
Registration Request Message
Phy Operating Mode
Capabilities
Optional Filtering Support
Number of CPE IPs
CFG Max-CPE
Errors
Stn Mtn Failures
Total US Flows
Total DS Flows
Total US Data
Total US Throughput
Total DS Data
Total DS Throughput
Active Classifiers
DSA/DSX messages
Dynamic Secret
Total Time Online
:DOC1.0
:Y
:RNG-REQ
:REG-REQ
:tdma
:{Frag=Y, Concat=Y, PHS=N, Priv=N}
:{802.1P=N, 802.1Q=N}
:1
:16
:0 CRCs,0 HCSes
:0 aborts,0 exhausted
:1
:1
:392279 packets,62671197 bytes
:393 bits/sec,2 packets/sec
:725538 packets,978593918 bytes
:6140 bits/sec,4 packets/sec
:0
:permit all
:0000000000000000
:159378 s
Sample output from

Mac Addr
: 0018:6892:89b8
Sfid
:2461823
Current State
: Active
Sid
:870
Traffic Priority
:0
Maximum Sustained rate
: 2048000 bits/sec
Maximum Burst
: 1600 bytes
Mimimum Reserved rate
: 4000 bits/sec
Minimum Packet Size
: 0 bytes
Admitted QoS Timeout
: 0 seconds
Active QoS Timeout
: 0 seconds
Maximum Concatenated Burst
: 0 bytes
Scheduling Type
: Best Effort
Request/Transmission policy
: 0x0
IP ToS Overwrite[AND-mask, OR-mask]
: 0x0, 0x0
Current Throughput
: 0 bits/sec, 0 packets/sec
Contention request
: 94262
Piggyback request
: 173510
Grants scheduled
: 268341
Grants not used
: 0
Token bucket(min reserved bytes)
: 1467
Packet received
: 392284
Bytes received
: 62671708 (bytes)
HCS errors
: 0
CRC errors
: 0
1-12

Cable modem status
Sfid
: 2461951
Current State
: Active
Sid
: N/A
Traffic Priority
: 0
Maximum Sustained rate
: 12288000 bits/sec
Maximum Burst
: 3044 bytes
Mimimum Reserved rate
: 0 bits/sec
Minimum Packet Size
: 0 bytes
Admitted QoS Timeout
: 0 seconds
Active QoS Timeout
: 0 seconds
Maximum Concatenated Burst
: 0 bytes
Scheduling Type
: Not yet defined
Request/Transmission policy
: 0x0
IP ToS Overwrite[AND-mask, OR-mask]
: 0x0, 0x0
Current Throughput
: 0 bits/sec, 0 packets/sec
Cable modem status

The CMTS displays the following status information about the cable modems:
offline No signal from cable modem.
init(r1) Cable modem sent initial ranging.
init(r2) Cable modem is ranging.
init(ov) CMTS moving CM to a new channel during static load balancing.
init(rc) Cable modem ranging complete.
init(ua) Upstream channel adjustment (3.0 modems).
init(d) DHCP discover received by CMTS.
init(i) DHCP reply received from server; no DHCP request from CM.
init(e) Early authentication encryption started (3.0 modems).
init(t) TOD exchange started.
init(o) CM has started to download the config file.
init(r) CMTS received register-request from CM, but not reg-ack yet.
init(bpi) Baseline privacy started.
online Cable modem registered; enabled for data.
online(d) CM registered, but network access for the CM is disabled.
1-13

To get information from the modem, perform the following steps:
Step
Command
Purpose
1.
cable modem remote-query <x>
2.
show cable modem <mac> remote-query immediate

community string <string>
Configure remote
query at the CMTS
Where:
and verify that the
remote query is also
<x> is the polling interval in seconds; 0 turns the remote query configured on the
off.
modem.
Display the modem

information.
Where:
<mac> is the MAC address associated with the cable

modem.
<string> is the text defining the community string.
Example output:
The show cable modem command outputs the following information about the
modem:
MAC Address
IP Address
S/N
Ratio
US
Pwr
DS TX Time Micro(dB)
Pwr Offset Reflection
Modem
State
1-14

Debug PacketCable
Debug PacketCable
The debug cable packetcable command provides the following information:
Step
Command
Purpose
1.
debug cable packetcable
Start PacketCable
debugging.
Where:
cops COPS messages.
events Event messages.
gate Gate information.
control Gate control events.
docsis DOCSIS messages.
Example:
CMTS# debug cable packetcable cops
Debug IP
The debug ip commands are as follows:
Step
Command
Purpose
1.
debug ip [bgp | isis | multicast | ospf | rip | snmp]
Start IP debugging.
Where:
bgp BGP routing information.
isis IS-IS information.
multicast Debug multicast packets.
ospf OSPF information.
rip Routing Information Protocol (RIP) information.
snmp Debug IP SNMP.
Example:
CMTS# debug ip rip
1-15
Debug BGP
Debug BGP
The Border Gateway Protocol (BGP) debug commands are as follows:
Step
Command
Purpose
1.
[no] debug ip bgp [events |filters | fsm | keepalives |

updates]
Start BGP
debugging.
Where:
events BGP events.
filters BGP filters.
fsm BGP Finite State Machine.
keepalives BGP keepalives.
updates BGP updates.
Example:
CMTS# debug ip bgp events
1-16

Debug IS-IS
Debug IS-IS
The Intermediate System-to-Intermediate System (IS-IS) protocol commands are as
follows:
Step
Command
Purpose
1.
[no] debug ip isis [adj-packets | all |checksum-errors |

events | local-updates | protocol-errors | route-events |
snp-packets | spf-events | spf-statistics | spf-triggers |
update-packets ]
Start IS-IS protocol

debugging.
Where:
adj-packets IS-IS Adjacency related packets.
all All IS-IS packets.
checksum-errors IS-IS LSP checksum errors.
events IS-IS events.
local-updates IS-IS local update packets.
protocol-errors IS-IS LSP protocol errors.
route-events IS-IS route related events.
snp-packets IS-IS CSNP/PSNP packets.
spf-events IS-IS Shortest Path First events.
spf-statistics IS-IS SPF timing and statistic data.
spf-triggers IS-IS SPF triggering events.
update-packets IS-IS update related packets.
Example:
Display all IS-IS debugging statistics:
CASA-CMTS# debug ip isis all
[Thu Jul 21 10:47:43 2011]-DE-CDB-1: smm6:
cdb_pop_ack_cache(): ack cache is empty, dbid
= 10(repeat count 2)
IS-IS Adjacency related packets debugging is
on
IS-IS local updates debugging is on
IS-IS SPF triggering events debugging is on
IS-IS authentication debugging is on
IS-IS client/sever information debugging is on
1-17
Debug OSPF
Debug OSPF
This sction describes the debugging commands for the Open Shortest Path First
(OSPF) routing protocol. The OSPF debug commands provide the following
information:
1-18

Debug OSPF
Step
Command
Purpose
1.
[no] debug ip ospf [error | events | ism| lsa | nsm | nssa|

packet]
Start OSPF
debugging.
Where:
error OSPF error information.
events OSPF event information.
ism OSPF Interface State Machine:

events
status
timers
lsa OSPF Link State Advertisement.

flooding
generate
install
refresh
nsm OSPF Neighbor State Machine

events
status
timers
nssa OSPF NSSA information.
packet OSPF packets.
Example:
Display a list of OSPF errors:
CASA-CMTS# debug ip ospf error
Display a list of OSPF events:
CASA-CMTS# debug ip ospf events
continued
1-19
Debug OSPF
Step
Command (continued)
Purpose
Display information about the interface state machine:

CASA-CMTS# debug ip ospf ism events
CASA-CMTS# debug ip ospf ism status
CASA-CMTS# debug ip ospf ism timers
Display information about link-state advertisement (LSA
events:
For flood events (updates received and acknowledgements):
CASA-CMTS# debug ip ospf lsa flooding
For LSA events:
CASA-CMTS# debug ip ospf lsa generate
For other events:
CASA-CMTS# debug ip ospf lsa install
CASA-CMTS# debug ip ospf lsa refresh
Display messages containing information about neighbor

events:
CASA-CMTS# debug ip ospf nsm events
CASA-CMTS# debug ip ospf nsm timers
CASA-CMTS# debug ip ospf nsm status
Display messages containing information about nssa:

CASA-CMTS# debug ip ospf nssas
1-20

Debug OSPF
OSPF packet information

To display information about each packet transmitted and received:
Step
Command
Purpose
1.
debug ip ospf packet

[all|dd|hello|ls-ack|ls-request|ls-update] [(send
[detail]|recv [detail]|detail)]
Display information
about each packet
transmitted and
received.
Where:
all Lists all OSPF packets.
dd Gives the database description.
hello Shows the OSPF hello traffic.
ls-ack Shows the OSPF link state acknowledgements.
ls-request Shows the link state requests.
ls-update Shows the link state update.
send Displays the sent packets.
detail Shows the details.
recv Displays the received packets.
Example:
CASA-CMTS# debug ip ospf packet all
1-21
Debug RIP
Debug RIP
The Routing Information Protocol (RIP) commands provide event and packet
information.
Step
Command
Purpose
1.
debug ip rip [events | packets]
Display RIP
information.
Where:
events RIP events.
packets RIP packets.
Example:
CASA-CMTS# debug ip rip packets
Debug LACP
The Link Aggregation Protocol (LACP) commands provide finite state machine,
events and LACP packet information:
Step
Command
Purpose
1.
debug ip lacp [fsm| events | packets]
Display LACP
information.
Where:
fsm Finite state machine.
events LACP events.
packets LACP packets.
Example:
CASA-CMTS# debug ip lacp fsm
1-22

Connection testing
Connection testing
For testing connectivity, the Casa CMTS supports the extended ping command with
Linux arguments that you enclose in quotations ().
In the following example, 192.168.3.8 is a host on the gige side and 10.248.1.1 is the
IP-bundle interface.
CASA-CMTS# ping "-I 10.248.1.1 192.168.3.8"
PING 192.168.3.8 (192.168.3.8) from 10.248.1.1 : 56(84)
64 bytes from 192.168.3.8: icmp_seq=1 ttl=64 time=0.357
bytes of data.
ms
ms
ms
2-1
Chapter 2. Casa CMTS diagnostics

commands
The Casa CMTS supports the following diagnostics:
SMM (GigE) and QAM diagnostics
Upstream and downstream diagnostics
DHCP tracing
System kernel messages
GigE interface monitoring
IP path tracing
Cable modem traffic monitoring
Core dumps
In addition, problems with the kernel will usually leave core dumps in memory that
can be retrieved and sent to Casa for analysis. The diagnostics are available in
diagnostic mode, by entering "diag" at the enable prompt and then entering the
password. This chapter covers the following topics:
Topic
Page
SMM diagnostics
2-2
QAM diagnostics
2-4
Downstream and upstream interface statistics
2-4
Checking for downstream errors
2-8
Upstream diagnostics (Release 5.4 only)
2-9
Past DHCP transactions
2-9
2-2

SMM diagnostics
Topic
Page
2-10
Capturing packets on the GigE interfaces
2-11
Tracing the IP path
2-13
Capturing cable modem traffic on the SMM
2-16
Displaying cable modems by modem ID
2-18
Core dumps
2-19
Removing old core dump files
2-19
Testing connectivity (extended Ping)
2-20
Other diagnostic commands
2-20
ARP table entry
2-21
Auto-reboot
2-21
Set the CPU receive rate
2-22
Turning power on and off to individual CMTS module
2-22
Shutdown or restart SNMP
2-23
Show ACL applications
2-23
Reboot a module unconditionally
2-24
Show kernel interface information
2-25
Display modem information by QAM
2-26
Display VLAN information
2-28
Display information about modems on a VLAN
2-29
SMM diagnostics
Two diagnostic commands are available for the SMM. One reports information on the
network side, and the other reports information about the path between the SMM and
the line cards. The second command is described in the section, QAM diagnostics.
Casa CMTS diagnostics commands
2-3
SMM diagnostics
To obtain information about the SMM GigE ports:

Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS(diag)#
2.
show gige <number> stats

Where:
<number> is the GigE port number on the SMM.
Example:
CASA-CMTS(diag)#show gige 2 stats
Example output:
CMTS(diag)#show gige <number> stats
snmpIfInOctets = 359733,
snmpIfInUcastPkts = 2002
snmpIfInNUcastPkts = 453,
snmpIfInDiscards = 378
snmpIfInErrors = 0,
snmpIfInUnknownProtos = 0
snmpIfOutOctets = 386113,
snmpIfOutUcastPkts = 2055
snmpIfOutNUcastPkts = 234,
snmpIfOutDiscards = 0
snmpIfOutErrors = 0,
snmpIfOutQLen = 0
snmpIpInReceives = 1808,
snmpIpInHdrErrors = 0
snmpIpForwDatagrams = 1402,
snmpIpInDiscards = 0
snmpDot1dBasePortDelayExceededDiscards = 0,
snmpDot1dBasePortMtuExceededDiscards = 0
snmpDot1dTpPortInFrames = 2456,snmpDot1dTpPortOutFrames =2289
snmpDot1dPortInDiscards = 0,
snmpEtherStatsDropEvents = 0
snmpEtherStatsMulticastPkts = 580,
snmpEtherStatsBroadcastPkts=108
snmpEtherStatsUndersizePkts = 0,snmpEtherStatsFragments = 0
snmpEtherStatsPkts64Octets = 767,
snmpEtherStatsPkts65to127Octets = 1383
2-4

QAM diagnostics
QAM diagnostics
The QAM diagnostics reports statistics about the QAM card, information about the
memory, and information about the data path between the SMM and the QAM.
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS(diag)#
2.
show module <number> stat qam

Where:
<number> is QAM slot number.
Example:
CASA-CMTS(diag)# show module 2 stat qam
Example output:
CASA-CMTS(diag)# show module 2 stat qam
mux_mgr_cnt: 512
pmt_mgr_free_cnt: 512
pid_mgr_free_cnt: 2000
pg_queue_free_cnt: 464
pkt_recv_cnt: 0
pkt_drop_cnt: 0
pkt_null_cfg: 0
pkt_no_egress: 0
ts_pkt_recv_cnt: 0
ts_pkt_drop_cnt: 0
hibuf_enqueued: 0
hibuf_dequeued_tx: 0
hibuf_enqueued_failed: 0
hibuf_drop: 0
hibuf_depth: 0
overflow hibuf to be free: 0
asi pkt tx: 0
asi data rate: 0
docsis pkt send cnt: 0
docsis pkt drop cnt: 0
docsis upstream data pkt cnt: 18297
Show the QAM

module statistics.
2-5
docsis downstream unicast pkt cnt: 20

enqueue limit per sf: 45000
pkt drop due to enqueue limit: 0
ups_proc_step = 80
ds_proc_step = 80
ds_data_enqueue_cnt = 0

The interface diagnostics reports downstream and upstream interface information.
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS(diag)#
2.
show interface qam <number> stat
Show the
QAMdownstream
interface statistics.

Example: Release 5.4
CASA-CMTS(diag)#show interface qam 0/1 stat
CASA-CMTS(diag)#show interface qam 0/0
3.
show interface upstream <number> stat
Show the
QAMdownstream
interface statistics.

CASA-CMTS(diag)# show interface upstream 0/1
stat
2-6

Example output: show interface qam (Release 5.4)

CASA-CMTS(diag)# show interface qam 0/1 stat
Interface QAM 0/1
IP address not assigned
MAC address 0017.1001.d189
Admin Status: UP
Channel 0:
Frequency
: 573000000
Network ID
: 0
Transport Stream ID : 0
Current throughput : 492 (Kb/s)
Number of active Streams: 0
Admin Status
: UP
Channel 1:
Frequency
: 579000000
Network ID
: 0
Admin Status
: UP
Channel 2:
Frequency
: 585000000
Network ID
: 0
Admin Status
: UP
Channel 3:
Frequency
: 591000000
Network ID
: 0
Admin Status
: UP
Example output:show interface qam (Release 5.2)

CASA-C2200-152(diag)#show interface qam 0/0
interface qam 0/0
no spectral inversion on
annex B
modulation 256qam
interleave 16
power 510
channel 0 frequency 615000000
channel 0 dsg dcd-enable
no channel 0 shutdown
2-7

no shutdown
!
Example output:show interface upstream (Release 5.4)

CASA-CMTS(diag)# show interface upstream 1/0 stat
Interface upstream 1/0 statistics
Admin status: UP
Received 18 broadcasts, 0 multicasts, 52736 unicasts
0 discards, 0 errors, 0 unknown protocol
84809 Unerroreds, 0 Correcteds, 0 Uncorrectables
Total Modems On This Upstream Channel: 1 ,1 active cm,0 secondary cm
Req Mslots 1883329570, Used Req Mslots 21280
Init Mtn Mslots 142217505, Used Init Mtn Mslots 0
Total Mslots 2025800893, Ucast Granted Mslots 253802
Avg upstream channel utilization: 0
Channel utilization interval: 30
Example output:show interface upstream (Release 5.2)

interface upstream 3/2
frequency 28000000
channel-width 3200000
power-level 0
power-adjustment continue 2
power-adjustment noise-percentage 30
power-adjust threshold 1
voice-bw-reserve 75
rate-limit
no ingress-cancellation
logical-channel 0 prov-attr-mask 0x0
logical-channel 0 profile 2
logical-channel 0 minislot 2
logical-channel 0 data-backoff automatic
logical-channel 0 ranging-backoff 0 4
no logical-channel 0 pre-equalization
logical-channel 0 ranging-priority 0x0
logical-channel 0 class-id 0x0
no logical-channel 0 shutdown
no shutdown
2-8


When checking for downstream errors between any QAM and the SMM from
diagnostic mode, note the following:
eth 1 is the QAM to SMM interface
eth 2 is the QAM to FPGA interface
If the errors on the eth 1 interface exceed 0.1% (divide errors by total rx), the SMM is
likely the cause of the errors. To confirm, replace the QAM and see if the errors are
still present. The following trouble-shooting steps will be necessary:
1.
If there are spares, swap the QAM first and recheck.
2.
If the errors persist after swapping the QAM, swap the SMM.
3.
If there are still errors, then the card cage must be replaced.
To check for downstream errors:

Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
show module <number> stat gige

Where:
<number> is QAM module number.
Example:
CASA-CMTS(diag)# show module 2 stat gige
Example output:
CASA-CMTS(diag)# show module 2 stat gige
Port eth1 or eth2:
total rx
: 351556736
dma0
: 71148
dma1
: 351485588
kernel : 3372
Show the QAM

downstream
statistics.
2-9
local :
drop
:
error
:
crc err
:
hi_water 0 :
hi_water 1 :
bitrate rx0:
bitrate rx1:
bitrate tx0:
351556736
0
0
0
4
11
0
2585360
8192
total tx
kernel
drop
error
1558768
11167
0
0
:
:
:
:
0 or less than .1% when divided by total rx

To obtain the SMM and the upstream card diagnostics, use the same command as
described in the previous section.
Past DHCP transactions

For problems with modems registering over the Dynamic Host Control Protocol
(DHCP), check the 128 past DHCP transactions:
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
show dhcp-trace
Show DHCP
transactions.
Example:
CASA-CMTS(diag)# show dhcp-trace
Example output:
CASA-CMTS(diag)# show dhcp-trace
0
US DIS xid=0149d38f domain=02 lc=1 ch= 2 tm=49f91c34 cm_id=00000022
2-10

yip=000.000.000.000
00:12:c9:20:5a:ea
xid=0149d38f
domain=02 lc=1 ch= 0
yip=010.231.001.128
00:12:c9:20:5a:ea
xid=0149d38f
00:12:c9:20:5a:ea
xid=0149d38f
yip=010.231.001.128
gw=010.231.001.001 s=192.168.009.001 0
DS OFF
tm=49f91c34 cm_id=00000022
gw=010.231.001.001 s=192.168.009.001 0
US REQ
tm=49f91c34 cm_id=00000022 yip=000.000.000.000

gw=010.231.001.001 s=192.168.009.001 0 DS ACK
tm=49f91c34 cm_id=00000022

Serious problems with the CMTS system kernel will result in error messages that are
collected in non-volatile random-access memory (NVRAM). To view these messages,
use the show dmesg command.
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
show dmesg
Show CMTS system

kernel messages.
Example:
CASA-CMTS(diag)# show dmesg
Look for messages that are repeated more than 10 times. Messages containing the
words oops, panic, warning, are considered critical as in the examples below:
[1265795931] Oops in arch/mips/mm/fault.c::do_page_fault, line
185[#1]:
[1265795931] Cpu 0
1265795931] $ 0
: 00000000 10001f01 00000000 00000000
1265795931] $ 4
: 803f0004 00000000 00000057 82f69f2a
1265795931] $ 8
: 82f69fe0 00001f00 00000000 82fca000
Copy these messages and send them to support@casa-systems.com.

2-11

To capture the packets on a GigE interface, use the tcpdump command. To display
the output on the screen or to write the output to a file, perform these steps:
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
tcpdump -i gige <number>
Start the tcpdump

routine on a GigE
interface.
Where:
-i Specifies that an interface on which to listen will be

specified in the next argument.
<number> The GigE interface number on the SMM.
Example:
CASA-CMTS(diag)# tcpdump -i gige 1
3.
tcpdmp -i gige <number> -w /fdsk/filename

Where:

<number> The GigE interface port number on the

SMM.
-w Write the output to the specified directory and

filename on the SMM. The dir command displays the file.
Write tcpdump
output to a file on the
SMM.
Example:
CASA-CMTS(diag)# tcpdump "-i gige 1 -w /
fdsk/test.out
To read the file, move it from the SMM to a TFTP server.
2-12

Use the other tcpdump arguments to specify specific traffic to capture, such as traffic
running over UDP ports 67 and 68.
Example
CMTS(diag)#tcpdump "-i gige 0 -vvv udp port 67 or udp port 68"
To collect the traffic to a specific host (such as the DHCP server):

Example
CMTS(diag)#tcpdump "-i gige 0 host 192.168.1.1
Example output:
*****
Type Ctrl-C to exit
*****
tcpdump: listening on eth2, link-type EN10MB (Ethernet), capture size
65535 bytes
38 packets captured
38 packets received by filter
0 packets dropped by kernel
Sample file listing:
19106 Dec 22 13:37 core.SMM-crl_rpc_server.275.txt
454281 Jan 27 15:49 core.SMM-shell.exe.tar.gz
2411 Jan 27 15:49 core.SMM-shell.exe.txt
24 Mar 9 14:35 test.out
Parse the file and send it to support@casa-systems.com.
2-13
Tracing the IP path
Tracing the IP path

To trace the IP path from any source to any destination, use the traceroute command
with the following options. The options must be enclosed in quotation marks.
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
CMTS(diag)# traceroute "[ -dFInrvx ] [ -f first_ttl ] [ -g

gateway] [ -i iface ] [ -m max_ttl ] [ -p port ] [ -q nqueries ]
" [ -s src_addr] [ -t tos ][ -w waittime ] [ -z pausemsecs ]
host [ packetlen ]"
Trace the IP path

from source to
destination.
Where:
-d Enable socket level debugging.
-F Set the "Don't Fragment" bit.
-I Use ICMP ECHO for probes.
-n Do not try to map IP addresses to host names when

displaying them.
-r Bypass the normal routing tables and send directly to

a host on an attached network. If the host is not on a
directly-attached network, an error is returned. This option
can be used to ping a local host through an interface that
has no route through it.
-v Verbose output. Received ICMP packets other than

TIME_EXCEEDED and UNREACHABLEs are listed.
-x Toggle IP checksums. Normally, this prevents

traceroute from calculating IP checksums. In some cases,
the operating system can overwrite parts of the outgoing
packet but not recalculate the checksum (so in some
cases the default is to not calculate checksums and using
x causes them to be calculated). Note that checksums
are usually required for the last hop when using ICMP
ECHO probes ( -I ). So they are always calculated when
using ICMP.
2-14

Tracing the IP path
Step
Command
Purpose
continued
-f first_ttl Specifies with what TTL to start. Defaults to

1.
-g gateway Tells traceroute to add an IP source routing

option to the outgoing packet that tells the network to route
the packet through the specified gateway. Not very useful
because most routers have disabled source routing for
security reasons.
-i iface Specifies the interface through which traceroute

should send packets. By default, the interface is selected
according to the routing table.
-m max_ttl Specifies the maximum number of hops

(max time-to-live value) traceroute will probe. The default
is 30.
-p port For UDP tracing, specifies the destination port

base traceroute will use (the destination port number will
be incremented by each probe).
-q nqueries Sets the number of probe packets per hop.

The default is 3.
-s src_addr Chooses an alternative source address.

Note that you must select the address of one of the
interfaces. By default, the address of the outgoing
interface is used.
-t tos For IPv4, set the Type of Service (TOS) and

Precedence value. Useful values are 16 (low delay) and 8
(high throughput). Note that in order to use some TOS
precendence values, you have to be super user.
-w waittime Set the time (in seconds) to wait for a

response to a probe (default 5.0 sec.).
-z pausemsec Minimal time interval between probes

(default 0). If the value is more than 10, then it specifies a
number in milliseconds, else it is a number of seconds
(float point values allowed too). Useful when some routers
use rate-limit for icmp messages.
host Host name or IP address.
packetlen The default probe datagram length is 38

bytes, but this may be increased by specifying a packet
size (in bytes) after the destination host name.
2-15
Tracing the IP path
Example output:
traceroute to verizon.net (206.46.232.39), 30 hops max, 38 byte
packets
1 192.168.2.1 (192.168.2.1) 0.564 ms 0.438 ms 0.402 ms
2 192.168.1.1 (192.168.1.1) 1.724 ms 1.482 ms 1.334 ms
3 192.168.0.1 (192.168.0.1) 3.573 ms 3.308 ms 3.400 ms
4 209.101.35.209 (209.101.35.209) 4.334 ms * 4.179 ms
5 208-41-205-1.client.dsl.net (208.41.205.1) 20.577 ms 16.912 ms
19.954 ms
6 ge-2-2-0.c00.nyc.megapath.net (155.229.123.121) 19.863 ms 17.526
ms 19.568 ms
7 ge-6-5.car1.NewYork1.Level3.net (209.246.126.1) 19.946 ms 17.224
ms 19.897 ms
8 vlan69.csw1.NewYork1.Level3.net (4.68.16.62) 19.893 ms 17.967 ms
19.767 ms
9 ae-64-64.ebr4.NewYork1.Level3.net (4.69.134.113) 24.904 ms
22.647 ms *
10 ae-6-6.ebr2.NewYork2.Level3.net (4.69.141.22) 19.224 ms 17.346
ms 19.626 ms
11 ae-2-52.edge2.NewYork2.Level3.net (4.69.138.227) 23.098 ms
17.541 ms ae-1-51.edge2.NewYork2.Level3.net (4.69.138.195) 25.399
ms
12 0.ge-2-0-0.BR3.NYC4.ALTER.NET (204.255.173.53) 17.668 ms
mci-level3-xe.newyork2.Level3.net (4.68.110.234) 17.970 ms
mci-level3-xe.newyork2.Level3.net (4.68.110.106) 57.640 ms
13 0.xe-0-1-3.XL3.NYC4.ALTER.NET (152.63.17.58) 18.088 ms
0.xe-5-0-3.XL3.NYC4.ALTER.NET (152.63.18.6) 17.976 ms
0.xe-5-1-3.XL3.NYC4.ALTER.NET (152.63.16.182) 19.120 ms
14 0.ge-7-2-0.XL3.DFW7.ALTER.NET (152.63.0.34) 102.254 ms 101.897
ms 104.069 ms
15 POS7-0.GW2.DFW13.ALTER.NET (152.63.103.229) 103.922 ms
POS6-0.GW2.DFW13.ALTER.NET (152.63.103.225) 102.292 ms 101.520 ms
16 verizon-gw.customer.alter.net (63.65.122.26) 104.015 ms 102.131
ms 103.928 ms
17 po121.ctn-core1.vzlink.com (206.46.225.18) 114.777 ms 101.656 ms
103.760 ms
18 206.46.228.130 (206.46.228.130) 104.236 ms 101.775 ms 104.338 ms
19 206.46.232.34 (206.46.232.34) 103.508 ms 102.530 ms 103.747 ms
2-16


To capture the traffic to and from a cable modem on the SMM (in flash) instead of a
remote server, use the mirror and tcpdump commands together.
First, open one window on the CMTS and start the mirror command (where 1.0.0.7 is
the IP address of the SMM interface):
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
mirror cm traffic <ip_addr> <mac_addr>

Where:
<ip_addr> IP address of the SMM.
<mac_addr> MAC address of the cable modem.
Example:
CASA-CMTS(diag)# mirror cm traffic 1.0.0.7
0018.c0bf.1058
Mirroring traffic for CM 0014.f887.d939 to
0x1000007
Begin monitoring
cable modem traffic.
2-17
Step
Command
Purpose
3.
tcpdmp -i gige<number> -w /fdsk/filename -s 0 udp port

<port_address> or udp port <port_address>
Write tcpdump
output to a file on the
SMM.
Where:

<number> Indicates the GigE interface port number on

the SMM.
-w Writes the output to the specified directory and

filename on the SMM. The dir command displays the file.
/fdsk/filename Specifies the name of the destination

file to which tcpdump information is written.
-s Specifies the number of bytes of data per packet.
0 Specifies the number of bytes of data per packet. 0

indicates no limit to the number of bytes.
<port_address> The UDP upstream and downstream

port addresses.
Example:
CASA-CMTS(diag)# tcpdump "-i gige1 -w /
fdsk/file.out -s 0 udp port 0xcace or udp

port 0xcacf
To read the file, move it from the SMM to a TFTP server.
Example output:
CASA-CMTS(diag)# tcpdump "-i gige1 -w /fdsk/file.out -s 0 udp
port 0xcace or udp port 0xcacf

*****
Type Ctrl-C to exit
*****
tcpdump: listening on eth2, link-type EN10MB (Ethernet), capture size
65535 bytes
In the first window, reset the cable modem. After a few minutes, type Ctrl-C key
combination to stop the capture, then transfer the file to the TFTP server. (Remember
to delete it from the SMM after transferring it.)
2-18

On the TFTP server, run the ccap command (./ccap test.out) to create a file called
out.cap. Use FTP to transfer this file to a PC running Wireshark (or a program
equivalent to Wireshark).
Change the Wireshark settings by editing preferences and frame protocols by
checking off the Treat all frames as DOCSIS frames box. Wireshark will decode the
DOCSIS control packets.

Cable modem status can be displayed by specifying the cable modem identifier from
the CMTS diag mode. Gathering cable modem information using the CMTS identifier
may be helpful when troubleshooting modem problems.
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
show cable <modem_id->
Begin monitoring
cable modem traffic.
Where:
<modem_id> Specifies the cable modem ID in the

range 1 to 4294967295.
Example:
CASA-CMTS(diag)# show cable modem 1
Example
CASA-C3000(diag)#show cable modem 1
MAC Address
IP Address
US
Intf
0026.5e77.43ba 0.0.0.0
3/1/0*
2000:232:1::6de2:d447
MAC Address
IP Address
US
DS
Intf
0/0/1*
MAC
Status
online(pt)
Prim RxPwr Timing Num BPI

Sid (dB) Offset CPEs Enb
29
-0.2 2359
0
yes
DS
MAC
Prim RxPwr Timing Num
BPI
2-19
Core dumps
0024.0147.9a2c 10.232.1.51
Intf
3/1/0

MAC Address
IP Address
US
Intf
5cac.4c9c.793b 0.0.0.0
3/1/0*
2000:232:1::f6ba:e732
CASA-C3000(diag)#
Intf
0/0/0
Status
online(pt)
Sid
27
(dB)
0.0
Offset CPEs Enb

2357
0
yes
DS
Intf
0/0/1*
MAC
Status
online(pt)
Prim RxPwr Timing Num BPI

Sid (dB) Offset CPEs Enb
30
-0.2 2363
0
yes
Core dumps
Serious problems with the kernel processes will cause the system to dump core
memory. These core dumps contain useful data for Casa engineering. Use the ls or dir
commands to see if these files exist. Core dumps start with the word core in the title as
in:
637205
18395
424762
17561
Dec
Dec
Nov
Nov
4
4
9
9
11:08
11:08
13:09
13:09
core.QAM-0-qam_daemon.145.tar.gz
core.QAM-0-qam_daemon.145.txt
core.SMM-snmpd.292.tar.gz
core.SMM-snmpd.292.txt
Use TFTP to transfer both the text and gz files; send them to
support@casa-systems.com.
Removing old core dump files

Delete old core dumps from memory:
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
coredump cleanup
Remove old core

dump files.
Example:
CASA-CMTS(diag)# coredump cleanup
2-20


For testing connectivity, the Casa CMTS supports the extended ping command with
Linux arguments that you enclose in quotations ().
In the following example, 192.168.3.8 is a host on the gige side and 10.248.1.1 is the
IP-bundle interface.
CASA-CMTS# ping "-I 10.248.1.1 192.168.3.8"
PING 192.168.3.8 (192.168.3.8) from 10.248.1.1 : 56(84)

Other useful diagnostic commands include:
Get ARP table entry
Auto-reboot
Set CPU receive rate
Turn off power modules
Shutdown/restart SNMP
Reboot module unconditional
Show kernel interface
bytes of data.
ms
ms
ms
2-21
ARP table entry

To get the ARP entry for a specific host:
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
arp get <ip_address>
Get host ARP entry.
Where:
<ip_address> is the host IP address.
Example:
CASA-CMTS(diag)# arp get 192.168.8.232
Auto-reboot
To configure the CMTS to auto-reboot if it does not receive a response from a
specified host within 40 seconds:
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
auto-reboot monitor <ip_address>
Set CMTS to
auto-boot.
Where:
<ip_address> is the host IP address.
Example:
CASA-CMTS(diag)#auto-reboot monitor
192.168.8.100
2-22

Set the CPU receive rate

To set the receive rate from the gigabit switch to the CPU interface:
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
gigabit-rx-cpu-rate <rate>
Set the CPU receive

rate.
Where:
<rate> is number between 0 and 8000 packets per second.
Example:
CASA-CMTS(diag)# gigabit-rx-cpu-rate 1000
Turning power on and off to individual CMTS module

To individually turn power on and off to specified CMTS modules:
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
power module <number> {on | off}

Where:
<number> specifies the module number in the range
0 to 15 depending on the specific CMTS you are managing.
Example:
CASA-CMTS(diag)# power module 4 off
Turn a specific
power module on or
off.
2-23
Shutdown or restart SNMP

To reset SNMP, first shut it down and then restart it.
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
snmp shutdown
Shutdown and
restart SNMP.
snmp restart
Example:
CASA-CMTS(diag)# snmp shutdown
CASA-CMTS(diag)# snmp restart

To show the application when an access control list is applied:
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
show ip access-list <name> applications
Show the
ACL-associated
applications.
Where:
<name> is the access list name.
This command accepts output modifiers.
Example:
CASA-CMTS(diag)# show ip access-list acl50
applications
2-24

Reboot a module unconditionally

To force a module to reboot in the event that the module reboot command does not
complete:
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS(diag)#
2.
reboot module <number> unconditional

Where:
<number> is the slot number of the module to be rebooted.
Example:
CASA-CMTS(diag)# reboot module 3 unconditional
Force an
unconditional reboot
of a specific module.
2-25
Show kernel interface information

To show information about the access control lists per interface:
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
show kernel interface <interface> acl
Show kernel
interface information.
Where:
<interface> is one of the following options:
eth <port> Ethernet interface with port specified.
gige <port> GigE interface with port specified.
trunk <port> Trunk interface with port specified.
loopback <number> The loopback interface number .
docsis-mac <ID> The DOCSIS mac-domain ID.
access-class {in | out} The system-level access class

(in or out).
Example:
CASA-CMTS(diag)# show kernel interface
docsis-mac 4 acl
2-26


To show the information about a modem associated with the QAM on which it is
registered:
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
show qos ds cm qam <number> ip address <ip_address> Show modem

information by QAM.
Where:
<number> is the QAM module number.
<ip_address> is the IPV4 or IPV6 address of the modem.
Example:
CASA-CMTS(diag)# show qos ds cm qam 4 ip
address 4.5.6.7
Example output:
ttl=341785873 ip=341228169 uni=340333695 mc=0
nx=0 ty=1 lc= 0 mcast=0000 pcnt=35 10.155.127.149 00186855961d cm_id=2983
cid=10
cm_tbl_idx= 3786 cm_id=2983 cid=10 psid=1452 v=0 00186855961d tek=025b1568
pkt: 0 18419 dbyte=14743143 arp: 18 14 dhcp: 2 2 maxip: 16 2 0 a=0 l=1
SF sf=01793f48 nx=017a4748 cm=2983 sfid=763903 dsid=1452 domain=3 f=01 tos_ow
=0xff00
cnt pkt=18180 byte=13621440 pkt sent=18180 byte sent=13621440 over_mx
drop_pkt=0 drop_byte=0
enqueue 0 pkt 0 byte marker_in 0 enqueue_priority 0 enqueue_limit 750000
qos_set_type: 06 docsis version: 0
active: priority=0 g_rate=0 g_bucket=60880 mx_rate=16001 mx_bucket=60880
gu_rate_bucket_counter = 60880, mx_rate_bucket_counter = 59560
mx_gu_negative = 0
admitted: priority=0 g_rate=0 g_bucket=60880 mx_rate=16000
mx_bucket=60880
mapping pri 0
enqueue pri 0 marker in 0
channel set id: 10
[ 10 ]
debug: gu_rate=0 mx_rate=3200001 lapsed=1614 mx_c=16000 gu_c=0
lct=0000e8a8
SF sf=017a4748 nx=00000000 cm=2983 sfid=763777 dsid=1452 domain=3 f=00 tos_ow
=0xff00
cnt pkt=239 byte=35067 pkt sent=239 byte sent=35067 over_mx drop_pkt=0
drop_byte=0
enqueue 0 pkt 0 byte marker_in 0 enqueue_priority 0 enqueue_limit 16000
2-27
qos_set_type: 06 docsis version: 0

active: priority=1 g_rate=0 g_bucket=60880 mx_rate=241 mx_bucket=60880
gu_rate_bucket_counter = 60880, mx_rate_bucket_counter = 58380
mx_gu_negative = 0
admitted: priority=1 g_rate=0 g_bucket=60880 mx_rate=240 mx_bucket=60880
mapping pri 0
enqueue pri 0 marker in 0
channel set id: 10
[ 10 ]
debug: gu_rate=0 mx_rate=48001 lapsed=154 mx_c=240 gu_c=0 lct=0000e40c
DS Classifiers:
CL cl=00a70768 nx=00a706f0 cm=2983 cl_id=15 sfid=763777 pri=0 es=0 ipver=4
ipv4 tos=00 00 00 proto=256
dip=00000000 00000000 sip=c0a8fe80 fffffffe sp=0 65535 dp=0 65535
ipv6 label 0x0 tos 0x0 0x0 0x0, next hdr 0x100, src ::/0, dst ::/0
vlan id low=0 high=0
pri low=0 high=0
pkt=0 byte=0 phs=00000000
CL cl=00a706f0 nx=00a70678 cm=2983 cl_id=14 sfid=763777 pri=0 es=0 ipver=4
dip=00000000 00000000 sip=3eb3013c fffffffc sp=53 53 dp=0 65535
pri low=0 high=0
pkt=219 byte=28771 phs=00000000
CL cl=00a70678 nx=00a70600 cm=2983 cl_id=13 sfid=763777 pri=0 es=0 ipver=4
dip=00000000 00000000 sip=3eb30280 ffffffc0 sp=0 65535 dp=0 65535
pri low=0 high=0
dip=00000000 00000000 sip=0a800140 fffffffe sp=0 65535 dp=0 65535
pri low=0 high=0
dip=00000000 00000000 sip=ac1f8000 fffff000 sp=0 65535 dp=0 65535
pri low=0 high=0
dip=00000000 00000000 sip=0a800700 ffffff00 sp=0 65535 dp=0 65535
pri low=0 high=0
pkt=20 byte=5340 phs=00000000
CL cl=00a70498 nx=00000000 cm=2983 cl_id=9 sfid=763777 pri=0 es=0 ipver=4
dip=00000000 00000000 sip=c0a8fc00 fffffc00 sp=0 65535 dp=0 65535
pri low=0 high=0
DS L2VPN Classifiers:
prt_ds_classifier_list(): null pointer
TEK addr=025b1568 nx=00000000 cm=2983 mac=0 said=1452 active_time=0 pkt=18402
alg=1
s1= 1 bb1e28c3679745d60e38cd7cdcf7d23b
2-28


To show the information about the VLANs associated with the QAM on which it is
registered:
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
show qos ds cm qam <number> ip address <ip_address> Show VLAN

114
information by QAM.
Where:
Example:
address 114
Example output:
CASA-C10000(diag)#show qos ds cm qam 4 ip address 114
L2VPN US: ttl=0 drop=0
DS: ttl=0 drop=0 NotDefined pkt=0 id=0
bc_src=0
l2vpn_vlan_tbl_prt():
l2vpn_addr_hs_tbl_prt():
CASA-C10000(diag)#CASA-C10000(diag)#
2-29

To show the information about the modems on a VLAN:
Step
Command
Purpose
1.
diag
Enter diagnostic
mode in the CLI.
Example:
CASA-CMTS# diag
CASA-CMTS (diag)#
2.
show qos ds cm qam <number> ip address <ip_address> Show information

115
about modems on a
VLAN.
Where:
Example:
address 115
Example output:
CASA-C10000(diag)#show qos ds cm qam 4 ip address 115
qam_cm_vlan_mac_tree_prt():
qam_vlan_cm_mac_tree_prt():
qam_vlan_mac_tree_prt(): vlan_mac
qam_vlan_mac_tree_prt(): vlan_mac_uniAddr
qam_vlan_mac_tree_prt(): vlan_mac_mcAddr
qam_l2vpn_cm_stat_tree_prt():
CASA-C10000(diag)#
Casa Systems, Inc.

100 Old River Road
Suite 100
Andover, MA 01810
USA
978-688-6706
Casa Systems
CMTS
2011 Casa Systems, Inc.
All rights reserved.
DOC-3006-01
Release 6.0.3
July 2011
Printed in United States of America

CMTS Debug - DiagRef - 7 - 27 - 11 - Release - 6.0.3

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

CMTS Debug - DiagRef - 7 - 27 - 11 - Release - 6.0.3

Transféré par

Droits d'auteur :

Formats disponibles

Casa Systems

Debugging and Diagnostics

2011 Casa Systems, Inc.

Chapter 1. Casa CMTS debugging commands

Casa Systems CMTS Release 6.0.3

Debugging and Diagnostics Reference

Debug PacketCable ........................................................................................ 1-14

Chapter 2. Casa CMTS diagnostics commands

Casa Systems CMTS Release 6.0.3

Debugging and Diagnostics Reference

Reboot a module unconditionally ..............................................................2-24

Casa Systems CMTS Release 6.0.3

About this guide

The following topics are covered in this guide:

Casa Systems CMTS Release 6.0.3

Debugging and Diagnostics Reference

Casa Systems C2200 CMTS Quick Installation

Casa Systems C2200 CMTS Hardware Installaton Guide

Casa Systems C3200 CMTS Quick Installation

Casa Systems C3200 CMTS Hardware Installation Guide

Casa Systems C10200 CMTS Hardware Installation Guide

Casa Systems C10G CMTS Hardware Installation Guide

Casa Systems C10G/C10200 CMTS Quick Installation

Casa Systems CMTS Software Configuration Guide

Casa Systems CMTS Debugging and Diagnostics Reference

Casa Systems CMTS Release 6.0.3

Conventions used in Casa documentation

Casa Systems CMTS Release Notes

Conventions used in Casa documentation

Commands and keywords in text are in

The show running-config

Bold italic font

Arguments mentioned in are in bold

Elements in square brackets are

CASA-CMTS# show rstp port

Indicates a required argument with a

Indicates an optional argument with a

Separates parameter values. Same as CASA-CMTS(config-router-o

A non-quoted set of characters. Do not CASA-CMTS# hostname

Casa Systems CMTS Release 6.0.3

Debugging and Diagnostics Reference

Terminal sessions and information the

[Wed Sep 1 20:58:07

Bold screen font

Information you must enter is in

CMTS# show docsis channel

Bold italic screen

Arguments for which you supply values CASA-CMTS(config-router-o

Non-printing characters such as

An exclamation point (!) or a pound

Authentication, Authorization, Accounting

Access Control List

Address Resolution Protocol

Asynchronous Time Division Multiple Access

Border Gateway Protocol

Baseline Privacy Interface

Cable Modem Termination System

Dynamic Bonding Change

Dynamic Channel Change

DOCSIS Data Manager

Data Over Cable Service Interface Specification

Dynamic Host Configuration Protocol

Casa Systems CMTS Release 6.0.3