Opmanager serial

Let us now assume you have purchased a Cisco series router. OpManager does not have a template yet this is as of Build no. Just go ahead and create a new template. These devices cannot be classified under any of the default categories like servers, routers, switches etc, and deserve a separate category.

The managing parameters too differ for this new device type. An ideal situation where you will define a new category view Eg: Sensors and define a fresh device template. You can have different models of sensors from the same vendor in a template or even combine Sensors from multiple vendors in the same template. Device Template : Specify the device type. Vendor Name : Select the vendor.

Click Add New to add a new vendor, and Save. Category : Select the category for the device type. Monitoring Interval : Configure the interval at which the device needs monitoring. Device Image : Select the image for this device type. Select Monitor : Click this option to select the monitors. Edit Thresholds : Click this option to edit thresholds.

Click Create button to create the new device template. Check the SNMP configurations, rediscover the device and re-add the monitors. Troubleshoot as follows:. This error is encountered when the SNMP agent in the monitored device is unable to respond to requests from OpManager within 5 secs.

Check the MIBs supported by the device and configure custom monitors for the required variables from the supported mibs. The above error is encountered when the monitored device is not in the network. Plug the device into the network. The above error too is encountered when the monitored device is not in the network. It is possible that the device is down, or is too busy.

Verify by opening a telnet session to the device from the machine where OpManager is installed and try connecting. Note : This will make the tray icon and splash screen disappear. The error codes and the resolutions are explained below:. Note :You will not find the tray icon and splash screen after you make these changes. This error is encountered when you specify the Username and password for monitoring the machine where OpManager is running.

Do not specify Username and password for the localhost. To resolve the issue, remove the configured user name and password from "Passwords" link in the device snapshot page. This error occurs when the user name provided does not have sufficient access privileges to perform the operation. This error occurs when the WMI is not available in the remote windows workstation. This happens in Windows NT. Such error codes might also occur in higher versions of Windows if the WMI Components are not registered properly.

This error occurs when there is some internal execution failure in the WMI Service winmgmt. The last update of the WMI Repository in that workstation could have failed. This error occurs when WMI is taking up too much memory.

This could be caused either by low memory availability or excessive memory consumption by WMI. Invalid namespace Compiler is not a normal error. It is possible that the desired application using the namespace is not installed properly. For any other error codes, refer the MSDN knowledge base. You will not be able to delete the profile from the client in such case.

So, follow the steps below:. There are quite a few things that you need to take note of when configuring modem-based sms alerts. Here it goes:. For instance, you can get the driver for Nokia from the following link:. This depends on your mobile phone model. In such case you need to download the driver from Nokia's website, which creates a virtual communication port. Other brands have their own cables, usually USB ones.

GSM Modems have a serial port and so you will need a standard serial cable. Reports list only the SNMP-enabled devices. OpManager requires a minimum of 1 hour to plot the collected data. Try accessing the reports after 1 hour from server startup. Assign both the Used Disk Space and Free Disk Space monitors to the devices and wait for two polling intervals and then view the report again. To view the partition-wise reports, you must assign the Free Disk Space and Used Disk Space graphs to the managed devices.

Refer to Assigning a Graph Profile to a Device for details. Assign both the Used Disk Space and Free Disk Space graphs to the devices, wait for two polling intervals and then view the report again. To display this properly, you need to specify the encode type of your agent in the Device Settings dialog. In the device snapshot page, select Device Properties link under Configure tab. Enter the encode type in the Encoding Box and click Save.

Otherwise, the report shows No Data Available. Follow the steps given below:. Configure the below given steps to enable Telnet in IE7 and Firefox. Identifying and troubleshooting network issues has never been this easier. You can use OpManager to identify root cause of network issues and troubleshoot them faster. For further tips to troubleshoot or find resolutions, dig into our online knowledgebase or write to us at our Support Portal. Troubleshoot Guide. Home » Resources » Troubleshooting Guide.

What is Server Management? What is SNMP? What is Virtual Server Management? What is Agentless Network Monitoring? What Is Virtualization? Failed to establish connection with Web Server. Gracefully shutting down.

Error Code Error in applying the OpManager 6. Gracefully shutting down Cause 1 While starting OpManager as 'root' user in Linux platform, the server goes down with the following message "Failed to establish connection with web server. Solution Change the value of the parameter Group in httpd.

Cause 2 If you are using Linux 8. This solution has worked for those using Fedora and Madrake Linux too. Solution Contact OpManager support with the details of the version installed including the Build number and email the license sent to you.

Can't create tables or not all the tables are created properly' error is displayed during OpManager startup Cause The database tables may be corrupted. Solution You can repair the corrupt tables. Error downloading client files from BE Cause This error occurs when the database tables are corrupted. Solution The database must be repaired and OpManager needs a restart. This repairs all the corrupt tables. After it finishes executing, run it once again to ensure all corrupt tables are repaired.

Devices are not discovered Cause This can happen if the ping requests to device get timed out. The DNS Server does not exist. Mapping So many 'Unknown' devices! How do I resolve this problem? How are Servers categorized in OpManager? Some servers are classified under desktops! How to define proper Device Templates?

So many 'Unknown' devices! Causes What is an 'Unknown' device? A device is grouped under 'Unknown' devices category due to the following reasons: Does not have one of these protocols enabled.

In-correct user name and password or a user does not have the required privilege. For instance, WMI expects the user to have domain administrator's privilege. An Anti-virus or a Firewall does not allow OpManager to access. Network configuration that restricts access to some information on the systems in your network. Few security settings in case of Windows environment that dis-allows access. What to do? Despite this, if you face issues, troubleshoot as follows: Do you see a blue star in the device icon on the maps?

The device is still not classified properly? Simply edit the category from the device snapshot page. If SNMP agent is not running on the router, it will be classified as a server or desktop. You can verify this by the blue star appearing on the top left corner of the device icon for the SNMP-enabled devices. To categorize the device properly, start the SNMP agent in the device. Rediscover the device with correct SNMP parameters. If the SNMP agent is running on the router and you still do not see the blue star in the device icon, then check if the SNMP parameters are properly specified during discovery.

If not, rediscover the device with correct SNMP parameters. The router is discovered as a server or desktop if the IP Forwarding parameter of the device is set to false. In the ip table, click ipForwarding node. Similarly, for switches and printers too, enable SNMP in the device and rediscover.

How to define proper device templates to get the devices classified correctly? When should I create new templates? Scenario 1 Let us now assume you have purchased a Cisco series router. Click the Template name to modify an existing one. OpManager is trying to contact the agent with incorrect credentials, such as a wrong password or wrong port. There is a delay and the queries sent by OpManager to the agents in the monitored devices are getting timed out or the devices are no longer in the network.

The particular OID for which the performance monitor is configured is not implemented in the device. Troubleshoot as follows: The possible reasons for the graphs not appearing are: The Resource monitors may not have been associated to this device. Associate the monitors. Check if SNMP is enabled properly on this device.

Check if the Agent is responding using the Mib Browser. If the device has just been added, wait for the first poll to happen. Following are the steps to troubleshoot: In the device snapshot page, scroll down to the monitors list. Click the Edit icon against a monitor. For instance, let us try the CPU Utilization monitor. The instances that respond with these values are noted, and the suffix for the instance can be used to obtain data for that FRU. Now we take the instances that returned 6 or 7 or 13 as the response, and we note down their instance IDs.

Here, A, B, C and E are the instances that provided the required responses. Therefore, these are the instances that OpManager should be able to query to perform hardware monitoring on that device. Now that we know the instance IDs, we can use them to check if we can query the required parameters from that instance. OpManager queries the name, status and value of each instance. So, if you want to perform hardware monitoring on the gives Juniper device, the following OIDs must respond when queried:.

For Supermicro devices supported from OpManager v Prerequisite: Supermicro's Superdoctor agent has to be installed to monitor hardware metrics through OpManager. Hardware Manufacturer -. Cisco Nexus temperature : 1 - Clear 2 - Attention unavailable 3 - Critical not operational Any other response is considered as 'Unknown'.

Prerequisites for Hardware Monitoring It is essential to monitor the hardware components of various critical devices in your network to ensure continuous service availability and network uptime. Where are the hardware tabs?

If you find the hardware tabs missing, follow the below steps: 1. If the sensors are not available, install VMware tools on that host.

Suppress Hardware Alarms: Check if the hardware alarms for the respective devices have been suppressed in OpManager. You can also go to the Hardware tab in the Device Snapshot page and suppress the hardware alarm for a particular device. Check if Hardware status is not updated: For OpManager to monitor the hardware of your devices, check if the following OIDs are responding properly.

This is the instance ID of the temperature sensor. For example, consider the OID.