Table Of Contents
Reinstalling Cisco DCNM Servers
Information About Reinstalling a Cisco DCNM Server
Reasons for Reinstalling a Cisco DCNM Server
Primary Server Reinstallation
Secondary Server Reinstallation
Reinstalling a Primary Cisco DCNM Server
Reinstalling a Secondary Cisco DCNM Server
Reinstalling with the CLI
Reinstalling with Install Manager
Feature History for Reinstalling Cisco DCNM Servers
Reinstalling Cisco DCNM Servers
This chapter describes how to reinstall a Cisco Data Center Network Manager (DCNM) server on a server system where a previous installation of the identical Cisco DCNM release is present.
This chapter includes the following sections:
•
Information About Reinstalling a Cisco DCNM Server
•Reinstalling a Primary Cisco DCNM Server
•Reinstalling a Secondary Cisco DCNM Server
•Feature History for Reinstalling Cisco DCNM Servers
Information About Reinstalling a Cisco DCNM Server
This section includes the following topics:
•Reasons for Reinstalling a Cisco DCNM Server
•Primary Server Reinstallation
•Secondary Server Reinstallation
Reasons for Reinstalling a Cisco DCNM Server
You can reinstall the Cisco DCNM server and the download service for the Cisco DCNM client. When you reinstall the primary Cisco DCNM server, you must choose one of the following types of reinstallation:
•Custom—Reinstalls the components that you select, without allowing you to change anything that you specified when you previously installed the Cisco DCNM server. Choose this reinstallation type when you want to do any of the following:
–Reinstall the Cisco DCNM server without changing database or configuration options.
–Reinstall the Cisco DCNM client download service.
–Reinstall the Cisco DCNM license, either from the same folder that previously contained the Cisco DCNM license file or from a different folder.
•Full Reinstall—Reinstalls the Cisco DCNM server and the Cisco DCNM client download service. Choose this reinstallation type when you want to do any of the following:
–Perform password recovery for the local administrator account.
–Change Cisco DCNM server authentication settings.
–Create a PostgreSQL installation.
–Change the database URL, database username, or database password for the existing PostgreSQL installation.
–Change the Cisco DCNM server IP address.
Note If you are using RHEL and you change the Cisco DCNM server IP address, you must also manually change the IP address in the INSTALL_DIR/bin/stopDCNM.sh script.
–Change any of the configurable ports that the Cisco DCNM server uses. For more information about ports, see the "Server Ports" section on page 1-3.
Note If you change the web server port number, it affects the URL that Cisco DCNM users use to download the Cisco DCNM client.
Note If you change the naming service port, it affects the port that Cisco DCNM users specify when they log into the Cisco DCNM client.
Neither reinstallation type allows you to change the installation folder or archive folder.
Primary Server Reinstallation
Primary server reinstallation is for reinstalling the Cisco DCNM server software for either of the following two purposes:
•You need to reinstall Cisco DCNM in a single-server environment
•You need to reinstall the primary Cisco DCNM server in a clustered-server environment.
Note If you change the configuration of the primary server during reinstallation, you must reinstall Cisco DCNM on all secondary servers that are in the same cluster as the primary server.
A primary server reinstallation uses the Cisco DCNM installer wizard to collect information about how the Cisco DCNM server should be configured. After you have provided the installer the information that it needs, it reinstalls the server software.
A primary server reinstallation also updates the re-installer.properties file in the INSTALL_DIR/dcm/dcnm/config directory. This file is for use during the reinstallation of 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 Reinstallation
A secondary server reinstallation is for the reinstallation of secondary Cisco DCNM servers in a clustered-server environment. If you reinstall the primary server and change its configuration, you must reinstall all the secondary servers that are in the same cluster as the primary server.
A secondary server reinstallation 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 re-installer.properties file from the primary server ensures that each secondary server is configured identically, as required by Cisco DCNM clustered-server deployments. For more information, see the "Clustered-Server Configuration Requirements" section on page 1-6.
Reinstalling a Primary Cisco DCNM Server
You can reinstall the Cisco DCNM server and the download service for the Cisco DCNM client.
Note If you change the configuration of the primary server during reinstallation, you must reinstall Cisco DCNM on all secondary servers that are in the same cluster as the primary server.
BEFORE YOU BEGIN
Stop the Cisco DCNM server. The upgrade cannot proceed until you stop the Cisco DCNM server. For detailed steps, see the Cisco DCNM Fundamentals Configuration Guide, Release 5.x.
Note Disable antivirus and instruction detection software on the server system. In general, disable any security software or feature that may interfere with the installation of the Cisco DCNM server software. After you have completed 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 on Microsoft Windows and using Remote Desktop Connection (RDC) to access the Cisco DCNM 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 server system.
Step 2 If you have not already done so, stop the Cisco DCNM server.
Step 3 Go to the directory that contains the Cisco DCNM installer 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:
When the Cisco DCNM installer starts, a warning dialog box indicates that the existing installation of the Cisco DCNM server was found.
Step 4 Click OK.
The Introduction step appears.
Step 5 Click Next.
The Reinstall step appears in the Cisco DCNM installer window.
Step 6 Choose the type of reinstallation that you want to perform by doing one of the following:
•If you want to reinstall both the Cisco DCNM server and the Cisco DCNM client download service, click Full Reinstall.
•If you want to reinstall only the Cisco DCNM server or only the Cisco DCNM client download service, click Custom.
Step 7 If you chose Custom, follow these steps:
a. Click Next.
The Reinstall Cisco DCNM step appears in the Cisco DCNM installer window. Under Install Set, check boxes for the components that you can reinstall appear.
b. Check the check boxes for the components that you want to reinstall and click Next.
If you chose the License component, the Choose Cisco DCNM License Folder step appears in the Cisco DCNM installer window.
c. If the Choose Cisco DCNM License Folder step appears, type or choose the path to the folder that contains the Cisco DCNM license file, and then click Next.
The Pre-Installation Summary step appears in the Cisco DCNM installer window.
d. Skip to Step 29.
Step 8 If you chose Full Reinstall, click Next.
The Database Options step appears in the Cisco DCNM installer window. You can use the existing PostgreSQL installation or you can use the Cisco DCNM installer to add a PostgreSQL installation.
Step 9 Next to RDBMS, click the option for the existing database that you want to use.
If the Cisco DCNM installer detected the existing database installation, the DB URL field shows the URL to the database.
Note If the Cisco DCNM installer detects that the existing installation of Cisco DCNM shares a database system with an installation of Cisco Fabric Manager Release 4.2(1) and later releases, the DB URL field shows the URL of the Fabric Manager database and cannot be configured.
Step 10 If the DB URL field does not have the correct URL to the Cisco DCNM database, type the correct URL. If you previously used the Cisco DCNM installer to create a PostgreSQL installation, the URL is typically as follows:
jdbc:postgresql://localhost:5432/dcnmdb
where 5432 is the default PostgreSQL server port number and dcnmdb is the default database name that the Cisco DCNM installer creates.
If you previously used a Oracle 10g database installation, the URL is typically as follows:
jdbc:oracle:thin:@localhost:1521:XE
where 1521 is the default Oracle server port number.
If you previously used a Oracle 11g database installation, the URL is typically as follows:
jdbc:oracle:thin:@localhost:1521:ORCL
where 1521 is the default Oracle server port number.
Step 11 In the DB Admin User field, type the username of a database user account that has administrator permissions in the database.
Step 12 In the DB Admin Password field, type the password for the database administrator username that you specified.
Step 13 In the DCNM DB User field, type the username that Cisco DCNM should use to access the database.
Step 14 In the DCNM DB Password field, type the password for the database user account that you specified.
Step 15 In the Confirm DCNM DB Password field, retype the password for the database user account that you specified.
Step 16 Click Next.
The Configuration Options step appears in the Cisco DCNM installer window.
Step 17 From the Server IP Address list, choose the IP address that you want to use for the Cisco DCNM 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 server binds to the IP address that you specify. If the IP address of the server system changes after you install the Cisco DCNM server, Cisco DCNM clients are unable to connect to the Cisco DCNM server and you must stop and reinstall the Cisco DCNM server so that you can reconfigure the IP address.
Step 18 If you want to change the port that the Cisco DCNM web server listens to, enter the new port number in the Web Server Port box. By default, the Cisco DCNM web server listens to TCP port 8080.
Note If you change the web server port number, it affects the URL that Cisco DCNM users use to download the Cisco DCNM client.
Step 19 If you want to change the port that the Cisco DCNM server accepts Cisco DCNM client connections on, enter the new port number in the Naming Service Port box. By default, the Cisco DCNM server accepts connections from Cisco DCNM clients on TCP port 1099.
Note If you change the Cisco DCNM server port number, it affects the port that Cisco DCNM users specify when they log into the Cisco DCNM client.
Step 20 (Optional) For the remaining service ports listed on the Configuration Options step, if you want to specify a different port number, follow these steps:
a. For each service port number that you want to change, type 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.
Step 21 Click Next.
The IP Multicast Addresses Configuration step appears in the Cisco DCNM installer window.
Step 22 (Optional) If you are installing the primary server for a Cisco DCNM server cluster, follow these steps:
a. In the Partition Name field, type a unique name for a Cisco DCNM server cluster. The default partition name is the database host instance ID. The name can contain letters and numbers only.
b. 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 server cluster.
c. As needed, change the multicast listening ports. You may need to change the multicast listening ports if the port numbers provided by the installer are already in use on the server system that you are installing Cisco DCNM on.
Step 23 Click Next.
The Local User Credentials step appears in the Cisco DCNM installer window.
Step 24 In the Local Admin Username field, type a name for a Cisco DCNM server user. The installer will create the Cisco DCNM server user and assign the Administrator role to it.
Step 25 In the Password field, type a password for the user, and then in the Confirm Password field, type the password again.
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 26 Click Next.
The Authentication Settings step appears in the Cisco DCNM installer window.
Choose the authentication method that the Cisco DCNM server should use to authenticate users who log into the Cisco DCNM client. You can choose one of the following:
•Local—Cisco DCNM client users will be authenticated by the Cisco DCNM server user accounts only.
•RADIUS—Cisco DCNM client users will be authenticated by a RADIUS server.
•TACACS+—Cisco DCNM client users will be authenticated by a TACACS+ server.
For RADIUS or TACACS+, you can specify up to three servers.
Step 27 If you chose RADIUS or TACACS+, for each server that you want to specify, do the following:
a. In the server address field, type 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 can communicate with the server, click Verify.
Step 28 Click Next.
Step 29 Carefully review the summary of your choices. If you need to change anything, click Previous and return to the applicable preceding step.
Step 30 When you are ready to install the Cisco DCNM server software, click Next.
The installer installs the Cisco DCNM server software.
The Start Cisco DCNM Server dialog box appears.
Step 31 Choose whether you want to start the Cisco DCNM server now. If you start the Cisco DCNM server now, a splash screen appears while the server starts.
The Install Complete step appears in the Cisco DCNM installer window, which also shows a Cisco DCNM instance ID number.
Step 32 (Optional) If you plan to order licenses for Cisco DCNM, record the Cisco DCNM instance ID number. The licensing process requires that you enter that number.
Note You can begin using Cisco DCNM without a licence 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 33 Click Done.
If you chose in Step 31 to start the Cisco DCNM server after installation, a splash screen appears while the server starts.
Step 34 (Optional) If you need to start the Cisco DCNM server, see the Cisco DCNM Fundamentals Configuration Guide, Release 5.x.
Step 35 (RHEL only) If you are using RHEL and you changed the Cisco DCNM server IP address during the reinstallation, open the INSTALL_DIR/bin/stopDCNM.sh script in a text editor and change the IP address to the new Cisco DCNM server IP address.
Reinstalling a Secondary Cisco DCNM Server
Depending on the operating system of the secondary server, you can reinstall the Cisco DCNM 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 running RHEL. For a secondary server running Microsoft Windows, you reinstall the Cisco DCNM server with the CLI.
Reinstalling with the CLI
This procedure describes how to reinstall the Cisco DCNM 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
Stop Cisco DCNM on the secondary server. The upgrade cannot proceed until you stop the Cisco DCNM server software. For detailed steps, see the Cisco DCNM Fundamentals Configuration Guide, Release 5.x.
You must have installed the primary Cisco DCNM server.
Determine the IP address of the secondary server.
Ensure that the secondary server system satisfies the prerequisites. For more information, see the "Prerequisites for Installing a Cisco DCNM Server" section on page 1-4.
Note Disable antivirus and instruction detection software on the server system. In general, disable any security software or feature that may interfere with the reinstallation of the Cisco DCNM 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 re-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 on Microsoft Windows and using Remote Desktop Connection (RDC) to access the Cisco DCNM 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 server system.
Step 3 Choose a directory and copy the following files to that directory:
•The re-installer.properties file that you copied from the primary Cisco DCNM server system.
•The Cisco DCNM 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 re-installer.properties file and the Cisco DCNM 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:
•For Microsoft Windows:
dcnm-k9.release.exe -i silent -f re-installer.properties -DDCNM_IP_ADDRESS=server_ip_address
•For RHEL:
sh dcnm-k9.release.bin -i silent -f re-installer.properties -DDCNM_IP_ADDRESS=server_ip_address
For example, to reinstall a secondary Cisco DCNM Release 5.0(2) server on a Microsoft Windows server system that is assigned the IPv4 address 10.72.139.14, the reinstallation command is as follows:
dcnm-k9.5.0.2.exe -i silent -f re-installer.properties -DDCNM_IP_ADDRESS=10.72.189.14
Table 6-1 describes the command syntax.
Table 6-1 Secondary Server Installation Command Syntax
|
Option
|
Description
|
-i silent |
Specifies that the installation is silent. |
-f re-installer.properties |
Specifies the re-installer.properties file. |
-DDCNM_IP_ADDRESS=server_ip_address |
Specifies the IPv4 address of the secondary server on which you are reinstalling the Cisco DCNM server software. |
Step 6 Monitor the DCNM_InstallLog.log file to determine the status of the reinstallation. 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 license, see Chapter 4, "Licensing a Cisco DCNM Deployment."
Reinstalling with Install Manager
DCNM Install Manager is a GUI tool for servers running Linux. It is designed to assist in performing silent mode operations on secondary servers (remote nodes).
Note 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 may interfere with the installation of the Cisco DCNM 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 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 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 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 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 may 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 may 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, select the secondary servers to perform the reinstall.
Step 7 Click the Verify icon in the toolbar 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 reinstall of the DCNM server.
If the DCNM Install Location field is blank, the Install Manager uses the default path, /usr/local/Cisco/dcm, for the reinstall of the DCNM 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 Click the Install icon in the toolbar to begin the reinstall on the selected secondary servers.
Before starting the reinstall, the Install Manager:
•Checks the connectivity to the server.
•Performs upgrade and re-installation depending on the version already installed.
Step 11 Monitor the Last Action Status column to determine the status of the reinstall.
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 reinstallation 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 license, see Chapter 4, "Licensing a Cisco DCNM 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 Reinstalling Cisco DCNM Servers
Table 6-2 lists the release history for this feature.
Table 6-2 Feature History for Reinstalling Cisco DCNM Servers
|
Feature Name
|
Releases
|
Feature Information
|
Support for a clustered-server environment |
5.0(2) |
This feature was introduced. |
Install Manager |
5.1 |
This feature was introduced. |
Feedback