Hardware is R.Pi4 with PoE hat connected to EX4200-48PX switch with port configured to provide up to 30W PoE (default).
First boot, waited 20 minutes before system enabled ethernet and came up with an IP address. Waited more than 8 hours and still no services open other than RPC Portmapper (111/tcp) according to map.
Rebooted (power cycled PoE port) and came back in about 60 seconds after power was restored (to same state as before).
800 seconds since system came back and still only RPC Portmapper available.
System is headless and in a location where attaching a monitor would be difficult at best, so hopingg to troubleshoot without having to attach a monitor, but since it doesn’t even bring up SSH, I’m at a bit of a loss as to next steps.
So this is interesting… Out of desperation (hooking up a monitor to this system is REALY inconvenient), I tried putting it on a different network. The network it was on had a direct IP (it was originally 192.159.xxx.217). I tried moving it to a VLAN that I use for experiments with NAT (192.168.100.xxx) which uses the same external ISP and that worked, it did eventually come up to where I could get to the HA web page. Of course, the first thing I did was install the SSH add-on. Frankly, IMHO, it would be good for that add-on to come by default with a mechanism for putting a public key into the image, perhaps through an authorized_keys file in the /boot partition like what is done on R.Pi OS for wpa_supplicant.conf.