Upgrading

Upgrade the product to the current version.
cavna37
If you have
DX NetOps Performance Management
, to upgrade
DX NetOps Virtual Network Assurance
(VNA), use the following upgrade path. If you have
DX NetOps Spectrum
, see the
DX NetOps Spectrum
documentation
.
If you have the Cisco Application Centric Infrastructure (ACI) plug-in configured, when you upgrade to 3.7.8 and higher, the previously set values for fault-codes, fault-types, and fault-severities are cleared. The faults are whitelisted and saved in the database. To prevent this, stop the WildFly service within 5 minutes of the upgrade and configure the filters as needed.
For more information about this plug-in, see Cisco ACI.
Verify the Prerequisites
Verify the following prerequisites before you upgrade
DX NetOps Virtual Network Assurance
:
  • Verify whether the
    numactl
    package is installed on the VNA host:
    rpm -qa | grep ^numactl
    If the required package is missing, install the package:
    If you are not the root user, use the sudo prefix.
    yum -y install numactl
  • Before you upgrade, back up the database.
    For more information, see Back Up and Restore.
Review Plug-in Configurations
During the VNA upgrade, your plug-in inventory and configurations are maintained. You can review your plug-in configurations by querying the following REST URL.
For more information, see Building.
Follow these steps:
  1. Query the following REST URL to find the engine ID:
    http://
    VNA_host
    :8080/vna/rest/v1/admin/engines
  2. Query the following REST URL for your plug-in configuration:
    http://
    VNA_host
    :8080/vna/rest/v1/admin/engines/
    Engine_ID
    /config
  3. Review the response.
    Example:
    {
    "AVAILABILITY_DELTA_TIME": "300",
    "AVAILABILITY_POLL_RATE": "0 */5 *",
    "DOMAIN_ID": "1",
    "INVENTORY_DELTA_TIME": "600",
    "INVENTORY_POLL_RATE": "0 */10 *",
    "PERFORMANCE_DELTA_TIME": "300",
    "PERFORMANCE_POLL_RATE": "0 */5 *",
    "PROTOCOL": "https",
    "VCENTER_IP": "10.241.16.37",
    "VCENTER_PASSWORD": "****",
    "VCENTER_USER_NAME": "[email protected]"
    }
    Passwords in the response are always encrypted.
Upgrade
DX NetOps Virtual Network Assurance
to a Custom Directory
From VNA 3.6.6, you can move existing VNA instance to a custom directory.
Do not delete the VNA server from the
DX NetOps Spectrum
OneClick admin page or from
NetOps Portal
.
Migrate
DX NetOps Virtual Network Assurance
and MySQL Data
When you upgrade to current VNA version, you back up the VNA and MySQL data. You can import them post upgrade to the new installation location.
Follow these steps:
  1. On the VNA server, copy the latest VNA version (3.6.6 or higher).
  2. Stop WildFly by issuing one of the following commands:
    service wildfly stop
    or
    systemctl stop wildfly
    Back up the Current CA VNA
  3. To back up your current VNA instance, execute the following commands:
    mkdir -p /<backup_directory>/db
    mkdir -p /<backup_directory>/collector
    mkdir -p /<backup_directory>/data
    /opt/CA/VNA/tools/bin/db_backup.sh /<backup_directory>/db/vna_backup
    cp -r /opt/CA/VNA/data/* /<backup_directory>/data/
    cp -r /opt/CA/VNA/collector/* /<backup_directory>/collector/
  4. Uninstall VNA using the
    /opt/CA/VNA/tools/bin/uninstall_vna.sh
    command.
Install
DX NetOps Virtual Network Assurance
in a New Location and Restore the Data
This section describes the steps to install the VNA on a custom directory and restore the old data from the
/opt/CA/VNA
directory.
Follow these steps:
  1. Install VNA 3.6.6 or higher from the copied installer.
  2. Enter a custom installation path.
    Follow the installation wizard and complete the installation.
  3. After the installation, note the owner of
    <new_vna_directory>/data
    and
    <new_vna_directory>/collector
    directories.
    By default
    wildfly
    is the owner.
  4. Note the owner & group of
    <new_vna_directory>/data/ID_CACHE>dat
    file.
    By default
    wildfly:wildfly
    is the owner and group name.
  5. (Optional) For a VNA Aggregator, note the owner and group of
    <new_vna_directory>/REMOTE_ID_CACHE.dat
    file.
    By default
    wildfly:wildfly
    is the owner and group name.
  6. Restore the database using the
    /<new_install_directory>/VNA/tools/bin/db_restore.sh /<backup_directory>/db/vna_backup
    command.
  7. Stop the existing VNA instance using the,
    service wildfly stop
    or
    systemctl stop wildfly
    command.
  8. Restore the files using the following commands:
    cp -r /<backup_directory>/data/* /root/CA/VNA/data/
    cp -r /<backup_directory>/collector/* /root/CA/VNA/collector/
  9. Issue the
    chown
    command to restore the owner and group of restored data files.
  10. Start VNA by issuing the
    service wildfly start
    command.
  11. Log in to VNA Swagger UI: http://
    VNA_host
    :8080/vna
  12. Update the existing plug-in.
Upgrade
DX NetOps Virtual Network Assurance
on Existing Directory
Follow these steps:
  1. In
    NetOps Portal
    , hover over
    Administration
    , and click
    Monitored Items Management: VNA Gateways
    .
  2. Select the active VNA Gateway, and then click
    Edit
    .
  3. Set
    Administrative Status
    to
    Down
    , and then click
    Save
    .
  4. Upgrade
    DX NetOps Performance Management
    .
  5. Install the new
    DX NetOps Virtual Network Assurance
    version.
    For more information, see Installing.
    The plug-in inventory and configurations are maintained.
  6. Complete prompts for all new plug-in parameters.
  7. Wait for a single polling cycle to complete.
  8. In
    NetOps Portal
    , for the VNA Gateway, set
    Administrative Status
    to
    Up
    .
    You can find the
    CA_Virtual_Network_Assurance_install_dd_mm_yyyy_hh_mm_ss.log
    installation log in the 
    /opt/CA/VNA/logs
    directory.