Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

Term Mon problems in 3845 Router....

When we go to term mon information is immediately scrolling even though we have issued the "un all" command.  The only way we can get it to stop is to go to config t and do "no logging monitoring debugging".  This doesn't happen in our other routers.  Any suggestions on what could be causing this before we open a TAC Case?  Thanks.  This is a   C3845 Router configured as a Voice Gateway with PRI's.

Thanks,

Jeff               

1 ACCEPTED SOLUTION

Accepted Solutions
Community Member

Term Mon problems in 3845 Router....

What you are seing are CDR logs

To generate them you would need to enable

Ex:

router(config)#gw-accounting syslog  

You can disable it using the no command

thanks

6 REPLIES

Term Mon problems in 3845 Router....

Hmmm....I know I'm asking the obvious, but have you typed "term no mon" and hit enter?

HTH,
John

*** Please rate all useful posts ***

HTH, John *** Please rate all useful posts ***
Hall of Fame Super Gold

Term Mon problems in 3845 Router....

Jeff

If it is accurate, as you report it, that you have done un all and are still being flooded with terminal monitor output then it is likely that what is generating the output is not debug.  It would be helpful to know what kind of output it is that is flooding your session with terminal monitor. So I would ask that you enable terminal monitor, let a bunch of output come to the screen. then disable monitor logging and post a sample of (at least 5 or 6) the messages that are flooding your terminal session.

HTH

Rick

Community Member

Term Mon problems in 3845 Router....

John - The problem isn't that we don't want it to log to the monitor.  The problem is we only only it to show when we go to term mon and turn debugging on.  For some reason when we turn turn logging monitor debugging it starts scrolling information without turning debugging on.

Rick - Here's some output that starts scrolling as soon as we turn on the logging monitor debugging...even when we issue the "un all" command.

Thanks,

Jeff

GSB-EVG2-38(config)#logging monitor debugging

GSB-EVG2-38(config)#

210518155: Dec 10 08:18:59.149: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId 96E9EE6B60DC11E38A5E001795275880, SetupTime 08:17:09.229 CST Tue Dec 10 2013, PeerAddress , PeerSubAddress , DisconnectCause 10  , DisconnectText normal call clearing (16), ConnectTime 08:17:09.229 CST Tue Dec 10 2013, DisconnectTime 08:18:59.149 CST Tue Dec 10 2013, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 5484, TransmitBytes 921312, ReceivePackets 5493, ReceiveBytes 878880

210518156: Dec 10 08:18:59.149: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:12/10/2013 08:17:09.223,cgn:,cdn:,frs:0,fid:5477561,fcid:96E9EE6B60DC11E38A5E001795275880,legID:5394B9,bguid:96E9EE6B60DC11E38A5E001795275880

210518157: Dec 10 08:18:59.149: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 2, ConnectionId 96E9EE6B60DC11E38A5E001795275880, SetupTime 08:17:09.229 CST Tue Dec 10 2013, PeerAddress , PeerSubAddress , DisconnectCause 10  , DisconnectText normal call clearing (16), ConnectTime 08:17:09.229 CST Tue Dec 10 2013, DisconnectTime 08:18:59.149 CST Tue Dec 10 2013, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 5484, TransmitBytes 877440, ReceivePackets 5484, ReceiveBytes 877440

GSB-EVG2-38(config)#

210518158: Dec 10 08:18:59.149: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:12/10/2013 08:17:09.223,cgn:,cdn:,frs:0,fid:5477562,fcid:96E9EE6B60DC11E38A5E001795275880,legID:5394BA,bguid:96E9EE6B60DC11E38A5E001795275880

GSB-EVG2-38(config)#

210518159: Dec 10 08:19:02.037: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId D3AC710060DC11E38A6D001795275880, SetupTime 08:18:51.167 CST Tue Dec 10 2013, PeerAddress , PeerSubAddress , DisconnectCause 10  , DisconnectText normal call clearing (16), ConnectTime 08:18:51.167 CST Tue Dec 10 2013, DisconnectTime 08:19:02.037 CST Tue Dec 10 2013, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 513, TransmitBytes 85716, ReceivePackets 543, ReceiveBytes 86412

210518160: Dec 10 08:19:02.037: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:12/10/2013 08:18:51.161,cgn:,cdn:,frs:0,fid:5477591,fcid:D3AC710060DC11E38A6D001795275880,legID:5394D7,bguid:D3AC710060DC11E38A6D001795275880

210518161: Dec 10 08:19:02.037: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 2, ConnectionId D3AC710060DC11E38A6D001795275880, SetupTime 08:18:51.167 CST Tue Dec 10 2013, PeerAddress , PeerSubAddress , DisconnectCause 10  , DisconnectText normal call clearing (16), ConnectTime 08:18:51.167 CST Tue Dec 10 2013, DisconnectTime 08:19:02.037 CST Tue Dec 10 2013, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 513, TransmitBytes 81612, ReceivePackets 513, ReceiveBytes 81612

GSB-EVG2-38(config)#

210518162: Dec 10 08:19:02.037: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:12/10/2013 08:18:51.161,cgn:,cdn:,frs:0,fid:5477592,fcid:D3AC710060DC11E38A6D001795275880,legID:5394D8,bguid:D3AC710060DC11E38A6D001795275880

GSB-EVG2-38(config)#

GSB-EVG2-38(config)#logging monitor debugging

GSB-EVG2-38(config)#

210518155: Dec 10 08:18:59.149: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId 96E9EE6B60DC11E38A5E001795275880, SetupTime 08:17:09.229 CST Tue Dec 10 2013, PeerAddress , PeerSubAddress , DisconnectCause 10  , DisconnectText normal call clearing (16), ConnectTime 08:17:09.229 CST Tue Dec 10 2013, DisconnectTime 08:18:59.149 CST Tue Dec 10 2013, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 5484, TransmitBytes 921312, ReceivePackets 5493, ReceiveBytes 878880

210518156: Dec 10 08:18:59.149: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:12/10/2013 08:17:09.223,cgn:,cdn:,frs:0,fid:5477561,fcid:96E9EE6B60DC11E38A5E001795275880,legID:5394B9,bguid:96E9EE6B60DC11E38A5E001795275880

210518157: Dec 10 08:18:59.149: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 2, ConnectionId 96E9EE6B60DC11E38A5E001795275880, SetupTime 08:17:09.229 CST Tue Dec 10 2013, PeerAddress , PeerSubAddress , DisconnectCause 10  , DisconnectText normal call clearing (16), ConnectTime 08:17:09.229 CST Tue Dec 10 2013, DisconnectTime 08:18:59.149 CST Tue Dec 10 2013, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 5484, TransmitBytes 877440, ReceivePackets 5484, ReceiveBytes 877440

GSB-EVG2-38(config)#

210518158: Dec 10 08:18:59.149: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:12/10/2013 08:17:09.223,cgn:,cdn:,frs:0,fid:5477562,fcid:96E9EE6B60DC11E38A5E001795275880,legID:5394BA,bguid:96E9EE6B60DC11E38A5E001795275880

GSB-EVG2-38(config)#

210518159: Dec 10 08:19:02.037: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId D3AC710060DC11E38A6D001795275880, SetupTime 08:18:51.167 CST Tue Dec 10 2013, PeerAddress , PeerSubAddress , DisconnectCause 10  , DisconnectText normal call clearing (16), ConnectTime 08:18:51.167 CST Tue Dec 10 2013, DisconnectTime 08:19:02.037 CST Tue Dec 10 2013, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 513, TransmitBytes 85716, ReceivePackets 543, ReceiveBytes 86412

210518160: Dec 10 08:19:02.037: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:12/10/2013 08:18:51.161,cgn:,cdn:,frs:0,fid:5477591,fcid:D3AC710060DC11E38A6D001795275880,legID:5394D7,bguid:D3AC710060DC11E38A6D001795275880

210518161: Dec 10 08:19:02.037: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 2, ConnectionId D3AC710060DC11E38A6D001795275880, SetupTime 08:18:51.167 CST Tue Dec 10 2013, PeerAddress , PeerSubAddress , DisconnectCause 10  , DisconnectText normal call clearing (16), ConnectTime 08:18:51.167 CST Tue Dec 10 2013, DisconnectTime 08:19:02.037 CST Tue Dec 10 2013, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 513, TransmitBytes 81612, ReceivePackets 513, ReceiveBytes 81612

GSB-EVG2-38(config)#

210518162: Dec 10 08:19:02.037: %VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:12/10/2013 08:18:51.161,cgn:,cdn:,frs:0,fid:5477592,fcid:D3AC710060DC11E38A6D001795275880,legID:5394D8,bguid:D3AC710060DC11E38A6D001795275880

GSB-EVG2-38(config)#

Community Member

Term Mon problems in 3845 Router....

What you are seing are CDR logs

To generate them you would need to enable

Ex:

router(config)#gw-accounting syslog  

You can disable it using the no command

thanks

Community Member

Term Mon problems in 3845 Router....

Thanks to all for the help.

Serge - You were correct.  Turning off the gw-accounting syslog stopped the messages that were scrolling when we would go to term mon.

Thanks!!!

Thank you all for the assistance!

Hall of Fame Super Gold

Term Mon problems in 3845 Router....

Jeff

Thank you for the additional information, which is quite helpful. It does show clearly that the output that is flooding your session is not debug output. The messages are severity level 5 messages that are being generated from some setting in your VOIP operation.

As I see it there are several options that you can consider:

- find what it is in the VOIP that is generating these messages about connections established, connections torn down, and history and turn this logging off.

- set the normal logging severity level for monitor to level 4. and change it when you really need to see the lower level of logging (realizing that the session will be flooded with output).

- live with this behavior.

HTH

Rick

286
Views
0
Helpful
6
Replies
CreatePlease to create content