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
Question: What is the expected service status?
Answer
See the following:
sudo systemctl status notifications
service@director-2-1-b:~> sudo systemctl status notifications
● notifications.service - NotificationService
Loaded: loaded (/usr/lib/systemd/system/notifications.service; enabled; vendor
preset: disabled)
Active: active (running) since Thu 2020-10-29 05:19:26 UTC; 6 days ago
Main PID: 5040 (vplex_launch_no)
Tasks: 188 (limit: 4915)
CGroup: /system.slice/notifications.service
├─5040 /bin/bash /opt/emc/VPlex/notification/script/
vplex_launch_notification.sh
└─5041 /usr/bin/java -jar /opt/emc/VPlex/notification/com-dell-vplex-
notification-1.0-SNAPSHOT.jar
Nov 05 01:12:50 director-2-1-b vplex_launch_notification.sh[5040]: 01:12:50.593 [flink-
akka.actor.default-dispatcher-2] INFO akka.event.slf4j.>
Nov 05 01:12:50 director-2-1-b vplex_launch_notification.sh[5040]: 01:12:50.642 [flink-
metrics-2] INFO akka.event.slf4j.Slf4jLogger - Slf4jLog>
Nov 05 01:12:50 director-2-1-b vplex_launch_notification.sh[5040]: 01:12:50.923
[scheduling-1] DEBUG c.d.v.n.e.s.SystemEventProcessor - Found 0>
Nov 05 01:12:50 director-2-1-b vplex_launch_notification.sh[5040]: 01:12:50.926 [flink-
akka.actor.default-dispatcher-3] INFO akka.event.slf4j.>
Nov 05 01:12:50 director-2-1-b vplex_launch_notification.sh[5040]: 01:12:50.942 [flink-
metrics-2] INFO akka.event.slf4j.Slf4jLogger - Slf4jLog>
Nov 05 01:12:51 director-2-1-b vplex_launch_notification.sh[5040]: 01:12:51.267
[scheduling-1] DEBUG c.d.v.n.e.s.SystemEventProcessor - Fetched>
Nov 05 01:14:26 director-2-1-b vplex_launch_notification.sh[5040]: Hibernate: select
idracalert0_.id as id1_4_, idracalert0_.app_name as app_na>
Nov 05 01:14:26 director-2-1-b vplex_launch_notification.sh[5040]: Hibernate: select
idracalert0_.id as id1_4_, idracalert0_.app_name as app_na>
Nov 05 01:14:26 director-2-1-b vplex_launch_notification.sh[5040]: Hibernate: select
idracalert0_.id as id1_4_, idracalert0_.app_name as app_na>
Nov 05 01:14:46 director-2-1-b vplex_launch_notification.sh[5040]: Hibernate: select
idracalert0_.id as id1_4_, idracalert0_.app_name as app_na>
service@director-2-1-b:~>
sudo systemctl status kafka
service@director-2-1-b:~> sudo systemctl status kafka
● kafka.service - Apache Kafka server (broker)
Loaded: loaded (/lib/systemd/system/kafka.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2020-10-29 04:58:48 UTC; 6 days ago
Docs: http://kafka.apache.org/documentation.html
Main PID: 2114 (java)
Tasks: 93 (limit: 4915)
CGroup: /system.slice/kafka.service
└─2114 java -Xmx1G -Xms1G -server -XX:+UseG1GC -XX:MaxGCPauseMillis=20
-XX:InitiatingHeapOccupancyPercent=35 -XX:+ExplicitGCInvokesC>
Nov 04 23:37:49 director-2-1-b kafka-server-start.sh[2114]: [2020-11-04 23:37:49,533]
INFO [GroupMetadataManager brokerId=0] Removed 0 expired >
Nov 04 23:47:49 director-2-1-b kafka-server-start.sh[2114]: [2020-11-04 23:47:49,533]
INFO [GroupMetadataManager brokerId=0] Removed 0 expired >
Nov 04 23:57:49 director-2-1-b kafka-server-start.sh[2114]: [2020-11-04 23:57:49,533]
INFO [GroupMetadataManager brokerId=0] Removed 0 expired >
Nov 05 00:07:49 director-2-1-b kafka-server-start.sh[2114]: [2020-11-05 00:07:49,533]
INFO [GroupMetadataManager brokerId=0] Removed 0 expired >
Nov 05 00:17:49 director-2-1-b kafka-server-start.sh[2114]: [2020-11-05 00:17:49,533]
INFO [GroupMetadataManager brokerId=0] Removed 0 expired >
Nov 05 00:27:49 director-2-1-b kafka-server-start.sh[2114]: [2020-11-05 00:27:49,533]
INFO [GroupMetadataManager brokerId=0] Removed 0 expired >
Troubleshooting
9