|
Hello,
On Sat, 29 Jul 2000, Gong Wei wrote:
> One of the practical application in our environment is for network
> management purpose. We have a group of management server, however, for load
> sharing/HA purpose I would like to let all of them appear as a single IP.
>
> The way the overall system works is that whenever there is a link state
> change on the edge switch port (connect/disconnect a pc/notebook to the
> switch port, for instance), a trap will be sent to the management server,
> which contains important info like the location of the switch, MAC address
> of the client, etc. These information will be used later to generate audit
> reports.
>
> Unfortunately currently there is no way to send certain packets to all real
> server, so unless the subsequent packets from the *client* (not the switch)
> happended to reach the real server, or else ....
>
> Obviously I could use persistence feature with 0.0.0.0 as the netmask, but
> this doesn't sounds like a neat solution ...
>
> The "security/flooding" concern something valid as not every system
> administrator knows what they are doing :-)
>
> This is just one particular instance whereby I found LVS doesn't fit into
> the picture nicely. In other situations especially WWW/FTP, it works really
> nice!
Obviously, you can't forward the DNS NOTIFY through LVS to
many real servers. So, try another way.
What about trying this (not tested):
notify yes;
also-notify { RIP1; RIP2; ... RIPn; };
May be one of the real servers will receive two notifications
but 2 > 0.
Regards
--
Julian Anastasov <uli@xxxxxxxxxxxxxxxxxxxxxx>
|
