Thank you for your response. It seems to be a zenmodeler bug. I don't know what have changed, may be the number of routes have increased and now zenoss can not collect it in 180 second, which is default. After that it says timeout and starts again collecting routes or may be continues to run different modeler plugins. Somehow after that message cisco goes into 100% cpu usage by snmp process. I fixed it by increasing timeout for zenmodeler in zproperties. It solved my problem, but still I don't understand, why running my router modeling from command line is much faster then by schedule.
I rebooted my machine - and after that I started having problems. So, it is obviously not because of zenmodeler process hanging. _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
