I'm really confused after a host migration of our DCNM environment. We upgraded from DCNM 5.2.1 to 6.1.2, and after that, from 6.1.2 to 6.2.1, as the recommended upgrade path. The new environment was installed in a new host, so we did a database backup and restored it. This procedure was done without any problems, we had the same information in the new host.
After that, we did a shutdown in the old host, and DCNM SAN stopped working, we can't connect to it. In other words, the new DCNM environment only works if old DCNM is up.
Checking the configuration, I have observed several things:
- Federation tab only shows the old server IP (view attach 1&2)
- When we connect to DCNM SAN, we connect to the new IP address, but when we try to manage the fabric, we are redirected to the old IP
- When we connect to DCNM SAN, the license tab only shows the old IP address, and give us the option to license it with the MAC of the server, I think that this tab shoud give us the option to register the new host, isn't it?
I also check the PLMapping.sh (from dcm/fm/bin), and give us the following output:
Well, I think I have found the answer (sorry about this, I will post the answer if someone has this error...).
The problem is based on the data file which is used to import the database. I suppose that there are some tables that define the federation or the DCNM host that collects data. To resolve this (if you change the IP), you must exec:
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...