-
null
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to install Broadband Access Center (BAC) in a lab environment to demonstrate product functionality and how to configure a cable modem termination system (CMTS) and the Cisco Network Registrar server to support BAC.
When you install BAC in a lab environment, the installation program installs all components on a single server. The lab installation program is designed to keep the installation and configuration as simple as possible by using a predefined overall system configuration. When you complete the installation, however, you must perform some setup on a CMTS and on Network Registrar.
This chapter features:
•Installing in a Lab Environment
•Configuring Network Registrar and a CMTS
You can install BAC in a lab environment on a computer running the Solaris 8 or 9 operating system. Before you run the installation program, use the following checklist to ensure that you are ready:
1. Verify the prerequisite system hardware and software requirements described in Overview, page 1-1
2. Ensure that you have root access to the computers where you intend to install BAC.
3. Keep your BAC evaluation license key or keys at hand. You need a valid license key for each technology that you want to provision with BAC.
4. Ensure that Network Registrar is installed and running on the servers on which you intend to install BAC extensions.
Note We recommend that you use Network Registrar 6.2.3.2 or later.
5. Determine the destination directory in which you want to install BAC. The default directory is /opt/CSCObpr.
Note We recommend that you have at least 350 MB of disk space available.
6. For extensions, determine the name of provisioning group to which the Network Registrar server belongs.
7. Verify that you have the necessary Network Registrar configuration files. For an example of these configuration files, see Network Registrar Configuration File Example, page A-1.
The lab installation program uses predefined default values for the installation that assume a specific network configuration. You are prompted for:
•BAC destination directory
•Network Registrar administrator username and password
•Shared secret password
You can install BAC in a lab environment in two modes:
To install BAC in a lab environment:
Step 1 Log in to the intended BAC host as root.
Step 2 At the Solaris system prompt, change the 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 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. Use this syntax:
gunzip BACC_271_SolarisK9.gtar.gz
c. Unpack the file with the .gtar extension that gunzip decompressed:
tar -xvf BACC_271_SolarisK9.gtar
The utility creates the /BACC_271_SolarisK9 directory in which the installation program, setup.bin, is extracted.
d. Change to the /BACC_271_SolarisK9 directory:
cd BACC_271_SolarisK9
Step 3 Enter this command to start the installation program:
> ./setup.bin -console
The installation program verifies that you have installed the required patches to the Solaris operating system. When the verification is complete, the program displays welcome information.
Step 4 Press Enter to continue.
Step 5 The program prompts you to choose the installation type. To choose Lab installation, enter l.
For example:
Choose Installation
Choose the type of BPR installation you want to install.
The Lab installation will store all components in the chosen destination.
Otherwise, you can select individual components and destinations.
Enter C for individual components or L for lab [C]:l
Step 6 To confirm the installation type and continue, enter y and press Enter.
Step 7 The program asks if you intend to provision voice technology devices.
For example:
Are you going to use a device(s) that supports Packetcable voice technology?
If you are going to use Packetcable devices we need some more info.
Enter Yes to Install Packetcable and No if you don't want Packetcable
installed [No]: y
If yes, enter y and press Enter; otherwise, enter n and press Enter.
Step 8 To confirm your entry, press Enter.
Step 9 The program displays a message that it is validating Lab settings, followed by the destination directory prompt. To accept the default home directory, /opt/CSCObpr, press Enter.
For example:
Destination Directory
Directory path for BPR_HOME
Location BPR_HOME
Installation Directory [/opt/CSCObpr]
Step 10 When the program asks if you want to create the default installation directory, enter y and press Enter.
For example:
Choosing yes will create the directory during the installation. Choosing no
will allow a different directory to be chosen.
The directory /opt/CSCObpr does not exist. Create it? (y/n/?) [yes]
Step 11 Confirm the destination directory. Press y and Enter to continue.
Step 12 The Network Registrar username and password prompt appears. Enter a valid administrator username and password. Enter the password again to confirm it.
For example:
Cisco Network Registrar Username and Password
Enter the administrator username and password for the NR server.
Enter the username and password for the NR server to be used in the lab
installation. You must confirm the NR password.
Network Registrar adminstrator Username [admin] admin
Network Registrar adminstrator Password [] changeme
Confirm Network Registrar Password [] changeme
Step 13 The program redisplays the administrator username, password, and password confirmation, and prompts you to confirm this information. Enter y and press Enter to continue.
Note If you chose not to install the voice technology in Step 7, jump to Step 18; otherwise, continue with this procedure.
Step 14 Enter the KDC realm name. Enter the KDC Interface Address and FQDN. Ensure that you enter the realm name that you used for all DPEs in the provisioning group; press Enter.
For example:
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.4.1]
KDC FQDN [bac-test.cisco.com]
KDC Realm [CISCO.COM]
Step 15 The program redisplays the KDC realm and prompts for a confirmation. Enter y and press Enter.
Step 16 The PacketCable Properties prompt appears. Enter the appropriate information and press Enter. Keep in mind that the KDC realm name you enter here must match the one you entered in the previous screen.
For example:
Enter PacketCable properties
Enter KDC Realm Name [CISCO.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 17 The program prompts you to confirm the PacketCable properties information. Enter y and press Enter to continue.
Step 18 Enter the shared secret password that you want to use for authentication between the BAC servers; the default password is secret. Press Enter.
For example:
Shared Secret Password
Enter the password to be used for authentication
among the BPR servers.
If you are performing a lab installation, then the password will be used for
all the servers. If this is a component installation, then the password you
enter must be the same as the components previously installed.
Enter the Shared Secret Password [secret] secret
Step 19 Press Enter to continue.
Step 20 The program displays the installation parameters that you selected. Enter y and press Enter to install the lab software.
For example:
Installation Parameters
This screen shows the installation parameters that you have chosen:
========== Confirmation ==========
The Lab/Demo Installation will install all components using the following
parameters:
Installation directory:/opt/CSCObpr
Is this correct (y/n/q/?) [yes]
Step 21 When installation is complete, the Installation Summary appears. Press Enter to exit the program.
Note Once installation is complete, install your licenses and the chain of certificates, without which the KDC does not start.
The lab installation prompts for:
•BAC destination directory
•Network Registrar administrator username and password
•Shared secret password
To install BAC in a lab environment from the GUI:
Step 1 Using an X-Windows client, log in to the computer on which you intend to install the BAC components, with root access.
Step 2 Ensure that the gzip and gtar utilities are available on your system to decompress and unpack the 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. Use this syntax:
gunzip BACC_271_SolarisK9.gtar.gz
c. Unpack the file with the .gtar extension that gunzip decompressed:
tar -xvf BACC_271_SolarisK9.gtar
The utility creates the /BACC_271_SolarisK9 directory in which the installation program, setup.bin, is extracted.
d. Change to the /BACC_271_SolarisK9 directory:
cd BACC_271_SolarisK9
Step 3 To start the installation program, enter:
> ./setup.bin
The installation program verifies that you have installed the correct patches on the Solaris operating system. When the verification is complete, the program displays welcome information.
Step 4 Click Next.
Step 5 The Choose Installation Type screen appears. Click the Lab radio button, then click Next.
Step 6 The lab installation program automatically checks for the presence of a TFTP server. If a TFTP server is detected, error messages appear and the installation terminates; otherwise, a PacketCable Panel screen appears.
Determine if you need to install the voice technology option and click:
•Yes if you want to install the voice technology option.
•No if you do not have a valid license key for this technology.
Step 7 Click Next.
Step 8 The Destination Directory screen appears. Enter the path of the directory in which you want to install BAC.
Step 9 Click Next.
Step 10 The installation program verifies that the selected installation directory exists and, if it does not, prompts you to automatically create it. Click Yes to continue. The installation program also confirms that the required disk space is available.
Step 11 The Network Registrar Username and Password screen appears. Enter the Network Registrar administrator username and password.
Step 12 Click Next.
Note If you chose not to install the voice technology from the PacketCable Panel in Step 6, jump to Step 16; otherwise, continue with this procedure.
Step 13 The Key Distribution Center Realm Name screen appears. You can choose to accept the default KDC Realm, FQDN, and interface address name; otherwise, enter the appropriate values.
Step 14 Click Next.
Step 15 The PacketCable Properties screen appears. Enter the appropriate information in the fields based on the following descriptions:
Step 16 Click Next.
Step 17 The Shared Secret Password screen appears. Enter and confirm the shared secret password.
Step 18 Click Next.
Step 19 The Lab Installation Parameters screen appears. This screen identifies the values that you have entered in the previous screens. To modify any of the values:
a. Click Back until the desired screen appears.
b. Make the necessary changes.
c. Click Next repeatedly until you return to this screen.
Step 20 Click Next to install the lab version of BAC.
Step 21 Once installation is complete, the Installation Summary appears. Click Finish.
For BAC to function, you need to set up Network Registrar client classes, policies, scopes, and selection tags. You also need to perform some configuration of CMTS devices.
Note The NR_HOME path that this procedure describes is defined as the Network Registrar installation directory (the default directory is /opt/nwreg2), followed by the /regional or /local directory depending on the Network Registrar version that is installed on your system. For example, if you have installed:
•Version 6.1 or later, use /opt/nwreg2/local/ for the local cluster and /opt/nwreg2/regional for the regional cluster.
•Versions lower than 6.1, use /opt/nwreg2/local.
To configure Network Registrar and CMTS devices:
Step 1 Set up scopes on your Network Registrar server. Use this syntax:
# NR_HOME/usrbin/nrcmd -N username -P password -b < BPR_HOME/cnr_ep/samples/bpr_cnr_hsd_sample_config.nrcmd
For example:
# /opt/nwreg2/local/usrbin/nrcmd -N admin -P changeme -b < /opt/CSCObpr/cnr_ep/samples/bpr_cnr_hsd_sample_config.nrcmd
Note The BPR_HOME/cnr_ep/samples/bpr_cnr_hsd_sample_config.nrcmd command runs a sample Network Registrar configuration script, which defines client classes, policies, scopes, and selection tags. You must update this file to reflect the IP address settings on your network. For information about this file, see Network Registrar Configuration File Example, page A-1. For detailed information about defining client classes, policies, scopes, and selection tags, refer to the Cisco Network Registrar User's Guide, 6.2.1.
Step 2 Enable the cable interface or interfaces on your CMTS with the correct IP addresses and DHCP helper address.
For example:
Note The IP addresses used here are identical to those in the sample script supplied with the BAC product. You must edit these addresses to match your own IP address range. Do not attempt to use these IP addresses in an operational environment.
# interface Cable3/0 qq
ip address 192.168.5.0 255.255.255.0
ip address 192.168.6.0 255.255.255.0 secondary
ip address 192.168.7.0 255.255.255.0 secondary
ip address 192.168.8.0 255.255.255.0 secondary
no ip directed-broadcast
no keepalive
cable downstream annex B
cable downstream modulation 64qam
cable downstream interleave-depth 32
cable downstream frequency 477000000
cable upstream 0 frequency 26000000
cable upstream 0 power-level 0
no cable upstream 0 shutdown
cable dhcp-giaddr primary
cable helper-address 10.10.4.10
Note A sample configuration script file is included with the BAC product. This file, called cmts_sample.cfg, resides in the BPR_HOME/cnr_ep/samples directory.
Step 3 To configure your CMTS to insert the DHCP relay agent information option in forwarded BOOTREQUEST messages, use this Cisco IOS command:
# ip dhcp relay information option
The default device detection logic in BAC uses DHCP Option 82 information (relay-agent information) to detect devices.
Step 4 To configure your CMTS so that it does not validate the relay agent information option in forwarded BOOTREPLY messages, use this IOS command:
# no ip dhcp relay information check