Manual Chapter : Common elements for traffic groups

Applies To:

Show Versions Show Versions

BIG-IP LTM

  • 15.0.0
Manual Chapter

Common elements for traffic groups

  1. On the Main tab, click
    Device Management
    Traffic Groups
    .
  2. In the Display Options area of the screen, verify that the
    Select All
    is selected.
  3. In the
    MAC Masquerade Address
    field, type a MAC masquerade address.
    When you specify a MAC masquerade address, you reduce the risk of dropped connections when failover occurs. This setting is optional.
  4. In the
    MAC Masquerade Address
    field, type a MAC masquerade address.
    For this setting, you should use an industry-standard method for creating a locally-administered MAC address. Each traffic group needs a MAC masquerade address to reduce the risk of dropped connections when failover happens.
  5. On the lower half of the screen, verify that the list shows the default floating traffic group (
    traffic-group-1
    ) for the local device.
  6. In the Name column, locate the name of the traffic group that you want to run on the peer device.
  7. In the Name column, view the names of the traffic groups on the local device.
  8. To the left of the traffic group name, select the check box.
  9. Select the check box to the left of the traffic group name.
    If the check box is unavailable, the traffic group is not active on the device to which you are currently logged in. Perform this task on the device on which the traffic group is active.
  10. Click
    Force to Standby
    .
    This displays target device options.
  11. On the Traffic Groups screen, click
    Create
    .
  12. In the
    Name
    field, type a name for the new traffic group.
  13. In the
    Name
    field, type a name for the new traffic group.
    An example of a traffic group name is
    traffic-group-2
    .
  14. In the
    Name
    field, type a name for the traffic group.
    For example, you can name the traffic group
    tg-customerA
    .
  15. In the
    Name
    field, type the name
    traffic-group-3
    for the new traffic group.
  16. In the
    Description
    field, type a description for the new traffic group.
    For example, you can type
    This traffic group manages failover for Customer B traffic.
  17. In the
    Description
    field, type a description for the new traffic group.
    For example, you can type
    This traffic group contains the floating IP addresses that are on BIGIP_B.
  18. Type a name for the new traffic group.
  19. Type the name
    traffic-group-2
    for the new traffic group.
  20. Type a description of the new traffic group.
  21. Click
    Next
    .
  22. Select a remote device as the default device for the new traffic group, and optionally specify a MAC masquerade address.
    When you specify a MAC masquerade address, you reduce the risk of dropped connections when failover occurs.
  23. From the
    Failover Method
    list, select
    HA Order
    .
  24. In the
    HA Load Factor
    field, specify a value that represents the application load for this traffic group relative to other active traffic groups on the local device.
    If you configure this setting, you must configure the setting on every traffic group in the device group.
  25. If you configured the
    Failover Methods
    setting with the option of
    Failover using Preferred Device List and then Load Aware
    , then in the
    HA Load Factor
    field, specify a value that represents the application load for this traffic group relative to other active traffic groups on the local device. Otherwise, skip this step.
    If you configure this setting, you must configure the setting on every traffic group in the device group.
  26. If you configured the
    Failover Methods
    setting with a value of
    Failover using Preferred Device List and then Load Aware
    , then configure the following settings. Otherwise, skip this step.
    1. Select or clear the check box for the
      Auto Failback
      option.
    2. If
      Auto Failback
      is selected, then in the
      Auto Failback Timeout
      field, type the number of seconds that you want the system to wait before failing back to the specified device. The range in seconds is from
      0
      to
      300
      . The default is
      60
      . A value of
      40
      to
      60
      seconds allows for state mirroring information to be re-mirrored for traffic groups.
    3. For the
      Failover Order
      setting, in the
      Load Aware
      box, select a device name and, using the Move button, move the name to the
      Preferred Order
      box. Repeat for each device that you want to include in the ordered list.
      This setting is optional. Only devices that are members of the relevant Sync-Failover device group are available for inclusion in the ordered list. If you have enabled the auto-failback feature on the traffic group, ensure that the first device in the ordered list is the device to which you want this traffic group to fail back to when that first device becomes available.
      If auto-failback is enabled and the first device in the
      Preferred Order
      list is unavailable, no auto-failback occurs and the traffic group continues to run on the current device. Also, if none of the devices in the list is currently available or there are no devices in the list when failover occurs, BIG-IP system performs load-aware failover instead, using the
      HA Load Factor
      setting.
    4. In the
      HA Load Factor
      field, specify a value that represents the application load for this traffic group relative to other active traffic groups on the local device.
      The BIG-IP system uses this value whenever it performs load-aware failover.
      If you configure this setting, you must configure the setting on every traffic group in the device group.
  27. If you configured the
    Failover Method
    setting with a value of
    Failover to Device with Best HA Score
    , then from the
    HA Groups
    list, select the HA group that you want to associate with this traffic group.
  28. From the
    Failover Method
    list, select a failover method:
    • Choose
      Failover to Device With Best HA Score
      when you want the BIG-IP system to choose the next-active device based on an HA health score for the device. You can only choose this option when you have configured the
      HA Group
      setting to assign an existing HA group to this traffic group.
    • Choose
      Failover using Preferred Device List and then Load Aware
      when you want the BIG-IP system to choose the next-active device based on either an ordered list of devices or relative traffic group load.
  29. From the
    Failover Method
    list, select
    HA Group
    .
  30. For the
    Failover Method
    setting, choose
    Failover using Preferred Device Order and then Load Aware
    .
  31. From the
    Failover Method
    list, choose
    Failover using Preferred Device Order and then Load Aware
    .
    This displays the
    HA Load Factor
    setting.
  32. From the
    HA Group
    list, select an HA group.
  33. From the
    HA Group
    list, select the HA group named
    ha_group_deviceA_tg1
    .
    Because each instance of this traffic group has its own HA group, the BIG-IP system never syncs this value to the other devices in the device group.
  34. From the
    HA Group
    list, select the HA group named
    ha_group_deviceB_tg1
    .
    Because each instance of this traffic group has its own HA group, the BIG-IP system never syncs this value to the other devices in the device group.
  35. From the
    HA Group
    list, select the HA group named
    ha_group_deviceA_tg2
    .
    Because each instance of this traffic group has its own HA group, the BIG-IP system never syncs this value to the other devices in the device group.
  36. From the
    HA Group
    list, select the HA group named
    ha_group_deviceB_tg2
    .
    Because each instance of this traffic group has its own HA group, the BIG-IP system never syncs this value to the other devices in the device group.
  37. Verify that the
    Enable
    check box is selected.
  38. Optionally, in the
    Active Bonus
    field, specify an integer the represents the amount by which you want the system to increase the overall score of the active device.
    The purpose of the active bonus is to boost an HA score to prevent frequent failover when the availability of trunks, pools, or clusters changes frequently (due to events such as link flapping).
  39. If you want pool availability to factor into the HA score calculation, then for the
    Pools
    setting, in the
    Available
    box, click a pool name and use the Move button to move the pool name to the
    Selected
    box.
    This populates the table that appears along the bottom of the screen with information about the pool.
  40. If you want trunk availability to factor into the HA score calculation, then for the
    Trunks
    setting, in the
    Available
    box, click a trunk name and use the Move button to move the trunk name to the
    Selected
    box.
    This populates the table that appears along the bottom of the screen with information about the trunk.
  41. If you have a VIPRION platform and want cluster availability to factor into the HA score calculation, then for the
    Clusters
    setting (VIPRION platforms only), in the
    Available
    box, click a cluster name and use the Move button to move the cluster name to the
    Selected
    box.
  42. In the table displayed along the bottom of the screen, for the
    Threshold
    setting, for each pool, trunk, or cluster in the HA group, optionally specify an integer for a threshold value.
  43. For the
    Weight
    setting, for each pool, trunk, or cluster in the HA group, specify an integer for the weight. The allowed weight for an HA group object ranges from
    10
    through
    100
    .
    This value is required.
  44. Select or clear the check box
    Always Failback to First Device if it is Available
    :
    • Select the check box to cause the traffic group, after failover, to fail back to the first device in the traffic group's ordered list when that device (and only that device) is available. If that device is unavailable, no failback occurs and the traffic group continues to run on the current device.
    • Clear the check box to cause the traffic group, after failover, to remain active on its current device until failover occurs again.
  45. In the General Properties and Failover Settings area of the screen, select or clear the
    Auto Failback
    option.
    • Select
      causes the traffic group to be active on the first device in the traffic group's ordered list, that device is available.
    • Clear
      causes the traffic group to remain active on its current device until failover occurs again.
  46. If auto-failback is enabled, in the
    Auto Failback Timeout
    field, type the number of seconds that you want the system to wait before failing back to the specified device. The range is from 0 to 300 seconds. The default is
    60
    . A value of
    40
    to
    60
    allows for state mirroring information to be re-mirrored for traffic groups.
  47. Make sure that the displayed traffic group settings are correct.
  48. Click
    Finished
    .
  49. Click
    Update
    .
  50. Repeat this task for each traffic group that you want to create.
  51. In the Failover Status area of the screen, view the state of all traffic groups on the device.
  52. Display any screen of the BIG-IP Configuration utility.
  53. In the upper left corner of the screen, view the failover state of the device.
  54. In the Name column, click the name of the traffic group for which you want to view the associated objects.
    This displays a list of all failover objects for the traffic group.
  55. In the Name column, click the name of a traffic group on the local device.
    This displays the properties of the traffic group.
  56. In the Name column, click
    traffic-group-1
    .
    This displays the properties of the traffic group.
  57. In the Name column, click
    traffic-group-2
    .
    This displays the properties of the traffic group.
  58. In the Name column, click the name of a traffic group.
    This displays the properties of the traffic group.
  59. Choose one of these actions:
    • If the device group has two members only, click
      Force to Standby
      . This displays the list of traffic groups for the device group and causes the local device to appear in the Next Active Device column.
    • If the device group has more than two members, then from the
      Target Device
      list, select a value and click
      Force to Standby
      .
  60. Choose one of these actions:
    • If the device group has two members only, click
      Force to Standby
      .
    • If the device group has more than two members, then from the
      Target Device
      list, select a value and click
      Force to Standby
      .
  61. For the
    Failover Order
    setting, in the
    Load-Aware
    box, select a device name and using the Move button, move the device name to the
    Preferred Order
    box. Repeat for each device that you want to include in the ordered list.
    This setting is optional. Only devices that are members of the relevant Sync-Failover device group are available for inclusion in the ordered list. If you have enabled the auto-failback feature on the traffic group, make sure that the first device in the ordered list is the device to which you want this traffic group to fail back to when that first device becomes available.
    If none of the devices in the
    Preferred Order
    list is currently available when failover occurs, the BIG-IP system uses load-aware failover instead.
  62. For the
    Failover Order
    setting, in the
    Available
    box, select a device name and using the Move button, move the device name to the
    Enabled
    box. Repeat for each device that you want to include in the ordered list.
    If you enabled the auto-failback feature on the traffic group, make sure that the first device in the ordered list is the device to which you want this traffic group to fail back to when that first device becomes available.
    If auto-failback is enabled and the first device in the
    Failover Order
    list is unavailable, no auto-failback occurs and the traffic group continues to run on the current device. Also, if none of the devices in the
    Failover Order
    list is currently available when failover occurs, the BIG-IP system ignores the
    Failover Order
    setting and performs load-aware failover instead, using the
    HA Load Factor
    setting.
  63. For the
    Failover Order
    setting, in the
    Available
    box, select the name of the device on which you want this traffic group to be active, and then move it to the
    Enabled
    box. Repeat for each device that you want to be the next-active device if failover occurs.
    You can put only members of the device group on the ordered list. You cannot put devices from the local trust domain on the list if they are not in the device group.
    In our sample device group, where we configured each traffic group to be active on a different device, the first device in
    traffic-group-1
    's
    Failover Order
    list is
    BIGIP_A
    . Similarly, the first device in the
    traffic-group-2
    list is
    BIGIP_B
    , and the first device in the
    traffic-group-3
    list is
    BIGIP_C
    .
  64. For the
    Failover Order
    setting, in the
    Available
    box, select the peer guest name, and using the Move button, move the name to the
    Enabled
    box.
    This setting is optional. Only devices that are members of the relevant Sync-Failover device group are available for inclusion in the ordered list.
  65. From the
    Failover Methods
    list, select
    Load Aware
    .