Licensing Requirements and Limitations for IPv4 User-Side Multicast
Licensing Requirements
This feature is a basic feature and is not under license control.
Restrictions and Guidelines
Restrictions |
Guidelines |
Impact |
|---|---|---|
Static multicast supports RUI. Only replication by session and by vlan are supported. Other replication modes, if configured, do not take effect. |
In RUI scenarios, run the multicast copy by-session command in the BAS interface view. Other replication modes are not supported. |
Only replication by session can take effect. |
Static multicast virtual scheduling supports Layer 2 common, PPPoE, and IPoE users, but does not support Layer 2 leased line users. |
None |
Multicast virtual scheduling does not take effect. |
Static multicast and dynamic multicast share multicast program and bandwidth resources. If the multicast program or bandwidth resource limit is reached, dynamic multicast is controlled. That is, static multicast users preempt the resources of dynamic multicast users. As a result, a user may fail to dynamically order a program after the user leaves the multicast group program and the applied resource is released. This is because the released resource may be occupied by a static multicast user. |
None |
A multicast program fails to be ordered. |
In VE interface access scenarios, the following multicast functions are not supported:
|
None |
The multicast functions that are not supported do not take effect. |
User-side multicast CAC does not support:
|
Deploy user-side multicast CAC in scenarios that support this feature. |
User-side multicast CAC does not take effect. |
User-side multicast BAS interfaces support Layer 2 common users, Layer 2 leased line users, but do not support support Layer 3 common users, Layer 3 leased line users, or L2VPN leased line users. |
None |
Layer 3 common users, Layer 3 leased line users, and L2VPN leased line users cannot join multicast groups. |
User-side multicast does not support global VE interfaces. |
None |
User-side multicast is not supported. |
For VPN users, IGMP configurations need to be performed in main interface views. IGMP configurations in sub-interface views do not take effect for VPN users. |
None |
IGMP configurations in sub-interface views do not take effect for VPN users. |
In the current version, the private MIB of the multicast feature supports only traps of public network instances, but not traps of VPN instances. |
None |
If both public network instances and VPN instances exist, only traps in the public network instance can be reported. |
In CU separation scenarios, the User-VLAN-related commands can be delivered only from the vBRAS-CP to the vBRAS-UP. |
Deliver the related command configurations from the vBRAS-CP. |
User-VLAN-related commands cannot be directly executed on the vBRAS-UP. |
In CU separation scenarios, the multicast-related commands can be delivered only from the vBRAS-CP to the vBRAS-UP. |
Deliver the related command configurations from the vBRAS-CP. |
Multicast-related commands cannot be directly executed on the vBRAS-UP. |
Previous
