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
Logs
The notifications log verifies the event processing. Events that are received from the NSWF can be verified by checking out the
Kafka logs.
The alerts also contain the various fields which narrow down the cause, component, and resource of the events. Also, the
properties panel contains the corrective action that can be taken to resolve the issues.
Logs path
Notification logs directory - /var/log/vplex/notification/
Kafka(Broker) logs directory- /var/log/kafka/EventsTopic-0/
Postgres logs - /var/log/postgresql
telegraf.log - /var/log/telegraf/
From CD
After performing collect-diagnostics, the CD file generates at /diag/collect-diagnostics-out/{GUID}-{cluster}-
diag-yyyy-mm-dd-HH.MM.SS.tar.gz. After untarring the CD file, the files for all the directors are in the
collect_{director}_yyyy-mm-dd-HH.MM.SS.tar.gz format. Untarring the director level tar.gz file gives all the
desired logs with the paths mentioned in the earlier Logs section. For example, the postgres logs are collected in /diag/
collect-diagnostics-out/collect_director-1-1-a_2020-10-28-15.31.23/var/log/postgresql. For all
other components, see the following table:
Feature
Old log location New log location (file name and
directory)
Log location in CD
system config - system_config.log - /var/log/
vplex/system_config
-
NDU - /var/log/VPlex/cli/capture/
vplex_node_software_upgrade
log: /var/log/vplex/
vplex_node_software_upgrade.log
/mgmt_server/cluster-1/
upgrade/
CLI
Refer : /var/log/VPlex/cli/
Files: audit.log_*,client.log_*,
capture.log_*
Refer : /var/log/VPlex/cli/
Files: audit.log_*,client.log_*,
capture.log_*
Refer: /
diag/collect-diagnostics-out/
smsLogs/clilogs
Files: audit.log_*,client.log_*,
capture.log_*
UI /var/log/VPlex/cli/restful.log_* /var/log/VPlex/cli/restful.log_* /diag/collect-diagnostics-out/
smsLogs/clilogs/restful.log_*
Restv2 /var/log/VPlex/cli/restful.log_* /var/log/VPlex/cli/restful.log_* /diag/collect-diagnostics-out/
smsLogs/clilogs/restful.log_*
notification -
notifications.log - /var/log/vplex/
notification/
Kafka(Broker) logs
directory- /var/log/kafka/
EventsTopic-0/
Postgres logs - /var/log/
postgresql
telegraf.log - /var/log/telegraf/
/diag/collect-diagnostics-
out/collect_director-1-1-
a_2020-10-28-15.31.23
dreamcatcher -
dreamcatcher.log - /var/log/
vplex/SupportAssist
ESE.log : /opt/dell/
vplex/ese/var/log/
-
Troubleshooting 5