Unsolved
19 Posts
0
1235
Vplex Kdrive is not running
Hi Team
We have vPlex local (VS2) where in I found warning alert that
“Operational status: Degraded “
Transitioning Indication : disk(s) not visible from all director
Health State: Minor Failure
Health Indication : engine-1-1:director-1-1-A: Vplex Kdrive is not running
Local COM:
fc-port-group-0: FAIL-Failed to determine expected connectivity
fc-port-group-1: FAIL-Failed to determine expected connectivity
We have 3 arrays connected to vplex which are showing unknow under Storage Array->connectivity
Can some one please help me what would cause of this error and method to fix.
Thanks
ankur.patel
286 Posts
0
February 11th, 2022 14:00
Did you open a support ticket for this? I think one needs more info to troubleshoot
rit1
19 Posts
0
February 12th, 2022 17:00
Hi Ankur
Unfortunately no,as system is just expired few days ago and unable to log case.
Can you give hit or link how to fix issue
Here is health check result of vplex
VPlexcli:/> health-check --full
Configuration (CONF):
Checking VPlexCli connectivity to directors.................... OK
Checking Directors Commission.................................. OK
Checking Directors Communication Status........................ Error
Checking Directors Operation Status............................ Error
Checking Inter-director management connectivity................ Error
Checking ports status.......................................... Warning
Checking Call Home Status...................................... OK
Checking Connectivity.......................................... Error
Checking COM Port Power Level.................................. Error
Checking Meta Data Backup...................................... Warning
Checking Meta Data Slot Usage.................................. OK
Back End (BE):
Checking Unreachable Storage Volumes........................... OK
Checking Degraded Storage Volumes.............................. OK
Checking Unhealthy Virtual Volumes............................. OK
Back end array status.......................................... Error
Validating paths to back end arrays............................ OK
Validating LUN limit per IT-Nexus.............................. Error
Front End (FE):
Checking Storage Views......................................... OK
Checking Front End HA.......................................... OK
Checking Front End Path........................................ Error
Cache:
Checking for sub-pages writes(25% or above of total writes).... Error
Checking for IO Processing Time................................ Error
Consistency Group Health:
Consistency Group Health....................................... OK
Consistency Group Setting...................................... OK
Director Health Status:
Checking Director Hardware..................................... Error
Checking SSD Hardware.......................................... Error
Checking Director RPMs......................................... Error
Recent Front-End/Back-End I/O Aborts:
ankur.patel
286 Posts
0
February 15th, 2022 07:00
Im sorry, Ive not seen this error before and feel it will take log analysis to determine the issue. The account team might have options to get support engaged
rit1
19 Posts
0
February 17th, 2022 01:00
Hi Ankur
I noticed that Director-A is not listing or showing it's ports when i executed below cmd, However i can see FE and BE ports list on Director-B
VPlexcli:/engines/engine-1-1/directors/director-1-1-A/hardware/ports>
And also when i checked uptime,i can see uptime only for Director-B,but for Director-A it's show blank
VPlexcli:/engines/engine-1-1/directors/director-1-1-A/hardware/ports> uptime
Director director-1-1-B: 1794 days, 12 hours, 55 minutes, 15 seconds.
Director director-1-1-A: -
So i m thinking if reboot of Director-A might help us to fix the issue .
Can some one please suggest or advise if reboot is only option or any other way ?
Thanks