RBK53 (v2.1.4.16): Satellite Restart with Wired Backhaul Failures

> What is the Mfr and model# of the non managed swtich?

I observed the same behavior when the unmanaged switch was eliminated and the RBR50 was plugged directly into one of the Verizon Router ethernet ports.  In any case, the switch is a Netgear GS108.  Another test could have been to isolate the RBR50 from the Verizon network and operate the RBR50 in router mode, since that could result in different behavior.  There is a lot of testing configurations that should be performed by Netgear, but it seems clear to me that they are quite deficient in this area.

> Did you also disable Daisy Chain before attempting to setup the wired backhaul? It should be disabled before configuring wired back haul.

No.  I tried to make the minimum changes necessary, and Netgear support did not indicate that Daisy Chain had to be disabled.  Perhaps it would be a useful test to perform, but I am boxed up and returning the product.

> Did you wait the 5 minutes per each satellite for the top led to turn on BLUE after connecting the ethernet between the router and satellite?

If I wait for the wireless bakhaul to be established before I connect the wired ethernet to the Satellites, then yes the network will recover.  But I think you miss the point of the problem -- if there is a power glitch, I should not have to manually choreograph the recovery of the network.

> Also did you set up an IP address reservation for each satellite after you got them connected?

No.  Perhaps another useful test to determine if it makes a difference, although the RBR50 seems to be able to discover the Satellites just fine without a fixed IP address.

> Was a factory reset performed on the system after the FW was updated to the most recent?

Yes.