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
service@director-1-1-a:/etc/opt/dell/vplex>
● The cat firmware_events.yaml | grep legacyDbgEvents lists the supported conditionID vs legacy debug
events mapping.
service@director-1-1-a:~> cd /etc/opt/dell/vplex
service@director-1-1-a:/etc/opt/dell/vplex>
service@director-1-1-a:/etc/opt/dell/vplex> cat firmware_events.yaml | grep
legacyDbgEvents
legacyDbgEvents: [scsi/156, scsi/157]
legacyDbgEvents: [scsi/72, scsi/73]
legacyDbgEvents: [scsi/154, scsi/166]
legacyDbgEvents: [scsi/126]
legacyDbgEvents: [scsi/71]
legacyDbgEvents: [scsi/79]
legacyDbgEvents: [scsi/91]
legacyDbgEvents: [scsi/123]
legacyDbgEvents: [scsi/158]
legacyDbgEvents: [scsi/147]
legacyDbgEvents: [apf/15]
legacyDbgEvents: [scsi/138]
legacyDbgEvents: [scsi/167]
legacyDbgEvents: [amf/45, amf/96, amf/97, amf/98, amf/99, amf/100, amf/101, amf/
223]
legacyDbgEvents: [amf/20]
legacyDbgEvents: [amf/24]
legacyDbgEvents: [amf/126]
legacyDbgEvents: [amf/146]
legacyDbgEvents: [amf/111]
legacyDbgEvents: [amf/181]
legacyDbgEvents: [amf/190]
legacyDbgEvents: [amf/158]
legacyDbgEvents: [amf/221]
legacyDbgEvents: [amf/141]
legacyDbgEvents: [amf/197]
legacyDbgEvents: [amf/233]
legacyDbgEvents: [amf/251]
legacyDbgEvents: [amf/267]
legacyDbgEvents: [amf/34, amf/35, amf/51, amf/52, amf/53, amf/54, amf/55, amf/56,
legacyDbgEvents: [amf/215, amf/216]
legacyDbgEvents: [amf/215, amf/216]
legacyDbgEvents: [amf/162]
legacyDbgEvents: [amf/226]
legacyDbgEvents: [amf/249, amf/250]
legacyDbgEvents: [amf/250, amf/270]
legacyDbgEvents: [amf/244, amf/245, amf/246]
legacyDbgEvents: [amf/203]
legacyDbgEvents: [amf/201, amf/206, amf/219]
legacyDbgEvents: [amf/205]
legacyDbgEvents: [amf/202, amf/207, amf/220]
legacyDbgEvents: [com/11]
legacyDbgEvents: [com/40]
legacyDbgEvents: [com/52]
legacyDbgEvents: [nmg/49, nmg/50, nmg/59]
legacyDbgEvents: [nmg/100]
legacyDbgEvents: [nmg/56, nmg/57]
legacyDbgEvents: [nmg/64, nmg/65, nmg/66, nmg/67]
legacyDbgEvents: [nmg/96]
legacyDbgEvents: [nmg/107, nmg/108, nmg/109]
legacyDbgEvents: [nmg/105, nmg/106]
legacyDbgEvents: [nmg/112, nmg/117]
legacyDbgEvents: [nmg/113, nmg/117]
legacyDbgEvents: [nmg/114, nmg/117]
legacyDbgEvents: [stdf/32]
legacyDbgEvents: [stdf/53]
legacyDbgEvents: [stdf/59]
legacyDbgEvents: [stdf/25]
legacyDbgEvents: [stdf/29]
legacyDbgEvents: [stdf/39]
legacyDbgEvents: [stdf/26]
legacyDbgEvents: [stdf/30]
Troubleshooting
7