Applies To:

Show Versions Show Versions

sol13310: Disabling nodes or pool members for maintenance (11.x)
How-ToHow-To

Original Publication Date: 02/09/2012
Updated Date: 11/04/2013

This article applies to BIG-IP 11.x. For information about other versions, refer to the following article:

Purpose

You should consider using this procedure under the following conditions:

  • You need to disable a node or pool member for maintenance.
  • You need to force a node or pool member offline for maintenance.

Prerequisites

You must meet the following prerequisite to use this procedure:

  • You have administrative access to the partition associated with the node or pool member.

Description

The BIG-IP system designates two terms for network devices to which a BIG-IP system load balances traffic: nodes and pool members. A node is identified as the network device's IP address, such as 10.10.10.10. A pool member is identified as the network device's IP address, the service port on which the pool member is listening, and the name of the pool to which it belongs. For example: myPool:10.10.10.10:80.

You can set the node and pool members to a Disabled or Forced Offline state. When you interrupt access to a network device for maintenance, you should change the state of the node to Disabled or Forced Offline. If the node is set to Disabled or Forced Offline, any pool member in the BIG-IP configuration that uses that same IP address is also set to Disabled or Forced Offline. Alternatively, when you disrupt only some services on a device, you should change the state of the affected pool members to Disabled or Forced Offline. For example, if you want to change the state of the HTTP, HTTPS, and FTP pool members using the server IP 10.0.0.10, you should disable or force the 10.0.0.10 node offline. If you want to only change the state of the HTTP pool members running on address 10.0.0.10 and port 80, you should disable or force all 10.0.0.10:80 pool members offline.

When set to Disabled, a node or pool member continues to process persistent and active connections. It can accept new connections only if the connections belong to an existing persistence session.

When set to Forced Offline, a node or pool member allows existing connections to time out, but no new connections are allowed.

Procedures

To disable a node for maintenance, perform one of the following procedures:

To disable a pool member for maintenance, perform one of the following procedures:

Setting the node state using the Configuration utility

Impact of procedure: Nodes that have been disabled accept only new connections that match an existing persistence session. Nodes that have been forced offline do not accept any new connections, even if they match an existing persistence session.

  1. Log in to the BIG-IP Configuration utility.
  2. Click Local Traffic.
  3. Click Nodes.
  4. Click Node List.
  5. Click the name of the node you want to set.
  6. For the State option, select either Disabled (Only persistence or active connections allowed) or Forced Offline (Only active connections allowed).
  7. Click Update.

Setting the node state to Disabled using the command line

Impact of procedure: Nodes that have been disabled accept only new connections that match an existing persistence session.

  1. Log in to the Traffic Management Shell (tmsh) by typing the following command:

    tmsh

  2. Set the node state to Disabled by using the following command syntax:

    modify ltm node <node name> session user-disabled

    For example, to set the state of the node 10.10.10.211 to Disabled, you would type the following command:

    modify ltm node 10.10.10.211 session user-disabled

    You can use the same command structure to enable a disabled node by changing the statement user-disabled to user-enabled.

    For example, you would use the following command syntax:

    modify ltm node <node name> session user-enabled

  3. Save the change by typing the following command:

    save sys config

Setting the node state to Forced Offline using the command line

Impact of procedure: Nodes that have been forced offline do not accept any new connections, even if they match an existing persistence session.

  1. Log in to the Traffic Management Shell (tmsh) by typing the following command:

    tmsh

  2. Set the node state to Forced Offline by using the following command syntax:

    modify ltm node <node name> state user-down

    For example, to set the state of the node 10.10.10.211 to Forced Offline, you would type the following command:

    modify ltm node 10.10.10.211 state user-down

    You can use the same command structure to place the node online by changing user-down to user-up.

    For example, you would use the following command syntax:

    modify ltm node <node name> state user-up

  3. Save the change by typing the following command:

    save sys config

Setting the pool member state using the Configuration utility

Impact of procedure: Pool members that have been disabled accept only new connections that match an existing persistence session. Pool members that have been forced offline do not accept any new connections, even if they match an existing persistence session.

  1. Log in to the BIG-IP Configuration utility.
  2. Click Local Traffic.
  3. Click Pools.
  4. Click Pool List.
  5. Click the Members link for the pool to which the pool member belongs.
  6. Click the pool member you want to set.
  7. For the State option, select either Disabled (Only persistence or active connections allowed) or Forced Offline (Only active connections allowed).
  8. Click Update.

Setting the pool member state to Disabled using the command line

Impact of procedure: Pool members that have been disabled accept only new connections that match an existing persistence session.

  1. Log in to the Traffic Management Shell (tmsh) by typing the following command:

    tmsh

  2. Set the pool member state to Disabled by using the following command syntax:

    modify ltm pool <pool name> members modify { <pool member:port> { session user-disabled } }

    For example, to set the state of the pool member 10.10.10.211:http in pool http-pool to Disabled, you would type the following command:

    modify ltm pool http-pool members modify { 10.10.10.211:http { session user-disabled } }

    You can use the same command structure when you modify the pool member states from disabled to enabled by changing the session variable from user-disabled to user-enabled.

    For example, you would use the following command syntax:

    modify ltm pool http-pool members modify { <pool member:port> { session user-enabled } }

  3. Save the change by typing the following command:

    save sys config

Setting the pool member state to Forced Offline using the command line

Impact of procedure: Pool members that have been forced offline do not accept any new connections, even if they match an existing persistence session.

  1. Log in to the Traffic Management Shell (tmsh) by typing the following command:

    tmsh

  2. Set the pool member state to Forced Offline by using the following command syntax:

    modify ltm pool <pool name> members modify { <pool member:port> { state user-down } }

    For example, to set the state of the pool member 10.10.10.211:http in pool http-pool to Forced Offline, you would type the following command:

    modify ltm pool http-pool members modify { 10.10.10.211:http { state user-down } }

    You can use the same command structure when you modify the pool member states from Offline to Online by changing the session variable from user-down to user-up.

    For example, you would use the following command syntax:

    modify ltm pool http-pool members modify { <pool member:port> { state user-up } }

  3. Save the change by typing the following command:

    save sys config

Supplemental Information

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)