Cisco ASR 5x00 Home eNodeB Administration Manual page 39

HeNB-GW Service Configuration Procedures
------------ Logical eNodeB Configuration ----------------------
logical-enb global-enb-id plmn id mcc <mcc_id> mnc <mnc_id> macro-enb-id
<macro_enodeb_id> -n
bind s1-mme ipv4-address <secondary3_ipv4_addr>
s1-mme sctp port <sctp_port_no>
associate mme-pool <mme_pool_name>
associate tai-list-db <lte_policy_tai_db>
exit
exit
-------------- HeNB-GW Access Service Configuration --------------------
henbgw-access-service <henb_access_svc_name> -n
bind s1-mme ipv4-address <primary_ipv4_addr>
s1-mme sctp port <sctp_port_no>
mme-id group-id <mme_id> mme-code <mme_code>
associate henbgw-network-service <henb_network_svc_name>
plmn id mcc <mcc_id> mnc <mnc_id>
-------------- S1-U Relay Configuration --------------------
s1u-relay
associate access-gtpu-service <gtpu_svc_access> context ingress
associate network-gtpu-service <gtpu_svc_network> context ingress
exit
exit
Notes:
 <
ingress_ctxt_name
 <
interface_name
defined for different services to bind including GTP-U and HeNB-GW Access and Network services.
 <
gtpu_svc_access
mode to provide GTP-U tunnel for HeNBGW Access service. This GTP-U service will be used as Access
GTP-U service and will be associated with the HeNB-GW Access Service in case s1-U relay is enabled.
 <
gtpu_svc_network
context mode to provide GTP-U tunnel for HeNBGW Network service. This GTP-U service will be used as
> is name of the source context in which HeNB-GW service is configured.
> is the name of the interface under which primary and secondary IP addreses are to be
> is the name of the GTP-U service configured in the <
> is the name of the second GTP-U service configured in the <
ingress_ctxt_name
Cisco ASR 5x00 Home eNodeB Gateway Administration Guide ▄
HeNB-GW Service Configuration ▀
> context
>
ingress_ctxt_name
39