the show ip cache flow clearly shows that the router is generating netflow data. If it is not getting to the analyzer there are a couple of things that I would suggest that you check:
- is there IP connectivity from the router to the address of the analyzer (192.168.9.101)?
- is the analyzer listening on port 9996?
- is the analyzer processing format version 5 packets?
- is there possibly any access list between the router and the analyzer which is not permitting UDP port 9996 to pass?
I would suggest that you do an extended ping from the router and in the extended ping specify 192.168.9.101 as the destination and specify ethernet 0 as the source. And if the extended ping does work then I would suggest an extended trace with destination 192.168.9.101 and source as ethernet 0 (to check on UDP packets instead of ICMP packets).
For extended ping you must be in privilege mode and you enter the command ping and press enter. The IOS then knows that you want extended ping and it asks a series of questions to get the information it needs to do the extended ping. For this issue the important questions are destination address (192.168.9.101) and when it asks if you want extended commands, you respond yes, and then specify the source address (address of the ethernet interface). Just take the defaults on the other questions by pressing enter.
The format of the permit rule will depend on what platform and on what direction it is being applied.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...