Proxy Mobile IPv6 Local Mobility Anchor Commands

This chapter describes the Cisco IOS XR softwarecommands used to configure and monitor features related to the Proxy Mobile IPv6 Local Mobility Anchor (LMA).

For detailed information about Proxy Mobile IPv6 LMA concepts, configuration tasks, and examples, refer to the IP Addresses and Services Configuration Guide for Cisco ASR 9000 Series Routers.

aaa accounting (pmipv6-lma)

To enable Local Mobility Anchor (LMA) accounting, use the aaa accounting command in PMIPv6 LMA configuration mode. To disable LMA accounting, use the no form of this command.

aaa accounting [ interim interim-interval ]

no aaa accounting [ interim interim-interval ]

Syntax Description

interim-interval

Interim accounting interval in minutes. It can have a value between 1 and 86400.

Command Default

None.

Command Modes

PMIPv6 LMA configuration

Command History

Release Modification

Release 5.3.0

This command was introduced.

Usage Guidelines

If the interim interim-interval option is specified, Interim-Update records are sent to the RADIUS security server at the configured interim-interval specified in minutes. Otherwise, only Start and Stop records are sent to the RADIUS security server.

There are two types of accounting sessions, one for Mobile Nodes and one for tunnels. Interim-Update records are enabled only for tunnel accounting and not for Mobile Node accounting. For information about AAA/RADIUS configuration for accounting, see the Authentication, Authorization, and Accounting Commands chapter in Cisco ASR 9000 Series Aggregation Services Router System Security Command Reference.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to enable LMA accounting: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma LMA domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)# aaa accounting interim 2

address (pmipv6)

To configure the IPv4 or IPv6 address for the LMA, use the address command in the PMIPv6 LMA configuration mode. To remove the IPv4 or IPv6 address for the LMA, use the no form of this command.

address {ipv4 ipv4-address | ipv6 ipv6-address}

no address {ipv4 ipv4-address | ipv6 ipv6-address}

Syntax Description

ipv4-address

The IPv4 address for the LMA.

ipv6-address

The IPv6 address for the LMA.

Command Default

None

Command Modes

IPv6 LMA configuration

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure the IPv4 address for the LMA within the PMIPv6 LMA configuration mode: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma lma1 domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)# address ipv4 192.168.0.1

address (pmipv6-lma-mll-cust-tpt)

To configure customer-specific IPv4 or IPv6 address for the Local Mobility Anchor (LMA) within a Mobile Local Loop (MLL), use the address command in the PMIPv6 LMA MLL Customer Transport configuration mode. To remove existing customer-specific IPv4 or IPv6 address, use the no form of this command.

address {ipv4 ipv4-address | ipv6 ipv6-address}

no address {ipv4 ipv4-address | ipv6 ipv6-address}

Syntax Description

ipv4-address

The IPv4 address for the LMA.

ipv6-address

The IPv6 address for the LMA.

Command Default

None

Command Modes

PMIPv6 LMA MLL Customer Transport configuration

Command History

Release Modification

Release 5.3.0

This command was introduced.

Usage Guidelines

There can only be two instances of addresses, one for IPv4 and one for IPv6.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure a customer-specific IPv4 address: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma LMA domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)# mobility-service mobile-local-loop
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll)# customer CUST1 vrf VRF1
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll-cust)# transport vrf TVRF1
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll-cust-tpt)# address ipv4 192.168.0.1

auth-option

To enable authentication for the Proxy Mobile IPv6 (PMIP6) domain and for a peer MAG with the LMA, use the auth-option command in the appropriate configuration mode. To disable the authentication, use the no form of this command.

auth-option spi spi-hex-value key ascii string

no auth-option spi spi-hex-value key ascii string

Syntax Description

spi spi-hex-value

Specifies the Security Parameter Index (SPI) in hexadecimal format. The range is from 0 to FFFFFFFF.

key ascii

Specifies the security key in ASCII format.

string

String key value.

Command Default

No authentication is set

Command Modes

PMIPv6 domain configuration

PMIPv6 LMA configuration

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure authentication for the PMIPv6 domain: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-domain)# auth-option spi FF key ascii FFD

auth-option (pmipv6-lma-mll-cust)

To enable customer-specific authentication in a Local Mobility Anchor (LMA) within a Mobile Local Loop (MLL), use the auth-option command in the PMIPv6 LMA MLL Customer configuration mode. To disable the customer-specific authentication, use the no form of this command.

auth-option spi spi-hex-value key ascii string

no auth-option spi spi-hex-value key ascii string

Syntax Description

spi spi-hex-value

Specifies the Security Parameter Index (SPI) in hexadecimal format. The range is from 0 to FFFFFFFF.

key ascii

Specifies the security key in ASCII format.

string

String key value.

Command Default

None.

Command Modes

PMIPv6 LMA MLL Customer configuration

Command History

Release Modification

Release 5.3.0

This command was introduced.

Usage Guidelines

This configuration overrides the global auth-option configuration in the PMIPv6 LMA Domain.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure authentication for a customer: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma LMA domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)# mobility-service mobile-local-loop
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll)# customer CUST1 vrf VRF1
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll-cust)# auth-option spi FF key ascii FFD

bce

To configure binding cache entries (BCEs) or bindings information, use the bce command in the PMIPv6 LMA configuration mode. To remove the BCEs information use the no form of this command.

bce {delete-wait-time milliseconds | lifetime seconds | maximum number}

no bce {delete-wait-time milliseconds | lifetime seconds | maximum number}

Syntax Description

delete-wait-time milliseconds

Specifies the time that LMA must wait before it deletes a BCE of a MN, upon receiving a PBU message from a MAG with a lifetime value of 0.

The time is entered in milliseconds and the range is 100-65535.

lifetime seconds

Specifies the permitted lifetime of a BCE in seconds. The granted lifetime is minimum of this configured value and the value received from the MAG in the PBU packet.

The time is entered in seconds and the range is 10-65535.

maximum number

Specifies the maximum number of BCEs that the LMA can support.

The range is 1-128000.

Command Default

None.

Command Modes

PMIPv6 LMA configuration

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure maximum number of BCEs that LMA can support: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma lma1 domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)# bce maximum 3400
RP/0/RSP0/CPU0:router(config-pmipv6-lma)# commit

This example shows how to configure permitted lifetime of a BCE: 

RP/0/RSP0/CPU0:router(config-pmipv6-lma)# bce lifetime 2500
RP/0/RSP0/CPU0:router(config-pmipv6-lma)# commit

bce (pmipv6-lma-mll-cust)

To configure customer-specific permitted lifetime of binding cache entries (BCEs) in a Local Mobility Anchor (LMA) within a Mobile Local Loop (MLL), use the bce command in the PMIPv6 LMA MLL Customer configuration mode. To remove customer-specific BCE lifetime, use the no form of this command.

bce lifetime seconds

no bce lifetime seconds

Syntax Description

lifetime seconds

Permitted lifetime of a BCE in seconds. The granted lifetime is minimum of this configured value and the value received from the MAG in the PBU packet.

The time is entered in seconds and the range is 10-65535.

Command Default

None.

Command Modes

PMIPv6 LMA MLL Customer configuration

Command History

Release Modification

Release 5.3.0

This command was introduced.

Usage Guidelines

This configuration overrides the global LMA BCE configuration.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure customer-specific lifetime of a BCE: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma LMA domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)# mobility-service mobile-local-loop
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll)# customer CUST1 vrf VRF1
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll-cust)# bce lifetime 2500

bri

To configure binding revocation indication (BRI) message parameters, use the bri command in the appropriate configuration mode. To remove BRI message parameters, use the no form of this command.

bri {delay {max | min} milliseconds | retries number}

no bri {delay {max | min} milliseconds | retries number}

Syntax Description

delay min milliseconds delay max milliseconds

Specifies the minimum and maximum time in milliseconds to wait before sending a BRI message to the LMA or MAG. The range is 500-65535.

retries number

Specifies the number of times the LMA should retransmit a BRI message. The range is 1-10.

Command Default

None.

Command Modes

PMIPv6 LMA configuration

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure BRI parameters for LMA: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma lma1 domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)#bri delay max 5000
RP/0/RSP0/CPU0:router(config-pmipv6-lma)#bri delay min 500
RP/0/RSP0/CPU0:router(config-pmipv6-lma)#bri retries 5

customer (pmipv6-domain-nai)

To configure the name of the customer for a Mobile Node (MN) present in the PMIPv6 domain, use the customer command in PMIPv6 Domain NAI configuration mode. To disable the customer configuration, use the no form of this command.

customer customer-name

no customer customer-name

Syntax Description

customer-name

Name of the customer.

Command Default

None.

Command Modes

PMIPv6 Domain NAI configuration

Command History

Release Modification

Release 5.3.0

This command was introduced.

Usage Guidelines

The customer is configured during Local Mobility Anchor (LMA) Mobile Local Loop (MLL) service configuration.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure a customer to which NAI belongs: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-domain)# nai example@example.com
RP/0/RSP0/CPU0:router(config-pmipv6-domain-nai)# customer CUST1

customer (pmipv6-lma-mll)

To configure the name and the VRF of a customer, use the customer command in PMIPv6 Local Mobility Anchor (LMA) Mobile Local Loop (MLL) configuration mode. To remove an existing customer, use the no form of this command.

customer customer-name vrf vrf-name

no customer customer-name vrf vrf-name

Syntax Description

customer-name

Name of the customer.

vrf-name

Name of the VRF.

Command Default

None.

Command Modes

PMIPv6 LMA MLL configuration

Command History

Release Modification

Release 5.3.0

This command was introduced.

Usage Guidelines

There can be many customers, however no two customers can be configured with the same VRF.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure the name and the VRF of a customer: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma LMA domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)# mobility-service mobile-local-loop
RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll)# customer CUST1 vrf VRF1
RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll-cust)#

clear ipv6 mobile pmipv6 lma binding

To clear all bindings held by the LMA, or bindings corresponding to a mobile access gateway peer (MAG), and a mobile node (MN) use the clear ipv6 mobile pmipv6 lma binding command in EXEC mode.

clear ipv6 mobile pmipv6 lma binding [all | mag mag-identifier | nai string]

Syntax Description

all

Clears all binding sessions held by the LMA.

mag mag-identifier

Clears the binding sessions for the MAG.

nai string

Clears the binding sessions for the MN.

Command Default

None.

Command Modes

EXEC mode

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to clear the binding sessions for the MN: 

RP/0/RSP0/CPU0:router# clear ipv6 mobile pmipv6 lma binding nai example@example.com

clear ipv6 mobile pmipv6 lma statistics

To clear PMIPv6 LMA statistics corresponding to a specified domain and a peer or a customer, use the clear ipv6 mobile pmipv6 lma statistics in EXEC mode.

clear ipv6 mobile pmipv6 lma statistics [domain domain-name peer peer-id | customer customer-name ]

Syntax Description

domain domain-name

Clears LMA statistics for the domain specified.

peer peer-id

Clears peer MAG statistics.

customer customer-name

Clears statistics of a specific customer.

Command Default

None.

Command Modes

EXEC mode

Command History

Release Modification

Release 5.2.2

This command was introduced.

Release 5.3.1

The customer customer-name keyword was added to this command.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to clear all LMA statistics: 

RP/0/RSP0/CPU0:router# clear ipv6 mobile pmipv6 lma statistics

default profile

To enable the default profile for the mobile node (MN), use the default profile command in Local Mobility Anchor (LMA) configuration mode. To disable the default profile, use the no form of this command.

default profile name

no default profile name

Syntax Description

name

Profile name of the MN.

Command Default

The default profile is disabled.

Command Modes

PMIPv6 LMA configuration

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure the default profile for the MN: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma lma1 domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)#address ipv6 2031:D8:0:0:FF00::F0
RP/0/RSP0/CPU0:router(config-pmipv6-lma)#default profile profile1

dscp control-plane (pmipv6-lma)

To configure the value of Differentiated Services Code Point (DSCP) in the outgoing PMIPv6 control plane messages, use the dscp control-plane command in PMIPv6 LMA configuration mode. To disable DSCP value configuration, use the no form of this command.

dscp control-plane dscp-value [ force ]

no dscp control-plane dscp-value [ force ]

Syntax Description

dscp-value

DSCP value. It can have a value between 1 and 63.

Command Default

None.

Command Modes

PMIPv6 LMA configuration

Command History

Release Modification

Release 5.3.0

This command was introduced.

Usage Guidelines

The outgoing PMIPv6 control plane messages include locally generated packets such as Proxy Binding Revocation Indications (PBRIs), Proxy Binding Revocation Acknowledgments (PBRAs), Heartbeat Requests, and packets sent in response to packets received from MAG such as Proxy Binding Acknowledgments (PBAs), PBRIs, PBRAs, and Heartbeat Responses.

If dscp-value is not specified, then the DSCP received in a request is used in the outgoing response packet. DSCP is not set in the other outgoing packets.

If dscp-value is specified without the force option:

  • The configured DSCP value is set in locally generated packets.

  • If the received packet does not have DSCP marking, the configured value is set in the outgoing packet.

  • If the received packet has DSCP marking that matches the configured value, then the DSCP received is set in the outgoing response packet.

  • If the received packet has DSCP marking that does not match the configured value, then the DSCP received is used in the outgoing response packet.

If dscp-value is specified with the force option, then the configured DSCP value is set in all outgoing packets.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure a DSCP value: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma LMA domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)# dscp control-plane 45

dscp control-plane (pmipv6-lma-mag)

To configure the value of Differentiated Services Code Point (DSCP) in the outgoing PMIPv6 control plane messages to the peering Mobile Access Gateway (MAG), use the dscp control-plane command in PMIPv6 LMA MAG configuration mode. To disable DSCP value configuration, use the no form of this command.

dscp control-plane dscp-value [ force ]

no dscp control-plane dscp-value [ force ]

Syntax Description

dscp-value

DSCP value. It can have a value between 1 and 63.

Command Default

None.

Command Modes

PMIPv6 LMA MAG configuration

Command History

Release Modification

Release 5.3.0

This command was introduced.

Usage Guidelines

This command overrides the dscp control-plane command configured at LMA global level. The outgoing PMIPv6 control plane messages include locally generated packets such as Proxy Binding Revocation Indications (PBRIs), Proxy Binding Revocation Acknowledgments (PBRAs), Heartbeat Requests, and packets sent in response to packets received from MAG such as Proxy Binding Acknowledgments (PBAs), PBRIs, PBRAs, and Heartbeat Responses.

If dscp-value is not specified, then the DSCP received in a request is used in the outgoing response packet. DSCP is not set in the other outgoing packets.

If dscp-value is specified without the force option:

  • The configured DSCP value is set in locally generated packets.

  • If the received packet does not have DSCP marking, the configured value is set in the outgoing packet.

  • If the received packet has DSCP marking that matches the configured value, then the DSCP received is set in the outgoing response packet.

  • If the received packet has DSCP marking that does not match the configured value, then the DSCP received is used in the outgoing response packet.

If dscp-value is specified with the force option, then the configured DSCP value is set in all outgoing packets.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure a DSCP value: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma LMA domain cisco.com
RP/0/RSP0/CPU0:router(config-pmipv6-lma)# mag mag1 dn1
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mag)# dscp control-plane 30

dynamic mag learning

To enable local mobility anchor (LMA) to accept proxy mobile IPv6 (PMIPv6) signaling messages from any MAG that is not locally configured, use the dynamic mag learning command in PMIPv6 LMA configuration mode. To enable the LMA to reject the PMIPv6 signaling messages from any MAG that is not locally configured, use the no form of the command.

dynamic mag learning

no dynamic mag learning

Syntax Description

This command has no keywords or arguments.

Command Default

LMA does not accept PMIPv6 signaling messages from any MAG that is not locally configured.

Command Modes

PMIPv6 LMA configuration

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to enable LMA to accept proxy mobile IPv6 (PMIPv6) signaling messages from any MAG that is not locally configured: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma lma1 domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)#dynamic mag learning

enforce heartbeat-to-mag (pmipv6-lma)

To enforce the values of Local Mobility Anchor (LMA) heartbeat parameters on the Mobile Access Gateway (MAG), use the enforce heartbeat-to-mag command in PMIPv6 LMA configuration mode. To disable this enforcement, use the no form of this command.

enforce heartbeat-to-mag

no enforce heartbeat-to-mag

Syntax Description

This command has no keywords or arguments.

Command Default

None.

Command Modes

PMIPv6 LMA configuration

Command History

Release Modification

Release 5.3.1

This command was introduced.

Usage Guidelines

Use this command to enforce on the MAG the values of heartbeat parameters (interval, retries and timeout) that are configured on the LMA either at the global level or at the peer/customer level. If heartbeat is configured both at the global and peer/customer levels, the values to be enforced on the MAG are used from the peer/customer level.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to enforce heartbeat values on the MAG: 


RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma LMA domain cisco.com
RP/0/RSP0/CPU0:router(config-pmipv6-lma)# enforce heartbeat-to-mag

heartbeat (pmipv6-lma)

To configure Local Mobility Anchor (LMA) heartbeat options, use the heartbeat interval command in PMIPv6 LMA configuration mode. To disable LMA heartbeat options, use the no form of this command.

heartbeat interval interval-value retries retries-value timeout timeout-value

no heartbeat interval interval-value retries retries-value timeout timeout-value

Syntax Description

interval-value

Interval between two heartbeat messages in seconds. It can have a value between 10 and 3600.

retries-value

Number of retries (in the absence of reply from the peer) before the path to the peer is declared as down. It can have a value between 1 and 10.

timeout-value

Timeout value to wait for a response from the peer after which the request is declared as timed out.

Command Default

None.

Command Modes

PMIPv6 LMA configuration

Command History

Release Modification

Release 5.3.0

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure heartbeat options for LMA: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma LMA domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)# heartbeat interval 20 retries 5 timeout 10

heartbeat (pmipv6-lma-mll-cust)

To configure customer-specific heartbeat options in a Local Mobility Anchor (LMA) within a Mobile Local Loop (MLL), use the heartbeat interval command in PMIPv6 LMA MLL Customer configuration mode. To disable customer-specific heartbeat options, use the no form of this command.

heartbeat interval interval-value retries retries-value timeout timeout-value

no heartbeat interval interval-value retries retries-value timeout timeout-value

Syntax Description

interval-value

Interval between two heartbeat messages in seconds. It can have a value between 10 and 3600.

retries-value

Number of retries (in the absence of reply from the peer) before the path to the peer is declared as down. It can have a value between 1 and 10.

timeout-value

Timeout value to wait for a response from the peer after which the request is declared as timed out.

Command Default

None.

Command Modes

PMIPv6 LMA MLL Customer configuration

Command History

Release Modification

Release 5.3.0

This command was introduced.

Usage Guidelines

This command overrides the global LMA heartbeat configuration.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure heartbeat options for a customer: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma LMA domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)# mobility-service mobile-local-loop
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll)# customer CUST1 vrf VRF1
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll-cust)# heartbeat interval 30 retries 10 timeout 10

hnp

To configure maximum home network prefix (HNP) that a mobile node can posses, use the hnp command in PMIPv6 LMA configuration mode. To remove the configured HNP number, use the no form of this command.

hnp maximum number

no hnp maximum number

Syntax Description

maximum number

Specifies the maximum allowed number of HNPs associated with a mobile node.

Command Default

None.

Command Modes

PMIPv6 LMA configuration

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure two HNPs for a mobile node: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma lma1 domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)#hnp maximum 2

ipv6 mobile pmipv6-domain

To configure the Proxy Mobile IPv6 (PMIPv6) domain, use the ipv6 mobile pmipv6-domain command in Global Configuration mode. To remove the PMIPV6 domain configuration, use the no form of this command.

ipv6 mobile pmipv6-domain domain-name

no ipv6 mobile pmipv6-domain domain-name

Syntax Description

domian-name

Specifies PMIPV6 domain name.

Command Default

No PMIPv6 domain is configured.

Command Modes

Global Configuration mode

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to enter PMIPv6 domain configuration mode and configure the PMIPv6 domain: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-domain)#

ipv6 mobile pmipv6-lma

To enable Local Mobility Anchor (LMA) service on the router, use the ipv6 mobile pmipv6-lma command in Global Configuration mode. To disable the LMA service, use the no form of this command.

ipv6 mobile pmipv6-lma lma-name domain domain-name

no ipv6 mobile pmipv6-lma lma-name domain domain-name

Syntax Description

lma-name

Specifies LMA name. This can be an instance name or any string that uniquely identifies the LMA.

domain domain-name

Specifies the PMIP domain to which the LMA belongs.

Command Default

LMA service on the router is not configured.

Command Modes

Global Configuration mode

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure the LMA: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma lma1 domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)#

ipv4-address

To configure the IPv4 address for a MAG within an LMA, use the ipv4-address command in the PMIPv6 LMA-MAG configuration mode. To remove the IPv4 address for the MAG, use the no form of this command.

ipv4-address ipv4-address

no ipv4-address ipv4-address

Syntax Description

ipv4-address

The IPv4 address for the MAG.

Command Default

No IPv4 address is configured for the MAG.

Command Modes

PMIPv6 LMA-MAG configuration

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure the IPv4 address for the MAG within the PMIPv6 LMA: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma lma1 domain DOMAIN1
RP/0/RSP0/CPU0:router(config-pmipv6-lma)#mag mag1 DOMAIN2 
RP/0/RSP0/CPU0:router(config-pmipv6-lma-mag)#ipv4-address 192.168.12.3

ipv6-address

To configure the IPv6 address for a MAG within an LMA, use the ipv6-address command in the PMIPv6 LMA-MAG configuration mode. To remove the IPv6 address for the MAG, use the no form of this command.

ipv6-address ipv6-address

no ipv6-address ipv6-address

Syntax Description

ipv6-address

The IPv6 address for the MAG.

Command Default

No IPv6 address is configured for the MAG.

Command Modes

PMIPv6 LMA-MAG configuration

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure the IPv6 address for the MAG within the PMIPv6 LMA: 


RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma lma1 domain DOMAIN1
RP/0/RSP0/CPU0:router(config-pmipv6-lma)#mag mag1 DOMAIN2 
RP/0/RSP0/CPU0:router(config-pmipv6-lma-mag)#ipv6-address 2010:DB::1

lma

To specify the Local Mobility Anchors (LMAs), or to configure the LMA for the Mobile Access Gateway (MAG), use the lma command in the appropriate configuration mode. To disable the LMA configuration, use the no form of this command

lma lma-identifier

no lma lma-identifier

Syntax Description

lma-identifier

Specifies LMA identifier.

Command Default

None.

Command Modes

PMIPv6 domain configuration

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure the LMA in PMIPv6 domain configuration mode: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-domain)#lma lma1 
RP/0/RSP0/CPU0:router(config-pmipv6-domain-lma)#

mag

To configure the Mobile Access Gateway (MAG) within the Proxy Mobile IPv6 (PMIPv6) domain or to configure the MAG within a Local Mobility Anchor (LMA), use the mag command in the PMIPv6 domain configuration mode or LMA configuration mode. To disable the MAG configuration, use the no form of this command

mag identifier domain-name

Syntax Description

identifier

MAG identifier.

domain-name

PMIPv6 domain identifier.

Command Default

The LMA within the PMIPV6 domain is not configured.

Command Modes

PMIPv6 LMA configuration

PMIPv6 domain configuration

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure the MAG in the PMIPv6 LMA: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma lma1 domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)#mag mag1 dn1 
RP/0/RSP0/CPU0:router(config-pmipv6-lma-mag)#

mnp (pmipv6-lma-mll)

To configure the maximum number of mobile network prefixes on a per address family, per logical mobile network (MN), and per customer basis, use the mnp command in PMIPv6 LMA Mobile Local Loop (MLL) configuration mode. As the maximum number is configured at the MLL service level, the configured values apply to all the customers configured under this service except for the customers for whom these values are configured explicitly under customer configuration. To disable the configuration, use the no form of this command.

mnp {ipv4 | ipv6 | afi-all } {logical-mn | customer } maximum number

no mnp {ipv4 | ipv6 | afi-all } {logical-mn | customer } maximum number

Syntax Description

ipv4

Specifies the limit for IPv4 prefixes.

ipv6

Specifies the limit for IPv6 prefixes.

afi-all

Specifies the limit for the aggregate of IPv4 and IPv6 prefixes.

logical-mn

Specifies the limit for every logical MN belonging to all customers.

customer

Specifies the limit for every customer across all of its logical MNs.

maximum number

Specifies the maximum number of prefixes.

Command Default

None.

Command Modes

PMIPv6 LMA MLL configuration

Command History

Release Modification

Release 5.3.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure the limit for IPv4 prefixes: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma LMA domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)# mobility-service mobile-local-loop
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll)# mnp ipv4 logical-mn maximum 10

mnp (pmipv6-lma-mll-cust)

To configure the maximum number of mobile network prefixes on a per address family, per logical mobile network (MN), and per customer basis, use the mnp command in PMIPv6 LMA Mobile Local Loop (MLL) Customer configuration mode. This configuration overrides the prefix limits configured at the MLL service level. To disable the configuration, use the no form of this command.

mnp {ipv4 | ipv6 | afi-all } {logical-mn | customer } maximum number

no mnp {ipv4 | ipv6 | afi-all } {logical-mn | customer } maximum number

Syntax Description

ipv4

Specifies the limit for IPv4 prefixes.

ipv6

Specifies the limit for IPv6 prefixes.

afi-all

Specifies the limit for the aggregate of IPv4 and IPv6 prefixes.

logical-mn

Sets the limit for every logical MN belonging to the specified customer.

customer

Sets the limit for the specified customer across all of its logical MNs.

maximum number

Specifies the maximum number of prefixes.

Command Default

None.

Command Modes

PMIPv6 LMA MLL Customer configuration

Command History

Release Modification

Release 5.3.2

This command was introduced.

Usage Guidelines

This command overrides the prefix limits configured at the MLL service level.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure the limit for IPv4 prefixes: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma LMA domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)# mobility-service mobile-local-loop
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll)# customer CUST1 vrf VRF1
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll-cust)# mnp ipv4 logical-mn maximum 10

mobility-service mobile-local-loop

To configure Mobile Loop Local (MLL) service on the Local Mobility Anchor (LMA), use the mobility-service mobile-local-loop command in PMIPv6 LMA configuration mode. To disable the MLL service, use the no form of this command.

mobility-service mobile-local-loop

no mobility-service mobile-local-loop

Command Default

None.

Command Modes

PMIPv6 LMA configuration

Command History

Release Modification

Release 5.3.0

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure the MLL service: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma LMA domain cisco.com
RP/0/RSP0/CPU0:router(config-pmipv6-lma)# mobility-service mobile-local-loop
RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll)#

network

To associate a network, to which an IPv4 or IPv6 pool can be configured, with a Local Mobility Anchor (LMA), use the network command in LMA configuration mode. To disassociate the network from the LMA, use the no form of this command.

network name

no network name

Syntax Description

name

Name of the network to be associated with the LMA.

Command Default

No network is associated.

Command Modes

PMIPv6 LMA configuration

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to associate a network with an LMA: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma lma1 domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)#network cisco
RP/0/RSP0/CPU0:router(config-pmipv6-lma-network)#

network (pmipv6-lma-mll-cust)

To associate a customer-specific network (to which an IPv4 or IPv6 pool can be configured) in a Local Mobility Anchor (LMA) within a Mobile Local Loop (MLL), use the network command in PMIPv6 LMA MLL Customer configuration mode. To remove an existing customer-specific network, use the no form of this command.

network { unauthorized | authorized network-name }

no network { unauthorized | authorized network-name }

Syntax Description

network-name

Name of the network to be associated with a customer.

Command Default

None.

Command Modes

PMIPv6 LMA MLL Customer configuration

Command History

Release Modification

Release 5.3.0

This command was introduced.

Usage Guidelines

Use the unauthorized keyword to configure an unauthorized network. In this case, no network pools are configured for address assignment. The address/prefix of the Logical Mobile Node (LMN) on the Mobile Access Gateway (MAG) and the network prefixes on the Mobile Network interfaces are accepted as received in the Proxy Binding Update (PBU).

Use the authorized keyword to configure a named network. In this case, the address/prefix of the LMN and Mobile Network prefixes are validated against the configured network pool. The uniqueness of the named network is ensured.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to associate a network with a customer: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma LMA domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)# mobility-service mobile-local-loop
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll)# customer CUST1 vrf VRF1
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll-cust)# network authorized cisco
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll-cust-network)#

nai (pmipv6-domain)

To configure the network access identifier (NAI) for the mobile node (MN) within the PMIPv6 domain, use the nai command in PMIPv6 domain configuration mode. To disable the NAI configuration, use the no form of this command.

nai [user]@realm

no nai [user]@realm

Syntax Description

[user]@realm

Fully qualified specific user address and realm. The @ symbol is required.

You can specify @realm for any user address at a specific realm.

Command Default

NAI for the MN is not specified.

Command Modes

PMIPv6 domain configuration

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure the NAI within the PMIPv6 domain: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-domain)# nai example@example.com
RP/0/RSP0/CPU0:router(config-pmipv6-domain-nai)#

pool (pmipv6)

To specify the IPv4 or IPv6 address pool, from which a home address is allocated to a mobile node (MN), in a Local Mobility Anchor (LMA), use the pool command in LMA-network configuration mode. To disassociate an IPv4 or IPv6 address pool from an LMA, use the no form of this command.

pool {mobile-node | mobile-network} {ipv4 | ipv6} start-address address pool-prefix length network-prefix length

no pool {mobile-node | mobile-network} {ipv4 | ipv6} start-address address pool-prefix length network-prefix length

Syntax Description

mobile-node

Specifies pool configuration for mobile nodes.

mobile-network

Specifies pool configuration for mobile networks.

ipv4

Specifies IPv4 address pool.

ipv6

Specifies IPv6 address pool.

start-address address

Specifies address pool start address.

pool-prefix length

Specifies the prefix length of the pool address.

The range is from 8 to 30.

network-prefix length

Specifies the network prefix length of the pool address. This argument is applicable for mobile network.

The range is from 8 to 32.

Command Default

None.

Command Modes

PMIPv6 LMA network configuration

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to specify the IPv4 address pool in an LMA: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma lma1 domain cisco.com
RP/0/RSP0/CPU0:router(config-pmipv6-lma)# network n1
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-network)# pool mobile-network ipv4 start-address 192.168.20.2 pool-prefix 22 network-prefix 8

pool (pmipv6-mll-cust-network)

To specify the IPv4 or IPv6 address pool for a customer-specific network in a Local Mobility Anchor (LMA) within a Mobile Local Loop (MLL), use the pool command in PMIPv6 LMA MLL Customer Network configuration mode. To disassociate an IPv4 or IPv6 address pool from a customer, use the no form of this command.

pool {mobile-node | mobile-network} {ipv4 | ipv6} start-address address pool-prefix length network-prefix length

no pool {mobile-node | mobile-network} {ipv4 | ipv6} start-address address pool-prefix length network-prefix length

Syntax Description

mobile-node

Specifies pool configuration for mobile nodes.

mobile-network

Specifies pool configuration for mobile networks.

ipv4

Specifies IPv4 address pool.

ipv6

Specifies IPv6 address pool.

start-address address

Specifies address pool start address.

pool-prefix length

Specifies the prefix length of the pool address.

The range is from 8 to 30. For ipv6 option, the range is from 8 to 62.

network-prefix length

Specifies the network prefix length of the pool address. This argument is applicable for mobile network.

The range is from 8 to 32. For ipv6 option, the range is from 8 to 64.

Command Default

None.

Command Modes

PMIPv6 LMA MLL Customer Network configuration

Command History

Release Modification

Release 5.3.0

This command was introduced.

Usage Guidelines

Use this command only if you have configured a named network using the network authorized command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to specify customer-specific IPv4 address pool in an LMA: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma LMA domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)# mobility-service mobile-local-loop
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll)# customer CUST1 vrf VRF1
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll-cust)# network authorized cisco
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll-cust-network)# pool mobile-network ipv4 start-address 192.168.20.2 pool-prefix 22 network-prefix 8

redistribute home-address (pmipv6-lma)

To enable redistribution of Home Address (HoA) and Home Network prefix (HNP) routes into routing protocols, use the redistribute home-address command in PMIPv6 LMA configuration mode. To disable redistribution of HoA and HNP routes, use the no form of this command.

redistribute home-address { host-prefix | disable }

no redistribute home-address { host-prefix | disable }

Syntax Description

host-prefix

Enables redistribution of HoA host prefix and HNP. If HoA and HNP are assigned from pools configured on the LMA, the pool prefixes are not redistributed.

disable

Disables redistribution of HoA host prefix and HNP as well as HoA/HNP pool prefixes.

Command Default

None.

Command Modes

PMIPv6 LMA configuration

Command History

Release Modification

Release 5.3.1

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to enable redistribution of HoA host prefix and HNP: 


RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma LMA domain cisco.com
RP/0/RSP0/CPU0:router(config-pmipv6-lma)# redistribute home-address host-prefix

replay-protection

To configure the replay protection mechanism within the Proxy Mobile IPv6 (PMIPv6) Local Mobility Anchor (LMA), use the replay-protection command in the PMIPv6 LMA configuration mode. To reset the replay protection mechanism to default window time, use the no form of this command.

replay-protection timestamp window seconds

no replay-protection timestamp

Syntax Description

timestamp

Enables the timestamp.

window seconds

Specifies the maximum time difference, in seconds, between the time stamp in the received Proxy Binding Update (PBU) message and the current time of the day on the Local Mobility Anchor (LMA).

The range is 1-255 seconds.

Command Default

The replay protection mechanism is configured with the default time stamp window period of 7 seconds.

Command Modes

PMIPv6 LMA configuration

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure the replay protection mechanism with a window period of 150 seconds within PMIPv6 LMA: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma lma1 domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)#replay-protection timestamp window 150

This example shows how to reset the replay protection mechanism to default window period within PMIPv6 LMA: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma lma1 domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)#no replay-protection timestamp

show ipv6 mobile pmipv6 lma binding

To display the list of the Local Mobility Anchor (LMA) bindings established over the Proxy Mobile IPv6 (PMIPv6) signaling plane, use the show ipv6 mobile pmipv6 lma binding command in EXEC mode.

show ipv6 mobile pmipv6 lma bindings{ nai nai-string| mag mag-identifier}

Syntax Description

nai nai-string

Displays the bindings for the mobile node (MN).

mag mag-identifier

Displays the bindings for the Mobile Access Gateway (MAG).

Command Default

None.

Command Modes

EXEC mode

Command History

Release Modification

Release 5.2.2

This command was introduced.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read

Examples

This is the sample output for the show ipv6 mobile pmipv6 lma binding command: 

RP/0/RSP0/CPU0:router#  show ipv6 mobile pmipv6 lma binding
----------------------------------------
[Binding][MN]: State: BCE_ACTIVE
[Binding][MN]: NAI: MAG@HDFC
[Binding][MN]: HOA: 10.10.10.150, Prefix: 24
[Binding][MN]: HNP: 2002:10::1
[Binding][MN][PEER]: Default Router: 10.10.10.1
        [Binding][MN]: ATT: (4) 
                [Binding][MN][PEER1]:LLID: MAG@HDFC
                [Binding][MN][PEER1]: Id: MAG1
                [Binding][MN][PEER1]: Lifetime: 3600(sec)
                [Binding][MN][PEER1]: Lifetime Remaining: 3219(sec)
                [Binding][MN][PEER1]: Tunnel: tunnel-ip65536
                [Binding][MN][GREKEY]: Upstream: 0, Downstream: 0
----------------------------------------

show ipv6 mobile pmipv6 lma globals

To display the global configuration details of the Local Mobility Anchor (LMA) or a specific customer, use the show ipv6 mobile pmipv6 lma globals command in EXEC mode.

show ipv6 mobile pmipv6 lma globals [ customer customer-name ]

Syntax Description

customer customer-name

(Optional) Displays global configuration details of a specific customer.

Command Default

None.

Command Modes

EXEC mode

Command History

Release Modification

Release 5.2.2

This command was introduced.

Release 5.3.2

The customer customer-name keyword was added to this command.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read

Examples

This is an example of global LMA configuration details: 

RP/0/RSP0/CPU0:router#  show ipv6 mobile pmipv6 lma globals
---------------------------------------------------
Domain  : D1

LMA Identifier  : LMA
        AAA Accounting                  : Enabled
        Max Bindings                    : 10000
        AuthOption                      : disabled
        RegistrationLifeTime            : 3600 (sec)
        BRI InitDelayTime               : 1000 (msec)
        BRI MaxDelayTime                : 2000 (msec)
        BRI MaxRetries                  : 1
        EncapType                       : IPV6_IN_IPV6
        RefreshTime                     : 300 (sec)
        Refresh RetxInit time           : 1000 (msec)
        Refresh RetxMax time            : 32000 (msec)
        Timestamp option                : enabled
        Validity Window                 : 7
        Service                         : Mobile Local Loop service enabled
        Dynamic MAG Learning            : enabled
        Max IPv4 LMN prefixes           : 16
        Max IPv6 LMN prefixes           : 16
        Max LMN prefixes                : 20
        Max IPv4 Customer prefixes      : 2000
        Max IPv6 Customer prefixes      : 2000
        Max Customer prefixes           : 2000


Customer: CUST1
        VRF                             : VRF1
        AuthOption                      : enabled

Customer: CUST2
        VRF                             : VRF2
        AuthOption                      : disabled

Peer :  MAG1
        AuthOption                      : enabled
        EncapType                       : GRE in IPV4

Network :cisco
        IPv4 Pool prefix                : 10.10.10.1 (24)
        IPv6 Pool prefix                : 2002:10::1 (62)
---------------------------------------------------

This is an example of global configuration details of a customer: 

RP/0/RSP0/CPU0:router#  show ipv6 mobile pmipv6 lma globals customer CUST1

Customer: CUST1
        VRF                             : VRF1
        AuthOption                      : enabled
MLL Service Globals:
        Ignore hoa                      : disabled
        Max IPv4 LMN prefixes           : 12
        Max IPv6 LMN prefixes           : 6
        Max LMN prefixes                : 16
        Max IPv4 Customer prefixes      : 3000000
        Max IPv6 Customer prefixes      : 1000000
        Max Customer prefixes           : 3000000
---------------------------------------------------

show ipv6 mobile pmipv6 lma stats

To display the global Local Mobility Anchor (LMA) statistics, use the show ipv6 mobile pmipv6 lma stats command in EXEC mode.

show ipv6 mobile pmipv6 lma stats [ domain domain-name peer peer-name | customer customer-name ]

Syntax Description

domain domain-name

(Optional) Displays the Proxy Mobile IPv6 (PMIPv6) domain information.

peer peer-name

(Optional) Displays the Mobile Access Gateway (MAG) information.

customer customer-name

(Optional) Displays statistics corresponding to a specific customer.

Command Default

None.

Command Modes

EXEC mode

Command History

Release Modification

Release 5.2.2

This command was introduced.

Release 5.3.1

The keyword customer customer-name was added to this command.

Release 5.3.2

The output of this command has been updated.

Usage Guidelines

No specific guidelines impact the use of this command.

Task ID

Task ID Operation

ipv6

read

Examples

This is an example of global LMA statistics: 

RP/0/RSP0/CPU0:router#  show ipv6 mobile pmipv6 lma stats 
[LMA] Stats: Total Bindings : 2
Proxy Binding Update Received Stats
                 Total: 26                                Drop: 0
AAA Accounting Stats
         Start Accounting Sent: 4                 Stop Accounting Sent: 0
-------------------------------------------------
Proxy Binding Acknowledgment Sent Stats
                         Total: 26                                Drop: 0
                   BA_ACCEPTED: 26                          BA_UNKNOWN: 0
                BA_UNSPEC_FAIL: 0                        BA_ADMIN_FAIL: 0
              BA_RESOURCE_FAIL: 0                       BA_HM_REG_FAIL: 0
             BA_HM_SUBNET_FAIL: 0                      BA_BAD_SEQ_FAIL: 0
                BA_CHANGE_FAIL: 0                         BA_AUTH_FAIL: 0
         PROXY_REG_NOT_ENABLED: 0                  NOT_LMA_FOR_THIS_MN: 0
    MAG_NOT_AUTH_FOR_PROXY_REG: 0               NOT_AUTHORIZED_FOR_HNP: 0
            TIMESTAMP_MISMATCH: 0            TIMESTAMP_LOWER_THAN_PREV: 0
            MISSING_HNP_OPTION: 0         BCE_PBU_PFX_SET_DO_NOT_MATCH: 0
  MISSING_MN_IDENTIFIER_OPTION: 0                    MISSING_HI_OPTION: 0
    NOT_AUTH_FOR_IPV4_MOBILITY: 0       NOT_AUTH_FOR_IPV4_HOME_ADDRESS: 0
    NOT_AUTH_FOR_IPV6_MOBILITY: 0         MULTIPLE_IPV4_HOA_NO_SUPPORT: 0
   GRE_KEY_OPTION_NOT_REQUIRED: 0
-------------------------------------------------
Proxy Binding Revocation Acknowledgment Received Stats
                         Total: 0                                 Drop: 0
                    BR_SUCCESS: 0                   BR_PARTIAL_SUCCESS: 0
                 BR_NO_BINDING: 0                      BR_HOA_REQUIRED: 0
      BR_GLOBAL_REVOC_NOT_AUTH: 0              BR_MN_IDENTITY_REQUIRED: 0
                BR_MN_ATTACHED: 0             BR_UNKNOWN_REVOC_TRIGGER: 0
   BR_REVOC_FUNC_NOT_SUPPORTED: 0           BR_PBR_NOT_SUPPORTED_STATS: 0
-------------------------------------------------
Proxy Binding Revocation Acknowledgment Sent Stats
                         Total: 0                                 Drop: 0
                    BR_SUCCESS: 0                   BR_PARTIAL_SUCCESS: 0
                 BR_NO_BINDING: 0                      BR_HOA_REQUIRED: 0
      BR_GLOBAL_REVOC_NOT_AUTH: 0              BR_MN_IDENTITY_REQUIRED: 0
                BR_MN_ATTACHED: 0             BR_UNKNOWN_REVOC_TRIGGER: 0
   BR_REVOC_FUNC_NOT_SUPPORTED: 0           BR_PBR_NOT_SUPPORTED_STATS: 0
-------------------------------------------------
Proxy Binding Revocation Indication Received Stats
                         Total: 0                                 Drop: 0
                BR_UNSPECIFIED: 0                      BR_ADMIN_REASON: 0
      BR_MAG_HANDOVER_SAME_ATT: 0             BR_MAG_HANDOVER_DIFF_ATT: 0
       BR_MAG_HANDOVER_UNKNOWN: 0             BR_USER_SESS_TERMINATION: 0
   BR_NETWORK_SESS_TERMINATION: 0             BR_OUT_OF_SYNC_BCE_STATE: 0
            BR_PER_PEER_POLICY: 0          BR_REVOKING_MN_LOCAL_POLICY: 0
-------------------------------------------------
Proxy Binding Revocation Indication Sent Stats
                         Total: 0                                 Drop: 0
                BR_UNSPECIFIED: 0                      BR_ADMIN_REASON: 0
      BR_MAG_HANDOVER_SAME_ATT: 0             BR_MAG_HANDOVER_DIFF_ATT: 0
       BR_MAG_HANDOVER_UNKNOWN: 0             BR_USER_SESS_TERMINATION: 0
   BR_NETWORK_SESS_TERMINATION: 0             BR_OUT_OF_SYNC_BCE_STATE: 0
            BR_PER_PEER_POLICY: 0          BR_REVOKING_MN_LOCAL_POLICY: 0
-------------------------------------------------
MM Stats
               Rcvd V4 Packets: 0                      Sent V4 Packets: 0
           Rcvd V4 Packet Drop: 0                  Send V4 Packet Drop: 0
               Rcvd V6 Packets: 0                      Sent V6 Packets: 0
           Rcvd V6 Packet Drop: 0                  Send V6 Packet Drop: 0
                Checksum Error: 0
-------------------------------------------------
Tenant Stats
  Number of single tenant MAGs: 2         Number of multi tenant MAGs: 0

This is an example of statistics specific to a customer: 

RP/0/RSP0/CPU0:router#  show ipv6 mobile pmipv6 lma stats customer CUST1

[LMA] Stats: Total Bindings : 1
Proxy Binding Update Received Stats
                         Total: 13                                Drop: 0
AAA Accounting Stats
         Start Accounting Sent: 2                 Stop Accounting Sent: 0
-------------------------------------------------
Proxy Binding Acknowledgment Sent Stats
                         Total: 13                                Drop: 0
                   BA_ACCEPTED: 13                          BA_UNKNOWN: 0
                BA_UNSPEC_FAIL: 0                        BA_ADMIN_FAIL: 0
              BA_RESOURCE_FAIL: 0                       BA_HM_REG_FAIL: 0
             BA_HM_SUBNET_FAIL: 0                      BA_BAD_SEQ_FAIL: 0
                BA_CHANGE_FAIL: 0                         BA_AUTH_FAIL: 0
         PROXY_REG_NOT_ENABLED: 0                  NOT_LMA_FOR_THIS_MN: 0
    MAG_NOT_AUTH_FOR_PROXY_REG: 0               NOT_AUTHORIZED_FOR_HNP: 0
            TIMESTAMP_MISMATCH: 0            TIMESTAMP_LOWER_THAN_PREV: 0
            MISSING_HNP_OPTION: 0         BCE_PBU_PFX_SET_DO_NOT_MATCH: 0
  MISSING_MN_IDENTIFIER_OPTION: 0                    MISSING_HI_OPTION: 0
    NOT_AUTH_FOR_IPV4_MOBILITY: 0       NOT_AUTH_FOR_IPV4_HOME_ADDRESS: 0
    NOT_AUTH_FOR_IPV6_MOBILITY: 0         MULTIPLE_IPV4_HOA_NO_SUPPORT: 0
   GRE_KEY_OPTION_NOT_REQUIRED: 0
-------------------------------------------------
Proxy Binding Revocation Acknowledgment Received Stats
                         Total: 0                                 Drop: 0
                    BR_SUCCESS: 0                   BR_PARTIAL_SUCCESS: 0
                 BR_NO_BINDING: 0                      BR_HOA_REQUIRED: 0
      BR_GLOBAL_REVOC_NOT_AUTH: 0              BR_MN_IDENTITY_REQUIRED: 0
                BR_MN_ATTACHED: 0             BR_UNKNOWN_REVOC_TRIGGER: 0
   BR_REVOC_FUNC_NOT_SUPPORTED: 0           BR_PBR_NOT_SUPPORTED_STATS: 0

-------------------------------------------------
Proxy Binding Revocation Acknowledgment Sent Stats
                         Total: 0                                 Drop: 0
                    BR_SUCCESS: 0                   BR_PARTIAL_SUCCESS: 0
                 BR_NO_BINDING: 0                      BR_HOA_REQUIRED: 0
      BR_GLOBAL_REVOC_NOT_AUTH: 0              BR_MN_IDENTITY_REQUIRED: 0
                BR_MN_ATTACHED: 0             BR_UNKNOWN_REVOC_TRIGGER: 0
   BR_REVOC_FUNC_NOT_SUPPORTED: 0           BR_PBR_NOT_SUPPORTED_STATS: 0
-------------------------------------------------
Proxy Binding Revocation Indication Received Stats
                         Total: 0                                 Drop: 0
                BR_UNSPECIFIED: 0                      BR_ADMIN_REASON: 0
      BR_MAG_HANDOVER_SAME_ATT: 0             BR_MAG_HANDOVER_DIFF_ATT: 0
       BR_MAG_HANDOVER_UNKNOWN: 0             BR_USER_SESS_TERMINATION: 0
   BR_NETWORK_SESS_TERMINATION: 0             BR_OUT_OF_SYNC_BCE_STATE: 0
            BR_PER_PEER_POLICY: 0          BR_REVOKING_MN_LOCAL_POLICY: 0
-------------------------------------------------
Proxy Binding Revocation Indication Sent Stats
                         Total: 0                                 Drop: 0
                BR_UNSPECIFIED: 0                      BR_ADMIN_REASON: 0
      BR_MAG_HANDOVER_SAME_ATT: 0             BR_MAG_HANDOVER_DIFF_ATT: 0
       BR_MAG_HANDOVER_UNKNOWN: 0             BR_USER_SESS_TERMINATION: 0
   BR_NETWORK_SESS_TERMINATION: 0             BR_OUT_OF_SYNC_BCE_STATE: 0
            BR_PER_PEER_POLICY: 0          BR_REVOKING_MN_LOCAL_POLICY: 0
-------------------------------------------------
Mobile Network Stats
           Number of IPv4 MNPs: 1                  Number of IPv6 MNPs: 0

transport (pmipv6-lma-mll-cust)

To configure customer-specific transport options in a Local Mobility Anchor (LMA) within a Mobile Local Loop (MLL), use the transport command in PMIPv6 LMA MLL Customer configuration mode. To disable customer-specific transport options, use the no form of this command.

transport [ vrf vrf-name ]

no transport [ vrf vrf-name ]

Syntax Description

vrf-name

Name of the VRF.

Command Default

None.

Command Modes

PMIPv6 LMA MLL Customer configuration

Command History

Release Modification

Release 5.3.0

This command was introduced.

Usage Guidelines

Transport options include peering or transport VRF and the LMA IPv4 and/or IPv6 addresses. The addresses are configured in the transport configuration mode using the address command.

A customer can have multiple transports and can have the same addresses in all transports. However, each customer must have a unique IPv4 and/or a unique IPv6 address.


Note

If the transport is in global VRF, then the vrf keyword and vrf-name can be omitted in this command.

Task ID

Task ID Operation

ipv6

read, write

Examples

This example shows how to configure transport options for a customer: 

RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# ipv6 mobile pmipv6-lma LMA domain cisco.com
 RP/0/RSP0/CPU0:router(config-pmipv6-lma)# mobility-service mobile-local-loop
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll)# customer CUST1 vrf VRF1
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll-cust)# transport vrf TVRF1
 RP/0/RSP0/CPU0:router(config-pmipv6-lma-mll-cust-tpt)#