Cutomer was having problems imaging computers connected to Aruba-S3500 switches.
We found that if the pc was on an access port they would image just fine but if the port was set to trunk with a native vlan that they could not image the pc.
We currently have all the edge ports set to trunk with native and access vlan set to their normal data network. We then also allow their VOIP vlan. So the network cable goes from the wall to their phone and then out of their phone into their pc. (Pretty standard)
With the port in that config mode they could not image the pc upon startup because it was if the network wasn't ready fast enough when booting up the pc. It didn't matter if the pc was straight on the network or if it was connected through their phone.
We found that if we turned stp off on the switch stack that would effectively eliminate this delay and they then could image the pc's connected on the back side of phones and any pc's directly connected to the edge ports in this trunk mode.
Again this was only a problem if the port was in trunk mode. Access ports worked just fine.
This site has redundant fiber feeds into the switch stack. So whenever they need to image they log into the switch. Admin down the redundant fiber port and then turn off stp on the stack. Once they are done reimaging they turn stp back on and reenable the redundant feed.
If anyone knows of another way or a work around for this that would be great !!! When speaking to Aruba about this they hoped to address this in future firmware release on the switch.