Ip flow-export destination article describes how to configure NetScaler AppFlow for SolarWinds. Ip flow-export source FastEthernet0/1.100 Here is my configuration for a Cisco 1841 that sends Netflows to a collector. The layer 2 port only cares about MAC addresses. The standard layer 2 switching port is totally unaware of the IP address in the Ethernet frame that it just switched. If it is the Management port, I don't think Netflow will work.Īlmost all of your match statements are matching on info that only exists at layer 3. The Netflow monitoring of the port that you use to log into the switch is going to have very little traffic on it. The netflow commands I can apply to those standard interfaces are those listed above: ip flow ingress and ip flow egress. What I'm trying to monitor are the standard gigabit interfaces. My switch does not allow flexible netflow to be applied to non-service module ports.
I've had users on other forums attempt to help me by pointing me to towards flexible netflow configurations that use the command ip flow monitor input applied to the interface they want to monitor. Neither of those commands were accepted on that port. I tried to run the ip nbar protocol-discovery and the ip route-cache flow on the port to be monitored. How do I get this port configured correctly to capture NetFlow data?Ĭonfig on switch: int gig ip flow ingress ip flow egress ip flow-export source ip flow-export version 5 ip flow-export destination 2055 When I click on the interface I want to monitor then click "Start Flow Capture" I get a 'NetFlow is not detected on the selected interface'. I can connect through the software to my switch, I can see all of the interfaces but none of them show NetFlow enabled.
Recently we had some suspicious traffic so I installed a new version of the software on a Win 10 machine. A few years back I had SolarWinds Real-Time NetFlow Analyzer working with my Cisco 3750x switch.
0 kommentar(er)
