Hi, First of all, we are using Fortimanager in Advanced ADOM mode. We
recently went through a lengthy process to upgrade both Fortimanager and
all registered Fortigates from v5.4 to v5.6. The final step once all of
the Fortigates had been upgraded wa...
Hi, We have Fortimanager VM v5.6.7 and have been adding Fortigate
devices up to our device license limit. Having to add two more
production Fortigates, we reviewed our devices and have Deleted several
test Fortigates from FMG. The total number of dev...
Hi, In FMG v5.6.7, we are using ADOMs in Advanced ADOM Mode. We have
configured three separate ADOMs, each of which have several Fortigate
devices added. In one of the ADOMs, I deleted a couple of Fortigate
devices and then checked the Devices-VDOMs ...
Hi, We're using FMG v5.6.7. I was in the middle of updating some Objects
in the Global ADOM and I Assigned All Objects to an ADOM called
NS-Custom. I then went to the NS-Custom ADOM to apply Policy updates to
the Fortigates and every single one fails...
Hi, We have an extensive environment consisting of multiple FG-60E,
FG-200D and FG-200E firewalls, all managed with Fortimanager. The FMG is
running v5.6.7 and we are in the process of upgrading the FGs from
v5.4.x to v5.6.7. We just introduced an FG...
Hi, Yes. There was a bug affecting Webfilters in the v5.6.7 FMG release
we were upgrading to. We then upgraded FMG to the latest at that time
(v5.6.8) and the bug was fixed. LarW63
Thank you for your time and direction. After checking both diag dvm
device list and looking into the root - unregistered devices I was able
to find which devices were consuming the "extra" licenses. Addressed
these and then were able to add the two n...
Ok, thank you all for your input. Generally, our implementation is
fairly straight forward with quite a few Site-Site VPNs and lengthy
policy-sets all running over a couple of VDOMs. The only thing really
out of the ordinary is that we are running a ...
Hi, Discovered a work-around with FMG v5.4.5. First, in FMG v5.4.3 I was
in the habit of using Interface-Pair view with Custom Column Settings
prior to the upgrade. Once upgraded to v5.4.5, this problem surfaced.
With v5.4.5, Interface-Pair View isn'...
The main reason for moving from one ADOM to another is a totally revised
policy set. So, I hadn't actually imported the original/old policy into
the new ADOM. Just tried pushing the revised policy set, which generated
the error. Upon your suggestions...
