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).
Licensing Requirements and Limitations for IPv4 Multicast VPN Configuration in Rosen Mode

Licensing Requirements and Limitations for IPv4 Multicast VPN Configuration in Rosen Mode

Licensing Requirements

This feature is a basic feature and is not under license control.

Restrictions and Guidelines

Restrictions

Guidelines

Impact

An IPv4 multicast VPN (Rosen) extranet does not support VLANIF interfaces, BDIF interfaces, QinQ termination sub-interfaces, dot1q termination sub-interfaces, or BAS interfaces.

None

The IPv4 multicast VPN (Rosen) extranet fails to forward traffic.

In IPv4 multicast VPN (Rosen) scenarios, public network packets do not support fragmentation or reassembly.

Properly plan path MTUs, preventing packet fragmentation.

In IPv4 multicast VPN (Rosen) scenarios, fragmented packets are discarded.

In a rosen MVPN extranet scenario, VPN instances cannot import routes of one another for multicast traffic on a PE on the multicast source side. When the receiver VPN has an Mtunnel outbound interface, the Mtunnel information of the receiver VPN cannot be sent to the source VPN.

Configure multicast traffic to cross between VPN instances on the PE at the multicast receiver side.

If local cross is not performed on the PE at the multicast receiver side, multicast traffic will be interrupted.

In a rosen MVPN scenario, BGP does not support the connector attribute. When the receiver PE performs RPF route selection in a VPN instance, the connector cannot be used as an RPF neighbor.

None

If a remote PE advertises VPNv4 routes carrying the connector attribute and the next hop in the VPNv4 route is different from the connector attribute, multicast traffic cannot be forwarded.

In inter-AS Rosen MVPN Option B and Option C scenarios, Ps and ASBRs do not support PIM Join/Prune messages carrying vector information.

None

If the restrictions are met, multicast traffic will be interrupted.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055017

Views: 44195

Downloads: 97

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