The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Revision history details are not provided for features introduced before release 21.24.
Revision Details
Release
First introduced
Pre 21.24
Feature Description
IPSec is a suite of protocols that interact with one another to provide secure private communications across IP networks.
These protocols allow the system to establish and maintain secure tunnels with peer security gateways. IPSec provides confidentiality,
data integrity, access control, and data source authentication to IP datagrams.
In CUPS, the functionality is available with IPSec in Tunnel mode both on Control Plane (CP) and User Plane (UP) nodes. The
IPSec crypto-maps are associated under the appropriate interface on respective nodes. The IPSec tunnel is created between
each CP or UP pair explicitly. There is no change that is required on Sx service configuration.
IPSec Tunnel Mode encapsulates the entire IP packet to provide a virtual secure hop between two gateways. It forms more familiar
VPN kind of functionality, where entire IP packets are encapsulated inside another and delivered to the destination. It encapsulates
the full IP header as well as the payload.
When Sx over IPSec is enabled on UP node running VPP, then following parameter must be used under “UPP Param” for Sx over
IPSec feature to work.
VPP_DPDK_DATA_SIZE=5120
The UPP Param is stored in staros_para.cfg file on a CD-ROM and this configuration is read and applied to VPP by UP during
its boot.
Note
This parameter introduces a memory overhead of about 800 MB. The user must consider this condition before using the feature.
If the UP has less RAM, then VM must be allocated with extra 1 GB of RAM memory for the feature to work properly.
For more information on IPSec support, refer StarOS IPSec Reference.
IKEv2 Keep-Alive Messages (Dead Peer Detection)
IPSec for Sx interface 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.
IPSec DPD is an optional configuration. If its disabled, the IPSec node
doesn't initiate DPD request. However, the node always responds to
DPD availability messages initiated by peer node regardless of its
DPD configuration.
The following method/formula can be used to calculate the keep-alive
interval value when Sx over IPSec feature is configured:
For IKESA Rekey, the lifetime
interval CLI must be configured
under ikev2-ikesa transform-set
transform_set. You must
also configure ikev2-ikesa rekey under
crypto map configuration.
Following is a configuration example:
The following is an example configuration of static route for interface.
ip route 209.165.200.224/27 Vlan1111 209.165.200.225
ip route 209.165.200.224/27 Vlan1111 209.165.200.226
ip route 209.165.200.224/27 Vlan1111 209.165.200.227
ip route 209.165.200.224/27 Vlan1111 209.165.200.228
ip route 209.165.200.224/27 Vlan1111 209.165.200.229
ip route 209.165.200.224/27 Vlan1111 209.165.200.230
ip route 209.165.200.224/27 Vlan1111 209.165.200.231
ip route 209.165.200.224/27 Vlan1111 209.165.200.232
ip route 209.165.200.224/27 Vlan1111 209.165.200.233
ip route 209.165.200.224/27 Vlan1111 209.165.200.234
Static Routes for Singlehop BFD
The following is an example configuration of static route for singlehop BFD.
ip route static bfd Vlan1111 209.165.200.225
ip route static bfd Vlan1111 209.165.200.226
ip route static bfd Vlan1111 209.165.200.227
ip route static bfd Vlan1111 209.165.200.228
ip route static bfd Vlan1111 209.165.200.229
ip route static bfd Vlan1111 209.165.200.230
ip route static bfd Vlan1111 209.165.200.231
ip route static bfd Vlan1111 209.165.200.232
ip route static bfd Vlan1111 209.165.200.233
ip route static bfd Vlan1111 209.165.200.234
Interface for Singlehop BFD
The following is an example configuration of interface for singlehop BFD.
interface Vlan1111
no shutdown
bandwidth 10000000
bfd interval 999 min_rx 999 multiplier 3
no bfd echo
ip address 209.165.200.224/27
ipv6 address 1111:222::1/112
BGP Configuration
The following is an example of BGP configuration with recommended timers.
This section contains sample CLI command output of show commands available for the Sx over IPSec feature in both CP and UP.
show crypto ikev2-ikesa security-associations summary
I - Initiator
R - Responder
Mgr Lifetime
ID VPN Local IPSec GW:Port Remote IPSec GW:Port State /Remaining
=== === ===================== ===================== ================ ===========
54 2 192.168.170.55 :500 192.168.196.55 :500 AUTH_COMPLETE(I) 86400/16448
1 IKEv2 Security Association found in this context.