Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

823

December 1st, 2008 04:00

ECC 6.1 / Vm ESX Discovery Error in EGV_Err.log

Hello,

i am trying to discover ESX Hosts over VirtualCenter Host or direcly.
The VM Agent is running on the CC Server itself.
I do get the message:
EGV 12:55:16 EGV 1 P E 4892 (11.02 MB) EGVAgent::RunDiscovery => Failed to send the VMware data to
- store for: "Hostname"

Within the logfile EGV.log the discovery is succeded.
EGV 13:44:02 C P T 6320 (16.48 MB) EGVAgentLog => Creating VMFile: file: vmware-1470.log; folder:
- [VM_ARZ_VMFS_13_NMR] FRA-POD0; fs: /vmfs/volumes/47fcdf08-f024f582-7d83-00096be60d6f
EGV 13:44:05 C P F 7516 (17.02 MB 12.000000K) EGVAgent::ProcessAlert => Checking alert status for
- fra-vm4.frankfur
EGV 13:44:05 C P F 7516 (17.02 MB) EGVAgent::Login => Connecting to Host=FRA-VM4, User=root
EGV 13:44:05 C P T 7516 (17.02 MB) EGVAgentLog => CVimServiceConnection::MakeConnection; connecting
- to https://FRA-VM4/sdk
EGV 13:44:05 C P T 7516 (17.17 MB 152.000000K) EGVAgentLog => MakeConnection; retCode is 0
EGV 13:44:05 C P T 7516 (17.17 MB) EGVAgentLog => MakeConnection; connection succeeded
EGV 13:44:05 C P T 7516 (17.17 MB) EGVAgentLog => CVimServiceConnection::Login; username: root
EGV 13:44:05 C P T 7516 (17.17 MB) EGVAgentLog => CVimServiceConnection::Login; result is 0
EGV 13:44:05 C P T 7516 (17.17 MB) EGVAgentLog => Connection to host FRA-VM4 username root succeeded;
- login succeeded

Within teh ECC Console i just the the manual created Hosts with HBA info. No ESX Tab or VM information.

Any suggestions ?

Thanks in advance

Sascha

55 Posts

December 1st, 2008 05:00

Hello Sharim,

Are you using VMOTION by any chance ?

If yes, might be worth try the following :

Cause #1
Discovery of EsxServer failed because hostname was not changed after VM was cloned from another EsxServer. Hostname must be unique always.

The same database constraint error may occur with VMotion use case in following scenario:
a. discover Esxserver1 that contains VM1
b. discover EsxServer2 that contains VM2
c. move VM1 to EsxServer2
d. re-discover EsxServer2.

Workaround - After the VM migration first re-discover the EsxServer which is the source for VMotion.
i.e. first re-discover EsxServer1 and then EsxServer2 in step d above.

If this would not be the case then, i would suggest to open an SR with EMC and provide agent logs and database dump for further investigation.

Regards
Nimai Sood
EMC Global Services.
No Events found!

Top