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

Aggregated network interfaces (bond) aren't resolved #667

Open
GuidoWilden opened this issue May 10, 2024 · 7 comments
Open

Aggregated network interfaces (bond) aren't resolved #667

GuidoWilden opened this issue May 10, 2024 · 7 comments
Labels
bug Something isn't working

Comments

@GuidoWilden
Copy link

Bug reporting acknowledgment

Yes, I read it

Professional support

None

Describe the bug

We have several machines (both Linux and Windows) that have LACP aggregated 10 Gbit/s network ports.
While they are recognised as such, no further information is collected, like which switch ports do they plug into etc..

Screenshot 2024-05-10 at 12 34 51

Maybe not so much a bug but a feature request rather.

To reproduce

  1. Create bonded/teamed port in either Windows or Linux
  2. Run inventory

Expected behavior

I wish it was possible to interrogate the interfaces for switch port connections etc.

Operating system

Linux

GLPI Agent version

Nightly build (git version in additional context below)

GLPI version

Other (See additional context below)

GLPIInventory plugin or other plugin version

GLPI Inventory v1.3.5

Additional context

GLPI version 10.0.15, GLPI agent nightly build v1.8-git3ddbbd8e

@GuidoWilden GuidoWilden added the bug Something isn't working label May 10, 2024
@g-bougard
Copy link
Member

Hi @GuidoWilden

can share the XML inventory and provide a snmpwalk output ?

The first question to answer will be to say if all required datas are provided or not by the agent.

@GuidoWilden
Copy link
Author

Hi @g-bougard
Any specific syntax for the snmpwalk? The usual

snmpwalk -v 1 -c public -t 15 -Cc -On -Ox <IP_ADDRESS> .1

Does not gather a lot.

@g-bougard
Copy link
Member

Don't you have any other access via SNMP v2c or SNMP v3 ?

@GuidoWilden
Copy link
Author

GuidoWilden commented May 10, 2024

When using v2c I get the following. (So really not much from a Linux host), using

snmpwalk -v 2c -c public -t 15 -Cc -On -Ox 10.120.10.113 .1

snmpwalk.txt.zip

@g-bougard
Copy link
Member

To me, we can't extract ports from this snmpwalk. You should have some security on this device which limit reported oid via public community.

@GuidoWilden
Copy link
Author

GuidoWilden commented May 13, 2024

I managed to get the two for a Linux host. I am still battling Windows but will send them when I manage.
ldnaz-vfx3.xml.zip

snmpwalk_vfx3.txt.zip

@GuidoWilden
Copy link
Author

Here the two files for a Windows host, however, the snmpwalk would not run without an error.
ldnaz-resolve2.xml.zip

snmpwalk_resolve2.txt.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants