Users Guide
Table Of Contents
- Dell EMC Storage Systems Events and Alerts Troubleshooting Guide for the metro node appliance
- Contents
- Troubleshooting
- Alerts and Logs
- Issue: Do not see a generated alert in Live Alerts for a generated event.
- Issue: Mapping the conditionID with firmware debug events
- Question: Threshold for metro node monitor alerts
- Question: What is the expected service status?
- Issue: How does a user can get the service dependencies of all notification-related services?
- Issue: Database connection error in the notifications service logs at start-up
- Question: Is there any limit to notification service retries?
- Issue: Alert is disabled
- Question: If NSFW is down, then how can a user identify it?
- Issue: Alerts in real time
- Question: How can a user read alerts from a node?
- Issue: SMTP server is not reachable.
- Question: When are the email notifications going to be sent?
- Question: What happens if the customer provides the wrong email ID?
- Question: Can a user change the state of an event to open from closed in UI?
- Question: How can a user map iDRAC alerts with the metro node port mapping?
- Issue: The iDRAC or monitor issue has been resolved but the alert is still in open state.
- Question: How can a user obtain the database schema details?
- Question: Is there a mapping for port level alerts between legacy and voyager?
- Question: Where a user can get the REST API notifications for all UI?
- Problem: The operational alert is not closed after 4 hours of created time.
- Issue: Service level failures
FC023 System Health SCSI Target FibreChannel Port <portId1> encountered an error, resulting in the generation of
excessive cores for the HBA. Disabling port <portId2>.
FC024 System Health SCSI Target FibreChannel Port <portId1> encountered an error and was unable to load firmware
for the HBA. Disabling port <portId2>.
FC025 System Health SCSI Target FibreChannel Port <portId1> encountered an error and was unable to access HBA
resources. Disabling port <portId2>.
FC102 System Health The <Controller> Port <Port> network link is down.
FC103 System Health The <controller ID> port <port ID> network connection is successfully started.
It is required to provide a mapping between the actual hardware controller/port location and metro node port naming
convention. It helps the customer/support personnel to understand which port is wrong, and it also helps in troubleshooting
with the help of generated alerts.
Port name format
<Port Type>-<PORT ID>
Where each field has the following possible values:
● Port Type:
○ IO- IO Port (front-end/back-end)
○ Communication Ports,
￭ LC- local-com
￭ WC- wan-com
￭ MC- mgmt-com
￭ EC- External Connection (SVC/CUST)
● PORT ID:
○ 00, 01, 02, 03
Issue: The iDRAC or monitor issue has been resolved
but the alert is still in open state.
Answer
There is no mechanism to generate all type of clear events which notify that the iDRAC or monitor issues have been resolved.
For more information related to iDRAC, see the iDRAC UI.
Question: How can a user obtain the database schema
details?
Answer
Database
Notification service is using the following database:
Database name
Tables Used by Purpose
notification
● alert_definition
● disabled_idrac_alert
● disabled_platform_alerts
● flyway_schema_history
Notification service
To store the alerts generated
through,
● SMS
14 Troubleshooting