Overview of Logical Interfaces
Logical interfaces do not exist physically. They are manually configured for data exchange.
This topic describes logical interfaces supported by devices.
Interface |
Description |
Configuration Reference |
---|---|---|
Eth-Trunk interface |
Has Layer 2 or Layer 3 features. An Eth-Trunk interface is formed by binding multiple Ethernet interfaces to provide more bandwidth and higher transmission reliability. |
For details about how to configure an Eth-Trunk interface, see Link Aggregation Configuration in the NetEngine AR Configuration Guide: LAN. |
Virtual-Template (VT) interface |
Used when PPP needs to transmit packets of other link layer protocols. |
- |
Virtual-Ethernet (VE) interface |
Used when other data link layer protocols need to be carried by the Ethernet protocol. |
- |
MP-Group interface |
Used to perform MP binding. MP group interfaces are dedicated to the MP application and usually used in scenarios requiring dynamic bandwidth. |
For details about how to configure an MP Group interface, see MP Configuration in the NetEngine AR Configuration Guide: WAN. |
Dialer interface |
Used to implement the Dialer Control Center (DCC) function. A physical interface can be bound to a dialer interface to inherit the configuration of the dialer interface. |
For details about how to configure a dialer interface, see DCC Configuration in the NetEngine AR Configuration Guide: WAN. |
Tunnel interface |
Has Layer 3 features, transmits packets, and identifies and processes packets transmitted over a tunnel. |
For details about how to configure a tunnel interface, see GRE Configuration in the NetEngine AR Configuration Guide: VPN. |
VLANIF interface |
Has Layer 3 features and enables VLANs to communicate after being assigned an IP address. |
For details about how to configure a VLANIF interface, see VLAN Configuration in the NetEngine AR Configuration Guide: LAN Configuration. |
Sub-interface |
A sub-interface is a virtual interface configured on a physical interface to allow a physical link to communicate with multiple remote devices. |
- |
MFR interface |
If a single FR link cannot provide sufficient bandwidth, and multiple FR physical links exist between devices, you can bundle these FR physical links into a Multilink Frame Relay (MFR) link to increase bandwidth. |
For details about how to configure an MFR interface, see FR Configuration in the NetEngine AR Configuration Guide: WAN Interconnection. |
Loopback interface |
A loopback interface is always Up and can be configured with a 32-bit subnet mask. |
- |
NULL interface |
Used in route filtering because any network packets sent to this interface are discarded. |
- |
Bridge interface |
A bridge interface has Layer 3 features and enables users on different network segments on a transparent bridge to communicate with each other after being assigned an IP address. |
For details about how to configure a bridge interface, see Transparent Bridging Configuration in the NetEngine AR Configuration Guide: LAN Configuration. |
Wlan-Radio interface |
Wlan-Radio interface is a kind of logical interface. You can configure the radio after creating a wlan-radio interface. |
For details about how to configure a Wlan-Radio interface, see the NetEngine AR Configuration Guide: WLAN-FAT AP. |
WLAN-BSS interface |
A WLAN-BSS interface is a virtual Layer 2 interface. Similar to a Layer 2 Ethernet interface of the hybrid type, a WLAN-BSS interface has Layer 2 attributes and supports multiple Layer 2 protocols. After creating a WLAN-BSS interface, bind a service set to the interface. |
For details about how to configure a WLAN-BSS interface, see the NetEngine AR Configuration Guide: WLAN-FAT AP. |