The traffic.xml file is read by the RSVP-TE module (RSVP). The file must be in the same folder as the executable network simulation file.
The XML elements used in the "traffic.xml" file:
The following presents an example file:
<?xml version="1.0"?>
<!-- Example of traffic control file -->
<traffic>
<conn>
<src>10.0.0.1</src>
<dest>10.0.1.2</dest>
<setupPri>7</setupPri>
<holdingPri>7</holdingPri>
<bandwidth>400</bandwidth>
<delay>5</delay>
</conn>
<conn>
<src>11.0.0.1</src>
<dest>11.0.1.2</dest>
<setupPri>7</setupPri>
<holdingPri>7</holdingPri>
<bandwidth>100</bandwidth>
<delay>5</delay>
</conn>
</traffic>
An example of using RSVP-TE as signaling protocol can be found in ExplicitRouting folder distributed with the simulation. In this example, a network similar to the network in LDP-MPLS example is setup. Instead of using LDP, "signaling" parameter is set to 2 (value of RSVP-TE handler). The following xml file is used for traffic control. Note the explicit routes specified in the second connection. It indicates that the route is a strict one since the values of every hop types are 0. The route defined is 10.0.0.1 -> 1.0.0.1 -> 10.0.0.3 -> 1.0.0.4 -> 10.0.0.5 -> 10.0.1.2.
<?xml version="1.0"?>
<!-- Example of traffic control file -->
<traffic>
<conn>
<src>10.0.0.1</src>
<dest>10.0.1.2</dest>
<setupPri>7</setupPri>
<holdingPri>7</holdingPri>
<bandwidth>0</bandwidth>
<delay>0</delay>
<ER>false</ER>
</conn>
<conn>
<src>11.0.0.1</src>
<dest>11.0.1.2</dest>
<setupPri>7</setupPri>
<holdingPri>7</holdingPri>
<bandwidth>0</bandwidth>
<delay>0</delay>
<ER>true</ER>
<route>1.0.0.1,0,1.0.0.3,0,1.0.0.4,0,1.0.0.5,0,10.0.1.2,0</route>
</conn>
</traffic>