Introduction to the Broadband Access Center CLI
This chapter describes licensing requirements for the Cisco Broadband Access Center (BAC) Device Provisioning Engine (DPE) and how you can access the command-line interface (CLI) of the DPE.
–
Accessing the DPE CLI from a Local Host
–Accessing the DPE CLI from a Remote Host
DPE Licensing
Licensing controls the number of DPEs that you can use. To configure the DPE from the CLI, you must have a valid license. If you run the commands described in this guide on an unlicensed DPE, the following message appears:
This DPE is not licensed. Your request cannot be serviced. Please check with your
system administrator for DPE licenses.
For details on how to obtain the license file, refer to the Release Notes for Cisco Broadband Access Center 4.0. Once you receive your license file, install BAC. Then, from the administrator user interface, use the following procedure to install the licenses that you purchased:
Note Before installing your license, ensure that you back it up in case you have to reinstall BAC.
Step 1 Once you receive your license file, save each file on the system from which you intend to launch the BAC administrator user interface.
Step 2 Launch your web browser on that system.
Step 3 Enter the administrator's location using this syntax:
http://machine_name:port_number/
Note To access the administrator user interface via HTTP over SSL, also known as HTTPS, enter:https://machine_name:port_number/
•machine_name—Identifies the computer on which the RDU is running.
•port_number—Identifies the computer port on which the server side of the administrator
application runs.
The default port number is:
–8100 for HTTP over TCP
–8443 for HTTP over SSL
The main login page appears.
Step 4 Enter the default username (admin) and default password (changeme).
Note If you are logging in for the first time, the Change Password screen appears. Enter a new password and confirm it. The password that you enter must have at least eight characters.
Step 5 Click Login.
The Main Menu page appears.
Step 6 Click the license link at the top of the Main Menu page, or choose Configuration > License Keys.
The Manage License Keys page appears.
Step 7 In the License File field, enter the complete path to the location of the license file on your local system. Remember to include the name of the license file while specifying the pathname. Or, click Browse.
Step 8 Click Add/Upgrade.
The details regarding the license file appear. For details on licensing in this release, refer to the Release Notes for Cisco Broadband Access Center 4.0.
Accessing the DPE CLI
To access the DPE CLI, open a Telnet session to port 2323 from a local or remote host. Before you proceed, however, familiarize yourself with the access levels on the DPE.
BAC specifies a certain access level to authorize DPE access. Table 1-1 identifies the two access levels, which are also known as command modes. Each mode provides access to a specific set of commands.
Use the enable, page 2-3, and disable, page 2-3, commands to switch between the two modes.
You can access the DPE CLI following the steps described in:
•Accessing the DPE CLI from a Local Host
•Accessing the DPE CLI from a Remote Host
Accessing the DPE CLI from a Local Host
To access the CLI from a local host, you can use:
# telnet local_hostname 2323
where local_hostname specifies the name of the local host.
Or, you can use:
# telnet 0 2323
Defaults
Once you access the CLI, enter the DPE password to continue. The default login and privileged mode passwords are changeme.
Note Although the default DPE password is changeme, it is not the same password that you use to access the BAC administrator user interface.
For information on how to change the login password and the privileged mode password, see
password, page 2-7, and enable password, page 2-4, respectively.
Examples
This result occurs when you access the DPE from a local host specifying its hostname.
bac_host# telnet local_bac_dpe 2323
Trying 10.10.2.25...
Connected to local_bac_dpe.example.com.
Escape character is '^]'.
Broadband Access Center 4.0 (SOL_BAC4_0_0_00000000_0000)
Device Provisioning Engine local_bac_dpe
User Access Verification
Password: <changeme>
local_bac_dpe> enable
Password: <changeme>
local_bac_dpe#
This result occurs when you access the DPE from a local host without specifying its hostname.
bac_host# telnet 0 2323
Trying 0.0.0.0...
Connected to 0.
Escape character is '^]'.
Broadband Access Center 4.0 (SOL_BAC4_0_0_00000000_0000)
Device Provisioning Engine local_bac_dpe
User Access Verification
Password: <changeme>
bac_dpe> enable
Password: <changeme>
bac_dpe#
Accessing the DPE CLI from a Remote Host
To access the CLI from a remote host, enter:
# telnet remote_hostname 2323
where remote_hostname specifies the name of the remote host.
Note If you cannot establish a Telnet connection to the CLI, the CLI server is probably not running. You may need to start the server. To start the server, enter:
# /etc/init.d/bprAgent start cli
Defaults
Once you access the CLI, you must enter the DPE password to continue. The default login and privileged mode passwords are changeme.
Note Although the default DPE password is changeme, remember that it is not the same password that you use to access the BAC administrator user interface.
For information on how to change the login password and the privileged mode password, see password, page 2-7, and enable password, page 2-4, respectively.
Examples
This result occurs when you access the DPE from a remote host specifying its hostname.
bac_host# telnet remote_bac_dpe 2323
Trying 10.10.2.10...
Connected to remote_bac_dpe.example.com.
Escape character is '^]'.
Broadband Access Center 4.0 (SOL_BAC4_0_0_00000000_0000)
Device Provisioning Engine remote_bac_dpe
User Access Verification
Password: <changeme>
remote_bac_dpe> enable
Password: <changeme>
remote_bac_dpe#
Feedback