Thaks for the response and sorry for the lack of detail but it applies to any libvirt installation by the looks. This only appears to be an issue with VMWare products as i have imported the VM into virtual box and the sleep facility there does not impact the networking.

This is a stock standard RHEL8.3 install with default Server with GUI install. No changes at all to any selection. After the VM boots the following routes will exist.

ip route
default via 172.16.50.2 dev ens160 proto dhcp metric 100
172.16.50.0/24 dev ens160 proto kernel scope link src 172.16.50.134 metric 100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown

If you suspend the then awake the VM the resulting routes are.

ip route
default via 172.16.50.2 dev ens160 proto dhcp metric 100
172.16.50.0/24 dev ens160 proto kernel scope link src 172.16.50.134 metric 100

The VM still thinks the bridge is running. You can use virt-manager to stop and restart the bridge and then the routes return. The more complicated networks behave in the same manner after sleep you need to disable and then reenable each to get them to work again. 

As stated, I can import this exact VM into virtual box and this does not happen. 

Any suggestions are welcome. Thanks.