Maybe it is simple, but I cannot find a good example and info.
I try to configure L3 cluster between two MC 7205 - they are in seperate DCs and seperate networks.
I have configured Cluster group under managed devices level and then added each physical controller to this group.
When I issue:
show lc-cluster group-membership
I see that self is in ISOLATED state and state of peer is alternating from
CONNECTED FROM SELF DISCONNECTED FROM PEER
In error logs I have
<ERRS> |cluster_mgr| cluster_gsm_delete_target_from_cluster_rep_key, Target 10.0.200.250 not present in cluster_rep_key
I suppose that I have missed a key somewhere, but I don't know where
Maybe someone had similar issue ?
Any help will be ok
A layer 3 cluster is not a feature...it is a drawback.... It indicates when a layer 2 cluster is misconfigured. It doesn't really serve a purpose. If an AP in a layer 3 cluster fails over to a second controller, it will deauth all of the clients on the AP and disconnect their sessions before failing over. Again, it doesn't make sense, and don't configure it. You might as well have failover between two local controllers that do not share the same layer 2 client VLAN.
Thanks cjoseph for the replay
ok, so what would You recomend for L3 connections between controlers ? LMS/Backup LMS or something more ?
I have made assumption that client can be deauth and disconnected. It is only for distatsrer recovery situation
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2020 Hewlett Packard Enterprise Development LPAll Rights Reserved.