copy logging

copy logging

Filters the current log file messages and concatenates the filtered messages into a new file.

Syntax: copy logging filename [from {[hh:mm][:ss] [month dd] [year]}] [to {[hh:mm][:ss] [month dd] [year]}] [platform {all | server server_id | bay baynum/controllernum | module baynum/slotnum}...] [[system system] [level level]...]

filename

Name of the new file (path optional) used by this command.

from hh:mm:ss month dd year

Changes the starting output time to the time and date specified.

The time field is in hours (hh), minutes (mm) and seconds (ss) in twenty-four hour time.

The date field consists of month (spelled out completely), day (enter two digits) and year (enter four digits.) Year is optional. Default: earliest date and time found in the files.

to hh:mm:ss month dd year

Changes the ending output time to the time and date specified.

The time field is in hours (hh), minutes (mm) and seconds (ss) in twenty-four hour time.

The date field consists of month (spelled out completely), day (enter two digits) and year (enter four digits.) Default: earliest date and time found in the files.

server server_id

ID of server you want to copy logs from.

bay baynum/
controllernum

The bay option follows the platform field if you are filtering for a bay controller.

baynum is the number of the bay on which this controller resides.

controllernum is the number of the controller to configure. This release supports two bay controllers numbered 1 and 2.

module baynum/slotnum

The module option follows the platform field if you are filtering for a module.

baynum defines the bay number in which this module is located.

slotnum defines the slot number to filter. Slots are numbered from 1 to 40 beginning at the top left of the machine. Each physical slot is numbered on the hardware for reference.

system

The source logging subsystem of the events to write to file. You can enter multiple system statements, delineated by a space. In the case of multiple system statements, enter the complete system and level statement for each system. Default: all subsystems.

level

All messages at or above the specified level are written to file. Default: all log messages.

Description: To write messages from the current log files into a new file, use the copy logging command. The copy logging command allows for specifying the start and end date of the messages to be copied. Messages written to the new file are in time order.

Factory Default: None.

Command Mode: Privileged.

Example 1: The following command line will create a file named ctrsrv1.log and search the current log files for all messages between January 4th through the 12th for all platforms for all subsystem messages at or above the warning severity level.

router#copy logging ctrsrv1.log from January 04 1999 to January 12 1999 platform all level warning

router#

Example 2: The following command line will create a file named critical.log and search the current log files for all messages on January 12th for all modules for all OS subsystem messages at the critical severity level.

router#copy logging critical.log from January 12 1999 to January 12 1999 platform module all system os level critical

router#

Related Commands: logging

filename	Name of the new file (path optional) used by this command.
from hh:mm:ss month dd year	Changes the starting output time to the time and date specified. The time field is in hours (hh), minutes (mm) and seconds (ss) in twenty-four hour time. The date field consists of month (spelled out completely), day (enter two digits) and year (enter four digits.) Year is optional. Default: earliest date and time found in the files.
to hh:mm:ss month dd year	Changes the ending output time to the time and date specified. The time field is in hours (hh), minutes (mm) and seconds (ss) in twenty-four hour time. The date field consists of month (spelled out completely), day (enter two digits) and year (enter four digits.) Default: earliest date and time found in the files.
server server_id	ID of server you want to copy logs from.
bay baynum/ controllernum	The bay option follows the platform field if you are filtering for a bay controller. baynum is the number of the bay on which this controller resides. controllernum is the number of the controller to configure. This release supports two bay controllers numbered 1 and 2.
module baynum/slotnum	The module option follows the platform field if you are filtering for a module. baynum defines the bay number in which this module is located. slotnum defines the slot number to filter. Slots are numbered from 1 to 40 beginning at the top left of the machine. Each physical slot is numbered on the hardware for reference.
system	The source logging subsystem of the events to write to file. You can enter multiple system statements, delineated by a space. In the case of multiple system statements, enter the complete system and level statement for each system. Default: all subsystems.
level	All messages at or above the specified level are written to file. Default: all log messages.

router#copy logging ctrsrv1.log from January 04 1999 to January 12 1999 platform all level warning router#

router#copy logging critical.log from January 12 1999 to January 12 1999 platform module all system os level critical router#

   Source File Name: Logging.fm
    HTML File Name: Logging4.html
    Last Updated: 02/25/05 at 14:31:54

copy logging

Please email suggestions and comments to: doc@avici.com