Installation of Broadband Access Center on Solaris
This chapter explains the procedure and sequence of event for a successful installation of Cisco Broadband Access Center (Cisco BAC) on Solaris. It covers the following topics:
•Preinstallation Tasks
•Installing Cisco Broadband Access Center
•Upgrading Cisco Broadband Access Center
•Uninstalling Cisco Broadband Access Center
Preinstallation Tasks
Before you begin to install BAC on Solaris, you need to perform the following set of tasks:
•Create users and groups.
•Assign privileges to users.
Following are the preinstallation procedures that a root user should perform:
Step 1 Create users and groups.
A new user is created by the system administrator.
For example:
useradd -u 102 -g 1110 -d /home/user -m -s /bin/sh -c "Test User" user
where -u is the user name
-g is the group name
-d is the directory location
A group is created and the user is assigned to that group.
where -g is the group name
Step 2 Assign privileges to users.
For example:
usermod -K defaultpriv=file_chown, file_link_any, file_owner, net_privaddr, proc_exec,
proc_fork,proc_info, proc_owner, proc_session, proc_setid user
Privileges are assigned to a new user by the system administrator to run the product.
To configure RBAC feature of Solaris, see System Administration Guide: Security Services for configuring RBAC in http://docs.sun.com/app/docs/doc/816-4557/rbactask-30?a=view.
Note During installation, it may be necessary to install several Solaris patches on your computer. Should patch installation become necessary, see the Sun Microsystems support site to download these patches. For a list of recommended patches, see Operating System Requirements, page 1-2.
Installing Cisco Broadband Access Center
This chapter explains the procedures you must follow to install Cisco Broadband Access Center (Cisco BAC) in a Solaris operating system environment.
This chapter includes:
•Installing Cisco Broadband Access Center
•Installing Components in Interactive Mode
•Installing Components in Noninteractive Mode
•Adding Components
Before you install Cisco BAC, ensure that you are ready by reviewing the checklist that Table 3-1 describes.
Table 3-1 Installation Checklist
|
|
1. Verify if your system meets the minimum system hardware and software requirements described in Chapter 1, "Overview." |
|
2. Ensure that you have access to the computers on which you intend to install Cisco BAC components. |
|
3. Save your license file on the system from which you intend to launch the Cisco BAC administrator user interface via a web browser. You need a valid service license file to configure Cisco BAC licensing. |
|
4. Determine the home directory (BPR_HOME) in which you want to install the Cisco BAC component or components. The default directory is /opt/CSCObac. Ensure that the target installation directory has enough disk space.
Note We recommend that you have at least 500 MB of disk space available otherwise installation will not take place.
|
|
5. For the RDU, determine where you want to install the data directory (BPR_DATA) and the database logs (BPR_DBLOG). The default directory is /var/CSCObac. Ensure that the target installation directory has enough disk space.
Note We recommend that you locate the data directory on a different physical disk than the home directory; for example, /var/disk0/CSCObac. The disk should have at least 1 GB and up to 30 GB of free space. The installation program, by default, installs the data directory, the database transaction logs directory, and the logs directory in the same location. We recommend that you locate the database transaction logs directory on the fastest disk on the system. Also, ensure that 1 GB of disk space is available.
|
|
6. Verify that you have minimum 500 MB of free space available in the /tmp directory for successful installation. |
|
7. For the RDU, determine the listening port number. The RDU uses this interface to communicate with other Cisco BAC components, such as DPEs and CNR extension points. The default port is 49187. |
|
8. For the RDU, determine the shared secret password that Cisco BAC servers on your network use as a token to authenticate communication with one another. The shared secret password should be the same for all Cisco BAC servers on your network. |
|
9. For the RDU, determine the ports through which you will access the administrator user interface using HTTP or HTTP over SSL (HTTPS). The default ports are: •8100 for HTTP •8443 for HTTPS |
|
10. Ensure that CNR 7.1.2.1 is installed and running on the servers on which you are installing Cisco BAC extensions.
Note To enable IPv6 support in Cisco BAC, you must install version 7.1.2.1 of CNR.
|
|
11. For the CNR extensions, determine the name of the provisioning group to which the CNR server belongs. |
|
12. For the CNR extensions, determine where you want to install the data directory (BPR_DATA). The default directory is /var/CSCObac. |
|
13. Verify that you have the necessary CNR configuration files. For an example of these configuration files, see Appendix A, "Network Registrar Configuration File Example." |
|
14. Verify that you have the necessary KDC servers available. |
|
15. Enable your machine to support IPv6. To enable IPv6, log in as root, and run:
# ifconfig intf inet6 plumb up
# touch /etc/hostname6.intf
where intf identifies the interface on which you want to enable IPv6. |
|
Installing Cisco BAC
This section describes how to work with the installation program and the initial installation steps. The initial steps in the Cisco BAC installation program are identical regardless of the component you are installing.
Note The procedure of running Cisco BAC as a non-root user is similar to that of a root user. The non-root user should have appropriate permissions to run the product. For list of permissions, see Preinstallation Tasks
To install Cisco BAC:
Step 1 Log in to the intended Cisco BAC host as root.
Step 2 At the Solaris system prompt, change directory to your CD-ROM drive or other installation media.
Ensure that the gzip and gtar utilities are available on your system 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 the file with the .gtar.gz extension. Enter:
gunzip -d BAC_4101_SolarisK9.gtar.gz
c. Unpack the file with the .gtar extension that gunzip decompressed. Enter:
gtar -xvf BAC_4101_SolarisK9.gtar
The utility creates the BAC_4101_SolarisK9 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 3 After the installation program is extracted, you can choose to install the components in interactive mode or noninteractive mode.
•Installing Components in Interactive Mode
•Installing Components in Noninteractive Mode
Installing Components in Interactive Mode
This section explains the procedures that you follow to install one or more Cisco BAC components interactively from the command line.
If you have not enabled IPv6 on your machine, a message similar to the following appears during installation:
Warning: IPv6 is not enabled on this system.
You can choose to enable IPv6 later, by running these commands:
# ifconfig intf inet6 plumb up
# touch /etc/hostname6.intf
where intf identifies the interface on which you want to enable IPv6.
Note Before you begin any of these procedures, you must complete the initial procedure described in Installing Cisco Broadband Access Center.
This section provides instructions on installing components in interactive mode:
•Installing the RDU in Interactive Mode
•Installing a DPE in Interactive Mode
•Installing CNR Extensions in Interactive Mode
•Installing the KDC in Interactive Mode
Installing the RDU in Interactive Mode
Install the RDU on a server running Solaris 10 that meets the requirements described in Operating System Requirements, page 1-2. You should install the RDU on a high-end system that is the most reliable server in your network.
Before installation, remove /rdu/db from /var/CSCObac/ directory.
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 Broadband Access Center. Then:
Step 1 To start the installation program in interactive mode, enter:
# pkgadd -d install-path/BAC_4101_SolarisK9/CSCObac.pkg CSCObac
where install-path specifies the complete path to the directory in which the BAC_4101_SolarisK9 directory has been created.
The installation program verifies that you have installed the required patches to the Solaris operating system. When the verification ends, welcome information appears as:
Welcome to the Cisco Broadband Access Center for Cable 4.1.0.1 (BAC) installation
program. This installation program installs BAC 4.1.0.1 on your system.
The installer for Cisco Broadband Access Center for Cable 4.1.0.1 enables
non-root user, who has appropriate permission to run the product.
The non-root user can run the product, provided the user has the following
file_chown, file_link_any, file_owner, net_privaddr, proc_exec, proc_fork,
proc_info, proc_owner, proc_session, proc_setid
In order to allow the non-root user or non-root users who belong to a specific
group to run Cisco BAC, specify the name of the non-root user and the
group in the "User and Group" prompt that appears next.
Else, to run as root user, specify the name as "root" and group as "root" in
the "User and Group" prompt that appears next.
Step 2 Press Enter to continue.
The program prompts you to add user name and user group name.
------------------ User and Group -----------------------
Enter the name of the user [?,q] user1
Enter the name of the group [?,q] group1
Step 3 Specify the user name and group name to run Cisco BAC.
Note If you want to run BAC as a root user, provide user and user group as root.
Step 4 Press Enter to continue.
The installation program prompts you to select one or more components.
Step 5 Enter y and press Enter at the RDU prompt.
To skip installing a DPE, CNR extension points, and the KDC, enter n and press Enter. You can choose to install these components later.
For example:
-------------- Installation Components ------------
Regional Distribution Unit (RDU) (y/n)? [n] y
Device Provisioning Engine (DPE) (y/n)? [n] n
Cisco Network Registrar extension points (y/n)? [n] n
Key Distribution Center (KDC) (y/n)? [n] n
Step 6 Confirm the components that you want to install; enter y and press Enter.
The program prompts you to confirm the components that you want to install.
------------------ Confirmation --------------
Is this correct (y/n/q)? [y] y
Step 7 Enter y and press Enter to continue.
Cisco BAC performs lease query requests by binding to the IP addresses and ports that are described in Table 3-2.
Table 3-2 Lease Query Address for Binding
|
|
|
IPv4 |
Wildcard1 |
67 |
IPv6 |
Wildcard |
547 |
If the installation program detects that either of these ports is being used by another process, it recommends that you use the dynamic ports that the operating system selects.
For example:
DHCPv4/DHCPv6 lease query port(s) (Udp/67 and Udp/547) is in use.
Configuring the RDU to use a dynamic port for DHCPv4/DHCPv6 lease query.
If port 67 and port 547 are available on the RDU, the installation program displays the home directory prompt.
Step 8 To accept the default directory, /opt/CSCObac, press Enter; or enter a different directory.
For example:
-------------- Home Directory -----------
Home Directory [/opt/CSCObac]
A confirmation prompt appears.
Step 9 To confirm the home directory location, enter y and press Enter.
The program prompts you to enter the data directory location.
Step 10 To accept the default directory, /var/CSCObac, press Enter; or enter a different directory.
For example:
-------------- Data Directory -----------
DB Data Directory [/var/CSCObac] /var/disk0/CSCObac
A confirmation prompt appears.
Step 11 To confirm the data directory location, enter y and press Enter.
The database log directory prompt appears.
Step 12 To accept the default directory, /var/CSCObac, press Enter; or enter another directory.
For example:
----------------- DB Log Directory -------------
DB Logs Directory [/var/CSCObac] /var/disk1/CSCObac
A confirmation prompt appears.
Step 13 To confirm the directory, enter y and press Enter to continue.
The program prompts you to enter the information related to the RDU, specifically the IP address and the listening port.
While the installation program obtains the IP address of the RDU automatically, you must enter a value for the listening port. The listening port is the port number that the RDU uses to communicate with other Cisco BAC components, such as DPEs and CNR extension points.
Step 14 To accept the default port number, 49187, press 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 DPE CLI Reference, 4.1.
For example:
------------------ RDU information ----------------
Enter the listening port of Regional Distribution Unit (RDU).
RDU Listening Port [49187]
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 CNR extension points in your network.
For example:
Enter the password to be used for authentication between BAC servers.
Enter the shared secret password [] <changeme>
Enter the shared secret password again [] <changeme>
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 installation parameters.
For example:
-------------------- Confirmation ----------------------
Home directory: /opt/CSCObac
DB Data directory: /var/disk0/CSCObac
DB Log directory: /var/disk1/CSCObac
The program prompts you to enter the HTTP port for the administrator user interface.
Step 19 To accept the default port, 8100, press Enter; or enter another port number.
For example:
Please enter Admin UI http port [8100]
Step 20 Confirm the HTTP port; enter y and press Enter.
For example:
------------------ Admin UI Information ----------------
Please enter Admin UI HTTP port [8100]
------------------ Confirmation --------------------
Is this correct (y/n/q)? [y] y
The program prompts you to enter the HTTPS port for the user interface.
Step 21 To accept the default port, 8443, press Enter; or enter another port number.
For example:
Please enter Admin UI HTTPS port [8443]
Step 22 Confirm the HTTPS port; enter y and press Enter.
The program displays the parameters you have selected to install the administrator user interface.
Step 23 Enter y and press Enter.
For example:
--------------------- Confirmation --------------------
Installation directory: /opt/CSCObac/rdu
Is this correct (y/n/q)? [y] y
The program prompts you to continue with the installation.
Step 24 Enter y and press Enter.
For example:
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <CSCObac> [y,n,?] y
After successful installation, the following message appears:
Installation of <CSCObac> was successful.
Installing a DPE in Interactive Mode
Install the DPE on a server running Solaris 10 that meets the requirements described in Operating System Requirements, page 1-2.
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 kill the TFTP or ToD server, carry out the steps that the error message lists.
To install the DPE, complete the initial installation described in Installing Cisco Broadband Access Center. Then:
Step 1 To start the installation program in interactive mode, enter:
# pkgadd -d install-path/BAC_4101_SolarisK9/CSCObac.pkg CSCObac
where install-path specifies the complete path to the directory in which the BAC_4101_SolarisK9 directory has been created.
The installation program verifies that you have installed the required patches to the Solaris operating system. When the verification ends, welcome information appears.
Welcome to the Cisco Broadband Access Center for Cable 4.1.0.1 (BAC) installation
program. This installation program installs BAC 4.1.0.1 on your system.
The installer for Cisco Broadband Access Center for Cable 4.1.0.1 enables
non-root user, who has appropriate permission to run the product.
The non-root user can run the product, provided the user has the following
file_chown, file_link_any, file_owner, net_privaddr, proc_exec, proc_fork,
proc_info, proc_owner, proc_session, proc_setid
In order to allow the non-root user or non-root users who belong to a specific
group to run Cisco BAC, specify the name of the non-root user and the
group in the "User and Group" prompt that appears next.
Else, to run as root user, specify the name as "root" and group as "root" in
the "User and Group" prompt that appears next.
Step 2 Press Enter to continue.
The program prompts you to add user name and user group name.
------------------ User and Group -----------------------
Enter the name of the user [?,q] user1
Enter the name of the group [?,q] group1
Step 3 Specify the user name and group name to run Cisco BAC.
Step 4 Press Enter to continue.
The installation program prompts you to select one or more components.
Step 5 Enter y and press Enter at the DPE prompt
To skip installing the RDU, CNR extension points, and the KDC, enter n and press Enter.
For example:
-------------- Installation Components ------------
Regional Distribution Unit (RDU) (y/n)? [n] n
Device Provisioning Engine (DPE) (y/n)? [n] y
Cisco Network Registrar extension points (y/n)? [n] n
Key Distribution Center (KDC) (y/n)? [n] n
Step 6 Confirm the components that you want to install; enter y and press Enter.
The program prompts you to confirm the components that you want to install.
------------------ Confirmation --------------
Is this correct (y/n/q)? [y] y
Step 7 Enter y and press Enter to continue.
The home directory prompt appears.
Step 8 To accept the default directory, /opt/CSCObac, press Enter; or enter another directory.
For example:
-------------- Home Directory -----------
Home Directory [/opt/CSCObac]
Step 9 Confirm the directory location; enter y and press Enter.
The data directory prompt appears.
Step 10 To accept the default directory, /var/CSCObac, press Enter; or enter another directory.
For example:
-------------- Data Directory -----------
DB Data Directory [/var/CSCObac]
Step 11 Confirm the directory location; enter y and press Enter.
The program prompts you to enter the shared secret password.
Step 12 Enter the shared secret password that you want to use for authentication between the Cisco BAC servers.
Note You must use the same shared secret password for the RDU, all DPEs, and CNR extension points in your network.
For example:
------------------ DPE information ---------------
Enter the password to be used for authentication between BAC servers.
Enter the shared secret password [] <changme>
Enter the shared secret password again [] <changme>
Step 13 Reenter the password for confirmation, and press Enter.
The program prompts you to confirm the installation.
Step 14 Enter y and press Enter.
Note If you choose not to proceed, the following message appears and the installation quits:
Installation of <CSCObac> was terminated due to user request.
No changes were made to the system.
The program begins the installation process. After successful installation, the following message appears:
Installation of <CSCObac> was successful.
Installing CNR Extensions in Interactive Mode
Install Cisco BAC extensions on all CNR 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 CNR server to use a static IP address.
Before you install CNR extensions, complete the initial installation described in Installing Cisco Broadband Access Center. Also, ensure that CNR is running. Then:
Step 1 To start the installation program in interactive mode, enter:
# pkgadd -d install-path/BAC_4101_SolarisK9/CSCObac.pkg CSCObac
where install-path specifies the complete path to the directory in which the BAC_4101_SolarisK9 directory has been created.
The installation program verifies that you have installed the required patches to the Solaris operating system. When the verification ends, welcome information appears.
Welcome to the Cisco Broadband Access Center for Cable 4.1.0.1 (BAC) installation
program. This installation program installs BAC 4.1.0.1 on your system.
The installer for Cisco Broadband Access Center for Cable 4.1.0.1 enables
non-root user, who has appropriate permission to run the product.
The non-root user can run the product, provided the user has the following
file_chown, file_link_any, file_owner, net_privaddr, proc_exec, proc_fork,
proc_info, proc_owner, proc_session, proc_setid
In order to allow the non-root user or non-root users who belong to a specific
group to run Cisco BAC, specify the name of the non-root user and the
group in the "User and Group" prompt that appears next.
Else, to run as root user, specify the name as "root" and group as "root" in
the "User and Group" prompt that appears next.
Step 2 Press Enter to continue.
This program prompts you to add user name and user group name.
------------------ User and Group -----------------------
Enter the name of the user [?,q] user1
Enter the name of the group [?,q] group1
Step 3 Specify the user name and group name to run Cisco BAC.
Step 4 Press Enter to continue.
The installation program prompts you to select one or more components.
Step 5 Enter y and press Enter at the CNR Extension Points prompt.
To skip installing the RDU, a DPE, and the KDC, enter n and press Enter.
For example:
-------------- Installation Components ------------
Regional Distribution Unit (RDU) (y/n)? [n] n
Device Provisioning Engine (DPE) (y/n)? [n] n
Cisco Network Registrar extension points (y/n)? [n] y
Key Distribution Center (KDC) (y/n)? [n] n
Note The installation program validates your CNR installation. You must install CNR 7.1.2.1 on your server. If the required version is not installed, the installation process terminates, and you must upgrade to the required CNR version before proceeding.
Step 6 Confirm the components that you want to install; enter y and press Enter.
The program prompts you to confirm the components that you want to install.
------------------ Confirmation --------------
Is this correct (y/n/q)? [y] y
Step 7 Enter y and press Enter to continue.
The home directory prompt appears.
Step 8 To accept the default directory, /opt/CSCObac, press Enter; or enter another directory.
For example:
-------------- Home Directory -----------
Home Directory [/opt/CSCObac]
The program then prompts you to confirm the directory.
Step 9 Press y and Enter to continue.
The data directory prompt appears.
Step 10 To accept the default directory, /var/CSCObac, press 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.
For example:
-------------- Data Directory -----------
DB Data Directory [/var/CSCObac] /var/disk0/CSCObac
Step 11 To confirm the directory, enter y 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. To accept the default information, press Enter; or enter alternative information.
For example:
------------------ CNR EP Info ---------------
Enter RDU IP Address or Hostname [bachost-rdu.example.com]
Enter RDU Listening Port [49187]
You are then prompted to enter the name of the extension point provisioning group.
Step 13 Enter the name of the CNR extension point group.
For example:
Enter the Cisco Network Registrar extension point provisioning group.
This a required field. The value you specify must contain only alphanumeric
characters without spaces. You can use the BAC command-line tool to
change this value after you complete this installation.
Enter Extension Point Provisioning Group [] group1
The program then asks you if you intend to provision PacketCable or voice technology devices.
Step 14 Enter y and press Enter if you are using PacketCable devices; press Enter if you are not.
For example:
Are you going to use devices that support PacketCable voice technology? [n]
If you enter n, omit Step 16 to 18. If you enter y, the program prompts you to enter several voice technology properties.
Step 15 The program prompts you to confirm the installation.
------------------ Confirmation --------------------
RDU IP Address: 10.10.10.10
Extention Point Provisioning Group: group1
Step 16 Enter details on the KDC realm name, the IP addresses for the primary and secondary DHCP servers, and the primary and secondary DNS servers.
For example:
------------------ PacketCable Configuration --------------
Enter KDC realm Name [CISCO.COM]
Enter IP Address for Primary DHCP [10.81.88.9]
Enter IP Address for Primary DNS [10.81.88.9]
Enter IP Address for Secondary DHCP []
Enter IP Address for Secondary DNS []
Step 17 Confirm the information; enter y and press Enter.
------------------- Confirmation ------------------------
Is this correct (y/n/q)? [y] y
Step 18 Press Enter to continue.
Step 19 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.
For example:
Enter the password to be used for authentication between BAC servers.
Enter the shared secret password [] <changeme>
Enter the shared secret password again [] <changeme>
Step 20 Press Enter.
The program displays the installation parameters you have selected.
Step 21 Enter y and press Enter to confirm the parameters, and install the CNR extensions.
For example:
------------------ Confirmation --------------------
RDU IP Address: 10.10.10.10
Extention Point Provisioning Group: default
Step 22 Press Enter to continue.
The program prompts you to confirm the installation.
Step 23 Enter y and press Enter.
For example:
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <CSCObac> [y,n,?] y
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 CNR server, you must configure the extensions. The procedure described in this section assumes that:
•The Cisco BAC component is installed in /opt/CSCObac.
•CNR is installed in /opt/nwreg2.
•The CNR username is admin and the password is changeme.
To configure extensions:
Step 1 Log in to the CNR 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
Step 3 To reload the CNR server, enter:
# /etc/init.d/nwreglocal stop
# /etc/init.d/nwreglocal start
Alternatively, to reload the DHCP server alone, enter:
# NR_HOME/local/usrbin/nrcmd -N admin -P changeme "dhcp reload"
Note Before you can use the CNR server, you must configure client classes, scope-selection tags, policies, and scopes. In an IPv6 environment, you must configure links and prefixes as well. See the User Guide for Cisco Network Registrar 7.1.
Validating Extensions
To validate the extensions installed on the CNR server, from the CNR Command Line Tool (nrcmd), run:
Note 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
file = libdexextension.so
file = libbprextensions.so
init-args = BPR_HOME=/opt/CSCObac,BPR_DATA=/var/CSCObac
entry = bprExecuteExtension
file = libbprextensions.so
init-entry = initExtPoint
Note The BPR_HOME and BPR_DATA values may be different in your installation.
Also in the nrcmd program, run:
nrcmd> dhcp listextensions
post-packet-decode: dexdropras
pre-packet-encode: prePacketEncode
pre-client-lookup: preClientLookup
Installing the KDC in Interactive Mode
You must install the KDC only when configuring a system to support voice technology operations.
Install the KDC on a Solaris 10 server that meets the requirements described in Operating System Requirements, page 1-2. For performance reasons, you should install the KDC on a separate server.
To install the KDC, complete the initial installation described in Installing Cisco Broadband Access Center. Then:
Step 1 To start the installation program in interactive mode, enter:
# pkgadd -d install-path/BAC_4101_SolarisK9/CSCObac.pkg CSCObac
where install-path specifies the complete path to the directory in which the BAC_4101_SolarisK9 directory has been created.
The installation program verifies that you have installed the required patches to the Solaris operating system. When the verification ends, welcome information appears.
Welcome to the Cisco Broadband Access Center for Cable 4.1.0.1 (BAC) installation
program. This installation program installs BAC 4.1.0.1 on your system.
The installer for Cisco Broadband Access Center for Cable 4.1.0.1 enables
non-root user, who has appropriate permission to run the product.
The non-root user can run the product, provided the user has the following
file_chown, file_link_any, file_owner, net_privaddr, proc_exec, proc_fork,
proc_info, proc_owner, proc_session, proc_setid
In order to allow the non-root user or non-root users who belong to a specific
group to run Cisco BAC, specify the name of the non-root user and the
group in the "User and Group" prompt that appears next.
Else, to run as root user, specify the name as "root" and group as "root" in
the "User and Group" prompt that appears next.
Step 2 Press Enter to continue.
The program prompts you to add user name and user group name.
------------------ User and Group -----------------------
Enter the name of the user [?,q] user1
Enter the name of the group [?,q] group1
Step 3 Specify the user name and group name to run Cisco BAC.
Step 4 Press Enter to continue.
The installation program prompts you to select one or more components.
Step 5 Enter y and press Enter at the KDC prompt.
To skip installing the RDU, a DPE, and the CNR extension points, enter n and press Enter.
For example:
-------------- Installation Components ------------
Regional Distribution Unit (RDU) (y/n)? [n] n
Device Provisioning Engine (DPE) (y/n)? [n] n
Cisco Network Registrar extension points (y/n)? [n] n
Key Distribution Center (KDC) (y/n)? [n] y
Step 6 Confirm the components that you want to install; enter y and press Enter.
The program prompts you to confirm the components that you want to install.
------------------ Confirmation --------------
Is this correct (y/n/q)? [y] y
Step 7 Enter y and press Enter to continue.
The home directory prompt appears.
Step 8 To accept the default directory, /opt/CSCObac, press Enter; or enter another directory.
For example:
-------------- Home Directory -----------
Home Directory [/opt/CSCObac]
A confirmation prompt appears.
Step 9 Enter y and press Enter.
The data directory prompt appears.
Step 10 To accept the default directory, /var/CSCObac, press Enter; or enter another directory.
For example:
-------------- Data Directory -----------
DB Data Directory [/var/CSCObac]
Step 11 To confirm, enter y and press Enter.
The KDC Configuration prompt appears.
Step 12 Enter the KDC interface address, the fully qualified domain name (FQDN), and the Kerberos realm name. The realm name should be consistent with the realm you give to the DPEs that belong to this provisioning group.
For example:
Note The warning in this example appears if there is more than one interface on your system.
------------------ KDC Configuration --------------
Key Distribution Center (KDC) Realm Name
Enter the Kerberos realm name for the KDC:
The realm name should be consistent with the realm you give to DPEs in this
provisioning group.
KDC Interface Address [10.10.10.22]:
KDC FQDN [bachost.example.com]:
Step 13 To confirm your entry and continue, enter y and press Enter.
The program prompts you to enter a password to generate the KDC service key.
Step 14 For each DPE, enter a password from 6 to 20 characters. The KDC service key mentioned here is one that you must generate on the DPE and the KDC to enable communication between the two components. To generate this service key, the password that you enter for the KDC must match the one that you enter for the corresponding DPE; otherwise, the DPE does not function.
For example:
Enter Password to generate Service-Key [] <changeme>
Enter Password to generate Service-Key again [] <changeme>
Note To generate the service key on the:
•DPE, use the service packetcable 1 registration kdc-service-key command from the DPE CLI. For details, see the Cisco Broadband Access Center DPE CLI Reference 4.1.
•KDC, use the KeyGen tool. For details, see the Cisco Broadband Access Center Administrator Guide 4.1.
Step 15 Press Enter.
Step 16 To confirm and continue, enter y and press Enter.
The program prompts you to enter the DPE FQDN.
Step 17 Enter the FQDN of the DPE, and press Enter.
For example:
Enter your DPE FQDN [] bac-dpe1.example.com
Step 18 Enter y and press Enter to confirm and continue.
Step 19 To add another DPE, enter y and press enter, or enter n and press Enter. The installation program uses the same voice technology shared key for all DPEs.
The program prompts you to confirm the installation.
Step 20 Enter y and press Enter.
For example:
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <CSCObac> [y,n,?] y
The installation proceeds, and displays the following message after successful installation:
Installation of <CSCObac> was successful.
Caution
After installing the KDC, install the licenses and the chain of certificates; otherwise, you cannot launch the KDC.
Installing Components in Noninteractive Mode
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 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, you must perform two steps, each of which is described in detail in subsequent sections:
1. Generate a response file, using:
# pkgask -r response -d install-path/BAC_4101_SolarisK9/CSCObac.pkg CSCObac
where install-path specifies the complete path to the directory in which the BAC_4101_SolarisK9 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 CNR extensions, you must generate a response file separately to install CNR extensions. You cannot use the response file that you generated to install the DPE to install CNR extensions.
2. After you generate the response file, start the installation program in noninteractive mode, using:
# pkgadd -n -r response -a BAC_4101_SolarisK9/bacadmin -d
BAC_4101_SolarisK9/CSCObac.pkg
For subsequent installations of the same component, you only need to run this pkgadd command.
If you have not enabled IPv6 on the machine, a warning message similar to the following appears:
Warning: IPv6 is not enabled on this system.
You can choose to enable IPv6 later, by running these commands:
# ifconfig intf inet6 plumb up
# touch /etc/hostname6.intf
where intf identifies the interface on which you want to enable IPv6.
Note Before you begin any of the procedures described in this section, complete the initial installation procedure described in Installing Cisco Broadband Access Center.
This section provides instructions on installing components in noninteractive mode:
•Installing the RDU in Noninteractive Mode
•Installing a DPE in Noninteractive Mode
•Installing CNR Extensions in Noninteractive Mode
•Installing the KDC in Noninteractive Mode
Installing the RDU in Noninteractive Mode
Install the RDU on a server running Solaris 10 that meets the requirements described in Operating System Requirements, page 1-2. 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 Installing Cisco Broadband Access Center. Then complete these procedures:
•Generating the Response File for the RDU
•Installing the RDU Using the Response File
Generating the Response File for the RDU
Use this procedure to generate a response file for RDU installation:
Step 1 To generate the response file, enter:
# pkgask -r response -d install-path/BAC_4101_SolarisK9/CSCObac.pkg CSCObac
where install-path specifies the complete path to the directory in which the BAC_4101_SolarisK9 directory has been created.
Note 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
where 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, welcome information appears.
Welcome to the Cisco Broadband Access Center for Cable 4.1.0.1 (BAC) installation
program. This installation program installs BAC 4.1.0.1 on your system.
The installer for Cisco Broadband Access Center for Cable 4.1.0.1 enables
non-root user, who has appropriate permission to run the product.
The non-root user can run the product, provided the user has the following
file_chown, file_link_any, file_owner, net_privaddr, proc_exec, proc_fork,
proc_info, proc_owner, proc_session, proc_setid
In order to allow the non-root user or non-root users who belong to a specific
group to run Cisco BAC, specify the name of the non-root user and the
group in the "User and Group" prompt that appears next.
Else, to run as root user, specify the name as "root" and group as "root" in
the "User and Group" prompt that appears next.
Step 2 Press Enter to continue.
The program prompts you to add user name and user group name.
------------------ User and Group -----------------------
Enter the name of the user [?,q] user1
Enter the name of the group [?,q] group1
Step 3 Press Enter to continue.
The installation program prompts you to select one or more components.
Step 4 Enter y and press Enter at the RDU prompt.
To skip installing a DPE, CNR extension points, and the KDC, enter n and press Enter. You can choose to install these components later.
For example:
-------------- Installation Components ------------
Regional Distribution Unit (RDU) (y/n)? [n] y
Device Provisioning Engine (DPE) (y/n)? [n] n
Cisco Network Registrar extension points (y/n)? [n] n
Key Distribution Center (KDC) (y/n)? [n] n
The program prompts you to confirm the components that you want to install.
Step 5 Enter y and press Enter to continue.
Cisco BAC performs lease query requests by binding to the IP addresses and ports that are described in Table 3-3.
Table 3-3 Lease Query Address for Binding
|
|
|
IPv4 |
Wildcard1 |
67 |
IPv6 |
Wildcard |
547 |
If the installation program detects that either of these ports is being used by another process, it recommends that you use the dynamic ports that the operating system selects.
For example:
DHCPv4/DHCPv6 lease query port(s) (Udp/67 and Udp/547) is in use.
Configuring the RDU to use a dynamic port for DHCPv4/DHCPv6 lease query.
If port 547 and port 67 are available, the installation program displays the home directory prompt.
Step 6 To accept the default directory, /opt/CSCObac, press Enter; or enter a different directory.
For example:
-------------- Home Directory -----------
Home Directory [/opt/CSCObac]
A confirmation prompt appears.
Step 7 To confirm the home directory location, enter y and press Enter.
The program prompts you to enter the data directory location.
Step 8 To accept the default directory, /var/CSCObac, press Enter; or enter a different directory.
For example:
-------------- Data Directory -----------
DB Data Directory [/var/CSCObac] /var/disk0/CSCObac
A confirmation prompt appears.
Step 9 To confirm the data directory location, enter y and press Enter.
The database log directory prompt appears.
Step 10 To accept the default directory, /var/CSCObac, press Enter; or enter another directory.
For example:
----------------- DB Log Directory -------------
DB Logs Directory [/var/CSCObac] /var/disk1/CSCObac
A confirmation prompt appears.
Step 11 To confirm the directory, enter y and press Enter to continue.
The program prompts you to enter the information related to the RDU, specifically the IP address and the listening port.
While the installation program obtains the IP address of the RDU automatically, you must enter a value for the listening port. The listening port is the port number that the RDU uses to communicate with other Cisco BAC components, such as DPEs and CNR extension points.
Step 12 To accept the default port number, 49187, press 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 DPE CLI Reference, 4.1.
For example:
------------------ RDU information ----------------
Enter the listening port of Regional Distribution Unit (RDU).
RDU Listening Port [49187]
Step 13 Confirm the listening port number; enter y and press Enter to continue.
The program prompts you to enter the shared secret password.
Step 14 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 CNR extension points in your network.
For example:
Enter the password to be used for authentication between BAC servers.
Enter the shared secret password [] <changeme>
Enter the shared secret password again [] <changeme>
Step 15 Press Enter to continue.
The program displays the parameters you have selected to install the RDU.
Step 16 Enter y and press Enter to confirm the installation parameters.
For example:
-------------------- Confirmation ----------------------
Home directory: /opt/CSCObac
DB Data directory: /var/CSCObac
DB Log directory: /var/CSCObac
The program prompts you to enter the HTTP port for the administrator user interface.
Step 17 To accept the default port, 8100, press Enter; or enter another port number.
For example:
------------------ Admin UI Information ----------------
Please enter Admin UI HTTP port [8100]
Step 18 Confirm the HTTP port; enter y and press Enter.
For example:
------------------ Confirmation --------------------
Is this correct (y/n/q)? [y]
The program prompts you to enter the HTTPS port for the user interface.
Step 19 To accept the default port, 8443, press Enter; or enter another port number.
For example:
Please enter Admin UI HTTPS port [8443]
Step 20 Confirm the HTTPS port; enter y and press Enter.
The program displays the parameters you have selected to install the administrator user interface.
Step 21 To confirm the parameters, enter y and press Enter.
For example:
--------------------- Confirmation --------------------
Installation directory: /opt/CSCObac/rdu
Is this correct (y/n/q)? [y]
Step 22 To continue, press Enter.
A message appears indicating that a response file has been created.
For example:
Response file </tmp/response> was created.
Processing of request script was successful.
Installing the RDU Using the Response File
After you generate the response file for the RDU, you can subsequently install the RDU using the following command:
# pkgadd -n -r response -a BAC_4101_SolarisK9/bacadmin -d BAC_4101_SolarisK9/CSCObac.pkg
CSCObac
Once you run the above command, the program installs the RDU. After successful installation, the following message appears:
# Linking /etc/rc2.d/S81bprAgent to /etc/init.d/bprAgent
# Linking /etc/rc1.d/K05bprAgent to /etc/init.d/bprAgent
# Linking /etc/rc0.d/K05bprAgent to /etc/init.d/bprAgent
Starting BAC Process Watchdog...
BAC Process Watchdog has started.
Registry update completed
Installation of <CSCObac> was successful.
Installing a DPE in Noninteractive Mode
Install the DPE on a server running Solaris 10 that meets the requirements described in Operating System Requirements, page 1-2.
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 kill the TFTP or ToD server, carry out the steps that the error message lists.
To install the DPE, complete the initial steps described in Installing Cisco Broadband Access Center. Then complete these procedures:
•Generating the Response File for the DPE
•Installing the DPE Using the Response File
Generating the Response File for the DPE
Use this procedure to generate a response file for DPE installation:
Step 1 To generate the response file, enter:
# pkgask -r response -d install-path/BAC_4101_SolarisK9/CSCObac.pkg CSCObac
where install-path specifies the complete path to the directory in which the BAC_4101_SolarisK9 directory has been created.
Note 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
where 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, welcome information appears.
Welcome to the Cisco Broadband Access Center for Cable 4.1.0.1 (BAC) installation
program. This installation program installs BAC 4.1.0.1 on your system.
The installer for Cisco Broadband Access Center for Cable 4.1.0.1 enables
non-root user, who has appropriate permission to run the product.
The non-root user can run the product, provided the user has the following
file_chown, file_link_any, file_owner, net_privaddr, proc_exec, proc_fork,
proc_info, proc_owner, proc_session, proc_setid
In order to allow the non-root user or non-root users who belong to a specific
group to run Cisco BAC, specify the name of the non-root user and the
group in the "User and Group" prompt that appears next.
Else, to run as root user, specify the name as "root" and group as "root" in
the "User and Group" prompt that appears next.
Step 2 Press Enter to continue.
The program prompts you to add user name and user group name.
------------------ User and Group -----------------------
Enter the name of the user [?,q] user1
Enter the name of the group [?,q] group1
Step 3 Press Enter to continue.
The installation program prompts you to select one or more components.
Step 4 Enter y and press Enter at the DPE prompt.
To skip installing the RDU, CNR extension points, and the KDC, enter n and press Enter.
For example:
-------------- Installation Components ------------
Regional Distribution Unit (RDU) (y/n)? [n] n
Device Provisioning Engine (DPE) (y/n)? [n] y
Cisco Network Registrar extension points (y/n)? [n] n
Key Distribution Center (KDC) (y/n)? [n] n
The program prompts you to confirm the components that you want to install.
Step 5 Enter y and press Enter to continue.
The home directory prompt appears.
Step 6 To accept the default directory, /opt/CSCObac, press Enter; or enter another directory.
For example:
-------------- Home Directory -----------
Home Directory [/opt/CSCObac]
Step 7 Confirm the directory location; enter y and press Enter.
The data directory prompt appears.
Step 8 To accept the default directory, /var/CSCObac, press Enter; or enter another directory.
For example:
-------------- Data Directory -----------
DB Data Directory [/var/CSCObac]
Step 9 Confirm the directory location; enter y and press Enter.
The program prompts you to enter the shared secret password.
Step 10 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, and CNR extension points in your network.
For example:
Enter the password to be used for authentication between BAC servers.
Enter the shared secret password [] <changeme>
Enter the shared secret password again [] <changeme>
Step 11 Reenter the password for confirmation, and press Enter.
A message appears indicating that a response file has been created.
For example:
Response file </tmp/response> was created.
Processing of request script was successful.
Installing the DPE Using the Response File
After you generate the response file for the DPE, you can subsequently install DPEs using the following command:
# pkgadd -n -r response -a BAC_4101_SolarisK9/bacadmin -d BAC_4101_SolarisK9/CSCObac.pkg
CSCObac
Once you run the above command, the program installs the DPE. After successful installation, the following message appears:
# Linking /etc/rc2.d/S81bprAgent to /etc/init.d/bprAgent
# Linking /etc/rc1.d/K05bprAgent to /etc/init.d/bprAgent
# Linking /etc/rc0.d/K05bprAgent to /etc/init.d/bprAgent
Starting BAC Process Watchdog...
BAC Process Watchdog has started.
Registry update completed
Installation of <CSCObac> was successful.
Installing CNR Extensions in Noninteractive Mode
Install Cisco BAC extensions on all CNR 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 CNR server to use a static IP address.
Before you install CNR extensions, complete the initial installation described in Installing Cisco Broadband Access Center. Also, ensure that CNR is running. Then, complete the procedures described in this section:
•Generating the Response File for CNR Extensions
•Installing CNR Extensions Using the Response File
Generating the Response File for CNR Extensions
Use this procedure to generate a response file to install CNR extensions:
Step 1 To generate the response file, enter:
# pkgask -r response -d install-path/BAC_4101_SolarisK9/CSCObac.pkg CSCObac
where install-path specifies the complete path to the directory in which the BAC_4101_SolarisK9 directory has been created.
Note 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
where 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, welcome information appears.
Welcome to the Cisco Broadband Access Center for Cable 4.1.0.1 (BAC) installation
program. This installation program installs BAC 4.1.0.1 on your system.
The installer for Cisco Broadband Access Center for Cable 4.1.0.1 enables
non-root user, who has appropriate permission to run the product.
The non-root user can run the product, provided the user has the following
file_chown, file_link_any, file_owner, net_privaddr, proc_exec, proc_fork,
proc_info, proc_owner, proc_session, proc_setid
In order to allow the non-root user or non-root users who belong to a specific
group to run Cisco BAC, specify the name of the non-root user and the
group in the "User and Group" prompt that appears next.
Else, to run as root user, specify the name as "root" and group as "root" in
the "User and Group" prompt that appears next.
Step 2 Press Enter to continue.
The program prompts you to add user name and user group name.
------------------ User and Group -----------------------
Enter the name of the user [?,q] user1
Enter the name of the group [?,q] group1
Step 3 Press Enter to continue.
The installation program prompts you to select one or more components.
Step 4 Enter y and press Enter at the CNR Extension Points prompt.
To skip installing the RDU, a DPE, and the KDC, enter n and press Enter.
For example:
-------------- Installation Components ------------
Regional Distribution Unit (RDU) (y/n)? [n] n
Device Provisioning Engine (DPE) (y/n)? [n] n
Cisco Network Registrar extension points (y/n)? [n] y
Key Distribution Center (KDC) (y/n)? [n] n
Note The installation program validates your CNR installation. You must install CNR 7.1.2.1 on your server. If the required version is not installed, the installation process terminates, and you must upgrade to the required CNR version before proceeding.
The program prompts you to confirm the components that you want to install.
Step 5 Enter y and press Enter to continue.
The home directory prompt appears.
Step 6 To accept the default directory, /opt/CSCObac, press Enter; or enter another directory.
For example:
-------------- Home Directory -----------
Home Directory [/opt/CSCObac]
The program then prompts you to confirm the directory.
Step 7 Press y and Enter to continue.
The data directory prompt appears.
Step 8 To accept the default directory, /var/CSCObac, press 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.
For example:
-------------- Data Directory -----------
DB Data Directory [/var/CSCObac] /var/disk0/CSCObac
Step 9 To confirm the directory, enter y and press Enter.
The program prompts you to enter information on the RDU required to install the extensions.
Step 10 Enter the IP address (or hostname) and the listening port of the host on which you have installed the RDU. To accept the default information, press Enter; or enter alternative information.
For example:
------------------ CNR EP Info ---------------
Enter RDU IP Address or Hostname [bachost-rdu.example.com]
Enter RDU Listening Port [49187]
You are then prompted to enter the name of the extension point provisioning group.
Step 11 Enter the name of the CNR extension point group.
For example:
Enter the Cisco Network Registrar extension point provisioning group.
This a required field. The value you specify must contain only alphanumeric
characters without spaces. You can use the BAC command-line tool to
change this value after you complete this installation.
Enter Extension Point Provisioning Group [] group1
The program then asks you if you intend to provision PacketCable or voice technology devices.
Step 12 Enter y and press Enter if you are using PacketCable devices; press Enter if you are not.
For example:
Are you going to use devices that support PacketCable voice technology? [n]
If you enter n, omit Step 16 till Step 20. If you enter y, the program prompts you to enter several voice technology properties.
Step 13 The program displays the installation parameters you have selected, confirm the information.
For example:
------------------ Confirmation --------------------
RDU IP Address: 10.10.10.10
Extention Point Provisioning Group: group1
Step 14 Press Enter to confirm the parameters, and install the CNR extensions.
Step 15 Confirm the information; enter y and press Enter.
Step 16 Press Enter to continue.
Step 17 Enter details on the KDC realm name, the IP addresses for the primary and secondary DHCP servers, and the primary and secondary DNS servers.
For example:
Note The warning in this example appears if there is more than one interface on your system.
------------------ PacketCable Configuration --------------
Enter KDC realm Name [EXAMPLE.COM]
Enter IP Address for Primary DHCP [10.10.10.1]
Enter IP Address for Primary DNS [10.10.10.3]
Enter IP Address for Secondary DHCP [10.10.10.2]
Enter IP Address for Secondary DNS [10.10.10.4]
Step 18 Press Enter.
Step 19 The program displays the PacketCable Configuration parameters you have selected, confirm the information.
Step 20 Enter y and press Enter.
Step 21 Press Enter to continue.
Step 22 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.
For example:
Enter the password to be used for authentication between BAC servers.
Enter the shared secret password [] <changeme>
Enter the shared secret password again [] <changeme>
Step 23 To continue, press Enter.
A message appears indicating that a response file has been created.
For example:
Response file </tmp/response> was created.
Processing of request script was successful.
Installing CNR Extensions Using the Response File
After you generate the response file for CNR extensions, you can subsequently install extensions using the following command:
# pkgadd -n -r response -a BAC_4101_SolarisK9/bacadmin -d BAC_4101_SolarisK9/CSCObac.pkg
CSCObac
Once you run the above command, the program installs CNR extensions. After successful installation, the following message appears:
Starting BAC Process Watchdog...
Installation of <CSCObac> was successful.
After you install the extensions, you must configure and validate them. For details, see Configuring Extensions, and Validating Extensions.
Installing the KDC in Noninteractive Mode
You must install the KDC only when configuring a system to support voice technology operations.
Install the KDC on a Solaris 10 server that meets the requirements described in Operating System Requirements, page 1-2. For performance reasons, you should install the KDC on a separate server.
To install the Key Distribution Center (KDC), complete the initial installation described in Installing Cisco Broadband Access Center. Then complete the procedures described in this section:
•Generating the Response File for the KDC
•Installing the KDC Using the Response File
Generating the Response File for the KDC
Use this procedure to generate a response file for KDC installation:
Step 1 To generate the response file, enter:
# pkgask -r response -d install-path/BAC_4101_SolarisK9/CSCObac.pkg CSCObac
where install-path specifies the complete path to the directory in which the BAC_4101_SolarisK9 directory has been created.
Note 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
where 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, welcome information appears.
Welcome to the Cisco Broadband Access Center for Cable 4.1.0.1 (BAC) installation
program. This installation program installs BAC 4.1.0.1 on your system.
The installer for Cisco Broadband Access Center for Cable 4.1.0.1 enables
non-root user, who has appropriate permission to run the product.
The non-root user can run the product, provided the user has the following
file_chown, file_link_any, file_owner, net_privaddr, proc_exec, proc_fork,
proc_info, proc_owner, proc_session, proc_setid
In order to allow the non-root user or non-root users who belong to a specific
group to run Cisco BAC, specify the name of the non-root user and the
group in the "User and Group" prompt that appears next.
Else, to run as root user, specify the name as "root" and group as "root" in
the "User and Group" prompt that appears next.
Step 2 Press Enter to continue.
The program prompts you to add user name and user group name.
------------------ User and Group -----------------------
Enter the name of the user [?,q] user1
Enter the name of the group [?,q] group1
Step 3 Press Enter to continue.
The installation program prompts you to select one or more components.
Step 4 Enter y and press Enter at the KDC prompt.
To skip installing the RDU, a DPE, and the CNR extension points, enter n and press Enter.
For example:
-------------- Installation Components ------------
Regional Distribution Unit (RDU) (y/n)? [n] n
Device Provisioning Engine (DPE) (y/n)? [n] n
Cisco Network Registrar extension points (y/n)? [n] n
Key Distribution Center (KDC) (y/n)? [n] y
Step 5 Confirm the component(s) that you want to install; enter y and press Enter.
The home directory prompt appears.
Step 6 To accept the default directory, /opt/CSCObac, press Enter; or enter another directory.
For example:
-------------- Home Directory -----------
Home Directory [/opt/CSCObac]
A confirmation prompt appears.
Step 7 Enter y and press Enter.
The data directory prompt appears.
Step 8 To accept the default directory, /var/CSCObac, press Enter; or enter another directory.
For example:
-------------- Data Directory -----------
DB Data Directory [/var/CSCObac]
Step 9 To confirm, enter y and press Enter.
The KDC Configuration prompt appears.
Step 10 Enter the KDC interface address, the fully qualified domain name (FQDN), and the Kerberos realm name. The realm name should be consistent with the realm you give to the DPEs that belong to this provisioning group.
For example:
Note The warning in this example appears if there is more than one interface on your system.
------------------ KDC Configuration --------------
Key Distribution Center (KDC) Realm Name
Enter the Kerberos realm name for the KDC:
The realm name should be consistent with the realm you give to DPEs in this
provisioning group.
KDC Interface Address [10.10.10.22]:
KDC FQDN [bachost.example.com]:
Step 11 To confirm your entry and continue, enter y and press Enter.
The program prompts you to enter a password to generate the KDC service key.
Step 12 For each DPE, enter a password from 6 to 20 characters. The KDC service key mentioned here is one that you must generate on the DPE and the KDC to enable communication between the two components. To generate this service key, the password that you enter for the KDC must match the one that you enter for the corresponding DPE; otherwise, the DPE does not function.
For example:
Enter Password to generate Service-Key [] <changeme>
Enter Password to generate Service-Key again [] <changeme>
Note To generate the service key on the:
•DPE, use the service packetcable 1 registration kdc-service-key command from the DPE CLI. For details, see the Cisco Broadband Access Center DPE CLI Reference 4.1.
•KDC, use the KeyGen tool. For details, see the Cisco Broadband Access Center Administrator Guide 4.1.
Step 13 Press Enter.
Step 14 To confirm and continue, enter y and press Enter.
The program prompts you to enter the DPE FQDN.
Step 15 Enter the FQDN of the DPE.
For example:
Enter your DPE FQDN [] bac-dpe1.example.com
Step 16 Press Enter to confirm and continue.
Step 17 To add another DPE, enter y and press enter, or enter n and press Enter. The installation program uses the same voice technology shared key for all DPEs.
A message appears indicating that a response file has been created.
For example:
Response file </tmp/response> was created.
Processing of request script was successful.
Installing the KDC Using the Response File
After you generate the response file for the KDC, you can subsequently install the KDC using the following command:
# pkgadd -n -r response -a BAC_4101_SolarisK9/bacadmin -d BAC_4101_SolarisK9/CSCObac.pkg
CSCObac
Once you run the above command, the program installs the KDC. After successful installation, the following message appears:
# Linking /etc/rc2.d/S81bprAgent to /etc/init.d/bprAgent
# Linking /etc/rc1.d/K05bprAgent to /etc/init.d/bprAgent
# Linking /etc/rc0.d/K05bprAgent to /etc/init.d/bprAgent
Starting BAC Process Watchdog...
BAC Process Watchdog has started.
Installation of <CSCObac> was successful.
Adding Components
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 largely 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 proceeding to add components, ensure that all the components belong to the Cisco BAC 4.1.0.1 version.
When the installation program detects the presence of one component on your system, it does not allow you the option of adding that particular component. It prompts you to add or install other components only.
For example, if you installed a DPE on a system and then rerun the installation program, the program does not give you the option of installing the DPE.
Regional Distribution Unit (RDU) (y/n)? [n] n
Cisco Network Registrar extension points (y/n)? [n] n
Key Distribution Center (KDC) (y/n)? [n] n
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.
Note You cannot reinstall a component that you have already installed. If you must carry out a reinstallation, first uninstall that component, and then install it again.
Upgrading Cisco Broadband Access Center
This section describes how to upgrade a Cisco Broadband Access Center for Cable (Cisco BAC) 2.7.1.x and 4.0.1.x installation to Cisco Broadband Access Center 4.1.0.1.
This Cisco BAC release supports online migration, using which you can migrate one server at a time without disrupting the entire Cisco BAC deployment.
Before upgrading to Cisco BAC 4.1.0.1, ensure that you obtain the license file that this release supports. Once the upgrade is complete, the installation program deletes all existing license keys. You must then install the license file that Cisco BAC 4.1.0.1 supports, using the administrator user interface. For details on obtaining and installing the license file, see the Release Notes for the Cisco Broadband Access Center 4.1.0.1.
You must stop the process watchdog (bprAgent) before upgrading. Once the upgrade is complete, Cisco BAC does not restart the process watchdog automatically. You must migrate your existing database first before starting the watchdog. For details on migration process, refer Migrating the RDU Database.
When upgrading from Cisco BAC 2.7.1.x or Cisco BAC 4.0.1.x to Cisco BAC 4.1.0.1, you must enter a new target location for these directories:
–Data (BPR_DATA)
–Database logs (BPR_DBLOG)
Note License is required to upgrade Cisco BAC 2.7.1.x to Cisco BAC 4.1.0.1.
The Cisco BAC upgrade procedure requires that you upgrade the components in the sequence recommended in below-mentioned sections. Performing the upgrade in any other sequence results in error during provisioning.
1. Before You Begin
2. Upgrading the RDU
3. Upgrading the DPE
4. Upgrading CNR Extensions
5. Upgrading the KDC
Before You Begin
Before upgrading Cisco BAC components, ensure that you backup the RDU database files. Throttling limits the I/O bandwidth used by the DB with backup utility. 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 to sleep mode till the rate comes down.
Note It is recommended to use the throttle option always since it is not an I/O intensive operation.
To back up the RDU database, run the backupDb.sh script in the BPR_HOME/rdu/bin directory.
For example:
# backupDb.sh /var/backup -throttle 500/opt/
where /var/backup identifies the database backup directory.
In this example, all backup database files are stored in a directory called /var/backup/rdu-backup-20071116-031028. The last subdirectory (rdu-backup-20070316-111028) is automatically created with a current time stamp.
Note The time-stamped subdirectory format is rdu-backup-yyyyMMdd-HHmmss. In this example, the subdirectory would be rdu-backup-20071116-031028, meaning that the directory contains a backup that was started at 3:10:28 a.m. on November 16, 2007.
For additional information on using the backupDb.sh tool, see the Cisco Broadband Access Center Administrator Guide 4.1.
Upgrading the RDU
Before upgrading the RDU, we recommend that you archive your files in the BPR_HOME/rdu/conf directory.
Also, stop the bprAgent before upgrade using following command:
/etc/init.d/bprAgent stop
You can upgrade the RDU from:
Cisco BAC 2.7.1.x to Cisco BAC 4.1.0.1
Cisco BAC 4.0.1.x to Cisco BAC 4.1.0.1
Cisco BAC 2.7.1.x to Cisco BAC 4.1.0.1
Step 1 Disable access to the RDU from the operations support system.
Step 2 Back up the existing RDU database, using the backupDb.sh tool. For details, see the Cisco Broadband Access Center Administrator Guide 4.1.
For example:
# /opt/CSCObpr/rdu/bin/backupDb.sh -nosubdir /disk1/backup
•-nosubdir—Disables the automatic creation of a subdirectory. If you do not use this option, a subdirectory is created and reported to the console.
•/disk1/backup—Identifies the location for the database backup files.
Step 3 Verify if the database has been backed up by checking the history.log file, which resides in the BPR_DATA directory.
Step 4 Restore the database that you have backed up to a consistent state, using the recoverDb.sh tool. For details, see the Cisco Broadband Access Center Administrator Guide 4.1.
For example:
# /opt/CSCObpr/rdu/bin/recoverDb.sh /disk1/backup
where /disk1/backup identifies the location of the database backup files.
Step 5 Copy the backed-up database to a safe location.
Step 6 If the operating system (OS) on which the existing Cisco BAC version runs does not meet the requirements for the 4.1.0.1 release, upgrade the OS.
Step 7 Install the 4.1.0.1 version.
For example:
# pkgadd -d BAC_4101_SolarisK9/CSCObac.pkg -a BAC_4101_SolarisK9/bacadmin CSCObac
When upgrading from 2.7.1.x, the installation program prompts you to enter locations for the:
•Home directory (BPR_HOME)
Note The home directory will be replaced if installation is done on the existing Cisco BAC BPR_HOME directory.
•Database directory (BPR_DATA)
Note The BPR_DATA directory should be removed manually after upgrade.
•Database logs directory (BPR_DBLOG)
It then upgrades the necessary libraries and property files but leaves your RDU database intact.
Step 8 After the installation is complete, upgrade the RDU database by following the steps described in Migrating the RDU Database.
Cisco BAC 4.0.1.x to Cisco BAC 4.1.0.1
Step 1 Disable access to the RDU from the operations support system.
Step 2 Back up the existing RDU database, using the backupDb.sh tool. For details, see the Cisco Broadband Access Center Administrator Guide 4.1.
For example:
# /opt/CSCObac/rdu/bin/backupDb.sh -nosubdir /disk1/backup
•-nosubdir—Disables the automatic creation of a subdirectory. If you do not use this option, a subdirectory is created and reported to the console.
•/disk1/backup—Identifies the location for the database backup files.
Step 3 Verify if the database has been backed up by checking the history.log file, which resides in the BPR_DATA directory.
Step 4 Restore the database that you have backed up to a consistent state, using the recoverDb.sh tool. For details, see the Cisco Broadband Access Center Administrator Guide 4.1.
For example:
# /opt/CSCObac/rdu/bin/recoverDb.sh /disk1/backup
where /disk1/backup identifies the location of the database backup files.
Step 5 Copy the backed-up database to a safe location.
Step 6 If the operating system (OS) on which the existing Cisco BAC version runs does not meet the requirements for the 4.1.0.1 release, upgrade the OS.
Step 7 To install the 4.1.0.1 version, run the pkgadd -d BAC_4101_SolarisK9/CSCObac.pkg -a BAC_4101_SolarisK9/bacadmin CSCObac command.
Output similar to the following appears. The output has been trimmed for brevity.
Processing package instance <CSCObac> from </var/CSCObac.pkg>
Cisco BAC product(sparc) 4.1.0.1
Welcome to the Cisco Broadband Access Center for Cable 4.1.0.1 (BAC) installation
program. This installation program installs BAC 4.1.0.1 on your system.
The installer for Cisco Broadband Access Center for Cable 4.1.0.1 enables
non-root user, who has appropriate permission to run the product.
The non-root user can run the product, provided the user has the following
file_chown, file_link_any, file_owner, net_privaddr, proc_exec, proc_fork,
proc_info, proc_owner, proc_session, proc_setid
In order to allow the non-root user or non-root users who belong to a specific
group to run Cisco BAC, specify the name of the non-root user and the
group in the "User and Group" prompt that appears next.
Else, to run as root user, specify the name as "root" and group as "root" in
the "User and Group" prompt that appears next.
Press Enter to Continue or q to Quit:
Step 8 Press Enter to continue.
The program prompts you to add user name and user group name.
Step 9 Specify the user name and group name to run Cisco BAC.
------------------ User and Group -----------------------
Enter the name of the user [?,q] user1
Enter the name of the group [?,q] group1
Step 10 Press Enter to continue.
The program prompts you to confirm upgrading.
Step 11 To confirm that you want to upgrade; enter y and press Enter.
Upgrading BAC from 4.0.1.7 to 4.1.0.1. Are you sure? [n]: y
Step 12 To accept the default directory, /opt/CSCObac, press Enter; or enter another directory. The program prompt also display the available disk space.
For example:
-------------- Home Directory -----------
Home Directory [/opt/CSCObac]
Available disk space for /opt/CSCObac is 3458249 kilobytes.
Step 13 Confirm the directory location; enter y and press Enter.
The data directory prompt appears.
Step 14 To accept the default directory, /var/CSCObac, press Enter; or enter another directory. The program prompt also display the available disk space.
For example:
-------------- Data Directory -----------
DB Data Directory [/var/CSCObac]
Available disk space for /var/CSCObac is 2614226 kilobytes.
Step 15 Confirm the directory location; enter y and press Enter.
Step 16 The program begins the installation process. After successful installation, the following message appears:
Installing Cisco BAC product as <CSCObac>
Installation of <CSCObac> was successful.
Step 17 To verify if the version information indicates Cisco BAC release 4.1.0.1, enter:
# pkgparam CSCObac VERSION
Step 18 You must manually restart the DPE process to finish the upgrade process.
For example, from the command line, run:
# /etc/init.d/bprAgent start
It then upgrades the necessary libraries and property files but leaves your RDU database intact.
Upgrading the DPE
Before upgrading your DPE, we recommend that you archive your files in the BPR_HOME/dpe/conf directory.
Also, stop the bprAgent before upgrade using following command:
/etc/init.d/bprAgent stop
You can upgrade the DPE from:
Cisco BAC 2.7.1.x to Cisco BAC 4.1.0.1
Cisco BAC 2.7.1.x to Cisco BAC 4.1.0.1
Step 1 Run the pkgadd -d BAC_4101_SolarisK9/CSCObac.pkg -a BAC_4101_SolarisK9/bacadmin CSCObac command.
Output similar to the following appears. The output has been trimmed for brevity.
Processing package instance <CSCObac> from </var/CSCObac.pkg>
Welcome to the Cisco Broadband Access Center for Cable 4.1.0.1 (BAC) installation
program. This installation program installs BAC 4.1.0.1 on your system.
The installer for Cisco Broadband Access Center for Cable 4.1.0.1 enables
non-root user, who has appropriate permission to run the product.
The non-root user can run the product, provided the user has the following
file_chown, file_link_any, file_owner, net_privaddr, proc_exec, proc_fork,
proc_info, proc_owner, proc_session, proc_setid
In order to allow the non-root user or non-root users who belong to a specific
group to run Cisco BAC, specify the name of the non-root user and the
group in the "User and Group" prompt that appears next.
Else, to run as root user, specify the name as "root" and group as "root" in
the "User and Group" prompt that appears next.
Press Enter to Continue or q to Quit:
Upgrading BAC from 2.7.1.2 to 4.1.0.1. Are you sure? [n]: y
Stopping BAC Process Watchdog...
File installation completed.
Installation of <CSCObac> was successful.
Step 2 To verify if the version information indicates Cisco BAC release 4.1.0.1, enter:
# pkgparam CSCObac VERSION
Step 3 You must manually restart the DPE process to finish the upgrade process.
For example, from the command line, run:
# /etc/init.d/bprAgent start dpe
Cisco BAC 4.0.1.x to Cisco BAC 4.1.0.1
Step 1 Run the pkgadd -d BAC_4101_SolarisK9/CSCObac.pkg -a BAC_4101_SolarisK9/bacadmin CSCObac command.
Output similar to the following appears. The output has been trimmed for brevity.
Processing package instance <CSCObac> from </var/CSCObac.pkg>
Cisco BAC product(sparc) 4.1.0.1
Welcome to the Cisco Broadband Access Center for Cable 4.1.0.1 (BAC) installation
program. This installation program installs BAC 4.1.0.1 on your system.
The installer for Cisco Broadband Access Center for Cable 4.1.0.1 enables
non-root user, who has appropriate permission to run the product.
The non-root user can run the product, provided the user has the following
file_chown, file_link_any, file_owner, net_privaddr, proc_exec, proc_fork,
proc_info, proc_owner, proc_session, proc_setid
In order to allow the non-root user or non-root users who belong to a specific
group to run Cisco BAC, specify the name of the non-root user and the
group in the "User and Group" prompt that appears next.
Else, to run as root user, specify the name as "root" and group as "root" in
the "User and Group" prompt that appears next.
Press Enter to Continue or q to Quit:
Step 2 Press Enter to continue.
The program prompts you to add user name and user group name.
Step 3 Specify the user name and group name to run Cisco BAC.
------------------ User and Group -----------------------
Enter the name of the user [?,q] user1
Enter the name of the group [?,q] group1
Step 4 Press Enter to continue.
The program prompts you to confirm upgrading.
Step 5 To confirm that you want to upgrade; enter y and press Enter.
Upgrading BAC from 4.0.1.7 to 4.1.0.1. Are you sure? [n]: y
Step 6 To accept the default directory, /opt/CSCObac, press Enter; or enter another directory. The program prompt also display the available disk space.
For example:
-------------- Home Directory -----------
Home Directory [/opt/CSCObac]
Available disk space for /opt/CSCObac is 3458249 kilobytes.
Step 7 Confirm the directory location; enter y and press Enter.
The data directory prompt appears.
Step 8 To accept the default directory, /var/CSCObac, press Enter; or enter another directory. The program prompt also display the available disk space.
For example:
-------------- Data Directory -----------
DB Data Directory [/var/CSCObac]
Available disk space for /var/CSCObac is 2614226 kilobytes.
Step 9 Confirm the directory location; enter y and press Enter.
Step 10 The program begins the installation process. After successful installation, the following message appears:
Installing Cisco BAC product as <CSCObac>
Installation of <CSCObac> was successful.
Step 11 To verify if the version information indicates Cisco BAC release 4.1.0.1, enter:
# pkgparam CSCObac VERSION
Step 12 You must manually restart the DPE process to finish the upgrade process.
For example, from the command line, run:
# /etc/init.d/bprAgent start
Upgrading CNR Extensions
Before upgrading CNR extensions, we recommend that you archive your files in the BPR_HOME/cnr_ep/conf directory.
Also stop the DHCP server and disable the CNR extension points before upgrade using following commands respectively:
/etc/init.d/nwreglocal Stop
/opt/nwreg2/local/usrbin/nrcmd -s < /opt/CSCObac/cnr_ep/bin/bpr_cnr_disable_extpts.nrcmd
To upgrade the CNR extensions from:
You can upgrade the DPE from:
Cisco BAC 2.7.1.x to Cisco BAC 4.1.0.1
Cisco BAC 2.7.1.x to Cisco BAC 4.1.0.1
Step 1 Run the pkgadd -d BAC_4101_SolarisK9/CSCObac.pkg -a BAC_4101_SolarisK9/bacadmin CSCObac command.
Step 2 Enable the CNR extension points and restart the DHCP server using following commands respectively:
/opt/nwreg2/local/usrbin/nrcmd -s < /opt/CSCObac/cnr_ep/bin/bpr_cnr_enable_extpts.nrcmd
/etc/init.d/nwreglocal Start
The upgrade script automatically copies the upgraded extension point files to the required directories. When complete, it prompts you to restart the CNR Server Agent.
Step 3 To verify if the output information indicates Cisco BAC release 4.1.0.1, enter:
# pkgparam CSCObac VERSION
Step 4 Go to the BPR_HOME/lib directory. If the upgrade was successful, the directory content appears similar to the list of installed files for the DPE upgrade with the addition of the libbprextensions-2x.so file.
Step 5 If a second check is required to verify upgrade success, go to the CNR_HOME/extensions/dhcp/dex directory and verify that these files appear:
-rwxr-xr-x 1 root bin 60904 Oct 29 2003 libdexextension.so
-rwxr-xr-x 1 root other 1530628 Jul 22 12:43 libbprextensions-2x.so
-rwxr-xr-x 1 root other 1560748 Aug 11 12:49 libbprextensions.so
Depending on the components installed, the directory content shown in this procedure may differ from the output featured above.
Cisco BAC 4.0.1.x to Cisco BAC 4.1.0.1
Step 1 Run the pkgadd -d BAC_4101_SolarisK9/CSCObac.pkg -a BAC_4101_SolarisK9/bacadmin CSCObac command.
Step 2 Also stop the DHCP server and disable the CNR extension points before upgrade using following commands respectively:
/opt/nwreg2/local/usrbin/nrcmd -s < /opt/CSCObac/cnr_ep/bin/bpr_cnr_enable_extpts.nrcmd
/etc/init.d/nwreglocal Start
Step 3 Output similar to the following appears. The output has been trimmed for brevity.
Processing package instance <CSCObac> from </var/CSCObac.pkg>
Cisco BAC product(sparc) 4.1.0.1
Welcome to the Cisco Broadband Access Center for Cable 4.1.0.1 (BAC) installation
program. This installation program installs BAC 4.1.0.1 on your system.
The installer for Cisco Broadband Access Center for Cable 4.1.0.1 enables
non-root user, who has appropriate permission to run the product.
The non-root user can run the product, provided the user has the following
file_chown, file_link_any, file_owner, net_privaddr, proc_exec, proc_fork,
proc_info, proc_owner, proc_session, proc_setid
In order to allow the non-root user or non-root users who belong to a specific
group to run Cisco BAC, specify the name of the non-root user and the
group in the "User and Group" prompt that appears next.
Else, to run as root user, specify the name as "root" and group as "root" in
the "User and Group" prompt that appears next.
Press Enter to Continue or q to Quit:
Step 4 Press Enter to continue.
The program prompts you to add user name and user group name.
Step 5 Specify the user name and group name to run Cisco BAC.
------------------ User and Group -----------------------
Enter the name of the user [?,q] user1
Enter the name of the group [?,q] group1
Step 6 Press Enter to continue.
The program prompts you to confirm upgrading.
Step 7 To confirm that you want to upgrade; enter y and press Enter.
Upgrading BAC from 4.0.1.5 to 4.1.0.1. Are you sure? [n]: y
Step 8 To accept the default directory, /opt/CSCObac, press Enter; or enter another directory. The program prompt also display the available disk space.
For example:
-------------- Home Directory -----------
Home Directory [/opt/CSCObac]
Available disk space for /opt/CSCObac is 3458249 kilobytes.
Step 9 Confirm the directory location; enter y and press Enter.
The data directory prompt appears.
Step 10 To accept the default directory, /var/CSCObac, press Enter; or enter another directory. The program prompt also display the available disk space.
For example:
-------------- Data Directory -----------
DB Data Directory [/var/CSCObac]
Available disk space for /var/CSCObac is 2614226 kilobytes.
Step 11 Confirm the directory location; enter y and press Enter.
Step 12 The program begins the installation process. After successful installation, the following message appears:
Installing Cisco BAC product as <CSCObac>
Installation of <CSCObac> was successful.
Step 13 To verify if the version information indicates Cisco BAC release 4.1.0.1, enter:
# pkgparam CSCObac VERSION
Upgrading the KDC
To upgrade the KDC from:
Cisco BAC 2.7.1.x to Cisco BAC 4.1.0.1
Cisco BAC 2.7.1.x to Cisco BAC 4.1.0.1
Step 1 Run the pkgadd -d BAC_4101_SolarisK9/CSCObac.pkg -a BAC_4101_SolarisK9/bacadmin CSCObac command.
Step 2 Manually start the Cisco BAC process watchdog to complete the upgrade process.
Step 3 To verify if the output information indicates Cisco BAC release 4.1.0.1, enter:
# pkgparam CSCObac VERSION
Note The Cisco BAC 4.1.0.1 KDC requires a new license. Before you start the Cisco BAC process watchdog, ensure that the correct license and certificates are installed.
Cisco BAC 4.0.1.x to Cisco BAC 4.1.0.1
Step 1 Run the pkgadd -d BAC_4101_SolarisK9/CSCObac.pkg -a BAC_4101_SolarisK9/bacadmin CSCObac command.
Output similar to the following appears. The output has been trimmed for brevity.
Processing package instance <CSCObac> from </var/CSCObac.pkg>
Cisco BAC product(sparc) 4.1.0.1
Welcome to the Cisco Broadband Access Center for Cable 4.1.0.1 (BAC) installation
program. This installation program installs BAC 4.1.0.1 on your system.
The installer for Cisco Broadband Access Center for Cable 4.1.0.1 enables
non-root user, who has appropriate permission to run the product.
The non-root user can run the product, provided the user has the following
file_chown, file_link_any, file_owner, net_privaddr, proc_exec, proc_fork,
proc_info, proc_owner, proc_session, proc_setid
In order to allow the non-root user or non-root users who belong to a specific
group to run Cisco BAC, specify the name of the non-root user and the
group in the "User and Group" prompt that appears next.
Else, to run as root user, specify the name as "root" and group as "root" in
the "User and Group" prompt that appears next.
Press Enter to Continue or q to Quit:
Step 2 Press Enter to continue.
The program prompts you to add user name and user group name.
Step 3 Specify the user name and group name to run Cisco BAC.
------------------ User and Group -----------------------
Enter the name of the user [?,q] user1
Enter the name of the group [?,q] group1
Step 4 Press Enter to continue.
The program prompts you to confirm upgrading.
Step 5 To confirm that you want to upgrade; enter y and press Enter.
Upgrading BAC from 4.0.1.7 to 4.1.0.1. Are you sure? [n]: y
Step 6 To accept the default directory, /opt/CSCObac, press Enter; or enter another directory. The program prompt also display the available disk space.
For example:
-------------- Home Directory -----------
Home Directory [/opt/CSCObac]
Available disk space for /opt/CSCObac is 3458249 kilobytes.
Step 7 Confirm the directory location; enter y and press Enter.
The data directory prompt appears.
Step 8 To accept the default directory, /var/CSCObac, press Enter; or enter another directory. The program prompt also display the available disk space.
For example:
-------------- Data Directory -----------
DB Data Directory [/var/CSCObac]
Available disk space for /var/CSCObac is 2614226 kilobytes.
Step 9 Confirm the directory location; enter y and press Enter.
Step 10 The program begins the installation process. After successful installation, the following message appears:
Installing Cisco BAC product as <CSCObac>
Installation of <CSCObac> was successful.
Step 11 To verify if the version information indicates Cisco BAC release 4.1.0.1, enter:
# pkgparam CSCObac VERSION
Step 12 Manually start the Cisco BAC process watchdog to complete the upgrade process.
For example, from the command line, run:
# /etc/init.d/bprAgent start
Note The Cisco BAC 4.1.0.1 KDC requires a new license. Before you start the Cisco BAC process watchdog, ensure that the correct license and certificates are installed.
Migrating the RDU Database
When the product is installed over the previous versions from which the user can migrate to Cisco BAC 4.1.0.1, the installer detects that RDU DB-Migration is needed, the necessary files should be updated along with package database. The user must run the "migrateDb.sh" shell script which will be located under BPR_HOME/migration.
The RDU database migration script allows you to migrate your RDU database from:
•Cisco BAC 2.7.1.x to Cisco BAC 4.1.0.1
•Cisco BAC 4.0.1.x to Cisco BAC 4.1.0.1
Backwards Compatibility
You can use the 4.1.0.1 RDU with a migrated database to operate with earlier versions of Solaris DPEs and CNR 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, ensuring the least disruption until you upgrade the specific DPE.
Note This Cisco BAC release provides multivendor support via Option 43 and its suboptions. When using this option, ensure that you modify templates used in earlier releases to be compatible with the template grammar that Cisco BAC 4.1.0.1 uses.
Verifying Database Integrity
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 live migration, because in the case of a large database, verification can take an extended length of time.
To verify the database:
•Before migration, run the verifyDb.sh tool on a backup snapshot.
Note 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 4.1.0.1 version of verifyDb.sh.
For example, enter:
# /opt/BPR_HOME/rdu/internal/db/bin/verifyDb.sh -dbdir /disk1/backup
This pathname is specific to the Cisco BAC installation version before migration.
•After migration, run the verifyDb.sh tool on the migrated database.
For example, enter:
# /opt/BPR_HOME/rdu/internal/db/bin/verifyDb.sh -dbdir /disk2/target
For details on the verifyDb.sh tool, see the Cisco Broadband Access Center Administrator Guide 4.1.
Cisco BAC 2.7.1.x to Cisco BAC 4.1.0.1
Migrating the RDU database from Cisco BAC 2.7.1.x to Cisco BAC 4.1.0.1 consists of two phases:
1. Phase 1—This phase is executed after installation via the migrateDb.sh tool.
2. Phase 2—This phase is executed when the RDU is first started up after the Phase 1 migration is completed.
The migration script (migrateDb.sh) is automatically installed when you run the Cisco BAC 4.1.0.1 installation program (pkgadd). Migration is accomplished by reading from the original database and writing it into a new database. For this purpose, you must allocate additional disk space for accommodating the newly created database.
The status of the first phase of migration is recorded in a migration log file, which is stored in the migrated database directory. The migration.log file identifies the version of the database that is being migrated and provides status messages for the migration process.
Note Migration deletes any outstanding jobs stored in the database, such as reliable batches that did not finish execution or pending Configuration Regeneration Service (CRS) jobs.
Migration Performance
A large Cisco BAC RDU database can be several gigabytes in size, and may take an extended length of time to migrate. The length of time that database migration takes depends largely on your hardware, hence using faster disks improves the time significantly.
Migration automatically compacts your database that may be fragmented. However, this Cisco BAC release stores additional data for every device. You can expect the size of the database to increase after migration by as much as 10 percent.
The migration process is optimized for speed and database compactness. As a result, migration requires a large amount of process heap size (memory). For example, migrating a 7-million device database requires approximately 1,024 MB of process heap size. Since the migration process is limited to 4 GB of heap space, migration is effectively limited to a database size of approximately 25-30 million devices.
The -Xmx parameter in the migrateDb.sh script determines the maximum process heap size for migration. The default setting of 3,072 MB for this parameter is sufficient for migrating a 20-million device database. You may need to fine-tune this setting to suit your environment. For example, to migrate smaller databases running on low-end systems with less memory, you can reduce the value of the maximum heap size setting. For databases that exceed the maximum supported scale, you may need to increase this setting.
To change the heap size parameter, in the migrateDb.sh script edit the value for the -Xmx parameter.
Licensing After Migration
The licensing scheme changes significantly in this release. You cannot use the license keys from earlier 2.7.1.x versions of Cisco BAC to provision your network using Cisco BAC 4.1.0.1. Any existing license keys are automatically deleted during database migration. To configure Cisco BAC licensing, you must obtain the license files via a license claim process and install them using the administrator user interface. For details, see the Release Notes for Cisco Broadband Access Center 4.1.0.1.
During migration, device counters are recalculated based on the number of devices in each provisioning group found in the database. New counters are recorded in the new database and used for licensing.
RDU Extension Migration
During database migration, custom extensions are reset to 4.1.0.1 defaults. Custom extensions must be updated to operate in the 4.1.0.1 environment. If you require custom extensions after migration, you must add them using the administrator user interface. For details, see the Cisco Broadband Access Center Administrator Guide 4.1.
Migration of Duplicate Class of Service and Node Name
This Cisco BAC release does not support duplicate names across technologies for Class of Service and nodes. If Cisco BAC detects duplicate names during database migration, the duplicate entries are automatically renamed in the following format:
•Class of Service—{Technology_Name}_{Original_ClassOfService_Name}
•Nodes—{Node_Type}_{Node_Name}
For example, if Cisco BAC encounters a gold Class of Service for a computer and a DOCSIS modem, either the computer Class of Service is renamed Computer_gold or the DOCSIS modem Class of Service is renamed DOCSISModem_gold. The appropriate warnings are issued to the console and migration log, and all properties containing the specific Class of Service value are automatically updated.
Table 3-4 describes the process of migration from 2.7.1.x to 4.1.0.1 using examples that assume that:
•Cisco BAC is installed in the default home directory (/opt/CSCObac).
•The backup of the previous version of the RDU database is located in the /disk1/backup directory.
Table 3-4 RDU Migration Workflow from 2.7.1.x to 4.1.0.1
|
|
|
Step 1 |
Select two disk partitions: one for the migrated database, and another as a temporary storage directory for the database transaction logs. Note For performance reasons, we recommend that you configure these disks on a fast I/O system, such as a RAID array with battery-backup write cache or a RAM disk. For details on migrating using a RAM disk, see Migrating Using a RAM Disk. The partitions that are used in the examples in this procedure are: •Volume /disk2/target—Used to write the migrated database data. The available disk space for the migrated database should be at least 120 percent of the size of the original database (which is the bpr.db file in the backup directory). •Volume /disk3/target—Used as the temporary storage directory. The available space on the temporary storage disk must be at least 2 GB. For performance reasons, however, we recommend that you locate this directory on a different disk from the backup database and the target database location. |
Solaris documentation |
Step 2 |
Run the migrateDb.sh tool on the backed-up database. The migrateDb.sh script resides in the BPR_HOME/migration directory. For a description of all arguments that this tools supports, see Using the migrateDb.sh Tool. For example:
# /opt/CSCObac/migration/migrateDb.sh -dbdir /disk1/backup
-targetdbdir /disk2/target -targetdblogdir /disk3/target &>
/var/run/migration-console.log &
•-dbdir—Specifies the location of the database backup that is to be migrated; in this case, /disk1/backup. •-targetdbdir—Specifies the target location where the migrated database should be placed; in this case, /disk2/target. This directory is created automatically during migration and must not exist before the script is executed. •-targetdblogdir—Specifies the target location for the temporary migration transaction log files; in this case, /disk3/target. This directory is created automatically during migration and must not exist before the script is executed. Note New database log files are created in this directory and later destroyed automatically during migration. Once migration is complete, all the necessary files are automatically copied from this directory to /disk2/target. After migration, you can delete this directory. |
Cisco Broadband Access Center Administrator Guide 4.1 |
Step 3 |
Observe the migration progress using the migration.log file. For example:
# tail -f /disk2/target/migration.log
|
Solaris documentation |
Step 4 |
Verify if the migration is complete using the migration.log file. If you find any warnings or notices, use the grep command-line tool. For example:
# tail /disk2/target/migration.log
Tue Oct 16 15:36:20 EDT 2007: Phase 1 of RDU database migration to
BAC 4.1.0.1 completed with 1 warning(s) and 2 notice(s).
# cat migration.log | grep "WARNING"
Tue Oct 16 15:57:23 EDT 2007: WARNING: Duplicate Class of Service
name [cg814wg_chn_n05] detected for [CableHomeWanMan] technology.
Class of Service object was renamed to
[CableHomeWanMan_cg814wg_chn_n05].
# cat migration.log | grep "NOTICE"
Tue Oct 16 19:06:23 EDT 2007: NOTICE: A deprecated property
[/dhcp/client-policy/response/boot-file] was found on object with
oid [2882304375712137210]. Property will be declared as custom
property.
Tip You may also find it useful to examine the device statistics printed at the end of the migration.log file.
|
Solaris documentation |
Step 5 |
Restore the migrated database into the target directories for the 4.1.0.1 RDU. This process copies the migrated database to the RDU BPR_DATA and BPR_DBLOG directories. For example:
# /opt/CSCObac/rdu/bin/restoreDb.sh /disk2/target
Note Once the migration process is complete, you can delete the content of /disk2/target and /disk3/target directories. |
Cisco Broadband Access Center Administrator Guide 4.1 |
Step 6 |
Start the RDU process from the Cisco BAC watchdog process command line, and look for messages on successful initialization in the rdu.log file. For example:
# /etc/init.d/bprAgent start rdu
|
Cisco Broadband Access Center Administrator Guide 4.1 |
Step 7 |
Verify if the second phase of migration has started. For example, rdu.log should include similar messages:
bac-test.example.com: 2007 10 17 02:36:28 EDT: %BAC-RDU-6-0695:
[Starting Phase 2 of RDU db migration].
|
Solaris documentation |
Step 8 |
Observe the progress of the migration. For example, rdu.log should include similar messages:
bac-test.example.com: 2007 10 10 02:50:36 EDT: %BAC-RDU-6-0695:
[Progress report for selection process...].
bac-test.example.com: 2007 10 10 02:50:36 EDT: %BAC-RDU-6-0695:
[Selection process stats: Read a total of 400000 DOCSISModem device
records].
bac-test.example.com: 2007 10 10 02:50:36 EDT: %BAC-RDU-6-0695:
[Selection process stats: Read a total of 400000 device records].
bac-test.example.com: 2007 10 10 02:50:36 EDT: %BAC-RDU-6-0695:
[Selection process stats: Ran selection on 398228 eligible
devices].
|
Solaris documentation |
Step 9 |
Verify if the second phase of migration is complete. For example, rdu.log should include a similar message:
bac-test.example.com: 2007 10 17 03:28:58 EDT: %BAC-RDU-6-0695:
[Completed Phase 2 of RDU db migration].
bac-test.example.com: 2007 10 17 03:28:58 EDT: %BAC-RDU-6-0695:
[RDU db migration has been finalized].
Also, you can check if the BPR_DATA/rdu/db/DB_VERSION file indicates the database version as 4.1.0.1. |
Cisco Broadband Access Center Administrator Guide 4.1 |
Note Migration preserves the device record revision numbers used in DPE synchronization. As a result, DPE repopulation is not triggered after the RDU database upgrade, ensuring the least disruption until you upgrade the specific DPE. |
Step 10 |
Verify the RDU operations by logging in to the administrator user interface. From Servers > RDU, you can check the RDU version and device count statistics. |
Cisco Broadband Access Center Administrator Guide 4.1 |
Using the migrateDb.sh Tool
Table 3-5 describes the arguments that you can use with the migrateDb.sh tool.
Table 3-5 Arguments for migrateDb.sh Tool for migration from 2.7.1.x to 4.1.0.1
|
|
|
|
|
-dbdir dir |
Specifies the location of the database backup that is to be migrated |
P |
|
None |
-dblogdir dir |
Specifies the location of the database logs that are to be migrated |
|
P |
The directory that the -dbdir option specifies |
-targetdbdir dir |
Specifies the target location where the migrated database will be placed |
P |
|
None |
-targetdblogdir dir |
Specifies the target location in which the migrated database transaction log files are stored temporarily during migration |
P |
|
None |
-cachesize value |
Specifies, in MB, the size of the memory cache. This paramater is optional. If you use this parameter, you must not exceed the 100-MB limit, unless you reduce the value of the -Xmx variable in the migrateDb.sh script by double the increase in the cache size. For example, if you set cache size to 200 MB, you must reduce the value of -Xmx thus: (200-100)*2 = 200 MB |
|
P |
100 MB |
-cmtsv value |
Specifies the CMTS DOCSIS version that is to be used during service selection. The service is selected based on the minimum version that the CMTS and the cable modem supports. The DOCSIS version that the cable modem supports is determined by the value of the dhcp-client-identifier option. The acceptable values are: •1.0 •1.1 •2.0 |
|
P |
1.1 |
-help |
Specifies usage for the tool |
|
P |
None |
You can use a number of arguments, as described in the following section, to specify the Class of Service and DHCP Criteria for promiscuous devices. These arguments are optional, provided the default objects, as specified here, exist in the database. The first phase of migration uses these objects to select the service for the devices granted promiscuous access. During the second phase of migration, the standard selection process for each device is performed according to the policies found in the RDU database. Any discrepancies are addressed in favor of the configuration found in the database. However, the migration process is most efficient if few discrepancies are encountered.
Tip While it may not be possible for you to specify these policy objects accurately if devices of the same type use different promiscuous policy objects, migration will be more efficient if you specify the most frequently used promiscuous objects.
|
-pcospc value |
Specifies the name of the most frequently used Class of Service for promiscuous computers |
|
P |
unprovisioned-computer |
-pcosmta value |
Specifies the name of the most frequently used Class of Service for promiscuous MTAs |
|
P |
unprovisioned-packet- cable-mta |
-pcoschwd value |
Specifies the name of the most frequently used Class of Service for promiscuous CableHome WAN-Data devices |
|
P |
unprovisioned- cablehome-wan-data |
-pcoschwm value |
Specifies the name of the most frequently used Class of Service for promiscuous CableHome WAN-MAN devices |
|
P |
unprovisioned- cablehome-wan-man |
-pcoscpe value |
Specifies the name of the most frequently used Class of Service for promiscuous custom CPE |
|
P |
unprovisioned- customcpe |
-pdcpc value |
Specifies the name of the most frequently used DHCP Criteria for promiscuous computers |
|
P |
genericCPE |
-pdcmta value |
Specifies the name of the most frequently used DHCP Criteria for promiscuous MTAs |
|
P |
genericCPE |
-pdcchwd value |
Specifies the name of the most frequently used DHCP Criteria for promiscuous CableHome WAN-Data devices |
|
P |
genericCPE |
-pdcchwm value |
Specifies the name of the most frequently used DHCP Criteria for promiscuous CableHome WAN-MAN devices |
|
P |
genericCPE |
-pdccpe value |
Specifies the name of the most frequently used DHCP Criteria for promiscuous custom CPE |
|
P |
genericCPE |
Migrating Using a RAM Disk
The RAM disk is a Solaris feature that allows you to mount a portion of the RAM as a disk volume. Disk I/O operations on such volumes are considerably faster and can be useful when you have large databases on systems with sufficient memory.
The procedures described in this section are optional and describe how to create and use different RAM disks to migrate your database instead of a regular disk volume, such as a fast RAID array with battery-backed write cache:
•Creating RAM Disk Volumes for Migration
•Using the RAM Disk Volumes for Migration
Creating RAM Disk Volumes for Migration
The following procedure creates three volumes for migration and assumes that the size of the original database is 9 GB. Adjust the volume sizes as required for your database and according to what the available memory permits.
Using the following procedure, you can create three RAM disks that you could use for migration:
•/ram-disk1—To contain the source database
•/ram-disk2—To contain the migrated database directory
•/ram-disk3—To contain the temporary migration transaction logs
Step 1 Ensure that enough memory is allocated to the RAM disk in the /etc/system file. This figure is a percentage of the total RAM on the system. Assuming a 64-GB RAM, this setting dedicates 32 GB to the RAM disk.
For example:
set ramdisk:rd_percent_physmem=50
Note If you also set the segmap_percent parameter, which determines the quantity of memory allocated to the OS I/O buffer cache, make sure that there is sufficient memory for both settings and some space is left for the OS operation.
Step 2 Reboot the system.
For example:
Step 3 Create three RAM volumes.
For example:
# ramdiskadm -a volume1 10g
# ramdiskadm -a volume2 12g
# ramdiskadm -a volume3 2g
Step 4 Create new file systems on each volume.
For example:
# newfs /dev/ramdisk/volume1
# newfs /dev/ramdisk/volume2
# newfs /dev/ramdisk/volume3
Step 5 Mount the volumes.
For example:
# mount /dev/ramdisk/volume1 /ram-disk1
# mount /dev/ramdisk/volume2 /ram-disk2
# mount /dev/ramdisk/volume3 /ram-disk3
Step 6 Verify the mount points and their size.
For example:
Using the RAM Disk Volumes for Migration
To use the RAM-disk volumes that you have created for migration:
Step 1 Copy the backup of your database to /ram-disk1.
For example:
# mkdir /ram-disk1/backup
# cp /disk1/backup/* /ram-disk1/backup/.
Step 2 Perform the first phase of migration according to the procedure that Table 3-4 describes. Remember to use a command similar to the one described here instead of the one mentioned in Step 2 of the table.
For example:
# /opt/CSCObac/migration/migrateDb.sh -dbdir /ram-disk1/backup
-targetdbdir /ram-disk2/target -targetdblogdir /ram-disk3/target
&> /var/run/migration-console.log &
Step 3 To ensure that the second phase of migration is executed with the database of the RAM disk:
a. Install the 4.1.0.1 RDU such that the database directory and the database logs directory (defined by the BPR_DATA and BPR_DBLOG variables, respectively) point to the volumes on the RAM disk.
b. After the second phase of migration is complete, stop the Cisco BAC process watchdog, using the /etc/init.d/bprAgent stop command from the Cisco BAC process watchdog command line.
c. Back up the database using:
BPR_HOME/rdu/bin/backupDb.sh -nosubdir /ram-diskX/migrated-db/
–BPR_HOME—Specifies the home directory, which is by default /opt/CSCObac.
–X—Specifies the RAM disk to which the RDU database is migrated.
d. Edit the bpr_definitions.sh file that is found in the home directory (by default /opt/CSCObac) and change the BPR_DATA and BPR_DBLOG locations to new directories located on permanent storage drives.
e. Recover and restore the database to the new RDU locations. Run the recoverDb.sh and the restoreDb.sh scripts, respectively, using:
BPR_HOME/rdu/bin/recoverDb.sh
where BPR_HOME specifies the home directory, which is by default /opt/CSCObac.
BPR_HOME/rdu/bin/restoreDb.sh /ram-diskX/migrated-db/
–BPR_HOME—Specifies the home directory, which is by default /opt/CSCObac.
–X—Specifies the RAM disk to which the RDU database is migrated.
For details on using these scripts, see the Cisco Broadband Access Center Administrator Guide 4.1.
f. Start the process watchdog, by running the /etc/init.d/bprAgent start command.
Cisco BAC 4.0.1.x to Cisco BAC 4.1.0.1
Migration of the RDU database from Cisco BAC 4.0.1.x to Cisco BAC 4.1.0.1 must be performed after you install Cisco BAC 4.1.0.1. You must use the migrateDb.sh tool to migrate the RDU database.
Note Migration from Cisco BAC 4.0.1 to Cisco BAC 4.1.0.1 takes less time and space.
Table 3-6 describes the process of migration from 4.0.1.x to 4.1.0.1 using examples that assume that:
•Cisco BAC is installed in the default home directory (/opt/CSCObac).
•The migration from Cisco BAC 4.0.1.x to Cisco BAC 4.1.0.1 is an inline migration where the source and the target DB are same and a separate target DB need not be created. The source DB is restored once the migration is complete.
•The backup of the previous version of the RDU database is located in the /disk4/backup directory.
Table 3-6 RDU Migration Workflow from 4.0.1.x to 4.1.0.1
|
|
|
Step 1 |
Run the migrateDb.sh tool on the backed-up database. The migrateDb.sh script resides in the BPR_HOME/migration directory. For a description of all arguments that this tools supports, see Using the migrateDb.sh Tool. For example:
# /opt/CSCObac/migration/migrateDb.sh -dbdir /disk4/backup
-dbdir—Specifies the location of the database backup that is to be migrated; in this case, /disk4/backup.
|
Solaris documentation |
Step 2 |
Observe the migration progress using the migration.log file. For example:
# tail -f /disk4/backup/migration.log
|
Solaris documentation |
Step 3 |
Verify if the migration is complete using the migration.log file. If you find any warnings or notices, use the grep command-line tool to search them. For example:
# tail /disk4/backup/migration.log
Completed database migration to BAC 4.1.0.1 release
|
Cisco Broadband Access Center Administrator Guide 4.1 |
Step 4 |
Restore the migrated database into the RDU BPR_DATA and BPR_DBLOG directories. For example:
# /opt/CSCObac/rdu/bin/restoreDb.sh /disk4/backup
|
Cisco Broadband Access Center Administrator Guide 4.1 |
Step 5 |
Start the RDU process from the Cisco BAC watchdog process command line, and look for messages on successful initialization in the rdu.log file, it will be up and running. For example:
# /etc/init.d/bprAgent start rdu
|
Cisco Broadband Access Center Administrator Guide 4.1 |
Step 6 |
Also, you can check if the BPR_DATA/rdu/db/DB_VERSION file indicates the database version as 4.1.0.1. |
Cisco Broadband Access Center Administrator Guide 4.1 |
|
Note Migration preserves the device record revision numbers used in DPE synchronization. As a result, DPE repopulation is not triggered after the RDU database upgrade, ensuring the least disruption until you upgrade the specific DPE. |
Step 7 |
Verify the RDU operations by logging in to the administrator user interface. From Servers > RDU, you can check the RDU version and device count statistics. |
Cisco Broadband Access Center Administrator Guide 4.1 |
Using the migrateDb.sh Tool
Table 3-7 describes the arguments that you can use with the migrateDb.sh tool for migration from 4.0.1.x to 4.1.0.1.
Table 3-7 Arguments for migrateDb.sh Tool for 4.0.1.x to 4.1.0.1 migration
|
|
|
|
|
-dbdir dir |
Specifies the location of the database backup that is to be migrated |
P |
|
None |
-dblogdir dir |
Specifies the location of the database logs that are to be migrated |
|
P |
The directory that the -dbdir option specifies |
-cachesize value |
Specifies, in MB, the size of the memory cache. This paramater is optional. If you use this parameter, you must not exceed the 100-MB limit, unless you reduce the value of the -Xmx variable in the migrateDb.sh script by double the increase in the cache size. For example, if you set cache size to 200 MB, you must reduce the value of -Xmx thus: (200-100)*2 = 200 MB |
|
P |
100 MB |
-help |
Specifies usage for the tool |
|
P |
None |
Uninstalling Cisco Broadband Access Center
This chapter describes how you can uninstall Cisco Broadband Access Center (Cisco BAC).
The procedure described in this chapter uninstalls the RDU, CNR extensions, the DPE, and the KDC, but it does not uninstall the CNR application. Before removing Cisco BAC you must manually remove the Cisco BAC configuration on CNR.
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: RDU, KDC, SNMP Agent, Tomcat, Cisco BAC agent, 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 CNR directory.
If you have installed Cisco BAC extensions on CNR, you must uninstall those extensions to completely uninstall the Cisco BAC program; otherwise, an error message similar to the following appears:
The uninstall program found a copy of the BAC extensions in the NR extension
directory(/opt/nwreg2/local/extensions/dhcp/dex/libbprextensions.so), please disable
the extensions and remove the library before uninstalling BAC.
Note The path to the CNR extensions differs based on the location where you have installed CNR; the default location is /opt/nwreg2.
If the uninstallation program fails to uninstall Cisco BAC, error messages appear.
This chapter describes:
•Uninstalling Cisco BAC
•Post-Uninstallation Task
Uninstalling Cisco BAC
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 1 Log in as root.
Step 2 Manually remove the configuration of the Cisco BAC extensions on the CNR server. You can do this from any server that has nrcmd installed and connectivity with CNR.
a. To uninstall the Cisco BAC extensions from your CNR configuration, enter:
# NR_HOME/local/usrbin/nrcmd -N admin -P changeme -b <
BPR_HOME/cnr_ep/bin/bpr_cnr_disable_extpts.nrcmd
b. To reload your DHCP server, enter:
# /etc/init.d/nwreglocal stop
# /etc/init.d/nwreglocal start
Alternatively, enter:
# NR_HOME/local/usrbin/nrcmd -N admin -P changeme "dhcp reload"
c. To remove the Cisco BAC extensions from the CNR extensions directory, enter:
# rm -rf NR_HOME/local/extensions/dhcp/dex/libbprextensions.so
Step 3 At the CLI prompt, enter:
The following information appears:
The following package is currently installed:
CSCObac Cisco BAC product
Do you want to remove this package? [y,n,?,q] y
Step 4 Enter y, and press Enter to start uninstalling.
## Removing installed package instance <CSCObac>
This package contains scripts which will be executed with super-user
permission during the process of removing this package.
Do you want to continue with the removal of this package [y,n,?,q] y
Step 5 Enter y and press Enter.
When uninstalling is complete, the following message appears:
Removal of <CSCObac> was successful.
Post-Uninstallation Task
After you have uninstalled Cisco BAC, you must 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:
The data and the database logs directories are deleted.