The following table shows the components and requirements for managing each distributed 3-Tier Platform:
Table 101. 3-Tier Platform management component requirements
Multisystem management and 3-Tier Platform networks
High bandwidth, low error, and low latency L3 connectivity.
Modern data centers
A minimum of 10 GbE connectivity for high bandwidth and low latency.
Subnets or VLANs
There must be no subnet or VLAN overlap on the management solution or managed, distributed 3-Tier Platforms.
Multisystem management and 3-Tier Platform network subnets
Routable network subnets that use L3 to the respective networks.
Multisystem management and components
Enable VMware-supported IP address ports and protocol connectivity.
Note: Configure firewalls for the management solution and 3-Tier Platform subnets and ports.
Distributed management for storage
For LCM discrepancies, deploy more Element Manager VMs to support the following storage management software:
- PowerMax: Install Solutions Enabler on the Element Manager VM to manage a single array at a time.
- Dell Unity XT: Unisphere manages Unity XT arrays over TCP/IP connections to the array management IP addresses. Install the Unisphere CLI on the Element Manager VM to access the Unity XT arrays.
- PowerScale: OneFS storage administration manages PowerScale over a TCP/IP connection to the management IP address of the cluster.
- Secure Connect Gateway: Secure Connect Gateway is an embedded Linux appliance to monitor 3-Tier Platform storage arrays and SAN switches.
- PowerPath/VE and PowerPath Virtual/Management Appliance: A single instance of PowerPath Virtual or Management Appliance supports PowerPath/VE on servers in multiple 3-Tier Platforms. Servers are discovered individually or through a VMware vCenter Server instance.
- Cisco MDS: Cisco MDS SAN switches and directors are managed over standard TCP/IP connections.
Distributed management for virtualization
Multisystem management uses a highly redundant model to maintain service and is restricted to a single geographic location for a VMware vSphere HA cluster. A dedicated VMware vCSA manages local workloads. The number of supported production VMware vCSAs depends on the management solution configuration.
Production VMware vCSAs can manage multiple 3-Tier Platforms. Each managed 3-Tier Platform must be in its own VMware vSphere data center.
Production workload servers should be in a subordinate VMware vSphere Cluster with a dedicated VMware VDS. VMware vSphere production workload migration does not support inter-3-Tier platforms.
Size the management solution local vCSA and workload domain vCSAs appropriately. Take account of the following requirements for managing multiple distributed 3-Tier Platform vSphere resources:
- Each production VMware vCSA is a fault domain. Analyze the type and number of resources for a single production vCSA to manage.
- Each production vCSA is homogenous from a firmware and software perspective. Run the same vSphere release on the production vCSA and its managed resources on supported configurations.
- Each production vCSA is a single maintenance domain. Analyze change control processes and timelines with the number of resources that a single vCSA manages.
- High bandwidth, low error, low latency, L3 connectivity to each distributed 3-Tier platform must be available on the management solution 3-Tier platform vCSA. To provide high bandwidth and low latency between the production vCSA and managed 3-Tier platform cluster resources in modern data centers, 10 GbE connectivity is required. This connectivity level provides a consistent deployment and operational experience for all vSphere managed resources.
- Management solution components require IP address ports and protocol and port connectivity that is compatible with VMware to all managed distributed 3-Tier Platform resources. For more information, see VMware Ports and Protocols.
- Use L3 connectivity for production vCSAs to connect to multiple distributed 3-Tier Platforms. This reduces the risk of overlapping VLANs and duplicate subnets.
- Determine the total production vCSA requirements and do not exceed vCSA configuration limits.
- Review ELM configuration maximums if vCSA ELM is configured for a production vCSA.
- Duplicate names for the VDS, port group, and production hosts in a production vCSA may cause management and 3-Tier Platform orchestration issues. Rename the resources to reduce the risk of operation error or separate them into different data centers in the same vCenter Server instance.
- If needed, update administrative practices to set vCSA permissions at the vSphere data center level or host level.
vSphere ESXi and vCenter Server are the core components of the virtual infrastructure for the management solution and the 3-Tier Platform.