# HNB-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 HNB-GW functionality for use in HNB 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:

- Information Required to Configure the System as an HNB-GW
- RTP Pool Configuration
- HNB-GW Service Configuration
- DSCP Marking Configuration
- DHCP Configuration
- IuCS over ATM Configuration
- Iu-Flex Configuration
- Logging Facility Configuration
- Congestion Control Configuration
- Alarm and Alert Trap Configuration
- SNMP-MIB Traps for HNB-GW Service
- Event IDs for HNB-GW Service

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 HNB-GW

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

- Required Local Context Configuration Information
- Required System-Level Configuration Information
- Required Source Context Configuration Information
- Required Destination Context Configuration Information

Note:

The following sections describe the minimum amount of information required to configure and make the HNB-GW operational on the 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 HNB-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 HNB-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 System-Level Configuration Information

The following table lists the information that is required to configure at the system-level Global configuration mode (context independent) to support 3G UMTS Femto support.
Table 2. Required Information for System Configuration

Required Information | Description
--- | ---
SS7 Routing Domain Configuration
SS7 Routing Domain id and variant | An identification for SS7 routing domain and must be an integer between 1 and 12 by which the SS7 routing domain will be identified and configured. A variant can be configured for the SS7 routing domain. some of them are: ansi: American National Standards Institute (U.S.A.) bici: Broadband Intercarrier Interface standard china: Chinese standard itu: International Telecommunication Union (ITU-T) Telecommunication Standardization Sector ntt: Japanese standard ttc: Japanese standard
Sub Service Field (SSF) | A network indicator in the subservice field for SS7 message signal units (MSUs). It can be configured with any of the following indicators: International National Reserved Spare
Application Server Process (ASP) instance | An M3UA Application Server Process (ASP) instance identified from 1 through 4. This instance need to configure end point address as well.
Peer server id | Specifies a peer server instance to setup a SIGTRAN peer for sending and receiving M3UA traffic. Up to 49 peer servers can be defined. A peer server id configuration may contain: Routing context for peer server to use Self point code in SS7 type address Operational Mode Peer Server Process (PSP) instance
Peer Server Process (PSP) instance | Specifies the peer server process instance in peer server id. The instance must be an integer from 1 to 4. A PSP instance configuration need to define: PSP mode: client or server Exchange mode: double ended or single ended End point address in SS7 address format Association of ASP instance
Signaling Connection Control Part (SCCP) Network Instance Configuration
SCCP Network Instance and variant | An identification for SCCP network instance and must be an integer between 1 and 12 by which the SCCP network instance will be identified and configured. A variant can be configured for the SS7 routing domain. some of them are: ansi: American National Standards Institute (U.S.A.) china: Chinese standard itu: International Telecommunication Union (ITU-T) Telecommunication Standardization Sector ntt: Japanese standard ttc: Japanese standard
SS7 Routing Domain id and variant | An identification for SS7 routing domain and must be an integer between 1 and 12 by which the SS7 routing domain will be identified and associated with this SCCP network instance.
Destination point code | Specifies the destination point code (DPC) in SS7 address format along with SSN and SCCP version.
Circuit Switched Network Configuration
Circuit Switched Network instance | An identification string between 1 and 63 characters (alpha and/or numeric) by which the Circuit Switched Core Networks instance which needs to be associated with HNB Radio Network PLMN id. An HNB-CS network instance is required for Femto UMTS access over IuCS/Iu-Flex interface between HNB-GW service and CS networks elements; i.e. MSC/VLR. Multiple CS network instances (maximum 8) can be configured on a system.
SCCP Network id | Specifies a predefined Signaling Connection Control Part (SCCP) network id in at system level in Global configuration mode to be associated with the CS network instance in order to route the messages towards MSC/VLR over IuCS interface.
RTP IP Pool name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the RTP pool is configured and associated with CS network configuration to allocate RTP IP address to session managers in HNB-GW service over IuCS towards CS core networks.
Default MSC point code | Specifies the default MSC point-code with HNB-CS network instance. This MSC point code (SS7 address) is used when HNB-GW is to be connected to only one MSC with in a CS network or as default MSC for all HNBs connected through specific HNB-CS network instance.
Packet Switched Network Configuration
Packet Switched Network instance | An identification string between 1 and 63 characters (alpha and/or numeric) by which the Packet Switched Core Networks instance which needs to be associated with HNB Radio Network PLMN id. An HNB-CS network instance is required for Femto UMTS access over IuPS/Iu-Flex interface between HNB-GW service and PS networks elements; i.e. SGSN. Multiple PS network instances (maximum 8) can be configured on a system.
SCCP Network id | Specifies a predefined Signaling Connection Control Part (SCCP) network id in at system level in Global configuration mode to be associated with the PS network instance in order to route the messages towards SGSN over IuPS interface.
GTP-U service name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the GTP-U service can be associated with HNB-GW system in PS network instance for GTP-U tunnel towards core network. It is pre-configured in destination context. Multiple names are needed if multiple GTP services is used. IMPORTANT: One GTP-U service can be associated in PS network instance to provide GTP-U tunnel over IuPS interface towards PS core network and another GTP-U service needs to be associated in HNB-GW service instance for GTP-U tunnel over Iuh interface towards HNB.
Default SGSN point code | Specifies the default SGSN point-code with HNB-CS network instance. This SGSN point code (SS7 address) is used when HNB-GW is to be connected to only one SGSN with in a PS network or as default SGSN for all HNBs connected through specific HNB-PS network instance.

Required Source Context Configuration Information

The following table lists the information that is required to configure the Source context on an HNB-GW.
Table 3. 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.
Iuh Interface Configuration (To/from Home-NodeB)
HNB-GW service Name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the HNB-GW service can be identified on the system. It is configured in Context configuration mode.Multiple names are needed if multiple HNB-GW services will be configured.
HNB-GW Service Configuration
Iuh interface IP address | IPv4 addresses assigned to the Iuh interface as SCTP bond address. This address will be used for binding the SCTP (local bind address(es)) to communicate with the HNBs using GTP-U.The HNB-GW passes this IP address during setting up the SCTP association with the HNB. Multiple addresses and subnets are needed if multiple interfaces will be configured.
Iuh SCTP Port | The physical port to which the Iuh interface will be bound. The local SCTP port used to communicate with the HNBs over Iuh interface.
RTP IP address | This is the IP address of HNB-GW which is configured as RTP address and sent to HNB to map the RTP streams with this IP address on HNB-GW. This configuration is required at HNB-GW to communicate with MSC/VLR over IuCS-over-IP tunnel.
RTP IP Pool name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the RTP pool is configured and associated with HNB-GW service to allocate RTP IP address to Session Manager instances over Iuh towards HNB.
Optional Security Gateway Configuration
Security Gateway IP address | This is the IP Address where the SeGW service is bound and shall be provided to HNB during SeGW-Discovery. Only one SeGW IP address can be configured.
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 as an Iuh. This crypto-map template is to be associated with HNB-GW service if SeGW is enabled and bind with HNB-GW service. 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 HNB-GW service.
RTP Pool Configuration
RTP IP Pool name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the RTP pool can be identified on the system to allocate RTP IP address to session manager instances over Iuh towards HNB. It is to be associated with HNB-GW service.
Radio Network PLMN Configuration
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.
Radio Network Controller (RNC) identifier | Specify the RNC id which shall be provided to HNB during HNB-REGISTRATION procedure. Depending upon the requirement the RNC-ID can be provided with the desired granularity in HNB-PS networks or HNB-CS Network Configuration.
GTP-U service name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the GTP-U service can be associated with HNB-GW system in HNB-GW service for GTP-U tunnel towards HNB access network (HNB). It is pre-configured in Context configuration mode. Multiple names are needed if multiple GTP-U services is used. IMPORTANT: One GTP-U service can be associated with HNB-GW service instance to provide GTP-U tunnel over Iuh interface towards HNB access network (HNB) and another GTP-U service needs to be associated with PS network instance for GTP-U tunnel over IuPS interface towards PS core network to GSNs.
GTP-U Tunnel Innerves Configuration
GTP-U service name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the GTP-U service can be associated with HNB-GW system for GTP-U tunnel towards HNB access network (HNB). Various control parameters can be configured for GTP-U packet transmission. Multiple names are needed if multiple GTP services is used.
GTP-U Tunnel interface IP address | IPv4 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 HNB using GTP-U tunnel. Multiple addresses and subnets are needed if multiple interfaces will be configured.
GTP-U Tunnel interface Port | The physical port to which the Iuh interface will be bound. The local GTP-U port used to communicate with the HNB over GTP-U tunnel interface.

Required Destination Context Configuration Information

The following table lists the information that is required to configure the destination context.
Table 4. 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.
GTP-U Tunnel Interface Configuration
GTP-U service name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the GTP-U service can be associated with HNB-GW system in PS network instance for GTP-U tunnel towards core network. Various control parameters can be configured for GTP-U packet transmission. Multiple names are needed if multiple GTP services is used.
GTP-U Tunnel interface IP address | IPv4 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 PS core network using GTP-U tunnel. Multiple addresses and subnets are needed if multiple interfaces will be configured.
GTP-U Tunnel interface Port | The physical port to which the Iuh interface will be bound. The local GTP-U port used to communicate with the PS core network over GTP-U tunnel interface.
RTP Pool Configuration
RTP IP Pool name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the RTP pool can be identified on the system to allocate RTP IP address to session manager instances over IuCS towards CS core networks. It is to be associated with PS network configuration.

## RTP Pool Configuration

This configuration sets the IP pools for assigning IP addresses per session manager. The session manager acts as a mediator between HNB and MSC, shielding the IP address details of either end-point from the other one. It works on both way of connection in establishing a RTP session between the HNB and HNB-GW over Iuh and between HNB-GW and the core network over IuCSoIP. Upon successful authentication of HNB, the session manager instances are assigned with a RTP IP addresses during HNB-GW service bringing up and similarly for CS-network connectivity in case of IuCSoIP.

IP addresses can be dynamically assigned from a single pool/a group of IP pools/a group of IP pool groups. The addresses/IP pools/ IP pool groups are placed into a queue in each pool or pool group. An address is assigned from the head of the queue and, when released, returned to the end. This method is known as least recently used (LRU).

When a group of pools have the same priority, an algorithm is used to determine a probability for each pool based on the number of available addresses, then a pool is chosen based on the probability. This method, over time, allocates addresses evenly from the group of pools.

IMPORTANT:

Note that setting different priorities on each individual pool can cause addresses in some pools to be used more frequently.

To configure the RTP IP pool:

1. Create the RTP IP pool for IPv4 addresses in source context for RTP pool allocation over Iuh interface by applying the example configuration in the IPv4 RTP Pool Creation Over IuCS section.
2. Create the RTP IP pool for IPv4 addresses in destination context for RTP pool allocation over IuCS interface by applying the example configuration in the IPv4 RTP Pool Creation Over Iuh section.
3. Verify your RTP IP pool configuration by applying the example configuration in the RTP IP Pool Configuration Verification section.
4. 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.

IPv4 RTP Pool Creation Over IuCS

Use the following example to create the IPv4 address RTP pool for RTP address allocation over IuCS interface towards CS core network.

    configure

       context <dest_ctxt_name>

          ip
    pool <cs_ip_pool_name> <ip_address/mask>

          end

Notes:

- <cs_ip_pool_name> is name of the IP pool configured in destination context named <dest_ctxt_name> and to be associated with CS Network Configuration to allocate RTP end point address towards CS network over IuCS interface.
- IP pool size needs to be determined on the number of sessMgr instances on HNB-GW. It uses one IP address for each session manager instance of user.
- To ensure proper operation with CS network configuration, RTP IP pools should be configured within a destination context.
- For more information on commands/keywords that configure additional parameters and options, refer ip pool command section in Context Configuration Mode Commands chapter of Command Line Interface Reference.

IPv4 RTP Pool Creation Over Iuh

Use the following example to create the IPv4 address RTP pool for RTP address allocation over Iuh interface towards HNB.

    configure

       context <dest_ctxt_name>

          ip
    pool <ip_pool_name> <ip_address/mask>

          end

Notes:

- <ip_pool_name> is name of the IP pool configured in destination context named <dest_ctxt_name> and associated with HNB-GW service to allocate the RTP end point address in HNB-GW service over Iuh interface.
- To ensure proper operation with HNB-GW configuration, RTP IP pools must be configured within the same context as HNB-GW.
- IP pool size needs to be determined on the number of sessMgr instances on HNB-GW. It uses one IP address for each session manager instance of user.
- To ensure proper operation with CS network configuration, RTP IP pools should be configured within a destination context.
- Each address in the pool requires approximately 24 bytes of memory. Therefore, in order to conserve available memory, the number of pools may need to be limited depending on the number of addresses to be configured and the type and number of data processing cards installed.
- Setting different priorities on individual pools can cause addresses in some pools to be used more frequently.
- For more information on commands/keywords that configure additional parameters and options, refer ip pool command section in Context Configuration Mode Commands chapter of Command Line Interface Reference.

### RTP IP Pool Configuration Verification

1. Verify that your IPv4 address pool configured properly by entering the following command in Exec Mode:

       show ip pool

   The output from this command will look similar to the sample shown below. In this example all IP pools were configured in the isp1 context.context : isp1:+-----Type: (P) - Public (R) - Private| (S) - Static (E) - Resource||+----State: (G) - Good (D) - Pending Delete (R)-Resizing||||++--Priority: 0..10 (Highest (0) .. Lowest (10))||||||||+-Busyout: (B) - Busyout configured||||||||||vvvvv Pool Name Start Address Mask/End Address Used Avail----- --------- --------------- --------------- ------ ------PG00 ipsec 12.12.12.0 255.255.255.0 0 254RG00 pool3 30.30.0.0 255.255.0.0 0 65534SG00 pool2 20.20.0.0 255.255.0.0 10 65524PG00 pool1 10.10.0.0 255.255.0.0 0 65534SG00 vpnpool 192.168.1.250 192.168.1.254 0 5Total Pool Count: 5

## HNB-GW Service Configuration

HNB-GW services are configured within source contexts and allow the system to function as an HNB-GW in the 3G UMTS wireless data network.

IMPORTANT:

This section provides the minimum instruction set for configuring an HNB-GW service that allows the system to process bearer contexts with IPsec authentication on SeGW. Commands that configure additional HNB-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 HNB-GW service with SeGW enabled:

1. Optional. Configure threshold parameters by applying the example configuration in the Total HNB-GW Session Thresholds chapter in Thresholding Configuration Guide.
2. Optional. Configure system to enable logging facilities for HNB-GW service session subscriber and protocols by applying the example configuration in the Logging Facility Configuration section.
3. Optional. Configure congestion control parameters for HNB-GW service instance on system by applying the example configuration in the Congestion Control Policy Configuration section.
4. Optional. Enable and configure the SNMP Traps to generate alarms and alerts from system for various events and thresholds for HNB-GW service instance by applying the example configuration in the Alarm and Alert Trap Configuration section.
5. Configure system to use source Boxer Internal address (SBIA) in hashing function for ECMP-LAG distribution of RTP traffic over IuCS interface for by applying the example configuration in the Hashing Algorithm Configuration section.
6. Create an interface in source context for Iuh interface by applying the example configuration in the Iuh Interface Configuration section.
7. Configure SS7 routing domain by applying the example configuration in the SS7 Routing Domain Configuration section.
8. Configure Peer Server identity for Circuit Switched (CS) core network in SS7 routing domain by applying the example configuration in the Peer Server Id Configuration for CS Core Network section.
9. Configure Peer Server identity for Packet Switched (PS) core network in SS7 routing domain by applying the example configuration in the Peer Server Id Configuration for PS Core Network section.
10. Configure SCCP network id with national variant by applying the example configuration in the SCCP Network Instance Configuration section.
11. Configure CS network parameters by applying the example configuration in the HNB-CS Network Configuration section.
12. Configure PS network parameters by applying the example configuration in the HNB-PS Network Configuration section.
13. Configure GTP-U service parameters by applying the example configuration in the GTP-U Service Configuration section.
14. Configure RTP pool parameters by applying the example configuration in the RTP Pool Configuration section.
15. Create and configure the global parameters for HNB-GW service(s) configured on a single chassis by applying the example configuration in the HNB-GW Global Configuration section.
16. Create and configure the HNB-GW service and associate related parameters with HNB-GW by applying the example configuration in the HNB-GW Service Configuration section.
17. Optional. Configure Security Gateway parameters with Crypto-template and enable SeGW by associating it with HNB-GW to enabling SeGW by applying the example configuration in the Security Gateway and Crypto Template Configuration section.
18. Optional. Configure x.509 security certificate for FAP with Crypto-template by applying the example configuration in the x.509 Certificate Configuration section.
19. Optional. Modify the HNB-CS Network configuration to support multiple MSC selection without Iu-Flex by applying the example configuration in the Multiple MSC Selection without Iu-Flex Configuration section.
20. Optional. Modify the HNB-GW service configuration to support the Open Access mode support for open HNBs and paging parameters by applying the example configuration in the Open Access Mode Configuration section.
21. Optional. Modify the HNB-GW service configuration to support the Hybrid Access mode support for Hybrid HNBs and paging parameters by applying the example configuration in the Hybrid Access Mode Configuration section.
22. Verify your HNB-GW configuration by following the steps in the HNB-GW Service Configuration Verification section.
23. 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.

Hashing Algorithm Configuration

Use the following example to configure the system to use SBIA for hashing algorithm in ECMP-LAG for even distribution of RTP packets over IuCS interface:

CAUTION:

This configuration is mandatory for standalone HNB-GW deployment and highly recommended in other deployment scenarios where HNB-GW is used in combination with other services.

    configure

      ecmp-lag
    hash use-sbia-only

      end

Notes:

- This is a global configuration level command and will apply to all services configured on chassis.
- This configuration provides the even distribution of RTP traffic seen over IuCS interface.
- If this option is not chosen, system uses IP Source Address, IP Destination Address, IP Protocol and Source Boxer Internal Address as inputs to the hashing algorithm for ECMP-LAG distribution.

Iuh Interface Configuration

Use the following example to configure the Iuh interfaces in source context:

    configure

      context
    <vpn_ctxt_name>
    -noconfirm

        interface <intf_name>

          ip
    address <ip_address>

          end

Notes:

- <vpn_ctxt_name> is name of the source context in which HNB-GW service is to configure.
- <intf_name> is name of the interface which is to be used for Iuh reference between HNB-GW and HNB.

SS7 Routing Domain Configuration

Use the following example to configure the SS7 routing domain id for HNB-GW service on system:

    configure

      ss7-routing-domain
    <Ss7rd_id> variant
    <v_type>
    -noconfirm

        ssf {international | national | reserved | spare}

        asp
    instance <asp_instance>

          end-point
    address <end_point_address>
    context <end_ctxt_name>

          end-point
    bind

          end

Notes:

- <end_point_address> is IP address of the end point associated with application server process for M3UA end-point parameters in a specific SS7 routing domain instance.
- <end_ctxt_name> is name of the context which is associated with end point IP address for application server process for M3UA end-point parameters in a specific SS7 routing domain instance.

Peer Server Id Configuration for PS Core Network

Use the following example to configure the Peer Server Id in SS7 routing domain for PS core network on system:

    configure

      ss7-routing-domain
    <ss7rd_id> variant
    <v_type>

        peer-server
    id <peer_server_id>

          name
    <sgsn_name>

          mode {loadshare | standby}

          routing-context <routing_ctxt_id>

          self-point-code
    <sgsn_pointcode>

          psp
    instance <psp_instance_id>

            psp-mode {client | server}

            exchange-mode [double-ended | single-ended]

            end-point
    address <end_point_address>

            associate
    asp instance<asp_instance>

            end

Notes:

- <ss7rd_id> is SS7 Routing domain identity number already configured for SS7 routing domain instance.
- <sgsn_pointcode> is the address of SGSN configured in HNB-PS Network Configuration section and to be used for SCCP network instance.

Peer Server Id Configuration for CS Core Network

Use the following example to configure the Peer Server Id in SS7 routing domain for CS core network on system:

    configure

      ss7-routing-domain
    <ss7rd_id> variant
    <v_type>

        peer-server
    id <peer_server_id>

          name
    <msc_name>

          mode {loadshare | standby}

          routing-context <routing_ctxt_id>

          self-point-code
    <msc_pointcode>

          psp
    instance <psp_instance_id>

            psp-mode {client | server}

            exchange-mode [double-ended | single-ended]

            end-point
    address <end_point_address>

            associate
    asp instance <asp_instance>

            end

Notes:

- <ss7rd_id> is SS7 Routing domain identity number already configured for SS7 routing domain instance.
- <msc_pointcode> is the address of MSC configured in HNB-CS Network Configuration section and to be used for SCCP network instance.

SCCP Network Instance Configuration

Use the following example to configure the SCCP network instance to be associated with HNB-GW service on system:

    configure

      sccp-network
    <sccp_id>
    variant <v_type>
    -noconfirm

        self-point-code
    <ss7_pointcode>

        associate
    ss7-routing-domain <ss7rd_id>

        destination
    dpc <sgsn_pointcode> name
    <dpc_route_name>

        destination
    dpc <sgsn_pointcode> version
    <sccp_variant>

        destination
    dpc <sgsn_pointcode> ssn
    <dest_subsystem_num>

        destination
    dpc <msc_pointcode> name
    <dpc_route_name>

        destination
    dpc <msc_pointcode> version
    <sccp_variant>

        destination
    dpc <msc_pointcode> ssn
    <dest_subsystem_num>

        end

Notes:

- <sccp_id> is SCCP network identifier to be associated with HNB-GW.
- <v_type> is type of variant to be used for SCCP network instance.
- <sgsn_pointcode> is the address of SGSN configured in HNB-PS Network Configuration section and to be used for SCCP network instance.
- <msc_pointcode> is the address of MSC configured in HNB-CS Network Configuration section and to be used for SCCP network instance.

HNB-PS Network Configuration

Use following example to configure the packet switched network parameters at system level to support HNB-GW service on system:

    configure

      ps-network
    <ps_network_name>
    -noconfirm

        global-rnc-id
    mcc <mcc_num>
    mnc <mnc_num>
    id <rnc_id>

        ranap
    reset {ack-timeout <timer_value> | guard-timeout <g_timer> | hnbgw-initiated | max-retransmissions <retries>}

        associate
    sccp-network <sccp_network_id>

        associate
    gtpu-service <gtpu_ps_svc_name>
    context <dest_ctxt_name>

        sgsn
    point-code <sgsn_point_code>

        no
    sgsn deadtime

        map
    core-network-id cn_id point-code
    <sgsn_point_code>

        end

Notes:

- <ps_network_name> is name of the packet switched network used with HNB-GW for IuPS session.
- <sgsn_point_code> is address of the SGSN in SS7 point code format to be used for packet switched traffic through HNB-GW.
- <gtpu_svc_name> is name of the GTP-U service configured in <gtpu_ctxt_name> to provide GTP-U tunnel over IuPS interface for packet switched traffic towards PS-CN.

HNB-CS Network Configuration

Use following example to configure the circuit switched network parameters at system level to support HNB-GW service on system:

    configure

      cs-network
    <cs_network_name>
    -noconfirm

        global-rnc-id
    mcc <mcc_num>
    mnc <mnc_num>
    id <rnc_id>

        ranap
    reset {ack-timeout <timer_value> | guard-timeout <g_timer> | hnbgw-initiated | max-retransmissions <retries>}

        associate
    rtp-pool <cs_ip_pool_name>
    context <dest_ctxt_name>

        associate
    sccp-network <sccp_network_id>

        msc
    point-code <msc_point_code>

        no
    msc deadtime

        map
    core-network-id cn_id point-code
    <msc_point_code>

        end

Notes:

- <cs_network_name> is name of the HNB-CS Network used with HNB-GW for IuPS session.
- <msc_point_code> is address of the MSC in SS7 point code format to be used for circuit switched call through HNB-GW.
- <cs_ip_pool_name> is name of the IP pool configured in destination context named <dest_ctxt_name> to allocate RTP end point address in this CS network over IuCS interface.

HNB-GW Global Configuration

Use the following example to configure the HNB-GW Global parameters on system to provide global parameters to all HNB-GW service on a single chassis.

    configure

      hnbgw-global

        access-control-db { imsi-purge-timeout <purge_timeout>
     | immediate }

        tnnsf-timer
    <timer_value>

        sctp
    alpha-rto <alpha_rto_dur>

        sctp
    beta-rto <beta_rto_dur>

        sctp
    max-retx [init | path | assoc] <max_retry>

        sctp
    max-in-strms <in_strms>

        sctp
    max-out-strms <out_strms>

        end

Notes:

- Global parameters for HNB-GW services on a chassis are provided through this configuration.

HNB-GW Service Configuration

Use the following example to configure a single of multiple HNB-GW service on system in source context to provide access to HNBs towards core networks:

    configure

      sgsn-global

        aggregate-ipc-msg { linkmgr | sessmgr } { flush-frequency frequency  | num-msgs number_msgs }

        exit

      context <vpn_ctxt_name>

        hnbgw-service
    <hnbgw_svc_name>
    -noconfirm

          sctp
    bind address <ip_address>

          sctp
    bind port <sctp_port>

          rtp
    mux

          rtcp
    report interval <dur>

          associate
    rtp-pool <ip_pool_name>

          associate
    gtpu-service <gtpu_iuh_svc_name>

          no
    handin cn-domain cs

          radio-network-plmn
    mcc <mcc>
    mnc <mnc_code>

            rnc-id <rnc_id>

            end

Notes:

- `aggregate-ipc-msg` is an optional command supplied through SGSN Global Configuration mode and used to reduce the latency of IPC messages in SessMgr or LinkMgr towards CN. For more information, refer Performance Improvement Commands section in Troubleshooting the Service chapter of this guide.
- <vpn_ctxt_name> is name of the source context in which HNB-GW service is configured.
- <hnbgw_svc_name> is name of the HNB-GW service which is to be configured for used for Iuh reference between HNB-GW and HNB. Multiple HNB-GW service can be configured in a single or multiple context on a single chassis.
- <ip_address> is the SCTP IP address on which is HNB will communicate with HNB-GW and has characteristics of Iuh interface.
- <gtpu_iuh_svc_name> is name of the GTP-U service configured in <vpn_ctxt_name> to provide GTP-U tunnel over Iuh interface towards HNB.
- <ip_pool_name> is name of the IP pool configured in source context named <vpn_ctxt_name> to allocate RTP end point address to session manager instance in HNB-GW service over Iuh interface.
- `rtcp report interval <dur>` command configures the generation of RTCP packet/ report types on a per HNB-GW service instance basis and sets the specified time interval <dur> in seconds between two consecutive RTCP reports.

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.

    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.
- <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.

    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>}

        ca-certificate
    name <ca_root_cert_name>
    pem { data <pem_data_string> | url <pem_data_url>}

          exit

        crypto
    template <segw_crypto_template>
    ikev2-dynamic

          authentication
    local certificate

          authentication
    remote certificate

          keepalive
    interval <dur>
    timeout <dur_timeout>

          certificate <x.509_cert_name>

          ca-certificate
    list ca-cert-name <ca_root_cert_name>

          payload
    <crypto_payload_name> match
    childsa [match {ipv4 | ipv6}]

            ip-address-alloc
    dynamic

            ipsec
    transform-setlist <ipsec_trans_set>

            end

    configure

      context <vpn_ctxt_name>

        subscriber
    default

          ip
    context-name <vpn_ctxt_name>

          ip
    address pool name <ip_pool_name>

          end

Notes:

- <vpn_ctxt_name> is name of the source context in which HNB-GW service is configured.
- <x.509_cert_name> is name of the x.509 certificate where PEM data <pem_data_string> and PKI <PKI_pem_data_string> is configured.
- <ca_root_cert_name> is name of the CA root certificate where PEM data <pem_data_string> is configured for CPE.

Security Gateway and Crypto map Template Configuration

Use the following example to configure the IPsec profile and Crypto map template enabling SeGW on HNB-GW for IPsec tunneling.

    configure

      context <vpn_ctxt_name>

        eap-profile <eap_prof_name>

          mode
    authentication-pass-through

          exit

        ip
    pool ipsec <ip_address> <subnetmask>

        ipsec
    transform-set <ipsec_trans_set>

          exit

        ikev2
    transform-set <ikev2_trans_set>

          exit

        crypto
    template <crypto_template>

          authentication
    eap-profile <eap_prof_name>

            exit

          ikev2-ikesa
    transform-set list <ikev2_trans_set>

          payload
    <crypto_payload_name> match
    childsa [match {ipv4 | ipv6}]

            ip-address-alloc
    dynamic

            ipsec
    transform-setlist <ipsec_trans_set>

            exit

          ikev2-ikesa
    keepalive-user-activity

          end

    configure

      context <vpn_ctxt_name>

        hnbgw-service <hnbgw_svc_name>

          security-gateway
    bind address <segw_ip_address>
    crypto-template <crypto_template>
    context <segw_ctxt_name>

          end

Notes:

- <vpn_ctxt_name> is name of the source context in which HNB-GW service is configured.
- <segw_ctxt_name> is name of the context in which Se-GW service is configured. By default it takes context where HNB-GW service is configured.
- <hnbgw_svc_name> is name of the HNB-GW service which is to be configured for used for Iuh reference between HNB-GW and HNB.

Multiple MSC Selection without Iu-Flex Configuration

Use the following example to configure the multiple MSC selection over IuCS interface for MSC pooling and sharing.

    configure

      cs-network <cs_network_name>

        associate
    sccp-network <sccp_network_id>

        map
    lac range <lac_start>
    to <lac_end>
    point-code <msc_point_code>

        end

Notes:

- <cs_network_name> is name of the HNB-CS network which is already configured and associated with HNB-GW service.
- <sccp_network_id> is the identifier used for the SCCP network which is already configured and associated with HNB-CS Network <cs_network_name>.
- LAC value must be an integer between 0 and 65535.

Open Access Mode Configuration

Use the following example to configure the Open Access Mode for open HNBs in an HNB-GW service instance. It also includes the paging optimization configuration for open HNBs.

    configure

      context <vpn_ctxt_name>

        hnbgw-service
    <hnbgw_svc_name>
    -noconfirm

          hnb-access-mode
    open max-registered-ue <reg_ue>

          end

    configure

    hnbgw-global

      paging
    open-hnb [ hnb-where-ue-registered fallback ] {always | never | only-if-with-paging-area}

      end

Notes:

- <vpn_ctxt_name> is name of the source context in which HNB-GW service is configured.
- <hnbgw_svc_name> is name of the HNB-GW service in which Open Access mode support is to be configured.
- <reg_ue> is number of the UEs allowed to be registered through any Open HNB in Open Access Mode support. By default 16 UEs are allowed.

Hybrid Access Mode Configuration

Use the following example to configure the Hybrid Access Mode for hybrid HNBs in an HNB-GW service instance. It also includes the paging optimization configuration for hybrid HNBs.

    configure

      context <vpn_ctxt_name>

        hnbgw-service
    <hnbgw_svc_name>
    -noconfirm

          hnb-access-mode
    hybrid max-non-access-controlled-ue <reg_ue_hyb>

          hnb-access-mode
    mismatch-action { accept-aaa-value | hnb-reg-rej }

          end

    configure

    hnbgw-global

      paging
    open-hnb [ hnb-where-ue-registered fallback ] {always | never | only-if-with-paging-area}

      hybrid-hnb [ hnb-where-ue-registered [ hnbs-having-imsi-in-whitelist
    fallback [ always | never | only-if-with-paging-area ] | fallback [always | never |only-if-with-paging-area]]| hnbs-having-imsi-in-whitelist fallback [always | never |only-if-with-paging-area] | always | never | only-if-with-paging-area ]

      end

Notes:

- <vpn_ctxt_name> is name of the source context in which HNB-GW service is configured.
- <hnbgw_svc_name> is name of the HNB-GW service in which Open Access mode support is to be configured.
- <reg_ue_hyb> is number of the UEs allowed to be registered through any Hybrid HNB in Hybrid Access Mode support. By default 16 UEs are allowed.

### Verifying HNB-GW Configuration

This section shows the configuration parameters configured for HNB-GW service.

1. Verify that your HNB-GW services were created and configured properly by entering the following command in Exec Mode:

       show hnbgw-service
       hnbgw-service <hnbgw_svc_name>}

   The output of this command displays concise listing of HNB-GW service parameter settings as configured on system.
2. Verify configuration errors of your HNB-GW services by entering the following command in Exec Mode:

       show configuration
       errors section hnbgw-service}

   The output of this command displays current configuration errors and warning information for the target configuration file as specified for HNB-GW service

## DSCP Marking Configuration

To configure DSCP marking for control and data packet over Iuh and Iu interface for HNB-GW service:

1. Modify HNB-GW service to configure the DSCP marking for SCTP and UDP packets over Iuh interface by applying the example configuration in the Configuring DSCP Marking over Iuh Interface section.
2. Modify HNB-GW service to configure the DSCP marking for UDP packets over Iu interface by applying the example configuration in the Configuring DSCP Marking for Data Packet over Iu Interface section.
3. Modify SGSN-Global configuration to create the DSCP template for SCTP packets and modify PSP Instance to associate this DSCP template for downlink packets with particular PSP intance by applying the example configuration in the Creating and Associating DSCP Template for Control Packets over Iu Interface section.
4. 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 DSCP Marking over Iuh Interface

To configure the DSCP marking over Iuh interface for SCTP and UDP packets modify the HNB-GW service by applying the following example configuration:

    configure

      context <vpn_ctxt_name>

        hnbgw-service
    <hnbgw_svc_name>
    -noconfirm

          ip
    iuh-qos-dscp protocol { sctp | udp } payload { all | gtpu | rtcp | rtp } { af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be |
    cs1 | cs2 | cs3 | cs4 | cs5 | cs6 | cs7 | ef }

          end

Notes:

- <vpn_ctxt_name> is name of the source context in which HNB-GW service is configured.
- <hnbgw_svc_name> is name of the HNB-GW service in which Open Access mode support is to be configured.
- For more commands and keyword options, refer Command Line Interface Reference.

Configuring DSCP Marking for Data Packet over Iu Interface

To configure the DSCP marking over Iu interface for UDP packets modify the HNB-GW service by applying the following example configuration:

    configure

      context <vpn_ctxt_name>

        hnbgw-service
    <hnbgw_svc_name>
    -noconfirm

          ip
    iu-qos-dscp protocol udp payload { all | gtpu | rtcp | rtp } { af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be |
    cs1 | cs2 | cs3 | cs4 | cs5 | cs6 | cs7 | ef }

          end

Notes:

- <vpn_ctxt_name> is name of the source context in which HNB-GW service is configured.
- <hnbgw_svc_name> is name of the HNB-GW service in which Open Access mode support is to be configured.
- For more commands and keyword options, refer Command Line Interface Reference.

Creating and Associating DSCP Template for Control Packets over Iu Interface

To create a DSCP template and associating it with particular PSP instance for SCTP packets over Iu interface modify the SGSN Gloal and PSP instance Configuration mode by applying the following example configuration:

    configure

      sgsn-global

        dscp-template
    <sctp_dscp_template> -noconfirm

           control-packet
    qos-dscp { af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be |
    cs1 | cs2 | cs3 | cs4 | cs5 | cs6 | cs7 | ef }

           end

    configure

      ss7-routing-domain
    <ss7rd_id> variant
    <v_type>

        peer-server
    id <peer_server_id>

          psp
    instance <psp_instance_id>

            associate
    dscp-template downlink <sctp_dscp_template>

Notes:

- <ss7rd_id> is pre-configured SS7 Routing Domain instance for HNB-GW service.
- <peer_server_id> is pre-configured Peer server id configured in SS7 Routing Domain instance for HNB-GW service.
- <psp_instance_id> is pre-configured PSP instance id configured for Peer-Server id in SS7 Routing Domain instance for HNB-GW service.
- <sctp_dscp_template> is the DSCP tempate created in SGSN Global mode for SCTP DSCP marking and associated with PSP instance in SS7 Routing Domain instance for HNB-GW service.

## DHCP Configuration

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

1. Create a DHCP service specific to HNB-GW service by applying the example configuration in the Configuring DHCP Service section.
2. Create a subscriber template for HNB clients sesssion and associate the DHCP service with created subscriber template by applying the example configuration in the Configuring Subscriber Template for HNB 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 HNB-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 61610

          end

Notes:

- <vpn_ctxt_name> is name of the source context in which HNB-GW service is configured.
- <dhcp_svc_name> is name of the DHCP service configured in Context Configuration mode for DHCP interface support in HNB-GW service.
- <dhcp_server_ip> IP address of the DHCP server associated with DHCP service for DHCP interface support in HNB-GW service.
- For more commands and keyword options, refer Command Line Interface Reference.

Configuring Subscriber Template for HNB

Configure the subscriber template to associate the DHCP service for HNB 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 DHCP service is configured.
- <dhcp_svc_name> is name of the pre-configured DHCP service configured in Context Configuration mode for DHCP interface support in HNB-GW service.
- For more commands and keyword options, refer Command Line Interface Reference.

## IuCS over ATM Configuration

To configure IuCS-over-ATM on HNB-GW service:

1. Configure and activate the SONET card by applying the example configuration in the Configuring the SONET Card section.
2. Modify the configured SS7 Routing Domain configuration with Linkset Id and ATM parameters by applying the example configuration in the Configuring Linkset Id and ATM Parameters section.
3. Configure ALCAP service and AAL2 node parameters by applying the example configuration in the Configuring ALCAP Service and AAL2 Node section.
4. Configure the ATM port and PVC for AAL2 and AAL5 type of PVC by applying the example configuration in the Configuring the ATM Port section.
5. Modify the configured HNB-CS Network service configuration to associate ALCAP service for IuCS-over-ATM support by applying the example configuration in the Associating ALCAP Service with HNB-CS Network Service section.
6. 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 the SONET Card

To configure a SONET card for IuCS-over-ATM facility, apply the following example configuration:

    configure

       card <sonet_card_num>

         framing {sonet | SDH}

         no
    shutdown

         end

Notes:

- For other configuration procedures of ATM card, refer Creating and Configuring ATM Interfaces and Ports section in System Administration Guide.
- For more commands and keyword options, refer Command Line Interface Reference.

Configuring Linkset Id and ATM Parameters

To configure the linkset id and ATM parameters you need to modify existing SS7 Routing domain configuration by applying the following example:

    configure

      ss7-routing-domain
    <ss7rd_id> variant
    <v_type>

        ssf {international | national | reserved | spare}

        linkset
    id <linkset_id>

          self-point-code <self_pointcode>

          adjacent-point-code <adj_pointcode>

          link
    id <link_id>
    link-type atm-broadband

          priority <link_priority_value>

          signaling-link-code <sig_link_code>

          exit

        exit

        route
    destination-point-code <rd_pointcode>
    linkset-id <linkset_id>

          end

Notes:

- <ss7rd_id> is pre-configured SS7 Routing Domain instance configured at the system level to provide IuCS-over-ATM support to HNB-GW service.

Configuring ALCAP Service and AAL2 Node

To configure the ALCAP service with AAL2 node a nd AAL2 path parameters apply the following example:

    configure

      context <alcap_ctxt_name>

        alcap-service
    <alcap_svc_name>
    -noconfirm

          associate
    ss7-routing-domain <ss7rd_id>

          self-point-code <alcap_pointcode>

          aal2-route
    endpoint <AESA_route_endpoint>
    aal2-node <aal2_node_name>

          aal2-node
    <aal2_node_name>

            point-code
    <aal2_pointcode>

            aal2-path-id
    <aal2_path_id> [block]

            end

Notes:

- <alcap_ctxt_name> is name of the context in which ALCAP service is configured.
- <alcap_svc_name> is name of the ALCAP service which is to be configured for IuCS-over-ATM between HNB-GW and CS core network.
- <ss7rd_id> is a pre-configured SS7 routing domain instance.
- <alcap_pointcode> is address of the ALCAP node in SS7 point code notation.

Configuring the ATM Port

To configure ATM port for IuCS-over-ATM facility, apply the following example configuration:

    configure

       port
    atm <sonet_card_num>/<port_num>

         no
    shutdown

         pvc
    vpi <vpi_num>
    vci <aal5_vci_num>
    type aal5

           no
    shutdown

           bind
    link ss7-routing-domain <ss7rd_id>
    linkset-id <linkset_id> link-id
    <link_id>

           exit

         pvc
    vpi <vpi_num>
    vci <aal2_vci_num>
    type aal2 cps-payload-size <cps_paylod_size>

           no
    shutdown

           bind
    alcap-service <alcap_svc_name>
    context <alcap_ctxt_name>
    aal2-node <aal2_node_name>
    aal2-path <aal2_path_id>

           end

Notes:

- <alcap_ctxt_name> is name of the context in which ALCAP service is configured.
- <alcap_svc_name> is name of the pre-configured ALCAP service which is bound to ATM port for IuCS-over-ATM between HNB-GW and CS core network.
- <aal2_node_name> is a pre-configured AAL2 node in ALCAP Service Configuration mode.
- <aal2_path_id> is a pre-configured identifier for AAL2 path in AAL2 Node Configuration mode.

Associating ALCAP Service with HNB-CS Network Service

To associate a pre-configured ALCAP service with HNB-CS Network Service for IuCS-over-ATM function, apply the following example configuration:

    configure

      cs-network <cs_network_name>

        associate
    alcap-service <alcap_svc_name>
    context <alcap_ctxt_name>

        end

Notes:

- <cs_network_name> is a pre-configured HNB-CS Network service associated with HNB-GW for CS session.
- <alcap_svc_name> is name of the ALCAP service configured in destination context named <alcap_ctxt_name> to provide IuCS over ATM support through this CS network.

## Iu-Flex Configuration

To configure Iu-Flex support on HNB-GW service:

1. Modify the configured HNB-CS Network configuration with Iu-Flex parameters by applying the example configuration in the Iu-Flex over IuCS Interface Configuration section.
2. Modify the configured HNB-PS Network configuration with Iu-Flex parameters by applying the example configuration in the Iu-Flex over IuPS Interface Configuration 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.

Iu-Flex over IuCS Interface Configuration

Use the following example to configure the Iu-Flex feature over IuCS interface for MSC pooling and sharing.

    configure

      cs-network <cs_network_name>

        map
    idnns range <idnns_start>
    to <idnns_end>
    point-code <msc_point_code> [ backup
    point-code <bkup_msc_point_code>]

        map
    nri range <nri_start>
    to <nri_end>
    point-code <msc_point_code>

        nri
    length <nri_value>

        null-nri <null_nri_value>

        offload-msc
    point-code <msc_point_code>

        end

Notes:

- <cs_network_name> is name of the HNB-CS network which is already configured and associated with HNB-GW service.
- <nri_value> must be an integer between 1 and 10. A zero NRI length value disables the Iu-Flex feature on HNB-GW service.
- offload-msc point-code <msc_point_code> command enables the exclusion of specific primary MSC during NAS Node Selection Function (NNSF) procedure when it needs to be off-loaded while using Iu-Flex functionality on HNB-GW node.

IMPORTANT:

Offload check is only for the primary point code and NOT for the backup point code. This command can be used for planned maintenance as well.

Iu-Flex over IuPS Interface Configuration

Use the following example to configure the Iu-Flex feature over IuPS interface for SGSN pooling and sharing.

    configure

      ps-network <ps_network_name>

        map
    idnns range <idnns_start>
    to <idnns_end>
    point-code <sgsn_point_code> [ backup
    point-code <bkup_sgsn_point_code>]

        map
    nri range <nri_start>
    to <nri_end>
    point-code <sgsn_point_code>

        nri
    length <nri_value>

        null-nri <null_nri_value>

        offload-sgsn
    point-code <sgsn_point_code>

        end

Notes:

- <sgsn_network_name> is name of the HNB-PS network which is already configured and associated with HNB-GW service.
- <nri_value> must be an integer between 1 and 10. A zero NRI length value disables the Iu-Flex feature on HNB-GW service.
- offload-sgsn point-code <sgsn_point_code> command enables the exclusion of specific primary SGSN during NAS Node Selection Function (NNSF) procedure when it needs to be off-loaded while using Iu-Flex functionality on HNB-GW node.

IMPORTANT:

Offload check is only for the primary point code and NOT for the backup point code. This command can be used for planned maintenance as well.

Logging Facility Configuration

Use the following example to configure the HNB-GW system to enable the logging and debug facilities for HNB-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.

    configure

      logging
    console

      logging
    display event-verbosity {min | concise | full}

      logging
    filter runtime facility aal2 { critical | error | warning | unusual | info | trace | debug }

      logging
    filter runtime facility alcap { critical | error | warning | unusual | info | trace | debug }

      logging
    filter runtime facility alcapmgr { critical | error | warning | unusual | info | trace | debug }

      logging
    filter runtime facility diameter { critical | error | warning | unusual | info | trace | debug }

      logging
    filter runtime facility hnb-gw { critical | error | warning | unusual | info | trace | debug }

      logging
    filter runtime facility hnbmgr { critical | error | warning | unusual | info | trace | debug }

      logging
    filter runtime facility sccp { 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 HNB-GW node.

1. Verify the logging facilities configured on HNB-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 configured logging facilities.

## Congestion Control Configuration

To configure Congestion Control functionality:

1. Configure Congestion Control Threshold by applying the example configuration in the Configuring the Congestion Control Threshold section.
2. Configure Service Congestion Policies by applying the example configuration in the Configuring Service Congestion Policies section.
3. Optional. Operator can configure the system to reject all new incoming calls to specific or all HNB-GW service instance in a busy-out or planned maintenance or for troubleshooting by applying the example configuration in the Configuring New Call Policy section.
4. 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 the Congestion Control Threshold

To configure congestion control threshold, apply the following example configuration:

    configure

       congestion-control
    threshold max-sessions-per-service-utilization <percent>

       congestion-control
    threshold tolerance <percent>

       end

Notes:

- There are several additional threshold parameters. See the Global Configuration Mode chapter of the Command Line Interface Reference for more information.
- The tolerance is the percentage under a configured threshold that dictates the point at which the condition is cleared.
- Repeat this configuration as needed for additional thresholds.

Configuring Service Congestion Policies

To create a congestion control policy, apply the following example configuration:

    configure

       congestion-control
    policy hnbgw-service action { drop | none | reject }

       end

Notes:

- For HNB-GW service sessions reject is the default action.

Configuring New Call Policy

To create a new call policy in a busy our or planned maintenance or other operator intervened scenario, apply the following example configuration:

    newcall policy hnbgw-service [all | name <hnbgw_svc_name>] reject

Notes:

- For HNB-GW service sessions reject is the default action for all new calls coming on a specific or all HNB-GW service instance.

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 HNB-GW service, apply the following example configuration:

    configure

        snmp
    trap { enable | suppress} [congestion] {ThreshTotalHNBGWHnbSess | ThreshTotalHNBGWIuSess | ThreshTotalHNBGWUeSess} [ target
    <trap_collector>]

        snmp
    trap { enable | suppress} {ThreshTotalHNBGWHnbSess | ThreshTotalHNBGWIuSess | ThreshTotalHNBGWUeSess} [ target <trap_collector>]

        snmp
    trap { enable | suppress} HNBGWALCAPNodeReset [ target
    <trap_collector>]

        snmp
    trap { enable | suppress} HNBGWALCAPPathBlock [ target
    <trap_collector>]

        snmp
    trap { enable | suppress} HNBGWALCAPPathReset [ target
    <trap_collector>]

        snmp
    trap { enable | suppress} HNBGWALCAPPathUnBlock [ target
    <trap_collector>]

        snmp
    trap { enable | suppress} HNBGWMSCRanapReset [ target
    <trap_collector>]

        snmp
    trap { enable | suppress} HNBGWSGSNRanapReset [ target
    <trap_collector>]

        snmp
    trap { enable | suppress} HNBGWServiceStart [ target
    <trap_collector>]

        snmp
    trap { enable | suppress} HNBGWServiceStop [ target
    <trap_collector>]

        snmp
    trap { enable | suppress} HNBGWServiceStop [ target
    <trap_collector>]

       end

Notes:

- 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 HNB-GW Service

SNMP traps are used to manage and monitor the service on HNB-GW node.
Supported SNMP traps and its id are indicated in the following table.
Table 5. SNMP Traps and Object Ids

Traps | Object Id
--- | ---
starThreshHNBGWHnbSess | starentTraps 484
starThreshClearHNBGWHnbSess | starentTraps 485
starThreshHNBGWUeSess | starentTraps 486
starThreshClearHNBGWUeSess | starentTraps 487
starThreshHNBGWIuSess | starentTraps 488
starThreshClearHNBGWIuSess | starentTraps 489
starHNBGWSGSNRanapReset | starentTraps 1155
starHNBGWMSCRanapReset | starentTraps 1156
starALCAPNodeReset | starentTraps 1157
starALCAPPathReset | starentTraps 1158
starALCAPBlock | starentTraps 1159
starALCAPUnBlock | starentTraps 1160

IMPORTANT:

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

Event IDs for HNB-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.

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 6. System Event Facilities and ID Ranges

Facility | Event ID Range
--- | ---
HNB-GW Facility Events | 151000-151999
HNB Manager Facility Events | 158000-158199
ALCAP Manager Facility Events | 160500-160899
ALCAP Protocol Facility Events | 160900-161399
SCTP Protocol Facility Events | 87300-87499
AAL2 Protocol Facility Events | 173200-173299
RANAP User Adaptation Protocol Facility Even | 152000-152009
RANAP Protocol Facility Event | 87700-87899
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
Lawful Intercept Log Facility Events | 69000-69999
Mobile IPv6 Facility Events | 129000-129999
Network Access Signaling Facility Events | 153000-153999
Statistics Facility Events | 31000-31999
System Facility Events | 1000-1999
System Initiation Task (SIT) Main Facility Events | 4000-4999
Threshold Facility Events | 61000-61999
Virtual Private Network Facility Events | 5000-5999