Manual

ip address <ipv4_addr> 255.255.255.0 secondary
exit
-------- Access and Network GTP-U Services Configuration ------
gtpu-service <gtpu_svc_access> -noconfirm
bind ipv4-address <secondary1_ipv4_addr>
exit
gtpu-service <gtpu_svc_network> -noconfirm
bind ipv4-address <secondary2_ipv4_addr>
exit
------------- HeNB-GW Network Service Configuration -----------
henbgw-network-service <henb_network_svc_name> -noconfirm
------------ 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 | ipv6-address } <ip_addr>
s1-mme sctp port <sctp_port_no>
associate henbgw 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 | ipv6-address } <ip_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> is name of the source context in which HeNB-GW service is configured.
•
<interface_name> is the name of the interface under which primary and secondary IP addresses are to
be defined for different services to bind including GTP-U and HeNB-GW Access and Network services.
•
<gtpu_svc_access> is the name of the GTP-U service configured in the <ingress_ctxt_name> context
mode to provide GTP-U tunnel for HeNB-GW 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> is the name of the second GTP-U service configured in the <ingress_ctxt_name>
context mode to provide GTP-U tunnel for HeNB-GW Network service. This GTP-U service will be
used as Network GTP-U service and will be associated with the HeNB-GW Access Service in case s1-U
relay is enabled.
•
<secondary1_ipv4_addr> is the IPV4 type address defined under the <interface_name> interface and
being bound to the <gtpu_svc_name1> GTP-U service.
•
<secondary2_ipv4_addr> is the IPV4 type address defined under the <interface_name> interface and
being bound to the <gtpu_svc_name2> GTP-U service.
•
<henb_network_svc_name> is the HeNB-GW Network service name
HeNB-GW Administration Guide, StarOS Release 19
48
HeNB-GW Service Configuration Procedures
HeNB-GW Service Configuration