chiu chun chir wrote:
> Dear Masters,
>
> Sorry forgot attachment last letter...
>
>
> I've set up cluster with 2 nodes ( tacomcs1-Active and tacomcs2-Standby) .
>
> OS is SUSE Eneterprise Server 10 with heartbeat-2.0.7-1.2 upgraded.
>
> I wish if tacomcs1 cannot reach the outside world network, all services can
> failover to tacomcs2.
>
> And all services will stay in tacomcs2 until it was failed or rebooted.
>
>
>
> I've follow the resource constraint illustrated at
> http://www.linux-ha.org/pingd.
>
> Topic -> Quickstart - Run my resource on the node with the best
> connectivity.
>
>
>
> And make a similar setting according the guide :
>
> <rsc_location id="my_resource:connected" rsc="my_resource">
>
> <rule id="my_resource:connected:rule" score_attribute="pingd" >
>
> <expression id="my_resource:connected:expr:defined"
>
> attribute="pingd" operation="defined"/>
>
> </rule>
>
> </rsc_location>
>
>
>
> After I use `yast` to modify tacomcs1 IP (Active node)
>
> (an IP address which cannot reach the gateway address : 10.31.70.1 -
> configured in ha.cf as a PingNode).
>
>
>
> In the first time, the group named 'TACO_SERVICES' had failover to tacomcs2
> (Standby node).
>
> After it failover, I'd modify tacomcs1 to correct IP Address - 10.31.70.8 -
> can reach gateway.
>
> But in the mean time, tacomcs1 become OFFLINE (showed by $ crm_mon -1).
>
>
>
> But after I restarted the both tacomcs1 and tacomcs2 HEARTBEAT service.
>
> And use `yast` to modify tacomcs1 (Active node) IP address to wrong IP
> (can't reach gateway).
>
> It does not failover to tacomcs2 anymore.
>
> In contrarily, tacomcs1 believes tacomcs2 was OFFLINE via $ crm_mon -1.
Don't change your running system's network configuration.
But, I don't quite understand what it is you did, or why you did it.
--
Alan Robertson <[EMAIL PROTECTED]>
"Openness is the foundation and preservative of friendship... Let me
claim from you at all times your undisguised opinions." - William
Wilberforce
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
