Part 1- Repeater App Traffic Group against [1945006!]
support NetScaler Command Center for quick reports Branch Repeater brought a lot of value to help visualize the level of performance factors with graphics for several BR units on a page. CC 4.x supported System Repeater Repeater class service and traffic Repeater ICA against the groups. Now CC 5.0 beta version supports 3 other groups. These are Repeater App Traffic ¸ Repeater QoS Stats and Repeater Stats Link .
Before discussing the functionality of the data surveyed quick reports, we will first outline the steps to configure the quick reports for new groups against. We presented a Repeater App Traffic against the group as an example.
We will use this example to explain the basic structure of the configuration of the counter group. Now select Device Family as a repeater, select Devices Name you want to run the report, select the desired meter Group , select against of this specific group, select the proceeding and at the end select the desired time period for graphics and click Show graph . Instance means classifiers application if App Repeater traffic. Otherwise, Stats Link in the instances of the group will total links and repeaters QOS stats group will list the traffic policies under the case.
Now let's walk-through Traffic App repeater new group counter groups against CC introduced in version 5.0.
group against Repeater App Traffic
Branch Repeater uses application definitions to separate traffic and application protocols. The group counter identifies only those applications through the graphic links on the basis of several application-based counters. Counters are listed as follows:
METERS : volume
-
App sent (bits-per - dry)
-
the total volume of traffic sent App across all links, measured in 1000-bytes. When a byte is 8-bit.
-
- App received volume (bits per second)
- The total volume of receivedon of total traffic ALLthe links, measured in 1000 -octets
- App packets sent
- the total number of traffic sent packetsof on all the links related to this app.
- App received packets
- The total number of traffic packets sent on any links related to this app.
- App fell sent volume (bits per second)
- total traffic app was not sent on the link because of QoS threshold, in 1000 -octets. QoS threshold is the limit of the bandwidth set on the links.
- App lowered the volume received (bits per second)
- The total received App traffic increased from the bond because of threshold QoS, in 1000 bytes. QoS threshold is the limit of the bandwidth set on the links.
- packet App fell sent
- The total number of unsent the link because the QoS threshold packets. QoS threshold is the limit of the bandwidth set on the links.
- App dropped packets received
- The total number of received packets striped link due to the QoS threshold. QoS threshold is the limit of the bandwidth set on the links.
This is a preview of the graphic on the application sent and received traffic volumes in bits per second.
Hopefully this gives you a good idea about these counters and full counter group and simply states how the performance charts on the App traffic on one interface.
the two blogs, I'll be covering the other two new quick reports BR, Repeater Repeater Link QoS statistics stats counter groups.
0 Komentar