|
|
Step 8 of the CSRC installation process is to configure your cable network for CSRC before you begin using the software. This chapter discusses example configurations for setting up Cisco Network Registrar and the uBR IOS.
This chapter also describes how to change the encoded passwords in the csrc.cfg file.
The CSRC distribution media contains a Perl script and companion files that you can use to set up Cisco Network Registrar (CNR) for operation with CSRC. The /opt/csrc/conf directory on the CSRC distribution media contains the following components:
For more information, see the following guides:
Before you run the cnrConfig.pl script, you must set the CNR license key, using the following command syntax:
license set key=value
To set the license key you must run the nrcmd program in interactive mode. For example, to set the license key to 1234 abcd 5678 efgh, enter the following (exiting is not necessary):
nrcmd -C cluster1 -N admin -P aicuser nrcmd> license set key=1234-abcd-5678-efgh 100 Ok nrcmd> exit
The cnrConfig.pl script is used to configure CSRC for CNR and has the following syntax:
# perl cnrConfig.pl [-dxk] [-f cnrCfgTemplate] [-O qryOutput] [-I qryInput]
where:
-d indicates to run in debug mode and to write program trace information to stdout.
-x creates the nrcmd batch file, but does not execute it. This option indicates on stdout what the batch command line would have been had it been executed.
-k saves the generated cnrConfig.cmd file. By default, this file is deleted after the nrcmd command executes since it contains plain text password information.
-f cnrCfgTemplate indicates the path to the cnrConfig.tmpl template file. By default, the cnrConfig.pl script assumes the cnrConfig.tmpl file resides in the current directory.
-O qryOutput indicates to write the CNR configuration information you specify interactively to the file specified in qryOutput.
-I qryInput indicates to read needed information from the file specified in qryInput instead of querying you interactively for the information.
For more information about the cnrConfig.pl script options, see the following sections.
The -f cnrCfgTemplate option indicates the path to the CNR configuration data template file. The cnrCfgTemplate argument must specify the path. The default is the cnrConfig.tmpl file in the current directory.
The generated and updated template file resides in the specified directory portion of the pathname or in the default directory location if this option is not specified. In all cases, the name of the generated CNR batch file is cnrConfig.cmd.
The -O qryOutput option writes the CNR configuration information you entered to the file specified in qryOutput. This allows you to subsequently execute the cnrConfig.pl script without requiring your input. It also provides a record of the nrcmd transaction. Cisco recommends that you execute the cnrConfig.pl script with the -O option specified if you intend to interactively provide answers to the script's questions.
You can choose to simply create a file manually instead of using the -O qryOutput option. If you do, you must provide the answers in the order in which the script asks the questions. For more information, see "The cnrConfig.pl Script Operation" section.
 | Caution The file you specify in qryOutput will contain plain text passwords. Be sure to protect the file after it is created. |
The -I qryInput option reads needed information from the file specified in qryInput instead of prompting you for it. You can create this file using the -O qryOutput option when you interactively execute the cnrConfig.pl script, or you can create the file manually.
If you create the qryInput file manually, you must provide the answers to the script's questions in the following format:
The following are examples of valid tokens:
validToken | # valid data and comment |
"Good Value" | # quoted valid white space |
"C:\A Good\Value Combo\" | # quoted valid white space |
1.2.3.4.5.6.7.8 | # valid multi-valued data |
The following are examples of invalid tokens:
Bad Value | # must quote tokens with valid white space |
"C:\A Bad Value" | # invalid white space |
C:\"Also Bad" | # must quote the entire token |
The cnrConfig.pl script first prompts for the following information about your CSRC installation in the order specified:
You can choose to specify this information interactively or non-interactively using an input file. In interactive mode, you enter the needed information when the cnrConfig.pl script prompts you for it. You can enter ? to display a brief description of the desired information before you enter a value. After you finish entering the needed information, the cnrConfig.pl script displays all of the values you entered for your verification. You can then accept the values or abort the program, leaving CNR configuration unchanged.
In non-interactive mode, the cnrConfig.pl script reads the values for needed information from an input file. In this case, the cnrConfig.pl script does not allow you to verify the values or abort any changes to the CNR configuration. For more information, see the "-O qryOutput" section and the "-I qryInput" section.
After the cnrConfig.pl script gathers the needed information, it does the following:
1. Parses the associated cnrConfig.tmpl template file (see the "The cnrConfig.tmpl Template File" section), replacing template tokens found in the cnrConfig.tmpl file with the associated values provided during the query phase.
2. Generates a CNR batch file called cnrConfig.cmd. This file resides in the directory specified by the -f option. If the -f option is not specified, the file resides in the current directory. The cnrConfig.cmd file is deleted by default. Use the -k option to save it.
3. Invokes the nrcmd command to run the CNR commands specified in the cnrConfig.cmd file.
4. Redirects stdout to store the results of the batch nrcmd session in a file called cnrConfigResults.out. This file resides in the same directory as the cnrConfig.cmd file.
The cnrConfig.pl script has the following limitations:
The cnrConfig.tmpl template file is a companion file on which the cnrConfig.pl script operates. The cnrconfig.tmpl file is actually a collection of CNR (nrcmd) commands. The file contains template tokens with the following format:
<<keyword>>
where <<keyword>> is an exact match for the name field of one of the cnrData hash elements defined at the beginning of the cnrConfig.pl script. A template token must match the value of one of the hash entries in the script file. If not, an error message appears, indicating the template token in error and its line number in the cnrConfig.tmpl file. The cnrConfig.pl script then aborts.
You can modify the default cnrconfig.tmpl file as desired. However, if you modify, add, or delete token templates, then you must also make the associated modifications to the cnrData associative array in the cnrConfig.pl script and to the ordering of these hash nodes in the sortedData array, if necessary. For information about making these modifications, see the cnrConfig.pl script.
The cnrConfig.tmpl file has the following limitations:
The CSRC distribution media contains an example configuration for the CableLabs uBR. This example configuration is available in the ubr-config.txt file in the distribution media's /opt/csrc/conf directory.
The passwords stored in the csrc.cfg file are encoded. If you change the LDAP or Cisco Network Registrar (CNR) password for the account that CSRC uses, you must update the password in the csrc.cfg file on each CSRC server host on which the file is present. To do this, you must first encode the password, using the csrcencode utility in the /opt/csrc/bin directory.
To encode a password, enter the following command:
# csrc_install_dir/bin/csrcencode password encoded password
where password is the password you want to encode and encoded password is the encoded password string that results from the command's execution.
After you encode the new password, you can copy the encoded password string and insert it into the csrc.cfg file in place of the previous password string.
Posted: Wed Oct 27 14:05:49 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.