After attempting to expand a standalone Spectrum system into a Distributed SpectroSERVER (DSS) environment, the following error is seen;
DX NetOps Spectrum 20.2 or later
The cause of the "The parent landscape does not exist in the location server map for the local landscape" error maybe that the Fully Qualified Domain Name (FQDN) of the Main Location Server (MLS) is entered in the following file on either one or more SpectroSERVERs in the DSS:
Check the $SPECROOT/LS/.locrc files on the SpectroSERVER systems to see if the Main Location Server (MLS) is configured using the Fully Qualified Domain Name (FQDN). If it is, change it to use the hostname. For example:
MLS using FQDN:
MLS using HostName:
After making the change, kill the running LocServer process on each of the SpectroSERVER systems. The processd daemon will restart a new LocServer process
Then restart the Spectrum OneClick systems (Spectrum Tomcat)
From CA Spectrum 9.x and later, it doesn't matter if the hostname configured on the SpectroSERVER system is FQDN, we advertise the hostname in the Location Server (LocServer). This was done to resolve an issue in previous SPECTRUM versions where the SpectroSERVER host had multiple IP addresses resolved to different domains.
For example: A SpectroSERVER host has multiple subnets, with the following names:
We will advertise "spectrumhost" in the LocServer and will bind to all available interfaces. We therefore require that `spectrumhost` be resolvable for any host that wants to connect to it.
For those systems on the usa.mydomain.com network, spectrumhost should resolve to spectrumhost.usa.mydomain.com. For those systems on the emea.ca.com network, spectrumhost should resolve to spectrumhost.emea.mydomain.com.