1 2 3 Previous Next 41 Replies Latest reply: Mar 17, 2012 3:01 PM by arteq Go to original post RSS
      • 15. Re: debug eigrp packets and U all
        lp4nb

        what were you trying to accomplish btw.

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

        Regards

        • 16. Re: debug eigrp packets and U all
          arteq

          any time, dudes...

          • 17. Re: debug eigrp packets and U all
            Wireless Mouse

            Ip4nb I was trying to see if packets were received from different destination using eigrp protocol.

             

            Anyway by asking you arteq I  always learn something new as I did not know about

            :

            Automore On

            Capabilities: Receives Logging Output

             

            and

            capabilities says none

            • 18. Re: debug eigrp packets and U all
              arteq

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

              • 19. Re: debug eigrp packets and U all
                Wireless Mouse

                This is very strange indeed again, I am still playing and you know what...I am doing this with another router,I console to R3 and run debug eigrp with capabilities none and I can see the messages, I telnet from a different router to R3 with capabilities none and I can not see the debug messages and if i turn on term mon i can see the messages...My question is why? I mean on console the term mon is turn off and I can see the debug messages

                • 20. Re: debug eigrp packets and U all
                  arteq

                  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?

                  • 21. Re: debug eigrp packets and U all
                    Wireless Mouse

                    Yes you are right again I can see that but its very tricky. its my problem to try to make logics and sense in the output  and in console i R3 in capabilities should said: Receives Logging Output but is saying NONE....I know arteq I know now that in console the term mon is always working by default ....just one second I will do something I will disable the term mon on console to see the output. I will be back in 1 min...............this is not making sense at all...the no term mon does not work....so what if you want to turn off the tem moni.....well either in console and telnet the ''no term mon '' is not working.

                    • 22. Re: debug eigrp packets and U all
                      Wireless Mouse

                      I found it ''term no mon'' i will be back in a min

                      • 23. Re: debug eigrp packets and U all
                        arteq

                        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

                        • 24. Re: debug eigrp packets and U all
                          Wireless Mouse

                          so from console

                           

                          R3#term no monitor

                          R3#show ter

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

                          Length: 24 lines, Width: 80 columns

                          Status: PSI Enabled, Ready, Active, Automore On

                          Capabilities: none

                           

                          AND

                           

                          R3#term no mon

                          R3#term mon

                          % Console already monitors

                           

                          Well in console let u use the term no mon! what for? if it does not make any difference?!

                           

                          R3#term no mon

                          R3#debug eigrp packets

                          EIGRP Packets debugging is on

                              (UPDATE, REQUEST, QUERY, REPLY, HELLO, IPXSAP, PROBE, ACK, STUB, SIAQUERY, SIAREPLY)

                          R3#

                          *Mar  1 00:47:14.371: EIGRP: Sending HELLO on FastEthernet0/0

                          *Mar  1 00:47:14.375:   AS 90, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

                          *Mar  1 00:47:15.095: EIGRP: Received HELLO on FastEthernet0/0 nbr 10.1.2.2

                          *Mar  1 00:47:15.095:   AS 90, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0

                          R3#

                          *Mar  1 00:47:16.011: EIGRP: Sending HELLO on Serial0/0

                          *Mar  1 00:47:16.015:   AS 90, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

                          R3#u all

                          All possible debugging has been turned off

                          R3#

                          *Mar  1 00:47:17.743: EIGRP: Received HELLO on Serial0/0 nbr 10.1.34.1

                          *Mar  1 00:47:17.747:   AS 90, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0

                          *Mar  1 00:47:18.667: EIGRP: Sending HELLO on FastEthernet0/0

                          *Mar  1 00:47:18.671:   AS 90, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

                          • 25. Re: debug eigrp packets and U all
                            Wireless Mouse

                            Two things....

                             

                            1) in the show term in console > capabilities >should say;Receives Logging Output

                             

                            2) the '' mon no ter '' should not be allowed if its not making any difference.

                             

                            I know what you mean that you want monitor for default as you want to see what is happening....but you would not like tem mon for default

                            when telneting,  guess information is as important regardless of telneting or consoling

                            • 26. Re: debug eigrp packets and U all
                              arteq

                              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).

                              • 27. Re: debug eigrp packets and U all
                                Wireless Mouse

                                Thanks arteq, very good research!!  There is so much to learn.....Cisco is like a Universe....it never ends and it expand further! You will never stop learning in Cisco! Never!

                                • 28. Re: debug eigrp packets and U all
                                  arteq

                                  cool...

                                  • 29. Re: debug eigrp packets and U all
                                    Greg, CCNP, JNCIP

                                    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 :-)