HP 6125G HP 6125G & 6125G/XG Blade Switches ACL and QoS Configuration - Page 52

Configuration example, Network requirements, Configuration procedure, Configuring SP+WRR queuing

Get HP 6125G PDF manuals and user guides View all HP 6125G manuals
Add to My Manuals
Save this manual to your list of manuals

Page 52 highlights

Configuration example Network requirements Configure WFQ queues on an interface and assign the scheduling weight 2, 5, 10, 10, and 10 to queue 1, queue 3, queue 4, queue 5, and queue 6, respectively. Configuration procedure # Enter system view. system-view # Configure WFQ queues on GigabitEthernet 1/0/1. [Sysname] interface gigabitethernet 1/0/1 [Sysname-GigabitEthernet1/0/1] qos wfq [Sysname-GigabitEthernet1/0/1] qos wfq 1 weight 2 [Sysname-GigabitEthernet1/0/1] qos wfq 3 weight 5 [Sysname-GigabitEthernet1/0/1] qos wfq 4 weight 10 [Sysname-GigabitEthernet1/0/1] qos wfq 5 weight 10 [Sysname-GigabitEthernet1/0/1] qos wfq 6 weight 10 Configuring SP+WRR queuing Configuration procedure To configure SP + WRR queuing: Step Command 1. Enter system view. system-view 2. Enter interface view. interface interface-type interface-number 3. Enable byte-count or qos wrr [ byte-count | packet-based WRR queuing. weight ] 4. Configure SP queue scheduling. qos wrr queue-id group sp Remarks N/A N/A By default, all ports use the SP queuing. By default, all the queues of a WRR-enabled port use the WRR queue scheduling algorithm. 5. Assign a queue to a WRR group and configure the scheduling weight for the queue. qos wrr queue-id group group-id { weight | byte-count } schedule-value By default, on a WRR-enabled port, byte-count WRR is enabled, and the weights of queues 0 through 7 are 1, 2, 3, 4, 5, 6, 7, and 8. NOTE: To guarantee successful WRR configuration, make sure that the scheduling weight type (byte-count or packet-based) is the same as the WRR queuing type (byte-count or packet-based) when you configure the scheduling weight for a WRR queue. 46

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
46
Configuration example
Network requirements
Configure WFQ queues on an interface and assign the scheduling weight 2, 5, 10, 10, and 10 to queue
1, queue 3, queue 4, queue 5, and queue 6, respectively.
Configuration procedure
# Enter system view.
<Sysname> system-view
# Configure WFQ queues on GigabitEthernet 1/0/1.
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] qos wfq
[Sysname-GigabitEthernet1/0/1] qos wfq 1 weight 2
[Sysname-GigabitEthernet1/0/1] qos wfq 3 weight 5
[Sysname-GigabitEthernet1/0/1] qos wfq 4 weight 10
[Sysname-GigabitEthernet1/0/1] qos wfq 5 weight 10
[Sysname-GigabitEthernet1/0/1] qos wfq 6 weight 10
Configuring SP+WRR queuing
Configuration procedure
To configure SP + WRR queuing:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter interface view.
interface
interface-type
interface-number
N/A
3.
Enable byte-count or
packet-based WRR queuing.
qos wrr
[
byte-count
|
weight
]
By default, all ports use the SP queuing.
4.
Configure SP queue
scheduling.
qos wrr
queue-id
group
sp
By default, all the queues of a WRR-enabled
port use the WRR queue scheduling algorithm.
5.
Assign a queue to a WRR
group and configure the
scheduling weight for the
queue.
qos wrr
queue-id
group
group-id
{
weight
|
byte-count
}
schedule-value
By default, on a WRR-enabled port, byte-count
WRR is enabled, and the weights of queues 0
through 7 are 1, 2, 3, 4, 5, 6, 7, and 8.
NOTE:
To guarantee successful WRR configuration, make sure that the scheduling weight type (byte-count or
packet-based) is the same as the WRR queuing type (byte-count or packet-based) when you configure the
scheduling weight for a WRR queue.