Aironet 1100 Stability Problem

[scottholwerda]

We have an 1100 Aironet AP running IOS 12.3(2). We are trying to connect a Zebra 105SL printer with the Wireless Print Server option where we are using a Cisco Aironet PCM352 PC Card. When the printer is turned on and starts to pull an ip address the AP reboots, then the client connects. If we cycle the power on the printer the AP will reboot again when the printer tries to pull an ip address. Laptops and other wireless devices seem to work fine.

Has anyone seen anything like this, or have any advice on what we could try?

Scott

[alinn · Accepted solution]

Hey Scott,

I have not seen this before and could not find any other documented issues with a Zebra printer that cuase the AP to reload. Reloads are never good.

I would suggest using IOS 12.2(15)XR2 and see if the issue stills remains.

I would also check the printer Firmware.

In October they released 60.13.0.3 which is the latest.

I did review the release notes and did not see any reported issues between the printer and any APs. But may want to go this route as well. This issue is software related and changing the code, I believe, will resolve the issue.

Hope this helps.

Regards,

Aaron

[scottholwerda]

Aaron,

We had firmware 60.13.0.3 but upgraded to 60.13.0.9 for the printer, but that made no difference. We also installed and test IOS 12.2(15)XR2 on the AP with both versions of the printer firmware and that solved the issue.

IOS 12.3(2)JA does not work with Zebra 105SL Wireless printers.

Thank you for your help,

Scott

[tphelan]

I'm seeing the same thing on both my 1100 AP's and my 350 AP's (upgraded to Cisco IOS) which have the 12.3.2 firmware. Both my 1100's and my 350's with 12.3.2 spontaneously reboot sometimes after 5 minutes, sometimes after 5 hours, but they never stay up for more than a day. Furthermore, the 4 different AP's I upgraded with this version rebooted at the same time! This leads me to conclude two things: 1. It is definitely the software since both my 350's and my 1100's exhibit the same problem. 2. Since all my AP's reboot at the same time, this leads me to believe it was some type of network request that caused the reboot. I was going sniff the network and examine the time when all the AP's rebooted to see if I could see what caused it, but simply going back to 12.2.15 solved the problem so I didn't bother. I hope Cisco is aware of this issue and will address it in future releases.

[janf]

I just upgraded all 57 of the AP1100's that I manage to 12.3(2)JA last week and this morning all 9 at the one location rebooted at the same time. I talked to a manufacturing engineer there and found out that he connected a new Zebra printer to the network the night before. This is a cool feature! Anyway, does anyone know if 12.3(2)JA2 resolves this?

[thisisshanky]

Interesting..Try loading JA2 and see if that helps!..if TAC is not aware of this, you probably cannot fix it without opening a case with TAC. Hopefully there should be a workaround soon. I will be interested in knowing the outcome!!

[pdotcisco]

I strongly recommend going back to 12.2.15 as it is the only thing I found that solved the problem. I posted earlier under a different User ID. Since downgrading to 12.2.15 both my 350's and 1100's have worked flawlessly

[janf]

I went up to the latest JA2 and so far so good. If I have anymore problems, then I will go down to 2.15 and post a msg.