|
|
|
Sets a stabilizing factor used to modify raw traffic-measurement values before storing them in the database.
hrtt-smoothing-factor <value> no hrtt-smoothing-factor
Must be in engine or policy configuration mode (config-engine or config-engine-policy), both of which require privileged-level access.
Use once globally or once per policy.
decision policy--none (uses the global setting)
The value set by the hrtt-smoothing-factor command is used to compute the value that gets stored in the database whenever a traffic measurement is recorded. The acceptable range, 0 through 1000, is an integer that represents the half-life of a measurement.
NOTE: If CNA is in route-assert mode, the smoothing factor should not be set to 0 except within a decision policy that also includes the route-assert-filter deny command. Routes should not be asserted to any prefix for which the smoothing factor is 0.
The specified value represents the number of new measurements required for a given measurement to contribute half of what it is currently contributing to the calculation of the hrtt value displayed in reports.
With the value of smoothing-factor set to 20, a given measurement’s contribution to the HRTT value that is stored in the database will be cut in half after 20 additional measurements have been received.
If the factor is changed to 10, a newly received measurement’s contribution to the HRTT value will be cut in half after 10 additional measurements have been received.
Adjusting this value allows you to determine whether newly made measurements should have more or less influence on CNA’s decision-making process.
To give more weight to newer measurements, lower the value. This will make measurements decay more rapidly in the calculation of HRTTs. CNA will then be more sensitive to changes in traffic, resulting in more route assertions.
Use the no form of the command to reset the value to its default.
|
|
|