2013-04-17 11:05 AM
we`re in the middle of a POC with OCBalance.
We`re using Balance 220.127.116.11.
Everything works apart from the vCenter Server Discovery.
Customer is using 2 vCenter-Servers in 2 different Datacenters. Both vCenter Servers were entered for Discovery, LogIn (Credentials) are working.
All ESXi-Servers were detected successfully.
Problem is the Discovery for the VM`s. Balance discovers only 200VM`s out of 700VM`s.
I have following Error Message:
vCenter Server collection failed:
Command Execution Failed Virtual Center Discovery. Collection interrupted for (IP-Adress vCenter-Server).
Uncategorizied exception occurred during JMS processing nested exception is javax.jms.JMSException:java.io.IOException
Thx in advance
2013-04-17 02:49 PM
I just have a few questions about your issue.
2013-04-18 09:55 AM
Discovery Processing (the server will never come out of the state Processing)
Attached 3 Screenshots.
Any help welcome.
2013-04-18 10:43 AM
Thanks, We may be seeing others in the field with a similar issue and using 5.1.
To fully understand the issue, there would need to be an engineering burt/jira opened to investaget further and the diagnostic logs woould need to be provided. I would recommend capturing the diagnostic information . See NetAppKB provided. https://kb.netapp.com/support/index?page=content&id=1013064&actp=search&viewlocale=en_US&searchid=1316617241110
The next Balance version being released version 18.104.22.168 has some fixes in it for vcenter and NAS datastore stats. Not sure if that applies for this issue but would be good to upgrade once its available in 2 weeks or so.
2013-04-18 10:48 AM
i will be onsite on sunday and will capture the recommended LOG`s
i opened a case (2004189626, OC Balance vCenter Discovery Problem).
Customer is using vCenter 5.0, Customer doesn`t use vCloud Director.
LogFiles are attached to the Case