Login
- Table of Contents
-
- 05-Layer 3—IP Services Command Reference
- 00-Preface
- 01-ARP commands
- 02-IP addressing commands
- 03-DNS commands
- 04-IP forwarding basics commands
- 05-Fast forwarding commands
- 06-Adjacency table commands
- 07-IRDP commands
- 08-IP performance optimization commands
- 09-UDP helper commands
- 10-IPv6 basics commands
- 11-IPv6 fast forwarding commands
- 12-Tunneling commands
- 13-GRE commands
- 14-HTTP redirect commands
- 15-ADVPN commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 04-IP forwarding basics commands | 151.94 KB |
display ip proxy-forward cache
snmp-agent trap enable ip-forwarding
load-balance hash-fields gtp-teid enable
Basic IP forwarding commands
display fib
Use display fib to display FIB entries.
Syntax
display fib | vpn-instance vpn-instance-name ] [ ip-address [ mask | mask-length ] ] [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. To display the FIB entries for the public network, do not specify any VPN instance.
ip-address: Displays the FIB entry that matches the specified destination IP address.
mask: Specifies the mask for the IP address.
mask-length: Specifies the mask length for the IP address. The value range is 0 to 32.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays FIB entries on all cards.
Usage guidelines
If you specify an IP address without a mask or mask length, this command displays the longest matching FIB entry.
If you specify an IP address and a mask or mask length, this command displays the exactly matching FIB entry.
Examples
# Display all FIB entries of the public network.
<Sysname> display fib
Route destination count: 5
Directly-connected host count: 0
Flag:
U:Usable G:Gateway H:Host B:Blackhole D:Dynamic S:Static
R:Relay F:FRR
Destination/Mask Nexthop Flag OutInterface/Token Label
0.0.0.0/32 127.0.0.1 UH InLoop0 Null
1.1.1.0/24 192.168.126.1 USGF MGE0/0/0 Null
127.0.0.0/8 127.0.0.1 U InLoop0 Null
127.0.0.0/32 127.0.0.1 UH InLoop0 Null
127.0.0.1/32 127.0.0.1 UH InLoop0 Null
# Display the FIB entries for VPN vpn1.
<Sysname> display fib vpn-instance vpn1
Route destination count: 6
Directly-connected host count: 0
Flag:
U:Usable G:Gateway H:Host B:Blackhole D:Dynamic S:Static
R:Relay F:FRR
Destination/Mask Nexthop Flag OutInterface/Token Label
0.0.0.0/32 127.0.0.1 UH InLoop0 Null
20.20.20.0/24 20.20.20.25 U MGE0/0/0 Null
20.20.20.0/32 20.20.20.25 UBH MGE0/0/0 Null
20.20.20.25/32 127.0.0.1 UH InLoop0 Null
20.20.20.255/32 20.20.20.25 UBH MGE0/0/0 Null
20.20.20.255/32 2001::1 UBH MGE0/0/0 Null
# Display the FIB entries matching the destination IP address 10.2.1.1.
<Sysname> display fib 10.2.1.1
FIB entry count: 1
Flag:
U:Usable G:Gateway H:Host B:Blackhole D:Dynamic S:Static
R:Relay F:FRR
Destination/Mask Nexthop Flag OutInterface/Token Label
10.2.1.1/32 127.0.0.1 UH InLoop0 Null
Table 1 Command output
|
Field |
Description |
|
Route destination count |
Number of route destination addresses. |
|
Directly-connected host count |
Number of directly-connected hosts that are learned through features such as ARP. |
|
FIB entry count |
Total number of FIB entries. |
|
Destination/Mask |
Destination address and the mask length. |
|
Nexthop |
Next hop address. |
|
Flag |
Flags of routes: · U—Usable route. · G—Gateway route. · H—Host route. · B—Blackhole route. · D—Dynamic route. · S—Static route. · R—Relay route. · F—Fast reroute. |
|
OutInterface/Token |
Output interface/LSP index number. |
|
Label |
Inner label. |
display fib count
Use display fib count to display FIB entry statistics.
Syntax
display fib count [ all | vpn-instance vpn-instance-name ] slot slot-number
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
all: Displays FIB entry statistics for the public network and all VPN instances.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters.
slot slot-number: Specifies a card by its slot number.
Usage guidelines
If you do not specify the all or vpn-instance keyword, this command displays FIB entry statistics for the public network.
Examples
# Display FIB entry statistics for the public network and all VPN instances on slot 10.
<Sysname> system-view
[Sysname] display fib count all slot 10
Total count: 3121
Route destination count: 6
Directly-connected host count: 0
VPN-Instance Name Route destination count Directly-connected host count
1 100 3
vpn1 1000 10
vpn2 2000 2
# Display FIB entry statistics for the public network on slot 10.
<Sysname> system-view
[Sysname] display fib count slot 10
Route destination count: 6
Directly-connected host count: 0
Table 2 Command output
|
Field |
Description |
|
Route destination count |
Number of route destination addresses. |
|
Directly-connected host count |
Number of directly-connected hosts that are learned through features such as ARP. |
|
Total count |
Number of FIB entries. |
|
VPN-Instance Name |
VPN instance name. |
display ip proxy-forward cache
Use display ip proxy-forward cache to display IPv4 data packet forwarding entries on the MPU.
Syntax
display ip proxy-forward cache [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an MPU. If you do not specify an MPU, the command displays the IPv4 data packet forwarding entries of the active MPU.
Usage guidelines
For a FIB-incapable MPU, the MPU does not search the FIB entries when forwarding packets, but sends the packets to the service module. The service module then searches its own FIB entries and is called the proxy module.
When the MPU receives a data flow, it sends the packet header tuple to the hardware. The hardware returns a random proxy module number and the MPU's forwarding module caches a binding entry of the data flow and the proxy module. Subsequent packets of the data flow will be forwarded to the corresponding proxy module based on the cached binding entry, ensuring data flow stability and avoiding packets of the same data flow being forwarded to different proxy modules.
If no traffic is passed through for a data flow for more than 3 seconds, the MPU deletes the corresponding binding entry.
Examples
# Display the cached proxy module entries on the active MPU.
<Sysname> display ip proxy-forward cache
Total number of proxy-forward entries: 2
SIP DIP Protocol ProxyNode
192.168.56.1 192.168.56.2 6 0
192.168.56.2 192.168.56.1 6 0
# Display the cached proxy module entries on the specified MPU.
<Sysname> display ip proxy-forward cache slot 1
Total number of proxy-forward entries: 2
SIP DIP Protocol ProxyNode
192.168.56.3 192.168.56.4 6 1
192.168.56.4 192.168.56.3 6 1
Table 3 Command output
|
Field |
Description |
|
Total number of proxy-forward entries |
Total number of cached proxy module entries. |
|
SIP |
Source IP address of the data flow. |
|
DIP |
Destination IP address of the data flow. |
|
Protocol |
Protocol number of the data flow. |
|
ProxyNode |
Proxy module number. |
display ip-cache
Use display ip-cache to display the cached destination IPv4 address entries of packets on the active and standby modules.
Syntax
display ip-cache [ vpn-instance vpn-instance-name ] [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, this command displays the IPv4 cached entries on the public network.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, the command displays the IPv4 cached entries on the active MPU.
Usage guidelines
Application scenarios
Use this command to view the IPv4 cached entries on the FIB-incapable MPU. This helps determine whether the forwarded IPv4 packets are directly forwarded to the destination module through FIB or transmitted to the proxy module for processing.
Operating mechanism
For a FIB-incapable MPU, both the MPU and the interface module maintain cached entries for the destination IPv4 addresses of the packets. These entries contain the most recent routes that have traffic passing through by the active and standby MPUs. The device delivers the corresponding routes of the cached entries to FIB. When forwarding packets, the device first queries the cached entries. If a cached entry corresponding to the destination address of the packet is found, the device continues to query FIB for packet forwarding. If no corresponding cached entry is found, the device establishes the cached entry and transmits the packet to the proxy module for processing.
The cached entry mechanism enables the MPU to directly forward the locally forwarded packets to the target interface module through FIB. This reduces performance degradation caused by packet transmission between interface modules.
If you do not specify any parameters, the command displays cached entries for the public network of the MPU.
Examples
# Display IPv4 cached entries on the MPU public network.
<Sysname> display ip-cache
Total number of ip-cache entries: 2
Status:BN-Before Notify N-Notified RS-Refresh Start RE-Refresh End
IP address Traffic Flag Status Aging time
192.168.56.1 0x0 N -
192.168.56.2 0x1 RE 400
# Display IPv4 cached entries on the MPU private network.
<Sysname> display ip-cache vpn-instance vpn1
Total number of ip-cache entries: 2
Status:BN-Before Notify N-Notified RS-Refresh Start RE-Refresh End
IP address Traffic Flag Status Aging time
192.168.56.1 0x0 N -
192.168.56.2 0x1 RE 400
Table 4 Command output
|
Field |
Description |
|
Total number of ip-cache entries |
Total number of cached entries for the packet destination IP address. |
|
IP address |
Destination IP address of the packet. |
|
Traffic Flag |
Traffic flag of the IPv4 cached entry: · 0x0—The IPv4 cached entry on this device do not have traffic queries, and the entry does not age. When the entry ages on other devices, it will be synchronously deleted. · 0x1—The IPv4 cached entry on this device have traffic queries, and the system will start an aging timer for the entry. After the timer expires, the entry is deleted. |
|
Status |
Status of the IPv6 cached entry: · BN-Before Notify—The entry has not been notified to routing. · N-Notified—The entry has been notified to routing. · RS-Refresh Start—The routing table starts to issue entries. · RE-Refresh End—Entry issuing by the routing table is complete. |
|
Aging time |
For IPv6 cached entries without traffic marking, the aging time field is set to "-," which indicates that no aging time exists for the entry. For entries with traffic marking, this field may display the aging time in seconds or displays a hyphen (-) if the aging time cannot be obtained. |
fib log enable
Use fib log enable to enable FIB logging.
Use undo fib log enable to disable FIB logging.
Syntax
fib log enable
undo fib log enable
Default
FIB logging is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
The logs are sent to the information center of the device. For the logs to be output correctly, you must also configure the information center on the device. For more information about information center configuration, see Network Management and Monitoring Configuration Guide.
To avoid memory consumption caused by log recording, you can use the undo fib log enable command to disable FIB logging.
Examples
# Enable FIB logging.
<Sysname> system-view
[Sysname] fib log enable
fib max-number
Use fib max-number to specify the maximum number of FIB entries on an interface module.
Use undo fib max-number to restore the default.
Syntax
fib max-number max-number slot slot-number
undo fib max-number
Default
The maximum number of FIB entries on an interface module is the maximum number of FIB entries supported by the device.
Views
System view
Predefined user roles
network-admin
Parameters
max-number: Specifies the maximum number of IPv4 FIB entries on an interface module, in the range of 0 to 4294967295.
slot slot-number: Specifies an interface module by its slot number.
Usage guidelines
To save memory resources, you can use this command to decrease the maximum number of FIB entries on an interface module.
If the value for the max-number argument exceeds the maximum number supported by the device, the configuration does not take effect on interface modules. The maximum number supported by the device is then applied to the interface modules.
If the number of FIB entries has reached max-number on an interface module, the module stops accepting new FIB entries issued by the MPU. The existing services on the module are not affected. If the MPU deletes some old FIB entries and notifies the interface module to delete the entries, the interface module can accept new FIB entries until the upper limit is reached again.
Examples
# Specify the maximum number of FIB entries on the interface module in slot 10 as 1000.
<Sysname> system-view
[Sysname] fib max-number 1000 slot 10
fib smooth
Use fib smooth to perform one-time FIB entry synchronization.
Syntax
fib smooth slot slot-number
Views
System view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies a card by its slot number.
Usage guidelines
Perform this task to synchronize FIB entries from the MPU to the specified interface module.
If the maximum number of IPv4 or IPv6 FIB entries (specified by using the fib max-number or ipv6 fib max-number command) is reached on the interface module, the module stops accepting new entries.
Examples
# Perform one-time FIB entry synchronization.
<Sysname> system-view
[Sysname] fib smooth slot 10
Related commands
fib max-number
ipv6 fib max-number
fib switch-enhance
Use fib switch-enhance to enable FIB route switching optimization.
Use undo fib switch-enhance to restore the default.
Syntax
fib switch-enhance
undo fib switch-enhance
Default
FIB route switching optimization is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
This feature is applicable to scenarios with high service traffic sustainability requirements. It enables the device to keep using the current route until the new route becomes available, instead of disconnecting the current route directly. This prevents packet loss caused by route switch, which might take hundreds of milliseconds.
The device can keep using the current route for a maximum of 10 seconds.
Examples
# Enable FIB route switching optimization.
<Sysname> system-view
[Sysname] fib switch-enhance
ip forwarding
Use ip forwarding to enable IPv4 packet forwarding on an interface that has no IPv4 address configured.
Use undo ip forwarding to disable IPv4 packet forwarding on an interface that has no IPv4 address configured.
Syntax
ip forwarding
undo ip forwarding
Default
If an interface has no IPv4 address configured, it cannot forward IPv4 packets.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
On a device that supports both IPv4 and IPv6, the next hop of an IPv4 packet might be an IPv4 address or an IPv6 address. If the output interface has no IPv4 address configured, the interface cannot forward the IPv4 packet. To solve this problem, execute this command on the interface. This feature allows the interface to forward IPv4 packets even though the interface has no IPv4 address configured.
Examples
# Enable IPv4 packet forwarding on Ten-GigabitEthernet 3/0/1 that has no IPv4 address configured.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 3/0/1
[Sysname-Ten-GigabitEthernet3/0/1] ip forwarding
# Enable IPv4 packet forwarding on VLAN-interface 1 that has no IPv4 address configured.
<Sysname> system-view
[Sysname] interface vlan-interface 1
[Sysname-Vlan-interface1] ip forwarding
ip forwarding-table save
Use ip forwarding-table save to save the IP forwarding entries to a file.
Syntax
ip forwarding-table save filename filename
Views
Any view
Predefined user roles
network-admin
Parameters
filename filename: Specifies the name of a file, a string of 1 to 255 characters. For information about the filename argument, see Fundamentals Configuration Guide.
Usage guidelines
The command automatically creates the file if you specify a nonexistent file. If the file already exists, this command overwrites the file content.
To automatically save the IP forwarding entries periodically, configure a schedule for the device to automatically run the ip forwarding-table save command. For information about scheduling a task, see Fundamentals Configuration Guide.
Examples
# Save the IP forwarding entries to the fib.txt file.
<Sysname> ip forwarding-table save filename fib.txt
ipv6 forwarding
Use ipv6 forwarding to enable IPv6 packet forwarding on an interface that has no IPv6 address configured.
Use undo ipv6 forwarding to disable IPv6 packet forwarding on an interface that has no IPv6 address configured.
Syntax
ipv6 forwarding
undo ipv6 forwarding
Default
If an interface has no IPv6 address configured, it cannot forward IPv6 packets.
Views
Interface view
Predefined user roles
network-admin
Usage guidelines
On a device that supports both IPv4 and IPv6, the next hop of an IPv6 packet might be an IPv4 address or an IPv6 address. If the output interface has no IPv6 address configured, the interface cannot forward the IPv6 packet. To solve this problem, execute this command on the interface. This feature allows the interface to forward IPv6 packets even though the interface has no IPv6 address configured.
Examples
# Enable IPv6 packet forwarding on Ten-GigabitEthernet 3/0/1 that has no IPv6 address configured.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 3/0/1
[Sysname-Ten-GigabitEthernet3/0/1] ipv6 forwarding
# Enable IPv6 packet forwarding on VLAN-interface 1 that has no IPv6 address configured.
<Sysname> system-view
[Sysname] interface vlan-interface 1
[Sysname-Vlan-interface1] ipv6 forwarding
snmp-agent trap enable fib
Use snmp-agent trap enable fib to enable SNMP notifications for FIB events.
Use undo snmp-agent trap enable fib to disable SNMP notifications for FIB events.
Syntax
snmp-agent trap enable fib
undo snmp-agent trap enable fib
Default
SNMP notifications for FIB events are enabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
This feature enables the FIB module to generate SNMP notifications for critical FIB events. The SNMP notifications are sent to the SNMP module. For the SNMP notifications to be sent correctly, you must also configure SNMP. For more information about SNMP configuration, see Network Management and Monitoring Configuration Guide.
Examples
# Disable SNMP notifications for FIB events.
<Sysname> system-view
[Sysname] undo snmp-agent trap enable fib
snmp-agent trap enable ip-forwarding
Use snmp-agent trap enable ip-forwarding to enable SNMP notifications for IP forwarding events.
Use undo snmp-agent trap enable ip-forwarding to disable SNMP notifications for IP forwarding events.
Syntax
snmp-agent trap enable ip-forwarding
undo snmp-agent trap enable ip-forwarding
Default
SNMP notifications for IP forwarding events are enabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
This feature enables the IP forwarding module to generate SNMP notifications for critical IP forwarding events. The SNMP notifications are sent to the SNMP module. For the SNMP notifications to be sent correctly, you must also configure SNMP. For more information about SNMP configuration, see Network Management and Monitoring Configuration Guide.
Examples
# Disable SNMP notifications for IP forwarding events.
<Sysname> system-view
[Sysname] undo snmp-agent trap enable ip-forwarding
Load sharing commands
bandwidth-based-sharing
Use bandwidth-based-sharing to enable IPv4 load sharing based on bandwidth.
Use undo bandwidth-based-sharing to disable IPv4 load sharing based on bandwidth.
Syntax
bandwidth-based-sharing
undo bandwidth-based-sharing
Default
The IPv4 load sharing based on bandwidth is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
This feature load shares flow traffic among multiple output interfaces based on their load percentages. The device calculates the load percentage for each output interface in terms of their expected bandwidths.
Devices that run load sharing protocols, such as Locator/ID Separation Protocol (LISP), implement load sharing based on the ratios defined by these protocols.
Examples
# Enable IPv4 load sharing based on bandwidth.
<Sysname> system-view
[Sysname] bandwidth-based-sharing
display ip load-sharing mode
Use display ip load-sharing mode to display the load sharing mode in use.
Syntax
display ip load-sharing mode slot slot-number
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays the load sharing mode for all cards.
Examples
# Display the load sharing mode in use.
<Sysname> display ip load-sharing mode slot 10
Load-sharing mode: per-flow
Load-sharing options: dest-ip | src-ip | ip-pro | dest-port | src-port | dest-mac | src-mac | ingress-port
Load-sharing algorithm: 1
IP tunnel load-sharing mode: outer
Table 5 Command output
|
Field |
Description |
|
Load-sharing mode |
The load sharing mode in use: · per-packet—Per-packet load sharing. · per-flow—Per-flow load sharing. |
|
Load-sharing options |
Options configured for load sharing: · dest-ip—Identifies flows by packet's destination IP address. · src-ip—Identifies flows by packet's source IP address. · ip-pro—Identifies flows by packet's IP protocol. · dest-port—Identifies flows by packet's destination port number. · src-port—Identifies flows by packet's source port number. · ingress-port—Identifies flows by packet's ingress port. · dest-mac—Identifies flows by packet's destination MAC address. · src-mac—Identifies flows by packet's source MAC address. |
|
Load-sharing algorithm |
Algorithm used by load sharing. |
|
IP tunnel load-sharing mode |
Load sharing for IP tunnel packets: · all—Identifies flows by inner and outer IP header information. · inner—Identifies flows by inner IP header information. · outer—Identifies flows by outer IP header information. |
Related commands
ip load-sharing mode
ip load-sharing mode
Use ip load-sharing mode to configure the load sharing mode.
Use undo ip load-sharing mode to restore the default.
Syntax
ip load-sharing mode { per-flow [ algorithm algorithm-number | [ dest-ip | dest-mac | dest-port | ip-pro | src-ip | src-mac | src-port | ip-tos ] * | per-packet } { global | slot slot-number }
undo ip load-sharing mode [ per-flow { algorithm | tunnel } ] { global | slot slot-number }
Default
The device implements per-flow load sharing. For the default load sharing modes used by cards, see Table 6.
Table 6 Default load sharing modes
|
Packet type |
Default load sharing mode |
|
IP unicast packets |
dest-ip, src-ip, dest-port, src-port |
|
IP multicast packets |
dest-ip, src-ip, dest-port, src-port |
|
Layer 2 frames |
dest-mac, src-mac |
|
MPLS L3VPN packets |
dest-ip, src-ip, dest-port, src-port |
|
MPLS L2VPN packets |
· IP packets: dest-ip, src-ip, dest-port, src-port · Other packets: dest-mac, src-mac |
|
MPLS LSPs |
· IP packets: mpls-label1, mpls-label2, dest-ip, src-ip, dest-port, src-port · Other packets: mpls-label1, mpls-label2, dest-mac, src-mac |
|
Other MPLS packets |
mpls-label1, mpls-label2 |
|
IP tunnel packets |
· IP packets: inner dest-ip, inner src-ip, inner dest-port, inner src-port · Non-termination MPLS packets: mpls-label1, mpls-label2 |
Views
System view
Predefined user roles
network-admin
Parameters
per-flow: Implements per-flow load sharing. If you specify none of the destination IP address, destination MAC address, destination port number, protocol number, source IP address, source MAC address, and source port number, the device performs per-flow load sharing based on the destination IP address and the source IP address of the packets.
algorithm algorithm-number: Specifies an algorithm for per-flow load sharing. The value range for the algorithm-number argument is 0 to 9. If you do not specify an algorithm, the default algorithm number is 0. If you specify an algorithm and then execute the undo ip load-sharing mode command, the algorithm number is set to 0.
dest-ip: Identifies flows by destination IP address.
dest-mac: Identifies flows by destination MAC address.
dest-port: Identifies flows by destination port.
global: Configures the load sharing mode globally.
ip-pro: Identifies flows by protocol number.
ip-tos: Identifies flows by type of service (TOS) of IPv4 packets or the traffic class (TC) of IPv6 packets.
src-ip: Identifies flows by source IP address.
src-mac: Identifies flows by source MAC address.
src-port: Identifies flows by source port.
per-packet: Implements per-packet load sharing.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command configures the load sharing mode for all cards.
Follow these guidelines when you use the ip load-sharing mode command to configure the load sharing mode on SFE-A cards:
· The device does not support the ip-pro keyword.
· The per-flow load sharing modes take effect on a card in the following order:
a. Algorithm-based per-flow load sharing configured globally or on the card (specified by the algorithm algorithm-number option).
b. Per-flow load sharing with a random combination of the dest-ip, dest-mac, dest-port, src-ip, src-mac, and src-port keywords on the card.
c. Global per-flow load sharing with a random combination of the dest-ip, dest-mac, dest-port, src-ip, src-mac, and src-port keywords.
d. Global default load sharing mode.
Examples
# Configure per-packet load sharing on slot 1.
<Sysname> system-view
[Sysname] ip load-sharing mode per-packet slot 10
# Configure per-flow load sharing by destination IP address and source IP address on slot 1.
<Sysname> system-view
[Sysname] ip load-sharing mode per-flow dest-ip src-ip slot 10
# Specify algorithm 1 for per-flow load sharing on slot 1.
<Sysname> system-view
[Sysname] ip load-sharing mode per-flow algorithm 1 slot 10
load-balance hash-fields gtp-teid enable
Use load-balance hash-fields gtp-teid enable to enable GTP tunnel load balancing.
Use undo load-balance hash-fields gtp-teid enable to disable GTP tunnel load balancing.
Syntax
load-balance hash-fields gtp-teid enable
undo load-balance hash-fields gtp-teid enable
Default
GTP tunnel load balancing is disabled.
Views
System view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
With this feature enabled, the device identifies GTP tunnel packets based on the fixed port number (2152) specified by the GTP protocol. It calculates the hash value using the TEID information in the GTP packets and the default load balancing factors. Based on the calculation results, the traffic on the link is aggregated for load balancing and equivalent routing load balancing.
Examples
# Enable GTP tunnel load balancing.
<Sysname> system-view
[Sysname] load-balance hash-fields gtp-teid enable
