Common configuration elements
Platform configuration
The deployment requirements and methods for components outside the NSP cluster can vary. However, some aspects of platform configuration are common to all components.
Time synchronization
|
CAUTION Service Degradation |
Some components, for example, members of an etcd cluster, fail to trust data integrity in the presence of a time difference. Failing to closely synchronize the system clocks among components complicates troubleshooting and may cause a service outage.
Ensure that you use only the time service described in this section to synchronize the NSP components.
The system clocks of the NSP components must always be closely synchronized. The RHEL chronyd service is the mandatory time-synchronization mechanism that you must engage on each NSP component during deployment.
Note: Only one time-synchronization mechanism can be active in an NSP system. Before you enable chronyd on an NSP component, you must ensure that no other time-synchronization mechanism, for example, the VMware Tools synchronization utility, is enabled.
RHEL /etc/hosts file
You must edit the /etc/hosts file on a component station to include:
An entry consists of one line for each server that maps the server IP address to the server hostname. The following is an example hosts file for an NSP deployment that has Chicago and New York data centers; each data center has three NSP cluster members and redundant NFM-P main servers:
198.51.100.7 nsdchicago1.company.org
198.51.100.8 nsdchicago2.company.org
198.51.100.9 nsdchicago3.company.org
198.51.100.13 nfmpchicago1.company.org
198.51.100.14 nfmpchicago2.company.org
203.0.113.5 nsdnewyork1.company.org
203.0.113.6 nsdnewyork2.company.org
203.0.113.7 nsdnewyork3.company.org
203.0.113.17 nfmpnewyork1.company.org
203.0.113.18 nfmpnewyork2.company.org