> HNB-GW Service Configuration Mode Commands
> The 3G UMTS Home-NodeB Gateway Service Configuration Mode manages access to the UMTS core network in a 3G UMTS network through a Femto node.
> access-control-db
> Configures the access control database parameters in an HNB-GW service instance to control HNB and UE access to the HNB-GW node.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> access-control-db imsi-purge-timeout {immidiate | dur }
> default access-control-db imsi-purge-timeout
> default
> Sets the default value to HNB-UE access control database on HNB-GW service instance.
> The default timeout duration for purging of the IMSI White List from the HNB-GW Access Control database is 24 hours. The HNB-GW service waits for 24 hours after all referenced HNBs have de-registered before purging the records.
> immidiate
> Sets the HNB-GW service to purge the HNB-UE access control database immediately after all referenced HNBs have de-registered.
> imsi-purge-timeout dur
> Sets the timeout duration (in minutes) for the access control database to wait before purging the IMSI values received as a White List from HMS/BAC.
> After all HNBs have de-registered, the Access Control database on HNB-GW maintains the IMSI White List received from HMS/BAC during HNB registration procedure for the configured durations before purging the list.
> dur is an integer from 1 through 1440.
> Usage
> Use this command to configure the HNB-UE access control database parameters on HNB-GW service.
> This command sets the timeout duration to maintain the IMSI White List received from HMS/BAC during HNB registration procedure in HNB-GW service for the configured dur in minutes after de-registration of all referenced HNBs from HNB-GW node and then purge the database.
> Example
> Following command sets the HNB-GW service instance to purge all IMSI records from HNB-UE access control database immediately after all referenced HNBs de-registered from HNB-GW service instance.
> access-control-db imsi-purge-timeout immidiate
> associate gtpu-service
> Associates a previously configured GTP-U service to bind the HNB-GW service with an HNB towards the HNB side. A GTP-U service must be configured in Context Configuration mode before using this configuration.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> associate gtpu-service svc_name
> no associate gtpu-service
> no
> Removes the associated GTP-U service from this HNB-GW service configuration.
> svc_name
> Identifies the name of the pre-configured GTP-U service to associate with an HNB-GW service towards the Home-NodeB side.
> svc_name ise an alphanumeric string of 1 through 63 characters.
> Usage
> Use this command to configure GTP-U data plan between HNB-GW service and Home-NodeB. The service defined for GTP-U can be configured in Context configuration mode.
> Important: Another GTP-U service can be used to bind the HNB-GW service towards the Core Network and can be configured in HNB-PS Configuration mode. For more information on GTP-U service configuration, refer GTP-U Service Configuration Mode Commands.
> Example
> Following command associates GTP-U service named gtpu-hnb1 with specific HNB-GW service towards Home-NodeB side.
> associate gtpu-service gtpu-hnb1
> associate rtp pool
> Associates a previously defined RTP pool (IP pool) with the HNB-GW service. This pool is used by HNB-GW to send an IP address to HNB where HNB uses it to map the RTP streams over Iuh interface. This command is used for RTP stream management on HNB-GW.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> associate rtp pool pool_name
> no associate rtp pool
> no
> Removes the associated RTP pool (IP pool) from this HNB-GW service configuration.
> pool_name
> Specifies the name of the pre-configured RTP IP pool that the HNB-GW uses to assign IP addresses when mapping RTP streams over the Iuh interface.
> pool_name is an alphanumeric string of 1 through 31 characters.
> Important: For IP pool (RTP pool) configuration, refer ip pool command in Context Configuration Mode Commands chapter.
> Usage
> Use this command to associate an RTP pool (IP Pool) with an HNB-GW service for allotment of RTP IP address to HNB-GW node and send the same to HNB for RTP stream management support. The HNB maps the RTP streams with received IP address(es) while communicating with HNB-GW over Iuh interface where HNB-GW communicates with MSC/VLR through IuCS-over-IP tunnel.
> This command is used for RTP stream management on HNB-GW.
> Important: This command must be used to provide IP address for mapping of RTP streams on Iuh interface between HNB and HNB-GW.
> Example
> Following command associates RTP pool named rtp_1 with HNB-GW service for RTP stream end point from Home-NodeB:
> associate rtp pool rtp_1
> end
> Exits the current configuration mode and returns to the Exec mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> end
> Usage
> Use this command to return to the Exec mode.
> exit
> Exits the current mode and returns to the parent configuration mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> exit
> Usage
> Use this command to return to the parent configuration mode.
> handin
> Allows or disallows the incoming hand-over of an MS in HNB-GW via the Serving Radio Network Subsystem (SRNS) Relocation procedure for the specified packet switched/circuit switched (PS/CS) core network (CN) domain.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> [no | default] handin cn-domain [cs | ps]
> no
> Disallows the incoming MS hand-over for the particular CN domain via SRNS Relocation procedure in an HNB-GW service instance.
> If hand-over is restricted the relocation request will be rejected with rejection cause “Relocation Not Supported In Target RNC Or Target System”.
> default
> Sets the HNB-GW service instance to allow the incoming MS hand-over for the particular CN domain via SRNS Relocation procedure in an HNB-GW service instance.
> cs
> Sets the HNB-GW service instance to allow the incoming MS hand-over for the CS core network domain via SRNS Relocation procedure in an HNB-GW service instance.
> ps
> Sets the HNB-GW service instance to allow the incoming MS hand-over for the PS core network domain via SRNS Relocation procedure in an HNB-GW service instance.
> Usage
> Use this command to set HNB-GW service instance for allowing/disallowing incoming hand-over of an MS in HNB-GW via SRNS Relocation procedure for PS or CS core network domain.
> If hand-over is restricted the Relocation Request message will be rejected with rejection cause “Relocation Not Supported In Target RNC Or Target System”.
> Example
> The following command configures the HNB-GW service instance to allow hand-over of an MS in HNB-W via SRNS Relocation procedure for PS core network domain:
> handin ps
> hnb-access-mode
> Configures the HNB access mode (open/closed) in HNB-GW service instance and related parameters. Currently it is used to configured Open Access mode support only.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> hnb-access-mode open max-registered-ue reg_ue
> no hnb-access-mode open
> default hnb-access-mode open
> no
> Disables Open Access mode support.
> If disabled and an Open HNB tries to register, the HNB-GW sends HNB-Registration-Reject message with “OA&M Intervention” cause.
> Important: UE-Reg/CS-Call/PS-Call requests (both existing and future) is allowed from already registered Open HNBs even after operator has disabled the Open Access support. No new Open HNB registration is allowed once operator disables the Open Access support.
> default
> Sets the default configuration of Open Access mode support.
> By default, HNB-GW allows registration of Open HNBs and a maximum of 16 UEs can register from an open HNB in an HNB-GW service instance.
> open max-registered-ue reg_ue
> Sets the HNB-GW service instance to allow the maximum number of UEs through an open HNB under Open Access mode support.
> reg_ue defines the maximum number of UEs that can register from an Open HNB as an integer from 1 through 32.
> If a UE tries to register from an Open HNB which has already reached to the configured limit configured, the HNB-GW sends HNB-Registration-Reject message with “ue not allowed in this hnb” cause in an HNB-GW service instance.
> Usage
> Use this command to configure the HNB-GW service instance for Open Access Mode support and related parameters.
> This command enable Open Access mode support to allow the UEs that can register from an Open HNB. If a UE tries to register from an Open HNB with an HNB-GW service instance, which is already reached to the limit configured through max-registered-ue reg_ue the HNB-GW sends HNB-Registration-Reject message with “ue not allowed in this hnb” cause.
> Important: If Operator has reduced the maximum number of UEs allowed per Open HNB during the session, this will not have any effect on already registered UEs/CS-Calls/PS-Calls even if previously configured reg_ue is beyond the newly configured reg_ue value. Limits is respected while handling new requests.
> Example
> The following command configures the HNB-GW service instance to allow 16 UEs to register through an open HNB:
> default hnb-access-mode open
> ip iu-qos-dscp
> Enables or disables the DSCP marking parameter for data packets carried over over an IuCS/IuPS interface towards MSC/SGSN. By default this command is Disabled.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> ip iu-qos-dscp protocol { sctp payload all | udp payload { gtpu | rtcp| rtp} } dscp_code
> [default | no] ip iu-qos-dscp protocol { sctp payload all | udp payload { gtpu | rtcp| rtp} }
> no
> Use this keyword to place the configuration in pass-through mode (no marking of DSCP). Use of this keyword is allowed even when there is no previous DSCP parameter set.
> Important: In this configuration the no keyword does not disable or remove a previous configuration.
> default
> Enables the DSCP marking on HNB-GW and set/restores the QoS parameters to their default setting.
> sctp payload all dscp_code
> Specifies the QoS traffic pattern towards MSC/SGSN in SCTP protocol association over IuCS/IuPS interface.
> By this keyword the Traffic classes specified by a user based on SCTP protocol and all type of payload identified based on the transport level port numbers.
> By default DSCP codes cs5 is supported for all payloads in SCTP protocol.
> udp payload { gtpu | rtcp| rtp} dscp_code
> Specifies the QoS traffic pattern towards MSC/SGSN in SCTP protocol association over IuCS/IuPS interface.
> By this keyword the Traffic classes specified by a user based on UDP protocol and GTPU, RTCP, and RTP type of payload identified based on the transport level port numbers.
> Default DSCP code in UDP traffic are:

> • | GTP-U: cs1

> • | RTCP: ef

> • | RTP: af41

> dscp_code
> Specifies the QoS DSCP codes supported for SCTP and UDP traffic and its payloads towards MSC/SGSN over IuCS/IuPS interface.
> following type of DSCP codes dscp_code are supported over IuH interface:

> • | af11: Marks traffic as Assured Forwarding 11 PHB (high throughput data)

> • | af12: Marks traffic as Assured Forwarding 12 PHB (high throughput data)

> • | af13: Marks traffic as Assured Forwarding 13 PHB (high throughput data)

> • | af21: Marks traffic as Assured Forwarding 21 PHB (low latency data)

> • | af22: Marks traffic as Assured Forwarding 22 PHB (low latency data)

> • | af23: Marks traffic as Assured Forwarding 23 PHB (low latency data)

> • | af31: Marks traffic as Assured Forwarding 31 PHB (multimedia streaming)

> • | af32: Marks traffic as Assured Forwarding 32 PHB (multimedia streaming)

> • | af33: Marks traffic as Assured Forwarding 33 PHB (multimedia streaming)

> • | af41: Marks traffic as Assured Forwarding 41 PHB (multimedia conferencing). This is the default DSCP code for RTP payloads in UDP protocol.

> • | af42: Marks traffic as Assured Forwarding 42 PHB (multimedia conferencing)

> • | af43: Marks traffic as Assured Forwarding 43 PHB (multimedia conferencing)

> • | cs1: Marks traffic with Class Selector 1 (low priority data). This is the default DSCP code for GTP-U payloads in UDP protocol.

> • | cs2: Marks traffic with Class Selector 2 (OAM)

> • | cs3: Marks traffic with Class Selector 3 (broadcast video)

> • | cs4: Marks traffic with Class Selector 4 (real-time interactive)

> • | cs5: Marks traffic with Class Selector 5 (signaling). This is the default DSCP code for all SCTP payloads.

> • | cs6: Marks traffic with Class Selector 6 (network control)

> • | df : Marks traffic as Default Forwarding (best effort: DSCP = 0)

> • | ef: Marks traffic as Expedited Forwarding PHB (telephony). This is the default DSCP code for RTCP payloads in UDP protocol.

> Usage
> Use this command to enable/disable the DSCP marking for data packets over IuCS/PS interface. This command assigns the DSCP levels to specific traffic patterns in order to ensure that the packets are delivered according to the precedence with which they are tagged. The Diffserv markings are applied to the IP header of every subscriber data packet transmitted over IuCS/IuPs interface(s) towards MSC/SGSN.
> This command adds DSCP marking on egress traffic going towards CN (CS/PS). To make the configuration pass-through mode or not marking DSCP at all in the packets, no variant of command is used. Use of no is allowed even when there is no previous DSCP configuration done.
> Important: By default this command is Disabled.
> Important: When DSCP configuration is not specified, the system works in pass-through mode and DSCP values in the ingress (from CN) and egress (to HNB) data packets remain unchanged. Multiple traffic classes can share the same code point value.
> Following type shown in following tables respectively:
> Supported DSCP Codes and Service Class

> Service Class | DSCP Code | Service Class | DSCP Code
> high throughput data | af11 af12 af13 | low priority data | cs1
> low latency data | af21 af22 af23 | OAM | cs2
> multimedia streaming | af31 af32 af33 | broadcast video | cs3
> multimedia conferencing | af41 af42 af43 | real-time interactive | cs4
> best effort/ default forwarding, value zero | df | Signaling | cs5
> telephony | ef | network control | cs6

> ‌
> The DSCP level can be configured for multiple traffic patterns within a single instance of this command.
> Example
> The following command configures the DSCP code for the SCTP IuCS/IuPS streaming traffic pattern for all payloads to be ef:
> ip iu-qos-dscp protocol sctp payload all ef
> ip iuh-qos-dscp
> Enables or disables the DSCP marking parameter for control and data packets transmitted over an IuH interface towards HNB. By default this command is Disabled.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> ip iuh-qos-dscp protocol { sctp payload all | udp payload { gtpu | rtcp| rtp} } dscp_code
> [default | no] ip iuh-qos-dscp protocol { sctp payload all | udp payload { gtpu | rtcp| rtp} }
> no
> Use this keyword to set the configuration in pass-through mode. Use of this keyword is allowed even when there is no previous DSCP parameter set.
> Important: In this configuration the no keyword does not disable/remove a previous configuration.
> default
> Enables the DSCP marking on HNB-GW and set/restores the QoS parameters to its default setting.
> sctp payload all dscp_code
> Specifies the QOS traffic pattern towards HNB in SCTP protocol association over IuH interface.
> By this keyword the Traffic classes specified by a user based on SCTP protocol and all type of payload identified based on the transport level port numbers.
> By default DSCP codes cs5 is supported for all payloads in SCTP protocol.
> udp payload { gtpu | rtcp| rtp} dscp_code
> Specifies the QOS traffic pattern towards HNB in SCTP protocol association over IuH interface.
> By this keyword the Traffic classes specified by a user based on UDP protocol and GTPU, RTCP, and RTP type of payload identified based on the transport level port numbers.
> Default DSCP code in UDP traffic are:

> • | GTP-U: cs1

> • | RTCP: ef

> • | RTP: af41

> dscp_code
> Specifies the QOS DSCP codes supported for SCTP and UDP traffic and its payloads towards HNB over IuH interface.
> following type of DSCP codes dscp_code are supported over IuH interface:

> • | af11: Marks traffic as Assured Forwarding 11 PHB (high throughput data)

> • | af12: Marks traffic as Assured Forwarding 12 PHB (high throughput data)

> • | af13: Marks traffic as Assured Forwarding 13 PHB (high throughput data)

> • | af21: Marks traffic as Assured Forwarding 21 PHB (low latency data)

> • | af22: Marks traffic as Assured Forwarding 22 PHB (low latency data)

> • | af23: Marks traffic as Assured Forwarding 23 PHB (low latency data)

> • | af31: Marks traffic as Assured Forwarding 31 PHB (multimedia streaming)

> • | af32: Marks traffic as Assured Forwarding 32 PHB (multimedia streaming)

> • | af33: Marks traffic as Assured Forwarding 33 PHB (multimedia streaming)

> • | af41: Marks traffic as Assured Forwarding 41 PHB (multimedia conferencing). This is the default DSCP code for RTP payloads in UDP protocol.

> • | af42: Marks traffic as Assured Forwarding 42 PHB (multimedia conferencing)

> • | af43: Marks traffic as Assured Forwarding 43 PHB (multimedia conferencing)

> • | cs1: Marks traffic with Class Selector 1 (low priority data). This is the default DSCP code for GTP-U payloads in UDP protocol.

> • | cs2: Marks traffic with Class Selector 2 (OAM)

> • | cs3: Marks traffic with Class Selector 3 (broadcast video)

> • | cs4: Marks traffic with Class Selector 4 (real-time interactive)

> • | cs5: Marks traffic with Class Selector 5 (signaling). This is the default DSCP code for all SCTP payloads.

> • | cs6: Marks traffic with Class Selector 6 (network control)

> • | df : Marks traffic as Default Forwarding (best effort: DSCP = 0)

> • | ef: Marks traffic as Expedited Forwarding PHB (telephony). This is the default DSCP code for RTCP payloads in UDP protocol.

> Usage
> Use this command to enable/disable the DSCP marking for control and data packets carried by the IP protocols and their payloads on IuH. This command assigns the DSCP levels to specific traffic patterns in order to ensure that the packets are delivered according to the precedence with which they are tagged. The Diffserv markings are applied to the IP header of every subscriber data packet transmitted over IuH interface(s) towards HNB.
> This command adds DSCP marking on egress traffic going towards HNB. To make the configuration pass-through mode or not marking DSCP at all in the packets, no variant of command is used. Use of no is allowed even when there is no previous DSCP configuration done.
> Important: By default this command is Disabled.
> Important: When DSCP configuration is not specified, system works in pass-through mode and DSCP value in the ingress (from CN) and egress (to HNB) control and data packets remain unchanged. Multiple traffic classes can share the same code point value.
> Following type shown in following tables respectively:
> Supported DSCP Codes and Service Class

> Service Class | DSCP Code | Service Class | DSCP Code
> high throughput data | af11 af12 af13 | low priority data | cs1
> low latency data | af21 af22 af23 | OAM | cs2
> multimedia streaming | af31 af32 af33 | broadcast video | cs3
> multimedia conferencing | af41 af42 af43 | real-time interactive | cs4
> best effort/ default forwarding, value zero | df | Signaling | cs5
> telephony | ef | network control | cs6

> ‌
> The DSCP level can be configured for multiple traffic patterns within a single instance of this command.
> Example
> The following command configures the DSCP code for the SCTP IuH streaming traffic pattern for all payloads to be ef:
> ip iuh-qos-dscp protocol sctp payload all ef
> paging open-hnb
> Cconfigures paging optimization parameters for open HNBs connected through Open Access mode in the HNB-GW service instance. Currently it is used to configure paging optimization for Open Access mode support only.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> paging open-hnb [hnb-where-ue-registered fallback ] {always | never | only-if-with-paging-area}
> default paging open-hnb
> default
> Sets the default behavior of paging optimization configuration for an open HNB while using Open Access mode support.
> By default the HNB-GW pages open HNBs only if paging-area IE is received in the paging message.
> {always | never | only-if-with-paging-area}
> Sets the HNB-GW service instance to page open HNB for a paging message.
> always: Sets the system to ALWAYS page the open HNBs irrespective of paging-area IE is received in paging messages.
> never: Sets the system to NEVER page any open HNB.
> only-if-with-paging-area: Sets the system to page the open HNBs only when paging-area IE is received in paging messages.
> hnb-where-ue-registered fallback {always | never | only-if-with-paging-area}
> Sets the HNB-GW service instance to page open HNB from where the UE is registered.
> always: Sets the system to ALWAYS page the open HNBs from where the UE is registered. If the UE is not registered then it pages the open HNBs irrespective of paging-area IE is received in paging messages.
> never: Sets the system to page the open HNBs from where the UE is registered. If the UE is not registered then it NEVER pages any open HNB.
> only-if-with-paging-area: Sets the system to ALWAYS page the open HNBs from where the UE is registered. If the UE is not registered then it pages the open HNBs only when paging-area IE is received in paging messages.
> Usage
> Use this command to configure the paging optimization parameters for open HNBs connected through Open Access mode in HNB-GW service instance.
> Example
> The following command configures the HNB-GW service instance to page an open HNB from where the UE is connected and paging-area IE is received in paging message:
> paging open-hnb hnb-where-ue-registered fallback only-if-with-paging-area
> radio-network-plmn
> Creates, remove and enters the HNB-RN-PLMN Configuration mode. In this mode you can configure various parameters for radio network public mobile land networks (PLMNs). A maximum of 16 radio PLMN-IDs can be configured in an HNB-GW service.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> radio-network-plmn mcc mcc_num mnc mnc_num [-noconfirm]
> no radio-network-plmn mcc mcc_num mnc mnc_num
> no
> Removes the configured radio network PLMN identifier for an HNB-GW service.
> Caution: Removing the PLMN-ID is a disruptive operation; the HNB-GW service will be re-started.
> mcc mcc_num
> Specifies the mobile country code (MCC) part of radio network PLMN identifier as an integer value from 101 through 998.
> mnc mnc_num
> Specifies the mobile network code (MNC) part of radio network PLMN identifier as a 2- or 3-digit integer from 01 through 998.
> -noconfirm
> Executes the command without any additional prompt and confirmation from the user.
> Usage
> Use this command to configure the radio network PLMN identifier for an HNB-GW service. This command also creates a configuration mode to configure various parameters for defined radio network PLMN identifier in HNB-GW service.
> Caution: Changing or removing the PLMN-ID is a disruptive operation; the HNB-GW service will be re-started.
> Entering this command results in the following prompt:
> [context_name]hostname(config-radio-network-plmn)#
> A maximum of 16 radio network PLMN identifiers are supported for an HNB-GW service.
> Example
> The following command configures the radio network PLMN identifier with MCC value as 102 and MNC value as 20 for an HNB-GW service:
> radio-network-plmn mmc 102 mnc 20
> ranap reset
> Configures various Radio Access Network (RAN) Application Part reset procedure parameters in an HNB access network.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> ranap reset {ack-timeout timer_value | guard-timeout g_timer | hnbgw-initiated | max-retransmissions retries}
> default ranap reset {ack-timeout | guard-timeout | hnbgw-initiated | max-retransmissions}
> no ranap hnbgw-initiated
> default
> Resets the RANAP RESET parameters on HNB-GW service instance.
> no
> Disables the RANAP RESET procedure related parameters in an HNB-GW service instance.
> ack-timeout timer_value
> Sets the timer value (in seconds) to wait for Reset Acknowledge from SGSN/MSC. This is used during HNB-GW initiated RANAP RESET procedure in HNB-GW service instance.
> timer_value is an integer value from 5 through 10. Default: 10
> guard-timeout g_timer_value
> Sets the timer value (in seconds) to send Reset Acknowledge to SGSN/MSC. After this duration the HNB-GW sends RESET-ACK to SGSN/MSC. This is used during SGSN/MSC initiated RANAP RESET procedure in HNB-GW service instance.
> g_timer_value is an integer value from 5 through 10. Default: 10
> hnbgw-initiated
> Enables the HNB-GW Initiated RANAP RESET procedures. Default: Disabled
> max-retransmission retries
> Sets the maximum number of retires allowed for transmission of RESET-ACK message to SGSN/MSC. This is used during RANAP RESET procedure in HNB-GW service instance.
> retries is an integer value from 0 through 2. When 0 is used retransmission is disabled. Default: 1
> Usage
> Use this command to configure the RANAP RESET procedure related parameters in HNB-GW service.
> Example
> The following command configures the HNB-GW initiated RANAP RESET Procedure for an HNB-GW service:
> ranap reset hnbgw-initiated
> rtcp report
> Enables or disables the generation of RTP Control Protocol (RTCP) packet/report types on a per HNB-GW service instance basis. It also sets the time interval in seconds between two consecutive RTCP reports.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> rtcp report interval dur
> [no | default] rtcp report interval
> no
> Disables the RTCP report generation on HNB-GW service. When RTP configuration is not explicitly mentioned, this is the default behavior.
> default
> Restores the report interval value to its default value of 5 seconds.
> interval dur
> Sets the time interval (in seconds) between two consecutive RTCP reports as an integer from 5 through 30. Default: 5
> Usage
> Use this command to configure the enabling or disabling of the generation of RTCP packet/ report types on a per HNB-GW service instance basis and sets the specified time interval in seconds between two consecutive RTCP reports.
> RTCP enables the receiver to detect if there is any packet loss and needs to compensate for any delay jitter. RTP and RTCP protocols work independently of the underlying Transport layer and Network layer protocols.
> Whenever this command is disabled, RTCP report generation stops from the next expiry of the previously configured interval and after enabling, reports are generated only for the calls that established as new calls in the future. For existing calls reports generated as per configuration in place.
> RTCP reports are generated for each RAB for RTP received from and sent to IuH interface.
> Important: The same interval is applicable for all kinds of RTCP packets/ reports across all sessions on an HNB-GW service.
> Example
> The following command configures the RTCP report generation interval to 15 seconds on an HNB-GW service for RTP stream:
> rtcp report interval 15
> rtp mux
> Configures the HNB-GW service to allow an Home-NodeB to multiplex multiple RTP streams in one IP packet. This support is provided for RTP stream management feature on HNB-GW.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> [no | default]rtp mux
> default
> Sets the multiplexing option to default state of “disabled”.
> no
> Removes the configured option to multiplex multiple RTP stream in one packet by Home-NodeB in HNB-GW configuration.
> Usage
> Use this command to allow an Home-NodeB to multiplex multiple RTP streams in one IP packet. This configuration support is provided for RTP stream management feature on HNB-GW and it is disabled by default.
> Example
> The following command sets the HNB-GW to allow HNB to multiplex multiple RTP stream in one packet:
> rtp mux
> sctp
> Configures the SCTP-related parameters like timeout duration for various timers and cookie life over an IuH interface in an HNB-GW service.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> sctp alpha-rto alpha_rto_dur
> sctp beta-rto beta_rto_dur
> sctp checksum-type [ adler32 | crc32 ]
> sctp cookie-life cookie_life
> sctp max-retx [ init | path | assoc ] max_retry
> sctp mtu-size [ start | min | max ] mtu_byte
> sctp rto { initial ini_rto_dur | min min_rto_dur | max max_rto_dur }
> sctp sack-frequency sack_frq
> sctp sack-period sack_dur
> sctp max-in-strms in_strms
> sctp max-out-strms out_strms
> default sctp {alpha-rto | beta-rto | checksum-type | cookie-life | max-retx [ init | path | assoc] | mtu-size [start | min | max ] | rto { initial | min | max} | sack-frequency | sack-period | max-in-strms | max-out-strms }
> default
> Restores the SCTP parameters to default value in HNB-GW service instance. Default values for all parameters are as follows:

> • | alpha-rto: 5 seconds

> • | beta-rto: 10 seconds

> • | checksum-type: CRC32

> • | cookie-life: 600 ms

> • | max-retx init: 5 retries

> • | max-retx path: 5 retries

> • | max-retx assoc: 10 retries

> • | mtu-size min: 508 Bytes

> • | mtu-size max: 1500 Bytes

> • | mtu-size start: 508 Bytes

> • | rto initial: 30 seconds

> • | rto min: 10 seconds

> • | rto max: 600 seconds

> • | sack-frequency: 2

> • | sack-period: 2 ms

> • | max-in-strms: 4

> • | max-out-strms: 4

> alpha-rto alpha_rto_dur
> Sets the alpha retransmission timeout duration (in seconds) for SCTP association between HNB and HNB-GW as an integer from 0 through 65535. A “zero” value disables the timer in this configuration. Default: 5
> beta-rto beta_rto_dur
> Sets the beta retransmission timeout duration (in seconds) for SCTP association between HNB and HNB-GW an integer from 0 through 65535. A “zero” value disables the timer in this configuration. Default: 10
> checksum-type [ adler32 | crc32 ]
> Sets the checksum algorithm type to be used in SCTP association between HNB and HNB-GW for packet validation. Default: CRC32
> adler32: Specifies the SCTP association to use Adler32 checksum algorithm for packet validation. By default this is disabled.
> crc32: Specifies the SCTP association to use 32-bit cyclic redundancy check (CRC) algorithm for packet validation. By default this is enabled.
> cookie-life cookie_life
> Sets the COOKIE life (in milliseocnds) for SCTP association between HNB and HNB-GW as an integer from 500 through 120000. Default: 600
> max-retx [ init | path | assoc ] max_retry
> Sets the maximum number of retries allowed in SCTP states for SCTP association between HNB and HNB-GW.
> init: Sets the maximum attempts allowed after T1-init timer expires. If the T1-init timer expires then the HNB-GW retransmits INIT chunk and re-start the T1-init timer without changing state. This is repeated up to the configured times with this configuration. After that, the HNB-GW aborts the initialization process. Default number of attempts max_retry for this state is 5.
> path: Sets the maximum attempts allowed after T3-rtx timer expires. Each time the T3-rtx timer expires on any address, or when a HEARTBEAT sent to an idle address is not acknowledged within a RTO, the error counter of that destination address incremented. When the value in the error counter exceeds this protocol parameter of that HNB address, the HNB-GW marks the destination transport address as inactive. Default number of attempts max_retry for this state is 5.
> assoc: Sets the maximum number of consecutive retransmissions to its peer is allowed. If the value of this counter exceeds the limit configured with this keyword the HNB-GW considers the peer HNB unreachable and stop transmitting any more data to it. The SCTP association is automatically closed when the peer endpoint becomes unreachable. Default number of attempts max_retry for this state is 10.
> max_retry is an integer from 1 through 255.
> mtu-size [ min | max | sart ] mtu_byte
> Sets the maximum transmission unit (MTU) size in Bytes for SCTP association between HNB and HNB-GW.
> min: Sets the minimum size of MTU for SCTP association between HNB and HNB-GW. Default minimum MTU size mtu_byte is 508 Bytes.
> max: Sets the maximum size of MTU for SCTP association between HNB and HNB-GW. Default maximum MTU size mtu_byte is 1500 Bytes.
> start: Sets the size of MTU for SCTP association at the start of session between HNB and HNB-GW. Default MTU size mtu_byte at initial sate is 508 Bytes.
> mtu_byte is an integer from 508 to 65535.
> rto { initial ini_rto_dur | min min_rto_dur | max max_rto_dur }
> Sets the Retransmission TimeOut (RTO) duration parameters for SCTP association between HNB and HNB-GW.
> initial ini_rto_dur: Sets the initial retransmission timeout duration (in seocnds) for SCTP association between HNB and HNB-GW as an integer from 1 through 1200. Default: 30.
> min min_rto_dur: Sets the minimal retransmission timeout duration (in seconds) for SCTP association between HNB and HNB-GW as an integer from 1 through 50. Default: 10
> max max_rto_dur: Sets the maximum retransmission timeout duration (in secinds) for SCTP association between HNB and HNB-GW as an integer from 5 through 1200. Default: 600.
> sack-frequency sack_frq
> Sets the number of chunks received before sending the Selective Acknowledgement chunk HNB from HNB-GW in SCTP association. the SACK chunk is sent to the HNB to acknowledge received DATA chunks and to inform the HNB of gaps in subsequently received DATA chunks.
> sack_frq is the frequency after which SACK chunk is sent to HNB specified as an integer from 1 through 5. Default: 2
> sack-period sack_dur
> Sets the duration (in seconds) after which Selective Acknowledgement chunk is sent to HNB from HNB-GW in SCTP association. The SACK chunk is sent to the HNB to acknowledge received DATA chunks and to inform the HNB of gaps in subsequently received DATA chunks.
> sack_dur is an integer from 0 through 5. A “zero” value disables the parameter.
> max-in-strms in_strms
> Sets the maximum number of inward SCTP streams allowed on HNB-GW for an associated HNB in an SCTP association as an integer from 1 through 16. Default: 4
> max-out-strms out_strms
> Sets the maximum number of outgoing SCTP streams allowed from HNB-GW for an associated HNB in an SCTP association as an integer from 1 through 16. Default: 4
> Usage
> Use this command to configure the SCTP protocol messaging and session management parameters in SCTP association between HNB and HNB-GW.
> Example
> The following command sets the SCTP COOKIE life to 600 milliseconds on HNB-GW for the SCTP association:
> default sctp cookie-life
> sctp bind
> Configures the SCTP IP address and port that is used for binding the SCTP socket to communicate with the Home-NodeB over an Iuh interface within an HNB-GW service.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> sctp bind { address address | port port_num }
> [ default | no ] sctp bind { address | port }
> default
> Sets the SCTP port to the default value of 600.
> address address
> Specifies the IP address of the HNB-GW Iuh interface in IPv4 dotted-decimal or IPv6 colon-separated notation.
> port port_num
> Specifies the SCTP port number to communicate with the Home-NodeBs using Iuh interface as an integer form 1 through 65535.
> Usage
> Use this command to assign the SCTP IP address and port with SCTP socket on HNB-GW to communicate with the Home-NodeB using Iuh interface. This SCTP configuration provides the IP-address and listen port where HNB-GW service shall bind to listen for incoming SCTP associations from HNB.
> Example
> The following command sets the SCTP port number 999 on HNB-GW to listen from Home-NodeB over Iuh interface:
> sctp bind port 999
> The following command sets the SCTP address 10.2.3.4 of HNB-GW to use with Home-NodeB over Iuh interface:
> sctp bind address 10.2.3.4
> sctp connection-timeout
> Configures the SCTP connection timeout duration to explicitly remove the SCTP association with a non-responsive HNB in an HNB-GW service.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> sctp connection-timeout dur
> [ default | no ] sctp connection-timeout
> no
> Disables the connection time out configuration on HNB-GW service.
> default
> Restores the connection timeout duration value to its default value of 10 seconds.
> dur
> Sets the connection timeout duration (in seconds) after which the association is explicitly removed. In case of an HNB de-registration scenario, the HNB-GW waits for configured amount time before initiating the procedure to clear the SCTP association.
> dur is an integer from 5 through 30. Default: 10
> Usage
> Use this command to configure the minimum duration value before removing the SCTP association between a non-responding HNB and HNB-GW. If HNB registration not happened within the configured period after the SCTP association is established then the SCTP association is explicitly removed. In a scenario where an HNB de-registered due to any reason, the HNB-GW waits for the configured amount of time before initiating the procedure to clear the SCTP association.
> Example
> The following command sets the SCTP connection timeout duration to 15 second on HNB-GW after expiry of which the SCTP association is removed:
> sctp connection-timeout 15
> sctp heart-beat-timeout
> Configures the SCTP heartbeat timer parameters for SCTP connection over an IuH interface in an HNB-GW service instance.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> sctp heart-beat-timeout dur
> [ default | no ] sctp heart-beat-timeout
> no
> Disables the heartbeat timer configuration for SCTP over IuH in HNB-GW service instance.
> default
> Restores the default time out value for heartbeat timer to 30 seconds.
> dur
> Sets the heartbeat timer timeout duration (in seconds) after which the next heartbeat command is sent to HNB from HNB-GW in SCTP over an IuH interface. In an HNB de-registration scenario, the HNB-GW waits for configured amount time before initiating the procedure to clear the SCTP association.
> dur is an integer from 1 through 300. Default: 30
> Usage
> Use this command to configure the minimum duration value before retransmitting the HEARTBEAT chunk to HNB from HNB-GW in SCTP transmission. By default HNB-GW monitors the reachability of the idle HNBs by sending a HEARTBEAT chunk periodically to the HNB address.
> Each time the HEARTBEAT timer expires on any address, or when a HEARTBEAT sent to an idle address is not acknowledged within a Retransmission Timeout duration, the error counter of that HNB incremented.
> When the value in the error counter exceeds the protocol parameter for maximum retransmission for that destination address, the HNB-GW mark the destination HNB as inactive and a notification is sent to the upper layer.
> Example
> The following command sets the SCTP HEARTBEAT timeout duration to 15 second on HNB-GW after expiry of which the HNB-GW retransmits the HEARTBAT chunk to HNB over SCTP association:
> sctp heart-beat-timeout 15
> security-gateway aaa
> Associates a pre-configured AAA Service group to use authentication parameters for Security Gateway (SeGW) functionality in HNB-GW service. The associated AAA server group is a pre-configured via Context Configuration mode.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> security-gateway aaa authentication { first-phase | second-phase } context ctx_name aaa-group aaa_grp
> no security-gateway aaa { attribute calling-station-id | authentication { first-phase | second-phase }
> no
> Removes previously configured AAA authentication or attribute setting from HNB-GW service while using SeGW functionary.
> attribute calling-station-id ms_id
> Specifies the calling station identifier from where the user placed the call.
> authentication { first-phase | second-phase } context ctx_name aaa-group aaa_grp
> Specifies the AAA authentication parameters to be used while using SeGW functionality in an HNB-GW service.
> first-phase: Specifies the parameters to be used for first phase of authentication while using SeGW functionality in an HNB-GW service. This associates the AAA parameters through AAA server group association with in it.
> second-phase: Specifies the parameters to be used for second phase of authentication while using SeGW functionality in an HNB-GW service. This associates the AAA parameters through AAA server group association with in it.
> context ctx_name: Specifies the name of the context to be used for first/second or both phases of authentication.
> aaa-group aaa_grp: Specifies the name of the AAA server group configured via Context Configuration mode with AAA parameters that will be used for first/second or both phases of authentication.
> Important: For more information on AAA server groups, refer AAA Server Group Configuration Mode Commands.
> Usage
> Use this command to associate or tie the AAA authentication or attribute parameters with an HNB-GW service which is to be used for first/second or both phase of authentication while using SeGW functionality in an HNB-GW service or removing AAA attribute “calling-station-id” from AAA message. This functionality is part of SeGW configuration support in an HNB-GW service.
> Caution: This is a critical configuration and need to be configured carefully when Security Gateway (SeGW) functionality required on HNB-GW service.
> Example
> The following command associates an AAA server group named sec_gw_grp1 with HNB-GW service to use specific AAA authentication parameters in first phase of authentication and another AAA server group named sec_gw_grp2 to use different AAA authentication parameter in second phase of authentication. Both AAA server groups are configured in same context named SeGW_ctx1:
> security-gateway aaa authentication first-phase context SeGW1 aaa-group sec_gw_grp1security-gateway aaa authentication second-phase context SeGW1 aaa-group sec_gw_grp2
> The following command disables a previously configured AAA authentication parameter for first phase of authentication:
> no security-gateway aaa authentication first-phase
> security-gateway bind
> Binds the SeGW in an HNB-GW service to a logical IP interface serving as an Iuh interface and associates an IPsec IKEv2 crypto-map template.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> security-gateway bind address address crypto-template cryp_name [ context ctxt_name]
> no security-gateway bind
> no
> Removes a previously configured IPSec IP address use for binding the IKEv2 IPSec tunnel (local bind address) to communicate with the Home-NodeBs using Iuh interface.
> bind address address
> Specifies the IP address for the Iuh interface for the IPSec tunnel. This is the IP address where the HNB-GW service is bound and that is provided to the Home-NodeB during HNB-GW discovery.
> The IP address is expressed in IPv4 dotted-decimal or IPv6 colon-separated notation.
> crypto-template cryp_name
> Specifies the Crypto-map template to be used for IPsec IKEv2 tunneling for the interface configured as an Iuh.
> cryp_name specifies the name of the pre-configured Crypto-map template which is configured in Crypto-Map Template Configuration mode and associated with the HNB-GW service to create an IPSec tunnel with a Home-NodeB during HNB-GW discovery procedure over an Iuh interface.
> context ctx_name
> Specifies the name of the pre-configured context in which the Security Gateway service is configured. By default this command uses the HNB-GW service context for the ecurity Gateway configuration.
> Usage
> Use this command to associate or tie the HNB-GW service to a specific logical IP address that is used for binding the Iuh socket to communicate with the Home-NodeB using IPSec tunnel. A maximum of one IP address can be configured with this command for one HNB-GW service.
> The HNB-GW passes the IP address during setting up the HNB-GW discovery procedure with the Home-NodeB.
> Caution: This is a critical configuration. The HNB-GW service cannot be started without this configuration. Any change to this configuration would lead to restarting the HNB-GW service and removing or disabling this configuration stops the HNB-GW service.
> Example
> The following command binds the logical IP interface with the address of 10.2.3.4 to the HNB-GW service using existing IPsec Crypto-Map template crypto1 to establish IPSec tunnel with Home-NodeB:
> security-gateway bind address 10.2.3.4 crypto-template crypto1
> The following command disables a binding that was previously configured:
> security-gateway bind address
> security-gateway username
> Configures the options related to user name received from MS.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> [ no | defualt ] security-gateway username mac-address-stripping
> no
> Disables previously configured option for user name received from MS.
> default
> Sets the user name option configuration of default setting of “Disable”.
> mac-address-stripping
> Sets the system to strip the MAC address from the user name received from the MS. Default: Disabled
> Usage
> Use this command to set the user name related options. By enabling this option system trips the MAC address from the user name received from MS.
> Example
> The following command sets the system to strip the MAC address from user name received from user MS:
> security-gateway username mac-address-stripping
> tnnsf-timer
> Configures the NAS Node Selection Function (NNSF) timer (T-NNSF) which is used by the HNB-GW to store the IMSI and the relevant Global-CN-ID in the short term after Paging. This timer is used for Iu-Flex feature support.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> tnnsf-timer dur
> [no | default] tnnsf-timer
> no
> Disables/removes the configured timer value of NNSF timer (T-NNSF) from HNB-GW service instance.
> default
> Sets the timer value of NNSF timer (T-NNSF) for HNB-GW service instance to default value of 30 seconds.
> tnnsf-timer dur
> Configures the NNSF timer (in seconds) which is used by the HNB-GW to store the IMSI and the relevant Global-CN-ID as an integer from 10 through 60. Default: 30
> Usage
> Use this command to configure the NNSF timer value in seconds for Iu-Flex support.
> Whenever the MSC sends the paging request with IMSI, the HNB-GW stores the Global_CN_ID of the node which issued the paging request message for the given IMSI and HNB-GW starts the tnnsf-timer. HNBGW stores the mapping of IMSI to Global_CN_ID until the tnnsf-timer expires
> Example
> The following command sets the NNSF timer value to 30 seconds in an HNB-GW service instance:
> default tnssf-timer
> ue registration-timeout
> Configures the UE registration timeout duration to de-register the connected UE from an HNB-GW service.
> Product
> HNB-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> ue registration-timeout dur
> [ default | no ] ue registration-timeout
> no
> Disables the UE registration timeout duration and explicitly de-registers UE from the HNB-GW service.
> default
> Restores the UE registration timeout duration value to its default value of 120 seconds.
> dur
> Sets the UE registration timeout duration (in seconds) after which the UE is de-registered from HNB-GW. In a scenario when all Iu connections are released for a subscriber, the HNB-GW service de-registers the UE after cthe onfigured duration only.
> dur is an integer from 60 through 300. Default: 120
> Usage
> Use this command to configure the minimum duration value before de-registering the UE when subscriber fails to establish the Iu connection. If subscriber’s Iu session does not established before configured period then UE is de-registered. Also in a scenario where all Iu connections are released for a subscriber, the HNB-GW service waits for configured period before starting UE deregistration procedure.
> Example
> The following command sets the UE registration timeout duration to 150 second on HNB-GW after expiry of which the UE is de-registered:
> ue registration-timeout 150

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883