Hi Steve,
Thanks for the suggestions. The issue does not appear to have anything to do with the cable. It worked perfectly on the old router. My main reason for replacing the router was basically because it had a recently discovered gaping security hole which D-Link has no plans to fix because they consider it obsolete. Since the modem (a Moto SB6120 was also EOL (an early DOCSIS 3.0 that was maxed out by the increased speed from Xfinity), I decided it was time to upgrade.
As you mention, the SBG10 has two gigabit ports. One of them was cabled to the gigabit switch to which all my wired devices are connected. I moved the non-OBI end of the OBI's cable from that switch to the spare port on the router. There is no difference in behavior. (Not surprised. The cabling through the switch has also worked for years.)
I then tried your "***1" suggestion. It read back the static IP address and stated that DHCP was disabled. The message seems to mean that it is a static IP, which is true. Not much info there except the Obi is working.
I have no trouble logging into the Obi's Web interface. (But, my password is much longer than "admin". <g>)
Some additional food for thought:
===============
A loooong time ago, I configured the Obi to write to syslog. (I can't even remember now where the heck that is enabled in the settings.) At the time, I also installed a program called "Syslog Watcher" on my main desktop. Recalling that, I fired up the syslog watcher service. With the telephone on hook, I see the same logged activity sequence over and over:
1. SNTP:Wait 6000
2. BASE:resolving root.pnn.obihai.com (wait 30 seonds)
3. BASE:resolving root.pnn.obihai.com (wait 30 seonds)
This is repeated three times. Then:
DNS: All servers are not responding!
(Then repeat from the top)
It appears to me that the issue may be that the OBI can't get DNS.