Dell UPS Management Software not working on Vmware VMA 4.1

Hi Michael,

The recommended choice for ESX 4.0 is to use the UPS optional Network Management Card (H910P part code) because VMWare and USB didn't work in 4.0. I believe there is enhanced support for USB in 4.1 but from what I can see this is still a little dubious.  This is a VMWare question rather than a Dell UPS question.  If you have the option to test with the NMC this would be good.  We can have a look at USB seperately.  Andy

I didn't choose that because first I would get the error

./CuiManager
CuiManager is starting...
Dell UPS Management Software - only for SNMP Device, version: 01.10.0005 2010-06-18
Any command using option "-help" will show it's messages!!
Dell Manager>*************Does this just mean I need an upgrade of the device software?

Does the above problem have to fixed before the ./configure is run?  I still have to run this correct?

What cable to I use from the T610 to the UPS?

I already have all of the VM shutting down gracefully by running the shutdown command but it does not shut down the ESX.  I don't know if that is a ghetto problem or if it is done by the apcupsd.

I am now using a Dell UPS instead of a TrippLite and the SNMP Device error no longer comes up.  Instead, what I get is

[vi-admin@vma ups]$ ./CuiManager
CuiManager is starting...
Invocation of this Java Application has caused an InvocationTargetException. This application will now exit. (LAX)

Stack Trace:
java.lang.UnsatisfiedLinkError: /opt/ups/jre/lib/i386/xawt/libmawt.so: libXext.so.6: cannot open shared object file: No such file or directory
        at java.lang.ClassLoader$NativeLibrary.load(Native Method)
        at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1751)
        at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1647)
        at java.lang.Runtime.load0(Runtime.java:769)
        at java.lang.System.load(System.java:967)
        at java.lang.ClassLoader$NativeLibrary.load(Native Method)
        at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1751)
        at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1668)
        at java.lang.Runtime.loadLibrary0(Runtime.java:822)
        at java.lang.System.loadLibrary(System.java:992)
        at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.awt.Toolkit.loadLibraries(Toolkit.java:1509)
        at java.awt.Toolkit. (Toolkit.java:1530)
        at java.awt.Color. (Color.java:250)
        at manager2.Manager2. (Manager2.java:176)
        at manager2.mautil.masetLanguageCui(mautil.java:1665)
        at manager2.cui.CuiTool.connectRmi(CuiTool.java:71)
        at manager2.cui.CuiManager.main(CuiManager.java:21)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at com.zerog.lax.LAX.launch(Unknown Source)
        at com.zerog.lax.LAX.main(Unknown Source)
GUI-

java.lang.UnsatisfiedLinkError: /opt/ups/jre/lib/i386/xawt/libmawt.so: libXext.so.6: cannot open shared object file: No such file or directory
        at java.lang.ClassLoader$NativeLibrary.load(Native Method)
        at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1751)
        at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1647)
        at java.lang.Runtime.load0(Runtime.java:769)
        at java.lang.System.load(System.java:967)
        at java.lang.ClassLoader$NativeLibrary.load(Native Method)
        at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1751)
        at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1668)
        at java.lang.Runtime.loadLibrary0(Runtime.java:822)
        at java.lang.System.loadLibrary(System.java:992)
        at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.awt.NativeLibLoader.loadLibraries(NativeLibLoader.java:38)
        at sun.awt.DebugHelper. (DebugHelper.java:29)
        at java.awt.Component. (Component.java:545)
        at com.zerog.lax.LAX.showExceptionDialog(Unknown Source)
        at com.zerog.lax.LAX.launch(Unknown Source)
        at com.zerog.lax.LAX.main(Unknown Source)

If I run ./monitor I get

[vi-admin@vma ups]$ ./monitor
 Starting Manager:
Unable to locate the application's 'main' class. The class 'manager2.Manager2' must be public and have a 'public static void main(String[])' method. (LAX)
GUI-
 Done
[vi-admin@vma ups]$

Hi Andy,

are there any news on this?

Is the 4.1 support still beta?

Thanks in advance

regards

I finally got back to this now and I'm seeing a few things that I'm not sure about.  I'm running this on VMA 4.1 with an ESXi 4.1 host.  When testing, I tried manually running upsVIShutdown.sh and got this output:

[vi-admin@vma ups]$ ./upsVIShutdown.sh

: No such file or directory /home/vi-admin/.bashrc

: command not found line 8:

: command not found line 14:

'/upsVIShutdown.sh: line 16: syntax error near unexpected token `do

'/upsVIShutdown.sh: line 16: `do

If I try running it as root, I get something slightly different:

[vi-admin@vma ups]$ sudo ./upsVIShutdown.sh

: No such file or directory /home/vi-admin/.bashrc

I checked and there certainly is a .bashrc dir:

[vi-admin@vma ups]$ ls -al ~vi-admin

total 100

drwx------ 6 vi-admin root  4096 May 12 11:13 .

drwxr-xr-x 4 root     root  4096 Jun 18  2010 ..

-rw------- 1 vi-admin root  3128 Apr 11 10:12 .bash_history

-rw-r--r-- 1 vi-admin root    33 Jun 18  2010 .bash_logout

-rw-r--r-- 1 vi-admin root   176 Jun 18  2010 .bash_profile

-rw-r--r-- 1 vi-admin root   158 Jun 18  2010 .bashrc

-rw-r--r-- 1 vi-admin root 31817 May 12 09:37 ghettoHostShutdown41.pl

drwxrwxrwx 2 vi-admin root  4096 Mar 14 15:00 InstallerData

drwxrwxrwx 3 vi-admin root  4096 Mar 15 13:03 Linux

-rw-r--r-- 1 vi-admin root    70 May 12 09:37 Shutdown.esx4.kominc.local.sh

drwx------ 2 vi-admin root  4096 May 12 11:13 .ssh

-rw-r--r-- 1 vi-admin root  1100 May 12 09:37 upsVIShutdown.sh

drwx------ 4 vi-admin root  4096 Mar 15 14:55 .vmware

[vi-admin@vma ups]$

I have no idea why it's complaining.

Official Dell vSphere 4.1 UPS support now available here:

<ADMIN NOTE: Broken link has been removed from this post by Dell>

Notes on the above:

1) You do not need the 'sudo vifpinit ' command at all from Chapter 7 page 118.  It is deprecated in 4.1

2) Your VMA must be on one of the hosts you are shutting down.  If your VMA is on ESXi host A and you're trying to shut down VMs on hosts B and C only, it won't work properly.  The VMs on hosts B and C will shut down, the VMA will shut down on host A but the hosts B and C will stay up.

Hi ANDYMCDONALD,

i installed the UPS management software but when i started the Cuimanager, did a "search4 -ip 10.128.1.250 -c public", but the command returns:

SNMP cannot bind port: 162

null

Any idea what im missing ?