|
Measures reported by NPSPolicyEngineTest
Every network policy must have at least one configured condition. NPS provides many conditions groups that allow you to clearly define the properties that the connection request received by NPS must have in order to match the policy. How quickly NPS matches requests with policies is a good measure of the efficiency of the NPS policy engine. Using the NPSPolicyEngineTest test, administrators can measure just that! This test reports the time taken by NPS to process requests, the rate of pending requests on NPS, and the number of requests that matched configured policies. In the process, the test reveals processing bottlenecks on the NPS and how they impact policy matching.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Last_round_trip_time |
Indicates the interval (in hundredths of a second) between the most recent request to NPS and its response. |
Secs |
Ideally, the value of this measure should be very low. A high value indicates that NPS is taking too long to verify whether/not requests it receives match with the policy configuration. |
| Matchd_remot_acess_polcy |
Indicates the average number of remote access policies that have been matched with requests per second. |
Number |
|
| Pending_requests |
Indicates the rate of requests destined for NPS that have not yet timed out or received a response. |
Reqs/Sec |
A high value could either indicate a processing bottleneck on NPS or a high timeout setting (which could be causing many requests to be retransmitted to the NPS). In the case of the latter, you may want to consider modifying the timeout setting to minimize the number of pending requests. |
|