Feature |
Feature Requirements |
Series |
Models |
|---|---|---|---|
Rosen MVPN Constraints |
IP multicast-IPv4 multicast VPN (Rosen) public network packets do not support fragmentation and reassembly. As a result, fragmented IP multicast-IPv4 multicast VPN (Rosen) packets are discarded. You are advised to properly plan the path MTU to prevent packet fragmentation. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Rosen MVPN Constraints |
Port extension does not support the distributed multicast VPN mode. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Rosen MVPN Constraints |
In a remote cross scenario of multicast VPN extranet, receiver VPNs cannot be configured on the PE where the source VPN resides. Therefore, the source VPN cannot be crossed to different VPNs. You are advised to configure a source VPN instance on the receiver PE to implement remote cross. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Rosen MVPN Constraints |
In inter-AS Rosen MVPN Option B and Option C scenarios, Ps and ASBRs do not support PIM Join/Prune messages carrying vector information. If the restrictions are met, multicast traffic will be interrupted. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Rosen MVPN Constraints |
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. 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. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Rosen MVPN Constraints |
In a Rosen MVPN extranet scenario, multicast traffic cannot be locally leaked between different VPN instances on a multicast source-side PE. If a receiver VPN has an Mtunnel outbound interface, the Mtunnel of the receiver VPN cannot be delivered to the source VPN. If multicast traffic is not locally leaked on the PE connected to the multicast receiver, multicast traffic cannot be forwarded. It is recommended that you configure multicast traffic to be locally leaked between different VPN instances on the PE at the multicast receiver side. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |