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

Reminder

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

upgrade

NE20E-S V800R010C10SPC500 Feature Description - Interface and Data Link 01

This is NE20E-S V800R010C10SPC500 Feature Description - Interface and Data Link
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).
Logical Interface

Logical Interface

A single physical interface can be virtually split into multiple logical interfaces. Logical interfaces can be used to exchange data.

Table 2-4 Logical interface list

Interface Name

Usage Scenario and Interface Description

DCN serial interface

After DCN is enabled globally, a DCN serial interface is automatically created.

Virtual Ethernet (VE) interface

When an L2VPN accesses multiple L3VPNs, VE interfaces are used to terminate the L2VPN for L3VPN access. Because a common VE interface is bound to only one board, services will be interrupted if the board fails.

Global VE interface

When an L2VPN access multiple L3VPNs, global VE interfaces are used to terminate the L2VPN for L3VPN access.

A common VE interface is bound to only one board. If a board where a VE interface resides fails, services on the VE interface will be interrupted. Unlike common VE interfaces, global VE interfaces support global L2VE and L3VE. Services on global VE interfaces will not be interrupted if some boards fail.

The loopback function on global VE interfaces works properly irrespective of whether a board is powered off or damaged. The loopback process has been optimized on global VE interfaces to enhance the interface forwarding performance.

Global VE interfaces can be created on a device if the device is powered on.

Flexible Ethernet (FlexE) interface

A physical interface in standard Ethernet mode has fixed bandwidth. However, FlexE technology enables one or more physical interfaces to work in FlexE mode and adds them to a group. The total bandwidth of this group can be allocated on demand to logical interfaces in the group. The group to which physical interfaces are added is referred to as a FlexE group. The logical interfaces that share bandwidth of the physical interfaces in the FlexE group are called FlexE interfaces (also referred to as FlexE service interfaces).

FlexE interface bandwidth varies, which allows services to be isolated. Compared with traditional technologies, FlexE technology permits bit-level interface bundling, which solves uneven per-flow or per-packet hashing that challenges traditional trunk technology. In addition, each FlexE interface has a specific MAC address, and forwarding resources between interfaces are isolated. This prevents head-of-line blocking (HOL blocking) that occurs when traditional logical interfaces such as VLAN sub-interfaces are used for forwarding.

FlexE interface technology especially fits scenarios in which high-performance interfaces are required for transport, such as mobile bearer, home broadband, and leased line access. Services of different types are carried on specific FlexE interfaces, and are assigned specific bandwidth. FlexE technology achieves service-specific bandwidth control, and meets network slicing requirements in 5G scenarios.

When a physical interface is switched from standard Ethernet mode to flexible Ethernet (FlexE) mode, FlexE interfaces are generated.For example, after the interface 50|100GE 0/9/0 is switched to a physical interface in FlexE mode, the interface name is changed to FlexE-50|100GE 0/9/0. Additionally, a series of FlexE interfaces named FlexE 0/9/129 to FlexE 0/9/148 are generated. slot-id/card-id in the service interface number is consistent with that in the physical interface number.

Loopback interface

A loopback interface can be either of the following:

  • Loopback interface

    A loopback interface is used when you need an interface that must be always in the Up state. A loopback interface has the following advantages:

    • Once a loopback interface is created, its physical status and data link protocol status always stay Up, regardless of whether an IP address is configured for the loopback interface.

    • A loopback interface can be assigned an IP address with a 32-bit mask, which reduces address consumption. The IP address of a loopback interface can be advertised immediately after being configured.

    • No link layer protocol can be configured for a loopback interface. Therefore, no data link layer negotiation is required, allowing the link layer protocol status of the interface to stay Up.

    • The device drops the packet with a non-local IP address as the destination IP address and a local loopback interface as the outbound interface.

    The advantages of a loopback interface help improve configuration reliability. The IP address of a loopback interface can be used as follows:
    • Can be configured as a packet's source IP address to improve network reliability.
    • Can be used to control an access interface and filter logs to simplify information displaying.
  • InLoopback0 interface

    An InLoopBack0 interface is a fixed loopback interface that is automatically created at the system startup.

    An InLoopBack0 interface uses the fixed loopback address 127.0.0.1/8 to receive data packets destined for the host where the InLoopBack0 interface resides. The loopback address of an InLoopBack0 interface is not advertised.

Null0 interface

A Null0 interface, similar to a null device supported in some operating systems, is automatically created by the system.

Because data packets sent to a Null0 interface are discarded, you can directly forward packets to be filtered to the Null0 interface without configuring ACLs.

A Null0 interface is used as follows:
  • Routing loop prevention

    A Null0 interface can be used to prevent routing loops. For example, a route to the Null0 interface is created when a set of routes are summarized.

  • Traffic filtering

    A Null0 interface can filter packets without an ACL.

No IP address or data link layer protocol can be configured on a Null0 interface.

Ethernet sub-interface

An Ethernet sub-interface can be configured on a physical interface or logical interface and can have an IP address configured to implement inter-VLAN communication.

An Ethernet sub-interface has Layer 3 features. It shares the physical layer parameters of the main interface but has independent link layer and network layer parameters. Enabling or disabling an Ethernet sub-interface does not affect the main interface where the sub-interface resides, whereas the main interface status affects the Ethernet sub-interface. Specifically, the Ethernet sub-interface can work properly only if the main interface is Up.

Eth-Trunk interface

An Eth-Trunk interface can have multiple physical interfaces bundled to increase bandwidth, improve reliability, and implement load balancing.

For more information, see Trunk.

VLANIF interface

A VLANIF interface belongs to a Layer 3 interface and can be configured with an IP address. A VLANIF interface that has an IP address configured enables a Layer 2 device to communicate with a Layer 3 device.

Layer 3 switching combines routing and switching and improves overall network whole performance. After a Layer 3 switch transmits a data flow using a routing table, it generates a mapping between a MAC address and IP address. When the Layer 3 switch receives the same data flow, it transmits the data flow over Layer 2 not Layer 3. The routing table must have correct routing entries, so that the Layer 3 switch can transmit the data flow for the first time. A VLANIF interface and a routing protocol must be configured on a Layer 3 switch to ensure Layer 3 route reachability.

ATM bundle interface

An ATM bundle interface is used to forward one type of service from NodeBs to an RNC over the same PW.

In the scenarios where multiple NodeBs connect to a CSG through E1, CE1, or CPOS links, each NodeB may have voice, video, and data services, which require the CSG to create three PVCs for each NodeB. If one PW is used to transmit one type of service on each NodeB, a large number of PWs must be configured on the CSG. The growing number of NodeBs and service types increasingly burdens the CSG.

To address this problem, sub-interfaces that connect NodeBs to the CSG and transmit the same type of service can be bound to one ATM bundle interface. A PW is then set up on the ATM bundle interface to transmit the services to the RNC. In this way, each type of service requires one ATM bundle interface and one PW on a CSG, thereby reducing the number of PWs, alleviating the burden on the CSG, and improving service scalability.

Channelized serial interface

Serial interfaces are channelized from E1 or CPOS interfaces to carry PPP services.

  • The number of a serial interface channelized from an E1 interface is in the format of E1 interface number:channel set number. For example, the serial interface channelized from channel set 1 of CE1 2/0/0 is serial 2/0/0:1.

  • The number of a serial interface channelized from a CPOS interface is in the format of CPOS interface number/E1 interface number:channel set number. For example, the serial interface channelized from channel 3 of CPOS 2/0/0's E1 2 is serial 2/0/0/2:3.

IP-Trunk interface

To improve link communication capability, multiple POS interfaces can be bundled to an IP-Trunk interface.

An IP-Trunk interface has the following advantages:

  • Increased bandwidth: The bandwidth of an IP-Trunk interface totals the bandwidths of the IP-Trunk's member interfaces.
  • Balanced traffic: An IP-Trunk interface can share traffic by distributing traffic among different links, thereby preventing traffic congestion caused by traffic loading on a single link.
  • Improved link reliability: If one member interface goes Down, traffic can still be forwarded by the remaining active member interfaces.

An IP-Trunk interface must have HDLC encapsulated as its link layer protocol.

For more information, see IP-Trunk.

POS-Trunk interface

A POS-Trunk interface can have multiple POS interfaces bundled to support APS. A POS-Trunk interface must have PPP encapsulated as its link layer protocol.

CPOS-Trunk interface

A CPOS-Trunk interface can have multiple CPOS interfaces bundled to support APS.

Trunk serial interface

A trunk serial interface is channelized from a CPOS-Trunk interface to support APS.

MP-group interface

An MP-group interface that has multiple serial interfaces bundled is exclusively used by MP to increase bandwidth and improve reliability.

For more information, see MP Principles.

Global MP-group interface

A protection channel can be configured to take over traffic from one or more working channels if the working channels fail, which improves network reliability. Before PPP is deploying on CPOS interfaces, two CPOS interfaces must be added to a CPOS-Trunk interface, which is then channelized into trunk serial interfaces.

A global MP-group interface can have multiple trunk serial interfaces bundled to carry PPP services. If one CPOS link fails, the other CPOS link takes over the PPP traffic.

IMA-group interface

When users access an ATM network at a rate between T1 and T3 or between E1 and E3, it is cost-ineffective for the carrier to directly use T3 or E3 lines. In this situation, an IMA-group interface can have multiple T1 or E1 interfaces bundled to carry ATM services. The bandwidth of an IMA-group interface is approximately the total bandwidths of all member interfaces.

For more information, see ATM IMA.

Global IMA-group interface

A protection channel can be configured to take over traffic from one or more working channels if the working channels fail, which improves network reliability. Before ATM services are deployed on CPOS interfaces, two CPOS interfaces must be added to a CPOS-Trunk interface, which is then channelized into trunk serial interfaces.

A global IMA-group interface can have multiple trunk serial interfaces bundled to carry ATM services. If one CPOS link fails, the other CPOS link takes over the ATM traffic.

Tunnel interface

A tunnel interface is used by an MPLS TE tunnel to forward traffic.

For more information, see Tunnel Interface.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055118

Views: 2770

Downloads: 8

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