Cisco Cisco Packet Data Gateway (PDG)
HNB-GW Service Configuration Procedures
▀ HNB-GW Service Configuration
▄ HNB-GW Administration Guide, StarOS Release 17
104
GTP-U Service Configuration
Use the following example to configure the GTP-U service parameters to provide GTP-U tunnel over Iuh and IuPS
interface. Separate instances of this service need to be configured for Iuh and IuPS interfaces.
interface. Separate instances of this service need to be configured for Iuh and IuPS interfaces.
configure
context <dest_ctxt_name> -noconfirm
gtpu-service <gtpu_ps_svc_name> -noconfirm
bind address {ipv4-address | ipv6-address} <ip_address>
path-failure detection-policy gtp echo
end
configure
context <vpn_ctxt_name> -noconfirm
gtpu-service <gtpu_iuh_svc_name> -noconfirm
bind address {ipv4-address | ipv6-address} <ip_address>
path-failure detection-policy gtp echo
end
Notes:
<
dest_ctxt_name
> is name of the destination context in which GTP-U service configured to provide GTP-U
tunnel over IuPS interface towards core network.
<
gtpu_ps_svc_name
> is name of the GTP-U service configured to provide GTP-U tunnel over IuPS interface
towards core network.
<
vpn_ctxt_name
> is name of the source context in which HNB-GW service is to be configured. The same
context must be used for GTP-U service configuration to provide GTP-U tunnel over Iuh interface towards
HNB.
HNB.
<
gtpu_iuh_svc_name
> is name of the GTP-U service configured to provide GTP-U tunnel over Iuh interface
towards HNB.
x.509 Certificate Configuration
Use the following example to configure the x.509 certificates on the system to provide security certification between
FAP and SeGW on HNB-GW.
FAP and SeGW on HNB-GW.
configure
certificate name <x.509_cert_name> pem { data <pem_data_string> | url <pem_data_url>}
private-key pem { [encrypted] data <PKI_pem_data_string> | url <PKI_pem_data_url>}
private-key pem { [encrypted] data <PKI_pem_data_string> | url <PKI_pem_data_url>}