Bert Driehuis wrote: > > I would *strongly* recommend against using this command unless you > really know what you're doing and/or don't mind a router reboot. > > The SNMP capture has resource usage limitations built in; I'd suggest > using that if this functionality is required. > Yes, thank you, I now that this may lock my router, but the router is not in production and is under my desk @ work. I do not mind to reboot it sometimes if I am dumb enough to lock it up. But if you are using some "debug ip packet ACL dump" you can limit your dump to what is interesting, and I dump it only to a syslog via a free interface, not to console. Anyway, my need is to capture some WAN traffic, because on the LAN is easy to capture. And as fas as I know, the SNMP capture is only for LAN. (RMON MIB) Of course there are powerfull (and expensive) protocol analysers for WAN, but unfortunately I cannot afford one of theese. (RMON II + other features that Cisco is saving for those WAN protocol analysers) I want WAN captures just for learning purposes.
Powered by MHonArc 2.6.10