Error: OneClick log alarms appearing on random SpectroSERVER landscapes in DX NetOps Spectrum

Products

• Network Observability
• Spectrum

Issue/Introduction

In a multi-landscape (DSS) environment, administrative alarms regarding OneClick web server log directory size limits (e.g., `webtomcat/logs`) appear on a seemingly random SpectroSERVER landscape rather than the Main Location Server (MLS)

Environment

* DX NetOps Spectrum (All Versions)

* Multi-landscape / Distributed SpectroSERVER (DSS) configuration

Cause

The `SizeCheckerTask` in OneClick uses a method to create events that does not specify a target landscape. Instead, it retrieves the first available connected landscape from the domain list. This results in the event and subsequent alarm being created on the VNM model of whichever landscape is first in the internal list.

Resolution

Behavior is functioning as designed (FAD) 

 

Workaround

To ensure OneClick log alarms are placed on the MLS, follow these steps to control the connection order:

1. Stop the OneClick Tomcat service.

2. Ensure the Main Location Server (MLS) SpectroSERVER is up and running.

3. Start the OneClick Tomcat service.

4. Verify that the MLS is the first landscape to connect to OneClick before other landscapes in the DSS environment are started or connected.