The policymap file is used to list the mapping of classes to policies and routers. In the policymap file, there is one line for each policy of a router. One router can have several policy maps. This policymap file is automatically created after performing the Create Policies for Classes in the NorthStar Planner client and then saving the network environment.
Each line in the policy map file contains information about the policy name, router name, defined classes and class policies (such as bandwidth and queue length). The priority class is always listed before the other classes. The format of each record is:
The following table provides the definition of each field (fields are separated by a vertical “|” line):
The type of queueing algorithm. Valid types are “CBWFQ”, “MDRR”, “MDRR strict”, “MDRR alternate”, “ERX”.
Reserved for future use. This field may be left empty for now.
Name of the router. This corresponds to the Node ID field in the muxloc file. A ‘-’ in this field indicates ‘Any Router’.
Name of a policy defined for the router
PriorityClass, Bandwidth(Kbps), -
Name of the priority class. This is followed by the bandwidth in Kbps, or the maximum bandwidth of the priority class. For MDRR queueing, this field should be substituted with the weight value.The ‘-’ indicates that this field (typically used for queue length) is not applicable for the priority class.
Classname, Bandwidth, QueueLength, bitmap, dscpbitmap, expbitmap, dscpbitmap1, bc, be, pir
This field defines the policy for each class. It is repeatable for up to 6 classes, not including the priority class.
The priority class is for Low Latency Queueing or Priority Queueing. Packets belonging to this class have higher priority than other classes. There is no queue limit for this class. That is why there is the dash “-“ in the third subfield.
CBWFQ| |Node0|policy_N0|voice,64,-|business_data,400,32|economy_data,100,16| CBWFQ| |Node1|policy_N1|voice,64,-,-,-|business_data,30%,32,-,-|economy_data,20%,16,-,-| MDRR strict| |-|policy1|first_class_data,6,-|business_data,3,30|class-default,1,40|
The following table explains the first line of the example:
Priority class name
After creating the policymap file, you need to let the system know where that file is. There are two ways of pointing to the policymap file:
Add in the specification file the following line:
policymap = policymap_filename
where policymap_filename is the name of the policymap file just created above.
Or, from the NorthStar Planner client edit the specification file. Click on Network Files tab of the Spec File Generation window. Select the policymap entry in the Device-Specific Files category, click Browse to locate the file, and then click the Set button.