SecGW Service Creation

This chapter describes the requirements and procedures for enabling the WSG (Wireless Security Gateway) service within StarOS. Enabling this service creates the SecGW.

This chapter discusses the following topics:

Prerequisites

This section describes the requirements that must be met prior to configuring the SecGW.

VPC-VSM Installation

VPC-VSM must be running in a virtual machine on a VSM CPU within the ASR 9000 chassis. This guide does not describe the installation process. Refer to other ASR 9000 documentation for detailed installation instructions.

The StarOS command line interface (CLI) for each VPC-VSM instance should be accessible via a remote access management port that is defined during the installation process. Refer to the VPC-VSM System Administration Guide for additional information on setting primary and secondary IP addresses for StarOS management ports. Alternatively, the StarOS CLI can be accessed via a hypervisor vConsole port.

For intrachassis and interchassis IPSec High Availability (HA) deployments, VPC-VSM must be installed on VSMs in the ASR 9000 chassis. StarOS Interchassis Session Recovery (ICSR) must also be enabled. Refer to the VPC-VSM System Administration Guide for ICSR installation and configuration information. For additional configuration requirements, see the High Availability for RRI section in the Reverse Route Injection chapter of this guide.

Refer to ASR 9000 documentation for additional information on HA active-standby configuration.

Network Interfaces

You will need to know the addressing information for all external interfaces to StarOS. The list of addresses is included but not limited to:
  • WSG service (endpoints, access groups)
  • VLANs
  • SNMP
  • DHCP

SecGW Configuration Sequence

The configuration sequence for enabling an SecGW is as follows:

For additional information, see the sample configurations provided in this guide.

IMPORTANT:

SecGW (WSG service) must be separately enabled and configured on each VPC-VSM instance. There are four CPUs on the VSM; each CPU runs a separate instance of VPC-VSM.

Crypto Templates

The StarOS CLI Crypto Template Configuration Mode is used to configure an IKEv2 IPSec policy. It includes most of the IPSec parameters and IKEv2 dynamic parameters for cryptographic and authentication algorithms. A security gateway service will not function without a configured crypto template. Only one crypto template can be configured per service.

A crypto template requires the configuration of the following parameters:
  • allow-cert-enc cert-hash-url – Enables support for certificate enclosure type other than default.
  • allow-custom-fqdn-idr – Allows non-standard FQDN (Fully Qualified Domain Name) strings in the IDr (Identification - Responder) payload of IKE_AUTH messages received from the UE with the payload type as FQDN.
  • authentication – Configures the gateway and subscriber authentication methods to be used by this crypto template.
  • blacklist – Enables use of a blacklist file
  • ca-certificate list – Binds an X.509 Certificate Authority (CA) root certificate to a crypto template.
  • ca-crl list – Binds one or more Certificate Authority-Certificate Revocation Lists (CA-CRLs) to this crypto template.
  • certificate – Binds a single X.509 trusted certificate to a crypto template.
  • control-dont-fragment – Controls the Don't Fragment (DF) bit in the outer IP header of the IPSec tunnel data packet.
  • dns-handling – Adds a custom option to define the ways a DNS address is returned based on proscribed circumstances described below.
  • dos cookie-challenge notify-payload – Configures the cookie challenge parameters for IKEv2 INFO Exchange notify payloads for the given crypto template.
  • identity local – Configures the identity of the local IPSec Client (IKE ID).
  • ikev2-ikesa – Configures parameters for the IKEv2 IKE Security Associations within this crypto template.
  • keepalive – Configures keepalive or dead peer detection for security associations used within this crypto template.
  • max-childsa – Defines a soft limit for the number of child Security Associations (SAs) per IKEv2 policy.
  • nai – Configures the Network Access Identifier (NAI) parameters to be used for the crypto template IDr (recipient's identity).
  • natt – Configures Network Address Translation - Traversal (NAT-T) for all security associations associated with this crypto template. This feature is disabled by default.
  • ocsp – Enables Online Certificate Store Protocol (OCSP) requests from the crypto map/template.
  • payload – Creates a new, or specifies an existing, crypto template payload and enters the Crypto Template Payload Configuration Mode.
  • peer network – Configures a list of allowed peer addresses on this crypto template.
  • remote-secret-list – Configures Remote Secret List.
  • whitelist – Enables use of a whitelist file.

You must create a crypto template before creating the WSG service that enables the SecGW.

IMPORTANT:

Refer to the IPSec Reference for comprehensive information regarding the creation of crypto templates.

A sample crypto template is shown below. It represents the output of the show crypto template tag template_name command.

Map Name: cryptotmplt01
=========================================
 
  Map
Status: Complete
 
  Crypto
Map Type: IPSEC IKEv2 Template
 
  IKE
SA Transform 1/1
 
    Transform
Set: ikesa-cryptotmplt01
      Encryption
Cipher: aes-chc-128
      Pseudo
Random Function: sha1
      Hashed
Message Authentication Code: sha1-96
      Diffie-Hellman
Group: 2
  IKE
SA Rekey: Disabled
  Blacklist/Whitelist : None
 
  OCSP
Status:        : Disabled
  OCSP
Nounce Status  : Enabled
 
  NAI: 99.99.99.30
 
  Remote-secret-list: <not
configured>
 
  Authentication
Local:
         Phase
1 - Pre-Shared Key (Size = 3)
 
 
  Self-certificate
Validation: Disabled
 
 
  IPSec
SA Payload 1/1 (Generic)
    Name : cryptotmplt01-sa0
    Payload
Local
      Protocol
255 Port 0-0 Address Range 67.67.0.1-67.67.0.1
    Payload
Remote
      Protocol
255 Port 0-0 Address Range 45.45.0.1-45.45.0.1
    IPSec
SA Transform 1/1
      Transform
Set: tselsa-cryptotmplt01
        Protocol: esp
        Encryption
Cipher: aes-cbc-128
        Hashed
Message Authentication Code: sha1-96
        Diffie-Hellman
Group: none
    IPSec
SA Rekey: Enabled
 
  Dead
Peer Detection: Disabled
 
 
  Maximum
CHILD_SA: 2 Overload Action: Ignore
 
  DOS
Cookie Challenge: Disabled
  Dont
Fragment: Copy bit from inner header
 
  Local
Gateway: Not Set
  Remote
Gateway: Not Set

Access Control Lists

IP access lists, commonly known as access control lists (ACLs), control the flow of packets into and out of the service. They are configured on a per-context basis and consist of “rules” (ACL rules) or filters that control the action taken on packets that match the filter criteria.

Separate ACLs may be created for IPv4 and IPv6 access routes.

WSG Service uses ACLs to specify traffic selectors for site-to-site tunnels. The wsg-service supports multiple access-lists.

You separately define ACLs outside of the wsg-service, at the context level. For information on creating and configuring ACLs, see the following:
  • Access Control Lists chapter in the VPC-VSM System Administration Guide
  • ACL Configuration Mode Commands chapter of the Command Line Interface Reference.

WSG Service Configuration

Configuring WSG Service enables SecGW functionality. The general configuration sequence includes:

IMPORTANT:

You must be logged into the StarOS CLI of a VPC-VSM instance to execute the commands described below.

IMPORTANT:

For complete information on CLI commands described below, see the Command Line Interface Reference.

WSG Service

This procedure enables WSG service and moves to WSG Configuration mode. The Wireless Security Gateway Configuration Mode is used to define the operating parameters for IPSec-based access control and handling of Encapsulating Security Payload (ESP) packets. Up to 25 WSG services can be configured per StarOS instance.

Execute the following command sequence to move to the Wireless Security Gateway Configuration Mode:
config
  context context_name
    wsg-service service_name

For additional information, see the WSG-Service Configuration Mode Commands chapter of the Command Line Interface Reference.

Bind Address and Crypto Template

In the WSG Configuration mode, the following command sequence binds the WSG service to the specified IPv4 or IPv6 address and crypto template.

bind address ip_address crypto-template template_name

The ip_address may be in IPv4 dotted-decimal or IPv6 colon-separated hexadecimal notation.

The template_name specifies an existing crypto template as an alphanumeric string of 0 through 127 characters.

Deployment Mode

A given instance of the WSG service can either support Remote Access tunnels or Site-to-Site tunnels. In the WSG Configuration mode, the following command sequence specifies the desired deployment mode.

deployment-mode { remote-access | site-to-site }

IMPORTANT:

There is no default deployment mode. You must configure the deployment mode as either remote-access or site-to-site before binding the service. Failure to specify a deployment mode will generate an error message when attempting to bind the address.

Access List

A WSG service that supports site-to-site tunnels should bind to an access list that specifies a single IP address for the destination IP; the subnet should be “32” for IPv4 and “128” for IPv6.

For the site-to-site scenario, the destination can be a subnet.

In the WSG Configuration mode, the following command sequence specifies the desired IPv4 access groups or address pools:
ip { access-group acl_list_name | address ( alloc-method { dhcp-proxy | local } | pool
name pool_name
In the WSG Configuration mode, the following command sequence specifies the desired IPv6 access groups or prefix pools:
ipv6 { access-group acl_list_name | address prefix-pool pool_name

IMPORTANT:

Remote Access (RA) tunnels require address pools that can be specified under the service.

The dhcp command in the WSG service specifies the DHCPv4 context and service name to be used when the IP address allocation method is set to dhcp-proxy. The specified DHCPv4 service is designated via the ip address alloc-method dhcp-proxy command. See

Duplicate Session Detection

The duplicate-session-detection command enables or disables allowing only one IKE-SA per remote IKE-ID. A new request will overwrite the existing tunnel. For a complete description of this feature, refer to the IPSec Reference.

Peer List

The peer-list command configures an SecGW to initiate an IKEv2 session setup request when the peer does not initiate a setup request within a specified time interval. For a complete description of this feature, refer to the IPSec Reference.

Pre-fragment MTU

You can specify the Maximum Transmission Unit (MTU) size (576–2048 bytes, default = 1400) which when exceeded initiates pre-tunnel (before encryption) fragmentation of clear packets within this WSG service.

In the WSG Configuration mode, the following command specifies the pre-fragment MTU:
pre_fragment
mtu size

Pre-Tunnel-Fragmentation improves packet processing performance as compared to post-tunnel-fragmentation.

If a clear IPv4 packet is longer than the predefined MTU size, it will be fragmented before the packet is encrypted and transmitted to the Internet.

If a clear IPv6 packet is longer than the predefined MTU size, it is dropped and an ICMP packet with the maximum length is sent back to the source. The source will then fragment the IPv6 packet and retransmit.

Responder Mode Duration

Use this command to specify the interval during which the WSG service (SecGW) will wait or a response from an IKE peer before switching to initiator mode (default is 10 seconds). This command is only available when a peer-list has been configured for the WSG service. See the IPSec Reference for additional information on configuring an SecGW as an IKE initiator.

Characteristics and Limitations

The following factors characterize WSG service configuration:
  • A WSG service configuration has precedence over the equivalent configuration in subscriber mode or the template payload.
  • Any changes made to a WSG service require that the service be restarted to apply any changed parameters. You restart the service by unbinding and binding the IP address to the service context.
  • Up to 16 named IPv4 pools can be configured. The list is sorted, and the addresses are allocated from the first pool in the list with available addresses.
  • Multiple IPv6 pools can be configured.
  • Multiple IPv4 and IPv6 ACLs can be configured.
  • IPv4 pools are only used for IPv4 calls; IPv6 pools are only used for IPv6 calls.

Lookup Priority

The Wireless Security Gateway Lookup Priority List Configuration Mode is used to set the priority (1–6) of subnet combinations for site-to-site tunnels.

The following command sequence sets the lookup priority:
config
   wsg-lookup
      priority priority_level source-netmask subnet_size destination netmask subnet_size 

For the packet lookup to work optimally, the top bits in the negotiated TSi for all the tunnels should be unique. The top number of bits that must be unique is equal to the lowest “destination-netmask” configured under all lookup priorities.

For example, if the lowest destination-netmask configured under any priority is 16:
priority 1 source-netmask
20 destination-netmask 18
priority 2 source-netmask
22 destination-netmask 16

A valid set of traffic selectors for the configured set of lookup priorities would be:

IPSec Tunnel 1: 10.11.1.0(tsi) - 20.20.1.0(tsr)

IPSec Tunnel 2: 10.10.2.0(tsi) - 20.20.2.0(tsr)

An invalid set of traffic selectors would be:

IPSec Tunnel 1: 10.10.1.0(tsi) - 20.20.1.0(tsr)

IPSec Tunnel 2: 10.10.2.0(tsi) - 20.20.2.0(tsr)

The above set is invalid because the top 16 bits for these two tunnels are not unique, both are 10.10.

The network should be designed to accommodate this requirement.

For additional information, see the WSG Lookup Priority List Configuration Mode chapter of the Command Line Interface Reference.

show Commands

The following Exec mode show commands display information associated with WSG service parameters and operating statistics. For detailed descriptions of these commands, see the Exec Mode show Commands chapter of the Command Line Interface Reference.

show wsg-lookup

This command displays the priority levels, as well as source and destination netmasks for all configured lookup priorities. The command syntax is:
show wsg-lookup
The following is a sample output for show wsg-lookup:
wsg-lookup
priority 1 source-netmask
32 destination-netmask 32
priority 2 source-netmask
24 destination-netmask 32
priority 3 source-netmask
32 destination-netmask 24
priority 4 source-netmask
24 destination-netmask 24

show wsg-service

This command displays information about all WSG services or a specified service. It also displays statistics for a specified WSG service or peer address.

The command syntax is:
show wsg-service ( all | name | srvc_name | statistics [ name srvc_name | peer-address ip_address ] [ | { grep grep_options | more } ] 
The following is a sample output for show wsg-service name wsg01:
Servicename: wsg01
  Context: wsg
  Bind: Done
  Max
Sessions : 8000
  IP
address: 10.10.10.30         UDP
Port: 500
  MTU: 1400
  Service
State: Started
  Crypto-template: cryptotmplt01
  deployment-mode : 1
The following is a sample output for show wsg-service statistics name wsg01:
WSG statistics for Service: wsg01


Session Stats:
  Current
sessions total:     0
  Simple-IP
IPv4 current:     0         Simple-IP
IPV6 current       0
  Data-Clients:               0
  Active
current:             0         Dormant current:             0


  Total
Simple-IP:            0
  Simple-IP-Fallback
attmpts: 0
      Successes:              0         Failures: 
                      0
  Simple-IP-Fallback
failure reasons:
      No
Mobile-IP RRQ Rx:    0         Not allowed                  0
     Tagged
Pool Address:     0         Misc.:                       0


  Simple-IP-attempts:         0
  Simple-IP
successes:        0


  Total
setup attempts:       0
  Total
setup successes:      0         Total
Attempts Failed:       0
  Disconnected
locally:       0


  Disconnect
remotely
      Before
connect:         0


Session Disconnect reason:
  Remote
disc. ipsec          0         Admin disconnect:            0
  Idle
timeout:               0         Absolute timeout:            0
  Long
duration timeout:      0         Session
setup timeout:       0
  No
resource:                0         Auth failure:                0
  Flow
add failure:           0         Invalid
dest-context:        0
  Source
address violation:   0         Duplicate Request:           0
  MAC
validation failure:     0         Addr
assign failure:         0
  Miscellaneous
reasons:      0


Data Stats:
  Total
Bytes Sent:           0         Total
Packets Sent:          0
  Total
Bytes Rcvd:           0         Total
Packets Rcvd:          0
  Total
Pkts Violations:      0


EAP Server Stats:
  Total
Received:             0
  Success
Received:           0         Challenge Received:          0
  Failures Received:          0         Discarded:                   0


  Total
Sent:                 0
  Initial
Requests:           0
  Requests
Forwarded:         0


EAP Mobile Stats
  Total
Received:             0
  Discarded:                  0

IPSec Configuration

SecGW functionality also requires configuration of StarOS IPSec features. See the Product Feature Mapping chapter in the IPSec Reference for a list of features supported on the SecGW.

The IPSec Reference provides detailed configuration information for individual features, including sample configurations.

Multiple SecGW Configurations per VSM

You must complete the configuration process described in this chapter on each VPC-VSM instance. There will be a total of four distinct SecGW configurations on each VSM (one per CPU).