Hi,

 port_label is cleaned field (from unusefull information), generated based on multiple possible Oids (ie ifDescr, ifName).

But anyway in db such fields ifDescr and ifName stored as is without changes and can used for alerts, etc.

port_label is short as possible for display in most pages.

I not see reasons for keep such data ( - Printer) for display in port names.
This exactly should be stored in ifAlias (wich is port description).

But.. if your device not support correct ifAlias, I can try to parse ifAlias for that os.

Attach debug discovery:
./discovery.php -d -m os,ports -h <device>
Christian
5 April 2018 at 18:37
Hello,

I was introduced to Observium in early March, and coming from a Nagios / Cacti type of monitoring, I am completely impressed with the power of Observium.  I have CE 17.9.0 and am in the process of deploying it at my location.

I have a couple of smart switches that support SNMP, but are not capable of a Port label.  Thus, Observium shows the switch as Port 1, Port 2, Port 3 instead of my desired “Port 1 - Bandwidth Control” “Port 2 - Linux Server” “Port 3 - Printer” … that sort of thing.  

I found that I could use NaviCat to edit the MySQL database to properly label the ports, but then the next polling cycle restores the generic port label 5 minutes later.


Is there any way for me to modify the polling to leave the label alone?  I don’t want to look into “locking” the [port_label] field of the database tables.

If I may also ask, is there any way to tell Observium that a down port is the normal (green) condition?  I have some switches with ports that are not active, and if something is plugged into them, an alert would be handy.

Thank you again for this amazing software.

Christian




_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

--
Mike Stupalov
Observium Limited, http://observium.org