Cisco DCNM Installation and Upgrade Guide for SAN Deployment, Release 11.5(1) - Installing the Cisco DCNM [Cisco Data Center Network Manager 11] (2024)

Close all instances of DCNM SAN client and Device Manager running on the server.

Click on Search icon.

A list of the latest release software for Cisco DCNM available for download is displayed.

The installer file is of the format dcnm-installer-x64.11.5.1.exe.

This file will be used during Silent Installation.

Double click on the dcnm.exe file.

InstallAnywhere progress bar appears to show the progress.

Choose a vendor from the OEM Vendor drop-down list.

• Cisco Systems, Inc─to install Cisco Data Center Network Manager.

• IBM─to install the IBM Data Center Network Manager.

The following message appears:

Please close the DCNM Installation wizard gracefully using "Done" optionon last installation step and wait for the installation wizard to close automatically. Do not restart the system or forcefully terminate the Installation wizard while it is still in progress." 

Click OK to continue.

Click Next.

Click Next.

Select the database that is based on your requirement.

• Install PostgreSQL—Installs the PostgreSQL database that is bundled along with the dcnm.exe.

• Existing PostgreSQL 9.4

• Existing Oracle 10g/11g/12c

• Existing Oracle 10g/11g/12c RAC

  In the Service Name field, enter the service name of the Oracle RAC server. Enter a maximum of three host IP addresses. Click OK. The DB URL is generated.

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

Cisco DCNM installation with existing PostgresSQL requires an existing schema with the same name as the DCNM username, which is owned by the same username. When there are no schemas existing with the DCNM username, or if you don’t have the ownership of the schema with the same dcnmuser name, the tables are created in the default schema, which is known as “public”.

In the DCNM DB User field, enter the username that the Cisco DCNM uses to access the database. In the DCNM DB Password field, enter the password for the database user account that you specified. If you select Add Server to an existing federation, modify the database URL by selecting the corresponding RDBMS option. Because all the servers in federation refer to the same database, you must provide the dcnmuser name and password of the primary server.

Click Next. Review the limitations with Oracle Database and click OK.

Click Next.

• 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 that are assigned to network interfaces on the server system.

• If you want to change the port that the Cisco DCNM-SAN web server listens to, enter the new port number in the SAN Web Server Port field. By default, the Cisco DCNM-SAN web server listens to TCP port 443.

  Note	During Cisco DCNM installation, use port numbers that are not commonly used. For example, 87 and 23 are reserved or restricted web ports.

Click Next.

Perform one of the following:

• Click Choose to select a path to store the DCNM LAN archive directory.

  Note	If you must choose a remote system, provide the UNC path. For example: //Server/Share/directorypath.

• Click Restore Default Folder to retain the default folder.

  Note	Ensure that this folder is accessible by all nodes in the Federation setup.

Click Next.

• In the Admin Username field, enter a name for a Cisco DCNM server user. The installer creates the Cisco DCNM server user and assigns the Administrator role to it.

• In the Password field, enter a password for the user, and in the Confirm Password field, reenter the password.

  Adhere to the following password requirements. If you don’t comply with the requirements, the DCNM application may not function properly:

  • It must be at least 8 characters long and contain at least one alphabet and one numeral.

  • It can contain a combination of alphabets, numerals, and special characters.

  • Do not use any of these special characters in the DCNM password for any deployment mode: <SPACE> & $ % ‘ “ ^ = < > ; :

Click Next.

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

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

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

You can configure LDAP authentication after installing DCNM.

Click Next.

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.

Click Next.

Click Previous to go to the previous tabs and modify the configuration.

Click Next.

The progress bar description shows the process during the installation.

Wait until the DCNM is deployed on the system.

The prompt will return after the silent install is complete.

Press Return key to launch the Web Interface of Cisco DCNM on Windows for LAN and SAN Management.

This makes the DCNM installed as a secondary appliance in a Federation setup. The Pre-installation Summary screen displays the Federation status and nodes in the Federation Settings area.

The following message appears:

Please close the DCNM Installation wizard gracefully using "Done" optionon last installation step and wait for the installation wizard to close automatically. Do not restart the system or forcefully terminate the Installation wizard while it is still in progress." 

Click OK to continue.

Cisco DCNM uses both strong and weak ciphers when connecting to switches. If user you wants to use only strong ciphers for network, select the checkbox. Ensure that the switches in your network support strong ciphers before you select checkbox, as DCNM will not be able to connect to switches which do not support strong ciphers.

The user name and password of the database are same for all the server installation forming the federation. Similarly, the user name and password of DCNM are same for all the server installation forming the federation.

#-----------------BASIC Properties---------------------DCNM_IP_ADDRESS=<ip_address_of_host_machine>USER_INSTALL_DIR=C:\\Program Files\\Cisco SystemsINSTALLATION_TYPE=NEW_INSTALL#INSTALLATION_TYPE=UPGRADESAN_FEDERATION=FALSE#SAN_FEDERATION=TRUE

If you are using PostgreSQL database, edit this block:

#------------------DATABASE Properties--------------------#User can configure these properties to use existing database or# install fresh Postgres as database for the DCNM. Existing database# can be postgres (remote or local), Oracle (remote or local)# or it can be Oracle RAC.#----------------------------------------------------USE_EXISTING_DB=FALSE#USE_EXISTING_DB=TRUEPG_DB_PATH=C:\\Program Files\\Cisco Systems\\dcm\\db#----------New Postgres---------------------------------DCNM_DB_URL=jdbc\:postgresql\://localhost\:5432/dcmdbDCNM_DB_NAME=dcmdbSELECTED_DATABASE=postgresqlDCNM_DB_USERNAME=dcnmuserDCNM_DB_USER_PASSWORD=dcnmuser

If you are using the Oracle database, edit this block:

#------------------DATABASE Properties--------------------#User can configure these properties to use existing database or# install fresh Postgres as database for the DCNM. Existing database# can be postgres (remote or local), Oracle (remote or local)# or it can be Oracle RAC.#----------------------------------------------------USE_EXISTING_DB=FALSE#USE_EXISTING_DB=TRUEORA_DB_PATH=C:\\oraclexe\\app\\oracle\\product\\10.2.0\\server

#-----------------User Configuration-----------------#DCNM User Configuration Properties#If you want to use special characters in DCNM_ADMIN#credentials,Please use escape character(\) before #the symbol [For eg. Password "an$6x12" must be specified as "an\$6x12" ].#----------------------------------------------------DECRYPT_PASSWORDS=FALSEDCNM_ADMIN_USER=adminDCNM_ADMIN_USER_PASSWORD=admin123#-----------------User Configuration-----------------

#----------------Secure Ciphers-------------------------------------#DCNM uses both strong and weak ciphers when connecting to switches#If user wants to use only strong ciphers for connection, please set#property to TRUE. Make sure your switches support strong ciphers before#setting the property as DCNM will not be able to connect to switches which#support only weak ciphers.#-----------------------------------------------------------------------SECURE_CIPHER=FALSE#SECURE_CIPHER=TRUE#-----------------------------------------------------------------------

#------------------------------IBM Raven Support----------------------#Set true if Vendor is IBM, by default false#---------------------------------------------------------------------IBM_INSTALL=FALSE /*Does not install IBM Data Center Network Manager*/#---------------------------------------------------------------------

You can check the status of installation in the Task Manager process.

Press Return key to launch the Web Interface of Cisco DCNM for SAN Management.

Close all instances of DCNM SAN client and Device Manager running on the server.

Click on Search icon.

A list of the latest release software for Cisco DCNM available for download is displayed.

The installer file is of the format dcnm-installer-x64.11.5.1.bin.

This file will be used during Silent Installation.

Run the dcnm.bin installer file.

InstallAnywhere progress bar appears showing the progress.

Choose a vendor from OEM Vendor drop-down list.

• Cisco Systems, Inc─to install Cisco Data Center Network Manager

• IBM─to install IBM Data Center Network Manager

The following message appears:

Please close the DCNM Installation wizard gracefully using "Done" optionon last installation step and wait for the installation wizard to close automatically. Do not restart the system or forcefully terminate the Installation wizard while it is still in progress." 

Click OK to continue.

Click Next.

In the Install Location field, click Choose, and provide the appropriate folder path. Click Restore Default Folder if DCNM is installed as a part of the Federation setup.

Click Next.

Select the database that is based on your requirement.

• Install PostgreSQL—Installs the PostgreSQL database that is bundled along with the dcnm.bin.

• Existing PostgreSQL 9.4—Existing PostgreSQL database that is already set up, with a clean schema.

• Existing Oracle 10g/11g/12c—Existing Oracle database that is already set up, with a clean schema.

• Existing Oracle 10g/11g/12c RAC—Existing Oracle database that is already set up, with a clean schema.

In the Service Name field, enter the service name of the Oracle RAC server. Enter a maximum of three host IP addresses. Click OK. The DB URL is generated.

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

If the tables are created in the default schema, you may encounter authentication issues after upgrading Cisco DCNM. You will have to create a schema with the sane name as the DCNM username owned by the same username. For instructions, see User and Schemas.

In the DCNM DB User field, enter the username that Cisco DCNM user uses to access the database. In the DCNM DB Password field, enter the password for the database user account that you specified. If you select Add Server to an existing federation, modify the database URL by selecting the corresponding RDBMS option. Because all the servers in Federation refer to the same database, you must provide the dcnmuser name and password of the primary server.

Click Next. Review the limitations with Oracle Database and click OK.

Click Next.

• 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 that are assigned to network interfaces on the server system.

• If you want to change the port that the Cisco DCNM-SAN web server listens to, enter the new port number in the SAN Web Server Port field. By default, the Cisco DCNM-SAN web server listens to TCP port 443.

  Note	During Cisco DCNM installation, use port numbers that are free. For example, 87 and 23 are reserved or restricted web ports.

Click Next.

Perform one of the following:

• Click Choose to select a path to store the DCNM archive directory.

  Note	If you must choose a remote system, provide the UNC path. For example: //Server/Share/directorypath.

• Click Restore Default Folder to retain the default folder.

Click Next.

• In the Admin Username field, enter a name for a Cisco DCNM server user. The installer creates the Cisco DCNM server user and assigns the Administrator role to it.

• In the Password field, enter a password for the user, and in the Confirm Password field, reenter the password.

  Adhere to the following password requirements. If you do not comply with the requirements, the DCNM application may not function properly:

  • It must be at least eight characters long and contain at least one alphabet and one numeral.

  • It can contain a combination of alphabets, numerals, and special characters.

  • Do not use any of these special characters in the DCNM password for any deployment mode: <SPACE> & $ % ‘ “ ^ = < > ; :

Click Next.

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

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

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

Click Next.

The Choose Link Folder is skipped and by default the location is /root directory.

Click Previous to go to the previous tabs and modify the configuration.

Click Next.

The progress bar description shows the process during the installation.

Wait until the DCNM is deployed on the system.

Press Return key to launch the Web Interface of Cisco DCNM for SAN Management.

This makes the DCNM installed as a secondary appliance in a Federation setup. The Pre-installation Summary screen displays the Federation status and nodes in the Federation Settings area.

The following message appears:

Please close the DCNM Installation wizard gracefully using "Done" optionon last installation step and wait for the installation wizard to close automatically. Do not restart the system or forcefully terminate the Installation wizard while it is still in progress." 

Click OK to continue.

Cisco DCNM uses both strong and weak ciphers when connecting to switches. If you use only strong ciphers for the network, select the checkbox. Ensure that the switches in your network support strong ciphers before you select checkbox, as DCNM will not be able to connect to switches which do not support strong ciphers.

The username and password of the database are same for all the server installation forming the federation. Similarly, the username and password of DCNM are same for all the server installation forming the federation.

#-----------------BASIC Properties---------------------DCNM_IP_ADDRESS=<ip_address_of_host_machine>USER_INSTALL_DIR=/usr/local/cisco/dcmINSTALLATION_TYPE=NEW_INSTALL#INSTALLATION_TYPE=UPGRADESAN_FEDERATION=FALSE#SAN_FEDERATION=TRUE

If you are using PostgreSQL database, edit this block:

#--------------New Postgress---------------------------PG_DB_PATH=/usr/local/cisco/dcm/db#PG_DB_PATH=/opt/dctest/cisco/dcm/db /*non-default installation directory*/#BACKUP_FILE=/opt/dctest/cisco/dcm/dcnm/bin/<backup-filename> /*non-default backup file directory*/DCNM_DB_URL=jdbc\:postgresql\://localhost\:5432/dcmdbDCNM_DB_NAME=dcmdbSELECTED_DATABASE=postgresqlDCNM_DB_USERNAME=dcnmuserDCNM_DB_USER_PASSWORD=dcnmuser#CLEAN_DATABASE=TRUE

If you are using the Oracle database, edit this block:

#------------------DATABASE Properties--------------------#User can configure these properties to use existing database or# install fresh Postgres as database for the DCNM. Existing database# can be postgres (remote or local), Oracle (remote or local)# or it can be Oracle RAC.#----------------------------------------------------USE_EXISTING_DB=FALSE#USE_EXISTING_DB=TRUEORA_DB_PATH=C:\\oraclexe\\app\\oracle\\product\\10.2.0\\server

#---------------------DATA PATH----------------#Data path is the folder location where DCNM LAN related #information like Config archives, templates etc. are stored.# In DCNM LAN Cluster mode this folder has to be a shared folder.#For linux and windows it will be different as the folder structure vaires#----------------------------------------------------DATA_PATH=/usr/local/cisco/dcm/dcnm#---------------------DATA PATH----------------

#-----------------User Configuration-----------------#DCNM User Configuration Properties#If you want to use special characters in DCNM_ADMIN#credentials,Please use escape character(\) before #the symbol [For eg. Password "an$6x12" must be specified as "an\$6x12" ].#----------------------------------------------------DECRYPT_PASSWORDS=FALSEDCNM_ADMIN_USER=adminDCNM_ADMIN_USER_PASSWORD=admin123#-----------------User Configuration-----------------

#----------------Secure Ciphers-------------------------------------#DCNM uses both strong and weak ciphers when connecting to switches#If user wants to use only strong ciphers for connection, please set#property to TRUE. Make sure your switches support strong ciphers before#setting the property as DCNM will not be able to connect to switches which#support only weak ciphers.#-----------------------------------------------------------------------SECURE_CIPHER=FALSE#SECURE_CIPHER=TRUE#-----------------------------------------------------------------------

#------------------------------IBM Raven Support----------------------#Set true if Vendor is IBM, by default false#---------------------------------------------------------------------IBM_INSTALL=FALSE /*Does not install IBM Data Center Network Manager*/#---------------------------------------------------------------------

You can check the status of installation by using the following command ps -ef | grep ‘LAX’ . The prompt will return after the silent install is complete.

Press Return key to launch the Web Interface of Cisco DCNM on Linux for SAN Management.

A list of the latest release software for Cisco DCNM available for download is displayed.

Click Search icon.

A list of the latest release software for Cisco DCNM available for download is displayed.

Depending on the version of the VMware vsphere web HTML5 interface may not work properly when deploying Huge or Compute OVA, as it does not allow users to specify extra disk size. Therefore, we recommend that you use Flex interface for deploying VMs.

If you're deploying OVF template using the ESXi 6.7, the installation fails if you use Internet Explorer browser with HTML5. Ensure that you one of the following options to successfully deploy OVF template with ESXi and 6.7:

• Mozilla Firefox browser, with HTML 5 support

  Use flex interface if HTML 5 is not supported

• Mozilla Firefox browser, with flex\flash support

• Google Chrome browser, with HTML 5 support

  Use flex interface if HTML 5 is not supported

You can also choose Actions > Deploy OVF Template.

Deploy OVF Template Wizard opens.

You can choose the OVA file by one of the following methods:

• Select the URL radio button. Enter the path of the location of the image file.

• Select Local File radio button. Click Browse. Navigate to the directory where the image is stored. Click OK.

Click Next.

Click Accept and click Next.

• In the Name field, enter an appropriate name for the OVF.

  Note	Ensure that the VM name is unique within the Inventory.

• In the Browse tab, select Datacenter as the deployment location under the appropriate ESXi host.

Click Next.

• Choose Small (Lab or POC) to configure the virtual machine with 8 vCPUs, 24GB RAM.

  Choose Small for proof-of-concept and other small-scale environments with fewer than 50 switches that are not expected to grow with time.

• Choose Large (Production) to configure the virtual machine with 16 vCPUs, 32GB RAM.

  We recommend that you use a Large deployment configuration when you are managing more than 50 devices to leverage better RAM, heap memory, and CPUs. For setups that could grow, choose Large.

• Choose Compute to configure the virtual machine with 16 vCPUs, 64GB RAM.

• Choose Huge to configure the virtual machine with 32 vCPUs, 128GB RAM.

  We recommend that you choose this configuration if you are deploying the SAN Insights features.

Click Next.

Click Next.

Click Next.

• dcnm-mgmt network

  This network provides connectivity (SSH, SCP, HTTP, HTTPS) to the Cisco DCNM Open Virtual Appliance. Associate this network with the portgroup that corresponds to the subnet that is associated with the DCNM Management network.

• enhanced-fabric-mgmt

  This network provides enhanced fabric management of Nexus switches. You must associate this network with the port group that corresponds to management network of leaf and spine switches.

  Note	This network is optional for Cisco DCNM SAN OVA/ISO Deployments.

• enhanced-fabric-inband

  This network provides in-band connection to the fabric. You must associate this network with port group that corresponds to a fabric in-band connection.

  Note	This network is not applicable for Cisco DCNM SAN OVA/ISO Deployments.

However, you can edit the network properties after installation, if required, using the appmgr update network-properties command. For more information, see Editing Network Properties Post DCNM Installation.

From the Destination Network drop-down list, choose to associate the network mapping with the port group that corresponds to the subnet that is associated with the corresponding network.

Click Next.

Enter the IP Address (for the outside management address for DCNM), Subnet Mask, and Default Gateway.

Ensure that add valid values for the Management Network properties. Properties with invalid values will not be assigned. The VM will not power on until you enter valid values.

From Release 11.3(1), for Huge and Compute configurations, you can add extra disk space on the VM. You can add from 32GB up to 1.5TB of disk space. In the Extra Disk Size field, enter the extra disk size that will be created on the VM.

Click Next.

Click Back to go to the previous screens and modify the configuration.

Click Finish to deploy the OVF template.

You can see the deployment status in the Recent Tasks area on the vSphere Client.

You can see the status in the Recent Tasks area.

A message indicating that the DCNM appliance is configuring appears on the screen.

***************************************************************Please point your web browser tohttps://<IP-address>:<port-number>to complete the application***************************************************************

Copy and paste the URL to the browser to complete the installation, using the Web Installer.

Click Next.

From the Installation mode drop-down list, choose SAN Only installation mode for the DCNM Appliance.

From the OEM Vendor drop-down list, choose your vendor. You can choose Cisco Systems, Inc. or IBM.

Click Next.

• In the Administrator Password field, enter the password that is used to connect to the applications in the Cisco DCNM.

  All special characters, except %$^=;.*\'" <SPACE> is allowed in the password.

  Enter the password again in the Repeat Administrator Password field.

• In the Database Password field, enter the password for the PostgreSQL database.

  All special characters, except %$^=;.*\'" <SPACE> is allowed in the password.

  Enter the password again in the Repeat Database Password field.

  Note	If Database Password field is left blank, it shall consider the Administrator password as the PostgreSQL password.

• In the Superuser Password (root) field, enter the password for the Superuser to access root privileges.

  Enter the password again in the Superuser Password field.

  Note	If the Superuser Password is left blank, it shall consider the Administrator password as the Superuser password. However, we recommend that you configure a strong password for security reasons.

Select the Show passwords in clear text check box to view the password that you have entered.

Click Next.

• In the Fully Qualified Hostname field, enter the hostname that is a fully qualified domain name (FQDN) as per RFC1123, section 2.1. Hostnames with only digits is not supported.

• In the DNS Server Address List field, enter the DNS IP address.

  You can also configure the DNS server using an IPv6 address.

  From Release 11.3(1), you can configure more than one DNS server.

• In the NTP Server Address List field, enter the IP address of the NTP server.

  The value must be an IP or IPv6 address or RFC 1123 compliant name.

  From Release 11.3(1), you can configure more than one NTP server.

• From the Timezone drop-down list, select the timezone in which you are deploying the DCNM.

Click Next.

However, you can edit the network properties after installation, if required, using the appmgr update network-properties command. If both eth0 and eth1 interfaces are configured, you can configure static routes to use a single interface using the same command. For more information, see Editing Network Properties Post DCNM Installation.

Click Next.

Click Next.

Click Previous to go to the previous tabs and modify the configuration. Click Start Installation to complete the Cisco DCNM Installation for the chosen deployment mode.

A progress bar appears showing the completed percentage, description of the operation, and the elapsed time during the installation. After the progress bar shows 100%, click Continue.

A success message appears with the URL to access DCNM Web UI.

***************************************************************Your Cisco Data Center Network Manager software has been installed.DCNM Web UI is available athttps://<<IP Address>>You will be redirected there in 60 seconds.Thank you***************************************************************

A list of the latest release software for Cisco DCNM available for download is displayed.

Click on Search icon.

A list of the latest release software for Cisco DCNM available for download is displayed.

You can either launch Java-based KVM or HTML-based KVM.

• Map CD/DVD

• Map Removable Disk

• Map Floppy Disk

Navigate to the location where the ISO image is located and load the ISO image.

For more information about using the UCS KVM Console window, see the Cisco UCS Server Configuration Utility, Release 3.1 User Guide at the following URL:

https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/ucsscu/user/guide/31/UCS_SCU/booting.html#wp1078073

For Cisco UCS with the disk size of 2TB or higher and with 4K sector size drivers, the UEFI boot option is required. For more information, see UEFI Boot Mode.

The option shown in the following image appears when the ISO image is booted with UEFI.

Enter 1 to configure the Cisco DCNM network interfaces from the available physical interfaces.

Enter 2 to configure the Cisco DCNM network interfaces from the available physical interfaces that are bundled together to form a single port-channel, configured as a trunk.

Choose the Management Interface (eth0) and Out-of-Band interface (eth1) from the Network Interface List. You can also configure the in-band interface (eth2) if necessary.

However, you can edit the network properties after installation, if required, using the appmgr update network-properties command. For more information, see Editing Network Properties Post DCNM Installation.

After the installation is complete, the system reboots and a message indicating that the DCNM appliance is configuring appears on the screen.

***************************************************************Please point your web browser tohttp://<IP-address>:<port-number>to complete the application***************************************************************

Copy and paste the URL to the browser to complete the installation using the Web Installer.

need info on dcnm-kvm-vm-huge.xml

A VM is created in the Virtual Machine Manager.

• device type: IDE disk

• cache-mode: default

• storage format: raw

We recommend that you use storage size of 500GB.

The operating system is installed.

Choose the Management Interface (eth0) and Out-of-Band interface (eth1) from the Network Interface List. You can also configure in-band interface (eth2) if necessary.

However, you can edit the network properties after installation, if required, using the appmgr update network-properties command. For more information, see Editing Network Properties Post DCNM Installation.

After the installation is complete, the system reboots and a message indicating that the DCNM appliance is configuring appears on the screen.

***************************************************************Please point your web browser tohttp://<IP-address>:<port-number>to complete the application***************************************************************

Copy and paste the URL to the browser to complete the installation using the Web Installer.

Click Next.

From the Installation mode drop-down list, choose SAN Only installation mode for the DCNM Appliance.

From the OEM Vendor drop-down list, choose your vendor. You can choose Cisco Systems, Inc. or IBM.

Click Next.

• In the Administrator Password field, enter the password that is used to connect to the applications in the Cisco DCNM.

  All special characters, except %$^=;.*\'" <SPACE> is allowed in the password.

  Enter the password again in the Repeat Administrator Password field.

• In the Database Password field, enter the password for the PostgreSQL database.

  All special characters, except %$^=;.*\'" <SPACE> is allowed in the password.

  Enter the password again in the Repeat Database Password field.

  Note	If Database Password field is left blank, it shall consider the Administrator password as the PostgreSQL password.

• In the Superuser Password (root) field, enter the password for the Superuser to access root privileges.

  Enter the password again in the Superuser Password field.

  Note	If the Superuser Password is left blank, it shall consider the Administrator password as the Superuser password. However, we recommend that you configure a strong password for security reasons.

Select the Show passwords in clear text check box to view the password that you have entered.

Click Next.

• In the Fully Qualified Hostname field, enter the hostname that is a fully qualified domain name (FQDN) as per RFC1123, section 2.1. Hostnames with only digits is not supported.

• In the DNS Server Address List field, enter the DNS IP address.

  You can also configure the DNS server using an IPv6 address.

  From Release 11.3(1), you can configure more than one DNS server.

• In the NTP Server Address List field, enter the IP address of the NTP server.

  The value must be an IP or IPv6 address or RFC 1123 compliant name.

  From Release 11.3(1), you can configure more than one NTP server.

• From the Timezone drop-down list, select the timezone in which you are deploying the DCNM.

Click Next.

However, you can edit the network properties after installation, if required, using the appmgr update network-properties command. If both eth0 and eth1 interfaces are configured, you can configure static routes to use a single interface using the same command. For more information, see Editing Network Properties Post DCNM Installation.

Click Next.

Click Next.

Click Previous to go to the previous tabs and modify the configuration. Click Start Installation to complete the Cisco DCNM Installation for the chosen deployment mode.

A progress bar appears showing the completed percentage, description of the operation, and the elapsed time during the installation. After the progress bar shows 100%, click Continue.

A success message appears with the URL to access DCNM Web UI.

***************************************************************Your Cisco Data Center Network Manager software has been installed.DCNM Web UI is available athttps://<<IP Address>>You will be redirected there in 60 seconds.Thank you***************************************************************

Save the dcnm-client.zip to your directory.

• If you are launching DCNM on Windows environment:

  Double-click on the FMClient.bat file to launch the Cisco DCNM SAN Client.

  Double-click on the DeviceManager.bat to launch the Cisco DCNM Device Manager.

• If you are launching DCNM on Linux environment:

  Run ./FMClient.sh Script to launch SAN Client.

  Run ./Devicemanager.sh script to launch Device Manager.

• For Windows deployment:

  Double-click on the FabricManager.bat file to launch the Cisco DCNM SAN Client.

  Double-click on the DeviceManager.bat file to launch the Cisco DCNM Device Manager.

• For Linux deployment:

  Run the ./ FabricManager.sh script to launch the Cisco DCNM SAN Client.

  Run the ./DeviceManager.sh script to launch the Cisco DCNM Device Manager.

keytool.exe -exportcert -file dcnmweb.crt -alias sme -keystore C:\[DCNM Install directory]\cisco\dcm\wildfly-14.0.1.Final\Standalone\configuration\fmserver.jks

keytool.exe -importcert -trustcacerts -file dcnmweb.crt -keystore fmtrust.jks -storetype jks

./keytool -exportcert -file dcnmweb.crt -alias sme -keystore /usr/local/cisco/dcm/wildfly-14.0.1.Final/standalone/configuration/fmserver.jks

./keytool -importcert -trustcacerts -file dcnmweb.crt -keystore fmtrust.jks -storetype jks

This is applicable on all DCNM Federation fresh installation, with default DCNM self-signed certificate. It is also applicable on DCNM Federation upgrade with default DCNM self-signed certificate.

The VNC client-server session is not encrypted.