Manual Chapter :
Creating an IKE Peer for dynamic template
Applies To:
Show Versions
BIG-IP APM
- 17.5.0, 17.1.2, 17.1.1, 17.1.0
BIG-IP Link Controller
- 17.5.0, 17.1.2, 17.1.1, 17.1.0
BIG-IP LTM
- 17.5.0, 17.1.2, 17.1.1, 17.1.0
BIG-IP AFM
- 17.5.0, 17.1.2, 17.1.1, 17.1.0
BIG-IP ASM
- 17.5.0, 17.1.2, 17.1.1, 17.1.0
Creating an IKE Peer for dynamic template
Use this task to create an IKE peer for dynamic template.
You must also configure the device at the other end of the IPsec tunnel.
- On the Main tab, click.
- Click theCreatebutton.The New IKE Peer screen opens.
- In theNamefield, type a unique name for the IKE peer.
- In theDescriptionfield, type a brief description of the IKE peer.
- In theRemote Addressfield, type the IP address of the device that is remote to the system you are configuring.This address must match the value of theTunnel Remote Addresssetting in the relevant IPsec policy.
- For theStatesetting, retain the default value,Enabled.
- In theVersionfield, selectVersion 2.
- For the Dynamic Endpoint Properties, in theDynamic Addressfield, type the peer dynamic address. For example, 192.0.2.1. This address must match theTunnel Remote Addresssetting in the IPsec policy.
- In theAddress Listfield, enter list of IPv4 and/or IPv6 subnets from which IP addresses are allocated for configuration payloads in IKE_AUTH. For example, 192.168.44.0/24 2001:db8::fffc:0:4a5/120.Devices in site A are allocated with IP addresses from the IP addresses given in address list.
- In theDHCP address IPv4field, type the DHCP address to return for INTERNAL_IP4_DHCP configuration payload requests in IKE_AUTH.
- In theDHCP address IPv6field, type the DHCP address to return for INTERNAL_IP6_DHCP configuration payload requests in IKE_AUTH.
- In theDNS address IPv4field, type the DNS address to return for INTERNAL_IP4_DNS configuration payload requests in IKE_AUTH.
- In theDNS address IPv6field, type the DNS address to return for INTERNAL_IP6_DNS configuration payload requests in IKE_AUTH.
- In theRemote Portfield, type the port number alternative to 500 for the remote peer's port.
- In theLocal Portfield, type the port number alternative to 500 for the local IKE listener port.
- For the Common Settings area, retain all default values.
- In thePresented ID Valuefield, enter the IP address to present as the BIG-IP system identity.
- In theVerified ID Valuefield, enter the IP address for the remote peer that the BIG-IP system should expect to receive and verify. For example, 192.0.2.1.
- ClickFinished.The screen refreshes and displays the new IKE peer in the list.
You now have an IKE peer defined for establishing
a secure channel.