Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hide Disabled Ports in /Overview and Device/Ports #1141

Closed
Ftelf opened this issue May 27, 2015 · 8 comments · Fixed by #1228
Closed

Hide Disabled Ports in /Overview and Device/Ports #1141

Ftelf opened this issue May 27, 2015 · 8 comments · Fixed by #1228

Comments

@Ftelf
Copy link

Ftelf commented May 27, 2015

User story:
I have a network device with 12 ports. Only first 8 ports would be ever used and are connected at the moment. There seems like no way to disable the unused ports completely. If I set them as "Disabled" or/and "Ignored" I can still see them in /Overview
http://fii.cz/qqvbjxjg
Also they are bothering in Device/Ports
http://fii.cz/vumjc
Question how to handle this classification ?
http://fii.cz/djdat

Also for discussion if this should have been handled by the Disabled flag, which is "maybe" used for disable the polling of the iface. Maybe new flag named "Hide" would be more useful. This is up to you.

@SaaldjorMike
Copy link
Member

Did you shutdown the interfaces on the switches themselves?

@Ftelf
Copy link
Author

Ftelf commented May 27, 2015

I follow your point. Yes, this is something I figured out few minutes ago. I did that on few routers.
http://fii.cz/dksrhqze
The ports disappeared from the /Overview. I may live with them laying in graphs, they are greyed out.

But there are few devices like wireless bridges with internal loopback, bridges, management devices which cannot be disabled this way. And it's really flustrating to see them around.
http://fii.cz/ztmvymua

Also is quite a good practise not to put down all of the ports but leave one or two as a management emergency port. Well in such case it may be a good thing to still have such port graphed. But I can imagine that such port could have a inverted event policy. Like Down is good, do not mention in overview. So I can imagine, that this would handle a "Hide" Port flag.

@laf
Copy link
Member

laf commented May 27, 2015

We should fix this anyway so you don't need to disable the ports on your device.

As for internal loopback and things, you can add config options to filter those out: http://docs.librenms.org/Support/Configuration/#interfaces-to-be-ignored

@laf
Copy link
Member

laf commented May 28, 2015

@Ftelf

I've just tested this. Setting the port to be ignored for me stops it being shown on the overview page!

Can you send screenshots of the ports you've set to ignore and a screenshot of them appearing on the overview page?

@Ftelf
Copy link
Author

Ftelf commented May 29, 2015

This is really embarrassing. I did tried this again and the "Ignore" flag did the job. I had to overlook this when tried the combinations of the disabled and ignored. Sorry for wasting your time.

@Ftelf Ftelf closed this as completed May 29, 2015
@Ftelf Ftelf reopened this May 29, 2015
@Ftelf
Copy link
Author

Ftelf commented May 29, 2015

I can confirm, that "Disabled" ports disappeared from global /Overview list. But they are still present in Device/Overview and also in Device/Ports.
http://fii.cz/rvamv
http://fii.cz/tzaxnwz
http://fii.cz/hrdsvc
http://fii.cz/rtrmpbne

@YukonRob
Copy link

Sorry to ask this here, new to this format. I can't find anywhere (as per screenshots above) to actually change the disable/ignore/etc settings. I am using a newer build however (8d10089). Nothing comes up in the docs either.

@laf
Copy link
Member

laf commented Mar 13, 2016

What do you want to change? I'd probably suggest opening a new issue and reference this issue by doing #1141

@lock lock bot locked as resolved and limited conversation to collaborators May 20, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants