Creating a match rule
Creating a match rule that references an LB class
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter LB class view. | loadbalance class class-name | N/A |
3. Create a match rule that references an LB class. | match [ match-id ] class class-name | By default, an LB class does not have any match rules. |
Creating a source IP address match rule
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter LB class view. | loadbalance class class-name | N/A |
3. Create a source IP address match rule. | match [ match-id ] source { ip address ipv4-address [ mask-length | mask ] | ipv6 address ipv6-address [ prefix-length ] } | By default, an LB class does not have any match rules. |
Creating an ACL match rule
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter LB class view. | loadbalance class class-name | N/A |
3. Create an ACL match rule. | match [ match-id ] acl [ ipv6 ] { acl-number | name acl-name } | By default, an LB class does not have any match rules. |
Creating an HTTP content match rule
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter HTTP LB class view. | loadbalance class class-name | N/A |
3. Create an HTTP content match rule. | match [ match-id ] content content [ offset offset ] | By default, an LB class does not have any match rules. This command is not supported by virtual servers of the fast HTTP type. |
Creating an HTTP cookie match rule
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter HTTP LB class view. | loadbalance class class-name | N/A |
3. Create an HTTP cookie match rule. | match [ match-id ] cookie cookie-name value value | By default, an LB class does not have any match rules. |
Creating an HTTP header match rule
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter HTTP LB class view. | loadbalance class class-name | N/A |
3. Create an HTTP header match rule. | match [ match-id ] header header-name value value | By default, an LB class does not have any match rules. |
Creating an HTTP URL match rule
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter HTTP LB class view. | loadbalance class class-name | N/A |
3. Create an HTTP URL match rule. | match [ match-id ] url url | By default, an LB class does not have any match rules. |
Creating a packet matching method match rule
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter HTTP LB class view. | loadbalance class class-name | N/A |
3. Create a packet matching method match rule. | match [ match-id ] method { ext ext-type | rfc rfc-type } | By default, an LB class does not have any match rules. |
Creating a RADIUS attribute match rule
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter RADIUS LB class view. | loadbalance class class-name | N/A |
3. Create a RADIUS attribute match rule. | match [ match-id ] radius-attribute { code attribute-code | user-name } value attribute-value | By default, an LB class does not have any match rules. |