Table 161 Troubleshooting Discovery and Discovery Data Collection (continued)
Scenario | Description | What to do |
|
|
|
When discovering a | An invalid user account was | Enter a valid user account that |
entered | has administrative privileges so | |
correct IP address is entered, |
| it can start WMI. |
but the host does not appear in |
|
|
the topology. |
|
|
The following can be seen on |
|
|
the host: |
|
|
• In Windows Event Manager |
|
|
the WinMgmt.exe process |
|
|
is not running. This process |
|
|
starts WMI.* |
|
|
• In the Windows Event Log, |
|
|
DCOM error messages are |
|
|
shown. |
|
|
|
|
|
*The CIM extension for Microsoft Windows enhances Windows Management Instrumentation (WMI) so that it can gather information from host bus adapters and make the information available to the management server.
IMPORTANT: One way to determine what is happening is to look at the log messages during discovery and getting element details. See ”Viewing Log Messages” on page 74 for more information.
Undiscovered Hosts Display as Storage Systems
On rare occasions, the management server displays undiscovered hosts as storage systems in System Manager. To resolve this issue, provide the host’s world wide name (WWN) as described in the following steps:
1.Determine the host’s WWN. This information is available on the IEEE Standards Association web site at http://standards.ieee.org/regauth/oui/oui.txt.
2.Select Options > Storage Essentials > Manage Product Health, and then click Advanced in the Disk Space tree.
3.Click Show Default Properties at the bottom of the page.
4.Copy the following property:
#hostPortWWNs=
5.Return to the Advanced page.
6.Paste the copied text into the Custom Properties box.
7.Uncomment the hostPortWWNs property by removing the hash mark (#) in front of hostPortWWNs.
712 Troubleshooting