Some intravenous drip of SNMP

One: How do I create my own MIB?

First of all: to define their own MIB, first familiar with the ASN.1 syntax, which has a foreigner's MIB book is very good, MIB's RFC document is it defined as if.

Second: See more other MIB, in fact, the definition is relatively simple, is type, scalar, table three main things.

II: I implement an agent process, if you capture SNMP port information that the other agent process on the same machine can not capture management information? My agent process serves only a particular OID, and if it does not belong to my OID, how can I give it to other agent processes that exist in the system?

The problem is to extend the agent, which is the extension agents, the SNMP system services under Windows, you can do it directly with extensions, so you can add your new OID to the system's SNMP service, which is relatively simple, as described in MSDN, It seems to be snmpextensionxxx, I don't remember very well!

Three: In the Tube equipment does not exist a MIB? My understanding, is not only in the management process of collecting the information of the various devices to form a MIB, and in the tube device does not have a real MIB?

Your understanding is wrong, the MIB is management information base is a managed information database, which is stored on the agent end, the concept of the agent in fact includes two parts, one is the narrow agent, (is to accept network SNMP protocol, return information), the other is the organization of MIB information.

Four: I want to boast platform management, agent process and the manager of the process of how to achieve convenience?

Convenient way:

There are two open SNMP development libraries, which are now the most used! One net-snmp, one is snmp++, can boast platform, but NET-SNMP is based on C language, and snmp++ is based on C + +, and generally used for Windows, on the contrary net-snmp more for linux!

I hope to help you,

Books! There is a simple SNMP network Management protocol and the principle and application of a good! The rest! I think it's enough to read the RFC document, RFC1213 (MIB-II) and so on!