show log configuration target

show log configuration target {console | memory-buffer | nvram | primary-msm | primary-node | backup-msm | backup-node | session | syslog {ipaddress | ipPort | vr vr_name} {[local0...local7 ]}}

Description

Displays the log configuration for the specified target.

Syntax Description

console Show the log configuration for the console display.
memory-buffer Show the log configuration for volatile memory.
nvram Show the log configuration for NVRAM.
primary-msm Specifies the primary MSM.
Note: This parameter is available only on modular switches.
primary-node Specifies the primary node in a stack.
backup-msm Specifies the backup MSM.
Note: This parameter is available only on modular switches.
backup-node Specifies the backup-node in a stack.
session Show the log configuration for the current session (including console display).
syslog Show the configuration for the specified syslog target.
ipaddress Specifies the syslog IP address.
ipPort Specifies the UDP port number for the syslog target.
vr_name Specifies the virtual router that can reach the server IP address.
Note: User-created VRs are supported only on the platforms listed for this feature in the Feature License Requirements document..
local0 ... local7 Specifies the local syslog facility.

Default

If no options are specified, the command displays the configuration for the current session and console display.

If a virtual router is not specified, VR-Mgmt is used.

Usage Guidelines

This command displays the log configuration for the specified target. The associated filter, severity, match expression, and format is displayed.

Example

The following command displays the log configuration:

show log configuration target

The following is sample output from this command:

Log Target      : memory-buffer
Enabled ?   : yes
Filter Name : DefaultFilter
Match regex : Any
Severity    : Debug-Data (through Critical)
Format      : MM/DD/YYYY HH:MM:SS.hh <Severity:Component.SubComponent.Condit
ion>
Buffer size : 1000 messages
Log Target      : nvram
Enabled ?   : yes
Filter Name : DefaultFilter
Match regex : Any
Severity    : Warning (through Critical)
Format      : MM/DD/YYYY HH:MM:SS.hh <Severity:Component.SubComponent.Condit
ion>
Log Target      : console
Enabled ?   : no
Filter Name : DefaultFilter
Match regex : Any
Severity    : Info (through Critical)
Format      : MM/DD/YYYY HH:MM:SS.hh <Severity:Component.SubComponent.Condit
ion>
Log Target      : primary-msm
Enabled     : yes
Filter Name : DefaultFilter
Match regex : Any
Severity    : Warning (through Critical)
Log Target      : backup-msm
Enabled     : yes
Filter Name : DefaultFilter
Match regex : Any
Severity    : Warning (through Critical)
In the case that the alert is not configured:
X670V-48t.1 # sh log configuration
Debug-Mode: Disabled 

Log Target       : memory-buffer    
    Enabled      : yes    
    Filter Name  : DefaultFilter    
    Match regex  : Any    
    Severity     : Debug-Data (through Critical)    
    Format       : MM/DD/YYYY HH:MM:SS.hh <Severity:Component.SubComponent.Condition>
    Buffer size  : 1000 messages
    Percent Full : 60%
    Full Alert   : None 

Log Target       : nvram
    Enabled      : yes
    Filter Name  : DefaultFilter
    Match regex  : Any
    Severity     : Warning (through Critical)
    Format       : MM/DD/YYYY HH:MM:SS.hh <Severity:Component.SubComponent.Condition> 

Log Target       : console
    Enabled      : no 
    Filter Name  : DefaultFilter
    Match regex  : Any
    Severity     : Info (through Critical)
    Format       : MM/DD/YYYY HH:MM:SS.hh <Severity:Component.SubComponent.Condition>
In the case that the alert is configured and the percentage threshold is set to 90:
X670V-48t.1 # sh log configuration
Debug-Mode: Disabled 

Log Target       : memory-buffer
    Enabled      : yes
    Filter Name  : DefaultFilter
    Match regex  : Any
    Severity     : Debug-Data (through Critical)
    Format       : MM/DD/YYYY HH:MM:SS.hh <Severity:Component.SubComponent.Condition>
    Buffer size  : 1000 messages    
    Percent Full : 60%
    Full Alert   : 90% 

Log Target       : nvram
    Enabled      : yes
    Filter Name  : DefaultFilter
    Match regex  : Any
    Severity     : Warning (through Critical)
    Format       : MM/DD/YYYY HH:MM:SS.hh <Severity:Component.SubComponent.Condition> 

Log Target       : console
    Enabled      : no 
    Filter Name  : DefaultFilter
    Match regex  : Any
    Severity     : Info (through Critical)
    Format       : MM/DD/YYYY HH:MM:SS.hh <Severity:Component.SubComponent.Condition>
In the case that the buffer is currently wrapping and the percentage threshold is set to 90:
X670V-48t.1 # sh log configuration
Debug-Mode: Disabled 

Log Target       : memory-buffer
    Enabled      : yes
    Filter Name  : DefaultFilter
    Match regex  : Any
    Severity     : Debug-Data (through Critical)
    Format       : MM/DD/YYYY HH:MM:SS.hh <Severity:Component.SubComponent.Condition>
    Buffer size  : 1000 messages
    Percent Full : 100% (wrapping)
    Full Alert   : 90% 

Log Target       : nvram
    Enabled      : yes
    Filter Name  : DefaultFilter
    Match regex  : Any
    Severity     : Warning (through Critical)
    Format       : MM/DD/YYYY HH:MM:SS.hh <Severity:Component.SubComponent.Condition> 

Log Target       : console
    Enabled      : no 
    Filter Name  : DefaultFilter
    Match regex  : Any
    Severity     : Info (through Critical)
    Format       : MM/DD/YYYY HH:MM:SS.hh <Severity:Component.SubComponent.Condition>

History

This command was first available in ExtremeXOS 10.1.

The primary-msm and backup-msm options were first available in ExtremeXOS 11.0.

The ipPort parameter was first available in ExtremeXOS 11.0.

The local0 ... local7 keywords were made optional in ExtremeXOS 11.4.

The UDP-port parameter was added in ExtremeXOS 16.2.

Platform Availability

This command is available on all platforms.