Thanks for the question. SamE wrote: > interface GigabitEthernet0/1/0 > ip address 192.168.1.1 255.255.255.0 > ip access-group 102 in > ip flow ingress > ip flow egress > ip nat inside > ip inspect test out > ip virtual-reassembly in > negotiation auto > no cdp enable >
I'm not a Cisco/NetFlow expert, but the major difference I see between your configuration for the interface and the example we have at: http://www.intermapper.com/support/faqs.aspx#faq-flows is that you've used "ip flow ingress" and "ip flow egress" instead of "ip route-cache flow". I am led to believe that the former configures flows on subinterfaces, while "ip route-cache flow" configures flows on the interface itself. I would remove the "ip flow ingress/egress", add the "ip route-cache flow", and then check with the following commands: Code: show ip flow export show ip cache flow This shows what flow information is being exported. Rich Brown Dartware -------------------- m2f -------------------- Read this topic online here: http://forums.intermapper.com/viewtopic.php?p=4169#4169 ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [email protected]
