Re: [tkined] matched but not captured.

Robin_Iddon@3com.com
Mon, 8 Sep 1997 12:11:33 +0000

This looks like a valid configuration to me - I suggest that the probe you
are using has run out of memory. You are using -1 as the octets requested,
so that means all available. Try setting it to 20K and see what happens.
Either octets granted will be a number close to (but not always the same
as) 20K or it will be zero. If it is zero then the probe has no more
resources - try rebooting it or deleting some other tables and things (but
be warned that this may not free up any actual memory; many probe
implementations are not dynamically allocated).

I am not sure I saw the start of this thread - which vendor's probe is
this? Some have either special community string requirements (but I do not
think that is the problem in this case) and some have special rules which
prevent them from capturing traffic to/from their own mac address (again
not the problem in this case I suspect).

Robin

--
!! This message is brought to you via the `tkined & scotty' mailing list.
!! Please do not reply to this message to unsubscribe. To subscribe or
!! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>.
!! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.