Good morning! What is the best way to add Elements that are housed in Mobile Vans or containers?
These elements are most of the time unavailable. The Views that contain these elements will always be in alarm. Is it possible to suppress the unavailable state alarm until the element is in use?
I was thinking of hiding these elements and passing the parameters from these elements to a virtual element.
In a booking context, one could indeed use the booking orchestration to start/stop those remote elements, so that they would only generate alarms and time-out events during the active time window.
If the elements are used only within a specific fixed time-frame (e.g. only relevant between 18.00h and 23.30h every weekday), then a fixed schedule can be used (without the need to involve SRM).
Question is indeed if and how DataMiner can be aware of the "until the element is in use".
I suspect that it might also be as follows: you never want to see the time-out on those elements, because when they are in time-out that's because they are not used, and when they are not in time-out, they are in use. So, in that case, we should be more looking for a solution where if one of those elements goes into timeout, then DataMiner suppresses that time-out. Is that how you would want it to be?
In that case, you could make a simple correlation rule that triggers on a Time-out happening (and some additional filtering, e.g. on an element in that specific View, or on those specific elements, etc.).
Upon triggering of the correlation rule, you would specify as an action an Automation script. In that script we should then mask the element, and also unmask it again when the time-out is gone. Not sure if this is doable. Let me check with some people that have more experience on this.
I checked already and we would have to mask the entire element (because masking just the time-out alarm apparently does not make the time-out icon disappear in the surveyor tree – and not even sure if this is intended or a bug). But masking the entire element makes it go away. The correlation rule supports triggering again upon clearing of the event, so that’s ok to then unmask the element. Mainly not sure about the script. The latter can be linked to the element that triggered the correlation, but not sure how to set it up exactly.
Let’s check further and we’ll circle back to you.
You could use an automation script like below, and trigger it from a correlation rule as Ben described. I’m assuming all elements of a certain van or container are in a single view here, and masking all elements in that view.
using Skyline.DataMiner.Automation;
public class Script
{
public static void Run(Engine engine)
{
string elementName = engine.GetScriptParam(“timeOutElement”).Value;
Element e = engine.FindElement(elementName);
string viewName = e.FindView();
Element[] elements = engine.FindElementsInView(viewName);
foreach (Element element in elements)
{
element.Mask(“NotInUse”);
}
}
}
Thanks for this advice!
Hallo Ben, that is more or less the idea.