cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1292
Views
0
Helpful
2
Replies

QoS on multiple sub-interfaces at HQ site

aoshea
Level 1
Level 1

Dear Support,

Many thanks for everyone’s assistance so far but have a final question to complete my QoS configuration.

Q. I have a double hub-and-spoke topology, that is redundant. Each remote site has a connection to both the datacentre and the HQ site. At both the HQ and Datacentre sites, they are connected to the remote sites via a LES 10 connection that has 6 sub-interfaces. Each remote site has bandwidth of 2Mbps.

If I have a single Ethernet interface (LES 10), that has several sub-interfaces how should I set the ‘shape’ parameter or do I need several ‘shapers’ (i.e. do i need a separate policy-map for each sub-interface or can it been done with a single one?)

i.e.

class-map match-all BULK-DATA

match ip dscp af11 af12

class-map match-all INTERACTIVE-VIDEO

match ip dscp af41 af42

class-map match-all VOICE

match ip dscp cs5

class-map match-all MISSION-CRITICAL-DATA

match ip dscp 25

class-map match-all ROUTING

match ip dscp cs6

class-map match-all SCAVENGER

match ip dscp cs1

class-map match-all NET-MGMT

match ip dscp cs2

class-map match-any CALL-SIGNALING

match ip dscp cs3

match ip dscp af31

class-map match-all TRANSACTIONAL-DATA

match ip dscp af21 af22

!

!

policy-map BRANCH-WAN-EDGE

class VOICE

priority percent 50

class INTERACTIVE-VIDEO

priority percent 2

class CALL-SIGNALING

bandwidth percent 5

class ROUTING

bandwidth percent 3

class NET-MGMT

bandwidth percent 2

class MISSION-CRITICAL-DATA

bandwidth percent 5

random-detect

class TRANSACTIONAL-DATA

bandwidth percent 2

random-detect dscp-based

class BULK-DATA

bandwidth percent 2

random-detect dscp-based

class SCAVENGER

bandwidth percent 1

class class-default

bandwidth percent 3

random-detect

!

policy-map Shaper-sub-int1100

class class-default

shape average 1984000

service-policy BRANCH-WAN-EDGE

!

policy-map Shaper-sub-int1111

class class-default

shape average 1984000

service-policy BRANCH-WAN-EDGE

!

policy-map Shaper-sub-int1113

class class-default

shape average 1984000

service-policy BRANCH-WAN-EDGE

!

policy-map Shaper-sub-int1114

class class-default

shape average 1984000

service-policy BRANCH-WAN-EDGE

!

policy-map Shaper-sub-int1115

class class-default

shape average 1984000

service-policy BRANCH-WAN-EDGE

!

policy-map Shaper-sub-int1116

class class-default

shape average 1984000

service-policy BRANCH-WAN-EDGE

!

interface FastEthernet1/0

speed 10

full-duplex

!

interface FastEthernet1/0.1100

service-policy output Shaper-sub-int1100

!

interface FastEthernet1/0.1111

service-policy output Shaper-sub-int1111

!

interface FastEthernet1/0.1113

service-policy output Shaper-sub-int1113

!

interface FastEthernet1/0.1114

service-policy output Shaper-sub-int1114

!

interface FastEthernet1/0.1115

service-policy output Shaper-sub-int1115

!

interface FastEthernet1/0.1116

service-policy output Shaper-sub-int1116

encapsulation dot1Q 1116

ip address 172.16.32.33 255.255.255.252

thanks again, regards Adrian.

1 Accepted Solution

Accepted Solutions

pkhatri
Level 11
Level 11

Hi Adrian,

You do need a separate service-policy for each sub-interface as each of them needs to have a shaper applied individually which would result in back-pressure being applied in order to build up queuss and service them accordingly.

Also, if you are applying the same policy to each sub-interface and are confident that the shaping rates for all of them are always likely to be the same, you can use a single policy-map for all the interfaces. That is, instead of creating separate "Shaper-sub-intxxx" policies, just create a single one and apply it to all the sub-interfaces individually.

Cheers,

Paresh.

View solution in original post

2 Replies 2

pkhatri
Level 11
Level 11

Hi Adrian,

You do need a separate service-policy for each sub-interface as each of them needs to have a shaper applied individually which would result in back-pressure being applied in order to build up queuss and service them accordingly.

Also, if you are applying the same policy to each sub-interface and are confident that the shaping rates for all of them are always likely to be the same, you can use a single policy-map for all the interfaces. That is, instead of creating separate "Shaper-sub-intxxx" policies, just create a single one and apply it to all the sub-interfaces individually.

Cheers,

Paresh.

Hi.

I have the same setup.

My problem is, I can attached a policy on one sub-interface. But I cant on another sub-interface.

Example:

Gi4/0/3.1500 - I cant attach the policy-map

Gi4/0/3.1510 - I can attahc the same policy-map..

Im using 7200 NPE-G1 built-in GE interface and 7600 SIP-600 WAN card.

comments on this?