A question about bandwidth reservation and priority

[TonyWang123]

Dear all,

I am using this project to simulate path computation with bandwidth constraint and priority. I first ran the server with topologiaLine.xml and then ran the QuickClient with the following cmd:

java -jar PCC-jar-with-dependencies.jar 127.0.0.1 4189 192.168.1.2 192.168.1.3 -rgbw 200

I assume that the -rgbw option is for the bandwidth and expect a result of no path since the max bandwidth of each link in the topology is 100. However, I got this result:

Respuesta RESP: <RP ReqID: 17 Prio: 0 Reopt: 0 Bid: 0 Loose: 0 SupOF: false retry false>PATH={ <ERO: /192.168.1.2:2 /192.168.1.3/32 > }

Are there some problems in my setting?

Also, in the current project, is it possible that a high-priority path computing request can preempt low-priority paths that already computed?

Thanks!
Xin

[oscargdd]

Hi Xin,
First of all, thanks for using the project and testing it!

When you run quick client, to specify the bandwidth you have two options:
-rgbw Use this to specify the Requested Generalized BandWidth (for example in flexi-grid optical networks) to specify the amount of spectrum needed (m, an integer of chunks of 12,5 GHz)
-rbw Use this to specify the Requested BandWidth (in terms of bits per second). I think this is the option you are interested in. Sorry, it was not documented.

Then, you can also specify, via the of code, which objective funtion to use, and you can configure the PCE to use a particular algorithm with an objetive function. If no OF code is specified, the default algorithm is chosen. Currently, the default alogithms looks for a path without considering the constrataints.

There is an algorithm that you can use for that, mpls.MPLS_MinTH_Algorithm
Add the following rule to the PCE xml:

And in the request add the option -of 500

Then, you will use this algorithm.

[TonyWang123]

Which rule to add to the xml? I tried the following:

<algorithmRule of="500" svec="false" name="mpls.MPLS_MinTH_Algorithm" isParentPCEAlgorithm="false" isMPLSAlgorithm="true"/>

And it seems not correct.

[TonyWang123]

One more question is that how the priority works in your implementation? I found the following code in QuickClientObject:

int prio = 1;
rp.setPrio(prio);

A high-priority request will preempt routes that already are computed?

Thanks!