IPSec for LTE/SAE

Features and Functionality

This section describes IPSec for LTE/SAE networks.

IPSec for LTE/SAE Networks

The Cisco P-GW (Packet Data Network Gateway), S-GW (Serving Gateway), and MME (Mobility Management Entity) support IPSec and IKEv2 encryption using IPv4 and IPv6 addressing in LTE/SAE (Long Term Evolution/System Architecture Evolution) networks, enabling up to 64K IPSec tunnels per ASR 5000 chassis. IPSec and IKEv2 encryption enables network domain security for all IP packet-switched networks, providing confidentiality, integrity, authentication, and anti-replay protection via secure IPSec tunnels.

Encryption Algorithms

IPSec for LTE/SAE supports the following control and data path encryption algorithms:

  • AES-CBC-128 (Advanced Encryption Standard-Cipher Block Chaining-128)
  • AES-CBC-256 (Advanced Encryption Standard-Cipher Block Chaining-256)
  • DES-CBC (Data Encryption Standard-Cipher Block Chaining)
  • 3DES-CBC (Triple Data Encryption Standard-Cipher Bock Chaining)

HMAC Functions

IPSec for LTE/SAE supports the following data path HMAC (Hash-based Message Authentication Code) functions:

  • AES-XCBC-MAC-96 (Advanced Encryption Standard-X Cipher Block Chaining-Message Authentication Code-96)
  • MD5-96 (Message Digest 5-96)
  • SHA1-96 (Secure Hash Algorithm 1-96)

IPSec for LTE/SAE supports the following control path HMAC (Hash-based Message Authentication Code) functions:

  • AES-XCBC-MAC-96 (Advanced Encryption Standard-X Cipher Block Chaining-Message Authentication Code-96)
  • MD5-96 (Message Digest 5-96)
  • SHA1-96 (Secure Hash Algorithm 1-96)
  • SHA2-256-128 (Secure Hash Algorithm 2-256-128)
  • SHA2-384-192 (Secure Hash Algorithm 2-384-192)
  • SHA2-512-256 (Secure Hash Algorithm 2-512-256)

Diffie-Hellman Groups

IPSec for LTE/SAE supports the following Diffie-Hellman groups for IKE and Child SAs (Security Associations):

  • Diffie-Hellman Group 1: 768-bit MODP (Modular Exponential) Group
  • Diffie-Hellman Group 2: 1024-bit MODP Group
  • Diffie-Hellman Group 5: 1536-bit MODP Group
  • Diffie-Hellman Group 14: 2048-bit MODP Group
  • None: No Diffie-Hellman Group (no perfect forward secrecy)

Dynamic Node-to-Node IPSec Tunnels

IPSec for LTE/SAE enables network nodes to initiate an IPSec tunnel with another node for secure signalling and data traffic between the nodes. Once established, a dynamic node-to-node IPSec tunnel continues to carry all of the signaling and/or bearer traffic between the nodes. Dynamic node-to-node IPSec for LTE/SAE is supported on the S1-MME interface for signalling traffic between the eNodeB and the MME, on the S1-U interface for data traffic between the eNodeB and the S-GW, and on the S5 interface for GTP-C signaling traffic and GTP-U data traffic between the S-GW and the P-GW.

Dynamic node-to-node IPSec gets configured using dynamic IKEv2 crypto templates, which are used to specify common cryptographic parameters for the IPSec tunnels such as the encryption algorithm, HMAC function, and Diffie-Hellman group. Additional information necessary for creating node-to-node IPSec tunnels such as authentication methods, certificate revocation lists, and traffic selectors are fetched dynamically from the IPSec tunnel requests.

For configuration instructions for dynamic node-to-node IPSec, see the configuration chapter in the administration guides for the MME, S-GW, and P-GW.

ACL-based Node-to-Node IPSec Tunnels

Node-to-node IPSec for LTE/SAE can also be configured using crypto ACLs (Access Control Lists), which define the matching criteria used for routing subscriber data packets over an IPSec tunnel. ACL-based node-to-node IPSec tunnels are configured using either IPv4 or IPv6 addressing, and are supported on the S1-MME interface for signalling traffic between the eNodeB and the MME, on the S1-U interface for data traffic between the eNodeB and the S-GW, and on the S5 interface for GTP-C signaling traffic and GTP-U data traffic between the S-GW and the P-GW.

Unlike other ACLs that are applied to interfaces, contexts, or to one or more subscribers, crypto ACLs are applied via matching criteria to crypto maps, which define tunnel policies that determine how IPSec is implemented for subscriber data packets. Prior to routing, the system examines the properties of each subscriber data packet. If the packet properties match the criteria specified in the crypto ACL, the system initiates the IPSec policy dictated by the crypto map. ACL-based node-to-node IPSec tunnels are configured using either IKEv2-IPv4 or IKEv2-IPv6 crypto maps for IPv4 or IPv6 addressing.

For configuration instructions for ACL-based node-to-node IPSec, see the configuration chapter in the administration guides for the MME, S-GW, and P-GW.

For more information on ACLs, see the System Administration Guide.

Traffic Selectors

Per RFC 4306, when a packet arrives at an IPSec subsystem and matches a 'protect' selector in its Security Policy Database (SPD), the subsystem must protect the packet via IPSec tunneling. Traffic selectors enable an IPSec subsystem to accomplish this by allowing two endpoints to share information from their SPDs. Traffic selector payloads contain the selection criteria for packets being sent over IPSec security associations (SAs). Traffic selectors can be created on the P-GW, S-GW, and MME during crypto template configuration by specifying a range of peer IPv4 or IPV6 addresses from which to carry traffic over IPSec tunnels.

For example, consider an eNodeB with an IP address of 1.1.1.1 and an S-GW with a service address of 2.2.2.2. The S-GW is registered to listen for IKE requests from the eNodeBs in the network using the following information:

  • Local Address: 2.2.2.2
  • Peer Address Network: 1.1.0.0 Mask: 255.255.0.0
  • Payload ACL (Access Control List): udp host 2.2.2.2 eq 2123 1.1.0.0 0.0.255.255

When an IKE request arrives a the S-GW from eNodeB address 1.1.1.1, the IPSec subsystem converts the payload ACL to: udp host 2.2.2.2 eq 2123 host 1.1.1.1, and this payload becomes the traffic selector for the IPSec tunnel being negotiated.

To properly accommodate control traffic between IPSec nodes, each child SA must include at least two traffic selectors: one with a well-known port in the source address, and one with a well-known port in the destination address. Continuing the example above, the final traffic selectors would be:

  • Destination port as well-known port: udp host 2.2.2.2 1.1.0.0 0.0.255.255 eq 2123
  • Source port as well-known port: udp host 2.2.2.2 eq 2123 1.1.0.0 0.0.255.255

Authentication Methods

IPSec for LTE/SAE supports the following authentication methods:

  • PSK (Pre-Shared Key) Authentication: A pre-shared key is a shared secret that was previously shared between two network nodes. IPSec for LTE/SAE supports PSK such that both IPSec nodes must be configured to use the same shared secret.
  • X.509 Certificate-based Peer Authentication: IPSec for LTE/SAE supports X.509 certificate-based peer authentication and CA (Certificate Authority) certificate authentication as described below.

X.509 Certificate-based Peer Authentication

X.509 specifies standard formats for public key certificates, certificate revocation lists, attribute certificates, and a certification path validation algorithm. X.509 certificates are configured on each IPSec node so that it can send the certificate as part of its IKE_AUTH_REQ for the remote node to authenticate it. These certificates can be in PEM (Privacy Enhanced Mail) or DER (Distinguished Encoding Rules) format, and can be fetched from a repository via HTTP or FTP.

CA certificate authentication is used to validate the certificate that the local node receives from a remote node during an IKE_AUTH exchange.

A maximum of sixteen certificates and sixteen CA certificates are supported per system. One certificate is supported per service, and a maximum of four CA certificates can be bound to one crypto template.

For configuration instructions for X.509 certificate-based peer authentication, see the configuration chapter in the administration guides for the MME, S-GW, and P-GW.

The figure below shows the message flow during X.509 certificate-based peer authentication. The table that follows the figure describes each step in the message flow.
Figure 1. X.509 Certificate-based Peer Authentication

Table 1. X.509 Certificate-based Peer Authentication
Step Description

1.

The peer node initiates an IKEv2 exchange with the local node, known as the IKE_SA_INIT exchange, by issuing an IKE_SA_INIT Request to negotiate cryptographic algorithms, exchange nonces, and perform a Diffie-Hellman exchange with the local node.

2.

The local node responds with an IKE_SA_INIT Response by choosing a cryptographic suite from the initiator’s offered choices, completing the Diffie-Hellman and nonce exchanges with the peer node. In addition, the local node includes the list of CA certificates that it will accept in its CERTREQ payload. For successful peer authentication, the CERTREQ payload must contain at least one CA certificate that is in the trust chain of the peer certificate. At this point in the negotiation, the IKE_SA_INIT exchange is complete and all but the headers of all the messages that follow are encrypted and integrity-protected.

3.

The peer node initiates an IKE_AUTH exchange with the local node by including the IDi payload, setting the CERT payload to the peer certificate, and including the AUTH payload containing the signature of the previous IKE_SA_INIT Request message (in step 1) generated using the private key of the peer certificate. The authentication algorithm used to generate the AUTH payload is also included in the AUTH payload. The peer node also includes the CERTREQ payload containing the list of SHA-1 hash algorithms for local node authentication. For successful server authentication, the CERTREQ payload must contain at least one CA certificate that is in the trust chain of the peer certificate.

4.

Using the CA certificate corresponding to the peer certificate, the local node first verifies that the peer certificate in the CERT payload has not been modified and the identity included in the IDi corresponds to the identity in the peer certificate. If the verification is successful, using the public key of the peer certificate, the local node generates the expected AUTH payload and compares it with the received AUTH payload. If they match, the authentication of the peer node is successful. Otherwise, the local node sends an IKEv2 Notification message indicating authentication failure.

5.

The local node responds with the IKE_AUTH Response, including the IDr payload, setting the CERT payload to the local node certificate, and including the AUTH payload containing the signature of the IKE_SA_INIT Response message (in step 2) generated using the private key of the local node certificate. The authentication algorithm used to generate the AUTH payload is also included in the AUTH payload.

6.

Using the CA certificate corresponding to the local node certificate, the peer node first verifies that the local node certificate in the CERT payload has not been modified. If the verification is successful, using the public key of the local node certificate, the peer generates the expected AUTH payload and compares it with the received AUTH payload. If they match, the local node authentication is successful. This completes the IKE_AUTH exchange.

7.

An IPSec SA gets established between the peer node and the local node. If more IPSec SAs are needed, either the peer or local node can initiate the creation of additional Child SAs using a CREATE_CHILD_SA exchange.



Certificate Revocation Lists

Certificate revocation lists track certificates that have been revoked by the CA (Certificate Authority) and are no longer valid. Per RFC 3280, during certificate validation, IPSec for LTE/SAE checks the certificate revocation list to verify that the certificate the local node receives from the remote node has not expired and hence is still valid.

During configuration via the system CLI, one certificate revocation list is bound to each crypto template and can be fetched from its repository via HTTP or FTP.

Child SA Rekey Support

Rekeying of an IKEv2 Child Security Association (SA) occurs for an already established Child SA whose lifetime (either time-based or data-based) is about to exceed a maximum limit. The IPSec subsystem initiates rekeying to replace the existing Child SA. During rekeying, two Child SAs exist momentarily (500ms or less) to ensure that transient packets from the original Child SA are processed by the IPSec node and not dropped.

Child SA rekeying is disabled by default, and rekey requests are ignored. This feature gets enabled in the Crypto Configuration Payload Mode of the system’s CLI.

IKEv2 Keep-Alive Messages (Dead Peer Detection)

IPSec for LTE/SAE supports IKEv2 keep-alive messages, also known as Dead Peer Detection (DPD), originating from both ends of an IPSec tunnel. Per RFC 3706, DPD is used to simplify the messaging required to verify communication between peers and tunnel availability. You configure DPD on each IPSec node. You can also disable DPD, and the node will not initiate DPD exchanges with other nodes. However, the node always responds to DPD availability checks initiated by another node regardless of its DPD configuration.

E-UTRAN/EPC Logical Network Interfaces Supporting IPSec Tunnels

The figure below shows the logical network interfaces over which secure IPSec tunnels can be created in an E-UTRAN/EPC (Evolved UMTS Terrestrial Radio Access Network/Evolved Packet Core) network. The table that follows the figure provides a description of each logical network interface.


Figure 2. E-UTRAN/EPC Logical Network Interfaces Supporting IPSec Tunnels

Table 2. E-UTRAN/EPC Logical Network Interfaces Supporting IPSec Tunnels
Interface Description

S1-MME Interface

This interface is the reference point for the control plane protocol between the eNodeB and the MME. S1-MME uses S1-AP (S1- Application Protocol) over SCTP (Stream Control Transmission Protocol) as the transport layer protocol for guaranteed delivery of signaling messages between the MME and the eNodeB (S1).

The S1-AP over SCTP signaling traffic gets carried over an IPSec tunnel.

When a subscriber UE initiates a connection with the eNodeB, the eNodeB initiates an IPSec tunnel with the MME, and SCTP signaling for all subsequent subscriber UEs served by this MME gets carried over the same IPSec tunnel.

S1-U Interface

This interface is the reference point for bearer channel tunneling between the eNodeB and the S-GW.

Typically, the eNodeB initiates an IPSec tunnel with the S-GW over this interface for subscriber data traffic. But the S-GW may also initiate an IPSec tunnel with the eNodeB if required.

S5 Interface

This interface is the reference point for tunneling and management between the S-GW and the P-GW.

Based on the requested APN from a subscriber UE, the MME selects both the S-GW and the P-GW that the S-GW connects to. GTP-C signaling traffic and GTP-U data traffic are carried over the IPSec tunnel between the S-GW and P-GW for the current and all subsequent subscriber UEs.



IPSec Tunnel Termination

IPSec tunnel termination occurs during the following scenarios:

  • Idle Tunnel Termination: When a session manager for a service detects that all subscriber sessions using a given IPSec tunnel have terminated, the IPSec tunnel also gets terminated after a timeout period.
  • Service Termination: When a service running on a network node is brought down for any reason, all corresponding IPSec tunnels get terminated. This may be caused by the interface for a service going down, a service being stopped manually, or a task handling an IPSec tunnel restarting.
  • Unreachable Peer: If a network node detects an unreachable peer via Dead Peer Detection (DPD), the IPSec tunnel between the nodes gets terminated. DPD can be enabled per P-GW, S-GW, and MME service via the system CLI during crypto template configuration.
  • E-UTRAN Handover Handling: Any IPSec tunnel that becomes unusable due to an E-UTRAN network handover gets terminated, while the network node to which the session is handed initiates a new IPSec tunnel for the session.

Configuring Optional Features on the MME

The configuration examples in this section are optional and provided to cover the most common uses of the MME in a live network. The intent of these examples is to provide a base configuration for testing.

The following optional configurations are provided in this section:

Configuring X.509 Certificate-based Peer Authentication

The configuration example in this section enables X.509 certificate-based peer authentication, which can be used as the authentication method for IP Security on the MME.

IMPORTANT:

IP Security is a licensed feature and requires the purchase of the IP Security feature license to enable it.

The following configuration example enables X.509 certificate-based peer authentication on the MME.

In Global Configuration Mode, specify the name of the X.509 certificate and CA certificate, as follows:

configure
   certificate
name <cert_name>
pem data <cert_pem_data>
   ca-certificate
name <ca_cert_name> pem
url <ca_cert_url>
   end
Notes:
  • The certificate name and ca-certificate list ca-cert-name commands specify the X.509 certificate and CA certificate to be used.
  • The PEM-formatted data for the certificate and CA certificate can be specified, or the information can be read from a file via a specified URL.

When creating the crypto template for IPSec in the Context Configuration Mode, bind the X.509 certificate and CA certificate to the crypto template and enable X.509 certificate-based peer authentication for the local and remote nodes, as follows:

configure
   context <mme_context_name>
      crypto
template <crypto_template_name>
ikev2-dynamic
         certificate
name <cert_name>
         ca-certificate
list ca-cert-name <ca_cert_name>
         authentication
local certificate
         authentication
remote certificate
         end
Notes:
  • A maximum of sixteen certificates and sixteen CA certificates are supported per system. One certificate is supported per service, and a maximum of four CA certificates can be bound to one crypto template.
  • The certificate name and ca-certificate list ca-cert-name commands bind the certificate and CA certificate to the crypto template.
  • The authentication local certificate and authentication remote certificate commands enable X.509 certificate-based peer authentication for the local and remote nodes.

Configuring Dynamic Node-to-Node IP Security on the S1-MME Interface

The configuration example in this section creates an IKEv2/IPSec dynamic node-to-node tunnel endpoint on the S1-MME interface.

IMPORTANT:

IP Security is a licensed feature and requires the purchase of the IP Security feature license to enable it.

The following configuration examples are included in this section:

Creating and Configuring an IPSec Transform Set

The following example configures an IPSec transform set which is used to define the security association that determines the protocols used to protect the data on the interface:

configure
   context <mme_context_name>
      ipsec
transform-set <ipsec_transform-set_name>
         encryption
aes-cbc-128
         group
none
         hmac
sha1-96
         mode
tunnel
         end

Notes:

  • The encryption algorithm, aes-cbc-128, or Advanced Encryption Standard Cipher Block Chaining, is the default algorithm for IPSec transform sets configured on the system.
  • The group none command specifies that no crypto strength is included and that Perfect Forward Secrecy is disabled. This is the default setting for IPSec transform sets configured on the system.
  • The hmac command configures the Encapsulating Security Payload (ESP) integrity algorithm. The sha1-96 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IPSec transform sets configured on the system.
  • The mode tunnel command specifies that the entire packet is to be encapsulated by the IPSec header including the IP header. This is the default setting for IPSec transform sets configured on the system.

Creating and Configuring an IKEv2 Transform Set

The following example configures an IKEv2 transform set:

configure
   context <mme_context_name>
      ikev2-ikesa
transform-set <ikev2_transform-set_name>
         encryption
aes-cbc-128
         group
2
         hmac
sha1-96
         lifetime <sec>
         prf
sha1
         end

Notes:

  • The encryption algorithm, aes-cbc-128, or Advanced Encryption Standard Cipher Block Chaining, is the default algorithm for IKEv2 transform sets configured on the system.
  • The group 2 command specifies the Diffie-Hellman algorithm as Group 2, indicating medium security. The Diffie-Hellman algorithm controls the strength of the crypto exponentials. This is the default setting for IKEv2 transform sets configured on the system.
  • The hmac command configures the Encapsulating Security Payload (ESP) integrity algorithm. The sha1-96 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IKEv2 transform sets configured on the system.
  • The lifetime command configures the time the security key is allowed to exist, in seconds.
  • The prf command configures the IKE Pseudo-random Function which produces a string of bits that cannot be distinguished from a random bit string without knowledge of the secret key. The sha1 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IKEv2 transform sets configured on the system.

Creating and Configuring a Crypto Template

The following example configures an IKEv2 crypto template:

configure
   context <mme_context_name>
      crypto
template <crypto_template_name>
ikev2-dynamic
         authentication
local pre-shared-key key <text>
         authentication
remote pre-shared-key key <text>
         ikev2-ikesa
transform-set list <name1>
. . . <name6>
         ikev2-ikesa
rekey
         payload
<name>
match childsa match ipv4
            ipsec
transform-set list <name1>
. . . <name4>
            rekey
            end
Notes:
  • The ikev2-ikesa transform-set list command specifies up to six IKEv2 transform sets.
  • The ipsec transform-set list command specifies up to four IPSec transform sets.

Binding the S1-MME IP Address to the Crypto Template

The following example configures the binding of the S1-MME interface to the crypto template:

configure
   context <mme_context_name>
      mme-service <mme_svc_name>
         bind
s1-mme ipv4-address <address>
ipv4-address <address> crypto-template <enodeb_crypto_template>
         end

Notes:

  • The bind command in the MME service configuration can also be specified as an IPv6 address using the ipv6-address command.
  • This example shows the bind command using multi-homed addresses. The multi-homing feature also supports the use of IPv6 addresses.
  • The bind command also allows the interface(s) to be associated with a crypto map supporting IP Security. This support applies to both IPv4 and IPv6 addresses.

Configuring ACL-based Node-to-Node IP Security on the S1-MME Interface

The configuration example in this section creates an IKEv2/IPSec ACL-based node-to-node tunnel endpoint on the S1-MME interface.

IMPORTANT:

IP Security is a licensed feature and requires the purchase of the IP Security feature license to enable it.

The following configuration examples are included in this section:

Creating and Configuring a Crypto Access Control List

The following example configures a crypto ACL (Access Control List), which defines the matching criteria used for routing subscriber data packets over an IPSec tunnel:

configure
   context <mme_context_name>
      ip
access-list <acl_name>
         permit
tcp host <source_host_address>
host <dest_host_address>
         end

Notes:

  • The permit command in this example routes IPv4 traffic from the peer server with the specified destination host IPv4 address to this MME with the specified source host IPv4 address.

Creating and Configuring an IPSec Transform Set

The following example configures an IPSec transform set which is used to define the security association that determines the protocols used to protect the data on the interface:

configure
   context <mme_context_name>
      ipsec
transform-set <ipsec_transform-set_name>
         encryption
aes-cbc-128
         group
none
         hmac
sha1-96
         mode
tunnel
         end

Notes:

  • The encryption algorithm, aes-cbc-128, or Advanced Encryption Standard Cipher Block Chaining, is the default algorithm for IPSec transform sets configured on the system.
  • The group none command specifies that no crypto strength is included and that Perfect Forward Secrecy is disabled. This is the default setting for IPSec transform sets configured on the system.
  • The hmac command configures the Encapsulating Security Payload (ESP) integrity algorithm. The sha1-96 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IPSec transform sets configured on the system.
  • The mode tunnel command specifies that the entire packet is to be encapsulated by the IPSec header including the IP header. This is the default setting for IPSec transform sets configured on the system.

Creating and Configuring an IKEv2 Transform Set

The following example configures an IKEv2 transform set:

configure
   context <mme_context_name>
      ikev2-ikesa
transform-set <ikev2_transform-set_name>
         encryption
aes-cbc-128
         group
2
         hmac
sha1-96
         lifetime <sec>
         prf
sha1
         end

Notes:

  • The encryption algorithm, aes-cbc-128, or Advanced Encryption Standard Cipher Block Chaining, is the default algorithm for IKEv2 transform sets configured on the system.
  • The group 2 command specifies the Diffie-Hellman algorithm as Group 2, indicating medium security. The Diffie-Hellman algorithm controls the strength of the crypto exponentials. This is the default setting for IKEv2 transform sets configured on the system.
  • The hmac command configures the Encapsulating Security Payload (ESP) integrity algorithm. The sha1-96 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IKEv2 transform sets configured on the system.
  • The lifetime command configures the time the security key is allowed to exist, in seconds.
  • The prf command configures the IKE Pseudo-random Function which produces a string of bits that cannot be distinguished from a random bit string without knowledge of the secret key. The sha1 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IKEv2 transform sets configured on the system.

Creating and Configuring a Crypto Map

The following example configures an IKEv2 crypto map:

configure
   context <mme_context_name>
      crypto
map <crypto_map_name> ikev2-ipv4
         match
address <acl_name>
         peer <ipv4_address>
         authentication
local pre-shared-key key <text>
         authentication
remote pre-shared-key key <text>
         payload
<name>
match ipv4
            lifetime <seconds>
            ipsec
transform-set list <name1>
. . . <name4>
            exit
         exit
      interface
<s1-mme_intf_name>
         ip
address <ipv4_address>
         crypto
map <crypto_map_name>
         exit
      exit
   port
ethernet <slot_number/port_number>
      no
shutdown
      bind
interface <s1-mme_intf_name> <mme_context_name>
      end

Notes:

  • The type of crypto map used in this example is IKEv2/IPv4 for IPv4 addressing. An IKEv2/IPv6 crypto map can also be used for IPv6 addressing.
  • The ipsec transform-set list command specifies up to four IPSec transform sets.

Configuring Optional Features on the eGTP S-GW

The configuration examples in this section are optional and are provided to cover the most common uses of the eGTP S-GW in a live network. The intent of these examples is to provide a base configuration for testing.

The following optional configurations are provided in this section:

Configuring X.509 Certificate-based Peer Authentication

The configuration example in this section enables X.509 certificate-based peer authentication, which can be used as the authentication method for IP Security on the S-GW.

IMPORTANT:

IP Security is a licensed feature and requires the purchase of the IP Security feature license to enable it.

The following configuration example enables X.509 certificate-based peer authentication on the S-GW.

In Global Configuration Mode, specify the name of the X.509 certificate and CA certificate, as follows:

configure
   certificate
name <cert_name>
pem data <cert_pem_data>
   ca-certificate
name <ca_cert_name> pem
url <ca_cert_url>
   end
Notes:
  • The certificate name and ca-certificate list ca-cert-name commands specify the X.509 certificate and CA certificate to be used.
  • The PEM-formatted data for the certificate and CA certificate can be specified, or the information can be read from a file via a specified URL.

When creating the crypto template for IPSec in Context Configuration Mode, bind the X.509 certificate and CA certificate to the crypto template and enable X.509 certificate-based peer authentication for the local and remote nodes, as follows:

configure
   context <sgw_context_name>
      crypto
template <crypto_template_name>
ikev2-dynamic
         certificate
name <cert_name>
         ca-certificate
list ca-cert-name <ca_cert_name>
         authentication
local certificate
         authentication
remote certificate
         end

Notes:

  • A maximum of sixteen certificates and sixteen CA certificates are supported per system. One certificate is supported per service, and a maximum of four CA certificates can be bound to one crypto template.
  • The certificate name and ca-certificate list ca-cert-name commands bind the certificate and CA certificate to the crypto template.
  • The authentication local certificate and authentication remote certificate commands enable X.509 certificate-based peer authentication for the local and remote nodes.

Configuring Dynamic Node-to-Node IP Security on the S1-U and S5 Interfaces

The configuration example in this section creates an IPSec/IKEv2 dynamic node-to-node tunnel endpoint on the S1-U and S5 interfaces.

IMPORTANT:

IP Security is a licensed feature and requires the purchase of the IP Security feature license to enable it.

The following configuration examples are included in this section:

Creating and Configuring an IPSec Transform Set

The following example configures an IPSec transform set, which is used to define the security association that determines the protocols used to protect the data on the interface:

configure
   context <sgw_context_name>
      ipsec
transform-set <ipsec_transform-set_name>
         encryption
aes-cbc-128
         group
none
         hmac
sha1-96
         mode
tunnel
         end

Notes:

  • The encryption algorithm, aes-cbc-128, or Advanced Encryption Standard Cipher Block Chaining, is the default algorithm for IPSec transform sets configured on the system.
  • The group none command specifies that no crypto strength is included and that Perfect Forward Secrecy is disabled. This is the default setting for IPSec transform sets configured on the system.
  • The hmac command configures the Encapsulating Security Payload (ESP) integrity algorithm. The sha1-96 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IPSec transform sets configured on the system.
  • The mode tunnel command specifies that the entire packet is to be encapsulated by the IPSec header, including the IP header. This is the default setting for IPSec transform sets configured on the system.

Creating and Configuring an IKEv2 Transform Set

The following example configures an IKEv2 transform set:

configure
   context <sgw_context_name>
      ikev2-ikesa
transform-set <ikev2_transform-set_name>
         encryption
aes-cbc-128
         group
2
         hmac
sha1-96
         lifetime <sec>
         prf
sha1
         end

Notes:

  • The encryption algorithm, aes-cbc-128, or Advanced Encryption Standard Cipher Block Chaining, is the default algorithm for IKEv2 transform sets configured on the system.
  • The group 2 command specifies the Diffie-Hellman algorithm as Group 2, indicating medium security. The Diffie-Hellman algorithm controls the strength of the crypto exponentials. This is the default setting for IKEv2 transform sets configured on the system.
  • The hmac command configures the Encapsulating Security Payload (ESP) integrity algorithm. The sha1-96 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IKEv2 transform sets configured on the system.
  • The lifetime command configures the time the security key is allowed to exist, in seconds.
  • The prf command configures the IKE Pseudo-random Function, which produces a string of bits that cannot be distinguished from a random bit string without knowledge of the secret key. The sha1 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IKEv2 transform sets configured on the system.

Creating and Configuring a Crypto Template

The following example configures an IKEv2 crypto template:

configure
   context <sgw_context_name>
      crypto
template <crypto_template_name>
ikev2-dynamic
         ikev2-ikesa
transform-set list <name1>
. . . <name6>
         ikev2-ikesa
rekey
         payload
<name>
match childsa match ipv4
            ipsec
transform-set list <name1>
. . . <name4>
            rekey
            end

Notes:

  • The ikev2-ikesa transform-set list command specifies up to six IKEv2 transform sets.
  • The ipsec transform-set list command specifies up to four IPSec transform sets.

Binding the S1-U and S5 IP Addresses to the Crypto Template

The following example configures the binding of the S1-U and S5 interfaces to the crypto template.

configure
   context <sgw_ingress_context_name>
      gtpu-service <gtpu_ingress_service_name>
         bind
ipv4-address <s1-u_interface_ip_address>
crypto-template <enodeb_crypto_template>
         exit
      egtp-service <egtp_ingress_service_name>
         interface-type
interface-sgw-ingress
         associate
gtpu-service <gtpu_ingress_service_name>
         gtpc
bind address <s1u_interface_ip_address>
         exit
      exit
   context <sgw_egress_context_name>
      gtpu-service <gtpu_egress_service_name>
         bind
ipv4-address <s5_interface_ip_address>
crypto-template <enodeb_crypto_template>
         exit
      egtp-service <egtp_egress_service_name>
         interface-type
interface-sgw-egress
         associate
gtpu-service <gtpu_egress_service_name>
         gtpc
bind address <s5_interface_ip_address>
         exit
      exit
   context <sgw_ingress_context_name>
      sgw-service
<sgw_service_name>
-noconfirm
         egtp-service
ingress service <egtp_ingress_service_name>
         egtp-service
egress context <sgw_egress_context_name>
         end

Notes:

  • The bind command in the GTP-U ingress and egress service configuration can also be specified as an IPv6 address using the ipv6-address command.

Configuring ACL-based Node-to-Node IP Security on the S1-U and S5 Interfaces

The configuration example in this section creates an IKEv2/IPSec ACL-based node-to-node tunnel endpoint on the S1-U and S5 interfaces.

IMPORTANT:

IP Security is a licensed feature and requires the purchase of the IP Security feature license to enable it.

The following configuration examples are included in this section:

Creating and Configuring a Crypto Access Control List

The following example configures a crypto ACL (Access Control List), which defines the matching criteria used for routing subscriber data packets over an IPSec tunnel:

configure
   context <sgw_context_name>
      ip
access-list <acl_name>
         permit
tcp host <source_host_address>
host <dest_host_address>
         end

Notes:

  • The permit command in this example routes IPv4 traffic from the peer server with the specified destination host IPv4 address to this SGW with the specified source host IPv4 address.

Creating and Configuring an IPSec Transform Set

The following example configures an IPSec transform set which is used to define the security association that determines the protocols used to protect the data on the interface:

configure
   context <sgw_context_name>
      ipsec
transform-set <ipsec_transform-set_name>
         encryption
aes-cbc-128
         group
none
         hmac
sha1-96
         mode
tunnel
         end

Notes:

  • The encryption algorithm, aes-cbc-128, or Advanced Encryption Standard Cipher Block Chaining, is the default algorithm for IPSec transform sets configured on the system.
  • The group none command specifies that no crypto strength is included and that Perfect Forward Secrecy is disabled. This is the default setting for IPSec transform sets configured on the system.
  • The hmac command configures the Encapsulating Security Payload (ESP) integrity algorithm. The sha1-96 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IPSec transform sets configured on the system.
  • The mode tunnel command specifies that the entire packet is to be encapsulated by the IPSec header including the IP header. This is the default setting for IPSec transform sets configured on the system.

Creating and Configuring an IKEv2 Transform Set

The following example configures an IKEv2 transform set:

configure
   context <sgw_context_name>
      ikev2-ikesa
transform-set <ikev2_transform-set_name>
         encryption
aes-cbc-128
         group
2
         hmac
sha1-96
         lifetime <sec>
         prf
sha1
         end

Notes:

  • The encryption algorithm, aes-cbc-128, or Advanced Encryption Standard Cipher Block Chaining, is the default algorithm for IKEv2 transform sets configured on the system.
  • The group 2 command specifies the Diffie-Hellman algorithm as Group 2, indicating medium security. The Diffie-Hellman algorithm controls the strength of the crypto exponentials. This is the default setting for IKEv2 transform sets configured on the system.
  • The hmac command configures the Encapsulating Security Payload (ESP) integrity algorithm. The sha1-96 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IKEv2 transform sets configured on the system.
  • The lifetime command configures the time the security key is allowed to exist, in seconds.
  • The prf command configures the IKE Pseudo-random Function which produces a string of bits that cannot be distinguished from a random bit string without knowledge of the secret key. The sha1 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IKEv2 transform sets configured on the system.

Creating and Configuring a Crypto Map

The following example configures an IKEv2 crypto map and applies it to the S1-U interface:

configure
   context <sgw_ingress_context_name>
      crypto
map <crypto_map_name> ikev2-ipv4
         match
address <acl_name>
         peer <ipv4_address>
         authentication
local pre-shared-key key <text>
         authentication
remote pre-shared-key key <text>
         payload
<name>
match ipv4
            lifetime <seconds>
            ipsec
transform-set list <name1>
. . . <name4>
            exit
         exit
      interface
<s1-u_intf_name>
         ip
address <ipv4_address>
         crypto
map <crypto_map_name>
         exit
      exit
   port
ethernet <slot_number/port_number>
      no
shutdown
      bind
interface <s1_u_intf_name> <sgw_ingress_context_name>
      end

Notes:

  • The type of crypto map used in this example is IKEv2/IPv4 for IPv4 addressing. An IKEv2/IPv6 crypto map can also be used for IPv6 addressing.
  • The ipsec transform-set list command specifies up to four IPSec transform sets.

The following example configures an IKEv2 crypto map and applies it to the S5 interface:

configure
   context <sgw_egress_context_name>
      crypto
map <crypto_map_name> ikev2-ipv4
         match
address <acl_name>
         peer <ipv4_address>
         authentication
local pre-shared-key key <text>
         authentication
remote pre-shared-key key <text>
         payload
<name>
match ipv4
            lifetime <seconds>
            ipsec
transform-set list <name1>
. . . <name4>
            exit
         exit
      interface <s5_intf_name>
         ip
address <ipv4_address>
         crypto
map <crypto_map_name>
         exit
      exit
   port
ethernet <slot_number/port_number>
      no
shutdown
      bind
interface <s5_intf_name> <sgw_egress_context_name>
      end

Notes:

  • The type of crypto map used in this example is IKEv2/IPv4 for IPv4 addressing. An IKEv2/IPv6 crypto map can also be used for IPv6 addressing.
  • The ipsec transform-set list command specifies up to four IPSec transform sets.

Configuring Optional Features on the P-GW

The configuration examples in this section are optional and provided to cover the most common uses of the P-GW in a live network. The intent of these examples is to provide a base configuration for testing.

The following optional configurations are provided in this section:

Configuring X.509 Certificate-based Peer Authentication

The configuration example in this section enables X.509 certificate-based peer authentication, which can be used as the authentication method for IP Security on the P-GW.

IMPORTANT:

IP Security is a licensed feature and requires the purchase of the IP Security feature license to enable it.

The following configuration example enables X.509 certificate-based peer authentication on the P-GW.

In Global Configuration Mode, specify the name of the X.509 certificate and CA certificate, as follows:

configure
   certificate
name <cert_name>
pem data <cert_pem_data>
   ca-certificate
name <ca_cert_name> pem
url <ca_cert_url>
   end
Notes:
  • The certificate name and ca-certificate list ca-cert-name commands specify the X.509 certificate and CA certificate to be used.
  • The PEM-formatted data for the certificate and CA certificate can be specified, or the information can be read from a file via a specified URL.

When creating the crypto template for IPSec in Context Configuration Mode, bind the X.509 certificate and CA certificate to the crypto template and enable X.509 certificate-based peer authentication for the local and remote nodes, as follows:

configure
   context <pgw_context_name>
      crypto
template <crypto_template_name>
ikev2-dynamic
         certificate
name <cert_name>
         ca-certificate
list ca-cert-name <ca_cert_name>
         authentication
local certificate
         authentication
remote certificate
         end

Notes:

  • A maximum of sixteen certificates and sixteen CA certificates are supported per system. One certificate is supported per service, and a maximum of four CA certificates can be bound to one crypto template.
  • The certificate name and ca-certificate list ca-cert-name commands bind the certificate and CA certificate to the crypto template.
  • The authentication local certificate and authentication remote certificate commands enable X.509 certificate-based peer authentication for the local and remote nodes.

Configuring Dynamic Node-to-Node IP Security on the S5 Interface

The configuration example in this section creates an IPSec/IKEv2 dynamic node-to-node tunnel endpoint on the S5 interface.

IMPORTANT:

IP Security is a licensed feature and requires the purchase of the IP Security feature license to enable it.

The following configuration examples are included in this section:

Creating and Configuring an IPSec Transform Set

The following example configures an IPSec transform set, which is used to define the security association that determines the protocols used to protect the data on the interface:

configure
   context <pgw_context_name>
      ipsec
transform-set <ipsec_transform-set_name>
         encryption
aes-cbc-128
         group
none
         hmac
sha1-96
         mode
tunnel
         end

Notes:

  • The encryption algorithm, aes-cbc-128, or Advanced Encryption Standard Cipher Block Chaining, is the default algorithm for IPSec transform sets configured on the system.
  • The group none command specifies that no crypto strength is included and that Perfect Forward Secrecy is disabled. This is the default setting for IPSec transform sets configured on the system.
  • The hmac command configures the Encapsulating Security Payload (ESP) integrity algorithm. The sha1-96 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IPSec transform sets configured on the system.
  • The mode tunnel command specifies that the entire packet is to be encapsulated by the IPSec header, including the IP header. This is the default setting for IPSec transform sets configured on the system.

Creating and Configuring an IKEv2 Transform Set

The following example configures an IKEv2 transform set:

configure
   context <pgw_context_name>
      ikev2-ikesa
transform-set <ikev2_transform-set_name>
         encryption
aes-cbc-128
         group
2
         hmac
sha1-96
         lifetime <sec>
         prf
sha1
         end

Notes:

  • The encryption algorithm, aes-cbc-128, or Advanced Encryption Standard Cipher Block Chaining, is the default algorithm for IKEv2 transform sets configured on the system.
  • The group 2 command specifies the Diffie-Hellman algorithm as Group 2, indicating medium security. The Diffie-Hellman algorithm controls the strength of the crypto exponentials. This is the default setting for IKEv2 transform sets configured on the system.
  • The hmac command configures the Encapsulating Security Payload (ESP) integrity algorithm. The sha1-96 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IKEv2 transform sets configured on the system.
  • The lifetime command configures the time the security key is allowed to exist, in seconds.
  • The prf command configures the IKE Pseudo-random Function, which produces a string of bits that cannot be distinguished from a random bit string without knowledge of the secret key. The sha1 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IKEv2 transform sets configured on the system.

Creating and Configuring a Crypto Template

The following example configures an IKEv2 crypto template:

configure
   context <pgw_context_name>
      crypto
template <crypto_template_name>
ikev2-dynamic
         ikev2-ikesa
transform-set list <name1>
. . . <name6>
         ikev2-ikesa
rekey
         payload
<name>
match childsa match ipv4
            ipsec
transform-set list <name1>
. . . <name4>
            rekey
            end

Notes:

  • The ikev2-ikesa transform-set list command specifies up to six IKEv2 transform sets.
  • The ipsec transform-set list command specifies up to four IPSec transform sets.

Binding the S5 IP Address to the Crypto Template

The following example configures the binding of the S5 interface to the crypto template:

configure
   context <pgw_ingress_context_name>
      gtpu-service <gtpu_ingress_service_name>
         bind
ipv4-address <s5_interface_ip_address>
crypto-template <sgw_s5_crypto_template>
         exit
      egtp-service <egtp_ingress_service_name>
         interface-type
interface-pgw-ingress
         associate
gtpu-service <gtpu_ingress_service_name>
         gtpc
bind ipv4-address <s5_interface_ip_address>
         exit
      pgw-service
<pgw_service_name>
-noconfirm
         plmn
id mcc <id>
mnc <id>
primary
         associate
egtp-service <egtp_ingress_service_name>
         end

Notes:

  • The bind command in the GTP-U and eGTP service configuration can also be specified as an IPv6 address using the ipv6-address command.

Configuring ACL-based Node-to-Node IP Security on the S5 Interface

The configuration example in this section creates an IKEv2/IPSec ACL-based node-to-node tunnel endpoint on the S5 interface.

IMPORTANT:

IP Security is a licensed feature and requires the purchase of the IP Security feature license to enable it.

The following configuration examples are included in this section:

Creating and Configuring a Crypto Access Control List

The following example configures a crypto ACL (Access Control List), which defines the matching criteria used for routing subscriber data packets over an IPSec tunnel:

configure
   context <pgw_context_name>
      ip
access-list <acl_name>
         permit
tcp host <source_host_address>
host <dest_host_address>
         end

Notes:

  • The permit command in this example routes IPv4 traffic from the peer server with the specified destination host IPv4 address to this PGW with the specified source host IPv4 address.

Creating and Configuring an IPSec Transform Set

The following example configures an IPSec transform set which is used to define the security association that determines the protocols used to protect the data on the interface:

configure
   context <pgw_context_name>
      ipsec
transform-set <ipsec_transform-set_name>
         encryption
aes-cbc-128
         group
none
         hmac
sha1-96
         mode
tunnel
         end

Notes:

  • The encryption algorithm, aes-cbc-128, or Advanced Encryption Standard Cipher Block Chaining, is the default algorithm for IPSec transform sets configured on the system.
  • The group none command specifies that no crypto strength is included and that Perfect Forward Secrecy is disabled. This is the default setting for IPSec transform sets configured on the system.
  • The hmac command configures the Encapsulating Security Payload (ESP) integrity algorithm. The sha1-96 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IPSec transform sets configured on the system.
  • The mode tunnel command specifies that the entire packet is to be encapsulated by the IPSec header including the IP header. This is the default setting for IPSec transform sets configured on the system.

Creating and Configuring an IKEv2 Transform Set

The following example configures an IKEv2 transform set:

configure
   context <pgw_context_name>
      ikev2-ikesa
transform-set <ikev2_transform-set_name>
         encryption
aes-cbc-128
         group
2
         hmac
sha1-96
         lifetime <sec>
         prf
sha1
         end

Notes:

  • The encryption algorithm, aes-cbc-128, or Advanced Encryption Standard Cipher Block Chaining, is the default algorithm for IKEv2 transform sets configured on the system.
  • The group 2 command specifies the Diffie-Hellman algorithm as Group 2, indicating medium security. The Diffie-Hellman algorithm controls the strength of the crypto exponentials. This is the default setting for IKEv2 transform sets configured on the system.
  • The hmac command configures the Encapsulating Security Payload (ESP) integrity algorithm. The sha1-96 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IKEv2 transform sets configured on the system.
  • The lifetime command configures the time the security key is allowed to exist, in seconds.
  • The prf command configures the IKE Pseudo-random Function which produces a string of bits that cannot be distinguished from a random bit string without knowledge of the secret key. The sha1 keyword uses a 160-bit secret key to produce a 160-bit authenticator value. This is the default setting for IKEv2 transform sets configured on the system.

Creating and Configuring a Crypto Map

The following example configures an IKEv2 crypto map:

configure
   context <pgw_context_name>
      crypto
map <crypto_map_name> ikev2-ipv4
         match
address <acl_name>
         peer <ipv4_address>
         authentication
local pre-shared-key key <text>
         authentication
remote pre-shared-key key <text>
         payload
<name>
match ipv4
            lifetime <seconds>
            ipsec
transform-set list <name1>
. . . <name4>
            exit
         exit
      interface <s5_intf_name>
         ip
address <ipv4_address>
         crypto
map <crypto_map_name>
         exit
      exit
   port
ethernet <slot_number/port_number>
      no
shutdown
      bind
interface <s5_intf_name> <pgw_context_name>
      end

Notes:

  • The type of crypto map used in this example is IKEv2/IPv4 for IPv4 addressing. An IKEv2/IPv6 crypto map can also be used for IPv6 addressing.
  • The ipsec transform-set list command specifies up to four IPSec transform sets.