Your asking for info from 'sudo systemctl status network' showed me what my problem is.

In order to clone the disk for the server I needed to have it come up with a new IP address as the 'real' server is up an running. I saved a copy of ifcfg-eth0 in /etc/sysconfig/network and called it ifcfg-eth0.save.
wcs-mf-winxs-db2p:~ # systemctl status network
 wicked.service - wicked managed network interfaces
   Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled)
   Active: active (exited) since Wed 2017-12-06 07:53:35 CST; 14s ago
  Process: 1884 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS)
 Main PID: 1884 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 512)
   CGroup: /system.slice/wicked.service

Dec 06 07:53:04 wcs-mf-winxs-db2p systemd[1]: Starting wicked managed network interfaces...
Dec 06 07:53:35 wcs-mf-winxs-db2p wicked[1884]: lo              up
Dec 06 07:53:35 wcs-mf-winxs-db2p wicked[1884]: eth0            up
Dec 06 07:53:35 wcs-mf-winxs-db2p wicked[1884]: eth0.save       no-device
Dec 06 07:53:35 wcs-mf-winxs-db2p systemd[1]: Started wicked managed network interfaces.
Seeing the 'eth0.save' in the list rang a bell where (about 10 years ago) we had weird network issues upgrading to SLES 10 when we named a saved copy as filename.save. I renamed ifcfg-eth0.save to save.ifcfg-eth0, rebooted, and tested. I was able to PuTTY in without issuing the temporary command to define the gateway.

Thank you very much for your assistance with this.