Cisco Broadband Access Center User manual

Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: [phone]
800 553-NETS (6387)
Fax: [phone]
Cisco Broadband Access Center for Cable
Installation Guide
Release 2.7
Text Part Number: OL-19105-01

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE 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 OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO 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 CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCDE, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome
to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS,
Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS,
Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step,
Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone,
MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase,
SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of
Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (0812R)
Cisco Broadband Access Center for Cable Installation Guide, Release 2.7
© 2002-2009 Cisco Systems, Inc. All rights reserved.

iii
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
CONTENTS
Preface vii
Audience vii
How This Guide Is Organized vii
Document Conventions viii
Related Documentation ix
Obtaining Documentation and Submitting a Service Request ix
CHAPTER 1Overview 1-1
Operating System Requirements 1-1
JDK Patches for Solaris 8 1-1
JDK Patches for Solaris 9 1-2
KDC Patches 1-2
Network Registrar Requirements 1-2
Hardware Requirements 1-2
Types of Installations 1-4
CHAPTER 2Preparing to Install Components 2-1
Broadband Access Center for Cable Components 2-1
Installation and Startup Process 2-2
Broadband Access Center Database Requirements 2-5
File System Block Size 2-5
Large File Support 2-6
Installation Checklist 2-6
Installation 2-7
Installation Using the Graphical User Interface 2-7
Installing from the Command Line 2-8
CHAPTER 3Installing Components 3-1
Installing Components Using the Graphical User Interface 3-1
Installing the Regional Distribution Unit 3-2
Installing Extensions on a Network Registrar Server 3-3
Installing Extensions 3-4
Configuring Extensions 3-5

Contents
iv
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
Validating Extensions 3-6
Installing the Key Distribution Center 3-7
Installing the Device Provisioning Engine 3-8
Installing Components Using the CLI 3-8
Installing the Regional Distribution Unit 3-9
Installing Network Registrar Extensions 3-11
Installing the Key Distribution Center 3-14
Installing the Device Provisioning Engine 3-16
CHAPTER 4Installing in a Lab Environment 4-1
Installation Checklist 4-1
Installing in a Lab Environment Using the GUI 4-2
Installing in a Lab Environment Using the CLI 4-3
Configuring Network Registrar and a CMTS 4-6
CHAPTER 5Post-Installation Activities 5-1
Enabling a Network Registrar Spoofing DNS Server 5-1
Configuring the Syslog Utility to Receive Alerts from BACC 5-1
Uninstalling Broadband Access Center 5-2
Uninstalling BACC from the Graphical User Interface 5-3
Uninstalling BACC from the Console Mode 5-3
CHAPTER 6Upgrading Broadband Access Center for Cable 6-1
Before You Begin 6-2
Upgrading the RDU 6-2
Upgrading the Solaris DPE 6-2
Upgrading Hardware DPEs 6-4
Upgrading Network Registrar Extensions 6-5
Upgrading the KDC 6-5
Migrating the RDU Database 6-6
CHAPTER 7Setting Up a Device Provisioning Engine 7-1
Hardware DPE Setup Sequence 7-1
Connecting the Device Provisioning Engine 7-1
Configuring and Running a Terminal Emulation Program 7-2
Logging In 7-2
Configuring a Device Provisioning Engine for Data 7-3

Contents
v
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
Configuring a Device Provisioning Engine for Voice Technology 7-5
Setting Up Voice Technology 7-5
Controls Available 7-7
Debugging 7-7
APPENDIX ANetwork Registrar Configuration File Example A-1
Configuration Scripts A-1
Sample Script for DOCSIS Modems and Computers A-1
Sample Script for DOCSIS Modems and PacketCable MTAs A-2
I NDEX

Contents
vi
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01

vii
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
Preface
Welcome to the Cisco Broadband Access Center for Cable Installation Guide 2.7. This chapter provides
an outline of the other chapters in this guide, and demonstrates the styles and conventions used in the
guide.
This chapter contains the following sections:
• Audience, page vii
• How This Guide Is Organized, page vii
• Document Conventions, page viii
• Related Documentation, page ix
• Obtaining Documentation and Submitting a Service Request, page ix
Audience
This installation guide enables system integrators, network administrators, and network technicians to
install Cisco Broadband Access Center for Cable, referred to as BACC throughout this installation guide,
on Solaris operating systems and to set up the Cisco device provisioning engine (DPE).
Note Within this installation guide you may encounter references to BACC. With two exceptions, these
references are actually referring to the BACC product. The exception are in those areas where you are
prompted to enter specific data that may also contain references to BACC and where references are made
to specific file, directory or pathnames.
In these instances, you must enter the characters exactly as they appear in this guide.
How This Guide Is Organized
This guide describes how to install BACC on Solaris operating system. The major sections of this guide
are described here:

viii
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
Preface
Document Conventions
This guide uses the following conventions:
• Boldface is used for commands, keywords, and buttons.
• Italic is used for command input for which you supply values.
• Screen font is used for examples of information that are displayed on the screen.
• Boldface screen font is used for examples of information that you enter.
• UNIX paths are indicated as follows: /tools/list/connections.
Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the
publication.
Caution Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
Section Title Description
Chapter 1 Overview Provides general requirements for a successful installation of
BACC.
Chapter 2 Preparing to Install
Components
Describes considerations you need to take into account as you
prepare to install BACC. For example, it describes the
individual components of BACC, the order of operations for
installing the software, and the BACC database requirements. It
also describes initial steps for installing the software using
either a graphical user interface or a command line interface.
Chapter 3 Installing
Components
Describes how to install the individual components of BACC
using either the graphical user interface or the CLI.
Chapter 4 Installing in a Lab
Environment
Describes how to install a lab version of BACC using either the
graphical user interface or the CLI.
Chapter 5 Post-Installation
Activities
Describes those activities that are performed following
installation.
Chapter 6 Upgrading
Broadband Access
Center for Cable
Describes the upgrade procedures performed on various BACC
components.
Chapter 7 Setting Up a Device
Provisioning Engine
Describes how to configure a device provisioning engine
(DPE).
Appendix A Network Registrar
Configuration File
Example
Shows examples of files used to configure Network Registrar
for high-speed data (HSD) and voice technology deployments.

ix
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
Preface
Related Documentation
Refer to these manuals for additional information:
• Release Notes for Broadband Access Center for Cable, Release 2.7
• Cisco Broadband Access Center for Cable Administrator’s Guide
• Cisco Broadband Access Center for Cable CLI Reference Guide
• To support the DPE-590:
– Device Provisioning Engine 590 Recovery CD-ROM Release Notes
– Cisco Content Engine 500 Series Hardware Installation Guide
• To support the DPE-2115:
– Device Provisioning Engine 2115 Recovery CD-ROM Release Notes
– Installation and Setup Guide for the Cisco 1102 VLAN Policy Server
Caution Refer to this guide for port and connector identification and to perform hardware installation only. Do
not attempt to perform any of the configuration instructions found in that guide.
• Cisco Network Registrar User’s Guide
• Cisco Network Registrar CLI Reference
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional
information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and
revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed
and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free
service and Cisco currently supports RSS Version 2.0.

x
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
Preface

CHAPTER
1-1
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
1
Overview
Broadband Access Center for Cable (BACC) automates the process of configuring and provisioning
cable network devices. BACC interfaces with Cisco Network Registrar, which includes a high-speed
DHCP server for IP address management and a DNS server.
This chapter describes:
• Operating System Requirements, page 1-1
• Network Registrar Requirements, page 1-2
• Hardware Requirements, page 1-2
• Types of Installations, page 1-4
Operating System Requirements
You must install BACC on a computer running the Solaris 8 or 9 operating system. You must have the
correct type and number of patches installed on your system before you can install BACC.
JDK Patches for Solaris 8
The JDK patches recommended for successful BACC installation include:
• 112003-03 • 108773-18 • 111310-01
• 109147-31 • 111308-05 • 112438-03
• 108434-18 • 108435-18 • 113886-26
• 113887-26 • 111111-04 • 112396-02
• 110386-03 • 111023-03 • 111317-05
• 113648-03 • 115827-01 • 116602-01
• 108652-86 • 108921-22 • 108940-65
• 108987-14 • 108528-29 • 108989-02
• 108993-39 • 109326-16 • 110615-13

1-2
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
Chapter 1 Overview
Network Registrar Requirements
JDK Patches for Solaris 9
The JDK patches recommended for successful BACC installation include:
KDC Patches
The KDC patches required for successful BACC installation include:
• 112438-01
• 109326-06
Network Registrar Requirements
Before you install BACC, be aware of these Cisco Network Registrar requirements:
• We recommend that you use Network Registrar 6.1.2.3 or higher with BACC 2.7.
• A Network Registrar DHCP server must be installed on a computer with Solaris 8 or 9.
• In a failover deployment of BACC, you must configure two redundant DHCP servers for failover.
• After you install BACC, ensure that Network Registrar scopes are configured to reflect failover
capability and the topology of the network on which BACC is installed.
For more information about configuring failover on Network Registrar servers, see the Network
Registrar User’s Guide.
Hardware Requirements
A BACC installation requires these servers:
• A regional distribution unit (RDU). This is the primary server in a BACC deployment. It contains
the central BACC database and manages the generation of configurations.
• One or more device provisioning engines (DPE). A Cisco device provisioning engine caches
provisioning information and handles all configuration requests including the transfer of
configuration files to devices. It is integrated with the Cisco Network Registrar DHCP server to
control the assignment of IP addresses. Multiple DPEs can communicate with a single DHCP server.
DPEs include factory installed software that enables provisioning, but you must perform some initial
set up.
Note The hardware installation procedures for the device provisioning engine are described in the following
guides:
• 113886-26 • 113887-26
• 112785-44 • 113096-03

1-3
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
Chapter 1 Overview
Hardware Requirements
• For the DPE-590, refer to the Cisco Content Engine 500 Series Hardware Installation Guide. This
can be found at:
http://www.cisco.com/en/US/docs/app_ntwk_services/waas/ce/ce500/installation/guide/
ce500hig.html
• For the DPE-2115, refer to the Installation and Setup Guide for the Cisco 1102 VLAN Policy Server.
This can be found at:
www.cisco.com/en/US/products/sw/secursw/ps2136/
products_installation_and_configuration_guide_book09186a00801f0d02.html
• A key distribution center (KDC). The KDC and the DPE registration services handle the
authentication of all voice technology media terminal adapters (MTAs). When a lab installation is
performed, the KDC is installed on the lab computer. For performance reasons however, in a
component installation, the KDC should be installed on a separate server.
Note The KDC is required only when configuring a system to support voice technology
operations.
• One or more Cisco Network Registrar servers. Network Registrar provides Dynamic Host
Configuration Protocol (DHCP) and Domain Name System (DNS) functionality. Implementing
dynamic DNS (DDNS) within Network Registrar, increases the number of servers you need to
deploy.
Table 1-1 describes the hardware requirements for each server.
Ta b l e 1-1 Hardware Recommendations per Provisioning Group
# Subscribers Server
Min. #
Servers
Recommended #
Servers 1Server Class
#
Processors Memory
10000 DPE 1 2 SUN V210 1GHz211 GB
CNR 1 2 SUN V210 1GHz 11 GB
KDC 1 - SUN V210 1GHz 11 GB
25000 DPE 1 2 SUN V210 1GHz211 GB
CNR 1 2 SUN V210 1GHz 11 GB
KDC 1 - SUN V210 1GHz 22 GB
100000 DPE 1 2 SUN V210 1GHz222 GB
CNR 1 2 SUN V210 1GHz 22 GB
KDC 1 - SUN V210 1GHz 22 GB
250000 DPE 2 2 SUN V210 1GHz222 GB
CNR 2 2 SUN V210 1GHz 22 GB
KDC - - NA3- -
500000 DPE 2 2 SUN V210 1GHz222 GB
CNR 2 2 SUN V210 1GHz 22 GB
KDC - - NA3- -

1-4
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
Chapter 1 Overview
Types of Installations
Types of Installations
This guide discusses two types of installation:
• Individual component installation—The installation program enables you to install one or more
individual components of BACC. The individual components are the RDU, Cisco Network Registrar
extensions, the Solaris device provisioning engine (DPE), and the KDC. Refer to Chapter 3,
“Installing Components” for specifics about installing the individual components.
• Lab installation—The installation program enables you to install BACC for use in a laboratory
environment for demonstration or evaluation prior to deploying BACC into a full network
implementation. Refer to Chapter 4, “Installing in a Lab Environment” for more information.
You can install BACC from the installation program’s graphical user interface (GUI) or from the
command line.
1 million DPE 2 2 SUN V210 1GHz222 GB or 4 GB4
CNR 2 2 SUN V210 1GHz 22 GB or 4 GB4
KDC - - NA3- -
Lab Install Single server
for all
1 1 SUN V210 1GHz 11 GB
1. The number of recommended servers is based on the average subscriber with two devices (1 cable modem and 1 PC).
2. With BACC 2.6.1 and later releases, the non-appliance Sun DPE can be replaced with a DPE-2115 single 3.06 Ghz CPU and 2 GB memory, which yields
equal or better performance.
3. Only 100000 MTA devices are currently supported per provisioning group.
4. 2 GB for configuration files that are less than or equal to 1.5 KB and 4 GB for configuration files that are more than 1.5 KB.
Table 1-1 Hardware Recommendations per Provisioning Group (continued)
# Subscribers Server
Min. #
Servers
Recommended #
Servers 1Server Class
#
Processors Memory

CHAPTER
2-1
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
2
Preparing to Install Components
This chapter provides the information you need to prepare for a successful Broadband Access Center for
Cable (BACC) component installation, including these topics:
• Broadband Access Center for Cable Components, page 2-1
• Installation and Startup Process, page 2-2
• Broadband Access Center Database Requirements, page 2-5
• Installation Checklist, page 2-6
• Installation, page 2-7
Broadband Access Center for Cable Components
The BACC component installation program prompts you to install one or more of these components:
• Regional distribution unit (RDU). The RDU is the primary server in the BACC provisioning system.
You should install the RDU on a Solaris 8 or Solaris 9 server that meets the requirements described
in the “Hardware Requirements” section on page 1-2. The RDU performs these functions:
– Manages the generation of device configurations.
– Acts as a clearinghouse through which all application programming interface (API) requests
must pass.
– Manages the BACC system.
• Network Registrar extensions. These extensions are the link between BACC and Network Registrar.
Install this component on all Network Registrar servers in your BACC environment. If you are
deploying BACC in a failover environment, you must also install the extensions on the failover
servers.
Note We recommend that you install the BACC Network Registrar extensions on a server running
Network Registrar 6.1.2.3 or higher.
• Device Provisioning Engine (DPE). BACC supports the deployment of a DPE on Solaris Sparc
computers running Solaris 8 or Solaris 9.
Note The DPE component now requires licenses to be installed at the RDU. If you have not yet
received your licenses, contact your Cisco Systems representative before proceeding.

2-2
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
Chapter 2 Preparing to Install Components
Installation and Startup Process
If, during DPE installation, the installation program detects the presence of a TFTP server running
on the same computer that the DPE being installed on, the installation is immediately terminated
and an error message appears on screen.
• Key Distribution Center (KDC). For maximum performance and segmentation of the network, you
may install one KDC instance per provisioning group. The KDC, along with the DPE registration
service, handles the authentication of all PacketCable voice technology MTAs. When a laboratory
installation is performed, the KDC is installed on the lab computer. For performance reasons
however, in a component installation, the KDC should be installed on a separate server. The KDC
component requires a license.
Note The KDC and DPE have service keys that are required to allow them to communicate.
Although the component installation program supports installing the components on the same computer,
in practice, you are likely to run the program on several different computers as described in these
sections:
1. Installing the RDU on a Solaris 8 or 9 server.
2. Installing the Network Registrar extensions on a Network Registrar server or servers.
3. Installing the DPE on Solaris Sparc computers running Solaris 8 or Solaris 9.
4. Installing the KDC server.
Installation and Startup Process
To ensure a smooth installation and startup process, complete the order of operations as listed in
Table 2-1.
Ta b l e 2-1 Installation and Startup Process
Item Description
1. Determine which components you are installing and on what computers.
2. Verify the file system block size of the directory in which you intend to install the BACC
database and database transaction log files. See the “Broadband Access Center Database
Requirements” section on page 2-5.
3. Review the installation checklist. See the “Installation Checklist” section on page 2-6.
4. Install a DPE. When you install the DPE, ensure that you have this information available:
• Home Directory location
• Data Directory location
After Solaris DPE installation is complete, you must configure the DPE using the command line
interface (CLI). Refer to the Cisco Broadband Access Center for Cable CLI Reference Guide
for these configuration instructions.

2-3
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
Chapter 2 Preparing to Install Components
Installation and Startup Process
5. Install the RDU. When you install the RDU, ensure that you:
• Obtain a valid BACC license key for each technology that you provision.
• Configure the syslog file for alerts. See the “Configuring the Syslog Utility to Receive
Alerts from BACC” section on page 5-1.
• Verify that the RDU is running by starting the administrators user interface. For more
information, see the Broadband Access Center for Cable Administrator’s Guide.
• Change the BACC administrator’s password. For more information, see the Broadband
Access Center for Cable Administrator’s Guide.
Note The existence of a text file called log.txt indicates that errors occurred during the
installation process. This text file is located under the <BACC_HOME> directory.
Table 2-1 Installation and Startup Process (continued)
Item Description

2-4
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
Chapter 2 Preparing to Install Components
Installation and Startup Process
6. Install and configure Network Registrar, if it is not already installed on your systems. We
recommend that you use Network Registrar 6.1.2.3 or higher. For more information, see the
Network Registrar Installation Guide.
• When you install Network Registrar Local Cluster (LCCM), ensure that you:
a. Obtain a valid Network Registrar license key for local cluster.
b. On all Network Registrar local cluster servers, install the BACC extensions for the
product. For more information see the “Installing Extensions on a Network Registrar
Server” section on page 3-3.
c. Configure Network Registrar, including its extensions. Specifically, you need to
configure scopes, policies, client-classes, and scope selection tags. For more
information, see the “Configuring Extensions” section on page 3-5, and also see the
Network Registrar User’s Guide.
d. Configure the syslog on the Network Registrar for alerts and debugging information.
See the “Configuring the Syslog Utility to Receive Alerts from BACC” section on
page 5-1.
e. Validate the installation by connecting to the administrative user interface and viewing
the administrator’s user interface. For more information, see the Cisco Broadband
Access Center for Cable Administrator’s Guide.
• When you install Network Registrar Regional Cluster (RCCM), ensure that you:
a. Identify the master server for Network Registrar Regional Installation, which
administers all the configured CNR local clusters. This server can be Solaris or
Windows or Linux. However, we recommend that you have the Solaris Operating
System on the CNR Regional Server.
b. Obtain a valid central-cluster license key for the CNR Regional Server.
c. After you install the BACC extensions for the product on all CNR local servers,
replicate the local data into regional and pull the “Replica Address Space”. For more
information see the Network Registrar User’s Guide.
d. Alternatively, you can also create subnets, client-classes, policies, and so on at RCCM
and push them to the required LCCM DHCP server. For more information, see the
Network Registrar User’s Guide.
e. Configure this CNR Regional CCM Server’s IP address, port number, and login details
into the RDU defaults for IP Reservation support. For more information, see the Cisco
Broadband Access Center for Cable Administrator’s Guide.
Note Network Registrar Release Version prior to 6.1 does not support Regional Cluster,
Hence BACC’s IP Lease Reservation Support feature cannot be used.
Table 2-1 Installation and Startup Process (continued)
Item Description

2-5
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
Chapter 2 Preparing to Install Components
Broadband Access Center Database Requirements
Broadband Access Center Database Requirements
Before you install BACC, be aware of these database considerations:
• File system block size
• Support for large files
File System Block Size
For optimum performance and reliability of the BACC database, configure the file system or systems
that contain the database files and database log files with an 8 KB block size or greater. If your system
configuration does not support an 8 KB block size, then configure the block size in multiples of 8 KB;
for example, 16 KB or 32 KB.
The installation program prompts you to specify a directory in which to install database files and
database log files. These directories are identified in BACC with system variables, <BACC_DATA> and
<BACC_DBLOG> respectively.
To verify that a directory resides on a file system with a minimum 8 KB block size, follow these steps:
Step 1 Run the UNIX mount command without any parameters to determine on which file system device the
directory resides. The default directory is /var/CSCObpr. For example:
/var on /dev/dsk/c0t0d0s4 read/write/setuid/intr/largefiles/onerror=panic/dev=2200004 on
Mon Nov 26 08:07:53
In this example, the file system device is /dev/dsk/c0t0d0s4.
7. Install and configure the KDC. When you install the KDC, ensure that you have this
information available:
• A valid license for KDC.
• KDC realm—Identified by a unique name, the KDC realm consists of a KDC, and the
clients and servers registered to that KDC.
Note The realm must match the certificate chain at the KDC.
• KDC FQDN—This is the fully qualified domain name on which the KDC server is located.
• KDC interface address—This is the interface (generally the IP address of the KDC server)
on which the KDC listens for requests.
Note During installation it may be necessary to install several Solaris patches on your
computer. The installation program will display a complete list of patches that are
required. Should patch installation become necessary, refer to the Sun Microsystems
website to download the required patches.
Note If you decide to terminate the BACC installation after the operating system database has been
installed, you must uninstall it before attempting to reinstall the product. If you do not do this,
and rerun the installation program, you cannot change the location of either the
<BACC_DATA> and <BACC_DBLOG> directories.
Table 2-1 Installation and Startup Process (continued)
Item Description

2-6
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
Chapter 2 Preparing to Install Components
Installation Checklist
Step 2 To determine the file system block size, use the df command. For example:
# df -g /dev/dsk/c0t0d0s4
Example output from the df command is as follows:
/var (/dev/dsk/c0t0d0s4 ): 8192 block size 1024 frag size
961240 total blocks 851210 free blocks 755086 available 243712 total files
239730 free files 35651588 filesys id
ufs fstype 0x00000004 flag 255 filename length
In this example, the block size is 8192 bytes, which is 8 KB. The block size of the selected directory,
therefore, is correct.
Large File Support
Ensure that the file system in which you place database files is configured to support files above 2 GB.
To verify large file support:
Step 1 Run the UNIX mount command without parameters.
Step 2 Note whether the intended file system contains the keyword largefiles.
An example output of the mount command is:
/var on /dev/dsk/c0t0d0s4 read/write/setuid/intr/largefiles/onerror=panic/dev=2200004 on
Mon Nov 26 08:07:53
In this example, the output contains the keyword largefiles. This file system, therefore, can support files
greater that than 2 GB.
Installation Checklist
Before you run the installation software, use this checklist to ensure that you are ready:
• Verify the prerequisite system hardware and software requirements described in Chapter 1,
“Overview”
• Determine the home directory (<BACC_HOME>) in which you want to install the BACC
component or components. The default directory is /opt/CSCObpr.
Note Cisco Systems recommends that yo have at least 350 MB of disk space available.
• Ensure that you have root access to the computers where you intend to install BACC components.
• Have your BACC license key or keys at hand. You need a valid license key for each technology that
you want to provision with BACC.
• For the RDU, determine where you want to install the data directory (<BACC_DATA>) and the
database transaction logs (<BACC_DBLOG>). (The default directory is /var/CSCObpr.)