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).
Configuring Dual-Root 1+1 Protection

Configuring Dual-Root 1+1 Protection

Configuring dual-root 1+1 protection accelerates multicast service convergence and improves reliability in case a sender PE on a P2MP tunnel fails.

Usage Scenario

In an NG MVPN scenario, if a sender PE on a P2MP tunnel fails, the VPN multicast service will be interrupted. The network can rely only on unicast route convergence for recovery. However, unicast route convergence takes a long time and may fail to meet the high reliability requirements of some multicast services. To resolve this problem, configure dual-root 1+1 protection. On the network shown in Figure 9-15, a primary P2MP tunnel is established with PE1 as the root node, and a backup P2MP tunnel is established with PE2 as the root node. When the links are working properly, multicast traffic is forwarded through both the primary and backup tunnels bidirectionally. The leaf node PE3 selects the multicast traffic received from the primary tunnel and discards the multicast traffic received from the backup tunnel. If PE1 or a public network link fails, PE3 can use BFD for P2MP TE/mLDP or multicast traffic detection to quickly detect the P2MP tunnel fault and choose to accept the multicast traffic received from the backup tunnel. This accelerates multicast service convergence and improves reliability.
Figure 9-15 Configuring dual-root 1+1 protection

Pre-configuration Tasks

Before configuring BFD for P2MP TE/mLDP based dual-root 1+1 protection, complete the following tasks:
  • RSVP-TE P2MP Tunnel:

    • Configure NG MVPN.

    • Configure BFD for P2MP TE on the root nodes.

    • Configure VPN FRR on the leaf nodes.

    • Globally enable BFD on the root and leaf nodes.

  • mLDP P2MP Tunnel:

    • Configure NG MVPN.

    • Configure BFD for mLDP P2MP on the root and leaf nodes.

    • Configure VPN FRR on the leaf nodes.

    • Globally enable BFD on the root and leaf nodes.

Before configuring multicast traffic detection based dual-root 1+1 protection, complete the following tasks:
  • Configure NG MVPN.

  • Configure VPN FRR on the leaf nodes.

Perform the following steps on the leaf nodes:

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 mvpnThe VPN instance IPv4 address family MVPN view is displayed.

  5. Run c-multicast frr

    C-multicast FRR is enabled. C-multicast FRR allows VPN multicast traffic to be imported to the primary and backup tunnels.

  6. (Only for multicast traffic detection based C-multicast FRR) Run c-multicast frr flow-detection-based

    Multicast traffic detection based C-multicast FRR is enabled.

  7. (Optional) Run multicast wtrwtr-time

    A switchback wait time is set for multicast VPN FRR in NG MVPN 1+1 scenarios.

  8. Run commit

    The configuration is committed.

Checking the Configurations

After configuring dual-root 1+1 protection, check the configurations.

Run the display pim [ vpn-instance vpn-instance-name | all-instance ] routing-table [ group-address [ mask { group-mask-length | group-mask } ] | source-address [ mask { source-mask-length | source-mask } ] | incoming-interface { interface-type interface-number | register | through-bgp } | outgoing-interface { include | exclude | match } { interface-type interface-number | register | none | pseudo } | mode { ssm | sm } | flags flag-value | fsm ] * [ outgoing-interface-number [ number ] ] command to check information about the PIM routing table.

# Run the display pim [ vpn-instance vpn-instance-name | all-instance ] routing-table command. The command output shows backup PIM entries in the PIM routing table.

<HUAWEI> display pim vpn-instance VPNA routing-table
 VPN-Instance: VPNA
 Total 0 (*, G) entry; 1 (S, G) entry

 (10.1.3.2, 225.1.1.1)
     RP: NULL
     Protocol: pim-sm, Flag: SPT ACT
     UpTime: 03:12:27
     Upstream interface: through-BGP
         Upstream neighbor: 2.2.2.2
         RPF prime neighbor: 2.2.2.2
         Backup Upstream neighbor: 3.3.3.3
         Backup RPF prime neighbor: 3.3.3.3
     Downstream interface(s) information:
     Total number of downstreams: 1
        1: GigabitEthernet1/0/0
             Protocol: pim-sm, UpTime: 03:12:27, Expires: 00:03:05
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055017

Views: 39425

Downloads: 97

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