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
Postgres Kafka Telegraf Notification Result Comments
it restarts the
Telegraf also.
Up Down Down Down FAIL Events are not
received. If the
Kafka, Telegraf,
and Notifications
are crashed/killed,
then it restarts
automatically.
Down Up Up Up FAIL Events are
buffered in Kafka
and pushed to
notification service
once it is up.
Events are not
lost. Notification
tries to reconnect
to the Postgres(db
storing fails). If
the Postgres fails
because of some
error, and then the
flink tries to restart
notifications for 10
times. After that
if it is not able
to connect to the
db, it stops the
notifications.
Down Up Up Down PASS Events are stored
in Kafka. Once
Postgres and
Notification is up,
then the events
start coming in.
Down Up Down Up FAIL Events are not
received until all
the services are up.
Down Up Down Down FAIL Events are not
received until all
the services are up.
Down Down Up Up FAIL Events are
buffered in
Telegraf based
on the buffer
size. If Kafka
is still unavailable
after the buffer
limit is reached,
Telegraf starts
discarding the
incoming events.
Down Down Up Down FAIL Events are
buffered in
Telegraf based
on the buffer
size. If Kafka
is still unavailable
42 Troubleshooting