You are right, I had one space only on the line with the MIB name. Once I added one more space indent on that line, it generated properly. Thank you very much for your help with this. Very much appreciated.
On Sunday, July 19, 2020 at 5:32:55 PM UTC+8 [email protected] wrote: > It's hard to tell from your email, but it's likely an indenting problem > with your generator yaml. > > This is what I get when I generate for that walk: > > https://github.com/SuperQ/tools/tree/master/snmp_exporter/avtech > > On Sun, Jul 19, 2020 at 8:32 AM Linkoid01 <[email protected]> wrote: > >> Thank you very much for your help thus far. However I am still not able >> to get it to generate. >> I removed the leading dot. My generator.yml file looks like this now: > > modules: >> # AVTech RoomAlert 32E >> ROOMALERT32E-MIB: >> walk: >> > - 1.3.6.1.4.1.20916.1.8.1.1.1.1 >> version: 1 >> auth: >> # Community string is used with SNMP v1 and v2. Defaults to >> "public". >> community: public >> # lookups: >> # - source_indexes: >> # lookup: >> # - source_indexes: >> # lookup: >> # overrides: >> >> >> I am getting the following message: >> ./generator generate >> level=info ts=2020-07-19T06:27:33.832Z caller=net_snmp.go:142 >> msg="Loading MIBs" >> from=$HOME/.snmp/mibs:/usr/share/snmp/mibs:/usr/share/snmp/mibs/iana:/usr/share/snmp/mibs/ietf:/usr/share/mibs/site:/usr/share/snmp/mibs:/usr/share/mibs/iana:/usr/share/mibs/ietf:/usr/share/mibs/netsnmp >> level=warn ts=2020-07-19T06:27:34.004Z caller=main.go:120 msg="NetSNMP >> reported parse error(s)" errors=1 >> level=error ts=2020-07-19T06:27:34.185Z caller=main.go:130 msg="Error >> generating config netsnmp" err="error parsing yml config: yaml: line 5: did >> not find expected key" >> >> I removed lookups and there are no indexes mentioned in this MIB for this >> device. >> >> I can perform snmpwalk on this oid just fine: >> >> snmpwalk -v 1 -c public 172.18.232.17 .1.3.6.1.4.1.20916.1.8.1.1.1.1 >> ROOMALERT32E-MIB::internal-tempf.0 = INTEGER: 7826 >> >> >> On Sunday, July 19, 2020 at 12:20:41 AM UTC+8 [email protected] wrote: >> >>> The leading dot is the problem. >>> >>> On Sat, Jul 18, 2020, 14:57 Linkoid01 <[email protected]> wrote: >>> >>>> Thanks for that, completely forgot about that. >>>> Here's what I have in the generator.yml file >>>> >>>> modules: >>>> # AVTech RoomAlert 32E >>>> ROOMALERT32E-MIB: >>>> walk: >>>> # internal >>>> - .1.3.6.1.4.1.20916.1.8.1.1 >>>> version: 1 >>>> auth: >>>> comunity: public >>>> lookups: >>>> - source_indexes: >>>> lookup: >>>> - source_indexes: >>>> lookup: >>>> overrides: >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Prometheus Users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/prometheus-users/951c906d-ed4a-4ef7-935f-9163a8c6ada9n%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/prometheus-users/951c906d-ed4a-4ef7-935f-9163a8c6ada9n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Prometheus Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/prometheus-users/a9c65275-259d-4d6b-8a9d-48a23410947an%40googlegroups.com >> >> <https://groups.google.com/d/msgid/prometheus-users/a9c65275-259d-4d6b-8a9d-48a23410947an%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/69929527-28be-42af-8641-67afa3bd8611n%40googlegroups.com.
