![]() ![]() 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. BFD egress packet monitoringĭoes not occur. 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.Ĭannot co-exist with netflow configurations for the following routers: 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 supported over VRF-enabled interfaces on the router.įlow exporter's destination on a VRF is not supported Starting with Cisco IOS XE Release 17.6.x VRF monitoring (ip flow monitor) is supported at the physical interface level. L2VPN Flow monitor configured under Xconnect does not monitor the flows and cache is not updated.Ĭonfiguring netflow monitor for both input and output direction under L2VPN Xconnect context (local connect) is not supported. Netflow ingress and egress monitoring in not supported on mpls core interface.Ĭonfiguration of caches entries number is not supported. ![]()
0 Comments
Leave a Reply. |