IMPORTANT:
CAUTION:
Information Required to Configure the System as an HeNB-GW
Required Local Context Configuration Information
| Required Information | Description |
|---|---|
| Management Interface Configuration | |
| Interface name | An
identification string between 1 and 79 characters (alpha and/or
numeric) by which the interface will be recognized by the system. Multiple names are
needed if multiple interfaces will be configured.
|
| IP address and subnet | IPv4
addresses assigned to the interface. Multiple addresses
and subnets are needed if multiple interfaces will be configured.
|
| Physical port number | The
physical port to which the interface will be bound. Ports are identified
by the chassis slot number where the line card resides followed
by the number of the physical connector on the card. For example,
port 17/1 identifies connector number 1 on the card in
slot 17. A single physical port
can facilitate multiple interfaces.
|
| Gateway IP address | Used when configuring static IP routes from the management interface(s) to a specific network. |
| Security administrator name | The name or names of the security administrator with full rights to the system. |
| Security administrator password | Open or encrypted passwords can be used. |
| Remote access type(s) | The type of remote access that will be used to access the system such as telnetd, sshd, and/or ftpd. |
Required Source Context Configuration Information
| Required Information | Description |
|---|---|
| Source context name | An identification string from 1 to 79 characters (alpha and/or numeric) by which the Source context is recognized by the system.Generally it is identified as source context. |
| Interface name | An
identification string between 1 and 79 characters (alpha and/or
numeric) by which the interface is recognized by the system. Multiple names are
needed if multiple interfaces will be configured.
|
| IP address and subnet | IPv4
addresses assigned to the interface. Multiple addresses
and subnets are needed if multiple interfaces will be configured.
|
| Physical port number | The physical port to which the interface will be bound. Ports are identified by the chassis slot number where the line card resides followed by the number of the physical connector on the card. For example, port 17/1 identifies connector number 1 on the card in slot 17. A single physical port can facilitate multiple interfaces. |
| Gateway IP address | Used when configuring static IP routes from the management interface(s) to a specific network. |
| Ingress and Egress GTP-U Services | |
| Ingress GTP-U service Name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the Ingress GTP-U service can be identified on the system. It is configured in Context Configuration Mode. When S1-U Relay is enabled, the Ingress GTP-U service configuration is critical as it has to be associated with the HeNB-GW Access Service. It is also called access-side GTP-U service for the HeNB-GW ACCESS service. |
| Egress GTP-U service Name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the Egress GTP-U service can be identified on the system. It is configured in Context Configuration Mode. When S1-U Relay is enabled, the Egress GTP-U service configuration is critical as it has to be associated with the HeNB-GW Access Service. It is also called network-side GTP-U service for the HeNB-GW ACCESS service. |
| GTP-U Tunnel interface IP address |
IP addresses assigned
to the interface as GTP-U bond address.
This address will be
used for binding the GTP-U service (local bind address(es)) for
sending/receiving GTP-U packets from/to HeNB using
GTP-U tunnel.
Multiple addresses
and subnets are needed if multiple interfaces will be configured.
|
| S1-AP Configuration (To/from Home-eNodeB) | |
| HeNB-GW access service Name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the HeNB-GW Access service can be identified on the system. It is configured in Context Configuration Mode. At a time, only one HeNB-GW Access Service can be configured per system. |
| HeNB-GW Network service Name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the HeNB-GW Network service can be identified on the system. It is also configured in Context Configuration Mode. At a time, only one HeNB-GW Network Service can be configured per system and therefore there is 1:1 mapping between HeNB-GW Access and Network services. |
Required Destination Context Configuration Information
| Required Information | Description |
|---|---|
| Destination context name |
An identification string
from 1 to 79 characters (alpha and/or numeric) by which
the destination context will be recognized by the system.
|
| Interface name |
An identification string
between 1 and 79 characters (alpha and/or numeric) by which
the interface is recognized by the system.Multiple names are needed
if multiple interfaces will be configured.
|
| IP address and subnet |
IPv4 addresses assigned
to the interface.
Multiple addresses
and subnets are needed if multiple interfaces will be configured.
|
| Physical port number |
The physical port to
which the interface will be bound. Ports are identified by the chassis
slot number where the line card resides followed by the number of
the physical connector on the card. For example, port 17/1 identifies
connector number 1 on the card in slot 17. A single physical port can
facilitate multiple interfaces.
|
| Gateway IP address |
Used when configuring
static IP routes from the management interface(s) to a specific
network.
|
|
HeNB-GW Access Service
Configuration
|
|
| S1-MME interface IP address |
IPv4/IPv6
addresses assigned to the S1-MME interface as SCTP bond address.This
address will be used for binding the SCTP (local bind address(es))
to communicate with the MME using eGTP. The HeNB-GW passes this
IP address during setting up the association with the MME. Multiple
addresses and subnets are needed if multiple interfaces will be configured.
|
| Public Land Mobile Network (PLMN) Identifiers |
Mobile Country Code
(MCC): The MCC can be configured to any integer value from 0
to 999.
|
|
Mobile Network Code
(MNC): The MNC can be configured to any integer value from 0
to 999.
|
|
| S1-MME SCTP Port |
The physical port to
which is used to communicate with the HeNBs over S1-MME interface.
It is usually an integer value ranging from 1 to 65535.
|
| MME ID Group ID |
MME Group ID to be
configured for the HeNB-GW Access Service. This is a required parameter
since the HeNB-GW acts as an MME to the HeNB(s) and this ID is filled
in the S1-SETUP response sent to the HeNB(s). It is an integer ranging
from 32768..65535.
|
| MME Code |
MME Code is also part
of the MME ID configuration. MME Group ID and MME Code both are
required for MME Identifier configuration for the HeNB-GW Access
service. It is an integer which ranges from 0..255.
|
| S1-U Relay |
Enables the S1-U relay
functionality for the HeNB-GW Access Service. Once S1-U Relay is
enabled, the association to Ingress and Egress GTP-U services is
considered as critical configuration for the HeNB-GW Access service.
|
| Associate HeNB-GW Network Service |
A pre-configured HeNB-GW
Network Service is required to be associated to the HeNB-GW Access
Service. User can enter a desired HeNB-GW Network service name even
if it is not pre-configured, but it will be required to be configured
in later course for this HeNB-GW Access service to come up.
|
| Optional Security Gateway Configuration | |
| Security Gateway IP address |
This is the IP Address
where the SeGW service is bound and shall be provided to HeNB during
SeGW-Discovery. This security gateway is associated with the HeNB-GW
Access Service.
Only one SeGW IP address
can be configured.
|
| Diameter Endpoint | An identification string from 1 to 63 characters (alpha and/or numeric) by which the Diameter endpoint configuration is recognized by the system. This Diameter Endpoint is required by the SeGW to communicate with the AAA server. |
| Diameter Endpoint Configuration | |
| Endpoint Name | An identification string from 1 to 63 characters (alpha and/or numeric) by which the Diameter endpoint configuration is recognized by the system. This Diameter Endpoint is required by the SeGW to communicate with the AAA server. |
| Origin realm name | An identification string between 1 through 127 characters. The realm is the Diameter identity. The originator.s realm is present in all Diameter messages and is typically the company or service name. |
| Origin host name | An identification string from 1 to 255 characters (alpha and/or numeric) by which the origin host is recognized by the system. |
| Origin host address | The IP address of the interface. |
| Peer name | The endpoint name described above. |
| Peer realm name | The interface origin realm name described above. |
| Peer address and port number | The IP address and port number of the OCS. |
| IPsec Crypto-map Template Configuration | |
| EAP profile | This
is the profile to be used to provide authenticator modes for incoming packets
on Security Gateway. Only one EAP profile
can be configured.
|
| IP Pool for IPsec Tunnel |
Specifies the IP pool
to assign IP address for IPsec traffic to use.
|
| IKEv2 Transform set |
IKEv2 transform set
for IKE security association.
|
| IPsec Crypto-map Template |
Specifies the Crypto-map
template to be used for IPsec IKEv2 tunneling for the interface
configured.
This Crypto-map template
is to be associated with HeNB-GW Access service if SeGW is enabled
and bind with this HeNB-GW Access service.
HeNB-GW Access Service
can run with or without the IPSec configuration. Since only one
HeNB-GW Access Service can be configured per system, either IPSec
can be configured or not.
Only one IPsec Crypto-map
Template can be configured.
|
| AAA Server Group Context name |
Specifies the name
of the context in which a AAA server group is configured for association
with SeGW for AAA parameters during subscriber authentication phases.
|
| AAA Server Group name |
Specifies the AAA server
group already configured in a context and is to be used for first/second
phase of authentication of subscriber while using SeGW functionality
in an HeNB-GW service.
|
|
HeNB-GW Network Service
Configuration
|
|
| Logical eNodeB | The
Logical eNodeB configuration option enables the configuration of
one or more logical eNodeBs within the HeNB-GW. The Logical eNodeB configuration
is usually used to support load balancing within a pool of TAIs. At
least one logical eNodeB configuration is required to START an HeNB-GW
Network service. 8 Logical eNodeBs are supported per HeNB-GW Network
service.
|
| Public Land Mobile Network (PLMN) Identifiers |
Mobile Country Code
(MCC): The MCC can be configured to any integer value from 0
to 999.
|
|
Mobile Network Code
(MNC): The MNC can be configured to any integer value from 0
to 999.
|
|
| Macro eNodeB ID | Macro eNodeB identifier, required as a parameter for the Logical eNodeB configuration. It is an option to the Home eNodeB identifier. |
| Home eNodeB ID | Home eNodeB identifier, required as a parameter for the Logical eNodeB configuration. It is an option to the Macro eNodeB identifier. |
| S1-MME interface IP address | IPv4 addresses assigned to the S1-MME interface as SCTP bond address. This address will be used for binding the SCTP (local bind address(es)) to communicate with the MME using eGTP. The HeNB-GW passes this IP address during setting up the association with the MME. Multiple addresses and subnets are needed if multiple interfaces will be configured. |
| S1-MME SCTP Port | The physical port to which is used to communicate with the HeNBs over S1-MME interface. It is usually an integer value ranging from 1 to 65535. |
|
Logical eNodeB Configuration
|
|
| MME Pool | A pre-configured MME pool to be associated with the Logical eNodeB. An MME pool is configured in the LTE Policy Configuration Mode. Only one MME Pool instance can be associated with a Logical eNodeB instance. All MMEs in the pool are assumed to support all TAIs in the associated TAI List DB object. One Logical eNodeB can connect up to 8 MMEs and therefore a max of 64 associations can be established between HeNB-GW and MME |
| TAI List DB | A pre-configured list of tracking area identity (TAIs) pool to be associated with the Logical eNodeB. A TAI List database is configured in the LTE Policy Configuration Mode. Only one TAI list DB can be associated with the Logical eNodeB instance. The tai-list-db contains a list of TAIs. These are sent in the S1 Setup message to the MME to indicate the list of TAIs supported by the eNodeB. The TAI database which can be associated to each logical EnodeB can accommodate 256 configuration of TACs. |
|
TAI List DB Configuration
|
|
| MCC |
Mobile Country Code
(MCC): The MCC can be configured to any integer value from 0
to 999.
|
| MNC |
Mobile Network Code
(MNC): The MNC can be configured to any integer value from 0
to 999.
|
| Tracking Area Code (TAC) | TAC is an integer value ranging from 0..65535. The HeNB-GW Network service searches these TACs for establishing UE connections. |
IMPORTANT:
HeNB-GW Service Configuration
configure
------------------
Context Configuration --------------------
context <ingress_ctxt_name>
----------- Interface
and IP addresses Configuration -----------
interface <interface_name>
ip
address <ipv4_addr> 255.255.255.0
ip
address <ipv4_addr> 255.255.255.0
secondary
exit
-------- Access and
Network GTP-U Services Configuration ------
gtpu-service
<gtpu_svc_access>
-noconfirm
bind
ipv4-address <secondary1_ipv4_addr>
exit
gtpu-service
<gtpu_svc_network>
-noconfirm
bind
ipv4-address <secondary2_ipv4_addr>
exit
------------- HeNB-GW
Network Service Configuration -----------
henbgw-network-service <henb_network_svc_name>
-noconfirm
------------ Logical
eNodeB Configuration ----------------------
logical-enb
global-enb-id plmn id mcc <mcc_id>
mnc <mnc_id>
macro-enb-id <macro_enodeb_id>
-n
bind
s1-mme { ipv4-address | ipv6-address } <ip_addr>
s1-mme
sctp port <sctp_port_no>
associate
henbgw mme-pool <mme_pool_name>
associate
tai-list-db <lte_policy_tai_db>
exit
exit
-------------- HeNB-GW
Access Service Configuration --------------------
henbgw-access-service <henb_access_svc_name>
-n
bind
s1-mme { ipv4-address | ipv6-address } <ip_addr>
s1-mme
sctp port <sctp_port_no>
mme-id
group-id <mme_id>
mme-code <mme_code>
associate
henbgw-network-service <henb_network_svc_name>
plmn
id mcc <mcc_id>
mnc <mnc_id>
-------------- S1-U
Relay Configuration --------------------
s1u-relay
associate
access-gtpu-service <gtpu_svc_access>
context ingress
associate
network-gtpu-service <gtpu_svc_network>
context ingress
exit
exit
IMPORTANT:
IMPORTANT:
IMPORTANT:
IPSec Configuration
For EAP-AKA Authentication Only
Configure
context <ctxt_name>
eap-profile <eap_profile_name>
mode
authenticator-pass-through
exit
ipsec
transform-set <ipsec_transform_set_name>
exit
ikev2-ikesa
transform-set <ikesa_transform_set_name>
exit
crypto
template <crypto_template_name>
ikev2-dynamic
authentication
remote eap-profile <eap_profile_name>
ikev2-ikesa
transform-set list <ikesa_transform_set_name>
payload <crypto_template_payload_name>
match childsa match ipv4
ipsec
transform-set list <ipsec_transform_set_name>
exit
exit
exit
For Certificate Based Authentication Only
Configure
certificate
name <cert_name>
pem url <url
format> private-key pem|der url|data <url or data format>
ca-cert
name <cacert_name>
pem|der url|data url or data format
context <ctxt_name>
ipsec
transform-set <ipsec_transform_set_name>
exit
ikev2-ikesa
transform-set <ikesa_transform_set_name>
exit
crypto
template <crypto_template_name>
ikev2-dynamic
authentication
remote certificate
authentication
local certificate
ikev2-ikesa
transform-set <ikesa_transform_set_name>
payload <crypto_template_payload_name>
match childsa match ipv4
ipsec
transform-set list <ipsec_transform_set_name>
exit
certificate <cert_name>
ca-certificate
list ca-cert-name <cacert_name>
exit
For Simultaneous support of Multiple Authentication schemes (EAP-AKA & Certificate)
Configure
certificate
name <cert_name>
pem url <url
format> private-key pem|der url|data <url or data format>
ca-cert
name <cacert_name>
pem|der url|data url or data format
context <ctxt_name>
eap-profile <eap_profile_name>
mode
authenticator-pass-through
exit
ipsec
transform-set <ipsec_transform_set_name>
exit
ikev2-ikesa
transform-set <ikesa_transform_set_name>
exit
ikev2-ikesa
auth-method-set <auth_profile_name1>
authentication
remote eap-profile <eap_profile_name>
exit
ikev2-ikesa
auth-method-set <auth_profile_name2>
authentication
local certificate
authentication
remote certificate
exit
crypto
template <crypto_template_name>
ikev2-dynamic
ikev2-ikesa
auth-method-set <auth_profile_name1> <auth_profile_name2>
ikev2-ikesa
transform-set list <ikesa_transform_set_name>
payload <crypto_template_payload_name>
match childsa match ipv4
ipsec
transform-set list <ipsec_transform_set_name>
exit
certificate <cert_name>
ca-certificate
list ca-cert-name <cacert_name>
exit
GTP-U Service Configuration
configure
context
<dest_ctxt_name>
-noconfirm
gtpu-service
<gtpu_svc_access>
-noconfirm
bind
address { ipv4-address | ipv6-address } <ip_address>
end
configure
context
<dest_ctxt_name>
-noconfirm
gtpu-service
<gtpu_svc_network>
-noconfirm
bind
address ipv4-address <ip_address>
end
LTE Policy Configuration
configure
lte-policy
henbgw
mme-pool <mme_pool_name>
-noconfirm
mme
<mme-name> { ipv4-address | ipv6-address } <ip_addr>
sctp port <sctp_port_no>
exit
tai-list-db <lte_policy_tai_db>
tai
mcc <mcc_id>
mnc <mnc_id>
tac <tac_code1> <tac_code2> <tac_code3>
exit
end
show henbgw-access-service
name <henbgw_access_svc_name>}
show henbgw-network-service
name <henbgw_network_svc_name>}
show configuration
errors section henbgw-network-service}
Logging Facility Configuration
logging filter active
facility henbapp level { critical | error | warning | unusual | info | trace | debug }
logging filter active
facility henbgw level { critical | error | warning | unusual | info | trace | debug }
logging filter active
facility henbgwdemux level { critical | error | warning | unusual | info | trace | debug }
logging filter active
facility henbgwmgr level { critical | error | warning | unusual | info | trace | debug }
configure
logging
console
logging
display event-verbosity {min | concise | full}
logging
filter runtime facility henb-gw level { critical | error | warning | unusual | info | trace | debug }
logging
filter runtime facility henbapp level { critical | error | warning | unusual | info | trace | debug }
logging
filter runtime facility henbgwdemux level { critical | error | warning | unusual | info | trace | debug }
logging
filter runtime facility henbgwmgr level { critical | error | warning | unusual | info | trace | debug }
logging
filter runtime facility sctp { critical | error | warning | unusual | info | trace | debug }
logging
filter runtime facility threshold { critical | error | warning | unusual | info | trace | debug }
IMPORTANT:
Alarm and Alert Trap Configuration
configure
snmp
trap enable ThreshHENBGWHenbSessions target [ target <trap_collector>]
snmp
trap enable ThreshHENBGWPagingMessages target <trap_collector>]
snmp
trap enable ThreshHENBGWUeSessions target <trap_collector>]
snmp
trap { enable | suppress} HenbgwAccessServiceStart
[ target <trap_collector>]
snmp
trap { enable | suppress} HenbgwAccessServiceStop
[ target <trap_collector>]
snmp
trap { enable | suppress} HenbgwMMESCTPAllAssocDown
[ target <trap_collector>]
snmp
trap { enable | suppress} HenbgwMMESCTPAllAssocDownClear
[ target <trap_collector>]
snmp
trap { enable | suppress} HenbgwMMESCTPAssocDown
[ target <trap_collector>]
snmp
trap { enable | suppress} HenbgwMMESCTPAssocUp
[ target <trap_collector>]
snmp
trap { enable | suppress} HenbgwNetworkServiceStart
[ target <trap_collector>]
snmp
trap { enable | suppress} HenbgwNetworkServiceStop
[ target <trap_collector>]
SNMP MIB Traps for HeNB-GW Service
| Traps | Object Id |
|---|---|
| starThreshHENBGWHenbSessions | starentTraps 513 |
| starThreshClearHENBGWHenbSessions | starentTraps 514 |
| starThreshHENBGWUeSessions | starentTraps 515 |
| starThreshClearHENBGWUeSessions | starentTraps 516 |
| starThreshHENBGWPagingMessages | starentTraps 517 |
| starThreshClearHENBGWPagingMessages | starentTraps 518 |
| starHenbgwAccessServiceStart | starentTraps 1193 |
| starHenbgwAccessServiceStop | starentTraps 1194 |
| starHenbgwNetworkServiceStart | starentTraps 1195 |
| starHenbgwNetworkServiceStop | starentTraps 1196 |
| starHenbgwMMESCTPAssocUp | starentTraps 1227 |
| starHenbgwMMESCTPAssocDown | starentTraps 1228 |
| starHenbgwMMESCTPAllAssocDown | starentTraps 1229 |
| starHenbgwMMESCTPAllAssocDownClear | starentTraps 1230 |
IMPORTANT:
Event IDs for HeNB-GW Service
IMPORTANT:
| Facility | Event ID Range |
|---|---|
| HeNB-GW Manager Facility Events | 193000-193999 |
| HeNB-GW Facility Events | 195000-195999 |
| HeNB-GW DEMUX Facility Events | 194000-194999 |
| SCTP Protocol Facility Events | 87300-87499 |
| AAA Client Facility Events | 6000-6999 |
| Alarm Controller Facility Events | 65000-65999 |
| Card/Slot/Port (CSP) Facility Events | 7000-7999 |
| Command Line Interface Facility Events | 30000-30999 |
| Event Log Facility Events | 2000-2999 |
| Threshold Facility Events | 61000-61999 |
Configuring DHCP Service
configure
context <vpn_ctxt_name>
dhcp-service
<dhcp_svc_name>
-noconfirm
dhcp
client-identifier ike-id
dhcp
server selection-algorithm use-all
dhcp
server <dhcp_server_ip>
dhcp
server port 67
end
Configuring Subscriber Template for HeNB
configure
context <vpn_ctxt_name>
subscriber
default
dhcp
service <dhcp_svc_name> context
<vpn_ctxt_name>
end