Upgrade to Catalyst Center 3.1.x

Catalyst Center 3.1.5 and later use an architecture that provides

  • improved network automation and monitoring
  • optimized resource utilization, and
  • increased security.

To upgrade Catalyst Center, you'll need to:

  1. Ensure that the requirements and tasks described in Upgrade requirements have been completed.
  2. Complete the appropriate upgrade scenario.

Refer to this article for a description of how to complete these steps.

Upgrade requirements

Before you start the upgrade, ensure that the requirements and tasks described in these sections have been completed:

Also review the information provided in these sections:

General

  • Confirm that no critical operations (such as backups or upgrades) are currently running.
  • Ensure that NTP is configured on your system.
  • For three-node HA clusters, confirm that each cluster node is healthy and HA is active.
  • Install the Catalyst Center 3.1.x upgrade package.

Supported Catalyst Center versions

Ensure that one of these Catalyst Center versions is installed on the appliance you'll be upgrading from:

  • 2.3.7.7.70047
  • 2.3.7.7-70047.10
  • 2.3.7.9.70301
  • 2.3.7.9.70301.10
  • 2.3.7.10.70209
  • 2.3.7.10.70209.10
  • 2.3.7.11.70047

If not, upgrade to version 2.3.7.11. Complete the steps described in the Cisco Catalyst Center Upgrade Guide.

Back up and restore

  • Confirm that Catalyst Center backups are configured correctly for automation.
  • Configure NFS for Assurance backups, if you want to preserve historical Assurance data after the upgrade. In the Cisco Catalyst Center Administrator Guide, complete the steps described in the topic relevant to your deployment:
    • Example of NFS server configuration—Ubuntu
    • Example of NFS server configuration—Red Hat
     Note
    • For Catalyst Center 3.1.6-75524.200 SMU and later, you can use either NFS or remote sync (rsync)/SSH for automation data backups.
    • Catalyst Center also supports Windows-based NFS servers, as well an NFS provided by a storage vendor (such as NetApp or Isilon).

Cisco IMC

  • Verify the Cisco IMC settings for your deployment.
  • To determine your appliance's part number, view the Product Name field in Cisco IMC's Summary page.
  • Although Cisco IMC firmware versions 4.1 and later are supported, we recommend that you install these versions:
    • DN2 appliances: 4.3(2.260007)
    • DN3 appliances: 4.3(6.260017)
  • Confirm that the Cisco IMC interface is properly configured for your appliances and is accessible.
  • Review and resolve any critical hardware alerts detected by Cisco IMC.

Hardware

  • Ensure you are upgrading a second or third-generation Catalyst Center appliance.
     Note

    The Catalyst Center 3.1.x upgrade does not support first-generation Catalyst Center appliances. In the Cisco Catalyst Center Data Migration article, see the migration procedure for Scenario 14.

Required upgrade wizard information

Have this information ready before starting the Catalyst Center 3.1.x upgrade wizard:

  • Catalyst Center admin superuser login credentials, as only users configured with the SUPER-ADMIN-ROLE can perform the upgrade
  • Cisco IMC login credentials

Upgrade considerations

  • Do not create backups or perform other maintenance tasks after starting the upgrade.
  • CLI-based tuning changes, such as disabling older ciphers and TLS versions, are not captured or carried forward.
  • Complete the Catalyst Center upgrade in one sitting to prevent losing configuration changes that are not captured in a backup.

Unsupported Catalyst Center appliances and features

  • DN1 (first-generation) Catalyst Center appliances
  • IPv6
  • Clusters enabled with intercluster (ICL) IPsec

Install the Catalyst Center 3.1.x upgrade package

To upgrade to the new Catalyst Center architecture, first install the Catalyst Center 3.1.x upgrade package.

Step 1

From the main menu, choose System > Software Management to open the Software Management page.

Step 2

Confirm that the Release Upgrade Wizard-X is available heading is displayed at the top of page.

Step 3

Click Download now.

Step 4

After the download prechecks complete successfully, click Download.

You can click the More details link to open a slide-in pane that indicates the progress of the applications that are being downloaded.

Step 5

Click Install now.

Step 6

After the installation prechecks complete successfully, click Install.

You can click the More details link to open a slide-in pane that indicates the progress of the applications that are being installed.

After installation of the Catalyst Center 3.1.x upgrade package finishes, the upgrade wizard should start automatically.

Verify Cisco IMC settings

Step 1

Log in to Cisco IMC.

The Summary page opens.

Step 2

Confirm that the part number for your Catalyst Center appliance (listed in the Product Name field) matches one of part numbers listed in the Prerequisites topic's Hardware table.

Step 3

Confirm that a supported Cisco IMC version is installed:

If version 4.1 or later... Then...

is listed in the Firmware Version field,

proceed to Step 4.

is not listed in the Firmware Version field,

update your Cisco IMC firmware. In the Cisco Catalyst Center Upgrade Guide, see the "Update the Cisco IMC firmware" topic.

Step 4

Confirm that your appliance's virtual drives are named correctly:

  1. In the Cisco IMC Navigation pane, choose Storage > Cisco 12G Modular RAID Controller.

  2. Click the Virtual Drive Info tab.

  3. Verify that these settings are configured for your appliance's virtual drives:

    DN2 appliances DN3 appliances Boot drive

    Virtual drive number

    Virtual drive name

    Virtual drive number

    Virtual drive name

    0

    SYSTEM

    237

    BOOT

    True

    1

    FUSION

    238

    SHARED

    False

    2

    NDP

    239

    ANALYTICS

    False

Upgrade scenarios

Review and complete the upgrade scenario that applies to your deployment.

Scenario 1: Upgrade a single or three-node Catalyst Center cluster

In this scenario, you are upgrading a single or three-node deployment to Catalyst Center 3.1.x. To upgrade to this new architecture and migrate your existing network data, complete this procedure.

 Note

The upgrade procedure is essentially the same for both single-node and three-node Catalyst Center clusters. The differences are minor and described where necessary.

Before you begin

  1. Review the upgrade requirements and confirm that they have been met.
  2. Install the Catalyst Center 3.1.x upgrade package.

Step 1

The Catalyst Center 3.1.x Upgrade window should open automatically after you install the upgrade package.

If...

Then...

this window opens,

 proceed to Step 2.

this window does not open,

choose System > Catalyst Center 3.1.x Upgrade from the main menu.

Step 2

You are prompted to ensure that these requirements are in place:

  • The remote backup server is properly configured and reachable.
  • Storage space cleanup or retention jobs are NOT running on the remote SSH or NFS server.
     Note

    Customers may have configured scheduled cleanup workflows on the backup storage—either a remote SSH server or an NFS server—to free up space for newer backups. Because these workflows are not controlled by Catalyst Center, they can interfere with the upgrade process. Before you proceed, ensure that these jobs are disabled.

Select Run Backup Readiness Check.

During the upgrade, a new backup is created automatically. The backup readiness check determines whether the local disk has sufficient space to create a full backup (the All Data option, which includes Automation and Assurance data) by verifying these conditions:

  • Your deployment's backup size is 1 TB or smaller.
  • The amount of free space for your NDP disk (/data/maglev/srv/ndp) is at least 1.7 times your estimated backup size, plus an additional 100 GB. For example, if your estimated backup size is 100 GB, you will need at least 270 GB of NDP space:
    • 170 GB for the backup (100 GB x 1.7)
    • 100 GB for the ISO download/rebuild
  • The amount of free space for your shared disk (/data/maglev/srv) is at least 1.7 times your estimated backup size. For example, if your estimated backup size is 100 GB, then your shared disk requires at least 170 GB (100 GB for the backup, plus 70 GB of additional buffer).

If all these conditions are true, you will see this:

 Note

A remote SSH server is mandatory for the upgrade, even when the backup is created on the local disk. During the upgrade, Catalyst Center archives the backup data to the remote SSH server, ensuring that an external copy is retained outside the appliance.

If the local disk cannot accommodate the full backup, the backup readiness check also verifies whether the NFS server is configured and can accommodate the backup, including the appropriate permissions and performance validations.

If the NFS checks pass, you will see this (note that storage is set to Remote SSH + NFS):

If critical NFS checks fail, you will not be able to proceed with the All Data option. Until the NFS issues are resolved, only the Without Assurance Data option is available. You will see this:

Step 3

Select the backup option you want to use:

  • All Data: Select to back up both Assurance and Automation data.
  • Without Assurance Data: Select to back up only Automation data. Then select Proceed to confirm this selection.
     Note

    If you select this option, historical data will not be carried forward.

Step 4

After the check completes, select Get started.

Step 5

Complete the Catalyst Center 3.1x upgrade wizard.

The wizard begins by retrieving information from your source Catalyst Center cluster, such as its configured backup server and FQDN.

 Note

In any of the wizard's pages:

  • Select Exit to stop the wizard. Specify whether you want to save any settings you have entered.
  • Select Get Support to open a window that provides an email template you can use to report any issues you encounter while completing the wizard.

  1. If the wizard flags any information it can’t retrieve, select the Retry retrieving all details link.

  2. After the wizard retrieves all the information for your source cluster, select Next.

  3. In the Server authentication page, enter the password for the user listed in the Username field and then select Next.

  4. In the Cisco IMC details page, enter the IP address for your cluster’s Cisco IMC, as well as its login credentials. For a three-node cluster, enter the Cisco IMC details for each node. Then select Next.

     Note
    • The IP address you specify must match the IP address configured for your Catalyst Center appliance's Cisco IMC instance. Catalyst Center displays an error if they don't match.
    • If you are upgrading a three-node cluster, an icon and progress bar are displayed for each appliance in the cluster.

  5. In the Notifications page, specify whether you want to receive status update emails during the upgrade:

    If...

    Then...

    you want to receive status update emails,
    1. Select the Yes radio button.
    2. (Optional) Select Edit to make changes to the current SMTP configuration.
    3. Enter the addresses that should receive status updates.
    4. (Optional) Select Test mail to check whether the addresses you just specified receive a message.
    5. Select Next.

    you do not want to receive status update emails,

    select Next (the No radio button is already selected, by default).

  6. In the Summary page, review the settings you entered while completing the wizard:

    If...

    Then...

    the settings displayed are correct,

    select Next.

    any of these settings are missing,

    select the Refresh link and confirm whether the settings you entered are now displayed.

    any of these settings are incorrect,
    1. Select Back to return to the relevant wizard page.
    2. Make the necessary changes and return to the Summary page.
     Note
    • To export the settings you entered, select Export.
    • The backup strategy (local disk or external NFS) and selected backup scope (All Data or Without Assurance) are displayed in the summary's Backup Details section.

    Catalyst Center performs multiple prechecks and flags any items that may require attention. Catalyst Center will not allow you to proceed if it detects any critical errors.

     Note

    The checks performed may vary depending on the deployment type—such as single-node, three-node, airgap, or disaster recovery deployments—as well as the backup configuration.

Step 6

Take one of these actions:

If...

Then...

the check does not flag any issues,
  1. Select Get started.
  2. Proceed to Step 7.

the check finds issues you need to correct,
  1. Try to resolve the issues flagged by the check. If you need assistance, email the Cisco support team. Select Get Support to access the email template you should use.
  2. After you have made the necessary corrections, choose System > Catalyst Center 3.1.x Upgrade from the main menu to rerun the checks.

Step 7

Start the Catalyst Center 3.1.x upgrade.

  1. Confirm that you want to go ahead with the upgrade.

    The precheck may flag some issues that do not require immediate attention, such as low download speed or NFS throughput. These issues are flagged as Warnings. After the prechecks complete and you select Next, you will see this:

    If...

    Then...
    you are unsure whether to ignore the warnings,

    email the Cisco support team.
    you would like to ignore the warnings and proceed, Check the check box to acknowledge the warning, then select Proceed anyway.

  2. The Confirm Migration Start dialog box opens.

    This is the last point where you can back out of the upgrade. Only complete these actions if you are ready to proceed:

    1. Check the I understand this action is irreversible check box.
    2. Select Start.

    Catalyst Center prepares your deployment's backup data and the ISO image to be installed for the upgrade. A new backup is created at this point, and data from that backup is restored during the upgrade.

  3. After Catalyst Center completes these tasks, select Next.

  4. In the Cluster Migration dialog box, select Proceed.

    • From this point forward, Catalyst Center will not be available until the upgrade completes.
    • The page updates during the upgrade. You can monitor its progress as it completes.
    • If you are upgrading a three-node cluster, progress bars are displayed for each appliance in the cluster.

Step 8

After the upgrade completes, you will see an upgrade summary. Select Home to open the Catalyst Center home page.

Step 9

Clean up older backups.

Backups created in earlier versions of Catalyst Center are no longer compatible and may not appear in the Backup & Restore page. Note that the backup data itself is still present in the configured backup storage locations, including the NFS directory and/or the remote SSH directory. To avoid unnecessary storage usage, we recommend cleaning up these older backups manually.

  1. In the configured remote SSH directory, remove these folders:

    • backup-metadata
    • fusion.postgres
    • maglev-system.credentialmanager
    • maglev-system.glusterfs
    • maglev-system.mongodb
    • ndp.elasticsearch

  2. In the configured NFS directory, remove the ndp folder.

Scenario 2: Upgrade an air-gapped deployment to Catalyst Center 3.1.x

In this scenario, you are upgrading an air-gapped deployment to Catalyst Center 3.1.x.

Step 1

Raise a request with the Cisco TAC.

A representative gives you access and instructions for downloading the binary image for your Catalyst Center version from a Cisco file server. The air gap binary image includes the Catalyst Center 3.1.x upgrade package and ISO image for the 3.1.x version you're upgrading to.

For example, if you are upgrading from Catalyst Center 2.3.7.10, you would download CatC-SW-23710-316.200rev7-Upgrade-AIRGAP.bin from the Software Download page.

Catalyst Center supports these airgap deployment types:

If the networkMode value is...

Then your deployment type is...

cloud

Cloud mode (not airgapped)

airgap

Network Airgap mode: Blocks all outbound cloud communication, allowing only private IP ranges (RFC1918) and explicitly permitted subnets via Calico policies.

offline

Standard Airgap mode: Blocks outbound communication to only the Cisco catalog server (the catalog server is set to offline). It does not block other network-level outbound traffic. You can use firewalls, proxy policies, access control lists (ACLs), and routing controls to control outbound network traffic.

Unlike Catalyst Center 2.3.7.x, the 3.1.x platform only supports Network Airgap mode. As a result:

If the deployment type is...

Then...

Network Airgap

you will continue using this mode in Catalyst Center 3.1.x.

Standard Airgap

Catalyst Center will set Network Airgap mode for your deployment during the upgrade to 3.1.x.

Step 2

Obtain the allowed IP ranges.

During the upgrade, you are prompted to provide a list of allowed IP ranges (in CIDR format). After your deployment is upgraded, only these IP ranges are permitted and reachable. This requirement applies to both Network Airgap and Standard Airgap deployments.

 Note

This is especially important for Standard Airgap deployments. In Catalyst Center 2.3.7.x, Standard Airgap mode allowed outbound network traffic to public IP ranges (only the catalog server was offline). After the upgrade to 3.1.x, Catalyst Center operates in Network Airgap mode, which restricts outbound traffic. Therefore, if Standard Airgap mode was set for your deployment in 2.3.7.x, you must provide all allowed public IP ranges so that they remain accessible after the upgrade.

To determine the list of allowed IP ranges:

If the deployment type is...

Then...

Network Airgap

In a secure shell, enter the sudo maglev-config calico info | grep -B5 -A20 allow-outbound-external command.

The output contains the destination attribute, which lists all configured allowed IP ranges.

Standard Airgap

Private IP ranges remain accessible after the upgrade. Therefore, you need to obtain a list of all publicly accessible IP ranges. These include, but are not limited to, the following configurations:

  • Cluster subnet and VIP
  • Container subnet
  • Host IP
  • DNS server
  • Static routes
  • NTP server
  • HTTP proxy

Step 3

Deploy the air gap binary image by entering the maglev catalog airgap install binary-image-filename command.

binary-image-filename is the binary image specific to your Catalyst Center version.

The Catalyst Center 3.1.x upgrade package and ISO image for the 3.1.x version you're upgrading to are installed.

Step 4

The upgrade process is different from the standard airgap upgrade. Read the section "Upgrade your single or three-node Catalyst Center cluster" to ensure you understand each step in the upgrade process.

During the upgrade, you are prompted to provide the list of allowed IP ranges (in CIDR format) in the Server authentication page.

Scenario 3: Upgrade a disaster recovery deployment to Catalyst Center 3.1.x

In this scenario, you are upgrading your disaster recovery deployment to Catalyst Center 3.1.x.

Before you begin

  1. Verify the Cisco IMC settings for your appliances.
  2. Install the Catalyst Center 3.1.x upgrade package on both your disaster recovery system's main and recovery sites.

When reenabling your disaster recovery system after the upgrade, ensure that you set the correct Catalyst Center cluster as the main site. Otherwise, you will lose all data.

 Note
  • Ensure that your disaster recovery system's main site is the current active site. This requirement is critical for a successful upgrade.
  • Ensure that you have your disaster recovery configuration information available, such as VIPs and BGP routers. You’ll need this information to form a disaster recovery system after the 3.1.x upgrade.

After you install the upgrade package, you should see this:

Contact the Cisco TAC so they can enable the upgrade of your disaster recovery deployment.

Scenario 4: Restore Catalyst Center 3.1.3 data

In this scenario, you are migrating your Catalyst Center 3.1.3 data to an appliance that has Catalyst Center 3.1.5 or later installed.

Step 1

Confirm that you have enough space to store your backups after upgrading to Catalyst Center 3.1.5 or later.

In the Cisco Catalyst Center Administrator Guide, see the "Backup storage requirements" topic.

Step 2

Back up your Catalyst Center 3.1.3 deployment.

In the Cisco Catalyst Center Administrator Guide, complete the steps described in the "Create a backup" topic.

Step 3

Install Catalyst Center 3.1.5 or later on your appliance.

See the Cisco Catalyst Center Installation Guide.

Step 4

Add the NFS server using the same location that was configured for Catalyst Center 3.1.3.

In the Cisco Catalyst Center Administrator Guide, complete the steps described in the "Add the NFS server" topic.

Step 5

Restore the backup you created in Step 2.

In the Cisco Catalyst Center Administrator Guide, complete the steps described in the "Restore data from backups" topic.

Scenario 5: Migrate data from one Catalyst Center appliance to another

Complete these steps to migrate data from an appliance (running Catalyst Center 2.3.7.x) to another Catalyst Center appliance (running Catalyst Center version 3.1.x).

 Note
  • If you are using the same IP addressing scheme on your Catalyst Center 3.1.3 appliance, shut down the Catalyst Center 2.3.7.x appliance before you start up the Catalyst Center 3.1.3 appliance to prevent IP conflicts.
  • Ensure that you have a DN2 or DN3 appliance running Catalyst Center 3.1.3with the same packages that are installed on your current 2.3.7.x appliance.
  • You can migrate data to an appliance with either the same or bigger profile. For example, you can migrate data from a medium appliance to another medium appliance or a large appliance.
  • Don't migrate data to an appliance with a smaller profile. For example, don't migrate data from an extra large appliance to a large appliance.

Step 1

Ensure that Catalyst Center 2.3.7.x (version 2.3.7.7 or later) is installed on your appliance.

Step 2

Back up your appliance's Assurance (optional) and automation data. In the Cisco Catalyst Center Administrator Guide, complete the steps described in these topics:

  1. "Configure backup servers"

  2. "Back up data now"

Step 3

From the Cisco software download site, download the relevant CatC_2.3.7.x-VA_MigrationScript_v3.tar.gz (which includes the CatC-2.3.7.x-VA_MigrationScript_v3.sh script) to your NFS server.

Step 4

Extract the .tar file and then copy CatC-2.3.7.x-VA_MigrationScript_v3.sh to your NFS server.

Step 5

Grant execute permission to the script by entering the chmod +x CatC-2.3.7.x-VA_MigrationScript_v3.sh command. (Replace 2.3.7.x with your specific version.)

Step 6

After the backup completes successfully, open an SSH console on your NFS server and enter these commands:

  • export LOCAL_BACKUP_DIR=NFS-server-path (path to the server where your appliance's Assurance data is backed up)
  • export REMOTE_SERVER_DIR=remote-server-path (path to the server where your appliance's automation data is backed up)
  • export REMOTE_SERVER_IP=automation-backup-server's-IP-address
  • export REMOTE_SERVER_PORT=22
  • export REMOTE_SERVER_USERNAME=remote-server-username
  • export REMOTE_SERVER_PASSWORD=remote-server-password

Step 7

Start the script by entering the ./CatC-2.3.7.x-VA_MigrationScript_v3.sh command. (Replace 2.3.7.x with your specific version.)

The script does two things:

  1. It creates a copy of the automation data backup file that resides on the remote server and places it on the NFS server.
  2. On the NFS server, it applies the latest Catalyst Center platform format to all backed-up data.

Step 8

After the script runs successfully, enter this command: unset REMOTE_SERVER_PASSWORD

Step 9

Configure the NFS server that the Catalyst Center 3.1.3 appliance will use:

  1. Log in to the Catalyst Center 3.1.3 appliance.

  2. In the Cisco Catalyst Center Administrator Guide, complete the steps described in the "Add the NFS server" topic.

    Enter the same NFS server IP address or hostname and path that you entered when completing Step 2.

Step 10

Restore the backup file that you created in Step 2.

In the Cisco Catalyst Center Administrator Guide, complete the steps described in the "Restore data from backups" topic. Enter the same encryption passphrase that you entered when completing Step 2.

After the restore operation completes, the automation and Assurance data from the physical appliance (first, second, or third-generation) migrate to the virtual appliance.

Scenario 6: Upgrade from a physical appliance to a virtual appliance

In this scenario, you are migrating your existing network data from a physical Catalyst Center appliance to a virtual appliance running Catalyst Center 3.1.5 or later on ESXi.

 Note
  • Catalyst Center only supports the migration of data from a single-node medium appliance to a Catalyst Center on ESXi virtual appliance.
  • The Catalyst Center on ESXi virtual appliance must have a different IP address than its source physical appliance.

Before you begin

  • Configure a virtual appliance running Catalyst Center 3.1.5 or later on ESXi. See the Cisco Catalyst Center 3.1.x on ESXi Deployment Guide.
  • Ensure that a backup server is configured for automation data, and that an NFS server is configured for Assurance data. NFS is mandatory for the migration of backup files from physical Catalyst Center appliances.

Step 1

Start the Catalyst Center 3.1.x upgrade wizard:

  1. From the main menu, choose System > Catalyst Center 3.1.x Upgrade.

  2. Click Get started.

Step 2

Complete the Catalyst Center 3.1.x upgrade wizard:

  1. In the Source Catalyst Center authentication page, enter the following information and then click Next:

    • The source cluster's IP address
    • The cluster's login credentials

    Catalyst Center displays a message if it cannot verify the security certificate that your cluster uses.

  2. If you want to proceed, click Confirm to close the message.

    The wizard then retrieves information from your source cluster, such as its configured NFS server and FQDN.

     Note
    If the wizard flags any information it can’t retrieve, click the Retry retrieving all details link.

  3. Click Next.

    The Server authentication page opens.

  4. Enter the following information, then click Next:

    • In the Outgoing proxy details section, your proxy server's login credentials.
    • In the Remote host details section, the password for automation backup and restore operations.
       Note

      By default, the VIPs and FQDN that are configured for your deployment are grayed out. These settings are not carried over, so you'll need to configure them after the upgrade.

    The Cisco IMC details page opens.

  5. Enter the IP address for your cluster’s Cisco IMC, as well as its login credentials. Then click Next.

     Note

    Catalyst Center displays a message if it cannot verify the security certificate that your cluster uses. If you want to proceed, click Confirm to close the message.

  6. In the Backup selection page, select the backup file you want to use for the upgrade and then click Next.

     Note
    • The latest full backup that's available is already selected by default.
    • If you want to retrieve the latest information for your source cluster, click Refresh.

  7. Enter the backup's encryption passphrase, then click Proceed.

  8. In the Notifications page, specify whether you want to receive status update emails during the upgrade:

    If...

    Then...

    you want to receive status update emails,
    1. Click the Yes radio button. The Primary SMTP Configuration area displays the current settings for your primary STMP server. If these settings have not been configured already, enter them now.
    2. (Optional) Click Edit to make changes to your primary SMTP server's settings.
    3. (Optional) In the Secondary SMTP Configuration area, enter the settings for your secondary SMTP server.
    4. In the Receiver's email(s) Configuration area, enter the addresses that should receive status updates.
    5. (Optional) Click Test mail to check whether the addresses you just specified receive a message.
    6. Click Next.

    you do not want to receive status update emails,

    click the No radio button and then click Next.

  9. In the Summary page, review the settings you entered while completing the wizard:

    If...

    Then...

    the settings displayed are correct,

    click Next.

    any of these settings are missing,

    click Refresh and confirm whether the settings you entered are now displayed.

    any of these settings are incorrect,
    1. Click Back to return to the relevant wizard page.
    2. Make the necessary changes and return to the Summary page.

    Catalyst Center performs multiple prechecks and flags any items that may require attention. Catalyst Center will not allow you to proceed if it detects any critical errors.

Step 3

Start the Catalyst Center 3.1.x upgrade.

  1. Confirm that you want to go ahead with the upgrade:

    If...

    Then...

    no items are flagged,

    click Proceed, then click Proceed again.

    items that don't require immediate attention are flagged,
    1. Click Ignore and proceed. A dialog box opens with more details on flagged items.
    2. Confirm that you want to go ahead with the upgrade without addressing these items by clicking Proceed.

    items that must be addressed before starting the upgrade are flagged,

    take care of these items before returning to this wizard page.

    After Catalyst Center completes these tasks, the Cluster Migration dialog box opens.

     Note

    This is the last point where you can back out of the upgrade. Only continue if you are ready to upgrade.

  2. Click Proceed.

    The backup configuration (both automation and Assurance/NFS) for your physical Catalyst Center appliance is removed. The appliance is powered down, and the upgrade begins. You can monitor the upgrade's progress as it completes.

     Note

    During the upgrade, you can cancel the restoration of your backup file by clicking Cancel Operation.

  3. After the upgrade completes, click No, exit to finalize the upgrade.

Scenario 7: Upgrade Catalyst Center on ESXi

In this scenario, you are upgrading your Catalyst Center 2.3.7.x on ESXi deployment to Catalyst Center on ESXi version 3.1.5 or later.

Step 1

Back up your Catalyst Center 2.3.7.x on ESXi deployment.

In the Cisco Catalyst Center Administrator Guide, complete the steps described in the "Back up data now" topic.

Step 2

Shut down Catalyst Center 2.3.7.x on ESXi.

Step 3

Configure a new Catalyst Center on ESXi virtual appliance (version 3.1.5 or later) with the same network settings as your previous virtual appliance.

See the Cisco Catalyst Center 3.1.x on ESXi Deployment Guide.

Step 4

Configure the physical disk or NFS server that will be used for backup and restore operations.

If...

Then...

you want to configure a physical disk,

refer to the Cisco Catalyst Center Administrator Guide and complete the steps described in these topics:

  • Add a physical disk for backup and restore
  • Configure the location to store backup files (when completing Step 3, choose the Physical Disk radio button)

you want to configure an NFS server,

enter the same NFS settings you used for Catalyst Center 2.3.7.x on ESXi.

In the Cisco Catalyst Center Administrator Guide, complete the steps described in these topics:

  • Add the NFS server
  • Configure the location to store backup files (when completing Step 3, choose the Network File System (NFS) radio button)

Step 5

Restore the backup you created in Step 1.

In the Cisco Catalyst Center Administrator Guide, complete the steps described in the "Restore data from backups" topic.

Scenario 8: Upgrade Catalyst Center on AWS

In this scenario, you are upgrading your Catalyst Center 2.3.7.x on AWS deployment to Catalyst Center on AWS version 3.1.5 or later.

Before you begin

  • Ensure that a backup server is configured for automation data, and that an NFS server is configured for Assurance data. NFS is mandatory for the migration of backup files from physical Catalyst Center appliances.
  • If you are using the same IP addressing scheme on your Catalyst Center 3.1.x appliance, shut down the Catalyst Center 2.3.7.x appliance before you start up the Catalyst Center 3.1.x appliance to prevent IP conflicts.

Step 1

Ensure that Catalyst Center 2.3.7.x (version 2.3.7.7 or later) is installed on your Catalyst Center on AWS deployment.

Step 2

Back up your appliance's Assurance (optional) and automation data. In the Cisco Catalyst Center Administrator Guide, complete the steps described in these topics:

  1. "Configure backup servers"

  2. "Back up data now"

Step 3

From the Cisco software download site, download the relevant CatC_2.3.7.x-VA_MigrationScript_v3.tar.gz (which includes the CatC-2.3.7.x-VA_MigrationScript_v3.sh script) to your NFS server.

Step 4

Extract the .tar file and then copy CatC-2.3.7.x-VA_MigrationScript_v3.sh to your NFS server.

Step 5

Grant execute permission to the script by entering the chmod +x CatC-2.3.7.x-VA_MigrationScript_v3.sh command. (Replace 2.3.7.x with your specific version.)

Step 6

After the backup completes successfully, open an SSH console on your NFS server and enter these commands:

  • export LOCAL_BACKUP_DIR=NFS-server-path (path to the server where your appliance's Assurance data is backed up)
  • export REMOTE_SERVER_DIR=remote-server-path (path to the server where your appliance's automation data is backed up)
  • export REMOTE_SERVER_IP=automation-backup-server's-IP-address
  • export REMOTE_SERVER_PORT=22
  • export REMOTE_SERVER_USERNAME=remote-server-username
  • export REMOTE_SERVER_PASSWORD=remote-server-password

Step 7

Start the script by entering the ./CatC-2.3.7.x-VA_MigrationScript_v3.sh command. (Replace 2.3.7.x with your specific version.)

The script does two things:

  1. It creates a copy of the automation data backup file that resides on the remote server and places it on the NFS server.
  2. On the NFS server, it applies the latest Catalyst Center platform format to all backed-up data.
 Note

After starting the script, you may see an error indicating that some items are missing. Install these items, and then restart the script.

Step 8

From the list of available backups, select the backup you want to migrate.

Step 9

After the script runs successfully, enter this command: unset REMOTE_SERVER_PASSWORD

Step 10

Configure the NFS server that the Catalyst Center3.1.x appliance will use:

  1. Log in to the Catalyst Center 3.1.x appliance.

  2. In the Cisco Catalyst Center Administrator Guide, complete the steps described in the "Add the NFS server" topic.

    Enter the same NFS server IP address or hostname and path that you entered when completing Step 2.

Step 11

Restore the backup file that you created in Step 2.

In the Cisco Catalyst Center Administrator Guide, complete the steps described in the "Restore data from backups" topic. Enter the same encryption passphrase that you entered when completing Step 2.

After the restore operation completes, verify that your system is functioning properly. Also confirm that all services are running in the System 360 page (System > System 360).

Scenario 9: Upgrade Catalyst Center on Azure

In this scenario, you are upgrading Catalyst Center 2.3.7.x to Catalyst Center on Azure version 3.1.5 or later.

Before you begin

  • Ensure that a backup server is configured for automation data, and that an NFS server is configured for Assurance data. NFS is mandatory for the migration of backup files from physical Catalyst Center appliances.
  • If you are using the same IP addressing scheme on your Catalyst Center 3.1.x appliance, shut down the Catalyst Center 2.3.7.x appliance before you start up the Catalyst Center 3.1.x appliance to prevent IP conflicts.

Step 1

Ensure that Catalyst Center 3.1.x (version 3.1.5 or later) is installed on your Catalyst Center on Azure deployment.

Step 2

Back up your appliance's Assurance (optional) and automation data. In the Cisco Catalyst Center Administrator Guide, complete the steps described in these topics:

  1. "Configure backup servers"

  2. "Back up data now"

Step 3

From the Cisco software download site, download the relevant CatC_2.3.7.x-VA_MigrationScript_v3.tar.gz (which includes the CatC-2.3.7.x-VA_MigrationScript_v3.sh script) to your NFS server.

Step 4

Extract the .tar file and then copy CatC-2.3.7.x-VA_MigrationScript_v3.sh to your NFS server.

Step 5

Grant execute permission to the script by entering the chmod +x CatC-2.3.7.x-VA_MigrationScript_v3.sh command. (Replace 2.3.7.x with your specific version.)

Step 6

After the backup completes successfully, open an SSH console on your NFS server and enter these commands:

  • export LOCAL_BACKUP_DIR=NFS-server-path (path to the server where your appliance's Assurance data is backed up)
  • export REMOTE_SERVER_DIR=remote-server-path (path to the server where your appliance's automation data is backed up)
  • export REMOTE_SERVER_IP=automation-backup-server's-IP-address
  • export REMOTE_SERVER_PORT=22
  • export REMOTE_SERVER_USERNAME=remote-server-username
  • export REMOTE_SERVER_PASSWORD=remote-server-password

Step 7

Start the script by entering the ./CatC-2.3.7.x-VA_MigrationScript_v3.sh command. (Replace 2.3.7.x with your specific version.)

The script does two things:

  1. It creates a copy of the automation data backup file that resides on the remote server and places it on the NFS server.
  2. On the NFS server, it applies the latest Catalyst Center platform format to all backed-up data.

After starting the script, you may see an error indicating that some items are missing. Install these items, and then restart the script.

Step 8

After the script runs successfully, enter this command: unset REMOTE_SERVER_PASSWORD

Step 9

Configure the NFS server that the Catalyst Center 3.1.x appliance will use:

  1. Log in to the Catalyst Center 3.1.x appliance.

  2. In the Cisco Catalyst Center Administrator Guide, complete the steps described in the "Add the NFS server" topic.

    Enter the same NFS server IP address or hostname and path that you entered when completing Step 2.

Step 10

Restore the backup file that you created in Step 2.

In the Cisco Catalyst Center Administrator Guide, complete the steps described in the "Restore data from backups" topic. Enter the same encryption passphrase that you entered when completing Step 2.

After the restore operation completes, verify that your system is functioning properly. Also confirm that all services are running in the System 360 page (System > System 360).

Troubleshoot upgrade issues

This topic describes the issues you may encounter while completing the 3.1.x platform upgrade workflow and how to resolve them.

Unsupported Catalyst Center appliances and features

First-generation (DN1) appliances

Issue: The 3.1.x platform upgrade does not support first-generation (DN1) Catalyst Center appliances.

Resolution: Complete the steps described in Scenario 5: Migrate data from one Catalyst Center appliance to another.

IPSEC-enabled HA clusters

Issue: The 3.1.x platform upgrade does not support High Availability (HA) clusters with IPSEC enabled.

Resolution: Complete the steps described in Scenario 5: Migrate data from one Catalyst Center appliance to another.

IPv6-enabled appliance

Issue: You are unable to upgrade a Catalyst Center appliance that has IPv6 enabled.

Resolution: Complete the steps described in Scenario 5: Migrate data from one Catalyst Center appliance to another.

Backup readiness issues

Remote backup server is not configured

Issue: The remote host for automation backups has not been configured.

Resolution:

  1. From the main menu, choose System > Backup & Restore.
  2. Select Configure.
  3. Enter the information for the remote host you will use to store backups. In the Cisco Catalyst Center Administrator Guide, Release 2.3.7.x, refer to the “Backup Server Requirements” and “Configure Backup Servers” topics.

Insufficient disk space on backup server

Issue: The amount of automation data you need to back up is larger than what can fit in a local backup.

Resolution: Contact the Cisco TAC for assistance.

Appliance/Cisco IMC issues

Invalid CIMC Credentials

Issue: You see an invalid credentials error.

Resolution: Confirm that you have entered the correct Cisco IMC credentials.

Invalid CIMC IP address

Issue: The Cisco IMC IP address you specified does not match the IP address of the Catalyst Center appliance you are upgrading to the 3.1.x platform.

Resolution: Verify that the Cisco IMC IP address you provided is correct and reachable.

Non-admin role CIMC user

Issue: You specified a non-admin Cisco IMC user.

Resolution: Specify a Cisco IMC user configured with the admin role. This is a requirement for the 3.1.x platform upgrade.

Connectivity to CIMC

If cannot reach Cisco IMC, check these items:

  • Confirm that you configured the correct Cisco IMC address for your Catalyst Center appliance.
  • If IP filtering is enabled, either disable it or add an IP address that Catalyst Center can reach in the allowed list:
    1. Log in to Cisco IMC.
    2. Select Admin > Network > Network Security.
    3. Uncheck Enable IP Filtering.
  • If SSH is disabled, enable it as it is required:
    1. Select Admin > Communication Services.
    2. Check SSH Enabled.
  • Ensure that the LDAP server is reachable. If multiple LDAP servers are configured:
    1. Log in to Cisco IMC.
    2. Select Admin > User Management > LDAP.
    3. Set a timeout value of 20 seconds. For example, if two LDAP servers are configured and one or both of these servers are unavailable, the login will fall back to local Cisco IMC users within 60 seconds.

Configured interface is physically disconnected

Issue: If you see this message, it indicates that Catalyst Center's cluster interface is not connected. All configured interfaces must be in the UP state and physically connected for the 3.x platform upgrade to proceed.

Resolution: Check or replace the physical connector or cable for the reported interface.

General issues

Email Notifications

Issue: An SMTP connection failure occurred after sending a test notification email.

Resolution: In the 3.1.x platform upgrade wizard’s Notifications page, confirm that you entered the correct SMTP settings.

Fallback options

This topic describes the options that are available if you completed the Catalyst Center 3.1.x upgrade and find yourself in one of these situations:

  • You need to delay your deployment's upgrade to Catalyst Center 3.1.x.
  • You experienced a catastrophic failure that requires a reimage of your Catalyst Center appliance.

Option 1 (recommended): Proceed with the Catalyst Center 3.1.x upgrade

To continue using the new platform, complete these steps:

  1. Install Catalyst Center or later.
  2. Restore the transformed backup file. Specify the NFS directory location in its NFS backup configuration.

Option 2: Revert back to Catalyst Center 2.3.7.x

To revert back to Catalyst Center 2.3.7.x, which runs on the previous platform, you'll need to complete these tasks:

  1. Reimage your appliance, installing the Catalyst Center 2.3.7.x version that was installed previously.
  2. Revert your backup file to the same Catalyst Center 2.3.7.x version.

For assistance, contact the Cisco TAC.