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 - DCN and Server Management

CloudEngine 8800, 7800, 6800, and 5800 V200R003C00

This document describes the configurations of Trill, FCoE, DCB, and NLB Server Cluster Association.
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).
Adjusting the TRILL Network Convergence Speed

Adjusting the TRILL Network Convergence Speed

Pre-configuration Task

Before adjusting the TRILL network convergence speed, complete the following task:

Configuration Procedure

You can choose one or more configuration tasks as required.

Configuring the Interval for Detecting Neighboring Device Faults

Context

Connection status between a TRILL device and its neighboring devices can be monitored by exchanging Hello packets at intervals. A neighboring device is considered Down if the TRILL device does not receive any Hello packets from the neighboring device within the specified period (called the holding time). The device fault then triggers routing table recalculation, and the TRILL network reconverges. To speed up fault detection, use the following methods to accelerate the speed of detecting TRILL neighboring device faults:

Procedure

  • Setting an interval at which Hello packets are sent
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run trill timer hello hello-interval

      The interval for sending Hello packets is configured on the interface.

      By default, Hello packets are sent on the interface every 10 seconds.

    4. Run commit

      The configuration is committed.

  • Setting the holding time for TRILL neighboring devices
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run trill timer holding-multiplier number

      The multiplier between the expiration time of TRILL neighboring devices and the Hello packet sending interval is configured to determine the holding time for the TRILL neighboring devices.

      By default, a TRILL neighboring device is considered Down after failing to receive three Hello packets.

    4. Run commit

      The configuration is committed.

Adjusting SNP and LSP Attributes

Context

When the network status changes, LSPs are sent to advertise these changes on TRILL networks, and SNPs are responsible for synchronizing the LSDB of each device on the network. You can adjust SNP and LSP attributes based on the actual network status to improve the network performance and reliability. The following table describes the SNP and LSP attributes.
Table 1-5 SNP and LSP attributes

Attribute

Description

Default Setting

Interval for sending CSNPs

All devices on a TRILL network periodically send CSNPs through the DRB to synchronize the LSDBs. After the interval for sending CSNPs is adjusted based on the network scale, the LSDBs can be synchronized in real time and CSNPs are not frequently sent to occupy a large amount of the device memory.

10 seconds

LSP intelligent timer

In the TRILL network, if the local routing information changes, the device generates a new LSP to notify this change. Many new LSPs caused by frequent routing information changes will occupy a large number of system resources. The LSP intelligent timer can automatically adjust the delay based on the change frequency of routing information, which accelerates the network convergence speed and does not affect the system performance.

The intelligent timer provides three parameters. The parameter functions are as follows:
  • If only max-interval is configured, the intelligent timer functions as an ordinary one-time triggering timer and TRILL generates LSPs at a specified interval.

  • If max-interval and init-interval are configured, init-interval determines the delay in LSP generation for the first time, and from the second time on, max-interval determines the delay in LSP generation. After the delay remains at the value specified by max-interval for three times or the TRILL process is restarted, the delay restores to the value specified by init-interval.

  • If max-interval, init-interval, and incr-interval are configured, init-interval determines the delay in LSP generation for the first time, and incr-interval determines the delay in generating the LSPs with the same ID for the second time. From the third time on, the delay in generating an LSP increases twice every time until the delay reaches the value specified by max-interval. After the delay remains at the value specified by max-interval for three times or the TRILL process is restarted, the delay restores to the value specified by init-interval.

  • max-interval: 2 seconds
  • init-interval: 0 milliseconds
  • incr-interval: 0 milliseconds

LSP refresh interval

When the network status changes, LSPs are sent to advertise these changes to other devices on the network. Based on the network scale, a long LSP refresh interval may delay the real-time change synchronization and a short interval may result in frequent LSP update and much memory occupation. After the LSP refresh interval is adjusted, the network can converge in real time and a proper number of LSPs are sent.

By default, the LSP refresh interval is 900s, and the maximum lifetime of an LSP is 1200s. Ensure that the LSP refresh interval is more than 300s shorter than the maximum LSP lifetime. This allows new LSPs to reach all routers in an area before existing LSPs expire.

Maximum LSP lifetime

The maximum LSP lifetime determines how long LSPs exist on the device. An LSP is deleted if the device does not receive the updated one after the maximum LSP lifetime expires. If the maximum LSP lifetime is set to an excessively short period, the device may discard the original LSPs when receiving new ones, which results in the failure of LSDB synchronization on the network. If the maximum LSP lifetime is set to an excessively long period, the LSDB cannot be updated in real time when the network status changes, which decreases the network convergence speed.

1200 seconds

LSP remaining lifetime

The LSP remaining lifetime specifies the remaining validity time of an LSP. When the remaining lifetime of an LSP is 0, this LSP is deleted. If the LSP remaining lifetime is incorrect, LSPs will be too fast or too slow to be aged out. As a result, routes cannot be converged. To address this issue, manually set the LSP remaining lifetime.

By default, the TRILL LSP Remaining Lifetime value is the maximum LSP age.

Minimum interval at which LSPs are sent

When there are a large number of LSPs on the device, multiple LSPs are sent each time at a specified interval. This attribute defines the minimum interval at which LSPs are sent. If the minimum interval is set to an excessively short period or there are too many LSPs to be sent each time, the network resources are occupied. Therefore, the device must be configured to send all LSPs equally based on the actual network load capability.

50 milliseconds

Interval at which LSPs are retransmitted over a P2P link

On a P2P network, the devices on the two ends of the link synchronize the LSDBs through LSP flooding. The device on one end sends an LSP; the device on the other end receives the LSP and replies with a PSNP. If the sending device does not receive the PSNP from the peer within a certain period, it resends the LSP.

If the retransmission interval is set to an excessively short period, LSPs are retransmitted improperly, which results in high CPU, memory and bandwidth usage.

5 seconds

Procedure

  • Setting an interval at which CSNPs are sent
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run trill timer csnp csnp-interval

      The interval for sending CSNPs is set on the interface.

    4. Run commit

      The configuration is committed.

  • Configuring the LSP intelligent timer
    1. Run system-view

      The system view is displayed.

    2. Run trill

      The TRILL view is displayed.

    3. Run timer lsp-generation max-interval [ init-interval [ incr-interval ] ]

      The intelligent timer used for generating LSPs is configured.

    4. Run commit

      The configuration is committed.

  • Setting the LSP refresh interval
    1. Run system-view

      The system view is displayed.

    2. Run trill

      The TRILL view is displayed.

    3. Run timer lsp-refresh refresh-time

      The LSP refresh interval is set.

    4. Run commit

      The configuration is committed.

  • Setting the maximum LSP lifetime
    1. Run system-view

      The system view is displayed.

    2. Run trill

      The TRILL view is displayed.

    3. Run timer lsp-max-age age-time

      The maximum lifetime is set for LSPs.

    4. Run commit

      The configuration is committed.

  • Setting the LSP remaining lifetime
    1. Run system-view

      The system view is displayed.

    2. Run trill

      The TRILL view is displayed.

    3. (Optional) Run lsp-remaining-lifetime refresh disable age-time

      TRILL LSP remaining lifetime adjustment is disabled.

      By default, automatic TRILL LSP remaining lifetime adjustment is enabled.

    4. Run lsp-remaining-lifetime refresh timer { refreshvalue | lsp-max-age }

      The LSP remaining lifetime is set.

    5. Run commit

      The configuration is committed.

  • Setting the minimum interval at which LSPs are sent
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run trill timer lsp-throttle throttleinterval [ count countnumber ]

      The minimum interval for sending LSPs is set.

    4. Run commit

      The configuration is committed.

  • Setting an interval at which LSPs are retransmitted over a P2P link
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run trill timer lsp-retransmit retransmit-interval

      The interval for retransmitting LSPs over a P2P link is set.

    4. Run commit

      The configuration is committed.

Setting the SPF Calculation Interval

Context

When the network status changes, TRILL calculates routes using the SPF algorithm to ensure accuracy. However, when the network status is unstable, frequent SPF calculation consumes excessive CPU resources, affecting services.

To solve this problem, configure an intelligent timer to control the SPF calculation interval. That is, set the SPF calculation interval to a small value to speed up TRILL route convergence, and set the interval to a large value after the TRILL network becomes stable.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run trill

    The TRILL view is displayed.

  3. Run timer spf max-interval [ init-interval [ incr-interval ] ]

    The SPF intelligent timer is configured.

    Specify the parameters based on the following rules:
    • If you only specify max-interval, the intelligent timer functions as an ordinary timer, and TRILL performs SPF calculation after routes are converged and max-interval expires.

    • If you specify both max-interval and init-interval, init-interval determines the delay in SPF calculation for the first time, and from the second time on, max-interval determines the delay in SPF calculation. After the delay remains at the value specified by max-interval for three times or the TRILL process is restarted, the delay restores to the value specified by init-interval.

    • If you specify max-interval, init-interval, and incr-interval, init-interval determines the delay in SPF calculation for the first time, and incr-interval determines the delay in SPF calculation for the second time. From the third time on, the delay in SPF calculation increases twice every time until the delay reaches the value specified by max-interval. After the delay remains at the value specified by max-interval for three times or the TRILL process is restarted, the delay restores to the value specified by init-interval.

  4. Run commit

    The configuration is committed.

Verifying the TRILL Network Convergence Speed Configuration

Procedure

  • Run the display trill interface verbose command to view detailed information about TRILL interfaces.
Translation
Download
Updated: 2019-05-08

Document ID: EDOC1100004349

Views: 31845

Downloads: 120

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