LMA Service Configuration
Mode Commands
The LMA Service Configuration
Mode is used to create and manage the Local Mobility Anchor configuration
supporting Proxy Mobile IP on a PDN Gateway in an eHRPD and E-UTRAN/EPC network.
IMPORTANT:
The commands or keywords/variables
that are available are dependent on platform type, product version,
and installed license(s).
aaa accounting
Enables the LMA to
send AAA accounting information for subscriber sessions.
Syntax
[ default | no ] aaa accounting
default
Sets the command to
the default condition of enabled.
no
Disables the ability
of the LMA to send AAA accounting information.
Usage:
Use this command to
enable the LMA service to send all accounting data (start, stop,
and interim) to the configured AAA servers.
IMPORTANT:
In order for this command
to function properly, AAA accounting must be enabled for the context
in which the LMA service is configured using the aaa accounting subscriber radius command.
Example:
The following command
disables aaa accounting for the LMA service:
no aaa accounting
bind address
Binds the LMA service
to a logical IP interface serving as the S2a (HSGW) or S5/S8
(S-GW) interface and specifies the maximum number of subscribers
that can access this service over the configured interface.
Syntax
bind address ipv6_address [ ipv4-address ipv4_address ] [ max-subscribers num ]
no bind address
no
Removes the interface
binding from this service.
address ipv6_address
Specifies the IPv6
address of the interface configured as the S2a or S5/S8
interface. ipv6_address is
specified in colon separated notation.
ipv4-address ipv4_address
Specifies optional
IPv4 HA/P-GW address to support DSMIP6 session using IPv4 transport.ipv4_address must
be entered as a standard IPv4 address in dotted decimal notation.
max-subscribers num
Default: 3000000
Specifies the maximum
number of subscribers that can access this service on this interface. num must
be configured to an integer between 0 and 3,000,000.
IMPORTANT:
The maximum number
of subscribers supported is dependant on the license key installed
and the number of active PSCs in the system. A fully loaded system
with 13 active PSCs can support 3,000,000 total subscribers. Refer
to the license key command and the Usage section (below) for additional information.
Usage:
Associate the LMA service
to a specific logical IP address. The logical IP address or interface
takes on the characteristics of an S2a or S5/S8 interface
that provides the session connectivity to an HSGW (S2a) or S-GW
(S5/S8). Only one interface can be bound to a service. The
interface should be configured prior to issuing this command.
This command also sets
a limit as to the number of simultaneous subscribers sessions that can
be facilitated by the service/interface at any given time.
When configuring the
max-subscribers option,
be sure to consider the following:
- The total number of
S2a or S5/S8 interfaces you will configure
- The total number of
subscriber sessions that all of the configured interfaces may handle during
peak busy hours
- An average bandwidth
per session multiplied by the total number of sessions
- The type of physical
port (10/100Base-T or 1000Base-Tx) that these interfaces
will be bound to
Taking these factors
into account and distributing your subscriber session across all available
interfaces will allow you to configure your interfaces to optimally
handle sessions without degraded performance.
Example:
The following command
would bind the logical IP interface with the address of
4551:0db8:85a3:08d3:3319:8a2e:0370:1344 to
the LMA service and specifies that a maximum of
300,000 simultaneous subscriber
sessions can be facilitated by the interface/service at
any given time:
bind address 4551:0db8:85a3:08d3:3319:8a2e:0370:1344
max-subscribers 300000
end
Exits the current mode
and returns to the Exec Mode.
Usage:
Change the mode back
to the Exec mode.
exit
Exits the current mode
and returns to the previous mode.
Usage:
Return to the previous
mode.
mobility-option-type-value
Changes the mobility
option type value used in mobility messages.
Syntax
mobility-option-type-value { custom1 | standard }
default mobility-option-type-value
default
Sets the command to
the default value of custom1.
custom1
(Default) Non-standard
type values used before they were defined by IANA.
standard
Standard type values
as defined by IANA. In addition, standard option uses type values defined
in RFC 5844 for HoA options for PMIPv6 PBU/PBA/revocation message.
Usage:
Use this command to
change the mobility option type value used in mobility messages.
Example:
The following command
changes the mobility option type value to standard:
mobility-option-type-value standard
refresh-advice-option
Configures inclusion
of a refresh advice option in the binding acknowledgement message
sent by the LMA.
Syntax
[ default | no ] refresh-advice-option
default
Returns the command
setting to the default setting of disabled.
no
Disables the inclusion
of the refresh advice option in the binding acknowledgement message sent
by the LMA
Usage:
Use this command to
enable the LMA to include this option in a binding acknowledgment sent
to the requesting MAG. The option provides a “hint” to
the MAG of when it should refresh the binding.
As defined in RFC 3775 “Mobility
Support in IPv6”, the binding refresh advice option can only
be present in the binding acknowledgement sent from the mobile node's
home agent in reply to a registration request. A refresh interval
parameter determines the amount of time until the mobile node must
send a new registration to the home agent to avoid de-registration
and loss of session.
IMPORTANT:
Refer to the refresh-interval-percent
and reg-lifetime commands for a complete understanding of registration
(binding) lifetimes and refresh intervals.
refresh-interval-percent
Configures percentage
of the granted registration lifetime to be used in the refresh interval
mobility option in a binding acknowledgement message sent by the
LMA service.
Syntax
refresh-interval-percent number
default refresh-interval-percent
default
Resets the command
value to the default setting of 75.
number
Default: 75
Sets the percent value
for session lifetimes for this service.
number must
be an integer value from 1 to 99.
Usage:
Use this command to
configure the amount of the granted registration lifetime to be
used in the refresh interval mobility option in the binding acknowledgement
message sent by the LMA service to the requesting MAG.
Refreshing a binding
or registration is based on the granted registration lifetime. Since
a refresh request must be within the granted range of a registration
lifetime, this command provides a method of setting the interval
of when a refresh request is sent.
As described in RFC
3775 “Mobility Support in IPv6”, if a binding
refresh advice option is present in the binding acknowledgement,
the refresh interval field in the option must be a value less than
the binding lifetime (also returned in the binding acknowledgement).
The mobile node then should attempt to refresh its registration
at the shorter refresh interval. The home agent will still honor
the registration for the lifetime period, even if the mobile node
does not refresh its registration within the refresh period.
IMPORTANT:
Refer to the refresh-advice-option
and reg-lifetime commands for a complete understanding of registration
(binding) lifetimes and refresh intervals.
Example:
The following command
sets the refresh interval percent to
90:
refresh-interval-percent 90
reg-lifetime
Configures the Mobile
IPv6 session registration lifetime for this service.
Syntax
reg-lifetime seconds
default reg-lifetime
default
Resets the command
value to the default setting of 600.
seconds
Default: 600
Sets the time value
for session lifetimes for this service.
seconds must
be an integer value from1 to 262140.
Usage:
Use this command to
limit PMIPv6 lifetime on this service. If the PBU contains a lifetime shorter
than what is specified, it is granted. If the lifetime is longer,
then HA service will limit the granted lifetime to the configured
value.
IMPORTANT:
Refer to the refresh-interval-percent
and refresh-advice-option commands for a complete understanding
of registration (binding) lifetimes and refresh intervals.
Example:
The following command
sets the registration lifetime for Mobile IPv6 sessions using this service
to
1200 seconds
(20 minutes):
reg-lifetime 1200
revocation
Enables the MIP revocation
feature and configures revocation parameters.
Syntax
revocation { enable | max-retransmission number | retransmission-timeout msecs }
default revocation { enable | max-retransmission | retransmission-timeout }
no revocation enable
default
Resets the keyword
to its default value.
no
Disables revocation
for this service.
enable
Default: disabled
Enables the MIP registration
revocation feature for the LMA service. When enabled, if revocation
is negotiated with a MAG and a MIP binding is terminated, the LMA
can send a Revocation message to the MAG. This feature is disabled
by default.
max-retransmission number
Default: 3
The maximum number
of retransmissions of a Revocation message before the revocation fails. number must
be an integer value from 0 through 10.
retransmission-timeout msecs
Default: 3000
The number of milliseconds
to wait for a Revocation Acknowledgement from the MAG before retransmitting
the Revocation message. msecs must
be an integer value from 500 through 10000.
Usage:
Use this command to
enable or disable the MIP revocation feature on the LMA or to change
settings for this feature.
Example:
The following command
sets the maximum number of retries for a Revocation message to
6:
revocation max-retransmission 6
The following command
sets the timeout between retransmissions to
10:
revocation retransmission-timeout 10
sequence-number-validate
Configures sequence
number validation of the received MIPv6 control packets by the LMA
service according to RFC 3775.
Syntax
[ default | no ] sequence-number-validate
default
Resets the command
value to the default setting of enabled.
Usage:
Use this command to
configure the sequence number validation of the received MIPv6 control
packets (PBUs) by the LMA service. This feature validates MIPv6
control packets and insures that any incoming packets with a sequence
number prior to the last number received is consider invalid.
If this service has
no cache entry of the home address included in the PBU, it will
accept any sequence value in the initial PBU from the mobile node.
setup-timeout
The maximum amount
of time allowed for session setup.
Syntax
setup-timeout seconds
default setup-timeout
default
Resets the command
value to the default setting of 60.
seconds
Default: 60 seconds
The maximum amount
of time, in seconds, to allow for setup of a session in this service. seconds must
be an integer value from 1 through 1000000.
Usage:
Use this command to
set the maximum amount of time allowed for setting up a session.
Example:
The following command
sets the maximum time allowed for setting up a session to 5 minutes
(300 seconds):
setup-timeout 300
signalling-packets
Enables the
DSCP marking feature for IP headers carrying outgoing signalling packets.
Syntax
signalling-packets
ip-header-dscp value
{ default | no } signalling-packets
ip-header-dscp
default
Restores the specified
parameter to its default setting of 0x0.
no
Disables the specified
functionality.
ip-header-dscp value
Used to configure the
QoS Differentiated Services Code Point (DSCP) marking for IP header
encapsulation.
value: Represents
the DSCP setting. It represents the first six most-significant bits
of the ToS field. It can be configured to any hex value from 0x0
through 0x3F. Default is 0x0.
Usage:
Use this command to
enable or disable the DSCP marking feature for IP headers carrying outgoing
signalling packets. DSCP marking is disabled by default.
Example:
The following command
configures the HSGW service to support DSCP marking for IP headers
carrying outgoing signalling packets:
signalling-packets
ip-header-dscp 0x21
simul-bindings
Specifies the maximum
number of “care-of” addresses that can simultaneously be
bound for the same user as identified by NAI and Home address.
Syntax
simul-bindings number
default simul-bindings
default
Resets the command
value to the default setting of 1.
number
Default: 1
Configures maximum
number of “care of” addresses that can be simultaneously
bound for the same user as identified by their NAI and home address. number must
be an integer value between 1 and 3.
Usage:
Per RFC 5213 (and 3775),
the LMA service creates a binding record known as a binding cache
entry (BCE) for each subscriber session it is facilitating. Each
BCE is associated with a care-of address. As the mobile node roams,
it is possible that the session will be associated with a new care
of address.
Typically, the LMA
service will delete an old binding and create a new one when the information
in the registration request changes. However, the mobile node could
request that the LMA maintains previously stored BCEs. This command
allows you to configure the maximum number of BCEs that can be stored
per subscriber if more than one is requested.
Example:
The following command
configures the service to support up to 2 addresses per subscriber:
simul-bindings 2
standalone
Configures the LMA
service to start in standalone mode.
Syntax
[ default | no ] standalone
default
Resets the command
value to the default setting.
Usage:
Use this command to
start the LMA service in standalone mode.
timestamp-option-validation
Configures validation
of timestamp option in binding update messages. By default, timestamp
option is mandatory.
Syntax
[ default | no ] timestamp-option-validation
default
Resets the command
value to the default setting of enabled.
Usage:
Use this command to
configure timestamp validation in binding update messages.
timestamp-replay-protection
Designates timestamp
replay protection scheme as per RFC 4285.
Syntax
timestamp-replay-protection
tolerance seconds
{ default | no } timestamp-replay-protection tolerance
default
Resets the command
value to the default setting of 7.
no
Disables the timestamp
replay protection feature.
tolerance seconds
Default: 7
Defines the acceptable
difference in timing (between timestamps) before rejecting packet,
in seconds. seconds must
be an integer value between 0 and 65535.
Usage:
Use this command to
define the acceptable difference in timing (between timestamps) before
rejecting packet.
Example:
The following command
sets the acceptable difference for timestamps to 10 seconds:
timestamp-replay-protection
tolerance 10