How to not discover Interfaces that are DOWN ( or not UP)

[mimimi (Y0d0g)]

Hello,

Modern Server have a lot of network interfaces.

We do not use all of them, how can I make sure that only interfaces with a link (up)
are discovered ?

In this case we are not interested in eno5, eno6, eno7, eno8

Unfortunately we can not use “disabled services” e.g. on eno5 because
we have no standards in our server fleet. Sometimes eno5 needs to be monitored.

I hope it is possible to skip/ignore Interfaces that have state “unknown”, is it ?

Thank in advance!

[rprengel (Ralf Prengel)]

Hallo,
try disabled services.
Ralf

[r.sander (Robert Sander)]

There are several configuration options that change the behaviour of checkmk wrt network interfaces.

Read Network Monitoring with Checkmk 2.0: Three rules to rule them all for a start.

[mimimi (Y0d0g)]

Well, there is a rule which could do what I am looking
for, but it does not seem to work for Linux Hosts:

Service discovery rules
    Network interface and switch port discovery

     Conditions for this rule to apply
       Specify matching conditions
         Match port states
          [x] 1 - up
          [ ] 2 - down
          [ ] 3 - testing
          [ ] 4 - unknown
          [ ] 5 - dormant
          [ ] 6 - not present
          [ ] 7 - lower layer down
          [ ] 8 - degraded

[kdeutsch (Karl Deutsch)]

Hi,
that’s the correct rule for this. Have you done a bulk discovery after setting up the rule? You have to use the 3rd Mode (“Add new services … remove vanished services”).

Karl

[mimimi (Y0d0g)]

Thanks Karl,

yes I manually did a Check_MK Discovery > Edit services without success.

And I now even did a cmk -II -v <servername> but it still discovers the lnx_if which are in unknown state.

The interesting part is that half of the rule is respected:

The Appearance of network interface > Use alias is respected but
not the Match port states > [x] - up and [ ] 4 - unknown part.

[mimimi (Y0d0g)]

Okay, now I got it working.

I have had two Network interface and switch port discovery rules in place.
One in the Main folder and one in a subfolder.

I assumed the one in the subfolder is more specific and winns but somehow the rule from the Main folder won.

Whatsoever I am now using ony one Network interface and switch port discovery in the main folder and it works like it should.