-
null
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter explains how to prepare for a successful installation of Broadband Access Center (BAC).
This chapter describes:
•Installation and Startup Process
The BAC component installation program prompts you to install:
•Regional Distribution Unit (RDU)
The RDU is the primary server in the BAC provisioning system. You should install the RDU on a Solaris 8 or 9 server that fulfills the requirements described in BAC Components at a Glance, page 1-3.
The RDU:
–Manages the generation of device configurations.
–Processes application programming interface (API) requests for all BAC functions.
–Manages the BAC system.
Note The installation program preloads required data into the RDU database, and starts the RDU daemon through the BAC process watchdog. The SNMP agent and the administrator user interface are installed for the RDU. For details on configuring the SNMP agent, refer to the Cisco Broadband Access Center DPE CLI Reference 2.7.1. For information on the BAC process watchdog and the administrator user interface, refer to the Cisco Broadband Access Center Administrator Guide 2.7.1.
•Device Provisioning Engine (DPE)
A DPE is the major component of the provisioning group, handling all device interactions with the RDU. You should install a DPE on Sun SPARC computers that run on Solaris 8 or Solaris 9 servers that meet the requirements described in BAC Components at a Glance, page 1-3.
The DPE:
–Caches instructions generated at the RDU.
–Manages various CPE protocol services. These services obtain their operating instructions from the instruction cache.
Note The installation program installs a CLI on your system to help configure the DPE. The BAC process watchdog and the SNMP agent are installed for the DPE also. For information on configuring the DPE and configuring the SNMP agent, refer to the Cisco Broadband Access Center DPE CLI Reference 2.7.1.
•Cisco Network Registrar extensions
The Network Registrar extensions are the link between BAC and Network Registrar. You should install this component on all Network Registrar servers in your BAC environment. If you are deploying BAC in a failover environment, ensure that you install the extensions on the failover servers also.
Note We recommend that you install the BAC Network Registrar extensions on a server on which Network Registrar 6.2.3.2 or later runs.
•Key Distribution Center (KDC)
The KDC, along with the DPE registration service, handles the authentication of all PacketCable voice technology MTAs. For maximum performance and segmentation of the network, you may install one KDC instance per provisioning group. When you perform a laboratory installation, the KDC is installed on the lab computer. For performance reasons however, in a component installation, you should install the KDC on a separate server.
Note The KDC and DPE require service keys, which allow them to communicate.
To ensure a smooth installation and startup process:
Note During installation, it may be necessary to install several Solaris patches on your computer. Should patch installation become necessary, refer to the Sun Microsystems support site to download these patches. For a list of recommended patches, see Operating System Requirements, page 1-1.
Step 1 Determine the computers and servers on which you are installing individual components of BAC.
Step 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 Database Requirements.
Step 3 Review the installation checklist described in Installing Broadband Access Center, page 3-1.
Step 4 Install the RDU. Ensure that you:
•Know the target location for the:
–Home directory
–Data directory
–Database Transaction Logs directory
•Verify the existence of a text file called log.txt, which indicates that errors occurred during the installation process. This file resides in the BPR_HOME directory.
Step 5 Install a DPE. Ensure that you know the target location for the:
•Home directory
•Data directory
Note If you exit the BAC installation after the operating system database is installed, you must uninstall the BPR_HOME and the BPR_DATA directories before installing the product again. See Uninstalling Broadband Access Center, page 8-1, for information on how to uninstall BAC. Also, stopping the installation midway does not generate the log file.
Step 6 After installing the RDU, ensure that you:
a. Obtain a valid BAC license key for each technology that you provision. This includes the DPE and the KDC components.
Note If you have not yet received your licenses, contact your Cisco representative before proceeding.
b. Verify that the RDU is running by starting the administrator user interface.
To launch the user interface, enter the administrator's location from your web browser using:
http://machine_name:port_number/
Note To access the administrator user interface via HTTP over SSL, also known as HTTPS, enter: https://machine_name:port_number/
•machine_name—Identifies the computer on which the RDU is running.
•port_number—Identifies the computer port on which the server side of the administrator application runs. The default port number is:
–8100 for HTTP over TCP
–8443 for HTTP over SSL
The main login page appears.
c. Change the BAC administrator's password.
To change the password, enter the default username (admin) and password (changeme). Click Login.
The Change Password screen appears and prompts you to change the default password. Enter a new password, and click Login.
Step 7 Optionally, configure the syslog file for alerts. See Configuring the Syslog Utility to Receive Alerts from BAC, page 5-1.
Note You can set up the syslog file on any BAC component server.
Step 8 After installing the DPE, ensure that you:
a. Change the DPE login password and the enable password from the command-line interface (CLI).
–To change the login password, access the CLI in the enabled mode, and enter:
dpe# password password
where password identifies the new DPE password.
–To change the DPE enable password, enter:
dpe# enable password password
where password identifies the local configured password currently in effect or, optionally, provides a new password. If this parameter is omitted, you are prompted for the password.
For more information, refer to the Cisco Broadband Access Center DPE CLI Reference 2.7.1.
b. Configure the DPE from the CLI. For configuration instructions, refer to the Cisco Broadband Access Center DPE CLI Reference 2.7.1.
Step 9 Install and configure Network Registrar, if it is not already installed on your systems. We recommend that you use Network Registrar 6.2.3.2 or later. At a minimum, you must have version 5.5.12 installed on your system. For installation information, refer to the Cisco Network Registrar Installation Guide, 6.2.
•When you install the 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 BAC extensions. See Installing Network Registrar Extensions from the CLI, page 3-6.
c. Configure Network Registrar, including its extensions. Specifically, you need to configure scopes, policies, client classes, and scope-selection tags. See Configuring Extensions, page 3-9. Also refer to the Cisco Network Registrar User's Guide, 6.2.1.
d. Configure the Network Registrar syslog for alerts and debugging information. See Configuring the Syslog Utility to Receive Alerts from BAC, page 5-1.
e. Validate the installation by connecting to the administrator user interface and viewing the administrator user interface. For more information, refer to the Cisco Broadband Access Center Administrator Guide 2.7.1.
•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 Network Registrar local clusters. This server can be Solaris, Windows, or Linux. However, we recommend that you have the Solaris operating system on the Network Registrar Regional Server.
b. Obtain a valid central-cluster license key for the Network Registrar Regional Server.
c. After you install the BAC extensions for the product on all Network Registrar local servers, replicate the local data into regional and pull the "Replica Address Space". For more information, refer to the Cisco Network Registrar User's Guide, 6.2.1.
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, refer to the Cisco Network Registrar User's Guide, 6.2.1.
e. Configure this Network Registrar Regional CCM Server's IP address, port number, and login details into the RDU defaults for IP Reservation support. For more information, refer to the Cisco Broadband Access Center Administrator Guide 2.7.1.
Note Network Registrar versions earlier than 6.1 do not support the Regional Cluster feature. Hence, you cannot use the IP Lease Reservation feature that BAC supports.
Step 10 Install and configure the KDC. When you install the KDC, ensure that you:
•Obtain a valid BAC license.
•Have the following information at hand:
–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—Identifies the fully qualified domain name on which the KDC server is located.
–KDC interface address—Identifies the interface (generally the IP address of the KDC server) on which the KDC listens for requests.
Before you install BAC, be aware of these database considerations:
•File system block size
•Large file support
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:
Step 1 Log in as root.
Step 2 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:
# mount
/var on /dev/dsk/c0t0d0s4 read/write/setuid/intr/largefiles/logging/xattr/onerror=panic/ dev=2200004 on Thu Jun 15 16:58:21 2006
In this example, the file system device is /dev/dsk/c0t0d0s4.
Step 3 To determine the file system block size, use the df command.
For example:
# df -g /dev/dsk/c0t0d0s4
/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.
Ensure that the file system in which you place database files is configured to support files larger than 2 GB.
To verify large file support:
Step 1 Log in as root.
Step 2 Run the UNIX mount command without parameters.
For example:
# mount
/ on /dev/dsk/c1t0d0s0 read/write/setuid/intr/largefiles/logging/xattr/onerror=panic/dev=1d80008 on Thu Jun 15 16:58:16 2006
/etc/mnttab on mnttab read/write/setuid/dev=4740000 on Thu Jun 15 16:58:14 2006
/var on /dev/dsk/c1t0d0s4 read/write/setuid/intr/largefiles/logging/xattr/onerror=panic/dev=1d8000c on Thu Jun 15 16:58:21 2006
/var/run on swap read/write/setuid/xattr/dev=1 on Thu Jun 15 16:58:22 2006
/tmp on swap read/write/setuid/xattr/dev=2 on Thu Jun 15 16:58:39 2006
Step 3 Note whether the intended file system contains the keyword largefiles.
For example:
/var on /dev/dsk/c1t0d0s4 read/write/setuid/intr/largefiles/logging/xattr/onerror=panic/dev=1d8000c on Thu Jun 15 16:58:21 2006
In this example, the output contains the keyword largefiles. This file system, therefore, can support files greater than 2 GB.