Overview

Role in the system

The connective layer between users, applications, data centres, cloud, branches and field sites. Bandwidth, latency, segmentation and redundancy decisions made here determine how every other layer behaves under load and fault.

Network design must consider performance, availability, segmentation, manageability and security as one combined problem.

Campus and multi-site wide-area networkA campus network with redundant core, distribution and access layers connects through a wide-area edge to two independent carriers. Three branch sites each connect to both carriers, one primary and one secondary. Segments for users, servers, cameras, sensors, guests and management traffic are kept separate across the network, and a network monitoring system observes all of it.CampusCore 1Core 2Distribution 1Distribution 2Access 1Access 2Access 3Redundant uplinks and link aggregation:no single uplink isolates an access switch.WAN edgefirewall, routingCarrier AprimaryCarrier Bsecondary, diverse routeBranchesLarge branchrouting, switching, wireless, local securityBranchSD-WAN edge, switching, wirelessSmall branchSD-WAN edge, backup link,local survivabilitySolid: primary pathDashed: secondary pathSegments kept separate end to endUsersServersCamerasSensorsGuestsManagementNetwork monitoringDevice availability, link utilisation, packet loss, latency, error rates, configuration and routing changes, environmental and power alarms
  • Data path
  • Power
  • Management path
  • Fault or alert
Campus, wide area and branches. Redundant campus layers, dual carriers, SD-WAN branch edges and segment separation, observed by network monitoring.

Network domains

Campus networks

A structured core, distribution and access hierarchy keeps failure domains small and makes the network predictable to operate and expand.

Capabilities may include:

  • Core switching
  • Distribution switching
  • Access switching
  • Structured network hierarchy
  • Redundant uplinks
  • Link aggregation
  • Virtual local area networks
  • Quality of service
  • Multicast
  • Network access control
  • Management networks
  • Power over Ethernet
  • Network monitoring

Branch networks

Branch design balances central policy management against local survivability when the wide-area link is down.

Branch architecture may include:

  • Routing
  • Switching
  • Wireless access
  • Local security
  • Wide-area connectivity
  • Application prioritisation
  • Backup links
  • Remote monitoring
  • Central policy management
  • Local survivability

Wide-area networks

Latency and packet loss, not just bandwidth, decide whether an application is usable over a given path, and carrier diversity decides whether a single outage isolates a site.

Wide-area design should consider:

  • Primary and secondary connectivity
  • Bandwidth requirements
  • Latency
  • Packet loss
  • Application priority
  • Encryption
  • Routing
  • Link failover
  • Carrier diversity
  • Monitoring
  • Service-level measurement

Software-defined wide-area networking

SD-WAN moves path selection from static routing to policy: traffic follows the link that currently meets the application’s requirements.

Software-defined wide-area networking can provide:

  • Centralised policy
  • Application-aware routing
  • Link optimisation
  • Dynamic path selection
  • Simplified branch deployment
  • Central visibility
  • Security integration
  • Reduced dependency on one carrier

Wireless infrastructure

Wireless is designed for capacity as well as coverage; a signal that reaches every corner can still fail when device density rises.

Wireless design should include:

  • Coverage
  • Capacity
  • User density
  • Device density
  • Interference
  • Roaming
  • Authentication
  • Guest access
  • Application requirements
  • Outdoor conditions
  • Backhaul
  • Controller architecture
  • Monitoring

Segmentation and visibility

Network segmentation

Each boundary below is a policy decision: what may cross it, in which direction, and how crossing is logged.

Segmentation may be required between:

  • Users
  • Servers
  • Applications
  • Security systems
  • Operations systems
  • Cameras
  • Sensors
  • Guest devices
  • Management traffic
  • Third-party systems

Network management

Visibility covers condition (is it up, how loaded, how many errors) and change (what was reconfigured, and what routing did as a result).

Network visibility should include:

  • Device availability
  • Interface status
  • Link utilisation
  • Packet loss
  • Latency
  • Error rates
  • Configuration changes
  • Routing changes
  • Environmental alarms
  • Power status
  • Security events

Discuss an ICT Requirement

Describe the requirement, the locations involved and where the project stands. We will respond with the technical questions that need answering first.

Discuss an ICT Requirement