The .img file will remimage the sensor to that version leaving the sensor with factory config defaults (normally this is done by interrupting the bootup and using rommon to tftp the .img file to the sensor). The .zip file is only used by VMS/MC or CSM to upgrade a sensor. The .pkg file is for upgrading a sensor from an older version and preserving the pre-upgrade sensor config using CLI or IDM.
If you reimage (.img) to 5.1(5)E1 then you are done. The other packages are of no use.
However, if you were at 5.1(4) and you wanted to upgrade your sensor, then you would use either IPS-K9-5.1-5-E1.pkg (CLI, or IDM) or IPS-CS-MGR-K9-5.1-5-E1.zip (MC or CSM). This would upgrade your sensor to 5.1(5)E1.
If you were at 5.1(5) and no engine level (could consider this to be E0) then you can apply the engine update: IPS-K9-engine-E1-req-5.1-5.pkg (CLI or IDM) or IPS-CS-MGR-engine-E1-req-5.1-5.zip (MC or CSM). This would upgrade your sensor to 5.1(5)E1
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...