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

5.3 Windows Troubleshooting
Please review the System Requirements prior to installing AutoNOC 2 to make sure your system meets the requirements. Please also read the 5.1 - General Troubleshooting page to find answers to common problems.

5.3.1 High CPU Usage, Small Model
Some users of Windows operating systems (like Advanced Server) have experienced high CPU usage conditions. This was tracked down to a poorly performing NT kernel driver in the shipping release of Windows 2000 Advanced Server. Installation of the latest Windows 2000 service pack (SP3 at the time of this writing) cleared up this problem.

5.3.2 Service Doesn't Install, Security Problems
AutoNOC 2 or Windows requires that the user installing the software have full administrative access.  AutoNOC 2 requires full access to the machine in order to use lower level networking protocols that standard access blocks. If you are having problems creating an account with this configuration, then consider installing AutoNOC on a fresh installation of Windows and logon with the default administrator account.

Some corporations use pre-imaged installations of Windows. It is possible some settings in the image may block the installation of new services.

5.3.3 Microsoft SNMP Agent Leaks Memory
Microsoft has confirmed that the Microsoft SNMP Agent will leak memory in some cases. This can be corrected be re-installing the latest service pack.

The following links to Microsoft support pages may be helpful.

5.3.4 Error: "Application Failed to Initialize Properly"
When this error occurs while trying to install AutoNOC, it means that an existing image of AutoNOC is already running or a different AutoNOC product. Please stop all other AutoNOC software and retry.

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