Release Notes for Citrix ADM 13.1-17.42 Release 编辑

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

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

Management and Monitoring

ADM support for BLX cluster

You can now add the BLX cluster in ADM. In the ADM GUI, the Cluster IP address (CLIP) is added and the count of the cluster nodes is now visible in the dashboard.

[NSADM-78588]

Improvements to handle broken DB streaming channel issues

In a high availability deployment setup, whenever there is a streaming replication error, Citrix ADM automatically detects that the DB streaming channel is broken, and the DB sync is triggered automatically in the background. The recovery of the broken DB streaming channel happens once every 24 hours. A user can also manually synchronize the database from the GUI using the Sync database button. The configuration files are synchronized automatically from the primary node to the secondary node and the self-replication of the database happens. You can view the progress of the database synchronization by clicking the View Logs button under Settings > Deployment.

[NSADM-71053]

Manage ADC instances in a GSLB cluster

Sometimes, in a GSLB cluster, the configuration objects of the ADC instances try to overwrite each other. And, it leads to a race condition. To address such issues, you need to control the master node selection in the GSLB cluster. The configuration in the master node will be applied to the remaining ADC instances. In Citrix ADM, you can now create a GSLB cluster group and add ADC instances. You can also select a master node among the ADC instances and set the priority order for master node selection.

Under Network Functions > GSLB, a user can now view only the entities from the master ADC node.

[NSADM-61374]

Security

IPv6 support in bot insight

When you drill down an application under Bot in Security > Security Violations > Application Overview, the Logs now display the IPv6 address for the Client IP and Bot True Client IP.

[NSADM-77376]

View analytics for Content Switching virtual server bound to Load Balancing virtual server

In Security > Security Violations, the Application Overview tab now displays analytics for content switching virtual server that is bound with load balancing virtual servers. Click the content switching virtual server and under Bound Load Balancing Server, you can view the list of load balancing servers bound to the content switching virtual server.

[NSADM-77369]

A unified process to enable analytics on virtual servers

Apart from the existing process to enable analytics, you can now use a single-pane workflow to configure analytics on:

• All the existing licensed virtual servers
• The subsequent licensed virtual servers

After configuration, this feature eliminates the necessity to manually enable analytics on the existing and subsequent virtual servers.

For more information, see A unified process to enable analytics.

[NSADM-74747]

Security violation - JSON SQL Injection Grammar

In Security > Security Violations, under WAF, you can now view the JSON SQL Injection Grammar violation for the selected application. For more information, see /wiki/citrix/en-us/citrix-application-delivery-management-service/analytics/security/application-overview.html.

[NSADM-62909]

StyleBooks

StyleBooks support nested parameter-conditions

In a StyleBook definition, you can now specify a parameter condition within a parameter condition. These conditions are called nested parameter conditions and use a repeat construct to define these conditions. The nested parameter conditions are useful when you want to apply an action to each item of a list parameter.Example:

parameters-conditions:
  -
    repeat: $parameters.lbvservers
    repeat-item: lbvserver
    parameters-conditions:
      -
        target: $lbvserver.port
        action: set-allowed-values
        condition: $lbvserver.protocol == "HTTPS"
        value: $parameters.ssl-ports
<!--NeedCopy-->