You can try using the svcuser account...or...if your GUI is up and running, you can temporarily give root access to log into the vipr nodes by changing a setting.   In "System" -> "General config"...select the security tab...and set the bottom 2 setting, Permit root console login" and "Permit root ssh access", to YES

Maybe that will help!

Also...while I don't know the exact issue you are seeing, "gateway" issue could be a problem with your nodes OVF settings...you may want to check those for your nodes:

to login to the console from virtual machine console, you can use svcuser/svcuser account - that's default password unless you change it in the UI during initial configuration.

once you are in, you can issue command "su -" to elevate to root account, it will ask you for credentials, and the default password for root account is "ChangeMe".

you may not log in directly as root until you allow it via API call or using UI Configuration as Jarrell described above.

I tried svcuser / svcuser but that doesn't work. I did not change anything during install and I can't get to the UI to change things since the VM network doesn't come up due to the gateway issue. I want to look on the VM to see how the network is configured. The settings match those shown in the link posted by Jay above.

Check the actual configuration settings in the properties for the vAPP: IP, gateway, etc. and make sure that those are correct – no missing entries. These would be found in vCenter, on the vApp for Controller right-click on the container and “Edit Settings”. We want to make sure that the values are those used during deployment. You can always make a snap of the VM’s prior to doing any changes (if you have space and permissions to perform that function).

default is svcuser / ChangeMe after a fresh deployment. But in your case, I would better check the VM and vApp settings in your vCenter. (boot order on vApp, ISO mounted on the VM...)