Skip to Content
Information
Space banner This version of the product is in limited support. However, the documentation is available for your convenience. You will not be able to leave comments.

Technical bulletin - Announcing Hotfix 20.02.00.006

Hotfix 20.02.00.006 is now available for TrueSight Network Automation version 20.02. This hotifx includes the new feature for defining the secondary Network Address Translation (NAT) address for devices.

Secondary NAT address for device communication

In a high availability environment, the application server in a secondary location might have a different NAT address for the devices than the primary application server. When failover occurs and the application server is switched over to the secondary server, you are required to update the NAT address of the devices manually to match with the secondary site network.

With this hotfix release, you can define a secondary NAT address (along with the primary NAT address) in advance. In case of failover, you just need to enable the new system parameter, Use Secondary NAT Address For Devices system parameter, to configure the application for the use of primary or secondary NAT address. This parameter minimizes the post failover tasks significantly.

You provide the secondary NAT address while adding a device both for the primary and auxiliary interfaces. The device view page displays the address for both primary and auxiliary interfaces if you have provided the same while adding the device.

Secondary NAT address can be defined and used in the following ways:

  • When importing a device using the Device Import Task – When importing devices in CSV or XML format using the Device Import Task, now you can define the Secondary NAT Address field for both the primary and auxiliary interfaces.
  • When editing multiple devices on the Edit Multiple Devices page – Update the Secondary NAT Address field for both the primary and auxiliary interfaces, if required.
  • When using substitution parameters in templates – Use global substitution parameters, secondary_nat and aux_secondary_nat.
  • When generating the Device Inventory report – Select the Secondary NAT Address and Auxiliary Secondary NAT Address fields under Device Interface. 
  • When attaching the Device Inventory report in the Send Email action – Select the Secondary NAT Address and Auxiliary Secondary NAT Address parameters while attaching the Device Inventory report.

Downloading the hotfix

For download instructions, contact BMC Customer Support.

Applying the hotfix on Windows

Before you apply the hotfix, do the following:

  1. Backup the TrueSight Network Automation database.
  2. Back up <TSNA_INSTALL_DIR>\tomcat\webapps\bca-networks.war outside the <TSNA_INSTALL_DIR>\tomcat\webapps directory.

Do the following to apply the hotfix:

  1. Copy the unzipped war file, bca-networks.war to the TrueSight Network Automation server.
  2. Stop the TrueSight Network Automation web server service.
  3. Copy bca-networks.war from the zip file to <TSNA_INSTALL_DIR>\tomcat\webapps.
  4. Delete the existing bca-networks directory from the <TSNA_INSTALL_DIR>\tomcat\webapps directory. 
    This directory will be recreated after you restart the TrueSight Network Automation web server service in step 6.
  5. Navigate to the <TSNA_INSTALL_DIR>\tools directory and run the following script: upgrade_db.bat
  6. Start the TrueSight Network Automation web server service.

Applying the hotfix on UNIX

Before you apply the hotfix, do the following:

  1. Backup the TrueSight Network Automation database.
  2. Navigate to the <TSNA_INSTALL_DIR>/tomcat/webapps directory and create a copy of the bca-networks.war file using the following command:
    cp bca-networks.war bcan-networks.war.ORIG
  3. Move the bcan-networks.war.ORIG file outside the <TSNA_INSTALL_DIR>/tomcat/webapps directory.

Do the following to apply the hotfix:

  1. Copy the unzipped war file, bca-networks.war to the TrueSight Network Automation server.
  2. Run the following command to stop the TrueSight Network Automation web server service: /etc/init.d/enatomcat stop
  3. Copy bca-networks.war from the zip file to <TSNA_INSTALL_DIR>/tomcat/webapps.
  4. Delete the existing bca-networks directory from the <TSNA_INSTALL_DIR>/tomcat/webapps directory. 
    This directory will be recreated after you restart the TrueSight Network Automation web server service in step 6.
  5. Navigate to the <TSNA_INSTALL_DIR>/tools directory and run the following script: upgrade_db.sh
  6. Run the following command to start the TrueSight Network Automation web server service: /etc/init.d/enatomcat start

Rolling back the hotfix

You can roll back the hotfix if the bca-networks.war file is corrupted or if you face any other issues.

Do the following:

  1. Go to the application server where you have applied the hotfix.
  2. Stop the TrueSight Network Automation web server service.
  3. Copy the bca-networks.war file that you backed up before applying the hotfix.
  4. Navigate to the <TSNA_INSTALL_DIR>\tomcat\webapps directory and replace the existing bca-networks.war file with the backed up file that you copied in the previous step.
  5. Restore the TrueSight Network Automation database.
  6. Start the TrueSight Network Automation web server service.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

TrueSight Network Automation 20.02