Users Guide

1045| External Services Interface Dell Networking W-Series ArubaOS 6.5.x| User Guide
Configuring ESI
You can use the following interfaces to configure and manage ESI and ESI syslog parser behavior:
l The Web user interface (WebUI), which is accessible through a standard Web browser from a remote
management console or workstation.
l The command line interface (CLI), which is accessible from a local console device connected to the serial port
on the controller or through a Telnet or Secure Shell (SSH) connection from a remote management console
or workstation.
By default, you can access the CLI only from the serial port or from an SSH session. To use the CLI in a Telnet
session, you must explicitly enable Telnet on the controller. The general configuration descriptions in the following
sections include both the WebUI pages and the CLI configuration commands. The configuration overview section is
followed by several examples that show specific configuration procedures.
In general, there are three ESI configuration “phases” on the controller as a part of the solution:
l The first phase configures the ESI ping health-check method, servers, and server groups. The term server
here refers to external server devices, for example, an AVF.
l The second phase configures the redirection policies instructing the controller how to redirect the different
types of traffic to different server groups.
l The final phase configures the ESI syslog parser domains and the rules that interpret and act on syslog
message contents.
The procedures shown in the following sections are general descriptions. Your application might be broader or
narrower than this example, but the same general operations apply.
Configuring Health-Check Method, Groups, and Servers
To configure the ESI health-check method, servers, and server groups, navigate to the Configuration >
Advanced Services > External Services view on the WebUI.
In the WebUI
1. Navigate to the Configuration > Advanced Services > External Services page.
2. Click Add in the Health Check Configuration section.
(To change an existing profile, click Edit.)
3. Provide the following details:
a. Enter a Profile Name.
b. Frequency (secs)—Indicates how often the controller checks to see if the server is up and running.
Default: 5 seconds.
c. Timeout (secs)—Indicates the number of seconds the controller waits for a response to its health
check query before marking the health check as failed. Default: 2 seconds.
d. Retry count—Is the number of failed health checks after which the controller marks the server as being
down. Default: 2.
4. Click Done.
5. Click Apply.
In the CLI
esipingprofile_name
frequencyseconds
retry-countcount
timeoutseconds