bluesky786 wrote: > Thanks!!!!!! i got it... > > > i don't know more about mibs more than they called Management Information > Base "keep statistical data of device " like router and switches > > i am confuse what zenoss will do with mibs ? > every rounter& switch can have its own unique mib ? > zenoss already providing all ports usage of any Device like switch how mibs > are important and zenoss can provide what type of information working with > any mibs and how we can load it ?????
MIBs are just text files that map the numeric OID to a textual name. They also provide a description and type (INTEGER, STRING, etc.) to the data that is stored there, and tell you whether it is a read-write or read-only value. In Zenoss MIBs are used by the Event Console. If you are sending SNMP Traps to Zenoss the Event Console can display more useful information than "snmp trap for 1.3.6.1.4.1.9789.1500.2.5" In this case it would translate that OID to "evt.spamFilterDetectsVirus" Load MIBs into Zenoss using the zenmib command from the command line. Your MIB files should be placed in the $ZENHOME/share/mibs/site directory and loaded as follows: Code: zenmib run mymibfile The Zenoss Administration guide (http://www.zenoss.com/community/docs) goes into more detail about this. For routers and switches you are correct, most of the information like interface counters, cpu, and memory are already included in the default IF-MIB and SNMPv2-MIB files. However, there is still a lot of useful information out there to be had. If you have a 2811 router you could query OID .1.3.6.1.4.1.9.9.13.1.4.1.3.1 and receive a value of "1". Not very useful... But if you had the the CISCO-ENVMON-MIB file you could instead query CISCO-ENVMON-MIB::ciscoEnvMonFanState.1 and receive a value of "normal". Code: # snmpget -v2c -c mystring 192.168.1.10 1.3.6.1.4.1.9.9.13.1.4.1.3.1 SNMPv2-SMI::enterprises.9.9.13.1.4.1.3.1 = INTEGER: 1 # snmpget -v2c -c mystring 192.168.1.10 CISCO-ENVMON-MIB::ciscoEnvMonFanState.1 CISCO-ENVMON-MIB::ciscoEnvMonFanState.1 = INTEGER: normal(1) Please note that the above example only applies to command-line queries. Last I checked Zenoss could not use the named format to query values. I am just trying to show you a general Cisco MIB example. One of my gripes about Zenoss is that it doesn't use the standard system location for MIB files, but has it's own, and on top of that you have to manually load them into the database. Most Linux systems place MIBs in a directory like /usr/share/snmp/mibs. As soon as you place them there they are available for use by the Net-SNMP libraries. Zenoss requires that the be in the $ZENHOME directory and loaded as previously stated. Once they are in Zenoss you can view and organize them under the Management/Mibs section. Two last notes about Cisco MIBs in particular. When you download them from Cisco they have a ".my" extention. Linux prefers them with a ".txt" extenstion, but don't despair. Just rename them. Several critical Cisco MIB files (like CISCO-TC) have an "Unsigned64" value that must manually be edited to "Unsigned32" before they will correctly load into Zenoss. I don't know why, it is just that way. Finally, if you do have any different questions perhaps you should make a new post. Just so the moderators don't get fussy! [Wink] -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=20040#20040 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
