Cisco Cisco Packet Data Gateway (PDG)
LMA Service Configuration Mode Commands
heartbeat ▀
Command Line Interface Reference, StarOS Release 17 ▄
6865
heartbeat
Configures the PMIPv6 heartbeat message interval, retransmission timeout, and max retransmission for the LMA
Service.
Service.
Product
P-GW
Privilege
Administrator
Syntax
heartbeat { interval seconds | retransmission { max number | timeout seconds } }
default heartbeat { interval | retransmission { max | timeout } }
no heartbeat
no
Disables the PMIPv6 heartbeat functionality. The P-GW starts sending heartbeat request to peers when the
heartbeat interval is configured.
heartbeat interval is configured.
default
Resets the specified parameter to the system default value.
interval seconds
The interval in seconds at which heartbeat messages are sent.
seconds
is an integer from 30 through 3600.
Default: 60
retransmission max number
The maximum number of heartbeat retransmissions allowed.
number
is an integer from 1 through 15.
Default: 3
retransmission timeout seconds
The timeout in seconds for heartbeat retransmissions.
seconds
is an integer from 1 through 20.
Default: 3
Usage
Proxy Mobile IPv6 (PMIPv6) is a network-based mobility management protocol to provide mobility without
requiring the participation of the mobile node in any PMIPv6 mobility related signaling. The Local Mobility
Anchor (LMA) service sets up tunnels dynamically to manage mobility for a mobile node.
This command provides configuration of heartbeat messages between the LMA and MAG services to know
the reachability of the peers, to detect failures, quickly inform peers in the event of a recovery from node
failures, and allow a peer to take appropriate action.
requiring the participation of the mobile node in any PMIPv6 mobility related signaling. The Local Mobility
Anchor (LMA) service sets up tunnels dynamically to manage mobility for a mobile node.
This command provides configuration of heartbeat messages between the LMA and MAG services to know
the reachability of the peers, to detect failures, quickly inform peers in the event of a recovery from node
failures, and allow a peer to take appropriate action.