Timeout status not clearing after comms are back

Solved1.10K viewsalarms SNMP timeout
3
2 Comments

Hi,

We have this issue with SNMP elements that do not clear the 'X' sign after getting connected again, as seen below:

The procedure we follow in such a case is to delete the stuck timeout alarm from DB and restart the element as follow:

Is this a known software bug or there could be something else involved?

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 11th July 2023
Ben Vandenberghe [SLC] [DevOps Enabler] commented

Sounds to me more like an issue with the design of the concerned driver. Do you have this on one specific type of element, or across multiple types?
Saddam Zourob [DevOps Advocate] commented

We do usually see them with the Linux Platform SNMP driver. I am not aware of seeing this happening to other protocols.

1 Answer

1
110 0 Comments

Hi Saddam,

If it's a driver provided by Skyline, can you please check whether you have the latest version?

If the issue still prevails then and it is a skyline driver, please contact our techsupport at techsupport@skyline.be, we might have to make a task and check the issue out to know what exactly is going wrong.

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 11th July 2023
You are viewing 1 out of 1 answers, click here to view all answers.