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
69
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,