Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Starting the Traffic Collection

 

A complete network, ready for traffic collection, requires a Global Network with at least one router group for collection, with every router group having a traffic data collector and at least one router, a valid collection interval (best to set at multiples of 300(sec) – 5 minute interval) and MIB data set from the Collection Data panel. Best practice would suggest creating a router group for every traffic data collector and limit the number of routers to about 100 to 150 per collector, though it can probably handle more.

To start collection, press the Start button, which is the first button on the toolbar. The server will then initiate a collection session on each collector associated with a router group. Currently, there are no means to start collection for just one router group, as the network is collected as a whole.

To stop collection, press the collection stop button (second button on toolbar).

Note

Collection will continue even if the client is shut down, as long as the collectors and the DGS are running. Even the DGS can be shut down for brief periods ( < 10 minutes) while still ensuring a continuous data stream because the data messages sent by the collectors are stored in message queues. As long as the messaging server is running, these messages will be available to the DGS for processing.

Be advised that any changes made to the collection elements in the client will affect the running collection upon saving, that is, removing a router from a router group will remove that router from collection, deleting a router group will terminate the corresponding collection session on its associated traffic data collector.

Collection Status

After collection has started, click on the Collection Status tab to monitor collection events. Any errors, warnings, and updates, including “traffic collected” events will appear there. There is a limit to the number of events displayed in the event table. To clear the events in the table, press the reset button. Note that this only resets the events table and not any element changes made in the client.

To check the collection status, go to the Collection Status tab. Clicking on an entry will also show expand the Short Description column in the Status Detail panel at the bottom of the window

Figure 1: Collection Status Panel
Collection Status Panel
  • An Event Type of “warning” (severity MINOR) will be highlighted in green by default, such as the “Task already queued or running, skipping:10.30.0.1” This message may be an indication that the router is still busy servicing the prior request.

  • An Event Type of “error” (severity MAJOR) will be highlighted in red by default. For example, an error’s description might be “[108.5.5.5] Timeout: No Response from 108.5.5.5” This indicates that the 108.5.5.5 router is not reachable.

  • An Event Type of “normal” (severity INFO) will not be highlighted by default. A typical Status Type is “CollectionUpdate” indicating that the rest of the collection is running smoothly. Another one is “CollectorRegister” and “CollectorStart” , that appears once the user has started up a new traffic data collector.

Collection Settings

The last tab, Collection Settings, allows the user to set different settings for the Traffic Collection Manager, such as the color settings from (Master Collection Panel > Panel - Collection Status).

Figure 2: Settings for Status Window
Settings for Status Window