This section contains the following information:
The Advanced Trending Agent is an application that gathers and stores the trend data (historic data) for any parameter instrumented by an SNMP agent, if it is defined by a MIB variable and not just pre-configured MIB variables.
The Advanced Trending Agent functionality is available on NetWare, Windows, and Linux platforms.
The Advanced Trending Agent periodically collects and stores the samples of the configured MIB variables. The collected data is exposed through an SNMP interface. This data can be used to view the long-term trend graphs of the parameters.
You can configure the Advanced Trending Agent using a configuration file or through SNMP interface. The Advanced Trending Agent includes a command line utility, which reads the configuration file for any updates. The utility also resets the data collected and starts collecting new data. You can also configure the Advanced Trending Agent with threshold values for the parameters and generate a trap when the value exceeds the threshold value.
The Advanced Trending Agent starts trending on MIB variables specified in a configuration file.
On Windows: installation_path/advtrend/ini/advtrend.ini file
On Linux: /etc/opt/novell/Novell ZENworks/zfs-mms-advtrend.conf file
You can modify the contents to add new parameters to trend upon or modify existing ones. The configuration file follows a standard INI format.
The section name can contain any value and is typically a meaningful name for the parameter being configured. All the section names in a given file must be distinct.
IMPORTANT: You cannot change the name of the section. If you do so, the data for the parameters is lost and new data is collected.
You cannot change the names of the keys. Each key represents a particular configuration that defines the trending activity for that parameter. There are certain mandatory keys that must be defined for any section. If these keys are not present, the Advanced Trending Agent ignores the entire section.
In a set of the configuration keys, some of the keys are treated as mandatory keys. That particular Configuration entry is read-only if the data for the Mandatory configuration keys is supplied or id the particular configuration entry is discarded.
A typical section looks like this:
[Interface In-Octets]
MIBVariable=1.3.6.1.2.1.2.2.1.10.1
MIBVariable Type=1
MIBVariableTrendingStatus=1
MIBVariableDisplayName=Interfaces
SampleInterval=5
SampleType=1
Buckets=80
ThresholdRising=100
ThresholdFalling=60
AlarmType=1
AlarmSeverity=4
ThresholdAlarmGenerationStatus=1
IdentifierOID={1.3.6.1.2.1.2.2.1.10.3}
Filters=2
F1={I1=MS TCP Loopback interface}
F2={I1=3COM 3C920 Integrated Fast Ethernet Controller 3C905C-TX Compatible) - Packet Scheduler Miniport}
FilterType=1
You must specify the following mandatory keys:
MIBVariable (key 1)
SampleInterval (key 5)
ThresholdRising (key 8, only if ThersholdAlarmGenerationStatus=1)
ThresholdFalling (key 9, only if ThersholdAlarmGenerationStatus=1)
AlarmType1 (key 10, only if ThersholdAlarmGenerationStatus=1)
For more information, see Quick Reference Table.
Before starting the Advanced Trending Agent on Linux, ensure that you have completed the following tasks:
You must configure the snmpd master agent so that it allows SNMPv1/v2c read-only access to the Advanced Trending Agent.
Edit the snmpd.conf file that is used by the snmpd master agent.
Ensure that the access control settings allow SNMPv1/SNMPv2c access to the local host on the entire OID tree (starting with .1)
For more information, refer to the question, How do I configure access control in the SNMP Frequently Asked Question.
You must configure the snmpd master agent so that the traps generated by the Advanced Trending Agent are sent to the site server.
Refer to man snmpd.conf (5) man page for the specific syntax to configure a trap sink.
You must configure the Advanced Trending Agent to use the same community string you have used to allow access in the Enabling the SNMPv1/SNMPv2c Access for the Local Host section.
To configure the Advanced Trending Agent, you must change the default purge interval.
The Advanced Trending Agent automatically trends on certain available MIB variables or specific instances of some SNMP tables. If these instances become unavailable, you can clean up the resources associated with the trending. You must configure the purge interval the Advanced Trending Agent should wait before this occurs.
This table provides you a quick reference to the values of the keys and the meaning:
The Advanced Trending Agent enables you to dynamically change the parameters of the trending activity for one or more MIB variables. You can add new entries or remove existing entries that are being trended in the configuration file.
After you make the changes, you must enter the advtrend command for the Advanced Trending Agent to retrieve the latest information. The advtrend command is available in the following locations:
Use the advtrend command to perform the following operations:
If you want to restart trending the parameters:
Make changes to the configuration file to add, modify, or delete any configuration sections.
At the server prompt, enter advtrend reset.
The new entries will replace existing entries according to the configuration settings. The trending will start from the beginning.
WARNING: Once you reset the information, the old data will be lost.
Edit the configuration file to include a new section for your parameter.
Define the required keys in the new section.
At the server prompt on NetWare enter advtrend reread, and for Windows or Linux, enter advtrend read_cfg.
The new entries to be trended are appended.
The entries to be trended for this configuration section are removed.
If you want to modify the values for the keys of an MIB variable being trended, do the following:
Edit the configuration file to change the values of the keys.
At the server prompt, on NetWare enter advtrend reread, and for Windows or Linux, enter advtrend read_cfg.
The Advanced Trending Agent will now use the new parameters.
If you modify the following parameters, the previous data will be removed: