12.03.2015 Views

FortiGate Administration Guide - FirewallShop.com

FortiGate Administration Guide - FirewallShop.com

FortiGate Administration Guide - FirewallShop.com

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Using virtual domains<br />

Virtual domains<br />

Using virtual domains<br />

This section describes how to use virtual domains to operate your <strong>FortiGate</strong> unit<br />

as multiple virtual units, providing separate firewall and routing services to multiple<br />

networks.<br />

This section describes:<br />

• Virtual domains<br />

• Enabling VDOMs<br />

• Configuring VDOMs and global settings<br />

Virtual domains<br />

Virtual domains (VDOMs) enable a <strong>FortiGate</strong> unit to function as multiple<br />

independent units. A single <strong>FortiGate</strong> unit is then flexible enough to serve multiple<br />

departments of an organization, separate organizations or be the basis for a<br />

service provider’s managed security service.<br />

VDOMs provide separate security domains that allow separate zones, user<br />

authentication, firewall policies, routing, and VPN configurations. Using VDOMs<br />

can also simplify administration of <strong>com</strong>plex configurations because you do not<br />

have to manage as many routes or firewall policies at one time. See “VDOM<br />

configuration settings” on page 72.<br />

To configure and use VDOMs, you must enable virtual domain configuration. See<br />

“Enabling VDOMs” on page 74.<br />

When you create and configure a VDOM, you must assign interfaces or VLAN<br />

subinterfaces to it. Optionally, you can assign an administrator account that can<br />

log in only to that VDOM. If the VDOM is created to serve an organization, this<br />

enables the organization to manage its configuration independently.The operating<br />

mode, NAT/Route or Transparent, is independently selectable for each VDOM.<br />

When a packet enters a VDOM, it is confined to that VDOM. In a VDOM, you can<br />

create firewall policies for connections between VLAN subinterfaces or zones in<br />

the VDOM. Packets do not cross the virtual domain border internally. To travel<br />

between VDOMs a packet must pass through a firewall on a physical interface.<br />

The packet then arrives at another VDOM on a different interface where it must<br />

pass through another firewall before entering. Both VDOMs are on the same<br />

<strong>FortiGate</strong> unit.The one exception is if you configure inter-VDOM routing using CLI<br />

<strong>com</strong>mands.<br />

The remainder of <strong>FortiGate</strong> functionality is global. It applies to all VDOMs. This<br />

means that there is one intrusion prevention configuration, one antivirus<br />

configuration, one web filter configuration, and so on. As well, VDOMs share<br />

firmware versions, antivirus and attack databases. For a <strong>com</strong>plete list of shared<br />

configuration settings, see “Global configuration settings” on page 73.<br />

<strong>FortiGate</strong> Version 3.0 MR5 <strong>Administration</strong> <strong>Guide</strong><br />

01-30005-0203-20070830 71

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!