Home > HP > Printer > HP 5500 Ei 5500 Si Switch Series Configuration Guide

HP 5500 Ei 5500 Si Switch Series Configuration Guide

    Download as PDF Print this page Share this page

    Have a look at the manual HP 5500 Ei 5500 Si Switch Series Configuration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1114 HP manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    Page
    of 2513
    							 48 
    SP+WFQ queuing 
    SP+WFQ queuing is similar to SP+WRR queuing. You can assign some queues on a port to the SP 
    scheduling group and the others to the WFQ scheduling group to implement SP + WFQ queue 
    scheduling. The switch schedules packets of qu eues in the WFQ group based on their minimum 
    guaranteed bandwidth settings, then uses SP queuing to schedule the queues in the SP scheduling group, 
    and at last uses WFQ to schedule the queues in  the WFQ scheduling group in a round robin fashion 
    according to their weights  
    Configuring SP queuing 
    Configuration procedure 
    To  c o n fig u re  SP  qu eu i ng :   
    Step Command Remarks 
    1.   Enter system view. 
    system-view N/A 
    2.  Enter interface view or 
    port group view. 
    • Enter interface view: 
    interface  interface-type 
    interface-number 
    •  Enter port group view: 
    port-group manual 
    port-group-name   Use either command. 
    Settings in interface view take effect on 
    the current interface. Settings in port 
    group view take effect on all ports in the 
    port group. 
    3.
      Configure SP queuing.  
    qos sp   The default queuing algorithm on an 
    interface is WRR queuing.
     
    4.  Display SP queuing 
    configuration.  display qos sp interface
     
    [  interface-type interface-number  ] [ | 
    {  begin |  exclude | include  } 
    regular-expression  ]  Optional. 
    Available in any view 
     
    Configuration example 
    Network requirements 
    Configure GigabitEthernet 1/0/1 to use SP queuing. 
    Configuration procedure 
    # Enter system view 
     system-view 
    # Configure GigabitEthernet1/0/1 to use SP queuing. 
    [Sysname] interface gigabitethernet 1/0/1 
    [Sysname-GigabitEthernet1/0/1] qos sp  
    						
    							 49 
    Configuring WRR queuing 
    Configuration procedure 
    To  c o n fig u re  W R R  qu e u i n g :   
    Step Command Remarks 
    1.  Enter system view. 
    system-view N/A 
    2.  Enter interface view or 
    port group view. 
    • Enter interface view: 
    interface  interface-type 
    interface-number 
    •  Enter port group view: 
    port-group manual 
    port-group-name   Use either command. 
    Settings in interface view take effect on 
    the current interface. Settings in port 
    group view take effect on all ports in 
    the port group. 
    3.
      Enable byte-count or 
    packet-based WRR 
    queuing.   qos wrr 
    [ byte-count  | weight  ]  Optional. 
    The default queuing algorithm on an 
    interface is WRR.  
    Only the 5500 EI switch supports the 
    byte-count and 
    weight keywords. 
     
    4.  Configure the scheduling 
    weight for a queue. 
    • For a byte-count WRR queue: 
    qos wrr  queue-id  group 
    group-id  byte-count 
    schedule-value  
    • For a packet-based WRR 
    queue: 
    qos wrr  queue-id  group 
    group-id  weight  schedule-value
     
    Select an approach according to the 
    WRR queuing type.  
    The 5500 SI switch supports only 
    packet-based WRR queue 
    configuration.  
    By default, packet-based WRR is used, 
    and the weights of queues 0 through 7 
    are 1, 2, 3, 4, 5, 9, 13, and 15. 
    5.  Display WRR queuing 
    configuration information 
    on interfaces.   display qos wrr interface
     
    [ interface-type interface-number  ] 
    [ |  { begin |  exclude | include } 
    regular-expression  ]  Optional. 
    Available in any view 
     
     
    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 confi
    gure the
    scheduling weight for a WRR queue.  
     
    Configuration example 
    WRR queuing configuration ex ample on a 5500 EI switch 
    1. Network requirements 
    {  Configure byte-count WRR on GigabitEthernet 1/0/1.  
    { Assign all queues to the WRR group, with the weights of 1, 2, 4, 6, 8, 10, 12, and 14.   
    						
    							 50 
    2.
     
    Configuration procedures 
    # Enter system view.  
     system-view 
    # Configure WRR queuing on port GigabitEthernet 1/0/1.  
    [Sysname] interface GigabitEthernet 1/0/1 
    [Sysname-GigabitEthernet1/0/1] qos wrr byte-count 
    [Sysname-GigabitEthernet1/0/1] qos wrr 0 group 1 byte-count 1 
    [Sysname-GigabitEthernet1/0/1] qos wrr 1 group 1 byte-count 2 
    [Sysname-GigabitEthernet1/0/1] qos wrr 2 group 1 byte-count 4 
    [Sysname-GigabitEthernet1/0/1] qos wrr 3 group 1 byte-count 6 
    [Sysname-GigabitEthernet1/0/1] qos wrr 4 group 1 byte-count 8 
    [Sysname-GigabitEthernet1/0/1] qos wrr 5 group 1 byte-count 10 
    [Sysname-GigabitEthernet1/0/1] qos wrr 6 group 1 byte-count 12 
    [Sysname-GigabitEthernet1/0/1] qos wrr 7 group 1 byte-count 14 
    WRR queuing configuration example on a 5500 SI switch 
    1. Network requirements 
    {  Configure WRR queuing on port GigabitEthernet 1/0/1.  
    { Assign all queues to the WRR group, with the weights of 1, 2, 4, 6, 8, 10, 12, and 14.  
    2. Configuration procedures 
    # Enter system view.  
     system-view 
    # Configure WRR queuing on port GigabitEthernet 1/0/1.  
    [Sysname] interface GigabitEthernet 1/0/1 
    [Sysname-GigabitEthernet1/0/1] qos wrr 
    [Sysname-GigabitEthernet1/0/1] qos wrr 0 group 1 weight 1 
    [Sysname-GigabitEthernet1/0/1] qos wrr 1 group 1 weight 2 
    [Sysname-GigabitEthernet1/0/1] qos wrr 2 group 1 weight 4 
    [Sysname-GigabitEthernet1/0/1] qos wrr 3 group 1 weight 6 
    [Sysname-GigabitEthernet1/0/1] qos wrr 4 group 1 weight 8 
    [Sysname-GigabitEthernet1/0/1] qos wrr 5 group 1 weight 10 
    [Sysname-GigabitEthernet1/0/1] qos wrr 6 group 1 weight 12 
    [Sysname-GigabitEthernet1/0/1] qos wrr 7 group 1 weight 14 
    Configuring WFQ queuing 
    Configuration procedure 
    To  c o n fig u re  W F Q  qu eu i ng :   
    Step Command Remarks 
    1.  Enter system view. 
    system-view N/A  
    						
    							 51 
    Step Command Remarks 
    2.  Enter interface view or 
    port group view. 
    • Enter interface view: 
    interface  interface-type 
    interface-number 
    •  Enter port group view: 
    port-group manual  port-group-name
     
    Use either command. 
    Settings in interface view take 
    effect on the current interface. 
    Settings in port group view take 
    effect on all ports in the port group.
     
    3.  Enable byte-count or 
    packet-based WFQ 
    queuing.   qos wfq [ byte-count
     | weight  ]  The default queuing algorithm on 
    an interface is WRR. 
     
    4.  Configure the 
    scheduling weight for a 
    queue. 
    • For a byte -count WFQ queue: 
    qos wfq  queue-id group  group-id  
    byte-count  schedule-value  
    • For a packet-based WFQ queue: 
    qos wfq  queue-id group  group-id  
    weight  schedule-value   Select a command according to 
    the WFQ type (byte-count or 
    packet-based) you have enabled. 
     
    If you have enabled WFQ on the 
    port, byte-count WRR applies by 
    default, and the default scheduling 
    weight is 1 for each queue.  
    5.
      Configure the minimum 
    guaranteed bandwidth 
    for a WFQ queue.  qos bandwidth queue queue-id
     min 
    bandwidth-value   Optional. 
    64 kbps by default for each queue. 
    6.
      Display WFQ queuing 
    configuration.  display qos wfq interface
     [ interface-type 
    interface-number  ] [ | { begin  | exclude  | 
    include  } regular-expression ]  Optional. 
    Available in any view 
     
     
    NOTE: 
    To guarantee successful WFQ configur ation, make sure that the scheduling weight type (byte-count or 
    packet-based) is the same as the WFQ queuing ty pe (byte-count or packet-based) when you confi
    gure the
    scheduling weight for a WFQ queue.  
     
    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  
    						
    							 52 
    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 or port 
    group view. 
    • Enter interface view: 
    interface 
    interface-type  
    interface-number 
    •  Enter port group 
    view: 
    port-group manual 
    port-group-name  Use either command. 
    Settings in interface view take effect on the 
    current interface. Settings in port group view 
    take effect on all ports in the port group. 
    3.
      Enable byte-count or 
    packet-based WRR queuing.  qos wrr 
    [ byte-count  | 
    weight ]   Optional. 
    By default, all ports use WRR queuing.  
    Only the 5500 EI switch supports the 
    byte-count and 
    weight keywords. 
     
    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, 
    packet-based WRR is enabled, and the 
    weights of queues 0 through 7 are 1, 2, 3, 4, 
    5, 9, 13, and 15. 
    The 5500 SI switch supports only the 
    weight 
    keyword.  
     
      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 confi
    gure the
    scheduling weight for a WRR queue.  
     
    Configuration example 
    Network requirements 
    •   Configure SP+WRR queue scheduling algorithm on GigabitEthernet 1/0/1, and use packet-based 
    WRR.  
    •   Configure queue 0, queue 1, queue 2, and queue 3 on GigabitEthernet 1/0/1 to be in SP queue 
    scheduling group.  
    •   Configure queue 4, queue 5, queue 6, and queue 7 on GigabitEthernet 1/0/1 to use WRR 
    queuing, with the weight 2, 4, 6, and 8, respectively.   
    						
    							 53 
    Configuration procedure 
    # Enter system view.  
     system-view 
    # Enable the SP+WRR queue scheduling algorithm on GigabitEthernet1/0/1.  
    [Sysname] interface GigabitEthernet 1/0/1 
    [Sysname-GigabitEthernet1/0/1] qos wrr weight 
    [Sysname-GigabitEthernet1/0/1] qos wrr 0 group sp 
    [Sysname-GigabitEthernet1/0/1] qos wrr 1 group sp 
    [Sysname-GigabitEthernet1/0/1] qos wrr 2 group sp 
    [Sysname-GigabitEthernet1/0/1] qos wrr 3 group sp 
    [Sysname-GigabitEthernet1/0/1] qos wrr 4 group 1 weight 2 
    [Sysname-GigabitEthernet1/0/1] qos wrr 5 group 1 weight 4 
    [Sysname-GigabitEthernet1/0/1] qos wrr 6 group 1 weight 6 
    [Sysname-GigabitEthernet1/0/1] qos wrr 7 group 1 weight 8 
    Configuring SP+WFQ queuing 
    Configuration procedure 
    To  c o n fig u re  SP  +  W F Q  qu eu i n g :  
    Step Command Remarks 
    1.  Enter system view. 
    system-view  N/A 
    2.  Enter interface view or port 
    group view. 
    • Enter interface view: 
    interface  interface-type  
    interface-number 
    •  Enter port group view: 
    port-group manual 
    port-group-name  Use either command. 
    Settings in interface view take effect on 
    the current interface. Settings in port 
    group view take effect on all ports in the 
    port group. 
    3.
      Enable byte-count or 
    packet-based WFQ 
    queuing.  qos wfq 
    [ byte-count  | weight ]
     By default, WRR queuing is enabled. 
     
    4.  Configure SP queue 
    scheduling.  qos wfq queue-id 
    group sp  By default, all the queues of a 
    WFQ-enabled port are in the WFQ 
    group.  
    5.
      Configure the scheduling 
    weight for a queue.  qos wfq queue-id
     group  
    group-id  { weight  | 
    byte-count  } schedule-value  By default, the scheduling weight is 1 for 
    each queue of a WFQ-enabled port. 
    6.
      Configure the minimum 
    guaranteed bandwidth for a 
    queue.  qos bandwidth queue 
    queue-id 
    min  bandwidth-value  Optional. 
    64 kbps for each queue by default.  
     
     
    NOTE: 
    To guarantee successful WFQ configur ation, make sure that the scheduling weight type (byte-count or 
    packet-based) is the same as the WFQ queuing ty pe (byte-count or packet-based) when you confi
    gure the
    scheduling weight for a WFQ queue.  
      
    						
    							 54 
    Configuration example 
    Network requirements 
    •  Configure SP+WFQ queuing on GigabitEthernet  1/0/1, and use packet-based WFQ scheduling 
    weights.  
    •   Configure queue 0, queue 1, queue 2, and queue 3 on GigabitEthernet 1/0/1 to be in SP queue 
    scheduling group.  
    •   Configure queue 4, queue 5, queue 6, and queue 7 on GigabitEthernet 1/0/1 to use WFQ 
    queuing, with the weight 2, 4, 6, and 8 and the minimum guaranteed bandwidth 128 kbps.  
    Configuration procedure 
    # Enter system view.  
     system-view 
    # Enable the SP+WFQ queue scheduling algorithm on GigabitEthernet1/0/1.  
    [Sysname] interface GigabitEthernet 1/0/1 
    [Sysname-GigabitEthernet1/0/1] qos wfq weight 
    [Sysname-GigabitEthernet1/0/1] qos wfq 0 group sp 
    [Sysname-GigabitEthernet1/0/1] qos wfq 1 group sp 
    [Sysname-GigabitEthernet1/0/1] qos wfq 2 group sp 
    [Sysname-GigabitEthernet1/0/1] qos wfq 3 group sp 
    [Sysname-GigabitEthernet1/0/1] qos wfq 4 group 1 weight 2 
    [Sysname-GigabitEthernet1/0/1] qos bandwidth queue 4 min 128 
    [Sysname-GigabitEthernet1/0/1] qos wfq 5 group 1 weight 4 
    [Sysname-GigabitEthernet1/0/1] qos bandwidth queue 5 min 128 
    [Sysname-GigabitEthernet1/0/1] qos wfq 6 group 1 weight 6 
    [Sysname-GigabitEthernet1/0/1] qos bandwidth queue 6 min 128 
    [Sysname-GigabitEthernet1/0/1] qos wfq 7 group 1 weight 8 
    [Sysname-GigabitEthernet1/0/1] qos bandwidth queue 7 min 128 
      
    						
    							 55 
    Configuring congestion avoidance (available 
    only on the 5500 EI) 
    Both bridge mode (Layer 2) and route mode (Layer 3) Ethernet ports support the congestion avoidance 
    function. The term  interface i n thi s  chapter  c ol le ctively refers  to  these  t ypes  of  por ts. You  c an use  the  port 
    link-mode  command to set an Ethernet port to operate in bridge or route mode (see  Layer 2—LAN 
    Switching Configuration Guide ). 
    Overview 
    Avoiding congestion before it occurs is a proactive approach to improving network performance. As a 
    flow control mechanism, congestion avoidance active ly monitors network resources (such as queues and 
    memory buffers), and drops packets when conges tion is expected to occur or deteriorate. 
    Co mp a re d  wi t h  e n d - to - e n d  fl ow  c o nt ro l,  t h i s  fl ow  c o ntro l  m e ch a n i s m  c ont ro l s  t h e  l o a d  of  m o re  fl ows  i n  a  
    device. When dropping packets from a source end, it  cooperates with the flow control mechanism (such 
    as TCP flow control) at the source end to regulate the network traffic size. The combination of the local 
    packet drop policy and the source-end flow contro l mechanism helps maximize throughput and network 
    use efficiency and minimize packet loss and delay. 
    Tail drop 
    Congestion management techniques drop all packets that are arriving at a full queue. This tail drop 
    mechanism results in global TCP synchronization. If  packets from multiple TCP connections are dropped, 
    these TCP connections go into the state of congestion  avoidance and slow start to reduce traffic, but 
    traffic peak occurs later. Consequently, the network traffic jitters all the time. 
    RED and WRED 
    You can use random early detection (RED) or weighted random early detection (WRED) to avoid global 
    TC P  synchronization. 
    Both RED and WRED avoid global TCP synchronization by randomly dropping packets. When the 
    sending rates of some TCP sessions slow down af ter their packets are dropped, other TCP sessions 
    remain at high sending rates. Link bandwidth is efficiently used, because TCP sessions at high sending 
    rates always exist. 
    The RED or WRED algorithm sets an upper threshold  and lower threshold for each queue, and processes 
    the packets in a queue as follows: 
    •   When the queue size is shorter than the lower threshold, no packet is dropped; 
    •   When the queue size reaches the upper thresh old, all subsequent packets are dropped; 
    •   When the queue size is between the lower threshol d and the upper threshold, the received packets 
    are dropped at random. The drop probability in a queue increases along with the queue size under 
    the maximum drop probability. 
      
    						
    							 56 
     NOTE: 
    The Switch Series does not support the upper threshold configuration.  
     
    Introduction to WRED configuration 
    On the 5500 EI Switch Series, WRED is implemen ted with WRED tables. WRED tables are created 
    globally in system view and then applied to interfaces. 
    Before configuring WRED, determine the following parameters: 
    •   Lower threshold —When the average queue length is below the lower threshold, no packet is 
    dropped. When the average queue length exceeds the lower threshold, the switch drops packets at 
    the user-configured drop probability.  
    •   Drop precedence —A parameter used in packet drop. Value 0 represents green packets, 1 
    represents yellow packets, and 2 represents red pac kets. Red packets are preferentially dropped.  
    •   Denominator —Denominator for drop probability calc ulation. A greater denominator means a 
    lower drop probability.  Tabl e  4 sho
    ws the denominator and the dr op probability dependencies.  
    Table 4  Denominator and the drop probability dependencies  
    Denominator   Dro
    p probability 
    0 100% 
    1 to 8  1/8 
    9 to 16  1/16 
    17 to 32  1/32 
    33 to 64 1/64 
    65 to 128  1/128 
     
    In a WRED table, drop parameters are configured on a per queue basis because WRED regulates 
    packets on a per queue basis.  
    A WRED table can be applied to multiple interfaces. For a WRED table already applied to an interface, 
    you can modify the values of the WRED table, but you cannot remove the WRED table. 
    Configuration procedure 
    To configure and apply a queue-based WRED table:  
    Step Command Remarks 
    1.   Enter system view. 
    system-view N/A 
    2.  Create a WRED table 
    and enter its view.  qos wred queue table 
    table-name N/A 
    3.  Configure the other 
    WRED parameters.  queue 
    queue-value  [ drop-level  
    drop-level  ] low-limit  low-limit  
    [ discard-probability  discard-prob  ] Optional. 
    By default, 
    low-limit is 10, and 
    discard-prob  is 10. 
      
    						
    							 57 
    Step Command Remarks 
    4.  Enter interface view or 
    port group view. 
    • Enter interface view: 
    interface  interface-type  
    interface-number 
    •  Enter port group view: 
    port-group manual  port-group-name
     
    Use either command. 
    Settings in interface view take 
    effect on the current interface. 
    Settings in port group view take 
    effect on all ports in the port group.
     
    5.  Apply the WRED table 
    to the interface or port 
    group.   qos wred apply 
    table-name N/A
     
     
    Configuration examples 
    Apply a WRED table to Layer 2 port GigabitEthernet 1/0/1. Set the  low-limit to 30 and  discard-prob  to 
    20 for queue 1.  
    # Enter system view.  
     system-view 
    # Create a queue-based WRED table named  queue-table1, and configure the drop parameters.  
    [Sysname] qos wred queue table queue-table1 
    [Sysname-wred-table-queue-table1] queue 1 low-limit 30 discard-probabili\
    ty 20 
    [Sysname-wred-table-queue-table1] quit 
    # Enter port view.  
    [Sysname] interface gigabitethernet 1/0/1 
    # Apply the WRED table to GigabitEthernet 1/0/1.  
    [Sysname-GigabitEthernet1/0/1] qos wred apply queue-table1  
    Displaying and maintaining WRED 
     
    Task Command Remarks 
    Display WRED configuration 
    information on the interface or all 
    interfaces.
      display qos wred interface
     [ interface-type 
    interface-number  ] [ | { begin  | exclude  | 
    include  } regular-expression ]  Available in any view 
    Display configuration information 
    about a WRED table or all WRED 
    tables.
      display qos wred table
     [ table-name ] [ | 
    {  begin |  exclude | include  } 
    regular-expression  ]  Available in any view
     
     
      
    						
    All HP manuals Comments (0)

    Related Manuals for HP 5500 Ei 5500 Si Switch Series Configuration Guide