Installing and Uninstalling Cisco BAC on Linux

This chapter explains how to successfully install Cisco BAC on Linux 6.4.

The SELinux and iptables 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.

Preinstallation Checks

The following checks must be performed before installing Cisco BAC on a Linux 6.4 machine:

Creating Setup For Non-root User

The Cisco BAC root user can create non-root users and groups, and enable the non-root users to run Cisco BAC components; RDU, DPE, CNR, and PAR.

You can create a setup where the root and the non-root users can run Cisco BAC together. For details on supported combinations, see Table 3-1 :

Table 3-1 Supported Combinations For Root and Non-Root Users

Cisco BAC Host Users
Supported Combinations To Run Cisco BAC Components

Root

A root user runs all the Cisco BAC components; RDU, DPE, CNR extension points, and PAR extension points.

Non-Root

A non-root user runs all the Cisco BAC components; RDU, DPE, CNR extension points, and PAR extension points.

Root and Non-Root

Combination 1:

  • Root user runs RDU
  • Non-root user runs DPE, CNR extension points, and PAR extension points

Combination 2:

  • Root user runs RDU and DPE
  • Non-root user runs CNR extension points, and PAR extension point

Combination 3:

  • Root user runs DPE, CNR extension points, PAR extension points
  • Non-root user runs RDU

Combination 4:

  • Root user runs CNR extension points, PAR extension points
  • Non-root user runs RDU and DPE

To create non-root users setup in Cisco BAC:

Step 1 Log into the intended Cisco BAC server as root.

Step 2 Create a group in Cisco BAC using the following command:

groupadd –g 1110 baceng
 

-g—group ID.

This creates a group named 1110 baceng.

Step 3 Create a user and assign user to the group using the following command:

useradd -u 102 -g 1110 -d /home/user -m -s /bin/sh -c "Test User" user
 
    • -u—user ID
    • -g—group ID
    • -d—directory location.

Step 4 Add the non-root user into /etc/sudoers file using the following command:

User_Alias NONROOT_BAC_USERS=user ID
 

user ID—non-root user ID

Step 5 Add all the BAC processes and executable scripts into /etc/sudoers file using the following commands:

Cmnd_Alias BAC_CORE_CMDLIST=/etc/init.d/bprAgent
 
Cmnd_Alias BAC_RDU_CMDLIST=<BPR_HOME>/bin/startRDU.sh,
<BPR_HOME>/internal/bin/runRDU.sh,
<BPR_HOME>/internal/db/native/runTool.sh,
<BPR_HOME>/internal/db/bin/dumpMainIndexFull.sh,
<BPR_HOME>/internal/db/bin/dumpOidIndex.sh,
<BPR_HOME>/internal/db/bin/dumpDbStats.sh,
<BPR_HOME>/internal/db/bin/dumpObjectByOid.sh,
<BPR_HOME>/internal/db/bin/dumpMainIndex.sh,
<BPR_HOME>/internal/db/bin/resetAdminPassword.sh,
<BPR_HOME>/internal/db/bin/dumpObjectsInAttributeIndex.sh,
<BPR_HOME>/internal/db/bin/dumpRelationshipIndex.sh,
<BPR_HOME>/internal/db/bin/dumpDeviceByFqdn.sh,
<BPR_HOME>/internal/db/bin/verifyDb.sh,
<BPR_HOME>/internal/db/bin/dumpDeviceByDeviceId.sh,
<BPR_HOME>/internal/db/bin/dumpSchema.sh,
<BPR_HOME>/internal/db/bin/dumpAttributeIndex.sh,
<BPR_HOME>/internal/db/bin/dumpIndexNames.sh,
<BPR_HOME>/internal/db/bin/dumpDeviceByOwnerID.sh,
<BPR_HOME>/internal/bin/runDictGen.sh,
<BPR_HOME>/internal/bin/shutdownRDU.sh,
<BPR_HOME>/internal/bin/runTemplateGen.sh,
<BPR_HOME>/bin/recoverDb.sh,
<BPR_HOME>/bin/backupDb.sh,
<BPR_HOME>/bin/stopRDU.sh,
<BPR_HOME>/bin/restoreDb.sh,
<BPR_HOME>/bin/deviceExport.sh,
<BPR_HOME>/bin/runCfgUtil.sh,
<BPR_HOME>/bin/runStatAnalyzer.sh
 
Cmnd_Alias BAC_DPE_CMDLIST=<BPR_HOME>/internal/bin/runDPE.sh,
<BPR_HOME>/internal/bin/shutdownDPE.sh,
<BPR_HOME>/bin/stopDPE.sh,
<BPR_HOME>/bin/runStatAnalyzer.sh,
<BPR_HOME>/bin/startDPE.sh
 
Cmnd_Alias BAC_CLI_CMDLIST=<BPR_HOME>internal/bin/runCLI.sh,
<BPR_HOME>internal/bin/shutdownCLI.sh,
<BPR_HOME>/bin/startCLI.sh,
<BPR_HOME>/bin/stopCLI.sh
 
Cmnd_Alias BAC_CAR_EP_CMDLIST=
Cmnd_Alias BAC_CNR_EP_CMDLIST=
 
Cmnd_Alias BAC_CLIENT_CMDLIST=<BPR_HOME>/internal/bin/runEvent Monitor.sh
 
Cmnd_Alias BAC_SNMP_CMDLIST=<BPR_HOME>/bin/snmpAgentCfgUtil.sh,
<BPR_HOME>/internal/bin/runSNMPAgent.sh,
<BPR_HOME>/internal/bin/shutdownSNMPAgent.sh
 
<BPR_HOME>/internal/lib/diagnosticsCommon.sh,

 

<BPR_HOME>—Cisco BAC product installation path, for example, /opt/CSCObac

Step 6 Provide access to all the BAC processes and executable scripts to the non-root BAC users in /etc/sudoers file, using the following command.

NONROOT_BAC_USERS ALL = BAC_CORE_CMDLIST, BAC_CLI_CMDLIST, BAC_CLIENT_CMDLIST, BAC_SNMP_CMDLIST, BAC_RDU_CMDLIST,BAC_DPE_CMDLIST,BAC_CNR_EP_CMDLIST, BAC_CAR_EP_CMDLIST

Note Cisco BAC also provides the updateSudoers.sh utility to update the /etc/sudoers file. If you use the updateSudoers.sh utility, you may skip step 4 to step 6.

Step 7 Set the /etc/sudoers file as the source file using the following command:

source /etc/sudoers
 

Step 8 Invoke the BAC executables and scripts using the following commands:

sudo /etc/init.d/bprAgent
 
sudo <BPR_HOME>/rdu/internal/db/bin/resetAdminPassword.sh
 

The setup for non-root users and groups is created in Cisco BAC.

 

Installing Cisco BAC

The initial steps in the Cisco BAC installation program are identical, regardless of the component you are installing. This section explains how to work with the installation program.

To install Cisco BAC:

Step 1 Log into the intended Cisco BAC with your username and password.

Step 2 At the Linux system prompt, change directory to your CD-ROM drive or other installation media.

Step 3 Ensure that the gzip and gtar utilities are available on your system under /bin directory, to decompress and unpack the Cisco BAC installation file, and:

a. Change to the directory in which you will decompress and extract the installation file.

b. Decompress and unpack the file with the .gtar.gz extension. Enter:

gtar zxvf BAC_3.10_LinuxK9.gtar.gz
 

The utility creates the BAC_3.10_LinuxK9 directory into which the installation program is extracted.

Note If the program displays a checksum error while unpacking, specify the path to the GNU tar on your machine.

Step 4 After the installation program is extracted, you can choose to install the components.

Before you begin any of these procedures, you must complete the initial procedure described in Installing Cisco BAC.

To install the Cisco BAC components, see:

 

Installing the RDU

Install the RDU on a server running Linux that meets the requirements described in Cisco BAC Components.

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 Installing Cisco BAC. After you do this:

Step 1 Enter the following command to start the installation program in interactive mode:

# <install-path>/BAC_3.10_LinuxK9/install_bac.sh
 

<install-path> —specifies the complete path to the directory in which the BAC_3.10_LinuxK9 directory has been created.

The installation program verifies that you have installed the required patches on the Linux 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. If you want to configure the non-root user to run Cisco BAC, ensure that the setup for non-root user is created. For details, see Creating Setup For Non-root User.

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, steps 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 the DPE, Cisco Network Registrar extension points, and Cisco Prime Access Registrar extension points, enter n and press Enter. You can choose to install these components later.

Step 7 Confirm the components that you want to install. To do this, enter y and press Enter.

The home directory prompt appears.

Step 8 Accept the default directory, /opt/CSCObac, by pressing Enter ; or enter another directory.

Step 9 Confirm the directory location. To do this, enter y and press Enter.

The data directory prompt appears.

Step 10 Accept the default directory, /var/CSCObac, by pressing Enter ; or enter another directory.

Step 11 Confirm the directory location. To do this, enter y and press Enter.

The database log 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 starts preparing the packages for the installation.

Step 14 Accept the default port number, 49187, by pressing Enter ; or enter another port number.

Caution If you change the default listening port value, ensure that the new value does not conflict with any existing port assignments. Also, ensure that you configure all DPEs with the correct RDU port number. For details on configuring the DPE, see the Cisco Broadband Access Center 3.8 DPE CLI Reference.

Step 15 Confirm the listening port number. To do this, 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 installation.

The program displays the installation parameters that you selected.

Step 18 Enter y and press Enter to confirm the parameters, and install the RDU component.

Step 19 Enter y and press Enter.

The program prompts you to continue with the installation.

Step 20 Enter y and press Enter.

After a successful installation, the following message appears:

Installation of <CSCObac> was successful.
 

Step 21 Launch the Cisco BAC administrator user interface to verify whether the RDU is running.

a. Enter the administrator’s location using the following URL:

http :// machine_name /

 

machine_name — Identifies the computer on which the RDU is running.

The main Login page appears.

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.

 

Installing the DPE

Install the DPE on a server running Linux that meets the requirements described in Cisco BAC Components.

Note 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 quits. To terminate the TFTP or ToD server, perform the steps that the error message lists.

To install the DPE, complete the initial installation described in Installing Cisco BAC. To start the installation program in interactive mode:

Step 1 Run:

# <install-path>/BAC_3.10_LinuxK9/install_bac.sh
 

< install-path> —Specifies the complete path to the directory in which the BAC_3.10_LinuxK9 directory has been created.

The installation program verifies that you have installed the required patches on the Linux 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. If you want to configure the non-root user to run Cisco BAC, ensure that the setup for non-root user is created. For details, see Creating Setup For Non-root User.

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, steps 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 DPE prompt.

To skip installing the RDU, Cisco Network Registrar extension points, and Cisco Prime Access Registrar extension points, enter n and press Enter. You can choose to install these components later.

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. To do this, 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. To do this, enter y and press Enter.

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 11 Re-enter the password for confirmation, and press Enter.

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.

Step 14 Confirm the information. To do this, enter y and press Enter.

The installation proceeds, and displays the following message after successful installation:

 
Installation of <CSCObac> was successful.
 

 

Installing the Cisco Network Registrar Extensions

Install the Cisco Network Registrar extension points on a Linux server that meets the requirements described in Cisco BAC Components.

To install the Cisco Network Registrar extension points, complete the initial installation described in Installing Cisco BAC. After you do this:

Step 1 Enter the following command to start the installation program in interactive mode:

# <install-path>/BAC_3.10_LinuxK9/install_bac.sh
 

< install-path> —Specifies the complete path to the directory in which the BAC_39_LinuxK9 directory has been created.

The installation program verifies that you have installed the required patches on the Linux operating system. When the verification ends, 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. If you want to configure the non-root user to run Cisco BAC, ensure that the setup for non-root user is created. For details, see Creating Setup For Non-root User.

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, steps 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 prompt.

To skip installing the RDU, DPE, and Cisco Prime Access Registrar extension points, enter n and press Enter. You can choose to install these components later.

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. To do this, 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.

The database log directory prompt appears.

Step 10 Accept the default directory, /var/CSCObac, by pressing Enter; or enter another directory.

Step 11 Confirm the directory location. To do this, enter y and press Enter.

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 12 Re-enter the password for confirmation, and press Enter.

The program prompts you to enter information on the RDU, required to install the extensions.

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 Confirm the information. To do this, enter y and press Enter.

The installation proceeds, and displays the following message after successful installation:

Installation of <CSCObac> was successful.
 

 

Configuring Extensions

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:

  • The Cisco BAC component is installed in /opt/CSCObac.
  • Cisco Network Registrar is installed in /opt/nwreg2.
  • The Cisco Network Registrar username is admin and the password is changeme.

To configure extensions:

Step 1 Log into the Cisco Network Registrar server, with root access.

Step 2 At the command line, enter:

# <NR_HOME>/local/usrbin/nrcmd -N admin -P changeme -b <
<BAC_HOME>/cnr_ep/bin/bpr_cnr_enable_extpts.nrcmd
    • To reload the Cisco Network Registrar server, enter:
# /etc/init.d/nwreglocal stop
# /etc/init.d/nwreglocal start
    • To reload the DHCP server alone, enter:
# <NR_HOME>/local/usrbin/nrcmd -N admin -P changeme "dhcp reload"

Note Before you can use the Cisco Network Registrar server, you must configure client classes, scope-selection tags, policies, and scopes. see the Cisco Prime Network Registrar 8.3 DHCP User Guide.

 

Validating Extensions

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:

  • Local—/opt/nwreg2/local/usrbin
  • Regional—/opt/nwreg2/regional/usrbin
nrcmd> extension list
100 Ok
dexdropras:
entry = dexdropras
file = libdexextension.so
init-args =
init-entry =
lang = Dex
name = dexdropras
preClientLookup:
entry = bprClientLookup
file = libbprextensions.so
init-args = BPR_HOME=/opt/CSCObac,BPR_DATA=/var/CSCObac
init-entry = bprInit
lang = Dex
name = preClientLookup
nrcmd>
 

Note The BPR_HOME and BPR_DATA values may be different in your installation.

Also, in the nrcmd program, run:

nrcmd> extension list
100 Ok
dexdropras:
entry = dexdropras
file = libdexextension.so
init-args =
init-entry =
lang = Dex
name = dexdropras
preClientLookup:
entry = bprClientLookup
file = libbprextensions.so
init-args = BPR_HOME=/opt/CSCObac,BPR_DATA=/var/CSCObac
init-entry = bprInit
lang = Dex
name = preClientLookup
nrcmd>
 

Note When you install all the components in the same Linux server, Cisco Network Registrar will not respond to the lease queries from RDU.

 

Installing the Cisco Prime Access Registrar Extension Points

Install the Cisco Abstract Registrar on a Linux server that meets the requirements described in Cisco BAC Components.

To install the Cisco Abstract Registrar, complete the initial installation described in Installing Cisco BAC. After you do this:

Step 1 Enter the following command to start the installation program in interactive mode:

# <install-path>/BAC_3.10_LinuxK9/install_bac.sh
 

< install-path> —Specifies the complete path to the directory in which the BAC_3.10_LinuxK9 directory has been created.

The installation program verifies that you have installed the required patches on the Linux 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. If you want to configure the non-root user to run Cisco BAC, ensure that the setup for non-root user is created. For details, see Creating Setup For Non-root User.

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, steps 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 PAR prompt.

To skip installing the RDU, DPE, and the Cisco Network Registrar extension points, enter n and press Enter. You can choose to install these components later.

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. To do this, 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. To do this, enter y and press Enter.

The program prompts you to enter information on the RDU required to install the extensions.

Step 11 Enter the IP address (or hostname) and the listening port of the host on which you have installed the RDU.

Step 12 Accept the default information, by pressing Enter; or enter alternative information.

Step 13 Confirm the information. To do this, enter y and press Enter.

The installation proceeds, and displays the following message after successful installation:

Installation of <CSCObac> was successful.
 

 

Adding Components in Linux

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.10 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.10 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.

Upgrading Cisco BAC

This section describes how to upgrade Cisco BAC 3.8.1, 3.8.1.x or 3.9 installation on Linux to Cisco BAC 3.10 Linux.

You must stop the process watchdog (bprAgent) before upgrading. After the upgrade is complete, Cisco BAC does not restart the process watchdog automatically. You must migrate your existing database first before starting the watchdog.

Upgrading Cisco BAC 3.8.1, 3.8.1.x or 3.9 on Linux requires upgrading the RDU and DPE from Cisco BAC 3.8.1, 3.8.1.x or 3.9 to Cisco BAC 3.10. You must perform the following set of tasks sequentially to upgrade the RDU and DPE:

1. Automatic Pre-Maintenance Activities

2. Backing Up the RDU Database

3. Migrating the RDU database

4. Upgrading RDU and DPE

Automatic Pre-Maintenance Activities

This script is used to automate Pre-maintenance window activities such as Backup, Database recovery and verification, and migration of the database, before any major upgrade from Cisco BAC 3.8.1, 3.8.1.x or 3.9 to 3.10. This script can be run on the server where RDU is installed. You can either choose a single prompt to complete all the above activities or execute them one-by-one by providing the appropriate inputs.The script is located at the following path: <install-path>/BAC_3.10_LinuxK9/pre_maintenance.sh

Backing Up the RDU Database

To back up the RDU database:

Step 1 Stop the bprAgent using the following command:

# /etc/init.d/bprAgent stop

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 Run the backupDb.sh script in the <BPR_HOME>/rdu/bin directory to back up the RDU database:

# ./backupDb.sh /var/backup
 

/var/backup —identifies the database backup directory.

In this example, all backup database files are stored in a directory called /var/backup/rdu-backup-20140907-063133. The last subdirectory (rdu-backup-20140907-063133) is automatically created with a current time stamp.

Step 3 Run the recoverDb.sh script in the <BPR_HOME>/rdu/bin directory to recover the RDU database:

# ./recoverDb.sh /var/backup/rdu-backup-20140907-063133
 

Step 4 Run the verifyDb.sh script in the <BPR_HOME>/rdu/internal/db/bin directory to verify the RDU database integrity:

# ./verifyDb.sh -dbdir /var/backup/rdu-backup-20140907-063133
 

The back up process for RDU database is completed, and the RDU database is recovered and verified.

 

Migrating the RDU database

To migrate the RDU database from Cisco BAC 3.8.1, 3.8.1.x or 3.9 to Cisco BAC 3.10:

Step 1 Run migrationTool.sh in the directory BAC_310_MigrationTool /migration:

#./migrationTool.sh -dbdir /var/backup/rdu-backup-20140907-063133
 

Step 2 Observe the migration progress using the migration.log file:

# tail -f /var/backup/rdu-backup-20140907-063133/migration.log
 

The RDU database is migrated from Cisco BAC 3.8.1, 3.8.1.x or 3.9 to Cisco BAC 3.10

 

Upgrading RDU and DPE

To upgrade the RDU and DPE components of Cisco BAC 3.8.1, 3.8.1.x or 3.9 to Cisco BAC 3.10:

Step 1 Decompress the Cisco BAC 3.10 installation package with .gtar.gz extension using the following command:

gunzip -d BAC_3.10_LinuxK9.gtar.gz
 

Step 2 Unpack the Cisco BAC 3.10 installation package with.gtar extension using the following command:

gtar -xvf BAC_3.10_LinuxK9.gtar
 

Step 3 To start the upgrade process for RDU and DPE, install the Cisco BAC 3.10 version using the following command:

“<install-path>/BAC_3.10_LinuxK9/install_bac.sh
 

The installation program prompts you to confirm if you want to proceed with the Cisco BAC 3.10 installation.

Step 4 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. If you want to configure the non-root user to run Cisco BAC, ensure that the setup for non-root user is created. For details, see Creating Setup For Non-root User.

Step 5 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 6 and 7 do not appear.

Step 6 Provide the name of the non-root user, and press Enter to continue.

Step 7 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 8 To confirm that you want to upgrade, enter y and press Enter.

Step 9 The following message appears:

You must perform the following set of tasks sequentially to upgrade the RDU and DPE:
1. Back Up the RDU Database
2. Recover the Backed up RDU Database
3. Verify the Recovered RDU Database
4. Migrate the Verified RDU Database
5. Verify the Migrated RDU Database [Optional]
The above steps can be performed manually.
Have you already performed the pre-maintenance script and/ or do you want to skip the above processes? (y/n) [n]: n

 

If you enter y, you will be directed to start upgrading the RDU and DPE. See step 10 below.

If you enter n, you will be directed to manually perform the tasks from 1-5 as listed above.

Step 10 In the following message that appears, enter y to remove the directories.

Before restoring the backing database, the existing db and dblog directories should be removed. Are you sure (y/n)? (y/n) [n]:

 

Step 11 In the following message that appears, enter y to restore the database.

Do you want to restore the latest database backup [/var/backup/rdu-backup-20150422-101419]? (y/n) [y]:

 

Step 12 Restart the bprAgent using the following command:

# /etc/init.d/bprAgent restart
 

The RDU and DPE is upgraded from Cisco BAC 3.8.1, 3.8.1.x or 3.9 to Cisco BAC 3.10 version.

 

Uninstalling Cisco BAC

This section describes how to uninstall Cisco Broadband Access Center (Cisco BAC).

The procedure described in this section uninstalls the RDU, DPE, Cisco Access Registrar extension points and Cisco Network Registrar extensions but it does not uninstall the Cisco Network Registrar application. Before removing Cisco BAC, manually remove the Cisco BAC configuration on Cisco Network Registrar.

The uninstallation program removes all files found in the installation directory (the default directory is /opt/CSCObac). The program also shuts down and removes these processes, if they are detected: SNMP Agent, Tomcat, Cisco BAC agent, RDU, 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 logs directories under /var/CSCObac. These files must be removed manually. (Subsequent sections describe how to delete these files.) Also, the program does not remove any files found in the Cisco Network Registrar directory.

If you have installed Cisco BAC extensions on Cisco Network Registrar, you must uninstall those extensions to completely uninstall the Cisco BAC program; otherwise, an error message appears.

Note The path to the Cisco Network Registrar extensions differs based on the location where you have installed Cisco Network Registrar; the default location is /opt/nwreg2.

If the uninstallation program fails to uninstall Cisco BAC, error messages appear.

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 1 Log in using your username and password.

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 connectivity with Cisco Network Registrar.

    • To uninstall the Cisco BAC extensions from your Cisco Network Registrar configuration, enter:
# <NR_HOME>/local/usrbin/nrcmd -N admin -P changeme -b <
<BPR_HOME>/cnr_ep/bin/bpr_cnr_disable_extpts.nrcmd
    • To reload your DHCP server, enter:
# /etc/init.d/nwreglocal stop
# /etc/init.d/nwreglocal start
 
    • To remove the Cisco BAC extensions from the Cisco Network Registrar extensions directory, enter:
# rm -rf <NR_HOME>/local/extensions/dhcp/dex/libbprextensions.so
 

Step 3 Manually remove the Cisco Prime Access Registrar extensions from the Cisco Prime Access Registrar server using the command:

# rm -rf <CAR_HOME>/scripts/radius/java/dpeext.jar
 

Step 4 Restart the Cisco Prime Access Registrar server by running:

# /etc/init.d/arserver restart
 

Step 5 Run the following command to uninstall:

# <install-path>/BAC_3.10_LinuxK9/uninstall_bac.sh
 

Step 6 Enter y to continue.

Step 7 Run the following commands to delete the previously installed directories.

 
rm -rf /opt/CSCObac
rm -rf /var/CSCObac/RDU
rm -rf /var/CSCObac/DPE
 
 

 

Post-Uninstallation Task

After you have uninstalled Cisco BAC, manually remove the data and database logs directories. To remove these directories:

Step 1 Log in as root.

Step 2 Remove the data and the database logs directories. (The default directory for both is /var/CSCObac.)

For example, enter:

# rm -rf /var/CSCObac
 

The data and the database logs directories are deleted.

Integrating Cisco BAC with Cisco Prime Central

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 Management server, like IP address and used ports.

BAC can be integrated and registered with Prime Central in two different modes: Active and DR (Disaster recovery) mode. While integrating with DR mode, the user needs to specify Domain Manager (DM) ID for successful integration.

Note In order to integrate BAC with Prime central in DR mode, the user must ensure that the dmid.xml file does not exist. The dmid.xml file resides in the directory <BAC_HOME>/prime_integrator.

After successful execution of this script, BAC will be registered with Prime Central as a Domain Manager instance. In addition, Prime Central is configured as one of the trap listeners in DPE to receive traps.

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.

For example:

[root@bac-sol-vm188 prime_integrator]# ./primeIntegration.sh

Step 3 Enter values for the following credentials at the prompt:

    • Prime Central integration mode: Active(a) or DR(d) (a, by default)
    • Prime Central Database Server IP address

The default value is the same IP address as the installed BAC RDU/DPE.

    • Prime Central database name ( primedb, by default)
    • Prime Central database port ( 1521, by default)
    • Prime Central database user name ( primedba, by default)
    • Prime Central database password
    • Prime Central SNMP Trap Host

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.

    • Prime Central SNMP Trap port ( 1162, by default)
    • Prime Central Domain Manager (DM) Id (1, by default)

Enter valid DM Id if integrating Prime Central in DR mode only. If Active mode is selected then this credential is not prompted.

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.