CA SPECTRUM Error: The parent landscape does not exist in the location server map for the local landscape (Legacy KB ID CNC TS31051 )

Document ID : KB000051790
Last Modified Date : 06/09/2018
Show Technical Document Details
Issue:
After attempting to expand a standalone Spectrum system into a Distributed SpectroSERVER (DSS) environment, the following error is seen;

SPC-OCA-10382: The parent landscape does not exist in the location server map for the local landscape.
 
Environment:
Spectrum 10.x
Cause:
The cause of the "The parent landscape does not exist in the location server map for the local landscape" error maybe the Fully Qualified Domain Name (FQDN) of the Main Location Server (MLS) is entered in the $SPECROOT/LS/.locrc file on the SpectroSERVER systems.
Resolution:
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:

LOC_SERVER_SOCKET_NUMBER=0xdaff
MAIN_LOCATION_SOCKET_NUMBER=0xdaff
MAIN_LOCATION_HOST_NAME=HostName.mydomain.com
MAX_CONNECTIONS=750
orb_args=-ORBpropStorage.natfwrc

MLS using HostName:

LOC_SERVER_SOCKET_NUMBER=0xdaff
MAIN_LOCATION_SOCKET_NUMBER=0xdaff
MAIN_LOCATION_HOST_NAME=HostName
MAX_CONNECTIONS=750
orb_args=-ORBpropStorage.natfwrc

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)

 

 

Additional Information:
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:

spectrumhost.usa.mydomain.com
spectrumhost.emea.mydomain.com

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

(Legacy KB ID CNC TS31051 )
Original Problem Environment:
SPECTRUM 09.00.00.00
CallT0000225276
swbug021944