HeNB-GW Service Configuration Procedures

This chapter is meant to be used in conjunction with the other chapters that describes the information needed to configure the system to support HeNB-GW functionality for use in HeNB access networks.

It is recommended that you identify the options from the previous chapters that are required for your specific deployment. You can then use the procedures in this chapter to configure those options.

This chapter describes following:

IMPORTANT:

At least one packet card must be made active prior to service configuration. Information and instructions for configuring the packet cards to be active can be found in the Configuring System Settings chapter of the System Administration Guide.

CAUTION:

While configuring any base-service or enhanced feature, it is highly recommended to take care of conflicting or blocked IP addresses and port numbers for binding or assigning. In association with some service steering or access control features, like Access Control List configuration, use of inappropriate port number may result in communication loss. Refer respective feature configuration document carefully before assigning any port number or IP address for communication with internal or external network.

Information Required to Configure the System as an HeNB-GW

This section provides a high-level series of steps and the associated configuration file examples for configuring the system to perform as an HeNB-GW node in a test environment. Information provided in this section includes the following:

Note:

The following sections describe the minimum amount of information required to configure and make the HeNB-GW operational on the LTE Femtocell network. To make the process more efficient, it is recommended that this information be available prior to configuring the system.

Note:

There are additional configuration parameters that are not described in this section. These parameters deal mostly with fine-tuning the operation of the HeNB-GW in the network. Information on these parameters can be found in the appropriate sections of the Command Line Interface Reference.

Required Local Context Configuration Information

The following table lists the information that is required to configure the local context on an HeNB-GW.


Table 1. Required Information for Local Context Configuration
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 Source Context Configuration Information

The following table lists the information that is required to configure the Source context on an HeNB-GW.


Table 2. Required Information for Source Context Configuration
Required Information Description
Source context name An identification string from 1 to 79 characters (alpha and/or numeric) by which the Source context is recognized by the system.Generally it is identified as source context.
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.
Ingress and Egress GTP-U Services
Ingress GTP-U service Name An identification string from 1 to 63 characters (alpha and/or numeric) by which the Ingress GTP-U service can be identified on the system. It is configured in Context Configuration Mode. When S1-U Relay is enabled, the Ingress GTP-U service configuration is critical as it has to be associated with the HeNB-GW Access Service. It is also called access-side GTP-U service for the HeNB-GW ACCESS service.
Egress GTP-U service Name An identification string from 1 to 63 characters (alpha and/or numeric) by which the Egress GTP-U service can be identified on the system. It is configured in Context Configuration Mode. When S1-U Relay is enabled, the Egress GTP-U service configuration is critical as it has to be associated with the HeNB-GW Access Service. It is also called network-side GTP-U service for the HeNB-GW ACCESS service.
GTP-U Tunnel interface IP address

IP addresses assigned to the interface as GTP-U bond address.

This address will be used for binding the GTP-U service (local bind address(es)) for sending/receiving GTP-U packets from/to HeNB using GTP-U tunnel.

Multiple addresses and subnets are needed if multiple interfaces will be configured.

S1-AP Configuration (To/from Home-eNodeB)
HeNB-GW access service Name An identification string from 1 to 63 characters (alpha and/or numeric) by which the HeNB-GW Access service can be identified on the system. It is configured in Context Configuration Mode. At a time, only one HeNB-GW Access Service can be configured per system.
HeNB-GW Network service Name An identification string from 1 to 63 characters (alpha and/or numeric) by which the HeNB-GW Network service can be identified on the system. It is also configured in Context Configuration Mode. At a time, only one HeNB-GW Network Service can be configured per system and therefore there is 1:1 mapping between HeNB-GW Access and Network services.


Required Destination Context Configuration Information

The following table lists the information that is required to configure the destination context.


Table 3. Required Information for Destination Context Configuration
Required Information Description
Destination context name

An identification string from 1 to 79 characters (alpha and/or numeric) by which the destination context will be recognized by the system.

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.

HeNB-GW Access Service Configuration

S1-MME interface IP address

IPv4/IPv6 addresses assigned to the S1-MME interface as SCTP bond address.This address will be used for binding the SCTP (local bind address(es)) to communicate with the MME using eGTP. The HeNB-GW passes this IP address during setting up the association with the MME. Multiple addresses and subnets are needed if multiple interfaces will be configured.

Public Land Mobile Network (PLMN) Identifiers

Mobile Country Code (MCC): The MCC can be configured to any integer value from 0 to 999.

Mobile Network Code (MNC): The MNC can be configured to any integer value from 0 to 999.

S1-MME SCTP Port

The physical port to which is used to communicate with the HeNBs over S1-MME interface. It is usually an integer value ranging from 1 to 65535.

MME ID Group ID

MME Group ID to be configured for the HeNB-GW Access Service. This is a required parameter since the HeNB-GW acts as an MME to the HeNB(s) and this ID is filled in the S1-SETUP response sent to the HeNB(s). It is an integer ranging from 32768..65535.

MME Code

MME Code is also part of the MME ID configuration. MME Group ID and MME Code both are required for MME Identifier configuration for the HeNB-GW Access service. It is an integer which ranges from 0..255.

S1-U Relay

Enables the S1-U relay functionality for the HeNB-GW Access Service. Once S1-U Relay is enabled, the association to Ingress and Egress GTP-U services is considered as critical configuration for the HeNB-GW Access service.

Associate HeNB-GW Network Service

A pre-configured HeNB-GW Network Service is required to be associated to the HeNB-GW Access Service. User can enter a desired HeNB-GW Network service name even if it is not pre-configured, but it will be required to be configured in later course for this HeNB-GW Access service to come up.

Optional Security Gateway Configuration
Security Gateway IP address

This is the IP Address where the SeGW service is bound and shall be provided to HeNB during SeGW-Discovery. This security gateway is associated with the HeNB-GW Access Service.

Only one SeGW IP address can be configured.

Diameter Endpoint An identification string from 1 to 63 characters (alpha and/or numeric) by which the Diameter endpoint configuration is recognized by the system. This Diameter Endpoint is required by the SeGW to communicate with the AAA server.
Diameter Endpoint Configuration
Endpoint Name An identification string from 1 to 63 characters (alpha and/or numeric) by which the Diameter endpoint configuration is recognized by the system. This Diameter Endpoint is required by the SeGW to communicate with the AAA server.
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 origin host is recognized by the system.
Origin host address The IP address of the interface.
Peer name The endpoint name described above.
Peer realm name The interface origin realm name described above.
Peer address and port number The IP address and port number of the OCS.
IPsec Crypto-map Template Configuration
EAP profile This is the profile to be used to provide authenticator modes for incoming packets on Security Gateway.

Only one EAP profile can be configured.

IP Pool for IPsec Tunnel

Specifies the IP pool to assign IP address for IPsec traffic to use.

IKEv2 Transform set

IKEv2 transform set for IKE security association.

IPsec Crypto-map Template

Specifies the Crypto-map template to be used for IPsec IKEv2 tunneling for the interface configured.

This Crypto-map template is to be associated with HeNB-GW Access service if SeGW is enabled and bind with this HeNB-GW Access service.

HeNB-GW Access Service can run with or without the IPSec configuration. Since only one HeNB-GW Access Service can be configured per system, either IPSec can be configured or not.

Only one IPsec Crypto-map Template can be configured.

AAA Server Group Context name

Specifies the name of the context in which a AAA server group is configured for association with SeGW for AAA parameters during subscriber authentication phases.

AAA Server Group name

Specifies the AAA server group already configured in a context and is to be used for first/second phase of authentication of subscriber while using SeGW functionality in an HeNB-GW service.

HeNB-GW Network Service Configuration

Logical eNodeB The Logical eNodeB configuration option enables the configuration of one or more logical eNodeBs within the HeNB-GW. The Logical eNodeB configuration is usually used to support load balancing within a pool of TAIs. At least one logical eNodeB configuration is required to START an HeNB-GW Network service. 8 Logical eNodeBs are supported per HeNB-GW Network service.

CAUTION:

Deleting or modifying any of the parameters for a fully configured logical eNodeB results in the termination of SCTP connections to MMEs from that logical eNodeb.

Public Land Mobile Network (PLMN) Identifiers

Mobile Country Code (MCC): The MCC can be configured to any integer value from 0 to 999.

Mobile Network Code (MNC): The MNC can be configured to any integer value from 0 to 999.

Macro eNodeB ID Macro eNodeB identifier, required as a parameter for the Logical eNodeB configuration. It is an option to the Home eNodeB identifier.
Home eNodeB ID Home eNodeB identifier, required as a parameter for the Logical eNodeB configuration. It is an option to the Macro eNodeB identifier.
S1-MME interface IP address IPv4 addresses assigned to the S1-MME interface as SCTP bond address. This address will be used for binding the SCTP (local bind address(es)) to communicate with the MME using eGTP. The HeNB-GW passes this IP address during setting up the association with the MME. Multiple addresses and subnets are needed if multiple interfaces will be configured.
S1-MME SCTP Port The physical port to which is used to communicate with the HeNBs over S1-MME interface. It is usually an integer value ranging from 1 to 65535.

Logical eNodeB Configuration

MME Pool A pre-configured MME pool to be associated with the Logical eNodeB. An MME pool is configured in the LTE Policy Configuration Mode. Only one MME Pool instance can be associated with a Logical eNodeB instance. All MMEs in the pool are assumed to support all TAIs in the associated TAI List DB object. One Logical eNodeB can connect up to 8 MMEs and therefore a max of 64 associations can be established between HeNB-GW and MME
TAI List DB A pre-configured list of tracking area identity (TAIs) pool to be associated with the Logical eNodeB. A TAI List database is configured in the LTE Policy Configuration Mode. Only one TAI list DB can be associated with the Logical eNodeB instance. The tai-list-db contains a list of TAIs. These are sent in the S1 Setup message to the MME to indicate the list of TAIs supported by the eNodeB. The TAI database which can be associated to each logical EnodeB can accommodate 256 configuration of TACs.

TAI List DB Configuration

MCC

Mobile Country Code (MCC): The MCC can be configured to any integer value from 0 to 999.

MNC

Mobile Network Code (MNC): The MNC can be configured to any integer value from 0 to 999.

Tracking Area Code (TAC) TAC is an integer value ranging from 0..65535. The HeNB-GW Network service searches these TACs for establishing UE connections.


HeNB-GW Service Configuration

HeNB-GW services are configured within source contexts and allow the system to function as an HeNB-GW in the 4G LTE wireless data network.

IMPORTANT:

This section provides the minimum instruction set for configuring an HeNB-GW service that allows the system to process bearer contexts with IPsec authentication on SeGW. Commands that configure additional HeNB-GW service properties are provided in the different chapters of Command Line Interface Reference.

These instructions assume that you have already configured the system level configuration as described in System Administration Guide.

To configure the system to work as HeNB-GW service with SeGW enabled:

  1. Configure a system context in the Global Configuration Mode, as shown in the Context Configuration section of the HeNB-GW Service Configuration example. Using this step, the user enters in the Context Configuration Mode.
  2. Create an interface and enter the interface configuration mode for newly created interface to add IP addresses along with the subnet mask for this interface, as shown in the Interface and IP Address Configuration section of the HeNB-GW Service Configuration example. These IP addresses are used to bind to different services including GTP-U Access and Network services and even interfaces like S1-MME.
  3. Configure the Access and Network GTP-U services, as shown in the Access and Network GTP-U Services Configuration section of the HeNB-GW Service Configuration example. These services are bound individually to the IP addresses configured in the Step 2.
  4. Configure the HeNB-GW Network service, as shown in the HeNB-GW Network Service Configuration section of the HeNB-GW Service Configuration example. Using this step, the user enters in the HeNB-GW Network Service Configuration Mode.
  5. Configure the logical eNodeB for the HeNB-GW Network service created in step4, as shown in the Logical eNodeB Configuration section of the HeNB-GW Service Configuration example.
  6. Bind the S1-MME using IP address of this interface to the Logical eNodeB created in Step 5. Enter the IP address in dotted decimal notation.
  7. Specify the SCTP port for the S1-MME interface bound in step 6.
  8. Associate the MME pool name to the Logical eNodeB. This MME pool can be created in the LTE Policy configuration mode, as shown in the LTE Policy Configuration example.
  9. Associate the TAI List database to the Logical eNodeB. This TAI List database can e configured in the LTE Policy configuration mode, as shown in the LTE Policy Configuration example.
  10. Configure the HeNB-GW Access service, as shown in the HeNB-GW Access Service Configuration section of the HeNB-GW Service Configuration example. Using this step, the user enters in the HeNB-GW Access Service Configuration Mode.
  11. Bind the S1-MME using IP address of this interface to the HeNB-GW service created in Step 10. Enter the IP address in dotted decimal notation.
  12. Specify the SCTP port for the S1-MME interface bound in Step 11.
  13. Configure the MME Group Identifier for the HeNB-GW Access service. As part of this configuration, group ID as well as the MME code has to be configured. MME ID is used as part of S1 setup procedure during HeNB association. It is an integer value ranging from 0 to 255.
  14. Associate the HeNB-GW Network service configured in the step 4 to this HeNB-GW Access Service.
  15. Configure the Public Land Mobile Network Identifiers MMC and MNC for this HeNB-GW Access Service.
  16. Enable the S1-U Relay for this HeNB-GW Access service. Using this step, the user enters in the S1-U Relay Configuration Mode. This is an optional step.
  17. Associate the Access and Network GTP-U services created in the Step 3 to this HeNB-GW Access service. Association of the GTP-U services is mandatory in case S1-U Relay is enabled.

HeNB-GW Service Configuration

Use the following example to configure the HeNB-GW service on system in source context to provide access to HeNBs towards core networks:

configure
------------------ Context Configuration --------------------
  context <ingress_ctxt_name>
----------- Interface and IP addresses Configuration -----------
    interface <interface_name>
      ip
address <ipv4_addr> 255.255.255.0
      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
  • <secondary3_ipv4_addr> is the IPv4 type address used to bind with the S1-MME interface.
  • <mme_pool_name> is the MME pool name as defined while the LTE policy configuration.

    IMPORTANT:

    This MME pool is associated with the HeNB-GW network service.

  • <lte_policy_tai_db> is the tracking area information database name as defined while the LTE policy configuration.

    IMPORTANT:

    This tracking area information database is associated with the HeNB-GW network service.

  • <henb_access_svc_name> is the name of the HeNB-GW Access service name.
  • <primary_ipv4_addr> is the IPv4 type primary address used to bind with the S1-MME interface for this HeNB-GW access service.
  • s1u-relay enables the S1-U relay functionality by the HeNB-GW service. When configured, user enters into S1-U relay configuration mode. In this mode user has to configure associations to the Access and Network GTP-U services for S1-U relay. When s1-u relay is enabled, the association to ingress and egress GTP-U services is considered as a critical configuration for the HeNB-GW Access service. When S1-U relay is enabled, both Access and Network GTP-Uu services need to be in STARTED state for the HeNB-GW Access service to START.

    IMPORTANT:

    Changing the S1-U Relay configuration is a disruptive operation. The HeNB-GW Service is re-started.

IPSec Configuration

Use the following example to configure the IPSec configuration which goes with the Security Gateway (SeGW) configuration on the HeNB-GW Access Service.

For EAP-AKA Authentication Only

Configure
  context <ctxt_name>
    eap-profile <eap_profile_name>
    mode
authenticator-pass-through
      exit
  ipsec
transform-set <ipsec_transform_set_name>
  exit
  ikev2-ikesa
transform-set <ikesa_transform_set_name>
  exit
  crypto
template <crypto_template_name>
ikev2-dynamic
      authentication
remote eap-profile <eap_profile_name>
      ikev2-ikesa
transform-set list <ikesa_transform_set_name>
          payload <crypto_template_payload_name>
match childsa match ipv4
          ipsec
transform-set list  <ipsec_transform_set_name> 
          exit
      exit
  exit

For Certificate Based Authentication Only

Configure
    certificate
name  <cert_name>
pem url <url
format> private-key pem|der url|data <url or data format>
    ca-cert
name <cacert_name>
pem|der  url|data url or data format
  context <ctxt_name>
    ipsec
transform-set <ipsec_transform_set_name>
    exit
    ikev2-ikesa
transform-set <ikesa_transform_set_name>
    exit
    crypto
template <crypto_template_name>
ikev2-dynamic
        authentication
remote  certificate
        authentication
local certificate
        ikev2-ikesa
transform-set <ikesa_transform_set_name>
        payload <crypto_template_payload_name>
match childsa match ipv4
            ipsec
transform-set list  <ipsec_transform_set_name> 
            exit 
        certificate <cert_name>
        ca-certificate
list ca-cert-name <cacert_name>
    exit

For Simultaneous support of Multiple Authentication schemes (EAP-AKA & Certificate)

Configure
    certificate
name  <cert_name>
pem url <url
format> private-key pem|der url|data <url or data format>
    ca-cert
name <cacert_name>
pem|der  url|data url or data format
  context <ctxt_name>
    eap-profile <eap_profile_name>
    mode
authenticator-pass-through
    exit
    ipsec
transform-set <ipsec_transform_set_name>
    exit
    ikev2-ikesa
transform-set <ikesa_transform_set_name>
    exit
      ikev2-ikesa
auth-method-set <auth_profile_name1>
        authentication
remote eap-profile <eap_profile_name>
        exit
      ikev2-ikesa
auth-method-set <auth_profile_name2>
        authentication
local certificate
        authentication
remote  certificate
        exit
      crypto
template <crypto_template_name>
ikev2-dynamic
        ikev2-ikesa
auth-method-set <auth_profile_name1> <auth_profile_name2>
        ikev2-ikesa
transform-set list <ikesa_transform_set_name>
        payload <crypto_template_payload_name>
match childsa match ipv4
            ipsec
transform-set list  <ipsec_transform_set_name> 
            exit 
        certificate <cert_name>
        ca-certificate
list ca-cert-name <cacert_name>
      exit
Notes:
  • <ctxt_name> is the context name on which unique EAP name is to configured.
  • <eap_profile_name> is a string of size 1 to 128 which configure the context level unique Extensible Authentication Profile (EAP) Name.
  • <ipsec_transform_set_name> configures the context level name to be used for the IKEv2 IKE Security Association Transform Set. It is a string of size 1 to 127.
  • <crypto_template_name> configures the name of the Crypto Template. It is a string of size 1 to 104.
  • <crypto_template_payload_name> is the name of the Crypto Template Payload being configured. This name is unique to the Crypto Template. It is a string of size 1 to 127.

GTP-U Service Configuration

Use the following example to configure the GTP-U service parameters to provide GTP-U tunnel over S1-U interface. The two GTP-U

configure
  context
<dest_ctxt_name>
-noconfirm
    gtpu-service
<gtpu_svc_access>
-noconfirm
      bind
address { ipv4-address | ipv6-address } <ip_address>
      end 
configure
  context
<dest_ctxt_name>
-noconfirm
    gtpu-service
<gtpu_svc_network>
-noconfirm
      bind
address ipv4-address <ip_address>
      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_svc_access> is name of the GTP-U service configured to provide GTP-U tunnel over S1-U interface towards S-GW or core network. This service has to be associated with the HeNB-GW Access Service in case S1-U Relay is enabled.
  • <gtpu_svc_network> is name of the GTP-U service configured to provide GTP-U tunnel over towards HeNB. This service has to be associated with the HeNB-GW Access Service in case S1-U Relay is enabled.

LTE Policy Configuration

Use the following example to configure the LTE Policy. Other configurations done under this config include MME pool and tracking area information list (TAI list) database.

configure
  lte-policy
    henbgw
mme-pool <mme_pool_name>
-noconfirm
      mme
<mme-name> { ipv4-address | ipv6-address } <ip_addr>
sctp port <sctp_port_no> 
      exit
    tai-list-db <lte_policy_tai_db>
      tai
mcc <mcc_id>
mnc <mnc_id>
tac <tac_code1> <tac_code2> <tac_code3>
    exit
  end 
Notes:
  • <mme_pool_name> is a string of size 1 to 63, which configures a specified MME pool.
  • <mme-name> is a string of size 1 to 63, which configures a specific MME.
  • <ipv4_addr> is the remote SCTP IP address for S1 association to configured MME.
  • <sctp_port_no> is the SCTP port which is an integer ranging from 1 to 65535.
  • <lte_policy_tai_db> is the tracking area information list database, which must be a string of size 1 to 64.
  • <mcc_id> is a three digit number between 100 to 999.
  • <mnc_id> is two/three digit number between 00 to 999
  • <tac_code1> is the tracking area code value ranging as a integer from 0 ... 65535. Up to 256 can be defined on one line.

Verifying HeNB-GW Configuration

This section shows the configuration parameters configured for HeNB-GW service.
  1. Verify that your HeNB-GW services were created and configured properly by entering the following commands in Exec Mode:
    show henbgw-access-service
    name <henbgw_access_svc_name>}
    
    show henbgw-network-service
    name <henbgw_network_svc_name>}
    
    The output of these command display concise listing of HeNB-GW Access and Network service parameter settings as configured on system.
  2. Verify configuration errors of your HeNB-GW services by entering the following command in Exec Mode:
    show configuration
    errors section henbgw-network-service}
    
    The output of this command displays current configuration errors and warning information for the target configuration file as specified for HeNB-GW Network service

Logging Facility Configuration

Use the following example to configure the HeNB-GW system to enable the logging and debug facilities for HeNB-GW subscriber and related protocols.

IMPORTANT:

This section provides the minimum instruction set for configuring logging facilities for system monitoring that allows the user to monitor the events and logging. commands that configure additional logging facilities are provided in the Exec Mode Command chapter of Command Line Interface Reference.

logging filter active
facility henbapp level { critical | error | warning | unusual | info | trace | debug }
logging filter active
facility henbgw level { critical | error | warning | unusual | info | trace | debug }
logging filter active
facility henbgwdemux level { critical | error | warning | unusual | info | trace | debug }
logging filter active
facility henbgwmgr level { critical | error | warning | unusual | info | trace | debug }
configure
  logging
console
  logging
display event-verbosity {min | concise | full}
  logging
filter runtime facility henb-gw level { critical | error | warning | unusual | info | trace | debug }
  logging
filter runtime facility henbapp level { critical | error | warning | unusual | info | trace | debug }
  logging
filter runtime facility henbgwdemux level { critical | error | warning | unusual | info | trace | debug }
  logging
filter runtime facility henbgwmgr level { critical | error | warning | unusual | info | trace | debug }
  logging
filter runtime facility sctp { critical | error | warning | unusual | info | trace | debug }
  logging
filter runtime facility threshold { critical | error | warning | unusual | info | trace | debug }

IMPORTANT:

Refer System Administration Guide for more information on logging facility configuration.

Displaying Logging Facility

This section shows the logging facility event logs for logging facilities enabled on HeNB-GW node.
  1. Verify the logging facilities configured on HeNB-GW system node by entering the following command in Exec Mode:
    show logging [ active | verbose]
    
    The output of this command provides the display of event logs for all configured logging facilities.

Alarm and Alert Trap Configuration

To enable and configure the SNMP Traps to generate alarms and alerts from system for various events and thresholds in HeNB-GW service, apply the following example configuration:

configure
  snmp
trap enable ThreshHENBGWHenbSessions target [ target <trap_collector>]
  snmp
trap enable ThreshHENBGWPagingMessages target <trap_collector>]
  snmp
trap enable ThreshHENBGWUeSessions target <trap_collector>]
  snmp
trap { enable | suppress} HenbgwAccessServiceStart
 [ target <trap_collector>]
  snmp
trap { enable | suppress} HenbgwAccessServiceStop
 [ target <trap_collector>]
  snmp
trap { enable | suppress} HenbgwMMESCTPAllAssocDown
 [ target <trap_collector>]
  snmp
trap { enable | suppress} HenbgwMMESCTPAllAssocDownClear
 [ target <trap_collector>]
  snmp
trap { enable | suppress} HenbgwMMESCTPAssocDown
 [ target <trap_collector>]
  snmp
trap { enable | suppress} HenbgwMMESCTPAssocUp
 [ target <trap_collector>]
  snmp
trap { enable | suppress} HenbgwNetworkServiceStart
 [ target <trap_collector>]
  snmp
trap { enable | suppress} HenbgwNetworkServiceStop
 [ target <trap_collector>]
Notes:
  • <trap_collector> is the name of the 1st trap target. It is a string of size 1 to 31.
  • There are several additional SNMP Traps which can be configured. Refer Global Configuration Mode chapter of the Command Line Interface Reference for more information.
  • For more information on SNMP Traps, refer System SNMP-MIB Reference.
  • Repeat this configuration as needed for additional traps.

SNMP MIB Traps for HeNB-GW Service

SNMP traps are used to manage and monitor the service on HeNB-GW node.

Supported SNMP traps and its id are indicated in the following table.
Table 4. SNMP Traps and Object Ids
Traps Object Id
starThreshHENBGWHenbSessions starentTraps 513
starThreshClearHENBGWHenbSessions starentTraps 514
starThreshHENBGWUeSessions starentTraps 515
starThreshClearHENBGWUeSessions starentTraps 516
starThreshHENBGWPagingMessages starentTraps 517
starThreshClearHENBGWPagingMessages starentTraps 518
starHenbgwAccessServiceStart starentTraps 1193
starHenbgwAccessServiceStop starentTraps 1194
starHenbgwNetworkServiceStart starentTraps 1195
starHenbgwNetworkServiceStop starentTraps 1196
starHenbgwMMESCTPAssocUp starentTraps 1227
starHenbgwMMESCTPAssocDown starentTraps 1228
starHenbgwMMESCTPAllAssocDown starentTraps 1229
starHenbgwMMESCTPAllAssocDownClear starentTraps 1230


IMPORTANT:

For more information on SNMP trap configuration and supported object ids, refer System SNMP-MIB Reference.

Event IDs for HeNB-GW Service

Identification numbers (IDs) are used to reference events as they occur when logging is enabled on the system. Logs are collected on a per facility basis.

Each facility possesses its own range of event IDs as indicated in the following table. Following table lists HeNB-GW specific and other required facilities and corresponding Event ID Ranges:

IMPORTANT:

Not all event IDs are used on all platforms. It depends on the platform type and the license(s) running.

For more information on logging facility configuration and event id, refer Configuring and Viewing System Logs chapter in System Administration Guide.
Table 5. System Event Facilities and ID Ranges
Facility Event ID Range
HeNB-GW Manager Facility Events 193000-193999
HeNB-GW Facility Events 195000-195999
HeNB-GW DEMUX Facility Events 194000-194999
SCTP Protocol Facility Events 87300-87499
AAA Client Facility Events 6000-6999
Alarm Controller Facility Events 65000-65999
Card/Slot/Port (CSP) Facility Events 7000-7999
Command Line Interface Facility Events 30000-30999
Event Log Facility Events 2000-2999
Threshold Facility Events 61000-61999


DHCP Configuration

To configure DHCP Proxy interface support on chassis for HeNB-GW service:

  1. Create a DHCP service specific to HeNB-GW service by applying the example configuration in the Configuring DHCP Service section.
  2. Create a subscriber template for HeNB clients sesssion and associate the DHCP service with created subscriber template by applying the example configuration in the Configuring Subscriber Template for HeNB section.
  3. Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration. For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.

Configuring DHCP Service

Configure a DHCP service for DHCP interface support in the HeNB-GW service by applying the following example configuration:

configure
  context <vpn_ctxt_name>
    dhcp-service
<dhcp_svc_name>
-noconfirm
      dhcp
client-identifier ike-id
      dhcp
server selection-algorithm use-all
      dhcp
server <dhcp_server_ip>
      dhcp
server port 67
      end
Notes:
  • <vpn_ctxt_name> is name of the source context for DHCP service.
  • <dhcp_svc_name> is name of the DHCP service configured in Context Configuration mode for DHCP interface support in HeNB-GW service.
  • <dhcp_server_ip> IP address of the DHCP server associated with DHCP service for DHCP interface support in HeNB-GW service.
  • For more commands and keyword options, refer Command Line Interface Reference.

Configuring Subscriber Template for HeNB

Configure the subscriber template to associate the DHCP service for HeNB clients by applying the following example configuration:

configure
  context <vpn_ctxt_name>
    subscriber
default
      dhcp
service <dhcp_svc_name> context
<vpn_ctxt_name>
      end
Notes:
  • <vpn_ctxt_name> is name of the source context in which Security gateway is configured.
  • <dhcp_svc_name> is name of the pre-configured DHCP service configured in Context Configuration mode for DHCP interface support in HeNB-GW service.
  • For more commands and keyword options, refer Command Line Interface Reference.

DHCP Service Engineering Rules

The following engineering rule applies to the DHCP Service:
  • Up to 8 DHCP servers may be configured per DHCP service.
  • A maximum of 3 DHCP server can be tried for a call.