
		Release Notes for HPE VC fv1-1.0.0-1014
		======================================

		       Backdoor for Regular FWU
		       ========================

Once an ICM has been updated using TFWU image fv1-1.0.0-85 ,
you may use standard FWU to update the board to another _UBIFS_ image.
Until we have FWU working through OneView, we have a backdoor for FWU.
Here is the backdoor FWU procedure:

    Download the FWU image, hpe_icm_fv1-1.0.0-1014-2016-10-11.pkg to a server.
	   wget http://hf-cit.us.rdlabs.hpecorp.net:9300/r1.0.0/Potash/production/fv1-1.0.0-1014/hpe_icm_fv1-1.0.0-1014-2016-10-11.pkg

    Rename the FWU image to hpe_icm.pkg.
	   /bin/mv hpe_icm_fv1-1.0.0-1014-2016-10-11.pkg hpe_icm.pkg

    Run the following commands from the same location:

	If your ICM has IPv4 IP:
	   scp hpe_icm.pkg fwupdate@192.168.25.25:.
	   ssh fwupdate@192.168.25.25 apply.update
	   ssh fwupdate@192.168.25.25 activate.update

	If your ICM has IPv6 IP:
	   scp hpe_icm.pkg fwupdate@[fe80::4c7b:94ff:fecb:fbc4%eth0]:.
	   ssh fwupdate@fe80::4c7b:94ff:fecb:fbc4%eth0 apply.update
	   ssh fwupdate@fe80::4c7b:94ff:fecb:fbc4%eth0 activate.update

    Use "fwupdate" for the password.

Since these images are signed, you cannot use regular FWU to update
from a production-signed image to a development-signed image; you have
to use TFWU to go from a production-signed image to a development-
signed image!


			 Notes & Known Issues
			 ====================

1) With this image, the ICM is expected to be managed by OneView. The
   IP address settings for the ICM come from OneView.
