The following restrictions apply to version 9 templates:
You can export only one version 9 template at a time.
You can sample packets from only one protocol family (inet or mpls) at a time.
You cannot apply the two different types of flow aggregation
configuration (cflowd version 5/8 and flow aggregation version 9)
at the same time.
Flow export based on an mpls-ipv4 template assumes
that the IPv4 header follows the MPLS header. In the case of Layer
2 VPNs, the packet on the provider router (P router) would look like
this:
MPLS | Layer 2 Header | IPv4
In this case, mpls-ipv4 flows
are not created on the PIC, because the IPv4 header does not directly
follow the MPLS header. Packets are dropped on the PIC and are accounted
as parser errors.
Outbound Routing Engine traffic is not sampled. A firewall
filter is applied as output on the egress interface, which samples
packets and exports the data. For transit traffic, egress sampling
works correctly. For internal traffic, the next hop is installed in
the Packet Forwarding Engine but sampled packets are not exported.
Flows are created on the monitoring PIC only after the
route record resynchronization operation is complete, which is 60
seconds after the PIC comes up. Any packets sent to the PIC would
be dropped until the synchronization process is complete.
