If device not support SNMP version 2c, replace -v2c with -v1.
And support for this device already exist.
Mike Stupalov
added a comment - For add support any unsupported device, you should make and create snmpdump from that device.
Not possible add support by MIB file!
You seen Bot comment in other issues how to create it:
Please make and attach additional information about the device:
full snmp dump from device:
snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk
If device not support SNMP version 2c, replace -v2c with -v1.
And support for this device already exist.
It would be very fine especially with the background, if you pay the Prof Edition, that also the devices that are needed are integrated. And you do not have to wait more than 2 years.
Mario Pascal Necker
added a comment - It would be very fine especially with the background, if you pay the Prof Edition, that also the devices that are needed are integrated. And you do not have to wait more than 2 years.
For add support any unsupported device, you should make and create snmpdump from that device.
Not possible add support by MIB file!
You seen Bot comment in other issues how to create it:
Please make and attach additional information about the device:
snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk
If device not support SNMP version 2c, replace -v2c with -v1.
And support for this device already exist.