Beta 1 of FusionInventory for GLPI (ex Tracker)

MHI · 2010-04-08 12:46:23

ddurieux wrote:

You prefer models with names?
I have made numbers because one model can be used for different devices / manufacturer / models so it's logic they haven't real name. Agent assign model with description of device with XML file (idem in glpi plugin when you click on re-assign model).
In 2.1.3 Tracker, we have generic models, in 2.2.0 Fusion, each model have its device (so some models are shared with many devices).
You understand ?

That's pretty much understood now. I am just confused what would be the best way to enter our own models. Should I use any number I for the xml file I come up with. Do you have any certain logic behind those numbers and also how can this be matched against each other when you for example release a new version where more models are included, because that could collide with my existing self made definitions, like using 'Printers0110" and you use it in new release for other printer than I do. Just would like to have a chance to keep that in sync, so that new releases are not jeopardising my exisiting additions. Maybe it would be good to come up with a fixed range for "own definition", so everybody knows, you will not use it in future releases.
Hope this is somehow understandable as well
Small example: I am sending you a SNMP model file which I did to share it in a future release with the public. I used for ecample "Network0111" for the ModelSNMP, but probably in the meantime you already used that number and change mine to "Network0200". This would mean to me that when installing the new version and updating the models on my side, my "Network0111" assignment would be overwritten with yours and to fix this takes a while.
Maybe you have a good idea or suggestion on how to handle this.

The other thing, do you have any idea why it's not pipcking up my newly created models that I added to the discovery.xml ?
sysDescr does match, but it's not gathering the information, like the serial.

ddurieux · 2010-04-08 13:00:23

It's depend of your devices, for some of them I use non sysdescr but an other oid (for HP printer for example).

I will think for model name.

If you do not want to create your own model, send me snmpwalk log to me, I create model in about 5 minutes, with my semi-automatic generation tool

MHI · 2010-04-08 13:06:03

ddurieux wrote:

If you do not want to create your own model, send me snmpwalk log to me, I create model in about 5 minutes, with my semi-automatic generation tool

Well, I somehow was smelling it that you have something like that

The only problem to send you an snmpwalk is that the company is kinda sensitive to send out IP/SNMP information to people they dont know. But hey, maybe that can be changed, huh

ddurieux · 2010-04-08 13:12:31

I have some informations of other company, and don't send to bad people

if it's just ip, change them.

It's difficult to give you tool, humm, I must explain to you. Can you join on IRC to explain this on freenode servers and join channels : #glpi OR #fusioninventory

Thanks

MHI · 2010-04-08 13:24:33

ddurieux wrote:

I Can you join on IRC to explain this on freenode servers and join channels : #glpi OR #fusioninventory
Thanks

Will try to join, but as far as I know IRC ports are blocked from within the company, otherwise I will try to join later on today from home.

ddurieux · 2010-04-08 13:35:28

or try with web : http://webchat.freenode.net

MHI · 2010-04-08 13:37:21

also blocked

Last edited by MHI (2010-04-08 13:37:33)

MHI · 2010-04-09 22:04:02

dd, I may have an idea regarding the file naming, so you do not have to change those. In my opibion it would be enough to add a column to the SNMP Model view (if possible) and named "device info" for example and to displaythere the content of the comments field, which has the exact device information. Maybe field should have a max characters limit, so the view does not get to funky when dealing with very long comments, like the Cisco ones. Just my two cents.

MHI

ddurieux · 2010-04-10 11:37:49

Yes, I have think to this too, but one model can be used by many different devices, I think to name FI-Networking-0001 for example but not yet very explicit.

I will try to see your solution with the model match many devices to see how to do this.

MHI · 2010-04-12 10:56:50

Maybe it could work also that way that you add the column which is just displaying the associated "Networking" and "Printer", like Networking0001 and then hyperlink that to a new view where it shows all model comments of the equipment that is running under that Networking0001 model.

ddurieux · 2010-04-12 12:39:42

yes, I think to export view we have in plugin for models to wiki, and it's a good idea

Can you resend me the 3 sql tables in middle of this week, I have models to add too

MHI · 2010-04-12 12:49:06

I won't have that much time to create models, because I will be on business trip. I need to get the snmpwalks from all the locations which will definately take a while, becuase I also need to write a HowTo , but as soon as I have a reasonalbe amount of data imported, you are the first to get those tables. Let's call it a resource problem, why it will take a while

ddurieux · 2010-04-12 13:52:06

I would like to release the modules SNMPQUERY and NETDISCOVERY of the fusioninventory agent friday or saturday and there is the file discovery.xml inside. So, If you have time to create these models, it could be great

MHI · 2010-04-12 13:54:15

Honestly I will try my very best to get at least some of the models done.

ddurieux · 2010-04-12 14:20:31

yes I know
Just try to release quickly now

MHI · 2010-04-14 13:06:35

dd, default mapping for Cisco switch firmware of .1.3.6.1.2.1.47.1.1.1.1.9.1 is firmware1 even if those switches just have one firmware. Shouldn't it be just firmware, where firmware1 and firmware2 are for teh switches with more than one entry for firmware ?
Just in process of creating some models and don't want to make wrong mapping. As said system suggests to map to firmware1. If that's okay, let me know, if not, should I change this to "firmware" ?

ddurieux · 2010-04-14 13:31:14

For cisco use only firmware (firmware 1 and 2 are used for procurve HP (they have 2 firemware version)

MHI · 2010-04-14 13:42:19

Cisco 4507 and larger ones also have up to 3 Firmware versions

SNMPv2-SMI::mib-2.47.1.1.1.1.9.1000 = STRING: "12.2(20r)EW1"
SNMPv2-SMI::mib-2.47.1.1.1.1.10.1000 = STRING: "12.2(20)EWA2,"
SNMPv2-SMI::mib-2.47.1.1.1.1.10.2000 = STRING: "12.2(20)EWA3"

All from same switch.

ddurieux · 2010-04-14 13:50:15

Humm it's because you have many switchs in the chassis. So for the moment, get only the first.

Perhaps in futures version of glpi, we can manage the chassis and each switch inside

Forum GLPI-Project

Announcement

#76 2010-04-08 12:46:23

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#77 2010-04-08 13:00:23

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#78 2010-04-08 13:06:03

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#79 2010-04-08 13:12:31

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#80 2010-04-08 13:24:33

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#81 2010-04-08 13:35:28

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#82 2010-04-08 13:37:21

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#83 2010-04-09 22:04:02

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#84 2010-04-10 11:37:49

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#85 2010-04-12 10:56:50

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#86 2010-04-12 12:39:42

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#87 2010-04-12 12:49:06

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#88 2010-04-12 13:52:06

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#89 2010-04-12 13:54:15

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#90 2010-04-12 14:20:31

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#91 2010-04-14 13:06:35

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#92 2010-04-14 13:31:14

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#93 2010-04-14 13:42:19

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

#94 2010-04-14 13:50:15

Re: Beta 1 of FusionInventory for GLPI (ex Tracker)

Board footer