AutoNOC 2.5 User Guide
Preface
Acknowledgements
System Requirements
Legal

Part 1 - Introduction
1.1 The Ideal Difference
1.2 Automated Operations
1.3 Services & Scaler
1.4 Acquisition Stacks
1.5 Portal Deployment
1.6 Discovery and Crawler
1.7 Monitoring Agents
1.8 Recoiling Database
1.9 Multiple Languages
1.10 Security

Part 2 - NOC Views
2.1 Investigate
2.2 Observe
2.3 Visualize
2.4 Alarms
2.5 Analyze
2.6 Design
2.7 Configure

Part 3 - Model Design
3.1 Object Model
3.2 Devices
3.3 Sets
3.4 Set Criteria
3.5 Probes
3.6 Logs & Events
3.7 Alarms
3.8 Actions
3.9 Reports
3.10 Users
3.11 Polling
3.12 Service Levels
3.13 Dependencies
3.14 Performance

Part 4 - Developer Features
4.1 Adding SNMP MIBs
4.2 Variables
4.3 OSP API
4.4 Probe Template
4.5 Log Template
4.6 Device Template
4.7 Interface Template
4.8 Rebranding

Part 5 - Troubleshooting
5.1 General Issues
5.2 Linux
5.3 Windows

Appendix
A.1 OSP API Functions
A.2 Variables
A.3 Object Reference

3.11 Polling
As described in 1.4 - Acquistion Stacks, AutoNOC features a very powerful multithreaded, multiprocessing operations and data acquisition core that can poll many different devices simultaneously.

3.11.1 PollEvery Variable
How AutoNOC polls data is defined and managed with the %POLLEVERY variable. For more information on variables see 4.2 - Variables.

The %POLLEVERY variable is defined for each device object by default. The default value is "60" which means poll every 60 seconds as is shown in the following screenshot:

This variable can be defined at the device level, component level, or at the template level. So, for instance, say you want the Ping probe to be called every 5 minutes instead of every 60 seconds, modify the Ping probe template and add a PollEvery definition to the template probe variable and that variable will override the value defined for the device.

Please note that customizing polling intervals can result in decreased optimization opportunities for AutoNOC's operation engine. One result of this is that, in an effort to serve acquisition requests on a timely basis, AutoNOC may end up polling some shared variables more than once. As an example, Total Traffic and Traffic In each share some of the same SNMP queries, when these probes are fired at the same time, AutoNOC optimizes away duplicate queries cleanly, quickly and efficiently. If the probes fire at different times, AutoNOC may miss out on some of these opportunities resulting in more queries.

3.11.2 Adaptive Polling
An interesting thing to note is that the %POLLEVERY variable is evaluated by the AutoNOC OSP Command Prompt under the scope of the object that holds the variable.

What is powerful about the polling variable being an expression is that opportunities for adaptive polling are present. For instance, you can create a polling variable like "if(%L<0,60,300)" which polls the device every 60 seconds if there is currently a problem, and every 300 seconds otherwise!

(C) 2007 - All Rights Reserved - AutoNOC LLC
      Call me!