If you are installing a distributed server configuration, with separate Application server and Device servers, you must first install Network Configuration Manager on the Application server, and then install it on the Device servers.
Before installing Device servers, ensure the Application or Combination servers have the same date and time as the candidate Device server. If not, the Device server will not be able to register with the Application or Combination servers, and the installation will fail.
To install a Device server using the console-based installer, follow these steps:
| Step |
Action |
|---|---|
| 1 |
Log into the server as the root user. |
| 2 |
Type bash install.sh –i console to run the installer in the console-based installer mode, and press Enter. The command prompt screen appears:
The installer begins to load. The install.sh script checks to ensure that all the prerequisites for the Network Configuration Manager are installed. The script automatically installs any missing prerequisites if the prerequisites are located in the Utils directory. The Core Setup Installer begins to load. |
| Core Setup Installer Procedures |
|
| 3 |
The introduction to the installer appears. Press Enter to continue. |
| 4 |
The License Agreement appears. Read the license agreement. Press Enter, and continue to press Enter to move through each page of the license agreement until you reach the final page. |
| 5 |
On the final page of the license agreement, type Y, and press Enter to accept the terms of the license agreement. |
| 6 |
The installer prompts you to select a server configuration. Enter 3, and press Enter to select Device server as your configuration type. |
| 7 |
The installer prompts you to choose an install folder. Press Enter to accept the default, or enter a location for the install folder. This is the location where Network Configuration Manager will be installed. |
| 8 |
Note:
This step only appears if the httpd.conf directory is not in the default location. The installer prompts you for the directory where httpd.conf is located. Press Enter to accept the default, or type the location of the httpd.conf file. This is where the Apache configuration file httpd.conf is located. |
| 9 |
Note:
This step only appears if the Java directory is not in the default location. The installer prompts you for the directory where Java is located. Press Enter to accept the default, or type the location of the Java directory. This is the location where the Java application is installed. |
| 10 |
Note:
This step only appears if the Tomcat directory is not in the default location. The installer prompts you for the directory where Tomcat is located. Press Enter to accept the default, or type the location of the Tomcat directory. This is the location where the Tomcat application is installed. |
| 11 |
The installer prompts you for the Application server IP. Enter an IP Address for the Application server, and press Enter. If you are installing Device server with a Cluster installation, then enter an IP Address for the active Network Configuration Manager Application server cluster, and press Enter. The Device servers will be set to the appropriate node when the clustered Application server becomes active. Do not type the virtual IP address of the cluster. |
| 12 |
The installer prompts you for the Device server alias. Press Enter to accept the default, or enter an Alias for the Combination server. This alias appears in the System Administration portion of Network Configuration Manager. This alias must not contain spaces or special characters. |
| 13 |
The installer prompts you to import root CA certificates. If you have any root CA certificates to import, provide the path for certificate root CA certificate file and then press Enter. |
| 14 |
The installer prompts for Certificate file location. Provide the path for the certificate file bundle.p12 and press Enter. |
| 15 |
The installer prompts for a password for Certificate. Type the same password that you entered while installing Application server and press Enter. |
| 16 |
Note:
You must perform this step irrespective of the mode of security you selected during the installation. The installer prompts for lockbox file location. Provide the path to the lockbox file lockb.clb that was copied earlier and press Enter. |
| 17 |
The installer prompts for a database password. Type the same password that you entered while installing Application or Database server and press Enter. |
| 18 |
The Summary window displays the product information (before installing), as well as the required disk space. Press Enter to start the installation. This portion of the installation may take several minutes. When complete, the Device Driver Installer begins to load. |
| Device Driver Installer Procedures |
|
| 19 |
While the Device Driver installer is running, a progress bar displays the install status. This portion of the installation may take several minutes. The installer displays the installation complete message.
Note:
During installation of the device drivers, the files in the custompackage directory that matches the files in the device drivers directory are listed. These files will override similar files in the device drivers directories. For example, if you have modified the file stdfuncs.inc for CiscoIOSRouter, it would be placed in the custom package directory and will override the same file in the /opt/smarts-ncm/package/cisco/ios directory. |
| 20 |
If you had chosen Standard Security mode during AS installation, copy lockb.ekey from [product directory]\data in the AS to [product directory]\data in DS. Change ownership of the file to ncm:voyence. |
Next step, go to “Post-Installation procedures” on page 119.
