F1000 series	Models	RIR compatibility
F1000-X-G5 series	F1000-A-G5, F1000-C-G5, F1000-C-G5-LI, F1000-E-G5, F1000-H-G5, F1000-S-G5	Yes
F1000-X-G3 series	F1000-A-G3, F1000-C-G3, F1000-E-G3, F1000-S-G3	Yes
F1000-X-G2 series	F1000-A-G2, F1000-C-G2, F1000-E-G2, F1000-S-G2	Yes
F1000-9X0-AI series	F1000-9390-AI, F1000-9385-AI, F1000-9380-AI, F1000-9370-AI, F1000-9360-AI, F1000-9350-AI, F1000-990-AI, F1000-980-AI, F1000-970-AI, F1000-960-AI, F1000-950-AI, F1000-930-AI, F1000-920-AI, F1000-910-AI, F1000-905-AI	Yes
F1000-9X0-AI series	F1000-9330-AI, F1000-9320-AI	No
F1000-C83X0 series	F1000-C8395, F1000-C8390, F1000-C8385, F1000-C8380, F1000-C8370, F1000-C8360, F1000-C8350	Yes
F1000-C83X0 series	F1000-C8330	No
F1000-C81X0 series	F1000-C8180, F1000-C8170, F1000-C8160, F1000-C8150, F1000-C8130, F1000-C8120, F1000-C8110	Yes
F1000-7X0-HI series	F1000-770-HI, F1000-750-HI, F1000-740-HI, F1000-720-HI, F1000-710-HI	Yes
F1000-7X0-HI series	F1000-730-HI	No
F1000-C-X series	F1000-C-EI, F1000-C-HI, F1000-C-XI, F1000-E-XI	Yes
F1000-V series	F1000-E-VG, F1000-S-VG	Yes
SecBlade IV	LSPM6FWD8, LSQM2FWDSC8	No

‌

F100 series	Models	RIR compatibility
F100-X-G5 series	F100-E-G5, F100-A-G5, F100-C-G5, F100-M-G5, F100-S-G5	Yes
F100-X-G3 series	F100-A-G3, F100-C-G3, F100-E-G3 , F100-M-G3, F100-S-G3	Yes
F100-X-G2 series	F100-A-G2, F100-C-G2, F100-E-G2, F100-M-G2, F100-S-G2	Yes
F100-WiNet series	F100-A80-WiNet, F100-A91-WiNet, F100-C80-WiNet, F100-C60-WiNet, F100-C50-WiNet, F100-S80-WiNet	Yes
F100-WiNet series	F100-A81-WiNet	No
F100-C-A series	F100-C-A6, F100-C-A5, F100-C-A3, F100-C-A2, F100-C-A1, F100-C-A6-WL, F100-C-A5-W, F100-C-A3-W	Yes
F100-X-XI series	F100-A-EI, F100-A-HI, F100-A-SI, F100-C-EI, F100-C-HI, F100-C-XI, F100-E-EI, F100-S-HI, F100-S-XI	Yes

‌

client enable

Use client enable to enable the RIR client globally.

Use undo client enable to disable the RIR client globally.

Syntax

client enable

undo client enable

Default

The RIR client is disabled globally.

Views

RIR view

Predefined user roles

network-admin

context-admin

Usage guidelines

To avoid NQA probes from occupying too many resources on a hub in a hub-spoke network, configure the hub as an RIR server and configure the spokes as RIR clients.

You can enable the RIR client globally or on an interface.

· Enabling the RIR client globally also enables the RIR client for all interfaces on the device. The interfaces can send link quality probe results for the RIR client.

· Enabling the RIR client on an interface allows only that interface to send link quality probe results for the RIR client.

When you enable the RIR client, follow these restrictions and guidelines:

· In a VXLAN network, only tunnel interfaces support enabling the RIR client. The RIR client uses the tunnel interfaces to send link quality probe results.

· The RIR server and RIR client cannot be both enabled on the same interface.

· If the enabled role (RIR server or client) on an interface is different from the globally enabled role, the interface-specific role takes effect on that interface.

Examples

# Enable the RIR client globally.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] client enable

Related commands

probe connect

probe sync-port

server enable

collaboration peer local

Use collaboration peer local to enable the local device to establish RIR collaboration relationship with a peer device.

Use undo collaboration peer local to restore the default.

Syntax

collaboration peer [ vpn-instance vpn-instance-name ] peer-ipv4-address local local-ipv4-address sync-port port-number

undo collaboration peer [ vpn-instance vpn-instance-name ] peer-ipv4-address local

Default

The local device does not establish RIR collaboration relationship with any device.

Views

RIR view

Predefined user roles

network-admin

context-admin

Parameters

vpn-instance vpn-instance-name: Specifies the MPLS L3VPN instance on which the local and peer devices establish RIR collaboration relationship. The vpn-instance-name argument is a case-sensitive string of 1 to 31 characters. The specified VPN instance must exist. If the local and peer IP addresses belong to the public network, do not specify this option.

peer-ipv4-address: Specifies an RIR collaboration peer by its IPv4 address.

local-ipv4-address: Specifies the IPv4 address of the local device. The local and peer devices must both belong to the public network or the same VPN instance.

sync-port port-number: Specifies the TCP port number used by the local and peer devices to synchronize link data. The value range for the port-number argument is 1024 to 65535. Make sure the port number is not used by any other service on the device.

Usage guidelines

Each pair of devices in an RIR collaboration device group must establish RIR collaboration relationship. You must configure this command on both the local and peer devices.

In a pair of devices with RIR collaboration relationship, the device with a lower IP address is the client. The client uses the port number specified by using this command to initiate a TCP connection request to its peer. Through the TCP connection, the local device can synchronize the configuration and status data of links that meet the service requirements to the peer device. The data does not include link data synchronized from other devices in the same RIR collaboration device group.

For the local device to select links from a peer device, you must execute the collaboration peer redirect command on both the local and peer devices.

The local and peer devices must use the same TCP port number for link data synchronization. A device can use the same or different TCP port numbers to synchronize data to different peers.

If you execute this command multiple times for the same pair of devices in the public network or a VPN instance, the most recent configuration takes effect.

Examples

# Establish RIR collaboration relationship between local device 1.1.1.1 and peer device 1.1.1.2 on the public network. They use TCP port number 6000 for link data synchronization.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] collaboration peer 1.1.1.2 local 1.1.1.1 sync-port 6000

# Establish RIR collaboration relationship between local device 1.1.1.1 and peer device 1.1.1.2 in VPN instance a. They use TCP port number 6000 for link data synchronization.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] collaboration peer vpn-instance a 1.1.1.2 local 1.1.1.1 sync-port 6000

Related commands

collaboration peer redirect

Use collaboration peer redirect to configure the redirect IP address of an RIR collaboration peer.

Use undo collaboration peer redirect to delete the redirect IP address of an RIR collaboration peer.

Syntax

collaboration peer [ vpn-instance vpn-instance-name ] peer-ipv4-address redirect [ vpn-instance redirect-vpn-instance-name ] redirect-ipv4-address

undo collaboration peer [ vpn-instance vpn-instance-name ] peer-ipv4-address redirect [ vpn-instance redirect-vpn-instance-name ]

Default

No redirect IP address is configured for an RIR collaboration peer.

Views

RIR view

Predefined user roles

network-admin

context-admin

Parameters

vpn-instance vpn-instance-name: Specifies the MPLS L3VPN instance on which the local and peer devices establish RIR collaboration relationship. The vpn-instance-name argument is a case-sensitive string of 1 to 31 characters. If the local and peer devices establish RIR collaboration relationship on the public network, do not specify this option.

peer-ipv4-address: Specifies an RIR collaboration peer by its IPv4 address.

vpn-instance redirect-vpn-instance-name: Specifies the MPLS L3VPN instance for the packets to be redirected to the redirect IPv4 address of the peer device. The redirect-vpn-instance-name argument is a case-sensitive string of 1 to 31 characters. If the packets to be redirected belong to the public network, do not specify this option.

redirect-ipv4-address: Specifies the redirect IPv4 address of the peer device.

Usage guidelines

Use this command on both the local and peer devices that have established RIR collaboration relationship. This command specifies the redirect IP address for packets redirected to a peer device on the public network or a VPN instance. When the local device selects links from the peer device to forward packets on the public network or a VPN instance, it performs the following operations:

· Looks up the routing table of the public network or VPN instance based on the redirect IP address.

· Forwards the packets to the peer device through the RIR dedicated link.

If you execute the undo form of this command without the vpn-instance redirect-vpn-instance-name option for a peer, the redirect IPv4 address of the public network is deleted for the peer.

If you execute this command multiple times for the same peer on the public network or in the same redirect VPN instance, the most recent configuration takes effect.

Examples

# Specify 2.1.1.1 as the redirect IP address in VPN instance b for peer device 1.1.1.2 in VPN instance a.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] collaboration peer vpn-instance a 1.1.1.2 redirect vpn-instance b 2.1.1.1

Related commands

collaboration peer local

delay threshold

Use delay threshold to set the link delay threshold.

Use undo delay threshold to restore the default.

Syntax

delay threshold threshold-value

undo delay threshold

Default

The link delay threshold is 10 milliseconds.

Views

SLA view

Predefined user roles

network-admin

context-admin

Parameters

threshold-value: Sets the link delay threshold, in the range of 10 to 60000 milliseconds.

Usage guidelines

Link delay refers to the interval between the sending time and receiving time of a packet.

The shorter the delay time, the higher the link quality.

A flow template uses the link delay threshold in its associated SLA to filter links that meet the link delay requirement.

Examples

# In SLA 1, set the link delay threshold to 1000 milliseconds.

<Sysname> system-view

[Sysname] sla 1

[Sysname-sla-1] delay threshold 1000

display tunnel flow-statistics

Use display tunnel flow-statistics to display flow ID-based traffic rate statistics for tunnels.

Syntax

display tunnel flow-statistics [ flow flow-id [ interface tunnel number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

flow flow-id: Specifies a flow template by its flow ID, in the range of 1 to 65535. If you do not specify a flow ID, this command displays statistics for all flow templates.

interface tunnel number: Specifies a tunnel interface by its tunnel interface number. The value range for the number argument is 1 to 65535. If you do not specify a tunnel interface, this command displays statistics about the specified flow template for all tunnel interfaces.

Examples

# Display flow ID-based traffic rate statistics for tunnels.

<Sysname> display tunnel flow-statistics

RIR flow 100:

Interface Out pps Out bps

Tunnel1 10 4800

Tunnel2 20 9600

RIR flow 101:

Interface Out pps Out bps

Tunnel3 10 4800

Tunnel4 20 9600

Table 1 Command output

Field	Description
RIR flow	Flow ID of an RIR flow template.
Interface	Tunnel interface name.
Out pps	Number of outgoing packets per second.
Out bps	Number of outgoing bits per second.

Related commands

reset tunnel flow-statistics

tunnel flow-statistics enable

expect-bandwidth

Use expect-bandwidth to specify the per-session expected bandwidth.

Use undo expect-bandwidth to restore the default.

Syntax

expect-bandwidth bandwidth

undo expect-bandwidth

Default

The per-session expected bandwidth is 0 kbps.

Views

Flow template view

Predefined user roles

network-admin

context-admin

Parameters

bandwidth: Specifies the bandwidth in kbps, in the range of 1 to 400000000.

Usage guidelines

The per-session expected bandwidth configured by using this command is not the actual bandwidth used by a session. It is only a value estimated based on user services.

When performing RIR link selection for a session, the device performs bandwidth detection based on the per-session expected bandwidth configured in the flow template to which the session belongs. If the used bandwidth plus the per-session expected bandwidth of a candidate link is less than 80% of its total bandwidth, the current available bandwidth of the candidate link meets the session bandwidth requirements. The link passes the bandwidth detection.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the per-session expected bandwidth to 10 kbps in flow template 1.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] flow 1

[Sysname-rir-flow-1] expect-bandwidth 10

Related commands

flow

Use flow to create a flow template and enter its view, or enter the view of an existing flow template.

Use undo flow to delete a flow template.

Syntax

flow flow-id

undo flow flow-id

Default

No flow templates exist.

Views

RIR view

Predefined user roles

network-admin

context-admin

Parameters

flow-id: Specifies a flow ID for the flow template. The flow ID is a hexadecimal string in the range of 0 to ffffff.

Usage guidelines

Use a flow template to define link selection policies (including the quality policy and link preference) that can filter qualified links for a type of service flow. After the device identifies the service of a packet based on the quintuple and DSCP of the packet, it assigns a flow ID to the packet according to the QoS policy applied to the service. Then, RIR selects a qualified link for the packet based on the link selection policies of the flow template that uses the flow ID.

Examples

# Create flow template 1 and enter its view.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] flow 1

[Sysname-rir-flow-1]

Related commands

remark flow-id (ACL and QoS Command Reference)

flow priority-based-schedule bandwidth-threshold

Use flow priority-based-schedule bandwidth-threshold to set the bandwidth usage thresholds for flow priority-based traffic scheduling.

Use undo flow priority-based-schedule bandwidth-threshold to restore the default.

Syntax

flow priority-based-schedule bandwidth-threshold upper upper-threshold lower lower-threshold

undo flow priority-based-schedule bandwidth-threshold

Default

The bandwidth usage upper threshold is 90% and the bandwidth usage lower threshold is 20%.

Views

RIR view

Predefined user roles

network-admin

context-admin

Parameters

upper upper-threshold: Sets the bandwidth usage upper threshold in percentage, in the range of 1 to 100. The upper threshold must be greater than or equal to the lower threshold.

lower lower-threshold: Sets the bandwidth usage lower threshold in percentage, in the range of 1 to 100.

Usage guidelines

If flow priority-based traffic scheduling is enabled, traffic scheduling is triggered when the bandwidth usage of a link exceeds the upper threshold. The scheduling might be last for several scheduling periods. Within each scheduling period, RIR redistributes the current lowest priority flow on this link to other links. The scheduling does not stop until the bandwidth usage of all links for the current lowest priority flow is below the lower threshold or only the highest priority flow is left on this link.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Enable flow priority-based traffic scheduling and set the bandwidth usage upper threshold and lower threshold to 80% and 30%, respectively.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] flow priority-based-schedule enable

[Sysname-rir] flow priority-based-schedule bandwidth-threshold upper 80 lower 30

Related commands

flow priority-based-schedule enable

Use flow priority-based-schedule enable to enable flow priority-based traffic scheduling.

Use undo flow priority-based-schedule enable to disable flow priority-based traffic scheduling.

Syntax

flow priority-based-schedule enable

undo flow priority-based-schedule enable

Default

Flow priority-based traffic scheduling is disabled.

Views

RIR view

Predefined user roles

network-admin

context-admin

Usage guidelines

To ensure that services with higher priority preferentially use link resources, enable flow priority-based traffic scheduling.

The priority of a flow that matches a flow template is determined by the ID of the SLA associated with that flow template. The greater the SLA ID, the higher the flow priority. To specify an SLA for a flow template, use the quality-policy command. If the command is not configured in a flow template, flows that match the flow template have the lowest priority.

Examples

# Enable flow priority-based traffic scheduling.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] flow priority-based-schedule enable

Related commands

quality-policy

sla

flow priority-based-schedule schedule-period

Use flow priority-based-schedule schedule-period to set the scheduling period for flow priority-based traffic scheduling.

Use undo flow priority-based-schedule schedule-period to restore the default.

Syntax

flow priority-based-schedule schedule-period schedule-period-value

undo flow priority-based-schedule schedule-period

Default

The scheduling period for flow priority-based traffic scheduling is 30 seconds.

Views

RIR view

Predefined user roles

network-admin

context-admin

Parameters

schedule-period-value: Sets the scheduling period for flow priority-based traffic scheduling, in seconds. The value range for this argument is 15 to 65535.

Usage guidelines

If flow priority-based traffic scheduling is enabled, traffic scheduling is triggered when the bandwidth usage of a link exceeds the upper threshold. The scheduling might be last for several scheduling periods. Within each scheduling period (set by using this command), RIR redistributes the current lowest priority flow on this link to other links. The scheduling does not stop until the bandwidth usage of all links for the current lowest priority flow is below the lower threshold or only the highest priority flow is left on this link.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the scheduling period for flow priority-based traffic scheduling to 20 seconds.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] flow priority-based-schedule enable

[Sysname-rir] flow priority-based-schedule schedule-period 20

jitter threshold

Use jitter threshold to set the link jitter threshold.

Use undo jitter threshold to restore the default.

Syntax

jitter threshold threshold-value

undo jitter threshold

Default

The link jitter threshold is 100 milliseconds.

Views

SLA view

Predefined user roles

network-admin

context-admin

Parameters

threshold-value: Sets the link jitter threshold, in the range of 0 to 3600000 milliseconds.

Usage guidelines

The jitter time equals the receiving time interval between two consecutive packets minus the sending time interval between the two consecutive packets. The shorter the jitter time, the higher the link quality. A flow template uses the jitter threshold in its associated SLA to filter links that meet the jitter requirement.

Examples

# In SLA 1, set the link jitter threshold to 1000 milliseconds.

<Sysname> system-view

[Sysname] sla 1

[Sysname-sla-1] jitter threshold 1000

link-select delay

Use link-select delay to set the link selection delay.

Use undo link-select delay to restore the default.

Syntax

link-select delay delay

undo link-select delay

Default

The link selection delay is 60 seconds.

Views

RIR view

Predefined user roles

network-admin

context-admin

Parameters

delay: Sets the link selection delay in seconds, in the range of 1 to 65535.

Usage guidelines

To improve packet forwarding efficiency, the device does not repeatedly perform link selection for traffic of the same session. After the device performs link selection for traffic of a session, it forwards the subsequent traffic of that session according to the previous link selection result. Link reselection is triggered when any link in the session's flow template has one of the following changes:

· The quality of a link becomes qualified from unqualified or the quality of a link becomes unqualified from qualified.

· The bandwidth usage of a link has reached the maximum.

To avoid frequent link selection caused by link flapping, RIR defines a link selection delay and link selection suppression period.

After the device performs link selection, it starts the link selection suppression period if the period has been configured. Within the link selection suppression period, the device does not perform link reselection, but it maintains the link state data. When the link selection suppression period ends, the link selection delay timer starts. If the link state still meets the conditions that can trigger link reselection when the delay timer expires, the device performs link reselection. If the link state changes to not meet the conditions that can trigger link reselection within the delay time, the device does not perform link reselection.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the link selection delay to 30 seconds.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] link-select delay 30

Related commands

link-select suppress-period

Use link-select suppress-period to set the link selection suppression period.

Use undo link-select suppress-period to restore the default.

Syntax

link-select suppress-period period-value

undo link-select suppress-period

Default

No link selection suppression period is configured. The device does not start the link selection suppression period after a link selection.

Views

RIR view

Predefined user roles

network-admin

context-admin

Parameters

period-value: Sets the link selection suppression period in seconds, in the range of 1 to 131070.

Usage guidelines

To avoid frequent link selection caused by link flapping, configure a link selection suppression period. The device starts the link selection suppression period after it performs a link selection.

Within the link selection suppression period, the device does not perform link reselection, but it maintains the link state data. When the link selection suppression period ends, the link selection delay timer starts. If the link state still meets the conditions that can trigger link reselection when the delay timer expires, the device performs link reselection. If the link state changes to not meet the conditions that can trigger link reselection within the delay time, the device does not perform link reselection.

As a best practice, set the link selection suppression period to a multiple of the link selection delay time. Make sure the suppression period is at least double of the link selection delay time.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the link selection suppression period to 60 seconds.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] link-select suppress-period 60

Related commands

link-select delay

load-balance per-packet enable

Use load-balance per-packet enable to enable per-packet load balancing.

Use undo load-balance enable to restore the default.

Syntax

load-balance per-packet enable

undo load-balance enable

Default

The RIR global link load balancing mode applies.

Views

Flow template view

Predefined user roles

network-admin

context-admin

Usage guidelines

Based on link bandwidth, RIR supports the following link load balancing modes:

· Per-session weight-based link selection mode—RIR global link load balancing mode that takes effect on all RIR flows. This mode can distribute the sessions that match the same flow template to different links according to the weights of the links. RIR selects only one link to transmit a session.

· Per-session periodic link adjustment mode—RIR global link load balancing mode that takes effect on all RIR flows. This mode not only can distribute the sessions that match the same flow template to different links, but also can periodically adjust links for the sessions. Within one adjustment period, RIR selects only one link to transmit a session.

· Per-packet mode—Flow-specific link load balancing mode that takes effect only on sessions that match the flow template where this mode is enabled. This mode can distribute the same session to different links for transmission.

The mechanisms of the per-packet mode are as follows:

· For preference-based primary link selection, preference-based backup link selection, and quality tolerant link selection—If multiple links with the same preference meet the requirements of a session, all these links are candidate optimal links for this session. When forwarding traffic for the session, the device distributes the traffic to these links packet by packet according to the remaining bandwidth weight of each link.

For example, the device needs 10 Mbps of bandwidth to transmit traffic for a session with flow ID 1. Links 1 and 2 are available to transmit traffic for this session. The remaining bandwidth of link 1 is 20 Mbps and the remaining bandwidth of link 2 is 30 Mbps. Finally, the traffic of this session uses 4 Mbps of bandwidth on link 1 and 6 Mbps of bandwidth on link 2.

· For bandwidth tolerant link selection—If multiple links meet the requirements of a session, all these links are candidate optimal links for this session. When forwarding traffic for the session, the device distributes the traffic to these links packet by packet. Each link has the same probability to be selected.

Because packets of the same session are distributed to multiple links, the receiver might receive out-of-order packets. As a best practice, do not enable per-packet load balancing for order-sensitive services (except the services that use protocols to maintain a correct packet order, for example, TCP).

Examples

# Enable per-packet load balancing mode in flow template with flow ID 1.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] flow 1

[Sysname-rir-flow-1] load-balance per-packet enable

load-balance per-session periodic-adjust adjust-interval

Use load-balance per-session periodic-adjust adjust-interval to set the adjustment interval for per-session periodic link adjustment mode.

Use undo load-balance per-session periodic-adjust adjust-interval to restore the default.

Syntax

load-balance per-session periodic-adjust adjust-interval interval-value

undo load-balance per-session periodic-adjust adjust-interval

Default

The adjustment interval for per-session periodic link adjustment mode is 30 seconds.

Views

RIR view

Predefined user roles

network-admin

context-admin

Parameters

interval-value: Sets the adjustment interval for per-session periodic link adjustment mode, in the range of 15 to 65535 seconds.

Usage guidelines

In per-session periodic link adjustment mode, the device periodically detects the bandwidth usage of all links that have RIR sessions at intervals configured by using this command. RIR reselect links for sessions that match a flow template if the links in the flow template meets the following requirements: The difference between the largest remaining bandwidth ratio and the smallest remaining bandwidth ratio becomes larger than or equal to the periodic adjustment upper threshold. The link adjustment might be last for several adjustment intervals. RIR stops link adjustment if one of the following requirements is met:

· The difference between the largest remaining bandwidth ratio and the smallest remaining bandwidth ratio of the links becomes smaller than the periodic adjustment lower threshold.

· The adjustment interval is the 20th interval after link reselection is triggered.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the adjustment interval for per-session periodic link adjustment mode to 20 seconds.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] load-balance per-session periodic-adjust adjust-interval 20

Related commands

load-balance per-session periodic-adjust enable

load-balance per-session periodic-adjust threshold

load-balance per-session periodic-adjust enable

Use load-balance per-session periodic-adjust enable to enable per-session periodic link adjustment mode.

Use undo load-balance per-session periodic-adjust enable to restore the default.

Syntax

load-balance per-session periodic-adjust enable

undo load-balance per-session periodic-adjust enable

Default

The per-session weight-based link selection mode is used.

Views

RIR view

Predefined user roles

network-admin

context-admin

Usage guidelines

Based on link bandwidth, RIR supports the following link load balancing modes:

· Per-packet mode—Flow-specific link load balancing mode that takes effect only on traffic that matches the flow template where this mode is enabled. This mode can distribute the same session to different links for transmission.

The mechanisms of the per-session periodic link adjustment mode are as follows:

· For preference-based primary link selection, preference-based backup link selection, and quality tolerant link selection—If multiple links with the same preference meet the requirements of a flow template, RIR selects one optimal link for each session of the flow template from these links. RIR preferentially selects the link with the lowest bandwidth usage for a session. The bandwidth usage adopted by RIR is the actual bandwidth usage plus the per-session expected bandwidth.

· For bandwidth tolerant link selection—If multiple links meet the requirements of a flow template, RIR selects one optimal link for each session of the flow template from these links. The link selected the last time for a session takes precedence over the other links for that session. If RIR performs link selection for a session for the first time, it selects a link based on the remaining bandwidth weights of the available links.

In per-session periodic link adjustment mode, the device periodically detects the bandwidth usage of all links that have RIR sessions at the configured adjustment intervals. RIR reselect links for sessions that match a flow template if the links in the flow template meets the following requirements: The difference between the largest remaining bandwidth ratio and the smallest remaining bandwidth ratio becomes larger than or equal to the periodic adjustment upper threshold. The link adjustment might be last for several adjustment intervals. RIR stops link adjustment if one of the following requirements is met:

· The difference between the largest remaining bandwidth ratio and the smallest remaining bandwidth ratio of the links becomes smaller than the periodic adjustment lower threshold.

· The adjustment interval is the 20th interval after link reselection is triggered.

For a flow template, the per-packet load balancing mode takes precedence over the global per-session periodic link adjustment mode. If the per-packet load balancing mode is not enabled for a flow template, the flow template uses the global link load balancing mode.

Examples

# Enable per-session periodic link adjustment mode.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] load-balance per-session periodic-adjust enable

Related commands

load-balance per-session periodic-adjust adjust-interval

load-balance per-session periodic-adjust threshold

Use load-balance per-session periodic-adjust threshold to set the periodic adjustment thresholds in per-session periodic link adjustment mode.

Use undo load-balance per-session periodic-adjust threshold to restore the default.

Syntax

load-balance per-session periodic-adjust threshold upper upper-threshold-value lower lower-threshold-value

undo load-balance per-session periodic-adjust threshold

Default

The periodic adjustment upper threshold is 50% and the periodic adjustment lower threshold is 20%.

Views

RIR view

Predefined user roles

network-admin

context-admin

Parameters

upper upper-threshold-value: Sets the periodic adjustment upper threshold, in the range of 1 to 100. The upper-threshold-value argument specifies the largest difference allowed between the largest remaining bandwidth ratio and the smallest remaining bandwidth ratio of all available links.

lower lower-threshold-value: Sets the periodic adjustment lower threshold, in the range of 1 to 100. After the difference between the largest remaining bandwidth ratio and the smallest remaining bandwidth ratio becomes smaller than this threshold, RIR stops link adjustment.

Usage guidelines

· The difference between the largest remaining bandwidth ratio and the smallest remaining bandwidth ratio of the links becomes smaller than the periodic adjustment lower threshold.

· The adjustment interval is the 20th interval after link reselection is triggered.

The periodic adjustment upper threshold must be greater than or equal to the periodic adjustment lower threshold.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the periodic adjustment upper threshold and the periodic adjustment lower threshold to 60% and 30%, respectively.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] load-balance per-session periodic-adjust threshold upper 60 lower 30

Related commands

load-balance per-session periodic-adjust enable

load-balance per-session periodic-adjust adjust-interval

log enable

Use log enable to enable RIR logging.

Use undo log enable to disable RIR logging.

Syntax

log enable

undo log enable

Default

RIR logging is disabled.

Views

RIR view

Predefined user roles

network-admin

context-admin

Usage guidelines

RIR logs record events occurred during the RIR process, such as link selection and reselection, quality change, bandwidth change, configuration change, and link fault events. The logs help the administrator analyze, maintain, and adjust the RIR network.

RIR logs are flow logs. To output RIR logs, you must also configure flow log features. For more information about flow logs, see Network Management and Monitoring Configuration Guide.

Examples

# Enable RIR logging.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] log enable

Related commands

userlog flow export host (Network Management and Monitoring Command Reference)

userlog flow syslog (Network Management and Monitoring Command Reference)

nqa

Use nqa to create an NQA link quality operation and enter its view, or enter the view of an existing NQA link quality operation.

Use undo nqa to delete an NQA link quality operation.

Syntax

nqa nqa-id

undo nqa nqa-id

Default

No NQA link quality operations exist.

Views

RIR view

Predefined user roles

network-admin

context-admin

Parameters

nqa-id: Specifies an NQA link quality operation by its ID, in the range of 0 to 128.

Usage guidelines

An NQA link quality operation allows a flow template to start UDP jitter probes based on the probe parameters in the operation in order to detect the quality of links.

You can configure a quality policy for a flow template to associate the flow template with an SLA and an NQA link quality operation. The device monitors the quality of links in the flow template based on the NQA link quality operation and compares the NQA probe results with the thresholds in the SLA. If all parameter values in the probe results of a link are lower than or equal to the thresholds in the SLA, the link is qualified for the flow.

To differentiate service flows that have different link quality requirements, associate the flow templates with NQA link quality operations that contain different probe parameter values. Two NQA link quality operations with different probe parameter values might offer different probe results for the same link.

In a VXLAN network, the NQA link quality probe targets are VXLAN tunnel interfaces enabled with the RIR client.

The device supports a maximum of 129 NQA link quality operations.

Examples

# Create NQA link quality operation 1 and enter its view.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] nqa 1

[Sysname-rir-nqa-1]

Related commands

nqa agent enable (Network Management and Monitoring Command Reference)

quality-policy

packet-loss threshold

Use packet-loss threshold to set the packet loss threshold.

Use undo packet-loss threshold to restore the default.

Syntax

packet-loss threshold threshold-value

undo packet-loss threshold

Default

The packet loss threshold is 100‰.

Views

SLA view

Predefined user roles

network-admin

context-admin

Parameters

threshold-value: Sets the packet loss threshold, in the range of 0 to 1000 in permillage.

Usage guidelines

The packet loss ratio is the number of lost packets to the total number of sent packets. The lower the packet loss ratio, the higher the link quality. A flow template uses the packet loss threshold in its associated SLA to filter links that meet the packet loss requirement.

Examples

# In SLA 1, set the packet loss threshold to 500‰.

<Sysname> system-view

[Sysname] sla 1

[Sysname-sla-1] packet-loss threshold 500

Related commands

sla

path link-type index preference

Use path link-type index preference to specify a link preference for a type of links with a specific link index in a flow template.

Use undo path link-type index preference to restore the default.

Syntax

path link-type { 4g | internet | mpls | mstp } index link-index preference preference

undo path link-type { 4g | internet | mpls | mstp } index link-index

Default

No link preference is specified for a type of links with a specific link index in a flow template.

Views

Flow template view

Predefined user roles

network-admin

context-admin

Parameters

4g: Specifies the 4G type.

internet: Specifies the Internet type.

mpls: Specifies the MPLS type.

mstp: Specifies the MSTP type.

index link-index: Specifies a link index in the range of 1 to 65535.

preference preference: Specifies a link preference in the range of 1 to 255. The lower the value, the higher the priority.

Usage guidelines

RIR preferentially selects links with higher preference.

The link type and link index specified in this command identify links on a VSI interface. .Because a VSI interface can have only one VXLAN tunnel between a hub and spoke, this command sets the link preference for a specific VXLAN tunnel.

You can assign the same link preference value to different links in the same flow template.

Examples

# In flow template 1, set the preference of MPLS link 1 to 100.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] flow 1

[Sysname-flow-1] path link-type mpls index 1 preference 100

Related commands

rir link-type

probe connect

Use probe connect to configure NQA link connectivity probe parameters.

Use undo probe connect to restore the default.

Syntax

probe connect interval interval timeout timeout

undo probe connect

Default

The NQA link connectivity probe interval is 100 milliseconds. The timeout time is 3000 milliseconds for waiting for a response to a link connectivity probe packet.

Views

RIR view

Predefined user roles

network-admin

context-admin

Parameters

interval interval: Sets the NQA link connectivity probe interval in milliseconds. The value range for the interval argument is 0 to 604800000. The value of 0 represents that only one probe is performed.

timeout timeout: Sets the timeout time for waiting for a response to a link connectivity probe packet. The value range for the timeout argument is 10 to 3600000 milliseconds.

Usage guidelines

The device starts to detect the connectivity of all links in flow templates after RIR is enabled. Spokes (RIR clients) performs consecutive probes at the configured intervals and wait for responses for the probe packets. If an RIR client has not received any responses on a link when the probe packet timeout timer expires, the client determines that the link has connectivity issues.

Setting a shorter probe interval obtains more precise probe results but requires more system resources.

Set a shorter probe packet timeout time if the requirement for link quality is high.

In a VXLAN network, the probe targets are VXLAN tunnel interfaces enabled with the RIR client.

Examples

# Set the NQA link connectivity probe interval to 30 milliseconds, and set the timeout time to 20 milliseconds for waiting for a response to a link connectivity probe packet.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] probe connect interval 30 timeout 20

Related commands

client enable

probe sync-port

server enable

probe interval

Use probe interval to set the NQA link quality probe interval.

Use undo probe interval to restore the default.

Syntax

probe interval interval

undo probe interval

Default

The NQA link quality probe interval is 100 milliseconds.

Views

NQA link quality operation view

Predefined user roles

network-admin

context-admin

Parameters

interval: Sets the NQA link quality probe interval, in the range of 0 to 604800000 milliseconds.

Usage guidelines

Use this command to specify the intervals at which the NQA client performs consecutive probes.

Examples

# In NQA link quality operation 1, set the probe interval to 60 milliseconds.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] nqa 1

[Sysname-rir-nqa-1] probe interval 60

Related commands

nqa

probe packet-dscp

Use probe packet-dscp to set the DSCP value of NQA link quality probe packets.

Use undo probe packet-dscp to restore the default.

Syntax

probe packet-dscp dscp-value

undo probe packet-dscp

Default

The DSCP value of NQA link quality probe packets is 63.

Views

NQA link quality operation view

Predefined user roles

network-admin

context-admin

Parameters

dscp-value: Sets the DSCP value of NQA link quality probe packets, in the range of 0 to 63. The larger the value, the higher the priority.

Usage guidelines

Assign different DSCP values to the probe packets of different NQA link quality operations to affect the priority of links in the flow templates associated with the operations.

Examples

# In NQA link quality operation 1, set the DSCP value of probe packets to 10.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] nqa 1

[Sysname-rir-nqa-1] probe packet-dscp 10

Related commands

nqa

probe packet-interval

Use probe packet-interval to set the intervals at which NQA link quality probe packets are sent.

Use undo probe packet-interval to restore the default.

Syntax

probe packet-interval interval

undo probe packet-interval

Default

NQA link quality probe packets are sent at intervals of 20 milliseconds.

Views

NQA link quality operation view

Predefined user roles

network-admin

context-admin

Parameters

interval: Sets the probe packet sending interval, in the range of 10 to 60000 milliseconds.

Usage guidelines

The device performs consecutive NQA link quality probes at intervals set by using the probe interval command and it sends multiple probe packets at each probe. The probe packet-interval command sets the probe packet sending interval within a probe.

Examples

# In NQA link quality operation 1, set the probe packet sending interval to 10 milliseconds.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] nqa 1

[Sysname-rir-nqa-1] probe packet-interval 10

Related commands

nqa

probe packet-number

Use probe packet-number to set the number of NQA link quality probe packets sent per probe.

Use undo probe packet-number to restore the default.

Syntax

probe packet-number number

undo probe packet-number

Default

An NQA client sends 100 NQA link quality probe packets per probe.

Views

NQA link quality operation view

Predefined user roles

network-admin

context-admin

Parameters

number: Sets the number of NQA link quality probe packets sent per probe, in the range of 10 to 1000.

Usage guidelines

The device performs consecutive NQA link quality probes at intervals set by using the probe interval command and it sends multiple probe packets at each probe. The probe packet-number command sets the number of probe packets sent at each probe.

Examples

# In NQA link quality operation 1, set the number of link quality probe packets sent per probe to 100.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] nqa 1

[Sysname-rir-nqa-1] probe packet-number 100

Related commands

nqa

probe packet-timeout

Use probe packet-timeout to set the timeout time for waiting for a response to an NQA link quality probe packet.

Use undo probe packet-timeout to restore the default.

Syntax

probe packet-timeout packet-timeout

undo probe packet-timeout

Default

The timeout time is 3000 milliseconds.

Views

NQA link quality operation view

Predefined user roles

network-admin

context-admin

Parameters

packet-timeout: Sets the timeout time for waiting for a response to an NQA link quality probe packet. The value range for this argument is 10 to 3600000 milliseconds.

Usage guidelines

A probe packet times out on an NQA client if the NQA client fails to receive any response to the probe packet when the probe packet timeout timer expires.

Examples

# In NQA link quality operation 1, set the NQA link quality probe packet timeout time to 200 milliseconds.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] nqa 1

[Sysname-rir-nqa-1] probe packet-timeout 200

Related commands

nqa

probe port

Use probe port to specify a destination port for NQA link quality probes.

Use undo probe port to restore the default.

Syntax

probe port port-number

undo probe port

Default

No destination port is specified for NQA link quality probes.

Views

NQA link quality operation view

Predefined user roles

network-admin

context-admin

Parameters

port-number: Specifies a destination port number in the range of 1024 to 65535.

Usage guidelines

Use this command for an NQA client. The destination port number must be the same as the listening port number on the NQA server.

Examples

# In NQA link quality operation 1, set the NQA link quality probe destination port to 65500.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] nqa 1

[Sysname-rir-nqa-1] probe port 65500

Related commands

nqa

probe sync-port

Use probe sync-port to specify a port for synchronizing probe information between the RIR client and the RIR server.

Use undo probe sync-port to restore the default.

Syntax

probe sync-port port-number

undo probe sync-port

Default

No port is specified for synchronizing probe information between the RIR client and the RIR server.

Views

RIR view

Predefined user roles

network-admin

context-admin

Parameters

port-number: Specifies a TCP port number in the range of 1024 to 65535.

Usage guidelines

Specify the same synchronization port on the RIR client and server for successful synchronization of link quality probe results.

Examples

# Set the port to 65550 for synchronizing probe information between the RIR client and the RIR server.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] probe sync-port 65550

Related commands

client enable

probe connect

server enable

quality-policy

Use quality-policy to configure a quality policy for a flow template.

Use undo quality-policy to restore the default.

Syntax

quality-policy sla sla-id nqa nqa-id

undo quality-policy

Default

No quality policy is configured for a flow template.

Views

Flow template view

Predefined user roles

network-admin

context-admin

Parameters

sla sla-id: Specifies an SLA by its ID, in the range of 0 to 128. The specified SLA must exist on the device.

nqa nqa-id: Specifies an NQA link quality operation by its ID, in the range of 0 to 128. The specified NQA link quality operation must exist.

Usage guidelines

Use this command to specify an SLA and an NQA link quality operation for a flow template. The device monitors the link quality based on the NQA link quality operation and compares the NQA probe results with the thresholds set in the SLA. The device selects only links that meet the quality requirements of the SLA for traffic that matches the flow template.

For flow priority-based traffic scheduling, the priority of a flow that matches a flow template is determined by the SLA ID specified in the quality policy of that flow template. The greater the SLA ID, the higher the flow priority. If no quality policy is configured for a flow template, flows that match the flow template have the lowest priority.

You can specify only one SLA and one NQA link quality operation for the quality policy of a flow template. However, you can specify the same SLA or NQA link quality operation for the quality policies of multiple flow templates.

If you execute this command multiple times for a flow template, the most recent configuration takes effect.

Examples

# Configure the quality policy of flow template 1 to associate SLA 2 with NQA link quality operation 1.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] flow 1

[Sysname-rir-flow-1] quality-policy sla 2 nqa 1

Related commands

flow priority-based-schedule enable

nqa

sla

reset tunnel flow-statistics

Use reset tunnel flow-statistics to clear flow ID-based traffic rate statistics for tunnels.

Syntax

reset tunnel flow-statistics [ flow flow-id [ interface tunnel number ] ]

Views

User view

Predefined user roles

network-admin

context-admin

context-operator

Parameters

flow flow-id: Specifies a flow template by its flow ID, in the range of 1 to 65535. If you do not specify a flow ID, this command clears statistics for all flow templates.

interface tunnel number: Specifies a tunnel interface by its tunnel interface number. If you do not specify a tunnel interface, this command clears statistics about the specified flow template for all tunnel interfaces.

Examples

# Clear flow ID-based traffic rate statistics for tunnels.

<Sysname> reset tunnel flow-statistics

Related commands

display tunnel flow-statistics

tunnel flow-statistics enable

rir

Use rir to enable the RIR process and enter RIR view, or directly enter RIR view if the RIR process is already enabled.

Use undo rir to disable the RIR process.

Syntax

rir

undo rir

Default

The RIR process is not enabled.

Views

System view

Predefined user roles

network-admin

context-admin

Usage guidelines

In a hub-spoke network, you must enable the RIR process on all hubs and spokes.

Examples

# Enable the RIR process and enter RIR view.

<Sysname> system-view

[Sysname] rir

[Sysname-rir]

rir backup

Use rir backup to configure a tunnel as an RIR backup tunnel.

Use undo rir backup to restore the default.

Syntax

rir backup

undo rir backup

Default

A tunnel is an RIR primary tunnel.

Views

VXLAN tunnel interface view

Predefined user roles

network-admin

context-admin

Usage guidelines

This command enables the RIR process if the RIR process has not been enabled. The undo form of this command does not disable the RIR process.

RIR selects qualified primary links prior to qualified backup links.

A spoke is typically connected to both a primary hub and a backup hub. You can specify the tunnels connected to the backup hub as backup tunnels. If no suitable link is available to reach the primary hub, the spoke can forward traffic through the backup tunnels to the backup hub to ensure service continuity.

Examples

# Configure VXLAN tunnel Tunnel 1 as an RIR backup tunnel.

<Sysname> system-view

[Sysname] interface tunnel1 mode vxlan

[Sysname-Tunnel1] rir backup

rir collaboration-link-group

Use rir collaboration-link-group to assign a VXLAN tunnel to an RIR collaboration link group.

Use undo rir collaboration-link-group to restore the default.

Syntax

rir collaboration-link-group group-id

undo rir collaboration-link-group

Default

A VXLAN tunnel belongs to the RIR collaboration link group with a group ID of 0.

Views

VXLAN tunnel interface view

Predefined user roles

network-admin

context-admin

Parameters

group-id: Specifies an RIR collaboration link group by its group ID in the range of 1 to 65535.

Usage guidelines

In an RIR collaboration device group, make sure all links to the same device or RIR collaboration device group are assigned to the same RIR collaboration link group. A device in an RIR collaboration device group can select links for service packets from the following links:

· ECMP links configured in the matching flow template on the local device.

· Links configured in the same flow template on devices that belong to the same RIR collaboration device group as the local device. In addition, the links belong to the same RIR collaboration link group as the candidate links on the local device.

You can use this command when RIR is enabled or disabled. However, this command takes effect only when RIR is enabled.

To ensure correct link selection, use this command on each device that belongs to the same RIR collaboration device group. Make sure all links to the same device or RIR collaboration device group are assigned to the same RIR collaboration link group.

In an RIR collaboration device group, make sure the links to different devices or RIR collaboration device groups are assigned to different RIR collaboration link groups.

In different RIR collaboration device groups, the links to the same device or RIR collaboration device group can be assigned to the same RIR collaboration link group. As a best practice to identify links, assign the links to different RIR collaboration link groups.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Assign VXLAN tunnel 1 to RIR collaboration link group 1.

<Sysname> system-view

[Sysname] interface Tunnel 1

[Sysname-Tunnel1] rir collaboration-link-group 1

rir link-type index

Use rir link-type to assign a link type and link index to a VSI interface.

Use undo rir link-type to restore the default.

Syntax

rir link-type { 4g | internet | mpls | mstp } index link-index

undo rir link-type { 4g | internet | mpls | mstp } index link-index

Default

No link type or link index is assigned to a VSI interface.

Views

VSI interface view

Predefined user roles

network-admin

context-admin

Parameters

4g: Specifies the 4G type.

internet: Specifies the Internet type.

mpls: Specifies the MPLS type.

mstp: Specifies the MSTP type.

index link-index: Specifies a link index in the range of 1 to 65535.

Usage guidelines

This command enables the RIR process if the RIR process has not been enabled. The undo form of this command does not disable the RIR process.

The link type and link index together uniquely identify a link between a hub and a spoke. For a flow template to use a link, you must assign a link type and index to the link. Use this command to configure the link type as 4G, Internet, MPLS, or MSTP. The link type only marks the network type of the link and it does not affect packet encapsulation.

VXLAN-based RIR allows a hub and a spoke to have only one VXLAN tunnel for a VSI interface (a VXLAN). By assigning a link type and index to the VSI interface, RIR can identify the VXLAN tunnel between the hub and spoke.

A VSI interface on a hub (or spoke) can have a VXLAN tunnel to each spoke (or hub). The VXLAN tunnels of the same VSI interface are assigned the same link type and link index.

A VSI interface can be associated only with one link type.

You must assign different link indexes to the same type of links on different VSI interfaces.

Examples

# Set the link type to MPLS and link index to 1 on VSI-interface 1.

<Sysname>system-view

[Sysname] interface vsi-interface 1

[Sysname-Vsi-interface1] rir link-type mpls index 1

rir role

Use rir role to enable the RIR client or the RIR server on a VXLAN tunnel interface.

Use undo rir role to restore the default.

Syntax

rir role { client | server }

undo rir role

Default

The default for this command depends on the configuration of the client enable and server enable commands.

Views

VXLAN tunnel interface view

Predefined user roles

network-admin

context-admin

Parameters

client: Specifies the RIR client.

server: Specifies the RIR server.

Usage guidelines

To avoid NQA probes from occupying too many resources on a hub in a hub-spoke network, configure the hub as an RIR server and configure the spokes as RIR clients.

You can enable the RIR client or server globally or on an interface.

· Enabling the RIR client or server globally also enables the RIR client or server for all interfaces on the device. The interfaces can send or receive link quality probe results.

· Enabling the RIR client or server on an interface allows only that interface to send or receive link quality probe results.

Enable the RIR server or RIR client, or use them in combination, depending on the role of the device in the network.

· If the device acts only as a hub, you can enable the RIR server globally.

· If the device acts only as a spoke, you can enable the RIR client globally.

· If the device acts as both a hub and a spoke, you can enable the RIR server and RIR client on the corresponding interfaces.

When you enable the RIR client or server, follow these restrictions and guidelines:

· In a VXLAN network, only tunnel interfaces support enabling the RIR client or server. The RIR server uses the tunnel interfaces to receive link quality probe results synchronized from RIR clients.

· The RIR client and RIR server cannot be both enabled on the same interface.

· If the enabled role (RIR server or client) on an interface is different from the globally enabled role, the interface-specific role takes effect on that interface.

To modify the role of an interface, you must first use the undo rir role command to remove the original role.

Examples

# Enable the RIR server on tunnel interface Tunnel 1.

<Sysname> system-view

[Sysname] interface Tunnel 1 mode vxlan

[Sysname-tunnel1] rir role client

Related commands

client enable

server enable

Use server enable to enable the RIR server globally.

Use undo server enable to disable the RIR server globally.

Syntax

server enable

undo server enable

Default

The RIR server is disabled globally.

Views

RIR view

Predefined user roles

network-admin

context-admin

Usage guidelines

To avoid NQA probes from occupying too many resources on a hub in a hub-spoke network, configure the hub as an RIR server and configure the spokes as RIR clients.

You can enable the RIR server globally or on an interface.

· Enabling the RIR server globally also enables the RIR server for all interfaces on the device. The interfaces can receive link quality probe results synchronized from RIR clients.

· Enabling the RIR server on an interface allows only that interface to receive link quality probe results synchronized from RIR clients.

When you enable the RIR server, follow these restrictions and guidelines:

· In a VXLAN network, only tunnel interfaces support enabling the RIR server. The RIR server uses the tunnel interfaces to receive link quality probe results synchronized from RIR clients.

· The RIR server and RIR client cannot be both enabled on the same interface.

· If the enabled role (RIR server or client) on an interface is different from the globally enabled role, the interface-specific role takes effect on that interface.

Examples

# Enable the RIR server globally.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] server enable

Related commands

client enable

probe connect

probe sync-port

sla

Use sla to create an SLA and enter its view, or enter the view of an existing SLA.

Use undo sla to delete an SLA.

Syntax

sla sla-id

undo sla sla-id

Default

No SLAs exist.

Views

RIR view

Predefined user roles

network-admin

context-admin

Parameters

sla-id: Specifies an SLA ID in the range of 0 to 128.

Usage guidelines

To meet the differentiated requirements of services on link quality, configure a Service Level Agreement (SLA) for each service. An SLA contains a set of parameters to evaluate link quality, including the link delay, jitter, and packet loss thresholds.

The quality policy of a flow template contains an SLA and an NQA link quality operation. By comparing the NQA link quality probe results with the thresholds in the SLA, the device determines whether a link meets the quality requirements of the service. If all parameter values in the probe results of a link are lower than or equal to the thresholds in the SLA, the link is qualified for the service.

The device supports a maximum of 129 SLAs.

Examples

# Create SLA 1 and enter its view.

<Sysname> system-view

[Sysname] rir

[Sysname-rir] sla 1

[Sysname-rir-sla-1]

Related commands

flow priority-based-schedule enable

quality-policy

tunnel flow-statistics enable

Use tunnel flow-statistics enable to enable flow ID-based traffic rate statistics for tunnels.

Use undo tunnel flow-statistics enable to disable flow ID-based traffic rate statistics for tunnels.

Syntax

tunnel flow-statistics enable

undo tunnel flow-statistics enable

Default

Flow ID-based traffic rate statistics for tunnels is disabled.

Views

System view

Predefined user roles

network-admin

context-admin

Examples

# Enable flow ID-based traffic rate statistics for tunnels.

<Sysname> system-view

[Sysname] tunnel flow-statistics enable

Related commands

display tunnel flow-statistics

tunnel flow-statistics interval

Use tunnel flow-statistics interval to set the intervals at which the device collects flow ID-based traffic rate statistics for tunnels.

Use undo tunnel flow-statistics interval to restore the default.

Syntax

tunnel flow-statistics interval interval

undo tunnel flow-statistics interval

Default

The device collects flow ID-based traffic rate statistics for tunnels at intervals of 300 seconds.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

interval: Specifies an interval in the range of 5 to 300 seconds.

Examples

# Enable the device to collect flow ID-based traffic rate statistics for tunnels at intervals of 100 seconds.

<Sysname> system-view

[Sysname] tunnel flow-statistics interval 100

Related commands

tunnel flow-statistics enable

14-Layer 3—IP Routing Command Reference

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us