I now have four of them, no eth access to any. Should I be able to NetInstall even with no eth lights?
All of these configured initially and I had working links in the shop. All of them lasted a day or two after initial config before failing in one way or another---two of them responded to a reset once and were reconfigured and worked, but the following day had no eth connectivity. At this point, I have one with no lights at all on application of PoE, one that lights very briefly and extinguishes, one one which LED1 flashes about once per second, and one that flashes at about ten times faster than that. I have tried to push all of these into NetInstall mode now by holding down the reset button as long as I can stand after application of PoE, with no apparent success. (None of them appears as drive in the PC NetInstall window) Again, no eth connectivity--would this appear to be the case if any of these were in the mode where they are looking for a NetInstall server? I don't have any experience with NetInstall without serial connectivity...
BTW, I did not do an update on any of these before they failed; my bad. I think they were running, like 5.12.
I don't see any posts anywhere about dead eth ports on the Metals, so I'm wondering what the heck is going on.

thanks in advance,
jag

That is weird. We've deployed 7 9HPns so far, and only one had a problem. It was a radio problem where it would associate fine and the signal levels looked good, but a lot of packets would get lost in transit. We replaced the unit and now the link works as it should.

Since you mentioned LEDs, I have never seen any of the LEDs on any of these units work at all. They always remain dark at all times for me, though everything else works normally.

You didn't maybe connect yours to a 48V power supply or something, did you?

No, they were all powered with the stock 24v PoE. I configured another batch of four and pretty much have the same result.

I’ve got one of the four still alive after powering up and bench testing the new units over the weekend. The one left is the one configured as AP Bridge. The others all got configured as Station-WDS, connected to the AP successfully and after powering down never rebooted successfully again— I just get the all too familiar flashing power LED, and no Ethernet connectivity. I have tried the reset button to reset and when that didn't work, to go to NetInstall mode. I have even opened one up and tried resetting with the reset hole, all with no success. No visible damage on the boards, BTW. They do get kind of hot sitting there, flashing and going nowhere (not fully booting?), but I’m guessing that’s what the heat-sink ribs on the housing are for.

Again all of these were powered up with antenna attached. When they connected with the AP, I think one saw RSSI levels approaching -20dBm briefly before I got both ends powered down enough. For the other two "CPEs", I don’t think they saw anything hotter than -38 to -40dBm RSSI. (I was able to get the “All Rates Fixed” setting in Winbox—not in the new WebFig GUI, though—and get the TX power down to 0dBm or less for indoor testing. The units then linked up at around -55dBm).

One thing I realized afterward is that I used the same yagi (an old M2 14dBi) and the same stock MTik right angle N-connector when I powered up all these radios. I just checked the right angle adapter with an ohmmeter and it looks fine, but I have no idea if the antenna is somehow internally shorted in its connector—I didn’t have the sense to change to another antenna before running out of radios. Does anyone know how a radio acts if it has been powered up without an antenna or attenuator and gotten damaged? I wonder if that’s what the flashing LED behavior is telling me.

Also, I’m wondering if there is any configuration screw-up I could be making to cause this. All these radios were set up with the WLAN and LAN ports in Bridge1, the AP in AP-Bridge and the would be CPEs in Station WDS (WDS dynamic mode). The AP did seem to be adding a new WDS interface for each station (e.g. WDS 3, WDS 4), but I’m guessing that is normal for AP mode (I’ve only done PtP links with MT before). I was setting the wireless protocol as “Any” for starters, thinking I would try Nstreme, NV2 later. No encryption, either, saving that for later config. 5MHz channels 922 center.

So, I guess my next move is to get a couple more radios and try with different antenna. Or maybe I should try to RMA these units? I really would like to know how to get these units working-- I'm hearing reports from others that they are the best option in 900 MHz!!

We are having the same issue.

After plugging in our 9HPns we have two radios that we have not been able to connect to over eth. One is showing the blinking light, the other is showing nothing.

However on a different pc with a different antenna we have had success with other 9HPns. Yet we cannot connect to the two bad 9Hpns with either pc.

Is this problem cause by using a bad antenna? Is it possible to fix these 9HPns?