VPlex KCS Newsletter August 2019

VPlex KCS Newsletter August 2019


***** The VPlex Team are now producing Video KB articles that can be found on YouTube *****



KB Article



VPLEX: AIX HBAs not logged into the VPLEX after host reboot





KB Article



VPLEX: How to interpret FC driver responses to Emulex chip errors in GeoSynchrony 6.1





KB Article



VPLEX: adding / removing an RPA from VPlex





KB Article



VPLEX: How to import a VPLEX license file




KB Article



VNX: Setting the Pool LUN default and allocation ownership correctly (User Correctable)





KB Article



VMware: Interpreting SCSI sense codes in VMware ESXi and ESX (289902)






New KBs to address NDU issues


KB Article



VPLEX: Director witness polling IO pause during NDU may cause Data Unavailable (DU).




KB Article



VPLEX: Stuck I/O may occur following a NDU rollback when I/O forwarding is active and a Data Unavailable (DU) situation may occur due to this issue.





KBs for issues in 6.0 SP1 P5


KB Article



VPLEX: For VS6 Hardware Possible Total Cluster Outage (TCO) during NDU I/O Forwarding Phase due to FCID differences




Do not dispatch for replacement of any parts for this issue.

It is first to be escalated to engineering for their review and recommendation of what action(s) need to be taken.



New Knowledge Base Articles with VS6/6.x:

458149 - VPLEX: Restoring System after Total Cluster Outage (TCO) and the system may no longer be restarted due to metadata corruption

469587 - VPLEX: Auto-resume attribute set to false on Distributed Device causes DU after cluster partition 

487310 - deals with VS2s that were part of the VS1 to VS2 Generational Upgrade (GenU)
There is now a process to convert a VS2 with non-standard port WWNs to standard port WWNs and this is covered in this KB

485956 - deals with failure when attempting to apply the VS2 settings on VS6

485957 - deals with performance impact during a VS2 Metro-FC to VS6 Metro-FC GenU while in mixed mode

487615 - ESA-2016-102, EMC VPLEX Security Update for Multiple Embedded Component Vulnerabilities*

*Note: these security vulnerability fixes are only for GeoSynchrony 6.0P1, they were not back ported to 5.5.x or 5.4SP1P5,

due to some kernel changes between 6.0 and 5.5

488848 - VPLEX: VS6: In Metro GenU, disabling the I/O Modules (IOM) on VS6 fails after ‘transferIO’ because CLI has connectivity to

remote directors

488851 - VPLEX: VS6: In Metro GenU, when upgrading the second cluster, stopping of the VS2 director fails

488852 - VPLEX: VS6: In Metro GenU, from VS2 to VS6, during the post upgrade validation step of cluster-2, there are management

                 connectivity errors

492332 - VPLEX: Slot-ID and TLA are not set during the course of the VS2 engine expansion procedure

492830 - VPLEX:GeoSynchrony upgrade to 6.0 Service Pack 1 Patch 1 will fail for certain VS2 configurations has been approved and published.

492966 - VPLEX: Migrate Certificates from SHA-1 to SHA-2

495036 - VPLEX: How to address Issues with VS2 to VS6 hardware upgrades

495287 - VPLEX: Boot from SAN not working on VPLEX VS6
502886 - VPLEX: For VS6 Hardware Possible Total Cluster Outage (TCO) during NDU I/O Forwarding Phase due to FCID differences
510645 - VPLEX: Checking for initiators logged in during VPLEX VS2-to-VS6 GenU
519226VPLEX: NDU failing to complete when running 'waiting for RecoverPoint splitter' for GeoSynchrony 6.0 SP1 P7
520431 - VPLEX: VS6 Unexpected Director OS Reboot
526458 - VPLEX: Playbook for VPLEX VS2 to VS6 Hardware Generational Upgrade (GenU) – (For Dell EMC use only)
527524 - VPLEX: Metro-FC with FCIP WAN performance interoperability issue at GeoSynchrony 6.1
529368 - VPLEX: Unable to enable a VS2 Front-End Port – NEW 1/17/2019

Knowledge Base Articles you need to be aware of:

465475 - deal with known Stuck I/O issues and using the OSD to assist in determining where the issue lies

335187 - VPLEX: How to determine the GeoSynchrony code versions for VPLEX. (now covers 6.0.x)



Dells Fiscal Year schedule for 2019, written as FYxx/Qx:

FY20/Q1 – February, March, April (2019)

FY20/Q2 – May, June July (2019)

FY20/Q3 – August, September, October (2019)

FY20/Q4 – November, December (2019), January (2020)



Current Target Codes

GeoSynchrony 5.5 Service Pack 2 Patch 4 ( as of 6th April 2018

GeoSynchrony 6.0 Service Pack 1 Patch 7 ( as of 15th May 2018

GeoSynchrony 6.1.x (Karst) was released in September 2018


  • Karst Q2’FY19 release of
    • Karst DA is targeted to for July 12th
    • RTO on August 26th
    • Karst GA targeted for August 30th


  • “Nalanda” = VPLEX GeoSynchrony 6.2

End Of Service Life (EOSL)


  • VPLEX VS1 – EOSL Date 31st August 2017
  • VS2 VPLEX-Geo went EOSL 31 July 2018
  • VPLEX VE – EOSL Date is 28th February 2019
  • 5.1.x EOSL on 30 April 2016
  • 5.2.x EOSL on 30 April 2017
  • 5.3.x EOSL on 30 April 2018
  • 5.4.x EOSL on 30 April 2019



Popular KB’s used last month:


KB Article Title



323253 : VPLEX: How to collect logs from a VPLEX Instance



334964 : VPLEX: How to restart VPlexManagementConsole to refresh VPLEX CLI/GUI



324094 : VPLEX: How to manually configure call home.



330110 : VPLEX: How to reset the admin password



457313 : VPLEX: 0x8a4a91fa / 0x8a4a31fb Management Server partitions full or exceeded xx percent threshold limit



323313 : VPLEX: How to perform a Basic Health check using VPlexcli



472497: VPLEX: Logical-units and Array Connectivity show as degraded



336564 : VPLEX: How to identify ports on a VPLEX director with low Rx and/or TX power - 0x8a54600f, 0x8a36303a, 0x8a363039



335182: VPLEX: Slow performance on VPLEX with a workload consisting of medium to large outstanding queue depth of large block reads



463942: VPLEX: Random temporary loss of connection to storage devices and/or performance degradation on ESXi hosts from version 5.5 u2





Useful to know Articles:


  • KB# 484453- VPLEX: Best Practice Guidelines – Master Article [https://support.emc.com/kb/484453]
    • This master KB article provides links to up to date VPlex Best Practices documents


****With swarm requests increasing the following KB articles will assist in initiating and engaging  in a successful collaboration******


  • KB#484448- VPLEX: How to collaborate with VPlex Support [https://support.emc.com/kb/484448]
    • This KB article provides a template for the case owner to fill out
    • The article also requests VPlex collect-diagnostics logs and provides the link to the KB article on how to collect these


  • KB#336056- How To Collaborate with the XtremIO Team [https://support.emc.com/kb/336056]
    • This KBA outlines the information needed in order to effectively collaborate with the XtremIO support team


  • KB#335164- Connectrix: How to collaborate with the Connectivity Team [https://support.emc.com/kb/335164]
    • This KB article outlines how to collaborate with Connectivity
    • This will enable the Connectivity team to efficiently assist in swarm requests



The following articles can be provided to the customer for gathering Host Grabs to avoid unnecessary collaborations with the Host teams:

  1. How To Create Solaris Grabs: https://support.emc.com/kb/468243
  2. How To Run EMC Grabs On An AIX Host: https://support.emc.com/kb/335706
  3. How To Create Linux Grabs: https://support.emc.com/kb/468251
  4. How To Run EMC Grabs on HP-UX: https://support.emc.com/kb/335700
  5. What logs need to be collected for Microsoft Windows-based EMC software?: https://support.emc.com/kb/304457
  6. How do I run an ESX or ESXi EMCGrab?: https://support.emc.com/kb/323232


** Recovery Procedures **

Recover procedures for data loss events in underlying back end storage arrays explaining what VPlex can and cannot do to recover data.


VPlex symptom: dead storage-volume


VNX Uncorrectables:

https://support.emc.com/kb/488035: VNX1/2: Uncorrectables/Coherency reported on VNX/VNX2 provisioned to a VPLEX (where device is marked as Dead due to SCSI check Condition 3/11/0) (DellEMC correctable)


Raid-1 device recovery:

https://support.emc.com/kb/470385 Recovering a VPLEX Metro Geo leg for distributed devices after storage failure or Data Loss on that leg occurred.

Additional info:

  • Solve procedure generator VPlex > VPlex procedures > administration procedures > manage > Recovering a raid-1 leg after experiencing data loss due to backend array failure this is a more detailed version KB 470385 above
  • KB 488035 above also has many supporting KB’s and doc’s