JUNOSe 9.1.x System Event Logging Reference Guide > System Logging Overview > Monitoring Logging System Events

Monitoring Logging System Events

Use the show log configuration command to display your log configuration. Use the show log data command to display system events on your screen.

You can use the output filtering feature of the show command to include or exclude lines of output based on a text string you specify. See show Commands in JUNOSe System Basics Configuration Guide, Chapter 2, Command-Line Interface for details.

show log configuration

• Use to show the logging configuration on your system.
• Example 1—Factory defaults are set

host1#show log configuration

  log destination console severity WARNING

  log destination nv-file severity CRITICAL

  no log engineering

  log fields timestamp instance no-calling-task 

  no log severity 

        category            severity   verbosity   filters

-------------------------   --------   ---------   -------

NameResolverLog             ERROR      low                

aaaAtm1483Cfg               ERROR      low                

aaaEngineGeneral            ERROR      low                

aaaServerGeneral            ERROR      low                

addressServerGeneral        ERROR      low                

atm                         ERROR      low                

atm1483                     ERROR      low                

atmAal5                     ERROR      low                

bgpConnections              ERROR      low                

...

cliCommand                  NOTICE     low                

controlNetworkSlave         ERROR      low                

cops                        ERROR      low                

...

udpTraffic                  ERROR      low 

• Example 2—Individual log udpTraffic is set to warning

host1#(config)#log severity warning udpTraffic

host1##show log configuration

  log destination console severity WARNING

  log destination nv-file severity CRITICAL

  no log engineering

  log fields timestamp instance no-calling-task 

  no log severity 

        category            severity   verbosity   filters

-------------------------   --------   ---------   -------

NameResolverLog             ERROR      low                

aaaAtm1483Cfg               ERROR      low                

aaaEngineGeneral            ERROR      low                

aaaServerGeneral            ERROR      low                

addressServerGeneral        ERROR      low                

atm                         ERROR      low                

atm1483                     ERROR      low                

atmAal5                     ERROR      low                

bgpConnections              ERROR      low                

...

cliCommand                  NOTICE     low                

controlNetworkSlave         ERROR      low                

cops                        ERROR      low                

...

udpTraffic                  WARNING*   low                

* Default severity setting is overridden by the individual log severity 
setting.

• Example 3—Log severity is set to alert

host1#(config)#log severity alert

host1#show log configuration

    log destination console severity WARNING

    log destination nv-file severity CRITICAL

    no log engineering

    log fields timestamp instance no-calling-task 

    log severity ALERT

        category            severity   verbosity   filters

-------------------------   --------   ---------   -------

NameResolverLog             ALERT#     low                

aaaAtm1483Cfg               ALERT#     low                

aaaEngineGeneral            ALERT#     low                

aaaServerGeneral            ALERT#     low                

addressServerGeneral        ALERT#     low                

atm                         ALERT#     low                

atm1483                     ALERT#     low                

atmAal5                     ALERT#     low                

bgpConnections              ALERT#     low                

...

cliCommand                  ALERT#     low                

controlNetworkSlave         ALERT#     low                

cops                        ALERT#     low                

...

udpTraffic                  ALERT#     low                

* Default severity setting is overridden by the system-wide severity 
setting.

• Example 4—Individual log atm is set to severity warning

host1#(config)#log severity warning atm

host1#show log configuration

    log destination console severity WARNING

    log destination nv-file severity CRITICAL

    no log engineering

    log fields timestamp instance no-calling-task 

    log severity ALERT

        category            severity   verbosity   filters

-------------------------   --------   ---------   -------

NameResolverLog             ALERT#     low                

aaaAtm1483Cfg               ALERT#     low                

aaaEngineGeneral            ALERT#     low                

aaaServerGeneral            ALERT#     low                

addressServerGeneral        ALERT#     low                

atm                         WARNING*   low                

atm1483                     ALERT#     low                

atmAal5                     ALERT#     low                

bgpConnections              ALERT#     low                

...

cliCommand                  ALERT#     low                

controlNetworkSlave         ALERT#     low                

cops                        ALERT#     low                

...

udpTraffic                  ALERT#     low                

* Default severity setting is overridden by the system-wide severity 
setting.

* Default severity setting is overridden by the individual log severity 
setting.

show log data

• Use to display system events.
• Use keywords to select which events are displayed:

• category—Limits the display to a single log event category. See the CLI online Help for available categories.

• Example

host1#show log data category os

• delta—Limits the display to events that occurred after the time set with the log baseline command.
• nv-file—Displays the information that is currently logged to nonvolatile storage.

• Example

host1#show log data nv-file

logFile.temp: The system cannot find the file specified.

ALERT 09/12/2000 21:29:17 os: ASSERTION FAILED: file mplsNvs2.cc, line 789

ALERT 09/20/2000 02:18:06 os: ASSERTION FAILED: file osPool.cc, line 819

ALERT 09/20/2000 02:26:35 os: ASSERTION FAILED: file osPool.cc, line 819

ALERT 09/20/2000 02:44:33 os: ASSERTION FAILED: file osPool.cc, line 819

ALERT 09/20/2000 04:56:35 os: ASSERTION FAILED: file osPool.cc, line 819

ALERT 09/27/2000 03:10:25 os: ASSERTION FAILED: file

/sw0/sc/nvs/include/../nvMapBackend.h, line 235

ALERT 10/02/2000 04:05:42 os: ASSERTION FAILED: file osHeap.cc, line 439

ALERT 10/02/2000 04:08:04 os: ASSERTION FAILED: file osMessageQueue.cc, line

42, rip1

ALERT 10/12/2000 03:43:38 os: PANIC: file osSemaphore.cc, line 54

ALERT 11/01/2000 02:03:49 os: ASSERTION FAILED: file cliCommand.cc, line 195

• severity—Displays events that have a specific severity level.

• Example

host1#show log data severity notice

NOTICE 01/10/2001 00:59:50 os: config -- using running

NOTICE 01/10/2001 00:59:52 os: srp application, build date: 0x3a437424 (FRI DEC 22 2000 15:32:52 UTC)

NOTICE 01/10/2001 00:59:52 os: last reset: user reboot, reason: not specified

NOTICE 01/10/2001 00:59:52 os: OsIsrRegistrar: 0xb

NOTICE 01/10/2001 00:59:52 os: OsIsrRegistrar: 0xa

NOTICE 01/10/2001 00:59:52 os: OsIsrRegistrar: 0x2

• By combining keywords, you can further limit the information displayed. See the CLI online Help for information about the keywords available at each level.

host1#show log data nv-file severity alert