> MAG Service Configuration Mode Commands
> The MAG Service Configuration Mode is used to create and manage a Mobility Access Gateway service in an HSGW (eHRPD network) or a P-MIP S-GW (LTE-SAE network). The MAG is the PMIP client and communicates with the Local Mobility Anchor (LMA) configured on a PDN Gateway.
> bind address
> Binds the 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.
> Product
> HSGW, S-GW
> Privilege
> Administrator
> Syntax
> bind address ip_address [ max-subscribers num ]
> no bind address
> no
> Removes the interface binding from this service.
> ip_address
> Specifies the IPv6 address of the interface configured as the S5/S8 interface. ip_address is specified in colon separated notation.
> max-subscribers num
> Default: 1500000
> Specifies the maximum number of subscribers that can access this service on this interface. num must be configured to an integer between 0 and 3000000.
> 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 MAG 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/from a PDN gateway. 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 MAG 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
> encapsulation
> Configures data encapsulation type to be used for specific MAG service.
> Product
> HSGW, S-GW
> Privilege
> Administrator
> Syntax
> encapsulation { gre | ipip }
> default encapsulation
> default
> Resets the encapsulation type to be used by this service to the default option of GRE.
> { gre | ipip }
> gre: Specifies that GRE encapsulation is to be used for PMIPv6 tunnel data between the MAG and the LMA. This is the default for this command.
> ipip: Specifies that IP-in-IP encapsulation is to be used for PMIPv6 tunnel data between the MAG and the LMA.
> Usage
> Use this command to select the encapsulation type to be used for PMIPv6 tunnel data between the MAG and the LMA.
> Example
> The following command sets the encapsulation data to IP-in-IP:
> encapsulation ipip
> end
> Exits the current mode and returns to the Exec Mode.
> Product
> All
> Privilege
> Administrator
> Syntax
> end
> Usage
> Change the mode back to the Exec mode.
> exit
> Exits the current mode and returns to the previous mode.
> Product
> All
> Privilege
> Administrator
> Syntax
> exit
> Usage
> Return to the previous mode.
> information-element-set
> Identifies the information element set of mobility options to be used in Proxy Binding Update (PBU) messages sent by the MAG to the LMA.
> Product
> HSGW, S-GW
> Privilege
> Administrator
> Syntax
> information-element-set { custom1 | standard }
> default information-element-set
> default
> Resets the command to the default value of “standard”.
> { custom1 | standard }
> custom1: Specifies that a custom set of mobility options to be used in proxy binding update messages that are sent in Vendor Specific Mobility Options. These options are:

> • | User Location Info

> • | Hardware Identifier

> • | Access Network Charging Identifier

> standard: Specifies that a standard set of mobility options are to be used in proxy binding update messages. The 3GPP specification, 29.275 defines these as Protocol Configuration Options.
> Usage
> Use this command to identify the type of information element set of mobility options to be used in PBU messages sent form the MAG to the LMA. The mobility options can be either standards-based (3GPP 29.275) or custom (vendor-specific as defined by 3GPP 29.275).
> Example
> The following command identifies the information element set of mobility options to use in PBU messages as custom:
> information-element-set custom1
> max-retransmissions
> Configures maximum number of retransmissions of Proxy MIP control messages to the LMA.
> Product
> HSGW, S-GW
> Privilege
> Administrator
> Syntax
> max-retransmissions num
> default max-retransmissions
> default
> Rests the maximum number of allowed retransmissions to the default value of 5.
> num
> Default: 5
> Specifies the maximum number of times the MAG service will attempt to communicate with the LMA before it marks it as unreachable.
> count can be configured to any integer value between 1 and 4294967295.
> Usage
> Use this command to limit the number of retransmissions to LMA before marking it as unreachable. If the value configured is reached, the call is dropped.
> Example
> The following command configures the maximum number of retransmissions for the MAG service to 3:
> max-retransmissions 3
> reg-lifetime
> Configures the Mobile IPv6 session registration lifetime for this service.
> Product
> HSGW, S-GW
> Privilege
> Administrator
> 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 PBA from the LMA contains a lifetime shorter or longer than what is specified, it is used instead.
> Example
> The following command sets the registration lifetime for Mobile IPv6 sessions using this service to 1200 seconds (20 minutes):
> reg-lifetime 1200
> renew-percent-time
> Configures percentage of lifetime at which a registration renewal is sent to the LMA.
> Product
> HSGW, S-GW
> Privilege
> Administrator
> Syntax
> renew-percent-time percent
> default renew-percent-time
> default
> Resets the command to the default value of 75.
> percent
> Default: 75
> Specifies the time when the registration renewal is sent to the LMA. percent is a percentage value of the registration lifetime and must be an integer value from 1 to 100.
> Usage
> Use this command to specify when a registration renewal is sent to the LMA for subscribers using this service.
> If the registration lifetime is 600 seconds (10 minutes) and this command is set to 75 (percent), then the registration renewal message is sent after 450 seconds of the registration lifetime has expired.
> Example
> The following command sets the registration renewal time for subscribers using this service to 90 percent of the registration lifetime:
> renew-percent-time 90
> retransmission-policy
> Configures the retransmission policy for Proxy MIP control message retransmissions.
> Product
> HSGW
> Privilege
> Administrator
> Syntax
> retransmission-policy { exponential-backoff | normal }
> default retransmission-policy
> default
> Returns the command to its default setting of exponential-backoff.
> { exponential-backoff | normal }
> Sets the retransmission timeout behavior for this service.
> exponential-backoff: Specifies that the Proxy Binding Update retransmission uses an exponential backoff to increase the retransmission timeout for each retry.
> normal: Specifies that the Proxy Binding Update retransmission uses the configured retransmission timeout value for all PBU retransmission retries.
> Usage
> Use this command to specify the retransmission policy for PMIP control messages.
> Example
> The following command sets the retransmission timeout policy for PMIP control packets to “normal”:
> retransmission-policy normal
> retransmission-timeout
> Configures the maximum allowable time for the MAG service to wait for a response from the LMA before it attempts to communicate with the LMA again (if the system is configured to retry the LMA) or marks the LMA as unreachable.
> Product
> HSGW, S-GW
> Privilege
> Administrator
> Syntax
> retransmission-timeout time
> { default | no } retransmission-timeout
> default
> Resets the timeout setting to the default value of 3.
> no
> Deletes a previously configured timeout value.
> time
> Default: 3 seconds (300)
> Specifies the maximum allowable time, in milliseconds, for the MAG service to wait for a response from the LMA before it: a) attempts to communicate with the LMA again (if the system is configured to retry the LMA) or b) marks the LMA as unreachable.
> time must be an integer value between 100 and 100000.
> Usage
> Use the retransmission timeout command in conjunction with the max-retransmissions command in order to configure the MAG services behavior when it does not receive a response from a particular LMA.
> Example
> The following command configures a retransmission timeout value of 5 seconds:
> retransmission-timeout 5

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883