Datacenter Network Design
In this post, I will try to show the power of a clear and straightforward diagram for building and troubleshooting a complex datacentre
This project was for one of the most significant IT projects in Australasia, but here I want to talk about a small project, the physical Networking for one of the data centres.
Note: This project is almost eight years old, and all the names and configs in these diagrams have been replaced
Technical Requirements
- The solution MUST support IPV6
- The solution MUST support a multitenant environment
- The solution MUST support SDWAN
- The solution MUST provide tenant and customer separation
- The solution MUST support SDN
- The solution MUST support scale-up and scale-out
Solution
- Any one of the big brands would support IPV6
- v-Routers, v-Firewalls and vLAN will be used
- Any one of big brands would support SDWAN
- Managed to and Managed from design
- Any one of the big brands would support SDN
- any clustering will provide the solution
Physical Connectivity
In this diagram, you have all the physical locations (e.g. rack number), name of the device, functionality and IP address to connect to the device
since it is not a rack design, so you do not have the exact location in the rack, but instead, you have all the physical connectivity, speeds and identical port number, including connectivity to other infrastructures
having the port numbers in this diagram was handy as I could request a configuration on the exact port without searching a spreadsheet for the correct port number
The logical diagram presents a multi-tenanted multi-datacentre solution.
Building Block Architecture (BBA) patterns are everywhere in this design for instance; every tenant has the same component LB/Router, the same connectivity to the tools and internet, which would help for automation and simplify the troubleshooting
at this stage, we could imagine a new customer and see how this pattern could be applied to the solution
The Architecture Blog 