Configuration Options Elements
Table 3-1 describe the fields on the page. An asterisk before the value field means the configuration is mandatory.
Table 3-1 IPFE Configuration Elements
| Element | Description | Data Input Notes |
|---|---|---|
| Inter-IPFE Synchronization | ||
| IPFE-A1 IP Address |
This address must reside on the internal management interface (IMI) network. This address is used for replicating association data between IPFEs and is not exposed to application clients. If left blank, the IPFE does not replicate association data. Although optional, this configuration is required for a fully functioning installation. |
Format: IPv4 or IPv6 address, or left blank Default: blank |
| IPFE-A2 IP Address |
This address must reside on the internal management interface (IMI) network. This address is used for replicating association data between IPFEs and is not exposed to application clients. If left blank, the IPFE does not replicate association data. Although optional, this configuration is required for a fully functioning installation. |
Format: IPv4 or IPv6 address, or left blank Default: blank |
| IPFE-B1 IP Address |
This address must reside on the internal management interface (IMI) network. This address is used for replicating association data between IPFEs and is not exposed to application clients. If left blank, the IPFE does not replicate association data. Although optional, this configuration is required for a fully functioning installation. |
Format: IP address, or left blank Default: blank |
| IPFE-B2 IP Address |
This address must reside on the internal management interface (IMI) network. This address is used for replicating association data between IPFEs and is not exposed to application clients. If left blank, the IPFE does not replicate association data. Although optional, this configuration is required for a fully-functioning installation. |
Format: IP address, or left blank Default: blank |
| * State Sync TCP Port | This port establishes and maintains a connection to its mate. If the connection is lost, it attempts to re-establish the connection based on the configuration of the state sync reconnect interval. |
Format: text box Range: 1-65535 Default: 19041 |
| * State Sync Reconnect Interval | Reconnect interval, in seconds, for syncing kernel state between IPFEs. |
Format: text box Range: 1-255 seconds Default: 1 |
| * Gratuitous ARP Type | Specify type of gratuitous ARP broadcast to send. |
Format: ARP Request, ARP Reply, Send both types Default: ARP Request |
| Traffic Forwarding | ||
| * Application Traffic TCP Reject Option |
How to reject TCP connections when no application servers are available. When no application servers are available, the IPFE must reject the TCP traffic that it receives. The IPFE can either drop packets or it can communicate to the application clients with TCP or ICMP messages. Select the option that can be best handled by the application client. |
Format: list Range:
Default: TCP Reset |
| * Application Traffic SCTP Reject Option |
How to reject SCTP connections when no application servers are available. When no application servers are available, the IPFE must reject the SCTP traffic that it receives. The IPFE can either drop packets or it can communicate to the application clients with ICMP messages. Select the option that can be best handled by the application client. |
Format: list Range:
Default: ICMP Host Unreachable |
| Packet Counting | ||
| * Imbalance Detection Throughput Minimum |
This value applies only to the hash algorithm selection. This is the value below which no throughput analysis is performed regarding the distribution of connections. This setting should not be changed from its default unless the IPFE is being tested with a very low load. This setting ensures the IPFE does not mark application servers as imbalanced when it is distributing very few messages between them. |
Format: text box Range: 1-2147483647 Default: 20000 |
| * Least Load Threshold | This value can be set to a packets-per-second rate below which the Least Load algorithm reverts to round robin. |
Format: text box Range: 1-2147483647 Default: 1 |
| * Cluster Rebalancing and Accounting |
Support for cluster rebalancing and packet accounting in measurements. When this is disabled, all accumulation of packet and byte measurements cease. Overload detection also stops. The disabled state is useful only for troubleshooting, which should be done by My Oracle Support . Contact My Oracle Support before disabling measurements and overload detection. |
Format: list Range:
Default: Enabled |
| Application Server Monitoring | ||
| * Monitoring Port |
TCP port to try periodic connections or monitoring of application servers. The IPFE opens a TCP connection to the application server's IP address and this port. The application server must listen on this port and should send heartbeats. |
Format: text box Range: 1-65535 Default: 9675 |
| * Monitoring Connection Timeout |
How long to wait for a connection to complete when polling the application servers for aliveness in seconds. If the IPFE detects that an application server has missed a configurable number of heartbeats - that is, more than that number of seconds have elapsed since the most recent heartbeat was received - then it considers the application server to be down. The IPFE removes a down application server from the traffic balancing pool and attempts to reconnect to the server. |
Format: text box Range: 1 - 255 Default: 3 |
| Monitoring Connection Try Interval |
Interval in seconds of periodically connecting to application servers to test for aliveness. While an application server is down, the IPFE periodically attempts to reconnect to it based on this configuration. |
Format: text box Range: 1 - 255 Default: 10 |
| Monitoring Protocol |
Application liveness monitoring method. If any Target Set has load balancing of Least Load, then this setting cannot be changed from Heartbeat due to the need for load information in the monitoring packets. The monitoring protocol allows the IPFE to determine the liveness of the application servers. The IPFE determines this either by listening for heartbeat messages from the application servers. When the protocol is set to Heartbeat, the IPFE connects to the monitoring port, sustains the connection, and receives heartbeat packets from the application server. In this case, the failure to receive a heartbeat packet within the period Back-end Connection Timeout indicates the server is dead. A dead server is removed from the traffic balancing pool. The IPFE attempts connections on the monitoring port until the server responds. When the server responds, the IPFE adds it back to the pool. |
Format: list Range:
Default: Heartbeat |
| Throttling and DoS Protection | ||
| Global Packet Rate Limit | Combined packet rate limit for a single IPFE at which overload throttling is applied. |
Format: text box Range: 10000 - 10000000 Default: 500000 |