I/G/D/C/B/A-Series Use of the 'set logging default severity x' Command

FAQ_User — Wed, 19 Feb 2014 00:01:00 GMT

Article ID: 14985

Products
I-Series
G-Series
D-Series
C5, C3, C2-Series
B5, B3, B2-Series
A4, A2-Series

Goals
Difference between the universal default severity and the application default severity.
Effect of using the '

code:

set logging default severity

' command, vs the '

code:

set logging application all level

' command.

Solution
There are unique logging severities (default value "

code:

") relevant to each supported log application; for example, with firmware 6.42.09.0005...G3(su)->show logging application

Application Current Severity Level
---------------------------------------------
89 CLIWEB 6
90 SNMP 6
91 STP 6
92 Driver 6
93 System 6
94 Stacking 6
95 RtrOspf 6
96 RtrMcast 6
97 RtrVrrp 6
112 UPN 6
118 Router 6

1(emergencies) 2(alerts) 3(critical)
4(errors) 5(warnings) 6(notifications)
7(information) 8(debugging)

G3(su)->
There is also one universal default logging severity (default value "

code:

"); for example, with firmware 6.42.09.0005...G3(su)->show logging default
Facility Severity Port
Defaults: local4 critical(3) 514
G3(su)->
A logging severity may be configured for each application, while severity-unconfigured applications remain at their default severity ("

code:

").
However, if the universal default logging severity is configured, then this value overrides the application default value ("

code:

").
Thus, the universal default logging severity while unconfigured affects nothing, but while configured affects severity-unconfigured applications.

Here is a configuration sequence which should make this clearer:

With no logging severity configurations, all applications log at severity 6.
If the universal logging default is then set to 5 ('
```
set logging default severity 5
```
'), then all applications log at severity 5.
If the STP application logging is then set to 4 ('
```
set logging application STP level 4
```
'), then STP logs at severity 4 and all other applications log at severity 5.
If the universal logging default is then returned to 3 ('
```
set logging default severity 3
```
'), then STP logs at severity 4 and all other applications log at severity 6.

Issued from a defaulted configuration, the '

code:

set logging application all level

' command in theory has the same effect as '

code:

set logging default severity

'. However, in the case of any undocumented events which log outside of the defined applications, the "catch-all" default severity level would be the only way to regulate such events.

In summary:

If you wish all applications to have the same non-default value, then set both the application severity and universal default severity (avoid the value "
```
3
```
").
If you otherwise are targeting one or more specific applications, then set the severity for those applications.

It is highly recommended that you do not use

code:

7(information)

code:

8(debugging)

logging for these products on a long-term basis. Not only does this result in much unimportant messaging that can obscure useful messaging, but over time it decreases system performance. So, use elevated logging levels if you must, while testing - then return them to default values.

It is highly recommended that you do permanently issue the '

code:

set logging local console enable file enable

' command. This provides reasonable syslog data in the output of a '

code:

show support

', while maintaining efficient system operation.

For systems running firmware 6.61.xx, see 14981.

topic I/G/D/C/B/A-Series Use of the 'set logging default severity x' Command in FAQs

I/G/D/C/B/A-Series Use of the 'set logging default severity x' Command