ip-section

Function

The ip-section command specifies a traffic diversion address for the cluster business group.

The undo ip-section command deletes the traffic diversion address for the cluster business group.

Format

ip-section [ section-id ] start-address [ end-address ] [ source-vsys vsys-name ] [ destination-vsys vsys-name ]

undo ip-section { section-id | start-address [ end-address ] }

Parameters

Parameter	Description	Value
section-id	Specifies the ID of the traffic diversion address segment.	USG6610E/6615E/6620E/6625E: The value is an integer ranging from 0 to 8191. USG6630E/6650E: The value is an integer ranging from 0 to 8191. USG6635E/6655E: The value is an integer ranging from 0 to 8191. USG6680E: The value is an integer ranging from 0 to 16383. USG6712E/6716E: The value is an integer ranging from 0 to 32767. If the ID is not specified, the system automatically uses the currently smallest available integer.
start-address	Specifies the start IP address of the traffic diversion address segment.	The value is in dotted decimal notation.
end-address	Specifies the end IP address of the traffic diversion address segment.	The value is in dotted decimal notation.
source-vsys	Indicates the source virtual system.	-
destination-vsys	Indicates the destination virtual system.	-
vsys-name	Specifies the name of a virtual system.	The virtual system must exist. If no virtual system is specified, the public system is used.

Views

Business group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenarios

In routing scenarios, you must configure a traffic diversion address for the business group. The traffic diversion address indicates the device's UNR that needs to be advertised. After the address is configured, the cluster advertises the route regarding the traffic diversion address for traffic diversion of upstream and downstream services.

Precautions

When configuring a traffic diversion address for the cluster business group, you can specify the source and destination virtual systems. If they are not specified, the public system is used.

In the business group, only the top three members will advertise traffic diversion addresses.

In IPSec, 32-bit UNRs should not be delivered for cluster traffic diversion. When a UNR is generated, traffic diversion addresses may be merged. For example, 10.1.1.2 and 10.1.1.3 can be merged into 10.1.1.2/31, and the route can be advertised. If the traffic diversion addresses are 10.1.1.1 and 10.1.1.2, they cannot be merged, and such routes conflict with direct routes on interfaces.

Do not set the IP address of any interface on the device as a traffic diversion address.

Example

# Set the traffic diversion addresses of business group 1 to 10.1.1.2-10.1.1.3.

C_No2_M<sysname> system-view
C_No2_M[sysname] business-group 1
C_No2_M[sysname-business-group-1] ip-section 10.1.1.2 10.1.1.3