Cisco Broadband Access Center 3.10 Installation Guide
Bias-Free Language
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.
- Updated:
- September 22, 2014
Chapter: Before You Begin
Before You Begin
This chapter describes the requirements and dependencies for installing Cisco BAC successfully.
Operating System Requirements
For Linux, you must install Cisco BAC on Red Hat Enterprise Linux 5.x or 6.4 using x86 and 64 bit hardware system with at least 4 GB of memory. The SELinux should be disabled. Also, ensure that before installing Cisco BAC, you install the sysstat package for the proper execution of the diagnostic scripts. This is an optional package which you might have not installed while installing Linux.
If the system has 64-bit libraries, you must also download and install 32-bit glibc and libgcc rpm packages on RHEL 6.1.
Download the two 32-bit packages, and install them using the below commands:
Minimum Hardware Requirements
Table 2-1 lists the minimum hardware requirements for the various Cisco BAC components.
|
|
|
|
|
|
|---|---|---|---|---|
Deployment Requirements
This section details the minimum hardware requirements that you need to successfully deploy Cisco BAC in your environment. This section contains:
Smallest Fully Redundant Deployment
A smallest fully redundant deployment of about 500,000 devices can be configured with one provisioning group that has two DPEs. This setup requires:
Incremental Scaling
For every additional 500,000 devices that you add, you need two DPEs configured in a new provisioning group. A single deployment can handle up to eight million devices.
A single pair of load balancers can handle DPEs in multiple provisioning groups. We recommend that you determine the number of load balancers, based on the network configuration of your service provider.
Types of Installation
This section describes how to install individual Cisco BAC components. The installation program enables you to install one or all components of Cisco BAC; that is, RDU, DPE, Cisco Network Registrar Extension Points, and Cisco Access Registrar Extension Points.
Note
This release does not feature a lab installation, but you can perform its equivalent by installing all components on a single machine. To perform the activity, we recommend that you have at least 500 MB of disk space available.
You can install RDU, DPE, Cisco Network Registrar, and Cisco Access Registrar through the CLI. For details on Cisco BAC components installation, see Installing and Uninstalling Cisco BAC on Linux.
Before you install Cisco BAC, familiarize yourself with the installation startup processes and checklists described in Before You Begin.
See Installation Worksheet, for information on Cisco BAC installation parameters.
Installation Checklist for Linux
Before you install Cisco BAC, review the checklist in Table 2-2 .
|
|
|
|---|---|
1. |
|
2. |
|
3. |
|
4. We recommend that you have at least 500 MB of disk space available; otherwise installation will not take place. |
|
5. |
|
6. We recommend that you locate the data directory on a different physical disk than the home directory; for example, /var/disk0/CSCObac. The disk should have at least 1 GB of free space. The installation program, by default, installs the data directory, the database transaction logs directory, and the logs directory in the same location. We recommend that you locate the database transaction logs directory on the fastest disk on the system. Also, ensure that 1 GB of disk space is available. |
|
7. |
|
8. |
|
9. |
|
10. |
|
11. |
|
12. |
|
13. |
|
14. config—File that controls the state of SELinux on the system. In this file, set the value of SELINUX to disabled and SELINUXTYPE to targeted. |
|
15.
Note |
|
16. |
|
17. |
Database Requirements
Before you install Cisco BAC, check the following:
File System Block Size
On Linux, block size is selected at the time of high-level formatting. If the mke2fs (i.e.,make ext2 filesystem) command is used to create the filesystem, valid block size vales are 1024, 2048 and 4096 bytes. The block size for any existing ext2 or ext3 file system (the most common file system types on Linux) can be obtained by using the dumpe2fs command with the device name as an argument.
The installation program prompts you to specify a directory in which you prefer to install database files and database transaction log files. These directories are identified in Cisco BAC with system variables BPR_DATA and BPR_DBLOG, respectively.
To verify that a directory resides on a file system with a minimum 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.
/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 block size of the file system, use the df command.
In this example, the block size is 4096 bytes, which is 4 KB.
Support for Large Files
Ensure that the file system in which you place database files is configured to support files larger than 2 GB.
Step 1 Run the UNIX mount command without parameters.
Step 2 Note whether the intended file system contains the keyword largefiles.
/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 Port Information
Before you install Cisco BAC, determine the ports on which the Cisco BAC components, the RDU, the DPE, CNR extensions and CAR extensions, listen during communication to one another or to the 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, appears:
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-3 lists the required external inbound ports and their default values.
|
|
|
|
|
|
|---|---|---|---|---|
Table 2-4 lists the external outbound ports and their default values.
|
|
|
|
|
|
|---|---|---|---|---|
Table 2-5 lists the internal ports and their default values.
|
|
|
|
|
|
|---|---|---|---|---|
Installation Worksheet
This section describes the basic configuration information required for successful installation of Cisco BAC. Table 2-6 provides the worksheet that you can use to record the information specific to the installation.
Feedback