Locating the Global Managers in the network
Global Manager
s in the networkIn choosing locations for the platforms
that support the
Global Manager
s, there may be restrictions on locations that are not related to network and application efficiency. Locating the Global Manager
s may be based on the following considerations:- Geographical requirements: An organization may require that allVMware Smart AssuranceManagers be based in a single Network Operations Center (NOC). Other organizations might have theGlobal Managerin the NOC and underlying Domain Managers located in regional data centers.
- Corporate organizational requirements: For example, organizations that have a distributed business management might require that components be located to match the organization’s structure.Communication between applications is influenced by network speed and latency. Avoid configurations that require aGlobal Managerto receive information from other applications across WAN links with high latency. Instead, consider placingGlobal Managers on both ends of high-latency WAN links. The hierarchicalGlobal Managerconfigurations can be used to eliminate high-latency link issues for these situations:
- Domain Managers that connect to aGlobal Managerover a high-latency link: Use the basic hierarchical, hierarchical aggregation, or hierarchical mesh configuration to place aGlobal Manageron the same side of the high-latency link as theDomain Managers.
- A group of clients that connect to aGlobal Managerover a high-latency link: Use the basic hierarchical, hierarchical presentation, or hierarchical mesh configuration to place aGlobal Manageron the same side of the high-latency link as the group of clients.After you determine the configuration and locations of theGlobal Managers, add system names andGlobal Managernames to your solution architecture diagram. Define IP addresses and dedicated port numbers when needed. Establish a host naming convention and aGlobal Managernaming convention before you settle on any names.