DX NetOps

 View Only

  • 1.  interface filtered not polled

    Posted Dec 19, 2025 10:35 AM

    Dear Community, could you help me? I'm being asked to register an interface, but when it searches for the interface, it appears as filtered and not polled.



    -------------------------------------------


  • 2.  RE: interface filtered not polled

    Posted Jan 12, 2026 12:02 PM

    Can you check your metric family condition, its getting filtered there.

    -------------------------------------------



  • 3.  RE: interface filtered not polled

    Posted Jan 15, 2026 10:40 AM

    Thank you for your response. We checked, through an OID query, and the interface is administratively and operationally down. My user is asking if, when the interface is administratively and operationally up, the "no polled" filter will be automatically removed and it will be recognized automatically.

    -------------------------------------------



  • 4.  RE: interface filtered not polled

    Posted 28 days ago

    I take it that you are talking about PM - in particular with the Data Agg. By default, for a fresh install of PM, there is no Network Interface monitoring. This has to be enabled and assigned to a Collection for interfaces to be polled.

    Now, if you look into the Monitoring Profile for the Network Interface polling, you will find that there is a default component filter that is applied.  In fact, it is one of the few (if only) monitoring profiles that does have a component filter applied by default. The rule is "Administrative Status does not equal down". What this means (it is a double negative) is that if the interface is admin down then the interface is not polled but if it is admin up then it is.

    The assumption here is that you have NOT touched this component filter. I would suggest NOT touching it at all. The reason for the component filter is that if you have a bunch of devices (switches being a good example), then they will have potentially a lot of interfaces that aren't active. As such, why poll something that isn't active?!?

    Now, to answer the question about it becoming responsive, well, by default, there is Change Detection setup (set at 24 hours) for the Network Interface monitoring profile. What this means is that the components that make up devices that are assigned to this profile are automatically "re-discovered" every 24 hours. If there are any changes then PM will automagically update the components. In the case of an interface becoming available (as in it is now admin up - someone has plugged something into it), then without updating PM manually (say through forcing an Update Metric Family), PM will pick up the interface within 24 hours and start polling it.

    -------------------------------------------