cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

738
Views
5
Helpful
1
Replies
Nadav
Rising star

DCNM 10.4.2 OVA: Is it possible to upgrade to DCNM 11.0.1 and maintain SAN support?

Hi everyone,

 

DCNM 11.0.1 doesn't support SAN in the OVA version.

 

1) We'd like to see if it's possible to have SAN support while upgrading from DCNM 10.4.2 OVA to 11.0.1 OVA, as a workaround to DCNM 11.0.1 OVA not having SAN support. Can anyone provide any insight?

 

2) Does DCNM 11.0.1 for Linux support HA? 

 

3) Does upgrading from DCNM 10.4.2 OVA to 11.0.1 retain all SAN configuration?

 

Thanks in advance for all the help!

1 ACCEPTED SOLUTION

Accepted Solutions
sbhadrav@cisco.com
Contributor

This section includes instructions for upgrading your Cisco DCNM Appliance installation in the following scenarios:
Cisco DCNM Installer version DCNM 11.0(1)
Release from which you can upgrade DCNM 10.4(2)
You can migrate Cisco DCNM with a local PostgreSQL database and Cisco DCNM in a High Availability (HA) environment. You must provide username and password for external oracle database.When upgrading to a newer DCNM version, you should use the same administrative password (as used in the existing setup) for the new DCNM setup. If you want to use a different password in the new setup, change the password in the existing DCNM setup before taking a backup and initiating the upgrade process.
Prior to Cisco DCNM Release 11.0(1), DCNM OVA and ISO supported SAN functionality. Beginning with Cisco DCNM 11.0(1), OVA and ISO does not ship with SAN support. You can upgrade to Release 11.0(1) only from DCNM Release 10.4(2).
Upgrade possible to LAN Fabric Deployment
Upgrade is not possible if SAN is used or is BottomUp configuration is used in 10.4(2).

Upgrade is possible to LAN Fabric Deployment if SAN and TopDown configurations is used in 10.4(2).

Upgrade is possible to Classic LAN Deployment if SAN and TopDown configurations are not used in 10.4(2).
Old database cannot be migrated to 11.0(1)

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.

Do not use any of these special characters in the DCNM password for all platforms:

<SPACE> " & $ % ' ^ = < > ; : ` \ | / , .*
From Cisco DCNM Release 11.0(1), the characters that are allowed in the Administrative password is restricted for OVA and ISO installations. Therefore while upgrading, the old password used in DCNM 10.4(2) is not valid. However, different passwords are allowed during Upgrade.

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, e.g. Postgres DBMS

However, after the upgrade, since Postgres DBMS is restored from the backup that is taken on DCNM 10.4(2), you must logon to the Cisco DCNM Web UI using the password used on DCNM Release 10.4(2) appliance.

Clear the browser cache before you launch the Cisco DCNM Web UI using the Management Network IP address, after upgrade. For instructions on how to clear the browser cache, see Clearing Browser Cache.

View solution in original post

1 REPLY 1
sbhadrav@cisco.com
Contributor

This section includes instructions for upgrading your Cisco DCNM Appliance installation in the following scenarios:
Cisco DCNM Installer version DCNM 11.0(1)
Release from which you can upgrade DCNM 10.4(2)
You can migrate Cisco DCNM with a local PostgreSQL database and Cisco DCNM in a High Availability (HA) environment. You must provide username and password for external oracle database.When upgrading to a newer DCNM version, you should use the same administrative password (as used in the existing setup) for the new DCNM setup. If you want to use a different password in the new setup, change the password in the existing DCNM setup before taking a backup and initiating the upgrade process.
Prior to Cisco DCNM Release 11.0(1), DCNM OVA and ISO supported SAN functionality. Beginning with Cisco DCNM 11.0(1), OVA and ISO does not ship with SAN support. You can upgrade to Release 11.0(1) only from DCNM Release 10.4(2).
Upgrade possible to LAN Fabric Deployment
Upgrade is not possible if SAN is used or is BottomUp configuration is used in 10.4(2).

Upgrade is possible to LAN Fabric Deployment if SAN and TopDown configurations is used in 10.4(2).

Upgrade is possible to Classic LAN Deployment if SAN and TopDown configurations are not used in 10.4(2).
Old database cannot be migrated to 11.0(1)

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.

Do not use any of these special characters in the DCNM password for all platforms:

<SPACE> " & $ % ' ^ = < > ; : ` \ | / , .*
From Cisco DCNM Release 11.0(1), the characters that are allowed in the Administrative password is restricted for OVA and ISO installations. Therefore while upgrading, the old password used in DCNM 10.4(2) is not valid. However, different passwords are allowed during Upgrade.

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, e.g. Postgres DBMS

However, after the upgrade, since Postgres DBMS is restored from the backup that is taken on DCNM 10.4(2), you must logon to the Cisco DCNM Web UI using the password used on DCNM Release 10.4(2) appliance.

Clear the browser cache before you launch the Cisco DCNM Web UI using the Management Network IP address, after upgrade. For instructions on how to clear the browser cache, see Clearing Browser Cache.