SpectroSERVER is not polling Pingable devices behind Secure Domain Connectors (SDC).
The issue only occurs for Pingable devices. SNMP managed devices on the same SDC do not have this issue.
The problem raised after upgrading Spectrum.
DX NetOps Spectrum: Any version
It appears that Catalog corruption is the root cause of this issue.
Internal testing confirms this: The poll attribute values update correctly with a working SSdb with the local SDC, but pingable devices become unreachable when using the customer's non-working SSdb with the same local SDC.
Perform the following steps in their environment to resolve the issue:
1. Capture the latest SSdb file by running an OLB on the problematic landscape.
2. Stop the SpectroSERVER.
3. Navigate to the $SPECROOT/SS/ directory and remove all .ix and .db files:
rm -rf *.db
rm -rf *.ix
4. Copy the MLS catalog SSdb file to the problematic landscape.
5. Load the catalogs from the MLS database file:
../SS-Tools/SSdbload -ic <MLS catalog SSdb>
6. Load only models from the backup file from step 1:
../SS-Tools/SSdbload -m <last backup file>
7. Start the SpectroSERVER and recycle the Tomcat server and its clients.
8. Verify the behavior of the pingable devices.