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
Relevant to
voyager
ID Name Called home Firmware
event
External RCA External Remedy
VPLEX BE port
and the switch.
port, especially
anything that has
been changed
recently. Reseat/
clean/replace the
hardware to
resolve the
problem. If the
problem persists,
and unable to
determine the
cause, then
contact DELL
Customer Service.
Yes 0x8a343013 stdf_19_WARNI
NG
Yes stdf/19 An enabled FE
port has gone
down as a
result of FC
cable pull,
switch reboot,
or disabling
switch port.
1. Check the FE
port status in
the /hardware/
ports context
of VPlexcli to
verify if it is still
in 'no-link'
state. If it is
the case, then
go to the next
steps.
2. Check the
switch and
ensure that it is
operational,
check the
switch logs for
errors that
indicate the
root cause of
the issue.
3. Check the
cabling and
SFPs along the
path, clean/
reset/replace
as needed.
No
0x8a369013 tach_19_CRITI
CAL
Yes tach/19 I/O fails due to
exchanges
timed out.
There might be
faulty hardware
on the I/O path.
Check for faulty
hardware with
following steps:
1. Identify the I/O
path specified
by the event.
2. Clean and
reseat the
cables on the
path.
3. If applicable,
check switch
stats to see if
any switch is
oversubscribed,
if so, try to
reroute some I/
O.
22 Troubleshooting