Frequently asked questions

No, the trial edition comes with all functionalities and you can monitor unlimited number of devices. If you need to extend your evaluation beyond 30 days, please request a license.

Please refer to the System Requirementspage.

Yes absolutely. Install a 30-day trial version and register yourself during installation to avail free technical support during evaluation period.

OpManager is licensed based on the number of monitored devices. Any device that responds to an ICMP ping can be monitored using OpManager e.g. Routers, Switches, Firewalls, Servers, UPS, printers. In a virtualized environment, every virtual instance is considered as a separate device for both monitoring and licensing purposes.

No, all ManageEngine products are licensed through a registered XML file. One can simply apply the license and use the same OpManager instance in production environments. One can even move the data to a different server if needed.

No, it is absolutely free. All you need to do is, ensure you have paid the Annual Maintenance and Support fee.

Absolutely, you can upgrade OpManager at any point of time. For instance, if you wish to upgrade OpManager 250 devices to 500 devices pack, you have to pay only the difference between these price slabs. Similarly for add-ons and plugins, you have to pay only the cost pertaining to it as per the current pricing.

The newly obtained license file has to be applied on your existing OpManager installation to enable the purchased devices pack or modules. It is not necessary to start things from scratch.

No. The license is restricted to a single installation of OpManager and not a consolidated license for the enterprise. In such a case you have to buy OpManager Enterprise Edition for remote network monitoring or separate license for each locations.

OpManager is an agent-less monitoring and management tool that uses a wide variety of protocols and technologies: ICMP, SNMP, WMI, CLI (Telnet/ SSH), TFTP, SCP. OpManager also includes a Syslog demon, SNMP Trap listener and Flow collectors for NetFlow, sFlow etc.. All these and more bring together many network performance monitoring and management capabilities within OpManager.

OpManager supports out-of-the-box over 100 vendors. To list a few: 3Com, Cisco, DELL, HP, D-Link, Extreme, Fortigate, Foundry, Juniper, Netgear, Netscreen, Nortel, Linux, Solaris, HP-UX, IBM-AIX, Microsoft Windows, APC, Libert.

The OpManager polling engine can monitor upto 10,000 Interfaces. However this depends on the system hardware, polling frequency and type of devices. The OpManager Enterprise Editioncan monitor upto 50,000 interfaces. To know the exact number of interfaces monitored by your OpManager installation, refer to the "About" page in the product (top right-hand side).

Yes through API. More about REST API here. Further OpManager integrates with ManageEngine products viz. ServiceDesk Plus On-Premise, Firewall Analyzer, Applications Manager, NetFlow Analyzer and Device Expert. See more on OpManager Integrations.

Yes, you can install OpManager on any Linux server viz. RedHat 7.x and above, Debian 3.0, Suse, Fedora, and Mandrake.

Note:

Installing OpManager on a Linux server will disable all WMI based monitors.

Apache Struts was used in OpManager till version 11600. Latest version of OpManager doesn't use 'Apache Struts'.

Note:

The following CVE id's are not applicable to OpManager:

• CVE-2013-2251
• CVE-2017-5638
• CVE-2018-11776

There’s no difference in the functionality. OpManager Enterprise Edition is designed to scale the network monitoring and management needs of large enterprises managing more than 500 servers or 5000 interfaces. The Enterprise Edition lets you deploy Probes for scalability on the LAN or in the remote locations to manage distributed networks.

Yes. Its Central-Probe architecture helps you manage distributed networks from a central location.

Refer the detailed system requirements specified here.

Yes, if you are managing more than 500 servers or 5000 interfaces, the Enterprise Edition is the best fit for you. Please sign-up using this form.Our support engineers will call and assist you.

OpManager is licensed based on the number of monitored devices. Any device that responds to an ICMP ping can be monitored using OpManager e.g. Routers, Switches, Firewalls, Servers, UPS, printers. In a virtualized environment, every virtual instance is considered as a separate device for both monitoring and licensing purposes.

Yes, it is possible provided you meet the system requirements of both the Central and Probe.

Yes it is secured. The Central and Probe communicate xml over HTTPS/HTTP connection.

Yes, the Enterprise Edition runs on MSSQL. However it also includes PostgreSQL bundled.

Ideally, OpManager will bind to both the IPs and can be accessed via both the addresses. In the Enterprise Edition deployment, you would have specified the Central Server address in the Probe. If both the IPs resolve to the address you have configured, there should not be any problem. If you have configured one of the IP addresses as the Central Server address, then you must take care to see that it automatically resolves/redirects to the other port that is available to effect the fail-over.

No, but OpManager MSP is built for scaling to the monitoring needs of emerging and large organizations. Handle network operations of multiple clients In MSP's simultaneously.

You need to migrate to version 124015 or above to apply Standard license.

No. You can only upgrade from OpManager Standard edition to OpManager Professional or OpManager Enterprise edition. Downgrade is not supported.

Yes. OpManager Essential edition has now been renamed as OpManager Professional edition.

Subinterfaces are listed based on two criteria:

• When two or more IP Addresses have the same ifIndex in the same device. (You can check it in ipAdEntifIndex (.1.3.6.1.2.1.4.20.1.2) in RFC1213-MIB)
• When two or more interfaces have the same IP address in the same device or different devices.

• Check whether the SNMP Credential is passed in the device.
• Check whether the ifTable returns an output in the MIB browser (Both Standalone and in OpManager).

• Check whether the SNMP Credential is passed in the device.
• Check whether the ifTable returns an output in the MIB browser (Both Standalone and in OpManager).

Check ifInOctects (.1.3.6.1.2.1.2.2.1.10) and ifOutOctects (.1.3.6.1.2.1.2.2.1.16) for the specified interface in the MIB Browser (RFC1213-MIB)

Traffic values are different in these Interface Graphs because, data collection happened at a different time. When you check real-time traffic during the interface's next poll, you may find that the real time traffic values and the interface graph values are the same.

Interface related reports are based on an hourly table. You can check these reports after an hour from when these interfaces were added.

The following may be the reasons for the ping option to fail even when the device is Up and running.

1. ICMP agent is not enabled in the destination device or server.

By default, OpManager checks the availability of a device with the help of ICMP ping function. But some business environment may only use the TCP agent in their devices as per their business functionality. In such cases, you can choose any of the alternate protocols (TCP or SNMP) to monitor the availability of those devices.

To change the monitoring method:

• Go to the Device Snapshot page of that particular device.
• Click on the three horizontal lines on the top right corner and select Edit Device details.
• Select TCP as the method under Availability Monitored via and save the changes.

2. The device may not be reachable from the OpManager server.

The following may be the reasons for a device to be Up and not reachable.

• Communication port may have been blocked by the Firewall.
• Network latency.
• ICMP traffic may have been disabled in that particular device.

User personality identifiable information like an email id/ phone number may be used multiple times in OpManager for various reasons across modules. The Personality Identifiable Information Search in OpManager allows you to locate the modules and view the total number of times a particular identity is used.

• Email ID
• Name
• Phone Number
• Mac Address
• IP Address

If a Nutanix cluster is directly deleted from OpManager, all the hosts and VMs under it will be monitored as individual physical devices if that cluster is still intact. But if the cluster itself has been dissociated from the network and is also deleted from OpManager, all devices under it will be reported as "Down" and will be raised as alerts in OpManager.

This error is shown when the mail server credentials are not configured (i.e. the 'User Name' and 'Password' fields under 'Authentication Details' in Settings -> General Settings -> Mail Server Settings are left blank), but the mail server used has a mandatory requirement for credentials to be configured.

OpManager will use only one postgres process but it may appear to be using more because, multiple products like Applications Manager and Service Desk Plus etc. might be installed in the same server. This is regular and expected behavior for postgress and is harmless.

This is mostly caused due to high latency between the Probe Server and the Central Server.

Open command prompt in the Probe Server and ping the Central Server, the ping response should be less than 100 ms, else the page loading in the Central Server might take time to load.

As of now, OpManager only supports Cisco IOS and Cisco IOS-XE type swithces and routers for IP SLA monitoring in OpManager.

Follow these steps to check for potential issues:

• The SNMP traps in OpManager listen on port 162, so check whether port 162 is available on the server.
• Please use a real-time packet capture tool to see if there is a response to the destination.
• Check the SNMP trap settings on OpManager to see if the device is listed on the 'selected' list.
• Finally, check for possible blockage issues due to firewall.

All promotions/advertisements related to the product will be shown in the product UI if this option is enabled.

Product related help will be shown in the product UI if this is enabled.

Click hereto learn about the pre-requisites for each credentials.

Click hereto learn about the impacts of providing wrong credentials.

Click hereto learn about the source router during VoIP monitor configuration.

Click hereto learn how to check the WMI credentials for Windows devices.

Click here to learn about SNMP context.

The login credentials would fail if one of the following scenarios occur:

a. AD Authentication:

• The Domain name is wrong.
• The wrong Domain is selected.
• The User is not present in the Domain selected.

b. Radius Server Authentication:

• User details are not present in the server.

SHA (Secure Hashing Algorithm) is a cryptographic hash function and the basic tool of modern cryptography. It takes an input and produces a 160-bit (20-byte) hash value, an encrypted form that cannot be reverted back to reveal the original message, or understood by making use of bitwise operations, modular additions, or compression functions.

Although both the SHA-256 and SHA-512 belong to the same family of the SHA-2 hash functions, there is a difference in the number of bits that they individually generate. The SHA-256 and SHA-512 each return a 256-bit hashed value and a 512-bit hashed value respectively. Additionally, the difference also lies in their capability to generate 2256 and 2512 random different hashes respectively.

AES (Advanced Encryption Standard) is a block cipher that relies on substitution-permutation network principle and encrypts data in blocks of 128 bits each, using keys of either 128, 192, or 256 bits. AES-128 is that variant of the AES algorithm that uses a 128 bit key for encryption.

This is totally dependent on the security level implemented by the user. If the selected security level is AuthNoPriv, it is not necessary. However, if it is set to AuthPriv, it is mandatory to specify the privacy protocol and the password.

Credential association failure occurs when the configured credentials are invalid for the selected device(s).

Auto Discovery happens when:

1. Auto VM Discovery is turned on:

OpManager runs Discovery process once every two hours to identify new VMs added to the host virtual device. This feature can be turned off for VMware and Xen devices. To do this, Go to Settings -> Discovery -> Credentials, choose a VM credential -> unselect Auto VM Discovery -> Save.

2. Discover via Trap is turned on:

OpManager can discover SNMP devices using Traps. To turn it off, Go to Discovery -> Discovery Settings -> Discover Devices via Trap -> Disable -> Save.

3. Devices added to Add-on Modules:

The devices that are discovered in the Add-on Modules such as NFA, NCM, FWA etc, will be automatically added into OpManager. You can disable this by setting the DISCOVER_EXTERNAL_NODE=true under OpManagerHome\conf\OpManager\discovery.properties (Restart OpManager service once the change is done).

4. Schedule Discovery:

Make sure your devices are not added to multiple discovery schedules. This will prompt OpManager to run discovery multiple times.

During discovery, if the device type is automatically identified by OpManager, then the value for the Device Type specified in the CSV will be ignored. Only when OpManager is not able to identify the device type automatically, the value for Device Type will be taken from the CSV file.

The device type may not be applied to the device because

• The device type may not be properly matched with the respective field in the CSV file.
• The device type may not be not resolved post discovery.

If both the IP addresses have the same DNS name, your NIC card will be added as a single device. On the other hand, if the IP addresses have different DNS names, each IP address will be added as an individual device.

Not reachable devices cannot be added from the Discovery Profile for the following reasons:

• To avoid adding too many not-reachable devices (especially the ones that doesn’t exist in your network).
• To restrict the devices that you don’t want to monitor from being added to OpManager.
• To increase the device discovery speed.

Click hereto learn about CIDR.

Click hereto learn about ReRun.

Click hereto learn about RuleEngine in OpManager.

Click hereto learn about access privileges for VMware credential.

Click hereto learn about the "Device not reachable" error and how to fix it.

Click hereto learn about Interface status polling.

Click hereto learn how you can configure a non-admin user for WMI monitoring.

Click hereto learn how to disable the dependency of devices.

Click hereto learn about device types.

Click hereto learn why device is categorized as unknown.

Click hereto learn more about this error and how to fix it.

Click hereto learn what happens when existing devices are rediscovered.

Click hereto learn how to find the missing VMs.

Click hereto learn how to import field properties from your files.

Click hereto learn why device is categorized as unknown.

Click hereto learn why some devices added with IP-address instead of host name?

Click hereto learn about the MIBs/OIDs used to discover Layer2 maps.

Click hereto learn about the list of ports to be opened in the firewall.

Click hereto learn about the MIBs/OIDs used to discover Layer2 maps.

Click hereto learn about rediscovering existing devices.

Click hereto learn how the re-run Discovery Rule Engine works.

Click hereto learn how the Status enable/disable option in rule engine works.

Click hereto learn how to troubleshoot vCenter Discovery issues.

Click hereto learn about the supported device types in OpManager.

Click hereto learn why devices are added with IP address as device name.

Click hereto learn about scheduled discovery/re-discovery and if it will affect existing devices.

Click hereto understand which ports are to opened in the firewall.,

To create a rule that automatically applies Notification profile to devices:

• Go to Settings > Discovery > Discovery Rule Engine and click on the Add Rule option on the top right.
• Fill in the name, description, choose an appropriate Criteria and click on the '+' symbol next to it.
• Under Actions, select Associate a Notification Profile, choose one from the available Notification Profiles displaced and click on the '+' symbol next to it.
• Save the created Discovery Rule.
• Schedule Automatic Discovery: Once the Discovery rule is created, you can schedule a discovery profile and include the created 'Discovery Rule'. This will help let you schedule device discovery and also perform the specified function (associating a Notification Profile).
• The selected Notification Profile will be automatically applied to all the discovered devices when the discovery is completed (as long as they satisfy the Criteria).

Click hereto learn how to add a subnet (CIDR) for monitoring?

During discovery of Nutanix devices, you can choose whether to turn on/off Auto VM discovery for that cluster by enabling or disabling the "Discover new VMs automatically" option. After discovery, you can do the same by navigating to the Device Snapshot page of the cluster, clicking on the hamburger menu on the top-right corner, selecting "Update Inventory" and enabling/disabling the "Discover new VMs automatically" in the 'Select Credentials' option.

Once you've added a new VM in your virtual network, it will be discovered into OpManager in the next discovery schedule for that virtual server. Usually, the new VM will be reflected in OpManager within two hours after addition. You can configure this rediscovery interval for any virtual server by navigating to the host/vCenter/Cluster Snapshot page, clicking on the tribar menu and selecting Update Inventory.

The discovered device status is marked as 'Unknown' in the following conditions:

• The credentials are invalid.
• A matching device template is not found (You can create a custom template or import custom-templates from third party website or forums).

The device status is classified as 'Not Monitored' when:

• The credentials are invalid or outdated.
• The device is not pingable from OpManager server.
• The device has been unmanaged by the network administrator.

Click hereto learn why devices are added with IP address as device name.

It maybe due to the following reasons:

• Check if the interface discovery is enabled in the discovery profile.
• SNMP credential failure.
• SNMP timeout due to large number of interfaces.

OpManager will add new devices automatically in the following scenarios:

• Scheduled discovery (scheduled by the admin/operator).
• Auto VM discovery is enabled.
• Devices discovered via SNMP traps (Settings > Discover Settings > discover devices via trap).

After creating a custom category, the operator must associate devices to this category. If not, the newly created category will not be displayed.

Click hereto know the difference between device type and category.

• Discovery - Interface is disabled in the Discovery Profile.
• Interface type is not selected in the Discovery - Interface page.

Click hereto know why some interfaces are in unmanaged state.

• Go to Inventory -> Interfaces.
• Choose the required interface from the list.
• Click on the menu icon on the top right corner of the interface summary page.
• Click on Threshold Settings and assign the threshold values for attention, trouble, critical for Utilization, Error Rate & Discard Rate.
• Click on save.

• Go to Inventory -> Interfaces.
• Select the required interfaces by ticking the appropriate check boxes and click on Generate Reports button on the top right corner.
• Choose the time frame, monitoring parameters and click on Generate Report.

Ifindex is an unique number that identifies each and every interface. When an interface is changed physically, the ifindex also changes. But, in OpManager, that interface will still have its old ifindex value. This directly affects the monitoring and data collection of that particular interface and triggers wrong alerts. You can either persist using the same ifIndex or enable schedule rediscovery for those interfaces in particular.

Reason: OpManager archives and maintains data from different performance tables regularly. Likewise, the data collected at that very instance is stored in the Statsdata table. This is known as raw or current data. This table is created every 24 hours, which means the backup of the previous day's data is carried out at the end of the day. So, when the custom time period mentioned is less than a day, OpManager will not have any data to display.

Solution: Since the backup takes place between 23.55 hrs to 23.58 hrs every day, specifying the duration from that day's midnight to the next day's midnight will fetch the necessary information.To know more about generic data archiving behaviour in OpManager, visit this page.

The primary reason for this mismatch is the fact that both the graphs fetch data in two different ways. In the real time graph, the refresh rate is set to 1 second by default and the polling happens every 10 seconds. Concurrently, in the interface snapshot graph, the default polling interval is 15 minutes, but can be customized to a minimum of 30 seconds. Here, the polling happens for the time interval that is specified by the user. Clearly, both the graphs fetch data at different polling intervals and operates differently.

Click hereto learn about Idle interfaces.

In the device snap shot page, the criteria for Notification Profiles will only be listed based on the device type and applications installed in the device.

Example: MSSQL related threshold criteria will only be available in the Notification Profile section of the device snap shot page if MSSQL is installed in the device.

• In ESX-based monitoring, only a particular host and its corresponding VMs will be discovered during the discovery process. In vCenter-based monitoring, all the hosts under the vCenter along with their VMs will be discovered.
• ESX-based monitoring does not capture vMotion (migration of a VM from one host to another), while it is captured in vCenter monitoring.
• In vCenter-based monitoring, OpManager will also fetch Datacenter and Cluster details. This does not happen in ESX based monitoring.

A VM is identified as unknown, if the VMware API does not have any information about the VM's Guest OS at that point of time. To discover the VM with the correct type, you can use SNMP / WMI / CLI credentials of the required device.

If a VM is listed as "Not monitored" under OpManager, these might be the possible reasons:

1. The VM was not selected for monitoring during discovery: If the VM was not selected during the discovery of the host/vCenter/Cluster, the corresponding VM will not be monitored. You can easily start monitoring it by navigating to the host/vCenter/Cluster page in OpManager, and clicking the green "Start monitoring" icon next to the unmonitored VM.

2. VM not reachable from OpManager: Sometimes, even if all the details are available, the VM won't be reachable from the OpManager server. This mostly happens because the corresponding VM is in a "powered off" state, or maybe because the VM is in a different network that the OpManager server is not able to access.

3.Wrong device name details/no IP available:

• When discovering a VMware device, OpManager will initially try to fetch the DNS name and IP address from the vCenter and reach the device via either of these (depending on the option selected in the Poll Using setting).
• If both of these details are not available in the vCenter, OpManager will finally try to discover the device using the VMs entity name. If the entity name is not resolved to any IP, the VM will then remain in an unmonitored state.
• When the VM is discovered using the device name, there will be issues with monitoring the VM when the device name is not resolved to a valid and reachable IP address.
• To avoid this, you can either try and discover VMs with their IP addresses. In the case of VMware, installing VMware tools will help sync all necessary device details from the VM with OpManager.

Yes, it is possible. Go to the vCenter/Host's Device Snapshot page, click the 'Virtual Machines' tab and you can see a list of all VMs discovered under that vCenter/Host. Click on the green 'Start monitoring' icon under 'Monitoring' column next to any unmonitored VM, and select the suitable credential profile(s) to start monitoring them.

Sometimes, during vCenter discovery, some of the VMs present in it won't be monitored automatically. This happens due to a couple of reasons:

• If the VM(s) is/are being monitored already in OpManager, it won't be discovered under the newly added vCenter.
• The hostname of the VM(s) provided by the vCenter does not return a valid IP address or DNS name.

In this case, you'll have to enable the unmonitored VMs manually. Here's how you can do it:

• Go to the vCenter's Device Snapshot page and click on the Virtual Machines tab.
• Now you can see the list of VMs available under that vCenter. Unmonitored VMs will have the green "Start monitoring" icon next to them under the Monitoring column.
• Click on the Start Monitoring button for the VM you wish to monitor, provide the IP address/DNS name details, select the applicable Credential profiles and click Discover to start monitoring it.

Unfortunately, monitoring of disk partitions in virtual servers is not available through API. To monitor them, you need to associate suitable OS credentials (SNMP, WMI, CLI) in addition to the VM credentials, and then add disk monitors from the Device Snapshot page or from Settings → Monitoring → Performance Monitors.

When a VM that has been discovered into OpManager is deleted from the user environment, it is not deleted from OpManager too. Instead, it is moved to an "Orphaned" state where the device is still present in OpManager but is not being monitored. If you wish to remove the device from OpManager too, you can simply click on the red "Stop Monitoring" button.

Yes, it is possible. To start monitoring it:

• Go to Virtualization → VMware and in the filters available on the left pane, select 'Datastores'. Select any datastore from the list, and click on the 'Monitors' tab of the Datastore Snapshot to view existing monitors and add new ones.
• You can also go the Device Snapshot page of the corresponding Host/vCenter, select the 'Datastores' tab, tap on any Datastore to open its Snapshot page, and click on the 'Monitors' tab to add, associate or remove monitors.

For basic discovery and monitoring, read only access privilege is enough but the user must have access to all the Hosts and vCenter servers. Advanced operations like executing workflows in VMs or hosts (like powering VMs on/off) can be performed only if the user has administrator privileges.

Yes, you can monitor the hardware of Hyper-V host devices. OpManager currently supports hardware monitoring for many vendors such as Cisco, HP, Dell and Juniper. To know more on the prerequisites for hardware monitoring, you can visit OpManager's help documentation on hardware monitoring.

If the values for Hyper-V VM memory utilization are being displayed wrongly, it might be because dynamic memory allocation has not been enabled in your HyperV host. Try enabling the "Dynamic Memory Allocation" for the VM which is displaying the wrong Memory Utilization values. (Note: This issue was only observed in older versions of Windows Server OS, mostly until 2008 R2).

This option allows you to choose if OpManager should automatically discover any new VMs that are created in a Xen environment in your network.

Yes, the severity level for VMware Events can be changed in two places.

Device specific:

• Go to the Device Snapshot page of any vCenter, select 'More Options' and click 'VMware events'.
• Click on the Edit icon next to the event that you want to modify, change the severity and click 'Submit'.

Global:

• Go to Settings → Monitoring → VMware Events and click 'Edit' next to any VMware Event.
• Change the severity to the desired value, and click 'Submit'. Note that this change will be reflected only when this VMware Event is associated to new devices.
• To change the severity of this event in existing devices, you can either re-associate the modified events to the necessary devices, or go to the Device Snapshot page and follow the device-specific steps mentioned above.

To disable VMware Event-related alerts, go to the vCenter's device snapshot page, click More Options and select the VMware events tab. Click the Bin icon next to the event you wish to delete.

You can create a Workflow to automate powering on/off the VMware VMs. To create one, go to Workflow → New Workflow and click on 'VMware' in the left pane. It contains all VMware related actions you can perform, including Power On/Power Off VMs. Drag and drop the relevant actions to create a workflow of your choice.

During discovery of any virtual server, you can select suitable SNMP/WMI/CLI credentials for the VMs hosted under it to fetch the proper device type. This is applicable for all virtual server types (VMware/HyperV/Xen/Nutanix).

In case you did not do this during discovery, you can go to Settings → Network Discovery, click on the Rediscovery tab and select the VMs and their suitable credential profiles to rediscover them and assign proper device types.

The following datatypes are supported for Performance monitors in OpManager:

• Integer
• Decimal
• String

Yes, thresholds for multiple instances from same device/instances from multiple devices can be configured simultaneously using Quick Configuration Wizard (QCW).

To do this:

• Go to Settings → Configuration → Quick Configuration Wizard. The QCW allows you to change the configuration such as Device Templates, Managing/Unmanaging devices or associating credentials/monitors to multiple devices at once.
• Select 'Thresholds', and select the 'Performance Monitors' tab.
• Under this tab, make sure that the 'Partition Details' option is selected under Monitors Type. Select the applicable options for 'Protocol', 'Category' and 'Filter by', and click 'Next'.
• In this page, all the Partition Details monitors that match the provided criteria (Protocol, Category, Filter By) are displayed, and you can select the instances for which you want to apply the new thresholds. Select it and click 'Configure' on the top right corner.
• In the following screen, provide the new thresholds for the different alarm statuses, and click 'Apply & Overwrite' to instantly modify the threshold values in the selected instances.

OpManager supports counters from all the sub-classes that are present under the abstract base class 'Win32_PerfRawData'.

To disable alerts for Application Monitors, go to Settings → Monitoring → Application Monitors, and remove the value under 'Thresholds' for the monitors that you no longer wish to receive alerts. Once you're done, click 'Save Configuration' to save it.

If you wish to apply these settings right away to some applications, click 'Apply Configuration' and select the devices of your choice.

If you want to perform thorough monitoring of your device(s), you can easily do so when you have full access privileges (Admin user).

If you have restricted access and you still want to be able to monitor all aspects of your WMI-based device(s), click here to know more on how to configure WMI access for non-admin users.

The latest version of OpManager supports NTLM v1 and v1.1. NTLM v2 is NOT supported..

OpManager supports monitoring of URLs with TLS versions as 1.0, 1.1 or 1.2.

OpManager uses URL templates to associate URL monitors to several devices at once. They are also used to associate URL monitors to devices during discovery itself, using Discovery Rule Engine. With URL templates, you can also use wildcards like $DEVICENAME$ and $IPADDRESS$ in the URL field to customise the monitor for every device.

The following vendors are supported for hardware monitoring in OpManager:

• Cisco devices that support BOTH these MIBs: Cisco-envmon-mib, ENTITY-MIB
• Cisco Nexus devices that run on CISCO-ENTITY-FRU-CONTROL-MIB
• Checkpoint devices that run on CHECKPOINT-MIB
• Juniper devices that run on JUNIPER-MIB
• HP servers that support ALL of these MIBs: CPQHOST-Mib, CPQHLTH-Mib, CPQSINFO-Mib
• Dell servers that support ALL of these MIBs: DELL-RAC-MIB, StorageManagement-MIB, MIB-Dell-10892

Check out our help documentation on prerequisites for hardware monitoring to know more on this topic.

OpManager supports the following scripting languages in its Script Templates:

• Powershell
• Linux shell script
• VBScript
• Perl
• Python

You can simply pass arguments to the script from the Command Line input as in any command, but it is mandatory that you have declared the value for the arguments in the body of the script.

For example, when passing arguments to a Shell script, the command line would look like this:

• cscript ${FileName}.sh a b c d e

where a, b, c, d and e are arguments used in the script body.

You can manually check if your script has been written properly. To do so:

• Copy the script body in a file.
• Save it with a suitable name. Also, decide the location in which the file will be saved, depending on where you are going to execute it.
  • To execute from the local server, save the file in the same device where OpManager is installed.
  • To execute it remotely, save it in the corresponding remote machine, in the path specified in the 'Execution Directory' field.
• To execute the script, open Command Prompt, type the value in the 'Command Line' field and replace the placeholders with proper value.
• Now execute it and get the output. If it displays any error, the custom script itself contains some issue. Try to find and rectify it, and then try the 'Test Script' command again after updating the content in the 'Script Body' field.

Yes, you can choose which files you want to monitor in a folder. In the 'Add' option in Folder monitors under Monitoring section, you have an option called 'All files' which you can enable if you want to monitor all files in the specified folder. If not, you can unselect it and provide the criteria for the files that you want to monitor (criteria can be filename or extension).

Yes, you can also monitor subfolders in any folder. In the Add Folder monitoring template window, you can just enable the 'Monitor Subfolders' option to start monitoring subfolders in the given path.

OpManager supports monitoring log files of all formats, provided that the user under whom the agent is installed in the device has Read permissions for the file to be monitored.

No, any changes to the OpManager server's IP Address will be automatically communicated to the agents on next restart of OpManager.

Updates for the agent file are bundled along with the OpManager installation file during every release. If there is an update available for the agent, OpManager automatically installs it for you. You need not manually update the agent files in your network devices.

No, any port changes done from the UI will automatically be communicated to the agents and need not be manually updated.

Depending on the functionality/mode of the agent, there are three types of agents in OpManager:

1. Idle agent - Agent that has been installed in a device but has not been mapped to any device. This might be because of the following reasons - the agent might be installed in a device already on agentless monitoring mode in OpManager, or the agent might not be mapped to any device yet. You can follow these steps to convert an idle agent to a regular monitoring agent.
2. Monitoring agent - This is the type of agent that is used for agent-based performance monitoring. This means the agent has been installed and properly mapped to a device, and that agent-based monitoring is active.
3. Log file agent - This means the agent installed in the device is only being used for log file monitoring purposes, and NOT for regular performance monitoring.

Yes, it is possible to monitor custom Eventlogs.

• If you wish to monitor custom Eventlogs, you can do so by clicking 'Add' from Settings → Monitoring → Event Logs.
• If you wish to monitor event logs for custom Eventlog files, it is necessary to add the file in OpManager first (using 'Add Custom EventLog rule') and then proceed with the process above to create a new rule.

It is not possible to change the severity for process-related alerts. By default, OpManager raises the alerts from Process Monitors as follows:

• Process down: Trouble
• Threshold violation: Attention

Yes, you can monitor processes with specific paths and arguments. OpManager fetches all running processes from a device and you can select the processes that you wish to monitor.

Yes, OpManager's Process Monitoring Templates allow you to monitor the processes running in any device in real-time.

Yes, you can use Workflows to test a running process and execute remedial actions based on the results.

To understand the 95th percentile calculation, please Click here

To understand the VoIP code, please Click here

To learn how to add more additional fields, please Click here

To learn how to add a new infrastructure to be monitored in OpManager, please Click here

To learn what is BCP, please Click here

To learn how to edit a bulk of links, devices, and shortcuts, please Click here

To learn how to change the color of the unit, please Click here

To learn about SMI, please Click here

To learn how to check whether the response of a URL contains a specific string in OpManager, please Click here

To learn about CLI, please Click here

To learn how to configure monitoring interval in bulk for all devices, please Click here

To learn about the custom fields in OpManager, please Click here

To learn how to delete the custom fields in OpManager, please Click here

To learn about the details of tables storing performance in OpManager, please Click here

To learn why the error "Device already exists" shows up, please Click here

To learn what does the option 'category' under 'criteria' signifies, please Click here

To learn how to change the device type icons, please Click here

To learn the difference between SNMP traps and SNMP monitors, please Click here

To learn why the disk utilization is not showing for some devices, please Click here

To learn how to add custom icons for devices, please Click here

To learn about FC switch, please Click here

To learn how the script monitoring works, please Click here

To learn how frequently should you monitor devices, please Click here

To learn how IPF / ASP license model works, please Click here

To learn how to monitor website URLs in OpManager, please Click here

To learn how to create IPSLA interface links, please Click here

To learn how to use DBMaintenance, please Click here

To learn the minimum monitoring interval configurable script monitors, please Click here

To learn how does the OpManager work, please Click here

To know what will happen if you move router category to a custom category, please click here

When adding a custom SNMP monitor, if you know the OIDs that you are going to use, you can directly provide them in the "Choose SNMP OID" field. But if you are not sure of the OIDs, you can use the built-in MIB browser in OpManager to select your OIDs by using the "Choose OID" button.

• To access the MIB browser, first click Choose OID.
• In the drop-down menu provided on the top-left corner of the OID browser, you can select the MIB file from which you want to select the SNMP OID. You can find a list of default/supported MIBs included in this drop-down.
• If you do not find a suitable MIB, you can also upload a MIB provided by your vendor using the Upload MIB option. Click Upload MIB to browse your files, select the suitable vendor-provided MIB file and click Upload.

Note: Please upload MIBs with RFC2578 MIB Standard to avoid parsing errors.

• You can search for the Object Identifier/Name directly using the OID Browser (Example: .1.3.6.1.2.1.1.3/sysUpTime). You can also browse and select the required OID directly from the MIB tree.
• Once you have selected an OID from the MIB tree, you will be able to view the OID, its Syntax and Description. You can now test the OID to check if the output is desirable by clicking Test OID. This option allows you to review an OID's output, even before adding it to the expression.

After all these steps are done, you can click on Choose OID in the same window to insert the selected OID into the Choose SNMP OID field.

To know what are the prerequisites for monitoring WAN RTT, please click here

To know which IP SLA should be enabled – UDP jitter or RTP or both. What is the difference?, please click here

To know why SNMP monitors are often not collecting data when using SNMP v3 credential, please click here

To know what are the functionalities of OpManager with respect to storage monitoring, please click here

To know what are the supported storage devices and protocols in OpManager?, please click here

To know what does the option 'sysDescr' under 'criteria' signify?, please click here

To know what is a Tape library, please click here

To know what to do when TestScript shows error, please click here

To know when configuring script monitors, what is the ideal 'Timeout' to be configured, please click here

To know what are the URLs supported in OpManager, please click here

To know how to configure VMware Datastore monitors, please click here

To know how to monitor VMware Events, please click here

To know how does VoIP monitoring work in OpManager, please click here

To know how to , please click here

If a device is added under multiple device downtime schedules, chances are that, one of the device downtime schedules under which the device is specified may still be in a running state. Hence, the specific device will continue to remain in downtime.

The Downtime schedule can be stopped at any time and when that is done, the device returns to being in a monitored state.

To stop status polling of all the devices belonging to a category, go to Quick Configuration Wizard > Monitoring Interval and uncheck all the devices categories that you wish to stop status polling.

To stop status polling of random devices in bulk: Go to Inventory, select multiple devices and choose the 3 dots near the generate report icon. Choose Monitoring Interval > Status polling toggle switch and set it to disable.

To know how to generate an Inventory Report of devices or interfaces using Custom Field values?, please click here

Unfortunately that is not possible. To know how to add a user defined Custom Field to your devices or Interfaces,click here

To know if you delete the custom field, will it affect the associated devices, please click here

To know what is a Group, please click here

To know what is a Subgroup, please click here

To know how can a combination of devices and interfaces be placed in a Group?, please click here

To know why you are not able to a create/edit a Group, please click here

To know what is Availability Distribution in a Group, please click here

To know how to , please click here

To know how can group members be automatically added in Group during discovery?, please click here

In OpManager, the IP SLA operations are supported only for Cisco devices using the IP SLA technology. OpManager supports,

• ICMP Echo operation (for WAN RTT Monitor)
• ICMP Path Echo operation (used for Trace Route)
• UDP Jitter operation (for VoIP Monitor)
• Video operation (for Video monitors)

In IP SLA monitors, any intervention in data collection is caused by four primary reasons.

• Possibility of configuring the wrong SNMP credentials.
• Incorrect configuration of the source device.
• Intermitent data collection in OpManager due to scalability.
• Communication error between the source and destination devices.

When an IP SLA monitor is configured in OpManager, the following changes are observed

• The running configuration will be updated with the new monitor configuration.
• Usage of the system resource will increase as the IP SLA monitor at the source consumes a small amount of memory and CPU. Generally, 3-12 KB of memory usage and 1-8% of CPU usage is observed.

This issue occurs due to the incorrect naming of the Vendor. The Vendor name should be specified as 'Cisco' (not Cisco Systems).

This is a device specific issue. Overloading a device may result in not having the resource to support this functionality. Troubleshooting the device can improve the performance and make the necessary resources available for other functionalities.

• sh ip sla application : Shows all types of operations supported
• sh ip sla statistics: Shows complete statistics related to the monitor.
• sh ip sla configuration: Shows configuration related to the monitor.
• sh ip interface brief : To know the IP address that is being used in the monitor configuration.

OpManager has an intuitive GUI to configure an IP SLA Monitor using SNMP credentials. The prerequisites for an IP SLA Monitor Configuration are :

• Source device should be a Cisco device with IP SLA agent running.
• The device should be configured with the correct SNMP credentials with RW community.

The SNMP set operation is done at the device side. This configuration is then applied and saved in the running configuration. Write to memory should be done by the network admin to save the configuration permanently.

OpManager currently supports the following vendor-protocol combinations for IPMI monitoring:

• Dell - SNMP and API
• HP - API
• IBM - SNMP
• SuperMicro- API

When adding a custom SNMP monitor, if you know the OIDs that you are going to use, you can directly provide them in the "Choose SNMP OID" field. But if you are not sure of the OIDs, you can use the built-in MIB browser in OpManager to select your OIDs by using the "Choose OID" button.

• To access the MIB browser, first click Choose OID.
• In the drop-down menu provided on the top-left corner of the OID browser, you can select the MIB file from which you want to select the SNMP OID. You can find a list of default/supported MIBs included in this drop-down.
• If you do not find a suitable MIB, you can also upload a MIB provided by your vendor using the Upload MIB option. Click Upload MIB to browse your files, select the suitable vendor-provided MIB file and click Upload.

Note: Please upload MIBs with RFC2578 MIB Standard to avoid parsing errors.

• You can search for the Object Identifier/Name directly using the OID Browser (Example: .1.3.6.1.2.1.1.3/sysUpTime). You can also browse and select the required OID directly from the MIB tree.
• Once you have selected an OID from the MIB tree, you will be able to view the OID, its Syntax and Description. You can now test the OID to check if the output is desirable by clicking Test OID. This option allows you to review an OID's output, even before adding it to the expression.

After all these steps are done, you can click on Choose OID in the same window to insert the selected OID into the Choose SNMP OID field.

To learn how to delete the in-built custom fields, please click here

To learn how the vendor templates differ from Device/Interface templates, please click here

To understand what you should do if you want only the traffic details of the interface and not it's up and down status, please click here

To learn how to calculate the speed of interface link in OpManager's business view, please click here

To learn how the interface report data is calculated, please click here

To learn how to disable interface status polling for individual / bulk interfaces, please click here

When applying a device template to a device manually to classify into a category, the monitors from the template are not associated to the device, please click here to know why

To learn the output format of script templates, please click here

To know about SysOID criteria and additional SysOID, please click here

To learn when to create a device template, please click here

To learn when to create a device template, please click here

To learn when to create a device template, please click here

To learn more about the RAID technology, please click here

To learn more about the RAID technology, please click here

Some interfaces are unmanaged, please click here to know why

To learn how to set threshold for WAN interface terminating on your firewall, please click here

If a device is moved from a default Device Category to a Custom Category, the device’s Snapshot page will be populated with the properties of the Custom Category. In addition to this, the Category section of the device will reflect the Custom Category.

To learn how to set threshold for WAN interface terminating on your firewall, please click here

If a device is moved from a default Device Category to a Custom Category, the device’s Snapshot page will be populated with the properties of the Custom Category. In addition to this, the Category section of the device will reflect the Custom Category.

Unfortunately it is not possible to create a new category. Custom categories created will have to inherit the properties of any of the default device categories.

Templates supplied by the respective device's vendors are called vendor templates, they can be found in Settings > Configuration > Vendor Templates. Only the templates that are predefined and present out of the box are classified as Device Templates.

To Sync your Device Template with OpManager’s shared Device Template repository, follow the below steps:

• Make sure your OpManager server is connected to an active internet connection and ensure OpManager’s shared device template repository URL is reachable from your OpManager Server.
• If you have enabled a Proxy Server, this information needs to be updated in OpManager to perform the sync operation. To update proxy information, go to Settings > General Settings > Proxy Server Settings and enter the corresponding information.

To Sync your Device Template with OpManager’s shared Device Template repository, follow the below steps:

• Make sure your OpManager server is connected to an active internet connection and ensure OpManager’s shared device template repository URL is reachable from your OpManager Server.
• If you have enabled a Proxy Server, this information needs to be updated in OpManager to perform the sync operation. To update proxy information, go to Settings > General Settings > Proxy Server Settings and enter the corresponding information.

When an alarm is raised corresponding to a business critical device (for e.g, a Web Server), the issue must be resolved immediately. In that case, Alarm Escalation Rules can be defined for the web server to notify the concerned person. To know more, click here

• Go to Settings > Monitoring > SNMP Trap processors.
• Click the 'Load from MIBs' button and select the relevant MIB.
• Select the trap processors that you want to enable, and click 'Save' to apply the changes.
• If you wish to add additional mibs from vendors, you can place those mibs under/mibs.

• Go to the directory where OpManager was installed and navigate to OpManager/Bin/MibBrowser.
• In the MiBBrowser, choose Trap viewer under View.
• Press Start to turn on the Trap viewer. All the traps entering OpManager will be displayed.

Go to Settings -> Tools -> Forward Trap. Click on Add Destination to add a destination host & port number to which the traps must be forwarded. Click on Start Forwarder to begin forwarding the traps to the desired host.

Please note that traps cannot be forwarded to selective destinations.

When a SNMP trap processor is disabled, the corresponding SNMP traps that are received will not be processed.

To change the SNMP trap port follow these steps:

• Navigate to Monitoring-->SNMP Trap Processors
• Click Trap Settings, change the Trap Port and Save.

Traps might not be received in OpManager because of connectivity or port availability issues. If you're not receiving any traps in OpManager, check the following:

• Check if the device that sends the trap is discovered and is not in 'unmanaged' state in OpManager.
• Check if the port specified for traps is not being blocked by your firewall.
• Try pinging the OpManager server from the concerned device to see if it's reachable.
• Also, check if the port assigned for receiving traps is available in OpManager and not being used by any other processes.

When a SNMP trap processor is disabled, the corresponding SNMP traps that are received will not be processed.

To learn why do you still see a device under maintenance even after it's maintenanace is over, please click here

To know if it's possible to place a device in multiple downtimeschedule profiles, please click here

To know if it's possible to update a downtime schedule profile while it is running, please click here

To learn about dynamic variables, please click here

When a device is under planned maintenance, alarms will be generated for the device. In that case, alarm suppression can be used.

Yes, alarms can be suppressed for custom time period. To know more about how to configure it, click here: How to suppress alarms?

The default SNMP Trap port number is 162.

Traps received in OpManager can be viewed lively using the Trap Viewer. The Trap Viewer can be accessed by the following ways:

1. Navigate to Alarms--> Trap Alarms and click on Trap Viewer icon on the right corner.
2. Navigate to Monitoring-->SNMP Trap Processors and click on Trap Viewer icon on the right corner.
3. Click on Tools --> Trap Viewer.

OpManager processes only the traps that have suitable Trap Processors. The reasons as to why you are unable to view Trap Alarms in OpManager and their solutions can be checked here.

The alarm actions available in OpManager are: Add Note, Clear, Acknowledge, UnAcknowledge and Delete.

Syslog alarm wont be raised if:

1. The same syslog message is not generated for the number of consecutive times within the time interval as configured.

   Example: Consider the consecutive times to be '2' and the time interval to be 300 seconds. An alarm will be raised only if the syslog message is received twice within a time interval of 300 seconds.

2. The received syslog does not match the below conditions in the rule created:
   • Syslog Facility
   • Syslog Severity
   • Match Text
   • Host

No, syslog messages received are not normally stored after they are processed. However, syslog messages when received in the form of alarms are stored and can be accessed by going to Alarms -> Syslog Alarms in the OpManager UI.

It is possible to push events from Cisco UCS Manager to OpManager as alerts. This can be enabled using the "Fault Settings" option in the hamburger menu of the UCS Snapshot page. You can choose one of two modes to raise alerts:

1. By Query (Recommended option): Fetches events from the UCS Manager at a specific interval. Optimum interval is 300 seconds.
2. Management API: Enables a dedicated event listener for the UCS device in OpManager, raising alerts in real-time. (Note: This is a resource-intensive option)
3. Click on Tools --> Trap Viewer.

Troubleshootng and fault resolution is an important aspect of network monitoring that helps organizations to maintain high availability for seamless business operations. RCA in OpManager provides a centralized platform to visualize, analyze and correlate IT monitoring data of your devices, interfaces and URLs to accelerate the process of troubleshooting and resolving issues.Learn more.

You have to create a group of interfaces and choose the appropriate group in RCA to troubleshoot issues in interfaces.

By default, only threshold enabled monitors and availability monitors are listed. If you want to list all the monitors, hover the cursor on the filter icon at the top and select Show all monitors.

• You can use this feature to record your findings at any given point. For example, while analyzing the CPU Utilization graph, you see a sudden spike. At that instant, you can click and add your interpretation on the reason behind the sudden spike as a annotation note.
• During your analysis, sometimes you may want to leave midway, at that point you can use the annotation feature and record your interpretations up to that point and save them. Once you come back, the annotation notes will help you to continue from where you left.
• You can also use this when multiple team members collaborate. For example, a network admin opens a RCA Profile and starts the process of troubleshooting, he completes his analysis and records his findings using annotation. Later, a senior-level manager can read the annotation notes, understand the issue and make data-driven decisions for the network.

You need not purchase a separate license. RCA comes bundled with the product from OpManager version 125628 and higher.

By default, the performance on that day is represented in the graph. However, you can use the drop down on the top right corner to select a different time duration.

Yes, please use the edit icon against the RCA Profile that you want to open. Then, click on the Resolved status button to switch to Reopen and continue your analysis.

You can populate up to 20 performance graphs in a RCA Profile

Once an annotation note has been added for a particular monitor in a RCA Profile, the annotation note will appear in all RCA Profiles wherever the same monitor for the same time period is selected.

The RCA data in the Probes are synced to the Central, hence all the RCA Profiles created in the Probes of OpManager Enterprise and MSP editions can be viewed in the Central.

To learn the different types of SMS notifications, please click here

To learn about global and device notification profiles and how can they be configured, please click here

To learn why there are more notification profiles listed than actually created after upgradation from 11600 , please click here

To know why notification emails are getting deleted, please click here

In "Run System Command" profile, execution error or output can be selected to be appended in the alarm message by the user. In the "Run Program" profile, execution error or output is appended by default to the alarm message.

Please follow the below steps to update the receiver email address in a bulk manner for all the notifications profiles:

Go to Settings --> General Settings --> Privacy Settings --> PII Search --> Choose the search type as 'Email ID' --> Enter the old Email ID which you want to change --> It will list all the places where this Email ID is used --> Click on the three dots and enter the new Email ID and click on Update --> This will update the new Email ID in the all the places where the old Email ID was used..

This happens when the alert notification message is more than 255 characters (which is as per SMPP v3.4 standard) but the target SMPP server is unable to retrieve the message with more than 255 characters from payload and deliver to recipient.

Recurring Trigger : This option helps you delay the trigger for the notification profile by a an amount of time in order to provide a buffer time for the alarm to be cleared. If you do not want to trigger the notification profile if the alarm has been acknowledged in the meantime, you can select the 'Do not trigger if alarm is acknowledged' checkbox.

Delayed Trigger : This option helps you re-trigger the notification profile at regular intervals, till the alarm is cleared. For instance, if you set trigger interval as 10 mins and restrict the number of triggers as 5 times, an alert will be notified every 10 mins, for 5 times or till alarm is cleared (whichever is earliest). If the number of triggers is set as empty, then alert will be notified for given interval, till the alarm is cleared. If you do not want to trigger the notification profile repeatedly if the alarm has been acknowledged, you can select the 'Do not trigger if alarm is acknowledged' checkbox.

Email based SMSconverts Emails into SMS messages. For example, OpManager sends an email to your SMS service provider (xxxxxxxxxx@sms.serviceprovider.com). They will convert your Email alert into an SMS compatible format and will push the notification to your intended recipient. This is not the case with SMS as there is no conversion involved and the alert is directly pushed as a text message.

Note: To use these notification profiles, the Mail Server settings and the SMS server settings must be configured.

Workflow is a framework used to automate tasks. It lets the users define conditions, variables and actions for performing tasks. Workflow helps in hassle-free network management and it is completely code-free. To know more, click here.

Workflow Variables are used to append dynamic values in a field of task. For e.g, let us consider a workflow variable $[DeviceName].

• When an alarm is triggered by the unavailability of a device, we can automate troubleshooting process with Ping Device command in workflow.
• Using the DeviceName (for e.g, Windows-7187), the action Ping Device can be automated for that particular device.
• On the other hand, by using the variable $[DeviceName], the same action can be automated for any device, as defined by the user.

• Alarm Trigger - Workflows are triggered based on generated alarms
• Schedule Trigger - Workflows are triggered on a specific time as defined by the user. To know more, click here.

Workflow actions are available for Network Configuration Management (NCM) add-on. To know more,Click here.

Perform the following steps on your Linux machine:

• Open OpManager, click on the Workflow tab.
• Open the Workflow from the given list.
• Click on the Ping Task and click on the edit icon.
• Update the packet size value as 56 bytes.
• Save the Workflow and execute it once again

In OpManager's workflows, there is a separate 'Take Snapshot' task available to make the process of getting VM snapshots much easier, without the help of any third-party tools. Simply go to Workflows → New Workflow, and the 'Take Snapshot' task will be available under the VMware section. You can configure an alarm or a time period as the trigger, to keep making snapshots at particular intervals.

To know how to add multiple devices in the map, please click here

To know how to add devices into a rack, please click here

To know how to add racks to the floor, please click here

To know how to change the rotation type of the floor, please click here

To know how to create a rack, please click here

To know how to customize VM Maps, please click here

To know how to delete a rack from the floor, please click here

To know how to troubleshoot this issue, please click here

To know why you are getting an error message saying 'Device mapping does not exist for this map' please click here

To know how to drill down to a rack from the 3D floor view, please click here

To know how to set up a path/Wall/Aisle, please click here

To know how to set the color of the tile of the floor, please click here

To know how to use Google Maps using JavaScript API, please click here

To know why you are seeing 'Internal Server Error' when discovering Layer 2 map, please click here

To know if the Layer2 maps work only for Cisco switches, please click here

To know why you are seeing the message "Device mapping does not exist for this map, please click here

To know how toset a background image in the map, please click here

To know what is a rack, please click here

To know how to remove a device from a rack, please click here

To know how to resize the floor, please click here

To know how to resize units, please click here

To know how to add shortcuts in Map, please click here

No, currently we do no have this option, however, we will be adding this option sometime in the future.

Google maps API allows geographical visualization of network infrastructure by enabling users to map network devices to real-time geographical locations on google maps. To leverage Google maps API in OpManager, a google map API key is needed. Click here to learn more.

You will have issues in configuring Google Maps due to the following reasons:

• Faulty internet connection
• Google's API key has expired/not enabled. To request a new API key click here

This is due to an error in the API key. Please check you API key and make sure it is enabled.

Yes. The devices configured in Google Maps will automatically be pushed to Zoho Maps.

Discovery mechanism functions with discovery protocols. Choose a discovery protocol that your devices are familiar with as this allows connected devices to discover information about each other.

OpManager supports five protocols read below to know what they are specific for.

CDP - (Cisco Discovery Protocol) Shares information about directly connected CISCO devices hence specifically used to connect Cisco devices.

LLDP - (Link Layer Discovery Protocol) Can also be used for discovering switches provided the respective vendor has issued support for it.

IP ROUTE - This is used as an alternate for CDP to connect Cisco devices.

FDB - (Forwarding Database) Exclusive to switches, FDB table stores information on which port the MAC was leaned on.

ARP - (Address Resolution Protocol) This protocol is supported by all vendors and here communication between two layer2 devices happens via the seed router.

To know what are the MIBs/OIDs used to discover Layer2 map, please click here

To know how to troubleshoot this issue, please click here

Enabling Uplink Dependency will stop the sibling devices from raising an alarm when the parent is down. This helps you avoid multiple device down alerts when the core/parent device is down. This can be performed from two places.

• When you are discovering Layer2 devices, Enable the Set Uplink Dependency option that is present in Discovery > Layer2 Discovery.
• To set uplink dependency to devices that are already discovered and monitored by OpManager, go to Settings > Configuration > Quick Configuration Wizard > Device Dependencies and choose the parent device. Click Manually Group Devices and select the devices that are connected to the parent device and click Associate.

Live status is not visible for the following reasons:

• The device that has been discovered in Layer 2 maps is not imported to OpManager.
• The device that is added to OpManager is not pingable/ is in unmanaged state.

Before checking the link connectivity status and traffic GUI in Business View, make sure:

• There is active signal transmission between the devices present in the Business View.
• There is an active physical connection between the devices that have been connected in the Business View using the connection link.

In Business View, click on the link connecting the various devices to know the connectivity status and traffic. For the sake of simplification, prefer creating a layer 2 map with your devices and then converting them to Business View using the Save as Business View option in Layer2 Maps.

Calculating the speed of the interface link in OpManager's business view: The interface link's speed is the average of InSpeed and OutSpeed of the interface. i.e, Speed = (InSpeed + OutSpeed)/2

For Example: If InSpeed = 200 Mbps; OutSpeed = 300 Mbps. Then, Speed = (InSpeed + OutSpeed)/2 = (200 + 300)/2 = 500/2 = 250 Mbps.

Business view is set to Fit to screen by default. Change this option to Normal Screen by clicking on the square icon near the zooming option. To magnify the view even further, press the "+" icon until a satisfactory size is achieved.

Select a Business View and click on the edit button. Now, press ctrl and choose multiple devices. Click on the Properties icon near the Grid icon and open the Bulk edit option. You can now edit multiple devices and links at once.

A Business view can be embedded within a business view using Shortcuts. To create a shortcut,

• Create a new Business view or open an existing one and click on Edit.
• Click on Add Shortcut icon on the toolbar, configure shortcut properties by assigning the Business view this shortcut icon should represent and click on Save.
• Clicking on this shortcut will open the Business view that it is linked to. You can create multiple shortcuts in a single Business view.

Connections between devices and shortcuts can be made by Links. To establish connection between devices/shortcuts, select a device and choose the Add Link icon from the toolbar.

An alternate option is to drag the link button present at the top right corner of the source device's icon and drop it on the destination device's icon.

To view the traffic/link arrow, open a Business view and click on Edit. Double click on a link connection and enable the Show Arrow option and press Save. Ensure there is traffic in the link for the arrow to be displayed.

The absence of a map legend can be attributed to the following reasons:

• Absence of link connection.
• When there is no traffic available.
• The devices in the business view should not be in an unmanaged state.

To know what is Interface Traffic Load Legend in Business view, please click here

To know what is a business view and what is its purpose, please click here

To know how to create a business view, please click here

To know how to add links between devices/shortcuts, please click here

To know how to create NFA interface links, please click here

To know how to customize your devices/shortcuts, please click here

To know how to delete a link/device/shortcut, please click here

To know how to obtain a business view for layer 2 devices, please click here

To know how to change the line from straight to dotted or curved line, please click here

Go to Settings > Basic Settings > User Management. If you wish to add a new user, click on Add User and fill the role and credentials listed under the User Details tab. If not, select an existing user from the list below. Click on Scope tab. Here, a list of all the existing Business views can be found. Click on Selected Business Views and choose the business views that the user can access.

When the layer2 map is saved as business view (using the 'Save as Business View' option), all devices associated with that layer2 map is discovered and the device and its mapping is saved in the Business View. In such cases, the device and its relationship may not be mapped if the IP address of the device is not valid.

Configuring Business Hour Rules allow IT admins to filter the reports generated on various parameters in a specific time period each day. The time window can be customized as per the business hours of one's organization.

Yes, reports for custom business hours can be generated. To configure custom business hours click here

Yes, reports for custom business hours can be scheduled. To know more on scheduling reports, click here

To know how to generate an inventory report to fetch all field values using custom fields, please click here

To know what is Performance Monitor Data Archiving, please click here

You can find the list of VMs/hosts under a cluster using Nutanix-specific reports available in the Reports section. Just go to Reports → Nutanix, and you'll find all the reports pertaining to Nutanix under this tab.

Graph Display Settings page allows the user to control the granularity of data being used to populate the performance graphs. Based on the time period needed for the graph, the closest value of these three (Detailed/Hourly/Daily) is taken.

For example, consider that the following values have been configured in this page:

• Detailed statistics: 1 to 7 days
• Hourly statistics: 8 to 30 days
• Daily statistics: 31 to 365 days

Now when generating any graph, if the time period is less than or equal to 7 days, OpManager uses the data from the Detailed Statistics table to plot the graph. Similarly if the given report period is lesser than or equal to 30/365 days, the data is fetched from the Hourly/Daily Statistics table accordingly.

For data to be recorded in your report, the monitors selected should be associated with devices and monitoring data should be collected in OpManager. You also need to specify the time period for which a report will be generated.

Check the Apply Criteria tab. The criteria fields are case-sensitive, so ensure that the values entered are as given in OpManager. For example, if the selected field is Device Name, then follow the same casing for that device name as given in the UI.

You can view up to 1000 rows in Preview. However, you can view all the rows in the final report, exported report and the scheduled reports.

You can cover up to 5 performance monitors in a report. However, there is no limitation to the inventory properties (monitors other than performance monitors) that can be covered in a report.

You can create reports covering monitoring data of devices, interfaces, service monitors, URL monitors and alarms.

Default reports usually cover only specific monitoring information. For example, virtual server reports cover information exclusively about your virtual environment. But using advanced reports feature, you can create your own report that covers multiple categories. For instance, you can view monitoring data of your storage devices and servers in a single report. You can specify the monitors based on your preference and create your own report with the required information you want to see.

The Apply Criteria tab filters your report based on the criteria you specify. For example, you can create a report to view the monitoring information of only servers by setting the value for Category field as Server.

The Group by column tab is used to group the data in the report based on certain criteria and also as a sorting mechanism. When there are multiple devices in your report, you can sort them based on a specific monitor fields that you have included. For example, you can sort the list based on the Device Type in ascending or descending alphabetical order.