VPlex KCS Newsletter February 2019

 

For restricted KB articles, please contact VPlex support for further information


KB Article

Link

Audience

VPLEX: Unexpected wan departure due to hardware failure on the WAN-COM module.

https://support.emc.com/kb/511245

Customers

 

 

KB Article

Link

 

VPLEX: How to find the procedure that talks to how to expand a virtual volume.

https://support.emc.com/kb/494892

Customers

 

 

KB Article

Link

 

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

https://support.emc.com/kb/522334

Customers

 

 

KB Article

Link

 

VPLEX: Unable to enable a VS2 Front-End Port

https://support.emc.com/kb/529368

Customers

 

 

KB Article

Link

 

VPLEX: Performance regression for VS2 Metro-IP systems on GeoSynchrony 6.1

https://support.emc.com/kb/528919

 

Customers

 

 

KB Article

Link

 

VPLEX: Management server is not accessible via SSH or Browser

https://support.emc.com/kb/498234

Customers

 

 

 

 

 

New KBs to address NDU issues

 

 

KB Article

Link

 

VPLEX: Custom NDU scripts that prevent the issues in VPLEX-4441, VPLEX-1589 and VPLEX-3647 simultaneously.

https://support.emc.com/kb/524664

Restricted

 

 

KB Article

Link

 

VPLEX: NDU failing to complete when running 'waiting for RecoverPoint splitter'

https://support.emc.com/kb/519226

Employees and Partners

 

KB Article

Link

 

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

https://support.emc.com/kb/523838

Customer

 

 

KB Article

Link

 

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.

https://support.emc.com/kb/523981

Customer

 

 

 

 

 

KBs for issues in 6.0 SP1 P5

 

KB Article

Link

 

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

https://support.emc.com/kb/502886

Customers

 

 

KB Article

Link

 

VPLEX: VS6 Unexpected VPLEX director firmware crash while running GeoSynchrony 6.0 Service Pack 1 Patch 5

https://support.emc.com/kb/514853

Employees and Partners

 

 

KB Article

Link

 

VPLEX: VS6 Mid-plane causes slic1 (IO Module) on director B to go missing or offline either with or without director B reboot.

https://support.emc.com/kb/514683

Employees and Partners

 

 

 

 

 

Note:
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.

 

 

Current Target Codes

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

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

 

 

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

 

  • Karst Q2’FY19 release of 6.1.0.00.00.23

  o Karst DA is targeted to for July 12th 6.1.0.00.00.17 

  • RTO on August 26th
  • Karst GA targeted for August 30th

 

  • “Nalanda” = VPLEX GeoSynchrony 6.2

 

 

End Of Service Life (EOSL)

 

  • VPLEX VE – EOSL Date is 28th February 2019
  • VPLEX VS2 Geo - EOL Date is 31st July 2015
  • VPLEX VS1 – EOSL Date 31st August 2017
  • 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

 

 

 

 

KB Article

Link

 

ETA 501370 EMC VPLEX: Potential silent data inconsistency if the target leg of a FULL Thin Rebuild or migration is a thin device in GeoSynchrony 6.0 Service Pack 1, and later

https://support.emc.com/kb/501370

 

 

 

Customers

 

NOTE**

This issue is specific to FULL Thin Rebuilds and migrations where the target is a thin device

DR1 log rebuilds (including Thin log rebuilds) are unaffected by this issue.

All rebuilds on thick devices are unaffected by this issue.

All rebuilds on thin devices where VPLEX rebuilds are set to thick are unaffected by the issue.

 

 

 

Latest Top 10 Viewed KB Articles:

 

Number

KB Article Title

Link

 

1

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

https://support.emc.com/kb/323253

Customers

2

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

https://support.emc.com/kb/334964

Customers

3

324094 : VPLEX: How to manually configure call home.

https://support.emc.com/kb/324094

Customers

4

330110 : VPLEX: How to reset the admin password

https://support.emc.com/kb/330110

Customers

5

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

https://support.emc.com/kb/457313

Customers

6

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

https://support.emc.com/kb/323313

Customers

7

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

https://support.emc.com/kb/472497

Customers

8

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

https://support.emc.com/kb/336564

Customers

9

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

https://support.emc.com/kb/335182

Customers

10

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

https://support.emc.com/kb/463942

Customers

 

 

 

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