No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


ME60 V800R010C10SPC500 Configuration Guide - LAN Access and MAN Access 01

This is ME60 V800R010C10SPC500 Configuration Guide - LAN Access and MAN Access
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring Layer 3 Communication Between VBDIF Interfaces

Configuring Layer 3 Communication Between VBDIF Interfaces

VBDIF interfaces are Layer 3 logical interfaces. After creating VBDIF interfaces, you can configure Layer 3 features on these interfaces.

Usage Scenario

When EVC that defines Layer 2 interfaces without IP addresses is used to communicate with a Layer 3 network, VBDIF interfaces that are logical interfaces in a bridge domain can be configured. VBDIF interfaces are network layer interfaces and can be assigned IP addresses. These VBDIF interfaces with IP addresses assigned can communicate with the Layer 3 network through the EVC module.


Both Layer 2 and Layer 3 traffic is transmitted over the VBDIF interface. Running the shutdown command in the VBDIF interface view prohibits only Layer 3 traffic. After running the display interface vbdif command, you can view that traffic statistics still increase on this VBDIF interface.

To prohibit all traffic on the VBDIF interface, run the shutdown command in the BD view.

Pre-configuration Tasks

Before configuring Layer 3 communication between VBDIF interfaces, complete the following task:


Configure the rewrite pop { single | double } command as an action to have all VLAN tags removed from packets.


  1. Run system-view

    The system view is displayed.

  2. Run interface vbdif bd-id

    A VBDIF interface is created and the VBDIF interface view is displayed.

    The BD ID specified in this command must be the ID of an existing BD.


    A VBDIF interface can be created for a BD only if it is bound to an EVC Layer 2 sub-interface that has the untag, dot1q, or QinQ encapsulation type configured.

  3. Run ip address ip-address { mask | mask-length } [ sub ]

    An IP address is assigned to the VBDIF interface for communication at the network layer.


    If IP addresses assigned to VBDIF interfaces belong to different network segments, a routing protocol must be configured to provide reachable routes. Otherwise, VBDIF interfaces cannot communicate with each other at the network layer. For configurations of routing protocols, see the ME60 Configuration Guide - IP Routing.

  4. (Optional) Run mtu

    The maximum transmission unit (MTU) is configured for the VBDIF interface.

    Generally, the IP layer controls the maximum length of frames that are sent each time. Any time the IP layer receives an IP packet to be sent, it checks which local interface the packet needs to be sent to and queries the MTU of the interface. Then, the IP layer compares the MTU with the length of the packets to be sent. If the packet length is greater than the MTU, the IP layer fragments the packet to ensure that the length of each fragment is smaller or equal to the MTU.

    If forcible unfragmentation is configured, certain packets are lost during data transmission at the IP layer. To ensure jumbo packets are not dropped during transmission, you need to configure forcible fragmentation. In this case, you can run the mtu command to set the size of a fragment.

    After using the mtu command to change the MTU of a VBDIF interface, you need to change the MTU of the peer VBDIF interface to ensure that the MTUs of both interfaces are the same. Otherwise, services may be interrupted.

  5. (Optional) Run forward-mode loopback

    Set the packet forwarding mode on a VBDIF interface to loopback.

    After the forward-mode loopback command is run to set the packet forwarding mode to loopback, downstream MTU fragmentation is supported on a VBDIF interface and multicast traffic statistics are for a copy of the traffic forwarded from VBDIF interfaces.

  6. (Optional) Run damping time delay-time

    The BD damping function is enabled, and the delay after which the BD Down event is reported to the BDIF interface is set.

    If all the interfaces added to a BD go Down, the BD will report a BD Down event to the corresponding BDIF interface, causing the BDIF interface status to change. The master/slave switchover will cause the BDIF interface to alternate frequently between Up and Down. As a result, network flapping occurs. To avoid this situation, enable the BD damping function on the BDIF interface. If the last Up interface in the BD becomes Down, the device enabled with the BD damping function will report the BD status to the BDIF interface after the set delay expires. If an interface in the BD becomes Up before the set delay expires, the BDIF interface status remains Up.

  7. Run commit

    The configuration is committed.

Checking the Configurations

After configuring a VBDIF interface, run the display interface vbdif command. The command output shows the physical status, link protocol status, IP address, and mask of a VBDIF interface.

<HUAWEI> display interface vbdif 10
Vbdif10 current state : UP (ifindex: 53247)
Line protocol current state : UP 
Last line protocol up time : 2014-01-26 11:37:29
Route Port,The Maximum Transmit Unit is 1500
Internet Address is
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is cc53-b5f1-1400
Current system time: 2014-01-26 11:40:48
    Last 300 seconds input rate 28825488 bits/sec, 28151 packets/sec
    Last 300 seconds output rate 25823120 bits/sec, 24454 packets/sec
    Input: 2205295 packets,282277504 bytes
           2205291 unicast,4 broadcast,0 multicast
           0 errors,0 drops
    Output:564392 packets,74499662 bytes
           564392 unicast,0 broadcast,0 multicast
           0 errors,0 drops
    Input bandwidth utilization  : --
    Output bandwidth utilization : --
Updated: 2019-01-04

Document ID: EDOC1100059440

Views: 27256

Downloads: 18

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Previous Next