Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell EMC Avamar for VMware 19.7 User Guide

PDF

Best practices and troubleshooting for applying security patch updates to proxies

Review the following items before you apply a security update patch to a proxy:

Best practices

  • Security updates are only supported for proxies that are managed by the Proxy Deployment Manager. For a manually deployed proxy, use the initproxyappliace.sh option to register a manually deployed proxy with the Proxy Deployment Manager. Older versions of Avamar do not support this form of patching.
  • Avamar 19.3 and later, adds support for the package installation tracking feature. Proxy installations from previous releases are not traceable. Dell EMC recommends that you deploy or update proxies to the most recent version by using the proxy upgrade functionality in the Proxy Deployment Manager.
  • If you update the VAMI or the registered VAMI service (AVAMAR provider: AvamarVMwareCombined-CIM-linux-sles12sp1-x86_64-version.rpm), ensure that you manually restart the vami-sfcb service on the proxy.

Troubleshooting

  • The patch install log resides on the proxy at /tmp/patch.log.

    If the installation fails, the proxy fetches the log content and displays the content in the AUI.

  • The install patch tracking log resides at /usr/local/avamarclient/var/patchinstall.log.

  • The install script does not reside on the proxy. If you need to modify this script for troubleshooting purposes, you can find the scripts at the following locations:

    • For the hotfix RPM, the script resides on the Avamar server at /usr/local/avamar/var/vcs/dm/installpatch.sh.
    • For the patch TGZ, the sec_rollup_proxy_install.sh script resides inside the TGZ package.

    The uploaded patch is saved in the Avamar server at /usr/local/avamar/var/vcs/dm/patches.

  • To troubleshoot the CIM service, create a new empty file at /tmp/CIM.log. The CIM service writes the log entry to this file.

  • You can change the upload file size limit by modifying the following lines in the MC REST API service .yaml file: 

    http: 
multipart:
max-file-size:50000MB
max-request-size:500000MB

  • If a proxy virtual machine was deleted or powered off from a VMware-side application such as the vSphere Client, the proxy is removed from the Proxy Deployment tab in the AUI Proxy Deployment Manager window. However, the proxy list in the Proxy Patches tab still lists the proxy.

    Clicking this proxy returns an HTTP 500 error that indicates No route to host (Host unreachable). If you encounter this issue, verify whether the proxy is temporarily unavailable or if the proxy has been permanently removed:

    • If the proxy is temporarily unavailable, power ON the proxy virtual machine, and then retry the operation in the Proxy Deployment Manager.
    • If the proxy has been permanently deleted, use the Asset Management window in the AUI to remove the proxy, and then retry the operation in the Proxy Deployment Manager.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\