Users Guide

NOTE: When you modify the xml le, you must select one of the following severities:
• CRITICAL
• MAJOR
• MINOR
• WARNING
• INFORMATIONAL
If you want OS10 to generate the event, set the Enable ag to true. To turn o event notication, set the Enable ag to
false.
If you enter invalid values, the event severity-profile command fails.
4 Copy the custom prole to the OS10 switch.
OS10# copy scp://username:password@a.b.c.d/dir-path/mySevProf.xml severity-profile://
mySevProf_1.xml
When you copy the custom prole, you must update the name of the custom prole. You cannot use the same name as the default
prole (default.xml) or the active prole (mySevProf.xml).
5 Apply the custom severity prole on the switch.
OS10# event severity-profile mySevProf_1.xml
NOTE: You must restart the switch for the changes to take eect.
6 Restart the switch.
OS10# reload
7 Use the show event severity-profile command to view the custom prole that is active.
OS10# show event severity-profile
Severity Profile Details
--------------------------------------------
Currently Active : default
Active after restart : mySevProf_1.xml
Delete custom severity prole
You can delete custom severity proles that you no longer need. However, you cannot delete the default or active severity prole.
To delete a custom severity prole, use the delete severity-profile://profile-name command. For example:
OS10# delete severity-profile://mySevProf_1.xml
System logging
You can change the system logging default settings using the severity level to control the type of system messages that log. The range of
logging severities are:
• log-emerg — System is unstable.
• log-alert — Immediate action needed.
• log-crit — Critical conditions.
• log-err — Error conditions.
• log-warning — Warning conditions.
• log-notice — Normal but signicant conditions, the default.
• log-info — Informational messages.
• log-debug — Debug messages.
1354
Troubleshoot OS10