[Linux-cluster] Linux-cluster Digest, Vol 76, Issue 18

[//qq李鹤]

------------------ Original ------------------
  From:  "linux-cluster-request"<linux-cluster-request at redhat.com>;
 Date:  Sat, Aug 21, 2010 00:00 AM
 To:  "linux-cluster"<linux-cluster at redhat.com>; 
 
 Subject:  Linux-cluster Digest, Vol 76, Issue 18

  
Send Linux-cluster mailing list submissions to
linux-cluster at redhat.com

To subscribe or unsubscribe via the World Wide Web, visit
https://www.redhat.com/mailman/listinfo/linux-cluster
or, via email, send a message with subject or body 'help' to
linux-cluster-request at redhat.com

You can reach the person managing the list at
linux-cluster-owner at redhat.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Linux-cluster digest..."


Today's Topics:

   1. Re: IP Source NAT (Kit Gerrits)


----------------------------------------------------------------------

Message: 1
Date: Fri, 20 Aug 2010 08:29:16 +0200
From: "Kit Gerrits" <kitgerrits at gmail.com>
To: "'linux clustering'" <linux-cluster at redhat.com>
Subject: Re: [Linux-cluster] IP Source NAT
Message-ID: <4c6e20b2.097b0e0a.7b55.ffff9aa4 at mx.google.com>
Content-Type: text/plain; charset="us-ascii"

 
Hello,

Most software allows you to configure the IP the software binds to.
Aside from that, I am not aware of of any other methods, provided by
clustering.
(The IP is simply added 'inside' the IP stack of the host)

In your case that would mean configuring the source IP in your monitoring
module (check_snmp) or the tool used inside the module (snmpget).
Snmpget should be configurable through snmp.conf with the following option:
     clientaddr [<transport-specifier>:]<transport-address>
           Specify source address used  by  command-line  tools,  see
           snmpcmd(1) , and by snmpd when sending notifications.
See:
http://www.mail-archive.com/net-snmp-users@lists.sourceforge.net/msg08109.ht
ml


In case of an iptables solution, this might help:
http://fixunix.com/snmp/65274-snmpget-snmpwalk-using-virtual-ip.html


Regards,

Kit

-----Original Message-----
From: linux-cluster-bounces at redhat.com
[mailto:linux-cluster-bounces at redhat.com] On Behalf Of Bernd Broermann
Sent: donderdag 19 augustus 2010 11:26
To: linux-cluster at redhat.com
Subject: [Linux-cluster] IP Source NAT

Hello Senol,
Hello all,

I my special case I want to setup a 2 Node Active/Passiv failover Cluster
with nagios ( nrpe/snmp ) as a service.

ClusterNode1IP -
                -> vIP  ----------- Clients (connects only allowed from vIP)
ClusterNode2IP -

The nrpe and snmp Agents only allow connects from the virtual IP of the
Cluster.

An iptables nat rule should do that for these ports.

But is there a best practice ?

Thank you





Hi Bernd,

your comments too much close but;

- if u are build two node fail-over (as Acrive-Passive) you can give to vIP
to active node starting,
- if u are using two or more server at the moment (for Load Balancing) then
your keywords "ipvsadm" and "Direct Routing".


2010/8/18 Bernd Broermann <bernd broermann com>

    Hello,

    How can I define a resource to make all outgoing network packets appear
    to be the virtual IPaddress ?

    I mean something like the "ipsrcaddr" resource in OCF:heartbeat.

    Thanks for answers,
    bernd

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



--
Linux-cluster mailing list
Linux-cluster at redhat.com
https://www.redhat.com/mailman/listinfo/linux-cluster
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.851 / Virus Database: 271.1.1/3082 - Release Date: 08/19/10
20:35:00



------------------------------

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

End of Linux-cluster Digest, Vol 76, Issue 18
*********************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20100821/f75acdd9/attachment.htm>