Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
This power bar has a firmware that can't be used with fence_apc
Version-Release number of selected component (if applicable):
fence-agents-3.0.12-8.el6_0.3.x86_64
How reproducible:
fence_apc --ip=66.254.58.197 --username=user --password=pass --plug=node101 --ssh
Steps to Reproduce:
1. call the above command
Actual results:
Node not fenced
Expected results:
Node fenced
Additional info:
There is 3 problems. First, ssh server on that bar is v2 only. So ssh_options (line 198) has to be commented out. Second, the prompt has changed to "apc>". So "cmd_prompt" has to be added to the device_opt array and --command-prompt="apc>" added to the command line. Next, the command to use the device has changed. Here's the output saved in the debug file after steps mentionned :
-------------------------
American Power Conversion Network Management Card AOS
v5.1.2
(c) Copyright 2009 All Rights Reserved RPDU 2g
v5.1.0
-------------------------------------------------------------------------------
Name : Unknown Date : 04/08/2011
Contact : Unknown Time : 10:49:39
Location : Unknown User : Device Manager
Up Time : 0 Days 2 Hours 18 Minutes Stat : P+ N4+ N6+ A+
Type ? for command listing
Use tcpip command for IP address(-i), subnet(-s), and gateway(-g)
apc>1
E101: Command Not Found
apc>2
E101: Command Not Found
apc>
-------------------------
When I connect manually, here are the commands availaible :
bkLowLoad bkNearOver bkOverLoad bkReading bkRestrictn devLowLoad
devNearOver devOverLoad devReading devStartDly humLow humMin
humReading olCancelCmd olDlyOff olDlyOn olDlyReboot olGroups
olName olOff olOffDelay olOn olOnDelay olRbootTime
olReboot olStatus phLowLoad phNearOver phOverLoad phReading
phRestrictn prodInfo sensorName tempHigh tempMax tempReading
userList whoami
So the command to send would be :
olReboot node101
Like so :
-------------------------
apc>olReboot node101
E000: Success
apc>
-------------------------
and then "quit" to logout.