NOTE:The procedures shown in the follow ing sectionsare based on the requirements in the example routed ESI topology. Your
application might be broader or narrower than this example, but the same general operations apply.
Health-Che ck Method , Groups, and S ervers
To configure the ESI health-checkmethod, servers, and server groups, navigate to the Configuration > Advanced
Services > External Services view on the WebUI.
Defining the Pin g Health-Check Me thod
In the WebUI
To configure a healthcheck profile:
1. Navigate to the Configuration > Advanced Services > Extern al Services pageo n the WebUI.
2. Click Add in the Health Check Configuration section.
To change an existing profile,click Edit.
3. Provide the following details:
a. Enter enter the name default for the Profile Name.
b. Frequency (secs)—Enter5.)
c. Timeout (secs)—Indicates the numberof seconds the controller waits for a response to its health check query
beforemarking the health check as failed. Default: 2 seconds. (In this example, enter 3.)
d. Retry count—Is the number of failedhealth checks after which the controller marksthe server as being down.
Default:2 . (In this example, enter3.)
4. Click Done when you are finished.
5. Click Apply.
In the CLI
Use these CLI commands to configure a health-checkmethod:
esipingprofile_name
frequencyseconds
retry-countcount
timeoutseconds
For example:
esipingdefault
frequency5
retry-count3
timeout3
Defining th e ESI Server
The followingsect ions describe how to configure an ESI server using the WebUI and CLI.
In the WebUI
To configure an ESI server:
1. Navigate to the Configuration > Advanced Services > Extern al Services pageo n the WebUI.
2. Click Add in the External Servers section.
3. Provide the following details:
a. Server Name.(This exampleuses t hename for ti_1.)
DellPowerConnect W- Series ArubaOS 6.2 | User Guide ExternalServicesInter face | 762