Weird AP-350 issue

Discussion in 'Cisco' started by Al Blake, Apr 15, 2004.

  1. Al Blake

    Al Blake Guest

    We have an AP-350 that is running 11.21. The unit is a few years old and has
    been exhibiting some weird problems - dropping all radio connections and
    refusing to do anything until restarted.
    So....I have taken it out of our production LAN and brought it home to work
    out whether the problem is configuration or in the box itself. I have
    connected it to an old 10BT hub I have at home and it powers up ok and picks
    all the correct DHCP parameters.

    I have done a complete system reset back to default settings including IP.
    After restart I can connect to the unit using a browser and everything looks
    fine....BUT only 1 in 10 or so pings to the unit actually replies. If I set
    a ping running @ 5 secs delay I get about 10-20 no replies....then a couple
    of replies...then the same again. eg:

    Reply from 192.168.0.11: bytes=32 time=1011ms TTL=64
    Reply from 192.168.0.11: bytes=32 time<10ms TTL=64
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 192.168.0.11: bytes=32 time=741ms TTL=64
    Reply from 192.168.0.11: bytes=32 time<10ms TTL=64
    Request timed out.
    Request timed out.

    Bear in mind this is a home network we are talking about here so even though
    it's 10BT there is zero traffic. If I ping the only other machine on my LAN
    I get 100% success.

    So it looks as though there is something pretty seriously wrong with the
    Ethernet? The unit is out of warranty and I know Cisco wont touch it so I
    guess my question before I throw the thing in the skip is:

    Has anyone seen this before? Are there any diagnostics I can run that tell
    me what the problem is before I bin the unit? Can it be fixed easily
    (cheaply) or should I give up?

    Al Blake, Canberra, Australia
    Al Blake, Apr 15, 2004
    #1
    1. Advertising

  2. Al Blake

    Al Blake Guest

    Extra info:

    I should have pointed out that the green ethernet light blinks as it
    receives traffic.......but also the green status light goes on and off in an
    irregular fashion! It DOESNT go amber (which is supposed to indicate an
    error) and it doesnt 'blink' regularly......it just goes on an off in an
    irregular pattern..
    Is this unit stuffed? Are the electronics packing up inside?


    "Al Blake" <> wrote in message
    news:407def03$0$16597$...
    > We have an AP-350 that is running 11.21. The unit is a few years old and

    has
    > been exhibiting some weird problems - dropping all radio connections and
    > refusing to do anything until restarted.
    > So....I have taken it out of our production LAN and brought it home to

    work
    > out whether the problem is configuration or in the box itself. I have
    > connected it to an old 10BT hub I have at home and it powers up ok and

    picks
    > all the correct DHCP parameters.
    >
    > I have done a complete system reset back to default settings including IP.
    > After restart I can connect to the unit using a browser and everything

    looks
    > fine....BUT only 1 in 10 or so pings to the unit actually replies. If I

    set
    > a ping running @ 5 secs delay I get about 10-20 no replies....then a

    couple
    > of replies...then the same again. eg:
    >
    > Reply from 192.168.0.11: bytes=32 time=1011ms TTL=64
    > Reply from 192.168.0.11: bytes=32 time<10ms TTL=64
    > Request timed out.
    > Request timed out.
    > Request timed out.
    > Reply from 192.168.0.11: bytes=32 time=741ms TTL=64
    > Reply from 192.168.0.11: bytes=32 time<10ms TTL=64
    > Request timed out.
    > Request timed out.
    >
    > Bear in mind this is a home network we are talking about here so even

    though
    > it's 10BT there is zero traffic. If I ping the only other machine on my

    LAN
    > I get 100% success.
    >
    > So it looks as though there is something pretty seriously wrong with the
    > Ethernet? The unit is out of warranty and I know Cisco wont touch it so I
    > guess my question before I throw the thing in the skip is:
    >
    > Has anyone seen this before? Are there any diagnostics I can run that tell
    > me what the problem is before I bin the unit? Can it be fixed easily
    > (cheaply) or should I give up?
    >
    > Al Blake, Canberra, Australia
    >
    >
    Al Blake, Apr 15, 2004
    #2
    1. Advertising

  3. Al Blake

    Al Blake Guest

    More stuff. Finally got a console cable to work.Tried to upgrade the
    IOS....but of course that failed :(
    Now when I reboot I get:
    Power-on reset.

    Copyright 1996-2000 Cisco Systems, Inc.
    Copyright 1984-2000 Wind River Systems, Inc.

    System ID: 0040965798FD
    Motherboard: MPC855 50MHz, 8192KB FLASH, 16384KB DRAM, Revision 90
    Bootstrap Ver. 1.09: FLASH, CRC 710B6415 (OK)
    Initialization: OK

    *** Bad CRC in File FLASH :FE16005C

    Memory Bank total used left
    DRAM 16738168 0 16738168
    Config 524288 540 523748
    FLASH 7733248 786524 6946724

    Memory Bank:File address size encoding type
    flags
    a) Config:AP Installation Key FE020000 64 none Key 0000
    b) Config:VAR Installation Key FE020040 52 none Key 0000
    c) Config:AWC_ConfigDB FE020074 424 AiroDB1 Data 0000
    d) FLASH :IOS_Upgrade 1.0 FE0A0000 393268 none Exec 0801
    e) FLASH :IOS_C350_BOOT 2 FE100034 393256 none 0x09 0800


    Socket Controller Error: No FPGA file!

    System ID: 0040965798FD
    Motherboard: MPC855 50MHz, 8192KB FLASH, 16384KB DRAM, Revision 90
    Bootstrap Ver. 1.09: FLASH, CRC 710B6415 (OK)
    Initialization: Improper Motherboard Config

    Is this box junk now?
    Al.


    "Al Blake" <> wrote in message
    news:407def03$0$16597$...
    > We have an AP-350 that is running 11.21. The unit is a few years old and

    has
    > been exhibiting some weird problems - dropping all radio connections and
    > refusing to do anything until restarted.
    > So....I have taken it out of our production LAN and brought it home to

    work
    > out whether the problem is configuration or in the box itself. I have
    > connected it to an old 10BT hub I have at home and it powers up ok and

    picks
    > all the correct DHCP parameters.
    >
    > I have done a complete system reset back to default settings including IP.
    > After restart I can connect to the unit using a browser and everything

    looks
    > fine....BUT only 1 in 10 or so pings to the unit actually replies. If I

    set
    > a ping running @ 5 secs delay I get about 10-20 no replies....then a

    couple
    > of replies...then the same again. eg:
    >
    > Reply from 192.168.0.11: bytes=32 time=1011ms TTL=64
    > Reply from 192.168.0.11: bytes=32 time<10ms TTL=64
    > Request timed out.
    > Request timed out.
    > Request timed out.
    > Reply from 192.168.0.11: bytes=32 time=741ms TTL=64
    > Reply from 192.168.0.11: bytes=32 time<10ms TTL=64
    > Request timed out.
    > Request timed out.
    >
    > Bear in mind this is a home network we are talking about here so even

    though
    > it's 10BT there is zero traffic. If I ping the only other machine on my

    LAN
    > I get 100% success.
    >
    > So it looks as though there is something pretty seriously wrong with the
    > Ethernet? The unit is out of warranty and I know Cisco wont touch it so I
    > guess my question before I throw the thing in the skip is:
    >
    > Has anyone seen this before? Are there any diagnostics I can run that tell
    > me what the problem is before I bin the unit? Can it be fixed easily
    > (cheaply) or should I give up?
    >
    > Al Blake, Canberra, Australia
    >
    >
    Al Blake, Apr 15, 2004
    #3
  4. Al Blake

    Hansang Bae Guest

    In article <407e0698$0$16594$>,
    says...
    > More stuff. Finally got a console cable to work.Tried to upgrade the
    > IOS....but of course that failed :(
    > Now when I reboot I get:



    The document (that comes with the upgrade) should have a section on
    recovery. Worked for me (though it was for a 1200)

    Also, keep in mind that Cisco boxes will rate-limit ICMP messages
    (although newer IOS is supposed to not rate-limit them)


    --

    hsb

    "Somehow I imagined this experience would be more rewarding" Calvin
    *************** USE ROT13 TO SEE MY EMAIL ADDRESS ****************
    ********************************************************************
    Due to the volume of email that I receive, I may not not be able to
    reply to emails sent to my account. Please post a followup instead.
    ********************************************************************
    Hansang Bae, Apr 15, 2004
    #4
  5. "Al Blake" <> writes:
    >We have an AP-350 that is running 11.21. The unit is a few years old and has
    >been exhibiting some weird problems - dropping all radio connections and
    >refusing to do anything until restarted.

    ....
    >Reply from 192.168.0.11: bytes=32 time=1011ms TTL=64
    >Reply from 192.168.0.11: bytes=32 time<10ms TTL=64
    >Request timed out.
    >Request timed out.
    >Request timed out.

    ....


    I had one that did the same exact thing, although I did manage to
    reload its OS at one point in time unlike your later failure.

    Only the total hardware replacement on contract fixed it, nothing else
    we did made any difference.
    --
    Doug McIntyre
    Network Engineer/Jack of All Trades
    Vector Internet Services, Inc.
    Doug McIntyre, Apr 15, 2004
    #5
  6. Al Blake

    Al Blake Guest

    Another update....
    Somehow - I dont know how (!) I managed to upgrade the unit to
    IOS.......(had to upload the IOS image file using xmodem as the version in
    upgrade_tar was corrupted....but it worked). Anyway after IOS installtion,
    reloading and a lot of prayers it works and guess what....now the Ethernet
    works perfectly.

    Yes that's right I can now ping and get a reply on every packet. Problem is
    that now the unit doesnt have a Radio Interface (or so it thinks).

    If I look under Interfaces in the web interface for IOS the only interface I
    can see if FastEthernet...which is working fine with no errors.
    I also see greyed out 'Radio0-not installed'......and the red light is
    flashing on the radio indicator on top of the unit.
    If I do a show int from the console I have a BVI1 and an Fe0...thats all.
    Shouldnt I have a radio interface as well?

    So...how can the IOS lose the radio transmitter inerface? More to the point
    how can I get IOS to find the radio interface? I am pretty sure this is a
    config thing but I cant work it out. I seemed to have swapped a problem with
    the ethernet for a problem with the radio during the IOS upgrade!

    Incidentally I now have both web and console access to the device so I can
    do anything ....if I knew what to do....

    Regards
    Al Blake, Canberra, Australia



    "Al Blake" <> wrote in message
    news:407def03$0$16597$...
    > We have an AP-350 that is running 11.21. The unit is a few years old and

    has
    > been exhibiting some weird problems - dropping all radio connections and
    > refusing to do anything until restarted.
    > So....I have taken it out of our production LAN and brought it home to

    work
    > out whether the problem is configuration or in the box itself. I have
    > connected it to an old 10BT hub I have at home and it powers up ok and

    picks
    > all the correct DHCP parameters.
    >
    > I have done a complete system reset back to default settings including IP.
    > After restart I can connect to the unit using a browser and everything

    looks
    > fine....BUT only 1 in 10 or so pings to the unit actually replies. If I

    set
    > a ping running @ 5 secs delay I get about 10-20 no replies....then a

    couple
    > of replies...then the same again. eg:
    >
    > Reply from 192.168.0.11: bytes=32 time=1011ms TTL=64
    > Reply from 192.168.0.11: bytes=32 time<10ms TTL=64
    > Request timed out.
    > Request timed out.
    > Request timed out.
    > Reply from 192.168.0.11: bytes=32 time=741ms TTL=64
    > Reply from 192.168.0.11: bytes=32 time<10ms TTL=64
    > Request timed out.
    > Request timed out.
    >
    > Bear in mind this is a home network we are talking about here so even

    though
    > it's 10BT there is zero traffic. If I ping the only other machine on my

    LAN
    > I get 100% success.
    >
    > So it looks as though there is something pretty seriously wrong with the
    > Ethernet? The unit is out of warranty and I know Cisco wont touch it so I
    > guess my question before I throw the thing in the skip is:
    >
    > Has anyone seen this before? Are there any diagnostics I can run that tell
    > me what the problem is before I bin the unit? Can it be fixed easily
    > (cheaply) or should I give up?
    >
    > Al Blake, Canberra, Australia
    >
    >
    Al Blake, Apr 15, 2004
    #6
  7. Al Blake

    PJML Guest

    Al Blake wrote:
    > Another update....
    > Somehow - I dont know how (!) I managed to upgrade the unit to
    > IOS.......(had to upload the IOS image file using xmodem as the version in
    > upgrade_tar was corrupted....but it worked). Anyway after IOS installtion,
    > reloading and a lot of prayers it works and guess what....now the Ethernet
    > works perfectly.
    >
    > Yes that's right I can now ping and get a reply on every packet. Problem is
    > that now the unit doesnt have a Radio Interface (or so it thinks).
    >
    > If I look under Interfaces in the web interface for IOS the only interface I
    > can see if FastEthernet...which is working fine with no errors.
    > I also see greyed out 'Radio0-not installed'......and the red light is
    > flashing on the radio indicator on top of the unit.
    > If I do a show int from the console I have a BVI1 and an Fe0...thats all.
    > Shouldnt I have a radio interface as well?
    >
    > So...how can the IOS lose the radio transmitter inerface?


    Have you uploaded the *right* IOS? I've seen odd things
    in the past with not-quite-right IOS not recognising
    interfaces [or recognising them in interestingly broken
    ways]
    PJML, Apr 15, 2004
    #7
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Ethan

    Weird issue with new wireless NIC.

    Ethan, Oct 24, 2004, in forum: Wireless Networking
    Replies:
    0
    Views:
    646
    Ethan
    Oct 24, 2004
  2. Jeff
    Replies:
    1
    Views:
    631
  3. Michael Williams

    weird issue with Pix 501

    Michael Williams, Oct 23, 2004, in forum: Cisco
    Replies:
    1
    Views:
    718
  4. tomviolin
    Replies:
    0
    Views:
    358
    tomviolin
    Dec 12, 2006
  5. tomviolin
    Replies:
    1
    Views:
    395
    Aaron Leonard
    Apr 4, 2007
Loading...

Share This Page