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

NE40E-M2 V800R010C10SPC500 Configuration Guide - Interface and Data Link 01

This is NE40E-M2 V800R010C10SPC500 Configuration Guide - 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).
Configuring Logical Interfaces

Configuring Logical Interfaces

This section describes how to configure logical interfaces. Logical interfaces are manually configured interfaces, which are used to exchange data. Logical interfaces do not exist physically.

Usage Scenario

For usage scenarios of logical interfaces, see "Logical Interface" in NE40E-Feature Description-Interface Management.

Table 2-6 Logical interface list

Feature

Interface Name

Configuration Guide

System management

DCN serial interface

This interface is automatically created by the system.

Interface management

Virtual Ethernet (VE) interface

Creating an L2VE Interface

Creating an L3VE Interface

Interface management

Global VE interface

Creating a Global-VE interface

Interface management

Loopback interface

Creating a Loopback Interface and Configuring Its IP Address

Interface management

Null0 interface

Entering the NULL Interface View

LAN access and MAN access

Ethernet sub-interface

Configuring Ethernet Sub-interfaces to Support Communication Between VLANs

LAN access and MAN access

Eth-Trunk interface

Eth-Trunk Interface Configuration

LAN access and MAN access

VLANIF interface

Configuring Layer 3 Communication Between VLANIF Interfaces

WAN access

IP-Trunk interface

Configuring an IP-Trunk Interface

WAN access

POS-Trunk interface

Configuring a POS-Trunk interface

WAN access

CPOS-Trunk interface

Creating a CPOS-Trunk Interface

WAN access

MP-group interface

Configuring MP

WAN access

Global MP-group interface

Creating a Global MP-Group or IMA-Group Interface and Adding a Trunk Serial Interface to It

WAN access

IMA-group interface

ATM IMA Configuration

WAN access

Global IMA-group interface

Creating a Global MP-Group or IMA-Group Interface and Adding a Trunk Serial Interface to It

MPLS

Tunnel interface

MPLS TE Configuration

Pre-configuration Tasks

Before configuring logical interfaces, connect interfaces and set their physical parameters to ensure that these interfaces are physically Up.

Configuration Procedures

Perform one or more of the following configurations (excluding checking the configuration) as required.

Creating a Global-VE interface

Global-VE interfaces are independent of boards. You can create Global-VE interfaces only if the Router is powered on.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface global-veve-number

    A Global-VE interface is created and the Global-VE interface view is displayed.

  3. Run commit

    The configuration is committed.

Configuring FlexE Interfaces

A physical interface in standard Ethernet mode can be switched to flexible Ethernet (FlexE) mode, and a series of FlexE interfaces are generated accordingly. Interconnected devices can communicate with each other only after the physical interfaces have the same interconnection parameters configured.

Context

The interconnected physical interfaces in FlexE mode at both ends must have the same configurations. Equally, a FlexE interface at the local end and its counterpart at the remote end must also have the same configurations. Specifically, the physical interface configurations include the same group ID (specified by group-id) and the same PHY number (specified by phy-number). The FlexE interface configurations include the same bandwidth (specified by bandwidth) and client ID (specified by client-id). phy-number specifies the number for a physical interface in a FlexE group. client-id specifies the service ID for a FlexE interface in a FlexE group.

NOTE:

This configuration process is supported only on the Admin-VS.

Procedure

  1. Activate the interface basic license and FlexE license.
    1. Run license active file-name

      The license file is activated on the master main control board.

    2. Run system-view

      The system view is displayed.

    3. Run license

      The license view is displayed.

    4. (Optional) If the subcard being used is a 2x50G FPIC, run:

      active port-basic slot slot-id card card-id port port-list

      The basic licenses are activated.

    5. Run active port-flexe slot slot-id card card-id port port-list

      FlexE interface licenses are activated on CM boards.

    6. Run commit

      The configuration is committed.

  2. Switch an Ethernet interface from standard mode to flexible mode.

    1. Run flexethmode enable port port-position

      The interface is switched to flexible Ethernet mode.

      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/3/0 is switched to a physical interface in FlexE mode, the interface name is changed to FlexE-50|100GE 0/3/0. Additionally, a series of FlexE interfaces named FlexE 0/3/129 to FlexE 0/3/148 are generated. slot-id/card-id in the service interface number is consistent with that in the physical interface number.

    2. Run commit

      The configuration is committed.

  3. Create an interface group on the subcard.
    1. Run flexe group slot slot-id card card-id group group-id

      A FlexE group is created on the subcard.

    2. Run commit

      The configuration is committed.

  4. (Optional) Set a sub-timeslot granularity for the subcard.
    1. (Optional) Run set flexe sub-time-slot granula

      A sub-timeslot granularity is set for the subcard.

      NOTE:
      When the bandwidth value set for a FlexE interface on a subcard is less than 5 Gbit/s, run the set flexe sub-time-slot granula command to configure a sub-timeslot granularity for the subcard.A sub-timeslot granularity is planned as needed:
      • If the sub-timeslot granularity uses the default value of 5 Gbit/s, the bandwidth value of a FlexE interface is an integer multiple of 5 Gbit/s, such as 5 Gbit/s, 10 Gbit/s, 15 Gbit/s, and so on.

      • If the sub-timeslot granularity is set to 1 Gbit/s, the bandwidth value of a FlexE interface is 1 Gbit/s, 2 Gbit/s, 3 Gbit/s, 4 Gbit/s, 5 Gbit/s, or an integer multiple of 5 Gbit/s.

      • If the sub-timeslot granularity is set to 1.25 Gbit/s, the bandwidth value of a FlexE interface is 1.25 Gbit/s, 2.5 Gbit/s, 3.75 Gbit/s, 5 Gbit/s, or an integer multiple of 5 Gbit/s.

    2. Run commit

      The configuration is committed.

  5. Add a physical interface in FlexE mode to the interface group.
    1. Run interface interface-type interface-number

      The view of a physical interface in FlexE mode, such as FlexE-50G 0/1/0, is displayed.

    2. Run flexe-group group-id

      The physical interface in FlexE mode is added to the interface group.

      NOTE:
      To ensure proper communication between connected devices, the physical interfaces in FlexE mode on both devices must be added to the same interface group. However, the interface groups on the subcards of the connected devices can be different. For example, interface groups group1 and group2 are configured on Device A; interface groups group2 and group3 are configured on Device B. The physical interfaces in FlexE mode interconnecting the devices must be added to group2.

    3. Run commit

      The configuration is committed.

  6. Configure the phy-number parameter for the physical interfaces in FlexE mode.

    NOTE:
    To ensure proper communication between the devices, the same phy-number value must be configured for the physical interfaces in FlexE mode at both ends.

    1. Run phy-numbernumber

      The phy-number parameter is configured for the physical interface in FlexE mode.

    2. Run commit

      The configuration is committed.

    3. Run quit

      Return to the system view.

  7. Configure a bandwidth value for a FlexE interface.

    NOTE:

    To ensure proper communication, the bandwidth values must be consistent between FlexE interfaces.

    1. Run slot slot-id

      The slot view is displayed.

    2. Run flexe config-mode card card-id { bandwidth | timeslot }

      The bandwidth configuration mode of a FlexE interface is set to the bandwidth mode or timeslot mode.

    3. Run quit

      Return to the system view.

    4. Run interface interface-type interface-number

      The view of a FlexE interface, such as FlexE 0/3/129, is displayed.

    5. (Optional) Run flexethgroup group-id bandwidth { 1 | 1.25 | 2 | 2.5 | 3 | 3.75 | 4 | bandwidth-value }

      Bandwidth is directly configured for the FlexE interface. If the bandwidth configuration mode is set to the bandwidth mode in 7.b, perform this step. Otherwise, skip this step.

    6. (Optional) Run binding interface { interface-name | interface-type interface-number } time-slot time-slot-list [ sub-time-slot sub-time-slot-list ]

      One or more 5 Gbit/s timeslots of a physical interface in FlexE mode in a FlexE group or one or more sub-timeslots in a 5 Gbit/s timeslot are bound to the FlexE interface. The bound timeslots or sub-timeslots constitute bandwidth of the FlexE interface. If the bandwidth configuration mode is set to the timeslot mode in 7.b, perform this step. Otherwise, skip this step.

    7. Run commit

      The configuration is committed.

  8. Configure the client-id parameter for a FlexE interface.

    NOTE:

    To ensure proper communication between interworking devices, run the client-id command on the interconnected FlexE interfaces to configure the same client ID.

    1. Run client-id client-id

      The client-id parameter is configured for the FlexE interface.

    2. Run commit

      The configuration is committed.

Creating a Loopback Interface and Configuring Its IP Address

In most cases, you need to assign IP addresses to loopback interfaces, and then use the loopback interfaces that are always Up to communicate with other devices.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface loopback loopback-number

    A loopback interface is created.

    You can create or delete loopback interfaces dynamically. Once a loopback interface is created, it remains Up all the time.

  3. Run ip address ip-address [ mask | mask-length ]

    The IP address of the loopback interface is configured.

  4. Run commit

    The configuration is committed.

Entering the NULL Interface View

The system automatically creates a NULL0 interface. The NULL interface is used for preventing routing loops and filtering traffic.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface null 0

    The NULL interface view is displayed.

    The NULL interface is always in the Up state but does not forward any data packets. In addition, IP addresses cannot be configured on the NULL interface, and data link layer protocol cannot be encapsulated on the NULL interface.

Follow-up Procedure

The NULL interface is used to prevent routing loops and filtering traffic. If the ip route-static 192.168.0.0 255.255.0.0 NULL 0 command is run, the device will discard all packets destined for the network segments 192.168.0.1 to 192.168.255.255.

Verifying the Logical Interface Configuration

After the configuration on the interface is completed, check the configurations.

Prerequisites

Configuration of the Global-VE interface, FlexE interface license, Loopback interface or NULL interface is completed.

Procedure

  • Run the display interface global-ve [ ve-number ] command to check the status of the Global-VE interface.
  • Run the display license resource usage port-flexe { all | slot slot-id } [ active | deactive ] command to check the activation of FlexE interface licenses on boards.
  • Run the display interface loopback [ loopback-number ] command to check the status of the Loopback interface.
  • Run the display interface null [ 0 ] command to check the status of the NULL interface.

Example

Run the display interface global-ve command. The command output shows that the status of the link protocol on the Loopback interface is UP.

<HUAWEI> display interface global-ve 1
Global-VE1 current state : UP
Description:HUAWEI, Global-VE1 Interface
Route Port,The Maximum Transmit Unit is 1500
Internet protocol processing : disabled
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 0001-0001-0001
Full-duplex mode, negotiation: disable
Current system time: 2014-01-17 11:31:45
Statistics last cleared:never
    Last 200 seconds input rate: 0 bits/sec, 0 packets/sec
    Last 200 seconds output rate: 0 bits/sec, 0 packets/sec
    Input: 0 bytes, 0 packets
    Output: 0 bytes, 0 packets
    Input:
      Unicast: 0, Multicast: 0
      Broadcast: 0, Drops: 0
    Output:
      Unicast: 0, Multicast: 0
      Broadcast: 0, Drops: 0
    Input bandwidth utilization  :    0%
    Output bandwidth utilization :    0%

Run the display license resource usage port-flexe { all | slot slot-id } [ active | deactive ] command to check the activation of FlexE interface licenses on boards.

<HUAWEI> display license resource usage port-flexe all
Global license information:
===============================================================================
FeatureName       Offline     Allocated     Activated     Available     Total  
LCR5S40VFLE0P       0            0             1             0           1

License detailed information:
===============================================================================
Physical Position    FeatureName     Needed Count    Used Count      Active Status
0/3/0               LCR5S40VFLE0P        1               1            Activated

Run the display interface loopback command. The command output shows that the status of the link protocol on the Loopback interface is UP.

<HUAWEI> display interface loopback 0
LoopBack0 current state : UP (ifindex: 39)
Line protocol current state : UP (spoofing)
Description:
Route Port,The Maximum Transmit Unit is 1500
Internet protocol processing : disabled
Current system time: 2010-07-15 16:58:21
Physical is Loopback
    Last 300 seconds input rate 0 bits/sec, 0 packets/sec
    Last 300 seconds output rate 0 bits/sec, 0 packets/sec
    Realtime 0 seconds input rate 0 bits/sec, 0 packets/sec
    Realtime 0 seconds output rate 0 bits/sec, 0 packets/sec
    Input: 0 packets,0 bytes,
           0 unicast,0 broadcast,0 multicast
           0 errors,0 drops,0 unknownprotocol
    Output:0 packets,0 bytes,
           0 unicast,0 broadcast,0 multicast
           0 errors,0 drops  

Run the display interface null command. The command output shows that the status of the NULL interface is UP.

<HUAWEI> display interface null 0
NULL0 current state : UP (ifindex: 1)
Line protocol current state : UP (spoofing)
Description:
Route Port,The Maximum Transmit Unit is 1500
Internet protocol processing : disabled
Current system time: 2010-07-15 16:59:03
Physical is NULL DEV
    Last 300 seconds input rate 0 bits/sec, 0 packets/sec
    Last 300 seconds output rate 0 bits/sec, 0 packets/sec
    Realtime 0 seconds input rate 0 bits/sec, 0 packets/sec
    Realtime 0 seconds output rate 0 bits/sec, 0 packets/sec
    Input: 0 packets,0 bytes,
           0 unicast,0 broadcast,0 multicast
           0 errors,0 drops,0 unknownprotocol
    Output:0 packets,0 bytes,
           0 unicast,0 broadcast,0 multicast
           0 errors,0 drops
Download
Updated: 2019-01-02

Document ID: EDOC1100058380

Views: 1809

Downloads: 15

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