对Diffserv-te的理解

Diffserv-te 结合了ds与te,克服了TE不能对流量分类的缺点.

Ds-te 使用所谓的sub-pool来建立，目前ds-TE只能通告一个SUB-SPOOL

配置思想：

1，  配置全局池和子池

2，  通常网络有数据流量和语音流量，在边缘区分流量，mqc中给语音流量使用exp5,用LLQ（EF PHB）并且对这个EXP5的流量限速，让所有EXP5的流量不超过sub-pool,子池通告大小和LLQ容量通常相等。并将该流量映射进ds-te.在cSPF计算完成后。通过rsvp通告sub-pool（LLQ队列大小）这个子池对应的是llQ的队列，因此只要在首端配置LLQ就可以了，以及沿LSP分配label.（ds-te承担exp5的流量，因为它使用了LLQ队列）

3，  设置首端带宽的大小

4，  设置好隧道抢占priority.全子池隧道可以抢占非子池的隧道。



 

Configuring the Pools and Tunnel

At the device level:

router-1(config)# ip cef

router-1(config)# mpls traffic-eng tunnels

[now one uses either the IS-IS commands on the left or the OSPF commands on the right]:

[now one resumes the common command set]:

router-1(config-router)# mpls traffic-eng router-id Loopback0

router-1(config-router)# exit

Create a virtual interface:

router-1(config)# interface Loopback0

router-1(config-if)# ip address 23.1.1.1 255.255.255.255

router-1(config-if)# no ip directed-broadcast

router-1(config-if)# exit

For the outgoing network interface:

interface POS4/0

ip address 10.1.1.1 255.255.255.0

mpls traffic-eng tunnels

ip rsvp bandwidth 140000 140000\

sub-pool 60000

 

Continuing at the network interface level, regardless of interface type:

[If using IS-IS instead of OSPF]:

router-1(config-if)# ip router isis

[and in all cases]:

router-1(config-if)# exit

At the tunnel interface:

router-1(config)# interface Tunnel1

router-1(config-if)# bandwidth 110000

router-1(config-if)# ip unnumbered Loopback0

router-1(config-if)# tunnel destination 27.1.1.1

router-1(config-if)# tunnel mode mpls traffic-eng

router-1(config-if)# tunnel mpls traffic-eng priority 0 0

router-1(config-if)# tunnel mpls traffic-eng bandwidth sub-pool 40000

router-1(config-if)# tunnel mpls traffic-eng path-option 1 dynamic

To ensure that packets destined to host 26.1.1.1 and subnet 26.1.1.0 are sent into the sub-pool tunnel,

we create a static route. At the device level:

router-1(config)# ip route 26.1.1.0 255.255.255.0 Tunnel1

router-1(config)# exit

And in order to make sure that the Interior Gateway Protocol (IGP) will not send any other traffic down

this tunnel, we disable autoroute announce:

router-1(config)# no tunnel mpls traffic-eng autoroute announce

 

For Service from Site A to Site D

At the inbound physical interface (FE4/0):

1. In global configuration mode, create a class of traffic matching ACL 100, called "sla-1-class":

class-map match-all sla-1-class

match access-group 100

2. Create an ACL 100 to refer to all packets destined to 26.1.1.1:

access-list 100 permit ip any host 26.1.1.1

3. Create a policy named “sla-1-input-policy”, and according to that policy:

a. Packets in the class called “sla-1-class” are rate-limited to:

– a rate of 8 million bits per second

– a normal burst of 1 million bytes

– a maximum burst of 2 million bytes

b. Packets which conform to this rate are marked with MPLS experimental bit 5 and are

forwarded.

c. Packets which exceed this rate are dropped.

d. All other packets are marked with experimental bit 0 and are forwarded.

policy-map sla-1-input-policy

class sla-1-class

police 8000000 1000000 2000000 conform-action set-mpls-exp-transmit 5 \

exceed-action drop

class class-default

set-mpls-exp-transmit 0

4. The policy is applied to packets entering interface FE4/0.

interface FastEthernet4/0

service-policy input sla-1-input-policy

For Service from Site B to Subnet “Province”

At the inbound physical interface (FE4/1):

1. In global configuration mode, create a class of traffic matching ACL 120, called "sla-2-class":

class-map match-all sla-2-class

match access-group 120

2. Create an ACL, 120, to refer to all packets destined to subnet 26.1.1.0:

access-list 120 permit ip any 26.1.1.0 0.0.0.255

3. Create a policy named “sla-2-input-policy”, and according to that policy:

a. Packets in the class called “sla-2-class” are rate-limited to:

– a rate of 32 million bits per second

– a normal burst of 1 million bytes

– a maximum burst of 2 million bytes

b. Packets which conform to this rate are marked with MPLS experimental bit 5 and are

forwarded.

c. Packets which exceed this rate are dropped.

d. All other packets are marked with experimental bit 0 and are forwarded.

policy-map sla-2-input-policy

class sla-2-class

police 32000000 1000000 2000000 conform-action set-mpls-exp-transmit 5 \

exceed-action drop

class class-default

set-mpls-exp-transmit 0

4. The policy is applied to packets entering interface FE4/1.

interface FastEthernet4/1

service-policy input sla-2-input-policy

 

 

 

 

For Both Services

The outbound interface (POS4/0 or ATM2/0.4) is configured as follows:

1. In global configuration mode, create a class of traffic matching experimental bit 5, called

"exp-5-traffic".

class-map match-all exp-5-traffic

match mpls experimental 5

 

2. Create a policy named “output-interface-policy”. According to that policy, packets in the class

“exp-5-traffic” are put in the priority queue (which is rate-limited to 62 kbits/sec).这个地方我认为应该配置成sub带宽的大小40M而不是62K

policy-map output-interface-policy

class exp-5-traffic

priority 62

3. The policy is applied to packets exiting subinterface ATM2/0.4 (left side) or interface POS4/0 (right

side):

interface POS4/0

service-policy output\

output-interface-policy

Tunnel Midpoint Configuration

All four interfaces on the 7200 midpoint router are configured identically to the outbound interface of

the head router (except, of course, for the IDs of the individual interfaces):

Configuring the Pools and Tunnels

At the device level:

router-3(config)# ip cef

router-3(config)# mpls traffic-eng tunnels

[now one uses either the IS-IS commands on the left or the OSPF commands on the right]:

router ospf 100

router-3(config-router)# net 49.0000.2400.0000.0011.00     redistribute connected

router-3(config-router)# metric-style wide              network 10.1.1.0 0.0.0.255 area 0

router-3(config-router)# is-type level-1                  network 11.1.1.0 0.0.0.255 area 0

router-3(config-router)# mpls traffic-eng level-1      network 24.1.1.1 0.0.0.0 area 0

router-3(config-router)# passive-interface Loopback0     network 12.1.1.0 0.0.0.255 area

router-3(config-router)#                                    network 13.1.1.0 0.0.0.255 area 0

router-3(config-router)#                                     mpls traffic-eng area 0

[now one resumes the common command set]:

router-3(config-router)# mpls traffic-eng router-id Loopback0

router-3(config-router)# exit

Create a virtual interface:

router-3(config)# interface Loopback0

router-3(config-if)# ip address 24.1.1.1 255.255.255.255

router-3(config-if)# exit

For one incoming network interface, first at the device level:

interface POS2/1

ip address 10.1.1.2 255.0.0.0

mpls traffic-eng tunnels

ip rsvp bandwidth 140000 140000\

sub-pool 60000

Continuing at the network interface level, regardless of interface type:

[If using IS-IS instead of OSPF]:

router-3(config-if)# ip router isis

[and in all cases]:

router-3(config-if)# exit

For the other incoming network interface, first at the device level:

interface POS1/1

ip address 11.1.1.2 255.0.0.0

mpls traffic-eng tunnels

ip rsvp bandwidth 140000 140000/

sub-pool 60000

Continuing at the network interface level, regardless of interface type:

[If using IS-IS instead of OSPF]:

router-3(config-if)# ip router isis

[and in all cases]:

router-3(config-if)# exit

[if using IS-IS instead of OSPF]:

router-3(config-subif)# ip router isis

router-3(config-subif)# exit

For one outgoing network interface:

ATM-PVC case appears on the left; POS case on the right]:

 

interface POS3/1

ip address 11.1.1.2 255.0.0.0

mpls traffic-eng tunnels

ip rsvp bandwidth 140000 140000\

sub-pool 60000

 

 

Continuing at the network interface level, regardless of interface type:

[If using IS-IS instead of OSPF]:

router-3(config-if)# ip router isis

[and in all cases]:

router-3(config-if)# exit

For the other outgoing network interface, first at the device level:

interface POS3/1

ip address 12.1.1.1 255.0.0.0

mpls traffic-eng tunnels

ip rsvp bandwidth 140000 140000\

sub-pool 60000

 

 

 

Tunnel Tail Configuration

The inbound interfaces on the 7200 tail router are configured identically to the inbound interfaces of

the midpoint routers (except, of course, for the ID of each particular interface):

Configuring the Pools and Tunnels

At the device level:

router-4(config)# ip cef

router-4(config)# mpls traffic-eng tunnels

[now one uses either the IS-IS commands on the left or the OSPF commands on the right]:

[now one resumes the common command set]:

router-4(config-router)# mpls traffic-eng router-id Loopback0

router-4(config-router)# exit

Create a virtual interface:

router-4(config)# interface Loopback0

router-4(config-if)# ip address 27.1.1.1 255.255.255.255

router-4(config-if)# exit

For one incoming network interface, first at the device level:

[ATM-PVC case appears on the left; POS case on the right]:

[then continue each case at the network interface level]:

router-4(config)# router isis router ospf 100

router-4(config-router)# net 49.0000.2700.0000.0000.00     redistribute connected

router-4(config-router)# metric-style wide                    network 12.1.1.0 0.0.0.255 area 0

router-4(config-router)# is-type level-1                    network 14.1.1.0 0.0.0.255 area 0

router-4(config-router)# mpls traffic-eng level-1           network 27.1.1.1 0.0.0.0 area 0

router-4(config-router)# passive-interface Loopback0        mpls traffic-eng area 0

router-4(config)# interface POS2/1

router-4(config-if)# mpls traffic-eng tunnels              ip address 12.1.1.2 255.0.0.0

router-4(config-if)# ip rsvp bandwidth 140000 140000\

sub-pool 60000

mpls traffic-eng tunnels

ip rsvp bandwidth 140000 140000\

sub-pool 60000

 

interface POS2/2

ip address 14.1.1.2 255.0.0.0

mpls traffic-eng tunnels

ip rsvp bandwidth 140000 140000\

sub-pool 60000

 

Continuing at the network interface level, regardless of interface type:

[If using IS-IS instead of OSPF]:

router-4(config-if)# ip router isis

[and in all cases]:

router-4(config-if)# exit

Because the tunnel ends on the tail (does not include any outbound interfaces of the tail router), no

outbound QoS configuration is used.

[if using IS-IS instead of OSPF]:

router-4(config-subif)# ip router isis

router-4(config-subif)# exit

 

 

Configuring the Pools and Tunnel

At the device level:

router-1(config)# ip cef

router-1(config)# mpls traffic-eng tunnels

[now one uses either the IS-IS commands on the left or the OSPF commands on the right]:

[now one resumes the common command set]:

router-1(config-router)# mpls traffic-eng router-id Loopback0

router-1(config-router)# exit

Create a virtual interface:

router-1(config)# interface Loopback0

router-1(config-if)# ip address 23.1.1.1 255.255.255.255

router-1(config-if)# no ip directed-broadcast

router-1(config-if)# exit

For the outgoing network interface:

interface POS4/0

ip address 10.1.1.1 255.255.255.0

mpls traffic-eng tunnels

ip rsvp bandwidth 140000 140000\

sub-pool 60000

 

Continuing at the network interface level, regardless of interface type:

[If using IS-IS instead of OSPF]:

router-1(config-if)# ip router isis

[and in all cases]:

router-1(config-if)# exit

At the tunnel interface:

router-1(config)# interface Tunnel1

router-1(config-if)# bandwidth 110000

router-1(config-if)# ip unnumbered Loopback0

router-1(config-if)# tunnel destination 27.1.1.1

router-1(config-if)# tunnel mode mpls traffic-eng

router-1(config-if)# tunnel mpls traffic-eng priority 0 0

router-1(config-if)# tunnel mpls traffic-eng bandwidth sub-pool 40000

router-1(config-if)# tunnel mpls traffic-eng path-option 1 dynamic

To ensure that packets destined to host 26.1.1.1 and subnet 26.1.1.0 are sent into the sub-pool tunnel,

we create a static route. At the device level:

router-1(config)# ip route 26.1.1.0 255.255.255.0 Tunnel1

router-1(config)# exit

And in order to make sure that the Interior Gateway Protocol (IGP) will not send any other traffic down

this tunnel, we disable autoroute announce:

router-1(config)# no tunnel mpls traffic-eng autoroute announce

 

For Service from Site A to Site D

At the inbound physical interface (FE4/0):

1. In global configuration mode, create a class of traffic matching ACL 100, called "sla-1-class":

class-map match-all sla-1-class

match access-group 100

2. Create an ACL 100 to refer to all packets destined to 26.1.1.1:

access-list 100 permit ip any host 26.1.1.1

3. Create a policy named “sla-1-input-policy”, and according to that policy:

a. Packets in the class called “sla-1-class” are rate-limited to:

– a rate of 8 million bits per second

– a normal burst of 1 million bytes

– a maximum burst of 2 million bytes

b. Packets which conform to this rate are marked with MPLS experimental bit 5 and are

forwarded.

c. Packets which exceed this rate are dropped.

d. All other packets are marked with experimental bit 0 and are forwarded.

policy-map sla-1-input-policy

class sla-1-class

police 8000000 1000000 2000000 conform-action set-mpls-exp-transmit 5 \

exceed-action drop

class class-default

set-mpls-exp-transmit 0

4. The policy is applied to packets entering interface FE4/0.

interface FastEthernet4/0

service-policy input sla-1-input-policy

For Service from Site B to Subnet “Province”

At the inbound physical interface (FE4/1):

1. In global configuration mode, create a class of traffic matching ACL 120, called "sla-2-class":

class-map match-all sla-2-class

match access-group 120

2. Create an ACL, 120, to refer to all packets destined to subnet 26.1.1.0:

access-list 120 permit ip any 26.1.1.0 0.0.0.255

3. Create a policy named “sla-2-input-policy”, and according to that policy:

a. Packets in the class called “sla-2-class” are rate-limited to:

– a rate of 32 million bits per second

– a normal burst of 1 million bytes

– a maximum burst of 2 million bytes

b. Packets which conform to this rate are marked with MPLS experimental bit 5 and are

forwarded.

c. Packets which exceed this rate are dropped.

d. All other packets are marked with experimental bit 0 and are forwarded.

policy-map sla-2-input-policy

class sla-2-class

police 32000000 1000000 2000000 conform-action set-mpls-exp-transmit 5 \

exceed-action drop

class class-default

set-mpls-exp-transmit 0

4. The policy is applied to packets entering interface FE4/1.

interface FastEthernet4/1

service-policy input sla-2-input-policy

 

 

 

 

For Both Services

The outbound interface (POS4/0 or ATM2/0.4) is configured as follows:

1. In global configuration mode, create a class of traffic matching experimental bit 5, called

"exp-5-traffic".

class-map match-all exp-5-traffic

match mpls experimental 5

 

2. Create a policy named “output-interface-policy”. According to that policy, packets in the class

“exp-5-traffic” are put in the priority queue (which is rate-limited to 62 kbits/sec).这个地方我认为应该配置成sub带宽的大小40M而不是62K

policy-map output-interface-policy

class exp-5-traffic

priority 62

3. The policy is applied to packets exiting subinterface ATM2/0.4 (left side) or interface POS4/0 (right

side):

interface POS4/0

service-policy output\

output-interface-policy

Tunnel Midpoint Configuration

All four interfaces on the 7200 midpoint router are configured identically to the outbound interface of

the head router (except, of course, for the IDs of the individual interfaces):

Configuring the Pools and Tunnels

At the device level:

router-3(config)# ip cef

router-3(config)# mpls traffic-eng tunnels

[now one uses either the IS-IS commands on the left or the OSPF commands on the right]:

router ospf 100

router-3(config-router)# net 49.0000.2400.0000.0011.00     redistribute connected

router-3(config-router)# metric-style wide              network 10.1.1.0 0.0.0.255 area 0

router-3(config-router)# is-type level-1                  network 11.1.1.0 0.0.0.255 area 0

router-3(config-router)# mpls traffic-eng level-1      network 24.1.1.1 0.0.0.0 area 0

router-3(config-router)# passive-interface Loopback0     network 12.1.1.0 0.0.0.255 area

router-3(config-router)#                                    network 13.1.1.0 0.0.0.255 area 0

router-3(config-router)#                                     mpls traffic-eng area 0

[now one resumes the common command set]:

router-3(config-router)# mpls traffic-eng router-id Loopback0

router-3(config-router)# exit

Create a virtual interface:

router-3(config)# interface Loopback0

router-3(config-if)# ip address 24.1.1.1 255.255.255.255

router-3(config-if)# exit

For one incoming network interface, first at the device level:

interface POS2/1

ip address 10.1.1.2 255.0.0.0

mpls traffic-eng tunnels

ip rsvp bandwidth 140000 140000\

sub-pool 60000

Continuing at the network interface level, regardless of interface type:

[If using IS-IS instead of OSPF]:

router-3(config-if)# ip router isis

[and in all cases]:

router-3(config-if)# exit

For the other incoming network interface, first at the device level:

interface POS1/1

ip address 11.1.1.2 255.0.0.0

mpls traffic-eng tunnels

ip rsvp bandwidth 140000 140000/

sub-pool 60000

Continuing at the network interface level, regardless of interface type:

[If using IS-IS instead of OSPF]:

router-3(config-if)# ip router isis

[and in all cases]:

router-3(config-if)# exit

[if using IS-IS instead of OSPF]:

router-3(config-subif)# ip router isis

router-3(config-subif)# exit

For one outgoing network interface:

ATM-PVC case appears on the left; POS case on the right]:

 

interface POS3/1

ip address 11.1.1.2 255.0.0.0

mpls traffic-eng tunnels

ip rsvp bandwidth 140000 140000\

sub-pool 60000

 

 

Continuing at the network interface level, regardless of interface type:

[If using IS-IS instead of OSPF]:

router-3(config-if)# ip router isis

[and in all cases]:

router-3(config-if)# exit

For the other outgoing network interface, first at the device level:

interface POS3/1

ip address 12.1.1.1 255.0.0.0

mpls traffic-eng tunnels

ip rsvp bandwidth 140000 140000\

sub-pool 60000

 

 

 

Tunnel Tail Configuration

The inbound interfaces on the 7200 tail router are configured identically to the inbound interfaces of

the midpoint routers (except, of course, for the ID of each particular interface):

Configuring the Pools and Tunnels

At the device level:

router-4(config)# ip cef

router-4(config)# mpls traffic-eng tunnels

[now one uses either the IS-IS commands on the left or the OSPF commands on the right]:

[now one resumes the common command set]:

router-4(config-router)# mpls traffic-eng router-id Loopback0

router-4(config-router)# exit

Create a virtual interface:

router-4(config)# interface Loopback0

router-4(config-if)# ip address 27.1.1.1 255.255.255.255

router-4(config-if)# exit

For one incoming network interface, first at the device level:

[ATM-PVC case appears on the left; POS case on the right]:

[then continue each case at the network interface level]:

router-4(config)# router isis router ospf 100

router-4(config-router)# net 49.0000.2700.0000.0000.00     redistribute connected

router-4(config-router)# metric-style wide                    network 12.1.1.0 0.0.0.255 area 0

router-4(config-router)# is-type level-1                    network 14.1.1.0 0.0.0.255 area 0

router-4(config-router)# mpls traffic-eng level-1           network 27.1.1.1 0.0.0.0 area 0

router-4(config-router)# passive-interface Loopback0        mpls traffic-eng area 0

router-4(config)# interface POS2/1

router-4(config-if)# mpls traffic-eng tunnels              ip address 12.1.1.2 255.0.0.0

router-4(config-if)# ip rsvp bandwidth 140000 140000\

sub-pool 60000

mpls traffic-eng tunnels

ip rsvp bandwidth 140000 140000\

sub-pool 60000

 

interface POS2/2

ip address 14.1.1.2 255.0.0.0

mpls traffic-eng tunnels

ip rsvp bandwidth 140000 140000\

sub-pool 60000

 

Continuing at the network interface level, regardless of interface type:

[If using IS-IS instead of OSPF]:

router-4(config-if)# ip router isis

[and in all cases]:

router-4(config-if)# exit

Because the tunnel ends on the tail (does not include any outbound interfaces of the tail router), no

outbound QoS configuration is used.

[if using IS-IS instead of OSPF]:

router-4(config-subif)# ip router isis

router-4(config-subif)# exit