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

4.6 Device Template
Device templates in AutoNOC generally specify definitions and settings for specific pieces of hardware. AutoNOC includes many built-in device templates and users are free to define their own. The following screenshot shows an example device template:

4.6.1 Information and SNMP Discovery Text
Device templates include fields to specify a Manufacturer, Model, and Type. Sets can be designed to grab devices that have certain text (e.g. "Router") in the key words. The template device text is also helpful in reporting back to users. The following screenshot shows an example device template:

It is useful to notice the SNMP Descriptions string list. This list of keywords is used during discovery of a device to see if a given device being discovered matches the template. AutoNOC utilizes an internal scoring formula that compares a devices SNMP description to the list of keywords. The more correct matches the more likely the chosen template is accurate for the current device.

4.6.2 Allowed Components, Interfaces, and Probes
Every device template can limit the types of objects that may be discovered for devices that are derived from the template. The following screenshot shows an example setup that specifies that only Interface components can be created for the device.

The Interfaces and Probes tabs allow the user to further limit which interfaces and probes may be discovered. Note that if no objects are chosen under the Limit To side of the object selection box, then all objects will be allowed. This is true throughout AutoNOC.

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