Why there is no debug output?

Greeting,
No output is generated when I place the command "debug frame-relay lmi"
I have tried the command "debug all" but nothing generated ... why?

try to type the command : terminal monitor

Similar Messages

  • Anyone Know *Why* There's No HDV Output Over FW?

    Hi
    Seeing as FCP 6 can ingest and play (via Cinema Desktop) HDV/ MPEG2 fine, does anyone know what the technical reason is that it can't stream playback (after rendering edits if need be) or lay back to HDV tape via the built in FW port?
    After all it's just a 25mbps data stream right?
    Are there just too many HDV formats? Or is it a matter of support still coming?
    Thanks for any illumination
    Lee

    When you're editing DV, the DV stream is converted to analog for viewing externally by the camera/deck/box you're using connected to the FW port on your Mac... so the problem here isn't that FCP can't do it... (it never could and probably never will) . The problem is that the hardware to do this isn't in any HDV device... Bet it's not cheap either. HDV is an MPEG stream, and to decode that in real time converting it to analog would take a LOT of heavy lifting... expensive heavy lifting.
    I'd suggest that you get a capture card that will do this... I'd look right at a Kona LH series card. Better yet, if you have an intel Mac, is an Io HD for the job. Capture as ProRes instead of HDV, and you'll find the whole system is faster, and graphics look a ton better.
    Jerry

  • Stupidly easy - trace source to debug output inunit test...

    I'm convinced that this is stupidly easy, but I cant figure it out...
    I have a class with "TraceSource "classname" and in debugging it work fine, I see the output in the "output" window, however when running unittests I only see "debug.Write" output...
    What am I missing... do I need to add a listener route or something?!
    - sure I'm noJedi but that's no reason to stop trying to make stuff levitate! -
    to clarify...this UnitTest:
    [TestMethod()]
    public void TestLogging()
    System.Diagnostics.Debug.WriteLine("this is a debug writeline");
    System.Diagnostics.Trace.WriteLine("this is a Trace writeline");
    var ts = new System.Diagnostics.TraceSource("classname");
    ts.TraceInformation("this is a ts.TraceInformation");
    throw new AssertInconclusiveException();
    outputs this:
    Test Name: TestLogging
    Test Outcome: Skipped
    Result Message: Exception of type 'Microsoft.VisualStudio.TestTools.UnitTesting.AssertInconclusiveException' was thrown.
    Result StandardOutput:
    Debug Trace:
    this is a debug writeline
    this is a Trace writeline
    Now... for SOME reason, THIS is NOT outputing to the DebugOutput either... when I step through the TEST...
    however stepping through code NOT in unit test does put stuff in the debug output window...
    What am I missing... why is the TraceSource not outputting... I can see in step through that the DefaultTraceListener is there (its the only listener) and I was under the impression that it directed output to the DebugOut output stream... is this not what
    I think it is...?!

    Hi Jack,
    I think you are correct in that my expectations were wrong.
    1) stepping through "SwitchLevel" is "Off", in the unit test, which is problematic.
    turning it on (to All) starts logging, but ONLY when I manually add a CONSOLETraceListener (and set the route to debug error stream to true)
    2) the doco you've pointed me at was what I was reading, but I think I read/misread it differently than you...
    I think its this that threw me:
    •A DefaultTraceListener emits Write and WriteLine messages to the OutputDebugString and to the Debugger.Log method. In Visual Studio, this causes the debugging messages to appear in the Output window. Fail and failed Assert messages also emit to the OutputDebugString Windows API and the Debugger.Log method, and also cause a message box to be displayed. This behavior is the default behavior for Debug and Trace messages, because DefaultTraceListener is automatically included in every Listeners collection and is the only listener automatically included.
    to my thinking this means that by default a "Default -> aka Debug (when DEBUGGGING)" is created for you always, and therefore in the ABSENCE of config stuff, this would be perfect for UNITTESTING - therefore TraceSource with nothing but a name
    should effectively produce the same output as "Debug.WriteLine"...
    that was my thinking, but it looks like even with 'SourceLevel.All" you still need to fiddle with it...
    Thanks for your input, for now, I've resolved this by adding the above stuff so that my existing TraceSources are at least outputting stuff in my tests so I can see more of what is going on without having to change my "TraceSource" calls to "Debug"
    calls everywhere.
    - sure I'm noJedi but that's no reason to stop trying to make stuff levitate! -

  • Filtering debug output from CUBE

    Hi all
    I'm trying to filter the output of the debug command "debug ccsip messages"
    This is my reference
    http://docwiki.cisco.com/wiki/Cisco_IOS_Voice_Troubleshooting_and_Monitoring_--_SIP_Debug_Output_Filtering_Support
    This is what I've done:
    ---snip--
    TR-47-0005.NEV#sh call filter match-list 1
      outgoing called-number XXXXXXXX
    debug condition match-list is set to EXACT_MATCH
    TR-47-0005.NEV#term mon
    TR-47-0005.NEV#sh debugging
    CCSIP SPI: SIP Call Message tracing is enabled  (filter is ON)
    TR-47-0005.NEV#
    --snip--
    It still gives me full debug output. Weather I go for "incoming called-number", "incoming calling-number", "outgoing called-number", "outgoing calling-number" or if I set the debug condition to "partial_match".
    Why is that?
    CUBE: 3945G
    IOS: c3900-universalk9-mz.SPA.152-4.M1.bin
    /Tony

    I have same problem, but only explanation I can find for this behavior is this:
    "Some debug output generated during a call may not have GUID information. These debugs, represented by /xxxxxxxxxxxx/ characters in the debug header, are not filtered and always appear."
    From my output there are lot of calls that have no GUID, even some calls that have GUID but NOT match condition appears in debug... Some people reported that they managed to work with diferent IOS, but for me it never worked on 3-4 versions of firmware.
    For me, best alternative for filtering is to use http://translatorx.cisco.com/
    Veselin

  • Cisco 1310 Roam Reason (Debug Output Possible?)

    I have some 1310s. One is in WGB mode.  It roams between the other Access Points that are in LAP mode.
    What I need to know is if there is a way to debug WHY the WGB roams.  Is there a debug that I can apply that will output the reason for the roam?  Usually it would be due to signal level change but there are other reasons as well.
    Hopefully this is an easy one. I keep alternating between associated access points and I can't figure out why.
    I have figured out that I can put the bridge in Install Mode to get an output of the RSSI level of the associated AP, but this does not tell my WHY the roam took place.
    Thanks!
    James

    Hi James,
    Here is the show command which will tel us about the roam history.. But not a debugging output though..
    show client roam-history
    >> As such there is no debug that give us just the Roam details.. Debug client will provide very good info..
    >>  I think we can manually set the channel on that LWAPP to something so  that the WGB will associate to that.. or if the TX power iscausing the  issue, then playing around with the TX power on the LWAPP may help us.
    Regards
    Surendra

  • Debug output interpretation

    It would be great if there were more guides that would help with the interpretation of debug output.
    On a similar note - I see in the Debug Master Reference for IOS gives examples and some explanation to these. It would be good if there was example output and some explanation for the PIX/ASA guides as well.

    Hi Cameron,
    Thanks for your feedback and sorry it's taken us awhile to research this.
    If you haven't already checked the debug section of the Cisco ASA 5500 Series Command Reference http://www.cisco.com/en/US/docs/security/asa/asa82/command/reference/d1.html, you may find some useful information there, but admittedly the level of detail varies from command to command. Historically, product management has preferred to have Cisco TAC assist customers in debugging because of the performance impact on the system. Our understanding is that this is why self-sufficient debug documentation has not been a priority.
    However, we have passed your comment along to the ASA/PIX group and it will be considered in the next reevaluation of documentation scope.
    Hilde
    Technical Writer

  • Debugging output not appearing

    I recently absorbed the task of supporting our CF MX 6.1
    server. We have an app that we need to debug - the developer asked
    us to add her IP address to the "Debugging IP Addresses" list. I
    turned on debugging and added her IP address to the list, but
    debugging output is not displaying; this is true even when you run
    the CF app on the server running CF. The steps I took are as
    follows:
    - In CF Administrator, checked Enable Robust Exception
    Information and Enable Debugging. Submitted changes and got msg
    Server has been updated successfully.
    - Added developer's IP address to the list of debugging IP
    addresses. She couldn't see the debug output. Neither could I.
    - Restarted CF server. No change.
    - Rebooted server box. No change.
    - Tried removing all IP addresses from list. Debugging input
    then shows for everyone.
    One thing of note regarding the setup of the server is that
    IE has "Internet Explorer Enhanced Security Configuration" enabled
    - don't know if this would have any impact. I'd also tried adding
    the local IP address of my machine (I'm on the same LAN as the
    server), and I got no debug info on my machine. Our whole LAN,
    including the CF Server's box, is behind an ISA server, but of
    course that wouldn't have any impact on the local server, and I
    don't *think* it would affect machines on the LAN, but I'm not
    certain of this.
    Showing the debug info to everyone is not an option, so we
    need to get the IP address filtering working. I've looked at the
    Windows event logs, the CF logs, and these forums, and can't find
    any helpful info.
    Server config:
    Windows Server 2003 (Standard Ed.) SP1
    ColdFusion MX 6.1 (6,1,0,63958) Standard
    Any suggestions would be very much appreciated.

    I figured out the problem - it turns out that even our LAN
    traffic goes through our ISA server, and the ISA server passes its
    IP address to IIS, so CFMX is seeing all traffic as coming from the
    same IP address - the LAN address of the ISA server. Adding that
    turned it on for everyone, so it seems that the solution lies in
    changing the config of the ISA server to pass through IP addresses.
    See post by "Smiley Dave" titled "Debug IP Addresses" for a little
    more info, though there's no info in that thread that he ever
    actually got it working.

  • Why there is a error in this query ?

    why there is a error in this query ?
    declare
    v_exist pls_integer;
    v_search varchar2(255) := '175';
    v_sql varchar2(255);
    begin
    for s in
    (select table_name, column_name
    from user_tab_columns
    where data_type like '%CHAR%'
    order by table_name, column_name)
    loop
    v_sql := 'select count(*) from '||s.table_name||
    ' where instr('||s.column_name||',' || CHR(39)|| v_search|| CHR(39) ||') > 0';
    execute immediate v_sql into v_exist;
    if v_exist > 0 then
    dbms_output.put_line(s.table_name||'.'||s.column_name||' matches the string.');
    end if;
    end loop;
    end;
    Error:
    The following error has occurred:
    ORA-00933: SQL command not properly ended
    ORA-06512: at line 14
    Edited by: user575089 on Dec 23, 2009 4:14 AM
    Edited by: user575089 on Dec 23, 2009 4:14 AM

    See, Right now i am in schema and see below :
    set serveroutput on;
    declare
    v_exist pls_integer;
    v_search varchar2(255) := 'SCOTT';
    v_sql varchar2(255);
    begin
    for s in
    (select '"'||table_name||'"' table_name,'"'||column_name||'"' column_name
    from user_tab_columns
    where data_type like '%CHAR%'
    and table_name not like '%$%'
    order by table_name, column_name)
    loop
    v_sql := 'select count(*) from '||s.table_name||' where instr('||s.column_name||',' || CHR(39)|| v_search|| CHR(39)||') > 0';
    --dbms_output.put_line(v_sql);
    --execute immediate v_sql;
    execute immediate v_sql into v_exist;
    if v_exist > 0 then
    dbms_output.put_line(s.table_name||'.'||s.column_name||' matches the string.');
    end if;
    end loop;
    end;
    "EMP"."ENAME" matches the string.
    "EXCEPTIONS"."OWNER" matches the string.
    "FLOW_TABLE"."OBJECT_OWNER" matches the string.
    "MYEMP"."ENAME" matches the string.
    PL/SQL procedure successfully completed.
    I am getting output; that i search "SCOTT" word in my search string.

  • Why can't I debug my JSF Portlet application after inserting an IFrame

    Hi,
    1) I created a jsf portlet application
    2) I add a button in my jsf portlet application
    3) I can debug my button's action method
    4) Now I open my jsp editor and add an iframe
    <iframe height="500" id="ifWindow" name="ifWindow"/>
    5) I try to debug my button's action method but the debug cursor never reaches it like in step 3
    6) I added a messageGroup but nothing appears there
    7) I monitored "C:\Program Files\Sun\Creator2_1\SunAppServer8\domains\creator\logs\server.log" and nothing appears there
    Is this a bug in Java Studio Creator or is there a problem with iframe in jsf portlet applications?
    Why can't I debug a jsf portlet application if I put an iframe?
    Has anyone got this to work in their jsf portlet application? What can I do to debug this simple application?
    Thanks,
    Marc

    Hi,
    I figured it out. I can debug my jsf application if I placed the iframe outside the <ui:form> element. If it's inside, I cannot debug the application. Are there any books or tutorials that I can read to get rules like this in JSF development?

  • Why there r two functions (do post & do get)

    why there r two functions doget() & dopost() while any code can run in any of them and give me the same result.
    sure, here is difference but what this difference ?
    thnx in advance

    thnx shudha
    this thread is very good, i pasted it here to clear the vision for otheres too:
    There are two points between GET and POST
    01) Amount of information u can get.
    02) Post is secure for getting Passwords and credit cards numbers.
    GET puts the form values into the URL string. GET is limited to about 256 characters (usually a browser limitation) and creates really ugly URLs.
    POST allows you to have extremely dense forms and pass that to the server without clutter or limitation in size. e.g. you obviously can't send a file from the client to the server via GET.
    Below lines are from http://www.microsoft.com/windows2000/techinfo/reskit/en/iisbook/c06_the_difference_between_get_and_post.htm
    QUOTE
    The GET method, which was used in the example earlier, appends name/value pairs to the URL. Unfortunately, the length of a URL is limited, so this method only works if there are only a few parameters. The URL could be truncated if the form uses a large number of parameters, or if the parameters contain large amounts of data. Also, parameters passed on the URL are visible in the address field of the browser�not the best place for a password to be displayed.
    The alternative to the GET method is the POST method. This method packages the name/value pairs inside the body of the HTTP request, which makes for a cleaner URL and imposes no size limitations on the form�s output. It is also more secure.
    UNQUOTE
    Hope abv will help.

  • Keyboard Manager (under Windows XP) spamming System Debug Output

    When running Windows XP, the Boot Camp keyboard manager (kbdmgr.exe) spams the system debug output every 500 ms with a message like "0.620690".
    This is inconvenient for a developer. Often I need to check out debug output in order to accomplish some task. But as soon as I start a Debug viewer application it gets flooded with that kbdmgr messages. That is more an annoyance than a problem.
    Is there a way to tell Keyboard Manager to start and remain silent?

    Yes, running the 2.1 drivers. KbdMgr.exe says it is 2.0.2.44 (exe version/build number) and Boot Camp systray app says it is 2.1 Build 210A12. Took another screenshot showing these version numbers:
    http://picasaweb.google.com/rholdorf/BootCamp/photo#5219317221537472034
    Yes, you are right. I am filtering out those messages. The sad side is that I have to do that once each boot. And I did that so many times that I got really annoyed.

  • No debug output displayed on 3745 while SSH or Telnet

    IOS 12.3(4)T4 on 3745.
    While Telnet, SSH or console into router we see no debug output even after turning Terminal monitor, we can only see the show outputs, etc. While consoled into the 3745 we see nothing there is No prompt or any messages at all.
    We tried replacing the console cable and placed it on different PCs or laptop still no go. I was thinking of reloading the router tomorrow night, but want to check if anyone has come across this problem. It was all working in the past without any changes.
    Is there like a command i need to add, etc. But i am 100% sure its all good on the 3745.
    Cheers!
    -Yavuz

    Try 'logging console'
    'sh logg' will show what is currently being logged, look for this line to see what is being logged to the console:
    Console logging: level debugging, 49 messages logged, xml disabled, filtering disabled
    Hope this helps

  • Recurring CFMX 7.02 debug output

    Hi,
    I'm trying some stuff with CFMX - got some knowledge with CF
    5.0. When I save the *.cfm site and try it in a brower everything
    is fine if I do not have an error (e.g. misspelling CF command like
    XMLElementNew). But... if I have a syntax mistake I got a big error
    message (as expected). When I correct the error in the cfm-file and
    retry within... 2 or 3 minutes... I get exactly the same error
    message with exactly the same debugging output... When I alter the
    page and have no "syntax mistake" all changes are shown by the next
    browser refresh...
    Is there something I can do to elemenate this "error
    caching?". It is very annoeing and blocking my debug and
    development process. I have no big experiances with CFMX Admin (I
    know how to add a database and set a Debug-IP... that's it). Does
    somebody know about this "problem?". I have no clew...
    thanks
    Michael

    Chances are you have the Admin set to cache files - go
    through the settings and turn off caching. Also, if you use MSIE,
    do not use "automatic" browser caching either, especially as a
    developer - since this will generally result in always pulling a
    cached file.

  • Strange access list debug output

    I have a router interface configured with the following access list:
    access-list 101 permit tcp any any eq 23
    access-list 101 deny ip any any
    effectively, telnet is allowed and all other protocols are denied. when I start a debug on this access-list (debug ip packet list 101 detailed) and start telnetting to the router, everything works (as it should). But when I look with "show ip access list" I see there are about 30 matches on the "...eq 23" rule, which is correct, but there are also around 30 matches on the deny ip any any rule. The debug output shows only port 23 traffic and return traffic.
    My question: what packets hit the "deny ip any any" rule when starting a telnet session?

    Hi
    Could be a name resolution issue but the easiest way to check would be to change your second line in the access-list to
    access-list 101 deny ip any any log
    HTH
    Jon

  • Excessive SPA112 debug output

    As a provider of VoIP related services we often use the debug output to help us troubleshoot problems, however, on the latest firmware version simply lifting the handset to go off hook and dialing a phone number produces over 300 messages at Debug Level 3. That's the device getting warmed up as once a call connects there are almost as many debug messages as there are RTP packets.
    It would be great if the Cisco engineers could trim the number of messages being sent out

    Wrong forum, post in "small business voice - ATA and adapters". You can move your post using the actions panel on the right.

Maybe you are looking for