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

Chapter 3
Getting Started with HP-UX Mobile IPv6
HP-UX Mobile IPv6 Deployment Components
32
warn Logs messages for warning conditions, for example, when dynamic
configuration occurs.
info Logs messages for informational conditions, for example, when a binding
cache entry is created.
debug Logs messages for debugging and troubleshooting conditions, for example,
when a mobility route is added.
num-mip6mod-instances
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.
mip6mod Binding Cache Parameters
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. The default
value for max-bindings is 10,000 or the value of max-home-bindings, whichever value is the
greater of the two.
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. The default value for max-home-bindings is 10,000 or the
value of max-bindings, whichever value is the least of the two.
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. The default value for
max-binding-lifetime is 262,140 (which is 4,369 minutes, or approximately 72 hours, or 3
days).
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 registration. The
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 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 refresh-advice-interval
value to 0 to disable the Binding Refresh Advice option. The default value is 0.
refresh-request-threshold
The refresh-request-threshold enables the Binding Refresh Request message and
determines when Correspondent Nodes sends Binding Refresh Request messages to
registered Mobile Nodes. When mip6mod is a Correspondent Node, it sends Binding Refresh
Request messages to Mobile Nodes. The refresh-request-threshold is relative to the
lifetime of the Mobile Node’s current registration.