Feature Requirements |
Series |
Models |
|---|---|---|
The interval at which the device sends Hello messages must be shorter than the neighbor holdtime. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The holdtime of Bootstrap messages sent from a BSR must be greater than the interval at which a C-BSR sends Bootstrap messages. Otherwise, BSR election is unstable. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The period during which the BSR keeps the Advertisement message from the C-RP must be longer than the interval for the C-RP to send Advertisement messages. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
To enable a device to communicate with a device that supports Auto-RP, enable the Auto-RP listening function. After this function is enabled, the device can receive Auto-RP announcement and discovery messages, resolve the source addresses of the messages, and perform RPF checks based on the source addresses. Currently, only IPv4 is supported. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
These two modes cannot be both configured on the same device in a PIM-SM domain. If Anycast-RP is implemented through PIM, you can also configure the device to advertise the source information obtained from MSDP peers in another domain to peers in the local domain. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If the source-specific multicast (SSM) model is used in PIM-SM scenarios, you do not need to deploy MSDP. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Ensure that the SSM group address ranges of all devices on the network are the same. Otherwise, faults may occur on the network. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In IPv4 multicast VPN (Rosen) scenarios, deploy PIM FRR on both source-end and receive-end devices. Otherwise, protection cannot be implemented. If PIM FRR is deployed on the receive-end device but not on the source-end device, no public-network protection forwarding paths are available for receive-end VPN protocol packets, causing VPN protocol forwarding failures if the public-network forwarding path fails. VPN protocol packet forwarding can recover only after route convergence is complete on the public network. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
PIM FRR does not support low-rate multicast traffic or multicast traffic with constant changing rates (no data packets exist in the configured detection period, which is 20 ms by default). In scenarios with low-rate multicast traffic or multicast traffic with constant changing rates, PIM FRR frequently performs switchovers mistakenly, resulting in packet loss. PIM FRR supports source-and group address-based deployment. Do not deploy PIM FRR for low-rate multicast services. Adjust the default detection period to adapt to low-rate multicast services and reduce the switchover time. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In Rosen MVPN scenarios, if PIM FRR is deployed on the public network, low-speed traffic cannot be filtered out based on VPN (S, G) entries. In this case, you can configure a switching threshold to confine low-speed services to Share-Group and then use an ACL to filter out traffic in Share-Group. Deploying PIM FRR on VPNs cannot solve the co-routing problem of the public network. PIM FRR deployed on the public network cannot filter out the low-speed traffic on a VPN. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
A multicast inbound interface supports PIM FRR deployment only if the interface is a Layer 3 Ethernet main interface, Ethernet sub-interface, Layer 3 Eth-Trunk interface, Eth-Trunk sub-interface,VLANIF interface or BDIF interface. If both or either of the master and slave inbound interfaces do not support PIM FRR, PIM FRR does not take effect. In this case, traffic is forwarded in common multicast mode, and protection cannot be implemented. Traffic switchovers depend on protocol hard convergence, and rapid switchovers are not supported. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Source cloning-based PIM FRR cannot protect multicast traffic whose rate is lower than 200 pps. You must configure an ACL to filter out such traffic. |
NetEngine 8000 F |
NetEngine 8000 F1A |
When PIM FRR is deployed on a ring network, PIM FRR must be configured on the intermediate devices of PIM FRR devices. In addition, the intermediate devices cannot be connected to non-Huawei devices. Otherwise, protection cannot be implemented. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The device where source cloning-based PIM FRR is deployed must have at least two paths to protect traffic. If there is only one path, PIM FRR does not work. |
NetEngine 8000 F |
NetEngine 8000 F1A |
If the inbound interface for source cloning-based PIM FRR traffic is a trunk interface, a trunk member interface change may trigger PIM FRR, causing a link switchover. Multicast traffic is switched or lost. |
NetEngine 8000 F |
NetEngine 8000 F1A |
Source cloning-based PIM FRR occupies one more copy of bandwidth than PIM FRR in another mode. |
NetEngine 8000 F |
NetEngine 8000 F1A |
In a scenario where a second fault occurs before the first fault is completely rectified (traffic interruption is also a fault), source cloning-based PIM FRR does not support fast switchover. Both primary and secondary links fail: 1, If strict explicit paths are used, protocol convergence is unavailable. As a result, traffic is interrupted. 2, If loose explicit paths are configured and there are normal links that meet the requirements of loose explicit path planning once primary and secondary links are faulty, services are restored based on protocol convergence, and fast switchover is not supported. |
NetEngine 8000 F |
NetEngine 8000 F1A |
Source cloning-based PIM FRR supports MVPN in Rosen mode and requires integrated MVPN service boards. In distributed mode, if the link connecting to the inbound interface of multicast traffic fails, the inbound interface is reselected. During the inbound interface reselection, packets are discarded. |
NetEngine 8000 F |
NetEngine 8000 F1A |
In a multicast scenario with equal-cost links or primary and secondary links, PIM is enabled only for the active link in use, but not enabled on the other links. After a link switchover occurs due to a configuration, route, or link change, multicast services will be interrupted, because PIM is not enabled on the newly selected link. If multicast services need to be transmitted along optimal routes of non-equal-cost links, PIM also needs to be enabled. You are recommended to enable PIM in the views of the interfaces on which PIM is disabled. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
FRR is deployed on the public network in a Rosen MVPN scenario. The inbound interface of the backup link on a leaf node on the public network is a trunk interface. If the primary link on the public network fails, some traffic on the trunk interface of the leaf node may fail to be forwarded. You are advised to perform the following configurations: 1. Configure a non-trunk interface as the inbound interface of the backup link on the public network. 2. Connect to the previous device of the leaf node. Rosen MVPN and public network MoFRR are configured on a board in NGSF mode. The outbound interface of a P node is a trunk interface, on which software-based interface selection is configured so that traffic on the trunk interface of the leaf node is not balanced based on the VPN. If load balancing is required, you can configure a switch group to perform load balancing based on the public network. In this manner, load balancing based on the VPN is implemented. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Port extension does not support PIM over GRE. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
External communication interfaces for port extension do not support multicast shaping. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In a multicast scenario with equal-cost links or primary and secondary links, PIM is enabled only for the active link in use, but not enabled on the other links. After a link switchover occurs due to a configuration, route, or link change, multicast services will be interrupted, because PIM is not enabled on the newly selected link. If multicast services need to be transmitted along optimal routes of non-equal-cost links, PIM also needs to be enabled. You are advised to enable PIM in the views of the interfaces on which PIM is disabled. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Multicast cannot be configured on untagged sub-interfaces. Before switching a sub-interface to an untagged sub-interface, delete the multicast configuration on the sub-interface. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When a virtual device is created, and configurations for multicast to invoke an ACL policy exist in the service VS, you cannot delete service VS directly in Admin-VS. An error message is displayed when a service VS is directly deleted in Admin-VS and the ACL configuration cannot be deleted in the service VS, without deleting the configurations for multicast to invoke an ACL policy one by one from the service VS. When deleting a service VS in the Admin-VS, you need to delete the configurations for multicast to invoke an ACL policy one by one from the service VS. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After the device is restarted, if the BFD session or BFD neighbor session is in Admin down state, the PIM status is not affected. When the BFD session is renegotiated, the PIM status is not affected either. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |