HP-UX Mobile IPv6 A.01.00 Administrator's Guide

Chapter 5
Administering the Mobile IPv6 Kernel Module with the mip6admin Tool
Starting, Stopping, and Dynamically-Configuring mip6mod
66
Dynamically-configuring mip6mod: setconfiguration
Use the setconfiguration command to dynamically-configure mip6mod (does not require mip6mod
retstart). Use options to configure any of the individual mip6mod parameters, or to specify a Mobile IPv6
configuration file— do not use options and a file name simultaneously. mip6mod must be running to use the
setconfiguration command.
If you use options to dynamically-configure individual mip6mod parameters, the new settings are not saved to
the mip6mod configuration file. If you want to save the settings you dynamically-configured using
setconfiguration, you must use mip6config to update the mip6mod configuration file, and save the changes
using the write command. mip6mod retains its current settings for all parameters that are not
dynamically-configured using setconfiguration command options. For this reason, the following individual
mip6mod parameter descriptions do not list their default values. Refer to “The Mobile IPv6 Kernel Module
Configuration File: /etc/mip6.conf” on page 31 to learn the default value for each parameter.
If you use specify a filename to dynamically-configure mip6mod with, the setconfiguration command uses
default values for each unconfigured entry in the file.
NOTE Dynamically setting a parameter that conflicts with the present configuration will not affect
the present Mobile IPv6 operation. For example, if mip6mod currently retains 25,000 home
agent binding cache entries, and you dynamically set
max_home_bindings to 20, 000—you will
not lose the 5,000 binding cache entries. After a binding cache entry expires, the entry is
removed from the binding cache. mip6mod will start adding new binding cache entries after it
reaches below the level you dynamically set, for example, mip6mod will start adding new
binding cache entries in this case once it reaches 19,999.
However, several mip6mod parameters are relative to one another, for example
max_error_rate and min_error_rate. Be sure when you use setconfiguration commands
and options that you do not set values that conflict with either present parameter values, or
values being dynamically-configured in the same setconfiguration command. The
mip6admin tool will void the entire setconfiguration command if any value for any option in
the command conflicts with either present parameter values, or values being
dynamically-configured in the same setconfiguration command. mip6mod retains its current
settings for all parameters that are not dynamically-configured using setconfiguration
command options.
Abbreviated: se[tconfiguration]
Syntax: setconfiguration [-f
conf_file ] [-ll log_level ] [-ni num_mip6mod_instances ]
[-mb
max_bindings ] [-mhb max_home_bindings ] [-bl binding_lifetime ]
[-bai
binding_refresh_advice_interval ]
[-brt
binding_refresh_request_threshold ] [-rl rate_limit ]
[-mxr
error_rate_max ] [-mnr error_rate_min ]
Options: -f
file_name The fully-qualified (absolute) path of Mobile IPv6 configuration file to
configure mip6mod with. Default values are used for unconfigured
parameters in the file. You must use this option first and exclusively
without additional options. All options following -f are ignored.
-ll
log_level The mip6mod log 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 following is a list of the levels in the
mip6mod logging hierarchy: