Previous page Next page

Creating a Load Threshold Table

Commands used to create or edit a load threshold table are:

direction
 
level
 
link
 
load resync-threshold-table
 
load threshold-table
 
load use-threshold-table
 
start-avoidance percent-below-max
 

 

Tables are created (or edited) by executing the load threshold-table command, which places the CNA system into threshold configuration mode (config-engine-threshold).

Use the direction command to specify direction of dataflow (inbound or outbound) of the samples to be used in the calculations.

Use the start-avoidance percent-below-max command to specify a starting threshold to be used as a default value for all cells in the table (though this value can be overridden for each link). This is an optional command; if a value is not specified, a default value will be used.

Use the level command to define each row of the table.

Use the link command to define the maximum usage allowed for each link, and a link-specific minimum threshold if desired. If the minimum is not specified, the table-wide value (either the default or the one you configured with the start-avoidance percent-below-max command) will be used.

The load use-threshold-table command, in engine configuration mode (config-engine), declares a global table to be used in all prefix calculations unless overridden by a decision policy.

When the table has been defined, use the resync load threshold-table command, which commits the table to the decision-maker database.

You can create multiple tables which can override the global table within decision policies. Tables are always created in config-engine mode, but can be associated with a policy with the load use-threshold-table command in config-engine-policy mode.

The example shown in Table 4 would be configured on the CNA as follows (beginning in engine configuration mode:

Avaya_ANS(config-engine)# load threshold-table example
 
Avaya_ANS(config-engine-threshold)# level 90
 
Avaya_ANS(config-engine-threshold-level)# link L1 30
 
Avaya_ANS(config-engine-threshold-level)# link L2 30
 
Avaya_ANS(config-engine-threshold-level)# link L3 30
 
Avaya_ANS(config-engine-threshold-level)# end
 
Avaya_ANS(config-engine-threshold)# level 104
 
Avaya_ANS(config-engine-threshold-level)# link L1 44
 
Avaya_ANS(config-engine-threshold-level)# link L2 30
 
Avaya_ANS(config-engine-threshold-level)# link L3 30
 
Avaya_ANS(config-engine-threshold-level)# end
 
Avaya_ANS(config-engine-threshold)# level 118
 
Avaya_ANS(config-engine-threshold-level)# link L1 44
 
Avaya_ANS(config-engine-threshold-level)# link L2 30
 
Avaya_ANS(config-engine-threshold-level)# link L3 44
 
Avaya_ANS(config-engine-threshold-level)# end
 
Avaya_ANS(config-engine-threshold)# level 132
 
Avaya_ANS(config-engine-threshold-level)# link L1 44
 
Avaya_ANS(config-engine-threshold-level)# link L2 44
 
Avaya_ANS(config-engine-threshold-level)# link L3 44
 
Avaya_ANS(config-engine-threshold-level)# end
 
Avaya_ANS(config-engine-threshold)# end
 
Avaya_ANS(config-engine)# end
 
Avaya_ANS(config-engine)# load use-threshold-table example
 
Avaya_ANS(config)# end
 
Avaya_ANS# resync load threshold-table example
 

 

This sequence of configuration commands entered on the command line will result in the following lines appearing in your configuration:

load threshold-table example
 
  level 90
 
    link L1 30
 
    link L2 30
 
    link L3 30
 
  end
 
  level 104
 
    link L1 44
 
    link L2 30
 
    link L3 30
 
  end
 
  level 118
 
    link L1 44
 
    link L2 30
 
    link L3 44
 
  end
 
  level 132
 
    link L1 44
 
    link L2 44
 
    link L3 44
 
  end
 
load use-threshold-table example
 

Note that neither start-avoidance percent-below-max nor direction were specified in the configuration. Therefore, the CNA defaults will apply.


Previous page Next page