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

Similar Messages

Cisco 1310 Roam Settings

I am trying to optimize my roam settings on a Cisco 1310 operating in WGB mode. The WGB will roam around and connect to various 1310s configured in LAP mode.
There are some optional settings that can be set including changing the beacon retries, data retries and also the RSSI level to force the WGB to roam if the RSSI reaches a certain level.
Does anyone know of any issues with these settings? For instance, I run my network at 9Mbps and want to force a roam when the RSSI reaches -77dB or worse.
Is it better to force this parameter or to just use default Cisco settings?
Thanks for any help you can provide. Cisco does detail the changes you can make but they don't go into much detail about the reasons for making changes to these options.
James

It depends a lot on the moving speed of the device. We've seen 10km/h WGBs and 80km/h WGBs mounted on trains.
It also depends on the coverage density. I never saw 2 situations where the same settings would work. It's more like a "try and see if it gives good results".

ISDN BRI - debug output

Hi,
I am having follwoingg output of debug ISDN commands. I am same output for many routers. ( unfound b cahnnel).
What could be the reason ? It is unable to bring up the interface. It doesnt seem to be IOS problem as same IOS is working at other places. Can it be a problem with Service provider some settings in ISDN switch ?
Debug output is
ISDN BR0 EVENT: process_rxstate: ces/callid 1/0x8008 calltype 1 HOST_DISCONNECT_ACK Nov 19 09:07:14 CET: ISDN BR0 **ERROR**: host_disconnect_ack: Unfound B-channel on Disconnect_Ack call id 0x8008.
Thanks in advance

Hey ,
Here are the codes for disconnect . Becoz i dont see ur complete output after ping + debug q931 -- kindly check the code in the following link.
if more help needed ..paste the above mentioned + sh isdn status.
Suspect a Telco issue. <<
http://www.cisco.com/warp/public/129/isdn_disc_code.html#
rate the post if helps ....

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

Firmware crash on cisco 1310 Bridge while upgrade to higher version

Dear experts,
My cisco 1310 Bridge old firmware C1310-K9W7-tar.123-8.jea3 is crash while i try to upgarade to the higher version C1310.K9W7-tar.124.10b.jda2 via HTTP service upgrade, any advise to get back the firmware.
rgds,
woo.

It appears that you are assigning IP address properly. For some reason we are not getting a response from TFTP server. This is typically one of 2 things:
1. Firewall on the TFTP server workstation
2. Connectivity issue between AP and TFTP server
I would check firewall settings on the TFTP workstation. Are you connecting the AP to the workstation directly or through a switch? If it is through a switch, you could plugin a different workstation to the AP switchport to make sure it could reach the server as well.
-Pat

Connection loss of cisco 1310 bridge.

Hi Experts,
I have cisco 1310 bridge with IOS version Version 12.3(7)JA5. Sometimes bridges are disconnecting by showing the following error message.
*Mar 1 01:22:21.856: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 003a.99eb.cc00 Reason: Previous authentication no longer valid
*Mar 1 01:22:22.115: %DOT11-4-MAXRETRIES: Packet to client 003a.99eb.cc00 reached max retries, removing the client
*Mar 1 01:22:26.414: %DOT11-4-MAXRETRIES: Packet to client 003a.99eb.cc00 reached max retries, removing the client
*Mar 1 01:22:26.484: %DOT11-6-ASSOC: Interface Dot11Radio0, Station SNUDH1BRIDGE 003a.99eb.cc00 Associated KEY_MGMT[NONE]
*Mar 1 01:22:27.386: %DOT11-4-MAXRETRIES: Packet to client 003a.99eb.cc00 reached max retries, removing the client
*Mar 1 01:22:27.388: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 003a.99eb.cc00 Reason: Previous authentication no longer valid
*Mar 1 01:22:30.831: %DOT11-4-MAXRETRIES: Packet to client 003a.99eb.cc00 reached max retries, removing the client
*Mar 1 01:22:31.170: %DOT11-4-MAXRETRIES: Packet to client 003a.99eb.cc00 reached max retries, removing the client
*Mar 1 01:22:31.786: %DOT11-4-MAXRETRIES: Packet to client 003a.99eb.cc00 reached max retries, removing the client
*Mar 1 01:22:31.854: %DOT11-6-ASSOC: Interface Dot11Radio0, Station SNUDH1BRIDGE 003a.99eb.cc00 Associated KEY_MGMT[NONE]
*Mar 1 01:22:33.277: %DOT11-4-MAXRETRIES: Packet to client 003a.99eb.cc00 reached max retries, removing the client
*Mar 1 01:22:33.279: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 003a.99eb.cc00 Reason: Previous authentication no longer valid
*Mar 1 01:22:35.760: %DOT11-4-MAXRETRIES: Packet to client 003a.99eb.cc00 reached max retries, removing the client
*Mar 1 01:22:36.456: %DOT11-4-MAXRETRIES: Packet to client 003a.99eb.cc00 reached max retries, removing the client
*Mar 1 01:22:37.264: %DOT11-4-MAXRETRIES: Packet to client 003a.99eb.cc00 reached max retries, removing the client
*Mar 1 01:22:37.356: %DOT11-6-ASSOC: Interface Dot11Radio0, Station SNUDH1BRIDGE 003a.99eb.cc00 Associated KEY_MGMT[NONE]
*Mar 1 01:22:39.198: %DOT11-4-MAXRETRIES: Packet to client 003a.99eb.cc00 reached max retries, removing the client
*Mar 1 01:22:39.200: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 003a.99eb.cc00 Reason: Previous authentication no longer valid
*Mar 1 01:22:39.518: %DOT11-4-MAXRETRIES: Packet to client 003a.99eb.cc00 reached max retries, removing the client
*Mar 1 01:22:39.771: %DOT11-4-MAXRETRIES: Packet to client 003a.99eb.cc00 reached max retries, removing the client
*Mar 1 01:22:42.093: %DOT11-4-MAXRETRIES: Packet to client 003a.99eb.cc00 reached max retries, removing the client
*Mar 1 01:22:43.580: %DOT11-4-MAXRETRIES: Packet to client 003a.99eb.cc00 reached max retries, removing the client
Once it is deassossiated, ihave to manually restart the bridges. How can avoid manual restarting so it would automatically associate after some time.
Also time is getting changed after restarting. Please help me to solve this problems.
Regards,
naisam

Hi,
Following are the answers for your questions.
How often does this happen ?
This is happnenig two or three times in a day and mostly at eavening when the data traffic is high.
What is the distance between the bridges and RSSI ?
Distance is near to 600 mtr and RSSI is continously keep on changing between -51 dBM to -75dBM
Did this ever work without this issue or is this a new install ?
This installed one year before as a back up to my fiber link. This problem started recently only.
Thanks,
Naisam

802.11 1310 Roam Log Help

I am trying to determine if my roaming is happening as it should. Sometimes it seems that the debug output shows a reassociation instead of a roam. That matters because with CCKM I think a reassociation requires reauthentication where as a Roam is practically seamless.
Here is the output from the log. Take a look and note the two differences when it connects.
Mar 11 03:41:23.229: %DOT11-4-UPLINK_DOWN: Interface Dot11Radio0, parent lost: Signal strength too low
Mar 11 03:41:23 172.22.0.29 16335: Mar 11 03:41:23.230: 22AB287A-0 Uplink: Lost AP, Signal strength too low
Mar 11 03:41:23 172.22.0.29 16336: Mar 11 03:41:23.231: 22AB294D-0 Uplink: Wait for driver to stop
Mar 11 03:41:23 172.22.0.29 16337: Mar 11 03:41:23.231: 22AB2A00-0 Uplink: Enabling active scan
Mar 11 03:41:23 172.22.0.29 16338: Mar 11 03:41:23.232: 22AB2A1A-0 Uplink: Scanning
Mar 11 03:41:24 172.22.0.29 16339: Mar 11 03:41:23.234: 22AB3B26-0 Uplink: Rcvd response from 0026.0b10.c4c0 channel 11 3042
Mar 11 03:41:24 172.22.0.29 16340: Mar 11 03:41:23.240: 22AB5347-0 Uplink: dot11_uplink_scan_done: rsnie_accept returns 0x0 key_mgmt 0x409600 encrypt_type 0x200
Mar 11 03:41:24 172.22.0.29 16341: Mar 11 03:41:23.240: 22AB5381-0 Uplink: ssid CDL1-B auth leap
Mar 11 03:41:24 172.22.0.29 16342: Mar 11 03:41:23.241: 22AB5393-0 Uplink: cut wpa_ie AKMs from 2 to 1
Mar 11 03:41:24 172.22.0.29 16343: Mar 11 03:41:23.241: 22AB53A4-0 Uplink: set wpa_ie AKM to 0x409600 assoc req
Mar 11 03:41:25 172.22.0.29 16344: Mar 11 03:41:23.241: 22AB53B8-0 Uplink: copy wpa_ie fields after AKM - 2 bytes
Mar 11 03:41:25 172.22.0.29 16345: Mar 11 03:41:23.242: 22AB53CA-0 Uplink: try 0026.0b10.c4c0, enc 200 key 6, priv 1, eap 11
Mar 11 03:41:25 172.22.0.29 16346: Mar 11 03:41:23.243: 22AB53E7-0 Uplink: Authenticating
Mar 11 03:41:25 172.22.0.29 16347: Mar 11 03:41:23.247: 22AB6B52-0 Uplink: Associating
Mar 11 03:41:25 172.22.0.29 16348: Mar 11 03:41:23.251: %DOT11-4-UPLINK_ESTABLISHED: Interface Dot11Radio0, Associated To AP AP2114-B 0026.0b10.c4c0 [CCKM FastRoaming]
Mar 11 03:41:26 172.22.0.29 16349: Mar 11 03:41:23.253: 22AB7FD2-0 Uplink: Fast CCKM re-authenticate
Mar 11 03:41:30 172.22.0.29 16350: Mar 11 03:41:30.229: %DOT11-4-UPLINK_DOWN: Interface Dot11Radio0, parent lost: Signal strength too low
Mar 11 03:41:30 172.22.0.29 16351: Mar 11 03:41:30.229: 231645CE-0 Uplink: Lost AP, Signal strength too low
Mar 11 03:41:30 172.22.0.29 16352: Mar 11 03:41:30.229: 231646A2-0 Uplink: Wait for driver to stop
Mar 11 03:41:30 172.22.0.29 16353: Mar 11 03:41:30.231: 23164BE0-0 Uplink: Enabling active scan
Mar 11 03:41:30 172.22.0.29 16354: Mar 11 03:41:30.232: 23164C04-0 Uplink: Scanning
Mar 11 03:41:31 172.22.0.29 16355: Mar 11 03:41:30.235: 23165F41-0 Uplink: Rcvd response from 0026.0b10.c4c0 channel 11 390
Mar 11 03:41:31 172.22.0.29 16356: Mar 11 03:41:30.242: %DOT11-4-UPLINK_ESTABLISHED: Interface Dot11Radio0, Associated To AP AP2114-B 0026.0b10.c4c0 [CCKM FastRoaming]
Mar 11 03:41:31 172.22.0.29 16357: Mar 11 03:41:30.242: 23167797-0 Uplink: Same as previous, send null data packet
Mar 11 03:41:31 172.22.0.29 16358: Mar 11 03:41:30.243: 231677BE-0 Uplink: Done
Why does it seem the second roam took so many fewer events? The second roam is like instantaneous.

Here is the output from a log last night. My question is why I would lose my connection and then reassociate with the same access point time and again.
Could it be interference knocking my signal too low?
See the output below:
Mar 10 03:43:28 172.22.0.45 9875: Mar 10 03:43:28.728: %DOT11-4-UPLINK_ESTABLISHED: Interface Dot11Radio0, Associated To AP AP3302-B 0024.c43b.c7b0 [CCKM FastRoaming]
Mar 10 03:43:28 172.22.0.45 9876: Mar 10 03:43:28.729: A4AB0BC4-0 Uplink: Fast CCKM re-authenticate
Mar 10 03:43:46 172.22.0.45 9877: Mar 10 03:43:47.706: %DOT11-4-UPLINK_DOWN: Interface Dot11Radio0, parent lost: Signal strength too low
Mar 10 03:43:47 172.22.0.45 9878: Mar 10 03:43:47.707: A5CD788D-0 Uplink: Lost AP, Signal strength too low
Mar 10 03:43:47 172.22.0.45 9879: Mar 10 03:43:47.707: A5CD796A-0 Uplink: Wait for driver to stop
Mar 10 03:43:47 172.22.0.45 9880: Mar 10 03:43:47.708: A5CD7A08-0 Uplink: Enabling active scan
Mar 10 03:43:47 172.22.0.45 9881: Mar 10 03:43:47.709: A5CD7A1D-0 Uplink: Scanning
Mar 10 03:43:47 172.22.0.45 9882: Mar 10 03:43:47.711: A5CD8B0B-0 Uplink: Rcvd response from 0024.c43b.c7b0 channel 11 656
Mar 10 03:43:47 172.22.0.45 9883: Mar 10 03:43:47.717: %DOT11-4-UPLINK_ESTABLISHED: Interface Dot11Radio0, Associated To AP AP3302-B 0024.c43b.c7b0 [CCKM FastRoaming]
Mar 10 03:43:47 172.22.0.45 9884: Mar 10 03:43:47.718: A5CD9FAF-0 Uplink: Compare1 0024.c43b.c7b0 - Rssi 54dBm, Hops 0, Count 0, load 0
Mar 10 03:43:48 172.22.0.45 9885: Mar 10 03:43:47.718: A5CD9FE9-0 Uplink: Compare2 0024.c43b.c6f0 - Rssi 42dBm, Hops 0, Count -1, load -4
Mar 10 03:43:48 172.22.0.45 9886: Mar 10 03:43:47.723: A5CDA031-0 Uplink: Compare1 0024.c43b.c7b0 - Rssi 54dBm, Hops 0, Count 0, load 0
Mar 10 03:43:48 172.22.0.45 9887: Mar 10 03:43:47.723: A5CDA050-0 Uplink: Compare2 0024.c43b.c6f0 - Rssi 42dBm, Hops 0, Count -1, load -4
Mar 10 03:43:48 172.22.0.45 9888: Mar 10 03:43:47.723: A5CDA315-0 Uplink: Same as previous, send null data packet
Mar 10 03:43:48 172.22.0.45 9889: Mar 10 03:43:47.724: A5CDA335-0 Uplink: Done
Mar 10 03:43:48 172.22.0.45 9890: Mar 10 03:43:48.037: del client 0024.c43b.c6f0
Mar 10 03:43:58 172.22.0.45 9891: Mar 10 03:43:59.706: %DOT11-4-UPLINK_DOWN: Interface Dot11Radio0, parent lost: Signal strength too low
Mar 10 03:43:59 172.22.0.45 9892: Mar 10 03:43:59.707: A68518C9-0 Uplink: Lost AP, Signal strength too low
Mar 10 03:43:59 172.22.0.45 9893: Mar 10 03:43:59.707: A68519A7-0 Uplink: Wait for driver to stop
Mar 10 03:43:59 172.22.0.45 9894: Mar 10 03:43:59.708: A6851A44-0 Uplink: Enabling active scan
Mar 10 03:43:59 172.22.0.45 9895: Mar 10 03:43:59.709: A6851A5A-0 Uplink: Scanning
Mar 10 03:43:59 172.22.0.45 9896: Mar 10 03:43:59.711: A6852C07-0 Uplink: Rcvd response from 0024.c43b.c7b0 channel 11 3795
Mar 10 03:43:59 172.22.0.45 9897: Mar 10 03:43:59.717: %DOT11-4-UPLINK_ESTABLISHED: Interface Dot11Radio0, Associated To AP AP3302-B 0024.c43b.c7b0 [CCKM FastRoaming]
Mar 10 03:43:59 172.22.0.45 9898: Mar 10 03:43:59.718: A6854298-0 Uplink: Same as previous, send null data packet
Mar 10 03:44:00 172.22.0.45 9899: Mar 10 03:43:59.718: A68542BE-0 Uplink: Done
Mar 10 03:44:01 172.22.0.45 9900: Mar 10 03:44:02.706: %DOT11-4-UPLINK_DOWN: Interface Dot11Radio0, parent lost: Signal strength too low
Mar 10 03:44:02 172.22.0.45 9901: Mar 10 03:44:02.707: A6B30157-0 Uplink: Lost AP, Signal strength too low
Mar 10 03:44:02 172.22.0.45 9902: Mar 10 03:44:02.707: A6B30234-0 Uplink: Wait for driver to stop
Mar 10 03:44:02 172.22.0.45 9903: Mar 10 03:44:02.708: A6B302D4-0 Uplink: Enabling active scan
Mar 10 03:44:02 172.22.0.45 9904: Mar 10 03:44:02.709: A6B302E9-0 Uplink: Scanning
Mar 10 03:44:02 172.22.0.45 9905: Mar 10 03:44:02.711: A6B3124D-0 Uplink: Rcvd response from 0024.c43b.c6f0 channel 11 3214
Mar 10 03:44:02 172.22.0.45 9906: Mar 10 03:44:02.717: %DOT11-4-UPLINK_ESTABLISHED: Interface Dot11Radio0, Associated To AP AP3302-B 0024.c43b.c7b0 [CCKM FastRoaming]
I was moving at 10kph at the time but I am just trying to figure out theoretically why the WGB would reassociate with the same AP time and again. I suspect this behaviour is not normal.
James

WLC - 7920 roam reason troubleshooting

Hi,
I have one WLC 4402 (4.1.185) and i have some cisco 7920 . I'm only use local mac filtering.
I also have WCS 4.1 and i tried to generate roam reason report but report didn't show any info.
How can i see in this info in WLC or in WCS.
Best Regards,
MC

Hi,
I didn't saw also PC's roaming. I thought i should I have to config CCKM instead of mac-filtering to see 7920 roam in WLC.
Regards,
MC

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.

Displaying Debug Output?!?

I have done some research on the cfsetting tag, specifically,
the showdebugoutput attribute, and for some reason, I cannot get it
to work.
I am having an issue with part of my site, where, in
development, a particular action page works fine, but in
production, the same action page, given the same input parameters
does not execute successfully.
In production, I am in a shared hosting environment.
Is there a way to turn on debug output if i set a
url.debugoutput = true??
thanks in advance.
sb

First question, have you confirmed with your hosting provider
that you
CAN use debugging? Debugging can be completely disabled from
the
administrator. If so, then no setting of the <cfsetting
...> tag or the
deprecated url.debugoutput query string will ever show
anything.

ISDN debug output

Hi,
I am giving here output of isdn debug command q931 and q921. but I am not in a position to find out what is the problem.
Is it related with serivce provides or with router. I am giving debug output at three different locations.
Pls see the attachment
Thanx in advance.
Subodh

this seems like a physical failure from the looks. (hardware, cabling....)
it could be a configuration error but i've never seen this type of isdn debug output with the typical configuration errors. (could be telco issue at their switch but haven't see this output from a telco idsn issue either)
clearly there is a problem with the router being able to allocate a B channel.
i see you get a TEI assigned. do you ever see MultiFrame Established? (show isdn status)
what version IOS?
please post your configuration if possible so we can see if anything wrong there.

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.

I am in hongkong and i want to reinstall watsapp on iphone4 but my simcard from India is not on roam. Is it possible as I want to retrieve chat history

i am in hongkong and i want to reinstall watsapp on iphone4 but my simcard from India is not on roam. Is it possible as I want to retrieve chat history

Try using wifi to connect. As for retrieving your chat history I'm not familiar with whatsapp

Cisco 1310 Roam Reason (Debug Output Possible?)

Similar Messages

Maybe you are looking for