ccherman3
asked on
PowerChute Network Shutdown on ESXi 4.1
Thru my vMA, I've installed PCNS 3.0 on 3 ESXi hosts in a cluster.
The problem I'm having is when I open a browser to connect to the software configuration on any host(https://xxx.xxx.xxx.xxx:5647), I cannot connect.
I've been working thru problems getting this to install and I feel that I'm getting close but not sure about this one.
I am not a Linux command line person by any stretch of the imagination either.....
Any input would be appreciated......thanks.
The problem I'm having is when I open a browser to connect to the software configuration on any host(https://xxx.xxx.xxx.xxx:5647), I cannot connect.
I've been working thru problems getting this to install and I feel that I'm getting close but not sure about this one.
I am not a Linux command line person by any stretch of the imagination either.....
Any input would be appreciated......thanks.
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
PCNS 3.0 installs on the vMA, and not the host ESXi servers?
ASKER
It installs on the ESXi hosts, but it's command line driven thru the vMA.....you run the install to the hosts from the vMA, at least that's the way it's spelled out in the documentation.
We normally install on the vMA, if using ESXi, ESXi has no service console for the software to fucntion.
On the vMA - sudo ./install_en.sh
and then...
Connect to the IP of the vMA machine ex. https://10.0.0.9:6547/login
On the vMA - sudo ./install_en.sh
and then...
Connect to the IP of the vMA machine ex. https://10.0.0.9:6547/login
The installation pdf states
"Installing PCNS:
The installation program must be run on the server to be protected.
On VMware, the installation program must be run on the ESXi VIMA (vMA)"
"Installing PCNS:
The installation program must be run on the server to be protected.
On VMware, the installation program must be run on the ESXi VIMA (vMA)"
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Now I'm not sure I understand the process.....I thought i did.
The link you sent was the one I did follow this morning before I posted to EE and after a successful install I stopped at the following line in the process.
Edit the shutdown.pl file attached to the end of this post and enter your ESXi host credentials.
So, based on your input, like I said, my understanding of the process and mechanics is probably flawed.
This my infrastructure:
3 ESXi 4.1 hosts running in a cluster call them HOST1, HOST2, and HOST3 - vMA is running on HOST2
Downloaded the PCNS zip file and copied it to /home/vi-admin directory via WinScp
Performed tar -xzvf pcns300ESXi.tar.gz then , cd ESXi
Then ran sudo ./install_en.sh
It installed with no problem, all authentication OK
I submitted my target servers HOST1, HOST2, HOST3.....all came back successful (but had to run the install 3 times to get target servers set up.....which is where I think my logic is flawed)
I think a light bulb just lit up......do I need to vMotion my vMA to each host server and point to the respective host server as the target at that point ? Then connect via the browser to configure the client ? Because, come to think of it, I was able to connect to the browser interface IF I entered the vMA IP address.....I think it's somewhat clearer to me now.......please confirm.
thanks for your input thus far....
The link you sent was the one I did follow this morning before I posted to EE and after a successful install I stopped at the following line in the process.
Edit the shutdown.pl file attached to the end of this post and enter your ESXi host credentials.
So, based on your input, like I said, my understanding of the process and mechanics is probably flawed.
This my infrastructure:
3 ESXi 4.1 hosts running in a cluster call them HOST1, HOST2, and HOST3 - vMA is running on HOST2
Downloaded the PCNS zip file and copied it to /home/vi-admin directory via WinScp
Performed tar -xzvf pcns300ESXi.tar.gz then , cd ESXi
Then ran sudo ./install_en.sh
It installed with no problem, all authentication OK
I submitted my target servers HOST1, HOST2, HOST3.....all came back successful (but had to run the install 3 times to get target servers set up.....which is where I think my logic is flawed)
I think a light bulb just lit up......do I need to vMotion my vMA to each host server and point to the respective host server as the target at that point ? Then connect via the browser to configure the client ? Because, come to think of it, I was able to connect to the browser interface IF I entered the vMA IP address.....I think it's somewhat clearer to me now.......please confirm.
thanks for your input thus far....
no need for any vMotion, vMA will connect to host via network.
connect to vMA via browser to configure
connect to vMA via browser to configure
make sure ALL host IP addresses are in a hosts filebin bin folder.
ASKER
Thanks for the input......I now have a clearer understanding of how this is supposed to work.