Hello,
When using a Cisco DCM element in a templated service and one table parameter enters alarm state, targeting only one service, all services sharing this element go into alarm state highlighting the same parameter, even though they shouldn't. So far I have observed this behavior with the "Alarms" table and "Service descrambling table".
I specified the filter for the included parameters to use a table row identifier which is unique to, and supplied upon creating each service so one alarm should not impact any other services.
This works well with other protocols, just not with Cisco DCM and therefore I am wondering if I am overlooking something or if this could maybe a bug?
Dataminer release 10.2.0.0-12184 CU6
DCM protocol version 1.0.3.73
Just wanted to add that this issue is resolved. It was a fault on my part.
In the templated service, if you enter the optional input parameter "N/A" it blanks out the input data field which has similar behavior to the "*" wildcard. This causes all services with that N/A value to enter alarm state even if in reality there is only one service in alarm since the affected parameter impacts all others as well due to the * behavior.