Re: fence_cisco_ucs issue within cluster.conf

Jayesh Shinde <jayesh.shinde@xxxxxxxxxxxxx> · Wed, 4 Nov 2015 20:06:47 +0530

    Hello , 

      My issue resolved by removing the --suborg  from cluster.conf  

      Redhat KB https://access.redhat.com/solutions/785903# 
      syntax not worked with me  for RHEL 6.5  i.e for --suborg

    IN KB its mentioned as
      :-- "While invoking fence_cisco_ucs agent from
      command line, please add /org- prefix to the real
      organization path like below

    $ fence_cisco_ucs --ip="a.b.c.d" --username="admin" --password="XXXXX" -z 1 --plug="UCSPROFILE2" --suborg="/org-RHEL/" -o status -v

      with above stntax , Error remain same  as follows below :-- 

      [root@mailbox2 ~]# fence_cisco_ucs --ip="172.17.1.30"
      --username="KVM" --password="myPassword" -z 1 --plug="mailbox1"
      --suborg="/org-root/ls-mailbox" -o status -v

      [root@mailbox2 ~]# fence_cisco_ucs --ip="172.17.1.30"
      --username="KVM" --password="myPassword" -z 1 --plug="mailbox1"
      --suborg="/org-root/" -o status -v

      Failed: Unable to obtain correct plug status or plug is not
      available.

      Where As if I remove  --suborg , then
        its working properly , as follows. 

      [root@mailbox2 ~]# fence_cisco_ucs --ip="172.17.1.30"
      --username="KVM" --password="myPassword"
      -z 1 --plug="mailbox1"  -o status -v

      Status: ON

      The same logic I used in cluster.conf and now fencing working fine
      :--)

        <fencedevices>

          <fencedevice agent="fence_cisco_ucs" ipaddr="172.17.1.30"
      ipport="443" login="KVM" name="CiscoFence" passwd="myPassword" ssl="on"/>

        </fencedevices>

      Thanks 

      Regards

        Jayesh Shinde

    On 11/04/2015 02:50 PM, Marek marx Grác
      wrote:

      Hi,

Thanks for a great report. I believe that problem is that in cluster.conf you set up ‘suborg=“/org-root/ls-mailbox” but on the command line you have it without “--" so it is not used at all. It is best shown at that verbose output.

On 2 November 2015 at 15:39:45, Jayesh Shinde (jayesh.shinde@xxxxxxxxxxxxx) wrote:

        command line fencing :--
-----------------------------
[root@mailbox2 ~]# /usr/sbin/fence_cisco_ucs -a 172.17.1.30 -l KVM -p
'myPassword' -o status -v -z --plug=mailbox1 --ipport=443
suborg="/org-root/ls-mailbox" ; *echo $?*

          outCookie="1446038319/bdd0ea5b-386f-4374-8eca-9ff7595c33f3"

        outRefreshPeriod="600" outPriv="pn-equipment,pn-maintenance,read-only"
outDomains="" outChannel="noencssl" outEvtChannel="noencssl"
outSessionId="web_29402_B" outVersion="2.2(3d)" outName="KVM">  

          cookie="1446038319/bdd0ea5b-386f-4374-8eca-9ff7595c33f3"

        inHierarchical="false" dn="org-root/ls-mailbox1/power"/>

          cookie="1446038319/bdd0ea5b-386f-4374-8eca-9ff7595c33f3" response="yes">  

      As you can see dn is org-root/ls-mailbox1/... with suborg set it will be org-root/ls-mailbox/ls-mailbox1/...
It should be enough to remove sub-org part from your cluster.conf

m,

-- 
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster