Upgrading bridged wraps remotely... how?

[Beebe]

I upgraded a v2 AP to v3 last night. All my v2 clients on that AP were psudo bridged v2 clients, they are not working with the v3 AP for some reason.

But I can still get into each client v2 radio. I can upgrade them one by one to v3, which I have been doing. Only trouble is, when I boot in v3 and change the bridge group to 9 on both the ethernet and wireless Interface, they establish a wds link to the AP, the customer does come online at this point but I can no longer access their wrap board.

Why is this? This wasn't the case with the 900mhz war board I deployed a few weeks back, I can still log into that customers board and he has a WDS link.

I'm hesitant to update more clients when it means I'll have to drive out there next time they have a problem, because I can't log into their board. What am I doing wrong?

Thanks,
Roger
(btw, I love the wrap upgrade process with the cross-over release. Upgraded half my backbone last night without a hitch).

[lonnie]

Did you also make sure to set the AP radio into a bridge group?

[Beebe]

Yes, I have the AP wpci1 and the cpe wpci and the cpe ether1 all in bridge group 9. Can't ping or log into the CPEs from the AP.

Thanks,
Roger

[lonnie]

Can you get me a login to the AP?

[Beebe]

Sent via email.

Thanks,
Roger

[lonnie]

We have discovered a bridging issue with the V3 WRAP version. Please do
not update any other units until we get a fix, which could be today
yet.

Sorry about this.

[tony]

For clarification, the bridge problem is only present when doing client-side bridging (client WDS).

In general, if you wish to have a client-side bridge (for a customer perhaps), make sure you are either using a WAR product, or a WRAP product with a WLM54G card installed. The way the bridge device is assigned it's MAC address can cause an inability to access the client's system from the wireless interface. (can still be accessed via the ethernet however).

We are working on a solution.