In order for your servers to respond to an SNMP request, there must be some sort of SNMP client to do the responding. The client uses MIB files to map data to OIDs. Now, it is possible the the OS has a built in client, I have not worked on the servers you mention and cannot say for sure.
One thing you can do is poll your servers to determine what data points are being exposed via SNMP. The following steps describe how to list all of these data points. 1. Most servers have SNMP Query configuration. Configure one of your servers with a community name and set the SNMP Query IP address to a Linux workstation. Give the IP address READ access. 2. Download all of the MIB files for your servers and software into a directory. 3. From the Linux workstation, CD to the directory with your MIB files and execute the snmpwalk command (part of the Net-SNMP package). I usually use the following syntax: Code: snmpwalk -v (SNMP version: 1 | 2c | 3) -c (community name) -m all -M +./ (IP address of server) Example: Code: snmpwalk -v1 -c public -m all -M +./ 192.168.1.1 This will list the system OIDs. If you want to view the custom enterprise OIDs, try: Code: snmpwalk -v (1 | 2c | 3) -c (community name) -m all -M +./ (IP address) SNMPv2-SMI::enterprises You may get a lot of data back, so it may be helpful to redirect the output to a file and use an editor to review it. The above commands will use the MIBs to interpret the OIDs into textual identifiers, making them easier to read. If you see OIDs that are mostly numbers, you likely don't have the MIB file for that OID. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=36695#36695 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
