We ran into a situation where we power cycled some of our remote equipment which included a SG90. Unfortunately it did not come back online either immediately or after waiting for 30+ minutes. The person onsite indicated that there were no lights on for this device. Unfortunately the spare did not pick up for it so we removed the spare and readded to the site as a standard switch and moved all the phones to that. We submitted an RMA. Later, I can now ping the device but director still indicates a communication error.
With the new device, I was planning on getting the MAC address, setting the IP address, and sending onsite to have them plug in. However, it seems the replacement never boots to a login prompt. It seems to be in a boot loop with a significant amount of time spent outputting:
and
It also seems to be retrying DHCP repeatedly.
There is also a countdown shortly after initial booting (and after its boot loop) where it says to press any key to stop autoboot. It does not respond to any key input during this countdown though.
Am I incorrect in my assumption that this should boot to a prompt for me to login where I can set the IP address? Do I need to plug this into a network so it gets a dhcp address to make it happy and boot?
With the new device, I was planning on getting the MAC address, setting the IP address, and sending onsite to have them plug in. However, it seems the replacement never boots to a login prompt. It seems to be in a boot loop with a significant amount of time spent outputting:
Code:
0x7f8d50 (tNetTask): TX ERRPR 0x1401
Code:
get_myaddress() delayed 19 sec, err=-1
There is also a countdown shortly after initial booting (and after its boot loop) where it says to press any key to stop autoboot. It does not respond to any key input during this countdown though.
Am I incorrect in my assumption that this should boot to a prompt for me to login where I can set the IP address? Do I need to plug this into a network so it gets a dhcp address to make it happy and boot?