Hi Team,
I am working on a Service Template for a T-Vips TVG420 device and I would like some guidance on filtering table rows correctly.
In the existing Visual Overview, the alarm state for NAU2 Port 3 is calculated using:
Max|[cardvar:ElementNameTVIP2]:3|[cardvar:ElementNameTVIP2]:23:Filter=fullFilter=(28 REGEX '^.+(?<!Ethernet )(Port 3)$')|ALARM
From the protocol:
- PID
3=Alarm Status - PID
23=Current Alarms: Severity - PID
28=Current Alarms: Index [IDX]/ display key
The regex: ^.+(?<!Ethernet )(Port 3)$
is intended to:
- Include alarm rows ending with
Port 3 - Exclude rows ending with
Ethernet Port 3
For example:
FEC threshold exceeded Port 3 - should be included AND Ethernet Port 3 - should not be included.
I am now trying to move this logic into a Service Template, so the Visual Overview can simply use the alarm state of the generated service child.
In the Service Template I have selected:
Alarm Status
<strong><code>Current Alarms: Severity</code></strong>
For Current Alarms: Severity, the Included rows field appears to support wildcard-based inclusion, for example:
*Port 3
However, that would also potentially include:
Ethernet Port 3
which would not match the behaviour of the existing tested regex.
My requirement is to achieve the equivalent of: Include all rows ending in "Port 3" and EXCEPT rows ending in "Ethernet Port 3"
Inside a Service Template.
Is there any supported way to:
- Use a regex or
fullFilterexpression in the Included rows field of a Service Template, - Exclude rows based on a substring such as
Ethernet, - Or achieve the same result using another supported Service Template mechanism?
I would prefer to keep this filtering logic inside the Service Template rather than maintaining the parameter filter again in Visio.
Any recommended approach would be appreciated.
Thanks
Gourav Jain
Hi,
As far as I know, the Included Rows field in a service template does not support regular expressions or full filter expressions. Regular expressions are only supported for the Parameter Mask field.
For your use case, one possible workaround is to include the full index in the CSV file and use it as input data for the service template.
Hope this helps.