cc/td/doc/product/rtrmgmt/baccable/cable27
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

CableHome Configuration

Non-Secure CableHome Provisioning Flow

Configuring CableHome

Configuring Network Registrar

Configuring the RDU

Configuring the Device Provisioning Engine


CableHome Configuration


This chapter describes the activities that must be performed to ensure a satisfactory CableHome deployment. There are two versions of the CableHome technology; secure (SNMP) and non-secure (DHCP). This chapter deals exclusively with the non-secure version.

Non-Secure CableHome Provisioning Flow

It is extremely useful to identify which step in the non-secure CableHome provisioning flow is failing before attempting to diagnose other details. Figure 6-1 illustrates a summary of the key provisioning flows and the following steps describe those flows.

Figure 6-1 Non-Secure CableHome Flows

1. DHCP:1—The WAN-Man obtains its IP lease during this step. The IP lease also specifies that the portal service is to be provisioned in the DHCP (non-secure) mode, the TFTP server and the configuration file.

2. TOD:2—Portal services achieve time synchronization with a time of day server in the MSO's network.

3. TFTP:3—Portal services obtain a configuration file in the manner similar to that described in step 1.

4. TFTP:4—Provided that the configuration file acquired in step 3 contains firewall information, portal services may also acquire a firewall configuration file.

5. SYSLOG/SNMP:5—Once successfully configured. Portal services send either a SYSLOG message or a SNMP PDU to inform BACC that it has been successfully configured.

6. DHCP:6—Provided that the portal services configuration file acquired in step 3 contains a MIB setting that sets the number of WAN-Data IP address to one or more, the portal services WAN-Data obtains the required number of IP addresses.

Configuring CableHome

This section describes how to configure Network Registrar, the CMTS.

Configuring Network Registrar


Step 1 Create selection tags for provisioned and unprovisioned WAN-Man and also for provisioned WAN-Data.

Step 2 Configure unprovisioned and provisioned client classes and scopes for cable modems, as specified in Network Registrar User's Guide.

Step 3 Configure unprovisioned and provisioned client classes and scopes for WAN-Man.

Step 4 Configure provisioned client classes and scopes for WAN-Data.

Step 5 Add routes to all the subnets.


Configuring the RDU

To configure CableHome support into the RDU perform these configurations:

Configuring CableHome WAN-Man

Configuring CableHome WAN-Data

Configuring CableHome WAN-Man


Step 1 Create a DHCPCriteria for the provisioned WAN-Man. To do this, set the client class to a client-class name that is configured in Network Registrar CableHome WAN-Man.

Step 2 Create a class of service for the provisioned WAN-Man.

Set the /cos/chWanMan/file to a CableHome configuration file appropriate for the class of service.

Set the /chWanMan/firewall/file to the desired Firewall configuration file.


Configuring CableHome WAN-Data

Configure these WAN-Data parameters whenever you want portal services to obtain the WAN-Data IP addresses:


Step 1 Create DHCPCriteria for WAN-Data.

Step 2 Create ClassOfService for WAN-Data.


Configuring the Device Provisioning Engine

To configure the DPE to support the CableHome technology:


Step 1 Open the CableHome device provisioning WAN-Man config file and verify that DHCP Option 60 is set to either CableHome1.0 or CableHome1.1. Some manufacturers use a proprietary MIB object to instruct a device to behave as either a pure cable modem, a non-CableHome router, or as a CableHome router. The device appears as a Computer whenever the device DHCP packet does not contain CableHome1.0 or CableHome1.1 in the DHCP Option 60.

Step 2 If you want the portal services to obtain IP addresses for WAN-Data:

Ensure that the WAN-Man configuration file contains TLV 28 that sets cabhCdpWanDataIpAddrCount to a value that is greater than 0.

In the cable modem configuration file, set the max number of CPEs to include the number of WAN-Data IP addresses.

Step 3 To enable self-provisioning when the CableHome device boots:

In the unprov-wan-man.cfg portal services configuration file, set the portal services in the passthrough mode

In the cable modem configuration file, set the maximum number of CPEs to at least 2 to allow provisioning of the WAN-Man and a computer. The computer can directly access sign-up web pages to be self-provisioned.

Step 4 Close and save the CableHome configuration file.



hometocprevnextglossaryfeedbacksearchhelp

Posted: Thu Feb 2 13:09:15 PST 2006
All contents are Copyright © 1992--2006 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.