One other thing regarding that "End of Mib" message. Cisco devices can also show this type of behavior which results from a common configuration mistake/interpretation
Say you configure your RO community on a cisco to be 1234 and not public. BUT you set your outgoing snmp traps to be community public. That cisco device will internally "enable" walking of the public community but with no permission to view anything. So it will reply to walking on the public community with no mibs and thus the End of Mib message. Changing your outgoing traps to use the same community as your RO community can remedy this problem. We had this issue which was preventing Zenoss from really figuring out the correct community since technically it got a reply from public even though our internal string was something else. Hopefully this helps someone. Cheers, Zach Davis -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=15832#15832 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
