Purely from an LTT over the top ridiculous level experiment. Just my two cents! I would love to see Linus revise this so it's truely redundant. Without a secondary ISP available to use as a failover, you're probably more likely to have issues with your ISP than with your routing layer. It's probably overkill if you only have a single ISP though. This would give you hardware redundancy on the Routing Layer as well. For this I would replace the UI options and use a couple of Netgate XG-7100 1U appliances with expansion cards setup in high availabilty mode. I do not believe that the UXG-Pro or any UI routing product supports having a second router in the stack. If one machine bricks for a non-PSU related reason the other would take over. AKA two physical routers at the Routing Layer in a "failover" configuration. One could argue that even with a single ISP, a high-availability routing configuration would be best. If the switch bricks, having a second wouldn't save the cameras immediately anyway since they can't be connected to more than one switch. If a switch PSU dies, you have the RPS to provide a failover. You can't connect any Protect series camera to multiple switches AFAIK, so connecting all of your cameras to a single switch IMO is fine. The clients/devices probably don't have a redundant connected so they are already a single point of failure. Since your access layer is directly connected to clients/devices, there's not a huge need to make that layer redundant. USW-Pro-48-PoE (1) SFP2 connects to USW-Aggregation (2) Port3. USW-Pro-48-PoE (1) SFP1 connects to USW-Aggregation (1) Port3. USW-EnterpriseXG-24 (2) SFP2 connects to USW-Aggregation (2) Port2. USW-EnterpriseXG-24 (2) SFP1 connects to USW-Aggregation (1) Port2. USW-EnterpriseXG-24 (1) SFP2 connects to USW-Aggregation (2) Port1. USW-EnterpriseXG-24 (1) SFP1 connects to USW-Aggregation (1) Port1. To connect your Access Layer redundantly to your now redundant Distribution Layer you would follow: This gives your Distribution layer redundancy to the Routing Layer. Then connect LAN2 to USW-Aggregation (2). Starting from your Routing Layer, you would connect the UXG-Pro LAN1 to USW-Aggregation (1) with a 10Gbit DAC cable. Workstations, Desktops, Servers, Devices, Etc USW-EnterpriseXG-24 Switch Enterprise XG 24 (2) USW-EnterpriseXG-24 Switch Enterprise XG 24 (1) UXG-Pro-US Next-Generation Gateway Pro (Early Access) If I were designing this network I would use: If LTT wants to implement a correctly designed redundant network, they need at least two identical switches on each tier of the network prior to their WAN connection. NetworkChuck has a really great video explaining redundant network design, on the small scale and even scaled out to enterprise scale: It looks like all of the switches are being connected in a daisy chain, so while they have redundant power, if one of those switches bricks for any reason other than a failed PSU, every network device below it will also be disconnected from the rest of the network. That said, by making a product like this available and "easy to implement" it allows for novice network designers like myself and the LTT crew to make a critical mistake in planning for redundancy. It allows for modular design and upgrade potential so that UI can market the same switches to SOHO that don't mind if a switch goes down until a replacement can be sourced, as well as those looking to maximize network up time. It's definitely a cool idea, a decentralized secondary PSU for all the networking devices in the rack. Other hardware failures are literally just as likely as PSU related failures.Īs someone that recently looking into a similarly sized deployment of Ubiquiti gear for a small business, I find it interesting to see that the LTT crew appears to have fallen into the same redundancy fallacy as I initially did regarding the RPS platform. TL DR - LTT accounted for PSU related redundancy, but did nothing to deal with other hardware failure from the switches.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |