Dell Unity: Lagerprocessorer vises som genstart i brugergrænsefladen, men ikke i CLI, og ingen fejlbehæftede LED'er (kan rettes af brugeren)

Summary: Denne artikel forklarer, hvorfor Unisphere-brugergrænsefladen muligvis viser SP erne forringet og genstarter, når de er i normal tilstand.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

SFP (Small Factor Pluggable) vises som manglende én gang i logfiler, og senere vises den som god.
SFP'er er kendt for at være uopdaget, hvis de har lidt støv eller ikke er helt indsat i porten.
Det er en almindelig faktor for forringelse af ydeevnen, da det forårsager konstante afbrydelser og kan endda være ansvarlig som en langsom dræningsenhed.

I Unisphere-brugergrænsefladen vises lagerprocessorerne som genstarter og i forringet tilstand ved 'SYSTEM' > , 'Service' > , 'Serviceopgaver'.

I Unisphere-brugergrænsefladen vises lagerprocessorerne som genstarter og i forringet tilstand ved 'SYSTEM' > , 'Service' > , 'Serviceopgaver'.


I en SSH-terminal, der bruger CLI, er begge SP'er imidlertid i normal tilstand.
Dette er indtil videre set i Unity OE-version 4.5.1.0.5.001.

Eksempel:

service@CKMxxxxxxxx spa:~/user# svc_diag
======== Now executing basic state ========
* System Serial Number is: CKMxxxxxxx
* System Model Number is: Unity 500
* System Friendly Host Name is: CKMxxxxxxxx
* Current Software version: c4dev_PIE_3786R-4.5.1.0.5.001.1552025209-GNOSIS_RETAIL
* Unisphere IP address(es): xx.xxx.xxx.xx xxxx::xxx:xxxx:xxxx:xxxx
* SSH Enabled: true
* FIPS mode: Disabled
* Boot Mode: Normal Mode
* Post Faults:  0x0000
* Backend Faults:       0x0000
* Boot Faults:  0x0000
* Rescue Reason:        0x0000
* Rescue reason for code 0x0000 - No faults detected.
* SP Service Hint Code: <None>

Cause

Denne særlige situation opstod ved installation af nye I/O-moduler.
Forpligtelsen blev ikke fuldført på grund af en ikke-optimal SFP, hvorfor sundhedsrelaterede operationer midlertidigt blev deaktiveret (svarende til hvad der sker under opgraderinger).
Da tilstandsundersøgelsen var deaktiveret, kunne systemet ikke identificere den korrekte status for lagerprocessorerne og rapporterede en tidligere kendt status for "genstart".

Du kan bekræfte, at det er det samme problem, ved at kontrollere følgende logfiler:
/var/tmp/ptm/ptm.log
/EMC/C4Core/log/c4_safe_ktrace.log

Dette kan ses live ved at køre kommandoerne på en SSH-terminal eller i Triaged Service Data Collection-logfiler:

Kommando/log #1: 
cat /var/tmp/ptm/ptm.log

Forventet output: 
=====================================Tasks=====================================
10:56 [ 16/22 ]  Core reboot sp if required (local)                  10 minutes
Start at: Thu May 23 10:56:19 2019
Complete at: Thu May 23 10:56:19 2019
===============================================================================
10:56 [ 17/22 ]  Core start c4 (local)                                5 minutes
Start at: Thu May 23 10:56:19 2019
Task Manager was terminated unexpectedly with signal <TERM>
.... <there might be a few extra lines here > ....
Previous failure detected. Not auto-restarting.
Kommando/log #2: 
less /EMC/C4Core/log/c4_safe_ktrace.log

Og kig efter SFP- eller mezzaninrelaterede begivenheder.
Vi kan se, at noget gik galt under installationen af de nye I/O-moduler: 
c4_safe_ktrace   INFO OBJ 3 RP:MEZZ(SP: 0, Slot: 0): fbe_base_env_send_resume_prom_read_async_cmd entry.
c4_safe_ktrace   INFO OBJ 3 RP:MEZZ(SP: 0, Slot: 0): Read async completed, workItem 0x7f2486432760, resumeStatus DEVICE_NOT_VALID_FOR_PLATFO
c4_safe_ktrace   INFO OBJ 3 100C0 : ModMgmt: CLEAR enclFaultLedReason Mezzanine RP Fault. <<<====== Fault detected in Root Port (RP)
..........
c4_safe_ktrace   INFO OBJ 3 100C0 : fbe_module_mgmt_check_module_state, SPB Mezzanine 0, state:ENABLED, substate:GOOD
c4_safe_ktrace   INFO OBJ 3 100C0 : fbe_module_mgmt_check_port_state Setting SPB Mezzanine 0, Port 0, state ENABLED, substate GOOD
c4_safe_ktrace   INFO OBJ 3 100C0 : fbe_module_mgmt_check_port_state Setting SPB Mezzanine 0, Port 1, state MISSING, substate MISS_SFP <<<=== SFP not detected 
c4_safe_ktrace   INFO OBJ 3 100C0 : fbe_module_mgmt_check_port_state Setting SPB Mezzanine 0, Port 2, state ENABLED, substate GOOD
c4_safe_ktrace   INFO OBJ 3 100C0 : fbe_module_mgmt_check_port_state Setting SPB Mezzanine 0, Port 3, state ENABLED, substate GOOD
c4_safe_ktrace   INFO OBJ 3 100C0 : fbe_module_mgmt_check_port_state Setting SPB Mezzanine 0, Port 4, state ENABLED, substate GOOD
c4_safe_ktrace   INFO OBJ 3 100C0 : fbe_module_mgmt_check_port_state Setting SPB Mezzanine 0, Port 5, state ENABLED, substate GOOD

Resolution

Du kan løse dette problem ved at forpligte I/O-modulerne igen, da de oprindeligt mislykkedes, ved hjælp af nedenstående kommandoer.
Seddel: Disse kommandoer kræver ikke root, men kræver et sundt system, så før du kører, skal du bekræfte, at dit system er fuldt operationelt, som sådan:

Kommando #1: 

uemcli -no /sys/general healthcheck -output csv -detail

Eksempler på output:
#1 (IKKE optimal) - fortsæt ikke, før de viste fejlproblemer er løst). 
"Error code"
"Warning: One or more asynchronous replication sessions, or one or more NAS Server or file system synchronous replication sessions, exist. This could cause problems during upgrade. Pause the replication sessions on the production array prior to starting the upgrade and resume them after completing the upgrade. [Warning Code: platform::check_replication_health_4]"
"Warning: One or more NAS servers may not be in a healthy state. You can continue with the upgrade, but it is recommended that you record the error code and contact your service provider. [Warning Code: dm::check_nas_servers_health_3]"
Operation completed successfully.

Bemærk: Der står "Opgrader", fordi det er den kommando, der bruges, før du udfører NDU (Non-Disruptive Upgrades). Årsagen til, at disse meddelelser vises, er imidlertid, at systemet (begge SP'er) skal genstartes.
Kommando #2 kan også kræve genstart, derfor er det vigtigt, at dette helbredstjek passerer uden [Fejlkode:].
[Advarsler] kan ignoreres, men kommandoprompt #2 er meddelelsen "Do you still want to continue," Og du kan indtaste "Ja". Dell Support anbefaler dog at afhjælpe alle advarsler og fejl i tilstandstjekket, før du fortsætter.
 
Hvis du vil genstarte en storageprocessor, skal du følge de trin, der er beskrevet i KB Dell Unity: Sådan genstarter du en lagerprocessor (kan rettes af brugeren)

#2 (Optimal) - du kan gå til Kommando #2 
"Error code"
Operation completed successfully.


Kommando #2: 

svc_change_hw_config -e

Forventet output: 
service@CKMxxxxxxxx spa:~/user# svc_change_hw_config -e
Checking if both SPs are in Normal mode...OK
INFO:    Beginning eSLIC or CNA Hardware Upgrade...
WARNING: This operation will cause several reboots to occur on the Storage Processors.
WARNING: Do NOT proceed further if the user is unaware of this downtime!
==============================System Information===============================
Task Manager Command:            /opt/ptm/task_mgr.pl
Starts at:                       Sat Oct  5 10:03:47 2019
Dual SP:                         Yes
SP:                              b
Platform:                        OBERON
Original Primary:                Yes
Model:                           Unity xxx
Serial Number:                   xxxxxxxxxxxxx
Total number of attempts:        0
===============================================================================

==========================Time Estimate for All Tasks==========================
Task name [ 22 tasks in total ]                      Estimated     Status
                                                           Time(Minutes)
  1         Slic wait for system ready slic (local)         3
  2      Core run pre upgrade health checks (local)         2
  3         ESLIC check eslic configuration (local)         1
  4                  Core enable auto start (local)         0
  5                Core clear boot counters (local)         0
  6               Core clear boot counters (remote)         0
  7                 Core force vdms off sp (remote)         2
  8                  ESLIC set esp boolean (remote)         1
  9                 Core disable quickboot (remote)         1
 10         Core reboot peer sp if required (local)        10
 11                          Core start c4 (remote)         5
 12              Core wait for system ready on peer         3
 13                  Core force vdms off sp (local)         2
 14                   ESLIC set esp boolean (local)         1
 15                  Core disable quickboot (local)         1
 16              Core reboot sp if required (local)        10
 17                           Core start c4 (local)         5
 18              Core wait for system ready (local)         3
 19         ESLIC final configuration check (local)         1
 20                           Core clean up (local)         0
 21                      Core clean up peer (local)         0
 22                 Core disable auto start (local)         0

===============================================================================

=========================Estimated Time for Services ==========================
Current Time:                                      10:03
Estimated Time when eSLIC will be complete:      10:52
===============================================================================
Do you wish to continue [ yes or no ]? >
Når du har indtastet "ja"Og tryk på"Retur"-Tasten, skal du se nedenstående output: 
=====================================Tasks=====================================
20:41 [ 17/22 ]  Core start c4 (local)                                5 minutes
===============================================================================
20:41 [ 18/22 ]  Core wait for system ready (local)                   3 minutes
===============================================================================
20:41 [ 19/22 ]  ESLIC final configuration check (local)             30 seconds
===============================================================================
20:41 [ 20/22 ]  Core clean up (local)                                5 seconds
===============================================================================
20:41 [ 21/22 ]  Core clean up peer (local)                           5 seconds
===============================================================================
20:41 [ 22/22 ]  Core disable auto start (local)                      5 seconds
===============================================================================
===================================SUMMARY=====================================
Status:                   Success
Actual Time Spent:        16452 minutes
Total Number of attempts: 1
Log File:                 /var/tmp/ptm/ptm.log
=====================================END=======================================
Disse er også logget ind /EMC/backend/log_shared/EMCSystemLogFile.log:
  
Platform_Basic      30018 [NOTICE] Audit: Service user executed the following service script command: svc_change_hw_config -e
IOModule            30010 [INFO] User: Starting the hardware configuration commit operation
Platform_Basic      30018 [NOTICE] Audit: Service user executed the following service script command: svc_dc -pbc udoctor
IOModule            30014 [INFO] User: Completed task <17> of <22> (Restarting services)
IOModule            30014 [INFO] User: Completed task <18> of <22> (Waiting for system ready state)
IOModule            30014 [INFO] User: Completed task <19> of <22> (Checking if upgrade complete)
IOModule            30014 [INFO] User: Completed task <20> of <22> (Cleaning up)
IOModule            30014 [INFO] User: Completed task <21> of <22> (Cleaning up)
IOModule            30014 [INFO] User: Completed task <22> of <22> (Disabling automatic restart)
IOModule            30011 [NOTICE] User: The hardware configuration has been successfully committed
Health              6044f [INFO] User: Storage Processor SP A is operating normally
Health              6044f [INFO] User: Storage Processor SP B is operating normally

Når outputtet ovenfor er blevet vist, skal du opdatere Unisphere-brugergrænsefladen og se, om status er ændret tilbage til normal (forventet).
Hvis ikke, skal du kontakte Dells tekniske support og henvise til denne artikel.


Bemærk: Flere oplysninger om denne kommando findes i dokumentet Tekniske bemærkninger til Dell EMC Unity-familieservicekommandoer™ på https://www.dell.com/support/home/en-us

 

Additional Information

BEMÆRK: Der er også et muligt dårligt møntcellebatteri, der forårsager et falsk positivt SP-genstartsproblem i brugergrænsefladen.
Se KB 000069296 Dell Unity: Møntcellebatteri på storageprocessoren (kan rettes af Dell)

Affected Products

Dell Unity 300, Dell EMC Unity Family

Products

Dell EMC Unity 300F, Dell EMC Unity 350F, Dell EMC Unity 400, Dell EMC Unity 400F, Dell EMC Unity 450F, Dell EMC Unity 500, Dell EMC Unity 500F, Dell EMC Unity 550F, Dell EMC Unity 600, Dell EMC Unity 600F, Dell EMC Unity 650F , Dell EMC Unity Family |Dell EMC Unity All Flash, Dell EMC Unity Family, Dell EMC Unity Hybrid ...
Article Properties
Article Number: 000056107
Article Type: Solution
Last Modified: 04 Dec 2025
Version:  6
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.