To start managing a BIG-IP® device, you must add it to the BIG-IP Devices inventory list on the BIG-IQ® system.
Adding a device to the BIG-IP Devices inventory is a two-stage process.
Before you can add BIG-IP® devices to the BIG-IQ® inventory:
If you are running BIG-IP version 11.5.1 up to version 11.6.0, you might need root user credentials to successfully discover and add the device to the BIG-IP devices inventory. Root user credentials are not required for BIG-IP devices running 11.5.0 - 11.5.1 and 11.6.0 - 12.x.
You can use a device's Properties screen to manage that device. You can log directly in to the device, remotely reboot it, and create an instant backup of its configuration. You can also view details about the managed device, such as:
To change the object settings on a managed device, there are four tasks to perform.
This figure illustrates the workflow you perform to manage the objects on BIG-IP® devices. Changing the settings is the second step in this process.
Change managed object workflow
The format for an IPv4 address is I<a>.I<b>.I<c>.I<d>. For example, 172.16.254.0/24.
The format for an IPv6 address is I<a>:I<b>:I<c>:I<d>:I<e>:I<f>:I<g>:I<h>..For example, 2001:db8:85a3:8d3:1319:8a2e:370:7348.
|Standard||Specifies a virtual server that directs client traffic to a load balancing pool and is the most basic type of virtual server. When you first create the virtual server, you assign an existing default pool to it. From then on, the virtual server automatically directs traffic to that default pool.|
|Forwarding (Layer 2)||Specifies a virtual server that shares the same IP address as a node in an associated VLAN.|
|Forwarding (IP)||Specifies a virtual server like other virtual servers, except that the virtual server has no pool members to load balance. The virtual server simply forwards the packet directly to the destination IP address specified in the client request.|
|Performance (HTTP)||Specifies a virtual server with which you associate a Fast HTTP profile. Together, the virtual server and profile increase the speed at which the virtual server processes HTTP requests.|
|Performance (Layer 4)||Specifies a virtual server with which you associate a Fast L4 profile. Together, the virtual server and profile increase the speed at which the virtual server processes Layer 4 requests.|
|Stateless||Specifies a virtual server that accepts traffic matching the virtual server address and load balances the packet to the pool members without attempting to match the packet to a pre-existing connection in the connection table. New connections are immediately removed from the connection table. This addresses the requirement for one-way UDP traffic that needs to be processed at very high throughput levels, for example, load balancing syslog traffic to a pool of syslog servers. Stateless virtual servers are not suitable for processing traffic that requires stateful tracking, such as TCP traffic. Stateless virtual servers do not support iRules, persistence, connection mirroring, rateshaping, or SNAT automap.|
|Reject||Specifies that the BIG-IP system rejects any traffic destined for the virtual server IP address.|
|DHCP Relay||Specifies a virtual server that relays Dynamic Host Control Protocol (DHCP) client requests for an IP address to one or more DHCP servers, and provides DHCP server responses with an available IP address for the client.|
|Internal||Specifies a virtual server that supports modification of HTTP requests and responses. Internal virtual servers enable usage of ICAP (Internet Content Adaptation Protocol) servers to modify HTTP requests and responses by creating and applying an ICAP profile and adding Request Adapt or Response Adapt profiles to the virtual server.|
|All Protocols||Specifies that the virtual server supports all network protocols.|
|TCP||Specifies that the virtual server supports the TCP protocol, defined in RFC 675.|
|UDP||Specifies that the virtual server supports the UDP protocol, defined in RFC 768.|
|SCTP||Specifies that the virtual server supports the Stream Control Transmission Protocol (SCTP) protocol, defined in RFC 4960.|
|Other||Provides the ability to specify another protocol. This setting is not available when you select Standard as the type.|
|All VLANs and Tunnels||Specifies that the virtual server is enabled on all VLANs and tunnels configured on the system.|
|Enabled on||Specifies that the virtual server is enabled on the VLANs and tunnels specified in the Selected list.|
|Disabled on||Specifies that the virtual server is disabled on the VLANs and tunnels specified in the Selected list.|
|Per Virtual Server||Applies rate limiting to this virtual server.|
|Per Virtual Server and Source Address||Applies Connection Rate Limit Source Mask to the source IP address of incoming connections to this virtual server, and applies the rate limit to connections sharing the same subnet. The Connection Rate Limit Source Mask specifies the number of bits in the IP address to use as a limit key.|
|Per Virtual Server and Destination Address||Applies Connection Rate Limit Destination Mask to the destination IP address of outgoing connections from this virtual server, and applies the rate limit to connections sharing the same subnet. The Connection Rate Limit Destination Mask specifies the number of bits in the IP address to use as a limit key.|
|Per Virtual Server, Destination, and Source Address||Applies Connection Rate Limit Source Mask and Connection Rate Limit Destination Mask to the source and destination IP address of incoming connections to this virtual server, and applies the rate limit to connections sharing the same subnet. The Connection Rate Limit Source Mask and Connection Rate Limit Destination Mask specify the number of bits in the IP addresses to use as a limit key.|
|Per Source Address (All Rate Limiting Virtual Servers)||Applies rate limiting based on the specified source address for all virtual servers that have rate limits specified. Per Destination Address (All Rate Limiting Virtual Servers): Applies rate limiting based on the specified destination address for all virtual servers that have rate limits specified.|
|Per Source and Destination Address (All Rate Limiting Virtual Servers)||Applies rate limiting based on the specified source and destination addresses for all virtual servers that have rate limits specified.|
|Preserve||Specifies that the system preserves the value configured for the source port, unless the source port from a particular SNAT is already in use, in which case the system uses a different port.|
|Preserve Strict||Specifies that the system preserves the value configured for the
source port. If the port is in use, the system does not process the
connection. Use this setting only for cases that meet at least one of
the following conditions:
|Change||Specifies that the system changes the source port. This setting is useful for obfuscating internal network addresses.|
You can use the BIG-IQ® ADC interface to add a node to a managed device.
Nodes are the basis for creating a load balancing pool. For any server that you want to be part of a load balancing pool, you must first create a node, that is, designate that server as a node. After designating the server as node, you can add the node to a pool as a pool member. You can also associate a health monitor with the node, to report the status of that server.
To select specific health monitors for this pool member: