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 - Virtual Access 01

This is ME60 V800R010C10SPC500 Configuration Guide - Virtual 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 Multicast AP Replication

Configuring Multicast AP Replication

This section describes how to configure multicast AP replication. After multicast AP replication is configured on a master, APs replicate multicast traffic for receivers. This decreases the load on the links between the master and APs.

Background

In a virtual access scenario, a master replicates Layer 3 multicast traffic and sends a copy to each receiver. This increases the load on the links between the master and APs. To resolve this issue, enable multicast AP replication on the master. After multicast AP replication is enabled, virtual access P2MP (vaP2MP) tunnels are established between the master and APs, as shown in Figure 2-19, after multicast AP replication is enabled, virtual access P2MP (vaP2MP) tunnels are established between the master and APs. Multicast traffic is imported into the vaP2MP tunnels on the master, exported from the vaP2MP tunnels on the APs, and replicated based only on tunnel paths in the vaP2MP tunnels. After reaching the APs, multicast traffic is locally replicated for receivers. In this situation, the master does not need to replicate multiple copies of multicast traffic for each receiver, and therefore the load on the links between the master and APs is decreased.

NOTE:
  1. After multicast AP replication is configured, multicast traffic is sent to APs over the vaP2MP tunnel between the master and APs, without querying the data entries of the PWIF interfaces. Therefore, external communication interface statistics on the master do not include multicast traffic statistics.
  2. When a switching is performed between multicast AP replication and non-multicast AP replication, forwarding entries must be updated, causing short-time packet loss.
  3. This configuration process is supported only on the Admin-VS.
Figure 2-19 Multicast AP replication
NOTE:

Multicast AP replication supports the following types of interfaces: PWIF Ethernet interfaces, PWIF Ethernet sub-interfaces, PWIF QinQ sub-interfaces, PWIF Dot1q VLAN tag termination, remote-trunk interfaces, remote-trunk sub-interfaces, remote-trunk QinQ sub-interfaces, and remote-trunk Dot1q VLAN tag termination.

Multicast AP replication supports Layer 3 multicast but does not support Layer 2 multicast in IPv4 scenarios.

Pre-configuration Tasks

Before configuring multicast AP replication, deploy Layer 3 multicast.

Procedure

  1. Run system-view

    The system view is displayed.

  2. (Optional) Run ip vpn-instance vpn-instance-name

    The VPN instance view is displayed.

  3. (Optional) Run ipv4-family

    The IPv4 address family is enabled for the VPN instance, and the VPN instance IPv4 address family view is displayed.

  4. Run multicast off-load p2mp [ wtr wait-time ]

    Multicast AP replication is enabled.

    When an AP is dual-homed to a primary and a secondary master, enable multicast AP replication on both the primary and secondary masters to establish the primary and backup vaP2MP tunnels. To implement 1+1 protection, deploy IGMP multicast dual-device hot backup. After the deployment, multicast traffic is imported into both the primary and secondary masters and is sent to an AP through the primary and backup vaP2MP tunnels. In normal cases, the AP accepts multicast traffic only from the primary vaP2MP tunnel. If the primary vaP2MP tunnel fails, the AP immediately accepts multicast traffic from the backup vaP2MP tunnel. After the primary vaP2MP tunnel recovers, the AP again accepts multicast traffic from the primary vaP2MP tunnel only after a period of time elapses. You can use the wtr wait-time parameter to change this time.

  5. (Optional) Adjust BFD for vaP2MP session parameters.
    1. Run virtual-access

      The virtual access view is displayed.

    2. Run bfd va-tunnel p2mp { min-tx-interval tx-interval | min-rx-interval rx-interval | detect-multiplier multiplier } *

      BFD for vaP2MP session parameters are adjusted.

    After vaP2MP tunnels are established, BFD for vaP2MP sessions are automatically established between the root and leaf nodes to quickly detect faults on the vaP2MP tunnels. BFD for vaP2MP session parameters include the minimum interval at which BFD for vaP2MP packets are sent, the minimum interval at which BFD for vaP2MP packets are received, and the local BFD for vaP2MP detection multiplier. Local BFD for vaP2MP detection time = Remotely configured local detection multiplier x Max {Locally configured minimum interval at which BFD for vaP2MP packets are received, Remotely configured minimum interval at which BFD for vaP2MP packets are sent}If the local end does not receive BFD for vaP2MP packets from the remote end within the local BFD for vaP2MP detection time, the local end considers the vaP2MP tunnels faulty. You can adjust BFD for vaP2MP session parameters to control BFD's sensitivity to faults. If high network reliability is required, adjust parameters to decrease the local BFD for vaP2MP detection time. If moderate network reliability is required, adjust parameters to increase the local BFD for vaP2MP detection time.

  6. Run commit

    The configuration is committed.

Checking the Configurations

After configuring multicast AP replication, check the configurations.

  • Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] va-tunnel p2mp command on a master to check information about multicast vaTunnels.

  • Run the display virtual-access va-tunnel p2mp [ tunnel-id tunnel-id ] command on a master to check vaP2MP tunnel information.

  • Run the display virtual-access va-lsp p2mp [ tunnel-id tunnel-id [ lsp-id lsp-id | s2l-destination s2l-destination-address ] * ] command on a master to check vaP2MP tunnels' LSP information.

  • Run the stelnet command on a master to log in to an AP. Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] forwarding-table [ group-address [ mask { group-mask | group-mask-length } ] | source-address [ mask { source-mask | source-mask-length } ] | incoming-interface { interface-type interface-number | register } | outgoing-interface { include | exclude | match } { interface-type interface-number | register | none } | statistics | [ verbose ] | slot slot-number ] * command to check the local multicast forwarding entries on the AP.

Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059451

Views: 3792

Downloads: 18

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