Viewing and filtering a router log for GET/

Discussion in 'Cisco' started by Dumb Luck, Jan 3, 2006.

  1. Dumb Luck

    Dumb Luck Guest

    I want to be able to view the logs on my router for any GET/ commands.
    When I use show logg I get:

    Router#show log
    Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
    Console logging: level debugging, 8289 messages logged
    Monitor logging: level debugging, 0 messages logged
    Buffer logging: disabled
    Trap logging: level informational, 8293 message lines logged

    But how do I actually see the messages? Then how do I filter these?

    thanks for any help!
    Dumb Luck, Jan 3, 2006
    1. Advertisements

  2. Dumb Luck

    Alcalin Guest

    Issue the command :
    Router#(config)logging buffered

    The buffer logging is actually disabled as the output of "show logg" tells
    Alcalin, Jan 3, 2006
    1. Advertisements

  3. Dumb Luck

    Dumb Luck Guest

    Ok, so I now enabled Buffer logging. Does that mean that the other
    logging, (monitor, or console) does not keep track of GET/ commands?
    If so then I will only be able to view the messages from now on right?
    Dumb Luck, Jan 3, 2006
  4. Dumb Luck

    Dumb Luck Guest

    What is the difference between Console, Monitor, Buffer, and Trap
    Dumb Luck, Jan 3, 2006
  5. Dumb Luck

    Alcalin Guest

    Yes this is correct.
    An history exists in the MIB but it contains only 1 entry.
    You can see it with : "sh logging history"
    Alcalin, Jan 3, 2006
  6. Dumb Luck

    Alcalin Guest

    Console means msg sent to the console port
    Monitor means msg sent to a vty line with monitoring ( "terminal monitor" in
    a CLI session to enable this feature)
    Buffer means msg sent to the logging buffer (feature that you've enabled)
    Trap means SNMP traps msg
    Alcalin, Jan 3, 2006
  7. Dumb Luck

    Dumb Luck Guest

    So if I am understanding you correctly, now that the buffer is enabled,
    all of the messages will be saved there? Then at a later date I can
    review those messages, is that correct? Is there a way to export those
    messages, to something like a csv file? How do I review the log once
    there is information stored in it?
    Dumb Luck, Jan 3, 2006
  8. Dumb Luck

    Dumb Luck Guest

    By the way thanks for the replys you have been a big help.
    Dumb Luck, Jan 3, 2006
  9. You can review the log msg by typing "sh logg" in a CLI session,
    though you should be aware that the default size of the logg buffer is
    4096 bytes.
    You can increase the logg buffer by issuing the command "logg buffer
    <size _in_bytes>"

    Export : the best way is to export logg msg to a syslog server
, Jan 4, 2006
  10. a écrit :
    All of the information in this thread is valid, however, you won't see
    urls accessed (which I think is what you are trying to see), at most,
    depending on the ACLs you have on your interfaces, you will see hits on
    port 80, but will not see the individual URLs.
    Francois Labreque, Jan 5, 2006
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.