hi ereader22
based on your tests, the enet port may be damaged. Connect AP to known working port and interrupt the boot process from the console and try the following (and capture it, since this will probably end up being in the RMA ticket, and someone will ask for it)
apboot> dhcp
... wait...
does it eventually get an IP address? if so, it can be fixed.
If not, rule out DHCP - again since you will likely be asked for it in the RMA, so easier to get all info just once:
apboot> setenv ipaddr 1.2.3.4
apboot> setenv netmask 255.255.255.0
apboot> setenv gatewayip 1.2.3.254
apboot> ping 1.2.3.100
where: 1.2.3.4 is the AP ip address, assumes /24, def gw not used but configure it anyhow and 1.2.3.100 is controller or any other reachable host.
If the above two tests fail, the enet port is likely damaged and you can RMA it under LLW terms and conditions unless you have a better support contract on it.
regards
-jeff