Symptoms

Note:VPLEX GeoSynchrony code levels prior to 6.2.x are End of Service Support (EOSS)For VPLEX GeoSynchrony 6.2.x all versions except 6.2.0.07.00.02 (6.2 P7) are EOSS.Start to plan to upgrade those VPLEX running any version prior to 6.2 Patch 7 to at least target code 6.2 P7 or to the latest code release. Issue:One or more of the following dial homes, for any of the listed FRUs below, has called home; Standby-Power-Supplies-A or B (SPS-A or SPS-B) - VS2: sps@stand-by-power-supply-A: :The specified FRU is not present. [Versions:MS{xx.xx.x.xx.x, xx.xx.x.x, xx.xx.x.xx}, Director{x.x.xxx.xx.x}, ClusterWitnessServer{xx.xx.x.x}] RCA: The specified FRU is not present. Remedy: Check if the correct FRU has been inserted in the slot. If the problem persists, contact EMC Customer Support. sps@stand-by-power-supply-B: :The specified FRU is not present. [Versions:MS{xx.xx.x.xx.x, xx.xx.x.x, xx.xx.x.xx}, Director{x.x.xxx.xx.x}, ClusterWitnessServer{xx.xx.x.x}] RCA: The specified FRU is not present. Remedy: Check if the correct FRU has been inserted in the slot. If the problem persists, contact EMC Customer Support. Sometimes users may see remote cluster reporting on its peer: peer-sps@stand-by-power-supply-A: :The specified FRU is not present. [Versions:MS{xx.xx.x.xx.x, xx.xx.x.x, xx.xx.x.xx}, Director{x.x.xxx.xx.x}, ClusterWitnessServer{xx.xx.x.x}] RCA: The specified FRU is not present. Power-Supplies (psa# or psb# or power-supply-a# or b#) - VS2/VS6: /engine/psa0: :The specified FRU is not present. [Versions:MS{xx.xx.x.xx.x, xx.xx.x.x, xx.xx.x.xx}, Director{x.x.xxx.xx.x}, ClusterWitnessServer{xx.xx.x.x}] RCA: The specified FRU is not present. Remedy: Check if the correct FRU has been inserted in the slot. If the problem persists, contact EMC Customer Support. /engine/psa1: :The specified FRU is not present. [Versions:MS{xx.xx.x.xx.x, xx.xx.x.x, xx.xx.x.xx}, Director{x.x.xxx.xx.x}, ClusterWitnessServer{xx.xx.x.x}] RCA: The specified FRU is not present. Remedy: Check if the correct FRU has been inserted in the slot. If the problem persists, contact EMC Customer Support. /engine/psb0: :The specified FRU is not present. [Versions:MS{x.x.x.x.x, x.x.x.x, x.x.x.x}, Director{x.x.x.x.x}, ClusterWitnessServer{x.x.x.x}] RCA: The specified FRU is not present. Remedy: Check if the correct FRU has been inserted in the slot. If the problem persists, contact EMC Customer Support. /engine/psb1: :The specified FRU is not present. [Versions:MS{x.x.x.x.x, x.x.x.x, x.x.x.x}, Director{x.x.x.x.x}, ClusterWitnessServer{x.x.x.x}] RCA: The specified FRU is not present. Remedy: Check if the correct FRU has been inserted in the slot. If the problem persists, contact EMC Customer Support. power-supply-a0 : PartNo 071-000-543 /SerialNo ASTACxxxxxxxxx /RevNo xxx :The specified FRU is not present [Versions:MS{x.x.x.x.x, x.x.x.x, x.x.x.x}, Director{x.x.xxx.xx.x}, ClusterWitnessServer{x.x.x.x}] RCA: The specified FRU is not present. Remedy: Check if the correct FRU has been inserted in the slot. If the problem persists, contact EMC Customer Support. power-supply-b0 : PartNo 071-000-543 /SerialNo ASTACxxxxxxxxx /RevNo xxx :The specified FRU is not present [Versions:MS{x.x.x.x.x, x.x.x.x, x.x.x.x}, Director{x.x.xxx.xx.x}, ClusterWitnessServer{x.x.x.x}] RCA: The specified FRU is not present. Remedy: Check if the correct FRU has been inserted in the slot. If the problem persists, contact EMC Customer Support. Uninterruptable-Power-Supplies (UPS) - VS2/VS6: ups@UPS-A: PartNo 078-000-052 /SerialNo QSXXXXXXXXXX /RevNo xxxx : The specified FRU is not present. [Versions:MS{x.x.x.x.x, x.x.x.x, x.x.x.x}, Director{x.x.x.x.x}, ClusterWitnessServer{x.x.x.x}] RCA: The specified FRU is not present. ups@UPS-B: PartNo 078-000-079 /SerialNo QSXXXXXXXXXX /RevNo 1XE1 : The specified FRU is not present. [Versions:MS{x.x.x.x.x, x.x.x.x, x.x.x.x}, Director{x.x.x.x.x}, ClusterWitnessServer{xxx.x.x}] RCA: The specified FRU is not present. Battery-Backup-Unit (BBU-a/b#) - VS6: /engine/bbu-a0: PartNo 078-000-123-05 /SerialNo ACPHxxxxxxxxxx /RevNo FFF :The operational state of the specified fru is Faulted. [Versions:MS{x.x.x.x.x, x.x.x.x, x.x.x.x}, Director{x.x.x.x.x}, ClusterWitnessServer{x.x.x.x}] RCA: The state of the specified FRU is faulted Remedy: Contact EMC Customer Support. /engine/bbu-b0: PartNo 078-000-123-05 /SerialNo ACPHxxxxxxxxxx /RevNo FFF :The operational state of the specified fru is Faulted. [Versions:MS{x.x.x.x.x, x.x.x.x, x.x.x.x}, Director{x.x.x.x.x}, ClusterWitnessServer{x.x.x.x}] RCA: The state of the specified FRU is faulted Remedy: Contact EMC Customer Support.

Cause

The call homes listed in the Symptoms section may be due to maintenance work being done, tests of the system, or checks, by those components themselves and as the FRU monitoring portion of the code is not aware of these component tests, or checks by the components. The FRU monitoring code only knows when it sees what it knows as an error for the FRUs it is to report the event via the call home notification mechanism that was setup at the time of initial installation or done at a later date, and to send the end user an e-mail alert and to send a report back to Dell as we monitor the VPLEX product for call home alerts.

Resolution

When an email alert is received by the user for the Dial Home event 0x8a4861d6, FRU not present, they must check and confirm the state of the reported FRU that as covered in this article. Steps for checking the state of a reported FRU not being present:The user is to log in to the VPLEX when any of the call homes listed in the Symptoms section have been reported to check the status of the FRU. If the FRU the alert was reported for shows no error or failure status, the call-home can be ignored.If, when checking the status of a FRU, it is in any other state than indicated in the sample outputs provided below must contact Dell VPLEX Support, by a chat, by calling them or by opening a Service Request (SR) to report the issue and mention this article. How to contact Dell VPLEX Support using Chat: To reach support start by going to Dell Support.com. When at the Welcome to Dell Support page, at the top where you see "Search Dell or Identify your product" enter VPLEX Series, VPLEX VS2 or VPLEX VS6, then scroll down and look on the right side and look for "Contact Technical Support." If you have an Active Service Contract, sign in. If you do not have an Active Service Contract, reach out to your local Dell Representative for further assistance. With the Active service contract and after you have signed in, you should see the Technical Issues page and here you see the options on how to contact VPLEX Support. Follow the steps below to check for the state of the FRUs mentioned in this article, To check the state of any of the below, FRUs requires logging into the management server of the cluster the reported FRU call home was received from. The following steps explain how to find which cluster and component the event was reported from and then how to log in to the management server and VPlexcli to check the current status of the FRU reporting the alert. To determine which cluster and component the call was reported from: In the call home alert message, to find out what cluster and component the event was reported for look for the 'ComponentID' line the issue was reported for, the first number listed in the ComponentID is the clusterID, for example director-2-1-B, the "2" indicates cluster-2. Example of call home: SymptomCode: 0x8a4861d6 Category: Status Severity: Error Status: Failed Component: DIRECTOR ComponentID: director-2-1-B <-- cluster-2, director-2-1-B was where the issue was reported from SubComponent: ZPEM SubComponentID: CallHome: Yes FirstTime: 20xx-09-29T15:27:35.096Z LastTime: 20xx-04-13T17:26:48.047Z Count: 1 CDATA: sps@stand-by-power-supply-B: :The specified FRU is not <<< in the CDATA it indicates the FRU the issue is with present. [Versions:MS{x.x.x.x.x, x.x.x.x.x, x.x.x.x.x}, Director{x.x.x.x.x}, ClusterWitnessServer{x.x.x.x.x}] RCA: The specified FRU is not present. Remedy: Check if the correct FRU has been inserted in the slot. If the problem persists, contact EMC Customer Support. Logging into the VPLEX Login into the management server for the VPLEX cluster the call home was reported from, using the service account credentials. Sample output: login as: service Using keyboard-interactive authentication. Password: Last login: Day Month date HH:MM:SS Year from x.x.x.x <<< IP Address the login is from service@ManagementServer:~> Then access the VPlexcli. Sample output: service@ ManagementServer:~> vplexcli Trying ::1... Connected to localhost. Escape character is '^]'. Enter User Name: service Password: Creating logfile:/var/log/VPlex/cli/session.log_service_localhost_ Logfile_T24531_YYYYMMDDHHMMSS VPlexcli:/> Below are the steps for how to check the state of each FRU that the call home may be for. Standby-Power-Supply (SPS-A or SPS-B) - VS2 only Follow the steps to log in as listed above under Logging into the VPLEX. Run the following vplexcli command to check the state of the Standby-Power-Supplies, ll /engines//stand-by-power-supplies/ Sample Output as reported for cluster-1: VPlexcli:/> ll /engines/*/stand-by-power-supplies/* /engines/engine-1-1/stand-by-power-supplies/stand-by-power-supply-a: Attributes: Name Value ---------------------- -------------- battery-status fully-charged << Shows the battery of the SPS is fully-charged battery-time-remaining 300 seconds operational-status online << online indicates the SPS is good part-number 078-000-050 revision-number A08 serial-number ACLSPxxxxxxxxx Contexts: Name ------------ conditioning /engines/engine-1-1/stand-by-power-supplies/stand-by-power-supply-b: Attributes: Name Value ---------------------- -------------- battery-status fully-charged battery-time-remaining 300 seconds operational-status online part-number 078-000-049 revision-number A06 serial-number ACxxxxxxxxxxxx If the "battery-status" shows charging or unknown and the "operational-status" shows offline or removed, or anything other than fully-charged and online for these two statuses' there is a possible issue, and you must contact Customer Support for further assistance. If the SPS shows 'fully-charged' and 'online', as listed in the above example, this issue can be ignored. Power-Supplies (psa/psb) - VS2/VS6Follow the steps under Logging into the VPLEX. Run the following vplexcli command to check the current state of the power-supplies, ll engines//power-supplies/ Sample Output as reported for cluster-1: VPlexcli:/> ll engines/*/power-supplies/* /engines/engine-1-1/power-supplies/power-supply-a0: Name Value ------------------------------ -------------- onDC false << Note this value operational-status online << note this vaule part-number 071-000-543 revision-number A08 serial-number ASTACxxxxxxxxx temperature-threshold-exceeded false /engines/engine-1-1/power-supplies/power-supply-a1: Name Value ------------------------------ -------------- onDC false operational-status online part-number 071-000-543 revision-number A08 serial-number ASTACxxxxxxxxx temperature-threshold-exceeded false /engines/engine-1-1/power-supplies/power-supply-b0: Name Value ------------------------------ -------------- onDC false operational-status online part-number 071-000-543 revision-number A08 serial-number ASTACxxxxxxxxx temperature-threshold-exceeded false /engines/engine-1-1/power-supplies/power-supply-b1: Name Value ------------------------------ -------------- onDC false operational-status online part-number 071-000-543 revision-number A08 serial-number ASTACxxxxxxxxx temperature-threshold-exceeded false If the 'onDC' shows as false and the 'operational-status' shows as 'online' this issue can be ignored. The alert was most likely a false positive in that there was a battery test occurring on the SPS when the FRU monitor portion of the code ran its check of the FRU states. If the 'onDC' value shows true and the 'operational-status' shows failure, this could indicate an issue. You must contact Customer Support for further assistance. Uninterruptible Power Supply (UPS) - VS2/VS6Follow the steps for Logging into the VPLEX above. Run the following vplexcli command to check the current state of the uninterruptable-power-supplies, ll clusters//uninterruptible-power-supplies/ Sample Output as reported for cluster-1 VPlexcli:/> ll clusters/*/uninterruptible-power-supplies/* /clusters/cluster-1/uninterruptible-power-supplies/ups-2-a: Name Value ------------------------ ------------- battery-replacement-date 03/25/13 < date battery was installed in UPS, if more than 3 years old the UPS should be replaced battery-status fully-charged << Note this value battery-time-remaining 5min operational-status online << Note this value revision-number 1XE1 serial-number QSxxxxxxxxxx /clusters/cluster-1/uninterruptible-power-supplies/ups-2-b: Name Value ------------------------ ------------- battery-replacement-date 03/24/13 battery-status fully-charged battery-time-remaining 5min operational-status online revision-number 1XE1 serial-number QSxxxxxxxxxx If the 'battery-status' shows as fully-charged and the 'operational-status' shows as online this issue can be ignored. The alert was most likely a false positive in that there was a battery test occurring on the UPS when the FRU monitor portion of the code ran its check of the FRU states. If the 'battery-status' shows charging and the 'operational-status' shows online check again in about 5 minutes as the battery test on the UPS may still be in-progress, if after five minutes the check shows the same status contact Customer Support for further assistance. If the 'battery-status' shows charging and the 'operational-status' shows offline or failure, this could indicate an issue. Contact Customer Support for further assistance. For a VS6 call home reporting a BBU as "FRU not present" to "FRU is Faulted," reference KBA 000167061, "VPLEX: Dial Homes "0x8a4861d6" for FRU not present and "0x8a4861d7" for FRU is Faulted, generated for VS6 Battery-Backup-Units" Related KBA for UPS issue:000169524 - VPLEX: SymptomCode 0x8a4830dc UPS load power lower than expected

Support Cases