Citrix Application Delivery Management

Release Notes for Citrix ADM 13.1–37.38 Release

This release notes document describes the enhancements and changes, fixed and known issues that exist for the Citrix ADM release Build 13.1–37.38.


  • This release notes document does not include security related fixes. For a list of security related fixes and advisories, see the Citrix security bulletin.

What’s New

The enhancements and changes that are available in Build 13.1–37.38.


Preview Instance Advisory details on Citrix ADM

Instance advisory is now available as a preview feature in Citrix ADM with Security and Upgrade advisory details. Citrix ADM performs a version scan on the ADCs to check for CVEs and also to get details on the ADCs that are running the EOM/EOL build.

To get updates on the latest CVEs, custom scans, and workflows to remediate and upgrade, you can select and onboard an ADC instance to ADM Service. For more information, see Instance Advisory.

For information on onboarding an ADC instance in ADM Service, review the GIF animations that are available on the Instance advisory pages.


View usage and license information for unmanaged CICO ADC instances

You can now navigate to Infrastructure > Pooled Licensing > Bandwidth Licenses > CICO to view the usage and license information for unmanaged CICO ADC instances on Citrix ADM.



StyleBooks support Citrix ADC BLX instances

While creating a configuration pack, you can now choose Citrix ADC BLX instances as the target instances. Earlier, StyleBooks supported Citrix ADC MPX, SDX, VPX, and CPX instances.


Fixed Issues

The issues that are addressed in Build 13.1–37.38.


  • On a Citrix Director integrated with Citrix ADM, when you navigate to Trends > Network, the network tab is inaccessible and an error message appears. As part of the fix, you can now access the Network tab without any issues.


Management and Monitoring

  • When Citrix ADM receives the syslog messages from Citrix ADC with a bad URI syntax, the Syslog Messages page in Infrastructure > Event Summary appears blank.


  • Sometimes, the temporary folders of ADM backup files are not deleted from the /var/mps/backup folder.


  • In Infrastructure > Instance > Citrix ADC, when you select an ADC instance and try to configure analytics, throughput of the virtual servers appears as zero. This issue happens only if you add any filters in the search bar.


  • Citrix ADM was not logging the details of HA Force failover command. With this fix, ADM HA Force failover details are logged in an external server before running the command.


  • When you navigate to Infrastructure > Events > Event Settings, chose the category for which you want to configure event severity and then clicked Configure Severity, you were unable to select and assign Information as the new severity level.


  • In the ADM GUI, some SDX SNMP traps are missing because ADM cannot process those traps from SDX appliances.



  • Asymmetric Crypto Units and Symmetric Crypto Units are now editable fields in the Citrix ADM GUI. You can enter the number of ASUs and SCUs while provisioning a Citrix ADC VPX instance on the Citrix ADC SDX appliance with Intel Coleto (COL) chips.

    Navigate to Infrastructure > Instances > Citrix ADC, and on the SDX tab, select an SDX instance where you want to provision a Citrix ADC VPX instance. In Select Action, select Provision VPX and in the page that displays, enter the crypto capacity under Crypto Allocation



  • When you create or update a configuration pack using a StyleBook created in version 13.0 or earlier, an error message “unknown parameters received in payload” appears.


Known Issues

The issues that exist in release 13.1–37.38.


  • When you enable analytics on a virtual server, some required information might be lost between ADC and ADM. As a result, the transaction data becomes invalid and is unavailable on the ADM reports.


Management and Monitoring

  • If you use VMware vMotion to schedule the ADM server migration on an ESXi hypervisor, the database streaming channel on the HA nodes is broken. As a result, you cannot access the ADM GUI.


  • When you configure a second NIC to isolate management access to Citrix ADM, the second NIC IP address is incorrectly assigned the same IP address of the primary NIC.



  • Deleting a load balancing virtual server from OpenStack fails because Citrix ADM does not honor the delete request. This issue persists even after you delete the components bound to the load-balancing virtual server.


Release Notes for Citrix ADM 13.1–37.38 Release