bind
Binds the service to a logical IP interface serving as the S2a (HSGW, SaMOG) 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
SaMOG
Privilege
Administrator
Mode
Exec > Global Configuration > Context Configuration > MAG Service Configuration
configure > context context_name > mag-service service_name
Entering the above command sequence results in the following prompt:
[context_name]host_name(config-mag-service)#
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 S5/S8 interface.
ipv6_address is specified in IPv6 colon-separated-hexadecimal notation.
ipv4-address ipv4_address
Specifies the IPv4 address of the interface configured as the S2a or S5/S8 interface.
Important |
The SaMOG PMIPv6-based S2a interface currently supports IPv4 bind address only. |
ipv4_address is specified in IPv4 colon-separated-hexadecimal notation.
max-subscribers num
Default: 1500000
Specifies the maximum number of subscribers that can access this service on this interface.
num must be an integer from 0 through 3000000.
Important |
The maximum number of subscribers supported depends on the installed license key and the number of active packet processing cards in the system. A fully loaded system can support 3,000,000 total subscribers. Refer to the license key command and the Usage section (below) for additional information. |
Usage Guidelines
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 P-GW. 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.
-
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 to which these interfaces will be bound
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.
Examples
bind address 4551:0db8:85a3:08d3:3319:8a2e:0370:1344 max-subscribers 300000