Synchronizing Traffic Collection

One fundamental problem affecting collection is that most organizations possess a limited number of collection devices that they can place throughout the network. Ideally, one of the approaches discussed above permits performing collection concurrently with the number of devices you already have available. However, if this is not the case, you do not necessarily have to acquire new devices in order to collect background traffic.

Your alternative is to collect traffic in phases. For example, if you determine that you require traffic collection at twenty locations in your network, and you own twelve RMON-2 probes. Then, you will need two phases of traffic collection. No individual location should have its traffic collection repeated, so in this case you would utilize the output from twelve probes on the first phase, and from eight probes on the second phase, or some similar partitioning. Relocating probes is not a trivial task, so you probably will not be able to do both phases one right after the other. In this case, you could do the second phase on the following day, but beginning at the same time of day. The objective is to gather data while the network is experiencing similar traffic patterns.

The background traffic system automatically synchronizes all imported traffic information to the same time. The first “bucket” of each source of background traffic is applied at the same time, and that time is determine by the “Background Traffic Start Delay” simulation attribute (set this value in the “Configure Simulation” dialog box).