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

Table of Contents

Preparing To Install Components
 Broadband Access Center Components
 Installation and Startup Process
 Broadband Access Center Database Requirements
 Installation Checklist
 Installation
 Upgrading to Broadband Access Center

Preparing To Install Components

This chapter provides the information you need to prepare for a successful Broadband Access Center for Cable (BAC) component installation, including these topics:

Broadband Access Center Components

The BAC installation program prompts you to install one or more of these components:

Note    Install the BAC Network Registrar extensions on a server running Network Registrar 6.0 or greater.
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 server.

2. Installing the Network Registrar extensions on a Network Registrar server or servers.

3. Installing the client API on one or more client workstations.

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.

Table 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 BAC database and database transaction log files. See the "Broadband Access Center Database Requirements" section.

3.

Review the installation checklist. See the "Installation Checklist" section.

4.

Install the RDU. When you install the RDU, ensure that you:

  • Obtain a valid BAC license key for each technology that you provision.
  • Configure the syslog file for alerts. See the "Configuring the Syslog Utility to Receive Alerts from BAC" section.
  • 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 BAC 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 <BPR_HOME> directory.
5.

Install and configure Network Registrar 6.0 or greater, if it is not already installed on your systems. For more information, see the Network Registrar Installation Guide.

When you install Network Registrar, ensure that you:

  • Obtain a valid Network Registrar license key.
  • On all Network Registrar servers, install the BAC extensions for the product. For more information see the "Installing Extensions on a Network Registrar Server" section.
  • 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, and also see the Network Registrar User's Guide.
  • Configure the syslog on the Network Registrar for alerts and debugging information. See the "Configuring the Syslog Utility to Receive Alerts from BAC" section.
  • Validate the installation by connecting to the administrative user interface and viewing the administrator's user interface. For more information, see the Broadband Provisioning Registrar Administrator's Guide.
6.

Install and configure the KDC. When you install the KDC, ensure that you have this information available:

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

If you intend to develop software that interoperate with BAC, install the BAC application programming interface on client workstations.

Note If you decide to terminate the BAC 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 <BPR_DATA> and <BPR_DBLOG> directories.

Broadband Access Center Database Requirements

Before you install BAC, be aware of these database considerations:

File System Block Size

For optimum performance and reliability of the BAC 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 BAC with system variables, <BPR_DATA> and <BPR_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.

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:

Installation

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

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

Installation Using the Graphical User Interface

To install BAC 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 BAC component.

Step 2   At the Solaris system prompt, navigate to the directory containing the setup.bin file. If you are using the BAC 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

The installation program verifies that you have installed the required patches to the Solaris 8 operating system and are running a supported version of Network Registrar. When the verification is complete, the Welcome screen appears (Figure 2-1).


Figure 2-1   Welcome Screen


Step 4   Click Next. The Choose Installation Type screen appears (Figure 2-2).


Figure 2-2   Choose Installation Type Screen


Step 5   Select one of the two installation types:

Step 6   Click Next. Depending on the option you selected in the preceding step, either the Installation Components screen appears (Figure 2-3), or you begin the lab installation.


Figure 2-3   Installation Components Screen


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 BAC 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 8 operating system and a supported version of Network Registrar. 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:

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.


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

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. To install in a lab environment go to the "Installing in a Lab Environment Using the CLI" section.


Upgrading to Broadband Access Center

This section describes how to upgrade a Broadband Provisioning Registrar (BPR) 2.0.3 or higher installation to BAC 2.5. If you have a BPR 2.0.2 release or any preceding releases, you must first upgrade your system to BPR 2.0.3 and then complete this upgrade procedure.

Note   Automated upgrade of BPR lab installations is not supported. The BAC installation program reports an error if a BPR lab installation upgrade is attempted. Consult your Cisco Systems representative for specific recommendations.

Upgrade Checklist

Prior to upgrading to BAC 2.5, you should familiarize yourself with the following upgrade rules:

1. You cannot add a DPE running BPR 2.0.x software into a provisioning group that already supports BAC 2.5.

2. You cannot revert a DPE running BAC 2.5 back to a BPR 2.0.x version without reverting all DPEs and deleting (or recreating) the provisioning group.

3. You cannot disable the PacketCable (voice) technology at a single server within a provisioning group; you must disable it at all servers (DPEs and NR extensions) in the group.

4. A provisioning group can have these DPE configurations:

    a. All servers support BAC 2.5 and have PacketCable enabled.

    b. All servers support BAC 2.5 and none have PacketCable enabled.

    c. All servers support BPR 2.0.3 only.

    d. A mixture of servers, supporting BAC 2.5 and BPR 2.0.3, with no PacketCable support at all.

Upgrade Process Overview

BAC 2.5 provides an incremental approach to upgrading your BPR system deployment; you should upgrade one component at a time. This approach helps to minimize the impact of the upgrade process on any ongoing provisioning operations.

BAC 2.5 can operate in a mixed-release environment where some components have been upgraded while others have not. However, the recommended sequence of component upgrade steps outlined in this chapter must be followed precisely.

Caution   Cisco does not recommend running in mixed-release BPR/BAC deployment mode beyond what is strictly necessary to perform the orderly upgrade of an entire deployment.
Note   Certain new features (like PacketCable) cannot be enabled in the provisioning group until all components in the provisioning group have been upgraded to BAC 2.5.

Upgrade Sequence

When upgrading, you must follow this sequence of activity:

Step 1   Upgrade the RDU server first. See the "Upgrading the RDU Server" section for additional information.

Step 2   Migrate the provisioning groups one by one. See the "Upgrading Provisioning Groups" section for additional information.


Upgrading the RDU Server

The RDU server upgrade process replaces the RDU server libraries with new versions, and migrates the database. The BAC installation program performs the upgrade process. The database migration is performed automatically when the RDU server starts after the BAC 2.5 installation is complete.

The RDU server component upgrade also upgrades or installs:

Caution   You must not uninstall the existing BPR RDU before installing the new version. The BAC installation program will remove the old version and install a new one.
Caution   BAC 2.5 does not support rolling back to BPR 2.0.3 after the upgrade has occurred. Please ensure that you have backed up the database before continuing.

RDU Upgrade Procedure

Complete this procedure to upgrade the RDU server from a previous BPR release:

Step 1   Stop the RDU server by running this command as a root user:

/etc/init.d/rduAgent stop

Step 2   Verify that the /var/tmp partition on your system, has sufficient space to support the database files.

Step 3   Run these commands to make a backup copy of all your database files:

mkdir -p /var/backup/rdu/db/
cp <BPR_DATA>/rdu/db/* /var/backup/rdu/db/.
mkdir -p /var/backup/rdu/dblog
cp <BPR_DBLOG>/rdu/dblog/* /var/backup/rdu/dblog/

Step 4   Run these commands to make a backup copy of all RDU configuration files:

mkdir -p /var/backup/rdu/conf
cp <BPR_DATA>/rdu/conf/* /var/backup/rdu/conf/

Step 5   Run this command to ensure that the disk/partition containing the database has at least 25% of total space available:

df -lk

Step 6   Run the BAC installation program in either the GUI or console-mode.

    a. If running in the console mode, use this command:

./setup.bin -console

    b. If running in the GUI mode, use this command:

./setup.bin

Step 7   The installer program detects that a previous RDU version is installed on your system and then prompts you to continue.

Step 8   Follow the installation program to upgrade the RDU. This program removes all old libraries and replaces them with the new BAC 2.5 libraries.

Note   The RDU server is not available for processing API or DPE requests during migration.

Step 9   Click Finish. When the installation program ends, the RDU server automatically restarts and the database migration begins.

Step 10   During migration the RDU server logs progress information into the following log files that you can monitor:

Once migration is complete, appropriate messages are printed into the logs.

Step 11   Run this command to restart the RDU server:

/etc/init.d/bprAgent restart rdu

Step 12   Check for successful initialization messages in the RDU server log file, located in the <BPR_DATA>/rdu/logs directory.

At this point, the RDU server upgrade is complete.

Note   The RDU database migration can take a significant amount of time to complete and you should plan accordingly. While specific performance will depend on hardware and other factors, the duration of migration could be approximately 10 minutes for every 100,000 devices in the database. Cisco recommends that you practice the RDU upgrade in a staging area prior to disrupting a live deployment.

Interrupting the RDU Upgrade

The consequences of interrupting the RDU upgrade process are different depending on which stage of the upgrade you interrupt. This applies when interruptions occur while:

    a. the upgrade process is run by the BAC installation program

    b. a database migration is performed after the BAC installation program finishes and the initial start of the RDU server

Warning Should it become necessary, for any reason, to interrupt the RDU installation during an upgrade, you may not be able to continue the upgrade by simply running the BAC installation program a second time. In this situation, you should re-install the BPR 2.0.x release and then run the BAC installation program again. When you re-install the BPR 2.0.3 release, you should restore the database using the backup that you made prior to attempting the upgrade.

If for any reason you interrupt the database migration process, which begins after the BAC installation program successfully upgrades the libraries and exits, the migration process will automatically restart the next time RDU server starts.

Upgrading Provisioning Groups

Once the RDU server has been successfully upgraded to the BAC 2.5 release, you can begin upgrading provisioning groups. Assuming that your provisioning group has redundant DPEs, and redundant DHCP servers, it will continue to service device requests while components are upgraded.

Complete these steps when migrating provisioning groups to BAC 2.5:

Step 1   Verify that all BPR components (DPEs and NR extensions) in the provisioning group have registered with the RDU at least once since it was upgraded. To do this, log in to the BAC administrator's user interface and verify that all servers are listed.

Step 2   Upgrade all DPEs in a given provisioning group. See the "Upgrading a DPE" section for additional information.

Step 3   Upgrade all Network Registrar extensions in the provisioning group. See the "Upgrading Network Registrar Extensions" section for additional information.


Once you have upgraded all DPEs and NR extensions in a given provisioning group to BAC 2.5, the provisioning group will switch to the BAC 2.5-only mode and will no longer operate in mixed-releases.

Achieving BAC-only mode for a provisioning group is significant for two reasons:

Upgrading a DPE

Completing this procedure will upgrade a DPE running BPR 2.0 to the BAC 2.5 version. You should refer to the Cisco Broadband Access Center for Cable Administrator's Guide for information on using some of the commands noted here.

To upgrade the DPE:

Step 1   Locate the upgrade bundle file, called upgrade20To25.bpr, on the BAC CD-ROM.

Step 2   FTP to the DPE with username admin and your DPE password.

Step 3   Change to the incoming directory and transfer the upgrade bundle file in binary mode to the DPE.

Step 4   Close the FTP session.

Step 5   Telnet and login to the DPE.

Step 6   Run the enable command to enter the privileged mode.

Step 7   Stop the DPE.

Step 8   Run the upgrade command. A list of all available upgrade bundles, including upgrade20To25.bpr, will appear.

Step 9   Locate the number corresponding to upgrade bundle upgrade20To25.bpr. Enter that number and the upgrade process starts. Once complete, the upgrade process automatically reboots the DPE.

Step 10   When the DPE reboots, telnet and login again.

Step 11   Run the show dpe command and verify the version of the DPE.


After completing the upgrade process, no further DPE configuration should be necessary to allow the DPE to continue its operation. However, you must enable any new feature separately after all provisioning group components are upgraded to BAC.

Note   Upgrading a DPE will clear its current cache. After the DPE is upgraded, and registered with the RDU, it will repopulate its cache.

Upgrading Network Registrar Extensions

You must upgrade all BAC Network Registrar (NR) extensions on each Network Registrar DHCP server in a given provisioning group.

Note   Only upgrade Network Registrar extensions, in a given provisioning group, after you have upgraded all DPEs in the provisioning group. You can log into the administrators user interface to verify the version of each DPE server in the provisioning group.

To upgrade NR extension point on each NR DHCP server:

Step 1   Log in as root.

Step 2   Manually unconfigure the BAC extensions on the Network Registrar server. You can unconfigure Network Registrar from any server that has nrcmd installed and connectivity with Network Registrar. Follow these steps:

Note    This procedure assumes the default installation directories for BAC and Network Registrar. It also uses the default Network Registrar username and password. If you installed these products in other directories, you should enter those directory names instead.

    a. To uninstall the BAC extensions from your Network Registrar configuration, use these commands:

<NR_HOME>/usrbin/nrcmd -N admin -P changeme -b <
<BPR_HOME>/cnr_ep/bin/bpr_cnr_disable_extpts.nrcmd

    b. To reload your DHCP server, use these commands:

/etc/init.d/aicservagt stop
/etc/init.d/aicservagt start

Alternatively, enter this command:

<NR_HOME>/usrbin/nrcmd -N admin -P changeme "dhcp reload"

    c. To remove the BAC extensions from the Network Registrar extensions directory, use this command:

rm -f <NR_HOME>/extensions/dhcp/dex/libbprextensions.so

Step 3   Run the BAC uninstallation program in either the GUI or console-mode.

    a. If running in the console mode, use this command:

<BPR_HOME>/_uninst/uninstall.bin -console

    b. If running in the GUI mode, use this command:

<BPR_HOME>/_uninst/uninstall.bin

Step 4   Install the BAC Network Registrar extension points. See "Installing Network Registrar Extensions" section for additional information.



hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Jan 15 07:01:11 PST 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.