Create a Dynamic Partition
With PacketWise's dynamic partition feature, subpartitions are automatically
created as users become active in a traffic class. This capability allows
service providers or enterprise customers to provision precise amounts
of bandwidth on a per-user basis in just one step. Dynamic partitions
also can be used to guarantee fairness per subpartition even in configurations
where bandwidth is oversubscribed. So, if demand ever exceeds available
bandwidth, dynamic partitions can ensure that each user will get the same
amount of bandwidth.
Note: If you are using the Easy Configure feature, you should
not create dynamic partitions.
|
|
Note: To perform this task from PolicyCenter, you must first select a group and/or unit configuration from the Group:
and Unit: drop-down lists at the top of the page.
|
To make a partition dynamic:
Note: To create a dynamic partition, you must
first create a static partition for the traffic class (see Create
a Partition) and then specify the dynamic partition settings. If you
already have a static partition defined for the traffic class, open the
partition definition (see Modify a Partition)
and then specify the dynamic partition settings.
1. In the New Partition (or Partition)
window, click details. The Dynamic Subpartition window appears.
 show screen
2. Define the user as a single IP address or a subnet:
- To define a user as a single IP address, select Single address.
- To define a user as a subnet, select Subnet, then select the
CIDR value that represents the number of constant bits in the address
range.
3. Select the side (Inside or Outside)
on which the different IP addresses or subnets that will generate dynamic
subpartitions will be found.
For example, in a configuration in which the PacketShaper
unit sits between a LAN and the Internet, select Inside to create
a dynamic subpartition for each inside client (LAN user) that connects
to any outside host. Alternatively, select Outside to create a
subpartition for each outside host connected to any inside client.
Note: Dynamic subpartitions can be based on inside
or outside systems, independent of the class' matching rules (which may
specify addresses or subnets specifically on the inside or outside). This
allows subpartitioning based on the addresses you classify, or their communicating
peer systems.
4. Define the new subpartition using the following
parameters:
| Field |
Description |
| Subpartition size |
The minimum amount of bandwidth to be assigned to each user, expressed
in bits per second (bps) or as a percentage of the static
partition's size (%). If the size is entered in bits per
second, you can follow the integer by a “k” (thousands)
or “M” (millions).
Set this field to zero to have PacketWise allocate bandwidth equitably
to each subpartition, so that the total of all subpartitions equals
the static partition's size.
Note: Minimum subpartition size is frequently best handled
by setting this field to zero and setting a maximum number of subpartitions
(covered below). However, you must use a non-zero size if you want
to implement per-session guaranteed rates within rate policies for
this same traffic.
|
| Burstable |
When selected, allows each subpartition to use available
excess bandwidth if needed; each subpartition will be allocated the
same amount of excess bandwidth. This field must be selected
with a subpartition size value of zero. When the subpartition's size
is explicit (not 0) and this box is unchecked, each subpartition has
a fixed size; when it is not using its reserved bandwidth, that bandwidth
is available to other traffic. |
| Limit |
The maximum amount of bandwidth to be assigned to each subpartition.
The limit can be specified in bits per second or as a percentage
of the static partition's size. Use this field only if you want
to enforce a cap on each user or subnet even if more bandwidth is
available. Managed bandwidth service providers are most frequently
in this position, needing to cut off usage at agreed-upon, paid-for
limits. If you don't want to enforce a cap, leave the field blank.
Even if this field is left blank, the limit on the static, parent
partition still restricts the total bandwidth for the aggregate
of all subpartitions.
|
5. Optional: Set a cap on the number of active
users in the dynamic partition by entering a value in the maximum number
of subpartitions box.
Note: If the partition is fixed (non-burstable),
be sure to put a cap on the dynamic subpartitions and create an overflow
partition. This will prevent oversubscription problems.
6. Optional: Create an overflow partition for
users to tap into if the cap is exceeded. Select the Enable checkbox
and then use the following parameters:
| Field |
Description |
| Overflow subpartition size |
The minimum amount of bandwidth in the overflow partition, expressed
in bits per second (bps) or as a percentage of the static partition's
size (%). If you leave this field blank, the overflow subpartition's
minimum size will be uncommitted (whatever is not committed
to other partitions). |
| Burstable |
When selected, allows the overflow partition to use available excess
bandwidth if needed. When this box is unchecked, the overflow partition
has a fixed size; when it is not using its reserved bandwidth, that
bandwidth is available to other traffic. |
| Limit |
The maximum amount of bandwidth in the overflow subpartition. The
limit can be specified in bits per second or as a percentage. Must
be blank or a number larger than the size field. |
Note: If you don't create an overflow partition,
flows will be refused when the cap is reached or when the partition limit
on the box is exceeded.
7. Click OK.
8. Click add partition to create the dynamic
subpartition.
Examples of dynamic partitions and their effects:
| Dynamic Partition Values |
Effects |
|
Static partition
Size: 1.5 Mbps
Burstable: not selected
Limit: (blank)
Dynamic subpartitions
Subpartition size: 0
Burstable: checked
Limit: (blank)
Maximum #: (blank)
Overflow partition: (blank)
|
With two users: they share the entire 1.5 Mbps. If one uses less
than 750 Kbps, then the other can access more. If the two users
don't use the 1.5 Mbps, it's available to other traffic classes
outside the static partition.
With 50 users: each gets 30 Kbps. If any don't use their quota,
it's shared among others that can use it. If there's still leftover
bandwidth in the static partition after all 50 users are serviced,
it's available to other traffic classes.
With 100 users: each gets 15 Kbps. Nobody can use more unless someone
uses less.
With 200 users: each gets 7.5 Kbps.
|
|
Static partition
Size: 1.5 Mbps
Burstable: not selected
Limit: (blank)
Dynamic subpartitions
Subpartition size: 0
Burstable: checked
Limit: (blank)
Maximum #: 100
Overflow partition: (blank)
|
With two users: they share the entire 1.5 Mbps. If one uses less
than 750 Kbps, then the other can access more. If the two users
don't use the 1.5 Mbps, it's available to other traffic classes
outside the static partition.
With 50 users: each gets 30 Kbps. If any don't use their quota,
it's shared among others that can use it. If there's still leftover
bandwidth in the static partition after all 50 users are serviced,
it's available to other traffic classes.
With 100 users: each gets 15 Kbps. Nobody can use more unless someone
uses less.
With 200 users: 100 each get 15 Kbps, 100 get refused.
|
|
Static partition
Size: 1.5 Mbps
Burstable: not selected
Limit: (blank)
Dynamic subpartitions
Subpartition size: 0
Burstable: checked
Limit: 30 Kbps
Maximum #: 100
Overflow partition: 100 Kbps
|
With two users: each have 30 Kbps. The remaining 1.4+ Mbps is available
to other traffic classes outside the static partition.
With 50 users: each gets 30 Kbps. If any don't use their quota,
it's not shared among other subpartition users. If there's
leftover bandwidth, it's available to other traffic classes outside
the static partition.
With 100 users: each gets 15 Kbps. Nobody can use more unless someone
uses less. And nobody can use more than 30 Kbps.
With 200 users: 100 each get 14 Kbps. And the remaining 100 share
the overflow partition at 1 Kbps each.
|
After the dynamic partition is set up, whenever a new user begins generating
flows in that class, a subpartition will be created for the user on the
fly. The per-user partition remains in existence until it's reused for
new flows by the same user or needed by another user.
See also:
Provision
Bandwidth Equitably
Modify a Dynamic Partition
Remove a Dynamic Partition
View Partition Information
Partition Overview
|
