There are ways (and posts) to limit what you pull for route information. You can also manually set up routes, so perhaps you could use some API for that + your info?
I think it can be done, but I'm not entirely sure how. I'd search the forums a bit on this. -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University darionalanya wrote, On 5/17/2009 9:46 AM: > We have a fairly large network (~2k devices), with the network core > containing a full internet table. The modeler seems to be having problems > because it can not import the full routing table. Our internal routing is > stored in ISIS / static / and connected routes whereas the Internet table, > which we don't need for modeling, is in BGP. Is there a way to have the > modeler only import certain types of routes? > > Alternatively, I can build a routing table list containing only the routes I > want via a shell script. Once I have this, is there a way to import the > information into the device so that Zenoss doesn't have to pull it via SNMP? > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://forums.zenoss.com/viewtopic.php?p=34917#34917 > > -------------------- m2f -------------------- > > > > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
