Archive | January 2016

Increase managed FortiAP’s with Fortigate 100D (and other models) Firewalls

With each built-in wireless controller in the Fortigate firewalls there is a max number of supported AP’s.  By default this number is halved when you use tunnel mode (ie. all controllers tunnel back to an interface/captive portal on the Fortigate 100d’s).   If you are using a central Fortigate/Fortigate HA Cluster as your controller it can be quite easy to go over 32 supported AP’s.  By default the 32 number is a hard limit(on the 100D, larger devices have larger limits), whether you are using tunnel mode or not.  In order to disable tunnel mode on your AP, thereby doubling your managed AP’s this is the process:

From the Fortigate’s CLI edit the controller config, edit your specific AP by Serial Number
2016-01-07_9-48-18

Type: “set wtp-mode remote” and type end.  Now you should see the number of supported devices as increased:

2016-01-07_9-50-16

Fortinet Guide: http://docs-legacy.fortinet.com/fos50hlp/50/index.html#page/FortiOS%205.0%20Help/wifi-ethernet_bridge.058.7.html

Veeam: Failed to prepare (Hyper-V) guests for volume snapshot

After a few big months (we recently moved back to the U.S. for a couple of years) – I thought I better get back to some blogging!  Here is a recent issue I’ve ran into for a customer while setting up a new Veeam environment to backup a Hyper-V cluster:

Host and guest O/S both Server 2012 R2.  When backing up a specific VM I received the following errors:

Unable to create snapshot (Microsoft CSV Shadow Copy Provider) (mode: Crash consistent). Details: Failed to prepare guests for volume snapshot.
Unable to create snapshot (Microsoft CSV Shadow Copy Provider) (mode: Crash consistent). Details: Failed to prepare guests for volume snapshot.
Processing servername Error: Failed to prepare guests for volume snapshot.

2016-01-04_10-28-20

I checked the VSS Writers, etc. and confirmed they were all good.  Checked to ensure there was snapshot space available.  There was no need to upgrade the Integration services as suggested.  After doing a little further digging, I noticed that the Hyper-V integration services components were set to disabled in the Guest O/S.  This was in spite of the properties for the VM stating otherwise:

2016-01-04_10-26-38
2016-01-04_10-27-59

The fix was to set all of the services to manual (triggered start) & reboot the VM.

2016-01-04_10-27-34

Once this was completed backup ran successfully!