Once you have filled out the obligatory information you will be able to create your support incident and will receive a Service Request ID. Rather than waiting for Research In Motion to contact you, I would suggest calling (877) 255-2377 (toll free) or (519) 888-6181. Select option 2 for technical support, followed by option 4 so that you can speak with a technician. Remember, this is a one time deal so use it wisely.

After buying the software you can download it immediately, I downloaded it on my vCenter server. Once I had it downloaded I opened the zip file and found multiple folders for different operating systems: ESX, ESXi, Windows, and Server 2008 Core. This client is running VMware vSphere 4 so I will be using the file in the ESX folder.

Open your vSphere Client and browse to a datatore and upload the pcns224esx.tar.gz file

SSH into the host and browse to your datastore which can be local or on shared storage.

cd /vmfs/volumes/<GUID>

Move the file to your home directory.

mv /home/<username>

Extract the compressed file.

tar -zxvf pcns224esx.tar.gz

Start the installation.

./install.sh

Press any key to view the license terms and space bar until you are done then type "yes" to agree to them. If you have only one UPS select 1 for the number of instances, if you have more select the appropriate number. I allowed the software to use the default installation directory and the bundled JRE which is version 1.5 update 18.

------------------------------------------------------------------
PowerChute Network Shutdown v.2.2.4 for VMware
Copyright (c) 2009 Schneider Electric, All Rights Reserved.
------------------------------------------------------------------

OS=Linux

Initializing ...

Press any key to display End User License Agreement

Do you agree to the above license terms? [yes or no]
yes

Please enter the PCNS instance number [1|2|3] or press enter to use default value of 1:

1 PCNS instance(s) will be installed.

Please enter the installation directory or press enter to install to the default directory (/opt/APC/PowerChute):

Are you sure you want to install PCNS to /opt/APC/PowerChute [Yes|No]?
Yes
Creating /opt/APC directory ...
PCNS will be installed to /opt/APC/PowerChute
Copying the installation files ...
Extracting PCNS files ...
PCNS is extracted to /opt/APC/PowerChute

Please enter java directory if you want to use your system java (example:/usr/local/bin/jre/jre1.5.0_18) or press enter to install the bundled Java:

Copying jre to /opt/APC/PowerChute/jre ...
Extracting jre to /opt/APC/PowerChute/jre ...

java version "1.5.0_18"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_18-b02)
Java HotSpot(TM) Client VM (build 1.5.0_18-b02, mixed mode, sharing)

JAVA_DIR=/opt/APC/PowerChute/jre/jre1.5.0_18

Configuring startup files ...
Startup script=/etc/rc.d/init.d/PowerChute
Updating Linux symbolic link ...
2010-08-21 05:00:57 (28215) WARN : OpenPort: Opening a previously opened port: 3052.
2010-08-21 05:00:59 (28749) WARN : OpenPort: Opening a previously opened port: 3052.
2010-08-21 05:01:00 (29226) WARN : OpenPort: Opening a previously opened port: 3052.
Configuring uninstall script ...

Completed.
Please run the PCNSConfig.sh script located within the PCNS installation directory to complete the installation.

After the installation has finished browse to the installation directory.

cd /opt/APC/PowerChute/group1/

Run the configuration file.

./PCNSConfig.sh

It will ask you to select the IP address that you want to register with the UPS. In my case I selected #3 which is the service console of the host, the other two are the iSCSI connections. It will also ask you for your subnet and how many UPS you have and the type.

It will want the IP address of your UPS, the port being used, the username, the password, and the authentication phrase. It did not like the password I entered, as it cannot be empty and no more than ten characters which mine was. I logged into the UPS and changed the password to something shorter that it would like.

If you have not configured an authentication phrase log into your UPS, select the UPS tab, select PowerChute, then configure. Also select the configuration link then the shutdown link and change the low battery duration to 5 minutes.

You should then be able to register with the UPS and start the service. Once you have done that you can browse to https://IP Address:6547 and login with the username/password you used in this configuration file.

--------------------------------------------------
PowerChute Network Shutdown Configuration Utility
--------------------------------------------------

Press Ctrl + C at anytime to abort.

[1]: 192.168.131.9
[2]: 192.168.130.9
[3]: 192.168.0.228

Please select the local host IP address to register [ 1 - 3 ]: 3

Please enter the subnet mask of the local host IP address to register or just press enter key to use default subnet mask [255.255.255.0]:

Configuring PowerChute Network Shutdown ...

[1]: Configure for a single UPS device
[2]: Configure for a parallel Silcon UPS / Smart-UPS VT / Galaxy system
[3]: Configure for multiple Smart-UPS or Galaxy devices
[4]: Configure for multiple Symmetra devices

Please select the appropriate configuration type (1) [ 1 - 4 ]: 1

Management Card IP: 192.168.0.210
Management Card Port # (80):
Administrator User Name: apc
Administrator Password: [ MASKED ]
Authentication Phrase (default): [MASKED ]

Setting Summary:

Management Card IP: 192.168.0.210
Management Card Port #: 80
Administrator User Name: apc
Administrator Password: [ MASKED ]
Authentication Phrase (default): [ MASKED ]

Do you wish to register these settings [ Yes | No | Abort ]? Yes

Registering PowerChute Network Shutdown with the management card ...
PowerChute Network Shutdown registration completed successfully.

Do you wish to start the PowerChute Network Shutdown service [ Yes | No ]? Yes
PowerChute Network Shutdown service started.

Configuration completed.

After the update I was unable to reach the web page to administer the application (although you can't really do anything through the page). I tried a reboot of the system which did not help either. At that point I started Googling to see the problem was  and how I go about fixing it, however I was not able to find anything useful.

There are a few posts on the VMware Communities about updating this appliance, this one has a workaround to VMware Tools breaking, by creating a symbolic link to the newer version of libssl and libcrypto, he did not comment on any issues accessing the webpage. As I sit here typing this article I can't say I tested the functionality of Data Recovery after the update, only the web page functional. However with the fact that VMware Tools breaks as reported in the post linked above and the fact that the web server breaks in the process I can't say I am comfortable with this updated product in a production environment.

With that said I am disappointed with VMware in regard to this particular product. While I know it is not their flagship software it can be purchased and is also included in every version of vSphere above standard as well as in their Essentials Plus bundle. I believe that a call to VMware support would also be a waste of time knowing that their response would be updating the appliance is not supported therefore support would not be given.

I would suggest to VMware that in their next release of Data Recovery that they use their own repositories rather than the official CentOS repos. This way they would then be able to release updates to the appliance that would not break it in the process. It is unacceptable these days to to leave production machines unpatched and force end users to troubleshoot on their own to figure out workarounds to problems that should not exist in the first place.

This post is purely subjective but I wanted to write it anyways, feel free to comment if you agree or disagree with my thoughts here.

Out-of-Band Management

I have used out-of-band management to save me multiple times, because I work mostly with Dell that safety is the Dell Remote Access Controller (DRAC). I have used their 4th, 5th, and 6th (current) generation. I have also used HP's Integrated Lights-Out (iLO) in their ProLiant G3, G5, and G6 servers to save me time/trouble as well. While both provide the same functionality I feel that Dell has a better product that is easier to use and manage. Below are some reasons why I say this based on my experience.

• IP Configuration - You can assign an IP during POST on both systems, however with Dell you are able to use OpenManage Server Administrator to make this change. HP does have a Windows based application called HP Lights-Out Online Configuration Utility however this is just another software that has to be loaded on a system.

• Keyboard input - For some reason HP requires you to assign hot keys to function keys or key combinations. Without doing this you would be unable to press f9 for example while connected to the console. With Dell the keyboard interaction is much more seamless and does not require you to pre-define hot keys.

• Virtual media - This feature allows you to mount an ISO so that you can boot from it or load software from it. For example you would be able to install VMware vSphere remotely without ever having access to the server. While I have had problems with the DRAC on this point I have had the iLO totally fail me all together.

• User management - If you lose, forget, or don't know the username/password to log into the interface you can reset it with Dell OpenManage Server Administrator. With HP you have to use a command line software in conjunction with an XML file that defines configurations

• Licensing - Dell is a hardware product that you buy whereas the iLO comes installed and needs to be licensed. Dell adopted HP's implementation in their current line of server with the iDRAC Express which provides the functionality that the unlicensed iLO provided. You still must buy the iDRAC Enterprise to get console access but there is no license to purchase or manage.

Management Software

Dell server management software is called OpenManage Server Administrator. Through OpenManage you are able to manage all of your hardware, DRAC, and storage controllers and arrays, view system information, and setup alerting. It also provides SNMP management functionality so that you can remotely monitor the system and remediate issues when they arise such as disk or power supply failures.

HP's System Management Homepage provides much of the same functionality, however there is also generally a ton of other software installed for management of the system. For example if you look in the add/remove programs or startup menu of a HP server you will find much more installed which means much more to update. While HP does provide their support pack to update everything at once I find that their management software is very bloated and cumbersome.

Furthermore doing a P2V of a HP server is so much more time consuming compared to a Dell server. After the P2V process there is more software to uninstall, NIC teaming software that glues itself into the TCP/IP configuration, files scattered everywhere on the hard drive (root, program files, system32) where as with Dell you simply uninstall OpenManage and any other unnecessary drivers.

Serial Numbers

Dell uses a service tag for their serial numbers, it is a short alpha numeric string that can be inputted on their support site to identify your system, check warranty status and download software. This serial number is also what you provide when you call in for technical support or need to renew a warranty. HP on the other hand uses a serial number and part number. The warranty checker on HP's website requires both of these to check the warranty status. As far as I know you are not able to look up your HP system by the serial number either.

Price

Dell is always less expensive than HP when buying direct or through a large distributor like CDW. While I really like my CDW rep and would love to give him more business I refuse to buy HP whenever possible.

Design

In my experience Dell servers have been easier to get into and work with, HP require a torx screw to remove or get into certain areas while Dell uses standard Phillips screws.

On a related note, I do not like HP servers nor am I a fan of their iLO.

Environment
BlackBerry Enterprise Server version 5.0
BlackBerry Monitoring Service version 5.0

Overview
After installing or upgrading to BlackBerry Monitoring Service 5.0, the BlackBerry Monitoring Console service will not start up.  When attempting to start the service the following error is observed:

The Tomcat logs for the BlackBerry Monitoring Service record the following entries:

[2009-12-13 13:22:06] [info] Procrun (2.0.3.0) started
[2009-12-13 13:22:06] [info] Running Service...
[2009-12-13 13:22:06] [info] Starting service...
[2009-12-13 13:22:06] [174  javajni.c] [error] The specified module could not be found.
[2009-12-13 13:22:06] [986  prunsrv.c] [error] Failed creating java \jre\bin\client\jvm.dll
[2009-12-13 13:22:06] [1260 prunsrv.c] [error] ServiceStart returned 1
[2009-12-13 13:22:06] [info] Run service finished.
[2009-12-13 13:22:06] [info] Procrun finished.

Typically, the BlackBerry Monitoring Service Tomcat logs are located in the following directory:

<drive>:\Program Files\Research In Motion\BlackBerry Enterprise Server\Monitoring Service\external\tomcat\logs

Cause
The Apache Tomcat process, which is required to run the BlackBerry Monitoring Service web page, is unable to access jvm.dll due to the incorrect path recorded in the Apache registry keys.

Resolution

1. Stop the all running BlackBerry Monitoring Services: Application Core, Data Collection Subsystem, and Polling Engine
2. Verify and notate the correct path where the jvm.dll file exists, typically "<drive>:\Program Files\Java\jdk1.6.0_15\jre\bin\client\jvm.dll"
3. Open the registry editor through Start > Run > regedit
4. Go to the Java registry key located under the Apache Software Foundation registry key:

HKEY_LOCAL_MACHINE\Software\Apache Software Foundation\Procrun 2.0\BBMonitoringConsole\Parameters\Java

HKEY_LOCAL_MACHINE\Software\Wow6432Node\Apache Software Foundation\Procrun 2.0\BBMonitoringConsole\Parameters\Java

5. Modify the Jvm value path of the jvm.dll file which was noted in step 2
6. Start all the BlackBerry Monitoring Services up and verify each service remains started
7. The BlackBerry Monitoring Console web page is now accessible

"For a child will be born to us, a son will be given to us; and the government will rest on His shoulders; and His name will be called Wonderful Counselor, Mighty God, Eternal Father, Prince of Peace."  - Isaiah 9:6

A call to Microsoft support generally means that something is really wrong so in that respect it is usually unpleasant. However, what I have always enjoyed is watching someone who really knows a specific product or server role resolve the issue because I always learn something. This is one of the more trivial things I have learned, but something new none the less.