|
Previous
|
Content |
Next
|
|
|
2.3.4- Edge32-ca-u32 |
|
 |
|
| Fourth example implemented by DS Linux Implementation is called
Edge32-ca-u32. This example is very similar to
the previous one. The goal, again, is to implement an edge router as a
re-marker device; i.e., packets are expected to come previously
marked, probably by another DS capable domain. At the same time
some policing on entering packets is required. The scheme is as
follows: |
|
|
| This time we are going
to take an alternative solution, perhaps a cleaner one. We are going to
implement four classes in the egress side (the side that face to the
inner side of your domain); these classes are as
follows: |
|
|
|
The idea is to implement a mechanism in the egress side with four
classes that, according to the class, mark the packet's DS field by
one of the outgoing values (AF41, AF42, AF43 or BE). |
|
Using Cisco we can do this as follows: |
|
|
|
Replace Y for your interface in the inner side of your
domain. |
|
What do we have? A simple marker that according to the packet's
qos-group will mark it using the mapping of Table 6 above. |
| What's next? Well, using CAR we have to police and mark
packets in a qos-group in a such way to fulfill the rules in
Table 7 above. Let's type then: |
| |
|
 |
| |
| Using a symbolic input interface X. |
| |
| Okay, dear fellows, next example is Edge31-cb-tables; here we go. |
|
|
|
|
|
|
|
|
|
Previous
|
Content |
Next
|
