Dear Christopher, Zevenet CE cluster works a little bit different than
Zevenet EE cluster, maybe here your misunderstanding, we will work in new
Zevenet CE version in order to create a shared Core between them.
Related to the Zevenet cluster, your proposal sounds useful, I would
appreciate if you could register your proposal in the tool enabled for
that: https://github.com/zevenet/zlb/issues, there are some enhacement
that other members have already registered.
Regards
2017-02-09 17:30 GMT+01:00 Christopher Young <mexigaba...@gmail.com>:
> You are correct. When I do a failover, I see that behavior. It is
> odd, though because I don't recall seeing that in the past. I had
> thought (clearly, incorrectly) that the only interfaces that would be
> failed back and forth would be the sub-(virtual)interfaces (:1 :2,
> etc.). Thanks for the clarification. Please let me know if there are
> any caveats to this setup perhaps based on the cluster type as I'm
> trying to make sure I fully understand what is normal vs. abnormal
> behavior.
>
> Thanks,
>
> Chris
>
> PS: One thought I had is that it might be useful to be able to
> (through configuration) exclude specific interfaces from this
> mechanism as you may want a specific interface up for monitoring and
> what-not. I realize it is normal for that to be the cluster
> interface, however it is a fairly standard practice in my world to
> purposely have cluster communications isolated from other traffic
> (separate physical network or VLAN). This is just a thought of mine
> so I certainly understand why it would be otherwise philosophically.
>
> On Thu, Feb 9, 2017 at 9:37 AM, Emilio Campos
> <emilio.campos.mar...@gmail.com> wrote:
> > Dear Christopher, I see everything configred and working as expected for
> a
> > cluster en zevenet ce.
> >
> >
> > As soon as you configure cluster service in eth1 and cluster starts then
> the
> > master node replicates all the network interfaces to node slave,
> following
> > all the iterfaces will be configured as down except the nic related with
> the
> > cluster (eth1).
> >
> > Check it and let me know.
> >
> > Regards
> >
> > 2017-02-08 21:35 GMT+01:00 Christopher Young <mexigaba...@gmail.com>:
> >>
> >> So, I've created a new ZenLB CE Cluster on a pair of systems. The
> >> setup involved a pair of NICs on each system. I'll try and explain
> >> below.
> >>
> >> -----
> >> netlb01 - eth0 - 10.26.250.63
> >> - eth1 - 10.26.251.60
> >>
> >> netlb02 - eth0 - 10.26.250.64
> >> - eth1 - 10.26.251.61
> >>
> >> cluster interface: eth1:1 - 10.26.251.59
> >> -----
> >>
> >> I generally like to create cluster interfaces on a dedicated network
> >> to isolate the traffic and also provide redundancy for clustering tech
> >> that allow it (dual paths).
> >>
> >> In any case, this is a setup I've used with ZenLB before in the past
> >> generally without issue, but this time I have a problem where eth0 on
> >> netlb02 (the secondary node) does not come up now (started the moment
> >> the cluster was configured which appears to have been successful).
> >> I've looked a the configs for obvious issues like IP conflicts and
> >> what-not and so far, I can't find anything.
> >>
> >> I'm wondering if this is something anyone else has encountered. I've
> >> looked at the configs in /usr/local/zenloadbalancer/config and thus
> >> far I can't find anything obvious.
> >>
> >> For example (file contents on netlb02):
> >>
> >> ===== if_eth0_conf ======
> >> eth0::10.26.250.64:255.255.255.0:up::
> >> ===== if_eth0:ntp_conf ======
> >> eth0:ntp:10.26.250.24:255.255.255.0:up::
> >> ===== if_eth1:1_conf ======
> >> eth1:1:10.26.251.59:255.255.255.0:up::
> >> ===== if_eth1_conf ======
> >> eth1::10.26.251.61:255.255.255.0:up::
> >>
> >> ---------------------
> >> The same on netlb01:
> >>
> >> ===== if_eth0_conf ======
> >> eth0::10.26.250.63:255.255.255.0:up::
> >> ===== if_eth0:ntp_conf ======
> >> eth0:ntp:10.26.250.24:255.255.255.0:up::
> >> ===== if_eth1:1_conf ======
> >> eth1:1:10.26.251.59:255.255.255.0:up::
> >> ===== if_eth1_conf ======
> >> eth1::10.26.251.60:255.255.255.0:up::
> >>
> >>
> >> ----------------------------
> >> ifconfig from netlb01:
> >>
> >> eth0 Link encap:Ethernet HWaddr 00:1a:4a:26:01:54
> >> inet addr:10.26.250.63 Bcast:10.26.250.255
> Mask:255.255.255.0
> >> inet6 addr: fe80::21a:4aff:fe26:154/64 Scope:Link
> >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> >> RX packets:27101 errors:0 dropped:0 overruns:0 frame:0
> >> TX packets:18922 errors:0 dropped:0 overruns:0 carrier:0
> >> collisions:0 txqueuelen:1000
> >> RX bytes:9965526 (9.5 MiB) TX bytes:4586928 (4.3 MiB)
> >>
> >> eth1 Link encap:Ethernet HWaddr 00:1a:4a:26:01:55
> >> inet addr:10.26.251.60 Bcast:10.26.251.255
> Mask:255.255.255.0
> >> inet6 addr: fe80::21a:4aff:fe26:155/64 Scope:Link
> >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> >> RX packets:3076 errors:0 dropped:0 overruns:0 frame:0
> >> TX packets:6496 errors:0 dropped:0 overruns:0 carrier:0
> >> collisions:0 txqueuelen:1000
> >> RX bytes:630297 (615.5 KiB) TX bytes:622917 (608.3 KiB)
> >>
> >> eth1:1 Link encap:Ethernet HWaddr 00:1a:4a:26:01:55
> >> inet addr:10.26.251.59 Bcast:0.0.0.0 Mask:255.255.255.0
> >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> >>
> >> eth0:ntp Link encap:Ethernet HWaddr 00:1a:4a:26:01:54
> >> inet addr:10.26.250.24 Bcast:10.26.250.255
> Mask:255.255.255.0
> >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> >>
> >> ----------
> >>
> >> ifconfig from netlb02:
> >>
> >> eth1 Link encap:Ethernet HWaddr 00:1a:4a:26:01:57
> >> inet addr:10.26.251.61 Bcast:10.26.251.255
> Mask:255.255.255.0
> >> inet6 addr: fe80::21a:4aff:fe26:157/64 Scope:Link
> >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> >> RX packets:5655 errors:0 dropped:0 overruns:0 frame:0
> >> TX packets:2718 errors:0 dropped:0 overruns:0 carrier:0
> >> collisions:0 txqueuelen:1000
> >> RX bytes:503808 (492.0 KiB) TX bytes:567462 (554.1 KiB)
> >>
> >>
> >>
> >> ----------
> >>
> >> Any hints or thoughts or troubleshooting steps would be most welcome!
> >>
> >> Thanks,
> >>
> >> Chris
> >>
> >>
> >> ------------------------------------------------------------
> ------------------
> >> Check out the vibrant tech community on one of the world's most
> >> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> >> _______________________________________________
> >> Zenloadbalancer-support mailing list
> >> Zenloadbalancer-support@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
> >
> >
> >
> >
> > --
> > Load balancer distribution - Open Source Project
> > http://www.zenloadbalancer.com
> > Distribution list (subscribe): zenloadbalancer-support@lists.
> sourceforge.net
> >
> > ------------------------------------------------------------
> ------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> > _______________________________________________
> > Zenloadbalancer-support mailing list
> > Zenloadbalancer-support@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
> >
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Zenloadbalancer-support mailing list
> Zenloadbalancer-support@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
--
Load balancer distribution - Open Source Project
http://www.zenloadbalancer.com
Distribution list (subscribe): zenloadbalancer-support@lists.sourceforge.net
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Zenloadbalancer-support mailing list
Zenloadbalancer-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
