Trigger with a large expression not showing precise problem

[udmsp]

Hello Zabbix forum,

I have created a trigger like this:

Expression:
{stadsref-wls06.prod.umit.dk:net.tcp.listen[5556].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[5557].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[5558].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[7001].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[7003].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[7005].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[8000].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[8005].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[8010].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[8015].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[8020].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[8025].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[8030].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[8035].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[8040].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[8045].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[8888].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[9001].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[9002].last()}=0 or
{stadsref-wls06.prod.umit.dk:net.tcp.listen[9003].last()}=0

The thing is that the problem always shows as if port 5556 is down, even if another port is down - I suppose Zabbix picks the first port on the list:

UFM: PROBLEM: Trigger for ports not in LISTEN mode for Stads server Stadsref-wls06

Trigger: Trigger for ports not in LISTEN mode for Stads server Stadsref-wls06
Trigger status: PROBLEM
Trigger severity: High
Trigger URL:

Item values:

1. Port 5556 (stadsref-wls06.prod.umit.dk:net.tcp.listen[5556]): 1



Anybody who knows if this can be corrected somehow ?

Best regards
Michael