Table Of Contents
Before Installing Broadband Access Center
BAC Components
Installation and Startup Process
Database Requirements
File System Block Size
Large File Support
Required Ports Information
Installation Checklist
Before Installing Broadband Access Center
This chapter provides the information that you need to prepare for a successful installation of Broadband Access Center (BAC).
This chapter describes:
•
BAC Components
• Installation and Startup Process
• Database Requirements
• Required Ports Information
• Installation Checklist
BAC Components
The BAC component installation program prompts you to install either or both of these components:
•Regional Distribution Unit (RDU).
The RDU is the primary server in the BAC provisioning system. You should install the RDU on a Solaris 9 server that meets the requirements described in the "Hardware Requirements" section on page 1-2.
The RDU:
–Generates instructions that direct responses from the provisioning group to various customer premises equipment (CPE).
–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 watchdog process. The SNMP agent and the administrator GUI are installed for the RDU.
For details on configuring the SNMP agent, refer to the Cisco Broadband Access Center DPE CLI Reference, Release 3.0. For information on the BAC watchdog process and the administrator GUI, refer to the Cisco Broadband Access Center Administrator's Guide, Release 3.0.
•Device Provisioning Engine (DPE).
BAC supports the deployment of a DPE on Sun SPARC computers running Solaris 9.
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 watchdog process 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, Release 3.0.
Installation and Startup Process
To ensure a smooth installation and startup process, complete the following order of operations:
Step 1 Determine the computers and the servers on which you are installing the 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 the database transaction log files (see the "Database Requirements" section).
Step 3 Review the installation checklist (see the "Installation Checklist" section).
Step 4 Install the RDU. Ensure that you:
•Know the target location for the following directories:
–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 is located under the BPR_HOME directory.
Step 5 Install a DPE. Ensure that you know the target location for the following directories:
•Home Directory
•Data Directory
Note If you exit the BAC installation after the operating system database has been installed, you must uninstall the BPR_HOME and the BPR_DATA directories before installing the product again. (For information on uninstallation, see Uninstalling Broadband Access Center, page 5-1.) Also, stopping the installation mid-way does not generate the log file.
If you rerun the installation without uninstalling the specified directories, you cannot change the location of the BPR_DATA or the BPR_DBLOG directories.
Step 6 After installing the RDU, ensure that you:
•Obtain a valid BAC license key for each technology that you provision, specifically for the CPE WAN Management Protocol and for the DPE component.
Note If you have not yet received your licenses, contact your Cisco representative before proceeding.
•Verify that the RDU is running by launching the BAC administrator user interface.
–To launch the administrator user interface, enter the administrator's location by using this syntax:
http://machine_name/
where machine_name identifies the computer on which the RDU is running.
Note To access the administrator user interface using HTTP over SSL/TLS, enter https://machine_name.
The server-side of the administrator application runs on a computer port. By default, this port number is set at 80 for HTTP and 443 for HTTP over SSL/TLS.
The main login page appears.
•Change the BAC administrator 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 BAC Alerts, page 6-1).
Note You can set up the syslog file on any BAC component server.
Step 8 After installing the DPE, ensure that you:
•Change the DPE login password and the enable password from the 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 the following command:
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, Release 3.0.
•Configure the DPE from the CLI. Refer to the Cisco Broadband Access Center DPE CLI Reference, Release 3.0, for these configuration instructions.
Step 9 Optionally, configure the syslog file for alerts (see Configuring the Syslog Utility to Receive BAC Alerts, page 6-1).
Note You can set up the syslog file on any BAC component server.
Database Requirements
Before you install BAC, remember:
•File system block size
•Large file support
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 transaction 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 transaction 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 Run the UNIX mount command without any parameters to determine on which file system device the directory resides. The default directory is /var/CSCObac.
For example:
# mount
/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
/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 larger than 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.
For example:
# mount
/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 than 2 GB.
Required Ports Information
Before installation, you must determine the ports on which the BAC components, the RDU and the DPE, listen during communication with each other or with CPE.
The installation program checks for the availability of all ports: both configurable and nonconfigurable.
If the port that you have specified is unavailable, the installation program displays a message; otherwise, the message similar to the following one appears:
Not a valid port number
In the case of a nonconfigurable port, the installation program notifies you and exits the program without making any changes to the system.
Table 2-1 lists the required ports and their default values:
Table 2-1 Default Ports Used by BAC Components
Component
|
Default Port Number
|
Protocol
|
Configurable?
|
Used by ...
|
RDU
|
49187
|
TCP
|
Yes
|
RDU process
|
RDU/DPE
|
49888
|
TCP
|
No
|
Process Watchdog
|
RDU/DPE
|
49887
|
TCP
|
No
|
SNMP Agent
|
RDU
|
80
|
TCP
|
Yes
|
Administrator user interface (HTTP)
|
RDU
|
443
|
TCP
|
Yes
|
Administrator user interface (HTTP over SSL/TLS)
|
DPE
|
49186
|
UDP
|
Yes
|
DPE process
|
DPE
|
2323
|
TCP
|
Yes
|
DPE CLI
|
DPE
|
7547
|
TCP
|
Yes
|
CWMP Service 1
|
DPE
|
7548
|
TCP
|
Yes
|
CWMP Service 2
|
DPE
|
7549
|
TCP
|
Yes
|
HTTP File Service 1
|
DPE
|
7550
|
TCP
|
Yes
|
HTTP File Service 2
|
| |
Note BAC supports two instances each for the CWMP service and the HTTP file service; so you can configure different options for each service.
For instance, CWMP service 1 is, by default, configured to require HTTP digest authentication; but without HTTP over the SSL/TLS protocol. This service is configured to run on port 7547 and is enabled by default. CWMP service 2 is configured on port 7547 with HTTP over SSL/TLS; but is disabled by default. You can reconfigure any of these defaults for each service to suit your requirements.
|
Installation Checklist
Before you run the installation software, ensure that you are ready by verifying with the following checklist. Also, check with the information detailed in the "Installation Notes" section on page 3-2.
1. Verify the prerequisite system hardware and software requirements described in the "Introduction" section on page 1-1.
2. Ensure that you have root access to the computers on which you intend to install BAC components.
3. Have your BAC license key or keys at hand. You need a valid license key for each technology that you want to provision with BAC, namely CWMP and the DPE.
4. Determine the home directory (BPR_HOME) on which you want to install the BAC component or components. The default directory is /opt/CSCObac.
Note Cisco recommends that you have at least 350 MB of disk space available for the home directory. For detailed information, see the "Installation Notes" section on page 3-2.
5. For the RDU, determine where you want to install the data directory (BPR_DATA) and the database transaction logs (BPR_DBLOG). The default directory is /var/CSCObac.
Note Cisco recommends that you install the database transaction logs on a different physical disk than the home directory or the data directory. For detailed information, see the "Installation Notes" section on page 3-2.
6. For the RDU, select the shared secret password that the BAC servers on your network use as a token to authenticate communication with one another. The shared secret password is the same for all BAC servers on your network.
