Symptoms

When Dell PowerStore encounters a problem, an error alert is generated to help identify the issue. This article explains the different possible causes and the relevant solutions for these error alerts. If your problem is not resolved despite the solution that is provided, check the technical support contact options. Note: Cannot find the information that you need? Let us know using the feedback form at the bottom of this article.

Cause

Cause is self-explanatory in the Alert Texts mentioned in Resolution section.

Resolution

Alert IDWITNESS_CONNECTIVITY_DISCONNECTEDAlert TextComplete connection loss detected for witness service with name %(witness_name).Error Code0x03300101ImpactIf an associated metro session fractures, the metro session's role (preferred or non-preferred) will determine which side of the metro session remains host accessible.Resolution Solution: Verify that a client outside of the PowerStore can access the witness service's host system. This can be achieved by testing network connectivity with tools like ping or telnet on port 443.If the witness service is unreachable, then investigate whether the witness service's host is operational. Verify whether the IP address or hostname was recently changed on the host. If yes, please remove the witness service configuration from the PowerStore and reconfigure it using the new IP address or hostname. If the host is operational and the networking is operating normally then attempt to restart the witness service.If access is successful, then investigate potential networking issues on the PowerStore. Review any recent networking changes on the PowerStore which may be inhibiting connectivity. Additionally, it may be helpful to investigate the physical network connections (cards, cables, etc.) for all PowerStore appliances. If everything listed above is ok, attempt to delete the witness in PowerStore and repeat the registration process from the beginning.Lastly, investigate any changes in the network topology, such as changes in switch settings, routing tables, DNS, etc. Alert IDWITNESS_CONNECTIVITY_PARTIALLY_DISCONNECTEDAlert TextPartial connection loss detected for witness service with name %(witness_name).Error Code0x03300102ImpactIf an associated metro session fractures, the metro session's role (preferred or non-preferred) will determine which side of the metro session remains host accessible.Resolution Solution: Verify the state and network connectivity of the witness, and restore to operation. Alert IDWITNESS_CONNECTIVITY_APPLIANCE_DISCONNECTEDAlert TextAppliance connection loss detected for witness service with name %(witness_name). Disconnected appliances: %(disconnected_appliances)Error Code0x03300103ImpactFor resources that reside on the disconnected appliances, if the metro session fractures, the session's role (preferred or non-preferred) will determine which side of the session remains host accessible.Resolution Solution: Verify that a client outside of the PowerStore can access the witness service's host system. This can be achieved by testing network connectivity with tools like ping or telnet on port 443.If the witness service is unreachable, then investigate whether the witness service's host is operational. Verify whether the IP address or hostname was recently changed on the host. If yes, please remove the witness service configuration from the PowerStore and reconfigure it using the new IP address or hostname. If the host is operational and the networking is operating normally then attempt to restart the witness service.If access is successful, then investigate potential networking issues on the PowerStore. Review any recent networking changes on the PowerStore which may be inhibiting connectivity. Additionally, it may be helpful to investigate the physical network connections (cards, cables, etc.) for all PowerStore appliances. If everything listed above is ok, attempt to delete the witness in PowerStore and repeat the registration process from the beginning.Lastly, investigate any changes in the network topology, such as changes in switch settings, routing tables, DNS, etc.

Support Cases