Create and Manage Hub-and-Spoke (Establishment All Peers) VPN
Create Hub-and-Spoke (Establishment All Peers) VPN
The hub-and-spoke (establishment all peers) is a route-based IPsec VPN topology where all peers (hub and spokes) establish tunnels with each other through the hub. The hub acts as the main control point. All spoke-to-spoke communication is routed through the hub.
Before You Begin
-
Read the IPSec VPN overview and view the field descriptions to understand your current data set. See IPsec VPN Overview.
-
Create addresses and address sets. See Create and Manage Addresses or Address Groups.
-
Create VPN profiles. See Create and Manage VPN Profiles
-
Define extranet devices. See Create Extranet Devices.
To create a hub-and-spoke (establishment all peers) VPN:
General Settings
|
Field |
Action |
|---|---|
|
Name |
Enter a unique string of maximum 63 alphanumeric characters without spaces. The string can contain colons, periods, dashes, and underscores. |
|
Description |
Enter a description containing maximum 255 characters for the VPN. |
|
Routing Topology |
Select one of the following options:
|
|
VPN Profile |
Select a VPN profile based on the deployment scenario.
|
|
Authentication Method |
Select an authentication method that the device uses to authenticate the source of IKE messages.
|
|
Max Transmission Unit |
Select the maximum transmission unit (MTU) in bytes. MTU defines the maximum size of an IP packet, including the IPsec overhead. You can specify the MTU value for the tunnel endpoint. The valid range is 68—9192 bytes. The default value is 1500 bytes. |
|
Pre-shared Key |
Establish a VPN connection using pre-shared keys, which is essentially a password that is same for both parties. Pre-shared keys are applicable only if the authentication method is pre-shared based. Select the type of pre-shared key to use:
|
|
Network IP |
Enter the IPv4 or IPv6 address of the numbered tunnel interface. This is the subnet address from where the IP address is automatically assigned for tunnel interfaces. |
|
Number of Spoke Devices Per Tunnel Interface |
Select All or specify the number of spoke devices to share one tunnel interface on hub. |
Device Settings
Add devices as endpoints in the VPN. If the selected device is part of an MNHA pair, you can add the devices separately, choosing one or both as needed.
To add devices:
-
Click Add, and click one of the following: Hub Device, Spoke Device, or Extranet Spoke Device.
The Add Device page is displayed.
- Configure the device parameters as described in Table 2.
- Click OK.
|
Field |
Action |
|---|---|
|
Device |
Select a device. |
|
External Interface |
Select the outgoing interface for IKE security associations (SAs). This interface is associated with a zone that acts as its carrier, providing firewall security for it. |
|
Tunnel Zone |
Select the tunnel zone. Tunnle zones are logical areas of address space that can support dynamic IP (DIP) address pools for NAT applications to pre- and post-encapsulated IPsec traffic. Tunnel zones also provide flexibility in combining tunnel interfaces with VPN tunnels. |
|
Metric |
Specify the cost for an access route for the next hop. |
|
Routing instance |
Select the required routing instance. |
|
Certificate |
Select a certificate to authenticate the VPN initiator and recipient. This is applicable in one of the following scenarios:
|
|
Trusted CA/Group |
Select the CA profile to associate it with the local certificate. This is applicable in one of the following scenarios:
|
|
Export |
Select the type of routes to export.
If you select OSPF or RIP export, the OSPF or RIP routes outside the VPN network is imported into a VPN network through OSPF or RIP Dynamic routing protocols. |
|
OSPF Area |
Select an OSPF area ID within the range 0—4,294,967,295 where the tunnel interfaces of this VPN must be configured. The OSPF area ID is applicable when the Routing Topology is OSPF-Dynamic Routing. |
|
Max Retransmission Time |
Select the retransmission timer to limit the number of times the RIP demand circuit re-sends update messages to an unresponsive peer. If the configured retransmission threshold is reached, routes from the next-hop router are marked as unreachable and the hold-down timer starts. You must configure a pair of RIP demand circuits for this timer to take effect. The retransmission range is from 5—180 seconds. The default value is 50 seconds. This option is applicable only when Routing Topology is RIP-Dynamic Routing. |
|
AS Number |
Select a unique number to assign to the autonomous system (AS). The AS number identifies an autonomous system and enables the system to exchange exterior routing information with other neighboring autonomous systems. The valid range is from 0—4294967295. The AS number is applicable only when Routing Topology is e-BGP Dynamic Routing. |
|
Protected Networks |
Configure the addresses or interface type for the selected device to protect one area of the network from the other. When a dynamic routing protocol is selected, the interface option is displayed. You can also create addresses by clicking Add New Address. |
VPN Profile Settings
Click View VPN Profile Settings to view or edit VPN profiles. If the VPN profile is default, you can edit the configurations. If the profile is shared, you can only view the configurations.
|
Field |
Action |
|---|---|
| IKE Settings | |
|
IKE Version |
Select the required IKE version, either V1 or V2, that is used to negotiate dynamic security associations (SAs) for IPsec. By default, IKE V2 is used. |
|
Mode |
Mode is applicable when the IKE Version is V1. Select an IKE policy mode.
|
|
Encryption Algorithm |
Select the appropriate encryption mechanism. |
|
Authentication Algorithm |
Select an algorithm that the device must use to verify the authenticity and integrity of a packet. |
|
Deffie Hellman group |
Select a Diffie-Hellman (DH) group to determine the strength of the key used in the key exchange process. |
|
Lifetime Seconds |
Select the lifetime for an IKE security association (SA). The valid range is from 180—86400 seconds. |
|
Dead Peer Detection |
Enable this option to permit the two gateways to determine if the peer gateway is up and responding to the Dead Peer Detection (DPD) messages that are negotiated during IPsec establishment. |
|
DPD Mode |
Select a DPD Mode.
|
|
DPD Interval |
Select a time period, in seconds, to send dead peer detection messages. The default interval is 10 seconds with a valid range of 2—60 seconds. |
|
DPD Threshold |
Select the failure DPD threshold value. This specifies the maximum number of times the DPD messages must be sent when there is no response from the peer. The default number of transmissions is 5 times with a valid range of 1—5. |
| Advance Settings | |
|
General IKE ID |
Enable this option to accept peer IKE ID. This option is disabled by default. If General IKE ID is enabled, the IKE ID option is disabled automatically. |
|
IKEv2 Re Authentication |
Select a reauthentication frequency. Reauthentication can be disabled by setting the reauthentication frequency to 0. The valid range is from 0—100. |
|
IKEv2 Re Fragmentation Support |
Enable this option to split a large IKEv2 message into a set of smaller ones so that there is no fragmentation at the IP level. |
|
IKEv2 Re-fragment Size |
Select the size of the packet at which messages are fragmented. By default, the size is 576 bytes for IPv4, and the valid range is from 570—1320. |
|
IKE ID |
Select one of the following options:
IKE ID is applicable only when General IKE ID is disabled. |
|
NAT-T |
Enable Network Address Translation-Traversal (NAT-T) if the dynamic endpoint is behind a NAT device. |
|
Keep Alive |
Select a time period, in seconds, to keep the connection alive. NAT Keepalives are required to maintain the NAT translation during the connection between the VPN peers. The valid range is from 1—300 seconds. |
| IPsec Settings | |
|
Protocol |
Select the required protocol to establish the VPN.
|
|
Encryption Algorithm |
Select the encryption method. This option is applicable if the Protocol is ESP. |
|
Authentication Algorithm |
Select an algorithm that the device must use to verify the authenticity and integrity of a packet. |
|
Perfect Forward Secrecy |
Select Perfect Forward Secrecy (PFS) as the method that the device uses to generate the encryption key. The PFS generates each new encryption key independently from the previous key. The higher numbered groups provide more security but require more processing time. |
|
Establish Tunnel |
Specify when to activate IKE:
|
| Advance Settings | |
|
VPN Monitor |
Enable this option to send Internet Control Message Protocol (ICMP) to determine if the VPN is up. |
|
Optimized |
Enable this option to optimize VPN monitoring and configure SRX Series Firewalls to send ICMP echo requests, also called pings, only when there is outgoing traffic and no incoming traffic from the configured peer through the VPN tunnel. If there is incoming traffic through the VPN tunnel, the SRX Series Firewalls considers the tunnel to be active and do not send pings to the peer. |
|
Anti Replay |
Enable this option for the IPsec mechanism to protect against a VPN attack that uses a sequence of numbers that are built into the IPsec packet. IPsec does not accept a packet for which it has already seen the same sequence number. It checks the sequence numbers and enforces the check rather than just ignoring the sequence numbers. Disable this option if there is an error with the IPsec mechanism that results in out-of-order packets, preventing proper functionality. By default, Anti-Replay detection is enabled. |
|
Install interval |
Select the maximum number of seconds to allow for the installation of a re-keyed outbound security association (SA) on the device. |
|
Idle Time |
Select the appropriate idle time interval, after which sessions and their corresponding translations will time out if no traffic is received. |
|
DF Bit |
Select how to process the Don’t Fragment (DF) bit in IP messages.
|
|
Copy Outer DSCP |
Enable this option to copy the Differentiated Services Code Point (DSCP) field from the outer IP header encrypted packet to the inner IP header plaintext message during decryption. The benefit in enabling this feature is that, after IPsec decryption, cleartext packets adhere to the inner class-of-service (CoS) rules. |
|
Lifetime Seconds |
Select the lifetime, in seconds, for an IKE security association (SA). The valid range is 180—86400 seconds. |
|
Lifetime kilobytes |
Select the lifetime, in kilobytes, for an IPsec security association (SA). The valid range is 64—4294967294 kilobytes. |
Manage Hub-and-Spoke (Establishment All Peers) VPN
-
Edit—Select the IPsec VPN, and then click the pencil icon (
). After editing IPsec VPN, you must deploy them to apply the configurations on the devices.
You cannot edit the IPsec VPN that is marked to be deleted.
-
Delete—Select the IPsec VPN, and then click the trash can icon (
). Follow the on-screen instructions. The IPsec VPN is not deleted from the associated devices at this moment. You must redeploy the IPsec VPN to delete it from the devices.
To revert the IPsec VPN marked for deletion, hover over the flag in the Status column, and select Undo Delete. The IPsec VPN status is reverted to the previous status.
-
Delete Hub-and-Spoke IPsec VPNs from Specific Devices—Select the IPsec VPN, and then click the pencil icon (
). Select the spokes to delete in the Devices section, and click the trash can icon (
). Follow the on-screen instructions. Deploy the VPN to delete the VPN from the spokes. You can revert the changes by editing the IPSec VPN and adding the devices back.
In a hub-and-spoke IPsec VPN that has multiple spoke and extranet devices, you can delete the VPN from specific spokes by deleting the spokes and redeploying the VPNs. However, when you delete a spoke that is an extranet device, the device configuration is deleted only from the VPN hub because Juniper Security Director Cloud does not manage the device.
You must retain at least one spoke in the hub-and-spoke IPsec VPN without which you won't be able to save the edited VPN.