Dell 6.2 Configuring the Example Routed ESI Topology

761| External Ser vicesInterface DellPowerConnect W- Series ArubaOS 6.2 | User Guide
Figure 347: Example Route-ModeTopology
In the topology shown, the followingco nfigurationsare entered on the controller andForti net gateway:
ESI server configuration on controller
lTrustedI P address = 10.168.172.3 (syslog source)
lUntrustedI P address = 10.168.171.3
lMode = route
IP routing configuration on Fort inet gateway
lDefault gateway (core router)= 10 .168.172.1
lStatic route for wireless user subnet (10.168.173.0/24) t hroughthe controller (10.168.171 .2)
Configuring the Example Routed ESI Topology
This section describes how to implement the example routed ESI topology shown in . T hedescripti on includest he
relevantconfiguration—both the WebUI and the CLI configuration processes are described—requiredon the
controllerto integrate with a AVF server appliance.
The ESI configuration process will redirect all HTTP user traffic to the Fortinet serverfor examination, and any
infected userw illbe blacklisted.The co nfigurationprocess consists of these general tasks:
lDefining the ESI server.
lDefining the defaultpi nghealth check method.
lDefining the ESI group.
lDefining the HTTP redirect filterfor sending HTTP traffic to the ESI server.
lApplying the firewallpolicy to t heguest role.
lDefining ESI parser domains and rules.
Thereare three configuration “phases” on the controller as a part of the solution.
lThe first phaseco nfiguresthe ESI ping health-checkmethod , servers , and servergroups .Thet erm server hererefers
to external AVF server devices.
lIn the second phase of thec onfigurationtask, the user roles are configured with the redirection policies (session
ACL definition) instructing the controllert o redirectt hedi fferenttypes of traffic to different server groups.
lIn the finalphase, the ESI parser domains and rules are configured.