cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
6912
Views
5
Helpful
8
Replies

Logging on Cisco Router.

Hi,

Yesterday, logging on our 3825 Voice Gateway, logging was running ok but someone left debugging on. I ran u all on the router and now there are no logs on the router when I telnet in and run sh log.

Today so far, it has only recorded me on the router.

Jan  7 08:55:21: %SYS-5-CONFIG_I: Configured from console by vty0 (xx.xx.xx.xx)
Jan  7 09:37:31: %SYS-5-CONFIG_I: Configured from console by vty0 (xx.xx.xx.xx)

Yesterday it was doing the following and this is what I would like it to be doing:

Jan  5 12:10:35: ISDN Se0/0/1:15 Q931: RX <- RELEASE pd = 8  callref = 0xEF8D
Jan  5 12:10:35: ISDN Se0/0/1:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x6F8D
Jan  5 12:10:36: ISDN Se0/0/1:15 Q931: RX <- CONNECT pd = 8  callref = 0xEFD9
        Connected Number i = 0x1183, '353861906362'
Jan  5 12:10:36: ISDN Se0/0/1:15 Q931: TX -> CONNECT_ACK pd = 8  callref = 0x6FD9
Jan  5 12:10:37: ISDN Se0/0/1:15 Q931: RX <- ALERTING pd = 8  callref = 0xEFDC
        Progress Ind i = 0x8488 - In-band info or appropriate now available
Jan  5 12:10:42: ISDN Se0/0/1:15 Q931: RX <- CONNECT pd = 8  callref = 0xEFDB
        Connected Number i = '!', 0x83, '868167797'
Jan  5 12:10:42: ISDN Se0/0/1:15 Q931: TX -> CONNECT_ACK pd = 8  callref = 0x6FDB
Jan  5 12:10:42: ISDN Se0/0/1:15 Q931: TX -> DISCONNECT pd = 8  callref = 0x6FD2
        Cause i = 0x8090 - Normal call clearing

The IOS and Router details are:

Cisco IOS Software, 3800 Software (C3825-ADVIPSERVICESK9-M), Version 12.4(15)T7, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by Cisco Systems, Inc.
Compiled Wed 13-Aug-08 23:16 by prod_rel_team

ROM: System Bootstrap, Version 12.3(11r)T2, RELEASE SOFTWARE (fc1)

What can I do to get this logging again?

Thanks

Anthony.

8 Replies 8

Disc01079
Level 1
Level 1

Ah Anthony, I think it is clear what happened here.

Typical logging information can be recognized by the message prefix %AAA-#-BBBBB. The messages you were receiving are debugging messages which you killed with your 'undebug all' command. I’m sorry but I'm not a router expert so I can’t tell you exact what the command should be to restore your messages but it should something like 'debug isdn …' (events or cc?). Cheers,

Dick Hogeweg

Hi,

Thanks for your respose.

I have tried these but I don't think it is a debugging issue as I have enabled debugging and disabled it numerous times before. I suspect that this may have something got to do with logging.

Thanks

Anthony.

Anthony

For the specific issue that you raise in your original post: the messages that you give as examples of what you want are output from debug isdn q931. If you want those messages to appear in the log, then you need to issue the privilege level command:

debug isdn q931

Perhaps the more broad question is that every syslog message has a severity level (debug is level 7, informational is level 6, and so on). You can set the severity level of messages to be sent to various syslog destinations. For example I typically set the severity level of buffer logging to debug (level 7) and set the severity level of console logging to informational (level 6). So if you are concerned about what messages are/are not showing in the syslog, you might start with determining theseverity levels associated with the various log destinations. That information is in the first group of lines of output to the show log command. (and you could find non-default settings using the command: show run | include log

HTH

Rick

HTH

Rick

Do you want the debug logs or the standard loggings?  If it's the latter, try "logging buffer ".

Hi Rick,

Thanks for your response.

I am going to try and be alot clearer this time. I have two voice gateway routers. One is logging the info, I need and the other is not. I will call them Is Logging and Not Logging.

The Is Logging router is logged the info I need. There is no debugging on the Is Logging router and it is logged the info on the router.

Please see extract on router.

Jan 11 13:57:53.048: %ISDN-6-CONNECT: Interface Serial2/0:13 is now connected to N/A N/A
Jan 11 13:57:54.660: %ISDN-6-CONNECT: Interface Serial2/0:13 is now connected to N/A N/A
Jan 11 13:57:54.660: %ISDN-6-DISCONNECT: Interface Serial2/0:11  disconnected from unknown , call lasted 37 seconds
Jan 11 13:58:03.304: %ISDN-6-CONNECT: Interface Serial2/0:14 is now connected to N/A N/A
Jan 11 13:58:06.220: %ISDN-6-DISCONNECT: Interface Serial2/0:4  disconnected from 876451397 , call lasted 268 seconds
Jan 11 13:58:09.303: %ISDN-6-CONNECT: Interface Serial2/0:14 is now connected to N/A N/A
Jan 11 13:58:24.823: %ISDN-6-DISCONNECT: Interface Serial2/0:18  disconnected from 8135395 , call lasted 813 seconds
Jan 11 13:58:31.134: %ISDN-6-CONNECT: Interface Serial2/0:16 is now connected to N/A N/A
Jan 11 13:58:37.134: %ISDN-6-CONNECT: Interface Serial2/0:16 is now connected to N/A N/A
Jan 11 13:58:40.970: %ISDN-6-DISCONNECT: Interface Serial2/0:10  disconnected from 860545884 , call lasted 121 seconds
Jan 11 13:58:50.789: %ISDN-6-DISCONNECT: Interface Serial2/0:7  disconnected from 879231517 , call lasted 268 seconds

On this router, it contains the following:

sh run | include log
service timestamps log datetime msec localtime
logging buffered 100000
logging console warnings
dot11 syslog
log config
no logging event link-status
no logging event link-status
no logging event link-status
no logging event link-status
no logging event link-status
no logging event link-status
log-adjacency-changes
logging facility syslog
logging xx.xx.xx.xx

logging xx.xx.xx.xx

snmp-server enable traps syslog
## Please remember to log out of your telnet session properly!
banner login ^C
logging synchronous
login
login
logging synchronous
login
login

On the Not Logging router, when I do a sh log, it contains no info.

sh run | include log
service timestamps log datetime localtime
logging buffered 4096
logging console warnings
dot11 syslog
log config
no logging event link-status
no logging event link-status
no logging event link-status
log-adjacency-changes
logging facility syslog
logging xx.xx.xx.xx

logging xx.xx.xx.xx

## Please remember to log out of your telnet session properly!
banner login ^C
banner motd ^CPlease remember to log out of your telnet session properly!^C
logging synchronous
login
login
login

What do I need to do to get the Not Logging to log the same as Is Logging.

I hope this makes sense.

Thanks

Anthony.

Hi Athony,

If you do a "sh logg", do you get "Buffer logging: level debugging, 16 messages logged" or "Buffer logging: disabled"?

You haven't mentioned what type of device the Is Logging router is.  I'm guessing it's either a 3845, 3600, or 2600.  If so, then those devices have call info and D channel logging enabled by default.  The 3825 does not.  Therefore, you need to configure the following under your ISDN/T1 interfaces:

logging event link-status bchan

logging event link-status dchan

That will give you equivalent logging to the other router. 

Excellent!  I was having the same issue...thanks!

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: