Prerequisites and guidelines for migrating from DCNM to ND
Upgrading from DCNM 11.5(4) consists of the following workflow:
-
Ensure you complete the prerequisites and guidelines described in this section.
-
Back up your existing configuration using a migration tool specific to the target ND release.
-
Deploy a brand new Nexus Dashboard cluster.
-
Restore the configuration backup you created in step 1.
![]() Note |
Before you proceed with the upgrade:
|
Fabric Type Compatibility
By using the appropriate Upgrade Tool, you can restore data that is backed up from DCNM Release 11.5(4) on a newly deployed Nexus Dashboard for the fabric type as mentioned in the following table.
![]() Note |
SAN fabrics are mainly unchanged in Nexus Dashboard release 4.1.1. |
Pre-4.1.1 fabrics |
4.1.1 fabric types |
|
---|---|---|
Fabric technologies |
Fabric types |
|
LAN |
||
VXLAN EVPN |
Data Center VXLAN EVPN |
Data Center VXLAN EVPN - iBGP |
eBGP VXLAN EVPN |
BGP fabric |
Data Center VXLAN EVPN - eBGP |
VXLAN EVPN |
Campus VXLAN EVPN |
Campus VXLAN EVPN |
eBGP Routed |
BGP fabric |
BGP fabric |
Classic LAN |
Enhanced Classic LAN |
Enhanced Classic LAN |
Classic LAN |
Classic LAN |
Legacy Classic LAN |
Custom |
External connectivity network |
External and inter-fabric connectivity network |
Custom |
Custom network |
External and inter-fabric connectivity network |
Custom |
Multi-site external network |
External and inter-fabric connectivity network |
LAN Monitor |
LAN Monitor |
External and inter-fabric connectivity network |
VXLAN EVPN |
VXLAN EVPN Multi-Site |
VXLAN (fabric group) |
Multi-Fabric Domain |
Fabric Group |
Classic (fabric group) |
IPFM |
||
IPFM |
IPFM |
IPFM |
IPFM |
IPFM Classic |
IPFM classic |
Generic Multicast |
IPFM Classic |
IPFM classic |
Multi-Fabric Domain |
Fabric Group |
IPFM (fabric group) |
Feature Compatibility Post Upgrade
The following table lists caveats associated with features that are restored from DCNM 11.5(4) backup after upgrading.
Feature in DCNM 11.5(4) |
Upgrade Support |
---|---|
Nexus Dashboard Insights configured |
Carried over from 11.5(4) |
Container Orchestrator (K8s) Visualizer |
Carried over from 11.5(4) |
VMM Visibility with vCenter |
Carried over from 11.5(4) |
Nexus Dashboard Orchestrator configured |
Not carried over from 11.5(4) |
Preview features configured |
Not carried over from 11.5(4) |
LAN switches in SAN installations |
Not carried over from 11.5(4) |
IPAM Integration |
Not carried over from 11.5(4) |
Custom topologies |
Not carried over from 11.5(4); must be recreated and saved |
Switches discovered over IPv6 |
Not carried over from 11.5(4) |
DCNM Tracker |
Not carried over from 11.5(4) |
Fabric Backups |
Not carried over from 11.5(4) |
Report Definitions and Reports |
Not carried over from 11.5(4) |
Switch images and Image Management policies |
Not carried over from 11.5(4) |
SAN CLI templates |
Not carried over from 11.5(4) |
Switch images/Image Management data |
Not carried over from 11.5(4) |
Slow drain data |
Not carried over from 11.5(4) |
Infoblox configuration |
Not carried over from 11.5(4) |
Endpoint Locator configuration |
You must reconfigure Endpoint Locator (EPL) post upgrade. However, historical data is retained up to a maximum size of 500 MB. |
Alarm Policy configuration |
Not carried over from 11.5(4) |
Performance Management data |
CPU/Memory/Interface statistics up to 90 days is restored post upgrade. Must be re-enabled on fabrics. |
Temperature data |
Temperature data is not saved in the backup and as a result is not restored after the migration. You must re-enable temperature data collection after the migration. |