Skip navigation
Cisco Learning Home > CCNP R&S Study Group > Discussions
This Question is Answered
1829 Views 41 Replies Latest reply: Mar 17, 2012 3:01 PM by arteq RSS Go to original post 1 2 3 Previous Next

Currently Being Moderated
  • lp4nb 520 posts since
    Jun 27, 2009
    Currently Being Moderated
    15. Mar 17, 2012 5:34 AM (in response to Wireless Mouse)
    Re: debug eigrp packets and U all

    what were you trying to accomplish btw.

    if not debuggin hellos, try using debug eigrp packet terse--  command.

    Regards

  • arteq 1,733 posts since
    Sep 11, 2011
    Currently Being Moderated
    16. Mar 17, 2012 5:35 AM (in response to Wireless Mouse)
    Re: debug eigrp packets and U all

    any time, dudes...

  • arteq 1,733 posts since
    Sep 11, 2011
    Currently Being Moderated
    18. Mar 17, 2012 5:48 AM (in response to Wireless Mouse)
    Re: debug eigrp packets and U all

    cool... i learn from you as well, gb&f... that's why we are here...

  • arteq 1,733 posts since
    Sep 11, 2011
    Currently Being Moderated
    20. Mar 17, 2012 6:49 AM (in response to Wireless Mouse)
    Re: debug eigrp packets and U all

    the console monitors by default...

     

    r3#sh term

    Line 0, Location: "", Type: ""

    Length: 24 lines, Width: 80 columns

    Baud rate (TX/RX) is 9600/9600, no parity, 2 stopbits, 8 databits

    Status: PSI Enabled, Ready, Active, Automore On

    Capabilities: none

     

    r3#term mon

    % Console already monitors

    r3#sh term

    Line 0, Location: "", Type: ""

    Length: 24 lines, Width: 80 columns

    Baud rate (TX/RX) is 9600/9600, no parity, 2 stopbits, 8 databits

    Status: PSI Enabled, Ready, Active, Automore On

    Capabilities: none

     

    was this answer helpful?

  • arteq 1,733 posts since
    Sep 11, 2011
    Currently Being Moderated
    23. Mar 17, 2012 7:03 AM (in response to Wireless Mouse)
    Re: debug eigrp packets and U all

    correct.. but i wouldn't do that... i want the terminal to monitor

     

    logging synchronous is another matter... it really should be the default for console and vty

  • arteq 1,733 posts since
    Sep 11, 2011
    Currently Being Moderated
    26. Mar 17, 2012 7:29 AM (in response to Wireless Mouse)
    Re: debug eigrp packets and U all

    terminal monitoring is for vty sessions... for console output limiting you have to go farther, see below... from cisco.com

     

    Limiting the Types of Logging Messages Sent to the Console

    To limit the types of messages that are logged to the console, use the logging console router configuration command. The full syntax of this command follows:

    logging console level
    no logging console

    The logging console command limits the logging messages displayed on the console to messages up to and including the specified severity level, which is specified by the level argument.

    The level argument is one of the keywords listed in http://www.cisco.com/en/US/docs/ios/12_0/debug/command/reference/dintro.html#wp3356. Keywords are listed in order from the most severe level to the least severe.

    The no logging console command disables logging to the console.

    Example

    The following example sets console logging of messages at the debugging level, which is the least severe level and which displays all logging messages:

    logging console debugging

    Logging Messages to an Internal Buffer

    The default logging device is the console; all messages are displayed on the console unless otherwise specified.

    To log messages to an internal buffer, use the logging buffered router configuration command. The full syntax of this command follows:

    logging buffered
    no logging buffered

    The logging buffered command copies logging messages to an internal buffer instead of writing them to the console. The buffer is circular in nature, so newer messages overwrite older messages. To display the messages that are logged in the buffer, use the privileged EXEC command show logging. The first message displayed is the oldest message in the buffer.

    The no logging buffered command cancels the use of the buffer and writes messages to the console (the default).

  • arteq 1,733 posts since
    Sep 11, 2011
    Currently Being Moderated
    28. Mar 17, 2012 7:40 AM (in response to Wireless Mouse)
    Re: debug eigrp packets and U all

    cool...

  • Greg, CCNP, JNCIP 171 posts since
    Sep 14, 2011
    Currently Being Moderated
    29. Mar 17, 2012 7:42 AM (in response to Wireless Mouse)
    Re: debug eigrp packets and U all

    It can be annoying, lots of log messages spewing out on a slow serial console, You can disable logging on the console port as follows:

     

    R1(config)# no logging console

     

     

    But in the real world, you probably shouldn't just ignore all log messages.  You can reserve some memory for buffering the current log messages, which you can read at your convenience on the router w/ "show log":

     

    R1(config)# logging buffered 1000000

     

     

    It's also a good idea to send log messages to a syslog server, which enables you to do all sorts of useful things on the server (e.g. store logs to hard disk, backup, search, sort, generate alarms/reports):

     

    R1(config)#logging x.x.x.x

     

     

    Edit: arteq's fast :-)

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)