 |
» |
|
|
|
Use the mip6admin commands described in this section to start,
stop, and dynamically-configure mip6mod. The following is a list
of the mip6admin commands described in this section: Starting
mip6mod: start | |
Use the start command to start and configure mip6mod with the specified
Mobile IPv6 configuration file. If no file name is specified, mip6mod
starts with /etc/mip6.conf. After starting mip6mod, mip6admin logs the MUX ID for
the mip6mod instance in /etc/mip6.muxids and updates the HP-UX IPv6 Router Advertisement Daemon,
rtradvd, of the mip6mod status. - Abbreviated:
star[t] - Syntax
start [-f conf_file] - Options:
- [-f conf_file]
The fully-qualified (absolute) path of Mobile IPv6
configuration file to configure mip6mod with. Default values are
used for invalid or unconfigured parameters in the file. If no conf_file
is specified, mip6mod starts with /etc/mip6.conf.
- Example:
mip6admin -start -f /etc/backup-mip6.conf
Info: started mip6mod successfully. |
Configuring
Automatic Start-up at System BootEdit
the /etc/rc.config.d/mip6 file to configure mip6mod to start automatically during
the system boot process. Set the MIP6= parameter to 1 to start HP-UX Mobile IPv6 during boot-up. Set the parameter
to 0 if you do not want mip6mod to start during boot-up. The
default setting is: MIP6=0. The /etc/rc.config.d/mip6 file also allows you to specify the name of the Mobile
IPv6 configuration file for the system to use after rebooting. Set
the MIP6_CONF_FILE= parameter to the absolute path of the Mobile IPv6
configuration file you want the system to use after rebooting. The
default setting is: MIP6_CONF_FILE=/etc/mip6.conf. Stopping
mip6mod: stop | |
Use the stop command to stop mip6mod. The stop command uses the MUX
IDs in /etc/mip6.muxids to stop the mip6mod instance in the kernel. - Abbreviated:
sto[p] - Syntax:
stop - Example:
mip6admin -stop
Info: stopped mip6mod successfully. |
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” 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: - a[lert]
Logs messages for critical conditions requiring immediate
attention, for example, exceeding memory space. - e[rror]
Logs messages for error conditions, for example,
when the binding cache reaches maximum capacity. Error conditions
might limit Mobile IPv6 performance, but might not require immediate
attention. - w[arn]
Logs messages for warning conditions, for example, when
dynamic configuration occurs. - i[nfo]
Logs messages for informational conditions, for
example, when a binding cache entry is created. - d[ebug]
Logs messages for debugging and troubleshooting conditions,
for example, when a mobility route is added.
- -ni num_mip6mod_instances
The number of mip6mod instances to start
and use for processing packets with the Mobility Header. The num_mip6mod_instances value must be an integer in the range [1-N],
where N represents the number of processors on the system.
| | | | | NOTE: While you
can increase the number of mip6mod instance running in the kernel
using the setconfiguration command, you cannot decrease the number of instances. Edit the
number of mip6mod instances parameter in the mip6mod configuration
file and restart mip6mod using mip6dmin to decrease the number of
mip6mod instances running in the kernel. | | | | |
- -mb max_bindings
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.
- -mhb max_home_bindings
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.
- -bl max_binding_lifetime
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],
and must be greater than the binding_refresh_advice_interval and binding_refresh_request_threshold values. (Note: 262,140 seconds is 4,369 minutes
or, approximately 72 hours, or 3 days).
- -bai binding_refresh_advice_interval
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. - -brt binding_refresh_request_threshold
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. - -rl error_rate_limit_threshold
The number (or limit) of error messages
mip6mod can send to Mobile Nodes before entering a controlled error
message rate. The error_rate_limit_threshold value must be an integer in the range [1-32].
The max_error_rate and min_error_rate parameters control how often mip6mod sends error
messages after it exceeds the error_rate_limit_threshold value. - -mxr max_error_rate
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.
- -mnr 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.
- Example:
mip6admin setconfiguration -bl 600 -ll warn -mhb 50000
Info: successfully re-configured mip6mod. |
Setting
(Toggle) mip6mod Security and Debugging Enforcement: debug | |
Use the debug command without options to display mip6mod debug and
troubleshooting settings. Use the debug command with options to
enable or disable a specific mip6mod debug setting. Use multiple
options to simultaneously change more than one setting. - Abbreviated:
[d]ebug - Syntax:
debug [-ipsec] [-rr] [-er] [-bu] - Options:
- -i[psec]
Enforces IPSec processing of home Binding Update
messages. - -rr
Enforces Return Routability procedure for Route
Optimization. - -er
Enforces Error-Rate Limit setting. - -bu
Enforces Binding Update message processing
- Example:
Compare the IPSec and Binding Update Settings
After Each Command# mip6admin -debug -ipsec -bu
DEBUG SETTINGS
**********************************************************************
Disable IP Security: Off
Disable Return Routablity: Off
Disable Error Rate Limit: Off
Disable Binding Update Processing: On
# mip6admin -debug -ipsec -bu
DEBUG SETTINGS
**********************************************************************
Disable IP Security: On
Disable Return Routablity: Off
Disable Error Rate Limit: Off
Disable Binding Update Processing: Off |
|
Printable version
