Cisco Catalyst Center Administrator Guide, Release 3.2.x

PDF

Install the witness site

Want to summarize with AI?

Log in

Overview

Information about setting up a virtual machine that serves as the witness site for the disaster recovery system on Catalyst Center.

Complete this procedure to set up the virtual machine to serve as the witness site for your disaster recovery system.

Procedure

1.

Download the OVF package that's specific to the Catalyst Center version that the witness site is running:

  1. Open https://software.cisco.com/download/home/286316341/type.

    Note

    You need a Cisco.com account to access this URL. See the following page for a description of how to create an account: https://www.cisco.com/c/en/us/about/help/registration-benefits-help.html

  2. In the Select a Software Type area, click the Catalyst Center software link.

    The Software Download page updates, listing the software available for the latest Catalyst Center release.

  3. Do one of these:

    • If the OVF package (*.ova) you need is already listed, click its Download icon.

    • Enter the relevant version number in the Search field, click its link in the navigation pane, and then click the Download icon for that version's OVF package.

2.

Copy this package to a local machine running VMware vSphere 7.0 or later.

3.

From the vSphere client, choose File > Deploy OVF Template.

4.

Complete the Deploy OVF Template wizard:

  1. Follow the instructions in the Source screen:

    1. Click Browse.

    2. Navigate to the witness site OVF package (.ova).

    3. Click Open.

    4. In the Deploy from a file or URL field, verify that the package path displays and then click Next.

      The OVF Template Details screen opens.

  2. Click Next >.

  3. Following the instructions in the Name and Location screen:

    • In the Name field, enter the name you want to set for the package.

    • In the Inventory Location field, select the folder that you want the package to reside in.

    • Click Next >.

    The Host/Cluster screen opens.

  4. Click the host or cluster on which you want to run the deployed template and then click Next >.

    The Storage screen opens.

  5. Click the storage drive for the virtual machine files to reside on and then click Next >.

    The Disk Format screen opens.

  6. Click the Thick Provision radio button and then click Next.

  7. Follow the instructions in the Network Mapping screen and then click Next:

    1. Click the IP address that is listed in the Destination Networks column.

    2. In the resulting drop-down list, choose the network that the deployed template should use.

    The Ready to Complete screen opens, displaying all of the settings that you have entered.

  8. Check the Power on after deployment check box and then click Finish.

  9. When the Deployment Completed Successfully dialog box opens, click Close.

5.

Enter the network settings for your witness site:

  1. Open a console to the virtual machine you just created by doing one of these tasks:

    • Right-click the virtual machine from the vSphere Client list and choose Open Console.

    • Click the Open Console icon in the vSphere Client menu.

    The Witness User Configuration window opens.

  2. Enter and confirm the desired password for the admin user (maglev), then press N to proceed.

  3. Enter these settings, then press N to proceed:

    • Its IP address

    • The netmask associated with the virtual machine IP address

    • The IP address of your default gateway

    • (Optional) The IP address of the preferred DNS server

  4. Enter one or more NTP server addresses or hostnames (separated by spaces), then press S to submit your settings and begin the configuration of the witness site.

    At least one NTP address or hostname is required.

  5. Verify that configuration has completed by using SSH port 2222 to log in to the IP address you configured for the witness site.

Note

Later, if you need to change the password configured for the maglev user on the witness site's VM, use the standard Linux passwd utility. You don't need to pause the disaster recovery system before doing this, and the password change will have no functional impact on disaster recovery operation.