UCMDB and UD Practitioners Forum (Previously CMS)
cancel

ESX Discovery eror on UCMDB

Highlighted
Fevzi
Collector

ESX Discovery eror on UCMDB

i use uCMDB 7.5 and i discovered ESX 3.5(Linux).it doscovered but i didnt find true RAM value, disks are empty and there is 2 CPU on machine but it found just 1.

So.... i dont know ESX discovery out of the box? or what can be the problem??

 

P.S. This thread has been moved from Application Perf Mgmt (BAC / BSM) Support and News Forum to CMS and Discovery Support and News Forum. -HP Forum Moderator

8 REPLIES
Alexander Arkhi
Honored Contributor

Re: ESX Discovery eror on UCMDB

Can you, please, supply communication log?
Fevzi
Collector

Re: ESX Discovery eror on UCMDB

can u tell me the log name ???
Alexander Arkhi
Honored Contributor

Re: ESX Discovery eror on UCMDB

Communication log is not just a log - it's a record file that Discovery creates upon discovery.
* In "Run Discovery" select the job you're running and right-click it.
* Select "Go to Pattern"
* Switch to "Pattern Management"
* Select "Create Communication Log" -> "Always"
* Mark checkbox "Include Results in Communication Log"
* Re-run Discovery
* In the list of "Success" triggered CIs select the destination that was processed by Discovery
* Right-click it
* Select "Debug -> Show communication log" (or something).

Attach the content of an XML as a file here.
Fevzi
Collector

Re: ESX Discovery eror on UCMDB

hi
i attached communication log.

Best regards
Fevzi
Collector

Re: ESX Discovery eror on UCMDB

and there is anotker log
Fevzi
Collector

Re: ESX Discovery eror on UCMDB

there is VM discover by TTY communication log
elcoyote
Collector

Re: ESX Discovery eror on UCMDB

Hello,

as you can see in your last log file, esx 3.5 is not supported : "Error, unsupported server version: 3.5.0".
Take a look at the jython script, you'll see which version are supported.

So you will discover nothing with the job VMWare.

Unfortunately there is no documentation about discovery package. The only way to know what they do is to analyse the jython.

About you're CPUs, if you look how the script discover cpu, you'll see it use the command line "cat /proc/cpuinfo" which return only 1 cpu.
When you said you have 2 cpu, you mean 2 physical CPUs or 1 CPU with 2 cores ?

For the RAM : with ESX server you allocate RAM for OS and RAM available for Virtual Host. So you'll see only the first value.
The script use the command line : "/usr/bin/free -m".

Hope this help.

Steve


Hadas Yehezkel
Regular Collector

Re: ESX Discovery eror on UCMDB

another thing u can do (i got this tip from R&D) in the Jython in the begining of the main body there's a line somthing like: Version=(2.5,3)u can jus add 3.5 and it should work
Hadas
//Add this to "OnDomLoad" event