1EMC CONFIDENTIAL—INTERNAL USE ONLY For VNX, there are 2 Drive part numbers affected; and Disk Drives will update their Firmware to C7A0. Please use the latest Firmware file available: For , C7A ndu ( _E04.fdf) is the correct version. For , C7A ndu ( _04.fdf) is the correct version. ETA / KB : HITACHI VIPER ODFU C7A0 I

2EMC CONFIDENTIAL—INTERNAL USE ONLY 1. SP Collects. Check for any Hardware or Software errors. It is essential we check for any “Bad Block” errors. 2a. If a single 600GB Viper-C drive has more than 25 bad block errors within a 1 hour period, perform the PACO-R XML workaround, and then force a Pro-active copy to Hot Spare (PACO/PACO-R) for the affected 600GB Viper-C drive. 2b. Create dispatch to have faulted drive replaced and postpone activity. Place note in dispatched SR to re- schedule activity once the drive has been replaced and update the individual who scheduled the ODFU. 3. If a single Viper drive has 25 bad blocks errors or less within the hour, or if bad blocks are against other drive types, allow normal backend process to resolve media errors. Perform the PACO-R XML workaround, and perform ODFU as normal. ETA / KB : HITACHI VIPER ODFU C7A0 SP COLLECTS/BAD BLOCK ERRORS I

3EMC CONFIDENTIAL—INTERNAL USE ONLY EXAMPLE OF BAD BLOCK ERRORS Note both 2_0_5 and 2_0_9 have >25 Bad Block Errors. Both drives must be examined for the timestamps of the errors

4EMC CONFIDENTIAL—INTERNAL USE ONLY EXAMPLE OF BAD BLOCK ERRORS Note that not all Bad Block errors have been displayed (“76 lines deleted”). You must therefore check Triiage_Splogs.txt for all Bad Block errors against these 2 drives.

5EMC CONFIDENTIAL—INTERNAL USE ONLY EXAMPLE OF BAD BLOCK ERRORS Disk Drive 2_0_9 shows >25 Bad Block errors within a 1 hour period.

6EMC CONFIDENTIAL—INTERNAL USE ONLY EXAMPLE OF BAD BLOCK ERRORS Disk Drive 2_0_5 shows >25 Bad Block errors within a 1 hour period. However……..pto…..

7EMC CONFIDENTIAL—INTERNAL USE ONLY EXAMPLE OF BAD BLOCK ERRORS Note that drive 2_0_5 was replaced on 04/03/15 at 15:57:04. According to Triiage_Splogs, no further Bad Blocks reported against that drive following replacement of the drive.

8EMC CONFIDENTIAL—INTERNAL USE ONLY ETA / KB : HITACHI VIPER ODFU C7A0 COPY TO HOT-SPARE UNISPHERE I

9EMC CONFIDENTIAL—INTERNAL USE ONLY “naviseccli –h copytohotspare -initiate” e.g. “naviseccli –h copytohotspare 0_0_7 – initiate” ETA / KB : HITACHI VIPER ODFU C7A0 COPY TO HOT-SPARE CLI COMMAND I

10EMC CONFIDENTIAL—INTERNAL USE ONLY R32 P217: Contains the improved PACO, “PACO-R”. If Block OE is already at R32 P217, then there is no need to apply the PACO-R XML fix. Perform ODFU to C7A0 for any 600GB Viper C drives. ETA /KB : HITACHI VIPER ODFU C7A0 BLOCK OE VERSIONS. I

11EMC CONFIDENTIAL—INTERNAL USE ONLY R32 P209/215/216: Update PACO to PACO-R by running the script contained in KB or by manually updating via flarecons.KB Perform ODFU to C7A0 for any 600GB Viper C drives. If a code upgrade is scheduled to any Block OE below P217, please update SR notes of the upgrade SR to instruct UE to implement PACO-R XML workaround post- upgrade. ETA /KB : HITACHI VIPER ODFU C7A0 BLOCK OE VERSIONS. I

12EMC CONFIDENTIAL—INTERNAL USE ONLY R32 P207 or less: Discuss with customer the scheduling of a code upgrade to R32 P216 (Target) or R32 P217. Perform ODFU to C7A0 for any 600GB Viper C drives. Please note for Unified systems, Block OE R32 P217 requires File OE Please be aware of other VNX systems customer may have already upgraded, or scheduled to be upgraded. Customer will most likely want to keep all systems running the same code. ETA /KB : HITACHI VIPER ODFU C7A0 BLOCK OE VERSIONS. I

13EMC CONFIDENTIAL—INTERNAL USE ONLY Upgrade all 600GB Hitachi Viper C drives to C7A0. Attach Post SP Collects to the SR. Instruct customer to wait 12 hours before putting the affected drives in to production. Direct customer to KB and the whitepaper attached for additional instructions regarding LUN binding.KB ETA /KB : HITACHI VIPER ODFU C7A0 PERFORMING ODFU. I