| Measurement |
Description |
Measurement Unit |
Interpretation |
| Cur_rate_threshold |
Indicates the limit of UDP packets handled every 10 milliseconds. |
Number |
This implies that within 10 milliseconds (ms) range, NetScaler can allow (receive or pass through) the set number of UDP packets. This threshold is configurable. Once this threshold is violated, subsequent UDP packets will be dropped by the appliance. You are hence advised to configure this limit based on the current and anticipated UDP traffic to the NetScaler appliance. To set/alter this limit, use the set rateControl command. |
| Data_received |
Indicates the amount of UDP data received during the last measurement period. |
MB |
These measures are good indicators of the UDP load on the NetScaler appliance. |
| Data_transmitted |
Indicates the amount of UDP data transmitted during the last measurement period. |
MB |
| Packet_received |
Indicates the number of UDP packets received during the last measurement period. |
Number |
| Packet_transmitted |
Indicates the number of UDP packets transmitted during the last measurement period. |
Number |
| Unknown_service |
Indicates the number of UDP packets that were received on a NetScaler port number that is not assigned to any service. |
Number |
This measure counts those UDP packets that were received, but dropped. |
| Bad_udp_checksum |
Indicates the number of packets that were received with a checksum error. |
Number |
|
| Rate_threshold_exceeded |
Indicates the number of times the Cur_rate_threshold measure has been violated. |
Number |
A high value of this measure indicates that the Cur_rate_threshold has been violated often. When this happens, you must first ensure that the UDP packets received are genuine. If they are genuine, then you must increase the current rate threshold. To set/alter this limit, use the set rateControl command. |