WANTED: real-world SNMP walks

[etingof]

Please-please-please!

Consider donating some snapshots of SNMP data (e.g. snmpwalk) as reported by any real-world hardware to the SNMP simulator project. Having the real-world SNMP probes would benefit many SNMP implementers and testers.

Technically, it can be a PR against snmpsim-data package adding your .snmpwalk or .snmprec files to the data directory. Or a URL to download. Or any other way.

Just keep in mind that your SNMP dumps may contain sensitive information. Therefore it's best to snmpwalk non-production devices.

With your permission, we would then publish these snmpwalk's online.

Thank you!

[v-zhuravlev]

https://github.com/v-zhuravlev/zbx_snmpsim/tree/master/data are these any good to you?

[etingof]

Awesome! Thank you! Will pull those in.

[v-zhuravlev]

I actually have more but I need to strip sensitive stuff first before I can publish them. Is there anything specific you need?

[etingof]

I actually have more but I need to strip sensitive stuff first before I can publish them. Is there anything specific you need?

Would be great!

I think the more varieties of the recorded hardware we have - the better. I am thinking of different network equipment, storage devices, appliances of all sorts...

[Benik3]

Hi, I have some devices walked to snmprec, mostly cameras :)
https://send.firefox.com/download/64d895bf7db95930/#3bzQsYmceWreG2QsaHRluA

[etingof]

Thank you, @Benik3!

[aquette]

hi @etingof
I'm willing to provide a number of power devices (UPS, ePDU, ATS) dumps, for which I have access to live agents. I may also push some network switches, if useful.
However, I also have some SNMP walks of agents I can't access (which I call "offline).
Like I did in NUT (https://github.com/networkupstools/nut/blob/master/scripts/subdriver/gen-snmp-subdriver.sh), I may be checking to complete snmprec for working "offline".
I also have a doubt on one thing, and hence a question: the dumps I'll be providing will also be useful for some other purposes (both opensource and professional). But for this, I'd need at least the sysOID to be part of the recording (I'm using sysOID for "fingerprinting" devices and using the right SNMP mapping).
So the question is: should I add and include the sysOIDs in the provided dumps?
Thanks and cheers

[etingof]

I'm willing to provide a number of power devices (UPS, ePDU, ATS) dumps, for which I have access to live agents. I may also push some network switches, if useful.

I think the more walks we publish for general public - the better! Thank you!

So the question is: should I add and include the sysOIDs in the provided dumps?

Having sysOID in the walk would be beneficial indeed! But do you have to do anything to make that happening? If you walk the whole OID tree of a device, that should get us sysOID automatically, no?

[aquette]

I'm willing to provide a number of power devices (UPS, ePDU, ATS) dumps, for which I have access to live agents. I may also push some network switches, if useful.

I think the more walks we publish for general public - the better! Thank you!

sure thing ;)

So the question is: should I add and include the sysOIDs in the provided dumps?

Having sysOID in the walk would be beneficial indeed! But do you have to do anything to make that happening? If you walk the whole OID tree of a device, that should get us sysOID automatically, no?

indeed too, though it may overload the provided data for not much added value in the end (having the whole MIBII with stats et all for example). Also, I'll have to anonymize some data (IP@, serial numbers, ...) to solve some privacy, though it raise the question of relevant data Vs privacy.

Note that I've in the meantime also found the support for .snmpwalk, which somehow answers my need (though a conversion tools, from these walks to .snmprec would be better)

So let's start with a first dump, partial one of an Eaton UPS (9PX): #77
Comments and feedback welcome

[etingof]

indeed too, though it may overload the provided data for not much added value in the end (having the whole MIBII with stats et all for example).

Arguably, even stats objects would make some sense from the simulation perspective. If the user points an NMS to the simulated agent, that NMS might be able to present the agent more realistically to the user.

Another possible step towards better simulation would be to replace static values for stats with references to the numeric variation module to make the counters actually ticking...

Also, I'll have to anonymize some data (IP@, serial numbers, ...) to solve some privacy, though it raise the question of relevant data Vs privacy.

I think obfuscated serial numbers and other inventory information should not affect the relevancy of the simulation.

Changing IP addresses (as an example) may break things here and there because table indices may include IPs, different tables may refer to the same IP which should be changed consistently everywhere etc.. This is hard to obfuscate by hand, but we do not have a suitable tool for that so far...

Still, I believe having at least partially realistic data is the grand awesomeness compared to having just scholastic MIB dumps! ;-)

[etingof]

I've pushed all real SNMP dumps into the snmpsim-data package. I think it makes sense for snmpsim to automatically discover and use .snmprec files from it, but that's a TODO.

Meanwhile, everyone is very welcome to PR against snmpsim-data!

Thanks!

[Benik3]

Kert KPREMIUM1000R UPS :)

UPS_Kert.zip

[etingof]

Thank you! I am working on putting all recordings together into snmpsim-data package.

[HBSpy]

snmp-H
My data from my work(IT NMS)
May it will help you

[etingof]

@HBSpy Thank you! I have one question - these files in data.src, are they produced from the snmpwalk files enclosed?

[HBSpy]

@HBSpy Thank you! I have one question - these files in data.src, are they produced from the snmpwalk files enclosed?

files in snmpwalk are generated from my customers' real devices, with snmpwalk -ObentU
files in data.src mostly are generated from snmpwalk with datafile.py

[etingof]

Aha, so they contain different information then! Awesome!

[timlegge]

I should be able to contribute the following in a few days:

Temperature sensor
Three PDUs
One Automatic Transfer switch

[etingof]

I should be able to contribute the following in a few days:

Temperature sensor
Three PDUs
One Automatic Transfer switch

That would be awesome! Thank you!

[timlegge]

https://github.com/timlegge/docker-snmpsim-openDCIM in the data directory (the Cisco ones are yours)

The files have been modified for variation as documented in the README.md

[etingof]

Awesome, thank you!

Should I pull the rest of the .snmprec files as well?

[timlegge]

Hi The Cisco snmprecs are a copy of the onee already in your repo I believe. Tim

…

On Fri, Nov 8, 2019 at 1:40 AM Ilya Etingof ***@***.***> wrote: Awesome, thank you! Should I pull the rest of the .snmprec files as well? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[etingof]

Ah, in that sense! I see.

BTW, there is a whole lot of cisco recordings here, however I figured that some of these files are too large to be served effectively. I am trying to rework the hashing mechanism.