i can't see any debug output, please help

[arendkolk]

Hi,

I am doing a multicast lab on the Partner Education Connection (=PEC) (MCAST PIM Dense Mode Protocol Mechanics - Challenge Lab - LabOps - IP)

and the ping goes fine from the source:

Reply to request 626 from 172.16.9.2, 140 ms

Reply to request 626 from 172.16.1.2, 264 ms

Reply to request 627 from 172.16.9.2, 140 ms

Even though i see that debugging is on, terminal monitor is on i don't see any messages when logged into lab on the PEC

R1#sh debugging

Generic IP:

  IP multicast packets debugging is on for group 224.1.2.3

IP multicast:

  IP multicast routing debugging is on for 224.1.2.3

  PIM debugging is on for 224.1.2.3

R1#sh logging

Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns)

    Console logging: level debugging, 25 messages logged

    Monitor logging: level debugging, 0 messages logged

    Buffer logging: level debugging, 5 messages logged

    Logging Exception size (4096 bytes)

    Trap logging: level informational, 31 message lines logged

Log Buffer (16000 bytes):

00:47:41: %SYS-5-CONFIG_I: Configured from console by console

00:49:16: %SYS-5-CONFIG_I: Configured from console by console

00:57:05: %SYS-5-CONFIG_I: Configured from console by console

00:58:38: %SYS-5-CONFIG_I: Configured from console by console

00:59:06: %SYS-5-CONFIG_I: Configured from console by console

R1# sh debu

R1#terminal monitor

% Console already monitors

[cadet alain]

Hi,

config t

logging monitor 7

Regards.

Alain

Don't forget to rate helpful posts.

[Alessio Andreoli]

Hi Arend,

conf t

logging console 7

logging buffe deb

end

wr

!

and then you can both see the logs by show logg command (buffer) either see the logs when you are connected via console.  The Alain suggestion is very useful if you are  connected to the machine via TTY

Take Care

Alessio