advertisement
19
Troubleshooting
OpenManage Essentials Troubleshooting Tool
The OpenManage Essentials troubleshooting tool is a standalone tool that installs along with OpenManage Essentials.
You can use the troubleshooting tool for a wide array of protocol related problems that are often at the root of discovery and alert issues.
This tool provides the following protocol-specific diagnostics to identify the problem with the remote node:
• Database—Fetches all the user defined databases present on the remote box.
• Dell|EMC—Verifies the connection to the Dell|EMC storage devices.
• ICMP—Verifies whether you can ping the remote device from the local box.
• IPMI—Verifies the IPMI protocol to connect to BMC/iDRAC.
• Name Resolution—Verifies whether you can get the resolved name from the local box.
• OpenManage Server Administrator Remote Enablement—This test helps you to verify that Dell OpenManage
Server Administrator's remote enablement feature is working on the managed node (Dell OpenManage Server administrator installed with the remote enablement component). This tool behaves like a Server Administrator
Distributed Web server (DWS) and connects to Server Administrator managed node instrumentation agent using the WSMAN protocol.
To connect successfully, the Managed Node must have OpenManage Server Administrator installed with the
Remote Enablement feature working.
• Port—Verifies whether managed node is listening to the specified port. You can specify 1-65,535 port numbers.
• PowerVault Modular Disk Arrays—Verifies that PowerVault modular disk storage array protocol is used to connect to PowerVault Storage devices.
• Services—Uses SNMP protocol to fetch the running services on the managed node.
• SNMP—Verifies SNMP connection to the remote node, using the required SNMP community string, retries, and time out. First it tries to connect to MIB-II agent and then various other agents to find out the type of device.
Troubleshooting Tool also gathers other agent specific information from that device.
• SSH—Verifies that the SSH protocol is used to connect to managed node.
• WMI—Verifies WMI/CIM connection to the remote node. Default retries and time out values are used internally.
• WSMAN—Attempts to connect to WSMAN client on the remote node. Use this test to verify connectivity problems with iDRAC, ESX, and other devices, which support WSMAN specification. This test will connect to such devices and will also list the exposed WSMAN profiles enabled on the remote device.
Troubleshooting Procedures
Troubleshooting Inventory
Inventoried Linux servers are listed under Non-Inventoried systems, numerous retries does not resolve this.
179
To resolve this issue for the Red Hat Enterprise Linux 5.5, SUSE Linux Enterprise Server version 10 and version 11 installed servers:
1.
Mount the
Dell Systems Management Tools and Documentation DVD
(version 6.5 or later) on the Linux server.
2.
Install srvadmin-cm rpm.
3.
Restart OpenManage Server Administrator 6.5.
4.
Make sure the OpenManage Server Administrator inventory collector is working from the location /opt/dell/ srvadmin/sbin/invcol, run /invcol -outc=/home/inv.xml.
5.
Perform server inventory.
Troubleshooting Device Discovery
If a device discovery is not successful, perform the following steps to troubleshoot and fix the problem:
1.
If the device assigned for discovery is a Dell PowerEdge system, ensure that Dell OpenManage Server
Administrator is installed on it.
2.
To discover Windows devices successfully, configure the SNMP services appropriately. For detailed information on configuring SNMP services on Windows, see
Configuring SNMP Services on Windows
.
3.
To discover Linux devices successfully, configure the SNMP services appropriately. For detailed information on configuring SNMP services on Linux, see
Configuring SNMP Services on Linux .
4.
After configuring the SNMP services, verify whether the SNMP services are responding correctly.
5.
If the device assigned for discovery is Microsoft Windows and you want to use WMI, ensure that the user name and password used in the WMI credentials has the local administrator permissions on the machine that you want to discover. You can use the Microsoft wbemtest utility to ensure that WMI connectivity to the Windows Server is correct.
6.
If the device assigned for discovery is a non-server network device, such as a printer, Dell PowerConnect switch, and so on, ensure that SNMP is enabled on the device. You can do this by accessing the Web interface for a device.
Configuring SNMP Services on Windows
1.
Open a command run prompt and type services.msc to open the Services MMC.
2.
Right-click SNMP Service and select Properties. If you cannot locate SNMP Service, you need to install it using
Add/Remove Windows Components.
3.
Click Security and ensure that Accept SNMP packets from any host is selected.
4.
Under Accepted Community Names, ensure that public (or a community string of your choice) is set. If not set by default, click Add, and type a community string in Community Name. Also select community rights as READ ONLY or
READ WRITE.
5.
Click Traps and ensure that the community string field has a valid name.
6.
In Trap destination, click Add and enter the Open Manage Essential Console IP address.
7.
Start the service.
Configuring SNMP Services on Linux
1.
Run the command rpm -qa | grep snmp , and ensure that the net-snmp package is installed.
2.
Run cd /etc/snmp to navigate to the snmp directory.
3.
Open snmpd.conf in the VI editor (vi snmpd.conf).
4.
Search snmpd.conf for # group context sec.model sec.level prefix read write notif and ensure that the values for fields read, write, and notif are set to all.
180
5.
At the end of the snmpd.conf file, just before Further Information, enter the Open Manage Essentials Console IP address in the following format: trapsink <OPEN MANAGE ESSENTIALS CONSOLE IP> <community string> For example, trapsink 10.94.174.190 public.
6.
Start the SNMP services (service snmpd restart).
Troubleshooting Receiving SNMP Traps
If you encounter a problem receiving SNMP traps, perform the following steps to troubleshoot and fix the problem:
1.
Check for network connectivity between the two systems. You can do this by pinging one system from another using the ping <IP address> command.
2.
Check the SNMP configuration on the managed node. Ensure that you have specified the OpenManage Essential console IP address and the community string name in the SNMP services of the managed node.
For information on setting SNMP on a Windows system, see Configuring SNMP Services on Windows
.
For information on setting SNMP on a Linux system, see
Configuring SNMP Services on Linux
.
3.
Ensure that the SNMP Trap service services are running in the Open Manage Essentials system.
4.
Check firewall settings to allow UDP 161, 162 ports.
Troubleshooting Discovery of Windows Server 2008–Based Servers
You also have to allow the server discovery. By default, the option is disabled in Windows Server 2008.
1.
Click Start → Control Panel → Network and Internet → Network and Sharing Center → Advanced Sharing Setting.
2.
Choose the drop-down arrow for the applicable network profile (Home or Work / Public) and under Network
Discovery, select Turn on network discovery.
Troubleshooting SNMP Traps for ESX or ESXi Versions 3.5, 4.x, or 5.0
Details: To generate virtual machine and environmental traps from ESX or ESXi 3.5 or 4.
x
hosts, configure and enable the embedded SNMP agent. You cannot use the Net-SNMP-based agent to generate these traps, although it can receive
GET transactions and generate other types of traps.
This represents a change in behavior from ESX 3.0.x, in which the configuration file for the Net-SNMP-based agent controlled the generation of virtual machine traps
Solution: Use the vicfg-snmp command from the Remote CLI or vSphere CLI to enable the SNMP agent and configure trap destinations. Each time you specify a target with the vicfg-snmp command, the settings you specify overwrite all previously specified settings. To specify multiple targets, specify them in a single command, separated by commas.
Troubleshooting Problems With Microsoft Internet Explorer
Follow the instructions in this section if you are experiencing any of the following:
• Unable to open OpenManage Essentials using Internet Explorer.
• Internet Explorer displays certificate errors.
• Internet Explorer displays a message to approve the certificate.
• Unable to browse the file system to deploy Server Administrator and system update.
• Unable to display the Device tree for devices.
181
• Unable to install active components.
1.
Open OpenManage Essentials on the client server using Internet Explorer.
2.
Click Tools → Internet Options → Security .
3.
Select Local intranet and click Sites.
4.
Click Advanced.
5.
Type the fully qualified name of the server where OpenManage Essentials is installed.
6.
Click Add.
If the issue persists, there may be an issue with the DNS server resolving the name of the OpenManage Essentials
server. See Resolving DNS Server Issues .
If a certificate error is displayed:
– Contact your system administrator to add the OpenManage Essentials certificate published to the ‘Trusted
Root Certificate Authorities’ and Trusted Publishers’ on domain systems.
– Add the OpenManage Essentials certificate to your ‘Trusted Root Certificate Authorities’ and ‘Trusted
Publishers’ certificate stores using Internet Explorer.
Resolving DNS Server Issues
To resolve DNS server issues:
1.
Contact your system administrator and add the name of the system running OpenManage Essentials to the DNS server.
2.
Edit your host file to resolve the IP of the system running OpenManage Essentials. The host file is located at
%windir%\System32\drivers\etc\hosts.
3.
Add the IP of the system running OpenManage Essentials to the Local intranet sites in Internet Explorer.
NOTE: You cannot remove the certificate errors unless you use the fully qualified name of the server running
OpenManage Essentials.
Troubleshooting Map View
Question: Why is the Map View feature not available?
Answer: The Map View feature is available only if you have discovered any Dell PowerEdge VRTX CMC with an
Enterprise license, using the WS-Man protocol. If the PowerEdge VRTX CMC with an Enterprise license is discovered using the SNMP protocol, the Map View feature is not available. Rediscovering the PowerEdge VRTX CMC using the
WS-Man protocol is required, if the Map View tab is not displayed in the device details portal of a Dell PowerEdge VRTX
CMC with an Enterprise license.
Question: Why am I unable to add a particular device on the map?
Answer: Only PowerEdge VRTX devices with an Enterprise license can be added to the map.
Question: The map does not load with the MapQuest or Bing map provider. What should I do?
Answer: This indicates a problem with the Internet connectivity.
• Verify if you are able to connect to the Internet through the browser.
• If the system connects to the Internet through the proxy:
– For MapQuest map provider — Configure the proxy settings in the OpenManage Essentials Preferences
→ Console Settings page.
– For Bing map provider — Verify if you configured the proxy server settings in Internet Explorer.
• Verify if you are able to access the MapQuest website.
Question: Why is the map loading slowly?
182
Answer: The map may load slowly as it requires more network bandwidth and graphic processing capability compared to normal browsing. Constant zooming and panning on the map may also slow the loading of the map.
Question: Why I am unable to locate an address using the search bar or Edit Device Locations dialog box?
Answer: There may be a problem with your Internet connection or the map provider may not be able to resolve the address.
• Verify if you are able to connect to the Internet through the browser.
• If the system connects to the Internet through the proxy:
– For MapQuest map provider — Configure the proxy settings in the OpenManage Essentials Preferences
→ Console Settings page.
– For Bing map provider — Verify if you configured the proxy server settings in Internet Explorer.
• Try to provide a variation of the address you provided. You can try providing a complete address. Abbreviations such as state, country, airport code, may have an unexpected result.
Question: Why cannot I use one map provider on the Home portal and another on the Devices portal?
Answer: The Map View available through the Home portal and the Devices portal are synchronized. Changes to the
Settings or device locations on the Map View are affected on both the portals.
Question: How can I enhance the Map View experience?
Answer: Improving the network bandwidth accelerates the loading of the map. A more powerful graphic card enables faster zooming and panning capability. When using the MapQuest provider, the map is rendered better if OpenManage
Essentials is launched on the management server.
183
184
advertisement
Related manuals
advertisement