Cluster configuration:My cluster consists of two machines: carbon and oxygen.I
use these two hostnames in the DRBD config and have defined their IPs in
/etc/hosts (crossover IPs - eth1):carbon 10.128.1.1oxygen 10.128.1.2
Each of these hosts also has their fullname defined in /etc/hosts (lan -
eth0):carbon.domain.com 192.168.10.151oxygen.domain.com 192.168.10.152
gethostip results:I just ran "gethostip -d carbon" and got 127.0.1.1.I check
/etc/hosts and I noticed that on the second line (above my handmade
definitions), carbon was set to 127.0.1.1.Also, when I run "uname -a", the
hostname it returns is carbon, not carbon.domain.com. Maybe I should change
the hostname to carbon.domain.com since IPMI is using eth0 and it is already
configured to use 192.168.10.151. Ping results:I am able to ping both
192.168.10.151 and 10.128.1.1 from both machines with no problem. > Date: Mon,
29 Oct 2012 21:58:19 -0700
> From: [email protected]
> To: [email protected]
> CC: [email protected]
> Subject: Re: [Linux-HA] IBM x3200 M3 Best IPMI STONITH Device
>
> What name did you use in the cluster configuration, exactly? What does
> 'gethostip -d <name>' resolve to?
>
> Regardless of that, can you ping the opposing node's IPMI IP address?
> I've seen shared IPMI/LAN not be able to ping it's own IPMI interface.
>
> digimer
>
> On 10/29/2012 09:48 PM, Josh Bowling wrote:
> > Well, I've tried a few things using your tutorials and I think I'm on
> > setting away from getting it up and going.
> > My problem seems to lie in the IP settings.
> >
> > On a machine with the hostname of "carbon", eth0 uses 192.68.0.151 while
> > eth1 uses 10.128.1.1.
> > Following a Pacemaker/Corosync tutorial, I set the name carbon equal to
> > 10.128.1.1 and carbon.domain.com <http://carbon.domain.com> equal to
> > 192.168.10.151. The only thing is that my IPMI sees to be using channel 1:
> >
> >
> > Set in Progress : Set Complete
> > Auth Type Support : NONE MD2 MD5 PASSWORD
> > Auth Type Enable : Callback :
> > : User : MD2 MD5 PASSWORD
> > : Operator : MD2 MD5 PASSWORD
> > : Admin : MD2 MD5 PASSWORD
> > : OEM :
> > IP Address Source : Static Address
> > IP Address : 192.168.10.151
> > Subnet Mask : 255.255.255.0
> > MAC Address : 5c:f3:fc:f2:35:95
> > SNMP Community String : public
> > IP Header : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10
> > BMC ARP Control : ARP Responses Enabled, Gratuitous ARP Disabled
> > Gratituous ARP Intrvl : 2.0 seconds
> > Default Gateway IP : 192.168.10.10
> > Default Gateway MAC : 00:00:00:00:00:00
> > Backup Gateway IP : 0.0.0.0
> > Backup Gateway MAC : 00:00:00:00:00:00
> > 802.1q VLAN ID : Disabled
> > 802.1q VLAN Priority : 0
> > RMCP+ Cipher Suites : 0,1,2,3,4
> > Cipher Suite Priv Max : uaaaaXXXXXXXXXX
> > : X=Cipher Suite Unused
> > : c=CALLBACK
> > : u=USER
> > : o=OPERATOR
> > : a=ADMIN
> > : O=OEM
> >
> >
> > Since IPMI is using the first lan channel, which means eth0 for me, I
> > set the IP address to 192.168.10.151.
> > When I do the following on a separate machine (the one connected to it
> > by both lan and crossover), it tells me that a connection could not be
> > made. What am I doing wrong?
> >
> > # ipmitool -I lan -U admin -P secret -H 192.168.10.151 chassis
> > status
> > Error: Unable to establish LAN session
> > Error sending Chassis Status command
> >
>
>
> --
> Digimer
> Papers and Projects: https://alteeve.ca/w/
> What if the cure for cancer is trapped in the mind of a person without
> access to education?
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
