Users Guide

Troubleshooting Your Application | Troubleshooting
702 OMNM 6.5.3 User Guide
WMI
If you are discovering WMI systems on your network, the following may be helpful.
1 Launch the wmiutil.exe command line tool from \owareapps\wmi\bin\"
2 You need to supply a user and a password along with an IP or hostname
Ty pin g
wmiutil.exe with no arguments returns launch the WMIUtil User Interface.
c:\Dorado\owareapps\wmi\bin\wmiutil.exe -user <user> -password <password> -
host <IP or Hostname>
Ty pin g wmiutil.exe ? at a command line returns what parameters are available for the
command line version.
NOTE:
Even if you do not need a domain to log into your WMI device, the graphic interface for this utility does
not work if the domain field is blank. Any content makes it work correctly.
See WMI Troubleshooting Procedures on page 715 and Additional WMI Troubleshooting on
page 723 for additional details.
Discovery Issues
Discovery may fail if its authentication or network parameters do not match the configuration of
devices discovered. Here, the results panel typically displays a message like
No Devices were
detected with selected Discovery Parameters
. Use the Inspect function in
Discovery Profiles to validate credentials entered.
Some additional sources of Discovery issues, and their solutions:
• Equipment with management IP Addresses in the selected subnet, range, and so on does not
exist. Correct the selected range and retry.
• The equipment in the selected range has already been discovered.
Managed devices can only be discovered once. Those devices that have already been
discovered appear in the Discovery Results section of the Discovery Wizard. Update the state
of previously discovered devices by selecting
Resync from the right-click menu. If you want to
re-discover these devices, delete them from the Managed Resources portlet
• The SNMP community strings/authentication on the equipment do not match the default
values used by this application. Correct the SNMP authentication selected for discovery.
• Discovery finds a device, but features like Direct Access, Backup and Actions do not work.
Solution: The device likely has a correct SNMP authentication, but an incorrect CLI (Telnet/
SSH) authentication. Either re-run the Discovery Profile after deleting the device and
correcting the authentications, or right-click to edit the device and add the CLI
authentication and management interface, then right-click to resync the device.
Note that you must log into the device as a user with enough permissions to accomplish all
discovery and other tasks. If you log in as a user with limited permissions, then discovery
results reflect those limits.
NOTE:
The Inspect feature of the Discovery wizard lets you validate authentications.
Alternative: The device is not supported by your current license or driver set. To request
support, use the MIB browser to navigate to RCC1213 ifTable details, and export/save this