Feature Requirements |
Series |
Models |
|---|---|---|
IPv4 private network routes and IPv6 private network routes support multi-PE load balancing. Route information is missing in the data sampled. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In the case of upstream original flow sampling on a sub-interface, the system fails to collect the source VLAN ID of packets. Only the destination VLAN ID can be collected, and the source VLAN ID is fixed to 0. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In the case of MPLS tunnel forwarding, neither the upstream nor the downstream next-hop IP address information of the ingress PE can be collected. Instead, FEC next-hop information can be successfully collected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In tunnel forwarding scenarios, the inbound interface cannot be restored in downstream sampling on the P node. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Information about the outbound interface, VLAN, and next hop cannot be collected for discarded packets. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When outbound interface sampling is configured and the route of the source IP address is the default route, only main interface information can be collected during inbound interface sampling. The collected inbound interface information is incorrect. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When outbound interface sampling is configured and the route of the source IP address is a black-hole route, only main interface information can be collected during inbound interface sampling. The collected inbound interface information is incorrect. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When outbound interface sampling is configured and the route of the source IP address is a static specific route, the route of the source IP address is inconsistent with the actual inbound interface information. The collected inbound interface information is incorrect. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
During aging processing, the aging time error of multi-core boards is 10s at most. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In a P2MP&NG-MVPN scenario: 1. Upstream sampling does not support the collection of outbound interface, next hop, TopLabelType, and TopLabelIpAddress information. 2. Downstream sampling does not support the collection of next hop, TopLabelType, and TopLabelIpAddress information. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In downstream sampling on the multicast VPN root node, only the source main interface can be sampled, and sub-interfaces and other logical interfaces cannot be sampled. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In the case of VXLAN packet sampling, VXLAN packets that have not been decapsulated after being encapsulated can be sampled. However, user packets cannot be sampled before they enter a VXLAN tunnel. Next hop and outbound interface information fails to be sampled in this scenario. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When traffic loading balancing is configured, a maximum of 64 equal-cost routes can be sampled. If more than 64 equal-cost routes exist, only 64 routes of them can be sampled. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
1. In the case of IPv4 multicast packet sampling, the system cannot collect information about the outbound interface, next hop, and number of replication times. 2. The function to sample transparently transmitted packets is not supported. 3. In the case of multicast VPN downstream sampling, the system can collect information only about the source main interface, not about any sub-interface or other logical interface. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
SR-MPLS TE does not support downstream sampling on the ingress PE. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When MPLS packets are not sampled, only the packets in the sampling process can be sampled separately. If the VPN header of the original packet has been removed or a VPN header has been added to the original packet, the original packet cannot be sampled separately. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When an interface alternates between up and down, no data can be collected on the inbound interface. After the flow table ages and is reestablished, the problem is resolved. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If the NetStream feature needs to be configured on a board, but the board does not support sampling data processing, you can configure a centralized sampling board that supports centralized service processing to process data. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Packet VLAN information is not collected for L3 sub-interface sampling. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In the scenario where NetStream and CGN are configured together, the sampling direction is inbound, and the sampled packet type is original packet, when inbound interface traffic diversion, outbound interface traffic diversion, IPv4 route-based traffic diversion, or IPv6-based route traffic diversion is configured, destination VPN information, outbound interface information, and destination route information cannot be collected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When NetStream works with CGN and the sampling direction is outbound and the sampled packet type is original packet, the source VPN information of the IPv4 forward behavior cannot be collected in the scenario where inbound interface traffic diversion, outbound interface traffic diversion, IPv4 route traffic diversion, IPv6 route traffic diversion, or hairpin is configured, and inbound interface information and source route information cannot be collected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When NetStream and IPsec are configured together and the sampling direction is inbound, the destination VPN information, outbound interface information, and destination address routing information cannot be collected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When NetStream and IPsec are configured together and the sampling direction is outbound, the source VPN information, inbound interface information, and source address routing information cannot be collected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The mask sampled from SRv6 packets is affected in the following scenarios: 1, In an SRv6 BE tunnel scenario, the mask in sampled inner packets on a transit node is displayed as 0. 2, In an SRv6 TE Policy scenario, the sampled mask on a transit node is displayed as 0. 3, On the network side of a PE where an SRv6 BE/TE Policy is configured, the mask in sampled outer packets is displayed as 0. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In an L2VPN/EVPN L2VPN over SRv6 tunnel scenario, after inner packet sampling is enabled for IPv4 or IPv6 packets, outer packets are still sampled on transit nodes, affecting SRv6 sampling results. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
SRv6 sampling results are affected in the following scenarios: 1, In an L2VPN/EVPN L2VPN over SRv6 tunnel scenario, sampling is not supported in the network-side outbound direction of the ingress and egress. 2, In an L2VPN/EVPN L2VPN over SRv6 tunnel scenario, sampling is supported in the network-side inbound direction of the ingress and egress. The "ipv6 netstream srv6-aware inner-header" command fails to take effect after being run, and outer packets are still sampled. In addition, information about the outbound interface (displayed as Unknown), next hop (displayed as 0.0.0.0), BGP next hop (displayed as 0.0.0.0), BGP AS number (displayed as 0), and mask (displayed as 0) cannot be obtained. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In an L2VPN/EVPN L2VPN over SRv6 tunnel scenario where inbound interface sampling is configured on the AC interfaces of the ingress and egress, information about the outbound interface (displayed as Unknown), next hop (displayed as 0.0.0.0), BGP next hop (displayed as 0.0.0.0), BGP AS number (displayed as 0), and mask (displayed as 0) cannot be obtained. If outbound interface sampling is configured, information about the inbound interface (displayed as unknown), next hop (displayed as 0.0.0.0), BGP next hop (displayed as 0.0.0.0), BGP AS number (displayed as 0), and mask (displayed as 0) cannot be obtained. In this case, SRv6 sampling results are affected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In SRv6 scenarios, information about packets with more than two layers of IPv6+SRH headers and more than two layers of SRH headers after IPv6 header cannot be collected. A reference packet format is as follows: IPv6+SRH+IPv6+SRH+IPv6+SRH+PayLoad or IPv6+SRH+SRH+SRH+PayLoad In this case, SRv6 sampling results are affected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
SRv6 sampling results are affected in the following network slicing scenarios: 1, The basic interface and slice interface are different physical interfaces in a FlexE group, and outbound interface sampling is configured. When traffic enters through the slice interface, the inbound interface for sampling is restored to the main interface where the slice interface resides. 2, The basic interface is a physical main interface, and the slice interface is a channelized sub-interface. Outbound interface sampling is configured. When traffic enters through the slice interface, the inbound interface for sampling is restored to the basic interface. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In IP over SRv6 TE Policy scenarios (including L3EVPNv4/EVPNv6 over SRv6 TE flow group, L3VPNv4/L3VPNv6 over SRv6 TE flow group, L3VPNv4/L3VPNv6 over SRv6 TE Policy, EVPN L3VPNv4/L3VPNv6 over SRv6 TE Policy, IP over SRv6 TE Policy, and DSCP-to-SRv6 TE Policy scenarios), SRv6 sampling results are affected if inbound sampling (interface or flow sampling) on the ingress PE meets one of the following conditions: 1, The list has only one layer, and the first SID is the local End.X SID. 2, The first SID is a binding SID or local End SID. 3, Shortcut processing is performed on the SRv6 TE Policy/SRv6 TE flow group based on the first SID. 4, In L3VPNv4/L3VPNv6 over SRv6 BE scenarios, shortcut processing is performed on SRv6 TE Policies based on locator routes. DstIf is displayed as UnKnown, NextHop as 0.0.0.0, BGPNextHop as 0.0.0.0, and DstAs as 0. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In IP over SRv6 TE Policy scenarios (including L3EVPNv4/EVPNv6 over SRv6 TE flow group, L3VPNv4/L3VPNv6 over SRv6 TE flow group, L3VPNv4/L3VPNv6 over SRv6 TE Policy, EVPN L3VPNv4/L3VPNv6 over SRv6 TE Policy, IP over SRv6 TE Policy, and DSCP-to-SRv6 TE Policy scenarios), SRv6 sampling results are affected if outbound sampling (interface or flow sampling) on the ingress PE meets one of the following conditions: 1, The list has only one layer, and the first SID is the local End.X SID. 2, The first SID is a binding SID or local End SID. 3, Shortcut processing is performed on the SRv6 TE Policy/SRv6 TE flow group based on the first SID. 4, In L3VPNv4/L3VPNv6 over SRv6 BE scenarios, shortcut processing is performed on SRv6 TE Policies based on locator routes. The display of SrcIf is related to the "encapsulation source-address" command of SRv6: 1, If the configured source-address has a corresponding interface, SrcIf is displayed as the interface. 2, If the configured source-address does not have a corresponding interface, the interface displayed in the SrcIf field (may be any physical interface on the sampling board, NULL0, or UnKnown) is incorrect. BGPnexthop is displayed as :: and DstAs as 0. 3, If source-address is not configured, the interface displayed in the SrcIf field (may be any physical interface on the sampling board or UnKnown) is incorrect. BGPNextHop is displayed as :: and DstAs as 0. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In IP over SRv6 TE Policy scenarios (including L3EVPNv4/EVPNv6 over SRv6 TE flow group, L3VPNv4/L3VPNv6 over SRv6 TE flow group, L3VPNv4/L3VPNv6 over SRv6 TE Policy, EVPN L3VPNv4/L3VPNv6 over SRv6 TE Policy, IP over SRv6 TE Policy, and DSCP-to-SRv6 TE Policy scenarios), SRv6 sampling results are affected if outbound sampling (interface or flow sampling) on the ingress PE meets one of the following conditions: 1, The first-hop SID route is unreachable. 2, The standby link for a switchover is a TI-LFA link. 3, Switchover microloop avoidance takes effect. 4, Switchback microloop avoidance takes effect. 5, TE FRR is triggered. The display of SrcIf is related to the "encapsulation source-address" command of SRv6: 1, If the configured source-address has a corresponding interface, SrcIf is displayed as the interface. 2, If the configured source-address does not have a corresponding interface, the interface displayed in the SrcIf field (may be any physical interface on the sampling board, NULL0, or UnKnown) is incorrect. BGPNextHop is displayed as :: and DstAs as 0. 3, If source-address is not configured, the interface displayed in the SrcIf field (may be any physical interface on the sampling board or UnKnown) is incorrect. BGPNextHop is displayed as :: and DstAs as 0. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When service chains are configured in IP over SRv6 TE Policy scenarios (including L3EVPN4/EVPNv6 over SRv6 TE flow group, L3VPNv4/L3VPNv6 over SRv6 TE flow group, L3VPNv4/L3VPNv6 over SRv6 TE Policy, EVPN L3VPNv4/L3VPNv6 over SRv6 TE Policy, IP over SRv6 TE Policy, and DSCP-to-SRv6 TE Policy scenarios), SRv6 sampling results are affected in the following situation: When inbound interface sampling is performed on the SFF in the SFF -> SF scenario, the value of DstIf is displayed as UnKnown, and inaccurate values are displayed in the NextHop and BgpNextHop fields. When outbound interface sampling is configured on the SFF, the values of NextHop, BgpNextHop, and DstAs are inaccurate. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If the source route is unreachable, the inbound interface can only be restored to a physical main interface or a physical member interface of a trunk interface. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In an IP over SRv6 service chain scenario, SRv6 sampling results are affected in the following situation: In the SF -> SFF scenario, when inbound interface sampling is performed on the SFF for traffic from the SF, DstIf is displayed as UnKnown, and inaccurate values are displayed in the NextHop and BgpNextHop fields. When outbound interface sampling is performed on the SFF for traffic sent from the SF, the value displayed in the SrcIf field is inaccurate. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In IP over SRv6 TE Policy scenarios (including L3EVPNv4/EVPNv6 over SRv6 TE flow group, L3VPNv4/L3VPNv6 over SRv6 TE flow group, L3VPNv4/L3VPNv6 over SRv6 TE Policy, EVPN L3VPNv4/L3VPNv6 over SRv6 TE Policy, IP over SRv6 TE Policy, and DSCP-to-SRv6 TE Policy scenarios) where outbound interface sampling is performed for penultimate hop popping, when the actual outbound interface is different from the outbound interface specified in the last-level SID's route information, SRv6 sampling results are affected, and the values displayed in the BgpNextHop and Nexthop fields are incorrect, and DstAs is displayed as 0. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In a scenario where BGP FlowSpec and ACL redirection to a tunnel are configured, after inbound interface sampling is configured, the information collected for NextHop and BGP NextHop is 0.0.0.0 or ::, and DstAs is displayed as 0. If the actual outbound interface is a logical interface such as a sub-interface or tunnel interface, the outbound interface can only be displayed as the corresponding physical main interface or trunk main interface, affecting SRv6 sampling results. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In a scenario where BGP FLowSpec and ACL redirection to a tunnel are configured, if outbound interface sampling is configured and the actual outbound interface is different from the pre-redirection outbound interface, the NextHop and BGP NextHop values are 0.0.0.0 or ::, and the DstAs value is 0, affecting SRv6 sampling results. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In IP over SRv6 TE Policy scenarios (including L3EVPN over SRv6 TE flow group, L3VPN over SRv6 TE flow group, L3VPN over SRv6 TE Policy, EVPN L3VPN over SRv6 TE Policy, IP over SRv6 TE Policy, and DSCP-to-SRv6 TE Policy scenarios), SRv6 sampling is not supported in SID compression scenarios. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When EVC sub-interface sampling or AC-side sampling on the ingress/egress is configured, information about packets' public-network-side interface (displayed as Unknown in the flow table and 0 in the reported data), mask (displayed as 0), as (displayed as 0), nexthop (displayed as 0), bgpnexthop (displayed as 0), and DstVlanId (displayed as 0) cannot be obtained. As a result, the sampling result on the EVC sub-interface is inaccurate. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In an L2VPN/EVPN L2VPN accessing L3 tunnel scenario, upstream and downstream sampling on a PE cannot obtain or output RD values. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In SRv6 TE Policy scenarios (including EVPN L3VPNv4 over SRv6 TE flow group, L3VPNv4 over SRv6 TE flow group, L3VPNv4 over SRv6 TE Policy, EVPN L3VPNv4 over SRv6 TE Policy, EVPN L3VPNv6 over SRv6 TE flow group, L3VPNv6 over SRv6 TE flow group, L3VPNv6 over SRv6 TE Policy, and EV\PN L3VPNv6 over SRv6 TE Policy scenarios), inbound sampling (interface or flow sampling) is performed on a P node. When one of the following conditions is met: 1, The list has only one layer, and the first SID is the local End.X SID. 2, The first SID is a binding or local End SID. 3, Shortcut processing is performed on the SRv6 TE Policy/SRv6 TE flow group based on the first SID. 4, In L3VPNv4/L3VPNv6 over SRv6 BE scenarios, shortcut processing is performed on SRv6 TE Policies based on locator routes. 5, The first-hop SID route is unreachable. 6, The standby link for a switchover is a TI-LFA link. 7, Switchover microloop avoidance takes effect. 8, Switchback microloop avoidance takes effect. 9, TE FRR is triggered. Information displayed in the DstIf, nexthop, BGPnexthop, and DstAs fields is incorrect. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In SRv6 TE Policy scenarios (including EVPN L3VPNv4 over SRv6 TE flow group, L3VPNv4 over SRv6 TE flow group, L3VPNv4 over SRv6 TE Policy, EVPN L3VPNv4 over SRv6 TE Policy, EVPN L3VPNv6 over SRv6 TE flow group, L3VPNv6 over SRv6 TE flow group, L3VPNv6 over SRv6 TE Policy, and EVPN L3VPNv6 over SRv6 TE Policy scenarios), outbound sampling (interface or flow sampling) is performed on a P node. When one of the following conditions is met: 1, The list has only one layer, and the first SID is the local End.X SID. 2, The first SID is a binding or local End SID. 3, Shortcut processing is performed on the SRv6 TE Policy/SRv6 TE flow group based on the first SID. 4, In L3VPNv4/L3VPNv6 over SRv6 BE scenarios, shortcut processing is performed on SRv6 TE Policies based on locator routes. 5, The first-hop SID route is unreachable. 6, The standby link for a switchover is a TI-LFA link. 7, Switchover microloop avoidance takes effect. 8, Switchback microloop avoidance takes effect. 9, TE FRR is triggered. Information displayed in the nexthop, BGPNexthop, and DstAs fields is incorrect. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In End.X PSP scenarios where an SRv6 TE Policy in encap or insert mode crosses Policy P nodes, when inbound sampling is performed, incorrect outbound interface information is displayed, and incorrect NextHop and NextAS information is collected, affecting SRv6 sampling results. When outbound interface sampling is performed, incorrect outbound interface information may be displayed, and incorrect NextHop and Next AS information is collected, affecting SRv6 sampling results. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In IP over SRv6 TE Policy reduce scenarios (including L3EVPN over SRv6 TE flow group, L3VPN over SRv6 TE flow group, L3VPN over SRv6 TE Policy, EVPN L3VPN over SRv6 TE Policy, IP over SRv6 TE Policy, and DSCP-to-SRv6 TE Policy scenarios), when outbound sampling is performed on the first P node and the node is an End.X node, correct DIP ReIndex information cannot be obtained, and DstIf and NextHop are displayed as the outbound interface and next hop corresponding to the next-hop SID, which affects SRv6 sampling results. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In SRv6 network slicing scenarios, packets carrying slice headers on the public network side do not support sampling. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Sampling for communication between Option B SRv6 and MPLS: 1, In the SRv6 -> MPLS direction, the inbound interface restored for outbound interface sampling is the main interface. The outbound interface restored for inbound interface sampling is the main interface. The sampling data of the next hop and BGP next hop is 0. 2, In the MPLS -> SRv6 direction, the inbound interface restored for outbound interface sampling is the main interface. The sampling data of the next hop and BGP next hop is 0. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After the upgrade, the 16-bit NSIndex is dynamically allocated to interfaces on the device. The NSIndex allocated to each interface may change. The sampling server needs to synchronize the mapping between the interface index and NSIndex on the device. Otherwise, the sampling server may fail to restore interface traffic based on the NSIndex before the upgrade. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If the NetStream feature needs to be configured on a board, but the board does not support sampling data processing, you can configure a centralized sampling board that supports centralized service processing to process data. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |