Extreme Networks EPICenter 5.0, Руководство пользователя

Страница: 119 / 208

Monitoring and Tuning EPICenter Performance
EPICenter Concepts and Solutions Guide 119
MAC address polling is enabled or disabled globally through the MAC Polling Server Properties in the
Admin applet. If enabled, MAC address polling can then be enabled on a per device basis through the
Inventory Manager.
Through the MAC Polling Server Properties, you set the amount of load, which determines the amount
of elapsed time between sets of FDB polling requests. A complete MAC address polling cycle consists of
multiple groups of requests, until all devices with MAC address polling enabled have been polled.
A setting of Light (recommended) means the elapsed time between groups of MAC address polling
requests will be calculated to place a lighter load on the EPICenter server. As a result, it will take longer
for the server to accomplish a complete polling cycle. Moving the load indicator towards Heavy will
shorten the elapsed time between groups of MAC address polling requests, at the cost of a heavier load
on the EPICenter server.
You can use the EPICenter Server State Summary Report to see the MAC address polling frequency
based on the current setting of the MAC Polling server properties. The Server State Summary report
tells you how long it took to complete the most recent polling cycle, as well as the average time it has
taken to perform a complete polling cycle. Based on this data you can determine if you need to adjust
the MAC Polling System Load factor.
Telnet Polling
Telnet polling is used for MAC address polling, for retrieving Netlogin information, for retrieving ESRP
information on older Extreme switches, and for retrieving Alpine power supply IDs. You cannot modify
its frequency other than as discussed for MAC polling in the previous section. You can disable Telnet
polling entirely, however, in the Devices area of Server Properties in the Admin applet.
If you disable Telnet Polling, MAC address polling is also disabled.
Performance of the EPICenter Server
Performance of the EPICenter server itself is affected by the number of devices you are managing as
well as the resources of the system on which the EPICenter server is running.
You can use the Windows Task Manager or a tool such as
top
in Solaris (available as downloadable
Freeware) to determine how much memory and processor the EPICenter server is consuming. The
larger the set of devices EPICenter tries to manage, the more resources it will require. If you also run
the EPICenter client on the same system as the EPICenter server, that will increase the load. You should
ensure that you have adequate processing power and enough memory to allow EPICenter to run
without extensive swapping.
The EPICenter Release Note provides information on the system requirements for the EPICenter server.
If EPICenter server performance is slow, you can look at the Thread Pool Statistics using the EPICenter
Server State Summary Report. Specifically, if the Percentage Wait per Request statistic is high (greater
than 20%) you can consider increasing the maximum thread pool size and the maximum number of
SNMP Sessions.
To do this, go the Admin applet, and select Scalability under the Server Properties tab. Then increase
both the Thread Pool Size and the Maximum number of SNMP sessions by between 25% to 50%