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

1.8 Recoiling Database
AutoNOC utilizes a powerful database technology called the Recoiling Database, or RDB. The database architecture is specifically designed to provide infinite histories of both performance and event based network data.

As AutoNOC receives data either from incoming events or from data computed while polling, it keeps the data in memory. At periodic intervals (which are user customizable) this data is flushed and written away to the RDB. When this file grows to a certain file size, AutoNOC will archive the file and create a new file. This process is carried out with “ACID” (Atomic, Consistent, Isolated and Durable) properties, meaning that the RDB cannot end up in an inconsistent state.

1.8.1 Database Volumes
As mentioned above, AutoNOC creates and grows database volumes over time. The following are the files related to this process.

Filename Description
current.rdb The current database file. This file is enlarged over time to hold blocks of new data. When this file grows to a certain size. AutoNOC 2 will archive the file and create a new file.
~recoil.rdb Temporary recoil construction file.
vYYYYMMMMDD-HHMMSS.rdb Archived historical database file. The timestamp is the date of the last data record included in the file.

It is safe to copy, back-up, and delete the v*.rdb archived historical database files. For example, it is okay to make a copy of these and burn them to CD. Once one of these files is created it is purely used as supplemental reference data by AutoNOC. If the apropriate data block volume is available, then graphs and analysis of the data contained in the file will be available. If the volume database is not available, AutoNOC will simply show a gap in the data.

1.8.2 Recoiling Database Settings
As shown in the following picture, the user can configure many settings for the recoiling process. It is possible to specify additional RDB paths for AutoNOC to search, how often AutoNOC should perform a recoil, the maximum size that a volume can grow to, and the compression level to use.

1.8.3 Backing Up the Model
When you utilize a back-up program to store the AutoNOC model, make sure that the back-up program excludes files that begin with ~. AutoNOC writes to these files live and reading from them while writing, as backup software does, can result in some lost data.

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