Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
3-Tier Platform Design Guide
Introduction Solution Design and Key Components Cisco UCS Managed Compute Layer Cisco Intersight Managed Compute Layer Network Layer Storage Layer Data Protection and Replication Management and Virtualization
Overview
Management components
iSCSI shared storage design
Management tools
Virtualization
Cluster configurations
Compute VLAN examples
Management applications
Managing multiple 3-Tier Platforms
Distributed management
Solution Configuration and Specifications References

Managing multiple 3-Tier Platforms

Home > Integrated Products > VxBlock 1000 and 3-Tier Platform Reference Architectures > Guides > 3-Tier Platform Design Guide > Managing multiple 3-Tier Platforms

Managing multiple 3-Tier Platforms

  • The integrated multisystem management solution manages more than one 3-Tier Platform.

    The solution connects to a single pair of management and ToR switches in a 3-Tier Platform. The data traffic must traverse the external network core to manage additional 3-Tier Platforms.

    The multisystem management solution hosts the workload domain VMware vCenter Servers. You can use a single VMware vCenter Server for multiple 3-Tier Platforms (up to the 2000 server limit) or purchase more VMware vCenter Server licenses to separate the workloads for each system.

    The following figure shows network connectivity for a multisystem management solution using a Unity XT array:

    A diagram of a multisystem management solution using a Unity XT[BM1][BM2]

    Figure 29.    Network connectivity for a Unity XT multisystem management solution

    VLANs 1611 and 1612 are for the management domain.

    VLANs 1631 and 1632 are for the workload domain.

    Note: DVSwitch-Mgmt uses VMNIC 4 and 5 when connecting to the Cisco Nexus 93108TC-FX3P. DVSwitch-Mgmt uses VMNICs 2 and 3 when connecting to the Cisco Nexus 92348GC-X.