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.
| Vendors Supported | A10* | AVI*** | Akamai** |
|---|---|---|---|
| Version Supported | v2.7.x , v4.0.1, v4.1.x, and v5.1.x |
16.2.x, 16.3.x, 17.1.x,17.2.x,18.2.x, 20.1.x, 22 |
|
| IP Address/FQDN | IP address and FQDN |
IP address and FQDN
Note: Device should not be added with
Cluster IP |
|
| 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. |
|
| Enable Password | Required | Not applicable | Not applicable |
| License Check | No | No | Not applicable |
| 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 |
| Internet Access/Proxy if Required | Not required | Not required | Not required |
| Location from which Certificates are discovered if managed | No specific location | No specific location (we use API's to get certificate details) | Not applicable |
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) | 5 | v9.x, v10.x , V11.x, v12.x, v13.x, v14.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/CyberAr c | Username /Password, Credential List AppViewx/CyberAr k Role:(Superuser access) |
| 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 |
| Vendors Supported | F5*** | HAproxy* | NginxPlux*** | Infoblox LBDN** |
|---|---|---|---|---|
| Version Supported | v10.x , v11.x , v12.x , v13.x, v14.x, v15.x, v16.x,
v17 |
1.4,x, 1.5.x, 1.6.x | R11, 18, 19, 20, 21, 22, 23, 24, 25,26, 27, 28, 29 | v8.2 and wapi v2.7.1 |
| IP Address/FQDN | IP address or FQDN | IP address | IP address | IP address or FQDN |
| User Privilege | { Role : Admin , bash access is required } Username /Password, Credential List AppViewx/CyberArk | 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 | Not applicable | Not applicable | Not applicable |
| License Check | Yes | Yes | Yes | Not applicable |
| Services and Ports for AppViewX Communication | 22 and 443 | 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 | 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 |
/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 |
- * - 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.
