Field
Definition
Gateway
This field is optional and does not need to be configured if the appliance and all of the
managed devices are on the same subnet.
If the appliance and any managed devices are on different subnets, enter the IP
address of the routing device. A gateway is the device that passes traffic from the local
subnet to devices on other subnets.
Routes are automatically created for each Isolation Subnet to the Isolation Gateway.
Routes traffic through eth1.
Isolation Scopes
Label
User specified name for the scope. Can be associated with a location, such as
Building-B, or a function within the organization, such as Accounting.
Note:
When setting up Layer 3 Network Configurations in the Configuration
Wizard, labels of DHCP Scopes should not begin with any of these strings:
"REG_", "REM_", "AUTH_", "DE_", "ISOL_", "VPN_", or "HUB_". These
are reserved.
Gateway
Default gateway for the client lease pool you are adding. Do not use the default
gateway for eth1.
Mask
Subnet mask for the default gateway.
Domain
Identifies the domain for this range of IP addresses. To help identify the VLAN,
incorporate part of the name in the domain. For example, for the isolation VLAN use
megatech-iso.com or for the registration VLAN use megatech-reg.com.
Note:
Note: If you use agents for OS X, iOS, and some Linux systems,
using a
.local
suffix in Domain fields may cause communications issues.
Example:
Incorrect dns suffix for reg:
tech-reg.megatech.local
Correct dns suffix for reg:
tech.megatech-reg.edu
Lease Pools
Starting and ending IP addresses that delineate the range of IP addresses available on
this route. You can use multiple ranges.
Lease Time
Lease Time in
seconds
Time in seconds that an IP address is available for use. When this time has elapsed
the user is served a new IP address. The recommended lease time for Isolation,
Registration, Remediation, Dead End, VPN and Authentication is 60 seconds.
Isolation IP Subnets
Subnets
IP Subnets are optional and used in situations like Client control via FlexCLI or roles
only Aruba/Xirrus integration.
List of IP Addresses and corresponding Subnet Masks indicating IP addresses for
which FortiNac will serve DNS. Should only be used for hosts that are being isolated by
FortiNac.
Can be any address on any subnet, as long as the same address is added to the filters
as an isolation address when configuring the device.
Layer 3 Network - Configure Route Scopes
31
Содержание FortiNac BFN320
Страница 1: ...Appliance Installation Guide Version 8 3 Date 8 24 2018...
Страница 7: ...4...
Страница 11: ...Hardware Setup Note You will be required to change the Configuration Wizard password during the setup process 8...
Страница 19: ...Software Configuration Figure 7 Download Documentation Window 16...
Страница 20: ...Password Setup Figure 8 Change Passwords Figure 9 Configuration Wizard Password Setup Password Setup 17...
Страница 22: ...7 Close the window or tab 8 Click Next to continue Password Setup 19...
Страница 27: ...Layer 2 Network Configure VLANS Figure 11 Layer 2 Isolation Figure 12 Add Subnet 24...
Страница 35: ...Layer 3 Network Configure Route Scopes Figure 15 Layer 3 Network Configuration Isolation Scopes 32...
Страница 39: ...Layer 3 Network Configure Route Scopes Figure 18 Layer 3 Access Point Management 36...
Страница 40: ...Figure 19 Layer 3 Add Access Point Management Scopes Layer 3 Network Configure Route Scopes 37...
Страница 42: ...Figure 20 Layer 3 Routes Import Route Scopes Window Layer 3 Network Configure Route Scopes 39...
Страница 44: ...Figure 21 Additional Routes Window Figure 22 Add Route Window Layer 3 Network Additional Routes 41...
Страница 46: ...Figure 23 Results Window Results Layer 2 Layer3 Networks Or Control Manager 43...
Страница 49: ...Change Passwords After Configuration 46...