Parent folderOpen Confluence

RWS Architecture article

DC Network Structure

DC Network Structure is the product-neutral architecture building block for data-center network structure, segmentation, and transport connectivity. It states what DC 3.0 needs fro

  1. Typeabb
  2. Statuscandidate
  3. Domainnetwork
On this page
  1. ABB DC Network Structure
  2. Summary
  3. Capabilities
  4. Constraints
  5. Service Description
  6. Roadmaps
  7. Landing Zones
  8. Interfaces
  9. Dependencies
  10. EIRA Alignment
  11. Available SBB's

ABB DC Network Structure

Summary

DC Network Structure is the product-neutral architecture building block for data-center network structure, segmentation, and transport connectivity. It states what DC 3.0 needs from this capability before a concrete SBB, product, or operating model is selected.

Capabilities

  • Provides data-center network structure, segmentation, and transport connectivity.
  • Defines the functional, technical, security, and quality expectations that SBBs must satisfy.
  • Keeps service ownership, interfaces, and consumption boundaries visible before product selection.
  • Enables traceability from architecture intent to implementation, operational evidence, and consuming services.

Constraints

  • The resulting SBB must fit the networks ownership model and document the support, lifecycle, and service-management boundary.
  • Security, privacy, logging, evidence, and compliance controls must be explicit enough to assess BIO2-aligned implementation where applicable.
  • Network design must support explicit segmentation, IPv6 planning, observability, and automated validation.
  • SBBs must avoid patterns that hide workload identity or prevent traceable routing decisions.

Service Description

This ABB offers a network foundation service that provides standardized connectivity, segmentation, routing, and underlay or overlay structure for DC 3.0. It is consumed by solution architects, platform teams, and service owners as the capability contract for selecting and shaping SBBs.

The service description remains implementation-neutral: product selection, hosting pattern, detailed runbooks, and service levels belong in the mapped SBB and related ADRs.

Roadmaps

  • Baseline: confirm scope, service ownership, constraints, and acceptance criteria for DC Network Structure.
  • MVP: validate the mapped SBB implementations and record the selected support and lifecycle model.
  • Next: add measurable service levels, evidence requirements, and roadmap dependencies once the SBB is selected.

Landing Zones

  • Private cloud and central DC 3.0 landing zone for core infrastructure and platform services.
  • Government cloud or external cloud landing zones only when the SBB documents the required control set, connectivity model, and data classification fit.

Interfaces

  • BGP, EVPN, VRF, VLAN, and routing interfaces as selected by network design.
  • Fabric automation and validation interfaces.
  • DNS, IPAM, load-balancing, and platform network attachments.

Dependencies

  • Depends on dns-dhcp-ipam for a supporting capability or integration boundary.
  • Depends on datacenter-infrastructure-management for a supporting capability or integration boundary.
  • Implemented by cisco-nexus-9000, cisco-nx-os as currently mapped SBB traceabilities.
  • Consuming ABB and SBB dependencies must be recorded as links when solution design identifies concrete upstream or downstream use.

EIRA Alignment

Available SBB's

  • cisco-nexus-9000 - Cisco Nexus 9000 is a candidate solution building block for the translated DC 3.0 ABB model. It remains candidate until the responsible architects confirm service ownership, support model, and acceptance criteria.
  • cisco-nx-os - Cisco NX-OS is a candidate solution building block for the translated DC 3.0 ABB model. It remains candidate until the responsible architects confirm service ownership, support model, and acceptance criteria.