A. 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.
A. Please refer to the System Requirements page.
A. Yes absolutely. Install a 30-day trial version and register yourself during installation to avail free technical support during evaluation period.
A. 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.
A. 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.
A. No, it is absolutely free. All you need to do is, ensure you have paid the Annual Maintenance and Support fee.
A. 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.
A. 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.
A. 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.
A. 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.
A. 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 Edition can 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).
A. 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 Integration.
A. Yes, you can install OpManager on any Linux server viz. RedHat 7.x and above, Debian 3.0, Suse, Fedora, Mandrake. However NCM plug–in supports only Windows OS and doesn’t support Linux.
Note: Installing OpManager on a Linux server will disable all WMI based monitors.
A. 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:
A. 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.
A. Yes. Its Central-Probe architecture helps you manage distributed networks from a central location.
A. Refer the detailed system requirements specified here.
A. 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.
A. 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.
A. Yes, it is possible provided you meet the system requirements of both the Central and Probe.
A. Yes it is secured. The Central and Probe communicate xml over HTTPS/HTTP connection.
A. Yes, the Enterprise Edition runs on MSSQL. However it also includes PostgreSQL bundled.
A. 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.
A. Yes, OpManager EE is built for scaling to the monitoring needs of emerging and large organizations.
A. You need to migrate to version 124015 or above to apply Standard license.
A. No. You can only upgrade from OpManager Standard edition to OpManager Professional or OpManager Enterprise edition. Downgrade is not supported.
A. Yes. OpManager Essential edition has now been renamed as OpManager Professional edition.
If you have any questions about OpManager, feel free to raise a support request and we’ll get back to you.
Subinterfaces are listed based on two criteria
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. 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,
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.
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.
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:
1. The SNMP traps in OpManager listen on port 162, so check whether port 162 is available on the server.
2. Please use a real-time packet capture tool to see if there is a response to the destination.
3. Check the SNMP trap settings on OpManager to see if the device is listed on the 'selected' list.
4. 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.
The login credentials would fail if one of the following scenarios occur:
a. AD Authentication:
b. Radius Server Authentication:
Credential association failure occurs when the configured credentials are invalid for the selected device(s).
Auto Discovery happens when:
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,
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 create a rule that automatically applies Notification profile to devices,
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 device status is classified as 'Not Monitored' when
It maybe due to the following reasons:
OpManager will add new devices automatically in the following scenarios:
After creating a custom category, the operator must associate devices to this category. If not, the newly created category will not be displayed.
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 https://www.manageengine.com/network-monitoring//faq/performance-monitor-data-archiving.html?utm_source=inproduct%27.
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.
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.
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:
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. 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:
In this case, you'll have to enable the unmonitored VMs manually. Here's how you can do it:
Yes, it is possible. To start monitoring it:
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.
vCenter or ESX/ESXi Server discovery may fail due to the following reasons:
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.)
Hyper-V discovery / rediscovery fails for the following reasons:
This option allows you to choose if OpManager should automatically discover any new VMs that are created in a Xen environment in your network.
OpManager monitors the status of UCS hardware components such as Fan modules, Ethernet ports, IO Modules, FEX and Adaptor units. Other detailed information such as Relationship charts between UCS components and all available information about the chassis are also stored by OpManager.
Yes, the severity level for VMware Events can be changed in two places.
Device specific:
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:
Yes, thresholds for multiple instances from same device/instances from multiple devices can be configured simultaneously using Quick Configuration Wizard (QCW).
To do this:
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.
Data collection could fail for a device because of the following reasons:
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:
OpManager supports the following scripting languages in its Script Templates:
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
You can manually check if your script has been written properly. To do so:
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.
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.
No, any changes to the OpManager server's IP Address will be automatically communicated to the agents on next restart of OpManager.
Depending on the functionality/mode of the agent, there are three types of agents in OpManager:
Yes, it is possible to monitor custom Eventlogs.
It is not possible to change the severity for process-related alerts. By default, OpManager raises the alerts from Process Monitors as follows:
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.
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.
When the core/parent device is on a scheduled downtime, the status of the child devices will be marked as Dependent Unavailable and their availability monitoring will be paused.
OpManager will resume monitoring the availability of the child devices after the parent device completes its downtime schedule.
You can check the availability status of the child devices at Settings > Reports > Availability and Response > Devices Availability
Unfortunately that is not possible. To know how to add a user defined Custom Field to your devices or Interfaces, click here.
In OpManager, the IP SLA operations are supported only for Cisco devices using the IP SLA technology. OpManager supports,
In IP SLA monitors, any intervention in data collection is caused by four primary reasons.
When an IP SLA monitor is configured in OpManager, the following changes are 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.
OpManager has an intuitive GUI to configure an IP SLA Monitor using SNMP credentials. The prerequisites for an IP SLA Monitor Configuration are :
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:
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.
Note: Please upload MIBs with RFC2578 MIB Standard to avoid parsing errors.
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.
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:
Alarm Escalation is an automated process, used to notify crucial issues to a higher authority when alarms are not cleared in a specified time period, through e-Mail and SMS. To know about configuration, click here.
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 -> 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.
To change the SNMP trap port follow these steps:
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:
When a SNMP trap processor is disabled, the corresponding SNMP traps that are received will not be processed.
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.
When a Trap port is blocked, it will be notified as a message on the top in Alarms -> Trap Alarms page in OpManager's UI.
Traps received in OpManager can be viewed lively using the Trap Viewer. The Trap Viewer can be accessed by the following ways:
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:
a. 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.
b. The received syslog does not match the below conditions in the rule created:
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:
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 SMS converts 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].
Click here for the list of workflow variables and their functions.
Workflow actions are available for Network Configuration Management (NCM) add-on. To know more, Click here.
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.
A. No, currently we do no have this option, however, we will be adding this option sometime in the future.
A. 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.
A. You will have issues in configuring Google Maps due to the following reasons:
A. This is due to an error in the API key. Please check you API key and make sure it is enabled.
A. 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.
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.
Live status is not visible for the following reasons:
A. Before checking the link connectivity status and traffic GUI in Business View, make sure:
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:A. 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.
A. 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. A Business view can be embedded within a business view using Shortcuts. To create a shortcut,
A. 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.
A. 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.
A. The absence of a map legend can be attributed to the following reasons:
A. 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.
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.
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:
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.
There are a few version-related restrictions when it comes to integrating ServiceDesk Plus On-Premise with OpManager. Please refer the table below to know the compatible version of OpManager and SDP.
| SDP On-Premise version | Suggested OpManager version | Compatibility status |
|---|---|---|
| 10513 and below | 11600-124096 | Compatible |
| 11000 - 11127 | 124097 and above | Compatible |
| 11128 - 11137 | 125214 and above | Compatible |
| 11138 - 11206 | 125410 and above | Compatible |
| 11300 and above | 125452 and above | Compatible |
On a general note, it is HIGHLY RECOMMENDED for users with SDP version 11.3 and above to integrate it with OpManager version 125452 and above to ensure the integration runs smoothly and to avoid any sort of compatibility issues.
Known compatibility issues:
| OpManager version | SDP On-Premise version | Compatibility status | Reason for incompatibility |
|---|---|---|---|
| 11600-124096 | 11000 and above | Incompatible | Issue with technician names in "Log a ticket" notification profile |
| 124097-125213 | 11128 and above | Incompatible | Internal issue with "Log a ticket" notification profile |
| 125214-125158 | 11138 and above | Incompatible | Configuration fails, "Internal server error" will be displayed |
| Versions below 125392 (except 125367) | 11200 and above | Incompatible | Configuration failure |
| Any version below 125452 | 11300 and above | Incompatible | Request failure if integration uses v1 REST API version. |
You can send alerts to your private channels via the OpManager-Slack Integration if your OpManager build number is 125340 or greater, since this feature was introduced only in the mentioned version.
If you use older versions of OpManager, you can enable this feature in your installation by upgrading to the latest build.
Administrator users in OpManager can control which channels from Slack should be listed under the Workflow/Notification Profile window.
You can also access the Third-Party Integrations page by clicking on the Plug icon in the top-right corner of the web client.
Once the Slack workspace is integrated with OpManager, all available public channels will be listed automatically under the 'Configure Channels' window. But in case of private channels, only those channels that have invited the OpManager-Slack app will be listed.
In case you use a proxy server in your network to access the Internet, you need to configure the proxy server details in OpManager too since an Internet connection is needed for the OpManager-Slack Integration to work properly.
Once you have the proxy server settings, navigate to Settings → General Settings → Proxy Server Settings in OpManager, click 'Enable' and provide the server details. Once done, you can proceed to configure and use the Slack Integration.
A. The intermediate and root certificates are needed to validate the server certificate provided. The server Certificate along with the intermediate and root certificates forms a complete chain, termed as 'Chain of trust', which establishes the authenticity of the certificate.
A. The URL shown as 'Not Trusted' is a browser specific feature. The reasons for a URL not shown as trusted can be one or both of the following:
- You are using a Self-signed certificate (or) and internal organization CA issued certificate, which is not trusted by the browser, unless you manually import it into the browser's certificate store.
-You are accessing the product with a Hostname or IP that is not specified in the Certificate's Common Name or the Subject Alternate Name (SAN) fields.
A. Self signed certificate works the same way just like any CA issued certificate. The only downside to it is that it will not be trusted by the browsers as it is created by us and not issued by a valid CA, to make this trusted, the certificate can be added to the browser's certificate manager or added to all computers via Windows Group policy. This can be used if you are planning to access the application only within your organization.
To change the self-signed certificate after server migration:
1. Please go to OpManager\conf and check if there is a file named "ITOMSelfSigned.pfx". If so, please delete or move the file to a different location.
2. Now go to Settings -> General Settings -> Security Settings -> and click on "Create" under the "Self-Signed" option. This will create a new Self-Signed certificate with the new host name.