Description of problem:

From cluster-summary.txt. This should be eth9 rather than eth11:

HB Address:   192.168.100.11
HB Interface: eth11

$ grep Node.address sos_commands/cluster/cman_tool_status 
Node addresses: 192.168.100.11 

I suspect sxconsole is looking at the ifcfg files:

$ grep -eONBOOT -e IPADDR etc/sysconfig/network-scripts/ifcfg-eth{9,11}
etc/sysconfig/network-scripts/ifcfg-eth9:ONBOOT=yes
etc/sysconfig/network-scripts/ifcfg-eth9:IPADDR=192.168.100.11
etc/sysconfig/network-scripts/ifcfg-eth11:ONBOOT=no
etc/sysconfig/network-scripts/ifcfg-eth11:IPADDR=192.168.100.11

...rather than what is active:

$ grep -B1 192.168.100.11 ifconfig
eth9      Link encap:Ethernet  HWaddr 9C:8E:99:0F:F7:C4  
          inet addr:192.168.100.11  Bcast:192.168.100.255  Mask:255.255.255.0

Version-Release number of selected component (if applicable):
sx-2.15-1.fc19.noarch

How reproducible:
100%

Steps to Reproduce:
1. run sxconsole against a sosreport with multiple interfaces assigned through ifcfg files to the the heartbeat address, with all but one configured to ONBOOT=no

Actual results:
sxconsole reports the alphabetically last interface with the matching IPADDR entry as the heartbeat interface, even if that one is ONBOOT=no

Expected results:
sxconsole reports the heartbeat interface correctly

Additional info: