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.1 General Troubleshooting
Please review the System Requirements prior to installing AutoNOC to make sure your system meets the requirements.

5.1.1 Images and Icons Don't Show Up
This can occur if you have a bad or corrupted download. Try re-downloading and re-installing the software.

5.1.2 Forgot Username and Password
The default logon username is administrator (you can also logon using the translation of this word in your native language). No password is required when logging in.

5.1.3 Can't Logon
Your username and password are case sensitive. Make sure you are typing it in exactly as it should be.

5.1.4 Device Discovery Not Working / Probes Not Showing Up
As a general rule, AutoNOC discovers devices by applying the expression for the probe on the device and checking if the expression was solvable. A solvable probe is one for which all the components necessary to analyze the expression were available on the device.

When discovery doesn't work, or a probe isn't available, it usually means the AutoNOC portal can't see the device, the port related to the probe, or a required protocol is unavailable.

  1. Make sure you can ping the device from the command line of the AutoNOC Portal to insure connectivity to the device is available.
  2. Make sure the device has SNMP installed on the remote device and it has it's SNMP agent setup with the necessary MIBs you wish to monitor. Typically the HOSTS MIB is an important one for a wide range of monitoring tasks.
  3. Make sure you have the correct SNMP community name entered in the discovery window and the device dialog box.
  4. Make sure AutoNOC 2 can see the remote SNMP port 161 by doing a port scan. On Linux you can use the nmap command and on Windows you can use our free port scan utility (available in Free Stuff).
  5. Lastly, make sure the right IP address is being entered for the device.
(C) 2007 - All Rights Reserved - AutoNOC LLC
      Call me!