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
Issue: Do not see a generated alert in Live Alerts for a
generated event.
Solution
Check the followings:
● Alert for condition_id is supported.
● Alert for condition_id is enabled.
● Alert for a component is enabled.
● The notifications service is enabled.
● In troubleshooting, see the notification stack.
Issue: Mapping the conditionID with firmware debug
events
Solution
Run cd /etc/opt/dell/vplex.
● The cat firmware_events.yaml provides the brief description about the conditionID.
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> vi firmware_events.yaml
- conditionId: '0x00120003'
conditionName: PathDisconnected
eventType: operational
objectType: CommunicationsPath
scope: director
severities:
- severity: critical
message: A communications path has been disconnected.
externalRCA: |-
A communications path has been disconnected due to network
connectivity issues.
externalRemedy: |-
Check the WAN COM or LOCAL COM path that was disconnected, then check
the switch logs for errors that will help pinpoint the root cause.
If errors point to hardware issues check/clean/replace the cables and
SFPs along the path. Engage Dell EMC Customer Support if unable to
determine the root cause.
callHome: true
enableDuringNDU: false
threshold: {count: 0, interval: 0}
additionalData:
- key: pathName
type: str
category: communicationsPathName
required: true
supplementalKey: false
- key: nodeUUID
type: uint
category: uuid
format: 0x%lx
required: true
supplementalKey: false
legacyDbgEvents: [udcom/3]
6
Troubleshooting