Whether to enable monitoring of active data flows for BIDIR-PIM groups. Enabling this is a prerequisite for the following. - Static RP load-splitting for BIDIR group ranges, as configured via pimStaticRPMultiPriority. - Load-splitting for BSR-learnt BIDIR RPs, as configured via the 'bidir' flag of pimTmEntBsrRPMultipathMode. - Next-hop load-splitting for BIDIR group ranges for data flows from the source to the RP, as configured via pimTmEntMultipathMode. All of the above perform load-splitting via a per-group algorithm specified by pimTmEntRPMultipathAlgorithm. This might improve bandwidth utilization in the network (without the configuration overhead of achieving it via defining different group ranges for different RPs), but it removes two of the benefits of BIDIR, as follows. - A per-group algorithm prevents the use of (*,G-prefix) forwarding rules. (*,G-prefix) forwarding rules help to reduce the number of (*,G) multicast forwarding rules needed on each node. - A per-group algorithm requires RP selection to be triggered when a new data flow occurs, rather than in advance. This adds complexity to the data plane, and introduces a setup delay when programming a (*,G) forwarding rule for a new data flow. If this configuration is changed whilst the entity is active, the entity will be deactivated and restarted with the new configuration value.