Information about the image - This string must follow the format below: Version: %s\n, Rel-Date: %s\n, Status: %s\n, Type: %s\n, Size: %s\n, Other-Info: %s\n\ Version: The version of the image and should match firmware VPD information. Rel-Date: The release date of the image which should match firmware VPD information of form MM/DD/YYYY. Status: To show if the image is currently Active or Not-Active (backup image ) or Reboot-Active (requires reboot to become active image) and should match firmware VPD information. Type: Boot Rom, Application, Bundled, Diagnostic, Generic Firmware which should match firmware VPD information. A Boot Rom or Application or Diagnostic or Generic image should be used to designate that the image is a single file when updates are performed for the targeted type of firmware. A Bundled image type would be used to designate that the file contains multiple firmware update packages. This should be used if all images in the bundled image have the same version, Release date, . If a bundled image then the image types included in the bundle must be listed in the Other Info. Size: Size of image in KB (Kilobyte) rounded to next 1KB increment. (Note: the MM will read the size of the current image in the IOM and if the size exceeds the allowable space on the MMs internal file system then the MM will not allow the file to be uploaded. In addition if the current image file size is within the limits of the MMs file system but the MM determines the new update image on an external server would exceed the MMs internal file systems allocation then the MM will fail the update. In this case the user on the MM will have to directly transfer the image to the IOM and not use the MMs file system as a source for the update. Other-Info: Any additional information that the IOM wishes to provide. String example 1: (Bundled image that is expanded on IOM) Version: 20.2.2.9, Rel Date: 09/26/2011, Type: Bundled, Status: Active, Size:27500KB, Other Info: Contains Boot ROM and Application images. String example 2: (Application image that is the backup image) Version: 20.1.0.20, Rel Date: 02/27/2012, Type: Application, Status: Not- Active, Size:1200KB, Other Info: None String example 3: (Application image that will become the active image on next reboot) Version: 20.1.0.25, Rel Date: 05/20/2012, Type: Application, Status: Reboot- Active, Size:1200KB, Other Info: None The format of the Firmware Image Information is very important and must be strictly followed. It is intended for other applications to parse and make use of the information. The string is made up of many parts of text information. Each part has the format of the form Token: information_string\n,. Each part consists of a token followed by token information. The end of each part is marked by a new line character, and a comma or a null character. The total length of the string cannot exceed 256 octets.