NCM: Device Family not synching across landscapes
Article ID: 400931
Updated On:
Products
Issue/Introduction
When a new device family is created, both SpectroServers are present in the Exists List in the General Information View -> Edit Device Family->Landscapes view.
After the customer added commands and credentials in the OC view, the Landscape hosting our test devices moves automatically to the “Does not exist in” list. Why?
When we search for both NCM script family models using the Locator, only the commands and credentials on one of the Landscapes are displayed in the Information tab. The other family is empty in these places.
What can prevent that the inputs during Device Family configuration will be written to all Landscapes?
Environment
any supported Spectrum release
Cause
All symptoms were caused by lack of sync between Main Location Server and some Landscapes servers.
It was due to a wrong MAIN_LOCATION_HOST_NAME= entry in .locrc on non-MLS server.
Resolution
MAIN_LOCATION_HOST_NAME= entry in .locrc must point to MLS
The change requires the location server restart using a command:
$SPECROOT/bin/cmdC localhost 2 LOCSERV
Additional Information
other symptoms of the same configuration problem:
Feedback
