Otherwise you have a hell of a lot of work ahead of you before you even start to think about sending data via SNMP. You are likely better off using something like a Raspberry Pi or similar running Linux, because all of the drivers, TCP/IP stack, and SNMP application, and bits in-between are taken care of already, and you only need to work out how to send the data you are interested in. Sorry to sound all negative, but there will be no copy/paste code that magically makes this work. Unless you just happen to get lucky and find someone who has already done what you're looking for (which I think is highly unlikely), simply put, you're not likely to achieve this the way you are thinking about it. The community names are essentially passwords theres no real difference between a community string and the password you use to access your. An agent is configured with three community names: read-only, read-write, and trap. fchk has given a good breakdown of the stack of protocols and services that are involved in accomplishing what you are asking for. SNMPv1 and SNMPv2 use the notion of communities to establish trust between managers and agents. The OSI model provides distinct operational separation between various software and hardware layers to ensure that it is not a monolithic mess requiring everyone to reimplement the entire thing themselves on a per application basis. You're talking about too many things in one go, and that's not how these things work.
0 Comments
Leave a Reply. |