|
|
This chapter provides information about how to install the Cisco Broadband Access Center for Broadband Aggregation (BAC) software, how to start BAC servers re-install the BAC software, and provides a list of all field components in the BAC installation windows.
Before you begin the installation process, be sure the system requirements have been met, as described in the "Broadband Access Center System Requirements" section, and the preinstallation tasks have been reviewed, as described in "Pre-installation Tasks."
This chapter includes the following sections:
The BAC software architecture is a client/server model. The BAC server is essential to the BAC operations. The BAC server works with both the server and the BAC database to enable provisioning and other functions. The BAC software is available in the CSCObacss directory and is available on the product CD-ROM. A command line interface is available to do some operations, however, most operations are done through a graphical user interface (GUI).
The BAC software supports the following installation types:
In a complete provisioning Broadband Access Center software installation, the BAC software (BAC client, graphical user interface) is installed on the same machine. You can also install the BAC software on a machine without a Cisco Configuration Engine or a UI Web server.
The distributed installation allows you to install components on different machines. This helps to share work loads and reduce the number of duplicate components.
You can distribute the Configuration Engine and the BAC UI Web server, but the rest of the BAC software is installed on the same machine as the BAC package. When you select the Configuration Engine or BAC UI Web server installation option, it installs a Configuration Engine or a BAC UI Web server, it does not install any of BAC servers on that machine. It is referred to as distributed because the user can install the BAC software on different machines and install as many Configuration Engines and UI Web servers on other machines and use all of them.
The BAC software product offers the following installation options:
After you select a BAC installation option, BAC software provides you with technology options:
Read these rules before you select how to install the BAC software:
 |
Note You can choose option 1 only once. Once you install option 1, if you run the ./bacInstall script again, the system detects this existing product and generates an error message to stop installation and does not continue. |
|
Note This is because option 2 already includes the BAC Web Server. It is not necessary to install two BAC UI Web servers on the same machine. |
The Oracle database is made up of a server and a client. The Oracle client must always be installed on the same machine as the BAC server. The recommended configuration is to install the Oracle server on a remote machine and the Oracle client on the BAC server machine. However, if you will be installing the BAC software and Oracle database on the same machine, you must increase the machine's memory.
 |
Caution Make certain that Oracle is started before you begin to install BAC. |
This section describes what to do before you begin the BAC installation when you install from a CD-ROM.
If your system does not have an automounted CD-ROM, you will need to mount it manually. For information about mounting the CD-ROM manually, see "Mounting the CD-ROM Manually" section.
Step 2 Login as user.
Step 3 Go to the CD-ROM directory where you want to store the build:
Step 4 Type the run script:
Step 5 Type the product path:
|
Note You can also install BAC on a remote machine using the Telnet session from a local machine. On the local machine, you must first run the xhost + command. This enables the local machine to accept an X-term display sent back from the remote machine. Then, you can start a Telnet session. |
Step 6 Set the DISPLAY environment variable:
Step 7 Go to the directory where you want to store the build:
Step 8 Run the BAC installation script:
|
Note This script allows you to install the BAC software in a location other than the default location (the /opt/CSCObacss directory for the BAC server). A symbolic link to the actual location will be created automatically. |
This section describes the installation options available to you when you install the BAC software. The BAC installation options, both complete provisioning and distributed, are:
To display the BAC Installation Options window, from the CD ROM and run ./bacInstall. The BAC installation window displays, as shown in Figure 3-1.
The BAC Installation Options menu displays the following options:
1. Complete Provisioning System—BAC with all components and Configuration Engine
2. BAC Installation without Config Engine—BAC with elected components
3. Config Engine—Configure one or more Configuration Engines on different machines
4. UI Web Server—Installs the BAC UI Web server and packages the JDK 1.4.1 necessary to run it
5. Quit—Exits BAC installation
This section describes what to do when you select the complete provisioning installation, which is installing BAC with Configuration Engine and all the other BAC components. Option 1, Complete Provisioning System is the default.
The Cisco Broadband Access Centerserver is central to BAC operations. The server works with both the client and the Cisco Broadband Access Centerdatabase to enable provisioning and other functions. The server and client communicate through the Common Object Request Broker Architecture (CORBA). The server queries the BAC database to obtain data for the client.
A complete BAC provisioning system includes the components listed and defined in Table 3-1.
Table 3-1 Cisco Broadband Access Center Components
Follow these steps to begin installing BAC:
|
Note The BAC technology options menu displays only when you select BAC installation option 1 and option 2. |
You can select one of the following technology options:
Step 2 For Broadband, enter 1 and press Return to select this option. The BAC Installation window appears, as shown in Figure 3-3.
For a description of the various fields provided in the BAC Installation window, see the "Installation Window Components and Field Descriptions" section.
Step 3 Specify the values that you gathered during pre-installation into the displayed fields in the Input Data pane.
Step 4 Scroll down in the Input Data pane, then specify the required Oracle database information in the newly displayed fields, as shown in Figure 3-4.
Step 5 Scroll down in the Input Data pane, then specify the required information and whether or not you would like to enable the configuration of the optional Cisco Broadband Access Center components in the newly displayed fields, as shown in Figure 3-5.
|
Note If you selected the Broadband technology option, the Cisco AR field, appears in the Input Data pane. |
Step 6 Scroll down again in the Input Data pane, then specify the required object database related information.
Step 7 If you want to check which BAC options are currently installed, click Installed Product.
A pop-up window displays that lists which BAC components are installed on this machine.
Step 8 Click Start.
The Output Log pane shows the progress of the installation. The BAC installation script runs through its checks. It then, depending upon the optional BAC components you selected (for example Cisco Networking Services, Cisco CNS Access Registrar, Cisco CNS Network Registrar, or CNS Configuration Engine), queries you on whether or not it should open the following configuration files for you to edit:
|
Note BAC also maintains a installation log file. This log file contains the same content that displays in the Output log pane. The installation log file is located in /var/tmp/bac. |
For details about these files and the entries you will need to edit, see "Configuring the Cisco Broadband Access Center Software."
Step 9 After installation completes, the window displays the following text:
Step 10 Click Exit.
If you select option 1, Complete Provisioning System and technology option 2, VoIPoE, then follow these steps:
Step 2 From the technology menu, enter 2 and press Return.
The same windows display (Figure 3-3, Figure 3-4, and Figure 3-5), except there is a field called Cisco NR, Cisco CNS Network Registrar, which appears in the second Input Data pane (not Cisco AR). Repeat the same steps from the previous section.
Step 3 Enter y if you have Cisco CNS Network Registrar installed prior to installation or n, if you do not.
Step 4 Click Exit.
This option allows you to install BAC and its components without a Configuration Engine.
Follow these steps when you select installation option 2 and technology option 1 or 2:
|
Note For a description of the various fields provided in the BAC Installation window, see the "Installation Window Components and Field Descriptions" section. |
Step 2 Select option 1 from the technology options. The BAC installation windows are the same as Figure 3-3, Figure 3-4, and Figure 3-5.
|
Note If you select installation option 2 and technology option 2, then the installation windows are the same as Figure 3-3, Figure 3-4, and Figure 3-5, except for the field, Cisco NR (Cisco CNS Network Registrar). |
Step 3 Specify the values that you gathered as described in the "Before You Begin Installation" section.
Step 4 Enter y if you have Cisco CNS Access Registrar installed prior to installation or n, if you do not.
Step 5 After you enter values in the required fields, click Start.
The Output Log pane shows the progress of the BAC installation script as it proceeds.
Step 6 Click Exit.
By distributed installation, you can define Cisco Configuration Engines and install components on different machines to help share the work loads. Follow these steps when you install configuration engines on different machines.
For a description of the various fields provided in the BAC Installation for Config Engine window, see the "Installation Window Components and Field Descriptions" section.
Step 2 Specify the values you gathered during pre-installation into the displayed fields in the Input Data pane.
Step 3 Scroll down in the Input Data pane, then specify the remaining required information in the newly displayed fields, as shown in Figure 3-7.
Step 4 If you want to check which BAC options are currently installed, click Installed Product. A pop-up window displays that lists which BAC components are installed on this machine.
Step 5 Click Start.
The Output Log pane shows the progress of the installation. The BAC installation script starts the provisioning system, checks the product source directory, copies required files, enters files, invokes installation for a Configuration Engine, and unzips packages.
After installation completes, the window displays the following text:
Step 6 Click Exit.
The BAC Web-based user interface (Web UI), provides service provider and subscriber management, network resource and inventory management, and network access for administrators and operators. For a UI Web server distributed installation, you must mount the template root directory and the Cisco Service Template Manager (CSTM) property file.
The Template Manager user interface is an integrated component of the BAC user interface and requires access to certain file system directories and files on the machine where BAC servers are running.
To make those directories and files accessible from the UI Web server machine, you must perform the share command on the directories on the BAC servers machine and then mount them on the UI Web Server machine. (Refer to the Unix share and mount commands how to do this.)
The following example describes how you get the directories and files to be shared and mounted.
Step 2 Use the share command to get the following directories to be shared on machine A:
Step 3 Mount these directories on machine B. You must mount the directory, /opt/CSCObacss/tm under the same name (the mount command allows directories to be mounted under a different name). You can mount the other two directories under any desired name.
For example, mount directories /opt/CSCObacss/common/templates and /opt/CSCObacss/cstm/config on machine B under the name /bacTemplateRoot, and /bacCSTMConfig, respectively. Respond to the two installation prompts as follows:
|
Note For the CSTM Property File prompt you must specify the file name Template.properties. |
Follow these steps when you select option 4 from the BAC Installation Options menu:
Step 2 Specify the values that you gathered during pre-installation into the displayed fields in the Input Data pane.
Step 3 Continue to scroll down in the Input Data pane and specify the remaining required information in the newly displayed fields as shown in Figure 3-9.
Step 4 If you want to check which BAC options are currently installed, click Installed Product. A pop-up window displays that lists which BAC components are installed on this machine.
Step 5 Click Start or Exit.
|
Note For a description of the various fields provided in the BAC Installation for UI Web Server window, see the "Installation Window Components and Field Descriptions" section. |
The SubscriberAccessManager is a server to handle the interface with RADIUS servers. SAM supports the integration with Cisco AR and Interlink Merit RADIUS server to work with BAC. After you install BAC software, you must set up the following to work properly with BAC.
If you intend to use Cisco Access Registrar for AAA services, then you might need to make changes to the configuration of Cisco Access Registrar or apply a patch release to the software. to make sure it is properly configured after installing BAC. Follow these steps:
|
Note These files must be accessible to the Access Registrar server. If your file system is mounted, the server can access any directory and you do not need to copy the files. However, if the file system is not mounted, you must copy the files. |
Step 2 If you change the default directory (/opt/CSCObacss/sam/scripts), then modify the following files before you load the directory to Access Registrar.
a. Modify the ar-sub-odbc.rc, ar-tunnel-odbc.rc, and ar-pvc-odbc.rc files that are in </sam/scripts> directory at one of these lines:
b. Modify the same file ar-sub-odbc.rc in /sam/scripts directory. Make the following changes to these lines only:
Step 3 Run the run_odbc_rc script to load the script to the CNS Access Registrar server. The default path in this script is /opt/CSCObacss/sam/bin.
|
Note You might need to modify the hostname that points to your CNS Access Registrar server host and the username and password. |
Step 4 If a patch to the BAC software is required, you apply the patch by running one of the following scripts:
|
Note For detailed information about CNS AR, go to this URL for instructions about configuring CNS AR: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cnsar/3_0/install/index.htm |
The BAC provides provisioning of a client in Merit text file (/etc/opt/aaa/clients) and provisioning subscriber, tunnel, and PVC through an external database. An SDK (software development kit) implementation is a Merit AATV plug-in to access the BAC database for authentication and authorization and return value if any.
Follow these steps to set up Interlink Merit to work properly with BAC:
Step 2 In order for BAC to configure Merit as remote host, you must add BAC host in the /etc/hosts file at the remote Merit host and /etc/hosts.equiv to allow shared host to configure the Merit host.
Step 3 Copy all ODBC driver library (libodbc.so, libodbcinst.so, liboraodbc.so) files from the BAC installed directory, /opt/CSCObacss/sam/merit/lib to the Merit library directory, default /opt/aaa/lib. The library should be accessed by root. Perform a symbolic link. Enter:
Step 4 Copy the BAC SDK library libsubscriber.so file, located in the BAC installed directory, /opt/CSCObacss/sam/merit/lib to the Merit AAA AATV plug-in directory, default /opt/aaa/aatv.
Step 5 Modify the dictionary file in /etc/opt/aaa/ directory on the Merit host by adding a new Authentication-Type, such as:
Step 6 Add new Cisco attributes to the dictionary file under the Cisco Extension section on the Merit host. These two attributes are for policy mapping support.
Step 7 Modify the authfile in /etc/opt/aaa directory on the Merit host by setting the realm that you decide to use the LNS as authentication-type, such as:
|
Note The realm uses for LNS cannot be used for proxy. The realm is not case sensitive. But the subscriber authentication is case-sensitive, such as:. user@cisco.com and user@Cisco.com are different. |
Step 8 Copy the process merit_client from the BAC installed directory /opt/CSCObacss/sam/merit/bin to the Merit host in the /etc/opt/aaa directory. You must be root to run this process.
Step 9 Check the radius daemon pid file (radiusd.pid) in the /var/opt/aaa/run directory. Make certain that during Merit installation, the default radius daemon pid file is under /var/run. If you do not change the directory, you should make a symbolic link. Enter:
|
Note If you only install Merit, you will not see the radiusd.pid file if you have not started your radius daemon. |
Step 10 Check that the clients file in /etc/opt/aaa directory on the Merit host has 0644 for root only. You should add a local host entry in the clients file, such as:
Step 11 Create the same account as the BAC provisioning user on the host that is running the Merit Radius server. If you are running BAC provisioning server as a specific account, you should make sure that you have the same account (same gid) on the host that the Merit daemon is running.
Step 12 Copy database setting (odbc.ini, odbcinst.ini) and SQL statement (stmt.sql) files from the BAC installed directory /opt/CSCObacss/sam/merit/scripts to the Merit host in /opt/aaa/odbc directory. You should:
a. Create /opt/aaa/odbc directory first.
b. Modify the odbc.ini file with the username, password, and DB (SID) to match your DB login.
Step 13 Copy environment setting (setenvs.sh) from /opt/CSCObacss/sam/merit/scripts to the Merit host in /opt/aaa/odbc directory. You must set the environment to the setting from setenvs.sh file before you can start Merit Radius server. You can modify the script to any shell (csh, ksh, bash) file so that you can either source or sh the environment.
Step 14 Shut down Radius server and restart it. You can start the radius server in a debug mode, such as:
The debug output is in /var/opt/aaa/logs. There are two files:
However, if you start radius daemon with debug mode, the provisioning process may not work properly. The radius daemon with debug mode does not write the process id to the radiusd.pid (/var/etc/opt/aaa/run) file. Once NAS is configured, the daemon is not refreshed if the pid is not properly written in the radiusd.pid file.
Step 15 Use the radcheck utility to test that the server is responding.
Step 16 Use the radpwtst utility to test the authentication.
|
Note Only clients file for Merit Radius server is modified with new NAS device after the user creates a device. |
If you select installation option 2, BAC Installation without Config Engine, from the BAC Installation Options menu, then you must start the servers.
|
Note For detailed information about the parameters in the following setup, see the CNS Configuration
Engine 1.3 Admin Guide at URL: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cns/ce/rel13/ag13/index.htm |
To start the servers running, follow these steps:
Step 2 The setup script begins and you are prompted for your root password.
You will see the screen display:
|
Note Make certain that the Cisco Configuration Engine hostname and IP address default is the same as |
Step 3 Choose operational mode for the system and follow the prompts:
Step 4 You are now ready to start the BAC software.
When pressing Exit during the installation process, the program will attempt to exit the process immediately. When you proceed to re-install, there are three possibilities:
1. If you press Start, a clean-up of the installed components will be attempted before the re-installation process begins.
2. If the clean-up process does not succeed, you must run the uninstall script before re-installing the software. To uninstall, see the "Uninstalling the Cisco Broadband Access Center Software" section.
3. If the automatic uninstallation process is not successful, enter the following commands manually as root to remove the software:
Table 3-2 lists and describes the various fields found within the BAC Installation window. Not all of the fields described in this section are displayed in this window at all times. The fields displayed are dependent upon the installation option you selected. See Figure 3-3, Figure 3-4, and Figure 3-5 for sample BAC Installation windows.
Table 3-2 BAC Window Components and Field Descriptions
| BAC Component or Field | Description |
|---|---|
The source directory of the BAC product. This will most likely be /cdrom/cdrom0. |
|
The destination directory for the BAC product. The default is the /opt directory. If other than the /opt, directory, a soft link is created from /opt to the specified destination directory. Cisco Configuration Engine installation requires the following minimum disk space for the three directories: |
|
The username of the BAC installation and administration user. |
|
The group name of the BAC installation and administration user. |
|
The host machine on which the Orbix Naming Service is running. |
|
The host machine on which the BAC Inventory Manager server is running. |
|
The host machine on which the BAC Service Provisioning Manager is running. |
|
The host machine on which the BAC CSTM (TM CORBA Server) is running. |
|
The root directory where the BAC CSTM server stores the actual template files. |
|
The full path name of the CSTM server's property file. The file is called Template.properties. |
|
The home directory of the Oracle client on the local machine. This directory is defined by the $ORACLE_HOME environment variable. |
|
The Oracle server ID (SID) for BAC to access the Oracle server through the Oracle client. Use the SID defined in the "Setting Up Oracle Before BAC Installation" section. The Oracle client must be able to resolve this string. |
|
The Oracle username for BAC to access the Oracle server through the Oracle client. Use the Oracle username defined in the "Setting Up Oracle Before BAC Installation" section. |
|
The Oracle password for BAC to access the Oracle server through the Oracle client. Use the Oracle password defined in the "Setting Up Oracle Before BAC Installation" section. |
|
In a simple installation architecture, this is the host name of the BAC server. In a distributed installation architecture, this is the host name for the BAC Provisioning Services. |
|
The domain name for the CORBA server so it can append to the machine's name and be resolved to the full name. This has nothing to do with the domain name referenced by the Network Inventory Manager. |
|
Indicates whether or not the Cisco CNS Network Registrar product is being used in conjunction with BAC. |
|
When you answer Y in this field, it only expands the CNS AR library in .../sam/bin and .../sam/lib directories and creates a cisco-ar soft link if one does not exist. You can install BAC first, answer Y in the CNS AR option, and then install CNS AR later or you can install CNS AR first and then install BAC later. |
|
Posted: Wed Jun 4 13:03:39 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
