Using Traffic Flows
Traffic flows provide another way to specify that the network and its components are processing traffic without having to represent in detail the patterns of that traffic. This approach does not require you to know the amount of traffic incident upon a given component; instead it calculates this amount for you based on an end-to-end description of the traffic. “End-to-end” means that traffic is specified from its originating host, to its final destination.
Traffic flows are specified and generated at the network layer. More precisely, as of this printing, this type of traffic operates only above the IP protocol. That is, every device containing an IP layer is also capable of being a source or destination for end-to-end traffic. This includes routers, servers, and workstations, but also LANs. Switches, for example, are not capable of acting as sources and destinations of end-to-end traffic.
Table 1: Sources and Destinations of Traffic Flows
- Routers
- Workstations
- Servers
- LANs
Specification of traffic flows essentially consist of a “traffic matrix”, where every host is considered a possible source of traffic for every other host. Here the term “host” is used generically to represent one of the sources or destinations of traffic, as shown in the table above. As you can imagine, this matrix can grow quite large. With just 1000 such hosts, for example, a traffic matrix with one million possible pairs of traffic would be defined. Fortunately, the traffic flow system is intelligent, allocating resources only for source-destination flows that actually contain traffic.
After you configure flows with the specified traffic, the models automatically route this traffic to the relevant devices in the network. This is done by using the routing models, such as RIP, OSPF, and IGRP, the same way explicit traffic is routed. Routing the traffic flows has the effect of creating traffic throughout the network on links, routers and switches, wherever the specified traffic would normally flow. With end-to-end traffic specification (as opposed to component-by-component), changes in the network infrastructure, or even changes like moving a server, are reflected correctly and automatically. This happens because the routes are recalculated in a new simulation of the network. For example, if you specify that 1000 packets per second are to flow between A and B over a defined interval, you can keep this traffic specification for two different network scenarios with a different path connecting A and B. In each simulation, the correct path will be selected and the traffic flows will affect corresponding parts of the network.