Limitations of the Background Traffic System

If you use background traffic, you must be aware of its limitations. Analytical modeling and hybrid analytical/discrete event simulation have some limitations because background traffic cannot capture all of the same behavior as pure discrete event simulation. Despite these existing limitations, the background traffic system is extremely useful, providing an approach to reduce simulation run times while still representing important effects of traffic in the network.

  • The background traffic system is IP-centric in its current implementation. This means that devices that are the sources and destinations of background traffic must contain the IP protocol. Pure IPX systems, for example, are not able to act in this capacity. Because IP is essentially the “conduit’ for background traffic information, only intermediate devices that support IP or that support IP at lower layers can be affected. Thus a Frame Relay switch that is part of an overall IP infrastructure can carry background traffic. However, no background traffic architecture exists at this time for a pure Frame Relay network that does not serve as a bearer of IP traffic.
  • Traffic flows (background routed traffic) only impact the network, not the server. Generating extra traffic in the network, by scaling the traffic flows for example, will not create a corresponding increase in task processing time on the server. This is due to the fact that the background traffic system is not capable of determining how traffic correlates to processing load on servers. It is therefore up to the user to take steps to properly load the servers. One way to accomplish this is to change the servers’ “background utilization” attribute.
  • Background traffic is transparent to certain protocol mechanisms. While many protocols in the model library are aware of the background traffic system, not all of their functionality reflects the presence of the additional traffic. For example, the weighted fair queuing mechanism of IP does not estimate background traffic’s contribution to queue lengths within each priority, because background traffic does not carry priority attributes at this time. Additional protocols and mechanisms that are not sensitive to the “background utilization” attribute are listed in the table below. This information is valid as of this printing. As integration of the background traffic system continues, you should check for availability of relevant model library upgrades.

Table 3: Models/Mechanisms that Do Not Account for Background Traffic¹

  • Non-LAN objects using switched or shared Token Ring
  • Non-LAN Objects using switched or shared FDDI
  • Non-LAN objects using half-duplex (shared) ethernet

Note 1: check for latest information