|
You should normally have a separate .cfg file for each device. This will make it much clearer what is going on! Then, routers2 will have a separate item in the Device menu per device, and within these, the Targets menu will show the interfaces for that device only.
Call cfgmaker once per device, rather than once for all devices.
If you need a single cfg file to run MRTG on, then you can subsequently create a 'master.cfg' that uses Include: to include these separate device cfg files. This would only be used by MRTG, and should be ignored by routers2 (you can add in routers.cgi*Ignore:yes to make routers2 ignore the master.cfg)
_________________ Steve Shipway UNIX Systems, ITSS, University of Auckland, NZ Woe unto them that rise up early in the morning... -- Isaiah 5:11
|