Dell PowerSwitch S4112F-ON EMC SmartFabric OS10 User Guide Release 10.5.1 - Page 1573

● MAJOR-A major error had occurred and requires escalation or notification. For example, a major alarm may trigger if an interface failure occurs, such as a port channel being down. ● MINOR-A minor error or noncritical condition occurred that, if left unchecked, might cause system service interruption or performance degradation. A minor alarm requires monitoring or maintenance. ● WARNING-A warning condition was observed, but it may or may not result in an error condition. ● INFORMATIONAL-An informational event had occurred, but it does not impact performance. Out of memory, temperature crossing a critical point, and so on, are examples of conditions when the system triggers an alarm. After the system recovers from the condition, the alarms are cleared. All stateful events of severity level CRITICAL, MAJOR, MINOR, or WARNING trigger alarms. However, you can customize the severity of events or turn off event notification using Severity profiles. Triggered alarms are in one of these states: ● Active-Alarm is raised and is currently active. ● Acknowledged-Alarm is raised; the user is aware of the situation and acknowledged the alarm. This alarm does not impact the overall health of the system or the system LED. Some alarms go directly from active to cleared state and require little-to-no administrative effort. You must acknowledge or investigate alarms with a high severity. OS10 stores all Active and Acknowledged alarms in the Current Alarm List (CAL), and archives all past events in the Event History List (EHL). Alarms in the CAL are cleared after a reload. The EHL is persistent and retains the archived events after a reload, reboot, or upgrade. The EHL can store a maximum of 86,000 events or 30 days of events, whichever is earlier. The system LED that indicates the status of the switch is based on the severity of the alarms in the CAL and it turns: ● Red-For CRITICAL or MAJOR alarms ● Amber-For MINOR or WARNING alarms ● Green-No alarms Severity profiles OS10 allows you to change the severity of events using severity profiles. A severity profile is a .xml file that defines the effective severity of events or disables the notification of events. OS10 comes with a default severity profile. You cannot modify or delete the default profile. However, OS10 allows you to define custom severity profiles. ● Default severity profile-All events are defined in the default profile. The default profile classifies the events as CRITICAL, WARNING, or INFORMATIONAL in severity. ● Custom severity profile-Contains events that you modify. You can classify events as CRITICAL, MAJOR, MINOR, WARNING, or INFORMATIONAL in severity. Events and their characteristics that are defined in the custom profile take precedence over the default profile. To create a custom severity profile, copy the default severity profile to a remote host and modify it. After the custom profile is created, copy it from the remote host to the OS10 switch and apply it. The custom profile takes effect after a system restart. NOTE: ● To customize severity profiles, your user account must have any one of the following privileges: System admin (sysadmin), security admin (secadmin), or network admin (netadmin). ● You cannot edit an active custom profile. To edit an active custom severity profile, select another severity profile and apply it. The severity-profile:// partition contains all the defined severity profiles. To view a list of severity profiles, use the dir severity-profile command. To delete a severity profile, use the delete command. You can delete all severity profiles except the default and active profiles. Troubleshoot Dell EMC SmartFabric OS10 1573