This reports any trunk port that is on a "switch-router" that is: <<int>> is down, line protocol is down (inactive).

Assuming the only way to fix/clear/resolve this is to administratively down the interface(s)?

That is correct. If you have a bunch of trunks in up/down state, how do you know when a redundant trunk has failed? I find it difficult to track failed trunk ports in a redundant network without some mechanism.

There are at least two mechanisms:

1. Administratively shutdown any unused trunk port. If it is configured as a trunk, shouldn't it be up/up? Perhaps it is easy to just leave the interface in up/down state, but then it is difficult to track which ports should be up/up.

2. You could use a tag on the interface description and only alert on trunk ports that have a tag that means that it is an important link.

If you don't care about this issue, then suppress it.

I have a couple ports that were trunk ports at one time, biut are no longer connected, that are generating this alarm.

So I shut them down...  Still in alarm.

So I configured them to not be trunk ports...  Still in alarm.

Very annoying!