smurdza

Ok, Thank you @g-bougard . I think everything is ok in GLPI, switch appear in GLPI and information about firmware and switch ports. I think device model is missing. @g-bougard...

@g-bougard I try did that, but in files CISCO-ENTITY-VENDORTYPE-OID-MIB.my, miss ID 1662 and agent can't join records :  Second firmware qustion, one and second switch have the same information...

Hi @g-bougard , I did snmpwalk and mib for firmware is the same: SNMPv2-SMI::mib-2.47.1.1.1.1.9.22 = STRING: "5.0(3)N2(4.01c)" SNMPv2-SMI::mib-2.47.1.1.1.1.9.1000022 = STRING: "5.0(3)N2(4.01c)" SNMPv2-SMI::mib-2.47.1.1.1.1.10.22 = STRING: "5.0(3)N2(4.01c)" SNMPv2-SMI::mib-2.47.1.1.1.1.10.1000022 = STRING: "5.0(3)N2(4.01c)" SNMPv2-SMI::mib-2.47.1.1.1.1.9.22...

@g-bougard Why GLPI create two device for the same switch ? Maybe it is problem ? 

I can send you to privat e-mail....

Sombody, can help me ? How to resolve this two problems ? Where is the problem ? 1) switching SNMP context to vlan 2) invalid interface ID xxxxxxx while setting...

Hi, i have the same problem, VM or ESXi phisical maschine don't automatic connect witch port on the switch. Did you resolve this problem ? Agent version : INVENTORY :...

> Seems because we not inventory the virtual switch on ESX, and not sure it's possible. @ddurieux I think it is possible. API ESX have that information: https://code.vmware.com/apis/358/vsphere/doc/vim.host.VirtualSwitch.html#field_detail

@iamtornado Have you any idea, how to resolved this problem ?

Hi, Its i briliant idea. I think very important is add vswitch inventory, because now connections between phisical and virtuals connection aren't avilable. API ESX have that information: https://code.vmware.com/apis/358/vsphere/doc/vim.host.VirtualSwitch.html#field_detail