{"searchBar":{"inputPlaceholder":"Выполните поиск по ключевому слову или задайте вопрос","searchBtn":"Поиск","error":"Введите ключевое слово для поиска"}}
{}

Наши бренды

{"support":{"yesButton":"Да","noButton":"Нет","feedback":{"title":"Что мы можем сделать лучше?"},"submitButton":"Отправить","successMessage":"Благодарим вас за отзыв","title":"Было ли это полезно?","feedbackPercentLabel":"пользователей считают это полезным","captcha":{"error":"Установите флажок"}}}
Поиск часто задаваемых вопросов

PowerChute Network Shutdown version 4.3 fails to power off Hosts in a Stretch Cluster when the Witness host is powered off.

Issue:
When the PowerChute Appliance is deployed to the same host that is running the vSAN Witness it shuts down this host before the other vSAN hosts if the Witness is powered off. This host should be the last to shut down.

Product Line:
PowerChute Network Shutdown version 4.3

Environment:
PowerChute Network Shutdown VM installed same ESXi host as the vSAN Witness Appliance.

Cause:
Witness host is off line when PowerChute initiates shut down process.

Solution:
1. Download the attached pcns_vsan_ftt.tar file.
2. Copy pcns_vsan_ftt.tar on to the PowerChute VM
3. Log into the PowerChute VM as root
4. Uncompress the file. tar -xvf pcns_vsan_ftt.tar
5. Stop the PowerChute service systemctl stop PowerChute
6. Rename the original pcns.jar mv /opt/APC/PowerChute/group1/comp/pcns.jar  /opt/APC/PowerChute/group1/comp/original_pcns.jar
7. Next copy the uncompress pcns_vsan_fft.jar to the PowerChute directory cp pcns_vsan_ftt.jar /opt/APC/PowerChute/group1/comp/pcns.jar (Note: when the file is copied the name is changed from pcns_vsan_ftt.jar to pcns.jar)
9. Change to permissions of the new pcns.jar file chmod 664 /opt/APC/PowerChute/group1/comp/pcns.jar
8. Re-start the PowerChute service systemctl start PowerChute 

 

Вложения

Не удается найти то, что нужно?

Обратитесь в нашу службу поддержки клиентов, чтобы получить техническую поддержку, помощь в составлении жалоб и многое другое.