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

2.7 Configure
Users that have access to the configure page (usually administrators of the AutoNOC installation) are able to control and modify how exactly AutoNOC works. Please read the prior topic 2.6 - Design to get familiar with how the window manager and web GUI works. The configure screen makes use of the same technology.

The following screen shows the configure page:

2.7.1 Licensing
AutoNOC's licensing dialog is relatively straight forward as shown in the following screen shot. It is useful to note that you can get counters for how many devices, probes, and users are currently defined in the model.

2.7.2 SNMP MIB Objects
All compiled SNMP MIB Object IDs are also listed in one large tree on the configure page. This includes descriptions, the object ID, textual ID, object type, status, etc., as shown in the following screen shot.

)

When exploring the tree, click on any tree item, and then click on the Object Information tab to retrieve the full information on the SNMP object. This tree is a useful reference when designing custom probes. For more information on adding and compiling your own MIBs, see the topic 4.1 - Adding SNMP MIBs.

2.7.3 Portal Setup
The portal setup dialog is used to customize the name, IP address, TCP port, and other settings of the AutoNOC portal.

As the following dialog shows, this is also where you configure the e-mail server for AutoNOC to send alerts to.

Full information on launching e-mail alerts based on alarms is available in section 3.8 - Actions. Additionally, you can find more information on configuring AutoNOC's firewall in section 1.10 - Security.

2.7.4 Services
The services configuration objects provide the user with access to the actual services and their settings that make AutoNOC work. You can find an in depth discussion of the AutoNOC services in section 1.3 - Services. To modify the settings of one of the services, click on the named service and browse the options presented.

Some common service tasks:

  • Stop Service
    Stops the service and prevents it from performing it's tasks.
  • Start Service
    Starts a stopped service.

2.7.5 Users
User objects (and user access) is managed on this page. Here are some common user tasks performed on this page.

  • Add User
    To add a new user click on the Users tree root and then select New User.
  • Delete User
    Open the Users tree root, click on the user to delete in order to open the user object dialog, and then click on the Delete button two times.

For more information on users, please see the full user discussion in section 3.10 - Users

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