Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco CVA120 Series Cable Voice Adapters

Cable Voice Adapter 120 Basic Installation and Troubleshooting

Downloads

Document ID: 12197


Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Setting up the CVA Out-Of-The-Box
Troubleshooting the CVA When It Does Not Come Online
IOS show and debug Commands on the CMTS
      Example of debug Commands on the CMTS
Sending Specific IOS Commands to the CVA
Sending an IOS Configuration File to the CVA
CMTS Configuration
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

One of the most common issues faced with the Cable Voice Adapter (CVA)120 series cable modems (CM) is not understanding where to start troubleshooting when the modem does not come online. The CVA CM differs from all other uBR900 series modems because the CVA does not have a console connection. In order to determine if the CVA has initialized successfully, you have to rely on the LED status.

To determine what stage the CVA is in, there are basic Cisco IOS® software commands that can be run from the headend side. Telnet access is another option. However, if the CVA does not come online and obtain an IP address, then Telnet access does not work. If the CVA has achieved online status, Telnet access works only if an IOS configuration file with enable and Telnet passwords is sent to the CVA via the Data-over-Cable Service Interface Specifications (DOCSIS) configuration file.

The purpose of this document is to illustrate basic setup in a lab environment for the CVA using Cisco Network Registrar (CNR), and to explore troubleshooting options for the CVA to achieve online status.

Note: This document assumes you have control over the headend side, which includes the Cable Modem Termination System (CMTS) and the provisioning servers. If you do not have control over the headend side, you cannot perform any of the troubleshooting tasks that are described in this document.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on these software and hardware versions:

  • uBR7246 VXR running IOS 12.1(6)EC1 acting as CMTS

  • CVA122 CM (MPC850) processor running IOS 12.1(5).XU1 acting as a CM

  • CNR version 5.0(6) which provides DHCP server, and has TFTP server and Time Server software running

  • DOCSIS Configurator tool Version 3.3

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Note: If you are not familiar with basic radio frequency (RF) setup in a lab environment using CNR, refer to Cable Modem Basic Install with Cisco Network Registrar.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Setting up the CVA Out-Of-The-Box

If there are no problems with RF and provisioning, the CVA, once connected to the headend, should come online with the default configuration that ships with the box. This is the default configuration: 

Current configuration : 1099 bytes
!
version 12.1
no service single-slot-reload-enable
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Router
!
no logging buffered
logging rate-limit console 10 except errors
!
!
!
clock timezone - 0
ip subnet-zero
no ip routing
no ip finger
!
!
!
!
interface Ethernet0
 ip address 10.50.50.7 255.255.255.0
 no ip route-cache
 bridge-group 59
 bridge-group 59 spanning-disabled
!
interface cable-modem0
 ip address docsis
 no ip route-cache
 cable-modem boot admin 2
 cable-modem boot oper 5
 bridge-group 59
 bridge-group 59 spanning-disabled
!
interface usb0
 ip address 10.50.50.7 255.255.255.0
 no ip route-cache
 arp timeout 0
 bridge-group 59
 bridge-group 59 spanning-disabled
!
ip classless
no ip http server
no ip http cable-monitor
!
!
!
snmp-server packetsize 4096
snmp-server manager
call rsvp-sync
!
voice-port 0
 input gain -2
!
voice-port 1
 input gain -2
!
mgcp modem passthrough voip mode ca
no mgcp timer receive-rtcp
!
mgcp profile default
!
!
line con 0
 transport input none
line vty 0 4
!
end

Router#

The CVA is online, has obtained an IP address of 10.50.50.7, and is operating in bridging mode. If you issue the telnet command to the CVA, you receive this message:

cobra#telnet 10.50.50.7 
Trying 10.50.50.7 ... Open
Password required, but none set
[Connection to 10.50.50.7 closed by foreign host]

This behaves exactly like any other Cisco router where you do not have the password being set under line vty 0 4 and an enable password.

Troubleshooting the CVA When It Does Not Come Online

Note: Contact your Internet Service Provider (ISP) before proceeding with troubleshooting.

When the CVA does not come online, verify the LED status on the front of the box.

cva1.gif

The most important LED is the Cable and Power Status. If the CVA has achieved online status, it stays ON, which indicates normal operation. If the LED is blinking, the system is locking on to downstream and upstream channels. Eventually, the LED should switch to permanent ON. This indicates the CVA is online.

From the headend, to verify that the CVA is online, the most useful command is show cable modem.

cobra# show cable modem 
Interface   Prim Online     Timing Rec    QoS CPE IP address      MAC address

            Sid  State      Offset Power

Cable3/0/U0 1    online     2811    0.00  5   0   10.50.50.6      0001.9659.4415

Cable3/0/U0 2    online     2812    0.25  5   0   10.50.50.7      0001.64ff.e4ad   

!--- CVA CM.


Cable3/0/U0 3    online     2289   -0.25  5   0   10.50.50.8      0050.7366.1fb9

If the Cable and Power Status LED remains blinking, verify that the coaxial cable is firmly connected. If it is connected, then the CVA could be in one of these states:

  • Offline state

  • Ranging process - init(r1),init(r2), and init(rc) state

  • DHCP - init(d) state

  • DHCP - init(i) state

  • TOD exchange - init(t) state

  • Option file transfer started - init(o) state

  • Reject (pk) and reject(pt) state

  • Registration - reject (m) state

  • Registration - reject (c) state

For information on why the CM is in one of these states, refer to Troubleshooting uBR Cable Modems Not Coming Online.

Note: It is important to remember that IOS show commands and debugs are not possible from the CVA end because there is no console connection. Any show or debug commands are performed from the headend router or the CMTS.

IOS show and debug Commands on the CMTS

As explained in this document, the most used IOS command on the CMTS is show cable modem.

cobra#show cable mode

Interface   Prim Online     Timing Rec    QoS CPE IP address      MAC address

            Sid  State      Offset Power

Cable3/0/U0 1    online     2811    0.00  5   0   10.50.50.6      0001.9659.4415

Cable3/0/U0 2    init(d)    2813   -0.75  2   0   10.50.50.7      0001.64ff.e4ad 

Cable3/0/U0 3    online     2289   -0.25  5   0   10.50.50.8      0050.7366.1fb9

This sate shows the CVA failing at the DHCP request state. Unfortunately, the debugs do not explicitly state this. Instead, turning on the debugs on the CMTS results in this message:

*Jul 20 03:38:18.700: CM not responding. SID 2 on I/F Cable3/0 marked offline

Thus, show cable modem is more useful.

You may want to repeat this command at close intervals to verify what state the modem is cycling. For example, Offline, Init(r1), Init(r2), Init(rc), Init(d), Offline indicates a DHCP problem.

Example of debug Commands on the CMTS

This is an example of debug commands on the CMTS:

  • debug cable interface cable 3/0 mac-address 0001.64ff.e4ad verbose followed by debug cable <option> where option can be mac-protocol, phy, ranging, registration, etc. Refer to Cisco CMTS Debugging Commands for more information.

Note: When running debugs on the CMTS, you have to issue the debug cable interface cable x/y [options] before issuing the debug cable <option> command. If you do not, there is no output display. This also prevents CPU overload because the debug output is being limited to one CM.

This is a sample output of debugs run on the CMTS: 

cobra#sh debug
CMTS:
  CMTS mac debugging is on
  CMTS ranging debugging is on
  CMTS registration debugging is on
  CMTS reset debugging is on
  CMTS phy debugging is on
CMTS specific:
  Debugging is on for Cable3/0, Address 0001.64ff.e4ad, Mask ffff.ffff.ffff
cobra#
*Jul 20 02:57:08.733: Ranging request from 0001.64ff.e4ad, SID 0 [16383] on Int0
*Jul 20 02:57:08.733: Initial Ranging: Downstream channel ID is 0 (configured 0)
*Jul 20 02:57:08.733: Reusing old primary sid 2 for modem 0001.64ff.e4ad
*Jul 20 02:57:08.733: Deleted CM from US Channel 1: New CM count 2 (2 active)
*Jul 20 02:57:08.733: Adding CM to US Channel 1: New CM count 3
*Jul 20 02:57:08.737: Starting UNREG_SID_TIMEOUT for Sid 2
*Jul 20 02:57:09.733: Ranging Modem 0001.64ff.e4ad, SID 2 on Interface Cable3/00
*Jul 20 02:57:09.733: Ranging request from 0001.64ff.e4ad, SID 2 [2] on Interfa0
*Jul 20 02:57:09.733: Ranging successful.
*Jul 20 02:57:11.965: Ranging Modem 0001.64ff.e4ad, SID 2 on Interface Cable3/00
*Jul 20 02:57:11.965: Ranging request from 0001.64ff.e4ad, SID 2 [2] on Interfa0
*Jul 20 02:57:11.965: Ranging successful.
*Jul 20 02:57:14.969: Ranging Modem 0001.64ff.e4ad, SID 2 on Interface Cable3/00
*Jul 20 02:57:14.969: Ranging request from 0001.64ff.e4ad, SID 2 [2] on Interfa0
*Jul 20 02:57:14.969: Ranging successful.
*Jul 20 02:57:17.973: Ranging Modem 0001.64ff.e4ad, SID 2 on Interface Cable3/00
*Jul 20 02:57:17.977: Ranging request from 0001.64ff.e4ad, SID 2 [2] on Interfa0
*Jul 20 02:57:17.977: Ranging successful.
*Jul 20 02:57:20.977: Ranging Modem 0001.64ff.e4ad, SID 2 on Interface Cable3/00
*Jul 20 02:57:20.981: Ranging request from 0001.64ff.e4ad, SID 2 [2] on Interfa0
*Jul 20 02:57:20.981: Ranging successful.
*Jul 20 02:57:23.693: Registration request from 0001.64ff.e4ad, SID 2 on Cable30
*Jul 20 02:57:23.693: Found a network access control parameter: Ok
*Jul 20 02:57:23.693: Found a class of service block: Ok
*Jul 20 02:57:23.693: Found Max CPE: Ok
*Jul 20 02:57:23.693: Found CM MIC: Ok
*Jul 20 02:57:23.693: Found CMTS MIC: Ok
*Jul 20 02:57:23.693: Found modem ip: Ok
*Jul 20 02:57:23.693: Found modem capabilities: Ok
*Jul 20 02:57:23.693: Finished parsing REG Request
*Jul 20 02:57:23.693: Sec sids obtained for all requested classes of service
*Jul 20 02:57:23.693: Performing connection admission control (CAC) for each Sid
*Jul 20 02:57:23.693: CAC Status for ClassID:1 is CAC_SUCCESS
*Jul 20 02:57:23.693: Registration Status: ok (0)
*Jul 20 02:57:23.697: Registration Response Transmitted
*Jul 20 02:57:23.981: Ranging Modem 0001.64ff.e4ad, SID 2 on Interface Cable3/00
*Jul 20 02:57:23.981: Ranging request from 0001.64ff.e4ad, SID 2 [2] on Interfa0
*Jul 20 02:57:23.981: Ranging successful.

Sending Specific IOS Commands to the CVA

In order to send specific IOS commands to the CVA, you need to use the IOS Configuration Command option under the Vendor Info tab. This is located in the DOCSIS Customer Premises Equipment (CPE) Configurator ( registered customers only) .

This is an example of a DOCSIS config file that sends a vty and enable passwords to the CVA:

cva2.gif

To verify that the correct configuration file is sent to the CVA, you should be able to Telnet to it from the CMTS:

cobra#show cable modem 

Interface   Prim Online     Timing Rec    QoS CPE IP address      MAC address

            Sid  State      Offset Power

Cable3/0/U0 1    online     2811   -0.25  5   0   10.50.50.6      0001.9659.4415

Cable3/0/U0 2    online     2811   -0.50  6   0   10.50.50.7      0001.64ff.e4ad 

!--- CVA CM.


Cable3/0/U0 3    online     2289   -0.50  5   0   10.50.50.8      0050.7366.1fb9
cobra#telnet 10.50.50.7
Trying 10.50.50.7 ... Open
User Access Verification
Password: 
Router>en
Password: 
Router#

This is the configuration displayed:

Router#show running-config 
Building configuration...
Current configuration : 1227 bytes
!
! Last configuration change at 12:29:52 - Fri Jul 20 2001
!
version 12.1
no service single-slot-reload-enable
no service pad
service timestamps debug datetime msec localtime
service timestamps log uptime
no service password-encryption
!
hostname Router
!
no logging buffered
logging rate-limit console 10 except errors
enable password changeme
!
!
!
clock timezone - 0
ip subnet-zero
no ip routing
no ip finger
!

!
!
interface Ethernet0
 ip address 10.50.50.7 255.255.255.0
 no ip route-cache
 bridge-group 59
 bridge-group 59 spanning-disabled
!
interface cable-modem0
 ip address docsis
 no ip route-cache
 cable-modem boot admin 2
 cable-modem boot oper 5
 bridge-group 59
 bridge-group 59 spanning-disabled
!
interface usb0
 ip address 10.50.50.7 255.255.255.0
 no ip route-cache
 arp timeout 0
 bridge-group 59
 bridge-group 59 spanning-disabled
!
ip classless
no ip http server
no ip http cable-monitor
!
!
!
snmp-server packetsize 4096
snmp-server manager
call rsvp-sync
!
voice-port 0
 input gain -2
!
voice-port 1
 input gain -2
!
mgcp modem passthrough voip mode ca
no mgcp timer receive-rtcp
!
mgcp profile default
!
!
line con 0
 transport input none
line vty 0 4
 password changeme
 login
!
end

Router#

Sending an IOS Configuration File to the CVA

Assume that the requirement here is to send an IOS configuration file instead of individual commands. For example, you should send this configuration file to the CVA:

hostname CVA
!
enable secret < password > [Choose a strong password with at least one capital letter, 
one number, and one special character.]
no ip domain-lookup
!
line vty 0 4
 password cisco
end

Complete these steps to send the configuration file to the CVA:

  1. Compose the configuration file using a text editor. To ensure no space characters are inserted after the passwords, enter a carriage return after each line.

  2. Save the configuration file.

  3. Copy it to the correct directory on the same TFTP server that the DOCSIS configuration file is located. In this case, the file is called IOS_CFG.TXT.

  4. Modify the DOCSIS configuration file by specifying the IOS Filename under the Vendor Info Tab in the DOCSIS CPE Configurator ( registered customers only) (see Figure 3).

  5. Ensure that the correct DOCSIS configuration file is specified under packet-file-name in the CM policy in CNR (refer to Cisco Network Registrar Configuration). In this example, the DOCSIS config file is CVA_IOS.CM.

Figure 3

cva3.gif

Once the CVA is online, you can verify by issuing a Telnet command to the CVA from the CMTS:

cobra#show cable modem 

Interface   Prim Online     Timing Rec    QoS CPE IP address      MAC address

            Sid  State      Offset Power

Cable3/0/U0 1    online     2811    0.00  5   0   10.50.50.6      0001.9659.4415

Cable3/0/U0 2    online     2812   -0.75  6   0   10.50.50.7      0001.64ff.e4ad  

!--- CVA CM.


Cable3/0/U0 3    online     2289   -0.50  5   0   10.50.50.8      0050.7366.1fb9
cobra#telnet 10.50.50.7
Trying 10.50.50.7 ... Open
User Access Verification
Password: 
CVA>en
Password: 
CVA#

The router name is now CVA, which indicates that the configuration was sent correctly. You can also verify that you have downloaded the correct IOS file by issuing the show version command on the CVA:

CVA#show version 
Cisco Internetwork Operating System Software 
IOS (tm) 120 Software (CVA120-K1V4Y5-M), Version 12.1(5)XU1, 
EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)
TAC:Home:SW:IOS:Specials for info
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Wed 14-Feb-01 11:08 by kirthi
Image text-base: 0x800100A0, data-base: 0x807CDA2C
ROM: System Bootstrap, Version 12.0(20001010:025045) [spaulsen-blue-3105 3108], 
DEVELOPMENT SOFTWARE
ROM: 120 Software (CVA120-K1V4Y5-M), Version 12.1(5)XU1, 
EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)
CVA uptime is 22 hours, 34 minutes
System returned to ROM by reload at 14:56:20 - Thu Jul 19 2001
System restarted at 15:03:35 - Thu Jul 19 2001
System image file is "flash:cva120-k1v4y5-mz.121-5.XU1.bin"
Host configuration file is "tftp://172.17.110.149/IOS_CFG.TXT"
cisco CVA122 CM (MPC850) processor (revision 3.r) with 32256K/1024K bytes of memory.
Processor board ID sad043708dm
Bridging software.
1 Ethernet/IEEE 802.3 interface(s)
1 Cable Modem network interface(s)
8192K bytes of processor board System flash (Read/Write)
7296K bytes of processor board Boot flash (Read/Write)
Configuration register is 0x2

Notice the line Host configuration file is "tftp://172.17.110.149/IOS_CFG.TXT". This line confirms that the correct file has been sent to the CVA. You can also confirm that the correct DOCSIS configuration file has been downloaded into the CVA by issuing the show controllers cable-modem 0 mac state | include Config File Name command:

CVA#show controllers cable-modem 0 mac state | include Config File Name 
Config File Name:           cva_ios.cm
CVA#

The next output is the show running-config command. Changes are highlighted.

Note: This process is additive. The old enable password is still there, but has been superseded by the enable secret command.

If different IOS configuration files are performed, make sure the next IOS file disables the previously set commands. The other alternative is to issue the write erase, then reload commands.


CVA#show running-config 
Building configuration...
Current configuration : 1311 bytes
!
! Last configuration change at 13:12:52 - Fri Jul 20 2001
!
version 12.1
no service single-slot-reload-enable
no service pad
service timestamps debug datetime msec localtime
service timestamps log uptime
no service password-encryption
!
hostname CVA
!
no logging buffered
logging rate-limit console 10 except errors
enable secret 5 $1$2clR$PnLaDc.dEIp6sQvqRyFaL/
enable password changeme
!
!
!
clock timezone - 0
ip subnet-zero
no ip routing
no ip finger
no ip domain-lookup
!
!
!
no console-port-enable
!
!
interface Ethernet0
 ip address 10.50.50.7 255.255.255.0
 no ip route-cache
 bridge-group 59
 bridge-group 59 spanning-disabled
!
interface cable-modem0
 ip address docsis
 no ip route-cache
 cable-modem boot admin 2
 cable-modem boot oper 5
 bridge-group 59
 bridge-group 59 spanning-disabled
!
interface usb0
 ip address 10.50.50.7 255.255.255.0
 no ip route-cache
 arp timeout 0
 bridge-group 59
 bridge-group 59 spanning-disabled
!
ip classless
no ip http server
no ip http cable-monitor
!
!
!
snmp-server packetsize 4096
snmp-server manager
call rsvp-sync
!
voice-port 0
 input gain -2
!
voice-port 1
 input gain -2
!
mgcp modem passthrough voip mode ca
no mgcp timer receive-rtcp
!
mgcp profile default
!
!
line con 0
 transport input none
line vty 0 4
 password cisco
 login
!
end

CMTS Configuration 

cobra#show running-config 
Building configuration...
Current configuration : 2228 bytes
!
version 12.1
service timestamps debug datetime msec localtime
service timestamps log datetime localtime
no service password-encryption
service udp-small-servers max-servers no-limit
!
hostname cobra
!
boot system flash slot0:ubr7200-k1p-mz.121-6.EC1.bin
no logging buffered
enable password cisco
!
no cable qos permission create
no cable qos permission update
cable qos permission modems
ip subnet-zero
no ip finger
no ip domain-lookup
ip name-server 172.17.110.131
!
!
interface Ethernet1/0
 ip address 172.17.110.151 255.255.255.224
 half-duplex
!
interface Ethernet1/1
 no ip address
 shutdown
 half-duplex
!
interface Ethernet1/2
 no ip address
 shutdown
 half-duplex
!
interface Ethernet1/3
 no ip address
 shutdown
 half-duplex
!
interface Cable3/0
 ip address 10.20.30.1 255.255.255.0 secondary
 ip address 10.50.50.1 255.255.255.0
 load-interval 30
 no keepalive
 cable downstream annex B
 cable downstream modulation 64qam
 cable downstream interleave-depth 32
 cable upstream 0 frequency 40000000
 cable upstream 0 power-level 0
 no cable upstream 0 shutdown
 cable upstream 1 shutdown
 cable upstream 2 shutdown
 cable upstream 3 shutdown
 cable upstream 4 shutdown
 cable upstream 5 frequency 40000000
 cable upstream 5 power-level 0
 cable upstream 5 shutdown
 cable dhcp-giaddr policy
 cable helper-address 172.17.110.149
!
interface Cable4/0
 no ip address
 no keepalive
 shutdown
 cable downstream annex B
 cable downstream modulation 64qam
 cable downstream interleave-depth 32
 cable upstream 0 shutdown
 cable upstream 1 shutdown
 cable upstream 2 shutdown
 cable upstream 3 shutdown
 cable upstream 4 shutdown
 cable upstream 5 shutdown
!
ip classless
ip route 0.0.0.0 0.0.0.0 172.17.110.129 254
no ip http server
!
!
!         
banner exec ^C
Cobra!!!
!
^C
alias exec scm show cable modem
!
line con 0
 exec-timeout 0 0
 transport input none
line aux 0
line vty 0 4
 exec-timeout 0 0
 password cisco
 no login
!
end
cobra#

NetPro Discussion Forums - Featured Conversations

Networking Professionals Connection is a forum for networking professionals to share questions, suggestions, and information about networking solutions, products, and technologies. The featured links are some of the most recent conversations available in this technology.
NetPro Discussion Forums - Featured Conversations for Cable
Network Infrastructure: Remote Access

Related Information

Updated: May 25, 2006Document ID: 12197