|
This chapter describes the configuration activities that you perform using these Main Menu options:
The Configuration page displays a list of all default configurations that you can modify using the Broadband Provisioning Registrar (BPR) administrator user interface. These configurations include:
The Defaults page, found under the Configuration option, lets you access the default settings for the overall system and the regional distribution unit (RDU). (See Figure 4-1.)
This section describes how to view and change these default settings.
To change your system defaults:
Step 2 Select Defaults from the Secondary Navigation bar and the Configure BPR Defaults page appears. (See Figure 4-1.)
Step 3 Enter the appropriate information for the SNMP read and write community strings.
Note The default values appearing in this page can be changed using the BPR application program interface. Refer to the Broadband Provisioning Registrar Developer's Guide for additional information. |
This information identifies the community strings that let you control access to MIB information stored on devices that support the SNMP protocol. Together, the read and write community strings act as passwords to access SNMP agent information. The write community string must be known by any device before information can be set on the SNMP agent.
Note To prevent unauthorized modification of configuration information, these community strings should be set on all SNMP Agents. |
Step 4 Click Submit when complete. Once the changes have been added to the administrative database, the BPR defaults successfully modified page appears. (See Figure 4-2.)
Step 5 Click the link indicated in Figure 4-2, and the Configure BPR Defaults page appears. (See Figure 4-1.)
To change your RDU default settings:
Step 2 Select Defaults from the Secondary Navigation bar and the Configure BPR Defaults page appears. (See Figure 4-3.)
Step 3 Click the RDU Defaults link to the left of the page, and the RDU Defaults page appears. (See Figure 4-4.)
Step 4 Click either Enabled or Disabled to activate or de-activate the Promiscuous mode within the RDU.
Step 5 Click Submit when complete. Once the changes have been made, the Defaults successfully modified page appears. (See Figure 4-5.)
Step 6 Click the link indicated in Figure 4-5, and the RDU Defaults page appears. (See Figure 4-4.)
DHCP criteria describes the specific criteria for a device when selecting a scope in Network Registrar. For example, a DHCP criteria called provisioned-docsis has an inclusion selection tag called tagProvisioned. The DHCP criteria is associated to a DOCSIS modem and, when this modem requests an IP address from the Network Registrar, Network Registrar will look for scopes that are associated to the scope selection tag called tagProvisioned and are in the correct network segment.
To access the DHCP Criteria page:
Step 2 Select DHCP Criteria from the Secondary Navigation bar and the Manage DHCP Criteria page appears. (See Figure 4-6.)
Step 2 Enter the name of the DHCP criteria you want to create.
Step 3 Enter the DHCP Criteria client class name.
Step 4 Enter the inclusion and exclusion selection tags.
Note When creating new DHCP Criteria, the client class and selection tag names you have to enter must be set up, using the same names, from within Network Registrar. Refer to the Network Registrar User's Guide and the Network Registrar CLI Reference Guide if you require additional information on these activities. |
Step 5 You can add or modify the properties that are added on the DHCP criteria. Enter or select a Property Name, or select an existing name, and enter or modify the appropriate Property Value.
Step 6 Click Add after changing or creating the property name-value pair.
Step 7 Click Submit when complete. Once the changes have been added to the administrative database, the DHCP criteria successfully added page appears. (See Figure 4-8.)
Step 8 Click the link indicated in Figure 4-8, and the Manage DHCP Criteria page appears. (See Figure 4-6.)
To modify existing DHCP criteria:
Step 2 Make the desired changes, to the client class, inclusion and exclusion selection tags, and the property value settings.
Step 3 Click Submit when complete. Once the criteria changes have been added to the administrative database, the DHCP criteria successfully modified page appears. (See Figure 4-10.)
Step 4 Click the link indicated in Figure 4-10, and the Manage DHCP Criteria page appears. (See Figure 4-6.)
Note Subsequent device configurations will include the changes you implement here. However, all existing configurations do not get changed. To make the changes in any existing configuration, you must regenerate the configuration using the application programming interface (API). |
Deleting DHCP criteria using the administrator application will not delete the actual DHCP server configurations from the DHCP server. You must delete the DHCP server configurations manually. To delete an existing criteria:
Step 2 Click the Delete icon corresponding to the desired criteria, and a deletion dialog box (similar to Figure 4-11) appears.
Step 3 Click OK to delete the criteria. Once the criteria is deleted, the Manage DHCP Criteria page appears. (See Figure 4-6.)
Note You can delete a DHCP criteria only if there are no devices associated with that criteria. |
Custom properties are conditions applied to client classes configured in Network Registrar. To access the Custom Property configuration page:
Step 2 Select Custom Property from the Secondary Navigation bar and the Configure Custom Properties page appears. (See Figure 4-12.)
Step 2 Enter the name of the new custom property.
Step 3 Select a custom property type from the drop-down list.
Step 4 Click Submit when complete. Once the property has been added to the administrative database, the Configure Custom Properties page appears. (See Figure 4-14.)
Step 5 Click the link indicated in Figure 4-14, and the Configure BPR Custom Properties page appears. (See Figure 4-12.)
To delete a custom property definitions:
Step 2 Click the Delete icon corresponding to the desired custom property, and the custom properties deletion dialog box appears. (See Figure 4-15.)
Step 3 Click OK to delete the custom property. Once the custom property is deleted the Configure Custom Properties page appears.
Caution You can delete custom properties even if they are currently in use. This could cause extreme difficulty to other areas where the properties are in use. |
BPR comes with default extension points for Cisco Network Registrar. (See Figure 4-16.)
Caution The information found in this page is used for device detection. Before changing the information in these fields, verify that doing so will not adversely affect the device detection function. |
Table 4-1 identifies the fields and buttons shown in Figure 4-16.
Table 4-1 Configure BPR Extension Points Page
Field or Button | Description |
---|---|
Identifies attributes taken from the Network Registrar request dictionary. |
|
Identifies attributes taken from the Network Registrar environment dictionary. |
|
Using the BPR administrator you can manage the external files served by a TFTP server (Figure 4-17.) You can add, delete, replace, or export any file type, including these:
Table 4-2 identifies the fields and buttons shown in Figure 4-17.
Table 4-2 Manage External Files Page
To add an existing external file:
Step 2 Select External Files from the Secondary Navigation bar. The Manage External Files page appears.
Step 3 Click Add and the Add External Files page appears as shown in Figure 4-18.
Step 4 Enter the Source filename and the external (destination) filename.
Note If you do not know the exact name source file, use the Browse function to navigate to the desired directory and select the file. By default, file sizes up to 12 MB are supported. |
Step 5 Click Submit to add the file. A confirmation page appears to indicate that the file has been added.
Table 4-3 identifies the fields and buttons shown in Figure 4-18.
Table 4-3 Add External Files Page
Field or Button | Description |
---|---|
Identifies the filename, including the complete path, of the file to be added. |
|
Lets you navigate through the computer to locate the desired source file. |
|
To replace an existing external file:
Step 2 Select External Files from the Secondary Navigation bar.
Step 3 Click the link that corresponds to the desired file. The Replace External Files page (Figure 4-19) appears. Note that the selected filename already appears on this page.
Step 4 Enter the path and filename of the source file to be used as a replacement for the displayed external filename.
Note If you do not know the exact name or location of the source file, use the Browse function to navigate to the desired directory and select the file. |
Step 5 Click Submit, to replace the selected file.
Step 6 After submitting the replacement file, a confirmation page appears to indicate that the replacement was performed successfully.
Table 4-4 identifies the fields and buttons shown in Figure 4-19.
Table 4-4 Replace External Files Page
Field or Button | Description |
---|---|
Identifies the filename and pathname, of the source file to be used. |
|
Lets you navigate through the computer to locate the desired source file. |
|
To export an external file, when the Internet Explorer browser is used:
Step 2 Select External Files from the Secondary Navigation bar.
Step 3 Enter the filename of the external file, in the External Files field, that you want to export.
Step 4 Click Search. The appropriate file should appear in the External Files list.
Step 5 Click the Export icon that corresponds to the selected file. A dialog similar to that shown in Figure 4-20 appears. Note that the name of the selected file already appears on this page.
Step 6 Select Save As from the File menu and save the file in the appropriate directory.
Note If you export a *.cm file (or any other binary file type), while using a Netscape browser, a series of standard save dialogs are displayed to allow the file to be exported with whatever filename and directory you choose. |
Complete this procedure to delete an existing external file:
Step 2 Select External Files from the Secondary Navigation bar.
Step 3 Enter the filename of the external file, in the External Files field, that you want to modify.
Step 4 Click Search. The appropriate file will appear in the External Files list.
Step 5 Select the appropriate file or files.
Step 6 Click Delete and a confirmation dialog box appears.
Step 7 Click OK to delete the file or Cancel to return to the Manage External Files page.
Note You cannot delete a file as long as it has a class of service associated with it. |
Using the BPR administrator, you can configure the classes of service offered to your customers. For example, you can associate DOCSIC options with different DOCSIS classes of service. You can use the BPR administrator user interface to add, modify, view, or delete any selected class of service. Start with the Manage Class of Service page, as shown in Figure 4-21.
Table 4-5 identifies the fields and buttons shown in Figure 4-21.
Table 4-5 Configure Class of Service Page
Field or Button | Description |
---|---|
A drop-down list that identifies the technology classes of service that you want to search for. This includes: Note Refer to the "Technology Defaults" section, for additional information on these areas of technology. |
|
Lets you search for all available classes of service belonging to the group of services selected above. |
|
To add a specific class of service:
Step 2 Select Class of Service from the Secondary Navigation bar.
Step 3 Click Add. The Add Class of Service page appears as shown in Figure 4-22. This page identifies the various settings for the selected class of service.
Step 4 Enter the name of your new class of service.
Step 5 Select a Class of Service Type.
Step 6 Enter a Property Name and Property Value in the appropriate fields. After entering this information, it is referred to as a Property Name:Property Value pair. The Property name identifies the file to be booted and the Property value is the binary file that is actually loaded into the device.
Assume that you want to create a new class of service called Gold-Classic for DOCSIS modems. You might:
a. Enter Gold-Classic as the Class of Service Name.
b. Select DOCSIS from the service type drop-down list.
c. Select the property /COS/DOCSIS/file.
d. Enter Gold-Classic.cm in the Property Value field and then continue with the rest of this procedure.
Step 7 Click Add to add the new class of service.
Step 8 Click Submit to finalize the process or Reset to return to the Manage Class of Service page.
Step 9 After adding the class of service, a confirmation page appears to indicate that the addition was performed successfully.
Caution When adding a DOCSIS class of service, you must specify the property /cos/docsis/file with the name of a previously added external file. |
Table 4-6 identifies the fields and buttons shown in Figure 4-22.
Table 4-6 Add Class of Service Page
Note Subsequent device configurations will include the changes you implement here. However, all existing configurations do not get changed. To make the changes in any existing configuration, you must regenerate the configuration using the application programming interface (API). |
To modify class of service properties:
Step 2 Select Class of Service from the Secondary Navigation bar.
Step 3 Select the class of service to be modified.
Step 4 Click the link corresponding to the desired class of service. The Modify Class of Service page appears as shown in Figure 4-23. Note that the selected class of service name and type are displayed beneath the page description.
Step 5 Make the necessary modifications to the name:value pairs, then click Add.
Step 6 Click Submit to make the modifications to the class of service.
Step 7 After modifying the class of service, a confirmation page appears to indicate that the modification was performed successfully.
Table 4-7 identifies the fields and buttons shown in Figure 4-23.
Table 4-7 Modify Class of Service Page
Step 2 Select Class of Service from the Secondary Navigation bar.
Step 3 Click the Delete icon for any desired class of service, and a confirmation dialog box similar to Figure 4-24 appears.
Step 4 Click OK to delete the file or Cancel to return to the Modify Class of Service page. (See Figure 4-23.)
Note A class of service cannot be deleted if devices are associated with it. |
Software licenses are used to activate specific features or to increase the functionality of your installation. Each is available as either a permanent license or an evaluation license.
Caution Do not attempt to deploy into a fully operational network with an evaluation license key installed. Any provisioning done using an evaluation license will be disabled when that evaluation license expires. |
Software licenses are entered during installation, as described in the Broadband Provisioning Registrar Installation Guide. However, when you upgrade from an evaluation license to a permanent license, you do not have to re-install the software. You can perform the upgrade directly from the BPR administrator user interface; you do not have to repeat the entire installation process.
The Manage License Keys page (Figure 4-25) displays a list of licenses that have been entered for your implementation. This BPR release supports both evaluation and permanent licenses for high-speed data (DOCSIS cable modems), residential VoIP (media termination adapters), and digital set-top boxes. The status of each available license is also displayed as either active, expired, not installed, or identifies the expiration date.
Note You can upgrade your evaluation licenses to permanent status. You can also upgrade a permanent license to increase the number of authorized devices. When you reach the limit of you number of licensed devices, new devices will not be provisioned, but exiting devices that are already provisioned continue to receive service. |
Table 4-8 identifies the fields and buttons shown in Figure 4-25.
Table 4-8 Manage License Keys Page
To add, modify, or delete a license:
Step 2 Place your cursor in the License Key field.
Step 3 Enter the new license key.
Step 4 Click Add/Upgrade to install the new license key. If you enter a permanent license key, it overwrites the corresponding evaluation key (if that key was installed). If you enter a license key (permanent or evaluation) for a new technology, it will appear in the technology list.
BPR has the capability to publish the provisioning information it tracks to an external datastore in real time. (See Figure 4-26.) To do this, a publishing plug-in must be developed to write the data to the desired datastore. Refer to the Broadband Provisioning Registrar Developer's Guide for additional information.
Note Care must be taken when using publishing plug-ins as they can decrease system performance. |
Table 4-9 identifies the fields and buttons shown in Figure 4-26.
To publish changes to an external datastore:
Step 2 Select Publishing from the Secondary Navigation bar. The Manage Publishing page appears as shown in Figure 4-26. This page displays a list of all available database plug ins and identifies the current status of each.
Step 3 Click on the appropriate dash or check symbol to enable or disable the required plug in. Note that as you click these symbols, the current status toggles from enabled (dash) to disabled (check). (See Figure 4-27.)
To modify the publishing plug-in settings:
Step 2 Select Publishing from the Secondary Navigation bar. The Manage Publishing page appears similar to that shown in Figure 4-27.
Step 3 Click the link corresponding to the plug-in you want to modify. The Modify Publishing Plug-in Settings page appears similar to that shown in Figure 4-28.
Step 4 Enter the required values in the Server, Port, IP Address, User, Password, and Confirm Password fields. These are all required fields and you must supply this information before proceeding.
Step 5 Click Submit to make the changes to the selected plug-in or Reset to clear all fields on this page.
The Technology Defaults page, available from the BPR Main Menu, gives you access to the current default settings for these supported technologies:
The Computer Defaults page (Figure 4-29) displays a list of default values currently applied to the computers supported by BPR.
Table 4-10 identifies the fields and buttons shown in Figure 4-29.
Table 4-10 Configure Computer Defaults Page
Note Any changes made will not affect the current devices. |
The Configure Custom CPE Defaults page (Figure 4-30) displays a list of default values currently applied to the computers supported by BPR.
Table 4-11 identifies the fields and buttons shown in Figure 4-30.
Table 4-11 Configure Custom CPE Defaults Page
Note Any changes made will not affect the current devices. |
The Configure DOCSIS Defaults page (Figure 4-31) displays a list of default DOCSIS values currently applied to cable modems supported by BPR.
Table 4-12 identifies the fields and buttons shown in Figure 4-31.
Note Any changes made will not affect the current devices. |
Table 4-12 Configure DOCSIS Defaults Page
The Configure DSTB Defaults page (Figure 4-32) displays a list of default values currently applied to digital set-top boxes supported by BPR.
Table 4-13 identifies the fields and buttons shown in Figure 4-32.
Table 4-13 Configure DSTB Defaults Page
Note Any changes made will not affect the current devices. |
XGCP is a gateway control protocol that lets external call agents control gateways in a Voice over IP (VoIP) environment. The Configure XGCP Defaults page (Figure 4-33) displays a list of default values currently applied to the computers supported by BPR.
Table 4-14 identifies the fields and buttons shown in Figure 4-33.
Table 4-14 Configure XGCP Defaults Page
Field or Button | Description |
---|---|
Enables or disables the use of the old string format, which does not include the version number. |
|
Note Subsequent device configurations will include the changes you implement here. However, all existing configurations do not get changed. To make the changes in any existing configuration, you must regenerate the configuration using the application programming interface (API). |
Posted: Wed Apr 23 16:42:20 PDT 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.