Asset Management Overview

AppViewX’s ADC solution provides a single-pane-of-glass view of complex ADC infrastructure, supporting physical and virtual devices from the industry’s leading ADC providers. It provides application-centric, customizable reports to help monitor application utilization and enable efficient capacity planning on the ADCs. It gives application and operation teams a topology view of the application delivery infrastructure for better visibility of their application. AppViewX can also project better insights into application health, state, status, utilization, and performance of applications from the managed network assets.

The ADC devices are managed/monitored under the following tabs within the Inventory:

  • Device
  • Groups
  • Back-up & Restore

Supported ADC Vendors and Prerequisites

To manage the Application Delivery Controller (ADC) devices on AppViewX, there are certain prerequisites. In the following tables, you can find the prerequisites for the supported vendors.

Prerequisites for Managing A10, AVI, Akamai, and Array
Vendors Supported A10* AVI*** Akamai** Array
Version Supported v2.7.x , v4.0.1, v4.1.x, v5.1.x, and v6.x 16.2.x, 16.3.x, 17.1.x,17.2.x,18.2.x, 20.1.x, 22, 30, 31.x Rel.APV.10.4.2.93
IP Address/FQDN IP address and FQDN
IP address and FQDN
Note: Device should not be added with Cluster IP
 IP address and FQDN
User Privilege CLI/WEB/xapi access and Read/Write access is required
System Admin Role for all tenants.
Note: SuperUser Access is required only to verify terminal check, not mandatory.
 Client token, Client Secret, Access Token, Host URL api access
Enable Password Required Not applicable Not applicable NA
License Check No No Not applicable No
Services and Ports for AppViewX Communication 22, 80, and 443 22, 443, 5514 (To receive syslog on AppViewX from AVI) 443 Outbound access from AppViewX is needed to manage the device and Perform Akamai Actions A port needs to be specified for API access.
Note: Any port no. can be used.
Internet Access/Proxy if Required Not required Not required Not required NA
Location from which Certificates are discovered if managed No specific location No specific location (we use API's to get certificate details) Not applicable NA

Prerequisites for Managing Amazon ELB, BigIQ, Cisco, and Citrix

Vendors Supported Amazon ELB** BigIQ** Cisco ACE** Citrix*
Version Supported Only Classic and Application ELB is supported 5.x (5.2/5.3), 7, 8 5 v9.x, v10.x , V11.x, v12.x, v13.x
IP Address/FQDN Not applicable IP address IP address IP address and FQDN
User Privilege Access Key, Secret Key, and Region information is required. { Role : Admin , tmsh access is required } Username /Password, Credential List AppViewx/CyberArk/Thycotic Username /Password, Credential List AppViewx/CyberArc Username /Password, Credential List AppViewx/CyberAr k Role:(Superuser access)/BeyondTrust
Enable Password Not applicable Not applicable Not applicable Not applicable
License Check Not applicable Yes No No
Services and Ports for AppViewX Communication Port 443, Outbound Internet access is required to manage the ELB in AWS Port 22 SSH Outbound Access from AppViewX is needed for SSH service and HTTPS service

Outbound Access from AppViewX for SSH and HTTPS service (Default/Custom Port Information) is required

Outbound access to port 5514 is required for Citrix Device to forward the syslog to AppViewX
Internet Access/Proxy if Required Required Not applicable Yes, if the needs be accessed with Public IP address. Yes, if the needs be accessed with Public IP address.
Location from which Certificates are discovered if managed Not applicable (Certificates that are assigned to the listeners will be discovered by AppViewX) Certificate Discovery is not supported Certificate Discovery is not supported Certificates are parsed only from the /flash/nsconfig/ssl/ directory
Prerequisites for Managing F5, HAproxy, NginxPlux, and Infoblox LBDN
Vendors Supported F5*** F5XC*** HAProxy* NginxPlux*** Infoblox LBDN**
Version Supported v10.x , v11.x , v12.x , v13.x, v14.x, v15.x, v16.x, v17 NA Open source version: 1.4.x, 1.5.x, 1.6.x, 2.x (Community), 2.x (Enterprise) R11, 18, 19, 20, 21, 22, 23, 24, 25,26, 27, 28, 29, 30, 31 v8.2 and wapi v2.7.1
IP Address/FQDN IP address or FQDN FQDN IP address IP address IP address or FQDN
User Privilege { Role : Admin , bash access is required } Username /Password, Credential List AppViewx/CyberArk/BeyondTrust admin Username /Password, Credential List AppViewx/CyberArc/Thycotic Access to Nginx installed configuration location and access to check syntax of niginx.conf and restart nginx service to apply the changes Superuser or access to LBDN objects that needs to be managed from AppViewX
Enable Password Not applicable NA Not applicable Not applicable Not applicable
License Check Yes No Yes Yes Not applicable
Services and Ports for AppViewX Communication 22 and 443 NA Port 22 SSH 22 and any custom port for stats 443 or custom port to access API calls
Internet Access/Proxy if Required Not applicable Internet access required Not applicable Not applicable Not applicable
Location from which Certificates are discovered if managed

/config/filestore/files_d/<partition>_d/certificate_d/

/etc/httpd/conf/ssl.crt/

/etc/pki/tls/certs/

V10

/config/ssl/ssl.crt/

/etc/httpd/conf/ssl.crt/

/etc/pki/tls/certs

 NA

/config/filestore/fil es_d/_d /certificate_d/ /etc/httpd/conf/ssl. crt/ /etc/pki/tls/certs/

V10

/config/ssl/ssl.crt/ /etc/httpd/conf/ssl. crt/ /etc/pki/tls/certs/

/etc/nginx/conf.d/ or any custom location

 Not applicable
Table 1. Prerequisites for Managing Cloudflare
Vendors Supported Cloudflare**
Version Supported v4
IP Address/FQDN NA
User Privilege Api Token
Note:
When creating a Cloudflare API token for managing load balancing, the following minimum permissions should be granted:Permissions:
  1. Zone-level Permissions: Load Balancing: Read/Edit

    This permission allows the token to manage and modify load balancer configurations within specified zones.

  2. Account-level Permissions: Load Balancing Pools and Monitors: Read/Edit

    This permission enables the token to manage and modify load balancing pools and health monitors within specified accounts.

Resources:

Account Resource: Include the specific account(s) that should be accessible using this token.

Zone Resource: Include all zones where load balancing management is required.
Enable Password NA
License Check NA
Services and Ports for AppViewX Communication Port 443, Outbound Internet access is required to manage the cloudflare
Internet Access/Proxy if Required Required
Location from which Certificates are discovered if managed NA
Note:
  • * - The vendors are supported for certificate management and automation only.
  • ** - The vendors are supported only for automation.
  • *** - The vendors are supported for device/application end-to-end management, certification management, and automation.