Pim i

PROCESS/POLICY

Description
This document describes the i11.1.1 release(from here on referred to as the ‘release’) as it applies to existing Scalar i6000 libraries. There are some major points to initially note: 1) In order to upgrade a library to this release one must have the new MCB2 PCBA(Printed Circuit Board Assembly). The release cannot be run on the legacy MCB PCBA. This MCB2 PCBA must be acquired before attempting to upgrade a library. 2) If the library to be upgraded has gen2 robotics, then the new RCU2 PCBA is also needed in order to facilitate upgrade to the release. The legacy RCU cannot be used with gen2 robotics for the release. The RCU2 PCBA must be acquired before attempting to upgrade to the release for this case. 3) For libraries that are going to remain with gen1 robotics after the upgrade, the usage of the legacy RCU is acceptable. 4) Given the variants of hardware, software, and configurations, it is important to understand clearly the existing library firmware and hardware version and the expected final library firmware and hardware version. 5) Note that the release does not support the 6404 FCB(Fibre Channel Blade) and also does not support SDLT drives. i8.x is the version of code that still supports SDLT drives. i10.x code is the version of code that still officially supports the 6404 FCB. 6) All libraries upgraded to the release must be i6000 units (not i2000). Rebranding and process reporting should be done prior to doing the upgrade. The release is an incremental release but it does involve both hardware and software changes if not already at i11. There are a number of changes and features added with the release so it is best to refer to the release notes for complete details. Given the variation of libraries that can be upgraded, the beginning points are broken down into groups as follows: 1) Libraries with gen1 robotics that are at i6.1 – i6.7 versions of software. 2) Libraries with gen1 robotics that are at i8.x versions of