RE : [SSI] [Cluster Alias/CVIP ] Wish List or is it already there ?
Brought to you by:
brucewalker,
rogertsang
From: John H. <john@Calva.COM> - 2002-03-26 08:59:06
|
> I was going through the cluster documentation of Tru64 to figure out > what exactly is CVIP.It actually made me prepare this wish list. I > wonder if any of this is already there. Shouldn't you be looking at the UnixWare NSC doc rather than Tru64? Or is the cvip implementation the same? > 1)Since we talk of Single System Image I guess we need to have the > external interface( I mean interface connected to the external > network ) of all the nodes to be shown on each node once i do > ifconfig ( I guess Brian once told about this. Brian ? ) Here's what I get on my NSC system: (net0.[01] is the cluster interconnect, net1.[01] is the external ether, cvip0 is the cvip and lo0 is the loopback.) # onall ifconfig -a (node 1) lo0: flags=4049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet 127.0.0.1 netmask ff000000 net0.1: flags=24043<UP,BROADCAST,RUNNING,MULTICAST,ICS> mtu 1500 inet 192.168.255.1 netmask ffffff00 broadcast 192.168.255.255 ether 00:03:47:40:ce:a3 cvip0: flags=84041<UP,RUNNING,MULTICAST,CVIP> mtu 1500 inet 213.39.1.236 netmask ffffffe0 net1.1: flags=4043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 213.39.1.243 netmask ffffffe0 broadcast 213.39.1.255 ether 00:06:5b:38:49:cf net1.2: flags=44043<UP,BROADCAST,RUNNING,MULTICAST,REMOTE> mtu 1500 inet 213.39.1.244 netmask ffffffe0 broadcast 213.39.1.255 ether 00:06:5b:38:49:ba net0.2: flags=64043<UP,BROADCAST,RUNNING,MULTICAST,ICS,REMOTE> mtu 1500 inet 192.168.255.2 netmask ffffff00 broadcast 192.168.255.255 ether 00:03:47:3f:c9:0d (node 2) lo0: flags=4049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet 127.0.0.1 netmask ff000000 net0.2: flags=24043<UP,BROADCAST,RUNNING,MULTICAST,ICS> mtu 1500 inet 192.168.255.2 netmask ffffff00 broadcast 192.168.255.255 ether 00:03:47:3f:c9:0d cvip0: flags=84041<UP,RUNNING,MULTICAST,CVIP> mtu 1500 inet 213.39.1.236 netmask ffffffe0 net1.2: flags=4043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 213.39.1.244 netmask ffffffe0 broadcast 213.39.1.255 ether 00:06:5b:38:49:ba net0.1: flags=64043<UP,BROADCAST,RUNNING,MULTICAST,ICS,REMOTE> mtu 1500 inet 192.168.255.1 netmask ffffff00 broadcast 192.168.255.255 ether 00:03:47:40:ce:a3 net1.1: flags=44043<UP,BROADCAST,RUNNING,MULTICAST,REMOTE> mtu 1500 inet 213.39.1.243 netmask ffffffe0 broadcast 213.39.1.255 ether 00:06:5b:38:49:cf I.E. the order of the output is different but the same information is printed. > .... where eth1 and eth2 are interfaces on node2 and node3. I should be > able to do any ifconfig operation on these interfaces. Can do on UW NSC. > I should be able to run a server on node1 that listen on IP associated > with eth1 or eth2 Can do on UW NSC. > 2) It will great if i can see my cluster alias as an interface on all > the nodes and if I can do a "ifconfig clu0 down" That will bring the > cluster IP down. On UW NSC doing "ifconfig cvip0 down" takes down the cvip, but the individual node interfaces (net1.1 and net1.2 for me) stay up. > If you have multiple cluster alias then ifconfig should show > only those alias to which the particular node belongs. > 3) I should be able to configure a cluster alias and should be able > to say node1 node2 and node3 belong to this alias and node4, node5 > and node6 belong to cluster alias2 AFAIK the cvip (all the cvip's, you can have many) on UW NSC applies to all nodes. > 3) A user configurable load balancing on the basis of connection in > the case of a multi instance configuration of different server like > webserver ( LVS ? ) On UW NSC it seems to be round robin. |