The Citrix Branch Repeater Monitoring Model

eG Enterprise provides a specialized Citrix Branch Repeater monitoring model that periodically checks application links, ICA traffic, QoS thresholds, and service class policies managed by the branch repeater, accurately points administrators to the problem areas – be it slow application links or latencies in processing ICA traffic – and helps them initiate and implement corrective action.

Figure 1 : The layer model of Citrix Branch Repeater

Each layer of Figure 1 above is mapped to a variety of tests, each of which report a wealth of performance information related to the branch repeater. Using these metrics, administrators can find quick and accurate answers to the following performance queries:

Is the branch repeater available over the network?
Was the branch repeater rebooted recently?
How much CPU is the branch repeater consuming?
Is the accelerated application traffic using the link bandwidth optimally? If not, the traffic for which application is consuming bandwidth excessively?
Have too many data packets been dropped due to QoS threshold violations? If so, which application has lost the maximum packets? Do the QoS thresholds for that application require fine-tuning?
How is the load on the branch repeater?
Is the branch repeater able to deliver a high compression ratio?
Have too many connections been left unaccelerated by the branch repeater?
Which ICA application is bandwidth-intensive? How well does the branch repeater accelerate traffic for this ICA application?
Are the service classes configured in the branch repeater regulating traffic well or are WAN links governed by the service classes still consuming too much bandwidth? If so, which service class is an ineffective accelerator? Should that service class's configuration be reset?
Are any WAN/LAN links handling more traffic than the bandwidth limit set for them? If so, which are those links?
Which traffic shaping policies configured in the branch repeater are poor accelerators and require tweaking?