Users Guide

1089 | External Services Interface Dell Networking W-Series ArubaOS 6.4.x| User Guide
Figure 232 ESI Parser Domains
The ESI syslog parser begins with a list of configured IP interfaces which listen for ESI messages. When a syslog
message is received, it is checked against the list of defined ESI servers. If a server match is found, the message
is then tested against the list of predefined rules.
Within the rule-checking process, the incoming message is checked against the list of rules to search first for a
condition match (see Syslog Parser Rules on page 1090). If a condition match is made, and the user name can
be extracted from the syslog message, the resulting user action is processed by first attempting to look up the
user in the local user table. If the user is found, the appropriate action is taken on the user. The default
behavior is to look for users only on the local controller. If the user is not found, the event is meaningless and is
ignored. This is the typical situation when a single controller is connected to a dedicated ESI server.
Peer Controllers
As an alternative, consider a topology where multiple controllers share one or more ESI servers.
Figure 233 ESI Peer Controllers
In this scenario, several controllers (master and local) are defined in the same syslog parser domain to act as
peers. From the standpoint of the ESI servers, because there is no accurate way of determining from which