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
array and LUN
masking.
2. Check array
configuration
and the
physical
connections
between:
a. The VPLEX
BE Port and
the backend
switch
b. back-end
switch and
the array
3. Try cleaning, or
replacing
cable(s), or
SFPs in the
path to the
storage
volume.
If the issue
persists, then
contact Dell
Customer Support.
No
0x8a633004 FEBECOM_PA
TH_DESTROYE
D
No febecom/4 A
communication
path is
destroyed
because the
remote end of
the path cannot
be reached.
● Check the
state of the
COM port,
ensure it is
enabled.
● Check the
cable and the
SFP, ensure
that these are
properly
plugged in.
●
Check the
switch if
applicable,
ensure it is
operational and
the
corresponding
port is enabled.
If the issue
persists, then
contact Dell
Customer Support.
No 0x8a633008 FEBECOM_LIN
K_DOWN
Yes febecom/8 Link went down
on a LOCAL
COM port. It
could be due to
another director
in the cluster
experiencing a
restart/reboot,
or a
Use the
VPlexcli command
director
uptime to
check if a
director restart/
reboot correlates
with the time of
the event. Else,
check the status
18 Troubleshooting