F3215-HP Load Balancing Module High Availability Configuration Guide-6PW101

133
Last succeeded probe time: 2012-11-22 09:54:03.8
Extended results:
Packet loss in test: 0%
Failures due to timeout: 0
Failures due to disconnect: 0
Failures due to no connection: 0
Failures due to sequence error: 0
Failures due to internal error: 0
Failures due to other errors: 0
Packet(s) arrived late: 0
# Display the history records of the DHCP operation.
[LB] display nqa history admin test1
NQA entry (admin admin, tag test1) history record(s):
Index Response Status Time
1 512 Succeeded 2012-11-22 09:54:03.8
The output shows that LB uses 512 milliseconds to obtain an IP address from the DHCP server.
DNS operation configuration example
Network requirements
As shown in Figure 50, configure a DNS operation to test whether LB can translate the domain name
host.com into an IP address through the DNS server, and test the time required for resolution.
Figure 50 Network diagram
Configuration procedure
# Assign each interface an IP address. (Details not shown.)
# Configure static routes or a routing protocol to make sure the devices can reach each other. (Details not
shown.)
# Create a DNS operation.
<LB> system-view
[LB] nqa entry admin test1
[LB-nqa-admin-test1] type dns
# Specify the IP address of the DNS server 10.2.2.2 as the destination address, and specify the domain
name to be translated as host.com.
[LB-nqa-admin-test1-dns] destination ip 10.2.2.2
[LB-nqa-admin-test1-dns] resolve-target host.com
# Enable the saving of history records.
[LB-nqa-admin-test1-dns] history-record enable
[LB-nqa-admin-test1-dns] quit
# Start the DNS operation.