Applies To:
Show VersionsBIG-IP AAM
- 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 13.0.1, 13.0.0
BIG-IP APM
- 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 13.0.1, 13.0.0
BIG-IP Link Controller
- 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 13.0.1, 13.0.0
BIG-IP Analytics
- 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 13.0.1, 13.0.0
BIG-IP LTM
- 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 13.0.1, 13.0.0
BIG-IP AFM
- 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 13.0.1, 13.0.0
BIG-IP PEM
- 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 13.0.1, 13.0.0
BIG-IP DNS
- 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 13.0.1, 13.0.0
BIG-IP ASM
- 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 13.0.1, 13.0.0
Introduction to local traffic operations
Using the BIG-IP® Configuration utility, you can manage the availability of server resources on the network by enabling and disabling certain local traffic server objects. These objects consist of server nodes and pool members, as well as virtual servers and their associated virtual addresses.
About server node state
A node in a server pool must be enabled in order to accept traffic. A node is a logical object on the BIG-IP® system that identifies the IP address of a physical resource on the network.
When you disable a node, the BIG-IP® system allows existing connections to time out or end normally. In this case, by default, the only new connections that the node accepts are those that belong to an existing persistence session.
Viewing the state of a node
It is easy to determine whether a node is currently enabled or disabled.
Enabling a node
You can enable a local traffic node that is currently disabled. When you enable a node, the BIG-IP® system allows all types of connections, including persistent connections.
Disabling a node except for persistent/active connections
You perform this task to disable a local traffic node that is currently enabled. When you disable a node, the BIG-IP® system disallows any incoming connections, but continues to process any persistent or active connections.
Forcing a node with active connections offline
You can disable a local traffic node to disallow all connections except for active connections. When you disable the node, the BIG-IP® system disallows any incoming connections (including persistent connections), but continues to process active connections. When all active connections have been processed, the node is fully offline.
About pool member state
You can enable or disable individual pool members. A pool member is a logical object on the BIG-IP® system that represents a specific server node and service. For example, a node with an IP address of 12.10.10.3 can have a corresponding pool member 12.10.10.3:80.
When you disable a pool member, the node continues to process any active connections or any connections for the current persistence session.
Viewing the state of a pool member
Before performing this task, determine the pool member that you want to force offline.
Enabling a pool member
Before performing this task, verify that the corresponding server node address is enabled.
Disabling a pool member except for persistent/active connections
Before performing this task, determine the pool member that you want to disable.
When you perform this task, the BIG-IP system, by default, allows persistent and active connections to be completed before the BIG-IP system marks the pool member as Offline.
Forcing a pool member with active connections offline
Before performing this task, determine the pool member that you want to force offline.
About virtual address state
You can enable or disable virtual addresses to manage virtual server availability to process traffic. You typically disable a virtual address when you want to drop or redirect traffic destined for all virtual servers associated with that virtual address.
Enabling a virtual address
You can enable a virtual address that is currently disabled. When you enable a virtual address, all associated virtual servers listen for traffic destined for that virtual address and process the traffic accordingly.
Disabling a virtual address
You can disable a virtual address that is currently enabled. When disabled, all associated virtual servers no longer listen for traffic destined for that virtual address.
Viewing the state of a virtual address
About virtual server state
You can enable or disable virtual servers to manage virtual server availability to process traffic. You typically disable a virtual server when you want to drop or redirect traffic destined for a specific IP address and service.
Viewing the state of a virtual server
You view the state of a virtual server to determine whether a virtual server is currently enabled or disabled.
Enabling a virtual server
You perform this task to enable a virtual server that is currently disabled. When enabled, the virtual server listens for traffic destined for the virtual server's IP address and service and processes the traffic according to the virtual server configuration.
Disabling a virtual server
You perform this task when you want to disable a virtual server that is currently enabled. When disabled, the virtual server no longer listens for traffic destined for the IP address and port specified in the virtual server configuration.