Date: Thu, 28 Mar 2024 21:14:21 +0000 (UTC) Message-ID: <1048650603.5503.1711660461696@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5502_281014632.1711660461692" ------=_Part_5502_281014632.1711660461692 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This topic provides a quick introduction to setting up your SNMP= Network Devices in Uptime Infrastructure Monitor as well as how to resolve= common setup issues.
The first step in setting up an SNMP device for monitoring within U= ptime Infrastructure Monitor is to add the device to Uptime Infrastructure = Monitor as an element. This is done from the My Infrastructure tab in= the Uptime Infrastructure Monitor tool bar via the Add System / Netwo= rk Device link in the tree panel on the left side of the screen. Afte= r clicking the link, the Add system dialogue will ask you for a display nam= e and description for the device, which can be any text.
The next choice is the option to select from the Type of System / D= evice, which will depend on the device type and the SNMP version it su= pports. The main choices for SNMP devices are:
For more details about SNMP and Uptime Infrastructure Monitor's SNMP sup= port, please refer to SNMP-based Systems in the Uptime Infrastructure Monitor 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 / sy= stem. If the majority of the devices / systems share the same connect= ion settings (ie. community string, port, etc.), it is recommended to enter= these settings in the Global Element Settings page of the Uptime= Infrastructure Monitor UI (Config -> Global Element Settings -> SNMP= Global Credentials), so that the Use Global SNMP Connection Configura= tion check box can be selected; otherwise, you will need to provide the con= nection 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 t= he save button to have Uptime Infrastructure Monitor attempt to communicate= with the device / system over SNMP and create the element. Some comm= on issues that may arise at this stage are:
Because the device / system is an element in Uptime Infrastructure Monit= or, a service monitor can be created to poll the results of specific O= IDs (Object Identifier). An OID is a numerical identifier for one spe= cific statistic or metric that is available from the device. These OIDs com= bine 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 Uptime Infrastructure Monitor tool bar. From there, sele= ct 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 c= hoice will be which host or service group to associate the service monitor = with. For now, check single system and select the eleme= nt / 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 Uptime Infrastructure Monitor MIB Browser, w= hich 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 minu= tes for Uptime Infrastructure Monitor to load the pre-bundled MIBs into mem= ory.
Once the MIBs are loaded into memory, the applicable OIDs for the device= can be selected by drilling down into the tree. Uptime Infrastructur= e Monitor includes a pre-bundled selection of MIBs from the most commo= n vendors, which can be found by drilling down to this location in the tree= :
iso -> org -> dod -> internet -&= gt; private -> enterprises (which translates to an OID of .1.3.6.1.= 4.1)
From within that location, the vendor of the device should be present an= d the appropriate OID for the device can be selected. For an OID to b= e valid, the right hand box needs to be populated with the following detail= s: OID, Syntax, Description.
If there are no OIDs present for the vendor or the particular device, ad= ditional MIBs can be obtained from the vendor directly and loaded into Upti= me Infrastructure Monitor. This step is done on the monitoring statio= n by placing the files in the <uptime_dir>/mibs/ directory, and resta= rting the up.time Data Collector (or uptime_core on Linux= / Unix platforms) service to refresh the MIB cache. See Adding MIBs to Uptime Infras= tructure Monitor 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. Th= e description / syntax information should provide some hints on what is an = appropriate choice for this particular OID. Once this step is complet= e, click next to provide some additional details about how to handle the re= sult.
Finally, click Add to add the OID to the service monitor and re= turn to the Add Service screen and proceed with the usual choices = about how Uptime Infrastructure Monitor will react to the results of the se= rvice 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 Ser= vice 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 setting= s.