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

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 an Ethernet Interface on an Interface Board

Configuring an Ethernet Interface on an Interface Board

You can configure parameters for Ethernet interfaces on interface boards to ensure that physical connections work properly between devices.

Usage Scenario

You need to configure parameters for an Ethernet interface before using the interface to transmit packets on an Ethernet.

All parameters for an Ethernet interface have default values, except the IP address. Any change to an Ethernet interface on a local device must be the same as that on the peer device.

Pre-configuration Tasks

None

Ethernet Interface Attributes

Listed in Table 3-2, different Ethernet interfaces on theME60 support different attributes.

Table 3-2 Ethernet interface attributes

Ethernet Interface Attribute

Ethernet Electrical Interface

Ethernet Optical Interface

10GE WAN Interface

10GE LAN/WAN Interface

Run the

mtu mtu or ipv6 mtu mtu command to configure an MTU.

Supported Supported Supported Supported
Run the

duplex { full | half | auto } command to configure a duplex mode.

Supported Not supported (the default full-duplex mode is supported) Not supported Not supported
Run the

speed { 10 | 100 | auto } command to configure the rate for an Ethernet electrical interface.

Supported Not supported Not supported Not supported
Run the

negotiation auto command to configure the auto-negotiation mode.

Supported Supported Not supported Not supported
Run the

flow control [ receive | send ] command to configure flow control on a GE interface.

Supported Supported Supported Supported
Run the

flag command to configure overhead bytes for a 10GE WAN interface.

Not supported Not supported Supported Supported by WAN interfaces but not supported by LAN interfaces

Configuration Procedures

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

Setting the Maximum Frame Length Allowed by an Ethernet Interface

Jumbo frames are designed for gigabit Ethernet networks. They are giant frames and their lengths vary according to vendors. To enable devices that transmit different lengths of jumbo frames to communicate successfully, adjust the maximum frame length allowed by either the local or peer Ethernet interface.

Context

An Ethernet network splits data into frames with a certain length and adds frame headers and trailers when transmitting them. If jumbo frames are used to complete file transfer, frame costs are reduced, and network resource utilization and transmission efficiency are improved.

To enable two interfaces to communicate successfully, ensure that a jumbo frame sent by an interface is not greater than that allowed by the other interface.

NOTE:
  • Properly plan the jumbo frame length before network deployment. A jumbo frame is discarded or processed incorrectly if its length exceeds that allowed by an interface.
  • Setting the maximum frame length allowed by an Ethernet interface limits the maximum length of Ethernet Layer 2 packets, thus affecting the MTU for Layer 3 packets. If a service also has MTU requirements, plan both the MTU and maximum frame length properly.

Perform the following operations on each ME device:

Procedure

  • Set the maximum frame length allowed by an Ethernet interface.
    1. Run system-view

      The system view is displayed.

    2. Run interface gigabitethernet interface-number

      The Ethernet interface view is displayed.

    3. Run jumboframe value

      The maximum frame length allowed by the Ethernet interface is set.

    4. Run commit

      The configuration is committed.

Configuring the MTU for an Ethernet Interface

MTU is the largest packet of data that can be transmitted on a network, expressed in bytes. MTU is determined by data link layer protocols, and MTU values vary with networks. A proper MTU is a prerequisite for normal communication between network devices.

Context

The size of packets is limited at the network layer. Whenever receiving an IP packet, the IP layer determines the next-hop interface for the packet and obtains the MTU configured on the interface. Then, the IP layer compares the MTU with the packet length. If the packet length is longer than the MTU, the IP layer fragments the packet into smaller packets, which are shorter than or equal to the MTU.

If unfragmentation is configured, some packets may be discarded during data transmission at the IP layer. To ensure that jumbo packets are not dropped during transmission, set an MTU on an interface to fragment these packets into smaller ones.

NOTE:
  • After changing the MTU on a specified interface, you need to restart the interface to validate the newly-configured MTU by running the shutdown and undo shutdown commands in sequence.
  • If the Ethernet interface has sub-interfaces, you need to run the undo shutdown command 15 seconds after running the shutdown command.
NOTE:
  • If the size of packets is much greater than the configured MTU value, the packets are broken into a great number of fragments. The packets may be discarded by quality of service (QoS) queues.

  • If the configured MTU value is too large, packets may be transmitted at a low speed.

  • After changing the MTU of an Ethernet interface, also change the MTU of the peer Ethernet interface to ensure that the MTUs of both interfaces are the same. If the MTUs are different, services may be interrupted.

Perform the following steps on each ME device:

Procedure

  • Set an IPv4 MTU for an Ethernet interface.
    1. Run system-view

      The system view is displayed.

    2. Run interface gigabitethernet interface-number

      The specified Ethernet interface view is displayed.

    3. Run mtu mtu

      An IPv4 MTU is set for the Ethernet interface.

      The MTU is expressed in bytes. The MTU value range of an Ethernet interface is determined by the device type.

    4. Run commit

      The configuration is committed.

  • Set an IPv6 MTU for an Ethernet interface.
    1. Run system-view

      The system view is displayed.

    2. Run interface gigabitethernet interface-number

      The specified Ethernet interface view is displayed.

    3. Run ipv6 enable

      IPv6 is enabled on the Ethernet interface.

    4. Run ipv6 mtu mtu

      An IPv6 MTU is set for the Ethernet interface.

      The MTU is expressed in bytes. The MTU value range of an Ethernet interface is determined by the specific device.

    5. Run commit

      The configuration is committed.

Follow-up Procedure

The length of a QoS queue is limited. If the size of packets is much greater than the configured MTU value, the packets are broken into a great number of fragments. The packets may be discarded by the QoS queue. To address this problem, you can increase the length of the QoS queue. The queue scheduling mechanism First In First Out (FIFO) is used on an interface by default. You can change the FIFO queue length. For detailed configuration of a QoS queue, see HUAWEI ME60 Multiservice Control Gateway Configuration Guide - QoS.

Configuring the Working Mode for an Ethernet Interface

An Ethernet interface works in either half-duplex or full-duplex mode at the physical layer of an Ethernet network. To ensure communication between devices, configure a proper working mode for an Ethernet interface.

Context

On a large-scale Ethernet network, it takes a great deal of time to manually set the interface rate and duplex mode, verify device configurations, and check statistics on Ethernet interfaces. Manually setting the interface rate and duplex mode is recommended only when auto-negotiation of an Ethernet link fails. When there is an auto-negotiation problem, upgrade software or hardware to support the auto-negotiation mechanism defined in IEEE 802.3u/z.

Perform the following steps on each ME device:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface gigabitethernet interface-number

    The specified Ethernet interface view is displayed.

  3. Run either of the following commands as required.

    • Run duplex { full | half | auto }

      The working mode is configured for the Ethernet interface.

    • Run negotiation auto

      The Ethernet interface is configured to work in auto-negotiation mode.

    NOTE:
    • Ethernet optical interfaces work only in full-duplex mode.
    • When connecting to a hub, an Ethernet electrical interface on the ME device must work in half-duplex mode because the hub can work only in half-duplex mode. When connecting to a LAN switch, an Ethernet electrical interface on the ME device can work in either full-duplex or half-duplex mode. Ethernet electrical interfaces on the ME device and peer device must work in the same mode.
    • If the working rate of a GE electrical interface is 1000 Mbit/s, you cannot configure the GE electrical interface to work in half-duplex mode.
    • If the working rate of a GE electrical interface is 1000 Mbit/s and auto-negotiation is enabled, you cannot configure the GE electrical interface to work in half-duplex or full-duplex mode. In addition, you cannot disable auto-negotiation on the interface.
    • If the working rate of a GE electrical interface is 10 Mbit/s or 100 Mbit/s, you can configure the GE electrical interface to work in half-duplex, full-duplex, or auto-negotiation mode.
    • If auto-negotiation is enabled on a GE electrical interface of a local device, auto-negotiation must also be enabled on the GE electrical interface of the peer device.

  4. Run commit

    The configuration is committed.

Configuring the Working Rate for an Ethernet Electrical Interface

The volume of traffic that can be transmitted on an Ethernet electrical interface is determined by the working rate of the interface. To ensure communication between devices, set a proper working rate for Ethernet electrical interfaces.

Context

On a large-scale Ethernet network, it takes a great deal of time to manually set the interface rate and duplex mode, verify device configurations, and check statistics on Ethernet interfaces. Manually setting the interface rate and duplex mode is recommended only when auto-negotiation of an Ethernet link fails. When there is an auto-negotiation problem, upgrade software or hardware to support the auto-negotiation mechanism defined in IEEE 802.3u/z.

You need to set the working rate only for Ethernet electrical interfaces, not Ethernet optical interfaces.

Perform the following steps on each ME device:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface gigabitethernet interface-number

    The specified Ethernet electrical interface view is displayed.

  3. Run speed { 10 | 100 | auto }

    The working rate is set for the Ethernet electrical interface.

  4. Run commit

    The configuration is committed.

Configuring the Optical or Electrical Mode for a GE Interface

In most cases, the system recognizes the interface module and therefore automatically sets the optical or electrical mode of an interface. If the system fails to recognize the interface module, configure the optical or electrical mode for an interface.

Context

Perform the following steps on each ME device:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface gigabitethernet interface-number

    The specified Ethernet interface view is displayed.

  3. Run port-type { copper | fiber-100 | fiber-1000 }

    The optical or electrical mode is configured.

    The port-type command can be used only on auto-sensing optical or electrical GE interfaces.

    If the ME device recognizes the type of a Small Form-Factor Pluggable (SFP) module, the system sets the optical or electrical mode of the interface accordingly without additional configurations.

    If the ME device does not recognize the type of an SFP module that works properly, you need to configure the working mode for the interface.

  4. Run commit

    The configuration is committed.

Configuring the LAN/WAN Transmission Mode for a 10GE Interface

A 10G XFP multi-mode optical transceiver works in either LAN or WAN mode. You can configure a proper mode as required.

Context

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

Perform the following steps on the ME device:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface gigabitethernet interface-number

    The view of the 10GE interface is displayed.

  3. Run shutdown

    The interface is shut down.

  4. Run set transfer-mode { lan | wan }

    The LAN/WAN transmission mode is configured for the 10GE interface.

  5. Run undo shutdown

    The interface is restarted.

    NOTE:

    Before configuring the LAN/WAN transmission mode for a 10GE interface, delete all configurations on the interface, excluding the IP address, and shut down the interface.

  6. Run commit

    The configuration is committed.

Configuring the Overhead Byte for a 10GE WAN Interface

SONET/SDH provides a variety of overhead bytes. You can configure overhead bytes for a 10GE WAN interface to implement monitoring at different levels.

Context

10 GE WAN interfaces need to use SDH/SONET as the frame format, and the overhead byte needs to be set.

Perform the following steps on the ME device:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface gigabitethernet interface-number

    The specified Ethernet interface view is displayed.

  3. Configure an overhead byte for the 10GE WAN interface.

    Run any of the following commands as required.

    • Run flag j0 64byte-or-null-mode [ j0-value ] or flag j0 { 16byte-mode | 1byte-mode } j0-value

      The overhead byte j0 is configured for the interface.

    • Run flag j1 64byte-or-null-mode [ j1-value ] or flag j1 { 16byte-mode | 1byte-mode } j1-value

      The overhead byte j1 is configured for the interface.

    • Run flag c2 c2-value

      The overhead byte c2 is configured for the interface.

  4. Run commit

    The configuration is committed.

Enabling Flow Control on a GE Interface

To prevent traffic congestion between a local device and its peer device, configure flow control on GE interfaces of both devices to control the rates at which the GE interfaces send and receive packets.

Context

Perform the following steps on each ME device:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface gigabitethernet interface-number

    The specified Ethernet interface view is displayed.

  3. Run flow control [ receive | send ]

    Flow control is enabled on a GE interface.

    After flow control is enabled on a GE interface, if the rate at which the peer interface sends traffic reaches the set threshold, such as 1 Gbit/s, the interface sends a Pause frame to instruct the peer interface to send traffic at a lower rate. If the peer interface also supports flow control, it sends data at a lower rate after receiving the Pause frame. This allows the local interface to process received frames properly. If the peer interface does not support flow control, it will not send data at a lower rate after receiving the Pause frame.

  4. Run commit

    The configuration is committed.

Configuring Self-Loop Detection on the GE Interface

After the self-loop detection function is enabled, the self-loop on an interface can be detected and then the interface is blocked.

Context

A router enabled with the loopback detect function periodically sends specially constructed loopback detect packets. If a self-loop exists on an interface, the loopback detect packets will be looped back to the router, and the router can then determine that a self-loop has occurred. A malicious attacker can trick a loopback-detect-enabled router into believing that a self-loop has occurred, by sending loopback detect packets obtained using Sniffer back to the router.

The GE interface self-loop detection function is used only for link self-loop tests in the service deployment phase. To prevent security risks, disable this function after services are running properly.

Do as follows on the ME devices:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface gigabitethernet interface-number

    The GE interface view is displayed.

  3. Run loopback-detect enable

    The self-loop detection function is enabled.

  4. Run loopback-detect block block-time

    Set the delay time of the interface recovery after the self-loop on the interface is eliminated.

Enabling the Statistics Function on a Sub-interface

After enabling the statistics function on a sub-interface, you can view the statistics about received or sent packets on the sub-interface.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number [ .subinterface-number ]

    The view of the Ethernet sub-interface that requires the statistics function is displayed.

  3. Run statistic enable

    The statistics function is enabled on an Ethernet sub-interface.

  4. Run commit

    The configuration is committed.

    NOTE:
    In addition to running the statistic enable command on a sub-interface to enable the statistics function, you can run the subinterface traffic-statistics enable command in the system view or Ethernet interface view to enable the statistics function in batches. Running the subinterface traffic-statistics enable command consumes a large number of system resources. Therefore, exercise caution when running this command. Note the following points:
    • If the subinterface traffic-statistics enable command is run in the system view, the traffic statistics function is enabled on all sub-interface of the device.
    • If the subinterface traffic-statistics enable command is run in the view of a physical interface, the traffic statistics function is enabled on all sub-interfaces of the interface.

Configuring the Hold-Time Interval After an Interface Goes Up/Down

When an interface frequently alternates between Up and Down, flapping may occur. To prevent the problem, you can configure the hold-time interval after an interface goes Up or Down.This command is supported only on the Admin-VS.

Procedure

  1. Run system-view

    The system view is displayed.

  2. To configure the hold-time interval after the interface goes Up or Down globally, perform either of the following configurations as required.

    • Run the carrier up-hold-time interval command to configure the hold-time interval before the interface goes Up.

    • Run the carrier down-hold-time interval command to configure the hold-time interval before the interface goes Down.

    When a non-default hold-time interval is configured on the interface, the interval configured on the interface takes effect. When the interface uses the default hold-time interval, the global configuration takes effect.

  3. To set the hold-time interval value on a speicified interface, Run interface interface-type interface-number

    The interface view is displayed.

  4. Run either of the following commands as required.

    • To configure the hold-time interval after an interface goes Up, run carrier up-hold-time interval

    • To configure the hold-time interval after an interface goes Down, run carrier down-hold-time interval

  5. Run commit

    The configuration is committed.

Disabling an Ethernet Interface or Sub-interface from Broadcasting Packets

To protect a device against attacks from broadcast packets and improve network security, disable the Ethernet interfaces or sub-interfaces on the device from broadcasting packets.

Context

An Ethernet interface or sub-interface broadcasts the packets they receive. Broadcasting attack packets from attackers consumes a lot of device resources, causing device performance deterioration and even device breakdown. To resolve this problem, disable the Ethernet interface or sub-interface from broadcasting packets.

You can disable the Ethernet interface or sub-interface from broadcasting packets if the network has fixed topologies or is configured with routes specified by static MAC addresses.

Procedure

  • Disable an Ethernet interface from broadcasting packets.

    NOTE:

    The Ethernet interface must work in Layer 2 mode. Otherwise, it cannot be disabled from broadcasting packets.

    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The view of the Ethernet interface to be disabled from broadcasting packets is displayed.

    3. Run portswitch

      The interface is switched to the Layer 2 mode.

      If the Ethernet interface has been operating in Layer 2 mode, skip this step.

    4. Run broadcast discard

      The Ethernet interface is disabled from broadcasting packets.

    5. Run commit

      The configuration is committed.

  • Disable an Ethernet sub-interface from broadcasting packets.

    NOTE:

    Before disabling an Ethernet sub-interface from broadcasting packets, make sure that the sub-interface is configured as a Dot1q sub-interface, QinQ VLAN tag termination sub-interface, Dot1q VLAN tag termination sub-interface, or QinQ stacking sub-interface.

    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number.subinterface-number

      The view of the Ethernet sub-interface to be disabled from broadcasting packets is displayed.

    3. Run any of the following commands:

      • To configure the Ethernet sub-interface as a Dot1q sub-interface, run the vlan-type dot1q vlan-id command.

      • To configure the Ethernet sub-interfaces as a Dot1q sub-interface and configure a policy for it, run the vlan-type dot1q vlanid { 8021p { 8021p-value1 [ to 8021p-value2 ] } &<1-8> | dscp { dscp-value1 [ to dscp-value2 ] } &<1-10>| default | eth-type eth-type-value } command.

      • To configure the Ethernet sub-interface as a Dot1q VLAN tag termination sub-interface, run the dot1q termination vid low-pe-vid [ to high-pe-vid ] [ vlan-group group-id ] command.

      • To configure the Ethernet sub-interface as a Dot1q VLAN tag termination sub-interface and configure a policy for it, run the dot1q termination vid low-pe-vid [ to high-pe-vid ] { 8021p { 8021p-value1 [ to 8021p-value2 ] } &<1-8> | dscp { dscp-value1 [ to dscp-value2 ] } &<1-10> | eth-type eth-type-value | default } [ vlan-group group-id ] command.

      • To configure the Ethernet sub-interface as a QinQ VLAN tag termination sub-interface, run the qinq termination pe-vid pe-vid [ to high-pe-vid ] ce-vid ce-vid [ to high-ce-vid ] [ vlan-group group-id ] command.

      • To configure the Ethernet sub-interface as a QinQ stacking sub-interface, run the qinq stacking vid low-ce-vid [ to high-ce-vid ] [ vlan-group group-id ] command.

      • To configure the Ethernet sub-interface as a QinQ stacking sub-interface and configure a policy for it, run the qinq stacking vid [ low-ce-vid to high-ce-vid ] { 8021p { 8021p-value1 [ to 8021p-value2 ] } &<1-8> | dscp { dscp-value1 [ to dscp-value2 ] } &<1-10> | eth-type eth-type-value | default } [ vlan-group group-id ] command.

    4. Run broadcast discard

      The Ethernet sub-interface is disabled from broadcasting packets.

    5. Run commit

      The configuration is committed.

(Optical) Setting a Bandwidth Mode for an Interface

An interface's bandwidth mode (1/10 Gbit/s) is restricted by its hosting device's hardware. Before setting a bandwidth mode for an interface, ensure that the hardware supports this function.

Context

When interconnecting interfaces that require the same bandwidth mode, you can run the port-mode command to set an interface's bandwidth.

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

Perform the following steps on the ME device:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The GE interface view is displayed.

  3. Set an interface's bandwidth.
    • Run port-mode { 1GE | 10GE }

      The bandwidth mode for a GE interface is configured.

  4. Run commit

    The configuration is committed.

Verifying the Ethernet Interface Configuration

After an Ethernet interface is successfully configured on an interface board, you can view information about the IP address, MTU, working rate, working mode, and interface type of the Ethernet interface, and statistics about packets sent and received on the interface.

Procedure

  • Run the display interface gigabitethernet interface-number command to check the status of the specified Ethernet interface.
  • Run the display transfer-mode command to check the transfer mode of a specific 10 GE LAN WAN interface.

Example

Run the display interface gigabitethernet interface-number command, and you can view the MTU, IP address, mask, working rate, and working mode of the Ethernet interface.

<HUAWEI> display interface gigabitethernet 2/0/0
GigabitEthernet2/0/0 current state : UP
Line protocol current state : UP(ifindex: 5)
Last line protocol up time : 2012-12-14 14:21:38
Description: 
Route Port,The Maximum Transmit Unit is 1500
Internet Address is 10.3.5.10/24
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 001a-bb2c-0101
The Vendor PN is FTM3112CSL40GHW 
The Vendor Name is SOURCEPHOTONICS 
Port BW: 1G, Transceiver max BW: 1G, Transceiver Mode: SingleMode
WaveLength: 1310nm, Transmission Distance: 40km
Rx Power:  -2.62dBm, normal range: [-23.011,  -2.999]dBm
Tx Power:  -2.94dBm, normal range: [-5.000,  0.000]dBm
Loopback:none, full-duplex mode, negotiation: disable, Pause Flowcontrol:Receive Enable and Send Enable
Last physical up time   : 2012-12-14 14:21:38
Last physical down time : 2012-12-14 14:21:36
Current system time: 2012-12-14 14:43:17
Statistics last cleared:never
    Last 300 seconds input rate: 603172 bits/sec, 691 packets/sec
    Last 300 seconds output rate: 1536 bits/sec, 2 packets/sec
   Input peak rate 603172 bits/sec, Record time: 2012-12-14 14:43:17
   Output peak rate 1536 bits/sec, Record time: 2012-12-14 14:43:17
    Input: 21530408 bytes, 193944 packets
    Output: 83966 bytes, 994 packets
    Input: 
      Unicast: 31766 packets, Multicast: 162177 packets
      Broadcast: 1 packets, JumboOctets: 346 packets
      CRC: 0 packets, Symbol: 0 packets
      Overrun: 0 packets, InRangeLength: 0 packets
      LongPacket: 0 packets, Jabber: 0 packets, Alignment: 0 packets
      Fragment: 0 packets, Undersized Frame: 0 packets
      RxPause: 0 packets
    Output:
      Unicast: 472 packets, Multicast: 521 packets
      Broadcast: 1 packets, JumboOctets: 0 packets
      Lost: 0 packets, Overflow: 0 packets, Underrun: 0 packets
      System: 0 packets, Overruns: 0 packets
      TxPause: 0 packets
    Last 300 seconds input utility rate:  0.07%
    Last 300 seconds output utility rate: 0.01%

Run the display transfer-mode command to view the transfer mode of a specific 10 GE LAN WAN interface.

[~HUAWEI-GigabitEthernet1/0/0] display transfer-mode
  Info: Transfer-mode is LAN    
Run the display loopback-detect block [ all | interface interface-type interface-number ] command to view the self-loop detection information about all the blocked interfaces.
<HUAWEI> display loopback-detect block all
Info: There is no block interface in this router.
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059440

Views: 29846

Downloads: 21

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