Frequently asked questions

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:

Note:

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

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

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).

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.

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

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:

• 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.

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.

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

• 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.

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.

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).

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.

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).

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

• 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.

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.

• 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.

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.

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.

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.

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.

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
• HUAWEI Switches that support the following MIB: HUAWEI-ENTITY-EXTENT-MIB
• PALO ALTO firelwalls that support the following MIBs: ENTITY-MIB, ENTITY-SENSOR-MIB​

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

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 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,

• 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.

• 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
• Huawei - SNMP and API
• H3C - SNMP

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.

The error message is displayed if any anomalies are detected within the detailed statistics or historical statistics data tables. These discrepancies may arise due to issues such as errors in table creation, table switching problems, or incorrect data insertion. If the issue occurs, users might encounter difficulties in viewing graphs while using filters, and generating reports. Kindly contact our support team with the SIF in such a scenario.

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.

• 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.

Please note that traps cannot be forwarded to selective destinations.

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.

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.

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

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.

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 (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 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.

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

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

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.

• 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.

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.

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.

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.