Release Notes for Citrix ADM 13.1-33.50 Release 编辑

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

Notes

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-33.50.

Infrastructure

Dual NIC support for ADM agent

You can configure a second NIC on ADM agent to manage access to Citrix ADM. Using the Dual NIC architecture, ADM agent will now be able to:

• Establish communication between ADM agent and ADC instances

• Establish communication between ADM agent and ADM service

For more information, see Dual NIC support on Citrix ADM.

[ NSADM-85781 ]

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 ADM Service.

[ NSADM-85452 ]

StyleBooks

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.

[ NSADM-86253 ]

Fixed Issues

The issues that are addressed in Build 13.1-33.50.

StyleBooks

After you upgrade Citrix ADM to any version (13.1.9.x version - 13.1.30.x version) from any older version, Citrix ADM rolls back the existing ConfigPacks to its earlier version.

[ NSHELP-33127 ]

Analytics

On a Desktop 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.

[ NSHELP-31776 ]

Management and Monitoring

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

[ NSHELP-32606 ]

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.

[ NSHELP-32567 ]

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.

[ NSHELP-32390 ]

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.

[ NSHELP-32328 ]

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

[ NSHELP-32326 ]

When you upgrade Citrix ADM from version 12.X to version 13.X, you cannot access the GUI.

[ NSHELP-32224 ]

When you navigate to Infrastructure>SSL Dashboard>SSL Certificates page, click the Export icon, and download the report in CSV format, the domain information is not exported and appears blank.

[ NSHELP-30767 ]

Known Issues

The issues that exist in release 13.1-33.50.

Management and Monitoring

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

[ NSHELP-32647 ]

In Gateway > HDX Insight, the data is not displayed because of the database corruption.

[ NSHELP-30459 ]

In ADM HA pair, the database status observed to be in Down status and not synchronizing even after trying with Sync Database option in the GUI for several times.

[ NSHELP-29626 ]

Miscellaneous

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.

[ NSHELP-26545 ]

Orchestration

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

[ NSADM-89919 ]