Author
Topic: ERS 5500 Cluster (Read 956 times)

We currently have one stack of 6 switches for our core. The core holds the IP info for all our VLAN's that we use in our HQ. (3 clients VLAN's, Server VLAN, Voice Vlan etc). We are looking at a DR site now from a networking viewpoint. We have an 20GB MLT running from the HQ core to a standalone stack in DR right now. That has been in place now for a year working quite happily. We are looking now at DR now at what if the core stack failed for any reason. Right now that would mean all our vlan's would die. Our stack right now uses stacking cables to form the stack in HQ. I have read some articles about switch clustering. Is that the route that we should be looking to bring the standalone stack into in the main stack so it would have the config if the main stack failed?

you basically have 3 possible scenario's:1) split your current 'core' stack into 2 smaller stacks and combine them into a cluster. Physically run part of the MLT to the 'edge' stack to the 2nd core stack (cluster node 2) to create a SMLT.2) build a cluster between the current 'core' stack and the 'edge' stack. 3) Split off 2 units of either stack, and build them into the custer. Connect the 2 edge stacks (remaining units of 'core stack' and edge stack) via SMLT to the new cluster.

All scenario's are valid, depending on the hardware you use, keep in mind that you need the same series switches on both sides to be able to cluster (ERS5xxx / ERS4xxx / ERS8xxx). Best is to keep the size of your core systems as small as possible and connect as much to the edge, connect these to both cluster units for maximum resiliency.

Also keep in mind that if you want to use VRRP and such, you'll need advanced licenses on both the cluster nodes.