Radio Interface Reset and Shutdown Frequently

As recently new office from end-Sept, we have found that the radio interface reset very frequently which has been  happening about over 15 times within 8 weeks for one AP on average. Some of  those (3 AP so far) got the radio interface down eventually and we need to  reload the AP to make it up again.
the AP model is AIR-LAP1142N-N-K9 and the IOS version is
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:表格內文;
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
st1\:*{behavior:url(#ieooui) }
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:表格內文;
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
c1140-k9w7-mx.124-21a.JA1. Power supply is made from the PoE switch c2960s. Is there any issue related to IOS? or some other factors may cause the issue happen? Any debug command can show the status of AP? Please advice.

Hi Surendra,
Other than IOS, will this radio interface reset and shutdown issue affect by the nearby AP which is not belongs to the same office.
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
Scenario:
The new office gets 2 floors. One is 5/F which has installed 9 APs with different channels and another one is 6/F which has installed 6 APs with different channels as well. We found that there are many events “%DOT11-4-MAXRETRIES: Packet to client reached max retries, removing the client” logged on 5/F and 6/F AP.
We also found that the radio interface reset very frequently which has been happening about over 15 times within 8 weeks for one AP on average. Some of those (3 AP so far) got the radio interface down eventually and we need to reload the AP to make it up again.
Is/ are there any possibility caused by otherenvironmental factors? Please advise.
Best regards,
Bell

Similar Messages

  • Dot11 radio interface reset protocol down

    I have a cisco 1400 that that show interface show int dott1 radio interface reset protocol down. I had a surge in the area and had the problem after. I copied the config over to a new Ap and power injector and the problem persists. The bridge is the non root bridge. I had read a caveat cscea75989 but it said take no action. Take no action is not fixing my problem at this time. Any suggestions would be appreciated. Thanks.

    There are a number of known issues on this. One which sounds similar is CSCea45031. Check if you are hitting the same.

  • My Iphone Will Just Reset And shutdown with out a temp warning or anything.

    My iPhone 4S Will just shut down and reset its;ef with out any warning. Sometime the brightsness will go all the way down before it shuts off. What Should I Do?

    Assuming your iPhone is well charged, place it in recovery mode as described here.  You may have to try this more than once to succeed.
    http://support.apple.com/kb/HT1808

  • I looked at system.log in the system profiler today and see lots of activity at 2 a.m. when I was fast asleep, should I worry? It seems to reset hostname and mentions frequent transitions for interface, looks weird to me (I'm not a teckie!)

    I looked at system.log in the system profiler today and see lots of activity at 2 a.m. when I was fast asleep, should I worry? It seems to reset hostname and mentions frequent transitions for interface, looks weird to me (I'm not a teckie!)
    This is a section:
    May 12 02:05:10 wendy-drapers-macbook configd[14]: setting hostname to "wendy-drapers-macbook.local"
    May 12 02:05:29 wendy-drapers-macbook kernel[0]: Auth result for: 00:26:44:14:17:a3 MAC AUTH succeeded
    May 12 02:05:29 wendy-drapers-macbook kernel[0]: AirPort: Link Up on en1
    May 12 02:05:29 wendy-drapers-macbook mDNSResponder[16]: Note: Frequent transitions for interface en1 (192.168.1.92); network traffic reduction measures in effect
    May 12 02:05:29 macbook configd[14]: setting hostname to "macbook.lan"
    May 12 02:05:31 macbook mDNSResponder[16]: Note: Frequent transitions for interface en1 (FE80:0000:0000:0000:021E:C2FF:FEB3:1A3E); network traffic reduction measures in effect
    May 12 02:05:34 macbook com.apple.launchd[1] (org.samba.nmbd): Throttling respawn: Will start in 5 seconds

    I've been seeing messages exactly like that (and many, many other kinds) in the Console since the first version of OS X.  They look menacing but are harmless.
    You don't need any kind of security software.
    Just surf the web carefully, pay attention to where you're going and don't install anything that you don't recognize.  If you are asked to enter an admin user name and password, DON'T.  Unless you know for sure that you initiated the installation from a known and reliable source (like Apple).
    Mac malware relies on social engineering.  No amount of security/anti-virus, blah, blah, blah software is going to help.

  • Cisco 1142AP Autonomous - Radio interface constantly reset and provides crash file

    Hello All,
    We have 10 Cisco 1142 Access Points currently configured as Autonomous and I'm experiecing very unusual behavior with the 2.4GHz radio interfaces on each of them. The IOS firmware is 15.2.2JB and they're connected to Cisco 2960 PoE switches. I'm not sure what could be causing this problem however it is service impacting and looks bad on me since I don't have a solution for it. One potential fix could be to upgrade the firmware to 15.2.4 but I'm sure if it is a firmware problem. Any advice would help. Here's an excerpt from the AP log:
    Aug 18 14:40:16:  Writing driver stats to flash:/ap_log_r0_0.log..
    Aug 18 14:40:21:
    Aug 18 14:40:21: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    Aug 18 14:40:22: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    Aug 18 14:40:23: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
    Aug 18 14:40:23: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
    Thanks,
    Ali Ibrahim

    You should be able to go in and view teh R0_0.log file.
    there might be something in there that you can do a bug search for.
    HTH,
    Steve

  • Aironet C1140 - Radio Interface Keeps in Reset State

    Hello,
    Recently we noticed that one of our C1142 access points has a radio interface (actually is only happening with the one working in BG, so its dot11radio 0) which is entering in reset state and doesn't leave that state. I've seen an older thread about similar (or equal?) issue but was on a different AP model (C1240 if I remember correctly).
    The radio interface controller information displays in the end a reset code:
    Last radio reset code: 06
    Radio resets - total:1 retries:0 failed:0
       Code/Count: 06/00001
    Although I was not able to find any information about this reset code in Cisco documents (maybe someone knows where I find it?).
    If I try to restart the interface via "shutdown" configuration command it doesn't fix the problem, the workaround that I know of is only by "reload"ing the whole accesspoint.
    Of course while in reset state no client can associate to this interface....
    Did anyone had similar problem? is there any documented BUG related to this?
    Thanks for your time,
    Jean-François Mousinho
    PS: firmware version is 12.4(21a)JA1.

    version information:
    Cisco IOS Software, C1140 Software (C1140-K9W7-M), Version 12.4(21a)JA1, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2009 by Cisco Systems, Inc.
    Compiled Wed 16-Sep-09 18:09 by prod_rel_team
    ROM: Bootstrap program is C1140 boot loader
    BOOTLDR: C1140 Boot Loader (C1140-BOOT-M) Version 12.4(18a)JA3, RELEASE SOFTWARE (fc1)
    TS_Piso8_SulEsq uptime is 3 days, 1 hour, 16 minutes
    System returned to ROM by reload
    System restarted at 10:47:38 Z Tue Sep 14 2010
    System image file is "flash:/c1140-k9w7-mx.124-21a.JA1/c1140-k9w7-mx.124-21a.JA1"
    This product contains cryptographic features and is subject to United...
    cisco AIR-AP1142N-E-K9     (PowerPC405ex) processor (revision B0) with 98294K/32768K bytes of memory.
    Processor board ID FCZ1426W04V
    PowerPC405ex CPU at 586Mhz, revision number 0x147E
    Last reset from reload
    1 Gigabit Ethernet interface
    2 802.11 Radio(s)
    32K bytes of flash-simulated non-volatile configuration memory.
    Base ethernet MAC Address: C8:4C:75:AE:8A:CC
    Part Number                          : 73-11451-08
    PCA Assembly Number                  : 800-30554-06
    PCA Revision Number                  : A0
    PCB Serial Number                    : FOC14233KEB
    Top Assembly Part Number             : 800-31273-04
    Top Assembly Serial Number           : FCZ1426W04V
    Top Revision Number                  : A0
    Product/Model Number                 : AIR-AP1142N-E-K9   
    Configuration register is 0xF
    TS_Piso8_SulEsq#sh inventory
    NAME: "AP1140", DESCR: "Cisco Aironet 1140 Series (IEEE 802.11n) Access Point"
    PID: AIR-AP1142N-E-K9  , VID: V03, SN: FCZ1426W04V
    Country is Portugal.
    Thanks for your time.
    Jean-François Mousinho

  • Cisco Wireless AP radio interface shutdown/Operation Status Down

    Hi,
    I am trying to troubleshoot the cause of the wireless AP 1142 radio shutdown; I was wondering where may be a good place to start on it/possibility of the radio shutting down. Once the radio is shown as down; I would just need to re-enable (disable/enable) it and the status changes to up status. I have attached a screen catpure of the radio interface showning down.
    The AP radios shutting down is intermittent; some APs has their "A/N" radio interface shutdown while others has their "G/N" radio interface shutdown. Not too sure what may most likely be causing it to shutdown?
    Any input is appreciated.
    Thanks.

    Do you have controller ?? if yes then posts out put of sh sysinfo commad.
    Paste the output of sh version command from AP.
    Also check: 
    1. Choose Wireless > 802.11a/n or 802.11b/g/n > Network
    Select the 802.11a (or 802.11b/g) Network Status check box to enable the 802.11a or 802.11b/g band.
    2. Wireless > Access Points > All APs then click on specific AP and make sure admin status is enable.
    Reagrds

  • Output errors and interface resets.

    hi Netpros,
    Any idea as to what could be causing output errors and interfece resets on the radio interfaces .. The output interpreter from Cisco does not show any information about the radio interfaces
    please see this output after clearing the counters
    Dot11Radio0 is up, line protocol is up
    Hardware is 802.11G Radio, address is 0015.c7a8.3d90 (bia 0015.c7a8.3d90)
    MTU 1500 bytes, BW 54000 Kbit, DLY 1000 usec,
    reliability 255/255, txload 1/255, rxload 1/255
    Encapsulation 802.1Q Virtual LAN, Vlan ID 1., loopback not set
    ARP type: ARPA, ARP Timeout 04:00:00
    Last input 00:00:07, output 00:00:00, output hang never
    Last clearing of "show interface" counters never
    Input queue: 0/75/962/0 (size/max/drops/flushes); Total output drops: 181678
    Queueing strategy: fifo
    Output queue: 0/30 (size/max)
    5 minute input rate 4000 bits/sec, 6 packets/sec
    5 minute output rate 1000 bits/sec, 1 packets/sec
    39213813 packets input, 3905641263 bytes, 0 no buffer
    Received 53803 broadcasts, 0 runts, 0 giants, 0 throttles
    0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
    0 input packets with dribble condition detected
    21236022 packets output, 3766719027 bytes, 0 underruns
    11617 output errors, 0 collisions, 25 interface resets
    0 babbles, 0 late collision, 0 deferred
    0 lost carrier, 0 no carrier
    0 output buffer failures, 0 output buffers swapped out
    Any input is much appreciated.

    Let's take a look at what you're worried about: 11,617 output errors divided by 21,236,022 packets output = 0.05% loss. Not really much to worry about there.
    As for the 25 interface resets, that's one reset for every 849,441 output packets. Again, nothing really to worry about, but one does wonder why those numbers are not zero.
    So how about taking a closer look at the following line you reported:
    Input queue: 0/75/962/0 (size/max/drops/flushes); Total output drops: 181678
    Notice in particular the "Input queue drops = 962" and more importantly, the "Total output drops = 181,678". You can find detailed troubleshooting information about these problems at: http://www.cisco.com/warp/public/63/queue_drops.html to help you figure out what the actual problem is and whether or not it can be rectified by fine tuning your parameters.
    FYI: Here is a standard definition of Output related errors: (taken from http://www-commeng.cso.uiuc.edu/uiucnet/reports/glossary.html )
    Output Errors
    - Output errors are the sum of all the output errors that occur on an interface.
    Out Success With Retry Errors
    - Out Success With Retry errors are output errors which indicate that a frame successfully transmitted after one or more collisions. Out Success With Retry Errors are the number of frames that experienced a a collision and retransmit before success. The total collisions divided by the number of Out Success With Retry errors will provide the average number of collisions per packet transmitted with collisions.
    Out of Window Collisions Errors
    - Out of Window Collisions are a type of output error. Out of window collision errors occur when a frame in the process of being transmitted collides with another frame. This error usually occurs either when some interface on the network fails to defer or the network has too many stations. (See Late Collisions.)
    Output Discard Errors
    - Output Discards are output errors that occur when the router has to throw a packet out instead of queuing it for transmission on the Ethernet. Output discard errors usually indicate that the network has more traffic than it can handle. They may also indicate a software discard such as no route to destination.
    Output FIFO Overrun Errors
    - FIFO Overruns are a type of output error. Output FIFO Overruns occur when the output queue in the adapter underflowed while putting a frame on the wire. This problem occurs when the interface is not receiving bits of the frame fast enough.
    Walt

  • After a one week logout and shutdown my macpro 1,1 laptop shows a black screen at startup attempts. The battery is fully charged and both resetting the power manager  and zapping the PRAM have failed to permit startup. What else can I try?

    After a one week logout and shutdown my macpro 1,1 laptop running OSx 10.6.8 shows a black screen at startup attempts. The battery is fully charged and both resetting the power manager  and zapping the PRAM have failed to permit startup. What else can I try?

    Startup – Black screen with cursor
    Startup Issues - Resolve
    Startup Issues - Resolve (2)

  • MW1 - radio resets and restarts the unit

    I just opened the package, tested all functions (pairing, multipoint, radio, playing music etc all working) and then I downloaded almost all Android applications (HTC Desire HD; not rooted; Android 2.3.5) and installed them. It offered me to upgrade (0.1.e.1.5) and I accepted. After restart new functionalities appeared (find phone, call log etc). All are working /except/ the radio!
    Whenever I choose radio function the frequency is set to "00.0 Mhz" and it forces to restarts the unit. All other functions are working perfectly. Having radio set embeded into the unit was one of the main reasons I have chosen this model (even though a simple present doesnt exist).
    PS: when it resets the unit, it shortly goes back to first option set (radio-music-settings) and the other /new/ options (with new icons) appear a bit later.
    What should I do to recover radio option? Any solution?

    Well, as I explained after the "factory reset" I could listen radio (the one embedded in MW1 not radio/music from Bluetooth devices).
    However, there is new problem:
    Pair a mobile phone (mine: HTC Desire HD) - primary pair
    Pair a PC (mine: Win7 pro on HP Probook 4520s + Broadcom 2070 Bluetooth and its software) - secondary pair
    Turn off PC Bluetooth.
    Using options button locate radio and tune in to a station. Make sure that you listen the radio station.
    While listening, turn on Bluetooth on PC.
    After three "pause sound" (which breaks the station sound), observe on MW1 that you cannot hear the station anymore, and all of unit buttons stops working, and display freezes at the station frequency.
    Later, unit displays "SONY" which means it rebooted/reset.
    Now whatever you do you cannot listen radio anymore unless you disable PC driver.
    Additional cases:
    The same reset happened several times when I browsed directories on PC using explorer.exe. This occurred after at most two click sounds (while browsing).
    I suspected about mixer settings and muted system sounds which didn't help
    Any idea? Similar experience?
    MW1 is really well thought device (multipoint + radio + SD card). I wanted to use it to switch between skype/PC and mobile, and when not talking listen to radio without using internet. However, these small bugs makes it "uncomfortable" for both end users and users like me.
    Please, SONY, at least respond to your users...

  • My Refurbished MacBook stops and needs to be shutdown frequently

    My Refurbished MacBook stops and needs to be shutdown frequently and I have no idea what to do about it. I will be in the middle of editing an unsaved document in word when the screen freezes and then announces that it needs to shutdown. Thank you, preemptively.
    Matt B.

    You are describing a kernel panic and you should not be seeing them frequently. Just as an example of typical usage: I use my MacBook about 6 hours a day every day and in the 9 weeks that I've owned this one I have seen no kernel panics at all. Kernel panics can be hardware related but can also be caused by operating system problems.
    Before you progress any further, the first thing you'll want to do is back up your data. Whether you attempt to fix the problem yourself, or let Apple handle it, your drive is going to be wiped. (And if you've installed a RAM upgrade it would be a good idea to remove it because that could be the cause of the panics.)
    If you call AppleCare you're likely to be told to wipe the drive and use the install DVD to return the computer to factory specs. If you have a local AppleStore your genius will (probably) do that for you. If removing the RAM, unplugging all your peripherals, and reinstalling the OS doesn't solve the problem then you'll know your problem is with the computer itself.

  • AP show in WLC but no radio interfaces

    I am have a problem with couple of our APs the model is AIR-LAP1131AG-A-K9 and we have a Cisco 4404 WLC. 2 of them show up on the controller but have no radio interfaces. I have a I have restarted the AP, reset to factory config all to no avail. When I restart or reset it does communicate with the controller, but still no a/b/g/n radios.
    Anyone have any ideas? Here is a snippet from the log when I restart the AP.
    I would appreciate and pointers here.
    Mar 24 14:20:23.948: [ERROR] spam_lrad.c 2016: AP 00:1d:a2:80:75:dc associated. Last AP failure was due to Link Failure
    Mar 24 14:20:23.948 apf_api.c:23237 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.948 apf_api.c:23224 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.947 apf_api.c:23237 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.947 apf_api.c:23224 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.947 apf_api.c:23237 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.947 apf_api.c:23224 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.947 apf_api.c:23237 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.947 apf_api.c:23224 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.947 apf_api.c:23237 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.947 apf_api.c:23224 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.947 apf_api.c:23237 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.947 apf_api.c:23224 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.947 apf_api.c:23237 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.947 apf_api.c:23224 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.946 apf_api.c:23237 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.946 apf_api.c:23224 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.946 apf_api.c:23237 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.946 apf_api.c:23224 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.946 apf_api.c:23237 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.946 apf_api.c:23224 APF-3-INVALID_RADIO_TYPE: Invalid radio type 255 received.
    Mar 24 14:20:23.903: [ERROR] spam_lrad.c 7012: 00:1d:a2:80:75:dc AP Country changed from:() to (US ).
    Mar 24 14:20:23.903: [ERROR] spam_lrad.c 6694: AP 00:1d:a2:80:75:dc: Invalid country code ().
    Mar 24 14:20:23.902: [ERROR] spam_lrad.c 7012: 00:1d:a2:80:75:dc AP Country changed from:() to (US ).
    Mar 24 14:20:23.902: [ERROR] spam_lrad.c 6694: AP 00:1d:a2:80:75:dc: Invalid country code ().

    Hi Rob,
    The WLC version is 4.1.171.0. I have been browsing the conversations here and there seems to a few that are having similar issues. I can't find anything related to this except this:
    CSCsl90841-After you upgrade a controller to software release 4.2.61.0, any access point that does not have region coding (such as the Airespace 1250 access point) is unable to join the controller. An "Invalid country code" message with a country code of 0xFFFF appears in the output of the debug lwapp events enable command.
    Workaround: Downgrade the controller to software release 4.1.
    And I am already on that version. This is rather bizarre. I am working from home for the next few day so I can't physically go pull the AP to look at the codes.
    It does associate with the controller but it just doesn't show any radio interfaces ie, a/b/g/n.
    When I go in and look at that AP on the controller it show everything including the country fine except for the radios. Very confusing.

  • Intermittant radio interface down on 1130 APs

    I am having unified wireless installation, with WiSM on 6500 at central site and around 90 nos of 1130 APs located at remote locations ( over WAN) as well as some APs locate in the same location.
    The APs are configured in WCS, using default AP template.
    Alsomot all APs are showing minor alarms saying " radio interface threshold violated".
    In addition, a major alarm posted frequently on WCS saying "radion interface down".
    Cleints are complaining that they are loosing connectkion momentarily but connected again automatically wo WLAN. But they will have to log in to application programs in such cases.
    a.Does anybody have similar experience, and
    b. What are the best settings for 1130 APs trhat we have to do explicitly in setting up the WCS template ?
    Thanks ,

    Might be due to interference and the fact that RRM is enalbled and the ap's are changing channels causing the radios to shut down temporarily. Either set the channel or try to change the threshold.
    Here is the error info:
    http://www.cisco.com/en/US/docs/wireless/wcs/4.2/configuration/guide/wcsevent.html#wp1139158

  • 1200 AP missing radio interface

    hi i have a 1200 ap and its radio interface is missing. i mean i am uanble to see its radio interface
    I really need this urgently.Anybody can help me

    cisco AIR-AP1231G-A-K9 (PowerPC405GP) processor (revision A0) with 14838K/1536K bytes of memory.
    Processor board ID FOC09501XL4
    PowerPC405GP CPU at 196Mhz, revision number 0x0145
    Last reset from power-on
    1 FastEthernet interface
    1 802.11 Radio(s)
    That was from an AP with the radio installed.
    Your config
    cisco AIR-AP1230B-E-K9 (PowerPC405GP) processor (revision A0) with 14326K/2048K bytes of memory.
    Processor board ID FOC07410KFY
    PowerPC405GP CPU at 196Mhz, revision number 0x00C4
    Last reset from power-on
    Bridging software.
    1 FastEthernet/IEEE 802.3 interface(s)
    32K bytes of flash-simulated non-volatile configuration memory.
    Yours doesn't show a radio module installed,
    You need a radio module

  • 3G interface resets but signal looks good

    Hi All,
      can anyone explain what this means.I have enabled the following debugs. everytime I look at it there is no issue with the signal. But my guess is the router interface is resetting due to the signal. Can anyone explain if its due to 3G signalling
    Router 881G
    CELLULAR:
      DATA debugging is on
      DM debugging is on
      ASYNC debugging is on
      RDM debugging is on
      CALLBACK debugging is on
    PPP:
      PPP authentication debugging is on
      PPP protocol errors debugging is on
      PPP protocol negotiation debugging is on
    BAP:
      BAP negotiation debugging is on
      BAP error debugging is on
    3688676: Mar 29 08:48:33.641 BRU: Ce0 PPP: Outbound ip packet dropped, line protocol not up
    3688677: Mar 29 08:48:33.641 BRU: Ce0 PPP: Outbound ip packet dropped, line protocol not up
    3688678: Mar 29 08:48:33.641 BRU: Ce0 PPP: Outbound ip packet dropped, line protocol not up
    3688679: Mar 29 08:48:33.641 BRU: Ce0 PPP: Outbound ip packet dropped,
    3688700: Mar 29 08:48:36.749 BRU: new DSR value received, 1
    3688701: Mar 29 08:48:36.749 BRU: old value: handshakes->DSR= 1
    3688702: Mar 29 08:48:38.741 BRU: %LINK-3-UPDOWN: Interface Cellular0, changed state to down
    3688703: Mar 29 08:48:38.741 BRU: Ce0 PPP: Sending cstate DOWN notification
    3688704: Mar 29 08:48:38.745 BRU: Ce0 PPP: Processing CstateDown message
    3688705: Mar 29 08:48:49.326 BRU: new DSR value received, 1
    3688706: Mar 29 08:48:49.326 BRU: old value: handshakes->DSR= 1
    3688707: Mar 29 08:48:49.758 BRU: new DSR value received, 1
    3688708: Mar 29 08:48:49.758 BRU: old value: handshakes->DSR= 1
    3688709: Mar 29 08:48:56.582 BRU: %LINK-3-UPDOWN: Interface Cellular0, changed state to up
    3688710: Mar 29 08:48:56.590 BRU: %DIALER-6-BIND: Interface Ce0 bound to profile Di1
    3688711: Mar 29 08:48:56.590 BRU: Ce0 PPP: Sending cstate UP notification
    3688712: Mar 29 08:48:56.594 BRU: Ce0 PPP: Processing CstateUp message
    Cellular0 is up, line protocol is up
      Hardware is 3G Modem-HSPA/UMTS/EDGE/GPRS-850/900/1800/1900/2100MHz / Global
      Description: [cewan-phy]
      MTU 1500 bytes, BW 5760 Kbit/sec, DLY 20000 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation PPP, LCP Open
      Open: IPCP, loopback not set
      Keepalive not supported
      Interface is bound to Di1 (Encapsulation PPP)
      Last input 00:00:00, output 00:00:00, output hang never
      Last clearing of "show interface" counters 2d03h
      Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: Class-based queueing
      Output queue: 0/1000/0 (size/max total/drops)
      30 second input rate 0 bits/sec, 0 packets/sec
      30 second output rate 0 bits/sec, 0 packets/sec
         53671 packets input, 15696493 bytes, 0 no buffer
         Received 0 broadcasts (0 IP multicasts)
         0 runts, 0 giants, 0 throttles
         0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
         62119 packets output, 13733542 bytes, 0 underruns
         0 output errors, 0 collisions, 5 interface resets
         0 unknown protocol drops
         0 output buffer failures, 0 output buffers swapped out
         0 carrier transitions
         DCD=up  DSR=up  DTR=up  RTS=up  CTS=up
    Hardware Information
    ====================
    Modem Firmware Version = K2_0_7_19AP C:/WS/F
    Modem Firmware built = 10/26/09
    Hardware Version = 1.0
    International Mobile Subscriber Identity (IMSI) = 206012210378433
    International Mobile Equipment Identity (IMEI) = 359109030082750
    Integrated Circuit Card ID (ICCID) = 8932002100084586363
    Mobile Subscriber International Subscriber
    IDentity Number (MSISDN) =
    Factory Serial Number (FSN) = D57138003301002
    Modem Status = Online
    Current Modem Temperature = 46 deg C, State = Normal
    PRI SKU ID = 9993165, SKU Rev. = 1.0
    Profile Information
    ====================
    Profile password Encryption level: 7
    Profile 1 = ACTIVE*
    PDP Type = IPv4
    PDP address = <ip address masked>
    Access Point Name (APN) = internet.proximus.be
    Authentication = None
    Username: , Password: 02
    * - Default profile
    Data Connection Information
    ===========================
    Data Transmitted = 10775742 bytes, Received = 12294276 bytes
    Profile 1, Packet Session Status = ACTIVE
            IP address = <ip address masked>
    Profile 2, Packet Session Status = INACTIVE
            Inactivity Reason = Normal inactivate state
    Profile 3, Packet Session Status = INACTIVE
            Inactivity Reason = Normal inactivate state
    Profile 4, Packet Session Status = INACTIVE
            Inactivity Reason = Normal inactivate state
    Profile 5, Packet Session Status = INACTIVE
            Inactivity Reason = Normal inactivate state
    Profile 6, Packet Session Status = INACTIVE
            Inactivity Reason = Normal inactivate state
    Profile 7, Packet Session Status = INACTIVE
            Inactivity Reason = Normal inactivate state
    Profile 8, Packet Session Status = INACTIVE
            Inactivity Reason = Normal inactivate state
    Profile 9, Packet Session Status = INACTIVE
            Inactivity Reason = Normal inactivate state
    Profile 10, Packet Session Status = INACTIVE
            Inactivity Reason = Normal inactivate state
    Profile 11, Packet Session Status = INACTIVE
            Inactivity Reason = Normal inactivate state
    Profile 12, Packet Session Status = INACTIVE
            Inactivity Reason = Normal inactivate state
    Profile 13, Packet Session Status = INACTIVE
            Inactivity Reason = Normal inactivate state
    Profile 14, Packet Session Status = INACTIVE
            Inactivity Reason = Normal inactivate state
    Profile 15, Packet Session Status = INACTIVE
            Inactivity Reason = Normal inactivate state
    Profile 16, Packet Session Status = INACTIVE
            Inactivity Reason = Normal inactivate state
    Network Information
    ===================
    Current Service Status = Normal, Service Error = None
    Current Service = Combined
    Packet Service = HSPA (Attached)
    Packet Session Status = Active
    Current Roaming Status = Home
    Network Selection Mode = Automatic
    Country = BEL, Network = PROXI
    Mobile Country Code (MCC) = 206
    Mobile Network Code (MNC) = 1
    Location Area Code (LAC) = 2603
    Routing Area Code (RAC) = 208
    Cell ID = 20324
    Primary Scrambling Code = 466
    PLMN Selection = Automatic
    Registered PLMN = BEL PROXIMUS , Abbreviated = PROXI
    Service Provider =
    Radio Information
    =================
    Radio power mode = ON
    Current Band = WCDMA 2100, Channel Number = 10588
    Current RSSI = -84 dBm
    Band Selected = Auto
    Number of nearby cells = 1
    Cell 1
            Primary Scrambling Code = 0x1D2
            RSCP = -84 dBm, ECIO = -2 dBm
    Modem Security Information
    ==========================
    Card Holder Verification (CHV1) = Disabled
    SIM Status = OK
    SIM User Operation Required = None
    Number of Retries remaining = 3

    Hi Marco,
        Connection goes down intermittently and it stays up for very long time, more than a day some time or some time certain no of hours. I am not running any ping. I am not sure about the timing it takes between IPCP is completed ("IPCP: State is Open") and the link is closed ("I TERMREQ").
    IOS c880data-universalk9-mz.151-1.T1.bin
    Model 881G
    One of my friend said there is a bug on 881G router IOS not sure about it though, but he hasnt seen my debug output.
    This is the bug he was saying but I am not sure if mine is related to that as my CHAT script dont seem to be time out.
    Problem Code: Error  Messages, Logs, Debugs Software Version: C880DATA-universalk9-mz.151-2. Problem  Details: Customer is running traffic over the 3card in a 881G. It fails however  I can see from "show cell 0 all" that the modem has 3G coverage and a good  signal as the RSSI is good. However the chat script continues to timeout. The  configuration has not changed and it has worked and fails intermi
    Thanks in Advance for your help
    I have attached the debug of the CHAT script when the link goes down and come back.
    3706575: Apr  1 08:51:03.995 BRU: Ce0 PPP: Outbound ip packet dropped, line protocol not up
    3706576: Apr  1 08:51:03.995 BRU: Ce0 PPP: Outbound ip packet dropped, line protocol not up
    3706577: Apr  1 08:51:03.995 BRU: Ce0 PPP: Outbound ip packet dropped, line protocol not up
    3706578: Apr  1 08:51:03.995 BRU: Ce0 PPP: Outbound ip packet dropped, line protocol not up
    3706579: Apr  1 08:51:03.999 BRU: Ce0 PPP: No remote authentication for call-out
    3706580: Apr  1 08:51:03.999 BRU: Ce0 LCP: Event[Timeout-] State[Closing to Closed]
    3706581: Apr  1 08:51:03.999 BRU: Ce0 LCP: Event[DOWN] State[Closed to Initial]
    3706582: Apr  1 08:51:03.999 BRU: Ce0 PPP: Phase is DOWN
    3706583: Apr  1 08:51:04.007 BRU: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cellular0, changed state to down
    3706584: Apr  1 08:51:06.007 BRU: %LINK-5-CHANGED: Interface Cellular0, changed state to reset
    3706585: Apr  1 08:51:06.011 BRU: Ce0 DDR: has total 0 call(s), dial_out 0, dial_in 0
    3706586: Apr  1 08:51:06.011 BRU: %DIALER-6-UNBIND: Interface Ce0 unbound from profile Di1
    3706587: Apr  1 08:51:06.011 BRU: Ce0 PPP: Sending cstate DOWN notification
    3706588: Apr  1 08:51:06.011 BRU: Ce0 PPP: Processing CstateDown message
    3706589: Apr  1 08:51:06.015 BRU: Di1 DDR: No free dialer - starting fast idle timer
    3706590: Apr  1 08:51:07.015 BRU: Di1 DDR: No free dialer - starting fast idle timer
    3706591: Apr  1 08:51:08.015 BRU: Di1 DDR: No free dialer - starting fast idle timer
    3706592: Apr  1 08:51:09.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
    3706593: Apr  1 08:51:10.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
    3706594: Apr  1 08:51:11.083 BRU: %LINK-3-UPDOWN: Interface Cellular0, changed state to down
    3706595: Apr  1 08:51:11.083 BRU: Ce0 PPP: Sending cstate DOWN notification
    3706596: Apr  1 08:51:11.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
    3706597: Apr  1 08:51:11.087 BRU: Ce0 PPP: Processing CstateDown message
    3706598: Apr  1 08:51:12.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
    3706599: Apr  1 08:51:13.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
    3706600: Apr  1 08:51:14.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
    3706601: Apr  1 08:51:15.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
    3706602: Apr  1 08:51:16.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
    3706603: Apr  1 08:51:17.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
    3706604: Apr  1 08:51:18.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
    3706605: Apr  1 08:51:19.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
    3706606: Apr  1 08:51:20.083 BRU: Di1 DDR: No free dialer - starting fast idle timer
    3706607: Apr  1 08:51:21.011 BRU: Ce0 DDR: re-enable timeout
    3706608: Apr  1 08:51:21.083 BRU: Ce0 DDR: rotor dialout [best] least recent failure is also most recent failure
    3706609: Apr  1 08:51:21.083 BRU: Ce0 DDR: rotor dialout [best] also has most recent failure
    3706610: Apr  1 08:51:21.083 BRU: Ce0 DDR: rotor dialout [best]
    3706611: Apr  1 08:51:21.083 BRU: Di1 DDR: Nailing up the Dialer profile [attempt 16]
    3706612: Apr  1 08:51:21.083 BRU: Di1 DDR: Dialer dialing - persistent dialer profile
    3706613: Apr  1 08:51:21.083 BRU: Ce0 DDR: Dialing cause Persistent Dialer Profile
    3706614: Apr  1 08:51:21.083 BRU: Ce0 DDR: Attempting to dial cellprofile1
    3706615: Apr  1 08:51:21.083 BRU: CHAT3: Attempting async line dialer script
    3706616: Apr  1 08:51:21.083 BRU: CHAT3: Dialing using Modem script: cellprofile1 & System script: none
    3706617: Apr  1 08:51:21.083 BRU: CHAT3: process started
    3706618: Apr  1 08:51:21.083 BRU: CHAT3: Asserting DTR
    3706619: Apr  1 08:51:21.087 BRU: CHAT3: Chat script cellprofile1 started
    3706620: Apr  1 08:51:21.087 BRU: CHAT3: Sending string: ATDT*99***1#
    3706621: Apr  1 08:51:21.087 BRU: CHAT3: Expecting string: CONNECT
    3706622: Apr  1 08:51:21.091 BRU: CHAT3: Completed match for expect: CONNECT
    3706623: Apr  1 08:51:21.091 BRU: CHAT3: Chat script cellprofile1 finished, status = Success
    3706624: Apr  1 08:51:23.171 BRU: %LINK-3-UPDOWN: Interface Cellular0, changed state to up
    3706625: Apr  1 08:51:23.171 BRU: Ce0 DDR: Dialer statechange to up
    3706626: Apr  1 08:51:23.175 BRU: %DIALER-6-BIND: Interface Ce0 bound to profile Di1
    3706627: Apr  1 08:51:23.175 BRU: Ce0 DDR: Dialer call has been placed
    3706628: Apr  1 08:51:23.175 BRU: Ce0 PPP: Sending cstate UP notification
    3706629: Apr  1 08:51:23.179 BRU: Ce0 PPP: Processing CstateUp message
    3706630: Apr  1 08:51:23.183 BRU: PPP: Alloc Context [852C2C68]
    3706631: Apr  1 08:51:23.183 BRU: ppp23 PPP: Phase is ESTABLISHING
    3706632: Apr  1 08:51:23.183 BRU: Ce0 PPP: Using dialer call direction
    3706633: Apr  1 08:51:23.183 BRU: Ce0 PPP: Treating connection as a callout
    3706634: Apr  1 08:51:23.183 BRU: Ce0 PPP: Session handle[AE000017] Session id[23]
    3706635: Apr  1 08:51:23.183 BRU: Ce0 LCP: Event[OPEN] State[Initial to Starting]
    3706636: Apr  1 08:51:23.183 BRU: Ce0 PPP: No remote authentication for call-out
    3706637: Apr  1 08:51:23.183 BRU: Ce0 LCP: O CONFREQ [Starting] id 1 len 20
    3706638: Apr  1 08:51:23.183 BRU: Ce0 LCP:    ACCM 0x000A0000 (0x0206000A0000)
    3706639: Apr  1 08:51:23.183 BRU: Ce0 LCP:    MagicNumber 0xE74DCDE6 (0x0506E74DCDE6)
    3706640: Apr  1 08:51:23.183 BRU: Ce0 LCP:    PFC (0x0702)
    3706641: Apr  1 08:51:23.183 BRU: Ce0 LCP:    ACFC (0x0802)
    3706642: Apr  1 08:51:23.183 BRU: Ce0 LCP: Event[UP] State[Starting to REQsent]
    3706643: Apr  1 08:51:23.191 BRU: Ce0 LCP: I CONFREQ [REQsent] id 7 len 25
    3706644: Apr  1 08:51:23.191 BRU: Ce0 LCP:    ACCM 0x00000000 (0x020600000000)
    3706645: Apr  1 08:51:23.191 BRU: Ce0 LCP:    AuthProto CHAP (0x0305C22305)
    3706646: Apr  1 08:51:23.191 BRU: Ce0 LCP:    MagicNumber 0x813CA39C (0x0506813CA39C)
    3706647: Apr  1 08:51:23.191 BRU: Ce0 LCP:    PFC (0x0702)
    3706648: Apr  1 08:51:23.191 BRU: Ce0 LCP:    ACFC (0x0802)
    3706649: Apr  1 08:51:23.191 BRU: Ce0 LCP: O CONFACK [REQsent] id 7 len 25
    3706650: Apr  1 08:51:23.191 BRU: Ce0 LCP:    ACCM 0x00000000 (0x020600000000)
    3706651: Apr  1 08:51:23.191 BRU: Ce0 LCP:    AuthProto CHAP (0x0305C22305)
    3706652: Apr  1 08:51:23.191 BRU: Ce0 LCP:    MagicNumber 0x813CA39C (0x0506813CA39C)
    3706653: Apr  1 08:51:23.191 BRU: Ce0 LCP:    PFC (0x0702)
    3706654: Apr  1 08:51:23.191 BRU: Ce0 LCP:    ACFC (0x0802)
    3706655: Apr  1 08:51:23.191 BRU: Ce0 LCP: Event[Receive ConfReq+] State[REQsent to ACKsent]
    3706656: Apr  1 08:51:23.191 BRU: Ce0 LCP: I CONFACK [ACKsent] id 1 len 20
    3706657: Apr  1 08:51:23.191 BRU: Ce0 LCP:    ACCM 0x000A0000 (0x0206000A0000)
    3706658: Apr  1 08:51:23.191 BRU: Ce0 LCP:    MagicNumber 0xE74DCDE6 (0x0506E74DCDE6)
    3706659: Apr  1 08:51:23.191 BRU: Ce0 LCP:    PFC (0x0702)
    3706660: Apr  1 08:51:23.191 BRU: Ce0 LCP:    ACFC (0x0802)
    3706661: Apr  1 08:51:23.191 BRU: Ce0 LCP: Event[Receive ConfAck] State[ACKsent to Open]
    3706662: Apr  1 08:51:23.199 BRU: Ce0 PPP: Queue CHAP code[1] id[1]
    3706663: Apr  1 08:51:23.211 BRU: Ce0 PPP: Phase is AUTHENTICATING, by the peer
    3706664: Apr  1 08:51:23.211 BRU: Ce0 CHAP: Redirect packet to Ce0
    3706665: Apr  1 08:51:23.211 BRU: Ce0 CHAP: I CHALLENGE id 1 len 35 from "UMTS_CHAP_SRVR"
    3706666: Apr  1 08:51:23.211 BRU: Ce0 PPP: Sent CHAP SENDAUTH Request
    3706667: Apr  1 08:51:23.211 BRU: Ce0 LCP: State is Open
    3706668: Apr  1 08:51:23.211 BRU: Ce0 PPP: Received SENDAUTH Response FAIL
    3706669: Apr  1 08:51:23.211 BRU: Ce0 CHAP: Using hostname from interface CHAP
    3706670: Apr  1 08:51:23.211 BRU: Ce0 CHAP: Using password from interface CHAP
    3706671: Apr  1 08:51:23.211 BRU: Ce0 CHAP: O RESPONSE id 1 len 41 from
    3706672: Apr  1 08:51:23.219 BRU: Ce0 CHAP: I SUCCESS id 1 len 4
    3706673: Apr  1 08:51:23.219 BRU: Ce0 PPP: Phase is FORWARDING, Attempting Forward
    3706674: Apr  1 08:51:23.223 BRU: Ce0 PPP: Phase is ESTABLISHING, Finish LCP
    3706675: Apr  1 08:51:23.223 BRU: Ce0 PPP: Phase is UP
    3706676: Apr  1 08:51:23.223 BRU: Ce0 IPCP: Protocol configured, start CP. state[Initial]
    3706677: Apr  1 08:51:23.223 BRU: Ce0 IPCP: Event[OPEN] State[Initial to Starting]
    3706678: Apr  1 08:51:23.223 BRU: Ce0 IPCP: O CONFREQ [Starting] id 1 len 22
    3706679: Apr  1 08:51:23.223 BRU: Ce0 IPCP:    Address 0.0.0.0 (0x030600000000)
    3706680: Apr  1 08:51:23.223 BRU: Ce0 IPCP:    PrimaryDNS 0.0.0.0 (0x810600000000)
    3706681: Apr  1 08:51:23.223 BRU: Ce0 IPCP:    SecondaryDNS 0.0.0.0 (0x830600000000)
    3706682: Apr  1 08:51:23.223 BRU: Ce0 IPCP: Event[UP] State[Starting to REQsent]
    3706683: Apr  1 08:51:23.227 BRU: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cellular0, changed state to up
    3706684: Apr  1 08:51:24.223 BRU: Ce0 IPCP: I CONFNAK [REQsent] id 1 len 16
    3706685: Apr  1 08:51:24.223 BRU: Ce0 IPCP:    PrimaryDNS (0x81060A0B0C0D)
    3706686: Apr  1 08:51:24.223 BRU: Ce0 IPCP:    SecondaryDNS (0x83060A0B0C0E)
    3706687: Apr  1 08:51:24.223 BRU: Ce0 IPCP: O CONFREQ [REQsent] id 2 len 22
    3706688: Apr  1 08:51:24.223 BRU: Ce0 IPCP:    Address 0.0.0.0 (0x030600000000)
    3706689: Apr  1 08:51:24.227 BRU: Ce0 IPCP:    PrimaryDNS (0x81060A0B0C0D)
    3706690: Apr  1 08:51:24.227 BRU: Ce0 IPCP:    SecondaryDNS (0x83060A0B0C0E)
    3706691: Apr  1 08:51:24.227 BRU: Ce0 IPCP: Event[Receive ConfNak/Rej] State[REQsent to REQsent]
    3706692: Apr  1 08:51:25.231 BRU: Ce0 IPCP: I CONFNAK [REQsent] id 2 len 16
    3706693: Apr  1 08:51:25.231 BRU: Ce0 IPCP:    PrimaryDNS (0x81060A0B0C0D)
    3706694: Apr  1 08:51:25.231 BRU: Ce0 IPCP:    SecondaryDNS (0x83060A0B0C0E)
    3706695: Apr  1 08:51:25.231 BRU: Ce0 IPCP: O CONFREQ [REQsent] id 3 len 22
    3706696: Apr  1 08:51:25.231 BRU: Ce0 IPCP:    Address 0.0.0.0 (0x030600000000)
    3706697: Apr  1 08:51:25.231 BRU: Ce0 IPCP:    PrimaryDNS (0x81060A0B0C0D)
    3706698: Apr  1 08:51:25.231 BRU: Ce0 IPCP:    SecondaryDNS (0x83060A0B0C0E)
    3706699: Apr  1 08:51:25.231 BRU: Ce0 IPCP: Event[Receive ConfNak/Rej] State[REQsent to REQsent]
    3706700: Apr  1 08:51:25.423 BRU: Ce0 IPCP: I CONFREQ [REQsent] id 2 len 4
    3706701: Apr  1 08:51:25.423 BRU: Ce0 IPCP AUTHOR: Done. Her address 0.0.0.0, we want 0.0.0.0
    3706702: Apr  1 08:51:25.423 BRU: Ce0 IPCP: O CONFACK [REQsent] id 2 len 4
    3706703: Apr  1 08:51:25.427 BRU: Ce0 IPCP: Event[Receive ConfReq+] State[REQsent to ACKsent]
    3706704: Apr  1 08:51:25.427 BRU: Ce0 IPCP: I CONFNAK [ACKsent] id 3 len 22
    3706705: Apr  1 08:51:25.427 BRU: Ce0 IPCP:    Address (0x0306B2904FF3)
    3706706: Apr  1 08:51:25.427 BRU: Ce0 IPCP:    PrimaryDNS (0x810651A93C6B)
    3706707: Apr  1 08:51:25.427 BRU: Ce0 IPCP:    SecondaryDNS (0x830651A93C6B)
    3706708: Apr  1 08:51:25.427 BRU: Ce0 IPCP: O CONFREQ [ACKsent] id 4 len 22
    3706709: Apr  1 08:51:25.427 BRU: Ce0 IPCP:    Address (0x0306B2904FF3)
    3706710: Apr  1 08:51:25.427 BRU: Ce0 IPCP:    PrimaryDNS (0x810651A93C6B)
    3706711: Apr  1 08:51:25.427 BRU: Ce0 IPCP:    SecondaryDNS (0x830651A93C6B)
    3706712: Apr  1 08:51:25.427 BRU: Ce0 IPCP: Event[Receive ConfNak/Rej] State[ACKsent to ACKsent]
    3706713: Apr  1 08:51:25.443 BRU: Ce0 IPCP: I CONFACK [ACKsent] id 4 len 22
    3706714: Apr  1 08:51:25.475 BRU: Ce0 IPCP:    Address (0x0306B2904FF3)
    3706715: Apr  1 08:51:25.475 BRU: Ce0 IPCP:    PrimaryDNS (0x810651A93C6B)
    3706716: Apr  1 08:51:25.475 BRU: Ce0 IPCP:    SecondaryDNS (0x830651A93C6B)
    3706717: Apr  1 08:51:25.475 BRU: Ce0 IPCP: Event[Receive ConfAck] State[ACKsent to Open]
    3706718: Apr  1 08:51:25.475 BRU: Ce0 IPCP: State is Open
    3706719: Apr  1 08:51:25.475 BRU: Di1 IPCP: Install negotiated IP interface address
    3706720: Apr  1 08:51:25.479 BRU: Ce0 DDR: dialer protocol up
    3706721: Apr  1 08:51:25.479 BRU: Di1 DDR: Persistent Dialer Profile nailed up successfully
    Cheers
    Raj

Maybe you are looking for

  • Message no. AC496 while posting F-90

    Dear Experts, While Posting F-90 for Asset Acquisition i am getting message Message no. AC496 Diagnosis Company code 5000 manages parallel currencies in Asset Accounting. For each area that posts automatically online to FI, you have to define one dep

  • How do I connect 7th generation Nano to miniboom speaker?

    How do I connect 7th generation ipod Nano to Mini Boom speaker bought at Apple store? 

  • Help! ORA-01031: insufficient privileges during "startup migrate" 8i to 9i

    Hello there, I am following the Oracle 9i upgrade checklist Doc ID: 159657.1 to upgrade from 8.1.7.3 to 9.2.0.4. In step 31, after setting the environment to new ORACLE_HOME, I am trying to start the 9.2.0.4 instance in migrate mode. This is the sequ

  • Apache C++ Standard Library 4.2.0 released

    October 29, 2007 -- The Apache C++ Standard Library project is pleased to announce that the official stdcxx 4.2.0 release is now available for download from the following location: http://people.apache.org/dist/incubator/stdcxx/releases/ For addition

  • What is the benefit of using managed paths?

    Why not just put everything under /sites? What is the value in organizing sites under managed paths - aprt from it looking nice what other benefits does it bring? For one thing organizations change their structures sometimes drastically and surely ad