[Linux-cluster] fence_apc does not like "outlet" user

[Ward, Timothy - SSD]

I have an APC 7901 and have been using the fence_apc tool to test the functionality.  In the past I've always used the "root" account to control the NPS but thats bad so I am trying to get an "outlet" user setup.  Here are my results:

[root at node1 ~]# fence_apc -a 10.1.1.12 -l root -n 3 -p root -o on -v
Status check successful. Port 3 is ON
Power On successful

[root at node1 ~]# fence_apc -a 10.1.1.12 -l device -n 3 -p device -o on -v
Status check successful. Port 3 is ON
Power On successful

[root at node1 ~]# fence_apc -a 10.1.1.12 -l cluster -n 3 -p cluster -o on -v
Traceback (most recent call last):
  File "/sbin/fence_apc", line 829, in ?
    main()
  File "/sbin/fence_apc", line 327, in main
    backout(sock) # Return to control screen
  File "/sbin/fence_apc", line 393, in backout
    i, mo, txt = sock.expect(regex_list, TELNET_TIMEOUT)
  File "/usr/lib64/python2.4/telnetlib.py", line 620, in expect
    text = self.read_very_lazy()
  File "/usr/lib64/python2.4/telnetlib.py", line 400, in read_very_lazy
    raise EOFError, 'telnet connection closed'
EOFError: telnet connection closed

I tried this with CentOS 5.1 and 5.2.  For users root=admin, device=device, cluster=outlet.

The info in /tmp/apclog does not have anything that is obviously useful (I compared the device and cluster user outputs).  I did notice the log does not fill until the fence_apc fails for the outlet "cluster" user.  I also tried a different outlet user name, checked that the outlet user has access to all of the outlets.

My next idea was to grit my teeth and upgrade the APC firmware.

Any suggestions would be welcome.

Thanks guys,
Tim

This e-mail and any files transmitted with it may be proprietary and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the sender.
Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of ITT Corporation. The recipient should check this e-mail and any attachments for the presence of viruses. ITT accepts no liability for any damage caused by any virus transmitted by this e-mail.