VMware VCD VPN + Fortigate

Posted on December 29th, 2012 by Luke Sheldrick.
Categories: IT / Tech.
Tags: , , , , , , , , , , , , , .

29 12 2012

I’ve been testing a new platform at the day job for the last couple of days, as a user. The main part of this, is I do all the tests as if I was the end user (i.e. our Customer). The platform is based on VMware’s Virtual Cloud Director 5.1. I’m working with our product team to get the platform ready to hand over to our customers, and filling in the missing gaps, when it comes to requirements, documentation and any support needs.

One thing I was playing with today, was the inbuilt VPN capabilities. The documentation from VMware here, if I am honest, is quite incomplete. Even as a seasoned VMware user, some elements, are confusing. So the documentation for this element, were, how do I put it… minimal (read: missing all the needed info). I assume it’s because they’re assuming that you’ll be connecting it to another vShield Edge device, so their defaults, would just work.

I was working with my physical test lab to simulate a customer’s existing hosted solution, i.e. a rack of equipment in their data centre. The firewall I was using was an old Fortigate 200A, however this is running the latest v4 FortiOS, so would be the same for any firewall from Fortinet (running V4, V3 would be very very similar, if you still have that out there).

So, let’s assume the following:

 vOrg Network:
 VShield Edge IP:
 All devices NATed behind the Edge device.
 Legacy Network:
 Fortigate IP:
 All devices NATed behind the Fortigate.

Login to the VCD Portal, and go to your vOrg network preferences, right click on the network you want to configure for VPN access.


Go to the VPN tab, and If not already enabled, enable the VPN service. Then select new.


Change the “Establish VPN to” to External Network.


From the below, we’re going to fill out.

 Name: Your choice
 Description: Your choice
 Local Networks: LS-Network2 (matches the Here I chose the network that matched my requirements. (Yours will differ, and you'll need to make the amendments throughout.)
 Peer Networks:
 VPN Endpoint: The vShield Edge device you're going to terminate the VPN on.
 Local ID: Your choice - just needs to match what you configure the firewall with.
 Peer ID: Your choice - just needs to match what you configure the firewall with.
 Peer IP: This is going to be your other firewall. So for me it was
 Encryption Protocol: again, your preference. AES256 is a sane default.
 Shared Key: Your choice - just needs to match what you configure the firewall with.
 The rest: I left as default.

Now this left me asking some questions, i.e. what were the other settings going to be, such as Authentication method, DH Group, PFS, Key lifetime..etc None of this is listed in the documentation/user guide.

Anyway, to continue, you need to add a firewall rule in, to allow communication between the two environments. Something like the below, but again, adapt to your requirements.


Moving on to the Fortigate. This took a while to work out, as basically, I had to configure the VPN, wait for the edge device to try and bring up the VPN to see what it was proposing, in order to then set the Fortigate to match these (read: a complete PITA). However now that’s been done, hopefully this will help someone.

Go to your VPN Settings, add a new Phase I


So the settings here:

 Name: Your choice.
 Remote Gateway: Static IP.
 IP Address: Edge device IP. Mine
 Local Interface: Your internet facing interface.
 Mode: I chose Main, but this can be your preference.
 Pre-shared Key: What you made up in the earlier steps.
 Enable interface mode (makes life a lot easier for firewall rules.)
 IKE Version: 1
 Local IP: I chose main - your config may differ.
 Encryption: Whatever you chose earlier. AES256 for me.
 Authentication: SHA1 (This is one of the settings not documented anywhere)
 DH Group: 2 (This is one of the settings not documented anywhere)
 Keylife: 28800 (This is one of the settings not documented anywhere)
 DPD: Disabled - The edge device didn't seem to respond to these, so the Fortigate tore the tunnel down. (This is one of the settings not documented anywhere)

Phase II:


 Name: Your choice.
 Phase I: Select the one you configured above.
 Encryption: AES256 (unless chosen different above)
 Authentication: SHA1 (This is one of the settings not documented anywhere)
 DH Group: 2 (This is one of the settings not documented anywhere)
 Keylife: 1800 (This is one of the settings not documented anywhere)
 Source Address: (yours will need to changed to match your network)
 Destination Address: (match your vOrg Network)
 The Rest: Default.

Next: create the firewall rules. Incoming and outgoing for the VPN interface. I wont go into details here, as if you’re reading this I expect you’ll know how to add a policy in.

Static Route. You’ll need to create a static route for the VPN, in order to route traffic down the interface. Interestingly, you didn’t need to do this on the Edge config.

Go to the Router > Static > Create new. Something like the below, amended to your network.


Once this is done, the VPN should come up.


Serial Console & Android

Posted on December 9th, 2012 by Luke Sheldrick.
Categories: IT / Tech.
Tags: , , , , , , , , , , , .

9 12 2012

You’re in a datacenter, all you have with you is a bag of cables, a crash cart, and your mobile. A core switch has fallen over, and you need to quickly see what the console it outputting.

I was tinkering at home, where I was building a lab of some cisco and fortigate kit, and needed to quickly set a management IP. I had a rollover cable, and a usb to serial converter, and wondered if my Samsung Galaxy Note, and the ‘USB-to-go’ cable would allow me to connect to the serial port on the switches and firewalls. Using the inbuilt terminal didn’t work, and I couldn’t get minicom to play. However I did find an app in the Play Store, that had support for most of the usb converters.

A bit of fiddling, and bingo, it all worked.

Android Serial Console
I got this to work on my Galaxy Note, however this should work with anything that has USB Host Mode support. This would be really useful on a tablet.

The best bit here, is to do this, it’s really rather cheap. What I used:

USB-to-go connector – for converting the micro usb (Micro-B) to standard Female USB(Type A).
USB-to-Serial – cheap PL2303 based converter
Cisco Rollover cable – Every DC will have hundreds of these.

Slick USB 2 Serial Terminal – Android app that talks directly to the USB-to-Serial converter. (Ad supported or pay for version).


1 of 11