![]() ![]() This release also asked for the serial number, the IP address and login credentials, but it didn’t checked the version of the 3PAR OS (or it doesn’t care if it’s unknown). At this point I had a functional SP running software release 4.1 MU2. This time, I was able to finish the “Moment of Birth” (MOB). So I grabbed a copy of the VSP 4.1 MU2 with P009 and deployed the VSP. I knew that earlier releases of the VSP doesn’t check the serial number of the StoreServ or the version of the 3PAR OS. While waiting for the 2nd level support, I was thinking about a solution. ![]() After a short remote session this morning, the support case was escalated to the 2nd level. But could cause the missing patch this behaviour? I called HP and explained my guess. Hmm… I knew that P003 was mandatory for the VSP 4.3 MU1 and 3PAR OS 3.2.1 MU3. I entered the SP ID, SP networking details, a lot other stuff, the serial number of the StoreServ, the IP address, credentials finally got this message: StoreServ HP 3PAR OS version validation failed - unable to retrieve StoreServ's HP 3PAR OS version. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |