Network design of Enterprise Ecommerce Company
https://www.youtube.com/watch?v=vUK1YS88ssI - Server farm
This diagram shows a typical enterprise network architecture split into an internal campus network, an edge layer, and connections to external providers. The main idea is that the inside of the company mostly uses private IP addresses, while the boundary to the outside world uses public IP addresses and routing devices.
Campus network
The left side is the Enterprise Campus, where users, servers, and internal devices live. It is organized into layers: Access, Distribution, Core, and Server Farm.
Access layer connects end devices like PCs, printers, and access switches.
Distribution layer aggregates access switches and applies policy, routing, and segmentation.
Core layer is the high-speed backbone that moves traffic quickly across the campus.
Server farm is where internal application and data servers sit.
The repeated “Private Addressing” labels mean these internal devices use RFC 1918-style private IP space rather than Internet-routable addresses.
Edge and NAT
The middle section is the Enterprise Edge, which is the boundary between the internal campus and external networks. This is where traffic often passes through firewalls, routers, and NAT devices.
NAT stands for Network Address Translation. It lets many internal private hosts share one or more public IP addresses when they access the Internet, which is why the diagram shows private addressing on the inside and public addressing on the outside.
External connections
The right side shows the SP Edge or service-provider side, including connections such as ISP 1, ISP 2, PSTN, and older Frame Relay/ATM networks. These represent different ways an enterprise can connect to carriers, the Internet, remote users, or legacy WAN services.
The diagram also labels use cases like WAN, Internet, E-commerce, and Remote Access to show that the enterprise edge supports multiple traffic types and security domains.
Simple example
A laptop inside the campus might get a private address like 10.x.x.x, send traffic to the core, then reach the edge router where NAT translates it to a public address before the packet goes out to the Internet. When the reply comes back, NAT maps it back to the original internal device.
| Network Type | Common Protocol |
|---|
| Small Enterprise DC | - OSPF |
| Medium Enterprise DC | - OSPF / EIGRP |
| Large Enterprise DC | - OSPF |
| Data Center | BGP |
Comments
Post a Comment