I've been working on this and the answer is "not easily".
I changed the IP address of a V6.1.0 VDP appliance through the configuration web portal (yes you can access that from the setting icon on the top right) and it does change the IP address of the overall appliance, but leaves some other important settings unchanged, so that certain aspects of the tomcat service fail.
The overall VDP appliance will load, then get stuck with some error messages-- after a very long timeout (more than 40 minutes) it will proceed, but you can no longer manage the server. The web portal will connect, but won't get data from the "proxy" and you can't manage the services or see anything. Not sure if this was fixed in the 6.1.1 update.
You can still ping the VDP appliance at the new IP address and use putty to log into it. I would guess that someone very savvy with SUSE Linux could fix things through a putty login to the VDP appliance, but I've not seen instructions on this.