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

Configuration Guide - Interface Management

CloudEngine 12800 and 12800E V200R003C00

This document describes the interface management configuration, including basic interface configuration, Ethernet interface configuration, and logical interface configuration.

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).
Overview of Interfaces

Overview of Interfaces

Interface Type

Interfaces of a device are used to exchange data and interact with other network devices. Interfaces are classified into management interfaces, physical service interfaces, and logical interfaces.

  • Management interfaces

    Management interfaces are used to log in to devices. Users can use management interfaces to configure and manage devices. Management interfaces do not transmit service data. For the configuration of management interfaces, see the CloudEngine 12800 and 12800E Series Switches Configuration Guide - Basic Configurations.

    Table 1-1 describes the management interfaces.

    Table 1-1 Management interfaces

    Interface

    Description

    Application

    Console interface

    A data connection equipment (DCE) interface that complies with the EIA/TIA-232 standard.

    The console interface is connected to the COM serial interface of a configuration terminal to set up an on-site configuration environment.

    MEth interface

    Complies with the 10/100/1000BASE-TX standard.

    The ETH interface can be connected to a network interface of a configuration terminal or network management workstation to set up an on-site configuration environment.

    Mini USB/Micro USB interface

    Complies with the USB 2.0 standard.

    The Mini USB/Micro USB interface can be connected to an operation terminal for onsite configuration.

    Only CE12800E support Micro USB, other device support Mini USB.

    System Inter-Connect Port (SIP) interface

    Complies with the IEEE802.3z standard.

    There are two SIP interfaces on the MPU of a CE12800&12800E switch. The SIP interface is a combo interface that is composed of a GE electrical interface and a GE optical interface. It is designed for connection between stack management links.

    NOTE:
    • The console interface and Mini USB/Micro USB interface share one internal serial port. You can use the console interface or Mini USB/Micro USB interface as the serial port according to your needs. When the Mini USB/Micro USB is activated, the console interface cannot be used.
    • When both the console interface and Mini USB/Micro USB interface have a cable connected, the Mini USB/Micro USB interface is recommended.
  • Physical service interfaces

    Physical interfaces exist on interface cards and transmit service data.

    Physical interfaces are sometimes called ports. This document uses the term interface.

    Table 1-2 describes the physical interfaces that the device supports.

    Table 1-2 Physical interfaces
    Interface Description
    GE electrical interface A GE electrical interface works at the data link layer, provides a maximum of 1000 Mbit/s transmission rate, processes Layer 2 protocol packets, and implements Layer 2 forwarding.
    GE optical interface A GE optical interface works at the data link layer, provides a maximum of 1000 Mbit/s transmission rate, processes Layer 2 protocol packets, and implements Layer 2 forwarding.
    10GE electrical interface A 10GE electrical interface works at the data link layer, provides a maximum of 10000 Mbit/s transmission rate, processes Layer 2 protocol packets, and implements Layer 2 forwarding.
    10GE optical interface A 10GE optical interface works at the data link layer, provides a maximum of 10000 Mbit/s transmission rate, processes Layer 2 protocol packets, and implements Layer 2 forwarding.
    25GE optical interface A 25GE optical interface works at the data link layer, provides a maximum of 25000 Mbit/s transmission rate, processes Layer 2 protocol packets, and implements Layer 2 forwarding.
    40GE optical interface A 40GE optical interface works at the data link layer, provides a maximum of 40000 Mbit/s transmission rate, processes Layer 2 protocol packets, and implements Layer 2 forwarding. A 40GE optical interface can be used as an independent interface or be split into two or four 10GE optical interfaces.
    100GE optical interface A 100GE optical interface works at the data link layer, provides a maximum of 100000 Mbit/s transmission rate, processes Layer 2 protocol packets, and implements Layer 2 forwarding.

    A 100GE optical interface can be used as an independent interface or be split into 10GE, 25GE, or 40GE optical interfaces. For details about interface split, see Configuring Interface Split.

    BITS Interfaces

    CE12800E provides two building integrated timing supply (BITS) interfaces: BITS0 and BITS1. BITS0 is used to input/output clock signals, while BITS1 is used to input/output time signals. BITS interfaces between two devices are connected using clock cables.

    NOTE:

    By default, an Ethernet interface on the device works in Layer 2 mode. To enable Layer 3 functions on the interface, run the undo portswitch command on the interface.

  • Logical interfaces

    Logical interfaces are manually configured and do not physically exist. They are responsible for transmitting service data.

    Table 1-3 describes the logical interfaces that the device supports.

    Table 1-3 Logical interfaces
    Interface Description Configuration Reference
    Eth-Trunk An Eth-Trunk is formed by binding multiple Ethernet interfaces to provide more bandwidth and higher transmission reliability. For details about how to configure an Eth-Trunk, see Link Aggregation Configuration in the CloudEngine 12800 and 12800E Series Switches Configuration Guide - Ethernet Switching.
    VLANIF interface A 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 CloudEngine 12800 and 12800E Series Switches Configuration Guide - Ethernet Switching.
    Layer 2 sub-interface On VXLAN networks, service access points are Layer 2 sub-interfaces. You can configure different flow encapsulation modes on the Layer 2 sub-interfaces, so that the Layer 2 sub-interfaces can process different data packets. For details about how to configure a Layer 2 sub-interface, see Configuring a VXLAN Service Access Point in the CloudEngine 12800 and 12800E Series Switches Configuration Guide - DCN and Server Management.
    Layer 3 sub-interface A Layer 3 sub-interface is a virtual interface configured on a main interface to implement inter-VLAN communication.
    NOTE:
    • Before configuring a Layer 3 sub-interface on a Layer 2 physical interface or Layer 2 Eth-Trunk, run the undo portswitch command to switch the interface to a Layer 3 interface.
    • The MAC address of a Layer 3 sub-interface is the same as that of the main interface.
    • A Layer 3 sub-interface can be assigned an IP address.
    -
    Stack interface A stack interface is a logical interface used to implement the stacking function. The stacking function virtualizes multiple switches into a logical switch to improve the forwarding performance of a large amount of data and network reliability in data centers. For details about how to configure a stack interface, see Stack Configuration in the CloudEngine 12800 and 12800E Series Switches Configuration Guide - Device Management.
    Loopback interface

    A loopback interface is always Up and can be configured with a 32-bit subnet mask.

    There is one unique loopback interface called the InLoopBack0 interface, which is automatically created at startup. The InLoopback0 interface is a special and fixed loopback interface. It 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 the InLoopBack0 interface is not advertised.

    -
    NULL interface A NULL interface used in route filtering because any network packets sent to this interface are discarded. -
    Tunnel interface A 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 IPv6 Transition Technology Configuration in the CloudEngine 12800 and 12800E Series Switches Configuration Guide - IP Service and GRE Configuration Guide in the CloudEngine 12800 and 12800E Series Switches Configuration Guide - VPN.

    Multicast tunnel interface (MTI) An MTI is a virtual interface that works as the channel for data exchange between a public network instance and a VPN instance on a provider edge (PE) in the multicast VPN scenario. Two PEs can exchange Protocol Independent Multicast (PIM) messages to set up a PIM neighbor relationship on a public network instance through MTIs.

    For details about how to configure an MTI, see Multicast VPN Configuration in the CloudEngine 12800 and 12800E Series Switches Configuration Guide - IP Multicast.

    FCoE interface If Fibre Channel over Ethernet (FCoE) is configured, devices communicate and transmit traffic through FCoE interfaces. Therefore, you need to configure FCoE logical interfaces on the devices. For details about how to configure an FCoE interface, see FCoE Configuration in the CloudEngine 12800 and 12800E Series Switches Configuration Guide - DCN and Server Management.
    NVE interface An NVE interface is the logical interface to establish VXLAN tunnels with other NVE devices.

    For details about how to configure an NVE interface, see VXLAN Configuration Guide in the CloudEngine 12800 and 12800E Series Switches Configuration Guide - DCN and Server Management.

    VBDIF interface A VBDIF interface is the virtual interface based on a BD to support Layer 3 features and implement communication between different BDs, between BD and non-BD networks, and between BDs and Layer 3 networks.

    For details about how to configure a VBDIF interface, see VXLAN Configuration Guide in the CloudEngine 12800 and 12800E Series Switches Configuration Guide - DCN and Server Management.

Management Interface Numbering Rules

The device supports Console, MEth, Mini USB/Micro USB, SIP management interfaces that exist on the MPU.

The following table lists the numbers of the management interfaces.

Table 1-4 Management interface numbers

Interface

Number

Console interface

console 0

MEth interface

MEth 0/0/0

Mini USB/Micro USB interface

console 0

SIP interface

On a single device, Sip slot ID/0/0 and Sip slot ID/0/1

In a stack, Sip frame ID/slot ID/0/0 and Sip frame ID/slot ID/0/1

Physical Interface Numbering Rules

The numbering rules for physical interfaces are as follows:

Before the stacking function is enabled, physical interfaces on the CloudEngine 12800 and 12800E Series switch are numbered in the format of slot ID/subcard ID/interface sequence number.

After the stacking function is enabled, physical interfaces on the CloudEngine 12800 and 12800E Series switch are numbered in the format of chassis ID/slot ID/subcard ID/interface sequence number.

  • Chassis ID: specifies the ID of a switch in a stack system. A maximum of two CloudEngine 12800 and 12800E Series switches can set up a stack. Therefore, the value of Chassis ID is 1 or 2.
  • Slot ID: specifies the ID of the slot in which a card is installed.
  • subcard ID: specifies the ID of a subcard on a card. Currently, cards do not support subcards and the value of subcard ID is 0.
  • interface sequence number: specifies the sequence number of an interface on the card. The value starts from 0.
Figure 1-1 Physical interface numbering diagram

There are two rows of interfaces on the interface card. These interfaces are numbered from top to bottom and left to right, starting with 0. For example, if a card is installed in slot 3 of a CloudEngine 12800 and 12800E Series switch, the fifth interface from left to right and top to bottom on the card is numbered 3/0/4. If the stacking function is enabled and the stack ID is 1, the interface is numbered 1/3/0/4.

Converted interfaces are numbered using the dimension numbering rule. For example, a 40GE interface is numbered 40GE x/y/0/n and is split into four 10GE interfaces, the converted 10GE interfaces are numbered 40GE x/y/0/n:1, 40GE x/y/0/n:2, 40GE x/y/0/n:3, and 40GE x/y/0/n:4.

Translation
Download
Updated: 2019-05-05

Document ID: EDOC1100004195

Views: 18736

Downloads: 37

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next