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 describes the requirements and dependencies for installing Cisco BAC successfully.
On Solaris
You must install Cisco BAC on a Sun SPARC platform that runs Solaris 10 operating system with at least 4 GB of memory. We recommend that you use a Sun SPARC multiprocessor platform.
Note Before installing Cisco BAC, download and install the recommended Solaris patches from the Sun Microsystems support site.
Cisco BAC ships with the required JRE version 1.6.0_27, which resides in the BPR_HOME/jre directory.
Ensure that you have the latest Solaris patch bundle for the operating system installed in your system, before you install Cisco BAC. We recommend Solaris 10 08/11 for Solaris 10 operating system.
You must also download and install the Java Platform Standard Edition (Java SE) cluster patches recommended by Sun Microsystems to install Cisco BAC on a system that runs Solaris 10, see Table 2-1.
|
|
120900-04 |
libzonecfg patch |
121133-02 |
Zones library and zones utility patch |
119254-44 |
Install and patch utilities patch, for more information, see Chapter 3, "Installing and Uninstalling Cisco BAC on Solaris" |
118918-24 |
Solaris crypto framework patch |
119042-10 |
svccfg and svcprop patch |
119578-30 |
FMA patch |
144488-09 |
Kernel patch |
Before you install Cisco BAC, you must install the SUNWxcu4 package available as part of the Solaris OS installation. This is an optional package that you might not have installed while installing Solaris.
On Linux
For Linux, you must install Cisco BAC on Red Hat Enterprise Linux 5 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.
Table 2-1 lists the minimum hardware requirements for the various Cisco BAC components.
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:
•Two RDU servers
•One RAID unit
•Two DPE servers
•One CAR server
•Two Cisco ACE units
•Two Cisco Network Registrar servers
•STUN server (required only for devices behind NAT setup)
•CMHS server
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.
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, Cisco Access Registrar Extension Points and STUN server.
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 component installation, see Installing and Uninstalling Cisco BAC on Solaris, page 3-1 for Solaris and Installing and Uninstalling Cisco BAC on Linux, page 4-1 for Linux.
Before you install Cisco BAC, familiarize yourself with the installation startup processes and checklists described in Before You Begin.
See the Installation Worksheet, for information on Cisco BAC installation parameters.
Before you run the installation program, use the following checklist to ensure your readiness.
|
|
---|---|
1. |
|
2. |
|
3. |
|
4. If you have not received your licenses, contact your Cisco representative before you proceed further. |
|
5. We recommend that you have at least 500 MB of disk space available for the home directory as well as for the /tmp directory and 5 MB of disk space available for /etc/init.d directory. |
|
6. By default, the database transaction logs directory (BPR_DBLOG) is installed in the same directory as the data directory (BPR_DATA). We recommend that you locate the database transaction logs directory on the fastest disk on the system. The installation program, by default, installs the data directory (BPR_DATA) in a location other than that of the home directory (BPR_HOME). The default location for the data directory is /var/CSCObac. We recommend that the data directory be on a different physical disk than the home directory; for example, /var/disk0/CSCObac. Your disk should have a minimum 1 GB free space. The specified directory becomes the top-level directory under which the installation program creates a number of subdirectories; for example, /var/disk0/CSCObac/rdu/db. |
|
7. Enter the shared secret password used by the Cisco BAC components for the RDU in the network. The shared secret password is the same for all Cisco BAC servers in your network. To find a list of Cisco BAC installation parameters, see Installation Worksheet. |
|
8. |
|
Before you install Cisco BAC, review the checklist in Table 2-4.
|
|
---|---|
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. a. /usr/sbin/setenforce 0
b. enforcing to disabled in /etc/selinux/config, and then reboot the machine. By default, the SE Linux feature is set to enforcing. |
|
15. /etc/init.d/iptables stop, and then reboot the machine. ![]() Note |
|
Before you install Cisco BAC, check the following:
On Solaris, for optimum performance and reliability of the Cisco 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 block size cannot be changed after the Unix File System (UFS) is mounted with a value. The value has to be set during Solaris disk partition.
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.
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 block size of the file system, use the df command.
For example:
On Solaris:
# 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.
On Linux:
# df -k .
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 16246460 3248448 12159420 22% /
# /sbin/dumpe2fs /dev/sda2 | grep 'Block size'
Block size: 4096
In this example, the block size is 4096 bytes, which is 4 KB.
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.
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:
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-5 lists the required external inbound ports and their default values.
Table 2-6 lists the external outbound ports and their default values.
Table 2-7 lists the internal ports and their default values.
This section describes the basic configuration information that you need to ensure a successful installation of Cisco Broadband Access Center (Cisco BAC). Table 2-7 is a worksheet that you can use to record the information specific to the installation.