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 Flow Analysis page under Inventory tab.
Resolution:
Please follow the below mentioned steps.
- Stop the OpManager service.
- Open Command Prompt with Run as Administrator.
- Navigate to ManageEngine\OpManager\conf directory.
- Edit the "system_properties" using Word Pad.
- After the last line add the below entry.
routSNMPTimeOut=RouterIP1-TIMEOUT_IN_MILLIS,ROUTERIP2-TIMEOUT_IN_MILLIS
Eg: routSNMPTimeOut=192.168.0.1-30000,192.168.0.2-30000,192.168.0.3-30000 - Rename the logs and start the OpManager service.
- Go to the device snapshot page > Edit the device, set SNMP, select the SNMP credential>Test SNMP and click on OK to save the SNMP credential.
- Click on Edit Device Details > Select Fetch SNMP from the router> Save.
Note: The above mentioned solutions is common for OpManager Essential and Plus, version 12.
New to ADSelfService Plus?
Related Articles
Interface Name/Description/Alias not updated due to SNMP in Netflow Analyzer v12
Scenario: If the device is using SNMP v2 by default , Device Interface ifname,ifdescription,ifalias and interface bandwidth speed will not get updated because Netflow analyzer to set to use SNMP v1 by default. Solution : To make SNMP v2 as ...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 ...Not able to see Syslog information in Firewall Analyzer within Opmanager V12
Solution : OpManager V12 has 2 different Syslog servers , one for capturing specific syslog messages based on the syslog rule configured for generating alarms in OpManager and another one for Firewall module for monitoring complete syslog traffic. ...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 ...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 ...