- Table of Contents
-
- 09-MPLS Command Reference
- 00-Preface
- 01-Basic MPLS commands
- 02-Static LSP commands
- 03-LDP commands
- 04-MPLS TE commands
- 05-Static CRLSP commands
- 06-RSVP commands
- 07-Tunnel policy commands
- 08-MPLS L3VPN commands
- 09-MPLS L2VPN commands
- 10-VPLS commands
- 11-L2VPN access to L3VPN or IP backbone commands
- 12-MPLS OAM commands
- 13-MCE commands
- Related Documents
-
Title | Size | Download |
---|---|---|
11-L2VPN access to L3VPN or IP backbone commands | 197.51 KB |
Contents
L2VPN access to L3VPN or IP backbone commands
l2vpn fast-forwarding srv6 virtual-ethernet
l2vpn-l3vpn enhance-mode enable
reset counters interface ve-l2vpn
reset counters interface ve-l3vpn
L2VPN access to L3VPN or IP backbone commands
bandwidth
Use bandwidth to set the expected bandwidth for an interface.
Use undo bandwidth to restore the default.
Syntax
bandwidth bandwidth-value
undo bandwidth
Default
The expected bandwidth for an interface is 100000 kbps.
Views
L2VE interface view
L2VE subinterface view
L3VE interface view
L3VE subinterface view
Predefined user roles
network-admin
Parameters
bandwidth-value: Specifies the expected bandwidth in the range of 1 to 400000000 kbps.
Usage guidelines
The expected bandwidth for an interface affects the CBQ bandwidth and the link costs in OSPF, OSPFv3, and IS-IS. For more information, see ACL and QoS Configuration Guide and Layer 3—IP Routing Configuration Guide.
Examples
# Set the expected bandwidth for VE-L2VPN 100 to 10000 kbps.
<Sysname> system-view
[Sysname] interface ve-l2vpn 100
[Sysname-VE-L2VPN100] bandwidth 10000
# Set the expected bandwidth for VE-L3VPN 100 to 10000 kbps.
<Sysname> system-view
[Sysname] interface ve-l3vpn 100
[Sysname-VE-L3VPN100] bandwidth 10000
default
Use default to restore the default settings for an interface.
Syntax
default
Views
L2VE interface view
L2VE subinterface view
L3VE interface view
L3VE subinterface view
Predefined user roles
network-admin
Usage guidelines
CAUTION: The default command might interrupt ongoing network services. Make sure you are fully aware of the impact of this command when you use it on a live network. |
This command might fail to restore the default settings for some commands for reasons such as command dependencies or system restrictions. Use the display this command in interface view to identify these commands. Use their undo forms or follow the command reference to restore their default settings. If your restoration attempt still fails, follow the error message instructions to resolve the problem.
Examples
# Restore the default settings for VE-L2VPN 100.
<Sysname> system-view
[Sysname] interface ve-l2vpn 100
[Sysname-VE-L2VPN100] default
This command will restore the default settings. Continue? [Y/N]:y
# Restore the default settings for VE-L3VPN 100.
<Sysname> system-view
[Sysname] interface ve-l3vpn 100
[Sysname-VE-L3VPN100] default
This command will restore the default settings. Continue? [Y/N]:y
description
Use description to configure the description of an interface.
Use undo description to restore the default.
Syntax
description text
undo description
Default
The description of an interface is VE-L2VPNnumber Interface, for example, VE-L2VPN100 Interface.
Views
L2VE interface view
L2VE subinterface view
L3VE interface view
L3VE subinterface view
Predefined user roles
network-admin
Parameters
text: Specifies a description, a case-sensitive string of 1 to 255 characters.
Usage guidelines
Configure descriptions for different interfaces for identification and management purposes.
You can use the display interface command to display the configured interface description.
Examples
# Configure a description of L2VPN-Terminate for VE-L2VPN 100.
<Sysname> system-view
[Sysname] interface ve-l2vpn 100
[Sysname-VE-L2VPN100] description L2VPN-Terminate
# Configure a description of L3VPN-Access for VE-L3VPN 100.
<Sysname> system-view
[Sysname] interface ve-l3vpn 100
[Sysname-VE-L3VPN100] description L3VPN-Access
display interface ve-l2vpn
Use display interface ve-l2vpn to display L2VE interface information.
Syntax
display interface [ ve-l2vpn [ interface-number | interface-number.subnumber ] ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ve-l2vpn [ interface-number | interface-number.subnumber ]: Displays information about L2VE interfaces or L2VE subinterfaces. The interface-number argument represents the number of an existing L2VE interface. The subnumber argument represents the number of an existing subinterface created on the interface. If you do not specify the ve-l2vpn keyword, this command displays information about all interfaces on the device. If you specify the ve-l2vpn keyword but do not specify the interface-number or interface-number.subnumber argument, this command displays information about all L2VE interfaces.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of interface descriptions.
down: Displays information about interfaces in the physical state of DOWN and the causes. If you do not specify this keyword, the command displays information about interfaces in all states.
Examples
# Display information about interface VE-L2VPN 100.
<Sysname> display interface ve-l2vpn 100
VE-L2VPN100
Interface index: 17805
Current state: UP
Line protocol state: UP
Description: VE-L2VPN100 Interface
Bandwidth: 100000kbps
Maximum transmission unit: 1500
Internet protocol processing: Disabled
IP Packet Frame Type:PKTFMT_ETHNT_2, Hardware Address: 0011-2200-0202
IPv6 Packet Frame Type:PKTFMT_ETHNT_2, Hardware Address: 0011-2200-0202
Link service is PWE3 ethernet mode
Physical: L2VE, baudrate: 100000000 bps
Last clearing of counters: Never
Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Input: 0 packets, 0 bytes, 0 drops
Output: 0 packets, 0 bytes, 0 drops
Table 1 Command output
Field |
Description |
VE-L2VPN100 |
Information about interface VE-L2VPN 100. |
Interface index |
Index of the VE-L2VPN interface. |
Current state |
Physical link state of the interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · UP—The interface is both administratively and physically up. |
Line protocol state |
Data link layer state of the interface. The state is determined through automatic parameter negotiation at the data link layer. · UP—The data link layer protocol is up. · UP (spoofing)—The data link layer protocol is up, but the link is an on-demand link or does not exist. This attribute is typical of null interfaces and loopback interfaces. · DOWN—The data link layer protocol is down. |
Description |
Description of the interface. |
Bandwidth |
Expected bandwidth of the interface, in kbps. |
Maximum transmission unit |
MTU of the interface. |
Internet protocol processing: Disabled |
The interface cannot process IP packets. |
Internet Address |
IP address of the interface. The primary attribute indicates that the address is the primary IP address. |
Link service |
Link service mode: · VPLS mode—This mode is available when the interface is bound with a VPLS instance. For more information about VPLS instances, see "Configuring VPLS." · PWE3 ethernet mode—This mode is available when the interface is associated with a PW whose encapsulation type is Ethernet. For more information about PWs, see "Configuring MPLS L2VPN." · PWE3 vlan mode—This mode is available when the interface is associated with a PW whose encapsulation type is VLAN. For more information about PWs, see "Configuring MPLS L2VPN." |
Physical: L2VE |
Physical type of the interface: L2VE interface or L2VE subinterface for terminating an MPLS L2VPN. |
Last clearing of counters |
Last time the counters were cleared by using the reset counters interface command. If the reset counters interface command has never been executed since the device started up, this field displays Never. |
Last 300 seconds input rate |
Average input rate in the last 300 seconds. |
Last 300 seconds output rate |
Average output rate in the last 300 seconds. |
Input: 0 packets, 0 bytes, 0 drops |
Total input packet statistics, including the number of input packets, input bytes, and dropped input packets. |
Output: 0 packets, 0 bytes, 0 drops |
Total output packet statistics, including the number of output packets, output bytes, and dropped output packets. |
# Display brief information about all L2VE interfaces.
<Sysname> display interface ve-l2vpn brief
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
L2VE1 DOWN DOWN --
# Display brief information about interface VE-L2VPN 2, including the entire interface description.
<Sysname> display interface ve-l2vpn 2 brief description
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
L2VE1 DOWN DOWN --
# Display information about interfaces in the physical state of DOWN and the causes.
<Sysname> display interface brief down
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
L2VE1 ADM Administratively
L2VE2 DOWN Not connected
Table 2 Command output
Field |
Description |
Brief information on interfaces in route mode: |
Brief information about Layer 3 interfaces. |
Interface |
Abbreviated interface name. |
Link |
Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · ADM—The interface has been shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Stby—The interface is a backup interface in standby state. |
Protocol |
Data link layer protocol state of the interface: · UP—The data link layer protocol of the interface is up. · DOWN—The data link layer protocol of the interface is down. · UP(s)—The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. This value is typical of null interfaces and loopback interfaces. |
Primary IP |
Primary IP address of the interface. This field displays two hyphens (--) if the interface does not have an IP address. |
Description |
Description of the interface. |
Cause |
Cause for the physical link state of an interface to be DOWN: · Administratively—The interface has been manually shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Not connected—The tunnel is not established. |
reset counters interface ve-l2vpn
display interface ve-l3vpn
Use display interface ve-l3vpn to display L3VE interface information.
Syntax
display interface [ ve-l3vpn [ interface-number | interface-number.subnumber ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ve-l3vpn [ interface-number | interface-number.subnumber ]: Displays information about L3VE interfaces or L3VE subinterfaces. The interface-number argument represents the number of an existing L3VE interface. The subnumber argument represents the number of an existing subinterface created on the interface. If you do not specify the ve-l3vpn keyword, this command displays information about all interfaces on the device. If you specify the ve-l3vpn keyword but do not specify the interface-number or interface-number.subnumber argument, this command displays information about all L3VE interfaces.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of interface descriptions.
down: Displays information about interfaces in the physical state of DOWN and the causes. If you do not specify this keyword, the command displays information about interfaces in all states.
Examples
# Display information about interface VE-L3VPN 100.
<Sysname> display interface ve-l3vpn 100
VE-L3VPN100
Interface index: 17824
Current state: UP
Line protocol state: UP
Description: VE-L3VPN100 Interface
Bandwidth: 100000kbps
Maximum transmission unit: 1500
Internet protocol processing: Disabled
IP Packet Frame Type:PKTFMT_ETHNT_2, Hardware Address: 0011-2200-0202
IPv6 Packet Frame Type:PKTFMT_ETHNT_2, Hardware Address: 0011-2200-0202
Physical: L3VE, baudrate: 100000000 bps
Last clearing of counters: Never
Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
Input: 0 packets, 0 bytes, 0 drops
Output: 0 packets, 0 bytes, 0 drops
Table 3 Command output
Field |
Description |
VE-L3VPN100 |
Information about interface VE-L3VPN 100. |
Interface index |
Index of the VE-L3VPN interface. |
Current state |
Physical link state of the interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · UP—The interface is both administratively and physically up. |
Line protocol state |
Data link layer state of the interface. The state is determined through automatic parameter negotiation at the data link layer. · UP—The data link layer protocol is up. · UP (spoofing)—The data link layer protocol is up, but the link is an on-demand link or does not exist. This attribute is typical of null interfaces and loopback interfaces. · DOWN—The data link layer protocol is down. |
Description |
Description of the interface. |
Bandwidth |
Expected bandwidth of the interface, in kbps. |
Maximum transmission unit |
MTU of the interface. |
Internet protocol processing: Disabled |
The interface cannot process IP packets. |
Internet address: ip-address/mask-length (Type) |
IP address of the interface and type of the address in parentheses. Possible IP address types include: · Primary—Manually configured primary IP address. · Sub—Manually configured secondary IP address. If the interface has both primary and secondary IP addresses, the primary IP address is displayed. If the interface has only secondary IP addresses, the lowest secondary IP address is displayed. · DHCP-allocated—DHCP allocated IP address. For more information, see DHCP configuration in BRAS Services Configuration Guide. · BOOTP-allocated—BOOTP allocated IP address. For more information, see DHCP configuration in BRAS Services Configuration Guide. · PPP-negotiated—IP address assigned by a PPP server during PPP negotiation. For more information, see PPP configuration in Layer 2—WAN Access Configuration Guide. · Unnumbered—IP address borrowed from another interface. · MTunnel—IP address of the multicast tunnel interface (MTI), which is the same as the IP address of the MVPN source interface. For more information, see multicast VPN configuration in IP Multicast Configuration Guide. |
Physical: L3VE |
Physical type of the interface: L3VE interface or L3VE subinterface for accessing an MPLS L3VPN or IP backbone. |
Last clearing of counters |
Last time the counters were cleared by using the reset counters interface command. If the reset counters interface command has never been executed since the device started up, this field displays Never. |
Last 300 seconds input rate |
Average input rate in the last 300 seconds. |
Last 300 seconds output rate |
Average output rate in the last 300 seconds. |
Input: 0 packets, 0 bytes, 0 drops |
Total input packet statistics, including the number of input packets, input bytes, and dropped input packets. |
Output: 0 packets, 0 bytes, 0 drops |
Total output packet statistics, including the number of output packets, output bytes, and dropped output packets. |
# Display brief information about all L3VE interfaces.
<Sysname> display interface ve-l3vpn brief
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
L3VE1 DOWN DOWN --
# Display brief information about interface VE-L3VPN 2, including the entire interface description.
<Sysname> display interface ve-l3vpn 2 brief description
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol Primary IP Description
L3VE1 DOWN DOWN --
# Display information about interfaces in the physical state of DOWN and the causes.
<Sysname> display interface brief down
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
L3VE1 ADM Administratively
L3VE2 DOWN Not connected
Table 4 Command output
Field |
Description |
Brief information on interfaces in route mode: |
Brief information about Layer 3 interfaces. |
Interface |
Abbreviated interface name. |
Link |
Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · ADM—The interface has been shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Stby—The interface is a backup interface in standby state. |
Protocol |
Data link layer protocol state of the interface: · UP—The data link layer protocol of the interface is up. · DOWN—The data link layer protocol of the interface is down. · UP(s)—The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. This value is typical of null interfaces and loopback interfaces. |
Primary IP |
Primary IP address of the interface. This field displays two hyphens (--) if the interface does not have an IP address. |
Description |
Description of the interface. |
Cause |
Cause for the physical link state of an interface to be DOWN: · Administratively—The interface has been manually shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Not connected—The tunnel is not established. |
Related commands
reset counters interface ve-l3vpn
interface ve-l2vpn
Use interface ve-l2vpn to create an L2VE interface or L2VE subinterface and enter its view, or enter the view of an existing L2VE interface or L2VE subinterface.
Use undo interface ve-l2vpn to delete an L2VE interface or L2VE subinterface.
Syntax
interface ve-l2vpn { interface-number | interface-number.subnumber }
undo interface ve-l2vpn { interface-number | interface-number.subnumber }
Default
No L2VE interfaces or L2VE subinterfaces exist.
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies the L2VE interface number. The value range for this argument is 1 to 8192.
interface-number.subnumber: Specifies the L2VE subinterface number. The value range for the subnumber argument is 1 to 4094.
Usage guidelines
A VE-L2VPN interface (an L2VE interface) or an L2VE subinterface terminates L2VPN packets. The L2VE interface performs the following operations:
· Removes the MPLS label from an MPLS L2VPN packet.
· Sends the original Layer 2 packet to an L3VE interface or L3VE subinterface that has the same interface number as the L2VE interface.
An L2VE subinterface sends original Layer 2 packets only to the L3VE interface that has the same interface number as the L2VE subinterface.
If an L2VE subinterface receives packets that carry VLAN tags, you must configure the L2VE subinterface to terminate the VLAN tags. For more information about VLAN termination, see Layer 2—LAN Switching Configuration Guide.
Deleting an L2VE interface also deletes all subinterfaces on the interface.
Before you create an L2VE subinterface, the main L2VE interface of the subinterface must already exist.
The VPLS access to L3VPN or IP backbone model does not support creating L2VE subinterfaces.
Examples
# Create L2VE interface VE-L2VPN 100, and enter L2VE interface view.
<Sysname> system-view
[Sysname] interface ve-l2vpn 100
[Sysname-VE-L2VPN100]
# Create L2VE subinterface VE-L2VPN 100.10, and enter L2VE subinterface view.
<Sysname> system-view
[Sysname] interface ve-l2vpn 100.10
[Sysname-VE-L2VPN100.10]
interface ve-l3vpn
Use interface ve-l3vpn to create an L3VE interface or L3VE subinterface and enter its view, or enter the view of an existing L3VE interface or L3VE subinterface.
Use undo interface ve-l3vpn to delete an L3VE interface or L3VE subinterface.
Syntax
interface ve-l3vpn { interface-number | interface-number.subnumber }
undo interface ve-l3vpn { interface-number | interface-number.subnumber }
Default
No L3VE interfaces or L3VE subinterfaces exist.
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies the L3VE interface number. The value range for this argument is 1 to 8192.
interface-number.subnumber: Specifies the L3VE subinterface number. The value range for the subnumber argument is 1 to 4094.
Usage guidelines
A VE-L3VPN interface (an L3VE interface) provides access to an MPLS L3VPN or IP backbone for packets. The L3VE interface forwards packets received from the backbone to an L2VE interface that has the same interface number as the L3VE interface.
If packets entering an MPLS L3VPN or IP backbone carry VLAN tags, you must create an L3VE subinterface on the L3VE interface to terminate the VLAN tags. For more information about VLAN termination, see Layer 2—LAN Switching Configuration Guide.
Deleting an L3VE interface also deletes all subinterfaces on the interface.
Before you create an L3VE subinterface, the main L3VE interface of the subinterface must already exist.
Examples
# Create L3VE interface VE-L3VPN 100, and enter L3VE interface view.
<Sysname> system-view
[Sysname] interface ve-l3vpn 100
[Sysname-VE-L3VPN100] quit
# Create L3VE subinterface VE-L3VPN 100.10, and enter L3VE subinterface view.
[Sysname] interface ve-l3vpn 100.10
[Sysname-VE-L3VPN100.10]
mac-address
Use mac-address to configure the MAC address of an L3VE interface.
Use undo mac-address to restore the default.
Syntax
mac-address mac-address
undo mac-address
Default
The MAC address of an L3VE interface is allocated by the device.
Views
L3VE interface view
Predefined user roles
network-admin
Parameters
mac-address: Specifies a MAC address in H-H-H format.
Usage guidelines
You cannot directly configure MAC addresses for subinterfaces. All subinterfaces on an interface use the MAC address of the interface.
When configuring a MAC address for an interface, do not specify the MAC addresses reserved for VRRP.
Examples
# Set the MAC address of interface VE-L3VPN100 to 0001-0001-0001.
<Sysname> system-view
[Sysname] interface ve-l3vpn 100
[Sysname-VE-L3VPN100] mac-address 1-1-1
l2vpn arp-dual-forward enable
Use l2vpn arp-dual-forward enable to enable transmission of ARP packets through both the primary and backup PWs.
Use undo l2vpn arp-dual-forward enable to disable transmission of ARP packets through both the primary and backup PWs.
Syntax
l2vpn arp-dual-forward enable [ aging aging-time ]
undo l2vpn arp-dual-forward enable
Default
Transmission of ARP packets through both the primary and backup PWs is disabled.
Views
Layer 3 Ethernet interface view
Layer 3 Ethernet subinterface view
Layer 3 aggregate interface view
Layer 3 aggregate subinterface view
Predefined user roles
network-admin
Parameters
aging aging-time: Specifies the aging time for cached ARP packets, in the range of 60 to 4294967295 seconds. The default aging time is 4294967295 seconds, which indicates that cached ARP packets never age.
Usage guidelines
In an MPLS L2VPN access to L3VPN or IP backbone network, a PE configured with PW redundancy transmits users' ARP packets only through the primary PW. The backup PW cannot learn the MAC addresses of users unless it receives ARP packets. Therefore, traffic loss will occur when the primary PW fails.
To avoid such traffic loss, configure this command to enable a PE to transmit ARP packets through both the primary and backup PWs. The primary and backup PWs also cache the transmitted ARP packets for synchronization in the following scenarios:
· A PE has transmitted ARP packets through a PW before you configure PW redundancy on the PE. The primary PW sends the cached ARP packets to the backup PW after the backup PW comes up.
· PW redundancy is configured on a PE, and then one of the PWs fails. The other PW sends the cached ARP packets to the failed PW after the failed PW recovers.
A cross-connect can cache ARP packets from a maximum of 200 source IP addresses. When the upper limit is reached, the cached ARP packets will be replaced in chronological order.
Examples
# On interface Ten-GigabitEthernet 3/0/1, enable transmission of ARP packets through both the primary and backup PWs, and set the aging time for cached ARP packets to 200 seconds.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 3/0/1
[Sysname-Ten-GigabitEthernet3/0/1] l2vpn arp-dual-forward enable aging 200
l2vpn fast-forwarding srv6 virtual-ethernet
Use l2vpn fast-forwarding srv6 virtual-ethernet to enable software fast forwarding for SRv6 tunnels in EVPN VPLS over SRv6 access to L3VPN or IP backbone networks.
Use undo l2vpn fast-forwarding srv6 virtual-ethernet to disable software fast forwarding for SRv6 tunnels in EVPN VPLS over SRv6 access to L3VPN or IP backbone networks.
Syntax
l2vpn fast-forwarding srv6 virtual-ethernet
undo l2vpn fast-forwarding srv6 virtual-ethernet
Default
Software fast forwarding is disabled for SRv6 tunnels in EVPN VPLS over SRv6 access to L3VPN or IP backbone networks.
Views
System view
Predefined user roles
network-admin
Usage guidelines
This command is supported only in EVPN VPLS over SRv6 access to L3VPN or IP backbone networking scenarios.
After you enable this feature in EVPN VPLS over SRv6 access to L3VPN or IP backbone networking scenarios, the SRv6 tunnel in the EVPN VPLS over SRv6 network will perform software-based fast forwarding for the packets entering the tunnel from L2VE interfaces.
Examples
# Enable software fast forwarding for SRv6 tunnels in an EVPN VPLS over SRv6 access to L3VPN or IP backbone network.
<Sysname> system-view
[Sysname] l2vpn fast-forwarding srv6 virtual-ethernet
l2vpn nd-dual-forward enable
Use l2vpn nd-dual-forward enable to enable transmission of ND packets through both the primary and backup PWs.
Use undo l2vpn nd-dual-forward enable to disable transmission of ND packets through both the primary and backup PWs.
Syntax
l2vpn nd-dual-forward enable [ aging aging-time ]
undo l2vpn nd-dual-forward enable
Default
Transmission of ND packets through both the primary and backup PWs is disabled.
Views
Layer 3 Ethernet interface view
Layer 3 Ethernet subinterface view
Layer 3 aggregate interface view
Layer 3 aggregate subinterface view
Predefined user roles
network-admin
Parameters
aging aging-time: Specifies the aging time for cached ND packets, in the range of 60 to 4294967295 seconds. The default aging time is 4294967295 seconds, which indicates that cached ND packets never age.
Usage guidelines
In an MPLS L2VPN access to L3VPN or IP backbone network, a PE configured with PW redundancy transmits users' ND packets only through the primary PW. The backup PW cannot learn the MAC addresses of users unless it receives ND packets. Therefore, traffic loss will occur when the primary PW fails.
To avoid such traffic loss, configure this command to enable a PE to transmit ND packets through both the primary and backup PWs. The primary and backup PWs also cache the transmitted ND packets for synchronization in the following scenarios:
· A PE has transmitted ND packets through a PW before you configure PW redundancy on the PE. The primary PW sends the cached ND packets to the backup PW after the backup PW comes up.
· PW redundancy is configured on a PE, and then one of the PWs fails. The other PW sends the cached ND packets to the failed PW after the failed PW recovers.
A cross-connect can cache ND packets from a maximum of 200 source IP addresses. When the upper limit is reached, the cached ND packets will be replaced in chronological order.
Examples
# On interface Ten-GigabitEthernet 3/0/1, enable transmission of ND packets through both the primary and backup PWs, and set the aging time for cached ND packets to 200 seconds.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 3/0/1
[Sysname-Ten-GigabitEthernet3/0/1] l2vpn nd-dual-forward enable aging 200
l2vpn-l3vpn enhance-mode enable
Use l2vpn-l3vpn enhance-mode enable to enable fast forwarding for L2VPN access to L3VPN.
Use undo l2vpn-l3vpn enhance-mode enable to disable fast forwarding for L2VPN access to L3VPN.
Syntax
l2vpn-l3vpn enhance-mode enable
undo l2vpn-l3vpn enhance-mode enable
Default
Fast forwarding for L2VPN access to L3VPN is disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
Execute this command to improve the forwarding performance of L2VE and L3VE interfaces.
After this command is executed, the device does not support L3VE subinterfaces.
After executing this command or its undo form, redeploy configuration to the interfaces on the device for this command or its undo form to take effect.
After you execute this command, the L3VE interfaces on the device do not support uRPF. For more information about uRPF, see uRPF configuration in Security Configuration Guide.
Examples
# In system view, enable fast forwarding for L2VPN access to L3VPN.
<Sysname> system-view
[Sysname] l2vpn-l3vpn enhance-mode enable
Do you want to change the l2vpn-l3vpn enhance mode?[Y/N]: y
mtu
Use mtu to set the MTU for an interface.
Use undo mtu to restore the default.
Syntax
mtu size [ spread ]
undo mtu [ spread ]
Default
The MTU for an interface is 1500 bytes.
Views
L3VE interface view
L3VE subinterface view
Predefined user roles
network-admin
Parameters
size: Specifies the MTU in bytes. The value range for this argument is 46 to 9600.
spread: Applies the MTU to all subinterfaces of the interface. Subinterfaces do not support this keyword.
Usage guidelines
If you configure the mtu size command in the view of an L3VE interface, the command takes effect only on the L3VE interface. If you configure the mtu size command in the view of an L3VE subinterface, the command takes effect only on the L3VE subinterface.
If you configure the mtu size spread command in the view of an L3VE interface, the command takes effect on the interface and all its subinterfaces.
For an L3VE subinterface, the MTU specified by the mtu size command takes precedence over that specified by the mtu size spread command.
Examples
# Set the MTU for VE-L3VPN 100 to 1430 bytes.
<Sysname> system-view
[Sysname] interface ve-l3vpn 100
[Sysname-VE-L3VPN100] mtu 1430
reset counters interface ve-l2vpn
Use reset counters interface ve-l2vpn to clear interface statistics.
Syntax
reset counters interface [ ve-l2vpn [ interface-number | interface-number.subnumber ] ]
Views
User view
Predefined user roles
network-admin
Parameters
ve-l2vpn [ interface-number | interface-number.subnumber ]: Clears statistics for L2VE interfaces or L2VE subinterfaces. The interface-number argument represents the number of an existing L2VE interface. The subnumber argument represents the number of an existing subinterface created on the interface. If you do not specify the ve-l2vpn keyword, this command clears statistics for all interfaces on the device. If you specify the ve-l2vpn keyword but do not specify the interface-number or interface-number.subnumber argument, this command clears statistics for all L2VE interfaces.
Usage guidelines
Use this command to clear old statistics so you can observe new traffic statistics on an interface.
Examples
# Clear statistics for VE-L2VPN 100.
<Sysname> reset counters interface ve-l2vpn 100
Related commands
display interface ve-l2vpn
reset counters interface ve-l3vpn
Use reset counters interface ve-l3vpn to clear L3VE interface statistics.
Syntax
reset counters interface [ ve-l3vpn [ interface-number | interface-number.subnumber ] ]
Views
User view
Predefined user roles
network-admin
Parameters
ve-l3vpn [ interface-number | interface-number.subnumber ]: Clears statistics for L3VE interfaces or L3VE subinterfaces. The interface-number argument represents the number of an existing L3VE interface. The subnumber argument represents the number of an existing subinterface created on the interface. If you do not specify the ve-l3vpn keyword, this command clears statistics for all interfaces on the device. If you specify the ve-l3vpn keyword but do not specify the interface-number or interface-number.subnumber argument, this command clears statistics for all L3VE interfaces.
Usage guidelines
Use this command to clear old statistics so you can observe new traffic statistics on an interface.
Examples
# Clear statistics for interface VE-L3VPN 100.
<Sysname> reset counters interface ve-l3vpn 100
Related commands
display interface ve-l3vpn
shutdown
Use shutdown to shut down an interface.
Use undo shutdown to bring up an interface.
Syntax
shutdown
undo shutdown
Default
L2VE interfaces, L2VE subinterfaces, L3VE interfaces, and L3VE subinterfaces are up.
Views
L2VE interface view
L2VE subinterface view
L3VE interface view
L3VE subinterface view
Predefined user roles
network-admin
Usage guidelines
CAUTION: Executing this command on an interface will interrupt the link established on the interface. Please be cautious. |
Examples
# Shut down VE-L2VPN 100.
<Sysname> system-view
[Sysname] interface ve-l2vpn 100
[Sysname-VE-L2VPN100] shutdown
# Shut down VE-L3VPN 100.
<Sysname> system-view
[Sysname] interface ve-l3vpn 100
[Sysname-VE-L3VPN100] shutdown
track l2vpn-network-state
Use track l2vpn-network-state to enable an interface to monitor PWs and SRv6 PWs.
Use undo track l2vpn-network-state to disable an interface from monitoring PWs and SRv6 PWs.
Syntax
track l2vpn-network-state
undo track l2vpn-network-state
Default
An interface does not monitor PWs or SRv6 PWs.
Views
L2VE interface view
Predefined user roles
network-admin
Usage guidelines
In L2VPN access to IP or L3VPN network scenarios, multiple PE-agg devices can be deployed to achieve redundancy backup. If the PW or SRv6 PW on a PE-agg fails, and the devices within the IP network or L3VPN network cannot detect the failure, they will still forward traffic to that PE-agg, leading to a traffic forwarding interruption. To resolve this issue, you can execute this command on the PE-agg device.
For L2VE interfaces that have already been bound to a VSI or cross-connect, after you execute this command in L2VE interface view, the PE-agg device will monitor all PWs and SRv6 PWs in the VSI or cross-connect. When all PWs and SRv6 PWs in the VSI or cross-connect go down, the status of the L2VE interface will change to Down. The status of the L3VE interface associated with the L2VE interface will also be set to Down, so that the traffic will be switched to other PE-agg devices.
Both the track l2vpn-network-state command and the track pw-state srv6 command can enable an interface to monitor PWs and SRv6 PWs. As a best practice, use the track l2vpn-network-state command to enable this feature. If you execute the track pw-state srv6 command, the command that takes effect is the track l2vpn-network-state command.
Examples
# Enable L2VE interface 1 to monitor PWs and SRv6 PWs.
<Sysname> system-view
[Sysname] interface ve-l2vpn 1
[Sysname-VE-L2VPN1] xconnect vsi vpna
[Sysname-VE-L2VPN1] track l2vpn-network-state
track pw-state srv6
Use track pw-state srv6 to enable an interface to monitor PWs and SRv6 PWs.
Syntax
track pw-state srv6
Default
An interface does not monitor PWs or SRv6 PWs.
Views
L2VE interface view
Predefined user roles
network-admin
Usage guidelines
In L2VPN access to IP or L3VPN network scenarios, multiple PE-agg devices can be deployed to achieve redundancy backup. If the PW or SRv6 PW on a PE-agg fails, and the devices within the IP network or L3VPN network cannot detect the failure, they will still forward traffic to that PE-agg, leading to a traffic forwarding interruption. To resolve this issue, you can execute this command on the PE-agg device.
For L2VE interfaces that have already been bound to a VSI or cross-connect, after you execute this command in L2VE interface view, the PE-agg device will monitor all PWs and SRv6 PWs in the VSI or cross-connect. When all PWs and SRv6 PWs in the VSI or cross-connect go down, the status of the L2VE interface will change to Down. The status of the L3VE interface associated with the L2VE interface will also be set to Down, so that the traffic will be switched to other PE-agg devices.
Both the track l2vpn-network-state command and the track pw-state srv6 command can enable an interface to monitor PWs and SRv6 PWs. As a best practice, use the track l2vpn-network-state command to enable this feature. If you execute the track pw-state srv6 command, the command that takes effect is the track l2vpn-network-state command.
Examples
# Enable L2VE interface 1 to monitor SRv6 PWs.
<Sysname> system-view
[Sysname] interface ve-l2vpn 1
[Sysname-VE-L2VPN1] xconnect vsi vpna
[Sysname-VE-L2VPN1] track pw-state srv6
Related commands
xconnect vsi (VXLAN Command Reference)