I add another information:
if I try a
on the device it responds with all mib presents.Code:snmpwalk -Os -c public -v2c 123.123.123.123
Thank you again
Bronze Partner
Re: OPC Client configuration
I add another information:
if I try a
on the device it responds with all mib presents.Code:snmpwalk -Os -c public -v2c 123.123.123.123
Thank you again
Employee
Re: OPC Client configuration
Hi Luca,
You could check with wireshark to see what the difference is.
With a "walk" usually a SNMP client sends "GET" and "GETNEXT", until it received the last oid from the MIB on the SNMP agent, this is also what our driver does, however you can also limit the amount of "GET" it will send, in the browse of the SNMP agent.
Best regards,
Mark
Bronze Partner
Re: OPC Client configuration
Hi Mark,
is it possible that the interrogation made by the driver is in V1? it seem that (watching on the device). That device support only V2C and doesn't answer on a V1 snmpwalk.
Could this be the problem? Is there any way to force Zenon driver to use V2C of SNMP?
Posting Rules
Reply With Quote