Part 1- Repeater App Traffic Counter Group

NetScaler Command Center support for Branch Repeater quick reports has brought a great deal of value to help visualize performance level factors through graphs for multiple BR devices in one page. CC 4.x supportedRepeater SystemRepeater Service Class and Repeater ICA traffic counter groups. Now CC 5.0 beta release supports 3 more groups. These are Repeater App Traffic¸ Repeater QoS Stats and Repeater Link Stats.

Before discussing the polled data functionality of quick reports, we will first briefly introduce the steps to configure the quick reports for the new counter groups. We have showcased a Repeater App Traffic counter group as an example.

We will be using this example to explain the basic structure of these counter group configuration. Now, select the Device Family as Repeater, select the Devices Name you want to run the report on, select the desired counter Group, select any one Counter of that specific group, select the Instance and in the end select the desired time Period for the graphs and click View Graph. Instance signifies application classifiers in Repeater App Traffic case. Otherwise, in Link Stats, group instances will be total repeater links and QOS stats group, will list traffic policies under instances.

Now, let’s walk-through the Repeater App Traffic counter group new counter groups introduced in CC 5.0 release.

Repeater App Traffic counter group

Branch Repeater uses application definitions to segregate the traffic into application and protocols. This counter group uniquely identifies these applications across the links andgenerates graphs on the basis of several application based counters. The counters are listed as follows:

COUNTERS:

  • App sent volume(bits-per-sec)

    • The total volume of App traffic sent on aggregate of all the links, measured in 1000-octets. Where an octet is equivalent to 8 bits.

  • App received volume(bits-per-sec)
    • The total volume of traffic receivedon aggregate of allthe links, measured in 1000-octets
  • App sent packets
    • The total number of packetsof traffic sent on all the links pertaining to that App.
  • App received packets
    • The total number of packets of traffic sent on all the links pertaining to that App.
  • App dropped sent volume(bits-per-sec)
    • The total App traffic not sent on the link due to QoS threshold, in 1000-octets. QoS threshold is the bandwidth limit set on the links.
  • App dropped received volume (bits-per-sec)
    • The total received App traffic dropped from the link due to QoS threshold, in 1000-octets. QoS threshold is the bandwidth limit set on the links.
  • App dropped sent packets
    • The total number of packets not sent on the link due to QoS threshold. QoS threshold is the bandwidth limit set on the links.
  • App dropped received packets
    • The total number of received packets dropped from the link due to QoS threshold. QoS threshold is the bandwidth limit set on the links.

This is a snapshot of the graph on the application sent and received traffic volumes in bits per second.

Hope this gives you a good idea on these counters and the counter group in complete and how simply it lays out the performance graphs on App traffic over one interface.

The next two blogs, I will be covering the other two new BR quick reports, Repeater QoS Stats and Repeater Link Stats counter groups.