Cisco Broadband Access Center User Manual

Cisco Broadband Access Center for Cable Installation

Release 2.7

Americas Headquarters

Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000

800 553-NETS (6387)

Fax: 408 527-0883

Guide

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 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 Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco 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 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 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

Store are service marks; and Access Registrar, Aironet, AsyncOS,

IMPLIED, INCLUDING, WITHOUT

Certified Internetwork Expert logo, Cisco IOS,

logo, LightStream, Linksys, MediaTone,

logo are registered trademarks of

Preface vii

Audience vii

How This Guide Is Organized vii

Document Conventions viii

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:

OL-19105-01

Cisco Broadband Access Center for Cable Installation Guide 2.7

vii

Preface

Section Title Description

Chapter 1 Overview Provides general requirements for a successful installation of

BACC.

Chapter 2 Preparing to Install

Components

Chapter 3 Installing

Components

Chapter 4 Installing in a Lab

Environment

Chapter 5 Post-Installation

Activities

Chapter 6 Upgrading

Broadband Access Center for Cable

Chapter 7 Setting Up a Device

Provisioning Engine

Appendix A Network Registrar

Configuration File Example

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.

Describes how to install the individual components of BACC using either the graphical user interface or the CLI.

Describes how to install a lab version of BACC using either the graphical user interface or the CLI.

Describes those activities that are performed following installation.

Describes the upgrade procedures performed on various BACC components.

Describes how to configure a device provisioning engine (DPE).

Shows examples of files used to configure Network Registrar for high-speed data (HSD) and voice technology deployments.

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.

viii

Cisco Broadband Access Center for Cable Installation Guide 2.7

OL-19105-01

Preface

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.

CHAP T ER

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

OL-19105-01

Cisco Broadband Access Center for Cable Installation Guide 2.7

1-1

Network Registrar Requirements

JDK Patches for Solaris 9

The JDK patches recommended for successful BACC installation include:

• 113886-26 • 113887-26

• 112785-44 • 113096-03

KDC Patches

The KDC patches required for successful BACC installation include:

• 112438-01

• 109326-06

Network Registrar Requirements

Chapter 1 Overview

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.

1-2

Note The hardware installation procedures for the device provisioning engine are described in the following

guides:

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

Server Class

10000 DPE 1 2 SUN V210 1GHz

CNR 1 2 SUN V210 1GHz 1 1 GB

KDC 1 - SUN V210 1GHz 1 1 GB

25000 DPE 1 2 SUN V210 1GHz

CNR 1 2 SUN V210 1GHz 1 1 GB

KDC 1 - SUN V210 1GHz 2 2 GB

100000 DPE 1 2 SUN V210 1GHz

CNR 1 2 SUN V210 1GHz 2 2 GB

KDC 1 - SUN V210 1GHz 2 2 GB

250000 DPE 2 2 SUN V210 1GHz

CNR 2 2 SUN V210 1GHz 2 2 GB

KDC - - NA

500000 DPE 2 2 SUN V210 1GHz

CNR 2 2 SUN V210 1GHz 2 2 GB

KDC - - NA

# Processors

1 1 GB

2 2 GB

Memory

- -

2 2 GB

- -

OL-19105-01

Cisco Broadband Access Center for Cable Installation Guide 2.7

1-3

Types of Installations

Table 1-1 Hardware Recommendations per Provisioning Group (continued)

Chapter 1 Overview

Min. #

# Subscribers Server

Servers

1 million DPE 2 2 SUN V210 1GHz

CNR 2 2 SUN V210 1GHz 2 2 GB or 4 GB

KDC - - NA

Lab Install Single server

1 1 SUN V210 1GHz 1 1 GB

Recommended # Servers

Server Class

# Processors Memory

2 2 GB or 4 GB

- -

for all

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.

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

“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.

Chapter 3,

1-4

Cisco Broadband Access Center for Cable Installation Guide 2.7

OL-19105-01

CHAP T ER

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.

OL-19105-01

–

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.

Cisco Broadband Access Center for Cable Installation Guide 2.7

2-1

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.

Chapter 2 Preparing to Install Components

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

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.

“Broadband Access Center Database

2-2

Cisco Broadband Access Center for Cable Installation Guide 2.7

OL-19105-01

Chapter 2 Preparing to Install Components

Table 2-1 Installation and Startup Process (continued)

Item Description

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 and Startup Process

installation process. This text file is located under the <BACC_HOME> directory.

OL-19105-01

Cisco Broadband Access Center for Cable Installation Guide 2.7

2-3

Installation and Startup Process

Table 2-1 Installation and Startup Process (continued)

Item Description

6. Install and configure Network Registrar, if it is not already installed on your systems. We

Chapter 2 Preparing to Install Components

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

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.

“Installing Extensions on a Network Registrar

• 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.

2-4

Cisco Broadband Access Center for Cable Installation Guide 2.7

OL-19105-01

Chapter 2 Preparing to Install Components

Table 2-1 Installation and Startup Process (continued)

Item Description

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

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.

Broadband Access Center Database Requirements

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.

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

OL-19105-01

In this example, the file system device is /dev/dsk/c0t0d0s4.

Cisco Broadband Access Center for Cable Installation Guide 2.7

2-5

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:

Chapter 2 Preparing to Install Components

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.

2-6

• 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.)

Cisco Broadband Access Center for Cable Installation Guide 2.7

OL-19105-01

Chapter 2 Preparing to Install Components

Note Cisco recommends that you install the database transaction logs on a different physical disk than either

the home directory or the data directory.

• For the RDU, select the shared secret password that BACC servers on your network use as a token

to authenticate communication with one another. The shared secret password is the same for all BACC servers on your network.

• We recommend that Network Registrar 6.1.2.3 or higher is installed and running on any servers

where you are installing BACC extensions.

• For extensions, determine the name of provisioning group to which the Network Registrar server

belongs.

• For Network Registrar extensions, determine where you want to install the data directory

(<BACC_DATA>).

• Verify that you have the necessary Network Registrar configuration files, (See Appendix A,

“Network Registrar Configuration File Example” for an example of these configuration files.)

• Verify that you have the necessary KDC servers available.

Installation

Note If you interrupt the installation program after it begins copying files, you may have to manually clean up

the locations of copied files.

Installation

The initial steps in the BACC installation program are identical regardless of the BACC component you are installing. This section describes how to work with the installation program and the initial installation steps.

You install BACC using either the graphical user interface (GUI) or the command line interface (CLI). Both of these interfaces are supplied with BACC.

Installation Using the Graphical User Interface

To install BACC using the graphical interface:

Step 1 Using an X-Windows client, log in as root on the computer on which you intend to install the BACC

component.

Step 2 At the Solaris system prompt, navigate to the directory containing the setup.bin file. If you are using the

BACC CD-ROM, you will find setup.bin located at the root of your CD-ROM drive.

Step 3 Enter this command to start the installation program:

> setup.bin

OL-19105-01

The installation program verifies that you have installed the required patches to the Solaris operating system. When the verification is complete, the Welcome screen appears.

Step 4 Click Next. The Choose Installation Type screen appears.

Cisco Broadband Access Center for Cable Installation Guide 2.7

2-7

Installation

Chapter 2 Preparing to Install Components

Step 5 Select one of the two installation types:

• Individual Components—This option enables you to install an RDU, Network Registrar extensions, the

DPE, or the KDC. See these sections for the appropriate installation instructions:

–

Installing the Regional Distribution Unit, page 3-2

–

Installing Extensions on a Network Registrar Server, page 3-3

–

Installing the Key Distribution Center, page 3-7

–

Installing the Device Provisioning Engine, page 3-8

• Lab—This option enables you to install the software in a laboratory environment. See Chapter 4,

“Installing in a Lab Environment” in this guide.

Step 6 Click Next. Depending on the option you selected in the preceding step, either the Installation

Components screen appears, or you begin the lab installation.

Note You must select one of the displayed installation components before you can proceed with the

installation.

Installing from the Command Line

To perform the initial installation procedure from the command line:

Step 1 Log into the intended BACC host as root.

Step 2 At the Solaris system prompt, change directory to your CD-ROM drive or other installation media. The

installation program, setup.bin, is at the root of this drive.

Step 3 Enter this command to start the installation program:

> setup.bin -console

The installation program verifies that you have installed the required patches to the Solaris operating system. When the verification is complete, the program displays welcome information.

Step 4 Press Enter to continue. The program prompts you to choose the installation type. You can choose to

install:

• Individual components

• Lab installation

Step 5 To choose individual components, enter C; or, to choose Lab installation, enter L. For example:

Choose Installation

Choose the type of BPR installation you want to install.

2-8

The Lab installation will store all components in the chosen destination. Otherwise, you can select individual components and destinations.

Enter C for individual components or L for lab [C]:c

Cisco Broadband Access Center for Cable Installation Guide 2.7

OL-19105-01

Chapter 2 Preparing to Install Components

The program prompts you to confirm the installation type.

Step 6 Press y and then Enter to continue.

At this point you must decide which installation you want to perform. To install individual components go to the

“Installing Components Using the CLI” section on page 3-8. To install in a lab environment go

to the “Installing in a Lab Environment Using the CLI” section on page 4-3.

Installation

OL-19105-01

Cisco Broadband Access Center for Cable Installation Guide 2.7

2-9

+ 53 hidden pages

Cisco Broadband Access Center User Manual

CONTENTS

Preface

Overview

Operating System Requirements

JDK Patches for Solaris 8

Network Registrar Requirements

JDK Patches for Solaris 9

KDC Patches

Hardware Requirements

Types of Installations

Preparing to Install Components

Broadband Access Center for Cable Components

Installation and Startup Process

Broadband Access Center Database Requirements

File System Block Size

Installation Checklist

Large File Support

Installation

Installation Using the Graphical User Interface

Installing from the Command Line