Cisco Configuration Engine Solaris Installation and Configuration Guide, 2.0

Installing the Product Software

---

Cisco Configuration Engine, 2.0 is a Cisco product designed to configure large numbers of customer-premise network devices in a plug-and-play manner.

System Requirements

•Sunfire V210 1 (2 CPU for 10,000 device connections).

•Solaris 2.8.

•1 GB RAM (2 GB for 10,000 device connections).

•ï40 GB disk space (70 GB for 10,000 device connections).

Cisco IOS Dependences

Table 1-1 lists Cisco IOS versions with corresponding versions of Cisco Configuration Engine, 2.0 including feature limitations associated with each version.

Table 1-1 Cisco Configuration Engine, 2.0 and Cisco IOS Dependencies

Cisco IOS	Configuration Engine	Limitations
12.3	1.3.2 or later
12.2(11)T	1.2 or later
12.2(2)T	1.2 or later with no authentication.	Applications are unable to use exec commands or point-to-point messaging.

Installing the Software

The Cisco Configuration Engine, 2.0 software is contained on a CD-ROM that is in the accessory kit.

---

Step 1 Install the CD-ROM into the disk drive on the host system.

Step 2 Copy the tar file into a new folder where disk space is large enough:

tar xvf <tarfilename>

---

Note The tar file must be the only file in this new folder.

---

Step 3 Enter the following commands:

./ce_install.sh

Step 4 After installing the software, log out, then log back in again, or create a new window.

Step 5 Enter the following commands:

cd $CISCO_CE_INSTALL_ROOT/CSCOcnsie/bin/

./setup

Step 6 Go to "System Configuration" for a description of how to configure your system.

---

Script Options

The Cisco Configuration Engine, 2.0 image is provided to the user in tar file format. Users should untar the image in a directory. Then, the user should go to that directory and run the ce_install.sh command.

In order to support different types of installations and setup, the scripts uses options to differentiate different requirements.

Because Cisco Configuration Engine, 2.0 must share the web infrastructure-related software with bundled Cisco software. The default behavior of the script is defined in the installRule.<os>.xml file. This file is located in the same directory where the Cisco Configuration Engine, 2.0 tar file is untarred. The installRule.<os>.xml file contains information about:

•Which package for which version should be installed.

•Can a package be shared.

•The behavior of the installation if the package exists or not.

•The methods to install and un-install the package.

The result of the installation is logged under /var/log/CNSCE/install.log, lists what exactly is being installed into the system. For a successful install, it should be the same as the contents of installRule.<os>.xml.

The installError.xml file is generated if there is an error during installation. Other files such as those that contain all Cisco Configuration Engine, 2.0 related environmental variables are generated during installation stage including: global.sh, global.csh, global.pm, and installdata.properties.

Options for ce_install.sh

The installation script, ce_install.sh, has the following options:

---

Note No option indicates default behavior which is described above.

---

-batch: This option allows non-interactive installation. The installation script reads the default values from installRule.<os>.xml file and installs Cisco Configuration Engine, 2.0 based on these settings without query for user input.

-demo: Installs the package without checking system resources except for minimum disk space, which is 650MB.

-force: install/uninstall Cisco Configuration Engine, 2.0 without installation or un-installation status check.

Options for Setup Script

The setup script, setup, has the following options:

Default option is interactive mode, that prompts the user to provide inputs and store them in a data file. The default value is read from setupRule.xml under ${CISCO_CE_INSTALL_ROOT}/CSCOcnsie/bin/.

The result will put in log file: /var/log/CNSCE/appliance-setup.log.

-s: batch mode which reads all the information it requires for setup without user interaction from the data file: ${CISCO_CE_INSTALL_ROOT}/CSCOcnsie/bin/setupRule.xml.

The result is put in a log file: /var/log/CNSCE/appliance-setup.log.

Before running batch mode the first time, you must run the utility script:

$CISCO_CE_HOME/bin/passwdEncryption.pl

This creates encrypted passwords and loads them into setupRule.xml. The passwords in XML must be in encrypted text, not plain text.

Uninstall Script

The uninstall script, ce_uninstall.sh, is copied into /var/ciscoce/install directory. This script reads the installdata.xml file to do package uninstall:

1. Stop all running Cisco Configuration Engine, 2.0 processes.

2. Remove all database data from BDB.

3. Remove installed database software if it is BDB.

4. Remove all presence of the installed packages.

Synchronize Clocks

The clock (date and time) on your host and the clock on the PC you use to access the Cisco Configuration Engine, 2.0 user interface should be synchronized. This is particularly important when scheduling an update-image job for a future time (refer to the Cisco Configuration Engine Administrator Guide, 2.0).

For this operation, the client-side check to ensure you have entered a valid time value is done using the clock on the PC with the browser used to access the Cisco Configuration Engine, 2.0 user interface. Consequently, if your host clock is behind the PC clock, the user interface does not allow the job to be scheduled.

For example, if your host clock read 11:10 while the PC clock read 12:10, the user interface will not allow a job to be scheduled before 12:10. It will issue an error message: Please input a future time.