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

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 12

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
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 Attributes for an Optical Interface

Configuring Attributes for an Optical Interface

This section describes how to configure attributes for an optical interface.

Configuring Interface Split

Context

The interface split function allows a high-bandwidth physical interface on the device to be configured as multiple independent low-bandwidth interfaces. A high-bandwidth interface on the device can be configured as multiple low-bandwidth interfaces or directly used based on the interface type on the remote device. The interface split function allows for flexible networking and lowers hardware costs.

A 40GE interface can be configured as four 10GE interfaces on the CX710 switch module 40GE converged switching plane. After a 40GE interface is split, connect the interface to four 10GE interfaces on the remote device using a one to four cable, as shown in Figure 4-3. If the 40GE interface is connected to a remote 40GE interface that is also split, the two 40GE interfaces can have the same type of 40GE QSFP+ optical modules installed and be connected using an optical fiber, not a one to four cable.

For the numbering method of converted interfaces, see Interface Overview.
Figure 4-3 Connecting the split 40GE interface to 10GE interfaces on the remote device

  • If an interface is split or the split configuration on the interface is canceled, the original configuration on the interface is lost. Therefore, exercise caution when you split an interface or cancel the split configuration.

  • If a 40GE interface has been added to a stack interface, the 40GE interface cannot be split.

  • The internal 40GE interface for connecting one CX710 switch module to another cannot be split.

  • If a 40GE interface is not split and is connected to four 10GE interfaces on the remote device using a one to four cable, the 40GE interface cannot go Up and the interface indicator is off. The four 10GE interfaces on the remote device can go Up and the interface indicators are on.

  • The indicator status of a split 40GE port is the same as that of the 10GE port to which the first split optical fiber is connected. It is recommended that you use the 10GE ports by starting from the one to which the first split optical fiber is connected.

  • Assume that a device is added to a stack and 40GE interfaces on the device are configured as 10GE interfaces. The device leaves the stack and a new device of the same model joins the stack. If the stack ID of the new device is the same as that of the original device, the original 40GE interface split configuration takes effect on the new device and the service configuration on the converted 10GE interfaces is retained. The configuration is automatically delivered to the new device without manual intervention. The time taken to start the device is longer than the time normally used to start a device.

  • In V100R001C10, converted interfaces are numbered by adding a dimension to the original interface number. In versions earlier than V100R001C10, converted interfaces are numbered by interface sequence. If the system software version is downgraded from V100R003C00SPC100 to an earlier version, the original interface split configuration is lost. You need to reconfigure the interface split function.
  • On the CX710 switch module 40GE converged switching plane, 10GE interfaces split from 40GE interfaces do not support the packet forwarding mode set to Cut Through.

Procedure

  1. Configure the numbering rule of converted interfaces.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      port split dimension interface  { 40ge interface-number1 [ to 40ge interface-number2 ] } &<1-12> [ split-type 4*10ge ]

      Interfaces converted from a 40GE interface are numbered using the dimension numbering rule or interface sequence numbering rule.

    3. Run:

      commit

      The configuration is committed.

    4. Run:

      quit

      Return to the user view.

    5. Run:

      save

      The current configuration is saved.

Configuring the Training Function on a 40GE Interface

Context

NOTE:

Only the CX710 switch module 40GE converged switching plane series switches support the configuration of the training function.

With the increase of transmission rate or frequency, attenuation of signal's high-frequency components becomes increasingly severe. To guarantee transmission performance of signals, it is necessary to compensate for signals, and commonly used compensation technologies are pre-emphasis and balancing. The pre-emphasis technology increases high-frequency components of signals at the transmitter end of transmission lines to compensate attenuation during the transmission. However, the pre-emphasis technology increases crosstalk while amplifying high-frequency components. To solve this problem, the balancing technology is developed. The balancing technology is used at the receiver end of transmission lines to function like a filter for filtering high-frequency crosstalk.

After the training function is enabled on a 40GE interface, the transmitter end exchanges frames with the receiver end to automatically set the pre-emphasis and balancing parameters, improving process efficiency of the two technologies. It should be noted that the negotiated parameters for the training function are obtained based on the site environment. If the site environment changes, for example, from high-temperature environment to low-temperature environment, the parameters may be inaccurate. Therefore, error codes may occur when the training function is enabled. The training function is optional in IEEE802.3 standards, and its implementation on different types of products from various vendors may differ. When connecting two devices, ensure that the training function must be enabled or disabled on both ends simultaneously.

NOTE:

CX710 does not support 40GE for auto-negotiation when it is connected to an optical cable; therefore, the CX710 does not support this function.

The training disable or undo training disable command can be configured only when a 40GE interface connects to a high-speed cable, and the training function takes effect on the interface only when the interface works in auto-negotiation mode.

On a 40GE interface connected to a high-speed cable and configured with the training function, if you run the negotiation disable command to set the interface working mode to non-auto negotiation, the training function will not take effect.

If a 40GE interface has been used as a stack interface, the training function cannot be disabled. If the training function is disabled on a 40GE interface, it cannot be configured as a physical stack member interface.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface 40ge interface-number

    The 40GE interface view is displayed.

  3. Run:

    training disable

    The training function is disabled on the interface.

    By default, the training function is enabled on a 40GE interface.

  4. Run:

    commit

    The configuration is committed.

Configuring Interface Aggregation

Context

The interface aggregation function combines multiple independent low-bandwidth interfaces on a device into a high-bandwidth interface.You can use multiple low-bandwidth interfaces or a high-bandwidth interface based on the interface type on the peer device. The interface aggregation function allows flexible networking and reduces hardware costs.

The CX31x series switch modules support aggregation of four 10GE interfaces into one 40GE interface. You can connect to the 40GE interface on the peer device by using a dedicated one-to-four cable, as shown in Figure 4-4. If the 40GE interface on the peer device is also aggregated, install four 10GE SFP+ modules in the four 10GE interfaces on both ends, and then connect the four pairs of interfaces by using optical cables.

For the numbering method of aggregation interfaces, see Interface Overview.
Figure 4-4 Connecting the aggregated 10GE interfaces to the 40GE interface on the peer device

  • After interfaces are aggregated or interface aggregation is canceled, the system prompts you to restart the server for the configuration to take effect. The original configuration on the interface will be lost after the restart. Therefore, perform the operation with caution.

  • If a 10GE interface has been added to a stack interface, the 10GE interface cannot be aggregated.

  • If four 10GE interfaces (for example, interfaces 1 to 4 or 5 to 8) in a space are not aggregated and connected to the 40GE interface on the peer device by using the same optical modules and a one-to-four cable, the 40GE interface cannot go Up and its indicator is off, while the four 10GE interfaces can go Up and the interface indicators are steady on.

  • If a high-speed cable connects to panel ports, the numbers of the 10GE ports on the 10GE high-speed cables must be connected to the for 10GE ports (ports 1 to 4 or 5 to 8) in the same space in the following sequence to ensure that the peer 40GE port can be in the UP state:
    • The four 10GE ports on high-speed cable 1 correspond to the 10GE ports 4, 8, 12, and 16 on the panel.
    • The four 10GE ports on high-speed cable 2 correspond to the 10GE ports 3, 7, 11, and 15 on the panel.
    • The four 10GE ports on high-speed cable 3 correspond to the 10GE ports 2, 6, 10, and 14 on the panel.
    • The four 10GE ports on high-speed cable 4 correspond to the 10GE ports 1, 5, 9, and 13 on the panel.
  • Assume that a device is added to a stack group and 10GE interfaces on the device are aggregated into a 40GE interface. The device leaves the stack group and a new device of the same model joins the stack group. If the stack ID of the new device is the same as that of the original device, the original 10GE interface aggregation configuration takes effect on the new device and the service configuration on the 40GE aggregation interfaces is retained. The configuration is automatically delivered to the new device without manual intervention. The time taken to start the device is longer than the time normally used to start a device.

Procedure

  1. Run the system-view command to go to the system view.
  2. Run the commit command to submit the configuration.
  3. Run the quit command to go to the user view.
  4. Run the save command to save the configuration.

    For the CX31x series switch modules, interface aggregation takes effects or cancels after you save the configuration and restart the device.

  5. Run the port aggregation interface { 10ge interface-number1 [ to 10ge interface-number2 ]} command to aggregate 10GE interfaces.

    By default, interfaces are not aggregated.

Checking the Configuration Result

Run the display port aggregation [ slot slot-id ] command to check the interface aggregation configuration result.

Configuring Unidirectional Single-Fiber Communication

Context

During network management and maintenance, the administrator may need to send traffic from users to a specified server for analysis, recording, and processing. If a server can receive and send packets, there is a possibility that the server forwards user traffic to other devices, causing a security risk. The unidirectional single-fiber communication function can address this issue. A single fiber means that two optical modules are connected by only one fiber, and unidirectional communication means that packets can be sent in only one direction. With this function, a switch can only send but cannot receive packets, and an analysis server can only receive but cannot send packets. The data security on the analysis server is ensured.

An optical module provides a TX end and an RX end. Generally, two optical modules are connected by two fibers. The TX and RX ends of one module are respectively connected to the RX and TX ends of another module. A device transmits and receives packets through two independent fibers. If the unidirectional single-fiber communication function is disabled, two devices cannot communicate with each other through a single fiber. After this function is configured, the devices can use only one fiber to communicate with each other.

As shown in Figure 4-5, SwitchA is connected to the upper-layer traffic distribution device through 10GE2/17/1. The traffic sent from the traffic distribution device enters SwitchA through 10GE2/17/1. SwitchA transmits packets through 10GE2/17/2, the analysis server receives packets through the optical interface. After the unidirectional single-fiber function is configured on interface 10GE2/17/2, you only need to connect the TX end of the optical module on 10GE2/17/2 to the RX end of the optical module on the analysis server through one fiber. Then the switch can transmit packets to the analysis server through a single fiber, and the analysis server can receive packets through a single fiber. In addition, the TX end of the optical module on the analysis server is not connected, so the analysis server cannot transmit packets, ensuring data security on the server.

Figure 4-5 Networking diagram of unidirectional single-fiber communication

NOTE:

CX710 switch module does not support this function.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface interface-type interface-number

    The interface view is displayed.

  3. Run:

    single-fiber enable

    Unidirectional single-fiber communication is configured.

    By default, unidirectional single-fiber communication is disabled.

  4. Run:

    commit

    The configuration is committed.

Triggering Error-down When the Received Optical Power Is Low

Context

When the Received optical power of an Ethernet optical interface is too low, faults such as packet loss will occur. The interface is still in Up state in this situation. Therefore, even if a backup link is configured, services cannot be switched to the backup link. To avoid impact on services, you can configure the function of triggering Error-down. After this function is configured, the device shuts down the interface if the Received optical power of the interface falls below the lower alarm threshold and records an ERROR DOWN(transceiver-power-low) state (this state means that the interface is Down because of low Received optical power). Then services can be switched to the backup link immediately.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface interface-type interface-number

    The interface view is displayed.

  3. Run:

    port transceiver-power-low trigger error-down

    The interface is configured to transit to the error-down state when the received optical power is low.

    By default, the Ethernet optical interface does not transit to the error-down state when the received optical power is low.

  4. Run:

    commit

    The configuration is committed.

Checking the Configuration

Run the display error-down recovery [ interface interface-type interface-number ] command in any view to check information about the interfaces in Error-down state.

Follow-up Procedure

An interface in the Error-down state can be recovered in either of the following methods:
  • Manual recovery. If a few interface needs to be recovered forcibly, run the shutdown and undo shutdown commands in the interface views. Alternatively, run the restart command in the interface views to restart the interfaces.
  • Automatic recovery. If a large number of interfaces need to be recovered, manual recovery is time consuming. You can run the error-down auto-recovery cause transceiver-power-low interval interval-value command in the system view to enable automatic interface recovery and set the recovery delay time. An interface in Error-down state can be automatically recovered when the specified delay time expires.
Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 58483

Downloads: 3621

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