Chapter 3. Installing the Cisco Broadband Access Software

Table Of Contents

Installing the Cisco Broadband Access Center Software

Cisco Broadband Access Center Software Installation Overview

Complete Provisioning Installation Description

Distributed Installation Description

BAC Menu Options

Before You Begin Installation

Installing BAC from a CD-ROM

Cisco Broadband Access Center Installation

Starting BAC Installation

Complete Provisioning System Installation

Installing the BAC Without Configuration Engine

Installing Configuration Engine

Installing UI Web Server

After Installing BAC

Setting Up CNS AR After Installing BAC

Setting Up Interlink Merit RADIUS Server After Installing BAC

Starting the BAC Servers

Re-Installing Broadband Access Center

Installation Window Components and Field Descriptions

Installing the Cisco Broadband Access Center Software

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 on page 1-4, and the preinstallation tasks have been reviewed, as described in Chapter 2, "Pre-installation Tasks."

This chapter includes the following sections:

• "Cisco Broadband Access Center Software Installation Overview" section

– "Complete Provisioning Installation Description" section

– "Distributed Installation Description" section

– "BAC Menu Options" section

• "Before You Begin Installation" section

• "Installing BAC from a CD-ROM" section

• "Cisco Broadband Access Center Installation" section

– "Complete Provisioning Installation Description" section

– "Installing the BAC Without Configuration Engine" section

– "Installing Configuration Engine" section

– "Installing UI Web Server" section

• "Starting the BAC Servers" section

• "After Installing BAC" section

• "Installation Window Components and Field Descriptions" section

Cisco Broadband Access Center Software Installation Overview

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:

•Complete provisioning—Single machine (simple)

•Distributed— Install Configuration Engines and/or BAC UI Web servers on different machines

Complete Provisioning Installation Description

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.

Distributed Installation Description

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.

BAC Menu Options

The BAC software product offers the following installation options:

•1) Complete Provisioning System—Installs all of the BAC servers software on a single machine with Configuration Engine.

•2) BAC Installation without Config Engine—Installs only the BAC software.

•3) Config Engine—Allows you to configure more than one Configuration Engine on different machines.

•4) UI Web Server—Allows you to add more than one user interface Web server.

•5) Quit—Exits out of BAC.

After you select a BAC installation option, BAC software provides you with technology options:

•1) Broadband—IP for Broadband Aggregation

•2) VoIPoE—VoIP over Ethernet

Before You Begin Installation

Read these rules before you select how to install the BAC software:

•Only one complete BAC installation can be installed per a machine.

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.

•The Cisco Configuration Engine and the UI Web server can co-exist on the same machine.

•Only one instance of the Cisco Configuration Engine or the UI Web server is allowed on a machine.

•Installation menu option 2 and option 4 cannot co-exist on the same machine.

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.

•Installation option 2 and option 3 installed together make up a complete BAC product.

•The BAC servers should be running before you start the BAC client GUI (see "Starting the BAC Servers" section.

•Install the Oracle database on either a local system or a remote system.

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.

•Gather the following information prior to invoking the BAC installation script:

–BAC product source directory of the installation program. The default is the place where the user has the build (for example, /cdrom/cdrom0/Solaris)

–The installation directory where you want to install the BAC product

–Your Oracle product information (home, SID, user name, and user password)

–UNIX root password

–Installer's user login and group names (this information can be obtained by using the id command at the command line prompt)

–Local host name

–Network domain name

–Config Engine host, Config Engine IP address, CNS Access Registrar: Y/N

•If you install BAC using option 2 from the BAC Installation Options menu, then you must stop all servers that are running. See "Performing Cisco Broadband Access Center Backup and Restore" section on page 5-4.

Installing BAC from a CD-ROM

This section describes what to do before you begin the BAC installation when you install from a CD-ROM.

Step 1 Insert the BAC CD-ROM in your CD-ROM drive.

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 on page 2-5.

Step 2 Login as user.

Step 3 Go to the CD-ROM directory where you want to store the build:

# cd /cdrom/cdrom0

Step 4 Type the run script:

./Install

Step 5 Type the product path:

# /cdrom/cdrom0/Solaris

Note You cannot run the BAC installation script as root.

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:

% setenv DISPLAY <machine>:0.0

Step 7 Go to the directory where you want to store the build:

# cd /cdrom/cdrom0

Step 8 Run the BAC installation script:

cd /<device>
% ./Install

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.

Cisco Broadband Access Center Installation

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:

• "Complete Provisioning System Installation" section

• "Installing the BAC Without Configuration Engine" section

• "Installing Configuration Engine" section

• "Installing UI Web Server" section

Starting BAC Installation

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.

Figure 3-1 BAC Installation Options

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

Complete Provisioning System 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

Component

Definition

Inventory Manager

Enables you to create administrative networks and manage network devices and resources.

Note Administrative networks partition network views so that one service provider cannot access information about another service provider's network.

For broadband aggregation, network inventory represents aggregating routers; cards, ports, and interfaces on aggregating routers; RADIUS servers; and subscribers. For VoIP over Ethernet, network inventory represents CPE devices.

Service Provisioning Manager

Enables you to create and manage service profiles, provisioning profiles, and task profiles. A service profile describes the service offered to a customer; a provisioning profile defines the technical implementation of the service profile; a task flow defines the sequence of operations required to fulfill a customer's request for services.

The Service Provisioning Manager component also provides the following:

•The capability to provision multiple service packages.

•Access to the API for OSS integration

•Rollback when an error occurs

Resource Manager

Allocates and reserves network resources. Used primarily in VoIP over Ethernet environments, the Resource Manager component also interacts with CNS Network Registrar to provide the following:

•IP address allocation and de-allocation

•IP address reservations

•DNS updates mapping IP addresses to fully qualified domain names (FQDNs)

Subscriber Access Manager

Configures network resources, such as RADIUS servers, with subscriber profiles.

VPN SC Template Manager

Enables you to create, modify, and delete configuration templates and to generate configuration files.

Configuration Delivery Manager

Sends the configuration for downloading onto the device using the Telnet gateway specified in the /opt/CSCObac/cdm/cdm.properties file. If you choose to download files using the Telnet gateway, you must also define terminal server attributes and connectivity attributes.

Authentication Server

Authenticates system administrators, technical operators, and so forth. It provides authorization at three different levels of permission.

Server Manager

Monitors the health of network servers and restarts a server if it fails.

Audit

Provides an audit trail of all requests for network service and enables viewing this information according to criteria that you specify.

Behavior Manager

Provides back-end server logic for the BAC software.

Relational Managed Object Repository (RMOR)

Provides a managed object repository and the interface between the Cisco Broadband Access Center Behavior Manager component and the underlying relational database.

Follow these steps to begin installing BAC:

Step 1 From the BAC Installation window, press Return, or enter 1 and press Return to select this option. The BAC Technology Options window appears, as shown in Figure 3-2.

Figure 3-2 BAC Technology Menu Options

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:

•Broadband—IP for broadband aggregation

•VoIPoE—VoIP over Ethernet

Step 2 For Broadband, enter 1 and press Return to select this option. The BAC Installation window appears, as shown in Figure 3-3.

Figure 3-3 BAC Installation Window - First Input Data Pane

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.

Figure 3-4 BAC Installation Window - Second Input Data Pane

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.

Figure 3-5 BAC Installation Window - Third Input Data Pane

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:

•Subscriber Access Manager—$BAC_HOME/sam/common/subaccessMgr.cfg

•Cisco CNS Network Registrar—$BAC_HOME/resourceMgr/common/ipservice.cfg and $BAC_HOME/resourceMgr/common/resourceMgr.cfg

•Configuration Delivery Manager—$BAC_HOME/cdm/scripts/cdm.properties

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 Chapter 4, "Configuring the Cisco Broadband Access Center Software."

Step 9 After installation completes, the window displays the following text:

*********END*********

Step 10 Click Exit.

If you select option 1, Complete Provisioning System and technology option 2, VoIPoE, then follow these steps:

Step 1 From the Installation menu, enter 1 and press Return. The BAC Installation and Technology Options window ( Figure 3-2) is displayed.

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.

Installing the BAC Without Configuration Engine

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:

Step 1 From the BAC Installation Options menu, select option 2, then press Return to select the BAC Installation without Config Engine installation option. The BAC Installation window appears with the Technical Options menu as shown in Figure 3-1.

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.

Installing Configuration Engine

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.

Step 1 From the BAC Installation Options menu (see Figure 3-1), select technology option 3, Config Engine, then press Return. The BAC Installation for Config Engine window ( Figure 3-6) is displayed.

Figure 3-6 BAC Installation for Config Engine Window - Part 1

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.

Figure 3-7 BAC Installation for Config Engine Window - Part 2

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:

*********END*********

Step 6 Click Exit.

Installing UI Web Server

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 1 Install BAC servers on machine A and install the distributed UI Web server on machine B.

Step 2 Use the share command to get the following directories to be shared on machine A:

•/opt/CSCObacss/common/templates

•/opt/CSCObacss/cstm/config

•/opt/CSCObacss/tm

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.

Note Remember these names because the install process will prompt you for them later.

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:

- prompt: Template Root directory: <-- answer: /bacTemplateRoot
- prompt: CSTM Property File: <-- answer: /bacCSTMConfig/Template.properties

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 1 From the BAC Installation Options menu (see Figure 3-1), select technology option 4, UI Web Server, then press Return. The first BAC Installation for UI Web Server window displays as shown in Figure 3-8.

Figure 3-8 BAC Installation for UI Web Server - First Pane

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.

Figure 3-9 BAC Installation for UI Web Server - Second Pane

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.

After Installing BAC

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.

•CNS AR

•Interlink Merit RADIUS

Setting Up CNS AR After Installing 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:

Step 1 Copy the following files from the /opt/CSCObacss/sam/scripts directory to a directory on the Access Registrar server (for example, /opt/CSCOar/scripts):

–ParseSubscriberODBC.tcl

–ParseTunnelODBC.tcl

–ParsePVCAuth.tcl

–auth-service-script.tcl

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:

set Filename <your directory>/ParseSubscriberODBC.tcl (ar-sub-odbc.rc file)
set Filename <your directory>/ParseTunnelODBC.tcl (ar-tunnel-odbc.rc file)
set Filename <your directory>/ParsePVCAuth.tcl (ar-pvc-odbc.rc file)

b. Modify the same file ar-sub-odbc.rc in /sam/scripts directory. Make the following changes to these lines only:

set UserID <your database user>
set Password <your database password>
set DataBase <your SID>
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:

./apply_patch.apply_patch.Broadband
./apply_patch.VoIPoE

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

Setting Up Interlink Merit RADIUS Server After Installing BAC

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 1 Log in as super user:

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:

ln -s libodbc.so.1.0.0 libodbc.so
ln -s libodbc.so.1.0.0 libodbc.so.1
ln -s libodbcinst.so.1.0.0 libodbcinst.so
ln -s libodbcinst.so.1.0.0 libodbcinst.so.1
ln -s liboraodbc.so.1.0.0 liboraodbc.so
ln -s liboraodbc.so.1.0.0 liboraodbc.so.1

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:

VALUE Authentication-Type LNS 31 (the next new value before Unassigned)

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.

Cisco.attr Cisco-Policy-Up 37 string(*,0,0)
Cisco.attr Cisco-Policy-Down 38 string(*,0,0)

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:

Cisco.com LNS "to handle user login from this realm"
NULL LNS " to handle tunnel that has no @realm situation"

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:

ln -s /var/opt/aaa/run <your Merit radius pid file>

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:

<your host> <shared key> type=NAS v1

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:

./radiusd -x -x -s

The debug output is in /var/opt/aaa/logs. There are two files:

•logfile is for server regular output

•radius.debug is for debugging trace

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.

Starting the BAC Servers

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 1 Run the start server script:

% cd BAC_HOME/script
% ./bacStartUp initial

Step 2 The setup script begins and you are prompted for your root password.

Password: Enter password.

You will see the screen display:

Now startup script will proceed with rest of the steps.....

Note Make certain that the Cisco Configuration Engine hostname and IP address default is the same as

Note Modular router support is only available in internal directory mode.

Step 3 Choose operational mode for the system and follow the prompts:

0=internal directory mode,
1=external directory mode. [0]
Enter the host name: bac-ma123-1
Enter the domain name: cisco.com
You must configure eth0 or eth1. Press Enter to skip.
Enter the eth0 ip address: 170.21.255.255
Enter the Country Code: us
Enter the Company Code: cisco
Configuration Engine user ID is used to log in to the web-based GUI and manage network device objects and templates. This account does NOT have shell access.
Enter Configuration Engine login name: admin
Enter Configuration Engine login password: ********
Re-enter Configuration Engine login password: ********
Enter internal LDAP server password: ********
Re-enter internal LDAP server password: ********

Encryption settings:
--------------------
Enable cryptographic (crypto) operation between Event Gateway(s)/Config
server and device(s) (y/n)? [y] n

Authentication settings:
------------------------
IOS Devices are normally authenticated before being allowed to connect to the Event Gateway/Config Server. Disabling authentication will increase security risk.

Enable authentication (y/n)? [y] n

Event services settings:
------------------------
Enter NSM directive (none, default, http): [default]
Enable Event Gateway debug log (y/n)? [n] y
Enter log file rotation timer (minutes, 0 = no rotation): [2]
Enter max log file size (Kbytes): [3072]
Enter the max versions of log file (0-99): [1]
Each Event Gateway process serves 500 devices. Maximum number ofEvent Gateways allowed is 11.

Enter number of Event Gateways that will be started with plaintext
operation: 10
Enter CNS Event Bus Network Parameter: [bac-ma123-1]
Enter CNS Event Bus Service Parameter: [7500]

Current settings of IMGW:
-------------------------
Gateway ID: bac-ma123-1
Run as daemon (y/n)? y
Timeout in seconds for a CLI command to complete: 180
Timeout in seconds to get the next prompt in Telnet session: 60
Concurrent Telnet session limit: 20
Remove temporary logs of Telnet sessions into devices (y/n)? y
Location of temporary logs of Telnet sessions into devices: /tmp
Hoptest success retry interval (sec): 7200
Hoptest failure retry interval (sec): 3600
Logging level (verbose, error, silent): error
Log file Prefix: IMGW-LOG
Log file size (bytes): 50331648
Log file rotation timer (minutes): 60
Logging mode (append, overwrite): append

Re-configure IMGW (y/n)? [n] y
Enter Gateway ID: [bac-ma123-1]
Run as daemon (y/n)? [y]
Enter Timeout in seconds for a CLI command to complete: [180]
Enter Timeout in seconds to get the next prompt in Telnet session: [60]
Enter Concurrent Telnet session limit: [20]
Remove temporary logs of Telnet sessions into devices (y/n)? [y]
Enter Location of temporary logs of Telnet sessions into devices: [/tmp]
Enter Hoptest success retry interval (sec): [7200]
Enter Hoptest failure retry interval (sec): [3600]
Enter Logging level (verbose, error, silent): [error] verbose
Enter Log file Prefix: [IMGW-LOG]
Enter Log file size (bytes): [50331648]
Enter Log file rotation timer (minutes): [60]
Enter Logging mode (append, overwrite): [append]

Please review the following parameters:
hostname: bac-ma123-1
domain name: cisco.com
eth0 IP address: 170.21.255.255
country code: us
company code: csco
Configuration Engine login name: admin
Configuration Engine login password: ********
internal LDAP server password: ********
Enable cryptographic (crypto) operation between Event Gateway(s)/Config server and device(s) (y/n)? n
Enable authentication (y/n)? n
NSM directive (none, default, http): default
Enable Event Gateway debug log (y/n)? y
log file rotation timer (minutes, 0 = no rotation): 2
max log file size (Kbytes): 3072
the max versions of log file (0-99): 1
number of Event Gateways that will be started with plaintext operation: 10
CNS Event Bus Network Parameter: bac-ma123-1
CNS Event Bus Service Parameter: 7500
Re-configure IMGW (y/n)? y
Gateway ID: cem-sf280-7
Run as daemon (y/n)? y
Timeout in seconds for a CLI command to complete: 180
Timeout in seconds to get the next prompt in Telnet session: 60
Concurrent Telnet session limit: 20
Remove temporary logs of Telnet sessions into devices (y/n)? y
Location of temporary logs of Telnet sessions into devices: /tmp
Hoptest success retry interval (sec): 7200
Hoptest failure retry interval (sec): 3600
Logging level (verbose, error, silent): verbose
Log file Prefix: IMGW-LOG
Log file size (bytes): 50331648
Log file rotation timer (minutes): 60
Logging mode (append, overwrite): append
Warning: setup cannot be aborted while committing changes.

Commit changes (y/n): y
do_plutoSupport ...
Shutdown servers ...
Configure IMGW ...
Configure DCL ...
Create DCL ...
Run configurator ...
Configure EvtGateway start/stop file ...
Register tibco rvrd start/stop script for system shutdown/restart ...
Run NSM configurator ...
echo default"://" > /opt/CSCOnsm/conf/tibgate-nsm.conf
Start servers ...
/etc/init.d/NetAppDCL start
Populate DCL with imgw data ...
Start tibco

/etc/init.d/tibco start >> /var/log/appliance-setup.log 2>&1
/etc/init.d/httpd start
/etc/init.d/Imgw start >> /var/log/appliance-setup.log 2>&1
/etc/init.d/EvtGateway start >> /var/log/appliance-setup.log 2>&1
Initialize Group for Internal Mode ...
Configure DAT ...
do_modularRouterSupport ...
Warning: plutosetup will open some class files to public access. It is a security risk.
Continue (y/n): y
Now startup script will proceed with rest of the steps.

Step 4 You are now ready to start the BAC software.

Re-Installing Broadband Access Center

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 on page 5-7.

3. If the automatic uninstallation process is not successful, enter the following commands manually as root to remove the software:

# pkgrm CSCObacss
# \rm -rf CSCObacss
# pkgrm TIBRV (CSCOesdk is the directory that is created and TIBRV is the package name)
# \rm -rf CSCOesdk

Installation Window Components and Field Descriptions

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

Product Source Dir

The source directory of the BAC product. This will most likely be /cdrom/cdrom0.

Product Destination Dir

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:

•/usr - 125 MB

•/opt - 210 MB

•/var - 200 MB

Installer's Login ID

The username of the BAC installation and administration user.

Installer's Group ID

The group name of the BAC installation and administration user.

UNIX Root Password

The password of the root user on the UNIX system.

Naming Service Host

The host machine on which the Orbix Naming Service is running.

IM host

The host machine on which the BAC Inventory Manager server is running.

SPM host

The host machine on which the BAC Service Provisioning Manager is running.

SPE host

The host machine on which the SPE CORBA Manager is running.

CSTM host (Cisco Service Template Manager)

The host machine on which the BAC CSTM (TM CORBA Server) is running.

Log Server host

The host machine on which the BAC Log Server is running.

Template root directory

The root directory where the BAC CSTM server stores the actual template files.

CSTM property file

The full path name of the CSTM server's property file. The file is called Template.properties.

Oracle Home Directory

The home directory of the Oracle client on the local machine. This directory is defined by the $ORACLE_HOME environment variable.

Oracle SID

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 on page 2-2. The Oracle client must be able to resolve this string.

Oracle User Name

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 on page 2-2.

Oracle User Password

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 on page 2-2.

BAC Server Host Name

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.

Network Domain Name

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.

Cisco CNS NR

Indicates whether or not the Cisco CNS Network Registrar product is being used in conjunction with BAC.

Cisco CNS AR

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.

Config Engine Host Name

The Cisco Configuration Engine host name.

Config Engine Host's IPAddress

The Cisco Configuration Engine IP address.

Component	Definition
Inventory Manager	Enables you to create administrative networks and manage network devices and resources. Note Administrative networks partition network views so that one service provider cannot access information about another service provider's network. For broadband aggregation, network inventory represents aggregating routers; cards, ports, and interfaces on aggregating routers; RADIUS servers; and subscribers. For VoIP over Ethernet, network inventory represents CPE devices.
Service Provisioning Manager	Enables you to create and manage service profiles, provisioning profiles, and task profiles. A service profile describes the service offered to a customer; a provisioning profile defines the technical implementation of the service profile; a task flow defines the sequence of operations required to fulfill a customer's request for services. The Service Provisioning Manager component also provides the following: •The capability to provision multiple service packages. •Access to the API for OSS integration •Rollback when an error occurs
Resource Manager	Allocates and reserves network resources. Used primarily in VoIP over Ethernet environments, the Resource Manager component also interacts with CNS Network Registrar to provide the following: •IP address allocation and de-allocation •IP address reservations •DNS updates mapping IP addresses to fully qualified domain names (FQDNs)
Subscriber Access Manager	Configures network resources, such as RADIUS servers, with subscriber profiles.
VPN SC Template Manager	Enables you to create, modify, and delete configuration templates and to generate configuration files.
Configuration Delivery Manager	Sends the configuration for downloading onto the device using the Telnet gateway specified in the /opt/CSCObac/cdm/cdm.properties file. If you choose to download files using the Telnet gateway, you must also define terminal server attributes and connectivity attributes.
Authentication Server	Authenticates system administrators, technical operators, and so forth. It provides authorization at three different levels of permission.
Server Manager	Monitors the health of network servers and restarts a server if it fails.
Audit	Provides an audit trail of all requests for network service and enables viewing this information according to criteria that you specify.
Behavior Manager	Provides back-end server logic for the BAC software.
Relational Managed Object Repository (RMOR)	Provides a managed object repository and the interface between the Cisco Broadband Access Center Behavior Manager component and the underlying relational database.

BAC Component or Field	Description
Product Source Dir	The source directory of the BAC product. This will most likely be /cdrom/cdrom0.
Product Destination Dir	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: •/usr - 125 MB •/opt - 210 MB •/var - 200 MB
Installer's Login ID	The username of the BAC installation and administration user.
Installer's Group ID	The group name of the BAC installation and administration user.
UNIX Root Password	The password of the root user on the UNIX system.
Naming Service Host	The host machine on which the Orbix Naming Service is running.
IM host	The host machine on which the BAC Inventory Manager server is running.
SPM host	The host machine on which the BAC Service Provisioning Manager is running.
SPE host	The host machine on which the SPE CORBA Manager is running.
CSTM host (Cisco Service Template Manager)	The host machine on which the BAC CSTM (TM CORBA Server) is running.
Log Server host	The host machine on which the BAC Log Server is running.
Template root directory	The root directory where the BAC CSTM server stores the actual template files.
CSTM property file	The full path name of the CSTM server's property file. The file is called Template.properties.
Oracle Home Directory	The home directory of the Oracle client on the local machine. This directory is defined by the $ORACLE_HOME environment variable.
Oracle SID	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 on page 2-2. The Oracle client must be able to resolve this string.
Oracle User Name	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 on page 2-2.
Oracle User Password	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 on page 2-2.
BAC Server Host Name	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.
Network Domain Name	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.
Cisco CNS NR	Indicates whether or not the Cisco CNS Network Registrar product is being used in conjunction with BAC.
Cisco CNS AR	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.
Config Engine Host Name	The Cisco Configuration Engine host name.
Config Engine Host's IPAddress	The Cisco Configuration Engine IP address.