
C
AGGREGATING DEVICES
| This appendix describes: | |
| ■ | Overview |
| ■ | Default Aggregation |
|
| |
Overview | Aggregation reduces the amount of memory and disk resources required | |
| by Traffix™ Manager by collating the data collected for many devices into | |
| a single device. For example, in sites where there is a lot of Internet | |
| traffic, some or all external devices can be aggregated together. This may | |
| be the only way to limit the resource usage to an acceptable level. Use | |
| the Aggregation dialog box to set up aggregation. | |
| Once a definition has been specified and the Traffix Manager processes | |
| and Map restarted, this only affects data collected from this point on, and | |
| not data already collected. | |
| This makes any data analysis for data which crosses an “aggregation | |
| change” boundary hard to interpret. In this case, 3Com® recommends | |
| that you start a new database. See Appendix B, “Database Management | |
| Using Traffix Control Panel” for more information. | |
|
| |
Default | Aggregation provides a solution to the problem of large numbers of | |
Aggregation | devices on your network, without forcing you to discard any devices. Any | |
| loss of data prevents you from seeing a true picture of how your network | |
| is being used. Aggregation works by grouping together related devices | |
| and replacing them with a single aggregate device. |
By default, all devices in the local DNS domain will be kept in detail, and it is only those outside the local domain that can be aggregated. See “Launching the Traffix Manager Client” on page 26 for more information about local domains. You can specify an alternative aggregation policy.