CBD Upgrade from 2.7.1 on Linux (ubuntu 20.04) to 2.9.1

[AbbyDoc]

Hello,

I have CBD 2.7.1 running on Linux (Ubuntu 20.04) in Azure and would like to upgrade to 2.9.1. I get the following:

Cisco Business Dashboard version 2.9.1 is available for upgrade but is not supported on this operating system version (Ubuntu 20.04.4 LTS (focal fossa)).
Please take a backup of the dashboard using the System > Backup page. Then create a new dashboard install based on the latest version. You may then restore the backup to the new dashboard.
See the Cisco Business Dashboard version 2.9.1 Cisco Business Dashboard - Cisco for details on upgrading.

I follow the instructions in the guide, but it does not work. There are certificate issues, and the devices will not register after restoring backup to a new Azure VM running. (22.04).

Kind regards

Abby

[Mark Fang · Accepted solution]

To ensure a successful upgrade and restore process, it's essential that the server address remains consistent, as the devices connect to the Dashboard using this address.

Have you ensured that the same public IP address is assigned to the new server instance? In Azure, you may need to follow these steps:
1.Stop Both VM Instances: First, stop both the old and new VM instances.
2.Dissociate the Public IP Address: Next, dissociate the public IP address from the old VM instance. This can be done in the Azure portal under the "Public IP addresses" section.
3.Associate the Public IP Address to the New Instance: After dissociating, associate the public IP address with the network interface of the new VM instance. Note, if there is already a public IP addresses associated with the network interface of the new VM instance, you may need to dissociate it first.
4.Start the New VM Instance: Finally, start the new VM instance.

[AbbyDoc]

Hi @Mark Fang 

Thank you for the reply.

Is there an official migration guide that I can follow to make sure I get all the steps right?

Regards

[Mark Fang]

Unfortunately, there isn't an official migration guide specifically for this scenario. The process for CBD itself is relatively straightforward, but the complexity arises from the Azure configuration. The steps involve managing your Azure resources, such as ensuring the same public IP address is assigned to the new server.

[AbbyDoc]

@Mark Fang 

Do I have to dissociate the license in Cisco Software Central before starting the new VM with CBD?

[Mark Fang]

Yes, please do it. Alternatively, you can deregister the license from the old VM.

[AbbyDoc]

@Mark Fang 

To confirm steps?

1. Create a new Azure VM Unbutu 22.04 with CBD 2.9.1 and shutdown.
2. Backup current working CBD 2.7.1.
3. Disassociated WAN IP.
4. Deregister the CBD license.
5. Accociate WAN IP from previous VM with new created VM.
6. Start the newly created VM and restore backup.
7. Register licence.

I am using Let's Encrypt for my certificate provided in CBD and when I last tried the migration, I noticed this was an issue.

Also, after the migration, will it be out to just update the underlaying OS Unbutu 20.24 without the need to migrate with varions CBD version releases?

[Mark Fang]

Please exchange steps 3 and 4 because you need the WAN IP to access the internet in order to deregister the license.

Since you are using a Let's Encrypt certificate, you are likely utilizing a domain name for the CBD server. This simplifies the process. You may only need to update the DNS record to point to the public IP of the new 2.9.1 CBD VM instance. This should allow devices to reconnect. However, ensure you deregister the CBD license from the old server and shut it down afterward.

[AbbyDoc]

Hi @Mark Fang 

Noted for the step exchanges.

All I did before was create a DNS name alias in Azure linked to CBD Static WAN as below. Is there a better option?

[Mark Fang]

Is it possible to update the DNS name alias to be linked to the public IP address of the new VM or update it to be the public IP address of the new VM directly?

[AbbyDoc]

I think it is possible to update the DNS name linked to the Public IP address in Azure after creating the new VM but I have not tried it. 

Is that what you mean?

[Mark Fang]

Right. Since DNS names must be unique, you'll need to clear the DNS name label on the old VM first. Once that's done, you can assign the original DNS name to the new VM.

[AbbyDoc]

Yes, that is correct.

@Mark Fang Based on suggestions

To confirm steps?

1. Create a new Azure VM Unbutu 22.04 with CBD 2.9.1 and shutdown.
2. Backup current working CBD 2.7.1.
3. Deregister the CBD license.
4. Remove DNS alias in Azure
5. Disassociated WAN IP.
6. Stop/shutdown VM in Azure.
7. Accociate WAN IP from previous VM with new created VM.
8. Add the same DNS alias as the one deleted from the old VM.
9. Start the newly created VM and restore backup.
10. Register licence.

[Mark Fang]

Correct.

[Mark Fang]

If I understand correctly, you already have a running CBD 2.9.1 instance with the backup restored. If that's the case, all you need to do now is remove the DNS alias from the old VM and assign it to the new VM.