Chapter 4. Configuring the Broadband Access Software

Table Of Contents

Configuring the Cisco BACBA Software

Configuring Configuration Delivery Manager

Configuring CNS Access Registrar

Configuring CNS Network Registrar

Configuring BACBA Server to Receive TIBCO Events

Configuring the Cisco Configuration Engine

Configuring the Cisco BACBA Software

This chapter provides information about how to configure the Cisco Broadband Access Center for Broadband Aggregation software (herein referred to as BACBA), as well as any of the optional components (for example, Cisco Networking Services products: Cisco CNS Access Registrar, Cisco CNS Network Registrar, and Cisco Configuration Engine) that you specified during the installation of the BACBA product.

This chapter includes the following sections:

• "Configuring Configuration Delivery Manager" section

• "Configuring CNS Access Registrar" section

• "Configuring CNS Network Registrar" section

• "Configuring BACBA Server to Receive TIBCO Events" section

• "Configuring the Cisco Configuration Engine" section

Configuring Configuration Delivery Manager

BACBA uses the optional Configuration Delivery Manager (CDM) property file to support two types of Configuration Engine setup. One is IMGW setup which supports Telnet download and console download and the other is CNS setup (HTTP setup) which supports HTTP download. Both setups are present in the CDM property file.

You must modify the contents of the cdm.properties file, on the machine where you installed the BAC.

To modify the contents of the cdm.properties file, follow these steps:

Step 1 Using the text editor of your choice (vi is used in this example), open the $BAC_HOME/cdm/properties/cdm.properties file:

vi $BAC_HOME/cdm/properties/cdm.properties

Step 2 To support IMGW, the following lines must be listed in cdm properties:

Config Engine_index=ip address
Config Engine_index.type=IMG
Config Engine_index.WEBADDRESS=http://ip address/imgw/IMGWDevice
Config Engine_index.BACNAME=hostname

Where the index starts from 0. The ip address is the BAC machine running the Configuration Engine software.

Step 3 To support CNS setup, the following line must be listed in cdm properties:

Config Engine_index=ip address

The following is an example of what values to enter to support both IMGW and CNS:

Config Engine_0=170.21.255.255
Config Engine_0.type=IMG
Config Engine_0.WEBADDRESS=http://170.21.255.255/imgw/IMGWDevice
Config Engine_0.BACNAME=bac-ma123-1

Config Engine_1=170.21.255.255

Configuring CNS Access Registrar

The Broadband Access Center uses the optional Cisco Networking Services Access Registrar (AR) product for PPP authentication. To allow these operations to work successfully, you must configure BACBA to work with the Cisco CNS Access Registrar product.

If you intend to use Cisco Access Registrar for AAA services, make sure it is properly configured after you install BAC. You might need to make changes to the configuration of Cisco Access Registrar or apply a patch release to the software.

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

Configuring CNS Network Registrar

The BACBA software handles assignment and reservation of IP addresses for the signaling and bearer channels. It also updates the IP to hostname mapping in DNS for the signaling channel and checks the forward and reverse zone. It uses the nameserver cache daemon to cache name resolution in memory. It diminishes the administrative burden associated with address management.

To allow these operations in the BAC environment, you must configure the Cisco Networking Services Network Registrar (CNS NR) product.

During installation of the BACBA product, you can edit the Cisco CNS Network Registrar related $BAC_HOME/resourceMgr/common/resourceMgr.cfg and ipservice.cfg configuration files by indicating that you wish to configure the Cisco CNS Network Registrar product.

For detailed instructions about obtaining and registering the CNS Network Registrar license, go to the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/ciscoasu/nr/nr60/install/index.htm

Configuring BACBA Server to Receive TIBCO Events

In order for the BACBA server to receive TIBCO events from the Cisco Configuration Engine device by using the rvrd daemon, rvrd must be configured only if Cisco Configuration Engine and BAC are on different networks. For information about configuring RVRD, see "Setting Up the Cisco Configuration Engine" section.

Note If you run Cisco Configuration Engine and BAC on the same network, then you do not have to configure RVRD. For information on how to configure the rvrd software, refer to the TIB/Rendezvous Administration Guide.

Configuring the Cisco Configuration Engine

Cisco BACBA uses the optional Cisco Configuration Engine for aggregator provisioning.

To allow these operations to work successfully, you must configure the Cisco Configuration Engine. Refer to the Cisco Configuration Engine documentation URL for detailed information:

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cns/ce/rel13/index.htm

Note The Cisco Configuration Engine that BAC is using supports SSH (Secure Shell protocol) 1.5/2.0. Secure Shell (SSH) is a server feature that provides a secure, encrypted remote connection to a router.