+90 (212) 915 1717satis@trustnet.com.tr
Support RequestRemote Support RequestBlog
EN
Trustnet

Search the published site content.

Contact us
Server corridor with red lighting

Data Center Networks

Design data centre traffic around application dependencies.

Discuss your requirements

Overview

East-west and north-south flows, latency requirements and failure domains are evaluated. Segmentation, redundant connectivity and capacity planning are clarified with application teams. Monitoring and configuration management support operability.

Fabric design around application dependencies

Do not reduce data-centre networking decisions to port counts. Review east-west traffic, external connectivity, administrative access and security boundaries together. In an ACI option, the leaf-spine fabric, APIC administration and application policy perform distinct roles. EPG and contract design should follow an application-owner-approved traffic matrix. Record existing VLAN and gateway dependencies before migration. The drawing is Cisco’s basic ACI reference; it neither makes ACI mandatory for every data centre nor establishes a capacity guarantee.

CISCO · Figure 1

Cisco ACI: physical fabric

Select nodes to read their roles; zoom or enter full screen to follow the connections.

WAN or CampusSpine 1Spine role interconnecting fabric leaves. The source shows two spines.Spine 2Spine role interconnecting fabric leaves. The source shows two spines.Leaf 1Leaf connecting workloads, APICs or external networks. Each source leaf connects to both spines.Leaf 2Leaf connecting workloads, APICs or external networks. Each source leaf connects to both spines.Leaf 3Leaf connecting workloads, APICs or external networks. Each source leaf connects to both spines.Leaf 4Leaf connecting workloads, APICs or external networks. Each source leaf connects to both spines.Server 1Physical server dual-attached to the first pair of leaves in the source.Server 2Physical server dual-attached to the first pair of leaves in the source.Server 3Physical server dual-attached to the first pair of leaves in the source.Server 4Physical server dual-attached to the first pair of leaves in the source.APIC 1Member of the fabric policy and management cluster, attached to the last two leaves. It is not an inline user-traffic hop.APIC 2Member of the fabric policy and management cluster, attached to the last two leaves. It is not an inline user-traffic hop.APIC 3Member of the fabric policy and management cluster, attached to the last two leaves. It is not an inline user-traffic hop.External router 1External router connecting the border-leaf pair to WAN/campus in the source.External router 2External router connecting the border-leaf pair to WAN/campus in the source.VMVirtual workload shown below a source server. The icon does not add a separate physical link.VMVirtual workload shown below a source server. The icon does not add a separate physical link.VMVirtual workload shown below a source server. The icon does not add a separate physical link.VMVirtual workload shown below a source server. The icon does not add a separate physical link.VMVirtual workload shown below a source server. The icon does not add a separate physical link.VMVirtual workload shown below a source server. The icon does not add a separate physical link.VMVirtual workload shown below a source server. The icon does not add a separate physical link.VMVirtual workload shown below a source server. The icon does not add a separate physical link.Physical fabric · APIC cluster · Virtual workloads
  • Fiziksel bağlantı / Physical connection
Explore the diagram

Select a node to read its role. Drag to pan or use the buttons to zoom.

Cisco physical fabric: two spines, four leaves, dual-attached servers and three APICs. WAN/campus connectivity uses the border-leaf pair. EPGs and contracts are not added as physical cables.

Controlled transition

Inventory and application dependencies establish the baseline. Architecture, capacity expectations and security rules are clarified with the relevant teams. Pilot scope, acceptance criteria and rollback steps are documented before implementation. Migration waves follow business impact; each wave compares essential access, critical application flows and monitoring evidence.

Handover and operations

Topology, configuration ownership and maintenance procedures belong in the handover. Monitoring and escalation follow the organisation’s operating model. Product and service scope is clarified through discovery; support levels are agreed contractually. Share your requirements with Trustnet to assess practical options for your existing infrastructure.

Technical insights

Article

Cisco ACI: From Fabric to Application Policy

Read spine–leaf fabric, APIC, EPGs and contracts together, and plan a data-center transition around application dependencies and verifiable acceptance criteria.

6 October 20264 min read

Technology Partners

All technology partners

Services

  • Consulting and Assessment

    We assess your existing infrastructure and business requirements, recommend suitable technology and support optimization and implementation. Our consultancy covers networks, data centers, unified communications, security and network optimization.

  • Architecture Design

    We plan, implement and commission network, server and security infrastructure. Scope includes data centers, virtualization, storage, backup and disaster recovery, with handover and ongoing management where agreed.

  • Deployment and Integration

    We address network, system and security deployment from site readiness through controlled transition and operational handover.