Enhanced Infrastructure Analytics with new indicators

Using the Infrastructure Analytics in Citrix ADM, you could monitor Citrix ADC instance scores by correlating multiple data sources. You can now view new indicators in Infrastructure Analytics to enrich the Citrix ADC instance score. These new indicators also help the administrators to quickly identify the root cause analysis of issues.

Note

Rule indicators are not supported for:

  • Citrix ADC instances configured in a cluster mode.

  • Citrix ADC instances configured with admin partitions.

In Citrix ADM, navigate to Networks > Infrastructure Analytics to view indicators for:

  • Port allocation failure

    Detects when Citrix ADC uses SNIP to communicate with a new server connection and total ports available on that SNIP are exhausted.

    The recommended action is to add another SNIP in the same subnet.

  • Session Buildup

    Detects when Citrix ADC memory is held up by SSL sessions.

  • No default route configuration

    Detects when the traffic gets dropped because of non-availability of routes.

  • IP conflict

    Detects if same IP address is configured or applied on two or more instances in a network.

  • VRID conflict

    Detects when there is VRID conflict and raises alert to administrator that there are intermittent access problems for the specified VRID.

  • VLAN mismatch

    Detects if there are any errors during VLAN configuration that are bound to IP subnets.

  • TCP small window attack

    Detects when there is a possible small window attack in progress. This alert is just for informational, because ADC already mitigates this attack.

  • Rate control threshold

    Detects when packets are dropped based on the configured rate control threshold.

  • Persistence Limit

    Detects when there are maximum hits imposed on the Citrix ADC memory.

  • GSLB site name mismatch

    Detects when there are GSLB configuration synchronization failures because of site name mismatch.

  • Malformed IP header

    Detects when sanity checks on IPv4 packets are failed.

  • Bad L4 checksums

    Detects when checksum validation for TCP packets is failed.

  • Increased CPU usage due to IP move

    Detects if there is a large number of macs to be updated.

  • Excessive packet steering

    Detects high levels of software packet steering due to the usage of asymmetric rss key type.

  • Layer 2 loop

    Detects the presence of layer 2 loops in the network.

  • Tagged VLAN mismatch

    Detects tagged VLAN packets received on an untagged interface.

    Intelligent-infra-analytics

Tabular view

You can also view anomalies using the tabular view option in Infrastructure Analytics. Navigate to Networks > Infrastructure Analytics and then click tabular-view to display all managed instances. Click Expand to expand for details.

Tabular-details

View details of an anomaly

For example, if you want to view details for IP address conflict in the network, click the anomaly that is displayed for IP address conflict to view the details.

Anamoly details

  • Details - Indicates what anomaly is detected

  • Detection Message - Indicates the MAC address for which the IP address has the conflict

  • Recommendations - Indicates the action item to resolve this IP address conflict

Enhanced Infrastructure Analytics with new indicators