Manual Chapter : Common elements for node tasks

Applies To:

Show Versions Show Versions

BIG-IP AAM

  • 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0

BIG-IP APM

  • 17.1.1, 17.1.0, 17.0.0, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0

BIG-IP Analytics

  • 17.1.1, 17.1.0, 17.0.0, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0

BIG-IP Link Controller

  • 17.1.1, 17.1.0, 17.0.0, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0

BIG-IP LTM

  • 17.1.1, 17.1.0, 17.0.0, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0

BIG-IP PEM

  • 17.1.1, 17.1.0, 17.0.0, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0

BIG-IP AFM

  • 17.1.1, 17.1.0, 17.0.0, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0

BIG-IP DNS

  • 17.1.1, 17.1.0, 17.0.0, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0

BIG-IP ASM

  • 17.1.1, 17.1.0, 17.0.0, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0
Manual Chapter

Common elements for node tasks

Local traffic pools use nodes as resources for load balancing. Nodes represent the actual server resources that host the applications.
  1. On the Main tab, click
    Local Traffic
    Nodes
    .
    The Node List screen opens.
  2. On the Main tab, expand
    Local Traffic
    , and click
    Nodes
    .
    The Node List screen opens.
  3. In the Name column, click a node name.
  4. In the Name column, click a node name.
    This displays the properties of the node.
  5. In the Name column, locate the node you want to enable.
  6. In the Name column, locate the node you want to disable.
  7. Click the
    Enable
    button.
  8. Click the
    Disable
    button.
  9. Select the check box to the left of the node name.
  10. For the
    State
    property, click
    Forced Offline (Only active connections allowed)
    .
  11. Click the
    Create
    button.
    The New Node screen opens.
  12. In the
    Address
    field, type the IP address of the alert server.
  13. In the
    Address
    field, type the IP address of the web application server.
  14. In the
    Address
    field, select
    Address
    and type the IP address of the node.
  15. For the
    Address
    setting, select either
    Address
    or
    FQDN
    , and then type either the IP address or the fully-qualified domain name of the node.
  16. Configure all other settings as needed or retain the default values.
  17. In the Configuration area of the screen, configure the settings as needed or retain the default values.
  18. For the
    Address
    setting, select
    FQDN
    , and then type the host name in the field.
  19. For the
    Address
    setting, select
    FQDN
    , and then type the host name in the field.
  20. In the
    Name
    field, type a descriptive label for the node.
    Names are case-sensitive.
  21. In the Configuration area, from the
    Health Monitors
    list, select the way that you want the system to apply monitors to the node.
    The default setting is
    Node Default
    .
    Node Default
    Specifies that the system uses the defined default monitors for nodes. The default monitors are defined on the Default Monitors screen of the BIG-IP Configuration utility.
    Node Specific
    Specifies that the system monitors this node with the monitors that you configure in the
    Select Monitors
    setting.
    When you select the
    Node Specific
    option, the screen refreshes to display the
    Select Monitors
    setting.
    None
    Specifies that the system does not monitor this node.
  22. You can move and add monitors to the appropriate list as needed.
    Active
    Specifies the health monitors that the system currently uses to monitor this node.
    Available
    Specifies the health monitors that are configured on the system, and that you can use to monitor this node.
  23. If you activate more than one health monitor (in the
    Select Monitors
    setting), specify the number of health monitors that must receive successful responses in order for the node to be considered available. The default is
    All
    .
  24. In the
    Ratio
    field, type a number for the ratio weight of the node.
  25. In the
    Connection Limit
    field, type a number for the maximum established connection limit for the node.
  26. In the
    Connection Rate Limit
    field, type a number that specifies the number of new connections accepted per second for the node.
  27. If you specified an IP address in the
    Address
    setting, click
    Finished
    . If you specified an FQDN, configure the remaining settings.
  28. From the
    Address Type
    list, select whether the node resolves to an IPv4 or IPv6 address. The default is
    IPv4
    .
  29. From the
    Address Type
    list, select whether the node resolves to an IPv4 or IPv6 address. The default is
    IPv4
    .
  30. From the
    Auto Populate
    list, select
    Enabled
    . The options are:
    Enabled
    The system automatically creates ephemeral nodes using the IP addresses returned by the resolution of a DNS query for the FQDN, that is, for each DNS entry of the resolved FQDN.
    Disabled
    The system automatically creates a node that corresponds to the IP address of only the first DNS entry of the resolved FQDN.
  31. In the
    Interval
    field, type the number of seconds before the system creates new ephemeral nodes or deletes expired ephemeral nodes based on the IP addresses returned in response to a DNS query for the FQDN of the node. The default is the TTL of the IP address in the DNS response.
  32. In the
    Down Interval
    field, type the number of seconds the system waits to mark an FQDN node down following a DNS query failure.
  33. In the State area, click
    Disabled (Only persistent or active connections allowed)
    .
    You can only disable the parent FQDN node or pool member. After disabling, the ephemeral dependents are then disabled, but you cannot directly disable an ephemeral node.
  34. For the
    Address
    field:
    1. If you want to specify the node by its IP address, click
      Nodes
      and type an IP address.
    2. If you want to specify the node by a fully-qualifed domain name (FQDN), click
      FQDN
      and type the node's FQDN.
  35. If you chose
    FQDN
    for the
    Address
    setting, then in the FQDN area of the screen, configure the settings as needed or retain the default values.
  36. Click
    Update
    .
    The screen refreshes, and the status in the Availability area changes.
  37. At the bottom of the screen, click
    Update
    .
  38. Click
    Cancel
    .
  39. Click
    Finished
    .
    The screen refreshes, and the new node appears in the node list.
  40. Locate the
    State
    property and view the selected value.