In WebSphere DataPower XC10 Appliance, you can experience low performance when you do not add an aggregate interface

Technote (troubleshooting)


Problem(Abstract)

Outbound replication traffic from WebSphere DataPower XC10 Appliance is sent on a single interface, instead of being distributed across all available interfaces. This problem occurs when the available interfaces are on the same subnet.

Symptom

You can experience low performance due to high volumes of traffic on an overloaded interface.


Cause

WebSphere DataPower XC10 Appliance uses the lowest indexed interface for outbound replica traffic.

Resolving the problem

To resolve this problem, complete the following steps:

  1. Aggregate the interfaces into a single, aggregate interface. After you aggregate the interfaces, the appliance implementation selects the outbound interface based on the lowest associated index.

    Using the command-line interface to create, edit, or remove aggregate interfaces is the preferred approach. For each operation, you must log in to the appliance first. After you complete an operation, run the clear-all command and restart your appliance.
    Aggregate the interfaces

      Console> create aggregate-interface myAgg
      Console aggregate-interface:myAgg> member eth3 eth4
      Console aggregate-interface:myAgg> ip
      CWZBR02205I: Entering "ip" mode
      Console aggregate-interface:myAgg ip> address 10.5.5.5/24
      Console aggregate-interface:myAgg ip> exit
      Console aggregate-interface:myAgg> primary-member eth3
      Console aggregate-interface:myAgg> aggregation-policy balance-tlb
      Console aggregate-interface:myAgg> show
      aggregate-interface myAgg:
      name "myAgg"
      AdminState "Enabled"
      use-arp "true"
      mtu "1500"
      ip
        use-dhcp "false"
        address "10.5.5.5/24"
        use-slaac "false"
        dad-transmits "1"
        dad-retransmit-timer "1000"
      end ip
      aggregation-policy "balance-tlb"
      lacp-selection-logic "stable"
      transmit-hash-policy "layer2"
      member "eth3" "eth4"
      primary-member "eth3"
    Edit the aggregate interface Console aggregate-interface:myAgg> aggregation-policy lacp
    Console aggregate-interface:myAgg> transmit-hash-policy layer3+4
    Console aggregate-interface:myAgg> exit
    Console> show aggregate-interface myAgg
    aggregate-interface myAgg: [Up]

    name "myAgg"
    AdminState "Enabled"
    use-arp "true"
    mtu "1500"
    ip
      use-dhcp "false"
      address "10.5.5.5/24"
      use-slaac "false"
      dad-transmits "1"
      dad-retransmit-timer "1000"
    end ip
    aggregation-policy "lacp"
    lacp-selection-logic "stable"
    transmit-hash-policy "layer3+4"
    member "eth3" "eth4"
    primary-member "eth3"
    Remove the aggregate interface Console> delete aggregate-interface myAgg
    Console> list aggregate-interface
    Console aggregate-interface:myAgg> exit
  2. Specify layer 3+4 for the Link Aggregation Control Protocol (LACP) hash policy.
  3. Interface indexes are updated when interface settings are modified. To force outbound replication traffic over a specific interface, either over an aggregate or individual interface, make artificial changes to the interfaces until the preferred interface has the lowest index.
    Note
    : The management port will also be used for outbound traffic if it is on the same subnetwork as the other interfaces, and it is the lowest indexed interface.
  4. (Optional) Verify that the preferred index is selected.
    From the command line for the appliance, run show status netif. Alternatively, run list ethernet-interface, and status ethernet-interface [interface_name] for each listed interface name. For aggregate interfaces, run list aggregate-interface and then status ethernet-interface [interface_name] for each aggregate interface name.

    In the results, the index for each interface is displayed. In the following example results, the specified index is highlighted in bold text:

    Console> show status netif
     eth0:        offline
     OpState:[Down]
     generic MTU:1500 carrier:false flags: BROADCAST MULTICAST  index:8
     ethernet Link:off MAC: 00:1a:64:88:a5:85 autoneg:on duplex:Full
      port:TP speed:1000Mbps
     statistics collisions:0 multicast:0 rx_bytes:0 rx_compressed:0
      rx_crc_errors:0 rx_dropped:0 rx_errors:0 rx_fifo_errors:0
      rx_frame_errors:0 rx_length_errors:0 rx_missed_errors:0
      rx_over_errors:0 rx_packets:0 tx_aborted_errors:0 tx_bytes:0
      tx_carrier_errors:0 tx_compressed:0 tx_dropped:0 tx_errors:0
      tx_fifo_errors:0 tx_heartbeat_errors:0 tx_packets:0
      tx_window_errors:0

Related information

Adding an aggregate interface in the WebSphere DataPowe

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere DataPower XC10 Appliance

Software version:

2.1, 2.1.0.1, 2.1.0.2

Operating system(s):

Firmware

Reference #:

1622298

Modified date:

2013-08-16

Translate my page

Machine Translation

Content navigation