×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

problem in debugging acccess server

Unanswered Question
Dec 27th, 2005
User Badges:


i am unable to connect ISDN users through access servers there is some problem amoung raduis, access server and billing machine so i felt i need to debug first on access server but when i am going to run debug command then i m getting no output, below is the exams. is this right command? i enabled the debugging but i am unable so see the logs (outputs) so what is missing here. please reply me as soon as possible.


AS5300a#debug aaa ?

accounting Accounting

administrative Administrative

attr AAA Attr Manager

authentication Authentication

authorization Authorization

db AAA DB Manager

id AAA Unique Id

ipc AAA IPC

per-user Per-user attributes

pod AAA POD processing

protocol AAA protocol processing

subsys AAA Subsystem


AS5300a#debug aaa acc

AS5300a#debug aaa accounting

AAA Accounting debugging is on

AS5300a#sh deb

AS5300a#sh debugging

General OS:

AAA Accounting debugging is on


AS5300a#


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
johansens Tue, 12/27/2005 - 02:41
User Badges:
  • Silver, 250 points or more

Check that you are logging to your controlling terminal.. do a "show log" and check that it's enabled, like this:


#sh log

Syslog logging: enabled (10 messages dropped, 154 messages rate-limited, 0 flushes, 0 overruns, xml disabled)

Console logging: level debugging, 8175 messages logged, xml disabled

Monitor logging: level debugging, 0 messages logged, xml disabled

Buffer logging: level debugging, 8328 messages logged, xml disabled

Logging Exception size (4096 bytes)

Count and timestamp logging messages: disabled

Trap logging: level informational, 7800 message lines logged



Here all destinations (except syslog via trap logging) is enabled for level "debugging".


If you are telnet'ing into the box, make sure you run "terminal monitor" to see the messages..


To enable logging of all debug-messages on the telnet session (if it's disabled), do a "logging monitor debugging" in config mode.


Did it help?

Actions

This Discussion