- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 01-Load balancing commands | 597.89 KB |
bandwidth busy-protection enable (transparent DNS proxy view)
connection-sync enable (transparent DNS proxy view)
display loadbalance dns-proxy statistics
display loadbalance dns-server
display loadbalance dns-server statistics
display loadbalance dns-server-pool
display loadbalance hot-backup statistics
display loadbalance link statistics
dns-server (DNS server pool view)
dns-server-pool (DNS server view)
dns-server-pool (LB action view)
ip address (transparent DNS proxy view)
ipv6 address (DNS server view)
ipv6 address (transparent DNS proxy view)
lb-policy (transparent DNS proxy view)
loadbalance log enable bandwidth-busy
port (transparent DNS proxy view)
predictor (DNS server pool view)
priority (DNS server pool member view)
probe (DNS server pool member view)
rate-limit bandwidth (link view)
reset loadbalance dns-proxy statistics
reset loadbalance dns-server statistics
reset loadbalance hot-backup statistics
reset loadbalance link statistics
selected-server (DNS server pool view)
service enable (transparent DNS proxy view)
sticky-sync enable (transparent DNS proxy view)
success-criteria (DNS server pool member view)
success-criteria (DNS server pool view)
success-criteria (DNS server view)
vpn-instance (DNS server view)
vpn-instance (transparent DNS proxy view)
Load balancing commands
The following compatibility matrixes show the support of hardware platforms for server load balancing:
|
Hardware |
Server load balancing compatibility |
|
MSR610 |
No |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK, MSR810-EI, MSR810-LM-EA, MSR810-LM-EI |
Yes |
|
MSR810-LMS, MSR810-LUS |
No |
|
MSR810-SI, MSR810-LM-SI |
No |
|
MSR810-LMS-EA, MSR810-LME |
Yes |
|
MSR1004S-5G, MSR1004S-5G-CN |
Yes |
|
MSR1104S-W, MSR1104S-W-CAT6, MSR1104S-5G-CN, MSR1104S-W-5G-CN, MSR1104S-W-5GGL |
Yes |
|
MSR2600-6-X1, MSR2600-15-X1, MSR2600-15-X1-T |
Yes |
|
MSR2600-10-X1 |
Yes |
|
MSR2630-G-X1 |
Yes |
|
MSR 2630 |
Yes |
|
MSR3600-28, MSR3600-51 |
Yes |
|
MSR3600-28-SI, MSR3600-51-SI |
No |
|
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP |
Yes |
|
MSR3600-28-G-DP, MSR3600-51-G-DP |
Yes |
|
MSR3600-28-G-X1-DP, MSR3600-51-G-X1-DP |
Yes |
|
MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG |
Yes |
|
MSR-iMC |
Yes |
|
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1 |
Yes |
|
MSR3610, MSR3620, MSR3620-DP, MSR3640, MSR3660 |
Yes |
|
MSR3610-G, MSR3620-G |
Yes |
|
MSR3640-G |
Yes |
|
MSR3640-X1-HI |
Yes |
|
Hardware |
Server load balancing compatibility |
|
MSR810-W-WiNet, MSR810-LM-WiNet |
Yes |
|
MSR830-4LM-WiNet |
Yes |
|
MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet |
Yes |
|
MSR830-6BHI-WiNet, MSR830-10BHI-WiNet |
Yes |
|
MSR2600-6-WiNet |
Yes |
|
MSR2600-10-X1-WiNet |
Yes |
|
MSR2630-WiNet |
Yes |
|
MSR3600-28-WiNet |
Yes |
|
MSR3610-X1-WiNet |
Yes |
|
MSR3620-X1-WiNet |
Yes |
|
MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet |
Yes |
|
Hardware |
Server load balancing compatibility |
|
MSR860-6EI-XS |
Yes |
|
MSR860-6HI-XS |
Yes |
|
MSR2600-15-X1-XS |
Yes |
|
MSR2630-XS |
Yes |
|
MSR3600-28-XS |
Yes |
|
MSR3610-XS |
Yes |
|
MSR3620-XS |
Yes |
|
MSR3610-I-XS |
Yes |
|
MSR3610-IE-XS |
Yes |
|
MSR3620-X1-XS |
Yes |
|
MSR3640-XS |
Yes |
|
MSR3660-XS |
Yes |
|
Hardware |
Server load balancing compatibility |
|
MSR810-LM-GL |
Yes |
|
MSR810-W-LM-GL |
Yes |
|
MSR830-6EI-GL |
Yes |
|
MSR830-10EI-GL |
Yes |
|
MSR830-6HI-GL |
Yes |
|
MSR830-10HI-GL |
Yes |
|
MSR1004S-5G-GL |
Yes |
|
MSR2600-6-X1-GL |
Yes |
|
MSR3600-28-SI-GL |
No |
auto-alloc address
Use auto-alloc address to enable the device to automatically obtain the IP address of a DNS server.
Use undo auto-alloc address to disable the device from automatically obtaining the IP address of a DNS server.
Syntax
auto-alloc address
undo auto-alloc address
Default
The device is disabled from automatically obtaining the IP address of a DNS server.
Views
DNS server view
Predefined user roles
network-admin
Usage guidelines
This command is mutually exclusive with the ip address and ipv6 address commands.
Before configuring this command, you must configure the router interface command. Otherwise, the IP address of the DNS server cannot be obtained.
If the device obtains multiple DNS server IP addresses, it uses the smallest available IP address.
Examples
# Enable the device to automatically obtain the IP address of DNS server ds1.
<Sysname> system-view
[Sysname] loadbalance dns-server ds1
[Sysname-lb-ds-ds1] auto-alloc address
Related commands
display loadbalance dns-server
bandwidth busy-protection enable (transparent DNS proxy view)
Use bandwidth busy-protection enable to enable the link protection feature for a transparent DNS proxy.
Use undo bandwidth busy-protection enable to disable the link protection feature for a transparent DNS proxy.
Syntax
bandwidth busy-protection enable
undo bandwidth busy-protection enable
Default
The link protection feature is disabled for a transparent DNS proxy.
Views
Transparent DNS proxy view
Predefined user roles
network-admin
Usage guidelines
This feature enables a transparent DNS proxy to select a DNS server from the DNS server pool based on the link bandwidth ratio. If the bandwidth ratio of a link exceeds the specified value, the corresponding DNS server is not selected.
If the link bandwidth ratio of all DNS servers in the DNS server pool exceeds the specified value, the link protection feature is automatically disabled. If the link bandwidth ratio of any DNS server drops below the specified value, the link protection feature is automatically enabled, and the corresponding DNS server is selected.
Examples
# Enable the link protection feature for transparent DNS proxy dns-proxy1.
<Sysname> system-view
[Sysname] loadbalance dns-proxy dns-proxy1
[Sysname-lb-dp-udp-dns-proxy1] bandwidth busy-protection enable
Related commands
bandwidth busy-rate (link view)
bandwidth busy-rate
Use bandwidth busy-rate to set the bandwidth ratio for an LB link.
Use undo bandwidth busy-rate to restore the default.
Syntax
bandwidth [ inbound | outbound ] busy-rate busy-rate-number [ recovery recovery-rate-number ]
undo bandwidth [ inbound | outbound ] busy-rate
Default
The bandwidth ratio is 70.
Views
LB link view
Predefined user roles
network-admin
Parameters
inbound: Specifies the inbound bandwidth ratio.
outbound: Specifies the outbound bandwidth ratio.
busy-rate-number: Specifies bandwidth ratio in the range of 1 to 100.
recovery recovery-rate-number: Specifies bandwidth recovery ratio in the range of 1 to 100. By default, if the bandwidth ratio is greater than 10, the bandwidth recovery ratio equals the bandwidth ratio minus 10; if the bandwidth ratio is smaller than or equal to 10, the bandwidth recovery ratio equals the bandwidth ratio.
Usage guidelines
If the bandwidth of an LB link exceeds the maximum expected bandwidth multiplied by the bandwidth ratio, the LB link is busy and will not be selected. If the bandwidth of the LB link drops below the maximum expected bandwidth multiplied by the bandwidth recovery ratio, the LB link participates in scheduling again.
If you do not specify the inbound or outbound keyword, this command sets the total bandwidth ratio.
The bandwidth ratio equals the current bandwidth divided by the maximum bandwidth of the LB link. If the maximum bandwidth is not limited, the supported maximum bandwidth is used for calculating the bandwidth ratio.
The bandwidth recovery ratio must be smaller than or equal to the bandwidth ratio of an LB link.
This command takes effect only on new sessions and does not take effect on existing sessions.
Examples
# Set the total bandwidth ratio and bandwidth recovery ratio for the LB link lk1 to 90 and 85.
<Sysname> system-view
[Sysname] loadbalance link lk1
[Sysname-lb-link-link1] bandwidth busy-rate 90 recovery 85
Related commands
display loadbalance link
max-bandwidth (link view)
busy-action continue
Use busy-action continue to configure the action of matching the next rule when all links or DNS servers are busy.
Use undo busy-action to restore the default.
Syntax
busy-action continue
undo busy-action
Default
The device assigns packets to links or DNS servers regardless of whether they are busy.
Views
Link-generic LB action view
DNS server LB action view
Predefined user roles
network-admin
Usage guidelines
This command enables the device to match the next rule when all links or DNS servers are busy.
Examples
# In the transparent DNS proxy scenario, configure DNS LB action a2 to match the next rule when all links or DNS servers are busy.
<Sysname> system-view
[Sysname] loadbalance action a2 type dns
[Sysname-lba-dns-a2] busy-action continue
class
Use class to specify an LB action for the specified LB class.
Use undo class to delete an LB class.
Syntax
class class-name [ insert-before before-class-name | insert-after [ after-class-name ] ] action action-name
undo class class-name
Default
No LB action is specified for the LB class.
Views
LB policy view
Predefined user roles
network-admin
Parameters
class-name: Specifies an LB class by its name, a case-insensitive string of 1 to 63 characters.
insert-before: Inserts the target class before an LB class (which must already be referenced by the current LB policy).
before-class-name: Specifies an LB class by its name, a case-insensitive string of 1 to 63 characters.
insert-after: Inserts the target class after an LB class (which must already be referenced by the current LB policy).
after-class-name: Specifies an LB class by its name, a case-insensitive string of 1 to 63 characters. If you do not specify this argument, the command inserts the target LB class after all LB classes.
action-name: Specifies an LB action by its name, a case-insensitive string of 1 to 63 characters.
Usage guidelines
This command sets an LB action for packets matching the specified LB class.
If you do not specify the insert-before and insert-after keywords, the command inserts the target LB class after all LB classes.
You can specify an LB action for different LB classes.
A DNS LB policy can reference DNS LB actions only; a generic LB policy can reference generic LB classes and generic LB actions only. This rule does not apply to HTTP LB policies.
Examples
# In the transparent DNS proxy scenario, specify the LB action lba3 for the LB class lbc3 in the DNS LB policy lbp3, and insert lbc1 before the LB class lbc0.
<Sysname> system-view
[Sysname] loadbalance policy lbp3 type dns
[Sysname-lbp-dns-lbp3] class lbc3 insert-before lbc0 action lba3
connection-sync enable (transparent DNS proxy view)
Use connection-sync enable to enable session extension information synchronization for a transparent DNS proxy.
Use undo connection-sync enable to disable session extension information synchronization for a transparent DNS proxy.
Syntax
connection-sync enable
undo connection-sync enable
Default
Session extension information synchronization is disabled for a transparent DNS proxy.
Views
Transparent DNS proxy view
Predefined user roles
network-admin
Usage guidelines
This command can back up session information to ensure service continuity during a master and backup switchover in hot backup mode.
Examples
# Enable session extension information synchronization for the transparent DNS proxy dns_proxy1.
<Sysname>system-view
[Sysname] loadbalance dns-proxy dns-proxy1
[Sysname-lb-dp-udp-dns-proxy1] connection-sync enable
default dns-server-pool
Use default dns-server-pool to specify the default (primary) DNS server pool for a transparent DNS proxy.
Use undo default dns-server-pool to restore the default.
Syntax
default dns-server-pool pool-name [ sticky sticky-name ]
undo default dns-server-pool
Default
No default DNS server pool is specified for a transparent DNS proxy.
Views
Transparent DNS proxy view
Predefined user roles
network-admin
Parameters
pool-name: Specifies a primary DNS server pool by its name, a case-insensitive string of 1 to 63 characters.
sticky sticky-name: Specifies a sticky group by its name, a case-insensitive string of 1 to 63 characters. If you do not specify a sticky group, the DNS server pool does not correspond to any sticky group.
Usage guidelines
If you execute the default dns-server-pool command multiple times, the most recent configuration takes effect.
Examples
# Specify the primary DNS server pool dns-pool1 and the sticky group st1 for the transparent DNS proxy dns-proxy1.
<Sysname> system-view
[Sysname] loadbalance dns-proxy dns-proxy1
[Sysname-lb-dp-udp-dns-proxy1] default dns-server-pool dns-pool1 sticky st1
default-class action
Use default-class action to specify the default LB action.
Use undo default-class to restore the default.
Syntax
default-class action action-name
undo default-class
Default
No default LB action is specified.
Views
LB policy view
Predefined user roles
network-admin
Parameters
action-name: Specifies an LB action by its name, a case-insensitive string of 1 to 63 characters.
Usage guidelines
This command sets the default LB action for packets that fail to match any LB class.
A DNS LB policy can reference DNS LB actions only; a generic LB policy can reference generic LB actions only. This rule does not apply to HTTP LB policies.
Examples
# In the transparent DNS proxy scenario, specify the default LB action lba3 for the DNS LB policy lbp3.
<Sysname> system-view
[Sysname] loadbalance policy lbp3 type dns
[Sysname-lbp-dns-lbp3] default-class action lba3
description
Use description to configure a description.
Use undo description to restore the default.
Syntax
description text
undo description
Default
No description is configured.
Views
LB action view/LB class view/LB policy view
Sticky group view
Link view
ISP view
DNS server view/DNS server pool member view/DNS server pool view
Predefined user roles
network-admin
Parameters
text: Specifies a description, a case-sensitive string of 1 to 127 characters.
Examples
# Configure the description LB action LBA1 for the DNS LB action lba1.
<Sysname> system-view
[Sysname] loadbalance action lba1 type dns
[Sysname-lba-dns-lba1] description LB action LBA1
display loadbalance action
Use display loadbalance action to display LB action information.
Syntax
display loadbalance action [ name action-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name action-name: Specifies an LB action by its name, a case-insensitive string of 1 to 63 characters. If you do not specify this option, the command displays information about all LB actions.
Examples
# Display information about all LB actions.
<Sysname> display loadbalance action
LB action: lba1
Description:
Type: Generic
State: Inactive
Forward type: Drop
IP ToS:
Fallback-action: Disabled
Busy-action: Force
TCP payload rewrite:
Value: QMGR.S01
Replacement: QMGR.S01%[variable]
Direction: Request
TCP payload rewrite:
Value: QMGR.S01_1
Replacement: QMGR.S01_2
Direction: Response
TCP payload rewrite:
Value: QMGR.S02_2
Replacement: QMGR.S01_2
Direction: Response
LB action: lba2
Description:
Type: HTTP
State: Active
Forward type: Server farm
Server farm: sf (in use)
Backup server farm: sfb
Sticky: sg3
Backup sticky: sg4
IP ToS: 20
Fallback-action: Disabled
SSL client policy:
Content rewrite:
Value:
Replacement:
Redirect relocation:
Redirect return-code: 302
Header delete:
Name: ww
Direction: Request
Header insert:
Name: aa
Value: 1234567890123456789012345678901234567890123456789012345678901234567890
Direction: Both
Header insert:
Name: cc
Value: dd
Direction: Request
Header rewrite:
Name: ee
Value: dd
Replacement: ff
Direction: Response
SSL URL rewrite:
Value: 12
Clear port: 12
SSL port: 123
LB action: lba3
Description: sina
Type: Link-generic
State: Active
Forward type: link group
Link group: lg1 (in use)
Backup link group: lg2
Sticky:
IP ToS:
Fallback-action: None
LB action: lba4
Description: xx
Type: DNS
State: Active
Forward type: DNS server pool
DNS server pool: dsp1
Sticky: st
IP ToS:
Fallback-action: Disabled
Busy-action: Force
LB action: lba5
Description:
Type: HTTP
State: Active
Forward type: Redirect
IP ToS:
Fallback-action: Continue
SSL client policy:
Content rewrite:
Value:
Replacement:
Redirect relocation: www.example.com
Redirect return-code: 302
LB action: lba6
Description:
Type: HTTP
State: Active
Forward type: Response
IP ToS:
Fallback-action: Response
Raw file name: 301.raw
SSL client policy:
Content rewrite:
Value:
Replacement:
Redirect relocation:
Redirect return-code: 302
Response file:
File: index.html
URL: /index/css
Response file:
File name: subsys_intf.js
URL: /index/subsys
Response file:
File name: subsys.js
URL: /subsys.js
Response zip file:
Zip file name: subsys.zip
Working path: /
Table 1 Command output
|
Field |
Description |
|
LB action |
LB action name. |
|
Description |
Description for the LB action. |
|
Type |
LB action type: · DNS. · Generic. · HTTP. · Link-generic. · RADIUS. |
|
State |
LB action state: · Active. · Inactive. |
|
Forward type |
Packet forwarding mode of the LB action: · Drop—Discards packets. · Drop(FIN-close)—Closes TCP connections by sending FIN packets (applicable to generic and HTTP LB actions). · Drop(RST-close)—Closes TCP connections by sending RST packets (applicable to generic and HTTP LB actions). · Forward—Forwards packets. · Server farm—Forwards packets through the server farm (applicable to generic, HTTP, and RADIUS LB actions). · Link group—Forwards packets through the link group (applicable to link-generic LB actions). · DNS server pool—Forwards packets through the DNS server pool (applicable to DNS LB actions). · Skip current DNS proxy (applicable to DNS LB actions). · Redirect—Redirects packets. · Response—Responds to client requests by using a file. |
|
Server farm |
Primary server farm name. (in use) indicates the server farm is in use. This field is displayed only when the packet forwarding mode is server farm. |
|
Backup server farm |
Backup server farm name. (in use) indicates the server farm is in use. This field is displayed only when the packet forwarding mode is server farm. |
|
Link group |
Default link group name. (in use) indicates the link group is in use. |
|
Backup link group |
Backup link group name. (in use) indicates the link group is in use. |
|
Sticky |
Primary sticky group name. This field is displayed only when the packet forwarding mode is server farm or DNS server pool. |
|
Backup sticky |
Backup sticky group name. This field is displayed only when the packet forwarding mode is server farm and the LB action type is HTTP or RADIUS. |
|
IP ToS |
ToS field value of IP packets. |
|
Fallback-action |
Action taken upon load balancing failure: · None—Does not take any action. · Continue—Matches the next rule. · Response—Responds to client requests by using a file. · Drop(FIN-close)—Closes TCP connections by sending FIN packets (applicable to generic and HTTP LB actions). · Drop(RST-close)—Closes TCP connections by sending RST packets (applicable to generic and HTTP LB actions). |
|
Busy-action |
Action taken upon busyness: · Continue—Matches the next rule. · Force—Assigns packets to links or DNS servers regardless of whether they are busy. |
|
SSL client policy |
SSL client policy name. This field is displayed for HTTP LB actions only. |
|
Content rewrite |
HTTP content rewrite configuration: · Value—Specifies the HTTP packet content to be rewritten. · Replacement—Specifies the content after rewrite. This field is displayed only for an HTTP-type LB action. |
|
Redirect relocation |
Redirection URL. This field is displayed only for HTTP-type LB actions. |
|
Redirect return-code |
Status code in the redirection packets. This field is displayed only for HTTP-type LB actions. |
|
Header delete |
Deletes the HTTP header. · Name—Name of the HTTP packet header. · Direction—Specifies HTTP requests, HTTP responses, or both. This field is displayed only when the header delete command is configured. |
|
Header insert |
Inserts the HTTP header. · Name—Name of the HTTP packet header. · Value—Content of the HTTP packet header. · Direction—Specifies HTTP requests, HTTP responses, or both. This field is displayed only when the header insert command is configured. |
|
Header rewrite |
Rewrites the HTTP header. · Name—Name of the HTTP packet header. · Value—Content of the HTTP packet header to be rewritten. · Replacement—Content after rewrite. · Direction—Specifies HTTP requests, HTTP responses, or both. This field is displayed only when the header rewrite command is configured. |
|
SSL URL rewrite |
Rewrites the URL in the Location header of HTTP response packets sent by the server. · Value—Regular expression for the location header URL. · Clear port—HTTP port number to be rewritten. · SSL port—SSL port number after rewrite. This field is displayed only when the ssl url rewrite command is configured. |
|
DNS server pool |
DNS server pool name. This field is displayed only when the packet forwarding mode is DNS server pool. |
|
Response file |
Responds to client requests by using an uncompressed file. |
|
File name |
Name of the uncompressed file. |
|
URL |
URL path used to match client requests. |
|
Response zip file |
Responds to client requests by using a compressed file. |
|
Zip file name |
Name of the compressed file. |
|
Working path |
Working path used to match client requests. |
|
Raw file name |
Response file used upon load balancing failure. |
|
TCP payload rewrite |
Rewrite the TCP payload: · Value—Content of the TCP packet header to be rewritten. · Replacement—Content after rewrite. · Direction—Specifies TCP requests, TCP responses, or both. This field is displayed only when the payload rewrite command is configured. |
display loadbalance class
Use display loadbalance class to display LB class information.
Syntax
display loadbalance class [ name class-name ]
Views
Any view
Predefined user roles
network-operator
Parameters
name class-name: Specifies an LB class by its name, a case-insensitive string of 1 to 63 characters. If you do not specify this option, the command displays information about all LB classes.
Examples
# Display information about all LB classes.
<Sysname> display loadbalance class
LB class: lbc1
Description:
Type: HTTP
Match type: Match-all
Match rule:
match 1 source ip address 1.2.3.0 24
match 2 source ipv6 address 1::2
match 3 cookie abc value 123
match 4 header def value 12
match 5 method ext xde
match 6 method rfc CONNECT
match 7 class cla2
match 8 url 2q3
match 9 acl ipv4 number 2000
match 10 acl ipv6 number 2001
match 11 acl ipv4 name aaa
match 12 acl ipv6 name bbb
match 13 isp name isp1
LB class: lbc2
Description:
Type: Generic
Match type: Match-any
Match rule:
match 1 class cla2
match 2 source ip address 1.2.23.0 24
match 3 source ipv6 address 1::12
match 4 acl ipv4 number 3000
match 5 acl ipv6 number 3001
match 6 acl ipv4 name ccc
match 7 acl ipv6 name ddd
match 8 isp name isp2
match 9 payload orcl
LB class: lbc3
Description:
Type: Link-generic
Match type: Match-any
Match rule:
match 1 class cla3
match 2 source ip address 1.2.3.0 24
match 3 source ipv6 address 1::12
match 4 acl ipv4 number 3002
match 5 acl ipv6 number 3003
match 6 acl ipv4 name ccc
match 7 acl ipv6 name ddd
match 8 isp name isp2
match 9 user u1
match 10 user-group lb-group
match 11 interface GE1/0/1
LB class: lbc4
Description:
Type: DNS
Match type: Match-any
Match rule:
match 1 class cla2
match 2 source ip address 1.2.3.0 24
match 3 source ipv6 address 1::12
match 4 acl ipv4 number 3002
match 5 acl ipv6 number 3003
match 6 acl ipv4 name ccc
match 7 acl ipv6 name ddd
match 8 destination ip address 1.2.3.0 24
match 9 destination ipv6 address 1::12
match 10 domain-name www.example.com
LB class: lbc5
Description:
Type: MySQL
Match type: Match-any
Match rule:
match 1 class cla2
match 2 source ip address 1.2.3.0 24
match 3 source ipv6 address 1::12
match 4 acl ipv4 number 3002
match 5 acl ipv6 number 3003
match 6 acl ipv4 name ccc
match 7 acl ipv6 name ddd
match 8 sql select
Table 2 Command output
|
Field |
Description |
|
LB class |
LB class name. |
|
Description |
Description for the LB class. |
|
Type |
LB class type: · DNS. · Generic. · HTTP. · Link-generic. · MySQL. · RADIUS. |
|
Match type |
Match type for the LB class: · Match-all—Requires matching all rules of the LB class. · Match-any—Requires matching any rule of the LB class. |
|
Match rule |
Match rules for the LB class. |
display loadbalance dns-proxy
Use display loadbalance dns-proxy to display transparent DNS proxy information.
Syntax
display loadbalance dns-proxy [ brief | name dns-proxy-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
brief: Displays brief transparent DNS proxy information. If you do not specify this keyword, the command displays detailed transparent DNS proxy information.
name dns-proxy-name: Specifies a transparent DNS proxy by its name, a case-insensitive string of 1 to 63 characters. If you do not specify this option, the command displays information about all transparent DNS proxies.
Examples
# Display brief information about all transparent DNS proxies.
<Sysname> display loadbalance dns-proxy brief
DNS proxy State Type VPN instance IP address Port
dns-proxy1 Active UDP 1.2.3.0/24 53
dns-proxy2 Inactive UDP -- 5353
# Display information about transparent DNS proxy dns-proxy1.
<Sysname> display loadbalance dns-proxy name dns-proxy1
DNS proxy: dns-proxy1
Type: UDP
State: Active
Service state: Enabled
VPN instance:
IPv4 address: 1.2.3.0/24
IPv6 address: --
Port: 53
DNS server pool: dns-pool1
Sticky: st
LB policy: dns-policy1
Connection synchronization: Enabled
Sticky synchronization: Enabled
Bandwidth busy protection: Disabled
Table 3 Command output
|
Field |
Description |
|
DNS proxy |
Transparent DNS proxy name. |
|
Type |
Transparent DNS proxy type. Only UDP is supported. |
|
State |
Transparent DNS proxy state: · Active—The transparent DNS proxy is available. · Inactive—The transparent DNS proxy is unavailable for any reason except that the transparent DNS proxy feature is disabled. · Inactive (disabled)—The transparent DNS proxy is unavailable because the transparent DNS proxy feature is disabled. |
|
Service state |
Transparent DNS proxy state: Enabled or Disabled. |
|
VPN instance |
VPN instance to which the transparent DNS proxy belongs. |
|
DNS server pool |
Default DNS server pool used by the transparent DNS proxy. |
|
Sticky |
Sticky group used by the transparent DNS proxy. |
|
Connection synchronization |
Session extension information synchronization state: Enabled or Disabled. |
|
Sticky synchronization |
Sticky entry synchronization state: Enabled or Disabled. |
|
Bandwidth busy protection |
Link protection state: Enabled or Disabled. |
display loadbalance dns-proxy statistics
Use display loadbalance dns-proxy statistics to display transparent DNS proxy statistics.
Syntax
In standalone mode:
display loadbalance dns-proxy statistics [ name dns-proxy-name ]
In IRF mode:
display loadbalance dns-proxy statistics [ name dns-proxy-name ] [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name dns-proxy-name: Specifies a transparent DNS proxy by its name, a case-insensitive string of 1 to 63 characters. If you do not specify this option, the command displays statistics for all transparent DNS proxies.
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays transparent DNS proxy statistics for all member devices. (In IRF mode.)
Examples
# Display statistics for the transparent DNS proxy dns-proxy1.
<Sysname> display loadbalance dns-proxy statistics name dns-proxy1
DNS proxy: dns-proxy1
Received requests: 100
Dropped requests: 2
Received responses: 98
Dropped responses: 0
Table 4 Command output
|
Field |
Description |
|
DNS proxy |
Transparent DNS proxy name. |
|
Received requests |
Number of DNS requests received by the transparent DNS proxy. |
|
Dropped requests |
Number of DNS requests dropped by the transparent DNS proxy. |
|
Received responses |
Number of DNS responses received by the transparent DNS proxy. |
|
Dropped responses |
Number of DNS responses dropped by the transparent DNS proxy. |
display loadbalance dns-server
Use display loadbalance dns-server to display DNS server information or DNS server pool member information.
Syntax
display loadbalance dns-server [ brief | name dns-server-name ]
display loadbalance dns-server dns-server-pool dns-server-pool-name [ name dns-server-name port port-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
brief: Displays brief DNS server information. If you do not specify this keyword, the command displays detailed DNS server information.
name dns-server-name: Displays detailed information about a DNS server. The dns-server-name argument specifies a DNS server by its name, a case-insensitive string of 1 to 63 characters.
dns-server-pool dns-server-pool-name: Displays information about members of a DNS server pool. The dns-server-pool-name argument specifies a DNS server pool by its name, a case-insensitive string of 1 to 63 characters.
dns-server dns-server-name port port-number: Displays information about a DNS server pool member. The dns-server-name argument specifies a DNS server pool member by its name, a case-insensitive string of 1 to 63 characters. The port-number argument specifies the port number of the DNS server pool member, in the range of 0 to 65535. If you do not specify this option, the command displays information about all members of a DNS server pool.
Usage guidelines
If you do not specify any parameter, the command displays detailed information about all DNS servers.
If the device obtains multiple DNS server IP addresses, it uses the smallest available IP address.
If no health monitoring method is specified, the device determines that all obtained DNS server IP addresses are available. If a health monitoring method is specified, the device determines that only the DNS server IP addresses that pass health monitoring are available.
Examples
# Display brief information about all DNS servers.
<Sysname> display loadbalance dns-server brief
(*) – Auto-alloc address using
DNS server Address Port Link State DNS server pool
ds1 10.150.100.100(*) 0 link1 Active dns_pool
ds2 20.150.100.100 5353 link2 Probe-failed dns_pool
ds3 -- 0 link3 Inactive dns_pool
ds4 --(*) 0 link3 Inactive dns_pool
# Display detailed information about DNS server ds1.
<Sysname> display loadbalance dns-server name ds1
(*) – Auto-alloc address using
dns-server: ds1
Description:
State: Active
VPN instance: --
Auto-alloc address: Enabled
IPv4 address: 10.150.100.100(*)
10.160.100.1
10.154.60.2
IPv6 address: --
Port: 0 (port number in original packet)
Link: link1
DNS server pool: dns-pool
Weight: 100
Priority: 4
Probe information:
Probe success criteria: All
Probe method State
t4 Succeeded
# Display information about all members of DNS server pool dsp1.
<Sysname> display loadbalance dns-server dns-server-pool dsp1
DNS server pool: dsp1
dns-server: ds1
Description: DNS server 1
Parent state: Inactive
State: Inactive
Port: 0 (port number in original packet)
Weight: 2
Priority: 2
Probe success criteria: All
Probe method State
icmp Failed
dns-server: rs2
Description: DNS server 2
Parent state: Inactive
State: Inactive
Port: 53
Weight: 100
Priority: 4
Probe information:
Probe success criteria: All
Probe method State
DNS Failed
Table 5 Command output
|
Field |
Description |
|
DNS server |
DNS server name. |
|
Address |
IP address of the DNS server. The asterisk (*) indicates that the IP address is automatically obtained and is being used. If all obtained IP addresses are unavailable, this field displays --(*). If no IP address is obtained and no IP address is manually configured, this field displays two hyphens (--). |
|
Link |
Link of the DNS server. |
|
Parent state/State |
DNS server state/DNS server pool member state: · Active—The DNS server is available. · Busy—The DNS server is busy. When the DNS server is in Active state and enabled with the link protection feature, this field displays Busy if the maximum expected bandwidth is reached. · Inactive—The DNS server is unavailable, because the configuration is not complete or the server is not referenced. · Probe-failed—Health monitoring has failed. · Unknown—Health monitoring is not configured. |
|
Description |
Description for the DNS server. |
|
Auto-alloc address |
Whether the device is enabled to automatically obtain the IP address of a DNS server: Disabled or Enabled. |
|
IPv4 address |
IPv4 address of the DNS server. |
|
IPv6 address |
IPv6 address of the DNS server. |
|
Port |
Port number of the DNS server. 0 means the port number in the packet is used. |
|
Weight |
Weight of the DNS server. |
|
Priority |
Priority of the DNS server. |
|
Probe information |
Detailed health monitoring information for the DNS server. |
|
Probe success criteria |
Health monitoring success criteria for the DNS server: · All—Health monitoring succeeds only when all the specified health monitoring methods succeed. · At least—Health monitoring succeeds when a specified minimum number of health monitoring methods succeed. |
|
Probe method |
Name of the NQA template used by the health monitoring method. |
|
State |
State of the health monitoring method: · Failed—Health monitoring has failed. · In progress—Health monitoring is in progress. · Invalid—Health monitoring is unavailable (because the configuration of the NQA template is not complete), or the DNS server is unavailable. · Succeeded—Health monitoring has succeeded. |
display loadbalance dns-server statistics
Use display loadbalance dns-server statistics to display DNS server statistics or DNS server pool member statistics.
Syntax
In standalone mode:
display loadbalance dns-server statistics [ name dns-server-name ]
display loadbalance dns-server statistics dns-server-pool dns-server-pool-name [ name dns-server-name port port-number ]
In IRF mode:
display loadbalance dns-server statistics [ name dns-server-name ] [ slot slot-number ]
display loadbalance dns-server statistics dns-server-pool dns-server-pool-name [ name dns-server-name port port-number ] [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name dns-server-name: Specifies a DNS server by its name, a case-insensitive string of 1 to 63 characters. If you do not specify this option, the command displays statistics for all DNS servers.
dns-server-pool dns-server-pool-name: Displays statistics for members of a DNS server pool. The dns-server-pool-name argument specifies a DNS server pool by its name, a case-insensitive string of 1 to 63 characters.
dns-server dns-server-name port port-number: Displays statistics for a DNS server pool member. The dns-server-name argument specifies a DNS server pool member by its name, a case-insensitive string of 1 to 63 characters. The port-number argument specifies the port number of the DNS server pool member, in the range of 0 to 65535. If you do not specify this option, the command displays statistics for all members of a DNS server pool.
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays DNS server statistics for all member devices. (In IRF mode.)
Examples
# Display statistics for the DNS server ds1.
<Sysname> display loadbalance dns-server statistics name ds1
DNS server: ds1
Received requests: 100
Send requests: 98
Dropped requests: 2
Received responses: 98
Send responses: 98
Dropped responses: 0
# Display statistics for all members of DNS server pool dsp1.
<Sysname> display loadbalance dns-server statistics dns-server-pool dsp1
DNS server pool: dsp1
DNS server (port: 20): ds1
Received requests: 100
Dropped requests: 2
Sent responses: 98
Dropped responses: 0
DNS server (port: 28): ds2
Received requests: 100
Dropped requests: 0
Sent responses: 100
Dropped responses: 0
Table 6 Command output
|
Field |
Description |
|
DNS server |
DNS server name. |
|
Received requests |
Number of DNS requests received by the DNS server. |
|
Send requests |
Number of DNS requests sent by the DNS server. |
|
Dropped requests |
Number of DNS requests dropped by the DNS server. |
|
Received responses |
Number of DNS responses received by the DNS server. |
|
Send responses |
Number of DNS responses sent by the DNS server. |
|
Dropped responses |
Number of DNS responses dropped by the DNS server. |
display loadbalance dns-server-pool
Use display loadbalance dns-server-pool to display DNS server pool information.
Syntax
display loadbalance dns-server-pool [ brief | name pool-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
brief: Displays brief DNS server pool information. If you do not specify this keyword, the command displays detailed DNS server pool information.
name pool-name: Displays detailed information about a DNS server pool. The pool-name argument specifies a DNS server pool by its name, a case-insensitive string of 1 to 63 characters.
Usage guidelines
If you do not specify any parameter, the command displays detailed information about all DNS server pools.
Examples
# Display brief information about all DNS server pools.
<Sysname> display loadbalance dns-server-pool brief
Predictor: RR - Round robin, RD - Random,
BW - Bandwidth, MBW - Max bandwidth,
IBW - Inbound bandwidth, OBW - Outbound bandwidth,
MIBW - Max inbound bandwidth, MOBW - Max outbound bandwidth,
HASH(SIP) - Hash address source IP,
HASH(DIP) - Hash address destination IP,
HASH(SIP-PORT) - Hash address source IP-port
DNS server pool Predictor Total Active
dns-pool RR 3 2
dns-pool1 RR 0 0
dns-pool2 RD 3 0
# Display detailed information about DNS server pool dns-pool.
<Sysname> display loadbalance dns-server-pool name dns-pool
DNS server pool: dns-pool
Description:
Predictor: Round robin
Selected server: Enabled
Min servers: 3
Max servers: 5
Probe information:
Probe success criteria: At-least 2
Probe method: t4
Total DNS servers: 3
Active DNS servers: 0
DNS server list:
Name State Address port Link Weight Priority
ds1 Active 10.150.100.100 0 link1 100 4
ds2 Probe-failed 20.150.100.100 5353 link2 100 4
ds3 Inactive -- 0 link3 100 4
Table 7 Command output
|
Field |
Description |
|
Predictor |
Scheduling algorithm of the DNS server pool: · RR—Weighted round robin algorithm. · RD—Random algorithm. · BW—Bandwidth algorithm. · IBW—Inbound bandwidth algorithm. · OBW—Outbound bandwidth algorithm. · MBW—Maximum bandwidth algorithm. · MIBW—Maximum inbound bandwidth algorithm. · MOBW—Maximum outbound bandwidth algorithm. · HASH(SIP)—Hash algorithm based on source IP address. · HASH(DIP)—Hash algorithm based on destination IP address. · HASH(SIP-PORT)—Hash algorithm based on source IP address and port number. |
|
DNS server pool |
DNS server pool name. |
|
Total |
Total number of DNS servers. |
|
Active |
Number of active DNS servers. |
|
Description |
Description for the DNS server pool. |
|
Selected server |
State of DNS server limit to participate in scheduling: disabled or enabled. If the state is enabled, the following fields are displayed: · Min servers—Minimum number of DNS servers that can participate in scheduling. · Max servers—Maximum number of DNS servers that can participate in scheduling. |
|
Probe information |
Detailed health monitoring information for the DNS server pool. |
|
Probe success criteria |
Health monitoring success criteria for the DNS server pool: · All—Health monitoring succeeds only when all the specified health monitoring methods succeed. · At least—Health monitoring succeeds when a specified minimum number of health monitoring methods succeed. |
|
Probe method |
Name of the NQA template used by the health monitoring method. |
|
Total DNS servers |
Total number of DNS servers. |
|
Active DNS servers |
Number of active DNS servers. |
|
Name |
DNS server name. |
|
State |
DNS server state: · Active—The DNS server is available. · Busy—The DNS server is busy. When the DNS server is in Active or Ramp state and enabled with link protection, this field displays Busy if the maximum expected bandwidth is reached. · Inactive—The DNS server is unavailable, because the configuration is not complete or the server is not referenced. · Probe-failed—Health monitoring has failed. |
|
Address |
IP address of the DNS server. The asterisk (*) indicates that the IP address is automatically obtained and is being used. If all obtained IP addresses are unavailable, this field displays --(*). If no IP address is obtained and no IP address is manually configured, this field displays two hyphens (--). |
|
Port |
Port number of the DNS server. |
|
Link |
Name of the link corresponding to the DNS server. |
|
Weight |
Weight of the DNS server. |
|
Priority |
Priority of the DNS server. |
display loadbalance hot-backup statistics
Use display loadbalance hot-backup statistics to display LB hot backup statistics.
Syntax
In IRF mode:
display loadbalance hot-backup statistics [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays LB hot backup statistics for all member devices. (In IRF mode.)
Examples
# Display LB hot backup statistics.
<Sysname> display loadbalance hot-backup statistics
Slot 2:
TryAdd TryDel AckDel AckOK AckNO NotSpt
StiSnd 1 0 0 0 0 0
StiRcv 0 0 0 0 0 0
StiSndFail 0 0 0 0 0 0
StiRcvFail 0 0 0 0 0 0
MsgSnd 1 0 0 0 0 0
MsgRcv 0 0 0 0 0 0
MsgSndFail 0 0 0 0 0 0
MsgRcvFail 0 0 0 0 0 0
MAllocFail 0 0 0 0 0 0
SesBkTotal : 0
SesBkFail : 0
SesResTotal: 0
SesResFail : 0
SesUpdate : 0
Table 8 Command output
|
Field |
Description |
|
Message for adding sticky entries. |
|
|
Message for deleting sticky entries. |
|
|
Message for acknowledging the deletion of sticky entries. |
|
|
Message indicating the sticky entries that can be deleted. |
|
|
Message indicating the sticky entries that cannot be deleted. |
|
|
Message indicating the unsupported sticky entries. |
|
|
Number of sent sticky entries. |
|
|
Number of received sticky entries. |
|
|
Number of sticky entry sending failures. |
|
|
Number of sticky entry receiving failures. |
|
|
Number of sent messages. |
|
|
Number of received messages. |
|
|
Number of message sending failures. |
|
|
Number of message receiving failures. |
|
|
MAllocFail |
Number of memory application failures. |
|
Number of session backups. |
|
|
Number of session backup failures. |
|
|
Number of session restorations. |
|
|
Number of session restoration failures. |
|
|
Number of session updates. |
display loadbalance link
Use display loadbalance link to display LB link information or link group member information.
Syntax
display loadbalance link [ brief | name link-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
brief: Displays brief information about all LB links. If you do not specify this keyword, the command displays detailed LB link information.
name link-name: Displays detailed information about the specified LB link. The link-name argument specifies an LB link name, a case-insensitive string of 1 to 63 characters.
Usage guidelines
If you do not specify the brief keyword or the name link-name option, the command displays detailed information about all LB links.
Examples
# Display brief information about all LB links.
<Sysname> display loadbalance link brief
Link Router IP/Interface State VPN instance Link group
Lk1 192.168.1.1 Busy -- lg
Lk2 192.168.2.1 Active -- lg
Lk3 Dialer0 Inactive -- lg
# Display detailed information about the LB link lk.
<Sysname> display loadbalance link name lk
Link: lk
Description: lk
State: Busy
VPN instance: --
Inherit VPN: Disabled
Router IP: 1.2.3.4
Router IPv6: --
Link-group: lg
Weight: 100
Priority: 4
Cost: 0
Slow-shutdown: Disabled
Connection limit: 0
Rate limit:
Connections: 10000
Bandwidth: 10000 kbps
Inbound bandwidth: 5000 kbps
Outbound bandwidth: 5000 kbps
Bandwidth busy:
Max bandwidth: 10000 kbps
Max inbound bandwidth: 5000 kbps
Max outbound bandwidth: 5000 kbps
Busy rate: 80
Inbound busy rate: 70
Outbound busy rate: 60
Busy recovery rate: 60
Inbound busy recovery rate: 60
Outbound busy recovery rate: 60
Probe information:
Probe success criteria: All
Probe method State
t4 Inactive
Link: lk2
Description: link2
State: Inactive
VPN instance: --
Inherit VPN: Disabled
IPv4 address state: Active
IPv6 address state: Inactive
Router interface: Dialer0
Link group: lg
Weight: 150
Priority: 3
Cost: 100
Slow shutdown: Enabled
Connection limit: 10000
Rate limit:
Connections: 10000
Bandwidth: 10000 kbps
Inbound bandwidth: 5000 kbps
Outbound bandwidth: 5000 kbps
Bandwidth busy:
Max bandwidth: 10000 kbps
Max inbound bandwidth: 5000 kbps
Max outbound bandwidth: 5000 kbps
Busy rate: 80
Inbound busy rate: 70
Outbound busy rate: 60
Busy recovery rate: 60
Inbound busy recovery rate: 60
Outbound busy recovery rate: 60
Probe information:
Probe success criteria: All
Probe method State
t4 Inactive
# Display information about all members of link group lg.
<Sysname> display loadbalance link link-group lg
Link group: lg
Link: lk1
Description: link 1
Parent state: Inactive
State: Inactive
Weight: 2
Priority: 2
Slow shutdown: Disabled
Connection limit: --
Connection rate limit: --
Probe information:
Probe success criteria: All
Probe method State
icmp Failed
Link: lk2
Description: link 2
Parent state: Inactive
State: Inactive
Weight: 100
Priority: 4
Slow shutdown: Disabled
Connection limit: --
Connection rate limit: --
Probe information:
Probe success criteria: All
Probe method State
tcp Failed
Table 9 Command output
|
Field |
Description |
|
Link |
LB link name. |
|
Router IP/Interface |
Gateway IP address or outgoing interface of the LB link. |
|
Parent state/State |
LB link state/Link group member state: · Active—The LB link is available. · Busy—The LB link is busy. · Inactive—The LB link is unavailable, because the configuration is not complete, the LB link is not referenced, or the virtual server is not enabled. · Probe-failed—Health monitoring has failed. · Ramp—Ramp-up phase of slow online. · Shutdown—The LB link is shut down. · Standby—Standby phase of slow online. · Unknown—Health monitoring is not configured. |
|
VPN instance |
VPN instance of the LB link. · Config—Manually configured. · Inherit—Inherited. |
|
Link group |
Link group to which the LB link belongs. |
|
Description |
Description for the LB link. |
|
Inherit VPN |
State of VPN instance inheritance: Enabled or Disabled. |
|
IPv4 address state |
IPv4 address state of the LB link: · Active—An available IPv4 address is obtained through the outgoing interface of the LB link. · Inactive—No available IPv4 address is obtained through the outgoing interface of the LB link. This field is displayed only if an outgoing interface is specified for an LB link. |
|
IPv6 address state |
IPv6 address state of the link: · Active—An available IPv6 address is obtained through the outgoing interface of the LB link. · Inactive—No available IPv6 address is obtained through the outgoing interface of the LB link. This field is displayed only if an outgoing interface is specified for an LB link. |
|
Weight |
Weight of the LB link. |
|
Priority |
Priority of the LB link. |
|
Cost |
Cost for proximity calculation. |
|
Slow shutdown |
Slow shutdown state of the LB link: · Disabled. · Enabled. |
|
Connection limit |
Maximum number of connections for the LB link. |
|
Connection rate limit |
Maximum number of connections per second for the LB link. |
|
Rate limit |
Rate limit of the LB link. |
|
Connections |
Maximum number of connections per second for the LB link. |
|
Bandwidth |
Maximum bandwidth for the LB link in kbps. |
|
Inbound bandwidth |
Maximum inbound bandwidth for the LB link in kbps. |
|
Outbound bandwidth |
Maximum outbound bandwidth for the LB link in kbps. |
|
Bandwidth busy |
Bandwidth ratio. |
|
Max bandwidth |
Maximum expected bandwidth for the LB link in kbps. |
|
Max inbound bandwidth |
Maximum inbound expected bandwidth for the LB link in kbps. |
|
Max outbound bandwidth |
Maximum outbound expected bandwidth for the LB link in kbps. |
|
Busy rate |
Bandwidth ratio for the LB link. |
|
Inbound busy rate |
Inbound bandwidth ratio for the LB link. |
|
Outbound busy rate |
Outbound bandwidth ratio for the LB link. |
|
Busy recovery rate |
Bandwidth recovery ratio for the LB link. |
|
Inbound busy recovery rate |
Inbound bandwidth recovery ratio for the LB link. |
|
Outbound busy recovery rate |
Outbound bandwidth recovery ratio for the LB link. |
|
Probe information |
Detailed health monitoring information for the LB link. |
|
Probe success criteria |
Health monitoring success criteria for the LB link: · All—Health monitoring succeeds only when all the specified health monitoring methods succeed. · At least—Health monitoring succeeds when a specified minimum number of health monitoring methods succeed. |
|
Probe method |
Name of the NQA template used by the health monitoring method. |
|
State |
State of the health monitoring method: · Failed—Health monitoring has failed. · In progress—Health monitoring is in progress. · Invalid—Health monitoring is unavailable (because the configuration of the NQA template is not complete), or the real server is unavailable. · Succeeded—Health monitoring has succeeded. |
display loadbalance link statistics
Use display loadbalance link statistics to display link statistics or link group member statistics.
Syntax
In standalone mode:
display loadbalance link statistics [ name link-name ]
In IRF mode:
display loadbalance link statistics [ name link-name ] [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name link-name: Specifies a link by its name, a case-insensitive string of 1 to 63 characters.
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays link statistics for all member devices. (In IRF mode.)
Examples
# Display statistics for the link lk1.
<Sysname> display loadbalance link statistics name lk1
Loadbalance link: lk1
Total connections: 1798
Active connections: 788
Max connections: 803
recorded at 11:02:49 on Tue May 21 2019
Connections per second: 157
Max connections per second: 163
recorded at 11:02:49 on Tue May 21 2019
Downstream traffic: 333332 bytes
Upstream traffic: 472054 bytes
Throughput: 4396 bps
Inbound throughput: 1214 bps
Outbound throughput: 3128 bps
Max throughput: 4564 bps
recorded at 11:02:49 on Tue May 21 2019
Max inbound throughput: 1214 bps
recorded at 11:02:49 on Tue May 21 2019
Max outbound throughput: 3320 bps
recorded at 11:02:49 on Tue May 21 2019
Received packets: 1798
Sent packets: 0
Dropped packets: 0
Received packets per second: 0
Sent packets per second: 0
Packet loss rate: 10
Table 10 Command output
|
Field |
Description |
|
Loadbalance link |
Link name. |
|
Total connections |
Total number of connections. |
|
Active connections |
Number of active connections. |
|
Max connections |
Maximum number of connections. |
|
Connections per second |
Number of connections per second. |
|
Max connections per second |
Maximum number of connections per second. |
|
Downstream traffic |
Downstream traffic (in bytes) received by the LB device. |
|
Upstream traffic |
Upstream traffic (in bytes) sent by the LB device. |
|
Throughput |
Total packet throughput in bps. |
|
Inbound throughput |
Inbound packet throughput in bps. |
|
Outbound throughput |
Outbound packet throughput in bps. |
|
Max throughput |
Maximum packet throughput in bps. |
|
Max inbound throughput |
Maximum inbound packet throughput in bps. |
|
Max outbound throughput |
Maximum outbound packet throughput in bps. |
|
Received packets |
Number of received packets. |
|
Sent packets |
Number of sent packets. |
|
Dropped packets |
Number of dropped packets. |
|
Packet loss rate |
Packet loss ratio of the link. |
display loadbalance policy
Use display loadbalance policy to display LB policy information.
Syntax
display loadbalance policy [ name policy-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name policy-name: Specifies an LB policy by its name, a case-insensitive string of 1 to 63 characters. If you do not specify this option, the command displays information about all LB policies.
Examples
# Display information about all LB policies.
<Sysname> display loadbalance policy
LB policy: lbp1
Description:
Type: Generic
Class: lbc1
Action: lba1
Default action: lba0
LB policy: lbp2
Description:
Type: HTTP
Default action:
LB policy: lbp3
Description:
Type: Link-generic
Class: lbc3
Action: lba3
Default action: lba3
LB policy: lbp4
Description:
Type: DNS
Class: lbc4
Action: lba4
Default action: lba4
LB policy: lbp5
Description:
Type: MySQL
Class: lbc5
Action: lba5
Default action: lba5
Table 11 Command output
|
Field |
Description |
|
LB policy |
LB policy name. |
|
Description |
Description for the LB policy. |
|
Type |
LB policy type: · DNS. · Generic. · HTTP. · Link-generic. · MySQL. · RADIUS. |
|
Class |
LB class for the LB policy. |
|
Action |
LB action for the LB class. |
|
Default class action |
Default LB action. |
display sticky dns-proxy
Use display sticky dns-proxy to display sticky entry information for transparent DNS proxies.
Syntax
In standalone mode:
display sticky dns-proxy [ dns-proxy-name dns-proxy-name ] [ class { class-name | default-class } | client-addr { ipv4-address | ipv6-address } | dns-server-addr { ipv4-address | ipv6-address } | dns-server-pool pool-name | dns-server-port port-number | key sticky-key ] * [ brief ]
In IRF mode:
display sticky dns-proxy [ dns-proxy-name dns-proxy-name ] [ class { class-name | default-class } | client-addr { ipv4-address | ipv6-address } | dns-server-addr { ipv4-address | ipv6-address } | dns-server-pool pool-name | dns-server-port port-number | key sticky-key ] * [ brief ] [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
dns-proxy dns-proxy-name: Specifies a transparent DNS proxy by its name, a case-insensitive string of 1 to 63 characters. If you do not specify this option, the command displays sticky entry information for all transparent DNS proxies.
class { class-name | default-class }: Specifies an LB class by its name, a case-insensitive string of 1 to 63 characters, or specifies the default LB class.
client-addr { ipv4-address | ipv6-address }: Specifies a client by its IPv4 or IPv6 address.
dns-server-addr { ipv4-address | ipv6-address }: Specifies a DNS server by its IPv4 or IPv6 address.
dns-server-pool pool-name: Specifies a DNS server pool by its name, a case-insensitive string of 1 to 63 characters.
dns-server-port port-number: Specifies a DNS server port number in the range of 0 to 65535.
key sticky-key: Specifies a key value, a case-sensitive string of 1 to 36 characters.
brief: Displays brief information about sticky entries. If you do not specify this keyword, the command displays detailed information about sticky entries.
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays sticky entry information for all member devices. (In IRF mode.)
Examples
# Display detailed sticky entry information for all transparent DNS proxies.
<Sysname> display sticky dns-proxy
DNS proxy name: dsp1
DNS server pool name: dns-pool
Class: cl
Sticky type: Address-port
Sticky method: Source IP
Sticky key: 3.0.0.13
DNS proxy addr: 33.44.1.1:80
DNS server addr: 7.0.0.7:80
Client addr: 3.0.0.1
Timeout: 100 sec
Expiration time: 58 sec
# Display brief sticky entry information for all transparent DNS proxies.
<Sysname> display sticky dns-proxy brief
Sticky type Sticky method Sticky key DNS proxy DNS server addr
Address-port Src IP 3.0.0.13 dsp1 7.0.0.7:80
Address-port Src IP 3.0.0.15 dsp2 7.0.0.8:80
Table 12 Command output
|
Field |
Description |
|
Sticky group name |
Name of the sticky group that generates the sticky entries. |
|
Sticky method |
Sticky method corresponding to the sticky entries: · Src IP—Source IPv4 address sticky method. · Src IPv6—Source IPv6 address sticky method. · Src IP and port—Source IPv4 address + source port sticky method. · Src IPv6 and port—Source IPv6 address + source port sticky method. · Dst IP—Destination IPv4 address sticky method. · Dst IPv6—Destination IPv6 address sticky method. · Dst IP and port—Destination IPv4 address + destination port sticky method. · Dst IPv6 and port—Destination IPv6 address + destination port sticky method. · Both IP—Source IPv4 address + destination IPv4 address sticky method. · Both IPv6—Source IPv6 address + destination IPv6 address sticky method. · Both IP and port—Source IPv4 address + source port + destination IPv4 address + destination port sticky method. · Both IPv6 and port—Source IPv6 address + source port + destination IPv6 address + destination port sticky method. |
|
Sticky key |
Key value corresponding to the sticky entry. |
|
Timeout |
Configured timeout time for sticky entries, in seconds. |
|
Expiration time |
Remaining lifetime of the sticky entry, in seconds. |
display sticky-group
Use display sticky-group to display sticky group information.
Syntax
display sticky-group [ name group-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name group-name: Specifies a sticky group by its name, a case-insensitive string of 1 to 63 characters. If you do not specify this option, the command displays information about all sticky groups.
Examples
# Display information about all sticky groups.
<Sysname> display sticky-group
Sticky group: sg1
Description:
Timeout: 60
Override limit: Disabled
Stickiness-over-busyness: Enabled
Matching across services: Enabled
Matching across virtual servers: Enabled
Sticky group type: Address-port
Method: Both IP and port
Mask: 32
Sticky group: sg2
Description:
Timeout: 60
Override limit: Disabled
Stickiness-over-busyness: Enabled
Sticky group type: HTTP header
Method: HTTP header name
Name: accept-encoding
Offset: 4
Start: gzip
Length: 10
Sticky group: sg3
Description:
Timeout: 60
Override limit: Disabled
Stickiness-over-busyness: Enabled
Sticky group type: RADIUS
Method: User-Name
Sticky group: sg4
Description:
Timeout: 86400
Override limit: Disabled
Stickiness-over-busyness: Disabled
Sticky group type: HTTP cookie
Method: HTTP cookie insert
Name: X-LB
Domain: example.com
Path: /test1
HttpOnly: Enabled
Secure: Enabled
Check all packets: Disabled
Table 13 Command output
|
Field |
Description |
|
Sticky group |
Sticky group name. |
|
Description |
Description for the sticky group. |
|
Timeout |
Timeout time for sticky entries in seconds. The value Infinite indicates that sticky entries never age out. |
|
Override limit |
Whether the feature of ignoring the limits for sessions that match sticky entries is enabled: Enabled or Disabled. |
|
Stickiness-over-busyness |
Whether the stickiness-over-busyness feature is enabled: Enabled or Disabled. |
|
Sticky group type |
Sticky group type: · Address-port—Address and port. · HTTP content—HTTP entity. · HTTP cookie. · HTTP header. · HTTP passive. · Payload—HTTP or UDP payload. · RADIUS. · SIP. · SSL. · UDP passive. · TCP payload. |
Table 14 Detailed information for sticky groups
|
Sticky group type |
Field |
Description |
|
Address-port |
Method |
Sticky method: · Source IP—Source IPv4 address sticky method. · Source IPv6—Source IPv6 address sticky method. · Source IP and port—Source IPv4 address + source port sticky method. · Source IPv6 and port—Source IPv6 address + source port sticky method. · Destination IP—Destination IPv4 address sticky method. · Destination IPv6—Destination IPv6 address sticky method. · Destination IP and port—Destination IPv4 address + destination port sticky method. · Destination IPv6 and port—Destination IPv6 address + destination port sticky method. · Both IP—Source IPv4 address + destination IPv4 address sticky method. · Both IPv6—Source IPv6 address + destination IPv6 address sticky method. · Both IP and port—Source IPv4 address + source port + destination IPv4 address + destination port sticky method. · Both IPv6 and port—Source IPv6 address + source port + destination IPv6 address + destination port sticky method. |
|
Mask |
Mask length for the sticky method. This field is displayed only for IPv4 sticky methods. |
|
|
Prefix |
Prefix length for the sticky method. This field is displayed only for IPv6 sticky methods. |
|
|
HTTP content |
Offset |
Offset value of the entity based on the start of the HTTP packet. |
|
Start |
Regular expression that marks the start of the entity. |
|
|
End |
Regular expression that marks the end of the entity. Either this field or the Length field is displayed, but not both of them. |
|
|
Length |
Length of the entity. Either this field or the End field is displayed, but not both of them. |
|
|
HTTP cookie |
Method |
Sticky method: · HTTP cookie insert—Cookie insert sticky method. · HTTP cookie rewrite—Cookie rewrite sticky method. · HTTP cookie get—Cookie get sticky method. This field is displayed only for the HTTP cookie sticky method. |
|
Name |
HTTP cookie name. This field is displayed only for the HTTP cookie sticky method. |
|
|
Domain |
Domain scope of the cookie. This field is displayed only for the HTTP cookie insert sticky method. |
|
|
Path |
Path scope of the cookie. This field is displayed only for the HTTP cookie insert sticky method. |
|
|
Offset |
Offset value based on the start of the cookie value. This field is displayed only for the cookie insert sticky method. |
|
|
Start |
Regular expression that marks the start of the cookie. This field is displayed only for the cookie insert sticky method. |
|
|
End |
Regular expression that marks the end of the cookie. Either this field or the Length field is displayed, but not both of them. This field is displayed only for the cookie insert sticky method. |
|
|
Length |
Length of the cookie. Either this field or the End field is displayed, but not both of them. This field is displayed only for the cookie insert sticky method. |
|
|
Cookie secondary name |
Name of the secondary cookie to be searched in the URI. This field is displayed only for the cookie insert sticky method. |
|
|
HttpOnly |
HttpOnly attribute of the cookie. This field is displayed only for the HTTP cookie insert or cookie rewrite sticky method. |
|
|
Secure |
Secure attribute of the cookie. This field is displayed only for the HTTP cookie insert or cookie rewrite sticky method. |
|
|
Check all packets |
Whether or not to enable checking for all packets. |
|
|
HTTP header |
Method |
Sticky method: · HTTP host—HTTP host based sticky method. · HTTP header name—HTTP header name based sticky method. · HTTP method—HTTP Request-Method based sticky method. · HTTP URL—HTTP URL based sticky method. · HTTP version—HTTP version based sticky method. This field is displayed only for the HTTP header sticky method. |
|
Name |
HTTP header name. This field is displayed only for the HTTP header name based sticky method. |
|
|
Offset |
Offset value of the HTTP header based on the start of the HTTP packet. This field is displayed only for the HTTP host or URL based sticky method. |
|
|
Start |
Regular expression that marks the start of the HTTP header. This field is displayed only for the HTTP host or URL based sticky method. |
|
|
End |
Regular expression that marks the end of the HTTP header. Either this field or the Length field is displayed, but not both of them. This field is displayed only for the HTTP host or URL based sticky method. |
|
|
Length |
Length of the HTTP header. Either this field or the End field is displayed, but not both of them. This field is displayed only for the HTTP host or URL based sticky method. |
|
|
Payload |
Offset |
Offset value of the HTTP or UDP payload based on the start of the HTTP packet. |
|
Start |
Regular expression that marks the start of the HTTP or UDP payload. |
|
|
End |
Regular expression that marks the end of the HTTP or UDP payload. Either this field or the Length field is displayed, but not both of them. . |
|
|
Length |
Length of the HTTP or UDP payload. Either this field or the End field is displayed, but not both of them. |
|
|
RADIUS |
Method |
Sticky method: · Framed-IP-Address—Sticky method based on the Framed-IP-Address attribute of RADIUS packets. · User-Name—Sticky method based on the User-Name attribute of RADIUS packets. · Code=attribute-code—Sticky method based on the attribute (specified by attribute-code) of RADIUS packets. This field is not displayed if no RADIUS attribute based sticky method is specified. |
|
SIP |
Method |
Sticky method, which can only be SIP Call-ID (SIP sticky method based on the Call-ID header field of SIP packets). |
|
SSL |
Method |
Sticky method, which can only be SSL session ID (SSL sticky method based on SSL session ID). This field is displayed only for the SSL sticky method based on SSL session ID. |
|
HTTP passive |
Method |
Sticky method: · HTTP header name—HTTP header name sticky method. · HTTP URL—HTTP URL sticky method. · HTTP content—HTTP content sticky method. |
|
Get |
Obtains the specified string in HTTP responses. |
|
|
Match |
Matches the specified string in HTTP requests. |
|
|
Name |
HTTP header name. This field is displayed only for the HTTP header name based sticky method. |
|
|
Start |
Regular expression that marks the start of the HTTP header. |
|
|
End |
Regular expression that marks the end of the HTTP header. Either this field or the Length field is displayed, but not both of them. |
|
|
Length |
Length of the HTTP header. Either this field or the End field is displayed, but not both of them. |
|
|
UDP passive |
Get |
Obtains the specified string in UDP responses. |
|
Match |
Matches the specified string in UDP requests. |
|
|
Start |
Regular expression that marks the start of the UDP payload. |
|
|
End |
Regular expression that marks the end of the UDP payload. Either this field or the Length field is displayed, but not both of them. |
|
|
Length |
Length of the UDP payload. Either this field or the End field is displayed, but not both of them. |
|
|
TCP payload |
Offset |
Offset value of the TCP payload based on the start of the TCP packet. |
|
Start |
Regular expression that marks the start of the TCP payload. |
|
|
End |
Regular expression that marks the end of the TCP payload. Either this field or the Length field is displayed, but not both of them. |
|
|
Length |
Length of the TCP payload. Either this field or the End field is displayed, but not both of them. |
dns-server (DNS server pool view)
Use dns-server to create a DNS server pool member and enter its view, or enter the view of an existing DNS server pool member.
Use undo dns-server to delete a DNS server pool member.
Syntax
dns-server dns-server-name port port-number
undo dns-server dns-server-name port port-number
Default
No DNS server pool members exist.
Views
DNS server pool view
Predefined user roles
network-admin
Parameters
dns-server-name: Specifies a DNS server pool member name, a case-insensitive string of 1 to 63 characters.
port-number: Specifies the port number of the DNS server pool member, in the range of 0 to 65535.
Usage guidelines
You can use one of the following methods to add a member to a DNS server pool:
· Use the dns-server command in DNS server pool view. H3C recommends using this method.
· Use the dns-server-pool command in DNS server view.
You cannot use both methods to add a member with the same DNS server name and port number to a DNS server pool.
Examples
# Add DNS server pool member ds1 and enter DNS server pool member view.
<Sysname> system-view
[Sysname] loadbalance dns-server-pool dsp1
[Sysname-lb-dspool-dsp1] dns-server ds1 port 10
[Sysname-lb-dspool-dsp1-#member#-ds1-port-10]
Related commands
dns-server-pool (DNS server view)
dns-server-pool (DNS server view)
Use dns-server-pool to specify a DNS server pool for a DNS server.
Use undo dns-server-pool to restore the default.
Syntax
dns-server-pool pool-name
undo dns-server-pool
Default
A DNS server does not belong to any DNS server pool.
Views
DNS server view
Predefined user roles
network-admin
Parameters
pool-name: Specifies a DNS server pool by its name, a case-insensitive string of 1 to 63 characters.
Usage guidelines
You can specify a DNS server pool that has not been created.
Examples
# Specify DNS server pool dns-pool1 for DNS server ds1.
<Sysname> system-view
[Sysname] loadbalance dns-server ds1
[Sysname-lb-ds-ds1] dns-server-pool dns-pool1
Related commands
display loadbalance dns-server
dns-server-pool (LB action view)
Use dns-server-pool to specify a DNS server pool for guiding packet forwarding.
Use undo dns-server-pool to restore the default.
Syntax
dns-server-pool pool-name [ sticky sticky-name ]
undo dns-server-pool
Default
No DNS server pool is specified for guiding packet forwarding.
Views
DNS LB action view
Predefined user roles
network-admin
Parameters
pool-name: Specifies a DNS server pool by its name, a case-insensitive string of 1 to 63 characters.
sticky sticky-name: Specifies a sticky group by its name, a case-insensitive string of 1 to 63 characters. If you do not specify a sticky group, the DNS server pool does not correspond to any sticky group.
Usage guidelines
This command is mutually exclusive with the forward all or skip current-dns-proxy command. If you configure one command, the other command (if configured) is automatically cancelled.
Examples
# Specify the DNS server pool dsp and the sticky group sg1 for DNS LB action lba1.
<Sysname> system-view
[Sysname] loadbalance action lba1 type dns
[Sysname-lba-dns-lba1] dns-server-pool dsp sticky st1
Related commands
forward all
fallback-action continue
Use fallback-action continue to match the next rule upon failure to find an available server.
Use undo fallback-action to restore the default.
Syntax
fallback-action continue
undo fallback-action
Default
Packets are dropped when no servers are available for the current LB action.
Views
LB action view
Predefined user roles
network-admin
Usage guidelines
This command enables packets to match the next rule in an LB policy when no servers are available for the current LB action.
This command does not apply to SIP virtual servers.
Examples
# Match the next rule upon failure to find a DNS server for the DNS LB action a2.
<Sysname> system-view
[Sysname] loadbalance action a2 type dns
[Sysname-lba-dns-a2] fallback-action continue
forward all
Use forward all to configure the packet forwarding mode.
Use undo forward to restore the default.
Syntax
forward all
undo forward
Default
The packet forwarding mode is to discard packets.
Views
DNS/Link-generic LB action view
Predefined user roles
network-admin
Usage guidelines
In DNS LB action view, this command is mutually exclusive with the dns-server-pool or skip current-dns-proxy command. In link-generic LB action view, the forward all and link-group commands are mutually exclusive. If you configure one command, the other command (if configured) is automatically cancelled.
This command does not apply to SIP virtual servers.
Examples
# In the transparent DNS proxy scenario, configure the packet forwarding mode for the DNS LB action lba3.
<Sysname> system-view
[Sysname] loadbalance action lba3 type dns
[Sysname-lba-dns-lba3] forward all
Related commands
dns-server-pool
ip
Use ip to configure the IPv4 sticky method.
Use undo ip to restore the default.
Syntax
ip [ port ] { both | destination | source } [ mask mask-length ]
undo ip
Default
No IPv4 sticky method is configured.
Views
Sticky group view
Predefined user roles
network-admin
Parameters
port: Specifies the sticky method as IPv4 address + port number. If you do not specify this keyword, the sticky method is IPv4 address.
both: Specifies the sticky method as source IPv4 address + destination IPv4 address (if you do not specify the port keyword), or source IPv4 address + source port number + destination IPv4 address + destination port number (if you specify the port keyword).
destination: Specifies the sticky method as destination IPv4 address if you do not specify the port keyword, or destination IPv4 address + destination port number if you specify the port keyword.
source: Specifies the sticky method as source IPv4 address if you do not specify the port keyword, or source IPv4 address + source port number if you specify the port keyword.
mask mask-length: Specifies the mask length for the sticky method.
Examples
# Configure the sticky method for the address and port-based sticky group sg1 as source IPv4 address.
<Sysname> system-view
[Sysname] sticky-group sg1 type address-port
[Sysname-sticky-address-port-sg1] ip source
# Configure the sticky method for the address and port-based sticky group sg1 as source IPv4 address + source port number.
<Sysname> system-view
[Sysname] sticky-group sg1 type address-port
[Sysname-sticky-address-port-sg1] ip port source
Related commands
sticky-group
ip address (DNS server view)
Use ip address to specify an IPv4 address for a DNS server.
Use undo ip address to restore the default.
Syntax
ip address ipv4-address
undo ip address
Default
No IPv4 address is specified for a DNS server.
Views
DNS server view
Predefined user roles
network-admin
Parameters
ipv4-address: Specifies an IPv4 address, which cannot be a loopback address, multicast address, broadcast address, or an address in the format of 0.X.X.X.
Usage guidelines
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Specify the IPv4 address for DNS server ds1 as 1.2.3.4.
<Sysname> system-view
[Sysname] loadbalance dns-server ds1
[Sysname-lb-ds-ds1] ip address 1.2.3.4
ip address (transparent DNS proxy view)
Use ip address to specify an IPv4 address for a transparent DNS proxy.
Use undo ip address to restore the default.
Syntax
ip address ipv4-address [ mask-length | mask ]
undo ip address
Default
No IPv4 address is specified for a transparent DNS proxy.
Views
Transparent DNS proxy view
Predefined user roles
network-admin
Parameters
ipv4-address: Specifies an IPv4 address, which cannot be a loopback address, multicast address, broadcast address, or an address in the format of 0.X.X.X.
mask-length: Specifies a mask length in the range of 0 to 32.
mask: Specifies a subnet mask.
Usage guidelines
A transparent DNS proxy processes a DNS request only when the destination IP address and port number of the DNS request match those of the transparent DNS proxy.
If server load balancing is configured, configure different IP addresses and port numbers for the transparent DNS proxy and the virtual server of the UDP type.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Specify the IPv4 address for transparent DNS proxy dns-proxy1 as 1.2.3.4/24.
<Sysname> system-view
[Sysname] loadbalance dns-proxy dns_proxy1
[Sysname-lb-dp-udp-dns-proxy1] ip address 1.2.3.4 24
ipv6
Use ipv6 to configure the IPv6 sticky method.
Use undo ipv6 to restore the default.
Syntax
ipv6 [ port ] { both | destination | source } [ prefix prefix-length ]
undo ipv6
Default
No IPv6 sticky method is configured.
Views
Sticky group view
Predefined user roles
network-admin
Parameters
port: Specifies the sticky method as IPv6 address + port number. If you do not specify this keyword, the sticky method is IPv6 address.
both: Specifies the sticky method as source IPv6 address + destination IPv6 address if you do not specify the port keyword, or source IPv6 address + source port number + destination IPv6 address + destination port number if you specify the port keyword.
destination: Specifies the sticky method as destination IPv6 address if you do not specify the port keyword, or destination IPv6 address + destination port number if you specify the port keyword.
source: Specifies the sticky method as source IPv6 address if you do not specify the port keyword, or source IPv6 address + source port number if you specify the port keyword.
prefix prefix-length: Specifies the prefix length for the sticky method.
Examples
# Configure the sticky method for the address- and port-based sticky group sg1 as source IPv6 address.
<Sysname> system-view
[Sysname] sticky-group sg1 type address-port
[Sysname-sticky-address-port-sg1] ipv6 source
# Configure the sticky method for the address- and port-based sticky group sg1 as source IPv6 address + source port number.
<Sysname> system-view
[Sysname] sticky-group sg1 type address-port
[Sysname-sticky-address-port-sg1] ipv6 port source
Related commands
sticky-group
ipv6 address (DNS server view)
Use ipv6 address to configure an IPv6 address for a DNS server.
Use undo ipv6 address to restore the default.
Syntax
ipv6 address ipv6-address
undo ipv6 address
Default
No IPv6 address is configured for a DNS server.
Views
DNS server view
Predefined user roles
network-admin
Parameters
ipv6-address: Specifies an IPv6 address, which cannot be a loopback address, IPv6 multicast address, link-local address, or all-zero address.
Usage guidelines
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Configure the IPv6 address for DNS server ds1 as 1001::1.
<Sysname> system-view
[Sysname] loadbalance dns-server ds1
[Sysname-lb-ds-ds1] ipv6 address 1001::1
ipv6 address (transparent DNS proxy view)
Use ipv6 address to configure an IPv6 address for a transparent DNS proxy.
Use undo ipv6 address to restore the default.
Syntax
ipv6 address ipv6-address [ prefix-length ]
undo ipv6 address
Default
No IPv6 address is configured for a transparent DNS proxy.
Views
Transparent DNS proxy view
Predefined user roles
network-admin
Parameters
ipv6-address: Specifies an IPv6 address, which cannot be a loopback address, IPv6 multicast address, link-local address, or all-zero address (If the prefix length is 0, you can specify the all-zero address.).
prefix-length: Specifies a prefix length for the IPv6 address, in the range of 0 to 128.
Usage guidelines
A transparent DNS proxy processes a DNS request only when the destination IP address and port number of the DNS request match those of the transparent DNS proxy.
If server load balancing is configured, configure different IP addresses and port numbers for the transparent DNS proxy and the virtual server of the UDP type.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Configure the IPv6 address for transparent DNS proxy dns-proxy1 as 1::2:3/112.
<Sysname> system-view
[Sysname] loadbalance dns-proxy dns-proxy1
[Sysname-lb-dp-udp-dns-proxy1] ipv6 address 1::2:3 112
lb-policy (transparent DNS proxy view)
Use lb-policy to specify an LB policy to be referenced by a transparent DNS proxy.
Use undo lb-policy to restore the default.
Syntax
lb-policy policy-name
undo lb-policy
Default
No LB policy is referenced by a transparent DNS proxy.
Views
Transparent DNS proxy view
Predefined user roles
network-admin
Parameters
policy-name: Specifies an LB policy by its name, a case-insensitive string of 1 to 63 characters.
Usage guidelines
By referencing an LB policy, a transparent DNS proxy implements load balancing for matching packets based on the packet contents.
A transparent DNS proxy can reference only a DNS policy template.
Examples
# Specify the LB policy dns-policy1 to be referenced by transparent DNS proxy dns-proxy1.
<Sysname> system-view
[Sysname] loadbalance dns-proxy dns-proxy1
[Sysname-lb-dp-udp-dns-proxy1] lb-policy dns-policy1
link (DNS server view)
Use link to associate a link with a DNS server.
Use undo link to restore the default.
Syntax
link link-name
undo link
Default
No link is associated with a DNS server.
Views
DNS server view
Predefined user roles
network-admin
Parameters
link-name: Specifies a link by its name, a case-insensitive string of 1 to 63 characters.
Usage guidelines
A DNS server can be associated with only one link. A link can be associated with multiple DNS servers.
Examples
# Associate link link1 with DNS server ds1.
<Sysname> system-view
[Sysname] loadbalance dns-server ds1
[Sysname-lb-ds-ds1] link link1
loadbalance action
Use loadbalance action to create an LB action and enter its view, or enter the view of an existing LB action.
Use undo loadbalance action to delete the specified LB action.
Syntax
loadbalance action action-name [ type dns ]
undo loadbalance action action-name
Default
No LB actions exist.
Views
System view
Predefined user roles
network-admin
Parameters
action-name: Specifies the LB action name, a case-insensitive string of 1 to 63 characters.
type dns: Specifies the DNS LB action type.
·
·
Usage guidelines
When you create an LB action, you must specify the LB action type. You can enter an existing LB action view without entering the type of the LB action.
Examples
# Create LB action lba1 with the DNS type, and enter LB action view.
<Sysname> system-view
[Sysname] loadbalance action lba1 type dns
[Sysname-lba-dns-lba1]
loadbalance class
Use loadbalance class to create an LB class and enter its view, or enter the view of an existing LB class.
Use undo loadbalance class to delete the specified LB class.
Syntax
loadbalance class class-name [ type dns [ match-all | match-any ] ]
undo loadbalance class class-name
Default
No LB classes exist.
Views
System view
Predefined user roles
network-admin
Parameters
class-name: Specifies the LB class name, a case-insensitive string of 1 to 63 characters.
type dns: Specifies the DNS LB class type.
·
·
[ match-all | match-any ]: Requires matching all rules or any rule of the LB class. match-all is the default match mode.
Usage guidelines
When you create an LB class, you must specify an LB class type. You can enter an existing LB class view without entering the type of the LB class.
Examples
# Create LB class lbc1 with the DNS type, and enter LB class view.
<Sysname> system-view
[Sysname] loadbalance class lbc1 type dns
[Sysname-lbc-dns-lbc1]
loadbalance dns-proxy
Use loadbalance dns-proxy to create a transparent DNS proxy and enter its view, or enter the view of an existing transparent DNS proxy.
Use undo loadbalance dns-proxy to delete a transparent DNS proxy.
Syntax
loadbalance dns-proxy dns-proxy-name type udp
undo loadbalance dns-proxy dns-proxy-name
Default
No transparent DNS proxies exist.
Views
System view
Predefined user roles
network-admin
Parameters
dns-proxy-name: Specifies the transparent DNS proxy name, a case-insensitive string of 1 to 63 characters.
type udp: Specifies the transparent DNS proxy type as UDP.
Examples
# Create the UDP transparent DNS proxy dns-proxy1, and enter UDP transparent DNS proxy view.
<Sysname> system-view
[Sysname] loadbalance dns-proxy dns-proxy1 type udp
[Sysname-lb-dp-udp-dns-proxy1]
Related commands
display loadbalance dns-proxy
loadbalance dns-server
Use loadbalance dns-server to create a DNS server and enter its view, or enter the view of an existing DNS server.
Use undo loadbalance dns-server to delete a DNS server.
Syntax
loadbalance dns-server dns-server-name
undo loadbalance dns-server dns-server-name
Default
No DNS servers exist.
Views
System view
Predefined user roles
network-admin
Parameters
dns-server-name: Specifies the DNS server name, a case-insensitive string of 1 to 63 characters.
Examples
# Create the DNS server ds1, and enter DNS server view.
<Sysname> system-view
[Sysname] loadbalance dns-server ds1
[Sysname-lb-ds-ds1]
loadbalance dns-server-pool
Use loadbalance dns-server-pool to create a DNS server pool and enter its view, or enter the view of an existing DNS server pool.
Use undo loadbalance dns-server-pool to delete a DNS server pool.
Syntax
loadbalance dns-server-pool pool-name
undo loadbalance dns-server-pool pool-name
Default
No DNS server pools exist.
Views
System view
Predefined user roles
network-admin
Parameters
pool-name: Specifies the DNS server pool name, a case-insensitive string of 1 to 63 characters.
Examples
# Create the DNS server pool dns-pool1, and enter DNS server pool view.
<Sysname> system-view
[Sysname] loadbalance dns-server-pool dns-pool1
[Sysname-lb-dspool-dns-pool1]
loadbalance link
Use loadbalance link to create an LB link and enter its view, or enter the view of an existing LB link.
Use undo loadbalance link to delete an LB link.
Syntax
loadbalance link link-name
undo loadbalance link link-name
Default
No LB links exist.
Views
System view
Predefined user roles
network-admin
Parameters
link-name: Specifies the LB link name, a case-insensitive string of 1 to 63 characters.
Usage guidelines
Each physical link connected to the external network corresponds to an LB link.
Examples
# Create the LB link lk1, and enter LB link view.
<Sysname> system-view
[Sysname] loadbalance link lk1
[Sysname-lb-link-lk1]
loadbalance log enable bandwidth-busy
Use loadbalance log enable bandwidth-busy to enable load balancing link busy state logging.
Use undo loadbalance log enable bandwidth-busy to disable load balancing link busy state logging.
Syntax
loadbalance log enable bandwidth-busy
undo loadbalance log enable bandwidth-busy
Default
Load balancing link busy state logging is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
Load balancing link busy state logging records busy states for all links.
Examples
# Enable load balancing link busy state logging.
<Sysname> system-view
[Sysname] loadbalance log enable bandwidth-busy
loadbalance log enable nat
Use loadbalance log enable nat to enable load balancing NAT logging.
Use undo loadbalance log enable nat to disable load balancing NAT logging.
Syntax
loadbalance log enable nat
undo loadbalance log enable nat
Default
Load balancing NAT logging is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
Load balancing NAT logging records NAT session information, including IP address and port translation information and access information.
Load balancing NAT logs are exported as flow logs. To export load balancing NAT logs, you must also configure flow log settings.
For more information about flow logs, see Network Management and Monitoring Configuration Guide.
Examples
# Enable load balancing NAT logging.
<Sysname> system-view
[Sysname] loadbalance log enable nat
loadbalance policy
Use loadbalance policy to create an LB policy and enter its view, or enter the view of an existing LB policy.
Use undo loadbalance policy to delete the specified LB policy.
Syntax
loadbalance policy policy-name [ type dns ]
undo loadbalance policy policy-name
Default
No LB policies exist.
Views
System view
Predefined user roles
network-admin
Parameters
policy-name: Specifies the LB policy name, a case-insensitive string of 1 to 63 characters.
type dns: Specifies the DNS LB policy type.
·
·
Usage guidelines
When you create an LB policy, you must specify the LB policy type. You can enter existing LB policy view without entering the type of the LB policy.
Examples
# Create LB policy lbp1 with the DNS type, and enter LB policy view.
<Sysname> system-view
[Sysname] loadbalance policy lbp1 type dns
[Sysname-lbp-dns-lbp1]
match acl
Use match class to create an ACL match rule or modify an existing ACL match rule.
Use undo match to delete a match rule.
Syntax
match [ match-id ] acl [ ipv6 ] { acl-number | name acl-name }
undo match match-id
Default
No match rules exist.
Views
LB class view
Predefined user roles
network-admin
Parameters
match-id: Specifies a match rule by its ID in the range of 1 to 65535. If you do not specify this argument, the system automatically assigns an available rule ID with the smallest number.
ipv6: Specifies an IPv6 ACL. If you do not specify this keyword, the command creates an IPv4 ACL.
acl-number: Specifies the ACL number in the range of 2000 to 3999.
name acl-name: Specifies an ACL by its name, a case-insensitive string of 1 to 63 characters starting with a letter.
Usage guidelines
If the specified ACL does not exist, this rule is not matched.
You can create a maximum of 65535 match rules for an LB class.
Examples
# In the transparent DNS proxy scenario, create an ACL match rule for DNS LB class lbc3.
<Sysname> system-view
[Sysname] loadbalance class lbc3 type dns
[Sysname-lbc-dns-lbc3] match acl 2000
match class
Use match class to create a match rule that references an LB class or modify an existing match rule that references an LB class.
Use undo match to delete a match rule.
Syntax
match [ match-id ] class class-name
undo match match-id
Default
An LB class does not have a match rule.
Views
LB class view
Predefined user roles
network-admin
Parameters
match-id: Specifies a match rule by its ID in the range of 1 to 65535. If you do not specify this argument, the system automatically assigns an available rule ID with the smallest number.
class-name: Specifies an LB class by its name, a case-insensitive string of 1 to 63 characters, to be referenced by the match rule. The current LB class cannot be referenced.
Usage guidelines
A match rule cannot reference an LB class that has already been referenced.
You can create a maximum of 65535 match rules for an LB class.
Examples
# In the transparent DNS proxy scenario, create a match rule that references the LB class lbc2 for DNS LB class lbc4.
<Sysname> system-view
[Sysname] loadbalance class lbc4 type dns
[Sysname-lbc-dns-lbc4] match class lbc2
match destination
Use match destination to create a destination IP address match rule or modify an existing destination IP address match rule.
Use undo match to delete a match rule.
Syntax
match [ match-id ] destination { ip address ipv4-address [ mask-length | mask ] | ipv6 address ipv6-address [ prefix-length ] }
undo match match-id
Default
An LB class does not have a match rule.
Views
DNS/Link-generic LB class view
Predefined user roles
network-admin
Parameters
match-id: Specifies a match rule by its ID in the range of 1 to 65535. If you do not specify this argument, the system automatically assigns an available rule ID with the smallest number.
ip address ipv4-address: Specifies an IPv4 address.
mask-length: Specifies a mask length in the range of 0 to 32. The default is 32.
mask: Specifies a subnet mask. The default is 255.255.255.255.
ipv6 address ipv6-address: Specifies an IPv6 address.
prefix-length: Specifies a prefix length in the range of 0 to 128. The default is 128.
Usage guidelines
You can create a maximum of 65535 match rules for an LB class.
Examples
# Create a match rule to match destination IPv4 address 1.1.1.1/32 for the DNS LB class lbc1.
<Sysname> system-view
[Sysname] loadbalance class lbc1 type dns
[Sysname-lbc-dns-lbc1] match destination ip address 1.1.1.1
match domain-name
Use match domain-name to create a domain name match rule or modify an existing domain name match rule.
Use undo match to delete a match rule.
Syntax
match [ match-id ] domain-name domain-name
undo match match-id
Default
An LB class does not have a match rule.
Views
DNS LB class view
Predefined user roles
network-admin
Parameters
match-id: Specifies a match rule by its ID in the range of 1 to 65535. If you do not specify this argument, the system automatically assigns an available rule ID with the smallest number.
domain-name: Specifies a domain name, a case-insensitive string of 1 to 253 characters. Each dot-separated part in the domain name can contain a maximum of 63 characters. The domain name can contain letters, digits, hyphens (-), underscores (_), dots (.), and wildcards (asterisks and question marks).
Usage guidelines
When you use wildcards (asterisks and question marks) in a domain name, follow these guidelines:
· The wildcards can substitute any characters except for dots (.).
· An asterisk (*) can substitute a character string.
· A question mark (?) can substitute a single character.
You can create a maximum of 65535 match rules for an LB class.
Examples
# Create a domain name match rule for DNS LB class lbc1 to match domain name www.example.com.
<Sysname> system-view
[Sysname] loadbalance class lbc1 type dns
[Sysname-lbc-dns-lbc1] match domain-name www.example.com
match source
Use match source to create a source IP address match rule or modify an existing source IP address match rule.
Use undo match to delete a match rule.
Syntax
match [ match-id ] source { ip address ipv4-address [ mask-length | mask ] | ipv6 address ipv6-address [ prefix-length ] }
undo match match-id
Default
An LB class does not have a match rule.
Views
LB class view
Predefined user roles
network-admin
Parameters
match-id: Specifies a match rule by its ID in the range of 1 to 65535. If you do not specify this argument, the system automatically assigns an available rule ID with the smallest number.
source: Specifies the match rule type as source IP address.
ip address ipv4-address: Specifies an IPv4 address.
mask-length: Specifies a mask length in the range of 0 to 32. The default is 32.
mask: Specifies a subnet mask. The default is 255.255.255.255.
ipv6 address ipv6-address: Specifies an IPv6 address.
prefix-length: Specifies a prefix length in the range of 0 to 128. The default is 128.
Usage guidelines
You can create a maximum of 65535 match rules for an LB class.
Examples
# In the transparent DNS proxy scenario, create a match rule that matches source IP address 1.1.1.1/32 for DNS LB class lbc3.
<Sysname> system-view
[Sysname] loadbalance class lbc3 type dns
[Sysname-lbc-dns-lbc3] match source ip address 1.1.1.1
max-bandwidth
Use max-bandwidth to set the maximum expected bandwidth of an LB link.
Use undo max-bandwidth to restore the default.
Syntax
max-bandwidth [ inbound | outbound ] bandwidth-value kbps
undo max-bandwidth [ inbound | outbound ]
Default
The maximum expected bandwidth of an LB link is not limited.
Views
Link view
Predefined user roles
network-admin
Parameters
inbound: Specifies the maximum inbound expected bandwidth.
outbound: Specifies the maximum outbound expected bandwidth.
bandwidth-value: Specifies the maximum expected bandwidth in the range of 0 to 4294967295. The value 0 means the bandwidth is not limited.
kbps: Specifies the bandwidth unit as kbps.
Usage guidelines
If you do not specify the inbound or outbound keyword, the maximum expected bandwidth equals the inbound expected bandwidth plus the outbound expected bandwidth.
This command takes effect only on new sessions and does not take effect on existing sessions.
In addition to being used for link protection, the maximum expected bandwidth is used for remaining bandwidth calculation in the bandwidth algorithm, maximum bandwidth algorithm, and dynamic proximity algorithm.
Examples
# Set the maximum expected bandwidth of the LB link lk1 to 1 kbps.
<Sysname> system-view
[Sysname] loadbalance link lk1
[Sysname-lb-link-lk1] max-bandwidth 1 kbps
# Set the maximum inbound expected bandwidth of the LB link lk1 to 1 kbps.
<Sysname> system-view
[Sysname] loadbalance link lk1
[Sysname-lb-link-lk1] max-bandwidth inbound 1 kbps
# Set the maximum outbound expected bandwidth of the LB link lk1 to 1 kbps.
<Sysname> system-view
[Sysname] loadbalance link lk1
[Sysname-lb-link-lk1] max-bandwidth outbound 1 kbps
port (DNS server view)
Use port to configure the port number of a DNS server.
Use undo port to restore the default.
Syntax
port port-number
undo port
Default
The port number of a DNS server is 0.
Views
DNS server view
Predefined user roles
network-admin
Parameters
port-number: Specifies a port number in the range of 0 to 65535. The value 0 means that the original port number is used.
Usage guidelines
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Specify the port number of DNS server ds1 as 5353.
<Sysname> system-view
[Sysname] loadbalance dns-server ds1
[Sysname-lb-ds-ds1] port 5353
port (transparent DNS proxy view)
Use port to configure the port number of a transparent DNS proxy.
Use undo port to restore the default.
Syntax
port port-number
undo port
Default
The port number of a transparent DNS proxy is 53.
Views
Transparent DNS proxy view
Predefined user roles
network-admin
Parameters
port-number: Specifies a port number in the range of 1 to 65535.
Usage guidelines
A transparent DNS proxy processes a DNS request only when the destination IP address and port number of the DNS request matches those of the transparent DNS proxy.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Specify the port number of transparent DNS proxy dns-proxy1 as 5353.
<Sysname> system-view
[Sysname] loadbalance dns-proxy dns-proxy1
[Sysname-lb-dp-dns-proxy1] port 5353
Related commands
display loadbalance dns-proxy
predictor (DNS server pool view)
Use predictor to specify a scheduling algorithm for a DNS server pool.
Use undo predictor to restore the default.
Syntax
predictor hash address { destination | source | source-ip-port } [ mask mask-length ] [ prefix prefix-length ]
predictor { random | round-robin | { bandwidth | max-bandwidth } [ inbound | outbound ] }
undo predictor
Default
The scheduling algorithm for a DNS server pool is weighted round robin.
Views
DNS server pool view
Predefined user roles
network-admin
Parameters
hash address: Specifies the hash algorithm based on the IP address.
destination: Specifies the hash algorithm based on the destination IP address.
source: Specifies the hash algorithm based on the source IP address.
source-ip-port: Specifies the hash algorithm based on the source IP address and port number.
mask mask-length: Specifies the mask length of the IPv4 address used in the hash algorithm. The value range for the mask-length argument is 0 to 32. The default is 32.
prefix prefix-length: Specifies the prefix length of the IPv6 address used in the hash algorithm. The value range for the prefix-length argument is 0 to 128. The default is 128.
random: Specifies the random algorithm, which randomly assigns DNS requests to DNS servers.
round-robin: Specifies the weighted round robin algorithm, which assigns DNS requests to DNS servers based on the weights of the DNS servers. A higher weight indicates more DNS requests will be assigned. The weight value used in this algorithm is configured in DNS server pool member view.
bandwidth: Specifies the bandwidth algorithm, which assigns DNS requests to DNS servers based on the weight and remaining bandwidth of the DNS servers. The weight value used in this algorithm is configured in DNS server view.
max-bandwidth: Specifies the maximum bandwidth algorithm, which always assigns DNS requests to the DNS server corresponding to the idle link with the largest remaining bandwidth.
inbound: Selects a DNS server based on the inbound bandwidth.
outbound: Selects a DNS server based on the outbound bandwidth.
Usage guidelines
If you do not specify the inbound or outbound keyword, the total bandwidth is used to select a DNS server.
In the bandwidth algorithm and maximum bandwidth algorithm, the remaining bandwidth is the maximum expected bandwidth minus the current bandwidth. If the maximum expected bandwidth is not configured, the remaining bandwidth is the maximum bandwidth of the link minus the current bandwidth.
Examples
# Specify the scheduling algorithm as random for DNS server pool dns-pool.
<Sysname> system-view
[Sysname] loadbalance dns-server-pool dns-pool
[Sysname-lb-dspool-dns-pool] predictor random
Related commands
max-bandwidth (link view)
rate-limit bandwidth (link view)
priority (DNS server pool member view)
Use priority to set the priority of a DNS server pool member.
Use undo priority to restore the default.
Syntax
priority priority
undo priority
Default
The priority of a DNS server pool member is 4.
Views
DNS server pool member view
Predefined user roles
network-admin
Parameters
priority: Specifies the priority value in the range of 1 to 8. A greater value means a higher priority.
Usage guidelines
Typically, only the members with the highest priority in a DNS server pool participate in scheduling. If the number of such members is smaller than the required minimum number, more members are selected by priority in descending order. If the allowed maximum number is exceeded after members with a certain priority are added, only some of the members with that priority are added.
Use this command together with the selected-server command in DNS server pool view.
Examples
# Set the priority of DNS server pool member ds1 to 3.
<Sysname> system-view
[Sysname] loadbalance dns-server-pool dsp1
[Sysname-lb-dspool-dsp1] dns-server ds1 port 10
[Sysname-dspool-dsp1-#member#-ds1-port-10] priority 3
Related commands
selected-server (DNS server pool view)
priority (DNS server view)
Use priority to set the priority of a DNS server.
Use undo priority to restore the default.
Syntax
priority priority
undo priority
Default
The priority of a DNS server is 4.
Views
DNS server view
Predefined user roles
network-admin
Parameters
priority: Specifies the priority value in the range of 1 to 8. A greater value means a higher priority.
Usage guidelines
Typically, only the DNS servers with the highest priority participate in scheduling. If the number of such DNS servers is smaller than the required minimum number, more DNS servers are selected by priority in descending order. If the allowed maximum number is exceeded after DNS servers with a certain priority are added, only some of the DNS servers with that priority are added.
Use this command together with the selected-server command in DNS server pool view.
Examples
# Set the priority of DNS server ds1 to 3.
<Sysname> system-view
[Sysname] loadbalance dns-server ds1
[Sysname-lb-ds-ds1] priority 3
Related commands
selected-server (DNS server pool view)
probe (DNS server pool member view)
Use probe to specify a health monitoring method for a DNS server pool member.
Use undo probe to restore the default.
Syntax
probe template-name
undo probe template-name
Default
No health monitoring method is specified for a DNS server pool member.
Views
DNS server pool member view
Predefined user roles
network-admin
Parameters
template-name: Specifies an NQA template by its name, a case-insensitive string of 1 to 32 characters.
Usage guidelines
Use the nqa template command to create an NQA template to be referenced by the health monitoring method. The DNS server pool uses the parameters defined in the NQA template to detect the availability of the pool members.
The health monitoring method configuration in DNS server pool member view takes precedence over the configuration in DNS server pool view.
The health monitoring result for a DNS server affects the availability of a DNS server pool member. The health monitoring result for a DNS server pool member does not affect the availability of a DNS server.
Examples
# Create the ICMP-type NQA template t4, and specify the health monitoring method for the DNS server pool member ds1 as t4.
<Sysname> system-view
[Sysname] nqa template icmp t4
[Sysname-nqatplt-icmp-t4] quit
[Sysname] loadbalance dns-server-pool dsp1
[Sysname-lb-dspool-dsp1] dns-server ds1 port 10
[Sysname-lb-dspool-dsp1-#member#-ds1-port-10] probe t4
Related commands
nqa template (Network Management and Monitoring Command Reference)
success-criteria (DNS server pool member view)
probe (DNS server pool view)
Use probe to specify a health monitoring method for a DNS server pool.
Use undo probe to restore the default.
Syntax
probe template-name
undo probe template-name
Default
No health monitoring method is specified for a DNS server pool.
Views
DNS server pool view
Predefined user roles
network-admin
Parameters
template-name: Specifies an NQA template by its name, a case-insensitive string of 1 to 32 characters.
Usage guidelines
Use the nqa template command to create an NQA template to be referenced by the health monitoring method. The DNS server pool uses the parameters defined in the NQA template to detect the availability of DNS servers.
The health monitoring method configuration in DNS server view takes precedence over the configuration in DNS server pool view.
Examples
# Create the ICMP-type NQA template t4, and specify the health monitoring method for the DNS server pool dns-pool as t4.
<Sysname> system-view
[Sysname] nqa template icmp t4
[Sysname-nqatplt-icmp-t4] quit
[Sysname] loadbalance dns-server-pool dns-pool
[Sysname-lb-dspool-dns-pool] probe t4
Related commands
nqa template (Network Management and Monitoring Command Reference)
success-criteria (DNS server pool view)
probe (DNS server view)
Use probe to specify a health monitoring method for a DNS server.
Use undo probe to restore the default.
Syntax
probe template-name
undo probe template-name
Default
No health monitoring method is specified for a DNS server.
Views
DNS server view
Predefined user roles
network-admin
Parameters
template-name: Specifies an NQA template by its name, a case-insensitive string of 1 to 32 characters.
Usage guidelines
Use the nqa template command to create an NQA template to be referenced by the health monitoring method.
The health monitoring method configuration in DNS server view takes precedence over the configuration in DNS server pool view.
Examples
# Create the ICMP-type NQA template t4, and specify the health monitoring method for DNS server ds1 as t4.
<Sysname> system-view
[Sysname] nqa template icmp t4
[Sysname-nqatplt-icmp-t4] quit
[Sysname] loadbalance dns-server ds1
[Sysname-lb-ds-ds1] probe t4
Related commands
nqa template (Network Management and Monitoring Command Reference)
success-criteria (DNS server view)
probe (link view)
Use probe to specify a health monitoring method for an LB link.
Use undo probe to restore the default.
Syntax
probe template-name
undo probe template-name
Default
No health monitoring method is specified for an LB link.
Views
Link view
Predefined user roles
network-admin
Parameters
template-name: Specifies an NQA template by its name, a case-insensitive string of 1 to 32 characters.
Usage guidelines
Use the nqa template command to create an NQA template to be referenced by the health monitoring method.
You can configure multiple health monitoring methods for an LB link. By default, health monitoring succeeds only when all the specified health monitoring methods succeed. You can use the success-criteria command to specify the health monitoring success criteria for the LB link.
Examples
# Create the ICMP-type NQA template t4, and specify the health monitoring method for the LB link lk1 as t4.
<Sysname> system-view
[Sysname] nqa template icmp t4
[Sysname-nqatplt-icmp-t4] quit
[Sysname] loadbalance link lk1
[Sysname-lb-link-lk1] probe t4
Related commands
nqa template (Network Management and Monitoring Command Reference)
success-criteria (link view)
rate-limit bandwidth (link view)
Use rate-limit bandwidth to set the maximum bandwidth of a link.
Use undo rate-limit bandwidth to restore the default.
Syntax
rate-limit bandwidth [ inbound | outbound ] bandwidth-value kbps
undo rate-limit bandwidth [ inbound | outbound ]
Default
The maximum bandwidth of a link is not limited.
Views
Link view
Predefined user roles
network-admin
Parameters
inbound: Specifies the maximum inbound bandwidth.
outbound: Specifies the maximum outbound bandwidth.
bandwidth-value: Specifies the maximum bandwidth in the range of 0 to 4294967295. The value 0 means the bandwidth is not limited.
kbps: Specifies the bandwidth unit as kbps.
Usage guidelines
If you do not specify the inbound or outbound keyword, the maximum bandwidth equals the inbound bandwidth plus the outbound bandwidth.
This command takes effect only on new sessions and does not take effect on existing sessions.
Examples
# Set the maximum bandwidth of the link lk1 to 1 kbps.
<Sysname> system-view
[Sysname] loadbalance link lk1
[Sysname-lb-link-lk1] rate-limit bandwidth 1 kbps
# Set the maximum inbound bandwidth of the link lk1 to 1 kbps.
<Sysname> system-view
[Sysname] loadbalance link lk1
[Sysname-lb-link-lk1] rate-limit bandwidth inbound 1 kbps
# Set the maximum outbound bandwidth of the link lk1 to 1 kbps.
<Sysname> system-view
[Sysname] loadbalance link lk1
[Sysname-lb-link-lk1] rate-limit bandwidth outbound 1 kbps
reset loadbalance dns-proxy statistics
Use reset loadbalance dns-proxy statistics to clear transparent DNS proxy statistics.
Syntax
reset loadbalance dns-proxy statistics [ dns-proxy-name ]
Views
User view
Predefined user roles
network-admin
Parameters
dns-proxy-name: Specifies a transparent DNS proxy by its name, a case-insensitive string of 1 to 63 characters. If you do not specify this argument, the command clears statistics for all DNS transparent proxies.
Examples
# Clear statistics for transparent DNS proxy dns-proxy1.
<Sysname> reset loadbalance dns-proxy statistics dns-proxy1
Related commands
display loadbalance dns-proxy statistics
reset loadbalance dns-server statistics
Use reset loadbalance dns-server statistics to clear DNS server statistics or DNS server pool member statistics.
Syntax
reset loadbalance dns-server statistics [ dns-server-name ]
reset loadbalance dns-server statistics dns-server-pool dns-server-pool-name [ name dns-server-name port port-number ]
Views
User view
Predefined user roles
network-admin
Parameters
dns-server-name: Specifies a DNS server by its name, a case-insensitive string of 1 to 63 characters. If you do not specify this argument, the command clears statistics for all DNS servers.
dns-server-pool dns-server-pool-name: Clears statistics for members of a DNS server pool. The dns-server-pool-name argument specifies a DNS server pool by its name, a case-insensitive string of 1 to 63 characters.
dns-server dns-server-name port port-number: Clears statistics for a DNS server pool member. The dns-server-name argument specifies a DNS server pool member by its name, a case-insensitive string of 1 to 63 characters. The port-number argument specifies the port number of the DNS server pool member, in the range of 0 to 65535. If you do not specify this option, the command clears statistics for all members of a DNS server pool.
Examples
# Clear statistics for DNS server ds1.
<Sysname> reset loadbalance dns-server statistics ds1
# Clear statistics for all members in DNS server pool dsp.
<Sysname> reset loadbalance dns-server statistics dns-server-pool dsp
Related commands
display loadbalance dns-server statistics
reset loadbalance hot-backup statistics
Use reset loadbalance hot-backup statistics to clear LB hot backup statistics.
Syntax
reset loadbalance hot-backup statistics
Views
User view
Predefined user roles
network-admin
Examples
# Clear LB hot backup statistics.
<Sysname> reset loadbalance hot-backup statistics
reset loadbalance link statistics
Use reset loadbalance link statistics to clear link statistics.
Syntax
reset loadbalance link statistics [ link-name ]
Views
User view
Predefined user roles
network-admin
Parameters
link-name: Specifies a link by its name, a case-insensitive string of 1 to 63 characters. If you do not specify this argument, the command clears statistics about all links.
Examples
# Clear statistics about all links.
<Sysname> reset loadbalance link statistics
reset sticky dns-proxy
Use reset sticky dns-proxy to clear sticky entry information for transparent DNS proxies.
Syntax
In standalone mode:
reset sticky dns-proxy [ dns-proxy-name dns-proxy-name ] [ class { class-name | default-class } | client-addr { ipv4-address | ipv6-address } | dns-server-addr { ipv4-address | ipv6-address } | dns-server-pool pool-name | dns-server-port port-number | key sticky-key ] *
In IRF mode:
reset sticky dns-proxy [ dns-proxy-name dns-proxy-name ] [ class { class-name | default-class } | client-addr { ipv4-address | ipv6-address } | dns-server-addr { ipv4-address | ipv6-address } | dns-server-pool pool-name | dns-server-port port-number | key sticky-key ] * [ slot slot-number ]
Views
User view
Predefined user roles
network-admin
Parameters
dns-proxy dns-proxy-name: Specifies a transparent DNS proxy by its name, a case-insensitive string of 1 to 63 characters. If you do not specify this option, the command clears sticky entry information for all transparent DNS proxies.
class { class-name | default-class }: Specifies an LB class by its name, a case-insensitive string of 1 to 63 characters, or specifies the default LB class.
client-addr { ipv4-address | ipv6-address }: Specifies a client by its IPv4 or IPv6 address.
dns-server-addr { ipv4-address | ipv6-address }: Specifies a DNS server by its IPv4 or IPv6 address.
dns-server-pool pool-name: Specifies a DNS server pool by its name, a case-insensitive string of 1 to 63 characters.
dns-server-port port-number: Specifies a DNS server port number in the range of 0 to 65535.
key sticky-key: Specifies a key value, a case-sensitive string of 1 to 36 characters.
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command clears sticky entry information for all member devices. (In IRF mode.)
Examples
# Clear sticky entry information for client address 3.0.0.1 of transparent DNS proxy dp.
<Sysname> reset sticky dns-proxy dns-proxy-name dp client-addr 3.0.0.1
reset sticky virtual-server
Use reset sticky virtual-server to clear sticky entry information for virtual servers.
Syntax
In standalone mode:
reset sticky virtual-server [ virtual-server-name virtual-server-name ] [ [ link { ip ipv4-address | ipv6 ipv6-address | interface { interface-type interface-number | interface-name } } | link-group link-group-name ] * | [ real-server-addr { ipv4-address | ipv6-address } | real-server-port port-number | server-farm server-farm-name | text text ] * ] [ class { class-name | default-class } | client-addr { ipv4-address | ipv6-address } | sticky-type { address-port | http-content | http-cookie | http-header | http-passive | payload | radius | sip | ssl | tcp-payload | udp-passive } [ key sticky-key ] ] *
In IRF mode:
reset sticky virtual-server [ virtual-server-name virtual-server-name ] [ [ link { ip ipv4-address | ipv6 ipv6-address | interface { interface-type interface-number | interface-name } } | link-group link-group-name ] * | [ real-server-addr { ipv4-address | ipv6-address } | real-server-port port-number | server-farm server-farm-name | text text ] * ] [ class { class-name | default-class } | client-addr { ipv4-address | ipv6-address } | sticky-type { address-port | http-content | http-cookie | http-header | http-passive | payload | radius | sip | ssl | tcp-payload | udp-passive } [ key sticky-key ] ] * [ slot slot-number ]
Views
User view
Predefined user roles
network-admin
Parameters
virtual-server virtual-server-name: Specifies a virtual server by its name, a case-insensitive string of 1 to 63 characters. If you do not specify this option, the command clears sticky entry information for all virtual servers.
link { ip ipv4-address | ipv6 ipv6-address | interface { interface-type interface-number | interface-name } }: Specifies a link by its IPv4 address, IPv6 address, or output interface.
link-group link-group-name: Specifies a link group by its name, a case-insensitive string of 1 to 63 characters.
real-server-addr { ipv4-address | ipv6-address }: Specifies a real server by its IPv4 or IPv6 address.
real-server-port port-number: Specifies a real server port number in the range of 0 to 65535.
server-farm server-farm-name: Specifies a server farm by its name, a case-insensitive string of 1 to 63 characters.
text text: Specifies a text string to match.
class { class-name | default-class }: Specifies an LB class by its name, a case-insensitive string of 1 to 63 characters, or specifies the default LB class.
client-addr { ipv4-address | ipv6-address }: Specifies a client by its IPv4 or IPv6 address.
sticky-type { address-port | http-content | http-cookie | http-header | http-passive | payload | radius | sip | ssl | tcp-payload | udp-passive }: Specifies a sticky group type.
key sticky-key: Specifies a key value, a case-sensitive string of 1 to 36 characters. If you do not specify key value, this command clears sticky entries for all key values.
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command clears sticky entry information for all member devices. (In IRF mode.)
Examples
# Clear sticky entry information for client address 3.0.0.1 of virtual server vs.
<Sysname> reset sticky virtual-server virtual-server-name vs client-addr 3.0.0.1
router interface
Use router interface to specify an outgoing interface for an LB link.
Use undo router interface to delete the outgoing interface for an LB link.
Syntax
router interface interface-type interface-number
undo router interface
Default
No outgoing interface is specified for an LB link.
Views
LB link view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an outgoing interface.
Usage guidelines
In scenarios where IP addresses are obtained through PPPoE, use this command to dynamically obtain the outbound next hop IP address through the specified outgoing interface.
The specified outgoing interface must be an interface that can dynamically obtain IP addresses.
You can configure both this command and the router ip or router ipv6 command. The command configured later overwrites the command configured first.
If you configure this command after configuring the vpn-instance (link view) command, this command overwrites the vpn-instance (link view) command. After you configure this command, you cannot configure the vpn-instance (link view) command.
Examples
# Specify Dialer0 as the outgoing interface for the LB link cnc.
<Sysname> system-view
[Sysname] loadbalance link cnc
[Sysname-lb-link-cnc] router interface Dialer0
router ip
Use router ip to specify the outbound next hop for an LB link.
Use undo router ip to restore the default.
Syntax
router ip ipv4-address
undo router ip
Default
The outbound next hop is not specified for an LB link.
Views
LB link view
Predefined user roles
network-admin
Parameters
ipv4-address: Specifies an IPv4 address, which cannot be a loopback address, multicast address, broadcast address, or an address in the format of 0.X.X.X.
Usage guidelines
You can specify only one outbound next hop for an LB link.
Examples
# Specify the outbound next hop as 1.2.3.4 for the LB link lk1.
<Sysname> system-view
[Sysname] loadbalance link lk1
[Sysname-lb-link-lk1] router ip 1.2.3.4
router ipv6
Use router ipv6 to specify the outbound next hop for an LB link.
Use undo router ipv6 to restore the default.
Syntax
router ipv6 ipv6-address
undo router ipv6
Default
The outbound next hop is not specified for an LB link.
Views
LB link view
Predefined user roles
network-admin
Parameters
ipv6-address: Specifies an IPv6 address, which cannot be an all-zero address, a multicast address, a loopback address, or a link-local address.
Usage guidelines
You can specify only one outbound next hop for an LB link.
Examples
# Specify the outbound next hop as 8008::8 for the LB link lk1.
<Sysname> system-view
[Sysname] loadbalance link lk1
[Sysname-lb-link-lk1] router ipv6 8008::8
selected-server (DNS server pool view)
Use selected-server to specify the number of DNS servers to participate in scheduling.
Use undo selected-server to restore the default.
Syntax
selected-server min min-number max max-number
undo selected-server
Default
The DNS servers with the highest priority participate in scheduling.
Views
DNS server pool view
Predefined user roles
network-admin
Parameters
min min-number: Specifies the minimum number of DNS servers to participate in scheduling, in the range of 1 to 1000.
max max-number: Specifies the maximum number of DNS servers to participate in scheduling, in the range of 1 to 1000. The value of the max-number argument must be greater than or equal to the value of the min-number argument.
Usage guidelines
If the number of DNS servers available to participate in scheduling exceeds the max-number setting, the max-number setting applies.
If the number of DNS servers available to participate in scheduling is less than the min-number setting, more DNS servers are selected by priority in descending order.
Examples
# Configure the minimum number and maximum number of DNS servers in DNS server pool dns-pool to participate in scheduling as 20 and 30, respectively.
<Sysname> system-view
[Sysname] loadbalance dns-server-pool dns-pool
[Sysname-lb-dspool-dns-pool] selected-server min 20 max 30
service enable (transparent DNS proxy view)
Use service enable to enable the transparent DNS proxy feature.
Use undo service enable to disable the transparent DNS proxy feature.
Syntax
service enable
undo service enable
Default
The transparent DNS proxy feature is disabled.
Views
Transparent DNS proxy view
Predefined user roles
network-admin
Examples
# Enable the transparent DNS proxy feature for transparent DNS proxy dns-proxy1.
<Sysname> system-view
[Sysname] loadbalance dns-proxy dns-proxy1
[Sysname-lb-dp-udp-dns-proxy1] service enable
set ip tos (LB action view)
Use set ip tos to set the ToS field value of IP packets sent to the server.
Use undo set ip tos to restore the default.
Syntax
set ip tos tos-number
undo set ip tos
Default
The ToS field of IP packets sent to the server is not changed.
Views
LB action view
Predefined user roles
network-admin
Parameters
tos-number: Specifies the ToS field value in the range of 0 to 255.
Examples
# In the transparent DNS proxy scenario, set the ToS field value to 20 for IP packets sent to the DNS server for the DNS LB action lba3.
<Sysname> system-view
[Sysname] loadbalance action lba3 type dns
[Sysname-lba-dns-lba3] set ip tos 20
skip current-dns-proxy
Use skip current-dns-proxy to skip the current transparent DNS proxy.
Use undo skip current-dns-proxy to restore the default.
Syntax
skip current-dns-proxy
undo skip current-dns-proxy
Default
The forwarding mode is to discard packets.
Views
DNS LB action view
Predefined user roles
network-admin
Usage guidelines
This command enables DNS requests to skip the current transparent DNS proxy and match the next transparent DNS proxy or virtual server.
A DNS request can skip a maximum of five transparent DNS proxies and virtual servers.
This command is mutually exclusive with the dns-server-pool or forward all command. If you configure one command, the other command (if configured) is automatically cancelled.
Examples
# Skip the current transparent DNS proxy in DNS LB action lba1.
<Sysname> system-view
[Sysname] loadbalance action lba1 type dns
[Sysname-lba-dns-lba1] skip current-dns-proxy
sticky-group
Use sticky-group to create a sticky group and enter its view, or enter the view of an existing sticky group.
Use undo sticky-group to delete the specified sticky group.
Syntax
sticky-group group-name [ type address-port ]
undo sticky-group group-name
Default
No sticky groups exist.
Views
System view
Predefined user roles
network-admin
Parameters
group-name: Specifies a sticky group name, a case-insensitive string of 1 to 63 characters.
type address-port: Specifies the sticky group type as address and port. When you create a sticky group, you must specify the sticky group type. You can enter an existing sticky group view without entering the type of the sticky group.
Usage guidelines
A sticky group uses a specific sticky method to distribute similar sessions to the same link. The sticky method applies to the first packet of a session. Subsequent packets of the session are distributed to the same link.
Examples
# Create the address- and port-type sticky group sg1 and enter sticky group view.
<Sysname> system-view
[Sysname] sticky-group sg1 type address-port
[Sysname-sticky-address-port-sg1]
sticky-sync enable (transparent DNS proxy view)
Use sticky-sync enable to enable sticky entry synchronization for a transparent DNS proxy.
Use undo sticky-sync enable to disable sticky entry synchronization for a transparent DNS proxy.
Syntax
sticky-sync enable [ global ]
undo sticky-sync enable
Default
Sticky entry synchronization is disabled for a transparent DNS proxy.
Views
Transparent DNS proxy view
Predefined user roles
network-admin
Parameters
global: Enables global synchronization.
Usage guidelines
This command can back up sticky entry information to ensure service continuity during a master and backup switchover in hot backup mode.
In a VRRP network, you must specify the global keyword for the sticky entry synchronization feature to take effect.
The device deletes existing sticky entries and generates new ones when the following events occur:
· Sticky entry synchronization is disabled.
· Sticky entry synchronization is changed from failover group-based synchronization to global synchronization.
· Sticky entry synchronization is changed from global synchronization to failover group-based synchronization.
Examples
# Enable sticky entry synchronization for transparent DNS proxy dns_proxy1.
<Sysname>system-view
[Sysname] loadbalance dns-proxy dns_proxy1 type udp
[Sysname-lb-dp-udp-dns_proxy1] sticky-sync enable
success-criteria (DNS server pool member view)
Use success-criteria to specify the health monitoring success criteria for a DNS server pool member.
Use undo success-criteria to restore the default.
Syntax
success-criteria { all | at-least min-number }
undo success-criteria
Default
Health monitoring succeeds only when all the specified health monitoring methods succeed.
Views
DNS server pool member view
Predefined user roles
network-admin
Parameters
all: Specifies the health monitoring success criteria as all successful health monitoring methods.
at-least min-number: Specifies the health monitoring success criteria as the specified minimum number of successful health monitoring methods, in the range of 1 to 4294967295.
Usage guidelines
If the min-number setting exceeds the number of existing health monitoring methods on the device, the number of existing health monitoring methods applies.
The health monitoring success criteria configuration in DNS server pool member view takes precedence over the configuration in DNS server pool view.
The health monitoring result for a DNS server affects the availability of a DNS server pool member. The health monitoring result for a DNS server pool member does not affect the availability of a DNS server.
Examples
# Configure the health monitoring success criteria for the DNS server pool member ds1 as a minimum number of 2 successful health monitoring methods.
<Sysname> system-view
[Sysname] loadbalance dns-server-pool dsp1
[Sysname-lb-dsp-dsp1] dns-server ds1 port 10
[Sysname-lb-dsp-dsp1-#member#-ds1-port-10] success-criteria at-least 2
success-criteria (DNS server pool view)
Use success-criteria to specify the health monitoring success criteria for a DNS server pool.
Use undo success-criteria to restore the default.
Syntax
success-criteria { all | at-least min-number }
undo success-criteria
Default
Health monitoring succeeds only when all the specified health monitoring methods succeed.
Views
DNS server pool view
Predefined user roles
network-admin
Parameters
all: Specifies the health monitoring success criteria as all successful health monitoring methods.
at-least min-number: Specifies the health monitoring success criteria as the specified minimum number of successful health monitoring methods, in the range of 1 to 4294967295.
Usage guidelines
If the min-number setting exceeds the number of existing health monitoring methods on the device, the number of existing health monitoring methods applies.
The health monitoring success criteria configuration in DNS server view takes precedence over the configuration in DNS server pool view.
Examples
# Configure the health monitoring success criteria for the DNS server pool dns-pool as a minimum number of 2 successful health monitoring methods.
<Sysname> system-view
[Sysname] loadbalance dns-server-pool dns-pool
[Sysname-lb-dspool-dns-pool] success-criteria at-least 2
Related commands
success-criteria (DNS server view)
success-criteria (DNS server view)
Use success-criteria to specify the health monitoring success criteria for a DNS server.
Use undo success-criteria to restore the default.
Syntax
success-criteria { all | at-least min-number }
undo success-criteria
Default
Health monitoring succeeds only when all the specified health monitoring methods succeed.
Views
DNS server view
Predefined user roles
network-admin
Parameters
all: Specifies the health monitoring success criteria as all successful health monitoring methods.
at-least min-number: Specifies the health monitoring success criteria as the specified minimum number of successful health monitoring methods, in the range of 1 to 4294967295.
Usage guidelines
If the min-number setting exceeds the number of existing health monitoring methods on the device, the number of existing health monitoring methods applies.
The health monitoring success criteria configuration in DNS server view takes precedence over the configuration in DNS server pool view.
Examples
# Configure the health monitoring success criteria for DNS server ds1 as a minimum number of 2 successful health monitoring methods.
<Sysname> system-view
[Sysname] loadbalance dns-server ds1
[Sysname-lb-ds-ds1] success-criteria at-least 2
Related commands
success-criteria (DNS server pool view)
success-criteria (link view)
Use success-criteria to specify the health monitoring success criteria for an LB link.
Use undo success-criteria to restore the default.
Syntax
success-criteria { all | at-least min-number }
undo success-criteria
Default
Health monitoring succeeds only when all the specified health monitoring methods succeed.
Views
LB link view
Predefined user roles
network-admin
Parameters
all: Specifies the health monitoring success criteria as all successful health monitoring methods.
at-least min-number: Specifies the health monitoring success criteria as the specified minimum number of successful health monitoring methods, in the range of 1 to 4294967295.
Usage guidelines
If the min-number setting exceeds the number of existing health monitoring methods on the device, the number of existing health monitoring methods applies.
Examples
# Configure the health monitoring success criteria for the LB link lk1 as a minimum number of 2 successful health monitoring methods.
<Sysname> system-view
[Sysname] loadbalance link lk1
[Sysname-lb-link-lk1] success-criteria at-least 2
Related commands
success-criteria (link group view)
timeout (sticky group view)
Use timeout to set the timeout timer for sticky entries.
Use undo timeout to restore the default.
Syntax
timeout { indefinite | timeout-value }
undo timeout
Default
The timeout timer for sticky entries is 86400 seconds for sticky groups of the HTTP cookie, HTTP passive, and UDP passive types and 60 seconds for sticky groups of other types.
Views
Sticky group view
Predefined user roles
network-admin
Parameters
indefinite: Specifies an indefinite timeout timer for sticky entries so that the sticky entries never age out. Sticky groups of the HTTP cookie type, HTTP passive type, and UDP passive type do not support this keyword.
timeout-value: Specifies the timeout timer in the range of 0 to 31536000 seconds for sticky groups of the HTTP cookie type and in the range of 10 to 604800 seconds for sticky groups of other types.
Usage guidelines
For sticky groups of the HTTP cookie type, the following principles apply:
· If the sticky method is cookie insert or cookie rewrite, a timeout timer of 0 indicates session persistency.
· If the sticky method is cookie get, a timeout timer of 0 indicates the timeout time for the sticky entries is 0 seconds.
Examples
# Set the timeout timer for sticky entries to 100 seconds in the address- and port-type sticky group sg1.
<Sysname> system-view
[Sysname] sticky-group sg1 type address-port
[Sysname-sticky-address-port-sg1] timeout 100
vpn-instance (DNS server view)
Use vpn-instance to specify a VPN instance for a DNS server.
Use undo vpn-instance to restore the default.
Syntax
vpn-instance vpn-instance-name
undo vpn-instance
Default
A DNS server belongs to the public network.
Views
DNS server view
Predefined user roles
network-admin
Parameters
vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters.
Examples
# Specify VPN instance vpn1 for DNS server ds1.
<Sysname> system-view
[Sysname] loadbalance dns-server ds1
[Sysname-vs-http-vs] vpn-instance vpn1
Related commands
display loadbalance dns-server
vpn-instance (link view)
Use vpn-instance to specify a VPN instance for a link.
Use undo vpn-instance to restore the default.
Syntax
vpn-instance vpn-instance-name
undo vpn-instance
Default
A link belongs to the public network.
Views
Link view
Predefined user roles
network-admin
Parameters
vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
Before executing this command, you must create the VPN instance by using the ip vpn-instance vpn-instance-name command. If the specified VPN instance has not been created, the link state will be unavailable.
Examples
# Specify VPN instance vpn1 for link lk1.
<Sysname> system-view
[Sysname] loadbalance link lk1
[Sysname-lb-link-lk1] vpn-instance vpn1
Related commands
ip vpn-instance (MPLS Command Reference)
vpn-instance (transparent DNS proxy view)
Use vpn-instance to specify a VPN instance for a transparent DNS proxy.
Use undo vpn-instance to restore the default.
Syntax
vpn-instance vpn-instance-name
undo vpn-instance
Default
A transparent DNS proxy belongs to the public network.
Views
Transparent DNS proxy view
Predefined user roles
network-admin
Parameters
vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters.
Examples
# Specify VPN instance vpn1 for transparent DNS proxy dns-proxy1.
<Sysname> system-view
[Sysname] loadbalance dns-proxy dns-proxy1
[Sysname-lb-dp-udp-dns-proxy1] vpn-instance vpn1
weight (DNS server pool member view)
Use weight to set the weight of a DNS server pool member.
Use undo weight to restore the default.
Syntax
weight weight-value
undo weight
Default
The weight of a DNS server pool member is 100.
Views
DNS server pool member view
Predefined user roles
network-admin
Parameters
weight-value: Specifies the weight in the range of 1 to 255. A greater value means a higher priority in scheduling.
Usage guidelines
The weight configured in this command is used in the weighted round-robin algorithm.
Examples
# Set the weight of the DNS server pool member ds1 to 150.
<Sysname> system-view
[Sysname] loadbalance dns-server-pool dsp1
[Sysname-lb-dspool-dsp1] dns-server ds1 port 10
[Sysname-lb-dspool-dsp1-#member#-ds1-port-10] weight 150
weight (DNS server view)
Use weight to set the weight of a DNS server to be used by the weighted round robin algorithm and bandwidth algorithm.
Use undo weight to restore the default.
Syntax
weight weight-value
undo weight
Default
The weight of a DNS server is 100.
Views
DNS server view
Predefined user roles
network-admin
Parameters
weight-value: Specifies the weight in the range of 1 to 255. A greater value means a higher priority in scheduling.
Examples
# Set the weight of the DNS server ds1 to 150.
<Sysname> system-view
[Sysname] loadbalance dns-server ds1
[Sysname-lb-ds-ds1] weight 150
