All mip6mod Parameters

The mip6mod logging level. When you specify a log level, mip6mod logs messages for that level and all levels above it in the logging hierarchy. For example, mip6mod logs Warn, Error, and Alert messages if you configure the log level as Warn. The highest level in the logging hierarchy is Alert; the lowest level is Debug.

The default value for log level is Error.

The following is a list of the levels in the mip6mod logging hierarchy:

The number of mip6mod instances to start and use for processing messages with Mobility Headers. The num_mip6mod_instances value must be an integer in the range [1-N], where N represents the number of processors on the system.

The default value for num_mip6mod_instances is 1.

The maximum number of combined Home Agent and Correspondent Node binding cache entries mip6mod can support. The max_bindings value must be an integer in the range [1-100,000] and must be greater or equal to the max_home_bindings value.

The default value for max_bindings is 10,000 or the value of max_home_bindings, whichever value is the greater of the two.

The maximum number of Home Agent binding cache entries mip6mod can support. The max_home_bindings value must be an integer in the range [1-100,000] and must be less or equal to the max_bindings value.

The default value for max_home_bindings is 10,000 or the value of max_bindings, whichever value is the least of the two.

The maximum lifetime, measured in seconds, for a binding cache entry. The max_binding_lifetime value must be an integer in the range [1-262,140].

The default value for max_binding_lifetime is 262,140 (which is 4,369 minutes or, approximately 72 hours, or 3 days).

When mip6mod is a Home Agent, it can “advise” registered Mobile Nodes when to refresh their registration (i.e., re-register) based on the lifetime of their current registrtion. The binding_refresh_advice_interval value, included in Binding Acknowledgement messages sent to Mobile Nodes, indicates when Mobile Nodes should re-register by specifying a number of seconds prior to the expiration of their current registration.

The binding_refresh_advice_interval value must be an integer in the range [0-262,140] and must be less than the max_binding_lifetime value. Set the binding_refresh_advice_interval value to 0 to disable the Binding Refresh Advice option.

The default value for binding_refresh_advice_interval is 0.

The binding_refresh_request_threshold determines when mip6mod (as a Correspondent Node) sends Binding Refresh Request messages to registered Mobile Nodes. The binding_refresh_request_threshold is relative to the lifetime of the Mobile Node’s current registration. The value of binding_refresh_request_threshold is the number of seconds prior to the expiration of the Mobile Node’s current registration that mip6mod sends Binding Refresh Request messages requesting the Mobile Nodes re-register.

The binding_refresh_advice_interval value must be an integer in the range [0-262,140] and must be less than the max_binding_lifetime value. Disable the Binding Refresh Advice option by setting the binding_refresh_advice_interval value to 0.

The default value for binding_refresh_advice_interval is 0.

The number (or limit) of error messages mip6mod can send to Mobile Nodes before entering a controlled error message rate. The max_error_rate and min_error_rate parameters control how often mip6mod sends error messages after exceeding the error_rate_limit_threshold value.The error_rate_limit_threshold value must be an integer in the range [1-32].

The default value for error_rate_limit_threshold is 10.

The max_error_rate is the maximum rate (i.e., highest frequency) mip6mod sends error messages at after exceeding the error_rate_limit_threshold. The max_error_rate value, in miliseconds, is the shorest duration (i.e., interval) between error messages. Smaller values are shorter durations between error messages, and therefore are faster rates.The max_error_rate value must be an integer in the range [10-9,990] and must be less (i.e., faster) than the min_error_rate value.

The default value for max_error_rate is 100. If the min_error_rate value is less than or equal to (i.e., faster) 100, the default max_error_rate value is 10 milliseconds less (i.e., faster) than the min_error_rate.

The min_error_rate is the minimum rate (i.e., least frequency) mip6mod sends error messages at after exceeding the error_rate_limit_threshold. The min_error_rate value, in miliseconds, is the longest duration (i.e.interval) between error messages. Larger values are longer durations between error messages, and therefore are slower rates.The min_error_rate value must be an integer in the range [20-10,000] and must be greater (i.e., slower) than the max_error_rate value.

The default value for min_error_rate is 1000. If the max_error_rate value is greater (i.e., slower) than 1000, the default min_error_rate is 10 milliseconds greater (i.e., slower) than max_error_rate.