Locate Domain Managers and platforms
Domain Manager
s and platformsWhen choosing locations for the platforms that support components, take note of restrictions on locations unrelated to network and product efficiency:
- Locations based on geography. Some organizations require allDomain Managers to be based in a single Network Operations Center (NOC). Others have theGlobal Managerin one NOC and the underlyingIP Managerin a regional data center.
- Locations based on corporate organizational requirements. For example, organizations with distributed management require that the deployment be partitioned to support a portion of a network that is split along bureaucratic rather than technical lines.
- Locations based on network security design. For example, if parts of the network are highly secured and ICMP or SNMP polling between these network segments is not allowed, separateIP Availability Managers have to support each segment.Polling and discovery are influenced by network speed and latency. If possible, consider network efficiency when locatingDomain Managers. Avoid configurations that require anDomain Managerto discover or poll large portions of the network across lower speed WAN links or other network bottlenecks. Consider placingDomain Managers on higher speed LAN networks.Add system names andDomain Managernames to your solution architecture diagram. Define IP addresses and dedicated port numbers when needed.Establish a host naming convention and aDomain Managernaming convention before you decide on any names. Specify the locations for the hosts that support theIP Availability ManagerandIP Performance Managers on the architecture solution diagram.