You are hoping to deploy a wicket in Dispel's partner environment. There are a few steps to this process.

Your PAM submits a request for a wicket to be built for your deployment.

Once your wicket is ready you will be onboarded to our partner environment where you will be able to download your wicket directly from the dashboard by navigating to Facilities -> <your facility> -> Wickets -> <your wicket>

From here you will be able to download your ISO. You will also find the password, and SHA 256 checksum which you will need later.

Prepare your firewall:

The wicket will need outbound only UDP access to 172.172.184.51 over ports 500 & 4500 (application IPSec) in order to form it's remote access tunnel.

To deploy your wicket first download the ISO and verify it downloaded properly by comparing the SHA256 checksum. This can be done by following the steps in this guide:

Once verified, you can deploy your wicket by following the install guide below:

The wicket deploys with a single configured interface set up for DHCP by default, but custom settings and additional interfaces can be set by running wicket interface configure on the wicket's CLI.

If you prefer to deploy the wicket on hardware the process will be the same with the addition of loading the ISO onto a bootable media for installation and booting your hardware off of the bootable media.

If you have connection issues the Debugging a Wicket’s Connection to the Dispel Network section of this guide can be helpful.

Now that your wicket is installed you should be able to see the red X turn to a green checkmark within 5 minutes to indicate that the system recognizes that your wicket is connected!

Once your wicket is connected you can being onboarding subnets, devices, and testing end-to-end connectivity!

To onboard a subnet to a wicket you will need to select the interface associated with that subnet (how the wicket should route to it), and hit add subnet under the wicket page in the dashboard: