Policy Blocks
For example, assume lan1 speed is 100Mbps and lan5000 and lan5001 are based on lan1. The aggregate of the reservations of all policies for lan5000, lan5001 and lan1 cannot exceed the speed of lan1 (100Mbps) minus 80Kbps.
NOTE | Circumstances beyond the control of the |
| software can affect the transmission rate. For example, a hub |
| or switch might be completely saturated by traffic from other |
| hosts. As an analogy, think of this software as acting like a |
| valve on a garden hose controlling the flow of water out the |
| end. However, if the hose is kinked, the kink controls the flow |
| even more than the valve does. |
|
|
|
|
NOTE | Use of the term reservation is unrelated to the same term as |
| used in RSVP or the IETF IntSrv model. |
|
|
max[imum] b2[suffix]
Specifies the maximum allowed bandwidth be limited to b2[suffix] for traffic matching any filter used by the policy.
Thus, traffic matching any filter used by the policy gets at least as much bandwidth as the res value specified and if the adapter has spare bandwidth, the traffic can be sent up to, but not more than, the amount specified by max.
The b2 parameter specifies the numeric value of the maximum bandwidth.
The [suffix] parameter for the max[imum] attribute uses the same syntax rules as the [suffix] parameter for the res[ervation] attribute.
No white space is allowed between b2 and the [suffix].
The specified max attribute cannot be less than the specified res attribute.
The minimum value that can be specified is zero, (res must also be zero), meaning the traffic class is always dropped. You can use this for traffic classes that you don’t want to allow on the network.
If you do not want
Chapter 4 | 73 |