Hi everyone,
My network team has been having a discussion lately on where 'random-detect' should be placed. For a long time we had it in the scavenger class and the default class. I've personally never heard of it being in more than one class. I think it should be in the default-class only.
So this raised more questions:
1. can it be in both classes? If yes, Are there any problems with this?'
2. Should it only be in one class?
3. should it be in the Parent policy TEST_ETH10000 under class-default so it applies random-detect to all classes in the child policy TEST-MPLS-QoS ??
How are other enterprises implementing random-detect?
! Configure child policy
policy-map TEST-MPLS-QoS
class Voice
priority 1000
class Video
bandwidth remaining percent 40
class VVSignaling
bandwidth remaining percent 24
set ip dscp cs3
class NetworkSupport
bandwidth remaining percent 5
class Scavenger
bandwidth remaining percent 1
set ip dscp cs1
police rate percent 40
random-detect ??????
class class-default
bandwidth remaining percent 30
set ip dscp default
random-detect ??????
! Configure Parent policy
policy-map TEST_ETH10000
class class-default
random-detect ??????
shape average 9500000
service-policy TEST-MPLS-QoS
! Apply to WAN interface
interface Gig1/1
description connection to MPLS ISP
service-policy output TEST_ETH100000
! Class-maps
class-map match-any Voice
match ip dscp ef
class-map match-any Video
match ip dscp af41 af42
class-map match-any VVSignaling
match ip dscp cs3
match ip dscp af31
class-map match-any NetworkSupport
match ip dscp cs6
match ip dscp cs2
match access-group name NetworkControl
class-map match-any Scavenger
match ip dscp cs1
match access-group name Scavenger-Protocols
thanks,
Dan