IMPORTANT:
Configuring the System to Perform as a Standalone HSGW
Information Required
Required Local Context Configuration Information
Required Information | Description |
---|---|
Management Interface Configuration | |
Interface name | An identification string between 1 and 79 characters (alpha and/or numeric) by which the interface will be recognized by the system.Multiple names are needed if multiple interfaces will be configured. |
IP address and subnet | IPv4 addresses assigned to the interface.Multiple addresses and subnets are needed if multiple interfaces will be configured. |
Physical port number | The physical port to which the interface will be bound. Ports are identified by the chassis slot number where the line card resides followed by the number of the physical connector on the card. For example, port 17/1 identifies connector number 1 on the card in slot 17.A single physical port can facilitate multiple interfaces. |
Gateway IP address | Used when configuring static IP routes from the management interface(s) to a specific network. |
Security administrator name | The name or names of the security administrator with full rights to the system. |
Security administrator password | Open or encrypted passwords can be used. |
Remote access type(s) | The type of remote access that will be used to access the system such as telnetd, sshd, and/or ftpd. |
Required HSGW Context Configuration Information
Required Information | Description |
---|---|
HSGW context name | An identification string from 1 to 79 characters (alpha and/or numeric) by which the HSGW context is recognized by the system. |
Diameter authentication dictionary | The name of the Diameter dictionary used for authentication. |
Diameter endpoint name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the Diameter endpoint is recognized by the system.The Diameter endpoint name identifies the configuration used to communicate with the 3GPP AAA server in the AAA context. |
Accounting policy name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the accounting policy is recognized by the system. The accounting policy is used to set parameters for the Rf (off-line charging) interface. |
A10/A11 Interface Configuration (To/from eAN/ePCF) | |
Interface name | An identification string between 1 and 79 characters (alpha and/or numeric) by which the interface is recognized by the system.Multiple names are needed if multiple interfaces will be configured. |
IP address and subnet | IPv4 addresses assigned to the interface.Multiple addresses and subnets are needed if multiple interfaces will be configured. |
Physical port number | The physical port to which the interface will be bound. Ports are identified by the chassis slot number where the line card resides followed by the number of the physical connector on the card. For example, port 17/1 identifies connector number 1 on the card in slot 17.A single physical port can facilitate multiple interfaces. |
Gateway IP address | Used when configuring static IP routes from the management interface(s) to a specific network. |
HSGW Service Configuration | |
HSGW service name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the HSGW service is recognized by the system.Multiple names are needed if multiple HSGW services will be used. |
Security Parameter Index Remote Address | eAN/ePCF IP address:Specifies the IP address of the eAN/ePCF. The HSGW service allows the creation of a security profile associated with a particular eAN/ePCF. |
SPI number:Specifies the SPI (number) which indicates a security context between the eAN/ePCF and the HSGW. | |
Encrypted secret:Configures the shared-secret between the HSGW service and the eAN/ePCF. This command can also be non-encrypted. |
Required MAG Context Configuration Information
Required Information | Description |
---|---|
MAG context name | An identification string from 1 to 79 characters (alpha and/or numeric) by which the MAG context is recognized by the system. |
S2a Interface Configuration (To/from P-GW LMA) | |
Interface name | An identification string between 1 and 79 characters (alpha and/or numeric) by which the interface is recognized by the system.Multiple names are needed if multiple interfaces will be configured. |
IP address and subnet | IPv6 address assigned to the interface.Multiple addresses and subnets are needed if multiple interfaces will be configured. |
Physical port number | The physical port to which the interface will be bound. Ports are identified by the chassis slot number where the line card resides followed by the number of the physical connector on the card. For example, port 17/1 identifies connector number 1 on the card in slot 17.A single physical port can facilitate multiple interfaces. |
Gateway IP address | Used when configuring static IP routes from the management interface(s) to a specific network. |
MAG Service Configuration | |
MAG Service Name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the MAG service is recognized by the system. |
Required AAA Context Configuration Information
Required Information | Description |
---|---|
Gxa Interface Configuration (to PCRF) | |
Interface name | An identification string between 1 and 79 characters (alpha and/or numeric) by which the interface is recognized by the system.Multiple names are needed if multiple interfaces will be configured. |
IP address and subnet | IPv6 addresses assigned to the interface.Multiple addresses and subnets are needed if multiple interfaces will be configured. |
Physical port number | The physical port to which the interface will be bound. Ports are identified by the chassis slot number where the line card resides followed by the number of the physical connector on the card. For example, port 17/1 identifies connector number 1 on the card in slot 17.A single physical port can facilitate multiple interfaces. |
Gateway IP address | Used when configuring static IP routes from the management interface(s) to a specific network. |
Gxa Diameter Endpoint Configuration | |
End point name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the Gxa Diameter endpoint configuration is recognized by the system. |
Origin realm name | An identification string between 1 through 127 characters.The realm is the Diameter identity. The originator’s realm is present in all Diameter messages and is typically the company or service name. |
Origin host name | An identification string from 1 to 255 characters (alpha and/or numeric) by which the Gxa origin host is recognized by the system. |
Origin host address | The IPv6 address of the Gxa interface. |
Peer name | The Gxa endpoint name described above. |
Peer realm name | The Gxa origin realm name described above. |
Peer address and port number | The IPv6 address and port number of the PCRF. |
Route-entry peer | The Gxa endpoint name described above. |
STa Interface Configuration (to 3GPP AAA server) | |
Interface name | An identification string between 1 and 79 characters (alpha and/or numeric) by which the interface is recognized by the system.Multiple names are needed if multiple interfaces will be configured. |
IP address and subnet | IPv4 addresses assigned to the interface.Multiple addresses and subnets are needed if multiple interfaces will be configured. |
Physical port number | The physical port to which the interface will be bound. Ports are identified by the chassis slot number where the line card resides followed by the number of the physical connector on the card. For example, port 17/1 identifies connector number 1 on the card in slot 17.A single physical port can facilitate multiple interfaces. |
Gateway IP address | Used when configuring static IP routes from the management interface(s) to a specific network. |
STa Diameter Endpoint Configuration | |
End point name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the STa Diameter endpoint configuration is recognized by the system. |
Origin realm name | An identification string between 1 through 127 characters.The realm is the Diameter identity. The originator’s realm is present in all Diameter messages and is typically the company or service name. |
Origin host name | An identification string from 1 to 255 characters (alpha and/or numeric) by which the STa origin host is recognized by the system. |
Origin host address | The IPv6 address of the STa interface. |
Peer name | The STa endpoint name described above. |
Peer realm name | The STa origin realm name described above. |
Peer address and port number | The IPv6 address and port number of the PCRF. |
Route-entry peer | The STa endpoint name described above. |
Rf Interface Configuration (to off-line charging server) | |
Interface name | An identification string between 1 and 79 characters (alpha and/or numeric) by which the interface is recognized by the system.Multiple names are needed if multiple interfaces will be configured. |
IP address and subnet | IPv4 addresses assigned to the interface.Multiple addresses and subnets are needed if multiple interfaces will be configured. |
Physical port number | The physical port to which the interface will be bound. Ports are identified by the chassis slot number where the line card resides followed by the number of the physical connector on the card. For example, port 17/1 identifies connector number 1 on the card in slot 17.A single physical port can facilitate multiple interfaces. |
Gateway IP address | Used when configuring static IP routes from the management interface(s) to a specific network. |
Rf Diameter Endpoint Configuration | |
End point name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the Rf Diameter endpoint configuration is recognized by the system. |
Origin realm name | An identification string between 1 through 127 characters.The realm is the Diameter identity. The originator’s realm is present in all Diameter messages and is typically the company or service name. |
Origin host name | An identification string from 1 to 255 characters (alpha and/or numeric) by which the Rf origin host is recognized by the system. |
Origin host address | The IPv6 address of the Rf interface. |
Peer name | The Rf endpoint name described above. |
Peer realm name | The Rf origin realm name described above. |
Peer address and port number | The IPv6 address and port number of the PCRF. |
Route-entry peer | The Rf endpoint name described above. |
configure
context
local
interface <lcl_cntxt_intrfc_name>
ip
address <ip_address> <ip_mask>
exit
server
<server-type>
exit
subscriber
default
exit
administrator
<name>
encrypted password <password>
ftp
ip
route <ip_addr/ip_mask> <next_hop_addr> <lcl_cntxt_intrfc_name>
exit
port
ethernet <slot#/port#>
no
shutdown
bind
interface <lcl_cntxt_intrfc_name>
local
end
Creating and Configuring an HSGW Context
configure
context
<hsgw_context_name>
-noconfirm
interface
<a10-a11_interface_name>
ip
address <ipv4_address>
exit
policy
accounting <rf_acct_policy_name>
-noconfirm
accounting-level {type}
operator-string <string>
exit
ip
domain-lookup
ip
name-servers <ipv4_or_ipv6_address>
dns-client <name>
port
ethernet <slot_number/port_number>
no
shutdown
bind
interface <a10-a11_interface_name> <hsgw_context_name>
end
Configuring Static IP Routes
Creating and Configuring MAG Context
Configuring the HSGW Service
configure
context
<hsgw_context_name>
-noconfirm
hsgw-service
<hsgw_service_name> -noconfirm
mobile-access-gateway
context <mag_context_name>
mag-service <mag_service_name>
associate
accounting-policy <rf_name>
spi
remote-address <epcf_address>
spi-number <num> encrypted
secret <secret>
plmn
id mcc <number>
mnc <number>
fqdn <domain_name>
gre
sequence-mode recorder
gre
flow-control action resume-session timeout <msecs>
gre
segmentation
unauthorized-flows
qos-update wait-timeout <seconds>
ip
header-compression rohc
bind
address <a10-a11_interface_address>
end
Configuring the MAG Service
configure
context
<mag_context_name>
-noconfirm
mag-servics
<mag_service_name>
-noconfirm
information-element-set custom1
bind
address <s2a_interface_address>
end
Creating and Configuring the AAA Context
configure
context
<aaa_context_name>
-noconfirm
interface <aaa_sta_ipv4_interface_name>
ip
address <ipv4_address>
exit
interface <pcrf_gxa_ipv6_interface_name>
ip
address <ipv6_address>
exit
interface <ocs_rf_ipv4_interface_name>
ip
address <ipv4_address>
exit
subscriber
default
exit
aaa
group default
diameter
accounting endpoint <rf_ofcs_server>
diameter
authentication endpoint <sta_cfg_name>
diameter
accounting server <rf_ofcs_server>
priority <num>
diameter
authentication server <3gpp_aaa_server>
priority <num>
exit
ims-auth-service <gxa_ims_service_name>
policy-control
diameter
origin endpoint <gxa_cfg_name>
diameter
dictionary <gxa_dictionry_name>
diameter
host-select table <#>
algorithm round-robin
diameter
host-select row-precedence <#>
table <#>
host <gxa_cfg_name>
exit
exit
aaa
group default
diameter
authentication dictionary <name>
diameter
authentication endpoint <sta_cfg_name>
diameter
authentication server <sta_cfg_name>
priority <#>
exit
diameter
endpoint <sta_cfg_name>
origin
realm <realm_name>
origin
host <name>
address <aaa_ctx_ipv4_address>
peer
<sta_cfg_name>
realm <name>
address <aaa_ipv4_address>
route-entry
peer <sta_cfg_name>
exit
diameter
endpoint <gxa_cfg_name>
origin
realm <realm_name>
origin
host <name>
address <aaa_ctx_ipv6_address>
peer
<gxa_cfg_name>
realm <name>
address <pcrf_ip_addr>
port <#>
route-entry
peer <gxa_cfg_name>
end
diameter
endpoint <rf_cfg_name>
origin
realm <realm_name>
origin
host <name>
address <aaa_ctx_ipv4_address>
peer
<rf_cfg_name>
realm <name>
address <ocs_ip_addr>
port <#>
route-entry
peer <rf_cfg_name>
end
Modifying the Default Subscriber
configure
context
<aaa_context_name>
-noconfirm
subscriber
default
ims-auth-service <gxa_ims_service_name>
rohc-profile-name <name>
end
Configuring QCI-QoS Mapping
configure
qci-qos-mapping <name>
qci
1 user-datagram dscp-marking <hex>
qci
3 user-datagram dscp-marking <hex>
qci
9 user-datagram dscp-marking <hex>
exit
Optional Header Compression Configuration
Verifying and Saving the Configuration