CJRNZ
Contributor
Contributor

VMA Integration with HDS Storage Tools

I have a VMA instance configured (4.0.0-161993) and have pointed to each of my Vcenter servers (x2) using the "vifp add server" commands and the authentication pass through to ESX hosts works fine. Now when attempting to add the instance as a virtual server to HDS device manager, I receive an error saying:

"The virtualization server or the virtualization-server management program could

not be detected. The wrong IP address or protocol might have been specified, or

the virtualization server or the virtualization-server management program might

not be in a normal state." (KAIC10663-E)

Has anyone else come across similar issues?

0 Kudos
9 Replies
oicyurmt
Contributor
Contributor

You mention configuring the target servers but have you enabled the vMA for SMI-S/CIMOM comms?

needs ...

- the network ports need to be open (default tcp/5989)

- CIMON interface configured/running (vmware-smis-setup.pl)

0 Kudos
CJRNZ
Contributor
Contributor

Thanks for that, however when running " sudo /etc/vmware/vmware-smis-setup.pl " I receive the following output in the /var/log/vmware/vmware-smis-setup.log:

Starting SMI-S setup at Wed Oct 6 00:59:08 2010...

checking availability of /etc/vmware/vmware-cim-config.xml...

checking availability of /var/pegasus/cimserver_planned.conf...

Checking and stopping Openwsman before setup

Stop Openwsman for setup

Failed to stop Openwsman. Exiting Setup.

Finished.

While attempting this change I also entered the port requirements as per the command below:

iptables -I INPUT -p tcp --dport 5989 -j ACCEPT && iptables -I INPUT -p tcp --dport 5988 -j ACCEPT && /etc/init.d/iptables save

Any ideas?

Thanks in advance.

0 Kudos
oicyurmt
Contributor
Contributor

Re.

Failed to stop Openwsman. Exiting Setup

Yep seen that - sorry can't be specific but you will have to cleanup some underlying processes

Re:

iptables -I INPUT -p tcp --dport 5989 -j ACCEPT && iptables -I INPUT -p tcp --dport 5988 -j ACCEPT && /etc/init.d/iptables save

I think you are over thinking the problem.

My comment re these ports was to do with the network firewalling.

Inside the vMA the smis-setup will handle the port setup as needed.

Notes:

Prior to the setup ...

$ netstat -an | grep 598

(= nothing)

After vmware-smis-setup ...

$ netstat -an | grep 598

tcp 0 0 :::5988 :::* LISTEN

tcp 0 0 :::5989 :::* LISTEN

$

Checking when HDvM doing discovery/refresh shows (AS AN EXAMPLE) ....

$ netstat -an | grep 598

tcp 0 0 :::5988 :::* LISTEN

tcp 0 0 :::5989 :::* LISTEN

tcp 0 0 ::ffff:192.168.0.233:5989 ::ffff:192.168.0.103:1881 ESTABLISHED

tcp 0 0 ::ffff:192.168.0.233:5989 ::ffff:192.168.0.103:1880 ESTABLISHED

tcp 0 0 ::ffff:192.168.0.233:5989 ::ffff:192.168.0.103:1882 ESTABLISHED

tcp 0 0 ::ffff:192.168.0.233:5989 ::ffff:192.168.0.103:1877 ESTABLISHED

tcp 0 0 ::ffff:192.168.0.233:5989 ::ffff:192.168.0.103:1879 ESTABLISHED

tcp 0 0 ::ffff:192.168.0.233:5989 ::ffff:192.168.0.103:1878 ESTABLISHED

$

0 Kudos
CJRNZ
Contributor
Contributor

I understand this, however the command still doesnt work. It prompts for a password (the vi-admin password) followed by user name & password (a read only account I have created on vcenter) which I enter - it then proceeds to output the error mentioned previously. Any idea?

0 Kudos
CJRNZ
Contributor
Contributor

    • I have started fresh with the latest build of VMA and configured as per the manual.

My latest update on this issue is as follows (same when running the .pl):

$ sudo /etc/vmware/vmware-smis-setup.sh

Stopping Openwsman before SMI-S setup!

Stop Openwsman for setup ?yes

Failed to stop Openwsman. Cannot continue with setup.

You must stop Openwsman before setup by executing:

sudo /etc/init.d/wsman stop

Log for this setup can be found at /var/log/vmware/vmware-smis-setup.log.

$ sudo /etc/vmware/vmware-smis-setup.pl

Password:

Can't load '/usr/lib/perl5/site_perl/5.8.8/libvmatargetlib_perl.so' for module vmatargetlib_perl: libtypes.so: cannot open shared object file: No such file or directory at /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/DynaLoader.pm line 230.

at /usr/lib/perl5/site_perl/5.8.8/VMware/VmaTargetLib.pm line 10

Compilation failed in require at /etc/vmware/vmware-smis-setup.pl line 11.

BEGIN failed--compilation aborted at /etc/vmware/vmware-smis-setup.pl line 11.

0 Kudos
TheEsp
Enthusiast
Enthusiast














0 Kudos
CJRNZ
Contributor
Contributor

Hi TheEsp,

I am currently running with Device Manager 6.4.0-01 and VMA 4.1

Did you run the vmware-smis-setup.sh or .pl script also?

To date I have defined the basic network requirements, set the Vcenter servers, configured AD auth and tested the pass through auth to the ESX hosts.

Still no luck when adding a "Virtualization Server" to Device manager though with non-secure checked.

CJRNZ

0 Kudos
TheEsp
Enthusiast
Enthusiast

Hi CJRNZ

It was awhile ago when I set it up , to be honest the documentation that HDS had written at the time , was very limited.

I ended up working along side a HDS PSO and we wrote our own documentation/notes on how to get it to work.

One thing to note is , if you have already loaded the device manager agents on your ESX hosts , then remove those hosts from Device Manager , I then added the ip address of each ESX host , in the cluster , and they came through.

I also disabled the vma's firewall /etc/init.d/iptables stop.

I am currently in the process of setting it up again ,so I'll keep you posted on how things go.

David

0 Kudos
HDS201110141
Contributor
Contributor

Hi David,

Any chance to grabe your hds integration documentation ?

Thx

Ben

0 Kudos