I reviewed the logs. While researching the warning, I found below information. Ensure you are running the latest firmware version for the switch. You can check the switch configuration and resource utilization to identify any bottlenecks. There are a configuration issue, a bug in the switch firmware, or a high volume of traffic.
ALM messages
This section lists the event and alarm management system log messages.
Table 1. ALM system log messagesALM system log messages
System log message
Severity
Description
Recommended action
ALM_ACCNT_EVENT: Accounting event was raised
INFORMATIONAL
Indicates a user login. When AAA accounting is configured, these logs are displayed for each user login.
No action is required.
ALM_AUTH_EVENT: Authentication event was raised
INFORMATIONAL
Indicates that user authentication was successful.
No action is required.
ALM_CLOCK_UPDATE: Clock changed
INFORMATIONAL
Indicates that system clock is changed.
No action is required.
ALM_HISTORY_PURGED: Older version of the alarm history detected, will be purged
INFORMATIONAL
Indicates that OS10 does not persist alarm history beyond Release 10.4.3.0.
No action is required.
ALM_SEQUENCE_ROLLOVER: OS10 Event sequence number rollover occured
INFORMATIONAL
Indicates that the event sequence is rolled over.
No action is required.
ALM_SYSTEM_RESTART:OS10 Event and Alarm management system restarted
INFORMATIONAL
Indicates that OS10 event and alarm management system is restarted.
Did you ever find a solution to this? We have a pair of Dell S5232F switches in VLT, were yours in VTL as well? ( I assume so as I see you mentioned its okay if its one at a time but not ideal )
We initially thought its triggered by a Nessus scan - but starting to think its a side affect of the nessus scan causing other devices to have network issues, which then are impacting the switches and causing the alarm / restart.
To be honest, there are a lot of troubleshooting needed to identify the root cause of the restart. As I know of, clients or servers which are connected to the switch which are rebooted or having error would not cause the switch itself to reboot.
My suggestion to check the switch logs and the server logs, to compare the time strap and find the root cause. If possible, you can contact the support for logs analysis.
DELL-Erman O
Moderator
•
3K Posts
0
May 9th, 2024 07:29
Hello,
I reviewed the logs. While researching the warning, I found below information. Ensure you are running the latest firmware version for the switch. You can check the switch configuration and resource utilization to identify any bottlenecks. There are a configuration issue, a bug in the switch firmware, or a high volume of traffic.
ALM messages
This section lists the event and alarm management system log messages.
Hope that helps!
Basil-WT
1 Rookie
•
4 Posts
0
January 8th, 2025 22:10
Did you ever find a solution to this? We have a pair of Dell S5232F switches in VLT, were yours in VTL as well? ( I assume so as I see you mentioned its okay if its one at a time but not ideal )
We initially thought its triggered by a Nessus scan - but starting to think its a side affect of the nessus scan causing other devices to have network issues, which then are impacting the switches and causing the alarm / restart.
DELL-Joey C
Moderator
•
4.1K Posts
0
January 9th, 2025 08:27
Hi,
To be honest, there are a lot of troubleshooting needed to identify the root cause of the restart. As I know of, clients or servers which are connected to the switch which are rebooted or having error would not cause the switch itself to reboot.
My suggestion to check the switch logs and the server logs, to compare the time strap and find the root cause. If possible, you can contact the support for logs analysis.