Ethernet Service Instance Interface Names Truncated
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;
[image: Inline images 1]
[image: Inline images 4]
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;
[image: Inline images 2]
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
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 [http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm...] On 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;
[Inline images 1]
[Inline images 4]
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;
[Inline images 2]
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
I would like to join discussion here as I have also noticed that vlan information is gone on port page. Was there any changes related to that Adam? 4 mar 2016 3:10 PM "Adam Armstrong" adama@memetic.org napisał(a):
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 http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird
On 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;
[image: Inline images 1]
[image: Inline images 4]
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;
[image: Inline images 2]
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
I don't really know what you're talking about, except that it's definitely not related to port labels.
DO NOT HIJACK THREADS.
adam.
Sent from Mailbird [http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm...] On 04/03/2016 14:47:02, Łukasz Sztukowski lukaszs@gmail.com wrote: I would like to join discussion here as I have also noticed that vlan information is gone on port page. Was there any changes related to that Adam? 4 mar 2016 3:10 PM "Adam Armstrong" <adama@memetic.org [mailto:adama@memetic.org]> napisał(a):
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 [http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm...] On 03/03/2016 14:56:27, Mailing Lists <lists@coop3r.com [mailto: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;
[Inline images 1]
[Inline images 4]
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;
[Inline images 2]
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 [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi Adam,
port_label fields look like this (which is presumably what you expected to see)
[image: Inline images 1]
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 http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird
On 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;
[image: Inline images 1]
[image: Inline images 4]
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;
[image: Inline images 2]
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
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 Mailbird [http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm...] On 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)
[Inline images 1]
On 4 March 2016 at 14:10, Adam Armstrong <adama@memetic.org [mailto: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 [http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm...] On 03/03/2016 14:56:27, Mailing Lists <lists@coop3r.com [mailto: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;
[Inline images 1]
[Inline images 4]
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;
[Inline images 2]
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 [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
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 Mailbird http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird
On 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)
[image: Inline images 1]
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 http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird
On 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;
[image: Inline images 1]
[image: Inline images 4]
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;
[image: Inline images 2]
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
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 mailto: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 Mailbird <http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird>On 04/03/2016 14:54:47, Mailing Lists <lists@coop3r.com <mailto:lists@coop3r.com>> wrote: Hi Adam, port_label fields look like this (which is presumably what you expected to see) Inline images 1 On 4 March 2016 at 14:10, Adam Armstrong <adama@memetic.org <mailto: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 <http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird>On 03/03/2016 14:56:27, Mailing Lists <lists@coop3r.com <mailto: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; Inline images 1 Inline images 4 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; Inline images 2 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 <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium_______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium_______________________________________________ observium mailing list observium@observium.org <mailto: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
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 mailto: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 Mailbird <http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird>On 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) Inline images 1 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 <http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird>On 03/03/2016 14:56:27, Mailing Lists <lists@coop3r.com <mailto: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; Inline images 1 Inline images 4 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; Inline images 2 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 <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium_______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium_______________________________________________ observium mailing list observium@observium.org <mailto: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
That's great! Looks good, thanks Mike!
On 15 Mar 2016, at 10:08, Mike Stupalov mike@observium.org wrote:
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 Mailbird
On 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)
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 > On 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
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
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!
On 15 Mar 2016, at 10:08, Mike Stupalov mike@observium.org wrote:
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 Mailbird http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird
On 04/03/2016 14:54:47, Mailing Lists < lists@coop3r.com lists@coop3r.com> wrote: Hi Adam,
port_label fields look like this (which is presumably what you expected to see)
[image: Inline images 1]
On 4 March 2016 at 14:10, Adam Armstrong < adama@memetic.org 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 http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird
On 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;
[image: Inline images 1]
[image: Inline images 4]
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;
[image: Inline images 2]
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 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 listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- Mike Stupalovhttp://observium.org
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
On 15.03.16 14:22, Mailing Lists wrote:
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.
Not related. Common issue when incomplete or erroneous snmp output (by walk in vlans module).
./discovery.php -d -m vlans -h <device>
On 15 March 2016 at 11:09, Tim Cooper <lists@coop3r.com mailto:lists@coop3r.com> wrote:
That's great! Looks good, thanks Mike! On 15 Mar 2016, at 10:08, Mike Stupalov <mike@observium.org <mailto:mike@observium.org>> wrote: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 <mailto: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 Mailbird <http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird>On 04/03/2016 14:54:47, Mailing Lists <lists@coop3r.com <mailto:lists@coop3r.com>> wrote: Hi Adam, port_label fields look like this (which is presumably what you expected to see) Inline images 1 On 4 March 2016 at 14:10, Adam Armstrong <adama@memetic.org <mailto: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 <http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird>On 03/03/2016 14:56:27, Mailing Lists <lists@coop3r.com <mailto: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; Inline images 1 Inline images 4 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; Inline images 2 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 <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium_______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium_______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium_______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium-- Mike Stupalov http://observium.org _______________________________________________ observium mailing list observium@observium.org <mailto: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
participants (6)
-
Adam Armstrong -
Mailing Lists -
Mike Stupalov -
Tim Cooper
-
Tom Laermans -
Łukasz Sztukowski