up.time 7 SNMP Monitoring Quick Start Guide|
This KB article provides a quick introduction to setting up your SNMP Network Devices in up.time 7 as well as how to resolve common set up issues.
Adding your network devices to up.time 7
The first step in setting up an SNMP device for monitoring within up.time is to add the device to up.time as an element. This is done from the My Infrastructure tab in the up.time tool bar via the Add System / Network Device link in the tree panel on the left side of the screen. After clicking the link, the Add system dialogue will ask you for a display name and description for the device, which can be any text.
The next choice is the option to select from the Type of System / Device, which will depend on the device type and the SNMP version it supports. The main choices for SNMP devices are:
For more details about SNMP and up.time's SNMP support, please refer to SNMP-based Systems in the up.time Administrator's Guide.
After selecting the appropriate device type for the element, provide the hostname or IP address and the SNMP connection details for the device / system. If the majority of the devices / systems share the same connection settings (ie. community string, port, etc.), it is recommended to enter these settings in the Global Element Settings page of the up.time UI (Config -> Global Element Settings -> SNMP Global Credentials), so that the Use Global SNMP Connection Configuration check box can be selected; otherwise, you will need to provide the connection details for each device / system.
The main options here are:
If uncertain of which SNMP values to select for the device / system, the following areas may be helpful to check:
After setting all the SNMP configuration values and hostname, click on the save button to have up.time attempt to communicate with the device / system over SNMP and create the element. Some common issues that may arise at this stage are:
Setting up a Service Monitor for the device's OIDs Now that the device / system has been added as an element in up.time 7, a service monitor can be created to poll the results of specific OIDs (Object Identifier). An OID is a numerical identifier for one specific statistic or metric that is available from the device. These OIDs combine with a MIB (Management Information Base), which defines and describes the possible values for this metric.
The SNMP poller service monitor can be created from the Services tab in the up.time tool bar. From there, select Add Service Monitor from the tree panel on the left and choose the SNMP Poller option from the Network Service Monitors section.
As described above, a Name and Description can be entered and the next choice will be which host or service group to associate the service monitor with. For now, check single system and select the element / host that was just created above for for the SNMP device.
Next, under the SNMP Poller Settings section, click the Add OID button to launch the up.time MIB Browser, which is used to either select the OID manually by it's numerical value (e.g. .1.3.6.1.4.1) or by selecting the value from the OID tree. If this is the first time launching the MIB browser, it may take a couple minutes for up.time to load the pre-bundled MIBs into memory.
Once the MIBs are loaded into memory, the applicable OIDs for the device can be selected by drilling down into the tree. Up.time includes a pre-bundled selection of MIBs from the most common vendors, which can be found by drilling down to this location in the tree:
From within that location, the vendor of the device should be present and the appropriate OID for the device can be selected. For an OID to be valid, the right hand box needs to be populated with the following details: OID, Syntax, Description.
If there are no OIDs present for the vendor or the particular device, additional MIBs can be obtained from the vendor directly and loaded into up.time. This step is done on the monitoring station by placing the files in the <uptime_dir>/mibs/ directory, and restarting the up.time Data Collector (or uptime_core on Linux / Unix platforms) service to refresh the MIB cache. See Adding MIBs to up.time for further details.
After selecting the OID to poll for the device / system, the appropriate data type needs to be selected under Collection Info and possibly choose an additional option of how to process the returned value. The description / syntax information should provide some hints on what is an appropriate choice for this particular OID. Once this step is complete, click next to provide some additional details about how to handle the result.
Finally, click Add to add the OID to the service monitor and return to the Add Service screen and proceed with the usual choices about how up.time will react to the results of the service monitor (e.g. Warning / Critical Thresholds, Timing / Alert Settings, Alert / Action Profiles). Once all the settings are completed, click Finish to complete the service monitor.
At this point, SNMP poller can be tested by clicking on the Test Service Monitor button. If all is well, the monitor should be able to successfully poll the OID on the device and return the result. If it does not work, review the error and re-check the service monitor settings. |
Article InfoIndex: 578 OptionsQuick Links |
Process Count Monitoring with Net-SNMP | Rating | Views | |
|---|---|---|---|
|
|
Processes metrics are not available by default via Net-SNMP; therefore the Net-SNMP collection method in up.time does not gather process metrics. With a few extra lines added to snmpd.conf and a... By: uptime Support | Date Created: 8-7-2013 | Last Modified: 8-8-2013 | Index: 598 |
 
|
4844 |
up.time fails to start after a system reboot | Rating | Views | |
|---|---|---|---|
|
This article outlines what to do when up.time services do not start after a system reboot. By: uptime Support | Date Created: 12-6-2006 | Last Modified: 7-14-2011 | Index: 106 |
|
2982 |
Can an SNMP device be added as a Net-SNMP agent? | Rating | Views | |
|---|---|---|---|
|
|
up.time's net-SNMP agent type is intended for server platforms. Most network devices (switches, routers, firewalls, etc...) do not have the full set of required MIB information and should be added... By: uptime Support | Date Created: 6-12-2010 | Last Modified: 9-13-2012 | Index: 449 |
|
3586 |
Net-SNMP Metrics | Rating | Views | |
|---|---|---|---|
|
This article outline the metrics that up.time collects from a server that is running Net-SNMP. By: uptime Support | Date Created: 1-26-2007 | Last Modified: 6-30-2011 | Index: 131 |
|
10024 |
Why is up.time server load so high at the start of the month? | Rating | Views | |
|---|---|---|---|
|
|
At the start of each month the up.time data archiving process initiates to clear out old data from your DataStore. This can be a very resource heavy operation and may take a great deal of time to... By: uptime Support | Date Created: 8-7-2010 | Last Modified: 8-10-2011 | Index: 469 |
|
2055 |
