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 work with the Cisco BAC program to install the Cisco BAC components—RDU, DPE, Cisco Network Registrar Extension Points, Cisco Access Registrar Extension Points, and STUN server. You can install the Cisco BAC components from the CLI. Both interfaces are supplied with the product.
You can download the Cisco BAC software from the location below:
http://www.cisco.com/cisco/software/navigator.html?mdfid=273446653
Be sure to install the RDU before installing the DPE. If you choose to install the DPE without installing the RDU, or without an RDU already installed on your system, the DPE fails to function normally.
When the program prompts you to enter a value during installation, note that the values in square brackets are default values. If you press Enter without entering fresh values, the program takes the default value.
During installation, the program generates a definitions file bpr_definitions.sh , which is copied to the target home directory <BPR_HOME> . The definition file stores the values for the:
The bpr_definitions.sh file is updated whenever new components are installed or added.
Note 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.
The following checks must be performed before installing Cisco BAC on a Solaris machine:
The Cisco BAC root user can create users and groups, and assign the appropriate privileges to the users.
A non-root user must be assigned with the following privileges to run Cisco BAC:
Note The Cisco BAC non-root user can run any process associated with socket connection, only if the net_access privilege is assigned to the non-root user. The net_access privilege is available only in Solaris 10 (update 9 and 10) and Solaris 11 platform.
To create users and groups, and assign privileges to the users:
Step 1 Log into the intended Cisco BAC server as root.
Step 2 Create a group in Cisco BAC using the following command:
This creates a group named 1110 baceng.
Step 3 Create a user and assign user to the group using the following command:
Step 4 Assign privileges to the user using the following command:
Step 5 Set password for the user using the following command:
<user_name> — name of the root or non-root user.
Note During installation, it may be necessary to install several Solaris patches on your computer. you can download the required Solaris patch from Sun Microsystems support site. For a list of recommended patches, see Operating System Requirements.
This section explains the procedures that you follow to install one or more Cisco BAC components interactively, from the command line interface.
Note Before you begin any of these procedures, you must complete the initial procedure described in Installation Checklist for Solaris.
You can install the Cisco BAC components from the CLI, as described in:
If you exit the Cisco BAC installation after the database is installed, you must uninstall the <BPR_HOME> and the <BPR_DATA> directories before you install Cisco BAC again. (For information on uninstallation, see Uninstalling Cisco BAC.) Also, if you stop the installation mid-way, the log file is not generated.
If you rerun the installation without uninstalling the specified directories, you cannot change the location of the <BPR_DATA> or the <BPR_DBLOG> directories.
This section describes how to install the RDU. You must install the RDU on a Solaris 10 or Solaris 11 server that meets the requirements described in the section, Operating System Requirements. You should install the RDU on a high-end system that is the most reliable server in your network. We recommend that you configure the RDU server to use a static IP address.
Note Before installation, remove /rdu/db from /var/CSCObac/ directory.
Note If BAC is previously installed and running, stop the bprAgent before install or upgrade:
/etc/init.d/bprAgent stopBAC Process Watchdog has stopped
After running the above command, you should also check the status:
/etc/init.d/bprAgent statusBAC Process Watchdog is not running
Step 1 Log into the intended Cisco BAC server as root.
Step 2 Start the installation program in interactive mode using the following command:
# < install-path> / BAC_3.9_SolarisK9/install_bac.sh
< install-path> — Specifies the complete path to the directory in which the BAC_3.9_Solaris directory has been created.
The installation program verifies that you have installed the required patches to the Solaris operating system. When the verification ends, the Welcome information appears.
Step 3 Press Enter to continue.
The installation program prompts you to provide the name of the user. Ensure that the appropriate user and group are created. For details, see Users and Groups.
Step 4 Enter y to install Cisco BAC for non-root user and group.
Note If you select n, Cisco BAC is installed with the root user and group credentials and in such a case, step 5 and 6 do not appear.
Step 5 Provide the name of the non-root user, and press Enter to continue.
Step 6 Provide the name of the group of the non-root user, and press Enter to continue.
The installation program prompts you to select one or more components.
Step 7 Enter y and press Enter at the RDU prompt.
To skip installing a DPE, CNR extension points, CAR extension points and STUN, enter n and press Enter. You can choose to install these components later.
Step 8 Enter y to confirm the components to be installed and press Enter to continue.
The Home Directory Destination prompt appears.
Step 9 Accept the default directory, /opt/CSCObac , by pressing Enter ; or enter a different directory.
Step 10 Enter y and press Enter to confirm the directory.
The data directory destination prompt appears.
Step 11 Accept the default directory, /var/CSCObac , by pressing Enter ; or enter another directory.
Step 12 Enter y and press Enter to confirm the directory.
Step 13 Enter the database transaction logs destination.
Step 14 Accept the default directory, /var/CSCObac , by pressing Enter ; or enter another directory.
Step 15 Enter y and press Enter to confirm the directory.
Step 16 Enter the listening port for the RDU.
Step 17 Accept the default value, 49187, by pressing Enter ; or enter another port number.
The installation program obtains the IP address of the RDU automatically. You need not enter this value manually.
Step 18 Enter y and press Enter to confirm the listening port number.
Step 19 Enter the shared secret password that you want to use for authentication between the Cisco BAC servers; the default password is secret .
Note You must use the same shared secret password for all RDUs and DPEs in your network.
Step 20 Press Enter to continue the installation.
The program displays the installation parameters that you selected.
Step 21 Enter y and press Enter to confirm the parameters, and install the RDU component.
Step 22 Enter y and press Enter .
The program prompts you to continue with the installation.
Step 23 Enter y and press Enter .
After a successful installation, the following message appears:
Step 24 Launch the Cisco BAC administrator user interface to verify whether the RDU is running.
a. Enter the administrator’s location using the following URL:
machine_name — Identifies the computer on which the RDU is running.
b. Change the Cisco BAC administrator password. To do this:
Enter the default username ( bacadmin ) and password ( changeme ), and click Login .
The Change Password screen appears and prompts you to change the default password.
c. Enter a new password, and click Login .
Optionally, configure the syslog file for alerts on the RDU server.
Note You can set up the syslog file on any Cisco BAC component server.
This section describes how to install the DPE.
Note Before proceeding to install the DPE, ensure that the RDU resides on your system. For details on installing the RDU, see Installing the RDU. RDU can also be installed on a different machine.
Note If BAC is previously installed and running, stop the bprAgent before install or upgrade:
/etc/init.d/bprAgent stopBAC Process Watchdog has stopped
After running the above command, you should also check the status:
/etc/init.d/bprAgent statusBAC Process Watchdog is not running
To install the DPE from the CLI:
Step 1 Log into the intended Cisco BAC server as root.
Step 2 Start the installation program in interactive mode using the following command:
# < install-path> / BAC_3.9_SolarisK9/install_bac.sh
< install-path> — Specifies the complete path to the directory in which the BAC_3.9_Solaris directory has been created.
The installation program verifies that you have installed the required patches to the Solaris operating system. When the verification ends, the Welcome information appears.
Step 3 Press Enter to continue.
The installation program prompts you to provide the name of the user. Ensure that the appropriate user and group are created. For details, see Users and Groups.
Step 4 Enter y to install Cisco BAC for non-root user and group.
Note If you select n, Cisco BAC is installed with the root user and group credentials and in such a case, step 5 and 6 do not appear.
Step 5 Provide the name of the non-root user, and press Enter to continue.
Step 6 Provide the name of the group of the non-root user, and press Enter to continue.
The installation program prompts you to select one or more components.
Step 7 Enter y and press Enter at the DPE prompt.
To skip installing a RDU, CNR extension points, PAR extension points and STUN, enter n and press Enter. You can choose to install these components later.
Step 8 Enter y to confirm the components that you want to install and press Enter to continue.
The Home Directory Destination prompt appears.
Step 9 Accept the default directory, /opt/CSCObac , by pressing Enter ; or enter a different directory.
Step 10 Enter y and press Enter to confirm the directory.
The data directory destination prompt appears.
Step 11 Accept the default directory, /var/CSCObac , by pressing Enter ; or enter another directory.
Step 12 Confirm the directory, press y and Enter .
The program prompts you to enter the RDU information required to install DPE.
Step 13 Enter the IP address (or hostname) and the listening port of the host on which you have installed the RDU.
Step 14 Accept the default information, by pressing Enter; or enter alternative information.
Step 15 Enter the shared secret password that you want to use for authentication between the Cisco BAC servers; the default password is secret.
Step 16 Press Enter to continue.
Note You must use the same shared secret password for all RDUs and DPEs in your network.
The program prompts you to continue with the installation.
Step 17 Enter y to confirm the IP address and the listening port. Press Enter.
After a successful installation, the following message appears:
Step 18 After you install the DPE, ensure that you change the DPE login password and the enable password from the CLI. The default DPE login password and enable password is changeme .
– Access the CLI in the enabled mode, and change the login password using the following command:
password — Identifies the new DPE password.
– Change the DPE enable password using the following command:
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, see the Cisco Broadband Access Center 3.8 DPE CLI Reference .
Step 19 Configure the DPE from the CLI. For more information, see the Cisco Broadband Access Center 3.8 DPE CLI Reference .
Optionally, you can configure the syslog file for alerts on the DPE server.
Note You can set up the syslog file on any Cisco BAC component server.
Install Cisco BAC extensions on all Cisco Network Registrar servers in your Cisco BAC environment. If you are deploying Cisco BAC in a fail-over environment, you must also install the extensions on the failover servers. After you install the extensions, you must configure them.
As a prerequisite to install CNR_EP, you must have installed Cisco Prime Network Registrar 8.1.3 (and above). For Cisco Prime Network Registrar installation information, see the Cisco Network Registrar 8.1 Installation Guide . This section explains how to install, configure, and validate these extensions.
You can download the Cisco BAC software from the below location:
http://www.cisco.com/cisco/software/navigator.html?mdfid=268439531
Note Cisco BAC 3.9 has been tested with Cisco Prime Network Registrar 8.1.3. Starting from Cisco Network Registrar 7.2, fix for co-resident Cisco Network Registrar and Cisco Access Registrar is available.
We recommend that you configure the Cisco Network Registrar server to use a static IP address.
To install the Cisco Prime Network Registrar Extension Point from the CLI:
Step 1 Log into the intended Cisco BAC server as root.
Step 2 Start the installation program in interactive mode using the following command:
# < install-path> / BAC_3.9_SolarisK9/install_bac.sh
< install-path> — Specifies the complete path to the directory in which the BAC_3.9_Solaris directory has been created.
The installation program verifies that you have installed the required patches to the Solaris operating system. When the verification ends, the Welcome information appears.
Step 3 Press Enter to continue.
The installation program prompts you to provide the name of the user. Ensure that the appropriate user and group are created. For details, see Users and Groups.
Step 4 Enter y to install Cisco BAC for non-root user and group.
Note If you select n, Cisco BAC is installed with the root user and group credentials and in such a case, step 5 and 6 do not appear.
Step 5 Provide the name of the non-root user, and press Enter to continue.
Step 6 Provide the name of the group of the non-root user, and press Enter to continue.
The installation program prompts you to select one or more components.
Step 7 Enter y and press Enter at the CNR prompt.
To skip installing a RDU, DPE, PAR extension points and STUN, enter n and press Enter. You can choose to install these components later.
Step 8 Enter y and press Enter.
The program prompts you to confirm the components that you want to install.
Step 9 Enter y and press Enter to continue.
The home directory destination prompt appears.
Step 10 Accept the default directory, /opt/CSCObac , by pressing Enter ; or enter a different directory.
Step 11 Enter y and press Enter to confirm the directory.
The data directory destination prompt appears.
Step 12 Accept the default directory, /var/CSCObac , by pressing Enter ; or enter another directory.
Step 13 Enter y and press Enter to confirm the directory.
The program prompts you to enter the required information on the RDU, to install the extensions.
Step 14 Enter the IP address (or hostname) and the listening port of the host on which you have installed the RDU.
Step 15 Press Enter to accept the default information; or enter alternative information.
You are prompted to enter the name of the extension point provisioning group. The program prompts you to confirm the installation.
Step 16 Press y and Enter to confirm and continue.
Step 17 Enter the shared secret password that you want to use for authentication between the Cisco BAC servers; the default password is secret.
The program prompts you to continue with the installation.
Step 18 Enter y and press Enter.
After a successful installation, the following message appears:
After installing Cisco Network Registrar Extension Point, you should manually update BPR_HOME and BPR_DATA directory before passing input to CNR extension script.
This configuration script enables the CSRC BPR CNR extension points. It is mandatory that this script be run prior to running CSRC BPR. Modify the reference to CSRC_HOME to point to a valid CSRC BPR home directory (ensure to backquote the directory separators).
To enable the Cisco Network Registrar Extension Point.
Step 1 After installing Cisco Network Registrar Extension Point, run this command to enable the Cisco Network Registrar extension points:
In case the default setting are changed, use the below options instead of -s.
Step 2 Restart the Cisco Network Registrar server using the following command:
Note Before you can use the Cisco Network Registrar server, you must configure scopes required for DHCP server.
After you install the Cisco BAC extensions on the Cisco Network Registrar server, you must configure the extensions. The procedure described in this section assumes that:
Step 1 Log into the Cisco Network Registrar server, with root access.
Step 2 At the command line, enter:
Note Before you can use the Cisco Network Registrar server, you must configure client classes, scope-selection tags, policies, and scopes.
To validate the extensions installed on the Cisco Network Registrar server, from the Cisco Network Registrar Command Line Tool ( nrcmd ), run:
Depending on whether you installed a local or regional cluster, the nrcmd tool is located in:
Note The BPR_HOME and BPR_DATA values may be different in your installation.
Also, in the nrcmd program, run:
Install Cisco BAC extensions on all Cisco Prime Access Registrar servers in your Cisco BAC environment. If you are deploying Cisco BAC in a failover environment, you also must install the extensions on the fail-over servers.
After you install extensions, you must configure them. This section explains how to install, configure, and validate these extensions.
As a prerequisite to install Cisco Access Registrar Extension Point, you should have installed Cisco Prime Access Registrar 6.0.1 or later. For PAR Extension Point installation information, see the Installing and Configuring Cisco Access Registrar 6.0.
The default value for tomcat server port (8005) and web UI port (8080) are the same for both Cisco Network Registrar and Cisco Prime Access Registrar servers. Hence, you need to change either the tomcat server port or web UI port before installing Cisco Prime Access Registrar Extension Point.
The tomcat server port of the Cisco Prime Access Registrar server and web UI port can be changed in /opt/CSCOar/apache-tomcat-5.5.27/conf/server.xml .
The tomcat server port of the Cisco Prime Network Registrar server and web UI port can be changed in /opt/nwreg2/local/tomcat/conf/server.xml .
You may choose to install Cisco Prime Network Registrar or Cisco Prime Access Registrar, first. However, we recommend that you install Cisco Prime Access Registrar before Cisco Network Registrar. Cisco Network Registrar allows you to change the Web UI (tomcat) port as part of the installation.
Cisco Prime Access Registrar 6.0.1 requires either JRE 1.5.x or 1.6.x, but CAR_EP needs JRE 1.6.x, so use JRE 1.6.x for Cisco Access Registrar 5.0.0.6.
We recommend that you configure the Cisco Prime Access Registrar server to use a static IP address.
To install the Cisco Access Registrar Extension Point from the CLI:
Step 1 Log into the intended Cisco BAC server as root.
Step 2 Start the installation program in interactive mode using the following command:
# < install-path> / BAC_3.9_SolarisK9/install_bac.sh
< install-path> — Specifies the complete path to the directory in which the BAC_3.9_Solaris directory has been created.
The installation program verifies that you have installed the required patches to the Solaris operating system. When the verification ends, the Welcome information appears.
Step 3 Press Enter to continue.
The installation program prompts you to provide the name of the user. Ensure that the appropriate user and group are created. For details, see Users and Groups.
Step 4 Enter y to install Cisco BAC for non-root user and group.
Note If you select n, Cisco BAC is installed with the root user and group credentials and in such a case, step 5 and 6 do not appear.
Step 5 Provide the name of the non-root user, and press Enter to continue.
Step 6 Provide the name of the group of the non-root user, and press Enter to continue.
The installation program prompts you to select one or more components.
Step 7 Enter y and press Enter at the PAR Extension Point prompt.
To skip installing the RDU, DPE, CNR extension points and STUN, enter n and press Enter. You can choose to install these components later.
Step 8 Enter y and press Enter.
The program prompts you to confirm the components that you want to install.
Step 9 Enter y and press Enter to continue.
The Home Directory Destination prompt appears.
Step 10 Accept the default directory, /opt/CSCObac , by pressing Enter ; or enter a different directory.
Step 11 Enter y and press Enter to confirm the directory.
The data directory destination prompt appears.
Step 12 Accept the default directory, /var/CSCObac , by pressing Enter ; or enter another directory.
Step 13 Enter y and press Enter to confirm the directory.
The program prompts you to enter information on the RDU required to install the extensions.
Step 14 Enter the IP address (or hostname) and the listening port of the host on which you have installed the RDU.
Step 15 Accept the default information, by pressing Enter ; or enter alternative information.
The program prompts you to confirm the installation.
Step 16 Enter y and press Enter to confirm and continue.
The program prompts you to continue with the installation.
Step 17 Enter y and press Enter.
After a successful installation, the following message appears:
To set up the Cisco Prime Access Registrar Extension Point, after installing Cisco Prime Access Registrar Extension Point, run the below script to create and setup extension points in Cisco Prime Access Registrar:
The DPE Auth Service hosts address and port should be manually provisioned. By default, the host address is localhost and auth service port is 7551. To change the default properties, run the following script with appropriate options:
Cisco BAC displays the following list of options:
Install the STUN on a server that meets the requirements described in Cisco BAC Components.
Step 1 Log into the intended Cisco BAC server as root.
Step 2 Start the installation program in interactive mode using the following command:
# < install-path> / BAC_3.9_SolarisK9/install_bac.sh
< install-path> — Specifies the complete path to the directory in which the BAC_3.9_Solaris directory has been created.
The installation program verifies that you have installed the required patches to the Solaris operating system. When the verification ends, the welcome information appears.
Step 3 Press Enter to continue.
The installation program prompts you to provide the name of the user. Ensure that the appropriate user and group are created. For details, see Users and Groups.
Step 4 Enter y to install Cisco BAC for non-root user and group.
Note If you select n, Cisco BAC is installed with the root user and group credentials and in such a case, step 5 and 6 do not appear.
Step 5 Provide the name of the non-root user, and press Enter to continue.
Step 6 Provide the name of the group of the non-root user, and press Enter to continue.
The installation program prompts you to select one or more components.
Step 7 Enter y and press Enter at the STUN server prompt.
To skip installing the RDU, DPE, Cisco Network Registrar extension points and the Cisco Prime Access Registrar extension points, enter n and press Enter. You can choose to install these components later.
Step 8 Enter y and press Enter.
The program prompts you to confirm the components that you want to install.
Step 9 Enter y and press Enter to continue.
The Home Directory Destination prompt appears.
Step 10 Accept the default directory, /opt/CSCObac , by pressing Enter ; or enter another directory.
Step 11 Confirm the directory location. To do this, enter y and press Enter .
The data directory prompt appears.
Step 12 Accept the default directory, /var/CSCObac , by pressing Enter ; or enter another directory.
Step 13 Confirm the directory location.To do this, enter y and press Enter .
The program prompts you to enter information on the RDU required to install the extensions.
Step 14 Enter the IP address (or hostname) and the listening port of the host on which you have installed the RDU.
Step 15 Accept the default information, by pressing Enter; or enter alternative information.
Step 16 Confirm the information. To do this, enter y and press Enter .
The program prompts you to enter the STUN HTTP listening port.
Step 17 Accept the default information, by pressing Enter; or enter alternative information.
The program prompts you to enter the STUN UDP listening port.
Step 18 Accept the default information, by pressing Enter; or enter alternative information.
The program prompts you to enter the STUN HTTP username.
Step 19 Accept the default information, by pressing Enter; or enter alternative information.
The program prompts you to enter the STUN HTTP password.
Step 20 Accept the default information, by pressing Enter; or enter alternative information.
The program prompts you to enter the password to be used for UDP CR authentication.
Step 21 Accept the default information, by pressing Enter; or enter alternative information
The program prompts you to enter the shared secret password. Enter the shared secret password that you want to use for authentication between the Cisco BAC servers.
Step 22 Re-enter the password for confirmation, and press Enter.
The installation proceeds, and displays the following message after successful installation:
This section explains the procedures that you follow to install one or more Cisco BAC components from the command line in noninteractive mode.
In order to install Cisco BAC in noninteractive mode, you must first generate a response file, in which you store values for installing a component. You can then use the response file as input while installing that component.
For subsequent installations of the same component, you only need to use a single command, which removes all installation prompts and installs the component using the values contained in the response file.
To install Cisco BAC in noninteractive mode:
Step 1 Generate a response file using the following command:
< install-path> — Specifies the complete path to the directory in which the BAC_3.9_Solaris directory has been created.
Running this command does not install Cisco BAC on your system; it only generates the response file in which you store values for installation.
Note that there can only be one response file. As a result, you can use the response file only to install the component for which you generate the response file. If you want to install another component, you must generate a response file for that component and install that component, using the response file generated for it.
For example, if you generate a response file to install the DPE, and, subsequently, you want to install Cisco Network Registrar extensions, you must generate a response file separately to install Cisco Network Registrar extensions. You cannot use the response file that you generated to install the DPE, to install Cisco Network Registrar extensions.
Step 2 After you generate the response file, start the installation program in non-interactive mode using the following command:
# install_bac.sh -r responsefile
Note Before you begin any of the procedures described in this section, complete the initial installation procedure described in Installation Checklist for Solaris.
The following sections provide instructions on installing components in noninteractive mode:
Install the RDU on a Solaris 10 or Solaris 11 server that meets the requirements described in Operating System Requirements. You should install the RDU on a high-end system that is the most reliable server in your network.
Note We recommend that you configure the RDU server to use a static IP address.
To install the RDU, complete the initial installation described in Installation Checklist for Solaris.
To generate a response file for RDU installation:
< install-path> — Specifies the complete path to the directory in which the BAC_3.9_Solaris directory has been created.
The response file is created in the directory in which you run the pkgask -r command.
If you want the response file to be generated in a specific location, enter:# pkgask -r response-file-path -d CSCObac.pkg
response-file-path — Specifies the path to the directory in which you want the response file to be generated; for example, /tmp/response . You can also give the response file any name; for example, outputFile .
The installation program verifies that you have installed the required patches to the Solaris operating system. When the verification ends, the Welcome information appears.
Step 2 Press Enter to continue.
The installation program prompts you to provide the name of the user. Ensure that the appropriate user and group are created. For details, see Users and Groups.
Step 3 Enter y to install Cisco BAC for non-root user and group.
Note If you select n, Cisco BAC is installed with the root user and group credentials and in such a case, step 4 and 5 do not appear.
Step 4 Provide the name of the non-root user, and press Enter to continue.
Step 5 Provide the name of the group of the non-root user, and press Enter to continue.
The installation program prompts you to select one or more components.
Step 6 Enter y and press Enter at the RDU prompt.
To skip installing a DPE, Cisco Network Registrar extension points, Cisco Prime Access Registrar extension points and STUN server, enter n and press Enter . You can choose to install these components later.
The program prompts you to confirm the components that you want to install.
Step 7 Enter y and press Enter to continue.
Step 8 Accept the default directory, /opt/CSCObac , by pressing Enter ; or enter a different directory.
A confirmation prompt appears.
Step 9 Enter y and press Enter to confirm the home directory location
The program prompts you to enter the data directory location.
Step 10 Accept the default directory, /var/CSCObac , by pressing Enter ; or enter a different directory.
Step 11 Enter y and press Enter to confirm the data directory location,
The database log directory prompt appears.
Step 12 Accept the default directory, /var/CSCObac , by pressing Enter ; or enter another directory.
Step 13 Enter y and press Enter to continue to confirm the directory.
The program prompts you to enter the information related to the RDU listening port.
The listening port is the port number that the RDU uses to communicate with other Cisco BAC components, such as DPEs and Cisco Network Registrar extension points.
Step 14 Accept the default port number, 49187, by pressing Enter ; or enter another port number.
Step 15 Confirm the listening port number; enter y and press Enter to continue.
The program prompts you to enter the shared secret password.
Step 16 Enter the shared secret password that you want to use for authentication among Cisco BAC servers, and confirm the password.
Note You must use the same shared secret password for the RDU, all DPEs, and Cisco Network Registrar extension points in your network.
Step 17 Press Enter to continue.
The program displays the parameters you have selected to install the RDU.
Step 18 Enter y and press Enter to confirm the parameters.
A message appears indicating that a response file has been created.
Step 19 After you generate the response file, start the installation program in noninteractive mode using the following command:
# install_bac.sh -r responsefile
Once you run the above command, the program installs the RDU. After successful installation, a message appears.
Install the DPE on a Solaris 10 or Solaris 11 server that meets the requirements described in Operating System Requirements.
We recommend that you configure the DPE server to use a static IP address.
During DPE installation, if the program detects a TFTP server or a ToD server running on the same server as the DPE, the installation displays an error message and exits. To terminate the TFTP or ToD server, perform the steps that the error message lists.
To install the DPE, complete the initial steps described in Installation Checklist for Solaris.
To generate a response file for DPE installation:
< install-path> — Specifies the complete path to the directory in which the BAC_39_Solaris directory has been created.
The response file is created in the directory in which you run the pkgask -r command. If you want the response file to be generated in a specific location, enter:
# pkgask -r response-file-path -d CSCObac.pkg
response-file-path — Specifies the path to the directory in which you want the response file to be generated; for example, /tmp/response . You can also give the response file any name; for example, outputFile .
The installation program verifies that you have installed the required patches to the Solaris operating system. When the verification ends, the Welcome information appears.
Step 2 Press Enter to continue.
The installation program prompts you to provide the name of the user. Ensure that the appropriate user and group are created. For details, see Users and Groups.
Step 3 Enter y to install Cisco BAC for non-root user and group.
Note If you select n, Cisco BAC is installed with the root user and group credentials and in such a case, step 4 and 5 do not appear.
Step 4 Provide the name of the non-root user, and press Enter to continue.
Step 5 Provide the name of the group of the non-root user, and press Enter to continue.
The installation program prompts you to select one or more components.
Step 6 Press Enter to continue.
The installation program prompts you to select one or more components.
Step 7 Enter y and press Enter at the DPE prompt.
To skip installing the RDU, Cisco Network Registrar extension points, Cisco Access Registrar extension points and the STUN server, enter n and press Enter .
The program prompts you to confirm the components that you want to install.
Step 8 Enter y and press Enter to continue.
The home directory prompt appears.
Step 9 Accept the default directory, /opt/CSCObac, by pressing Enter ; or enter another directory.
Step 10 Confirm the directory location; enter y and press Enter .
The data directory prompt appears.
Step 11 Accept the default directory, /var/CSCObac, by pressing Enter ; or enter another directory.
Step 12 Confirm the directory location; enter y and press Enter .
The program prompts you to enter the information related to the RDU, specifically the IP address and the listening port.
You must enter a value for the IP address and listening port. The listening port is the port number that the RDU uses to communicate with other Cisco BAC components, such as DPEs and Cisco Network Registrar extension points.
Step 13 Accept the default port number, 49187, by pressing Enter ; or enter another port number.
Step 14 Confirm the listening port number; enter y and press Enter to continue.
The program prompts you to enter the shared secret password.
Step 15 Enter the shared secret password that you want to use for authentication between the Cisco BAC servers. You must use the same shared secret password for the RDU, all DPEs, Cisco Network Registrar extension points and in your network.
Step 16 Re-enter the password for confirmation, and press Enter .
A message appears indicating that a response file has been created.
Step 17 After you generate the response file, start the installation program in noninteractive mode using the following command:
# install_bac.sh -r responsefile
After you run the above command, the program installs the DPE. After successful installation, a message appears.
Install Cisco BAC extensions on all Cisco Network Registrar servers in your Cisco BAC environment. If you are deploying Cisco BAC in a failover environment, you also must install the extensions on the failover servers.
After you install extensions, you must configure them. This section explains how to install, configure, and validate these extensions.
Note We recommend that you configure the Cisco Network Registrar server to use a static IP address.
Before you install Cisco Network Registrar extensions, complete the initial installation described in Installation Checklist for Solaris. Also, ensure that Cisco Network Registrar is running.
To generate a response file to install Cisco Network Registrar extensions:
< install-path> — Specifies the complete path to the directory in which the BAC_3.8_Solaris directory has been created.
The response file is created in the directory in which you run the pkgask -r command. If you want the response file to be generated in a specific location, enter:
# pkgask -r response-file-path -d CSCObac.pkg
response-file-path — Specifies the path to the directory in which you want the response file to be generated; for example, /tmp/response . You can also give the response file any name; for example, outputFile .
The installation program verifies that you have installed the required patches to the Solaris operating system. When the verification ends, the Welcome information appears.
Step 2 Press Enter to continue.
The installation program prompts you to provide the name of the user. Ensure that the appropriate user and group are created. For details, see Users and Groups.
Step 3 Enter y to install Cisco BAC for non-root user and group.
Note If you select n, Cisco BAC is installed with the root user and group credentials and in such a case, step 4 and 5 do not appear.
Step 4 Provide the name of the non-root user, and press Enter to continue.
Step 5 Provide the name of the group of the non-root user, and press Enter to continue.
The installation program prompts you to select one or more components.
Step 6 Enter y and press Enter at the Cisco Network Registrar Extension Points prompt.
To skip installing the RDU, DPE, Cisco Access Registrar extension points and the STUN server, enter n and press Enter .
Note The installation program validates your Cisco Network Registrar installation. You must install Cisco Network Registrar 7.2 (and above) on your server. If the required version is not installed, the installation process terminates. You must upgrade to at least Cisco Network Registrar 7.2, before proceeding.
The program prompts you to confirm the components that you want to install.
Step 7 Enter y and press Enter to continue.
The home directory prompt appears.
Step 8 Accept the default directory, /opt/CSCObac , by pressing Enter ; or enter another directory.
The program then prompts you to confirm the directory.
Step 9 Press y and Enter to continue.
The data directory prompt appears.
Step 10 Accept the default directory, /var/CSCObac , by pressing Enter ; or enter another directory.
Note The installation program, by default, installs the data directory <BPR_DATA> on a different directory than the home directory <BPR_HOME>. We recommend that the data directory be on a different physical disk than the home directory; for example, /var/disk0/CSCObac.
Step 11 Enter y and press Enter to confirm the directory,
The program prompts you to enter information on the RDU required to install the extensions.
Step 12 Enter the IP address (or hostname) and the listening port of the host on which you have installed the RDU.
Step 13 Accept the default information, by pressing Enter ; or enter alternative information.
You are prompted to enter the name of the extension point provisioning group.
Step 14 Enter the name of the Cisco Network Registrar extension point group.
Step 15 Enter y and press Enter .
Step 16 Enter the shared secret password that you want to use for authentication among Cisco BAC servers. You must use the same shared secret password for all Cisco BAC servers on your network.
Step 17 Press Enter to continue,
A message appears indicating that a response file has been created.
Step 18 After you generate the response file, start the installation program in noninteractive mode using the following command:
After you run the above command, the program installs the DPE. After successful installation, a message appears.
After you install the extensions, you must configure and validate them. For details, see Configuring Extensions, and Validating Extensions.
Install the Cisco Prime Access Registrar Extensions on a Solaris 10 server that meets the requirements described in Operating System Requirements.
To install the Cisco Prime Access Registrar Extensions, complete the initial steps described in Installation Checklist for Solaris.
To generate a response file for Cisco Prime Access Registrar Extensions installation:
< install-path> — Specifies the complete path to the directory in which the BAC_3.8_Solaris directory has been created.
The response file is created in the directory in which you run the pkgask -r command. If you want the response file to be generated in a specific location, enter:
# pkgask -r response-file-path -d CSCObac.pkg
response-file-path — Specifies the path to the directory in which you want the response file to be generated; for example, /tmp/response . You can also give the response file any name; for example, outputFile .
The installation program verifies that you have installed the required patches to the Solaris operating system. When the verification ends, the Welcome information appears.
Step 2 Press Enter to continue.
The installation program prompts you to provide the name of the user. Ensure that the appropriate user and group are created. For details, see Users and Groups.
Step 3 Enter y to install Cisco BAC for non-root user and group.
Note If you select n, Cisco BAC is installed with the root user and group credentials and in such a case, step 4 and 5 do not appear.
Step 4 Provide the name of the non-root user, and press Enter to continue.
Step 5 Provide the name of the group of the non-root user, and press Enter to continue.
The installation program prompts you to select one or more components.
Step 6 Press Enter to continue.
The installation program prompts you to select one or more components.
Step 7 Enter y and press Enter at the CAR prompt.
To skip installing the RDU, DPE, Cisco Network Registrar extension points, and the STUN server, enter n and press Enter .
The program prompts you to confirm the components that you want to install.
Step 8 Enter y and press Enter to continue.
The home directory prompt appears.
Step 9 Accept the default directory, /opt/CSCObac, by pressing Enter ; or enter another directory.
Step 10 Confirm the directory location; enter y and press Enter .
The data directory prompt appears.
Step 11 Accept the default directory, /var/CSCObac, by pressing Enter ; or enter another directory.
Step 12 Confirm the directory location; enter y and press Enter .
The program prompts you to enter the information related to the RDU, specifically the IP address and the listening port.
You must enter a value for the IP address and listening port. The listening port is the port number that the RDU uses to communicate with other Cisco BAC components, such as DPEs and Cisco Network Registrar extension points.
Step 13 Accept the default port number, 49187, by pressing Enter ; or enter another port number.
Step 14 Confirm the listening port number; enter y and press Enter to continue.
Step 15 After you generate the response file, start the installation program in noninteractive mode using the following command:
# install_bac.sh -r responsefile
After you run the above command, the program installs the Cisco Prime Access Registrar. After successful installation, a message appears.
Install STUN on a Solaris 10 server that meets the requirements described in Operating System Requirements.
To install the STUN server, complete the initial steps described in Installation Checklist for Solaris.
To generate a response file for STUN server installation:
< install-path> — Specifies the complete path to the directory in which the BAC_3.8_Solaris directory has been created.
The response file is created in the directory in which you run the pkgask -r command. If you want the response file to be generated in a specific location, enter:
# pkgask -r response-file-path -d CSCObac.pkg
response-file-path — Specifies the path to the directory in which you want the response file to be generated; for example, /tmp/response . You can also give the response file any name; for example, outputFile .
The installation program verifies that you have installed the required patches to the Solaris operating system. When the verification ends, the Welcome information appears.
The installation program prompts you to provide the name of the user. Ensure that the appropriate user and group are created. For details, see Users and Groups.
Step 2 Enter y to install Cisco BAC for non-root user and group.
Note If you select n, Cisco BAC is installed with the root user and group credentials and in such a case, step 3 and 4 do not appear.
Step 3 Provide the name of the non-root user, and press Enter to continue.
Step 4 Provide the name of the group of the non-root user, and press Enter to continue.
The installation program prompts you to select one or more components.
Step 5 Enter y and press Enter at the STUN prompt.
To skip installing the RDU, DPE, Cisco Network Registrar extension points, and the Cisco Prime Access Registrar extension points, enter n and press Enter .
The program prompts you to confirm the components that you want to install.
Step 6 Enter y and press Enter to continue.
The home directory prompt appears.
Step 7 Accept the default directory, /opt/CSCObac, by pressing Enter ; or enter another directory.
Step 8 Confirm the directory location; enter y and press Enter .
The data directory prompt appears.
Step 9 Accept the default directory, /var/CSCObac, by pressing Enter ; or enter another directory.
Step 10 Confirm the directory location; enter y and press Enter .
The program prompts you to enter the STUN HTTP listening port.
Step 11 Accept the default information, by pressing Enter; or enter alternative information.
The program prompts you to enter the STUN UDP listening port.
Step 12 Accept the default information, by pressing Enter; or enter alternative information.
The program prompts you to enter the STUN HTTP username.
Step 13 Accept the default information, by pressing Enter; or enter alternative information.
The program prompts you to enter the STUN HTTP password.
Step 14 Accept the default information, by pressing Enter; or enter alternative information.A message appears indicating that a response file has been created.
Step 15 After you generate the response file, start the installation program in noninteractive mode using the following command:
# install_bac.sh -r responsefile
After you run the above command, the program installs the STUN server. After successful installation, a message appears.
This section describes the procedures to reinstall Cisco Broadband Access Center (Cisco BAC). Reinstallation in Cisco BAC is enabled only for the purpose of restoring an installation that is corrupted.
This release does not support reinstalling the Regional Distribution Unit (RDU), the Device Provisioning Engine (DPE) and Cisco Network Registrar that are already installed on your system. If you need to reinstall them, first uninstall the RDU and DPE, and then reinstall them.
To reinstall Cisco BAC from the CLI:
Step 1 Back up your database using the following command:
<BPR_HOME> — Specifies the home directory. The default directory is /opt/CSCObac.
To use this command, you must provide the target directory to place the backup files. This directory should be on a disk or partition that has available disk space equivalent to 120% of the current database file size.
For more information on Database backup, see the Cisco Broadband Access Center 3.9 Administrator Guide .
Step 2 Uninstall Cisco BAC from your system. For information on how to unistall Cisco BAC, see Uninstalling Cisco BAC for Solaris, and Uninstalling Cisco BAC for Linux.
Step 3 Install Cisco BACon your system. For information on how to install Cisco BAC, see Preinstallation Checks or Installing Components in Noninteractive Mode for Solaris, and Installing Cisco BAC for Linux.
Step 4 After you install Cisco BAC 3.9 on your system, restore the database from the backup, and copy the recovered database to the database location of the RDU. For information on how to restore the database, see the Cisco Broadband Access Center 3.9 Administrator Guide .
This section describes how you can add one component of Cisco BAC to a system on which other components have already been installed. This situation arises mainly in a deployment similar to a lab installation, where, for the purposes of testing, more than one component is installed on a single machine. The definitions file ( bpr_definitions.sh ) is updated whenever you add new components.
Note Before you add components, ensure that all the components belong to the Cisco BAC 3.9 version.
When the installation program detects the presence of one component on your system, it does not allow you to add that particular component. It prompts you to add or install only other components.
For example, if you have installed a DPE on a system and then rerun the installation program, the program does not allow you to install the DPE.
The procedures for adding a component are similar to those for a fresh installation, except that the program does not allow you to add the component that you have already installed.
You cannot reinstall a component that you have already installed. If you must perform a reinstallation, first uninstall that component, and then re-install it.
Note Before you add the DPE, ensure that the RDU and the DPE belong to the BAC 3.9 version.
When the installation program detects the presence of an RDU on your system, it does not allow you to re-add the RDU. It prompts you to add or install only the DPE.
Note To ensure a smooth installation, we recommend that you install the RDU before you install the DPE.
Unlike the procedure in a fresh installation, while adding a DPE, you cannot install the home <BPR_HOME> and data <BPR_DATA> directories in a location of your choice. The directories are installed only in the location where you choose to install the RDU directories.
Note Adding the other components from the CLI is similar to Adding a DPE from the CLI.
Step 1 Log into the computer on which you intend to install Cisco BAC components, with root access. Use an X-Window client to log in.
Step 2 At the Solaris system prompt, change directory to your CD-ROM drive or other installation media. The installation program, pkgadd, is at the root of this drive.
Step 3 Start the installation program using the following command:
install-path>
/BAC_3.8_Solarisk9/install_bac.sh
The installation program verifies that you have installed the correct patches to the Solaris operating system. When the verification is complete, the program displays the Welcome screen.
The installation program prompts you to provide the name of the user. Ensure that the appropriate user and group are created. For details, see Users and Groups.
Step 4 Enter y to install Cisco BAC for non-root user and group.
Note If you select n, Cisco BAC is installed with the root user and group credentials and in such a case, step 5 and 6 do not appear.
Step 5 Provide the name of the non-root user, and press Enter to continue.
Step 6 Provide the name of the group of the non-root user, and press Enter to continue.
The installation program prompts you to select one or more components.
Step 7 Enter y and press Enter at the DPE prompt.
The installation program prompts you to add only the DPE.
Step 8 Confirm the components that you want to install; enter y and press Enter to continue.
The program displays a message that it is starting individual component validation.
Step 9 Press Enter to continue.
When validation is complete, the program prompts you to enter the IP address and the listening port of the RDU.
Step 10 Press Enter to accept the hostname of the RDU.
Note The installation program obtains the IP address of the RDU automatically. You do not need to enter this value.
Step 11 Accept the default port number, 49187, by pressing Enter ; or enter another port number.
Step 12 Confirm the IP address and the listening port number; enter y and press Enter .
The program prompts you to enter the shared secret password.
Step 13 Enter the password that you want to use for authentication between the Cisco BAC servers, and press Enter .
Note You must use the same shared secret password for all RDUs and DPEs in your network. The default password is secret.
Step 14 Press Enter to continue.
The installation parameters that you selected, appear.
Step 15 Enter y and press Enter to confirm the parameters, and add the DPE.
The Installation Summary appears when the installation is complete.
Step 16 Press Enter to exit the installation program.
The Installation Summary appears when the installation is complete.
Step 17 Press Enter to exit the installation program.
Table 3-1 provides the list of DPE properties used in Cisco BAC 3.9.
Note Unless the property values are changed either in DPE properties or via DPE CLI, the default values will be used.
See the Cisco Broadband Access Center 3.9 Administrator Guide for the Cisco Access Registrar property file. The property file is explained in the section Using the changeARProperties.sh Tool.
See the Cisco Broadband Access Center 3.9 Administrator Guide for the Cisco Network Registrar property file. The property file is explained in the section Using the changeNRProperties.sh Tool.
Table 3-2 provides the list of STUN properties used in Cisco BAC 3.9.
Note This topic is applicable to Cisco BAC installation on both Solaris and Linux.
Cisco BAC can be integrated with Cisco Prime Central to receive EPM MIB OIDs traps in the Prime Central alarm browser.
Each RDU and DPE component is registered as individual domain manager with Prime Central application.
To integrate BAC with the Prime Central alarm browser, use the primeIntegration.sh script that is available under <BAC_HOME>/prime_integrator directory, as part of RDU/DPE installation. You must invoke this script to integrate BAC with Prime Central and to register Prime Central as one of the trap listener.
Note Before integrating with Cisco BAC, ensure that Prime Central is successfully installed in the network, and that you know the credentials of the Prime Central server and the Fault Mangement server, like IP address and used ports.
It is recommended to install both RDU and DPE components, and then run the primeIntegration.sh script in the DPE.
If you install RDU and run the primeIntegration.sh script in the RDU before installing the DPE component, you cannot run this script in the DPE later to register the Prime Central SNMP Trap Host for DPE. In this case, after DPE component installation, you must manually register the Prime Central Fault Management server as one of the trap listener, using the snmpAgentCfgUtil.sh script in the DPE.
This manual registration also applies to subsequent DPE installations, as the registration of BAC as an application with Prime Central happens at the first instance of running primeIntegration.sh .
To integrate Cisco BAC with Prime Central, from the RDU/DPE CLI:
Step 1 Change directory to <BAC_HOME> /prime_integrator.
Step 2 Run primeIntegration.sh .
[root@bac-sol-vm188 prime_integrator]# ./primeIntegration.sh
Step 3 Enter values for the following credentials at the prompt:
The default value is the same IP address as the installed BAC RDU/DPE.
The default value is the same IP address as the Prime Central server IP address. Instead, if the Fault Management server is installed in a different machine, you can mention its IP address here.
After successful execution of this script, Cisco BAC is registered with Prime Central as a domain manager instance, and Prime Central is also configured as one of the trap listeners in DPE to receive traps.
This section describes how to upgrade from an earlier version of Cisco BAC to Cisco BAC 3.9.
Before upgrading to Cisco BAC 3.9, ensure that you obtain the license file that this release supports. After the upgrade is complete, the installation program deletes all existing license keys. You must then install the license file that Cisco BAC 3.9 supports, using the administrator user interface.
For details on obtaining and installing the license file, see the Cisco Broadband Access Center 3.8 Release Notes .
The Cisco BAC upgrade procedure requires that you upgrade the components as recommended in the following sections. Performing the upgrade in any other sequence results in error during provisioning.
1. Backing Up the RDU Database
Before upgrading Cisco BAC components, ensure that you back up the RDU database files. Throttling limits the I/O bandwidth used by the DB with backup utility. The Throttle option specifies the rate at which the backup tool reads the files it copies. While using this option, if the reading rate is high, the tool goes into Sleep mode till the rate comes down.
We recommend that you use the Throttle option always since it is not an I/O intensive operation.
# ./ backupDb.sh -nosubdir -throttle 500/var/backup
/var/backup — Identifies the database backup directory.
Note It is always recommended to take backup of RDU database when the bprAgent is not running. Otherwise, the backed-up database may not have the latest information, and this may lead to some incorrect data values in the DB statistics. For example, the number of CWMP devices may not appear correct.
Step 2 Back up the following files. Backup is required only if you have customized these files.
– Other xml files and dtd files
Step 3 Back up the existing RDU database, using the backupDb.sh tool. For details, see the Cisco Broadband Access Center 3.9 Administrator Guide .
Ensure that the database has been backed up by checking the history.log file, which resides in the BPR_DATA directory.
Step 4 Recover the database that you have backed up to a consistent state, using the recoverDb.sh tool. For details, see the Cisco Broadband Access Center 3.9 Administrator Guide .
where /disk1/backup identifies the location of the database backup files.
Step 5 After recovering the database, verify it by running the command:
Note In case of any error while verifying the database, contact Cisco Support.
For additional information on using the backupDb.sh tool, see the Cisco Broadband Access Center 3.9 Administrator Guide.
The Cisco BAC 3.9 RDU with a migrated database can operate with earlier versions of Solaris DPEs and Cisco Network Registrar Extensions servers for gradual online migration.
Migration preserves the device record revision numbers used in DPE synchronization. As a result, DPE repopulation is not triggered after the RDU database upgrade. This ensures the least disruption until you upgrade the specific DPE.
We recommend that you perform a dry run of the migration process on a staging (nonproduction) system, instead of on a live system, during RDU downtime. These steps may not be practical during a live migration, because in the case of a large database, verification can take an extended length of time.
Step 1 Before migration, run the verifyDb.sh tool on a backup snapshot.
To verify the database before migration, use the verifyDb.sh tool from the Cisco BAC installation corresponding to the version of the database. You cannot verify a nonmigrated database with the Cisco BAC 3.9 version of verifyDb.sh.
This pathname is specific to the Cisco BAC installation version that was installed before migrating to Cisco BAC 3.9.
Step 2 After migration and upgrade to Cisco BAC 3.9, run the Cisco BAC 3.9 versions of verifyDb.sh tool on the migrated database.
If any error occurs during the process, the log file, bpr-verify-db-log.xml, is generated in the path <BPR_HOME> /rdu/internal/db/bin, which contains the details of the error.
For details about the verifyDb.sh tool, see the Cisco Broadband Access Center 3.9 Administrator Guide .
This release of Cisco BAC consists of a migration tool that facilitates DB portability between platforms. You can also use this migration tool to migrate between different platforms. This tool contains JRE 1.6.0_27, Berkeley db 5.1.25 libraries and Cisco BAC 3.9 bpr.jar.
In Cisco BAC 3.9, Solaris to Solaris RDU database migration can be done using the Migration Tool (BAC_39_MigrationTool.tar.gz).
Before you start with the migration task, ensure you perform the steps explained in Using the RDU Migration Tool.
In the following section, steps 1 to 10 have to be done on the Solaris server which has the earlier version of Cisco BAC and steps 11 to 13 need to be done on the Linux server where Cisco BAC 3.9 needs to be installed.
To perform a database migration:
Step 1 Copy the BAC_39_MigrationTool.tar.gz from Cisco.com location.
Step 2 Go to the directory BAC_39_MigrationTool /migration.
Step 3 Run migrationTool.sh > help and follow the help instructions.
Step 4 After the migration is complete, copy the whole database directory and backed-up files to the Cisco BAC 3.9 setup machine.
Step 5 Restore the following files.
a. Files under <BAC_HOME>/rdu/conf/ .
– Other xml files and dtd file
b. MIB files under <BAC_HOME>/rdu/mibs /
c. *.xml files under <BAC_HOME>/snmp/conf/
Note While restoring the files, make sure that you merge the changes without overwriting the newly installed files.
Before upgrading the RDU, we recommend that you archive your files in the <BPR_HOME>/rdu/conf directory.
Note If BAC is previously installed and running, stop the bprAgent before install or upgrade:
/etc/init.d/bprAgent stop
After running the above command, you should also check the status:
/etc/init.d/bprAgent statusBAC Process Watchdog is not running
Upgrading of RDU is possible for the following Cisco BAC versions and platforms:
Step 1 Back up the RDU database. For details, see Backing Up the RDU Database
Step 2 Copy the backed-up database to a safe location.
Step 3 Migrate the RDU database. For details, see Migrating the RDU Database
Step 4 If the operating system (OS) on which the existing Cisco BAC version runs does not meet the requirements for the Cisco BAC 3.9 release, upgrade the OS to Solaris 10 or Solaris 11.
When upgrading the installation program prompts you to enter locations for the:
Note The home directory will be replaced if installation is done on the existing Cisco BAC BPR_HOME directory.
Note The DATA directory should be removed manually before the upgrade. Ensure you take the backup of the old database before you remove the DATA directory.
It then upgrades the necessary libraries and property files but leaves your RDU database intact.
Step 5 Install the Cisco BAC 3.9 version using the following command:
# < install-path>
/BAC_3.9_SolarisK9/install_bac.sh
a. When prompted, press Enter to continue, the upgrade message is displayed.
b. Enter y to start the upgrade process.
d. Enter y to install Cisco BAC for non-root user and group.
Note If you select n, Cisco BAC is installed with the root user and group credentials and in such a case, steps e and f do not appear.
e. Provide the name of the non-root user, and press Enter to continue.
f. Provide the name of the group of the non-root user, and press Enter to continue.
Note If you wish to specify non-root username and group name you must manually change the root folder permissions of the database using chown command.
A verification message appears if the upgrade is successful and that you can restore the DB and start the bprAgent.
g. Delete the following DB and log before you perform the restore operation:
h. Run restoreDB.sh on the newly copied directory.
i. Verify whether the version information indicates Cisco BAC release 3.9 using the following command:
Step 6 Manually restart the RDU process to finish the upgrade process using the following command:
# /etc/init.d/bprAgent start rdu
Note While upgrading from earlier version of Cisco BAC, the program displays warning messages for the properties that are already present in the DB. For example, "A custom property with the name [/server/rdu/allow-unknown-cpe] already exists in the system." Such warning messages can be ignored.
In Cisco BAC 3.9, Solaris to Linux RDU Database migration can be done using the Migration Tool (BAC_39_MigrationTool.tar.gz).
Note Before you start with the migration task, ensure you carry out the steps explained in Using the RDU Migration Tool.
Note In the following section, steps 1 to 10 have to be done on the Solaris server which would be having the earlier version of Cisco BAC and steps 11 to 14 need to be done on the Linux server where Cisco BAC 3.9 needs to be installed.
To perform a database migration, and install RDU:
Note It is always recommended to take backup of RDU database when the bprAgent is not running. Otherwise, the backed-up database may not have the latest information, and this may lead to some incorrect data values in the DB statistics. For example, the number of CWMP devices may not appear correct.
Step 2 Back up the existing Cisco BAC 3.x RDU database, using the backupDb.sh tool. For details, see the Cisco Broadband Access Center 3.9 Administrator Guide .
Step 3 Back up the following files. Backup is required only if you have customized these files.
– Other xml files and dtd files
Step 4 Verify if the database has been backed up by checking the history.log file, which resides in the BPR_DATA directory.
Step 5 Recover the database that you have backed up to a consistent state, using the recoverDb.sh tool. For details, see the Cisco Broadband Access Center 3.9 Administrator Guide .
where /disk1/backup identifies the location of the database backup files.
After recovering the database, verify it by running the command:
Note In case of any error while verifying the database, contact Cisco Support.
Step 6 Copy the BAC_39_MigrationTool.tar.gz from Cisco.com location.
Step 7 Go to the directory BAC_39_MigrationTool /migration.
Step 8 Run migrationTool.sh > help and follow the help instructions.
Step 9 After the migration is complete, copy the whole database directory and backed-up files to the Linux server where Cisco BAC 3.9 is being installed.
Step 10 Restore the following files.
a. Files under <BAC_HOME>/rdu/conf/ .
– Other xml files and dtd file
b. MIB files under <BAC_HOME>/rdu/mibs /
c. *.xml files under <BAC_HOME>/snmp/conf/
Note While restoring the files, make sure that you merge the changes without overwriting the newly installed files.
Step 11 Run the restoreDB.sh on the newly copied directory.
A verification message is displayed if the database is successfully restored and you can start the RDU server.
Note Before running the restoreDb.sh tool, you must stop the RDU server by running the /etc/init.d/bprAgent stop rdu command. Also, remember to back up the database, then remove all files from the rdu/db and the rdu/dblog directories.
Step 13 Install the RDU component of Cisco BAC 3.9 Linux. For details, see Installing and Uninstalling Cisco BAC on Linux
Before upgrading the DPE, we recommend that you archive your files in the <BPR_HOME>/dpe/conf directory.
Step 1 Upgrade to Cisco BAC 3.9 using the following command:
# < install-path>
/BAC_3.9_Solarisk9/install_bac.sh
a. Press Enter to continue when you are prompted and the following message is displayed:
Upgrading BAC from <earlier version> to 3.9. Are you sure? (y/n) [n]:
b. Enter y to start the upgrade process.
< install-path> — Specifies the complete path to the directory in which the BAC_3.9_Solaris directory has been created.
To verify whether the version information indicates Cisco BAC release 3.9, enter:
Step 2 Restart the DPE process to complete the upgrade process using the following command:
# /etc/init.d/bprAgent start dpe
Upgrading the CNR Extensions is similar to Upgrading the RDU.
Upgrading the CAR Extensions is similar to Upgrading the RDU.
This section describes how to uninstall Cisco BAC from the CLI.
Note You cannot separately uninstall the RDU and DPE that are installed on the same server. Both components are uninstalled together.
The uninstall program removes all the DPE and RDU component files under the installation directory (the default installation directory is /opt/CSCObac ) that are installed in the same server when the uninstall command is run. It also shuts down and removes these processes if they are detected: RDU, SNMP Agent, Tomcat, Watchdog, and DPE.
The uninstallation program does not remove files that were placed outside the installation directory. For example, a component installation places the database and database transaction logs directories under /var/CSCObac .
These files must be manually removed. However, if you choose to install the home, data, and database transaction log directories in the same location, the uninstallation program warns you that continuing the uninstallation will remove the data and log files.
If the program fails to uninstall Cisco BAC, error messages appear.
Note After uninstalling Cisco BAC, manually remove the Data and Database Transaction Logs directories (see Post-Uninstallation Task).
This section describes the procedures to uninstall Cisco BAC.
After uninstalling Cisco BAC, manually remove the data and database logs directories. See Post-Uninstallation Task.
To uninstall Cisco BAC from the command line:
Step 2 Manually remove the configuration of the Cisco BAC extensions from the Cisco Network Registrar server. You can do this from any server that has nrcmd installed and has connectivity with Cisco Network Registrar.
Step 3 Manually remove the Cisco Prime Access Registrar extensions from the Cisco Access Registrar server using the following command:
Step 4 Restart the Cisco Prime Access Registrar server using the following command:
Step 5 At the CLI prompt, enter:
Step 6 Enter y, and press Enter to start uninstalling.
Step 7 Enter y and press Enter.
When uninstallation is complete, a message appears.
After uninstalling Cisco BAC, manually remove the data and database transaction logs directories. To remove these directories:
Step 2 Remove the data and the database transaction logs. (The default directory for both is /var/CSCObac .)
The data and the database transaction logs directories are deleted.