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.5 Probes
In AutoNOC, a probe is an object that actively queries data about the network and stores it in a database structure at a preset time interval. For instance, there is a built-in ping probe as well as many other types of probes.

Probes represent the object implementation of data acquisition and polling within the software. The following screenshot shows the location in a device of an example Interface Status probe.

The majority of probe functionality and settings is implemented in probe templates. You can even author your own probes by creating a probe template. For more information on authoring your own probes see 4.4 - Probe Template.

3.5.1 Database Storage

The Database tab of a probe provides a quick and dirty capability to see the raw data within the probe records. An example from a NET-SNMP Processor Utilization probe is shown below in the following screenshot.

The raw data for the database can also be downloaded by clicking on Download Data (CSV File).

3.5.2 Probe Discovery
AutoNOC uses the probe template, device template, interface template, and other objects to discover a device. It constructs the device by generating objects from the user's currently defined templates. During the Discovery process AutoNOC builds probes from the probe templates provided for the device in question.

The process works by first seeing which probe templates are available and relevant to the current discovery. It then takes each probe template, sets the object scope to the relevant component and then tries to solve the expression. If the expression can be solved and it returns a valid answer, then AutoNOC will keep that probe template, generate a probe for the device, and when discovery is complete, it will begin polling data for the device.

For more information on probe polling, see 3.11 - Polling and for more information on discovering devices, see 3.2 - Devices.

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