debug isdn ..no output shown

Answered Question
Apr 28th, 2008
User Badges:

I've seen this problem once before but cant remember how to solve it.

I'm running a 2851 as a h323 gateway connected to an E1. when i run 'debug isdn q931' i'm not seeing the output although i know for a fact calls are going in and coming out. i'm connected via console which monitors so term mon is not needed but i'm sure there is a logging command or something that then makes the output be shown.

just cant remember...can anybody help??

Correct Answer by Richard Burts about 9 years 4 weeks ago

Andy


It is possible (but in my experience less likely) for the same issues to impact debug output to telnet sessions. Someone could have changed the severity level or could have disabled logging to the monitor (which is what sends output to telnet sessions). For telnet the command is simmilar (but not quite the same):

logging monitor debug


One way to check things is to issue the show log command. In the first group of lines displayed it should show the various logging destinations and how they are set (console logging, buffer logging, and trap logging). It should show what is enabled and what is disabled and what severity level is set for each.


HTH


Rick

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Richard Burts Mon, 04/28/2008 - 12:50
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

Andy


There are several things that may result in debug output now showing up on the console. It is possible that someone has configured the console output for a level that excludes debug output (which is level 7). Or it is possible that someone has configured the console to not display syslog output.


The solution to both of these is to configure:

logging console debug


HTH


Rick

andy.butler Mon, 04/28/2008 - 13:39
User Badges:

thanks rick i'll give that a try. would a similar command work for a telnet session or would that be the same problem?

this was an out of the box router so it seems strange but i really appreciate your help

Correct Answer
Richard Burts Mon, 04/28/2008 - 14:02
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

Andy


It is possible (but in my experience less likely) for the same issues to impact debug output to telnet sessions. Someone could have changed the severity level or could have disabled logging to the monitor (which is what sends output to telnet sessions). For telnet the command is simmilar (but not quite the same):

logging monitor debug


One way to check things is to issue the show log command. In the first group of lines displayed it should show the various logging destinations and how they are set (console logging, buffer logging, and trap logging). It should show what is enabled and what is disabled and what severity level is set for each.


HTH


Rick

Richard Burts Tue, 04/29/2008 - 03:47
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

Andy


I am glad that my response was helpful in resolving your question. Thank you for using the rating system to indicate that your question was resolved (and thanks for the rating). It makes the forum more useful when people can read a question and can know that there was a response that did help resolve the question.


The forum is an excellent place to learn about Cisco networking. I encourage you to continue your participation in the forum.


HTH


Rick

Actions

This Discussion