eG Monitoring
 

Measures reported by CtxXcXDZoneTest

Deployments that span widely-dispersed locations connected by a WAN can face challenges due to network latency and reliability. One of the means by which these challenges can be mitigated is by configuring zones. Zones can help users in remote regions connect to resources without necessarily forcing their connections to traverse large segments of the WAN. In other words, zones connect users to resources that are closest to them, keeping traffic ‘local’. Using zones allows effective Site management from a single Citrix Studio console, Citrix Director, and the Site database.

A Site always has one primary zone, which should include the central Site database and at least two Delivery Controllers. It can also optionally have one or more satellite zones, which should include one or more VDAs, Controllers, StoreFront servers, and NetScaler Gateway servers.

When a Delivery Controller in a zone (primary/satellite) fails, another one in the same zone will take over. But how does an administrator determine that a failover has occurred in a primary zone? By executing this test at regular intervals, administrators can be promptly alerted if a controller in primary zone fails over to another controller in the same zone. Additionally, this test also scans each zone configured in a site and reports the number of controllers, delivery groups, and machine catalogs in that zone.

Outputs of the test : One set of results for each zone configured in the Delivery Controller site being monitored

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
is_primary_zone Indicates whether/not this is the primary zone.   The values that this measure reports and their corresponding numeric values are listed in the table below:

Measure Value Numeric Value
Yes 1
No 0

Note:

By default, this measure reports the above-mentioned Measure Values to indicate whether a zone is a primary or a satellite zone. However, in the graph of this measure, the same will be represented using the numeric equivalents.
is_primary_zone_changed Indicates whether/not the state of the primary zone changed during the last measurement period.   This measure will report a value only if the ‘is_primary_zone’ measure reports the value ‘Yes’.

Typically, when a controller in a primary zone fails over to another controller in the same zone in the last measure period, then this measure will report the value Yes. If no failover has occurred in the primary zone between two measure periods, then the value of this measure will be No.

The numeric values that correspond to the measure values discussed above are listed in the table below:

Measure Value Numeric Value
Yes 1
No 0

Note:

By default, this measure reports the above-mentioned Measure Values to indicate whethe/not a failover has occurred in the primary zone. However, in the graph of this measure, the same will be represented using the numeric equivalents.
No_of_controller Indicates the number of controllers in this zone. Number Use the detailed diagnosis to know which controllers are in this zone and when each controller was last started.

No_of_delivery_group Indicates the number of delivery groups in this zone. Number Use the detailed diagnosis of this measure to know which delivery groups are operating in this zone.
No_of_catalog Indicates the number of machine catalogs in this zone. Number Use the detailed diagnosis of this measure to identify the machine catalogs in this zone.