Cisco DCNM Installation and Licensing Guide, Release 5.x
Installing Cisco DCNM-LAN Servers
Downloads: This chapterpdf (PDF - 183.0KB) The complete bookPDF (PDF - 3.69MB) | Feedback

Installing Cisco DCNM-LAN Servers

Table Of Contents

Installing Cisco DCNM-LAN Servers

Information About Cisco DCNM-LAN Server Installation

Primary Server Installation

Secondary Server Installation

Installing a Primary Cisco DCNM-LAN Server

Installing a Secondary Cisco DCNM-LAN Server

Installing with the CLI

Installing with Install Manager

Feature History for Installing Cisco DCNM-LAN Servers


Installing Cisco DCNM-LAN Servers


This chapter describes how to install Cisco Data Center Network Manager for LAN (DCNM-LAN) server software on a server system where no previous Cisco DCNM-LAN server installation is present.

This chapter includes the following sections:

Information About Cisco DCNM-LAN Server Installation

Installing a Primary Cisco DCNM-LAN Server

Installing a Secondary Cisco DCNM-LAN Server

Feature History for Installing Cisco DCNM-LAN Servers


Note The Cisco DCNM installer is the installer for both DCNM-SAN and DCNM-LAN. The installer provides support for the initial installation of both DCNM-SAN and DCNM-LAN on a server.


Information About Cisco DCNM-LAN Server Installation

This section includes the following topics:

Primary Server Installation

Secondary Server Installation

Primary Server Installation

You perform a primary server installation when you are installing the Cisco DCNM-LAN server software for either of the following two purposes:

You are deploying a single-server Cisco DCNM-LAN environment.

You are installing the first Cisco DCNM-LAN server in a clustered-server environment.

A primary server installation uses the Cisco DCNM installer wizard to collect information about how the Cisco DCNM-LAN server should be configured. After you have provided the installer the information that it needs, it installs the server software.

A primary server installation also creates the following files in the INSTALL_DIR/dcm/dcnm/config directory:

installer.properties—For use during the installation of each secondary server in the server cluster that the primary server belongs to.

re-installer.properties—For use during the reinstallation of any secondary server in the server cluster that the primary server belongs to.

licenses-installer.properties—For use during the Cisco DCNM-LAN license installation with any secondary server in the server cluster that the primary server belongs to.

On a Microsoft Windows server system, the default INSTALL_DIR value is C:\Program Files\Cisco Systems. On a RHEL server system, the default INSTALL_DIR value is /usr/local/cisco.

Secondary Server Installation

You perform a secondary server installation when you are installing additional Cisco DCNM-LAN servers in a clustered-server environment. This type of installation can only be performed after you install the primary server in the cluster.

A secondary server installation is a silent installation. After you run the installer from a command prompt, the installer does not prompt you for information. Instead, a secondary server installation uses the information from the installer.properties file that was created when you installed the primary server in the cluster that the secondary server belongs to.

Using the installer.properties file from the primary server ensures that each secondary server is configured identically, as required by Cisco DCNM-LAN clustered-server deployments. For more information, see the "Clustered-Server Configuration Requirements" section.

Installing a Primary Cisco DCNM-LAN Server

This section describes how to install the Cisco DCNM-LAN server software on a primary server system of a clustered-server environment or as the only server in a single-server environment.

BEFORE YOU BEGIN


NoteFor a single-server deployment, you must have performed Step 1 through Step 3 in the "Deploying a Single-Server Cisco DCNM-LAN Environment" section.

For a clustered-server deployment, you must have performed Step 1 through Step 5 in the "Deploying a Clustered-Server Cisco DCNM-LAN Environment" section.


If you want the Cisco DCNM-LAN server to use a previously installed database, ensure that the database is running. If the database is remote to the primary server system, ensure that the database is reachable from the primary server system.

Determine the full path to the archive directory that you want Cisco DCNM-LAN to use. If you are deploying a clustered-server Cisco DCNM-LAN environment, determine the full path from the primary server to the directory that you prepared for use by all servers in the cluster. The path to the archive directory does not need to be identical on each server; however, all servers in the cluster must use the same archive directory.

Disable antivirus and instruction detection software on the server system. In general, disable any security software or feature that might interfere with the installation of the Cisco DCNM-LAN server software. After you complete the installation, reenable the software or features.

DETAILED STEPS


Step 1 Log into the server with a user account that has the required privileges, as follows:

For Microsoft Windows, the user account must be a member of the local administrators group.

For RHEL, the user account must be root.

If you are installing Cisco DCNM-LAN on Microsoft Windows and using Remote Desktop Connection (RDC) to access the Cisco DCNM-LAN server system, start RDC from a command prompt and use the /console option, as follows:

C:\>mstsc /console /v:server
 
   

where server is the DNS name or IP address of the Cisco DCNM-LAN server system.

Step 2 Go to the directory where you downloaded the Cisco DCNM-LAN server software and run one of the following files:

For Microsoft Windows, run the dcnm-k9.release.exe file.

For RHEL, use the following sh command:

sh dcnm-k9.release.bin

Note For Microsoft Windows and RHEL, the console command option is not supported.



Note Using the Cisco DCNM-LAN installer in GUI mode requires that you must login to the remote server using VNC or XWindows. Using telnet or SSH to install Cisco DCNM-LAN in GUI mode is not possible.


After the installer prepares the installation, the Introduction step appears in the Cisco DCNM installer window.

Step 3 Click Next when the Introduction step appears in the Cisco DCNM installer window after the installer prepares the installation.

Step 4 Click Next when the Please Read Before Continuing information appears in the Cisco DCNM installer window.

Step 5 Enter the following when the Choose Install Folder step appears in the Cisco DCNM installer window:

a. Check the DCNM-LAN checkbox.

b. (Optional) If you want to change the default installation folder, type or choose the desired installation folder.

c. Click Next.

The Database Options step appears in the Cisco DCNM installer window. You can use an existing PostgreSQL installation or an existing Oracle installation. If PostgreSQL is not installed on the server system, you can use the Cisco DCNM installer to add a PostgreSQL installation.


Note If the Cisco DCNM installer detects an installation of Cisco DCNM-SAN Release 4.2(1) and later releases on the server system, the only database option that is available is the database that DCNM-SAN is configured to use.


Step 6 If you want to install PostgreSQL, do the following:

a. Next to RDBMS, click Install PostgreSQL.

If your server system runs RHEL, the System User dialog box appears.

b. (RHEL only) In the System User dialog box, enter the username for the user account that should be used to run the PostgreSQL software. This user account should not have administrator or root privileges.

c. In the DB Admin User field, enter the username of a database administrator account. The installer creates the administrator account that you specify.

d. In the DB Admin Password field, enter the password for the database administrator username that you specified.

e. In the DCNM DB User field, enter the username that Cisco DCNM-LAN should use to access the database. The default username is dcnmuser. The installer will create the user account that you specify.

f. In the DCNM DB Password field, enter the password for the database user account that you specified.

g. In the Confirm DCNM DB Password field, reenter the password for the database user account that you specified.

h. (Optional) If you want to change the default PostgreSQL database installation folder, in the Install Location field, enter or choose the desired installation folder.

Step 7 If you want to use an existing relational database management system (RDBMS) installation, do the following:

a. Next to RDBMS, click one of the following:

Use existing PostgreSQL 8.1/8.2/8.3

Use existing Oracle 10g/11g

If the Cisco DCNM installer detected an existing RDBMS installation, the DB URL field shows the URL to the database.


Note If the Cisco DCNM installer detects an installation of Cisco DCNM-SAN Release 4.2(1) and later releases on the server system, the DB URL field shows the URL of the DCNM-SAN database and cannot be configured.


b. If the DB URL field does not have the correct URL to the database, enter the correct URL.


Note The database is not automatically created. You need to manually create the database. A valid database URL is required to create a database schema and connect to it.


c. In the DB Admin User field, enter the username of a database user account that has permissions to create the Cisco DCNM-LAN database schema and Cisco DCNM-LAN database user account.

d. In the DB Admin Password field, enter the password for the database administrator username that you specified.

e. In the DCNM DB User field, enter the username that Cisco DCNM-LAN should use to access the database.

The installer uses the Cisco DCNM-LAN admin user that you specified to create the Cisco DCNM-LAN database user account.

f. In the DCNM DB Password field, enter the password for the database user account that you specified.

g. In the Confirm DCNM DB Password field, reenter the password for the database user account that you specified.

Step 8 Click Next.

Step 9 If the Choose Database (PostgreSQL/Oracle) Root Folder step appears in the Cisco DCNM installer window, do the following:

a. Enter or choose the folder that contains the BIN directory for the existing RDBMS that you specified. The installer lists the default installation paths for the supported databases.

b. Click Next.

The Configuration Options step appears in the Cisco DCNM installer window.

Step 10 From the Server IP Address list, choose the IP address that you want to use for the Cisco DCNM-LAN server. The list shows only the IP addresses currently assigned to network interfaces on the server system.


Note The IP address of the server system should be statically assigned. The Cisco DCNM-LAN server binds to an IP address that you specify during installation. If the IP address of the Cisco DCNM-LAN server changes, Cisco DCNM-LAN clients are unable to connect to the Cisco DCNM-LAN server and you must reinstall the Cisco DCNM-LAN server so that you can reconfigure the IP address.


Step 11 If you want to change the port that the Cisco DCNM-LAN web server listens to, enter the new port number in the Web Server Port field. By default, the Cisco DCNM-LAN web server listens to TCP port 8080.


Note If you change the web server port number, it affects the URL that Cisco DCNM-LAN users use to download the Cisco DCNM-LAN client.


Step 12 If you want to change the port that the Cisco DCNM-LAN server accepts Cisco DCNM-LAN client connections on, enter the new port number in the Naming Service Port field in Advanced Settings. By default, the Cisco DCNM-LAN server accepts connections from Cisco DCNM-LAN clients on TCP port 1099.


Note If you change the Cisco DCNM-LAN server port number, it affects the port that Cisco DCNM-LAN users specify when they log into the Cisco DCNM-LAN client.


Step 13 (Optional) For the remaining service ports listed on the Configuration Options step, if you want to specify a different port number, follow these steps in Advanced Settings:

a. For each service port number that you want to change, enter the new port number in the field.

b. Click Resolve Port Conflicts.

If the Cisco DCNM installer detects that a port that you specified is already in use, it automatically assigns an unused port number to the service.

c. Click OK to save the Advanced Settings.

Step 14 Click Next to save the Configuration Options and the IP Multicast Addresses Configuration step appears in the Cisco DCNM installer window.

Step 15 (Optional) If you are installing the primary server for a Cisco DCNM-LAN server cluster, follow these steps:

a. In the Partition Name field, enter a unique name for a Cisco DCNM-LAN server cluster. The default partition name is the database host instance ID. The name can contain letters and numbers only.

b. (Optional) As needed, change the multicast IP addresses. You may need to change the multicast IP addresses if the addresses provided by the installer are already in use in the routing environment of the Cisco DCNM-LAN server cluster.

c. (Optional) As needed, change the multicast ports. You may need to change the multicast ports if the port numbers provided by the installer are already in use on the server system that you are installing Cisco DCNM-LAN on.

Step 16 Click Next.

The Choose Archive Folder step appears in the Cisco DCNM installer window.

Step 17 Do one of the following:

If you are deploying a clustered-server Cisco DCNM-LAN environment, enter or choose the archive folder that you prepared for use by all the servers in the cluster.

If you are deploying a single-server Cisco DCNM-LAN environment, you can accept the default archive folder or choose the desired archive folder.

Step 18 Click Next.

The Local User Credentials step appears in the Cisco DCNM installer window.

Step 19 In the Local Admin Username field, enter a name for a Cisco DCNM-LAN server user. The installer creates the Cisco DCNM-LAN server user and assign the Administrator role to it.

Step 20 In the Password field, enter a password for the user, and then in the Confirm Password field, reenter the password.


Note We recommend that you use a strong password. Common guidelines for strong passwords include a minimum password length of eight characters and at least one letter, one number, and one symbol. For example, the password Re1Ax@h0m3 has ten characters and contains uppercase and lowercase letters in addition to one symbol and three numbers.


Step 21 Click Next.

The Authentication Settings step appears in the Cisco DCNM installer window.

Choose the authentication method that the Cisco DCNM-LAN server should use to authenticate users who log into the Cisco DCNM-LAN client. You can choose one of the following:

Local—Cisco DCNM-LAN client users are authenticated by the Cisco DCNM-LAN server user accounts only.

RADIUS—Cisco DCNM-LAN client users are authenticated by a RADIUS server.

TACACS+—Cisco DCNM-LAN client users are authenticated by a TACACS+ server.

For RADIUS or TACACS+, you can specify up to three servers.

Step 22 If you chose RADIUS or TACACS+, for each server that you want to specify, do the following:

a. In the server address field, enter the IPv4 address of the server in dotted-decimal format.

b. In the secret key field, type the shared secret of the server.

c. (Optional) If you want to ensure that Cisco DCNM-LAN can communicate with the server, click Verify.

Step 23 Click Next.

If you are using Microsoft Windows, the installer asks you to specify a shortcut to the application. If you are using RHEL, the installer asks you to specify a link folder.

Step 24 Choose the shortcut or link options that you want.

Step 25 (Optional) If you want the installer to create the shortcuts for all users who can log into the server system, check the Create Icons for All Users check box.

Step 26 Click Next.

The Pre-Installation Summary step appears in the Cisco DCNM installer window.

Step 27 Carefully review the summary of your choices. If you need to change anything, click Previous until the Cisco DCNM installer window displays the step that you need to change, and then return to the applicable preceding step.

Step 28 Click Next when you are ready to install the Cisco DCNM-LAN server software.

The installer installs the Cisco DCNM-LAN server software.

The Installing DCNM installer window appears.

Step 29 Choose whether you want to start the Cisco DCNM-LAN server now. If you start the Cisco DCNM-LAN server now, a splash screen appears while the server starts.

The Install Complete step appears in the Cisco DCNM installer window. The Cisco DCNM instance ID number is displayed.

Step 30 (Optional) If you plan to order licenses for Cisco DCNM-LAN, record the Cisco DCNM instance ID number. The licensing process requires that you enter that number.


Note You can begin using Cisco DCNM-LAN without a license but some features are not available unless you purchase and install a license and apply the license to managed devices that you want to use licensed features with.


Step 31 Click Done.

If you chose in Step 29 to start the Cisco DCNM-LAN server after installation, a splash screen appears while the server starts.

Step 32 (Optional) If you need to start the Cisco DCNM-LAN server, see the Cisco DCNM Fundamentals Guide, Release 5.x.

Step 33 (Optional) If you want to install a Cisco DCNM-LAN license, see Chapter 10 "Licensing a Cisco DCNM-LAN Deployment."


Installing a Secondary Cisco DCNM-LAN Server

Depending on the operating system of the secondary server, you can install the Cisco DCNM-LAN server using the CLI or the DCNM Install Manager tool. You can use the CLI or the DCNM Install Manager tool for a secondary server that runs RHEL. For a secondary server that runs Microsoft Windows, you install the Cisco DCNM-LAN server with the CLI.

This section includes the following topics:

Installing with the CLI

Installing with Install Manager

Installing with the CLI

This procedure describes how to install the Cisco DCNM-LAN server software on a secondary server system of a clustered-server environment. Secondary server installations use a silent installation method, which requires the use of a command line interface—for Microsoft Windows, a command prompt window, and for RHEL, a shell window.

The Cisco DCNM installer creates the DCNM_InstallLog.log file in the home directory of the user account that you use to install the secondary server. You can determine the success of the secondary server installation by monitoring the DCNM_InstallLog.log file.

BEFORE YOU BEGIN


Note You must have performed Step 1 through Step 8 in the "Deploying a Clustered-Server Cisco DCNM-LAN Environment" section.


The database that the primary Cisco DCNM-LAN server is configured to use must be running when you install a secondary server.

Determine the IP address of the secondary server.

Determine the full path from the secondary server to the archive directory that you have prepared for use by all servers in the cluster. The path to the archive directory does not need to be identical on each server; however, all servers in the cluster must use the same archive directory.


Note Disable antivirus and instruction detection software on the server system. In general, disable any security software or feature that might interfere with the installation of the Cisco DCNM-LAN server software. After you have completed the installation, reenable the software or features.


DETAILED STEPS


Step 1 From the primary server system, get a copy of the installer.properties file from the following location:

INSTALL_DIR/dcm/dcnm/config

On a Microsoft Windows server system, the default INSTALL_DIR value is C:\Program Files\Cisco Systems. On a RHEL server system, the default INSTALL_DIR value is /usr/local/cisco.

Step 2 Log into the secondary server with a user account that has the required privileges, as follows:

For Microsoft Windows, the user account must be a member of the local administrators group.

For RHEL, the user account must be root.

If you are installing Cisco DCNM-LAN on Microsoft Windows and using Remote Desktop Connection (RDC) to access the Cisco DCNM-LAN server system, start RDC from a command prompt and use the /console option, as follows:

C:\>mstsc /console /v:server
 
   

where server is the DNS name or IP address of the Cisco DCNM-LAN server system.

Step 3 Choose a directory and copy the following files to that directory:

The installer.properties file that you copied from the primary Cisco DCNM-LAN server system.

The Cisco DCNM-LAN server software that you downloaded.

Step 4 At a command prompt, change directories as needed to ensure that the working directory is the directory that contains the installer.properties file and the Cisco DCNM-LAN server software. On Microsoft Windows, use the chdir command without arguments to display the working directory. On RHEL, use the pwd command.

Step 5 Run the applicable command as follows:

For Microsoft Windows:
dcnm-k9.release.exe -i silent -f installer.properties -DDCNM_IP_ADDRESS=server_ip_address -DDATA_PATH=configuration_archive_directory [-DUSER_INSTALL_DIR=installation_directory]

For RHEL:
sh dcnm-k9.release.bin -i silent -f installer.properties -DDCNM_IP_ADDRESS=server_ip_address -DDATA_PATH=configuration_archive_directory [-DUSER_INSTALL_DIR=installation_directory]

For example, to install a secondary Cisco DCNM-LAN Release 5.0(2) server in the default installation directory on a Microsoft Windows server system that is assigned the IPv4 address 10.72.139.14 and that has the directory W:\DCNMdata prepared for the Cisco DCNM-LAN configuration archive, the installation command is as follows:

dcnm-k9.5.0.2.exe -i silent -f installer.properties -DDCNM_IP_ADDRESS=10.72.189.14 
-DDATA_PATH=W:\DCNMdata
 
   

Table 9-1 describes the command syntax.

Table 9-1 Secondary Server Installation Command Syntax 

Option
Description

-i silent

Specifies that the installation is silent.

-f installer.properties

Specifies the installer.properties file.

-DDCNM_IP_ADDRESS=server_ip_address

Specifies the IPv4 address of the secondary server on which you are installing the Cisco DCNM-LAN server software.

-DDATA_PATH=
configuration_archive_directory

Specifies the full path to the archive directory that you prepared for use by all the servers in the cluster.

-DUSER_INSTALL_DIR=
installation_directory

(Optional) Specifies the full path to a custom installation directory. If you do not include this option, the Cisco DCNM-LAN server is installed at the applicable default location:

For Microsoft Windows: C:\Program Files\Cisco Systems

For RHEL: /usr/local/cisco


Step 6 Monitor the DCNM_InstallLog.log file to determine the status of the installation. The Cisco DCNM installer writes the log file to the home directory of the current user account.

Step 7 (Optional) If you want to install a Cisco DCNM-LAN license, see Chapter 10 "Licensing a Cisco DCNM-LAN Deployment."


Installing with Install Manager

Cisco DCNM Install Manager is a GUI tool for servers running Linux. It is designed to assist in performing silent mode installation operations on secondary servers (remote nodes).


Note Cisco DCNM Install Manager does not support Windows servers.



Note Disable antivirus and instruction detection software on the server system. In general, disable any security software or feature that might interfere with the installation of the Cisco DCNM-LAN server software. After you have completed the installation, reenable the software or features.


DETAILED STEPS


Step 1 To access Install Manager, navigate to the dcnm-install-manager.sh file that is located in the bin folder where the DCNM-LAN server was installed.

The default bin folder location for servers running Linux is /usr/local/Cisco/dcm/dcnm/bin.

Step 2 Double click the dcnm-install-manager.sh file to launch Install Manager.

Step 3 In the DCNM Installer Folder drop-down list, choose the path that contains the binary executable file for DCNM-LAN server installation.

Step 4 Click the New icon in the toolbar near the top of the Install Manager GUI for every secondary server.

A new row in the list of Server Nodes is created every time that the New icon is clicked.


Note Click the Delete icon in the toolbar to delete a selected row in the list of Server Nodes. This action does not delete a secondary server from the clustered-server environment.


Step 5 For each secondary server represented by a row in the list of Server Nodes, enter the following:

Server name or IP address in the Server Name/IP Address field.

Protocol used for connectivity in the Protocol field.

The protocol is either Telnet or SSH.

User credentials (user ID and password) used for connecting to the secondary server in the User Credentials field.

The user credentials are used for SSH connectivity to the server. Telnet connectivity to the server does not require user credentials.

Alternatively, default user credentials can be set by entering the credentials in the Default Credentials section of the GUI. The default credentials are used when the User Credential field is blank.

(Optional) Comments that might be useful to identify the secondary server in the Comments field.

The Last Action Status column in the list of Server Nodes includes the success or failure status of the last performed action. Clicking the + icon for the Last Action Status expands the display to show the entire log of actions performed on the server.

Step 6 In the list of Server Nodes, choose the secondary servers to perform the installation.

Step 7 In the toolbar, click the Verify icon to verify the connectivity to the selected secondary servers.

Correct any connectivity issues before continuing the installation.

Step 8 (Optional) In the DCNM Install Location field, enter the path on the secondary server for the installation of the DCNM-LAN server.

If the DCNM Install Location field is blank, the Install Manager uses the default path, /usr/local/Cisco/dcm, for the installation of the DCNM-LAN server.

Step 9 In the Data Path Location field, enter the path for the archival configuration data for the secondary servers.

The data path is the same for all the secondary servers and matches the data path of the primary server.

Step 10 In the toolbar, click the Install icon to begin the installation on the selected secondary servers.

Before starting the installation, the Install Manager does the following:

Checks the connectivity to the server.

Performs upgrade and reinstallation depending on the version already installed.

Step 11 Monitor the Last Action Status column to determine the status of the installation.

In addition, you may also review the DCNM_Installer_Manager.log file. This file, located at /root/.dcnm, contains the log for all the operations of the Install Manager.

If the installation operation fails on a secondary server, the installation log of the secondary server is automatically copied to /usr/local/Cisco/dcm/FailureLog_<SECONDARY_SERVER_IP_ADDRESS>.log on the primary server, where <SECONDARY_SERVER_IP_ADDRESS> is the IP address of the secondary server.

Step 12 (Optional) To install a Cisco DCNM-LAN license, see Chapter 10 "Licensing a Cisco DCNM-LAN Deployment."



Note The Install Manager is a standalone application. The settings specified are not saved and are not persistent. The settings are lost when the Install Manager GUI is closed.


Feature History for Installing Cisco DCNM-LAN Servers

Table 9-2 lists the release history for this feature.

Table 9-2 Feature History for Installing Cisco DCNM-LAN Servers 

Feature Name
Releases
Feature Information

Multicast IP address configuration for clustered-server environments

5.0(2)

This feature was introduced.

Secondary server installation

5.0(2)

This feature was introduced.

Install Manager

5.1

This feature was introduced.