Skip to main content

Hello,

 

When I am trying to use Blocked-Packets-Per-Interface  feature on pfSense, I get the following error : UNKNOWN: Need to specify OIDs.

 

Same when I try to launch the following command (from centreon documentation) :

/usr/lib/centreon/plugins/centreon_pfsense.pl \
    --plugin=apps::pfsense::snmp::plugin \
    --mode=pfinterfaces \
    --hostname='10.0.0.1' \
    --snmp-version='2c' \
    --snmp-community='my-snmp-community' \
    --filter-name='em.*' \
    --warning-traffic-in-block='80' \
    --warning-traffic-out-block='90' \
    --critical-traffic-in-block='80' \
    --critical-traffic-out-block='90' \
    --use-new-perfdata

 

I activated my IT-100 license and installed pfSense plugin. Any idea of what could be the issue ?

 

Thank you.

👋

 

@ElFabinou if you have updated the command to match your setup you can add --debug to see what else it gets us

 

/usr/lib/centreon/plugins/centreon_pfsense.pl \
    --plugin=apps::pfsense::snmp::plugin \
    --mode=pfinterfaces \
    --hostname='10.0.0.1' \
    --snmp-version='2c' \
    --snmp-community='my-snmp-community' \
    --filter-name='em.*' \
    --warning-traffic-in-block='80' \
    --warning-traffic-out-block='90' \
    --critical-traffic-in-block='80' \
    --critical-traffic-out-block='90' \
    --use-new-perfdata --debug

 

When a new service gets added you can also get the command by going to “ Monitoring > Resources Status” selecting the service and get access to the command from the right panel. You can use that to run it in the terminal as centreon-engine user.

 

You can also begin with the Troubleshooting guide

 

https://docs.centreon.com/pp/integrations/plugin-packs/getting-started/how-to-guides/troubleshooting-plugins/

 

🤞

Hello,

 

Thank you for your answer, here is the result I get from this command :

 

Any idea ? Thank you !

Is there an particular one that you are looking for? 

 

    --filter-name
            Filter by interface name (can be a regexp).

 

I had to put a netgate pfsense box in centreon today, but I had that same issue as OP

 

the template out of the box has multiple issues :

  • the Blocked-Packets-Per-Interface service in the host template uses the macro FILTER = “em.*”
  • the discovery for the interface is broken, and all the scanned interface are set with the filter “em.*

there are no interfaces called “em.*” in the pfsense box (paid version 23.9) 

on the physical box the relevant interfaces are prefixed“mvneta”

on a free edition (as a VM) they are prefixed “vmx” 

you get a “.” when there are vlan, like “mvneta1.10”

 

I’m guessing the “em.*” was something on a old pfsense release, and this is now hard coded in the custom template, but as the discovery is not setting the correct name all the interface check seems broken

 

a quick fix for the autodiscovery

put that in the FILTERNAME :

^$name$$

like any nic autodiscover, and also remove “em.*” from the interface

 

in the “ Blocked-Packets-Per-Interface “ service, simply replace “em.*” by “.*”

Reply


Terms & ConditionsCookie settings