Known Behaviour for Logging Level Configs

Components use the cli “logging level comp_name i0” to set their logging levels to non-default values. Each component can have different logging levels set as their default values. There is difference in behaviour between DME running config displayed and system level running config command.

Example for Configuring Logging Level ARP

Logging level default value for arp is 3:
switch(config)# logging level arp 3
switch(config)# show running-config arp | grep -i logging
switch(config)#

switch(config)# logging level arp 5
switch(config)# show running-config arp | grep -i logging
logging level arp 5
Here correctly the non-default value(i.e 5) appear ini running config.

Now the corresponding dme running-config commands:
switch(config)# logging level arp 3
switch(config)#
switch(config)# show system internal dme running-config dn sys/logging/loglevel/facility-arp | grep -i severity
"severityLevel": "errors"

switch(config)# logging level arp 5
switch(config)# show system internal dme running-config dn sys/logging/loglevel/facility-arp | grep -i severity

switch(config)#

Note: The DME running-config for any component’s logging level will always consider “logging level 5” as the default value and hence not display it on DME running-config. The logging level will display all other logging levels as non-default in DME running config.

If a replace operation is done from the container level, the operation fails with the following error:

logging level cfs : delete is not allowed Commit Failed

Note: This failure is for component cfs, but this could occur for any non-deletable Managed Object (MO).