Foundry NetIron M2404C and M2404F Metro Access Switches
Configuring HQoS (Rev.03)
Configuration
© 2008 Foundry Networks, Inc.
Page 41 of 98
Each created queue will have WRED profile applied to it. Either the user configured WRED
profile or, in case that the user does not configure WRED profile, the default policy will be
applied.
The user will not be able to delete or configure profiles 1, 33, 57.
Scheduling Policy Default Configuration
Ingress Scheduling Default Policy (Scheduling Policy – InSDef)
NOTE
The default ingress scheduling policy and service ingress policy must be applied
manually on the service ingress.
Table 3
shows the default Ingress Scheduling Policy configuration.
Table 3: Ingress Scheduling Policy Default Configuration
Default Value
Parameter
Priority
Parent
WFQ Profile
L1 low priority scheduler is enabled – Low0
low
-
0
L2 low priority scheduler is enabled – Low0
low
Low0
0
L1 high priority scheduler is enabled – High1
high
-
0
L2 high priority scheduler is enabled – High8
high
High1
0
Egress Scheduling Default Policy (Scheduling Policy – EgSDef)
Table 4
shows the default Egress Scheduling Policy configuration.
Table 4: Egress Scheduling Policy Default Configuration
Default Value
Parameter
Priority
Parent
WFQ Profile
L1 low priority scheduler is enabled – DefEg0
low
-
0
L2 low priority scheduler is enabled – DefEL2
low
DefEg0
0
L1 high priority scheduler is enabled – DefEg1
high
-
0
L2 high priority scheduler is enabled – DefEg8
high
DefEg1
0
The user can configure the default schedulers, but they cannot be deleted.