![]() Routers and switches are polled to log IP and MAC addresses and map them to switch ports. Single Database would most likely work, but I'd like each data center to have it's own. Free download page for Project Netdisco's netdisco-mibs-2.4.tar.gz.Netdisco is an SNMP-based L2/元 network management tool designed for moderate to large networks. Without CDP Autodiscovery I'd be adding things for days.Īnyone ever built a distributed Cacti system? I'm thinking of putting one in each datacenter but I'd like to tie them together in such a way you can look at the info from each in each datacenter. I just found out I'm going to be adding our other US data centers to Cacti & NetDisco so I'll be at well over 10,000 switches/routers/etc when it's all said and done. If you add the CDP Autodiscovery I'd be interested. Time permitted, I may add fancy graphing and CDP Autodiscovery, but that is not a priority today. However, you could quite easily export you data from your existing database and import into Cacti's MacTrack. So, there is no cross polination, which some may see as a detractor. Thanks, it turns out that the critical package was: yum install perl-ExtUtils-MakeMaker. I did this more to maintain cacti's original database than anything else. The devices in MacTrack are separate from Cacti's. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |