How to work with unknown devices in OpManager?

How to work with unknown devices in OpManager?

There are 2 reasons for devices to go in to  "Unknown" Category in OpManager:

1)Device credentials (SNMP/WMI/CLI) are not added or discovered with wrong credentials in OpManager.

2)Credentials are correct but OpManager does not have built-in Device Templates.

Solution:

1)Add the credentials to the Credential Library  , Go to settings > Discovery > Credentials > Add Credential>select the credential type based on the device type > provide the credentials > Save and then try to discover or add  the device using the credentials. 

2)To create a new Device Template > Settings > Monitoring > Device Template > Add Template > type in the Template name based on the Device Model (ex: Cisco 2960 Series ) , Vendor ( ex: Cisco , if you do not the see the vendor in the drop down list , create new and add it) , select the Category (Ex: Switch) , click on Query Device , provide the device IP or name ,type in SNMP  community > click on Query , this will get the SysOID from the device and add that to the template > Save the Template , now try to discover or add the device using correct credentials which will categorize them properly.

After the above steps , devices will be categorized properly, however if the device is matched with the above new template , we need to add custom SNMP monitors.

Refer the link below to add custom SNMP Monitors :
                  New to ADManager Plus?

                    New to ADSelfService Plus?

                      • Related Articles

                      • End user Monitoring in OpManager

                        This feature is to correlate and exhibit the data across our internal modules  OpManager, NetFlow Analyzer &Firewall Analyzer  from an end user perspective.  Consider as Company(ABC)  has 'x' number of employees. Each one will have a device with ...
                      • Device/Interface Name not populating in Traffic (NFA) Module for SNMP V3 - OpManager v12

                        Issue:  Device/Interface Name not getting populated for N/w Devices monitored using SNMP V3 protocol OpManager v12. Analysis:  When the device takes longer time to respond for the SNMP V3 requests, then the device name will not get populated in the ...
                      • Steps to Enable Telnet and RDP options in Browsers to use with Opmanager

                        Steps to Enable Telnet and RDP options in Browsers to use with OpManager       Enabling Telnet and RDP protocols in browsers: There are some prerequisites that needs to be met based on the browsers you use to work with Remote Desktop and Telnet ...
                      • Migration of Opmanager V12 from one server to another Server

                        Steps: 1)Stop ManageEngine  OpManager Service 2)Go to OpManager command prompt with run as Admin and execute  BackupDB.bat  from OpManager\bin\backup      folder.      A backup file will be created under OpManager\backup folder ( ...
                      • Enabling SSL using .PFX certificate in OpManager version 12

                        Steps to enable SSL using .Pfx certificate 1. First you need to convert the .pfx type to .truststore type.  Place your .pfx certificate in \OpManager\jre\bin\ folder.  To do that, open a command prompt as an Administrator and go to \OpManager\jre\bin ...