Tuesday, July 30, 2019

Redundant ring (?) network topology with EdgeSwitch 16-Port XG

Good afternoon,

This is a crosspost from ITdept, got recommended to post this here instead. And as it seems images are not allowed I'll be using links to images describing the situation. I am quite new to networking on this scale, so don't be harsh and explain it using simple dummy words :-) thanks! Also, this will be a forklift upgrade (new word I learned at the other post on ITdept).. so any other devices, it's possible. However the company demands we kind of stay true to our original plan using Ubiquity.

My second post on Reddit, after I have been reading and following topics for quite some time. I work at a small IT company and we recently acquired a nice (larger) customer. The customer has three locations on the same industrial site. There is fiber optic between each location, as can be seen on the attached drawing.

https://i.redd.it/sq1em2prq1d31.png

We have already bought some EdgeSwitch 16-Port XG to try it out. Although it is possible to make a single ring and to use port blocking, a double ring is quite a challenge. In addition, there is 50 ms downtime when a new route (as in, fiber route) must be chosen and I would prefer to see this without downtime.

My intention is to use the switches as a L2 network. The switches know the VLAN's, the routers do not.

For example:

192.168.1.1 = Guest network, VLAN 5, connected to firewall and guest access points

172.16.2.1 = LAN network VLAN 2, attached to firewall and endpoint switches

172.16.3.1 = MGMT network VLAn 3, attached to mgmt devices, firewall, etc.

https://i.redd.it/ilmt52utq1d31.png

Our idea was to install 2 "core" switches of the EdgeSwitch 16-Port XG type at each location. Connect these two switches together, connect servers to both switches (double uplink) and thus create a reliable solution.

Only now it gets pretty complicated and I am a bit lost.

Do you have suggestions as to how this can best be built up?

Thanks for reading and taking your time.



No comments:

Post a Comment