
Table 30 Troubleshooting Discovery and Discovery Data Collection (continued)
Scenario | Description | What to do |
|
|
|
| There is a problem with | Try Discovery Data Collection |
| Discovery Data Collection from | again. |
| the host. | 1. |
| If the steps provided do not | |
|
| |
| work, see ”Link Between a |
|
|
| |
|
| |
|
| |
The host appears managed, |
|
|
but it is not connected to the |
|
|
switch. |
|
|
|
|
|
| The switch has not been | Try discovering the switch |
| discovered. | again. |
|
| |
|
| |
The element appears |
| 1. |
|
| |
discovered, but a connected |
|
|
switch does not appear. |
|
|
|
|
|
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.
406 Troubleshooting