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 V800R010C10SPC500 Configuration Guide - IP Multicast 01

This is NE40E V800R010C10SPC500 Configuration Guide - IP Multicast
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).
(Optional) Configuring Switching Between I-PMSI and S-PMSI Tunnels

(Optional) Configuring Switching Between I-PMSI and S-PMSI Tunnels

Context

An NG MVPN uses the I-PMSI tunnel to send multicast data to receivers. The I-PMSI tunnel connects to all PEs on the MVPN and sends multicast data to these PEs regardless of whether these PEs have receivers. If some PEs do not have receivers, this implementation will cause redundant traffic, wasting bandwidth resources and increasing PEs' burdens. S-PMSI tunnels solve this problem by sending multicast data only to PEs interested in the data.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ip vpn-instance vpn-instance-name

    The VPN instance view is displayed.

  3. Run ipv4-family

    The VPN instance IPv4 address family view is displayed.

  4. Run multicast routing-enable

    Multicast routing is enabled.

  5. Run mvpn

    The VPN instance IPv4 address family MVPN view is displayed.

  6. Run spmsi-tunnel

    The MVPN S-PMSI view is displayed.

  7. Run group group-address { group-mask | group-mask-length } [ source source-address { source-mask | source-mask-length } ] [ threshold threshold-value ] { mldp | rsvp-te p2mp-template p2mp-te-template-name } [ limit number ]

    The address pool range and criteria for switching between I-PMSI and S-PMSI tunnels are configured.

  8. (Optional) Run switch-delay switch-delay

    A delay for switching from the I-PMSI tunnel to an S-PMSI tunnel is configured.

    The sender PE starts a switch-delay timer before switching multicast data from the I-PMSI tunnel to an S-PMSI tunnel. This step configures the timer value. The sender PE continues to detect the multicast data forwarding rate before the switch-delay timer expires. If the forwarding rate is consistently above the specified switching threshold throughout the timer lifecycle, the sender PE switches multicast data from the I-PMSI tunnel to an S-PMSI tunnel. If the forwarding rate is consistently below the specified switching threshold throughout the timer lifecycle, the sender PE still uses the I-PMSI tunnel to send multicast data.

  9. (Optional) Run holddown-time interval

    A hold time for switching from an S-PMSI tunnel to the I-PMSI tunnel is configured.

    In some cases, the multicast data forwarding rate may fluctuate around the specified switching threshold. To prevent multicast data from being frequently switched between the I-PMSI and S-PMSI tunnels, the sender PE does not immediately switch data back to the I-PMSI tunnel when detecting that the forwarding rate is below the specified switching threshold. Instead, the sender PE starts a switchback hold timer. This step configures the timer value. Before the timer expires, the sender PE continues to detect the multicast data forwarding rate. If the forwarding rate is consistently below the specified switching threshold throughout the timer lifecycle, the sender PE switches multicast data back to the I-PMSI tunnel. Otherwise, the sender PE still uses the S-PMSI tunnel to send multicast data.

  10. (Optional) Run tunnel-detect-delay tunnel-detect-delay

    A delay for checking tunnel status when the bearer tunnel of VPN instance multicast data changes is configured. The tunnel-detect-delay command needs to be run only on the receiver PE.

    In RSVP-TE P2MP tunnel dual-root 1+1 protection scenarios, multicast data may be switched from the primary I-PMSI tunnel to the backup I-PMSI tunnel if the S-PMSI tunnel is not ready during data switching. To solve this problem, start a tunnel status check delay timer on leaf PEs:
    • Before the timer expires, leaf PEs delete tunnel protection groups to skip the status check of the primary I-PMSI or S-PMSI tunnel.
    • After the timer expires, leaf PEs start to check the primary I-PMSI or S-PMSI tunnel status again.

  11. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055017

Views: 39846

Downloads: 97

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