Controllerless Networks

Anyone have any configuration guide about this kind of setup.

Both MC are managed by MM located in Building A. 1MC is building A with network 192.168.1.x and another in building B with network 172.16.1.x. I wish to build both MC into one cluster for failover purpose with different network.

May I know does this setup can be done? have any reference?

Should I enable L3 redundancy when intial setup the MC via CLI?

Still need setup VRRP? if yes, then what IP should used? if no, then we need set primary and secondary MC IP in "LMS" setting under AP group right?

what is the function for "Exclude VLANS" when assign individual MC into the cluster profile created. Does it fill in the VLANs which does not exist in both MC right?

This is a setup where you'd use LMS and Backup LMS configuration in the AP group configuration.  Do not configure a cluster, proper operation of a cluster requires L2 connectivity.

Anyone have any configuration guide about this kind of setup.

Both MC are managed by MM located in Building A. 1MC is building A with network 192.168.1.x and another in building B with network 172.16.1.x. I wish to build both MC into one cluster for failover purpose with different network.

May I know does this setup can be done? have any reference?

Should I enable L3 redundancy when intial setup the MC via CLI?

Still need setup VRRP? if yes, then what IP should used? if no, then we need set primary and secondary MC IP in "LMS" setting under AP group right?

what is the function for "Exclude VLANS" when assign individual MC into the cluster profile created. Does it fill in the VLANs which does not exist in both MC right?

Hi Chulcher,

Thank you for your reply. What you mean is cluster can't used for L3 right?

If not in cluster, when building A MD down, building A AP can direct failover to MD in building B without downtime? as AP will only failover between the MD is same cluster right? Then, I only need add both MD under same group without adding into cluster profile?

 Next, enable "L3 redundancy" when intial setup the Mobility Controller with md mode via CLI actually is refer to MM is setup in L3 environment, not refer to mobility controller right? 

This is a setup where you'd use LMS and Backup LMS configuration in the AP group configuration.  Do not configure a cluster, proper operation of a cluster requires L2 connectivity.

Anyone have any configuration guide about this kind of setup.

Both MC are managed by MM located in Building A. 1MC is building A with network 192.168.1.x and another in building B with network 172.16.1.x. I wish to build both MC into one cluster for failover purpose with different network.

May I know does this setup can be done? have any reference?

Should I enable L3 redundancy when intial setup the MC via CLI?

Still need setup VRRP? if yes, then what IP should used? if no, then we need set primary and secondary MC IP in "LMS" setting under AP group right?

what is the function for "Exclude VLANS" when assign individual MC into the cluster profile created. Does it fill in the VLANs which does not exist in both MC right?

Cluster is meant for L2 deployments, a cluster operating in L3 mode should be considered degraded and needing to be fixed.

If you don't have L2 connectivity between the two controllers then you DO NOT want a seamless failover, you NEED the drop of the client connections so that you force a new IP address to be pulled.  LMS/B-LMS failover is quick but has a downtime as the AP re-bootstraps and connects to the new controller.

L3 redundancy configuration should be referring to the Mobility Conductor configuration for the managed device, allowing for a MCR in a separate data center to be installed for redundancy.

Hi Chulcher,

Thank you for your reply. What you mean is cluster can't used for L3 right?

If not in cluster, when building A MD down, building A AP can direct failover to MD in building B without downtime? as AP will only failover between the MD is same cluster right? Then, I only need add both MD under same group without adding into cluster profile?

 Next, enable "L3 redundancy" when intial setup the Mobility Controller with md mode via CLI actually is refer to MM is setup in L3 environment, not refer to mobility controller right? 

This is a setup where you'd use LMS and Backup LMS configuration in the AP group configuration.  Do not configure a cluster, proper operation of a cluster requires L2 connectivity.

Anyone have any configuration guide about this kind of setup.

Both MC are managed by MM located in Building A. 1MC is building A with network 192.168.1.x and another in building B with network 172.16.1.x. I wish to build both MC into one cluster for failover purpose with different network.

May I know does this setup can be done? have any reference?

Should I enable L3 redundancy when intial setup the MC via CLI?

Still need setup VRRP? if yes, then what IP should used? if no, then we need set primary and secondary MC IP in "LMS" setting under AP group right?

what is the function for "Exclude VLANS" when assign individual MC into the cluster profile created. Does it fill in the VLANs which does not exist in both MC right?

Hi chulcher,

So it mean if we want do for L3 failover, the configuration needed is using LMS in AP group and this method must have some downtime when 1 of the controller down right? Both controller will be managed under different group or same group without cluster profile?

Cluster is meant for L2 deployments, a cluster operating in L3 mode should be considered degraded and needing to be fixed.

If you don't have L2 connectivity between the two controllers then you DO NOT want a seamless failover, you NEED the drop of the client connections so that you force a new IP address to be pulled.  LMS/B-LMS failover is quick but has a downtime as the AP re-bootstraps and connects to the new controller.

L3 redundancy configuration should be referring to the Mobility Conductor configuration for the managed device, allowing for a MCR in a separate data center to be installed for redundancy.

Hi Chulcher,

Thank you for your reply. What you mean is cluster can't used for L3 right?

If not in cluster, when building A MD down, building A AP can direct failover to MD in building B without downtime? as AP will only failover between the MD is same cluster right? Then, I only need add both MD under same group without adding into cluster profile?

 Next, enable "L3 redundancy" when intial setup the Mobility Controller with md mode via CLI actually is refer to MM is setup in L3 environment, not refer to mobility controller right? 

This is a setup where you'd use LMS and Backup LMS configuration in the AP group configuration.  Do not configure a cluster, proper operation of a cluster requires L2 connectivity.

Anyone have any configuration guide about this kind of setup.

Both MC are managed by MM located in Building A. 1MC is building A with network 192.168.1.x and another in building B with network 172.16.1.x. I wish to build both MC into one cluster for failover purpose with different network.

May I know does this setup can be done? have any reference?

Should I enable L3 redundancy when intial setup the MC via CLI?

Still need setup VRRP? if yes, then what IP should used? if no, then we need set primary and secondary MC IP in "LMS" setting under AP group right?

what is the function for "Exclude VLANS" when assign individual MC into the cluster profile created. Does it fill in the VLANs which does not exist in both MC right?