On 29/3/2013 11:09 πμ, Adrian Popa wrote:
> Not all routers/ IOS versions/cards support ip flow ingress and ip
> flow egress on any interface, so you should just export one direction
> from all interesting interfaces.
Yes, that's what I finally did:
#show ip flow interface
GigabitEthernet0/0.1
ip flow ingress
GigabitEthernet0/0.5
ip flow ingress
GigabitEthernet0/0.102
ip flow ingress
GigabitEthernet0/0.132
ip flow ingress
GigabitEthernet0/0.575
ip flow ingress
GigabitEthernet0/0.576
ip flow ingress
GigabitEthernet0/1.1
ip flow ingress
GigabitEthernet0/1.100
ip flow ingress
FastEthernet1/0
ip flow ingress
FastEthernet1/1
ip flow ingress
Serial1/0/0
ip flow ingress
Tunnel1
ip flow ingress
I also set "ipv6 flow ingress" to all interfaces (with IPv6 addresses)
but this is not listed with the above command.
Interestingly, *some* outbound traffic was being recorded, while also,
at times, outbound traffic was being recorded more extensively (strange
behavior).
Now that I switched to the "standard" model (without egress), things
look to work nicely.
Regards,
Nick
------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete
for recognition, cash, and the chance to get your game on Steam.
$5K grand prize plus 10 genre and skill prizes. Submit your demo
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
_______________________________________________
Nfsen-discuss mailing list
Nfsen-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
