To Next Page

To Previous Page

Tuning and Debugging EPICenter

EPICenter Concepts and Solutions Guide

138

</table>

<table>

</table>

</scalar>

</collection>

</collections>

Within the outermost collections statement, you can define multiple individual collections, each

bracketed with

The collection properties must be defined in the collection statement at the beginning of each collection

definition:

Table OIDs are defined in

<oid ... > statements, included between <table> and </table>

statements. OIDs from different tables must be put in separate

<table> statements. The label portion of

the statement appears in the MIB Collections Detail report, and as a heading in the exported data file.

Scalar OIDs are defined in

<oid ... > statements included between a <scalar> and </scalar>

statement.

The devices that should be polled are specified by IP address in <

scope ipAddress ...> statements,

one for each IP address.

The completed file must be named

collections.xml, and placed in the user/collections directory. The

Reload button in the MIB Poller Summary report will load the collections.xml specification, and begin

the collection process if the

initialState property specifies “running.”

Figure 62 on page 142 shows an example of an actual

collections.xml file.

Table 6: Control properties for a MIB collection specification

name A name for the collection

pollingIntervalInSecs The interval at which EPICenter should poll for the variables defined in this collection

initialState Whether this collection should start running immediately upon loading (values are

“running” and “stopped”)

saveData Whether the collected data should be saved to the EPICenter database (“yes” or “no”)

maxPollsPerDevice The maximum number of poll result sets that should be saved in the database

deletePercentage The percentage of the saved data that should be deleted when the file reaches it

specified limit

Extreme Networks EPICenter Guide User Manual

Questions and Answers: