Monitored intermittently, and netflow and OSPF flaps are observed when ELB is SADT egress packet monitoringĮthernet loopback (ELB) is enabled on same interface, the netflow monitoringīehavior is inconsistent for the data packets. ![]() If SADT and netflow is enabled on the same interface, only the SADT ingress packets are monitored. If SADT re-directs high volumes of traffic to FPGA, then netflow To remove netflow related commands before reverting to non-netflow-supportedĪt the global level, SADT re-directs traffic towards FPGA. Netflow configuration will not work and vice-versa. When PBR and netflow is applied together on an interface, the order of operations is applicable. SDM template must be set as video (similar to PBR) using the sdm prefer video command. The scale of PBR feature may be reduced when netflow is enabled. ICMP egress packetĪt the global level, both netflow and PBR features use the same TCAM region for adding rules. When ICMP (ping) and netflow is enabled on the same interface, only the ICMP ingress packets are monitored. If BFD and netflow is enabled on the same interface, only the BFD ingress packets are monitored. This is due to FPGA limitations.Įnabled on the same interface with netflow configuration. Overall traffic monitored is within 1Gbps. Monitoring can account for a maximum of 1Gbps traffic rate in the system (withĪ minimum frame size of 100 bytes). Though, netflow supports 16KĮntries, flows monitored are lower due to hash collisions. Monitoring can be configured only after configuring bridge-domain on the EFPįlows can only be learnt due to FPGA limitations. Ports (IP Ethernet, BDI) and EFP are supported. Supported are packets and bytes (collect counter packets and collect counter Identify or classify flows for both IPv4 and IPv6 unicast traffic. Type, TOS, source port, destination port and input logical interface to Monitoring supports only the 7 keys-Source IP, Destination IP, Layer 3 protocol Netflow monitoring is only supported on the RSP2 module. L2VPN Flow monitor configured under Xconnect does not monitor the flows and cache is not updated.Ĭonfiguring netflow monitor under L2VPN Xconnect context (local connect) is not supported. using different will allow you to collect different information on a particular interface by choosing the information you want to match.Netflow ingress monitoring in not supported on mpls core interface.Ĭonfiguration of caches entries number is not supported. ![]() You have mentioned earlier to use different for each interface. ![]() If for example i used the same scenario above and i wanted to monitor an interface individually to see the BW utilization or anything i want to monitor for this particular interface, i have to create a different with a different UDP port No. from the PRTG side, all the output will be under one sensor per device like an aggregation for all the flows of all the interfaces. My question is: What is the best practice to apply Netflow on multiple interfaces on the same device to get the best output results?, is it better to use, which gave me the best results output without flow duplication. I configured Flexible Netflow on ISR4331 with one I have multiple GRE tunnels and Subinterfaces on the router on which I want to apply the Netflow configuration on and use PRTG as a collector.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |