Not related.Not sure if its related, but when running the discovery to update the port_label with Mikes fix I noticed a LOT of this message in the vlans module across multiple devices:
Invalid arguments passed into function get_port_by_index_cache(). Please report to developers.Invalid arguments passed into function get_port_by_index_cache(). Please report to developers.Invalid arguments passed into function get_port_by_index_cache(). Please report to developers.Invalid arguments passed into function get_port_by_index_cache(). Please report to developers.Invalid arguments passed into function get_port_by_index_cache(). Please report to developers.
On 15 March 2016 at 11:09, Tim Cooper <lists@coop3r.com> wrote:
That's great! Looks good, thanks Mike!Hi,
haha.. first time I see such ifDescr :)
fixed in r7675.
On 15.03.16 12:31, Tom Laermans wrote:
I think that's best! Mike's been away for a little while and now that he's back it's probably the most efficient to work via JIRA.
Tom
On 03/15/2016 10:00 AM, Mailing Lists wrote:
Is it worth me logging this in JIRA so it can be looked at when time allows?
On 4 March 2016 at 14:56, Adam Armstrong <adama@memetic.org> wrote:
This is probably more related to Mike's newish code which tries to parse the port name, rather than it actually truncating the port at any particular length.
adam.
Sent from MailbirdOn 04/03/2016 14:54:47, Mailing Lists <lists@coop3r.com> wrote:
Hi Adam,
port_label fields look like this (which is presumably what you expected to see)
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
On 4 March 2016 at 14:10, Adam Armstrong <adama@memetic.org> wrote:
Can you see what port_label is for these ports?
You can see it using the 'data dump' icon on the right hand side of the navbar on the port page.
adam.
Sent from Mailbird_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observiumOn 03/03/2016 14:56:27, Mailing Lists <lists@coop3r.com> wrote:
Am I imagining things, or did Observium previously correctly display Ethernet service instance interfaces in the GUI? I've noticed recently that all the interfaces names for service instance interfaces seem to be truncated in a few of the views
Picture speaks a thousand words, where these show GigabitEthernet0/16. now, I am sure they previously would have been listed as GigabitEthernet0/16.ServiceInstance.1234 etc;
Discovery debug example from the device shows the interfaces captured as the full name:
([ifDescr] => GigabitEthernet0/1.ServiceInstance.206[ifAlias] => Description[ifName] => Gi0/1.SI.206[ifType] => l2vlan[ifOperStatus] => up)
If you search in the ports for for the full interface name it knows it as the right thing;
Looks like the GUI just truncates the names? Obviously this makes it harder than it should be to identify the correct interface in the list. Any chance we can have this show the whole thing? :)
Thanks,Tim C
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- Mike Stupalov http://observium.org_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- Mike Stupalov http://observium.org