Guidelines and Limitations
The guidelines and limitations for installing and upgrading Cisco DCNM are as follows:
General Guidelines and Limitations
-
Adhere to the following password requirements. If you do not comply with the requirements, the DCNM application might 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.
-
All special characters, except %$^=;.*\'" <SPACE> is allowed in the password.
-
After upgrade, you can login to the DCNM server using the new sysadmin password. However, you must use the old DCNM password to login to the Web UI.
-
The new Administrative password that is entered is used in the following scenarios.
-
—accessing the DCNM appliance via its console.
-
—accessing the appliance via SSH
-
—for applications running on the appliance, for example, Postgres DBMS
-
-
-
Do not interrupt the boot process (such as pressing the Ctrl+ALT + DELETE keys) when installing DCNM. If you interrupt, you must restart the installation process.
-
Ensure that you configure the timezone after installation or upgrade, before performing any other operations on the Cisco DCNM Appliance. Use the NTP server for configuring timezones.
-
To check the status of the running Postgres database in Native HA setup, use following command:
dcnm# su - postgres -c dcnm# pg_ctl -D /usr/local/cisco/dcm/db/data status
Do not use the systemctl command.
-
Do not begin the password with Hash (#) symbol. Cisco DCNM considers the password as an encrypted text if it begins with # symbol.
Fresh Installation
-
For Virtual Appliances (OVA/ISO), the installer installs the Operating system and Cisco DCNM components.
-
The DCNM OVA cannot be deployed by connecting the vSphere client directly to the ESXi server.
Upgrade
-
You can choose to discard the old performance manager (PM) data and continue to upgrade to DCNM Release 11.4(1). For instructions about how to drop performance manager data, see Performance Manager Data Management before Upgrading to Release 11.4(1). If you choose to retain the old PM data while you upgrade to Release 11.4(1), we recommend that you contact Cisco TAC for further assistance.
-
Ensure that you do not perform inline upgrade from an SSH session. The session may timeout and result in an incomplete upgrade.
-
Disable Telemetry in the earlier release before you upgrade.
-
Disable Telemetry before you deploy Compute Nodes. You can enable Telemetry after deploying compute nodes.
For DCNM in Native HA mode, Telemetry is supported with 3 compute nodes only.
-
If you need to run Network Insights applications, you must install 3 compute nodes.
-
Disable Telemetry before modifying Interface settings. You can enable Telemetry after modifying the settings.
-
During a backup and restore process, the compute nodes are also included in the backup. After you deploy the new compute, you can restore the backup on the compute node.
If there was no backup, disconnect the 3 compute nodes, and erase the data on all the compute nodes. On the Cisco DCNM Web Client UI, navigate to Application > Compute. Select the + icon to join the compute nodes.
-
To erase data on the compute node, logon to the compute node through an SSH session and erase the data using the rm -rf /var/afw/vols/data command.
Note
You must run the above command separately on all compute nodes to erase data.
-
Before starting NIR application after upgrade, on the DCNM Web UI, choose Application > Preferences. Modify the network settings as required. If you do not modify the network settings after upgrade before you enable the Telemetry on the Fabrics, the configuration will not complete. You must stop the NIR app, modify the network settings and start the app again, to resolve the issue.