Inline active flow monitoring: Multiple BGP next hops

We have added support for reporting an accurate BGP next-hop address for traffic load-balanced over multiple BGP peers in the ingress direction. Previously, we reported the first address in a list of BGP next hops. To contain this accurate BGP next-hop address, we use the IPv4 BGP Nexthop Address (IE 18) field in the IPv4 and MPLS-IPv4 templates and the IPv6 BGP Nexthop Address (IE 63) field in the IPv6 and MPLS-IPv6 templates, for both the IPFIX and the version 9 formats. 

To configure this feature, include the multi-bgp-path statement at the [edit services flow-monitoring (version-ipfix | version9) template] hierarchy level. For IPv6 and MPLS-IPv6 flows, you also need to configure the ipv6-extended-attrib statement at the [edit chassis fpc slot-number inline-services flow-table-size] hierarchy level. When this feature is enabled, the fragmentIdentification (IE 54) field reports a value of 0.