Chapter 1 Introduction to the BACC Command Line Interface

This chapter contains detailed information on the CLI commands that you use in conjunction with the DPE. It identifies how to start and stop the command line interface and differentiates between the hardware and Solaris device provisioning engines (DPEs).

The CLI described in this guide is used on both the DPE-590 and DPE-2115 devices. There are some differences between the commands used on these hardware DPEs and those used on the Solaris DPE. The "Command Usage" section identifies the commands used on either type of DPE.

Accessing the DPE Command Line Interface

You access the command line interfaces for hardware and Solaris DPEs in different ways. The hardware DPE is accessed using either telnet or by accessing the console port on the actual DPE device. The Solaris CLI can only be accessed by Telneting to port 2323.

Accessing the Hardware CLI

When using either the DPE-590 or DPE-2115, you must connect your computer to the serial console port on the hardware DPE . Once connected you should complete these steps:

Step 1

Initiate a Hyper Terminal connection between your computer and the DPE. Once the connection is made, you are prompted to enter the DPE password.

Step 2

Enter the DPE password and then continue with the CLI operations you need to perform.

Note

Although the default DPE password is changeme, it is NOT the same password used to enter into the BACC administrator's user interface.

Accessing the Solaris CLI

You can access a Solaris device provisioning engine command line interface in one of two different ways; from a remote host or from a local host.

Accessing the Solaris DPE from a Remote Host

To access the command line interface for a Solaris DPE, from a remote host, run this command:

Accessing the Solaris DPE from a Local Host

To access the command line interface for a Solaris DPE, from a local host, run either of these commands:

Note If a Telnet connection cannot be made to the Solaris CLI it is likely that the CLI is not running, you may need to start the CLI server using this command:

/etc/init.d/bprAgent start cli

Command Usage

Some CLI commands can be used on either the hardware or Solaris DPEs. Others however, can be used on one or the other, but not both. The DPEs supported by individual commands are identified appropriately in the descriptions of the individual commands. This support is also provided at a glance in Table 1-1.

Table 1-1 DPE/CLI Command Support
Command	DPE Support	Command	DPE Support	Command	DPE Support
aaa authentication	Both	no debug dpe event-manager	Both	show dpe	Both
clear bundles	Both	no debug dpe exceptions	Both	show dpe config	Both
clear cache	Both	no debug dpe framework	Both	show hostname	Both
clear logs	Both	no debug dpe messaging	Both	show interface ethernet <0...1> config	Hardware
clock set	Hardware	no debug dpe netsnmp	Both	show interface ethernet <0...1> stats	Hardware
debug dpe cache	Both	no debug dpe registration	Both	show interface ethernet <intf0\|intf1> config	Solaris
debug dpe connection	Both	no debug dpe registration - detail	Both	show interface ethernet <intf0\|intf1> stats	Solaris
debug dpe dpe-server	Both	no debug dpe snmp	Both	show ip	Both
debug dpe event-manager	Both	no debug dpe tftp	Both	show ip route	Both
debug dpe exceptions	Both	no docsis shared-secret	Both	show log	Both
debug dpe framework	Both	no dpe provisioning-group primary	Both	show log last <1....9999>	Both
debug dpe messaging	Both	no dpe provisioning-group secondary	Both	show log run	Both
debug dpe netsnmp	Both	no ip default-gateway	Hardware	show memory	Both
debug dpe registration	Both	no ip domain-name	Hardware	show packetcable snmp log	Both
debug dpe registration - detail	Both	no ip name-server	Hardware	show packetcable snmp log last <1..9999>	Both
debug dpe snmp	Both	no ip route	Hardware	show packetcable snmp log run	Both
debug dpe tftp	Both	no ntp server	Hardware	show running-config	Both
debug on	Both	no packetcable	Both	show syslog	Hardware
disable	Both	no packetcable registration encryption	Both	show syslog last	Hardware
docsis shared-secret	Both	no packetcable snmp key-material	Both	show syslog run	Hardware
dpe port	Both	no snmp-server community string [ro\|rw]	Both	show tftp files	Both
dpe provisioning-group primary	Both	no snmp-server contact	Both	show version	Both
dpe provisioning-group secondary	Both	no snmp-server host	Both	snmp-server community string [ro\|rw]	Both
dpe rdu-server (host)	Both	no snmp-server inform	Both	snmp-server contact	Both
dpe rdu-server (IP)	Both	no snmp-server location	Both	snmp-server host	Both
dpe reload	Both	no snmp-server udp-port	Solaris	snmp-server inform	Both
dpe shared-secret	Both	no syslog log-server	Hardware	snmp-server location	Both
dpe start	Both	no tacacs-sever <host>	Both	snmp-server reload	Both
dpe stop	Both	no tftp allow-create-dirs	Both	snmp-server start	Both
enable	Both	no tftp allow-override	Both	snmp-server stop	Both
enable password	Both	no tftp allow-read-access	Both	snmp-server udp-port	Solaris
exit	Both	no tftp allow-write-access	Both	support bundle cache	Both
		no tftp verify-ip	Both	support bundle state	Both
help	Both	ntp server (host)	Hardware	support daemon ftp enabled	Hardware
host (host)	Hardware	ntp server (IP)	Hardware	support daemon telnet enabled	Hardware
host (IP)	Hardware	packetcable enable	Both	syslog log-server	Hardware
hostname	Hardware	packetcable registration encryption	Both	syslog mode both	Hardware
interface ethernet <intf0\|intf1> provisioning enabled	Solaris	packetcable registration kdc-service-key	Both	syslog mode local	Hardware
interface ethernet <intf0\|intf1> provisioning fqdn <fqdn>	Solaris	packetcable registration policy-privacy	Both	syslog mode remote	Hardware
interface ethernet 0...1 ip address	Hardware	packetcable snmp key-material	Both	tacacs-server retries	Both
interface ethernet 0...1 ip enabled	Hardware	packetcable snmp timeout	Both	tacacs-server timeout	Both
interface ethernet 0...1 provisioning enabled	Hardware	password	Both	tacacs-sever <host>	Both
interface ethernet 0...1 provisioning fqdn	Hardware	ping (host)	Hardware	tftp allow-create-dirs	Both
ip default-gateway	Hardware	ping (IP)	Hardware	tftp allow-override	Both
ip domain-name	Hardware	poweroff	Hardware	tftp allow-read-access	Both
ip name-server	Hardware	reload	Hardware	tftp allow-write-access	Both
ip route	Hardware	show bundles	Both	tftp verify-ip	Both
log level	Both	show clock	Both	traceroute (host)	Hardware
no debug	Both	show commands	Both	traceroute (IP)	Hardware
no debug dpe cache	Both	show cpu	Both	upgrade	Hardware
no debug dpe connection	Both	show device-config	Both	uptime	Both
no debug dpe dpe-server	Both	show disk	Both

Command Line Interface Organization

The BACC CLI is organized into the following functional groups and are further organized into these chapters:

Table Of Contents