IAP-225 daisy chain off second port

[SPWiFi]

I recently deployed 3x IAP-225s in an auditorium setting.  It was installed with the version 6.3.1.0-4.0.0 software.  We used existing cabling and their were only 2 runs available, so on one of the IAPs we configured the following:

more>>Wired>> eth1 port = wired port profile

This allowed us to 'daisy chain' the third AP to one of the other APs.  It worked fine.

But, we experienced connectivity issues per this thread:

ARUBA 225 DHCP ISSUE

We upgraded the firmware to 4.0.0.5 and this seems to have solved the connection issues...

However, we immediately noticed that the third AP was no longer reachable and didn't show up on the controller's associated list. 

Did something occure with the firmware upgrade that no longer supports using the secondary port for wired access??

[Marcus]

Can you clarify how the two -225s are physically connected?

Is it :  network-->Eth0 IAP_#1 -->Eth1 out----> Eth0 IAP_#2

Eth0 must always be the uplink to the network and Eth1 is the downlink to other wired devices.  Can you show us what your Eth1 wired profile looks like on IAP#1?

[SPWiFi]

Yep.. just like you described:  Eth0 connects to network, Eth1 connects to Eth0 of second AP.

It worked just fine until I updated the firmware and then instantaneously lost connectivity.

[martin.liska@flex.com]

... since i do not see any updates to this thread and we are experiencing exactly the same issues using IAP-205s running version 6.5.4.2 (build 61807) - is this by design or are we running into a different bug here ?

[mannvishal]

Could you paste a show tech?