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
legacyDbgEvents: [stdf/23]
legacyDbgEvents: [stdf/24]
legacyDbgEvents: [stdf/56]
legacyDbgEvents: [stdf/34]
legacyDbgEvents: [stdf/31]
legacyDbgEvents: [stdf/19]
legacyDbgEvents: [sfp/9]
legacyDbgEvents: [sfp/7]
legacyDbgEvents: [sfp/11, sfp/12]
legacyDbgEvents: [sfp/11, sfp/12]
legacyDbgEvents: [sfp/11, sfp/12]
legacyDbgEvents: [sfp/11, sfp/12]
legacyDbgEvents: [dios/20]
legacyDbgEvents: [dios/13]
legacyDbgEvents: [utl/16]
legacyDbgEvents: [vmg/1, vmg/2, vmg/3]
legacyDbgEvents: [vmg/29]
legacyDbgEvents: [ndu/3]
legacyDbgEvents: [nvol/5]
legacyDbgEvents: [nvol/6]
legacyDbgEvents: [nvol/7]
legacyDbgEvents: [nvol/9]
legacyDbgEvents: [floor/31]
legacyDbgEvents: [floor/32]
legacyDbgEvents: [ipc/18, ipc/19, ip/2, ip/3]
legacyDbgEvents: [udcom/3]
legacyDbgEvents: [fc/1]
legacyDbgEvents: [fc/8]
legacyDbgEvents: [fc/13]
legacyDbgEvents: [fc/14]
legacyDbgEvents: [fc/15]
legacyDbgEvents: [fc/16]
legacyDbgEvents: [fc/17]
legacyDbgEvents: [fc/24]
legacyDbgEvents: [fc/25]
legacyDbgEvents: [fc/29]
legacyDbgEvents: [fc/30]
service@director-1-1-a:/etc/opt/dell/vplex>
Question: Threshold for metro node monitor alerts
Answer
See the following:
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 vplex-partition-monitor.yaml
thresholds: {
/dev/sda1: {warning: 80, critical: 90},
/dev/sda2: {warning: 80, critical: 90},
/dev/sda4: {warning: 80, critical: 90},
/dev/sda7: {warning: 80, critical: 90},
/dev/sda8: {warning: 80, critical: 90},
/dev/sda9: {warning: 80, critical: 90},
/dev/sda10: {warning: 80, critical: 90}
}
service@director-1-1-a:/etc/opt/dell/vplex>
8
Troubleshooting