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.
Note:Installing OpManager on a Linux server will disable all WMI based monitors.
The following CVE id's are not applicable to OpManager:
Subinterfaces are listed based on two criteria:
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:
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.
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.
Follow these steps to check for potential issues:
a. AD Authentication:
b. Radius Server Authentication:
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.
The device type may not be applied to the device because
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:
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:
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.
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.
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:
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:
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.
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.
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.
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:
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:
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:
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:
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:
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:
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
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.
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
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.
To Sync your Device Template with OpManager’s shared Device Template repository, follow the below steps:
To Sync your Device Template with OpManager’s shared Device Template repository, follow the below steps:
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:
Traps received in OpManager can be viewed lively using the Trap Viewer. The Trap Viewer can be accessed by the following ways:
Syslog alarm wont be raised if:
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.
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:
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..
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 (firstname.lastname@example.org). 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.
Workflow Variables are used to append dynamic values in a field of task. For e.g, let us consider a workflow variable $[DeviceName].
Perform the following steps on your Linux machine:
You will have issues in configuring Google Maps due to the following reasons:
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.
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: 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.
A Business view can be embedded within a business view using Shortcuts. To create a shortcut,
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.
The absence of a map legend can be attributed to the following reasons:
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. On a general note, it is HIGHLY RECOMMENDED for users with SDP version 11.3 and above to integrate it with OpManager version 125489 and above to ensure the integration runs smoothly and to avoid any sort of compatibility issues.
|SDP On-Premise version||Suggested OpManager version||Compatibility status|
|11212 and above, 11300 and above||125457, 125473, 125476, 125489 and above||Compatible|
|11138 - 11206||125410 and above||Compatible|
|11128 - 11137||125214 and above||Compatible|
|11000 - 11127||124097 and above||Compatible|
|10513 and below||11600-124096||Compatible|
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.|
If you are an Administrator in OpManager, navigate to Settings → General Settings → Third-Party Integrations → Slack, click 'Configure Channels', select the channels you want to list and click Save.
You can also access the Third-Party Integrations page by clicking on the Plug icon in the top-right corner of the web client.
|SDP MSP Version||OpManager Version||Compatibility status||Reason for incompatibility (If Incompatible)|
|Less than 10600||Compatible with all versions of OpManager||Compatible|
|Version 10600 & above||Version 125614 and above||Compatible|
|Version 10600 & above||Less than version 125614||Incompatible||Due to certain API depreciation on SDP MSP and a new requirement where OpManager need to be configured on SDP MSP mandatorily.|
NOTE: Asset sync from OpManager MSP is only supported for SDP MSP version 10525 and above.
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:
To change the self-signed certificate after server migration:
|File name of blacklisted files||File path of blacklisted files|