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.2 Automated Operations
AutoNOC means "automated network operations" or more specifically, a set of software tools that provides an integrated set of high performance management and troubleshooting tools that work well together and are as labor-free as possible.

Automated and integrated network operations the premise of AutoNOC. If you deploy AutoNOC, you will not need the four, five, or six applications typically required to detect and handle network problems. This saves money, saves time, reduces labor, and makes life that much more grand in the modern operations group.

AutoNOC is, in essence, a better, faster, more cost effective solution for a very complex and challenging technology problem. That is, the problem of how to monitor and manage everything happening inside large dynamic environments in a clean, practical manner.

In the Preface we discussed the important characteristics of a network operations platform, so let us now get into more depth about the functionality required for such a technology solution. The following are some of the key functional components that a network operations platform must include:

  • Polling (Active Monitoring)
  • Event Listening (Passive Monitoring, i.e., wait for events to come in)
  • Persistence and Data Storage
  • Analytics, Reporting, and Visualization
  • Alarms and Conditional Action Launches
  • User Interface
  • Customizability and Developer Features
  • Discovery and Model Building Capabilities
  • Sets and Queries for Custom Views
  • Security
  • Scalability
  • Authentication Compatibility
  • Multi-Language Support

AutoNOC takes all of these functional elements and integrates them together in a single coherent web application. The advantages for doing this are many and varied, but the prime reasoning is to deliver a better, faster, and more cost effective management solution.

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