- Table of Contents
-
- 06-System
- 01-High availability group
- 02-VRRP
- 03-Track
- 04-BFD
- 05-NQA
- 06-Basic log settings
- 07-Session log settings
- 08-NAT log settings
- 09-AFT log settings
- 10-Threat log settings
- 11-Application audit log settings
- 12-URL filtering log settings
- 13-Bandwidth alarm logs
- 14-Attack defense log settings
- 15-NetShare log settings
- 16-Report settings
- 17-Session settings
- 18-Signature upgrade
- 19-Software upgrade
- 20-License management
- 21-Administrators
- 22-Date and time
- 23-Configuration management
- 24-Packet capture
- 25-Webpage Diagnosis
- 26-Packet trace
- 27-Fast Internet Access
- 28-SNMP
- 29-IRF
- 30-IRF advanced settings
- 30-IRF advanced settings(only for F50X0-D and F5000-AK5X5 firewalls)
- 31-Contexts
- 31-Contexts(only for F50X0-D and F5000-AK5X5 firewalls)
- 32-About
- 33-MAC address learning through a Layer 3 device
- 34-Bandwidth management logs
- 35-Configuration log settings
- 36-Context rate limit logging
- 37-Heartbeat log settings
- 38-Diagnostic Info
- 39-IP access logs
- 40-IP reputation log settings
- 41-IPsec diagnosis
- 42-Load balancing logging
- 43-Load balancing test
- 44-MAC authentication online users
- 45-Packet capture
- 45-Packet capture(only for F50X0-D and F5000-AK5X5 firewalls)
- 46-Ping
- 47-Reboot
- 48-Security policy log
- 49-Tracert
- 50-WAF log settings
- Related Documents
-
Title | Size | Download |
---|---|---|
43-Load balancing test | 30.38 KB |
Load balancing test
Introduction
The administrator can test the load balancing result by specifying the protocol, source IPv4/IPv6 address, source port number, destination IPv4/IPv6 address, and destination port number.
Performing a load balancing test
Procedure
1. Select System > Diagnosis Center > Load Balancing Test.
2. Configure test parameters.
Table 1 Test parameter configuration items
Item |
Description |
Slot number |
Specify the slot number to be tested. |
Chassis/Slot/CPU number |
Specify the chassis/slot/CPU number to be tested. This parameter is supported only by distributed devices in IRF mode. |
IP type |
IP address type: · IPv4 · IPv6 |
VPN instance |
Specify the VPN instance to be tested. |
Destination IPv4/IPv6 address |
Specify the destination IPv4/IPv6 address to be tested. Typically, specify the IP address of the virtual server. |
Source IPv4/IPv6 address |
Specify the source IPv4/IPv6 address to be tested. |
Protocol layer |
Specify the layer of the information that can be identified by load balancing. · Layer 4: Identifies network layer and transport layer information. · Layer 7: Identifies network layer, transport layer, and application layer information. |
Layer 4 protocol |
Select a way to identify a protocol: · Protocol name · Protocol number |
Protocol name |
Specify the protocol to be tested: · ICMP · TCP · UDP |
Protocol number |
Enter the number of the protocol to be tested. |
Layer 7 protocol |
Specify a way to identify an HTTP packet: · Import HTTP packet · Construct HTTP packet |
Import HTTP packet |
Import the HTTP packet to be tested. The file containing the HTTP packet content must be suffixed with .txt, and cannot be larger than 5000 bytes. |
HTTP request method |
Specify an HTTP request method: · GET · POST |
URL |
Specify a URL for the HTTP packet, case sensitive. A URL can contain letters, digits, hyphens (-), underscores (_), and periods (.). The URL cannot contain consecutive periods and question marks (?). |
HTTP packet header |
Specify a space-separated list of up to 10 HTTP packet headers. A header cannot contain question marks (?). |
HTTP packet content |
Specify the content of the HTTP packet body. The HTTP packet content cannot contain question marks (?). |
Destination port number |
Enter the destination port number to be tested. Support for this parameter depends on the protocol. |
Source port number |
Enter the source port number to be tested. Support for this parameter depends on the protocol. |
3. Click Start testing. For more information about the test result, see Table 2.
Field |
Description |
Slot number |
Slot number of the device. The displayed value for this field depends on your configuration. |
Chassis number/Slot number/CPU number |
Chassis/slot/CPU number of the device. This field is supported only by distributed devices in IRF mode. The displayed value for this field depends on your configuration. |
Matched virtual server name |
Name of the matching virtual server. The displayed value for this field depends on your configuration. |
No virtual server is matched |
N/A |
Matched class name |
Name of the matching class. The displayed value for this field depends on your configuration. |
Default action is matched |
N/A |
Matched server farm name |
Name of the matching default server farm. The displayed value for this field depends on your configuration. |
Matched link group name |
Name of the matching default link group. The displayed value for this field depends on your configuration. |
Forwarding mode |
Forwarding mode: · Load balancing is not performed because the destination address is the address of the local device. · Load balancing is not supported because an HTTP virtual server is matched. · Forwards packets. · Forwards packets to the real server. · Forwards packets to the link. · Drops packets. · Redirects packets. |
Selected real server name |
Name of the matching real server. The displayed value for this field depends on your configuration. |
Selected link name |
Name of the matching link. The displayed value for this field depends on your configuration. |
Scheduling algorithm used to select a real server |
Scheduling algorithm used to select the real server: · Predictor · Sticky method |
Scheduling algorithm used to select a link |
Scheduling algorithm used to select the link: · Predictor · Sticky method · Proximity |
Packet drop reason |
Packet drop reason: · Number of connections or bandwidth for the virtual server exceeded the limit. · No class is matched and no available server farm is configured. · No class is matched and no available link group is configured. · No available real server in the server farm. · No available link in the link group. · Action is drop. · A sticky entry was matched but the number of connections or bandwidth for the real server exceeded the limit. · A sticky entry was matched but the number of connections or bandwidth for the link exceeded the limit. · A class was matched but no available server farm exists in the action of the class. · A class was matched but no available link group exists in the action of the class. · The HTTP packet is invalid. · The HTTP request line is invalid. · The HTTP header is invalid. · The chunk HTTP content is invalid. |