Users Guide

Troubleshooting Your Application | Troubleshooting
OMNM 6.5.3 User Guide 697
Multi-NIC Host Fails to return to the portal
—When you click the Return to ... link from
Control panel, some unexpected URL appears in the browser. To see the root of this problem,
go to
Portal > Portal Settings and compare the Virtual Host entry to the application server’s
IP address. If they are different, then DNS has two different IP addresses associated with the
same hostname. OpenManage Network Manager needs an unambiguous IP address and
associated hostname for both application server and client.
Workaround(s): 1. Use a local host file and map the IP selected during installation to the
hostname. 2. Set the DNS server to only resolve the selected IP address to this machine’s
hostname.
• Installer fails immediately with error
Create Process failed ==> %1 is not a
valid Win64 application.
Solution: Change the value of the %TEMP% environment variable. Change the default value
of the
%TEMP% environment variable to another path you have already configured, for
example:
C:\Temp . Use the Windows System Tools menu to do this.
Troubleshooting Flow
As part of the troubleshooting process, you can often determine the culprit for problems by a
process of elimination. The following questions may help determine what is the real issue:
Discovery/Resync
See Communication Problems on page 701, Preventing Discovery Problems on page 701 and
Discovery Issues on page 702
• Can you ping the device you are having difficulty discovering? If you can ping them, and have
discovered them, but ping still does not work from within the application, do the devices have
an ICMP management interface when you right-click >
Edit them? If not, add the interface
and resync.
• Is your system permitted access to the device (on the Access Control List)?
• Are firewalls blocking access to the device(s)?
NOTE:
The command service iptables stop turns off the Linux firewall. Turning it off temporarily is
recommended when you first install.
• Is any other software on the application server/mediation server host causing a port conflict?
(Uninstall it)
• Is SNMP is configured on the target device and read/trap, write community strings? Is SNMP
correctly set up? (check with Network Tools and MIB browser or a tool like iReasoning’s MIB
browser)
• Is Telnet or SSH configured on the target device and can you Telnet/SSH to the device
through a command line shell or an application like puTTY?
NOTE:
Some devices support only SSH v2. Consult release notes for specifics.
• Are authentications created in the Authentication portlet with protocols and passwords set
correctly, with adequate timeout and retries configured for your network’s latency?
• Are Discovery Profiles using the created authentications?
• Does device fail to resync after deployment?
wait up to a minute before resync as SNMP agent is not enabled yet on the device.